Develop Bugs

[Q] SCH-I435 (Verizon) Anyway to get custom recovery?

Hello everyone, please be patient with me as I am relatively new to modifying phones. However, I have spent a good portion of the past 1-2 weeks looking into this problem on XDA + google, and I am at the end of my rope.
Here is my problem (I'm sure you already know):
I have no current solution to installing a custom recovery on my phone. I really just want custom recovery to restore FULL backups via Nandroid or equivalent.
Here are my questions:
1) In download mode, Odin has no problem flashing an official image/firmware (tar.md5) to the phone. Is it possible to create my own image of my phone into one file and flash it via Odin to my phone when I would like to restore? I have a feeling that something in the phone checks the hash of the image (I'm sure that I'm not saying it right), and that, considering my image would be twice the size of the official, there would be no way to make my image pass using collisions or what not. However, this would probably be my first choice after safestrap (assuming that won't work), so let me know.
2) I have read that certain people with phones similar to mine (not my variant though) have successfully "swapped" the external and internal SD cards. If I remember correctly they just change a couple lines in void.fstab. If this could actually be done, I could easily restore a backup to the now external internal SD, then change the settings to reswap on reboot. I feel like this is too good to be true though, as I have not seen this as a solution to my specific problem online. Is this actually a suitable option?
3) Currently my phone model is not an officially recognized device which Safestrap will work on. However, I have read that it is possible to do on my model using the Safestrap version which corresponds to a close variant of my phone. Can this be done? Please let me know if you have any information on this.
4) I guess this would be the last resort. I'm pretty good at taking things apart, but even better I can put those things back together Is the internal "SD" really just an SD card deep inside the phone? Would it be possible to replace that card for the purpose of backing up?
Here are my phone specs:
-Samsung Galaxy S4 Mini (SCH-I435)
-The carrier is Verizon Wireless
-Android Version 4.4.2 (kitkat)
-Baseband Version I435VRUBOC1
-Kernel Version 3.4.0 [email protected] #1 Fri May 23 2014
-Build Number KOT49H.I435VRUBOC1
-Hardware Version I435.05
-Configuration version B13.SAM.SCHI435.0
-Needless to say, phone is rooted and has busybox + etc correctly installed.
Any help will be greatly, GREATLY appreciated -- even if that help is telling me that it isn't possible. I can't seem to give up on this.
Thanks,
Kurt

Help
Does anyone have any advice on this? I would REALLY appreciate it. Thanks again.
-Kurt

I'm also interested on this. Thanks for your efforts

Nope no recovery because the Verizon minis bootloader is locked. It can be rooted with kingroot i think its called and then switched to SuperSU by replacing it.(I used super sume pro to get rid of kr) ****!!After root install a application like "disable application [root]" and disabe all Knox applications and any unused apps.(look for a list of recommended apps to disable)

Kannz2 said:
Nope no recovery because the Verizon minis bootloader is locked. It can be rooted with kingroot i think its called and then switched to SuperSU by replacing it.(I used super sume pro to get rid of kr) ****!!After root install a application like "disable application [root]" and disabe all Knox applications and any unused apps.(look for a list of recommended apps to disable)
Click to expand...
Click to collapse
How did you switch it over to SuperSU? I tried, but when it tried updating the root binaries it couldn't continue because of KNOX, so I was stuck with Kingoroot's.

I used this method to replace KINGROOT NewKingrootV4.50_C120_B220_xda_release_2015_07_22_105243 with supersu. most other versions i tried didnt want to cooperate and would make me lose root after one reboot. also i bought the pro version of supersume pro its 4$ off google play.

Kannz2 said:
I used this method to replace KINGROOT NewKingrootV4.50_C120_B220_xda_release_2015_07_22_105243 with supersu. most other versions i tried didnt want to cooperate and would make me lose root after one reboot. also i bought the pro version of supersume pro its 4$ off google play.
Click to expand...
Click to collapse
I tried it with the free version they linked to and it de-rooted it, so maybe I'll try later when I have enough Opinion Rewards credit to get the pro version. That or it doesn't work on this phone with Kingoroot. (The Google Play description says it should do Kingoroot though.)

Did you download the correct version? The one off the kingroot site doesn't work for me. It just deroots. I still have root on both of my s4mini Verizon phones. Try this link to get a working one.HERE scroll down a bit and the different versions are there. Try each one starting with 4.5. Also remember to restart after you root with kingroot and install super sume after the restart.

