i have broken screen and i wanna install twrp but i can't accept swipe to allow modifications, also my otg is broken. there's any chance by adb slideload install other rom or magisk?
Custom ROM packages if I recall, cannot be sideloaded. Even if they could be sideloaded, what good would it do you given your digitizer is broken? Get the screen replaced first, then worry about a custom ROM.
Related
I'm currently sitting on the stock 6.0.1 B29 ROM for my 2017U A7, which is BL unlocked, rooted (SU 2.79-SR2), Xposed, with RootSwitch working, and TWRP.
What's the most simply way for me to upgrade to Nougat while maintaining those things listed above (aside from Xposed which I know doesn't support Nougat yet)?
Would I be forced to wipe my phone after installing Nougat in order to get everything working optimally?
Are there any issues or potential problems when upgrading that I should be aware of?
Read the nougat thread in general.
lafester said:
Read the nougat thread in general.
Click to expand...
Click to collapse
I have seen this thread: https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
But I was wondering there was a more simple or directly method which doesn't involve EDL mode?
Edit: Nevermind, I don't know why I was expecting a more simple method, nothing on the A7 is more straightforward than that. I'd still like to know if I should be expecting any issues and if a full wipe is needed. For that matter will my phone be wiped anyway if I install that ROM?
Cyrus D. said:
I'm currently sitting on the stock 6.0.1 B29 ROM for my 2017U A7, which is BL unlocked, rooted (SU 2.79-SR2), Xposed, with RootSwitch working, and TWRP.
What's the most simply way for me to upgrade to Nougat while maintaining those things listed above (aside from Xposed which I know doesn't support Nougat yet)?
Would I be forced to wipe my phone after installing Nougat in order to get everything working optimally?
Are there any issues or potential problems when upgrading that I should be aware of?
Click to expand...
Click to collapse
I don't see any reason that you couldn't flash the universal bootstack and modem for the U variant from the Lineage thread, and then flash the stock Nougat ROM that's posted in the BadBoyz Magisk thread. Or just flash the bootstack and modem, then flash that ROM, being that it's stock and should still allow you to pass SafetyNet.
bluestudy said:
I don't see any reason that you couldn't flash the universal bootstack and modem for the U variant from the Lineage thread, and then flash the stock Nougat ROM that's posted in the BadBoyz Magisk thread. Or just flash the bootstack and modem, then flash that ROM, being that it's stock and should still allow you to pass SafetyNet.
Click to expand...
Click to collapse
I would assume that it'd overwrite TWRP and I'd have to reinstall that again, and considering all the steps overall, that's not really any faster than jcadduono's EDL mode method.
Basically I was hoping there was a method that could just allow one package to be directly flashed and get it all done in one simple go to prevent any possible mistakes.
I said screw and installed the necessary program and drivers to flash the package with the Nougat bootloader + ROM + TWRP in EDL mode, it appears to detect properly, but I don't know if I want to go through with it until Xposed arrives. Between YouTube ads or grinding my face with a belt sander, I think the latter is less painful and horrific.
On the topic of SafetyNet, I currently pass it if I switch root off, yet Nintendo games won't install on my phone. They show as "incompatible with your device" the same as if they detect I have root. I have SUHide installed as well, but I have no idea how to check on that (where it is or how it functions for that matter). Installing the APKs from an alternate source just results in them crashing on start-up. Nintendo REALLY don't want root users playing any of their games.
Cyrus D. said:
I would assume that it'd overwrite TWRP and I'd have to reinstall that again, and considering all the steps overall, that's not really any faster than jcadduono's EDL mode method which installs the bootstack + ROM + TWRP from one package and can recover a brick.
Basically I was hoping there was a method that could just allow one package to be directly flashed and get it all done in one simple go so I don't have to do a song and dance every time I want to change my ROM. But I don't know if I can just do that with jcadduono's package because IIRC TWRP doesn't automatically install things to where they should be, you have to manually select it (recovery, etc) and that package needs to be installed to multiple locations. Or maybe I have no idea what I'm talking about it.
I said screw and installed the necessary program and drivers to flash the package with the Nougat bootloader + ROM + TWRP in EDL mode, it appears to detect properly, but I don't know if I want to go through with it until Xposed arrives. Between YouTube ads or grinding my face with a belt sander, I think the latter is less painful and horrific.
On the topic of SafetyNet, I currently pass it if I switch root off, yet Nintendo games won't install on my phone. They show as "incompatible with your device" the same as if they detect I have root. I have SUHide installed as well, but I have no idea how to check on that (where it is or how it functions for that matter). Installing the APKs from an alternate source just results in them crashing on start-up. Nintendo REALLY don't want root users playing any of their games.
Click to expand...
Click to collapse
Have been able to play Pokemon Go (my son, lol) and Fire Emblem on several Lineage based ROMs using Magisk. Can also get Android Pay to work (except for my bank currently not supporting it, but it doesn't show that I'm running any third party ROM or have my bootloader unlocked.) So, that might be the way for you to go, if you decide to try it out. As far as the EDL method, I've never tried it, but it does seem like an extremely useful tool.
Sorry went back and edited my post. It seems I was mistaken and I'd have to at least flash 2 packages by the EDL method, the TWRP package isn't the full ROM, just the bootloader and recovery. The only thing I can get working is Pokemon Go if I switch off root. Is Magisk working on the stock Nougat ROM as well?
My device is due soon and been going through the forum preparing myself. I am a bit confused though and would appreciate some help.
1- TWRP
From my other devices N5, 5T etc flash TWRP and you're on your way.
With this device it's Fastboot boot into regular TWRP wipe, then into deadman's TWRP to install ROM. Other instructions mention going into partition A then to B. Is permanent TWRP install not suitable for this device?
2-Root & Magsik
It seems that everything on this device is dependent on using Magsik for one thing or the other. I prefer to use SU as it always works with my setup. I'm not interested in safetynet. Do i really need to use Magsik?
After ROM install I use Xposed, SU, Xprivacy Lua, Titanium pro, Tasker.
Thanks.
bluegrass55 said:
My device is due soon and been going through the forum preparing myself. I am a bit confused though and would appreciate some help.
1- TWRP
From my other devices N5, 5T etc flash TWRP and you're on your way.
With this device it's Fastboot boot into regular TWRP wipe, then into deadman's TWRP to install ROM. Other instructions mention going into partition A then to B. Is permanent TWRP install not suitable for this device?
2-Root & Magsik
It seems that everything on this device is dependent on using Magsik for one thing or the other. I prefer to use SU as it always works with my setup. I'm not interested in safetynet. Do i really need to use Magsik?
After ROM install I use Xposed, SU, Xprivacy Lua, Titanium pro, Tasker.
Thanks.
Click to expand...
Click to collapse
As much as I'd like to help you, I don't get what you mean. Care you elaborate?
Sent from my Mi A1
I want to flash a permanent TWRP & flash ROMs etc like on a regular device.
Can this be done on this device?
Of course
Mod edit by @gregbradley Rule 2
Casual racism was deleted
I found this for you, hope it provides some info, also try forcing Google to give you results with kws like "SuperSU" and "su" by placing them inside quotes "" and by adding a + in front of a keyword.
https://forum.xda-developers.com/mi-a1/how-to/cf-auto-root-september-update-t3681024
1. You can Install TWRP permanently
As there is no separate recovery partition
fastboot flash recovery recoveryname.img command will fail
So you need to temporarily boot your phone to TWRP first n then make it permanent (Optional)
2. You can use SuperSu, technically there shouldn't be any problem as bothe Magisk and SuperSu patches Boot Image (haven't tested though)
Thank you for your replies.
Managed to install TWRP and decided to stick with stock for now, but install of Xposed fails. Now looking to solve that.
Bought this device because it was cheap. If Xposed install fails will return it.
I have made a guide to simplify the installation procedure: https://forum.xda-developers.com/mi-a1/how-to/lineageos-gapps-magisk-twrp-dolbyatmos-t3762939/
If you want to stay on stock, you can skip the LineageOS related stuff.
Thread cleaned
Lets be honest, this is a development site, lets keep the racism out of here.
Greg
bluegrass55 said:
Thank you for your replies.
Managed to install TWRP and decided to stick with stock for now, but install of Xposed fails. Now looking to solve that.
Bought this device because it was cheap. If Xposed install fails will return it.
Click to expand...
Click to collapse
I know you don't want to install Magisk, but you can install Xposed with Magisk without any issues
After updating to the latest software I found that with the exception of the first time I tried it which weirdly enough worked, I can't for the life of me successfully boot after rooting.
I rooted once and had to uninstall magisk because of a conflicting module but now no matter what I try I always get stuck on essential's splash screen.
Does anyone else have this problem? If I flash the stock boot image I can boot just fine.
have you try flashing update, then boot image then magisk consecutively before any reboot? I'm out of the country at the moment w/o access to my PC, and I can't even risk a soft brick while traveling.
Are you getting as far as installing magisk again? cause from what you've written it sounds like it is working but the module that caused the original issue is still there. you can remove magisk by flashing the stock boot image but the magisk image with all installed modules is still there.
If that is the case then there are a few tool out there to mount the magisk image and remove the module.
I tried a few when I had a similar issue and the only one that worked was this one.
https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165
what you would need to do is flash twrp. boot into recovery. (decryption never works for me so would recomend either sideload or adb push to /data/media)
flash the stock boot image back.
then reinstall magisk
flash the magisk recovery manager
once loaded go to the advanced section of twrp select terminal and type mm and follow the on screen instruction to remove the afflicted module then reboot and you should be sorted.
Although that being said if that isn't the issue you're having then can you explain how far you get with trying to reinstall and whats going wrong.
Ibanez33 said:
Are you getting as far as installing magisk again? cause from what you've written it sounds like it is working but the module that caused the original issue is still there. you can remove magisk by flashing the stock boot image but the magisk image with all installed modules is still there.
If that is the case then there are a few tool out there to mount the magisk image and remove the module.
I tried a few when I had a similar issue and the only one that worked was this one.
https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165
what you would need to do is flash twrp. boot into recovery. (decryption never works for me so would recomend either sideload or adb push to /data/media)
flash the stock boot image back.
then reinstall magisk
flash the magisk recovery manager
once loaded go to the advanced section of twrp select terminal and type mm and follow the on screen instruction to remove the afflicted module then reboot and you should be sorted.
Although that being said if that isn't the issue you're having then can you explain how far you get with trying to reinstall and whats going wrong.
Click to expand...
Click to collapse
I can't believe I hadn't thought of that. The conflicting modules were still there and I just had to remove them. Thanks so much man, I was about to wipe my phone out of frustration!
I rooted using the standard process, unlock bootloader, flash twrp img, flash twrp zip, flash magisk zip. But now my fingerprints register but don't work when trying to unlock. Anyone else with same problems, or a solution to this one?
I'm sorry I solved it myself. It was due to my matte screen guard. It worked perfect after removing it.
Hello everyone.
I made some test in installing some custom roms in some old devices always avoiding to install TWRP permanently on the drive (i used it in boot mode and then adb listen in TWRP and adb command from PC).
I've done this in order to preserve the stock recovery mode.
I decided to install pixel experience as my default rom in my redmi note 7 and i noticed that this rom will use OTA updates so i'm asking you if i should install TWRP (or other recovery images) permenently in order to make it work properly.
Another question that i have revolves around Magisk, is this tool needed in order to make pixel experience work fine?
BTW i don't understand why TWRP does not officially support RN7 lol (eventually i'll use a porting or another recovery )
Thank you everyone
First, sorry for not answering your main question but I'm more intrigued as to how you can flash a custom rom without using a custom recovery like TWRP. Also, is it possible to permanently install TWRP? How you do this?
Second, Magisk is not needed for the rom but allows some other customizations, fixes and root access.
you need some kind of custom recovery that supports your phone, its what allows you to install roms. There are a few out there such as TWRP, organge fox, etc. Chose whatever you like that has good support for your device.