Related
Hello folks of XDA, especially the Italians one since i'm creating this thread to address one of the most wanted feature of the Italian Intesa San Paolo home banking mobile application for Android, that is making PayGo work with a custom ROM, rooted phone, ecc....
Now let's first state what PayGo is and what's the problem:
PayGo it's a feature of the application that allows you to emulate the contactless chip of one of you credit/debit card through NFC.
PayGo requires your phone to be unrooted and unmodified.
Every attempt to hide the modifications through Magisk Hide allows you to pass the initial warning of the application about Root and Custom ROM but the feature then fails to start with an unknown error.
So, summing up, PayGo won't work even if you pass SafetyNet checks and no one seems to understand what it checks.
Now, I'm a developer but I'm not even close to understand how security checks and stuff works under the hood in Android but my guess is that PayGo checks somehow if the bootloader is unlocked or not. Following this intuition I Googled how to check from application code if the bootloader is unlocked or not. One answer on Andorid Stack Exchange seemed to be really useful: it states that from a dialer app you can check if the bootloader is unlocked or not. Now, that answer reminded me that I was always wondering why Intesa San Paolo app was asking for phone permissions even if it never used them (at least apparently) and an idea popped to my mind:
what if the app asks for phone permissions only to check as dialer if the phone has unlocked bootloader or not?
Well, I revoked phone permission to the app and tried to open PayGo and guess what, it asks phone permissions right away! If you deny them and check "don't ask me again" it won't even open anymore, so my guess may be right.
The problem now is to understand what values is returned to the dialer and how to modify it so that we can test it.
Any good soul that can offer a solution through, i don't know, a Magisk module or something?
Thank you for your time in reading this, I hope it helps someone
@Diomorgan, @Errtu73, @olivercervera may find this thread useful
Have you tried disabling ADB debugging? I have personally tested PayGo and works
olivercervera said:
Have you tried disabling ADB debugging? I have personally tested PayGo and works
Click to expand...
Click to collapse
Yes, it passes the first warning but then fails to start with unknown error
You are lucky because I'm customer of the Intesa group (although I usually don't use this app)
As I said earlier, it works perfectly on my device. The issue is specific to your ROM/device.
I just activated the App and PayGo right now...
olivercervera said:
You are lucky because I'm customer of the Intesa group (although I usually don't use this app)
As I said earlier, it works perfectly on my device. The issue is specific to your ROM/device.
I just activated the App and PayGo right now...
Click to expand...
Click to collapse
Well I tried it on a OnePlus One with Sultanxda LOS but no luck, same on LG G4 with official LOS. Which phone and ROM are you using?
I'll try with my OnePlus 5 keeping the stock ROM, hoping it will work
Lamba92 said:
Well I tried it on a OnePlus One with Sultanxda LOS but no luck, same on LG G4 with official LOS. Which phone and ROM are you using?
I'll try with my OnePlus 5 keeping the stock ROM, hoping it will work
Click to expand...
Click to collapse
I'm on Xiaomi Mi5 and LOS 15.1 (Android 8.1)
LOS is not the problem, probably there was something weird in the ROMs you tried. Some old ROMs are implemented in a way that Magisk can't really work/hide everything, most of them before SafetyNet/Magisk era.
Try with stock ROM and Magisk, you should be fine.
I'm trying to enable fingerprint sign on in the Wells Fargo app on my rooted, magisk pixel 2 on the latest march update. I've tried a couple times to enable it and it tells me that fingerprint sign on is currently unavailable. Anybody else experiencing the same issue?
enzyne said:
I'm trying to enable fingerprint sign on in the Wells Fargo app on my rooted, magisk pixel 2 on the latest march update. I've tried a couple times to enable it and it tells me that fingerprint sign on is currently unavailable. Anybody else experiencing the same issue?
Click to expand...
Click to collapse
Working for me, but I'm stock.
I'm rooted with TWRP flashed. Other apps (like Walmart) that require fingerprint find it, but my banking app (PNC) doesn't, and doesn't work at all (restarts during a check deposit), so there's something causing a problem somewhere.
Rukbat said:
I'm rooted with TWRP flashed. Other apps (like Walmart) that require fingerprint find it, but my banking app (PNC) doesn't, and doesn't work at all (restarts during a check deposit), so there's something causing a problem somewhere.
Click to expand...
Click to collapse
Are you using Magisk? I use the PNC app and have it selected with magisk hide and fingerprint works.
1.Try depositing a check.
2. What version of the app are you running?
So just an update I was after a day able to add fingerprint sign on. I just got this account so that may be why. I dont have paper checks to deposit that often but if i ever get one i will report back.
Rukbat said:
1.Try depositing a check.
2. What version of the app are you running?
Click to expand...
Click to collapse
I'm running 4.3.1. It crashes now when the camera would open to capture a check image, but it used to work before. I hadn't used it in a while so must be something broken in an update... All the other functions except for check deposit are working.
Same version - and that's the only reason I use the app. Since I'm on the desktop all day, I do everything else on the desktop. Tech support promised that they'd have a fix out by end of March, beginning of April at the latest. Nothing yet. Oh - when it crashes, it comes up with the name and password screen when you rerun it, and won't accept the fingerprint.
A company I used to work for had a sign hanging in their cafeteria that said that it costs $1,000 to get a customer, but you can lose one with a single wrong word. I think I'm about to become one of PNC's "lost customers". The local Walmart, where I am at least once a week, has a bank branch inside (and the store is pretty much around the corner). The next time I'm there, I'm talking to them. Even if they don't have an app, I'm there all the time anyway. And PNC is 4 miles across town. It will be interesting to see if the app eventually works, but this isn't how you run a software department. (I know - I spent 45 years developing software, most of them either as lead or as head of the department. An "I can't use the program because it doesn't work" would immediately put that bug at the top of my) list - and get someone assigned to fix it.)
I finally loaded the May factory image on my unlocked and Magisk rooted 3 a couple weeks back, and I noticed that every single app now reports user data and cache as 0 when I bring up app info. Makes it difficult to troubleshoot apps short of completely uninstalling them. Has anyone else seen this issue, and have you found a fix? I'm trying to wait a few days before getting the June update, just because there have been a few problems with the last couple updates and Magisk, I'd like to know if my 10 minute task will end up taking me an hour or more.
scooter1979 said:
I finally loaded the May factory image on my unlocked and Magisk rooted 3 a couple weeks back, and I noticed that every single app now reports user data and cache as 0 when I bring up app info. Makes it difficult to troubleshoot apps short of completely uninstalling them. Has anyone else seen this issue, and have you found a fix? I'm trying to wait a few days before getting the June update, just because there have been a few problems with the last couple updates and Magisk, I'd like to know if my 10 minute task will end up taking me an hour or more.
Click to expand...
Click to collapse
are you using magisk systemless host module/magisk hide? if yes then flash below/kirisakura kernel which should fix the issue
https://forum.xda-developers.com/showpost.php?p=79658098&postcount=1774
SacredDeviL666 said:
are you using magisk systemless host module/magisk hide? if yes then flash below/kirisakura kernel which should fix the issue
https://forum.xda-developers.com/showpost.php?p=79658098&postcount=1774
Click to expand...
Click to collapse
From what I heard the other day when I posted about the grayed out clear cache/data in Google Play Store, Freak07 doesn't even know what he did that fixed the issue. Do you have more information about how it was resolved? I'd hate to be limited to one kernel that fixes the issue without reason (when obviously many of us use others for other reasons).
sliding_billy said:
From what I heard the other day when I posted about the grayed out clear cache/data in Google Play Store, Freak07 doesn't even know what he did that fixed the issue. Do you have more information about how it was resolved? I'd hate to be limited to one kernel that fixes the issue without reason (when obviously many of us use others for other reasons).
Click to expand...
Click to collapse
It's something to do with pixel's f2fs partitions and Magisk so its not a kernel issue to be addressed by kernel devs
https://github.com/topjohnwu/Magisk/issues/1109#issuecomment-499181858
Yeah apparently only @Freak07 kernel fixes the issue caused by magisk/pixel parition.
ElementalX is close to stock and he won't deviate from it and which is good too. Probably @flar2 would know what is the difference?
SacredDeviL666 said:
It's something to do with pixel's f2fs partitions and Magisk so its not a kernel issue to be addressed by kernel devs
https://github.com/topjohnwu/Magisk/issues/1109#issuecomment-499181858
Yeah apparently only @Freak07 kernel fixes the issue caused by magisk/pixel parition.
ElementalX is close to stock and he won't deviate from it and which is good too. Probably @flar2 would know what is the difference?
Click to expand...
Click to collapse
I appreciate the reply. It's not a huge issue for me, but you guessed it that I use ElementalX. I just have to disable the Edge Sensor module if I need to clear data/cache in Google Play Store (typically once a month to get Play Store to show the devices as certified).
sliding_billy said:
I just have to disable the Edge Sensor module if I need to clear data/cache in Google Play Store (typically once a month to get Play Store to show the devices as certified).
Click to expand...
Click to collapse
THAT'S the quick fix that I was looking for. Thanks.
scooter1979 said:
THAT'S the quick fix that I was looking for. Thanks.
Click to expand...
Click to collapse
Haha, no problem.
I'm rooted on Pie June update (PQ3B.190605.006) and suffering from infamous "CaptivePortalLogin keeps stopping" issue reported on Reddit ( can't post link due to policy, sorry).
As a temporary solution I use CAPTIVE_PORTAL_MODE_IGNORE in Settings.java to prevent Android from detection of captive portals.
To do that in root shell on device run:
settings put global captive_portal_mode 0
The same could be accomplished over ADB.
After updating that setting I don't get notifications until opening page in browser, which redirects me to the login page of the Wi-Fi provider.
I'm looking for ideas how to make CaptivePortalLogin to work on PQ3B.190605.006 version.
Tried to remove Magisk, reflash clean and replace CaptivePortalLogin in /system/apps with different APK provided here on XDA, sideloaded July PQ3B.190705.003 version, but nothing helped.
SOLUTION: Clean flash of July update PQ3B.190705.003 on both A/B and full factory reset.
my workaround for this is basically turning on airplane mode -> turn on wifi and connect to network -> open browser and load a random page to be redirected to the captive portal.
Did it work with the march version? Looks like even stock phones seem to have a problem with it according to reddit. It worked just fine for me on june when it wasnt rooted..
Thank you so much for workaround! It works.
For your question about March version, I don't have an answer if it worked out of the box, as I didn't try it.
It would be nice to fix CaptivePortalLogin, not sure how to attack it though.
While waiting on support to fix CaptivePortalLogin, I came up with a temporary solution, to avoid a brute force "Airplane mode" method. I decided to use CAPTIVE_PORTAL_MODE_IGNORE in Settings.java to prevent Android from detection of captive portals.
Solution:
in root shell on device run:
settings put global captive_portal_mode 0
The same could be accomplished over ADB.
After updating that setting I don't get notifications until opening page in browser, which redirects me to the login page of the Wi-Fi provider.
I hope someone can benefit from this solution until we get a real fix for CaptivePortalLogin.
I have disabled MAC address randomization in the advanced options of the WiFi network and it seems to solve the issue. Many captive portals use the MAC address to identify the device, so this would be a good explanation of the problem.
Thanks for suggestion. That option was off on my device by default and I didn't play with it. And in my case Captive Portal Login crashed on every network implementation from my corporate one to coffee shop.
R0BiN0705 said:
my workaround for this is basically turning on airplane mode -> turn on wifi and connect to network -> open browser and load a random page to be redirected to the captive portal.
Did it work with the march version? Looks like even stock phones seem to have a problem with it according to reddit. It worked just fine for me on june when it wasnt rooted..
Click to expand...
Click to collapse
This did not help
Still keep getting captiveportal crashed.
Any other suggestions?
Look at my original post or post #4 how to use CAPTIVE_PORTAL_MODE_IGNORE to disable Captive Portal login.
Wow! I am glad I am not the only one experiencing this issue!
I have the google pixel 3a with June security patch and rooted with Magisk via patched boot image.
Im wondering, is this due to Magisk or is this an actual issue with the June 2019 Factory Images/OTA?
Thanks!
djjohnnyblaze said:
Wow! I am glad I am not the only one experiencing this issue!
I have the google pixel 3a with June security patch and rooted with Magisk via patched boot image.
Im wondering, is this due to Magisk or is this an actual issue with the June 2019 Factory Images/OTA?
Thanks!
Click to expand...
Click to collapse
I speculate it's a bug in June update, because it did crash for me with or without Magisk. But on another hand I would expect more activity on this thread if it is a widespread issue.
pasha_d said:
I speculate it's a bug in June update, because it did crash for me with or without Magisk. But on another hand I would expect more activity on this thread if it is a widespread issue.
Click to expand...
Click to collapse
Looked at some threads on Reddit and it seems like even new devices are having this issue.
I don't think anyone knows what's causing it but this is a big deal. What scares me is one thread that said a replacement device works now with June security update. How could this be hardware though? Especially if it was working prior to June 2019 security update ...
The July security patch did not resolve this issue. How do we escalate this?
Issue had already been raised... No fix yet.
https://issuetracker.google.com/issues/135711621
karimski75 said:
Issue had already been raised... No fix yet.
https://issuetracker.google.com/issues/135711621
Click to expand...
Click to collapse
Not sure where they're going to fix it though, maybe in Q only. I'm looking for a fix in Pie.
Here is the post from assigned developer from Google:
vi.. @google.com <vi.. @google.com> #83 Jul 9, 2019 02:26AM
Marked as fixed.
The issue has been fixed and it will become available in a future Android release. Please keep an eye on the release notes(https://developer.android.com/preview/release-notes)
It crashes for me too. Bummer!
Stock and non-rooted.
Pasha_d posted a solution that worked for me. You need to be rooted.
https://forum.xda-developers.com/pixel-3a/help/captiveportallogin-apk-t3940042
Pasha, did you ever find a copy of the March version of the captiveportallogin.apk?
No I didn't. The only ones I found on APK mirror were from February. Nobody replied to my original request here on XDA.
I was able to turn off data. Load a web page and sign in over wifi.
pasha_d said:
No I didn't. The only ones I found on APK mirror were from February. Nobody replied to my original request here on XDA.
Click to expand...
Click to collapse
March apk
Hello,
I have an unlocked, rooted Pixel 7, Android 13 panther. My device is rooted, and the bootloader is unlocked. I have Magisk 25.2 installed with Zygisk and enforce denylist active.
I cannot seem to get my device to pass SafetyNet. I use YASNAC and am continually getting a CTS profile Match Fail.
I have installed the magisks modules, Universal SafetyNet fix, and Magisk Hide Props Config.
I cannot figure out a sequence of options using Hide Props Config that will get me to pass SafetyNet.
Is there anyone who might have any suggestions?
i have the exact same issue
captain_howdy said:
Hello,
I have an unlocked, rooted Pixel 7, Android 13 panther. My device is rooted, and the bootloader is unlocked. I have Magisk 25.2 installed with Zygisk and enforce denylist active.
I cannot seem to get my device to pass SafetyNet. I use YASNAC and am continually getting a CTS profile Match Fail.
I have installed the magisks modules, Universal SafetyNet fix, and Magisk Hide Props Config.
I cannot figure out a sequence of options using Hide Props Config that will get me to pass SafetyNet.
Is there anyone who might have any suggestions?
Click to expand...
Click to collapse
dangercl0se said:
i have the exact same issue
Click to expand...
Click to collapse
you both need to check out the post below (or better yet, get from his Github) and use Displax's updated mod to Universal SafetyNet fix. The original USNF hadn't worked with the Pixel 6 (or Pixel 7), where his original mod worked and passed everything but Strong Integrity. Then, when it came to the Pixel 7 Pro, he needed to mod it again and we all have been using his mod_2.0 to get things to work.
Of course, after applying the module and putting Google Play Store, Google Services Framework, & Google Play Protect Service in the Denylist (every entry in its subdirectory ticked), be sure to clear data from them to make sure you get the best chance at passing safetynet...
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
simplepinoi177 said:
you both need to check out the post below (or better yet, get from his Github) and use Displax's updated mod to Universal SafetyNet fix. The original USNF hadn't worked with the Pixel 6 (or Pixel 7), where his original mod worked and passed everything but Strong Integrity. Then, when it came to the Pixel 7 Pro, he needed to mod it again and we all have been using his mod_2.0 to get things to work.
Of course, after applying the module and putting Google Play Store, Google Services Framework, & Google Play Protect Service in the Denylist (every entry in its subdirectory ticked), be sure to clear data from them to make sure you get the best chance at passing safetynet...
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
Click to expand...
Click to collapse
the 2.0 file worked for me, i get CTS pass now
but cannot hide root from Citibank app though. any chance you may know a fix? or the citibank guys are that good?
I vey same issue with my bank app Bt Pay. Only reason i cant stay rooted.
dangercl0se said:
the 2.0 file worked for me, i get CTS pass now
but cannot hide root from Citibank app though. any chance you may know a fix? or the citibank guys are that good?
Click to expand...
Click to collapse
Need Shamiko. Set apps in deny list but don't enforce the deny list.
LLStarks said:
Need Shamiko. Set apps in deny list but don't enable the deny list.
Click to expand...
Click to collapse
Unless the app is even "smarter". Like my own bank app.
dangercl0se said:
the 2.0 file worked for me, i get CTS pass now
but cannot hide root from Citibank app though. any chance you may know a fix? or the citibank guys are that good?
Click to expand...
Click to collapse
I was having trouble with Chase a while back. What I did was clear the banking app's cache/data, enable airplane mode, and reboot after passing safetynet adding the banking app to DenyList. I was then able to log in and successfully hide root from the app. Good luck!
LLStarks said:
Need Shamiko. Set apps in deny list but don't enforce the deny list.
Click to expand...
Click to collapse
still doesn't work, citibank can detect magisk (which was hidden) before i login lol
dangercl0se said:
the 2.0 file worked for me, i get CTS pass now
but cannot hide root from Citibank app though. any chance you may know a fix? or the citibank guys are that good?
Click to expand...
Click to collapse
I use the Citibank app myself and am able to get it to work. You gotta make sure that everything under its sub-directory is ticked as well -- just checked and there's 4 entries in its subdirectory that needs to be ticked. Another thing that might help is to Click Hide the Magisk app; when you hide it, you'll have the optional opportunity to change the Magisk app's name to whatever you wish. Also, you can do what kornball said below as that's also a good idea as well.
kornball said:
I was having trouble with Chase a while back. What I did was clear the banking app's cache/data, enable airplane mode, and reboot after passing safetynet adding the banking app to DenyList. I was then able to log in and successfully hide root from the app. Good luck!
Click to expand...
Click to collapse
Try to use Ice Box app and freeze magisk, then see if banking app works. I had to do that on my last phone. You can easily open magisk by opening ice box app first.
Weird stuff, folks. I imagine that something else is being done amiss as I have a similar setup and don't have any safetynet issues that affect the access to my banking apps/GPay/Prime Video/etc.
I don't even use Displax's USNF mod. Heck, I barely even use the denylist.
I would suggest that you wipe the device clean, re-image it with the latest A13 build, re-root and then set everything up again. But this time, do not install the Magisk Hide Props. That is only needed for those on custom ROMs (which I imagine you aren't using).
dangercl0se said:
still doesn't work, citibank can detect magisk (which was hidden) before i login lol
Click to expand...
Click to collapse
Did you enable Zygisk?
I'm honestly having trouble with Chase at the moment. Usually I'm able to hide Magisk enough to get fingerprints working.
The Citi app doesn't work for me either, despite all other workarounds, and everything else works other than setting the fingerprint reader for use with the Chase app (but that can be worked around while temporarily not rooted). I'll just use the Citi website if I need to.
LLStarks said:
Did you enable Zygisk?
I'm honestly having trouble with Chase at the moment. Usually I'm able to hide Magisk enough to get fingerprints working.
Click to expand...
Click to collapse
I forgot to set the fingerprint before I rooted when I updated the firmware, but I'm just going to try to remember to do it on the next firmware update, hopefully. I never found any other workaround that always works.
roirraW edor ehT said:
The Citi app doesn't work for me either, despite all other workarounds, and everything else works other than setting the fingerprint reader for use with the Chase app (but that can be worked around while temporarily not rooted). I'll just use the Citi website if I need to.
I forgot to set the fingerprint before I rooted when I updated the firmware, but I'm just going to try to remember to do it on the next firmware update, hopefully. I never found any other workaround that always works.
Click to expand...
Click to collapse
For Chase, here's how I got it to work on my P6 previously. There's an old thread where someone installed a downgraded version, but I didn't need to do that:
I force stopped the app and cleared cache/data. I then enabled airplane mode, went into the Chase app and entered my credentials. I hit the fingerprint option and hit "sign on." I got the error saying no data connection available. I reenabled data and signed on.
kornball said:
For Chase, here's how I got it to work on my P6 previously. There's an old thread where someone installed a downgraded version, but I didn't need to do that:
I force stopped the app and cleared cache/data. I then enabled airplane mode, went into the Chase app and entered my credentials. I hit the fingerprint option and hit "sign on." I got the error saying no data connection available. I reenabled data and signed on.
Click to expand...
Click to collapse
I've tried that before on my Pixel 6 Pro and it didn't work. I just tried it again, exactly as you said, and it didn't work for me this time either. I'm glad it works for you. It's no big deal for me to do it while unrooted - just too lazy to unroot until I have to manually update the firmware anyway.
The downgrade app solution worked for a short while, but the app requires that it's reasonably up to date to work at all, so that option was never for the long term.
kornball said:
For Chase, here's how I got it to work on my P6 previously. There's an old thread where someone installed a downgraded version, but I didn't need to do that:
I force stopped the app and cleared cache/data. I then enabled airplane mode, went into the Chase app and entered my credentials. I hit the fingerprint option and hit "sign on." I got the error saying no data connection available. I reenabled data and signed on.
Click to expand...
Click to collapse
This unfortunately did not work for me. I pass safetynet and have magisk hidden as well as Chase on the deny list with all the ticks selected.
roirraW edor ehT said:
The Citi app doesn't work for me either, despite all other workarounds, and everything else works other than setting the fingerprint reader for use with the Chase app (but that can be worked around while temporarily not rooted). I'll just use the Citi website if I need to.
I forgot to set the fingerprint before I rooted when I updated the firmware, but I'm just going to try to remember to do it on the next firmware update, hopefully. I never found any other workaround that always works.
Click to expand...
Click to collapse
I can't believe you and dangercl0se haven't gotten Citi app to work!!! You, the creator the the quintessential guide of whom I followed step by step to get my root working, are having troubles with it when I haven't done anything particular or different than you would have done?! Doesn't seem right to me....i'm baffled as to why things are seamless for some people are are stubborn/difficult for others....
simplepinoi177 said:
you both need to check out the post below (or better yet, get from his Github) and use Displax's updated mod to Universal SafetyNet fix. The original USNF hadn't worked with the Pixel 6 (or Pixel 7), where his original mod worked and passed everything but Strong Integrity. Then, when it came to the Pixel 7 Pro, he needed to mod it again and we all have been using his mod_2.0 to get things to work.
Of course, after applying the module and putting Google Play Store, Google Services Framework, & Google Play Protect Service in the Denylist (every entry in its subdirectory ticked), be sure to clear data from them to make sure you get the best chance at passing safetynet...
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
Click to expand...
Click to collapse
Did all this, still failing for me.
Beefheart said:
Did all this, still failing for me.
Click to expand...
Click to collapse
I can only assume you mean passing safetynet and not getting the banking apps to work....
Only thing left that I can think of that I didn't include in that post is to make sure you have "systemless hosts" module installed as well; i know it's pretty obvious but just trying to cover all the bases....
If so and still failing, I suggest going to roirraW "edor" ehT's guide/thread -- it's probably the most active thread on this forum and is where many is bringing up their failing to pass it while going through all the steps...
*there's also Homeboy76's guide HERE if it's clearer/easier to follow for you...
unfortunately there's no real debug logs to state why it's not working out, so the best that I can suggest is that you're going to have be a lot more descriptive on what & how you "did all this" with luck that that'll show something you may have missed and/or start from scratch and follow each and every step exactly of roirraW "edor" ehT's/Homeboy76's guide and hope it works out that way.
Good luck to you and I hope this helps...