Cheers everyone,
I followed the modified Chainfire tutoria by @jcase to root my HTC Bolt. I followed that by putting the Bad Boyz ROM on it as well, just for fun. That whole process was a success. I tinkered with some of my favorite apps, and now I'm not able to turn on my Wi-Fi anymore.
Here's what I've done: modified Chainfire root, Bad Boyz rom through TWRP, and manually cleared both caches using TWRP after noticing the Wi-Fi issue.
Where and when it started: I'm not a fan of the built-in hot-spot application, so I've had a steady relationship with WiFi Tether Router in the Play Store. I attempted to use this with the HTC 10 configuration provided by the app's author, which resulted in my situation now and the app doesn't even function properly.
Where and how it gets weird: The fixed hot-spot application built-in works perfectly. I can use it for Internet access with all the devices I own.
I'm in a pretty LTE rich area, so this isn't critical, just annoying.
Any help is welcome and appreciated.
Easiest thing is just wipe and reflash the Rom. Don't use a different app. Stock app works flawlessly.
fyi--latest twrp can be used along w/ supersu
http://forum.xda-developers.com/devdb/project/?id=18340#downloads
Hi all,
Basically I want to root my mobile without loosing access to my corporate mail and banking app (which doesnt work on rooted mobiles - and which I assume will work with magisk). I have below queries if anyone can answer will be grateful
1) I want to use adaway, font changer, build.prop hack for api2, all mods in this thread https://goo.gl/PZYFZH & https://goo.gl/fgDMWu (Some of them req twrp). Will I still be able to access corporate mail ?
2) can I just unroot and re-lock bootloader to get and install OTA
3) Will I lose data after point 2
1. as long as you enable Magisk hide + specify your email/banking apps in the menu, you should be able to use them. You might be out of luck if you use Xposed though (it breaks Safetynet).
2. when OTA arrives, restore stock boot image from Magisk, apply OTA and when the phone asks for a reboot, install Magisk to the second, updated partition. After reboot you'll have updated and rooted system.
3. there is no need to relock the bootloader, so no risk of data loss.
_mysiak_ said:
1. as long as you enable Magisk hide + specify your email/banking apps in the menu, you should be able to use them. You might be out of luck if you use Xposed though (it breaks Safetynet).
2. when OTA arrives, restore stock boot image from Magisk, apply OTA and when the phone asks for a reboot, install Magisk to the second, updated partition. After reboot you'll have updated and rooted system.
3. there is no need to relock the bootloader, so no risk of data loss.
Click to expand...
Click to collapse
Thanks a lot. I installed magisk. Everything is good so far. Any good modules/mod/hacks can you suggest please
Also Reg 2nd point, i dont mind losing all the data. Just in case anything happens, can I flash stock rom, and get the phone back in mint condition?
You can relock the bootloader as long as you have stock kernel, recovery and system. Lazy way is to uninstall magisk ("restor stock boot image"), the safest way is to download stock rom and flash it (with or without data wipe). Btw. Xiaomi is the first phone which did not perform factory reset while unlocking the bootloader, so it's possible that you will lose nothing during relocking.
Personally I'm using these modules/mods from repository:
1. Google framework - to be able to install Google phone dialer from play store
2. Google lens enabler - to be able to use..Google lens
3. Greenify4Magisk
4. Xposed
+
5. Custom made module with these build.prop fixes - enable EIS, camera2api, add more volume steps, fix voice recording noise (there is similar module available at XDA with additional mods which I wasn't interested in)
_mysiak_ said:
You can relock the bootloader as long as you have stock kernel, recovery and system. Lazy way is to uninstall magisk ("restor stock boot image"), the safest way is to download stock rom and flash it (with or without data wipe). Btw. Xiaomi is the first phone which did not perform factory reset while unlocking the bootloader, so it's possible that you will lose nothing during relocking.
Click to expand...
Click to collapse
Thanks a lot.
_mysiak_ said:
Personally I'm using these modules/mods from repository:
1. Google framework - to be able to install Google phone dialer from play store
2. Google lens enabler - to be able to use..Google lens
3. Greenify4Magisk
4. Xposed
+
5. Custom made module with these build.prop fixes - enable EIS, camera2api, add more volume steps, fix voice recording noise (there is similar module available at XDA with additional mods which I wasn't interested in)
Click to expand...
Click to collapse
Thanks for sharing.
Well, I was using this mod for google dialer before rooting. - https://goo.gl/iSxS45. Have to say its awesome.
Also using google lens, mi A1 module by @sooti, iYTB magisk, greenify, ifont, adaway, GCAM mod with hdr+ and zsl. Still exploring
aks_pk said:
Well, I was using this mod for google dialer before rooting. - https://goo.gl/iSxS45. Have to say its awesome.
Click to expand...
Click to collapse
If I'm not mistaken, it doesn't support nearby places search and caller ID, the only two features which are missing in stock Mi A1 dialer But with Google framework + unmodded Google dialer, everything works fine. There is only one disadvantage - if you install Google dialer and then boot phone without Google framework module enabled, it will disappear from installed apps and mess up dialer permissions and settings and you'll need to reinstall it later. But IMHO it's worth the risk
hey there,
i was using custom roms back in the day with my oppo find 7, so android 7ish. Back than maintaining custom roms was a major pain in .... because, at least for me, i needed to full flash every time there was an update and most roms were kind of buggy as well.
Since my 9t is being annoying lately (EU 12.0.5) with shutting down apps way to often/fast, forgetting logins, making backups everywhere, switching back to light mode, no idea how to do a proper cleanup without deleting half my app settings etc. I was wondering what the state of the custom rom is nowadays.
I was thinking about getting something smaller, but since the pixel 5 is out of sale, the zenfone 8 missing wireless charge and no real alternative and all of them are more than 600 bucks, so i dont want to get a new phone tbh, prices are out of this world imho. Also iam quit pleased with the device itself, i.e. battery, performance, everyday stuff
so basically here is what i want to know:
How are updates handled in Pixelexperience or lineage?
how hard/easy is installation?
is google pay working?
is there a relyable way to make a full backup of my phone to go back to as is now?
did anybody experience the mentioned issues and maybe has a solution?
bonus qquestions
is there any major improvement in upcomming MIUI Versions(12.1, 12.5) and a roadmap of rollout?
what does SOT mean?
thanks in advance
for updates you may have to re flash the newer rom.
2. installation is easy given you know how to do it.
3. google pay is working fine.
4. twrp is the way, but believe me you won't aspire to go back.
5. I am running pixel experience rom on MI A2 device, the device is working great.
*/learn from youtube properly how to flash recovery, install rom for your device */
best of luck
I'm on Xiaomi.eu Stable (did use Weeklies for 6 months) - daily driver / business phone
If you like MIUI, you have A11, MIUI 12.5, debloated, all stable
You only flash ROM from TWRP (of course, first time, when switching to, Format Data is mandatory).
Later they have like OTA mechanism (Updater downloads ROM in zip, reboots to TWRP and upgrades)
not sure if i really like miui or not, thats why i was eyeing pixel/zenfone, i was pretty happy with my Mi A1 before the 9t
wouldnt a twrp backup break my safety net? if i remember correctly i need to unlock/root
suraj123 said:
2. installation is easy given you know how to do it.
Click to expand...
Click to collapse
well i knew it, but it has been ages
Abudinka said:
not sure if i really like miui or not, thats why i was eyeing pixel/zenfone, i was pretty happy with my Mi A1 before the 9t
wouldnt a twrp backup break my safety net? if i remember correctly i need to unlock/root
well i knew it, but it has been ages
Click to expand...
Click to collapse
For flashing any other ROM you need to unlock Bootloader - and that breaks Safety Net, not TWRP folder or so
However, Xiaomi.eu has built-in patch to pass SafetyNet with no need for Magisk, any Magisk module, anything
I.e., you switch to Xiaomi.eu (with Bootloader unlocked), no need to install Magisk and any of the modules like USNF, MHPC, etc) and you have SafetyNet, Device Certified in Google Play.
Also Widevine L1 and Netflix really plays in FullHD, HDR-10
And if you need Magisk for something else, you just enable MagiskHide and you still have SafetyNet etc.
No troubles here with SafetyNet
how much free space do i need for a twrp backup? most likely half of the internal space i guess.
so basically for every other rom besides xiami.eu i need to worry about safety net with magisk or similar?
I have TWRP Nandroid backup of 15 GB, but most of that is Data.
You don't need the backup for installing/updating the ROM.
That's only for your comfort
But I put it to PC and delete from the phone (if really needed, TWRP can also connect to PC and you can copy it back to phone before restoring)
I never needed to restore
And one more but very important thing
TWRP (backup) has NOTHING with SafetyNet. SafetyNet DOES NOT look do you have TWRP folder, or do you have Magisk app/mngr (I'm not talking about thevMagisk core/service but apk)
Unfortunately, there are too many unknowledgeable people writing that and similar nonsense elswhere
Problem is (and that's the reason why it might look 'similar' from the end user's point of view) that various banking apps, ganes and so, use VARIOUS methods and in some cases even speculative GUESSES trying to find if your device is SAFE for their apps and businesses (whatever that means for somebody), or is your phone 'rooted' (also in the very loose sense)
Those methods and guesses may include:
- Testing SafetyNet (framework provided by Google, partly in Google Play Services and partly on Google servers).
Fornally, when Bootloader is unlocked and/or with custom ROM (not certified with Google) or rooted (stock) ROM , you *should* fail SafetyNet - but there are methods to trick Google and still to pass SafetyNet.
Actually, to flash any such nod (custom ROM or recovery, or root, you first need to unlock Bootloader - and that's the first thing that SafetyNet looks for, but on some phones and ROMs it is possible to fool even the Google's SafetyNet)
That's the reason why thosre apps combine various other methods trying to find (or just to guess) if your phone is 'safe' or not
Some use sofisticated methods looking for su in the path or modified init.rc, or bypass Magisk Hide acting as isolated processes - that way finding the gllitches in MagiskHide making them possible to detect Magisk
But some use very PRIMITIVE guesses:
- If they find TWRP folder, they 'conclude' you 'must' be having TWRP, hence your Bootloader 'must' have been unlocked and you might have been flashed the root or custom ROM, hence they simply declare your phone as 'unsafe' or "rooted'.
But you could take 100% stock and not-modded phone and just create there a folder named TWRP on Internal memory - and your phone will fail their 'safety' pass (but not the Google's SafetyNet)
- Similarly, some just look if they find that the com.topjohbwu.magisk package installed (being Magisk apk, but that is not Magisk as core/service).
Again, you can take 100% stock, not-modded phone and just install there the Magisk apk (maybe, because you wantef to use its built-in SafetyNet checker), and those apps will declare your phone was 'rooted' - which is again total nonsense
On the other side, that is all about statistics. There will be let's say 0.001% of people who do have TWRP folder but not custom TWRP recovery and similarly 0.005% people who do have Magisk app but no Magisk
On the other side, 90% of people who do have custom Recovery will also have TWRP folder and 60% of people with Magisk service/core will also have Magisk app (formerly mngr) - the rest 40% of Magisk users will have hided/obfuscated/repackaged Magisk app (therefore, it cannot be found under the com.tophohnwu.magisk package name)
Hence those apps (and their developers, or better to say those who paid those developers to implemen that GUESSES) can take them rights to declare the phones with TWRP foldersor Magisk app installed as 'unsafe'
Those 1-5 users out of 100000, who by incidence do have TWRP folder (but no custom recovery) or Magisk app (but no Magisk) - bad luck, who cares about them
On the other side, that guesses (since they didn't come up with anything more sofisticated) will make them possible to catch 500 users with TWRP or Magisk, who tricked the Google's SafetyNet (but didn't even think about that primitive possibilities to 'catch' them)
thanks for the explanation, i most likely have a look this evening. Still, most app data will be lost when switching to pixel experience i assume
Abudinka said:
thanks for the explanation, i most likely have a look this evening. Still, most app data will be lost when switching to pixel experience i assume
Click to expand...
Click to collapse
Please find and read instructions for switching to the (custom) ROM - they can be found elswhere
An important and a MUST step is Formatting Data (that also formats Internal memory). Hence not 'most' but ALL user spps, their settings, your data like photos, contacts, Wifi passwords and everything will be wiped
Read and learn about what and how can be backed up. Good luck
im fully aware, that switching to another rom needs a full wipe and therefore loss of all data if not backup'ed.
I was more hoping one could provid a link and/or recommend something convienent.
And one more point. You must first unlock Bootloader - find where/how, apply for and you will need to wait 7 days
Unlocking bootloader performs Factory reset. However, at that time you are still on MIUI and you can use Xiaomi Cloud to backup and restore upon Factory resetting
(Once you unlock Bootloader, you can make Nandroid backups in TWRP but you cannot restore to custom ROM what you backed-up from MIUI, or vice versa
Once you switch to your custom ROM (and potentially root), you can use some apps for backing up and restore - but avoid the old and outdated Titanium
Hence I don't really see a point in TWRP backups, only just-in-case, for restoring the last working point in case of (soft) brick cases
zgfg said:
(Once you unlock Bootloader, you can make Nandroid backups in TWRP but you cannot restore to custom ROM what you backed-up from MIUI, or vice versa
Click to expand...
Click to collapse
Thanks alot again for the detailed explanation. This was the detail i was looking for. so basically its impossible to avoid losing app settings which are not saved in cloud and assigned to an app account.
The hint about miui backup/xiaomi cloud comes in handy as well. Also regarding the delayed bootload unlock, if it really takes up to 30 days (as stated on the pixelexperience install guide), maybe the Sony event on 26th brought something interessting
Abudinka said:
Thanks alot again for the detailed explanation. This was the detail i was looking for. so basically its impossible to avoid losing app settings which are not saved in cloud and assigned to an app account.
The hint about miui backup/xiaomi cloud comes in handy as well. Also regarding the delayed bootload unlock, if it really takes up to 30 days (as stated on the pixelexperience install guide), maybe the Sony event on 26th brought something interessting
Click to expand...
Click to collapse
It usually takes (and not from recently) exactly 168 hours = 7 days, no more or less.
There are also threads here on XDA about
Unless Xiaomi just recently changed the policy, but that could also depend on models
SOT = screen on time
Hey everyone, I'm pretty new with ROMs and everything regarding Android, but I've been trying to flash an AOSP ROM, whether official or not, just to get GPAY or my banking app to work on my A20e.
You can download the apps, they run fine, you can add your card and input the SMS code and everything, only problem is at the last step where GPay just gives me a standard error and my banking app gives me a "Digitization not finalized".
I got both GPAY and BTPay (my banking app) to work with the stock rom, so It can't be the card itself.
Has anyone ran into this or managed to fix it?
Have you rooted the device with Magisk? If so, go to the Magisk settings and toggle on 'MagiskHide'
burningcreation said:
Have you rooted the device with Magisk? If so, go to the Magisk settings and toggle on 'MagiskHide'
Click to expand...
Click to collapse
It's not rooted.