Related
Every Pie Rom I've installed with the February Update, kills my WIFI. It comes and goes, it's not stable. Check it guys, CHECK IT.
JJ5150 said:
Every Pie Rom I've installed with the February Update, kills my WIFI. It comes and goes, it's not stable. Check it guys, CHECK IT.
Click to expand...
Click to collapse
Strange, i'm running Ressurection Remix with no problems at all. Maybe you should check/reflash your radio?
Wisse said:
Strange, i'm running Ressurection Remix with no problems at all. Maybe you should check/reflash your radio?
Click to expand...
Click to collapse
Resurrection Remix is still UNOFFICIAL. Last version is 02/09. February OFFICIAL Security Update was Updated February 16-19, and all the PIE ROMS that are OFFICIALLY Updated with this update KILL THE WIFI.
Thanks tho.
I am using pixel experience and there isn't any problem I encountered
SAPTADIP MALAKAR said:
I am using pixel experience and there isn't any problem I encountered
Click to expand...
Click to collapse
May I ask what model number you have?
I'm running AEX 6.3 and my wifi is perfectly fine.
JJ5150 said:
May I ask what model number you have?
Click to expand...
Click to collapse
Hey , I am using Moto G5s plus and the model number is XT1804.
SAPTADIP MALAKAR said:
Hey , I am using Moto G5s plus and the model number is XT1804.
Click to expand...
Click to collapse
I'm on XT1806
I was presented with a workaround... Disable WIFI scanning in settings. Fixes Wifi drops. NO DICE. Totally unstable wifi.
No problem with me too.. using pixel experience on xt1804
I'm using havoc os in my XT1806 and everything is working great, also most people don't have your problem, you should restore your stock ROM backup and try to clean flash any pie ROM, this is not the devs fault.
Juancasa14 said:
I'm using havoc os in my XT1806 and everything is working great, also most people don't have your problem, you should restore your stock ROM backup and try to clean flash any pie ROM, this is not the devs fault.
Click to expand...
Click to collapse
Hi, i have a XT1806 too, I want to have the gcam, I just unlocked the bootloader, but I'm afraid to root it and flash a rom, how did you do it, thanks
prophetgamer said:
Hi, i have a XT1806 too, I want to have the gcam, I just unlocked the bootloader, but I'm afraid to root it and flash a rom, how did you do it, thanks
Click to expand...
Click to collapse
Hi ! Don't be afraid, if you follow every step correctly you shouldn't have any problems, if you already unlocked your bootloader you should flash the latest version of TWRP if you want to root your phone, you can't use gcam unless you do it because you need to enable cam2api by adding a specific line to the build.prop.
If you decide to root it, just flash the treble version of TWRP and then flash the latest version of magisk, then you'll be able to modify your build.prop !
Ask me if you need any help
Juancasa14 said:
Hi ! Don't be afraid, if you follow every step correctly you shouldn't have any problems, if you already unlocked your bootloader you should flash the latest version of TWRP if you want to root your phone, you can't use gcam unless you do it because you need to enable cam2api by adding a specific line to the build.prop.
If you decide to root it, just flash the treble version of TWRP and then flash the latest version of magisk, then you'll be able to modify your build.prop !
Ask me if you need any help
Click to expand...
Click to collapse
hello again, I tried to make a backup of the system image but it always says backup failed, I already made the wipe data to decrypt, but it did not work
prophetgamer said:
Hi, i have a XT1806 too, I want to have the gcam, I just unlocked the bootloader, but I'm afraid to root it and flash a rom, how did you do it, thanks
Click to expand...
Click to collapse
prophetgamer said:
hello again, I tried to make a backup of the system image but it always says backup failed, I already made the wipe data to decrypt, but it did not work
Click to expand...
Click to collapse
You don't need to backup the system image, just backup system, data and boot, and also persist and efs just in case you lose your IMEI. Are you using treble TRWP?
I got the T-mobile REVVLRY+ today, and naturally, I wanted to put the stock motorolla firmware on it. Partly to see if I could, partly to get rid of the T-Mobile bloat and see what Motorola features T-Mobile had removed.
Everything went swimmingly, I have PPW29.98-107 installed, I even have WIFI Calling. What I did lose, however, is VoLTE. I did use TWRP to perform a backup before flashing, so I tried restoring it to get a better look at how VoLTE works in the T-Mobile firmware. This is where things got hairy. I stupidly only backed up boot, system, and data. When I use TWRP to restore them, I get stuck in a boot loop. The built in boot loop fix in TWRP didn't help.
1. Any ideas on getting as close to stock as I can with only the boot, system, and data partitions?
2. Does anyone have access to a REVVLRY+ that would be willing to do a full backup that I may try to restore?
*Edit* SO I used the code *#*#4636#*#* and VoLTE provisioned is enabled, so maybe I do have VoLTE?
*Edit 2* Google Pay doesn't work, even after locking the bootloader. The device says that the operating system has been modified. Still trying to get it to restore.
FOUND IT!
I found a repo of firmware that has the TMO firmware! flashing now!
I can't share the external link yet.
BanterJSmoke said:
I found a repo of firmware that has the TMO firmware! flashing now!
I can't share the external link yet.
Click to expand...
Click to collapse
Where did you find it at? I would like to know because I'm trying to port Lineage OS to this phone. However, once I unlock the bootloader, I won't have an OS to use for it and i'll be screwed.
serris-chan said:
Where did you find it at? I would like to know because I'm trying to port Lineage OS to this phone. However, once I unlock the bootloader, I won't have an OS to use for it and i'll be screwed.
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/lake/official/TMO/
HOW to
Hi, I just picked up the Revvlry+. Do you have step by step to install the Stock Moto firmware? I miss some of the features of the Moto. Also, was it easy to restore the TMO firmware just in case?
did you make any progress into the volte research? im on a unlocked xt1965-2 and using metro but i dont get volte in any of the stock roms or custom roms. i have tried flashing the modem from the stock tmo rom which didnt really do anything. i will probably try to flash the entire tmo rom tonight and see if it boots. im thinking if i get volte in the tmo rom and backup the persist, vendor and efs. then if i restore them onto a working cutom rom with volte enabled, volte should work.
i have also read about different scenarios in where you have to install workarounds to enable volte on treble roms. like installing the ims.apk to route the calls to volte and flashing a volte enabler to inject the correct files into the vendor partition.
my other device is a moto g5 plus which has numerous volte issues when switching between stock and custom roms or between different versions of android.
Did you use the Moto G7 Plus TWRP? I just picked up a Revvlry+ and I'm looking to root to install lawnchair or pixel launcher as a system app.
successfully unlocked the bootloader of my t-mobile revvlry which is a rebranded moto g7 i did it using this method but i'm going to be a little cautious on rooting unless i know it's safe and won't brick i could use some help with this https://www.androidinfotech.com/root-moto-g7-plus-pie/ i have the revvlry not the plus i want to try multirom installer and install ubuntu touch on it but i don't want to screw up my only phone but the only way i can try it is if i had root permissions to do so to install linux tried userland but i couldn't get unity desktop to work i'd rather have full root instead of fakeroot update: i was able to boot twrp before but now it doesn't work i think my firmware updated cause now when i run fastboot boot twrp.img nothing happens and i end up with remote failed reboot the phone and it goes directly to recovery with the only option is to do a factory reset
ghostdogg49504 said:
successfully unlocked the bootloader of my t-mobile revvlry which is a rebranded moto g7 i did it using this method but i'm going to be a little cautious on rooting unless i know it's safe and won't brick i could use some help with this https://www.androidinfotech.com/root-moto-g7-plus-pie/ i have the revvlry not the plus i want to try multirom installer and install ubuntu touch on it but i don't want to screw up my only phone but the only way i can try it is if i had root permissions to do so to install linux tried userland but i couldn't get unity desktop to work i'd rather have full root instead of fakeroot update: i was able to boot twrp before but now it doesn't work i think my firmware updated cause now when i run fastboot boot twrp.img nothing happens and i end up with remote failed reboot the phone and it goes directly to recovery with the only option is to do a factory reset
Click to expand...
Click to collapse
Are you saying with a Tmobile Revvlry, you were able to just go to the Motorola bootloader unlock page, paste your unlock codes, and presto as if it was just a normal Moto phone? If so, that is awesome!
I am thinking of swapping my Moto G7 Play with a Revvlry because of the 3gb RAM and NFC (the size of the G7 Play is perfect, I don't want to be forced to carry around a giant phone), but would love to flash the stock Moto G7 Play ROM over the Tmobile version. Not sure I'm willing to risk it, but if anyone has tried, I'd love to hear about it.
Logged into my account for this. Sorry if this is a little offtopic, but I want to see if this phone is compatible(or rather, how compatible it is) not only with Stock ROMs, but also with custom ROMs. For those REVVLRY owners, what have been your experience with this?
ultracoolguy said:
Logged into my account for this. Sorry if this is a little offtopic, but I want to see if this phone is compatible(or rather, how compatible it is) not only with Stock ROMs, but also with custom ROMs. For those REVVLRY owners, what have been your experience with this?
Click to expand...
Click to collapse
Phone works great with stock ROMs. I haven't tested out any custom ROMs, but I do have root on my REVVLRY.
tri_cchan said:
Phone works great with stock ROMs. I haven't tested out any custom ROMs, but I do have root on my REVVLRY.
Click to expand...
Click to collapse
nice man
Relocking Bootloader
Would I do the OEM lockbootloader command to lock it back
Can confirm flashing Moto g7 play firmware on T-Mobile revvlry. Caveat, you can no longer take OTA's and NFC is broken. Also can be bootloader unlocked through the Moto website.
Wouldn't you need to flash the G7 plus firmware for NFC to work?
guitardoc64 said:
Wouldn't you need to flash the G7 plus firmware for NFC to work?
Click to expand...
Click to collapse
That makes sense, the SD632 is NFC capable however I'm on the G7 play not the plus (I know, I know wrong forum)
I can't get the stock rom to work. It just bootloops every time. I tried all 3 versions. Any ideas?
Hey friends, would one of you kind sould who own the Revvlry+ be kind enough to post this Wallpaper?
Thanks in advance!
BanterJSmoke said:
I found a repo of firmware that has the TMO firmware! flashing now!
I can't share the external link yet.
Click to expand...
Click to collapse
Did you manage to restore it with firmware? Because I have a bootloop and I'm looking for a solution
quiet boy
I just solved the problem I had like 4 crazy hours with solve bootloop, the problem that I commanded automatic flash, not flashing the vendor partition and then flashed the manual vendor partition
mfastboot flash vendor vendor.img and ready
edit:
for users with Revvlry+ variant (XT1965-T) use this Flash.bat
[Important] Read this before FLASHING/Updating to Stock PIE 9 {SPRINT,TMO AT&T ETC}
Mates! for newbies specially Sprint,TMO and Atn&t users I know you are sad to hear that you won't get stock Pie update and you have been watching threads here on XDA showing how to flash captured Stock Pie of Verizon/Brazil variant on your Sprint ,at&t TMO variants this very important to know that DO NOT UPDATE/FLASH 9.0 Pie update of Verizon/Brazil variants. Otherwise you will loose your IMEI, Baseband N, modem. AND definitely NO WIFI and there is turning back
That update only works for Verizon/brazil variant devices which are getting updates by Motorola it's not for sprint at&t tmo etc THIS ONLY WORKS FOR VARIANTS WHICH ARE ANNOUNCED BY MOTO.
Reasons: when you flash stock pie your Oreo modem is replaced with Pie modem which doesn't matches to your variant which results in loosing of imei,base band and wifi.
Even if you try to flash back oreo with a clean flash you may be able to use your stock oreo but due to pie modem you won't be able to downgrade to your oreo modem and in result your imei baseband will still be gone with pie and there is no solution haven't been found yet.
Please if you really want to use pie there are other custom roms like Dirty Unicorns, CR Droid,Havoc and Lineage OS use them till the developers found an solution for this problem. Thank you!
just don't flash modem,see no problems.sprint - pie
Can at&t ariants flash it?
As it is locked...
Dreamerok said:
just don't flash modem,see no problems.sprint - pie
Click to expand...
Click to collapse
Considering that I've tried to flash the Verizon Pie Image on my Z2 force, and nearly made it useless, how did you do yours? Flashing the Indian Variant?
KOAO said:
Considering that I've tried to flash the Verizon Pie Image on my Z2 force, and nearly made it useless, how did you do yours? Flashing the Indian Variant?
Click to expand...
Click to collapse
yeap
indian via fastboot without mode etc guide on the forum. or manual flash via fastboot each file.
found this
Found this forum:
bbs.ixmoe.com/t/topic/22171
Could be a solution to unbrick ?
Dreamerok said:
yeap
indian via fastboot without mode etc guide on the forum. or manual flash via fastboot each file.
Click to expand...
Click to collapse
So.....you flashed everything but the modem files and everything works for Sprint? I'd assume you didn't flash the bootloader?
Basically want to know which files you flashed and what issues you've seen if any. Much appreciated ??
gokart2 said:
So.....you flashed everything but the modem files and everything works for Sprint? I'd assume you didn't flash the bootloader?
Basically want to know which files you flashed and what issues you've seen if any. Much appreciated
Click to expand...
Click to collapse
work fine for me. some bugs with wifi (quick connect disconect sometimes)
battery better. twrp * magisk + gpay ) gcam last works perfect. motocamera & motoprojector ? moto verve buds work
Just came to me....there might be a way to revert back firmware. Way back in 3vo 3d days there was a Boost mobile update that had a newer Android version then what the Sprint people got. So many of us flashed it and had problems. And couldn't revert back.
The best kernel dev I've seen to date (name cannot be given due to settlement between him an xda) found he could hex edit the previous bootloaders version number to be post the Boost version, which then allowed it to flash. And we could then revert back to the Sprint firmware/ROM. I don't know how Moto checks or limits firmware flashing, but just an idea?
I have same problem but i had Lineage OS Backup and flashed it. Now I have normal Lineage OS on Partition B and Lineage OS with Problem on Partition A. (Official Rom only uses A partition, Lineage OS supports A/B partition update). I don't know if there is any way to copy B partition IMEI and Baseband on Partition A.
Moto z2 force sprint
I have also same issue no wifi or network n also no imei if i install lineage os will it resolves imei issue
Zuhaib King said:
I have also same issue no wifi or network n also no imei if i install lineage os will it resolves imei issue
Click to expand...
Click to collapse
can you update what have you done?
Zuhaib King said:
I have also same issue no wifi or network n also no imei if i install lineage os will it resolves imei issue
Click to expand...
Click to collapse
I have the same problem. Can I fix it somehow?
I've tried everything and I just get a bootloop. If anyone has the steps that worked for them I'd love to have my root back. Thanks community!
What exactly have you tried? We can't give you a solution for problems we don't know...
Had the same problem on 118-15-11-2, so I flashed 55-37-7 instead and it rooted fine on Magisk 20.1.
Will 55-37-7 work with Tmobile Moto G6? Haven't tried flashing that one yet.
fireman644 said:
Will 55-37-7 work with Tmobile Moto G6? Haven't tried flashing that one yet.
Click to expand...
Click to collapse
I have a Moto G6 (Ali) xt1925-6 and yes currently on retail ppss29.55-37-7 which has October patch. I've not had any problems flashing the 118 or the 55 retail builds as long as they have same or newer security patches.
Skippy12359 said:
Had the same problem on 118-15-11-2, so I flashed 55-37-7 instead and it rooted fine on Magisk 20.1.
Click to expand...
Click to collapse
Did you install Magisk by patching the recovery.img (recovery mode)? Normal installation through boot.img causes a bootloop, afaik.
https://forum.xda-developers.com/moto-g6/how-to/magisk-twrp-moto-g6-t4006983
WoKoschekk said:
Did you install Magisk by patching the recovery.img (recovery mode)? Normal installation through boot.img causes a bootloop, afaik.
https://forum.xda-developers.com/moto-g6/how-to/magisk-twrp-moto-g6-t4006983
Click to expand...
Click to collapse
After flashing and setting up 55-37-7 stock pie, I booted to twrp and flashed magisk 20.1. It boot fine and then installed magisk manager apk and had root.
Skippy12359 said:
After flashing and setting up 55-37-7 stock pie, I booted to twrp and flashed magisk 20.1. It boot fine and then installed magisk manager apk and had root.
Click to expand...
Click to collapse
Alternate route - I flashed to ALI_RETAIL_9.0_PPS29.118-11-1 (back to July Pie) and used magisk 19.3, DM Verity Disabler from August.
Seems to work fine, but wants to keep updating the system with latest version of Pie from December.
I did try to flash ALI_RETAIL_9.0_PPS29.55-24, but that killed my T-Mobile connection (wouldn't turn on the radio and/or recognize the SIM.)
Can anyone tell us what the difference between 55 and 118 variants are?
PS. My phone is the U.S. G6.
oldguy51 said:
Alternate route - I flashed to ALI_RETAIL_9.0_PPS29.118-11-1 (back to July Pie) and used magisk 19.3, DM Verity Disabler from August.
Seems to work fine, but wants to keep updating the system with latest version of Pie from December.
I did try to flash ALI_RETAIL_9.0_PPS29.55-24, but that killed my T-Mobile connection (wouldn't turn on the radio and/or recognize the SIM.)
Can anyone tell us what the difference between 55 and 118 variants are?
PS. My phone is the U.S. G6.
Click to expand...
Click to collapse
The big question is which variant of the Moto G6 do you have? For example I have XT1925-6 which is the US Unlocked variant. You need to flash the correct firmware for your variant.
https://mirrors.lolinet.com/firmware/moto/ali/official/
Go here once you know your variant to get the exact right firmware. Who is your provider?
I have the XT-1925-6 Tmobile US unlocked bootloader. I had root with PPS29-118-11-1. Now that I have updated to -2 I have lost root and get a bootloop everytime I try and flash Magisk or DM-verity. Could you help? Thanks.
fireman644 said:
I have the XT-1925-6 Tmobile US unlocked bootloader. I had root with PPS29-118-11-1. Now that I have updated to -2 I have lost root and get a bootloop everytime I try and flash Magisk or DM-verity. Could you help? Thanks.
Click to expand...
Click to collapse
Maybe you should try try "retail" firmware. If you havr the xt-1925-6 variant, it will work. US unlocked will accept it. The version is ALI_RETAIL_9.0_PPS29.55-37-7_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
It worked for many of us. You can use RSDLite, as long as you are connected by a USB 2 port. Do a backup first, because your internal storage will be deleted.
If you truly have an xt-1925-6, it will work
Yeah I tried flashing the firmware but it wouldn't take. Gave me errors at the beginning and wouldn't flash. I'll try again with a USB 2 port and RSDlite. I was using manual commands.
theseeker2654 said:
The big question is which variant of the Moto G6 do you have? For example I have XT1925-6 which is the US Unlocked variant. You need to flash the correct firmware for your variant.
Go here once you know your variant to get the exact right firmware. Who is your provider?
Click to expand...
Click to collapse
I'm connecting to T-Mobile, but I can't remember if the phone is used or a New in Box from Amazon at some point. It is a GSM version.
Here's a pair of questions that might help us noobs:
1. How do you tell which version of the moto g6 phone you have? (if there's a link to another discussion that gives this info, awesome.)
2. Is there a map of the hardware types to appropriate retail images? When I looked in the RETAIL directory for the link above, there appears to be two versions for 9.0 - 29.55 and 29.118 - with my phone functioning in the .118 stream through trial and error.
Thanks!
-og
OK I have used the ALI_RETAIL_9.0_PPS29.55-37-7_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and the device will boot stock. Wiped it and followed the usual steps to root it. Once I apply Magisk or dm_verity disabler there is a bootloop. Could anyone please provide the steps needed to root and prevent the bootloop. I have tried everything that I can think of. Using Magisk 20.2 and dm_verity 12/27/19. Should I try another version? Thank you.
fireman644 said:
OK I have used the ALI_RETAIL_9.0_PPS29.55-37-7_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and the device will boot stock. Wiped it and followed the usual steps to root it. Once I apply Magisk or dm_verity disabler there is a bootloop. Could anyone please provide the steps needed to root and prevent the bootloop. I have tried everything that I can think of. Using Magisk 20.2 and dm_verity 12/27/19. Should I try another version? Thank you.
Click to expand...
Click to collapse
According to posts in this thread, one says don't use dm_verity zip and another says edit fstab.qcom. I haven't tired either yet as I'm still on Aug patch with updates "disabled".
Here is how I eventually rooted PPSS29.118-15-11-2:
https://forum.xda-developers.com/showpost.php?p=81229155&postcount=381
I was never able to boot after trying to flash TWRP, so I just didn't bother flashing TWRP. Booting it manually was enough.
I only flashed Magisk-19.4 from TWRP, nothing else. I have no idea if directly flashing a newer Magisk might have worked.
I'm now updated to Magisk-20.3 and everything works.
fireman644 said:
OK I have used the ALI_RETAIL_9.0_PPS29.55-37-7_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and the device will boot stock. Wiped it and followed the usual steps to root it. Once I apply Magisk or dm_verity disabler there is a bootloop. Could anyone please provide the steps needed to root and prevent the bootloop. I have tried everything that I can think of. Using Magisk 20.2 and dm_verity 12/27/19. Should I try another version? Thank you.
Click to expand...
Click to collapse
For the installation of Magisk I used the .zip v19.3 because the latest (v20.3) caused a bootloop.
Here are the steps that worked for me:
1.) Boot into TWRP and copy the fstab.qcom from /vendor/etc
2.) Edit fstab.qcom like this:
line 9: forceencrypt=/dev/block/bootdevice/by-name/metadata => encryptable=/dev/block/bootdevice/by-name/metadata
This will remove forceencryption and will only work if you format /data!! But you should do this anyway before flashing the magisk.zip
3.) Replace the fstab.qcom in/vendor/etc with the edited one. Be sure the permissions are 0644 (rw-r--r--). To change it open the terminal command and type
Code:
chmod 0644 /vendor/etc/fstab.qcom
4.) Flash the magisk.zip to install Magisk
During the installation process Magisk will remove dm-verity
5.) Reboot and update Magisk Manager + Magisk to v20.3
Hi, I have decided to gather boot images and magisk patched images to one thread for now. I will try to edit this thread to be up-to-date. You can let me know what could you want next or if anything is wrong etc.
Stock boot.img files (direct links):
EU NE2213_11_A.12
Stock boot.img - link
EU NE2213_11_A.10
Stock boot.img - link
Magisk patched boot.img are here a file that can be downloaded (I am using magisk canary usually, but in Magisk, you can change the channel from the canary to stable etc.) - names as the versions come.
Below this there are those magisk patched files which you just flash (or boot and then flash directly from the Magisk app) via fastboot
Reserved
Don't you need to patch vendor_boot.img as well like OnePlus 9 pro ?
HessNL said:
Don't you need to patch vendor_boot.img as well like OnePlus 9 pro ?
Click to expand...
Click to collapse
Apparently not. I have patched that stock boot via magisk, then via fastboot boot <patchedimage.img> booted (and also tested if it actually boots) and when it booted, via magisk app I did "Direct install (recommended)", rebooted and done.
Oh okay you had a temporary boot we that's good to know well it works that's the most important thing ain't it
Noob question I been on locked bootloader for years so haven't been in the root scene, but I have US model NE2215 I'm guessing I need to wait for the firmware to be available to get the boot img? Did I just got my phone too early? Already oem unlocked now just waiting for twrp and root info. I always wanted a OnePlus phone because the community is big, but doesn't seem like much people upgraded from 9 pro.
HessNL said:
Oh okay you had a temporary boot we that's good to know well it works that's the most important thing ain't it
Click to expand...
Click to collapse
Yes, because this is probably and currently the most secure option to root it as we haven't got twrp available yet.
BuBbLeFIZzY said:
Noob question I been on locked bootloader for years so haven't been in the root scene, but I have US model NE2215 I'm guessing I need to wait for the firmware to be available to get the boot img? Did I just got my phone too early? Already oem unlocked now just waiting for twrp and root info. I always wanted a OnePlus phone because the community is big, but doesn't seem like much people upgraded from 9 pro.
Click to expand...
Click to collapse
That's not that you have it early. The phone itself is early in spite of rooting and doing things like rooting, custom recoveries, ROMs etc. I currently can't find boot img for your model, but once I do, I will post it here for you with patched one.
Thank you kouzelnik3 for this thread !
I was going to dl original firmware and patch it myself but found your thread in time with all ready to flash
Rooted OP10 pro done, now i can't wait to see some TWRP and roms in the future
fozzy056 said:
Thank you kouzelnik3 for this thread !
I was going to dl original firmware and patch it myself but found your thread in time with all ready to flash
Rooted OP10 pro done, now i can't wait to see some TWRP and roms in the future
Click to expand...
Click to collapse
You're really welcome, I wanted to unite those currently quite hard rooting stuff!
And yes, I can't wait to see twrp too!
Is there a known stock boot.img of the NE2215_11_A.10? I assume I shouldn't use the 2213_11_A.10.
GeekMcLeod said:
Is there a known stock boot.img of the NE2215_11_A.10? I assume I shouldn't use the 2213_11_A.10.
Click to expand...
Click to collapse
Not yet unfortunately. Or I don't know about it yet. :/
kouzelnik3 said:
Not yet unfortunately. Or I don't know about it yet. :/
Click to expand...
Click to collapse
Yeah.. I googled a lot last night once I got my phone trying to find it to root it. I need me that extra bit of customization.
Is there a way I can get it from my phone?
what am i doing wrong here rooted for 7+ years and some reason can't get this working.
Just moved over from ColorOS to Oxygen - when i try to flash the boot.img (patched one) all i get is this
Johnstan725 said:
what am i doing wrong here rooted for 7+ years and some reason can't get this working.
Just moved over from ColorOS to Oxygen - when i try to flash the boot.img (patched one) all i get is this
Click to expand...
Click to collapse
Ignore me but for anyone else that tries looks like i had to reboot bootloader and flash the img via bootloader...
thought it's normally flashed via fastboot?! weird phone
Johnstan725 said:
Ignore me but for anyone else that tries looks like i had to reboot bootloader and flash the img via bootloader...
thought it's normally flashed via fastboot?! weird phone
Click to expand...
Click to collapse
You should wipe the phone and start all over or else you won't be able to take ota updates. Never flash the patched boot image since you bypass the magisk backup feature. You have to wait for the full update package to update if you flash the boot. Ppl have previously had update issues after flashing.
g96818 said:
You should wipe the phone and start all over or else you won't be able to take ota updates. Never flash the patched boot image since you bypass the magisk backup feature. You have to wait for the full update package to update if you flash the boot. Ppl have previously had update issues after flashing.
Click to expand...
Click to collapse
Wiped the phone already, what difference would it make if i remove root or flash stock boot then flash ota and reflash boot?
Johnstan725 said:
Wiped the phone already, what difference would it make if i remove root or flash stock boot then flash ota and reflash boot?
Click to expand...
Click to collapse
Not sure what else magisk does during the backup process, but doing what you’re describing didn’t work for users on 8T and they usually ended up soft bricking. Everyone who flashed it vice installing from magisk app had to wait for op to post the full rom or for someone to post a repacked fastboot rom to update.
You do what you need to do, I’m just giving you some experience and recommendations since you just wiped and flashed the boot.
g96818 said:
Not sure what else magisk does during the backup process, but doing what you’re describing didn’t work for users on 8T and they usually ended up soft bricking. Everyone who flashed it vice installing from magisk app had to wait for op to post the full rom or for someone to post a repacked fastboot rom to update.
You do what you need to do, I’m just giving you some experience and recommendations since you just wiped and flashed the boot.
Click to expand...
Click to collapse
Interesting.
I moved over from ColorOS to oxygen OS, wiped the device then just booted a patched boot img, and installed direct.
I assume I flash ota and go onto magisk and do inactive slot? Where does the issue lie what method should I have gone down?
Johnstan725 said:
Interesting.
I moved over from ColorOS to oxygen OS, wiped the device then just booted a patched boot img, and installed direct.
I assume I flash ota and go onto magisk and do inactive slot? Where does the issue lie what method should I have gone down?
Click to expand...
Click to collapse
Hmmm. Well you should be fine if you patched the boot and let magisk do the install. I only suggested wiping since you said you flashed the img from the bootloader.
You might run into the same problem I have with the 9RT. I too upgraded from color to oos and couldn’t update at all, even though I rooted from the magisk app. I had to wait for someone to make a fastboot rom. I had no problems updating color following my method, but not oos after switching. Hopefully that’s not the case for you.