I just had to re-image my phone, so I did it according to your directions. (Though with the free version still of super sume) and it worked, although it won't update to the newest root binaries. It fails when I try. Did you have this issue? Other than that, SuperSU works.

I updated using "normal" and it worked fine for me. Glad su works at least. also for one phone I did a full unroot factory reset and then I reflashed a tar with Odin. Did the normal root with kingroot 4.5. Restarted tried a few root things like no frills cpu thing then installed super sume pro. Did stage 1. An 2 then supersu started up automatically it asks to update (I think net connection is needed) *do update "normal" because there isnt any recovery. Uninstalled kingroot like supersume says. Did a few root things then restarted. (Checked for superuser after reboot and it stayed)

Uconnect App on Pie

Pixel 2 XL on 9.0
Bootloader Unlocked
TWRP Recovery
Rooted via Magisk 17.1
The Uconnect app for my Jeep no longer functions because the new version for Android 9.0 checks for an unlocked bootloader or root. When trying to login to the Uconnect app, I receive a popup that states I'm using an unapproved device. When contacting the developer, they claim that it's because my device is a security threat. I've tried Magisk Hide to no avail.
Any suggestions?

Same thing here too. I have an older S6 Edge + running a rooted Android 7.0 with Magisk 17.1. Magisk Hide doesnt fix it as well.

having this issue as well with the latest uConnect app. Pixel 2XL is rooted and unlocked. I loaded the latest stock firmware 9.0 and tried the uConnect app prior to rooting and it works on my end, but still a no-go once Magisk is installed. I even tried the magisk hide and the module that can alter prop to further hide magisk and no go. I think it may be that it is looking for root and is awfully good at finding it. If anyone can get this to work, would be great! I dont get why FCA is so worried about root. One would think that since we have to go through a VERY specific sequence to get root and unlock the bootloader, that we would have quite a grip on what goes on with our phones. Anyways, if someone comes up with something......

Uconnect is detecting Magisk Manager. You have to uninstall it in order for Uconnect to work.

Well that sucks

I ran into something like this, but it was because I had an old version of the app. I uninstalled Uconnect completely and re-installed. After the re-install it was a new blue colored logo instead of the black one and has a different layout.
Not sure if this is the same problem, but figured I'd mention it.

TechnovationLLC said:
I ran into something like this, but it was because I had an old version of the app. I uninstalled Uconnect completely and re-installed. After the re-install it was a new blue colored logo instead of the black one and has a different layout.
Not sure if this is the same problem, but figured I'd mention it.
Click to expand...
Click to collapse
And you are rooted?

CyberpodS2 said:
And you are rooted?
Click to expand...
Click to collapse
I tested root and non rooted. Both seemed to function fine for me. I initially thought rooted might be the issue for me, but it ended up being the old app.

Fresh install from play store gets me this.

Perhaps see if you can hunt down an older version apk and sideload that. That happens to me from time to time. Always has. Across different devices.

MrWhite0429 said:
Perhaps see if you can hunt down an older version apk and sideload that. That happens to me from time to time. Always has. Across different devices.
Click to expand...
Click to collapse
Sadly, if I install an older version it prompts to update with no way around it... If anyone knows a version that works please post here.

Wondering if a logcat would help to pinpoint the issue and assist the magisk developer with a fix.

MrWhite0429 said:
Perhaps see if you can hunt down an older version apk and sideload that. That happens to me from time to time. Always has. Across different devices.
Click to expand...
Click to collapse
The old (black) version of the app doesn't work with 9.0

Very discouraging
I am using black version for now this is very discouraging though. The new app version would be nice working because the black looks as though they won't be updating it anymore.

Viol8ter said:
I am using black version for now this is very discouraging though. The new app version would be nice working because the black looks as though they won't be updating it anymore.
Click to expand...
Click to collapse
Which version of Android are you on and which app version? Thanks!

lu270bro said:
Which version of Android are you on and which app version? Thanks!
Click to expand...
Click to collapse
I am on 8.0. Though I read somewhere someone said to hide the magisc manger with random name and it worked after clearing app cache. I'm happy and thankyou.

Same issue on my OnePlus 5T, the Black Icon version cannot connect to the network on Pie and the new Blue Icon is detecting something. I think it detects the unlocked bootloader, I tried to repackage Magisk Manager and it had no effect.

Machine318 said:
Same issue on my OnePlus 5T, the Black Icon version cannot connect to the network on Pie and the new Blue Icon is detecting something. I think it detects the unlocked bootloader, I tried to repackage Magisk Manager and it had no effect.
Click to expand...
Click to collapse
I have never been able to get it working on this phone since the blue icon change. Sucks...

