I'm looking for a way to TWRP flash a Pie GSI (Resurrection Remix, to start with), and am getting the TWRP error "E:Cannot flash images to file systems" using @Pretoriano80's TWRP https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447
[EDIT] TWRP is actually v3.2.2-1 from @schwabe93
I remember there were at least two different TWRPs that worked on my M5 8.5 (SHT-W09 C567 in my case), and one of them was for a device similar to the M5 8.4, ?P10 Lite maybe?
Anyways, I'm looking for any guidance that will allow me to flash a Pie (and eventually Q) GSI img via TWRP.
THANKS
why TWRP for GSI??
you can simpely flash the gsi rr using fastboot methode
THE MAXIMUM POWER said:
why TWRP for GSI??
you can simpely flash the gsi rr using fastboot methode
Click to expand...
Click to collapse
No computer. ?
TiTiB said:
No computer.
Click to expand...
Click to collapse
Ohh, my bad, btw never install any images instead of erecovery because you will not be able to recover your tablet as you do not have PC
THE MAXIMUM POWER said:
Ohh, my bad, btw never install any images instead of erecovery because you will not be able to recover your tablet as you do not have PC
Click to expand...
Click to collapse
Thanks @THE MAXIMUM POWER
The "no computer" thing is only temporary, thankfully.
I don't fully understand your post. Do you mean the image overwrites erecovery? When I first rooted my tablet (3-4 months ago) I installed a bunch of gsi's but didn't like them, so went with LOS 15.1 and still have erecovery working—it even started it's download (I was curious).
I'm happy with LOS, but, well TiTiB stands for Tweak it Til it Breaks, sooo....I just can't help myself—gotta have something to, uh, tweak. And, as I said, I want to eventually use Android Q.
TiTiB said:
Thanks @THE MAXIMUM POWER
The "no computer" thing is only temporary, thankfully.
I don't fully understand your post. Do you mean the image overwrites erecovery? When I first rooted my tablet (3-4 months ago) I installed a bunch of gsi's but didn't like them, so went with LOS 15.1 and still have erecovery working—it even started it's download (I was curious).
I'm happy with LOS, but, well TiTiB stands for Tweak it Til it Breaks, sooo....I just can't help myself—gotta have something to, uh, tweak. And, as I said, I want to eventually use Android Q.
Click to expand...
Click to collapse
Yes, i meant do not overwrite any images over erecovery, nice name btw, i used Q on my M5 and it was very buggy, i couldn't even connect to wifi, also im verrrrrry addicted to installing gsis on my tablet, i can not stuck one week without playing around with the Tablet, e. G. Yesterday i was on resurrection remix from openkirin because it it customizable, today i reinstalled the original firmware because it is more beautiful than the stock, tomorrow im going to reinstall rr because i like the stock, after two days lineage and so on and so on.
THE MAXIMUM POWER said:
Yes, i meant do not overwrite any images over erecovery, nice name btw, i used Q on my M5 and it was very buggy, i couldn't even connect to wifi, also im verrrrrry addicted to installing gsis on my tablet, i can not stuck one week without playing around with the Tablet, e. G. Yesterday i was on resurrection remix from openkirin because it it customizable, today i reinstalled the original firmware because it is more beautiful than the stock, tomorrow im going to reinstall rr because i like the stock, after two days lineage and so on and so on.
Click to expand...
Click to collapse
Thanks for clarification. It'll be at least a few months b4 I consider Q—still too new.
Still, I want to track down the "E:Cannot flash images to file systems". I figured out that the TWRP I'm using doesn't have "System Image" as one of the options for flashing, so I was trying to flash the GSI to "System", but need to flash it to "System Image".
The quest continues!
TiTiB said:
Thanks for clarification. It'll be at least a few months b4 I consider Q—still too new.
Still, I want to track down the "E:Cannot flash images to file systems". I figured out that the TWRP I'm using doesn't have "System Image" as one of the options for flashing, so I was trying to flash the GSI to "System", but need to flash it to "System Image".
The quest continues!
Click to expand...
Click to collapse
Well, in order to see the "install as system image", you MUST decrypt your device first and then use the latese petroin twrp, but if your device was stolen by somebody, you will regret the decryption as all your data will be available for him
So i advice u touse the fastboot mode
THE MAXIMUM POWER said:
Well, in order to see the "install as system image", you MUST decrypt your device first and then use the latese petroin twrp, but if your device was stolen by somebody, you will regret the decryption as all your data will be available for him
So i advice u touse the fastboot mode
Click to expand...
Click to collapse
Already decrypted—my M5 almost never leaves the house.
I initially used @Pretoriano80's TWRP. Is that the one? I don't remember why, or even if, I didn't like it at the time. Could be that I just wanted to try something different—very typical for me.
TiTiB said:
Already decrypted—my M5 almost never leaves the house.
I initially used @Pretoriano80's TWRP. Is that the one? I don't remember why, or even if, I didn't like it at the time. Could be that I just wanted to try something different—very typical for me.
Click to expand...
Click to collapse
Good, last time i used this twrp i liked it very much, but i also uninstalled it because it did not install the system images as it should, sometimes it worked, sometimes doesnt
Installed @Pretoriano80's TWRP, RR GSI, and had loops at the RR boot screen. I let it cycle 4 times b4 giving up. Think I'll uninstall Magisk and Xposed (might be a requirement anyway) and try again.
THE MAXIMUM POWER said:
Yes, i meant do not overwrite any images over erecovery, nice name btw, i used Q on my M5 and it was very buggy, i couldn't even connect to wifi, also im verrrrrry addicted to installing gsis on my tablet, i can not stuck one week without playing around with the Tablet, e. G. Yesterday i was on resurrection remix from openkirin because it it customizable, today i reinstalled the original firmware because it is more beautiful than the stock, tomorrow im going to reinstall rr because i like the stock, after two days lineage and so on and so on.
Click to expand...
Click to collapse
So what is your verdict on the GSIs? Is there a pie one with the magnetic cover working for wakeup?
I have the SHT-AL09 C636 on Pie and I have been itching on flashing the GSIs, but I really don't have too much time nowadays to tinker :crying:
Thanks!
jgaviota said:
So what is your verdict on the GSIs? Is there a pie one with the magnetic cover working for wakeup?
I have the SHT-AL09 C636 on Pie and I have been itching on flashing the GSIs, but I really don't have too much time nowadays to tinker :crying:
Thanks!
Click to expand...
Click to collapse
The GSIs are basically and in principle good, but you can not compare them to the original firmware is well built for our device and support all features, take this for example, PUBG run on EMUI way smother than the GSI.
unfortunately, i do not have the magnetic keyboard to test it, btw yours shouldn't support it as the SHT version does not have the conection dots at the buttom
jgaviota said:
So what is your verdict on the GSIs? Is there a pie one with the magnetic cover working for wakeup?
I have the SHT-AL09 C636 on Pie and I have been itching on flashing the GSIs, but I really don't have too much time nowadays to tinker :crying:
Thanks!
Click to expand...
Click to collapse
I haven't tried any since they first came out months ago. I've read good things about EMUI 9.1, though.
BTW, still no success flashing GSI via TWRP. ?
THE MAXIMUM POWER said:
The GSIs are basically and in principle good, but you can not compare them to the original firmware is well built for our device and support all features, take this for example, PUBG run on EMUI way smother than the GSI.
unfortunately, i do not have the magnetic keyboard to test it, btw yours shouldn't support it as the SHT version does not have the conection dots at the buttom
Click to expand...
Click to collapse
Thanks for your reply, I'm talking about a magnetic cover (not the keyboard). Any case with the proper magnets will wake up the device when you open it, it is a very convenient feature in any tablet
jgaviota said:
Thanks for your reply, I'm talking about a magnetic cover (not the keyboard). Any case with the proper magnets will wake up the device when you open it, it is a very convenient feature in any tablet
Click to expand...
Click to collapse
My apologize for misunderstanding, i do not have magnetic cover, i think the openkirin.net roms might work, not sure
Related
The Sony Xperia Z2 tablet has got to be the most horrible device in android history to root or install a recovery on it. The process and the complexity of it is just horrible. You daren't ever make the slightest change to a rom or anything in twrp as it just screws everything up on this device. I can't count the amount of roms i've put on it just to totally trash the device and you have to start from scratch. Either you put a new rom on, it wipes the recovery, you have to piss about using flashtool to flash some other ftf on just to get into recovery, then you have to then flash another tft to get root, the list just goes on and on. I don't even know why sony mobile even bother offering the bootloader unlock option in the first place, it's an absolute nightmare. It's basically you can have root with the official stock firmware, if you want a custom rom spend the next 2 weeks trying to get supersu installed on it. The most horrible device I've ever come across.
Then sell it :laugh:
Somehow I cannot share this view. Running Carbon ROM with Magisk without any issues. For a more than 4 years old tablet the Z2 stands its ground, I don't regret having bought it.
Just hoping that we'll get Pie...
BabelHuber said:
Then sell it :laugh:
Somehow I cannot share this view. Running Carbon ROM with Magisk without any issues. For a more than 4 years old tablet the Z2 stands its ground, I don't regret having bought it.
Just hoping that we'll get Pie...
Click to expand...
Click to collapse
I've tried Carbon and would love to use it but it just screws up the tablet after install and recovery gets wiped so you can't even go back to restore a back up. You then have to reflash using Emma then back into flashtool to reflash the tft to get recovery to work again because flashtool ends up reporting back that the current tft is not compatible with the device. It's a finicky device to root. It's got to be the worst out of all android devices. E.g my Samsung s9 had it rooted and flashed with a custom rom in around 5 mins. No matter what firmware is installed. Sony decided that after 23.1.A.575 or whatever rooting was not possible after that. Also every method on here telling you how to do it is different to each other and inconsistant. I tried 23.1.A.575 root for UK and it would not allow for twrp to be booted into. I had to use xperiafirm to download the Taiwanese version so I could get the batch script to allow recovery so holding down power on volume down would allow twrp to load. It's just a painstakingly horrible device to root to get something so simple. But yes your right probably best time to get rid and something different. Sorry for the rant it's just been a frustration for me.
Sorry to say so, but rcstar has a very good step by step description on how to install the ROM. I followed it to the point and have no issues whatsoever.
TWRP, Magisk and Substratum work, like everything else.
It's not a device which is easy to mess with, you are right. But it's doable.
BabelHuber said:
Sorry to say so, but rcstar has a very good step by step description on how to install the ROM. I followed it to the point and have no issues whatsoever.
TWRP, Magisk and Substratum work, like everything else.
It's not a device which is easy to mess with, you are right. But it's doable.
Click to expand...
Click to collapse
I've followed so many without much success. I tried the solution by kulvertti to the letter and the tab was having non of it. I think the problem also is that a lot of the links are dead to the specific tft you need to download so getting the exact version is tricky. The only one that has worked for me is the Taiwanese rom then using the recovery script by danalec to get Marshmallow flashed which is what I'm running now. So I made a back up today and thought OK let me try carbon because I can get all the nice customization options like being able to choose a dark theme for the settings menu instead of piercing white. What is it with manufacturers wanna make every thing bright and painful on the eyes. Anyway downloaded gaps wiped system etc installed rom and once it loaded the system was all unstable and lost root and recovery. So I give up now and have to accept I can only have marshmallow on it.
Danalec has a very simple root method for Marshmallow in the general section. This is one of the best tablets out there by far. Build quality doesn't come close with other brands.
Hi all,
Feels good to be back.
let's cut to the chase, Im looking for a new Custom ROM for my RN3 Kate Device(as I always used MIUI Stable ROMs, currently MIUI10); I kept looking at all those ROMs/versions ( and some kernels ) and it's stupidly overwhelming, I can't even count them anymore; dont get me wrong tho, its a good thing.
Since Q3 2018 I've been using my RN3 Kate mostly for gaming, but also, browsing / Mail / Youtube. My RN3 It's no longer my daily driver.
So, I should be looking at performance/gaming ROMs (/Kernels), not customization centered ROMs, right ? The problem is, how can I distinguish between them ?
I mean, back in day almost every ROM/Kernel had, like, 7 or 8 lines explaining what the project was all about, not only that but also "101" Screenshots, performance numbers, all that jazz; Im not seeing that anymore, not for the most part, that is.
Other thing that grinds my gears, is the bootloader, in most threads it says that I need to unlock in MM (MIUI Dev ROM), I have already unlocked my RN3 in the same month I got it or something like that; The official unlocking way. Up to this very day (MM MIUI10 Global Stable), in the phone, it still says that is unlocked.
Even if I flash that latest Dev ROM, how can I unlock it again, how is that possible ? how does that even work ?
I would like to have some knowledge members to help me out on this, to give me some advices, if possible, It would be much appreciated.
NMRH said:
Hi all,
Feels good to be back.
let's cut to the chase, Im looking for a new Custom ROM for my RN3 Kate Device(as I always used MIUI Stable ROMs, currently MIUI10); I kept looking at all those ROMs/versions ( and some kernels ) and it's stupidly overwhelming, I can't even count them anymore; dont get me wrong tho, its a good thing.
Since Q3 2018 I've been using my RN3 Kate mostly for gaming, but also, browsing / Mail / Youtube. My RN3 It's no longer my daily driver.
So, I should be looking at performance/gaming ROMs (/Kernels), not customization centered ROMs, right ? The problem is, how can I distinguish between them ?
I mean, back in day almost every ROM/Kernel had, like, 7 or 8 lines explaining what the project was all about, not only that but also "101" Screenshots, performance numbers, all that jazz; Im not seeing that anymore, not for the most part, that is.
Other thing that grinds my gears, is the bootloader, in most threads it says that I need to unlock in MM (MIUI Dev ROM), I have already unlocked my RN3 in the same month I got it or something like that; The official unlocking way. Up to this very day (MM MIUI10 Global Stable), in the phone, it still says that is unlocked.
Even if I flash that latest Dev ROM, how can I unlock it again, how is that possible ? how does that even work ?
I would like to have some knowledge members to help me out on this, to give me some advices, if possible, It would be much appreciated.
Click to expand...
Click to collapse
If u r flashing miui fastboot rom using PC then u need to select "Clean all" option.
If u select "clean all and lock" option then ur bootloader will get relocked. So select clean all.
If your bootloader status is unlocked then good.
To check bootloader status using fastboot command.
fasboot oem device-info
If unlock= true then ur phone is jail free.
u can install latest twrp 3.2.3 img and flash custom roms.
Black_Stark said:
If u r flashing miui fastboot rom using PC then u need to select "Clean all" option.
If u select "clean all and lock" option then ur bootloader will get relocked. So select clean all.
If your bootloader status is unlocked then good.
To check bootloader status using fastboot command.
fasboot oem device-info
If unlock= true then ur phone is jail free.
u can install latest twrp 3.2.3 img and flash custom roms.
Click to expand...
Click to collapse
Hi, thx for your help !
Views run fast, replies, not so much.
I see, so we no longer need to use 3th party software, thats nice…
its sure better than Sony's lack of support back in the day…
I did it, Lattest Dev ROM "kate_global_images_9.1.10_20190110.0000.00_6.0_global_a354395fdc" got flashed, and I still get the same result, its unlocked, like it should be.
Im pretty sure that Im missing some intel here, but its ok.
Print: https: //imgur. com/a/ocqkX0G
Based on my description, can you provide any ROM/Kernel recommendations ?
NMRH said:
Hi, thx for your help !
Views run fast, replies, not so much.
I see, so we no longer need to use 3th party software, thats nice…
its sure better than Sony's lack of support back in the day…
I did it, Lattest Dev ROM "kate_global_images_9.1.10_20190110.0000.00_6.0_global_a354395fdc" got flashed, and I still get the same result, its unlocked, like it should be.
Im pretty sure that Im missing some intel here, but its ok.
Print: https: //imgur. com/a/ocqkX0G
Based on my description, can you provide any ROM/Kernel recommendations ?
Click to expand...
Click to collapse
Did u install twrp ?
Black_Stark said:
Did u install twrp ?
Click to expand...
Click to collapse
I just did, like 15 seconds ago.
Version 3.2.3-0
In this version Im no longer able to root; Im pretty sure I was running some moded version with SuperSU.
For those new custom ROMs the rooting method should be diferent anyway...
NMRH said:
I just did, like 15 seconds ago.
Version 3.2.3-0
In this version Im no longer able to root; Im pretty sure I was running some moded version with SuperSU.
For those new custom ROMs the rooting method should be diferent anyway...
Click to expand...
Click to collapse
Dont use supersu. Flash magisk if u want root.
Flash Aex pie and gapps. Nice rom with good battery.
Black_Stark said:
Dont use supersu. Flash magisk if u want root.
Flash Aex pie and gapps. Nice rom with good battery.
Click to expand...
Click to collapse
I see,
AEX 9.0, I like it, the gaming performance its also good, a bit better than MIUI10; nothing major, but still noticible. I cant notice any change in batery department, but it's holding up nicely (so far), I guess.
There's a major issue, Magisk (v18) was a "no go".
Some people are reporting a Error on flashing, in my case, I did NOT got any error, but it seems that it doesnt work anyway. Is there a workaround to this ?
Or maybe you could tell me any other ROM, root capable. Im willing to try it.
2014... 2019, Root its still not trivial, I guess some things doesn't change.
Edit: Nevermind, after some diging I found some people saying to keep flashing until the app show up. It doesnt make any sense, but it does work, after flashing the third time the app is now showing up. Rooted successfully.
Thx for your help, really appreciated.
NMRH said:
I see,
AEX 9.0, I like it, the gaming performance its also good, a bit better than MIUI10; nothing major, but still noticible. I cant notice any change in batery department, but it's holding up nicely (so far), I guess.
There's a major issue, Magisk (v18) was a "no go".
Some people are reporting a Error on flashing, in my case, I did NOT got any error, but it seems that it doesnt work anyway. Is there a workaround to this ?
Or maybe you could tell me any other ROM, root capable. Im willing to try it.
2014... 2019, Root its still not trivial, I guess some things doesn't change.
Edit: Nevermind, after some diging I found some people saying to keep flashing until the app show up. It doesnt make any sense, but it does work, after flashing the third time the app is now showing up. Rooted successfully.
Thx for your help, really appreciated.
Click to expand...
Click to collapse
U dont need to flash 3 times.
Magisk takes time to appear in first reboot. Its a bug . if it does not appear even after 5 min. Then restart phone. It will appear next reboot. I did it and it shows up in next reboot.
Black_Stark said:
U dont need to flash 3 times.
Magisk takes time to appear in first reboot. Its a bug . if it does not appear even after 5 min. Then restart phone. It will appear next reboot. I did it and it shows up in next reboot.
Click to expand...
Click to collapse
I understand, although, I can confirm this was not the case.
To be more precise, the phone was actually rebooted twice, before those re-flashes. The app was nowhere to be seen.
Some people are getting a error when flashing (maybe due to older versions), there's probably something wrong on their end too, in some way;
thanks for looking into that and finding that bug, I'm pretty sure other people will see this thread, just like I saw others.
NMRH said:
I understand, although, I can confirm this was not the case.
To be more precise, the phone was actually rebooted twice, before those re-flashes. The app was nowhere to be seen.
Some people are getting a error when flashing (maybe due to older versions), there's probably something wrong on their end too, in some way;
thanks for looking into that and finding that bug, I'm pretty sure other people will see this thread, just like I saw others.
Click to expand...
Click to collapse
Flash 17.3 magisk.
Magisk 18 is buggy.
LineageOS 17.1 - Official
There is now an official LineageOS 17.1 build available for Ocean! This was not created by me. Most credit seems to be due to SyberHexen. I'm simply posting here because nobody else has done so.
Main Page
Installation Instructions
Greek2me said:
...LineageOS 17.1 - Official...
Click to expand...
Click to collapse
A tear of joy comes to my eye. Thanks for the heads up.
I've been using it daily and so far it's great. No bugs to report yet.
Greek2me said:
I've been using it daily and so far it's great. No bugs to report yet.
Click to expand...
Click to collapse
Thanks for that reassurance.
I'll be a few days behind you. My G7 Power is on a truck. I had been shopping for new device and wanted Moto G7 Power but did not see it in LOS. Then I saw your post. Within minutes I ordered the one I had been eyeing.
As to this thread, typically an LOS official ROM thread will have certain standard language and statements in the original posts. I have no complaint, I'm obviously delighted that you shared the information and you provide links to the official instructions, but be prepared to manage the inclusion of additional information in this thread or hand the thread off to a maintainer to make it the official official thread, or we follow to a new official thread LOS Moto G7 of power.
In any event... Thanks again!
Getting the following error when trying to flash <lineage-17.1-20200912-nightly-ocean-signed.zip>
Error applying update: 18 (ErrorCode::
kDownloadPayloadPubKeyVerificationError)
IronTechmonkey said:
Thanks for that reassurance.
I'll be a few days behind you. My G7 Power is on a truck. I had been shopping for new device and wanted Moto G7 Power but did not see it in LOS. Then I saw your post. Within minutes I ordered the one I had been eyeing.
As to this thread, typically an LOS official ROM thread will have certain standard language and statements in the original posts. I have no complaint, I'm obviously delighted that you shared the information and you provide links to the official instructions, but be prepared to manage the inclusion of additional information in this thread or hand the thread off to a maintainer to make it the official official thread, or we follow to a new official thread LOS Moto G7 of power.
In any event... Thanks again!
Click to expand...
Click to collapse
I'm glad I could reach you on time! I'll keep that in mind about the thread - thanks for the heads-up.
toddk63 said:
Getting the following error when trying to flash <lineage-17.1-20200912-nightly-ocean-signed.zip>
Error applying update: 18 (ErrorCode::
kDownloadPayloadPubKeyVerificationError)
Click to expand...
Click to collapse
I would recommend that you try the installation again, taking care to follow the pre-installation instructions here. Additionally, I recommend that you wipe everything (system, data, internal storage, and cache) before attempting to install LOS.
Install went fairly smooth last night.
Have had a few times (usually when playing a video via the browser) that the "shutdown" popup will show. Phone reboots but the Lineage "corrupt" screen comes up. Hitting Try Again works and it boots successfully.
Device in hand, I’m doing some research before flashing so here is a question about backing up and restoring when using this ROM on G7 Power (and maybe A/B devices in general). I’ve become accustomed to (or spoiled by) being able to install ROM/Gapps/SU, backup, or restore OS and apps (boot, data, system) from TWRP using resources on the external SD without connecting to computer. Not only was that convenient but it was also good for ROM bug testing; easy to test > break > restore.
Having accepted the reality of being attached to a computer for some of this work I’m still wondering about the best way to get full device backups. On a Moto X4 running LOS 15.1, where I had flashed in a recommended order to keep TWRP and LOS on the device (without LOS overwriting boot) there were problems with backing up. The ROM ran fine but any attempt to back it up (whether on device running TWRP via ADB) seemed to trash the existing installation so it would not boot. To be clear I’m not talking about attempts to restore a backup; the mere act of backing up the existing partitions seemed to break things. At the time SyberHexen gave some advise but I never had a chance to try it, and wanted to do a bit more fishing here first.
So - long story/question short(er): Does anybody here know what is the most reliable way to create a “whole device” backup (equivalent to boot/data/system from before A/B) so that a ROM scrambled by testing can be easily restored…to a backup copy that can be selected from an archive of backups (as opposed to just the other slot)?
IronTechmonkey said:
Device in hand, I’m doing some research before flashing so here is a question about backing up and restoring when using this ROM on G7 Power (and maybe A/B devices in general). I’ve become accustomed to (or spoiled by) being able to install ROM/Gapps/SU, backup, or restore OS and apps (boot, data, system) from TWRP using resources on the external SD without connecting to computer. Not only was that convenient but it was also good for ROM bug testing; easy to test > break > restore.
Having accepted the reality of being attached to a computer for some of this work I’m still wondering about the best way to get full device backups. On a Moto X4 running LOS 15.1, where I had flashed in a recommended order to keep TWRP and LOS on the device (without LOS overwriting boot) there were problems with backing up. The ROM ran fine but any attempt to back it up (whether on device running TWRP via ADB) seemed to trash the existing installation so it would not boot. To be clear I’m not talking about attempts to restore a backup; the mere act of backing up the existing partitions seemed to break things. At the time SyberHexen gave some advise but I never had a chance to try it, and wanted to do a bit more fishing here first.
So - long story/question short(er): Does anybody here know what is the most reliable way to create a “whole device” backup (equivalent to boot/data/system from before A/B) so that a ROM scrambled by testing can be easily restored…to a backup copy that can be selected from an archive of backups (as opposed to just the other slot)?
Click to expand...
Click to collapse
Some people have done it with success if u not rooted and have twrp flashed u can't read internal sd it is cripted until magisk is flashed .No I heard that dmvertey will decript with out root but u can't set lock screen in os.
roadkill42 said:
Some people have done it with success if u not rooted and have twrp flashed u can't read internal sd it is cripted until magisk is flashed .No I heard that dmvertey will decript with out root but u can't set lock screen in os.
Click to expand...
Click to collapse
This is the latest twrp for this phone touch ishue should b fixed. Siberhexon updated twrp
roadkill42 said:
Some people have done it with success if u not rooted and have twrp flashed u can't read internal sd it is cripted until magisk is flashed .No I heard that dmvertey will decript with out root but u can't set lock screen in os.
Click to expand...
Click to collapse
Thanks, I've heard about issues with lock screen/encryption and would deal with that for testing purposes by disabling security before doing anything in TWRP. I may have to be content with re-flashing and restoring apps if anything breaks.
[EDIT] I saw that you added a link to a TWRP build.which is appreciated but I would first try the official one (twrp-installer-3.4.0-0-ocean.zip) which the LOS instructions indicate. If I did use an alternative I'd want to get it from a designated portal and know more about its origins.
Derp. Disregard previous mention of official build. That was Pixel not LOS. As yet this is the only thread for LOS Ocean Moto G7 Power dev.
IronTechmonkey said:
Derp. Disregard previous mention of official build. That was Pixel not LOS. As yet this is the only thread for LOS Ocean Moto G7 Power dev.
Click to expand...
Click to collapse
Well the official one is missing some things then one I posted whit h has no problems I use it
roadkill42 said:
Well the official one is missing some things then one I posted whit h has no problems I use it
Click to expand...
Click to collapse
The post you replied to was about LOS, not TWRP, but as to TWRP, I appreciate that you shared and I know custom versions of TWRP may have important additional capability, but I would still not recommend anyone use TWRP from an unknown source. You can make it a known source by sharing a link to where it came from or to its developer.
IronTechmonkey said:
The post you replied to was about LOS, not TWRP, but as to TWRP, I appreciate that you shared and I know custom versions of TWRP may have important additional capability, but I would still not recommend anyone use TWRP from an unknown source. You can make it a known source by sharing a link to where it came from or to its developer.
Click to expand...
Click to collapse
What we use on tellagram group for moto g7 power so it's is better than the one from the official it will get this soon from what I was told believe syber hexon one who did it
roadkill42 said:
What we use on tellagram group for moto g7 power so it's is better than the one from the official it will get this soon from what I was told believe syber hexon one who did it
Click to expand...
Click to collapse
Aaaahhhh, now you are making a connection to things I know. The fact that SyberHexen worked on it would be enough for me to trust it. In any event it is still best to link to the source rather than re-post (whenever possibe) so that people may see the trail and know what they are dealing with. Perhaps you could edit the post where you shared it, to say it came from some of the same devs that work on the ROM. With a note like that I would have had no doubts. In any event, I may wait for the patch to go official and work around the issue until then but it is good to know about. Thanks again for the tip and the tweaked version of TWRP.
[EDIT] Here is a direct link to the download: https://androidfilehost.com/?fid=8889791610682939639.
IronTechmonkey said:
Device in hand, I’m doing some research before flashing so here is a question about backing up and restoring when using this ROM on G7 Power (and maybe A/B devices in general). I’ve become accustomed to (or spoiled by) being able to install ROM/Gapps/SU, backup, or restore OS and apps (boot, data, system) from TWRP using resources on the external SD without connecting to computer. Not only was that convenient but it was also good for ROM bug testing; easy to test > break > restore.
Click to expand...
Click to collapse
Yes, I actually performed my entire installation using TWRP and had all of the necessary files loaded on the external SD card. The only time (to my recollection) that a PC is necessary is to launch TWRP for the first time using Fastboot.
edit: A note of caution: Be sure to follow the "copy partitions" steps regardless. If you do not, you will brick your device. This must only be done once when you transition from stock to a custom ROM.
Greek2me said:
Yes, I actually performed my entire installation using TWRP and had all of the necessary files loaded on the external SD card. The only time (to my recollection) that a PC is necessary is to launch TWRP for the first time using Fastboot.
edit: A note of caution: Be sure to follow the "copy partitions" steps regardless. If you do not, you will brick your device. This must only be done once when you transition from stock to a custom ROM.
Click to expand...
Click to collapse
Thanks. That's the same drill I used for Moto X4 so I'm set... in that regard.
Unfortunately I did a stupid thing facilitated by Moto's dreadful documentation. Having used several devices with sim/SD tray in top right top edge, and with the in-box documentation failing to label the Mic that is now at the top right edge, I very likely damaged the mic thinking it was the tray. My fault for missing a different label for the tray but Moto made this error too easy (and their support claimed the top Mic was the proximity sensor). I will try to exchange device and start over.
does anyone know how to "relock" bootloader on this device even if that is just removing the bootloader lock warning?
IronTechmonkey said:
Thanks. That's the same drill I used for Moto X4 so I'm set... in that regard.
Unfortunately I did a stupid thing facilitated by Moto's dreadful documentation. Having used several devices with sim/SD tray in top right top edge, and with the in-box documentation failing to label the Mic that is now at the top right edge, I very likely damaged the mic thinking it was the tray. My fault for missing a different label for the tray but Moto made this error too easy (and their support claimed the top Mic was the proximity sensor). I will try to exchange device and start over.
does anyone know how to "relock" bootloader on this device even if that is just removing the bootloader lock warning?
Click to expand...
Click to collapse
Not recommended as this can really brick your device.
Just flash custom bootloader logo.bin to remove that screen
---------- Post added at 12:38 AM ---------- Previous post was at 12:37 AM ----------
I'll be making new devdb posts for official G7 ocean/channel..
once threads are active please post there.
Thx
SyberHexen said:
Not recommended as this can really brick your device.
Just flash custom bootloader logo.bin to remove that screen
Click to expand...
Click to collapse
That's what I was fishing for. There may be a chance I don't have to exchange device but if so that's what I'll do. Thanks for the coaching and for the work on Moto devices, especially the G7 Power.
Hi, I just noticed you have to flash with a pc every time with roms with this phone. Is there no way to flash roms with twrp? And if so how come? Search function if completely broken so I can't search if this has already been asked
Which exact model do you have? On my XT2041-4 I had no issue just doing "fastboot flash recovery twrp-3.4.0-0-sofia-test9.img" and replacing the recovery without problems. Although people with differing models have reported touch screen issues (although some suggest plugging in a usb mouse to bypass them).
So if you can get TWRP installed there shouldn't be any need to use a computer anymore, although its not such a big hasstle really how often do you flash a new ROM when you are away from your computer? As for the backup/restore function it is unreliable with the G Power.
Not sure about model but its the eu version XT2041-3 I think?
Anyway, I had intalled a newer version of twrp and that's why I had issues. I installed the one you suggested and now it works so thanks a lot! I saw a few people say recovery was bad for this phone so that's why I thought it wouldn't work. So again thanks!
Tronicdesu said:
Not sure about model but its the eu version XT2041-3 I think?
Anyway, I had intalled a newer version of twrp and that's why I had issues. I installed the one you suggested and now it works so thanks a lot! I saw a few people say recovery was bad for this phone so that's why I thought it wouldn't work. So again thanks!
Click to expand...
Click to collapse
Glad it works for you, what they mean by bad I guess is the bug I mentioned on some models, and the backup/restore function not working properly with encrypted data. You will also have to reflash the original recovery if you want to apply an OTA update.
Forgive the intrusion, but I believe in his original post Tronicdesu asks a valid question which remains unanswered. It seems to me he's asking about flashing ROMs, not flashing TWRP.
You can indeed flash TWRP using a PC and then use TWRP when detached from your PC. But what can you do with TWRP besides flashing modules and wiping data and such? Can you flash a new ROM? I'm pretty sure you cannot. Can you backup your phone? Maybe not. But I'm not 100% sure on either count.
Most OP installation instructions in these ROM forums describe using your PC to install their custom wares. This is a far cry from the good old days of downloading a ROM, a new Gapps, then firing up TWRP. Remember CWM?
It seems to me custom ROM flashing is dying a slow death from complications introduced by Project Treble. Perhaps Treble made life easier for vendors wanting to update their existing phones with (mostly non-existent) ROMs. But lightly-committed enthusiasts have a devil of time installing a custom ROM nowadays.
In the case of Motorola, it doesn't help when they sell ninety-nine variants of the same hardware to retail customers, and more to a dozen different carriers.
I just bought my new Moto G Power 2020 from Amazon. I love the hardware. But when I look at custom ROM options and the steps needed... Crikey! Do I have to stand on one foot and stick my finger somewhere?
Forgive the rant, am I barking up the wrong tree here?
As for the backup/restore function it is unreliable with the G Power.
Click to expand...
Click to collapse
Yeah, so just cross your fingers.
...A few people say recovery was bad for this phone so that's why I thought it wouldn't work. So again thanks!
Click to expand...
Click to collapse
Yup, and a big shout out to Team Win Recovery Project!
I'm not trolling here. I don't know what to do with my fingers! Bite them?
Hi
Quite bored of Oneplus updates for my Nord 2 5G that transforms more and more the phone in publicity support for OnePlus CEO messages, and adding features I don't care at all, I'm looking to flash it with an alternative ROM.
What is most stable and operational ROM for that device currently ? The version of the device I have is DN2103 (bought in Switzerland).
Thanks for your advices,
Vincèn
Tried them all. Evolution X is the most often updated and works the best for me.
Hey there!
I also need some much needed insight in how to continue with this device (DN2103 bought in NL, Europe; just updated from 11.A.14 to 11.A.21). I suspect I will probably need the same answer as OP is looking for.
This is my second OnePlus, I was using a OnePlus X before running my first and only ROM, Lineage OS, to be able to move on to Android 10. Then screen broke for the second time after I had already fixed up the whole phone myself before that using brand new parts (Screen, frame, backplate) except for the motherboard still original. So I decided it was time for a new device.
Really love the DN2103 itself, except for the whole rooting / OTA update process, although it was a good training in getting to know all the technicalities. I had been running rooted 11.A.14 since it came out till yesterday, because I was avoiding dealing with the whole process again.
Anyway I kicked myself under my butt and got myself to 11.A.21 now. I was planning to just continue updating OOS till the latest 11.C.10 / 11.C.13, because after all this effort, I'm too curious to not check out the new Android.
But I just happened to read some thread where people were saying that somewhere after 11.C.4 it's not possible anymore to get into fastboot / BROM mode and thus no means to get TWRP?? That sounds horrible, one mistake rooting and it would be a big mess, having to downgrade to OOS 11 again and bla bla bla, why the f...?
So, I just need to hear this from someone, is this correct? I'm too tired to investigate now myself after a 20h OTA/rooting session behind me and just 3h sleep.
And how is everyone dealing with it that wants root? Has everyone moved on to other ROMs for Android 12 / 13, because of this?
In the update process yesterday for some reason my phone did a complete wipe without asking / warning. So I really need to get to a stage in this update process where I can restore all my ****. I've been at this for 24h right now and was happy to do so as I was making steps. but now I suddenly got hit in the face by this news.
tl;dr PLEASE confirm/deny this news (underlined part above) and help me decide if the only comfortable way is to ditch OOS for a custom ROM to get Android 12 / 13 with root & TWRP. I've thrown 24 hours into OTA updating OOS 11, now got to 11.A.21, but phone somehow got wiped in process, so now I really need to finish upgrading and restore data, because I'm without all the apps / accounts etc. I depend on for daily life.
I do really enjoy the road but now I HATE being lost along the way. Show me the light and, if ROM, same question as OP
Sorry if a bit off-topic + long post...
Yes, you need to have android 11 to enter fastboot. I had 12 and had to downgrade. Trust me, this is the most fuked up thing.
wuttehhell said:
Yes, you need to have android 11 to enter fastboot. I had 12 and had to downgrade. Trust me, this is the most fuked up thing.
Click to expand...
Click to collapse
Stop waiting for oneplus. There are great roms on android 13 that work very nice. What i am using is Evolution X. Tried them all and this is the one i stick to. Found no bugs, very consistent updates and the team as i see work very fast on every bug people find.
Btw, u dont need root to change rom, only if you want. I personally dont use root and works great.
wuttehhell said:
Tried them all. Evolution X is the most often updated and works the best for me.
Click to expand...
Click to collapse
Thanks for the info, and noticed too in forum that it looks to be the most up-to-date and maintained ROM for DN2103 and it looks to have no more any blocking bugs such as Wifi or Bluetooth not working, or random reboots/crashes. I'm running right now version DN2103_11_C.12 with Android 12. Is it ok to upgrade to Evolution X straight ? as I see people speaking about downgrade first to Android 11 :/
wuttehhell said:
Stop waiting for oneplus. There are great roms on android 13 that work very nice. What i am using is Evolution X. Tried them all and this is the one i stick to. Found no bugs, very consistent updates and the team as i see work very fast on every bug people find.
Click to expand...
Click to collapse
Thanks a lot for confirming! I'd already read the thread and indeed Evolution looks like the best option, so that's decided then. Wish me luck flashing the ROM
And about root, I really have some essential mods that need root. For example Advanced Charge Controller (I use it with the GUI app ACCA for convenience, else it's only terminal). I limit my charging by default to 80%, which translates in about a 4x increase in lifetime of the battery. On normal days I don't need any more than that, and it always has the option to charge to 100% if you know you're gonna have a long day without charging capabilities.
vincebay said:
Thanks for the info, and noticed too in forum that it looks to be the most up-to-date and maintained ROM for DN2103 and it looks to have no more any blocking bugs such as Wifi or Bluetooth not working, or random reboots/crashes. I'm running right now version DN2103_11_C.12 with Android 12. Is it ok to upgrade to Evolution X straight ? as I see people speaking about downgrade first to Android 11 :/
Click to expand...
Click to collapse
As I understand, and as @wuttehhell just confirmed in this thread, once you update OxygenOS beyond Android 11, fastboot and BROM mode don't work anymore. This means you can't install a custom recovery like TWRP to flash a new ROM, neither can you flash it using fastboot.
This means you have to rollback to Android 11 first. Fortunately OnePlus has official rollback packages, which is just a .ZIP archive like any other update, except it will downgrade to a previous version. Warning: a rollback package will WIPE ALL DATA. So make sure to backup anything you need to keep before downgrading. The upside is you can do a clean flash of the ROM (flashing method where device gets wiped), which is the most stable method and gives you a fresh OS that will use less battery and such.
I think the process of downgrading itself is very simple though. If you get stuck let us know, there's many knowledgeable people here lucky for us so keep a positive attitude and with a little luck we'll both be running Evolution X in the coming days!
Releece said:
As I understand, and as @wuttehhell just confirmed in this thread, once you update OxygenOS beyond Android 11, fastboot and BROM mode don't work anymore. This means you can't install a custom recovery like TWRP to flash a new ROM, neither can you flash it using fastboot.
This means you have to rollback to Android 11 first. Fortunately OnePlus has official rollback packages, which is just a .ZIP archive like any other update, except it will downgrade to a previous version. Warning: a rollback package will WIPE ALL DATA. So make sure to backup anything you need to keep before downgrading. The upside is you can do a clean flash of the ROM (flashing method where device gets wiped), which is the most stable method and gives you a fresh OS that will use less battery and such.
I think the process of downgrading itself is very simple though. If you get stuck let us know, there's many knowledgeable people here lucky for us so keep a positive attitude and with a little luck we'll both be running Evolution X in the coming days!
Click to expand...
Click to collapse
@Releece thanks for the details and so if I have well understood the whole process:
backup datas
Downgrade to Android 11 using the OTA downgrade package and procedure from oneplus (which implies a full reset of device)
Reboot at least one tine in Android 11
Flash TWRP
Reboot in TWRP (be careful not to boot Android or I'll have to reflash TWRP)
Flash Evolution X zip
Boot normally and enjoy Evolution X
Am I correct ? I have seen also that the phone has the same annoying double "bank" when you flash it that I had on previous OnePlus phones. Does it imply I have to do each flashing process on both banks ?
Thanks
vincebay said:
@Releece thanks for the details and so if I have well understood the whole process:
backup datas
Downgrade to Android 11 using the OTA downgrade package and procedure from oneplus (which implies a full reset of device)
Reboot at least one tine in Android 11
Flash TWRP
Reboot in TWRP (be careful not to boot Android or I'll have to reflash TWRP)
Flash Evolution X zip
Boot normally and enjoy Evolution X
Am I correct ? I have seen also that the phone has the same annoying double "bank" when you flash it that I had on previous OnePlus phones. Does it imply I have to do each flashing process on both banks ?
Thanks
Click to expand...
Click to collapse
Yep that should do it, looks like you did your research and understand the process.
I had the same question earlier. Strangely I found that the Nord 2 does not have A / B partitioning. I can only detect an A-partition with apps designed to test it. I didn't have to do anything extra / another way while rooting with Magisk, OTA updates or flashing ROM. I thought A/B was enforced on all phones since Android 10 or sth, but apparently not all.
I would add one extra step, after you reboot into TWRP (before flashing the ROM) make a backup of all the individual partitions one by one (so you can restore any single partition in the future), even the tiniest ones.
Some contain calibration data for e.g. Bluetooth and fingerprint sensor that are specific to your device. Now this whole process should leave them untouched, but if anything ever happens to them, the only way to get your phone working again is to send your phone to a service centre, so it's a good idea to have everything backed up.
They will be stored in the TWRP folder in /sdcard/, which is the folder you can see on your PC. So after backing them all up, you can just copy them to your PC.
I successfully flashed Evolution yesterday, and all went well Initially the new Android 13 UI was a bit of a shock from what I was used to, but I'm starting to like it already, especially after going over the settings. And it works smooooth like butter. The only thing that annoyed me was the haptic feedback, which feels very mushy instead of snappy. But putting vibration strength to low helps a lot. Maybe I can find a way to modify it later.
I had one little hickup: Evolution install instructions say this for TWRP before flashing ROM:
"3. Tap [Wipe] , then [Format data]. type "yes" and Enter"
But when I did this, it removed the media folder at /data/media/ instead of just emptying it. I remember it gave me a pop-up saying something like, for /data/media/ to get populated I would probably need to boot to system. But if I would've done that stock would overwrite recovery.
I don't have a lot of knowledge about this, but this folder gets mounted to /sdcard/ and is where your internal storage is mounted to. So after the wipe I wanted to copy the ROM .zip to my phone using the file manager. Windows did recognize my phone as having internal storage, and I could open it, but it didn't see any file/folder/free space and I couldn't copy anything to it.
I solved it by renaming ROM to sth simple like evolution.zip, placing it inside platform-tools folder, and then using ADB push command, so it looked like:
ADB push C:/platform-tools/evolution.zip /data/
It doesn't give any feedback while copying and I didn't even see much disk usage on Windows task manager, so I was about to get nervous and close the terminal, but then it suddenly completed successfully and I could see the evolution.zip in TWRP file manager. After that flashing took just a few minutes and everything went perfect.
Now I don't know if it's maybe a typo in the instructions or if TWRP had a bug, but I don't think so as it specifically gave me a prompt about it. I think it's better to just tap [Wipe] and then do the usual factory reset slider, with data, dalvik and cache selected. Think I'll make a post later in the Evolution thread to ask.
Good luck!
Hi, I don´t like the colors on Oxygen OS. I don't know if it's cause by our screen or is something related with the ROM. In Samsung or Xiaomi colors are more brilliant and saturated. In Evolution ROM, can you modify this issue?
So I have been able to dowgrade my DN2103 to 11_A20 running Android 11 but I'm stuck there !
Each time I try to flash twrp or load it in device I get that:
[email protected]:~/Bureau$ fastboot boot twrp.img
Sending 'boot.img' (131072 KB) OKAY [ 3.310s]
Booting FAILED (remote: 'not allowed in locked state')
fastboot: error: Command failed
[email protected]:~/Bureau$ fastboot flash recovery twrp.img
Sending 'recovery' (131072 KB) OKAY [ 3.371s]
Writing 'recovery' FAILED (remote: 'not allowed in locked state')
fastboot: error: Command failed
I have unlocked OEM protection into it and allow USB debug. Any ideas what's the problem ?
damn was a long time I had not done Android flashing so was a little more complicated but made it (well it looks to be so far Will see if it boots after initial setup and now hanging on the Phone initial preparation but should go very soon I think
Thanks