Hi, i updated my xz premium to pie and installed most recent pie for my phone, (47.2.A.10.107) but I installed TWRP and tried to flash magisk but i couldnt do it gives error, (encryption related error) , twrp cant flash encrypted rom magisk, i wiped all data in order to avoid encryption but i every time when i flash new rom it is encrypted , how can i flash pie latest version and root my phone?
Never had the decryption issue stop Magisk but try this first and then Magisk.
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
bobsright said:
Never had the decryption issue stop Magisk but try this first and then Magisk.
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Click to expand...
Click to collapse
finally i could root my device but with different method , now problem is i cant flash anything with using twrp, it gives mounting error, i dont want to delete my data again because i installed a lot of programs, Can you help me?
i think it is ENCRYPTION problem
murad1990 said:
finally i could root my device but with different method , now problem is i cant flash anything with using twrp, it gives mounting error, i dont want to delete my data again because i installed a lot of programs, Can you help me?
i think it is ENCRYPTION problem
Click to expand...
Click to collapse
If the issue is with mounting the storage where your, whatever it is you're trying to flash, then put that file on an external drive and connect it to your phone via an OTG cable. Once you flash that zip in my last response, you won't have this issue. How did you root your phone?
Ok i unlocked bootloader, flashed stock pie rom, then flashed twrp but not latest one, because latest gave me mount error, i flashed 3.2.1 it solved my mounting problem, then i flashed janjan kernek then magisk. But problem is i lost most of functionalities of my phone(drm key lost) is there any way to restore it? Or is there any kernel?
murad19900 said:
Ok i unlocked bootloader, flashed stock pie rom, then flashed twrp but not latest one, because latest gave me mount error, i flashed 3.2.1 it solved my mounting problem, then i flashed janjan kernek then magisk. But problem is i lost most of functionalities of my phone(drm key lost) is there any way to restore it? Or is there any kernel?
Click to expand...
Click to collapse
Afraid not. There are steps to take to get temp root to back up those keys before unlocking the bootloader, and then restoring the keys after unlock. There's a whole thread on that here: https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510. I never bothered with all that and have not had any issues that concern me. What issues are you having?
Image enhancement doesnt work i think, and other camera function as well, any other function?
murad19900 said:
Image enhancement doesnt work i think, and other camera function as well, any other function?
Click to expand...
Click to collapse
Yeah, I couldn't tell you. As for me the phone still does what I need it to do. As far as the camera it still takes the pics I need it to take. I don't social media so I don't need the special effects/enhancements people use for that. When it comes to taking pictures, that's what I have a camera for. My phone is for calls, text, and email and web search when I'm not near my computer. You could try other phone apps to see if they replace what's lost. I believe photo quality is as stock.
Sorry I mean video image enhancement, and i want to ask question, do you think i should stay stock rom or use one of these carbon, existenz...
murad19900 said:
Sorry I mean video image enhancement, and i want to ask question, do you think i should stay stock rom or use one of these carbon, existenz...
Click to expand...
Click to collapse
Well same answer as far as video too.
I'm using eXtstenZ Pie. It's the stock rom with enhancements. It's stable and customizable. I would install the Aroma Add-on at the same time. I've tried Carbon but I had sim card issues, that may be resolved by now. There is also a Lineage 17.1 available but I don't believe it's reliable enough for a main phone. If you don't mind experimenting you could try that as it's Android 10. There's Tomahawk Project if you want barebones and get away from Google. CrDroid also out there. These last three I have not tried.
I am sorry but, i dont know so much about the android phones, I am using stock, exitstenz looks like custom rom, or is this modified stock? Because i lot changes and it doesnt have stock rom interface
murad19900 said:
I am sorry but, i dont know so much about the android phones, I am using stock, exitstenz looks like custom rom, or is this modified stock? Because i lot changes and it doesnt have stock rom interface
Click to expand...
Click to collapse
Yes, it's a modified stock rom.
To flash it, i just need to fladh latest firmware then twrp, then magisk?
If you're already on .107, you're good there. Then from twrp flash eXistenZ then flash Magisk. If you're going to use Aroma Add-on flash it next and you should be good to go. Also, with this phone you can install twrp in recovery partition so you don't have to use a computer every time you want to use twrp. You have to unzip it and save the .img file to where you put all the other files you flash, then from twrp install the image to recovery partition. Then next time you need to flash something, hold power and volume down at the same time (after turning phone off) when the screen just starts to light up release the buttons and it'll boot into twrp.
Thanks, but i have a another question, i flashed 47.2.a.6.30 version pie with using emma, and used janjan kernel of the same version, everyting works without any problem, should i stay this version or i must update to the 107 then root my phone? What is the advantages of the janjan's kernel? and without any custom kernel can i root my phone after flashing 107 firmware?
Don't know anything about the janjan kernel and it's compatibility with eXistenZ. As far as firmware version just flash the eXistenZ version that matches your rom version, I believe there is a list on the first page of the thread that tells which file to use.
---------- Post added at 08:27 PM ---------- Previous post was at 08:19 PM ----------
I don't know anything about the janjan kernel or it's compatibility with eXistenZ.
You can stay on that firmware if you wish. Just use the correct version of eXistenZ for it.
You can root any kernel once bootloader is unlocked. You loose root when you change firmware versions though.
Related
I keep reading posts that tell me to flash Magisk using custom recovery but my phone says 'update from external storage is disabled' so that's a no go.. And I can't use Odin because it's a ZIP file, not MD5, .TAR, SMD. etc. What else can I do? I've only ever managed to root my phone once and that was using CF AUTO Root which can be flashed by Odin.
KRandy21 said:
I keep reading posts that tell me to flash Magisk using custom recovery but my phone says 'update from external storage is disabled' so that's a no go.. And I can't use Odin because it's a ZIP file, not MD5, .TAR, SMD. etc. What else can I do? I've only ever managed to root my phone once and that was using CF AUTO Root which can be flashed by Odin.
Click to expand...
Click to collapse
Please tell us the specific phone model and rom. Magisk need to be flashed (installed) using a custom recovery e.g. TWRP. TWRP can be flashed using Odin even if the device isn't actually rooted.
LS.xD said:
Please tell us the specific phone model and rom. Magisk need to be flashed (installed) using a custom recovery e.g. TWRP. TWRP can be flashed using Odin even if the device isn't actually rooted.
Click to expand...
Click to collapse
My phone model is Samsung S5 Neo and I'm running 5.1 custom ROM. So, what you're saying is, I can flash TWRP using Odin and that will become my default recovery when I press home, volume up and the power button?
KRandy21 said:
My phone model is Samsung S5 Neo and I'm running 5.1 custom ROM. So, what you're saying is, I can flash TWRP using Odin and that will become my default recovery when I press home, volume up and the power button?
Click to expand...
Click to collapse
TWRP will replace the stock recovery. How did you manage to install a custom rom without a custom recovery?
LS.xD said:
TWRP will replace the stock recovery. How did you manage to install a custom rom without a custom recovery?
Click to expand...
Click to collapse
I managed to find a file with the file type .MD5 and used Odin, plugged my phone in and downloaded with no problem.
KRandy21 said:
I managed to find a file with the file type .MD5 and used Odin, plugged my phone in and downloaded with no problem.
Click to expand...
Click to collapse
That must be a modified stock rom. TWRP will allow you to install any kind of rom without any restrictions.
LS.xD said:
That must be a modified stock rom. TWRP will allow you to install any kind of rom without any restrictions.
Click to expand...
Click to collapse
Sweet! Thanks for the insight. This is what happens when you're a total noob. I find all this rooting and custom ROM larky confusing. I always stumble into issues along the way. So, install TWRP on my laptop and that will have the correct file type to be flashed by Odin, and then use TWRP to flash Magisk.. anything else or will I have any other problems? Don't want to clumsily stumble into a landmine.
KRandy21 said:
Sweet! Thanks for the insight. This is what happens when you're a total noob. I find all this rooting and custom ROM larky confusing. I always stumble into issues along the way. So, install TWRP on my laptop and that will have the correct file type to be flashed by Odin, and then use TWRP to flash Magisk.. anything else or will I have any other problems? Don't want to clumsily stumble into a landmine.
Click to expand...
Click to collapse
What the exact phone model? SM-xxxx
You can download TWRP as .tar.md5 and flash it using Odin.
Best case is to install Magisk on a fresh installation without root/exposed framework already installed.
LS.xD said:
What the exact phone model? SM-xxxx
You can download TWRP as .tar.md5 and flash it using Odin.
Best case is to install Magisk on fresh installation without root/exposed framework already installed.
Click to expand...
Click to collapse
That's fine as I don't have Xposed or Root access at the moment. My phone model is SM-G903F.
KRandy21 said:
That's fine as I don't have Xposed or Root access at the moment. My phone model is SM-G903F.
Click to expand...
Click to collapse
TWRP download
just a hint: there is already an official Marshmallow 6.0.1 release for you device and you probably should look out a newer rom.
LS.xD said:
TWRP download
just a hint: there is already an official Marshmallow 6.0.1 release for you device and you probably should look out a newer rom.
Click to expand...
Click to collapse
Why would you suggest that? In case I reach a point where apps are no longer compatible with my outdated software? Thanks, I might do that. I have stuck with 5.1 simply because I'm preferring it and also Marshmallow have made it harder to bypass security and root the device. I'm thinking it might not be safe now that I know this is a modded ROM, so I should probably look for an official one.
Can I make a Nandroid backup with TWRP? That sounds like it could be useful for any hiccups.
KRandy21 said:
Can I make a Nandroid backup with TWRP? That sounds like it could be useful for any hiccups.
Click to expand...
Click to collapse
Nandroid Backup and many other features are provided by TWRP
---------- Post added at 10:08 PM ---------- Previous post was at 09:54 PM ----------
KRandy21 said:
Why would you suggest that? In case I reach a point where apps are no longer compatible with my outdated software? Thanks, I might do that. I have stuck with 5.1 simply because I'm preferring it and also Marshmallow have made it harder to bypass security and root the device. I'm thinking it might not be safe now that I know this is a modded ROM, so I should probably look for an official one.
Click to expand...
Click to collapse
Marshmallow is already fully supported and you will be able to get full control to anything you like. Usually you can trust roms you get at the XDA forum as its a pretty active community and harmfull users would be banned real quickly. The only point is that modded stock rom or custom roms like LineageOS and derivates may not be stable and cause functionality issues.
So I've used this forum to find TWRP for my device https://forum.xda-developers.com/ga...official-experimental-twrp-galaxy-s5-t3293379, I'm not sure how to 'Run flash-recovery.sh' because, as I mentioned, it won't let me flash from my SD card.. Any help would be appreciated!
UPDATE: Managed to get TWRP as my custom recovery. Thanks so much for your help! I genuinely had no idea you could flash TWRP onto your phone! I was using the app which is hopeless. Most forums I've found say 'boot in recovery' which is quite unclear if you're not familiar with that..
Can I flash Nougat update onto my S5 Neo? It's originally not supported, that's the only reason I'm asking..
Can I still root with Magisk on that operating system as well and restore from Nandroid backup?
Hey all,
I love stock android! So when i read about OpenKirin I was excited. Did anyone use this to install LineageOS on our mate9 successful? What are your experiences?
I have another question as well: I changed my model to the MHA-L29, rooted with a custom recovery.
OpenKirin says it needs to have the stock one. Does anyone have a link to the stock MHA-L29 recovery and a guide on how to install it?
dekraan said:
Hey all,
I love stock android! So when i read about OpenKirin I was excited. Did anyone use this to install LineageOS on our mate9 successful? What are your experiences?
I have another question as well: I changed my model to the MHA-L29, rooted with a custom recovery.
OpenKirin says it needs to have the stock one. Does anyone have a link to the stock MHA-L29 recovery and a guide on how to install it?
Click to expand...
Click to collapse
First off, this thread probably belongs in Q/A.
Moving on:
I've run all 3 provided ROMs, Carbon as my daily driver and Lineage and RR for testing various things. They all work pretty well.
For stock recovery & ramdisk, download your current firmware (or if you've run other Treble ROMs as well, the version that corresponds to your current build number in Settings / System / About Phone) using Firmware Finder - you only need the main update.zip for this. You'll also need one of the utilities for extracting them. There's Huawei Update Extractor (I think that's what it's called anyway) for Windows, or https://github.com/marcominetti/split_updata.pl for Linux / Mac. Extract the ramdisk and recovery ramdisk images and there you go.
Installing those is a matter of rebooting into the bootloader and running:
fastboot flash recovery_ramdisk recovery_ramdisk.img
fastboot flash ramdisk ramdisk.img
(The name for recovery_ramdisk.img may vary a bit - the windows app will extract it as RECOVERY_RAMDIS.img.)
From there, just follow their instructions. If you have any problems, hit up the Telegram chat linked off the site, someone will be willing to help.
@irony_delerium, thank you very much. That sounds like something even I can do without too much problems
How do you like it, being on LineageOS?
dekraan said:
@irony_delerium, thank you very much. That sounds like something even I can do without too much problems
How do you like it, being on LineageOS?
Click to expand...
Click to collapse
Like I said in my original reply, my daily driver is Carbon; the Lineage builds I've only run briefly because NFC wasn't enabled, but the CarbonROM builds there have it. I use Google Pay every day, so it's kind of a requirement for me.
With that said, the only thing that's got issues for me is the camera app, and most of the blame for that is with Huawei. It generally works, but it'll close & restart often when switching modes or trying to start a recording.
I know there are various other minor issues with recording video in all 3, again because Huawei. (They put together bum codecs, and then patched the system side of the EMUI media stack to deal with the bum codecs, instead of fixing the codecs.)
Also worthy of mention (especially because I see people asking about this all the time): there is no VoLTE support. The devs are aware of it. Unless you're on a network that is pure LTE, it's mostly a non-issue. If you are, it's probably a deal breaker.
Getting on from there, they're all clean Android experiences, without the overbearing weight of EMUI. They don't try to pull some of the things EMUI did - the final breaking point for me was when it insisted on terminating apps in the background regardless of how much you might actually be using them. (In my case, AdGuard as a VPN service.)
Dear Sir
How Can I Revert to Stock Emui?
I am on Lineage baeta 4 ROM.
With Stock Recovery.
Tried Update and Hwota Methods but no Success.
I have Searched Everywhere.
Please Do A Step By Step Guide for Newbies.
Regards
talpur1 said:
Dear Sir
How Can I Revert to Stock Emui?
I am on Lineage baeta 4 ROM.
With Stock Recovery.
Tried Update and Hwota Methods but no Success.
I have Searched Everywhere.
Please Do A Step By Step Guide for Newbies.
Regards
Click to expand...
Click to collapse
Some comments before, Huawei Firmware Extractor. Extract system.img from the stock rom you used before flash Lineage.
Flash stock system.img in fastboot.
I have downloaded and tried to extract 4 roms but The Extractor tool is Giving error.
Its Giving invalid Hearder crc error.
talpur1 said:
I have downloaded and tried to extract 4 roms but The Extractor tool is Giving error.
Its Giving invalid Hearder crc error.
Click to expand...
Click to collapse
Go to settings in the app and disable CRC checking. (Bug in the app.)
I was on OldDroid's OpenKirin, but today switched to Carbon Beta 2 from https://openkirin.net/download/. This installed without problems and I did a hard reset as part of installation. The earlier version worked very well, except there were a few bugs. I haven't found any bugs in this ROM yet.
Random question: Does anyone know if it's safe to go from one build to another directly? I'm trying Lineage but would like to give Resurrection Remix a go. The instructions say that you should be coming from EMUI...
Thanks
jellmoo said:
Random question: Does anyone know if it's safe to go from one build to another directly? I'm trying Lineage but would like to give Resurrection Remix a go. The instructions say that you should be coming from EMUI...
Thanks
Click to expand...
Click to collapse
It's fine to go between them, provided you reload the stock ramdisk (if you installed Magisk) & factory reset before booting into the new ROM.
irony_delerium said:
It's fine to go between them, provided you reload the stock ramdisk (if you installed Magisk) & factory reset before booting into the new ROM.
Click to expand...
Click to collapse
You can switch between the Custom Roms. I always do. Backup your data on the data partition via USB to PC, go to TWRP do a factory reset and then install the new image via fastboot. Reboot and rejoice
mcc2005 said:
You can switch between the Custom Roms. I always do. Backup your data on the data partition via USB to PC, go to TWRP do a factory reset and then install the new image via fastboot. Reboot and rejoice
Click to expand...
Click to collapse
TWRP only works right on a Huawei device if you're either decrypted or running EMUI. (On a custom ROM, with an encrypted device, TWRP doesn't even start up - it locks up at the splash screen.)
Factory reset using stock recovery. Only using stock recovery. The OpenKirin team will not support any other configuration.
yes you are right. but there is still the possibility to do these things with a patched TWRP. I use this for my Mate 9 https://drive.google.com/file/d/1h50RJ6LNNSEVW9CS16C0NjeP7ZZNTECE/view?usp=sharing
mcc2005 said:
yes you are right. but there is still the possibility to do these things with a patched TWRP. I use this for my Mate 9 https://drive.google.com/file/d/1h50RJ6LNNSEVW9CS16C0NjeP7ZZNTECE/view?usp=sharing
Click to expand...
Click to collapse
And the reason why I say anything is because the 2 most common problems I see are:
1) "I'm on Jio, where's my VoLTE?"
2) "I used TWRP and (it's not working | I screwed up | it's broken)".
The response to the first is universally, go back to stock.
The second, restore your entire stock firmware and then follow the instructions exactly as they are written.
With root, you can back up your apps with Titanium. I haven't had good luck with backing up settings with Titanium and after attempting to restore settings, I usually wind up wasting an hour or two and then factory-resetting and just reinstalling the apps. Now I don't even bother backing up settings, but just back up my apps. Even then two or three seem to be botched but uninstalling/reinstalling those will fix that problem. (It isn't always the same ones, either; not sure what causes this). This approach avoids the pain of configuring apps, e.g. travel app usernames and passwords, as well as preserving messages and the like. The biggest nuisance for me is that I carry around 40 unread Amazon books, which have to be sent to the phone (and I'm not so good at remembering which ones I've already read out of the more than 500 in my account), and I carry a bunch of google offline maps, which have to be manually recreated. Lastpass helps with login information too.
In my most recent (Carbon B2) install, I didn't bother with the backup but installed everything fresh and I had a fully functioning phone with 99% of the configuration I like within 2 hours, since I'd been pretty careful to put all the passwords and so on for my roughly 80 apps into a secured text file, as well as backing up my Nova launcher settings.
Hi guy's I got a question if anyone can help me out
I'm on MHA-L29 8.0.0.360 (c567)
No custom rom but I got root with supersu
How can I install this carbon rom I try allready but twrp ask me on what partition I want to install the .img file and It shows bunch of it
I'm running twrp latest by pretoriano
Thank you very much guys
Caguayote said:
Hi guy's I got a question if anyone can help me out
I'm on MHA-L29 8.0.0.360 (c567)
No custom rom but I got root with supersu
How can I install this carbon rom I try allready but twrp ask me on what partition I want to install the .img file and It shows bunch of it
I'm running twrp latest by pretoriano
Thank you very much guys
Click to expand...
Click to collapse
Restore your stock ramdisk and recovery partitions. (I'd actually start with a full restore to stock firmware first: get your vendor patches in order. 8.0.0.369 is available for most phones on c567, 370 might be available.)
Factory reset using stock recovery. Flash with fastboot. Magisk for root & SafetyNet.
irony_delerium said:
Restore your stock ramdisk and recovery partitions. (I'd actually start with a full restore to stock firmware first: get your vendor patches in order. 8.0.0.369 is available for most phones on c567, 370 might be available.)
Factory reset using stock recovery. Flash with fastboot. Magisk for root & SafetyNet.
Click to expand...
Click to collapse
do you know where can i download the stock ramdisk and recovery partition for mate 9 i was running 8.0.0.369 sorry i put 360
im stuck on twrp splash screen and i cant go to access my backup file to restore and i only access fastboot mode
but my phone says unlocked then frp says lock thanks for all your help
Now i'm using android 7.0. based rom aur 2.3, if i want to install that stock android rom, do i have to flash android 8 based twrp?
I'll be switching to Project Fi soon from ATT. With the switch I'll lose my only reason for being rooted (wifi hotspot) since Fi offers hotspot for no extra charge. Am I able to install OTA updates with an unlocked bootloader if everything else is stock (ie. not rooted)?
geicogecko said:
I'll be switching to Project Fi soon from ATT. With the switch I'll lose my only reason for being rooted (wifi hotspot) since Fi offers hotspot for no extra charge. Am I able to install OTA updates with an unlocked bootloader if everything else is stock (ie. not rooted)?
Click to expand...
Click to collapse
I think you should be able to
Sent from my Pixel 2 XL using Tapatalk
You cannot take OTA updates normally with an unlocked bootloader. The phone will download the update, but the update will fail.
You CAN update manually using either OTA or factory images from here and following my guide here.
To sideload OTA images using either stock recovery or TWRP, follow the instructions here.
Excellent, thank you. I'd rather not wipe the phone so I guess I'll settle for sideloading OTAs. And it would be nice to be able to root later on if I decide I need to.
geicogecko said:
Excellent, thank you. I'd rather not wipe the phone so I guess I'll settle for sideloading OTAs. And it would be nice to be able to root later on if I decide I need to.
Click to expand...
Click to collapse
The nice thing about getting an OTA is that it installs in the background and a quick reboot to finish the update. Why not start fresh with a full wipe since you're changing carriers. It's not super difficult to get it set up again and now you have a clean install. I say that because I'm about to suggest you relock the bootloader and see how it runs. You obviously have the oem switch enabled so its really easy to go back and unlock if you so desire. Just a thought. I liked Project Fi when I had it but it didn't make financial sense in my case with a family plan. Good luck.
geicogecko said:
Excellent, thank you. I'd rather not wipe the phone so I guess I'll settle for sideloading OTAs. And it would be nice to be able to root later on if I decide I need to.
Click to expand...
Click to collapse
Just for ****s and giggles, I tried installing the OTA zip through TWRP. Worked like a charm.
Please note that if you do this, the kernel and recovery will revert to stock, so you'll have to boot TWRP via fastboot and reflash.
socal87 said:
Just for ****s and giggles, I tried installing the OTA zip through TWRP. Worked like a charm.
Please note that if you do this, the kernel and recovery will revert to stock, so you'll have to boot TWRP via fastboot and reflash.
Click to expand...
Click to collapse
Did you let it reboot on its own, or did you manually boot into TWRP, find the file and flash it that way?
k.s.deviate said:
Did you let it reboot on its own, or did you manually boot into TWRP, find the file and flash it that way?
Click to expand...
Click to collapse
I'm not sure I understand your question. I flashed the OTA file in recovery using TWRP. There is no way to flash things in recovery without rebooting...
socal87 said:
I'm not sure I understand your question. I flashed the OTA file in recovery using TWRP. There is no way to flash things in recovery without rebooting...
Click to expand...
Click to collapse
After the OTA downloaded, did you just reboot when it asked you to, or, did you manually boot into TWRP and find the OTA file to flash. OR, did you download the OTA from an third party and flash that way.
k.s.deviate said:
After the OTA downloaded, did you just reboot when it asked you to, or, did you manually boot into TWRP and find the OTA file to flash. OR, did you download the OTA from an third party and flash that way.
Click to expand...
Click to collapse
I downloaded the OTA directly from https://developers.google.com/android/ota, then rebooted into TWRP and flashed the zip.
I'm on stock software with the exception of Magisk and Flash kernel, so OTAs always fail. Thus, I have Automatic System Updates turned off in Developer Options.
Regardless of how you do it, the OTA will always overwrite /boot, so you'll lose custom kernel and recovery.
bobby janow said:
The nice thing about getting an OTA is that it installs in the background and a quick reboot to finish the update. Why not start fresh with a full wipe since you're changing carriers. It's not super difficult to get it set up again and now you have a clean install. I say that because I'm about to suggest you relock the bootloader and see how it runs. You obviously have the oem switch enabled so its really easy to go back and unlock if you so desire. Just a thought. I liked Project Fi when I had it but it didn't make financial sense in my case with a family plan. Good luck.
Click to expand...
Click to collapse
I may do this eventually. I want to see what having a non-rooted phone is like first. I haven't had a non-rooted phone in probably eight years. If I find out I really don't need root for anything, I may relock the bootloader.
socal87 said:
Just for ****s and giggles, I tried installing the OTA zip through TWRP. Worked like a charm.
Please note that if you do this, the kernel and recovery will revert to stock, so you'll have to boot TWRP via fastboot and reflash.
Click to expand...
Click to collapse
Wait... do you mean you actually flashed the downloaded, official OTA zip using TWRP over a rooted OS with no issues at all?... Interesting. Was that flashed OTA, a security patch only?
Sent from my Moto Z2 Play using XDA Labs
The Analog Kid said:
Wait... do you mean you actually flashed the downloaded, official OTA zip using TWRP over a rooted OS with no issues at all?... Interesting. Was that flashed OTA, a security patch only?
Sent from my Moto Z2 Play using XDA Labs
Click to expand...
Click to collapse
When the 9.0 update came out, I installed that via TWRP. Again, as noted, this will install it to both slots, and when it boots, it will boot via the other slot.
So, for instance, if you happen to be on slot A, and you install the OTA, it installs the stock kernel to slot B, and boots via that slot - stock kernel, no Magisk or TWRP. After it boots , when it is "Finishing update", it installs the stock kernel to slot A.
So, every time you flash an OTA, you need to let it boot, then reboot into bootloader, boot TWRP via fastboot, install TWRP, install kernel, and Magisk.
geicogecko said:
I may do this eventually. I want to see what having a non-rooted phone is like first. I haven't had a non-rooted phone in probably eight years. If I find out I really don't need root for anything, I may relock the bootloader.
Click to expand...
Click to collapse
So... How's the non-rooted phone experience going so far? Because I can't get fully used to the experience yet (I have this phone for a month now) and coming from... well, ALL of my previous devices rooted too (about an eight year span as well). Even though the phone in question (Z2 Play) runs very smooth and plain "force-close-less" (yeah, you know root) I still don't find myself quite at home without Xposed and it's useful modules, for example... Oreo is nice indeed but, on the other hand, I also have this little tiny bit temptation for Android 9... Sure, if it ever lands on my phone in less than a year! Quite a bet.
Sent from my Moto Z2 Play using XDA Labs
---------- Post added at 10:31 PM ---------- Previous post was at 10:28 PM ----------
socal87 said:
When the 9.0 update came out, I installed that via TWRP. Again, as noted, this will install it to both slots, and when it boots, it will boot via the other slot.
So, for instance, if you happen to be on slot A, and you install the OTA, it installs the stock kernel to slot B, and boots via that slot - stock kernel, no Magisk or TWRP. After it boots , when it is "Finishing update", it installs the stock kernel to slot A.
So, every time you flash an OTA, you need to let it boot, then reboot into bootloader, boot TWRP via fastboot, install TWRP, install kernel, and Magisk.
Click to expand...
Click to collapse
... That's only if you want to preserve root, I guess? AND for Pixel devices, right?
Sent from my Moto Z2 Play using XDA Labs
The Analog Kid said:
So... How's the non-rooted phone experience going so far? Because I can't get fully used to the experience yet (I have this phone for a month now) and coming from... well, ALL of my previous devices rooted too (about an eight year span as well). Even though the phone in question (Z2 Play) runs very smooth and plain "force-close-less" (yeah, you know root) I still don't find myself quite at home without Xposed and it's useful modules, for example... Oreo is nice indeed but, on the other hand, I also have this little tiny bit temptation for Android 9... Sure, if it ever lands on my phone in less than a year! Quite a bet.
Sent from my Moto Z2 Play using XDA Labs
---------- Post added at 10:31 PM ---------- Previous post was at 10:28 PM ----------
... That's only if you want to preserve root, I guess? AND for Pixel devices, right?
Sent from my Moto Z2 Play using XDA Labs
Click to expand...
Click to collapse
Yes. If you're otherwise stock aside from an unlocked bootloader, you can sideload the OTA zip...or, copy it to internal storage, reboot to recovery, and install it that way.
If you want to keep TWRP, you'll have to boot the TWRP image after installing and rebooting, then flash TWRP. The OTA does not wipe data (obviously); it just returns everything in /boot and /system to stock.
The Analog Kid said:
So... How's the non-rooted phone experience going so far? Because I can't get fully used to the experience yet (I have this phone for a month now) and coming from... well, ALL of my previous devices rooted too (about an eight year span as well). Even though the phone in question (Z2 Play) runs very smooth and plain "force-close-less" (yeah, you know root) I still don't find myself quite at home without Xposed and it's useful modules, for example... Oreo is nice indeed but, on the other hand, I also have this little tiny bit temptation for Android 9... Sure, if it ever lands on my phone in less than a year! Quite a bet.
Click to expand...
Click to collapse
So I actually took the advice and relocked the bootloader. No issues. I think there was one app that I would've needed root for, but I can't remember what it was. I didn't use Xposed. I don't even know if it works on the Pixel. Like I said in the opening post, I only needed it to enable wifi hotspot, so others may notice it more.
Were you able to update with ota after relocking your boot loader? I tried it after and the update would install but stay at 0% then eventually fail. Any suggestions? Thanks.
ychongy13 said:
Were you able to update with ota after relocking your boot loader? I tried it after and the update would install but stay at 0% then eventually fail. Any suggestions? Thanks.
Click to expand...
Click to collapse
You should be able to install the latest OTA image using stock recovery:
https://developers.google.com/android/ota
So, I've flashed OneUI on my phone (I only flashed AP and CSC, no new bootloader), and TWRP doesn't seem to work with it since it can't read or wipe the data partition. Also, booting is a little weird. Sometimes it works perfectly, but sometimes it goes into a freeze bootloop thing where the boot animation freezes, and a few seconds later it reboots. I'm wondering if this has anything to do with me having a treble gsi on the phone before OneUI. Maybe the partition table didn't go back to stock after flashing? (the fstab must have though, since it's in the boot img) Or maybe it has something to do with having a different csc on the phone? (phone is XEH, but the firmware is DBT) I've tried re-flashing it with no luck. (it even freezes just randomly too, then goes into the bootloop.)
VDavid003 said:
So, I've flashed OneUI on my phone (I only flashed AP and CSC, no new bootloader), and TWRP doesn't seem to work with it since it can't read or wipe the data partition. Also, booting is a little weird. Sometimes it works perfectly, but sometimes it goes into a freeze bootloop thing where the boot animation freezes, and a few seconds later it reboots. I'm wondering if this has anything to do with me having a treble gsi on the phone before OneUI. Maybe the partition table didn't go back to stock after flashing? (the fstab must have though, since it's in the boot img) Or maybe it has something to do with having a different csc on the phone? (phone is XEH, but the firmware is DBT) I've tried re-flashing it with no luck. (it even freezes just randomly too, then goes into the bootloop.)
Click to expand...
Click to collapse
Good thing you skip the bootloader and modem.
Are developer who had done kernel and twrp has disappeared.
You can try to send him a pm.
Their are universal twrp that you could try.
What twrp are you using mean build?
mchlbenner said:
What twrp are you using mean build?
Click to expand...
Click to collapse
I tried BlackMesa123's official TWRP, and the treble twrp, none of them worked how they should.
I'm gonna try that one now (actually a little later 'cause personal stuff)...
VDavid003 said:
I tried BlackMesa123's official TWRP, and the treble twrp, none of them worked how they should.
I'm gonna try that one now (actually a little later 'cause personal stuff)...
Click to expand...
Click to collapse
I have flashed the new twrp it seems to work well
From the link I sent you.
https://www.google.com/amp/s/forum....ent/recovery-blackedtwrp-t3881548/amp/?espv=1
Working twrp for ab 2018.
Oh ok, I'll try it soon.
Any idea why do the freezes/bootloops happen tho?
VDavid003 said:
Oh ok, I'll try it soon.
Any idea why do the freezes/bootloops happen tho?
Click to expand...
Click to collapse
I have no I idea I rebooted five times with no mishaps.
Could are twrp is just not fully meant for pie.
mchlbenner said:
I have no I idea I rebooted five times with no mishaps.
Could are twrp is just not fully meant for pie.
Click to expand...
Click to collapse
Idk, currently I'm on stock 9.0 recovery and I'm getting freezes, bootloops but just randomly. I'm thinking maybe somehow it's related to treble... The stock recovery is even complaining about not finding /vendor, and some other partition.
VDavid003 said:
Idk, currently I'm on stock 9.0 recovery and I'm getting freezes, bootloops but just randomly. I'm thinking maybe somehow it's related to treble... The stock recovery is even complaining about not finding /vendor, and some other partition.
Click to expand...
Click to collapse
I would do a reflash .
what did was updated to the new Oreo bootloader then flash a rooted pie backup.
I had no reboots but I rebooted it could take a threw times to reboot.
Since I flash the new twrp I can reboot without issue.
Did you flash your region pie it should not really matter I have a the Russian pie and I flashed a Canadian csc to get volte working.
If you root use magisk 18.1 zip and use the twrp I link you.
mchlbenner said:
I have flashed the new twrp it seems to work well
From the link I sent you.
https://www.google.com/amp/s/forum....ent/recovery-blackedtwrp-t3881548/amp/?espv=1
Working twrp for ab 2018.
Click to expand...
Click to collapse
So I've tried it and same thing... Also, here's what the stock recovery says (sorry for the 2 decades old webcam):
Blackmesa's TWRP:
Treble TWRP:
The one you sent me:
mchlbenner said:
I would do a reflash .
what did was updated to the new Oreo bootloader then flash a rooted pie backup.
I had no reboots but I rebooted it could take a threw times to reboot.
Since I flash the new twrp I can reboot without issue.
Did you flash your region pie it should not really matter I have a the Russian pie and I flashed a Canadian csc to get volte working.
If you root use magisk 18.1 zip and use the twrp I link you.
Click to expand...
Click to collapse
Didn't see you replied. I'll try that - flashing oreo and restoring backup.
VDavid003 said:
So I've tried it and same thing... Also, here's what the stock recovery says (sorry for the 2 decades old webcam):
Blackmesa's TWRP:
Treble TWRP:
The one you sent me:
Click to expand...
Click to collapse
Remember you have to reformat after installing twrp.
It took me only two minutes to find the new twrp.
20 reboots without issue.
mchlbenner said:
Remember you have to reformat after installing twrp.
It took me only two minutes to find the new twrp.
20 reboots without issue.
Click to expand...
Click to collapse
You mean wiping data right?
'cuz that's what's failing on the screenshots.
For me the first about 12 hours was normal, then the freezes and bootloops started happening.
So it didn't fix the bootloops, but at least TWRP works now!
VDavid003 said:
You mean wiping data right?
'cuz that's what's failing on the screenshots.
For me the first about 12 hours was normal, then the freezes and bootloops started happening.
Click to expand...
Click to collapse
No reformat it will whiipe everything mean your downloaded apps
I was able to install TWRP and root with Magisk when the pie update was uploaded on this forum.
---------- Post added at 01:25 PM ---------- Previous post was at 01:24 PM ----------
And yes you need to erase everything
Well, I was able to root and fix twrp, but I still get bootloops and freezes...
I think I'll just wait for pie to be released on my csc and until that, I'll either get used to it or go back to Phh-treble (I've never tought I'd say a custom ROM that is not even meant for this specific device is more stable (for me) than the official)
VDavid003 said:
Well, I was able to root and fix twrp, but I still get bootloops and freezes...
I think I'll just wait for pie to be released on my csc and until that, I'll either get used to it or go back to Phh-treble (I've never tought I'd say a custom ROM that is not even meant for this specific device is more stable (for me) than the official)
Click to expand...
Click to collapse
I am having the exact same issues you are. In fact, are you using my phone when I sleep?
If you want to try out a 9.0 gsi that'll run pretty darn good in the meantime, try aospext's 9. Works well enough to use daily and you'll get a "4g" constant connection.
And since you have the same issues, this should give you a flawless run. If you are just entering a clean treble, wipe it all. Everything including internal. Just not your emovable of course.
Flash the vendor in from A8 that says 8.1 and 9.0 compatible. Flash the .img. Reboot recovery flash vendor again and then gapps. I did magisk after a normal run through and the latest was a 50% pass on safety. Gonna try it again right now for a third time. No issues with booting at all. If you do it differently all hell breaks loose and you'll be booted but with a severe case of "no system webview syndrome" or "chrome ain't no system app useless-lee-itus" The force closing of apps could be mistaken for an old Atari video game..
---------- Post added at 09:28 AM ---------- Previous post was at 08:58 AM ----------
Don't do what i suggested unless you've got a frikken system webview handy from a rom. all nicely in a folder. Toss it rightly in twrp.
mindlery said:
I am having the exact same issues you are. In fact, are you using my phone when I sleep?
If you want to try out a 9.0 gsi that'll run pretty darn good in the meantime, try aospext's 9. Works well enough to use daily and you'll get a "4g" constant connection.
And since you have the same issues, this should give you a flawless run. If you are just entering a clean treble, wipe it all. Everything including internal. Just not your emovable of course.
Flash the vendor in from A8 that says 8.1 and 9.0 compatible. Flash the .img. Reboot recovery flash vendor again and then gapps. I did magisk after a normal run through and the latest was a 50% pass on safety. Gonna try it again right now for a third time. No issues with booting at all. If you do it differently all hell breaks loose and you'll be booted but with a severe case of "no system webview syndrome" or "chrome ain't no system app useless-lee-itus" The force closing of apps could be mistaken for an old Atari video game..
---------- Post added at 09:28 AM ---------- Previous post was at 08:58 AM ----------
Don't do what i suggested unless you've got a frikken system webview handy from a rom. all nicely in a folder. Toss it rightly in twrp.
Click to expand...
Click to collapse
Lol
Well, it's good to see it's not me being stupid or my phone being broken
Soo.. looks like I fixed it.. What I did is downgraded to stock 8.0 and let OTA do it's job. I know it must have updated my bootloader (thus adding new locks to my device) but so far no bootloops,freezes, or anything. It might have been the bootloader, or the modem, or idk.
VDavid003 said:
Soo.. looks like I fixed it.. What I did is downgraded to stock 8.0 and let OTA do it's job. I know it must have updated my bootloader (thus adding new locks to my device) but so far no bootloops,freezes, or anything. It might have been the bootloader, or the modem, or idk.
Click to expand...
Click to collapse
Their where no freezing or issues on Oreo.
Android pie was released and it would freeze at boot and watching videos.
So I am not an entire noob when it comes to these things, I've flashed ROMs on phones for 8 years now, but this Moto G7 Power screwed me up good.
I tried installing CrDroid from this post. I didn't even notice the A/B part at first, I went through all the usual steps, I booted TWRP, then flashed it, rebooted into the installed TWRP, flashed CrDroid, GApps and Magisk and rebooted, hoping to start Android up. At that part it all screwed up. The phone didn't boot AT ALL, and after a while I found that blankflash zip file and managed to get into the bootloader again. The only thing I can do now is boot into TWRP, not flash, and when I boot, the touchscreen does not work.
So, where do I go from here? I now only have an unlocked bootloader to play with. What are the exact steps to flash the firmware? Why do I need to flash firmware to slot A anyway? Isn't or wasn't there firmware out of the box on the device? The guides for this phone are vague and people write really short and rambling sentences in the steps and mention certain files out of the blue without explanation or download link.
1 - Which firmware file do I need? I have an XT1955-4 bought in a Dutch shop called Belsimpel with no sim. I assume it's an international variant. Here is a download list of all the firmware variants, but how do I know which one to pick? Will it wipe things like IMEI data? The box says the type is M3C94, and it seems to be this international variant.
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
4 - The 'guide' in the CrDroid thread suddenly mentions copypartitions.zip. What is that file, and why do I need to flash it? It says I have to flash it in Slot A. Does TWRP give options to switch slots? I wish I could check but since my touch screen doesn't work in TWRP..
5 - During the actual ROM install part, the guide says Flash ROM.zip + TWRP_installer/boot.img ramdisk method Why do I need to install TWRP again? And what is the ramdisk method? How do you do that?
Can someone please explain in detail step by step what I need to do?
kerelberel said:
So I am not an entire noob when it comes to these things, I've flashed ROMs on phones for 8 years now, but this Moto G7 Power screwed me up good.
I tried installing CrDroid from this post. I didn't even notice the A/B part at first, I went through all the usual steps, I booted TWRP, then flashed it, rebooted into the installed TWRP, flashed CrDroid, GApps and Magisk and rebooted, hoping to start Android up. At that part it all screwed up. The phone didn't boot AT ALL, and after a while I found that blankflash zip file and managed to get into the bootloader again. The only thing I can do now is boot into TWRP, not flash, and when I boot, the touchscreen does not work.
So, where do I go from here? I now only have an unlocked bootloader to play with. What are the exact steps to flash the firmware? Why do I need to flash firmware to slot A anyway? Isn't or wasn't there firmware out of the box on the device? The guides for this phone are vague and people write really short and rambling sentences in the steps and mention certain files out of the blue without explanation or download link.
1 - Which firmware file do I need? I have an XT1955-4 bought in a Dutch shop called Belsimpel with no sim. I assume it's an international variant. Here is a download list of all the firmware variants, but how do I know which one to pick? Will it wipe things like IMEI data? The box says the type is M3C94, and it seems to be this international variant.
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
4 - The 'guide' in the CrDroid thread suddenly mentions copypartitions.zip. What is that file, where do I download it, and why do I need to flash it? It says I have to flash it in Slot A. Does TWRP give options to switch slots?
5 - During the actual ROM install part, the guide says Flash ROM.zip + TWRP_installer/boot.img ramdisk method Why do I need to install TWRP again? And what is the ramdisk method? How do you do that?
Can someone please explain in detail step by step what I need to do?
Click to expand...
Click to collapse
1. go to settings - system - about phone check build number, this is the firmware you'll need
2. there's a thread here regarding that matter check again
3. I'm not aware of this issue
4. you'll only need to flash that file once coming from stock rom - https://androidfilehost.com/?fid=4349826312261636295
5. because it be overwritten by lineage recovery.
ramdisk method is just another way of installing twrp back when we still dont have the installer zip
vinoxflame said:
1. go to settings - system - about phone check build number, this is the firmware you'll need
2. there's a thread here regarding that matter check again
3. I'm not aware of this issue
4. you'll only need to flash that file once coming from stock rom - https://androidfilehost.com/?fid=4349826312261636295
5. because it be overwritten by lineage recovery.
ramdisk method is just another way of installing twrp back when we still dont have the installer zip
Click to expand...
Click to collapse
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
then try another version of twrp or the unofficial orangefox recovery for our device
vinoxflame said:
then try another version of twrp or the unofficial orangefox recovery for our device
Click to expand...
Click to collapse
I tried an older version of TWRP which didn't work either. I am not aware of Orangefox, but I don't see any mention, official or unofficial for the G7 Power. There's no mention in the G7 Power forum either.
kerelberel said:
I tried an older version of TWRP which didn't work either. I am not aware of Orangefox, but I don't see any mention, official or unofficial for the G7 Power. There's no mention in the G7 Power forum either.
Click to expand...
Click to collapse
it's on the telegram group
vinoxflame said:
it's on the telegram group
Click to expand...
Click to collapse
No it is not. There's no mention of G7 Power in the search results. Only E5.
kerelberel said:
No it is not. There's no mention of G7 Power in the search results. Only E5.
Click to expand...
Click to collapse
deleted
vinoxflame said:
https://t.me/mG7Power
tell me if it is not!!!!
Click to expand...
Click to collapse
From the desktop search in this one I couldn't find it: https://t.me/OrangeFoxRecovery I didn't know there was a separate chat for each device. But thanks.
FWIW when this happened to me I did the blankflash thing to get it back to bootloader. Then I used the LMSA tool from Motorola to do a rescue/restore.
I also used LMSA to force the update to the most recent security update. In general, it seems a very useful utility.
https://www.motorola.com/us/lenovo-motorola-smart-assistant
I had this issue after blankflashing this temperamental device out of a brick. While in twrp you can do "adb shell" then "twrp install /path/to/zip" I think this has to do with new twrp versions on older firmwares
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
When i had this issue go reboot fastboot
then fastboot boot recovery.img or twrp as your boot img do what you need to do just dont flash it to boot only boot from it so you preserve your real boot should fix the touch screen part only time i had prob like this is when i flashed twrp to recovery without disabling dm verity etc. But I cant even get a stock OTA since I flashed twrp as recovery nor can I find a RETUS stock recovery.img so far if i had that I can update and keep magisk etc, then reflash twrp when im done.
---------- Post added at 06:06 PM ---------- Previous post was at 05:58 PM ----------
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
When i had this issue go reboot fastboot
then fastboot boot recovery.img or twrp as your boot img do what you need to do just dont flash it to boot only boot from it so you preserve your real boot should fix the touch screen part only time i had prob like this is when i flashed twrp to recovery without disabling dm verity etc. But I cant even get a stock OTA since I flashed twrp as recovery nor can I find a RETUS stock recovery.img so far if i had that I can update and keep magisk etc, then reflash twrp when im done. The latest stock RETUS build i can find is here https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip but if i do that i will lose all my apps AGAIN etc I am trying to just get the stock recovery img from previous version so I can install the ota in magisk you just tap uninstall tap restore images to get stock boot as well then ota should work once its done go back into magisk and install to inactive slot but you will or could need TWRP A/B retention script so that you keep it even after ota...which you will first go in magisk tap uninstall restore images, but must have stock recovery not twrp installed at this time either from what i can tell, once ota is successful install the TWRP A/B Retention script but do this before you install magisk to inactive slot from magisk manager after that it should work. But I cannot locate a stock recovery.img thus far.... and I dont wanna redownload my apps right now, so I may just wait til I see a rom i really think ill like and say screw it.
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
I also installed crDroid and after that twrp-3.3.1-2-ocean.img was not responding to touch, but twrp-3.3.1-0-ocean.img works. (btw I was doing a fastboot -w in between.)
Edit:
Ah nevermind, I have it constantly when installed, with both versions.
s33b said:
I also installed crDroid and after that twrp-3.3.1-2-ocean.img was not responding to touch, but twrp-3.3.1-0-ocean.img works. (btw I was doing a fastboot -w in between.)
Edit:
Ah nevermind, I have it constantly when installed, with both versions.
Click to expand...
Click to collapse
I've flashed another stock rom (https://forum.xda-developers.com/g7-power/how-to/guide-moto-g7-power-supra-flash-to-t3927138) and it worked with twrp-3.3.1-0-ocean.img not with the newest.
kerelberel said:
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
Click to expand...
Click to collapse
You use fastboot commands in the bootloader.
The firmware contains a flash file with all fastboot commands you'll need.
kerelberel said:
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
Click to expand...
Click to collapse
TWRP has adb enabled by default. So instead of TWRP you can use
Code:
abd shell twrp --help
So you can use the basic functions like backup, install, and so on.
I had the same issue...
I'm not sure everyone is experiencing the same issue here, but I've been dealing with that exact problem the entire time I've had this phone. While this work around won't work every time, it will eventually work (for me within 3 tries). It doesn't matter if your "fastboot boot twrp.img" or running an installed version, all are the same. Even the latest 3.4.0.0.
As soon as you start recovery, start tapping the area of the screen where the "Advanced button" is in recovery. I mean tap as fast as you can, use two fingers if you need to. If it doesn't work right away, "adb reboot bootloader" and try again. I can get this to work within 3 tries. Its sucks and its stupid, but it works.
TheGuysGuysGuy said:
I'm not sure everyone is experiencing the same issue here, but I've been dealing with that exact problem the entire time I've had this phone. While this work around won't work every time, it will eventually work (for me within 3 tries). It doesn't matter if your "fastboot boot twrp.img" or running an installed version, all are the same. Even the latest 3.4.0.0.
As soon as you start recovery, start tapping the area of the screen where the "Advanced button" is in recovery. I mean tap as fast as you can, use two fingers if you need to. If it doesn't work right away, "adb reboot bootloader" and try again. I can get this to work within 3 tries. Its sucks and its stupid, but it works.
Click to expand...
Click to collapse
I getba link to one that works for u. https://t.me/CustoKernal_JavaShin_Mods/565. Fastboot boot (name of recovery)
roadkill42 said:
I getba link to one that works for u. https://t.me/CustoKernal_JavaShin_Mods/565. Fastboot boot (name of recovery)
Click to expand...
Click to collapse
Again not everyone is experiencing this same issue. A custom kernel isn't going to help when its incompatible with my ROM. My stupid workaround works for "No Touch Screen Response" in TWRP as well as OrangeFox. Its happened to me in both. Happily cruising along on Paranoid Android Quartz.
TheGuysGuysGuy said:
Again not everyone is experiencing this same issue. A custom kernel isn't going to help when its incompatible with my ROM. My stupid workaround works for "No Touch Screen Response" in TWRP as well as OrangeFox. Its happened to me in both. Happily cruising along on Paranoid Android Quartz.
Click to expand...
Click to collapse
The problem with the touch is the right driver needs to b installed that kernel I shared makes it work and stick I'm on it now go to tellagram group Moto g7 power support group both twrp and ofox there that works not the one from twrp it's self and the twrp there has some other features that one from official one has that don't work
This boot image gave me a touchscreen and allowed me to flash a regular twrp: hxxps://f.emvn.me/android-roms-and-stuff/twrp.3.4-kakarot.boot.img
Thanks to whoever made it.