why does a car/radio company care what a joke glad i dont have a car with unconnect

OK boys and girls. I think I found a fix. might not work for all of you, but I got the App to load and let me in.
I'm running the latest Pie version, Magisk 18.1 (Riru - Core v16, Riru - Ed Xposed) and XPrivacyLua (xposed module)
in XPrivacyLua for the Uconnect App, I restricted, Get Applications. Uconnect Logs in.

5T would rooting gain access to Samsung gear and control Gear 2 (R280) & Gear 360?

5T would rooting gain access to Samsung gear and control Gear 2 (R280) & Gear 360?
I've looked all over for a tutorial.
TIA.

Yes it should. I assume your problem is these apps don't show up for you in the app store or they say they aren't compatible with your device? I had that issue with my 6T and my Gear S3. If that is indeed the case you just need to root with Magisk and use:
Magisk Hide Props Module
That module will let you change your device fingerprint to a certified one or something else if necessary. I can test this theory tonight on a rooted 5T with this module if you know what apps you are looking for. (I know what apps are needed for my Gear S3)
Both Magisk and that Module are installed in TWRP. However that module is activated and run from a terminal emulator on the phone. Personally I use this one:
Terminal Emulator
Once running that type:
su <--Hit enter, hit ok when Magisk asks, this will give terminal emulator root.
Now type:
props <--This runs the module you will now get menus choose pick certified fingerprint. It should be pretty self explanatory from here. Any questions ask.
Normal Magsik stuff I recommend hiding Google stuff from Magisk and renaming it with a random name.

Yea, Tried using Wear but doesn't find the R-280 or Gear 360. I remember a modded Gear apk a while back but it didn't work non-root.
So I should root. Is there a good tutorial link that incorporates this props list in the process? Or what rom would be good for this?
I've fairly familiar with the rooting process but it's been a bit.
Thanks for your help.

I've found on several devices now, that sometimes, my cars, headsets, watches, may not pair if the device has been on for some time. A restart and all the sudden everything connects no issue. My Gear S3 is no exception. Restart the phone and my watch and all the sudden it finds it. Your location can be off (my is always off except when using navigation), but those apps do need location permission.
Your best bet is to use FunkWizard's Guide. It doesn't have the props module stuff in it, however once TWRP is installed and you flash magisk, it's just reboot once so magisk will be installed, fully, and then go back to recovery. Then flash the module, then flash busy box. You'll be good to go. (I did realize I left out an important piece of information, that module needs BusyBox to work. You can get that here at the bottom of this post. <-- That BusyBox installer is also installed in TWRP. )
As for ROMs I use Lineage on everything. The privacy guard is the big seller for LOS for me. However that props module works in OOS, on the 5T I used it until LOS came out, back when it was first released. Also used it on my 6T until LOS was fully working with my watch. So all this stuff should work fine in OOS if you want to stay "stock".

Hmm. Got a Havoc installed and Magisk 19. "props not found" when typed in terminal after giving SU permissions. Any ideas?
Also, Anyone know where to download the older Samsung Gear apks or what apps to use for pairing the devices I mentioned?
Thanks again!

djphooka said:
Hmm. Got a Havoc installed and Magisk 19. "props not found" when typed in terminal after giving SU permissions. Any ideas?
Also, Anyone know where to download the older Samsung Gear apks or what apps to use for pairing the devices I mentioned?
Thanks again!
Click to expand...
Click to collapse
When you go into Magisk go to Modules in the menu, does the MagiskHide PropsConfig and BusyBox appear under Modules? I would guess they do not if "props" does not work.
Have you ever used APK Mirror ? It is a very handy site sometimes. It's from Android Police, so at least it's not a completely unknown source. That's not to say you shouldn't use direct sources whenever possible.

OhioYJ said:
Yes it should. I assume your problem is these apps don't show up for you in the app store or they say they aren't compatible with your device?
Click to expand...
Click to collapse
What do I do now? I have Magisk running busybox and props.
Galaxy Wear doesn't find my watch. Isn't there an older version available that might?

djphooka said:
What do I do now? I have Magisk running busybox and props.
Galaxy Wear doesn't find my watch. Isn't there an older version available that might?
Click to expand...
Click to collapse
I don't know that version would help, but you can try other versions on ApkMirror if you want. I know even in stock form connecting my watch sometimes takes some persistence. Sometimes it takes rebooting both devices to get it recognized, sometimes it just a matter of going back and forth and scanning multiple times. It basically never finds it the first time. Been through it many of times, as you can't just reconnect a the watch after a clean install, it's always completely reset the watch and reconnect as a new device.

Google pay / etc

After finally getting a ROM installed, I found out that Google pay won't work, along with Samsung pay in the Galaxy watches.
They know the system is rooted and what not I even tried to use magisk hide but it doesn't seem to work for these apps. Is there anyway I can restore this functionality?

Magisk Hide is useless for Google Pay it'll still detect your phone if its still rooted. There's a magisk module called GPay SQlite it pretty much patches the part where google tries to detect if the device is rooted. I've been using this module for a long time and hasn't failed once on me, its definitely worth your time installing this one.
Here's the link to the forum which has the download on there.
https://forum.xda-developers.com/showpost.php?p=79643248&postcount=176

xSpartacusx said:
After finally getting a ROM installed, I found out that Google pay won't work, along with Samsung pay in the Galaxy watches.
They know the system is rooted and what not I even tried to use magisk hide but it doesn't seem to work for these apps. Is there anyway I can restore this functionality?
Click to expand...
Click to collapse
I have a Gear S3 and it seems to work well ONLY if you hide Magisk Manager and then use Magisk hide Samsung Pay. This is as of a couple weeks ago when all the bootloader unlock detection was happening. I haven't tried since then. You can fail CTS/Safetynet, but still get Samsung Pay to work.

Knxed_ said:
Magisk Hide is useless for Google Pay it'll still detect your phone if its still rooted. There's a magisk module called GPay SQlite it pretty much patches the part where google tries to detect if the device is rooted. I've been using this module for a long time and hasn't failed once on me, its definitely worth your time installing this one.
Here's the link to the forum which has the download on there.
https://forum.xda-developers.com/showpost.php?p=79643248&postcount=176
Click to expand...
Click to collapse
There's like 50 links. There which do I download?

xSpartacusx said:
After finally getting a ROM installed, I found out that Google pay won't work, along with Samsung pay in the Galaxy watches.
They know the system is rooted and what not I even tried to use magisk hide but it doesn't seem to work for these apps. Is there anyway I can restore this functionality?
Click to expand...
Click to collapse
Only reason why I have yet to root my Pixel 2 XL.

Ya im not sure how to fix GPay on this device!

xSpartacusx said:
There's like 50 links. There which do I download?
Click to expand...
Click to collapse
This link here is the most up to date version of the GPay patch, this will link you the download. You gotta flash it through recovery to get it working.
https://github.com/stylemessiah/GPay-SQLite-Fix/releases/download/v2.0/GPay.SQLite.Fix.v2.0.zip

Xposed Framework+Root Cloak

A banking app does not run because of a rooted device.
have Magisk 23.0, tried MagiskHide.....no joy.
Google search resulted another option Xposed Installer+RootCloak
Downloaded and run Xposed 3.1.5....not installed, no matching zip were found.
Phone is an LG G4 H812, flashed with Pixel Experience Android 9, detected as an LG-H815.
Any suggestion on how to get Xposed+RootCloak installed ? or any other way to trick banking app?
Thanks!

jeno1957 said:
A banking app does not run because of a rooted device.
have Magisk 23.0, tried MagiskHide.....no joy.
Google search resulted another option Xposed Installer+RootCloak
Downloaded and run Xposed 3.1.5....not installed, no matching zip were found.
Phone is an LG G4 H812, flashed with Pixel Experience Android 9, detected as an LG-H815.
Any suggestion on how to get Xposed+RootCloak installed ? or any other way to trick banking app?
Thanks!
Click to expand...
Click to collapse
The trick is:
Install magisk
Go in magisk settings and repackage magisk to hide it
Install your banking app but do NOT start it
Hide magisk for that app in magisk settings
Install Insular or Shelter
Use insular/shelter to clone the banking app into the work profile
Start the banking app from within insular/shelter so that it starts from the working profile NOT from regular android
Enjoy.

Thanks for your reply.
Although x-posed framework developing stopped, managed to find an unofficiaial version, and after I was able to install and run RootCloak....however bank app still did not work.
Back to stock....
Installed Freedom_OS_H815_v7.5
It is Nougat 7.0, software v29a, +flashed with Titan kernel v1.8.
Aroma installer is a great feature, every custom ROM should have it, to be able select what you want to install.
I am not familiar with Insular/Shelter app and usage, more to learn....