[Metro][Stock] SOFIAP-T QPRS30.80.64.6.2 - Moto G Stylus (Moto G Pro) ROMs, Kernels, Recoveri

100% Stock ROM for the Metro by T-Mobile Moto G Stylus
Requirements:
ADB & Fastboot from here:
https://developer.android.com/studio/releases/platform-tools
ADB & Fastboot set into your OS environment
(This allows adb to be used in any folder)
Instructions here:
https://wiki.lineageos.org/adb_fastboot_guide.html#installing-adb-and-fastboot
7-Zip to extract the .7z file:
https://www.7-zip.org/
Download:
QPRS30.80.64.6.2
Older Downloads:
QPRS30.80.64.6
QPRS30.80.64.3
Flashing Instructions:
1. Extract the zip using 7-Zip
2. Boot into Fastboot
3. Run the flash-all.bat this should automatically start flashing all the partitions
This will wipe everything. If you want to keep your data, before running open the .bat file with a text editor and remove -w from
Code:
fastboot -w reboot
​
(If on another platform than Windows you'll need to change the .bat file to your OS)
Looking for the Retail variant Stock ROM?
See Here:
https://forum.xda-developers.com/mo...t/stock-rom-motorola-g-stylus-retail-t4104451

QPRS30.80.64.6
https://mega.nz/file/nQkRHByR#md9YeMeAS4Vp6_lhL3pm9Bbqx1JrCeMHW8Lbkzr1RQo

cbc0201 said:
QPRS30.80.64.6
https://mega.nz/file/nQkRHByR#md9YeMeAS4Vp6_lhL3pm9Bbqx1JrCeMHW8Lbkzr1RQo
Click to expand...
Click to collapse
Thanks for the download. I added to the OP with the flash-all.bat

DMedina559 said:
Thanks for the download. I added to the OP with the flash-all.bat
Click to expand...
Click to collapse
Okay so I have a question based on my observation maybe stupid may not be I don't care
Q: how do I identify if my phone is the RETUS or the SOFIAP-T?
Q: Sorry this is the observational question,the build number nomenclature in my phone does not have an s at the end of the QPR but in this forum it does but when you download the file it does not. Or does that not matter?
---------- Post added at 03:13 AM ---------- Previous post was at 03:09 AM ----------
LinuxAndroidAlwys said:
Okay so I have a question based on my observation maybe stupid may not be I don't care
Q: how do I identify if my phone is the RETUS or the SOFIAP-T?
Q: Sorry this is the observational question,the build number nomenclature in my phone does not have an s at the end of the QPR but in this forum it does but when you download the file it does not. Or does that not matter?
Click to expand...
Click to collapse
I have QPR30.80.64.6 model XT2043-4

LinuxAndroidAlwys said:
Okay so I have a question based on my observation maybe stupid may not be I don't care
Q: how do I identify if my phone is the RETUS or the SOFIAP-T?
Q: Sorry this is the observational question,the build number nomenclature in my phone does not have an s at the end of the QPR but in this forum it does but when you download the file it does not. Or does that not matter?
---------- Post added at 03:13 AM ---------- Previous post was at 03:09 AM ----------
I have QPR30.80.64.6 model XT2043-4
Click to expand...
Click to collapse
You should be able to tell in the about phone menu in the settings. And the S might be a typo I'm not sure I'll have to check

DMedina559 said:
You should be able to tell in the about phone menu in the settings. And the S might be a typo I'm not sure I'll have to check
Click to expand...
Click to collapse
I figured it out but I'm still confused about the s

LinuxAndroidAlwys said:
I figured it out but I'm still confused about the s
Click to expand...
Click to collapse
The s is just a typo on my end. I'll fix asap

Not sure If I'm in the rightr thread or not but need serious help !!! I had twrp on my phone was trying to reboot system and hit a slot phone went black and will not boot into fastboot turn on, nothing! It is as dead as a dorrnail ie hard bricked . I have loaded all the drivers for phone and qualcomm. Computer only recognizes phone as Qualcomm 9008 mode not bulk mode. Anyone know how to restore phone at least to be able to get into fadtboot? Anyone help would be very much appreciated this is my daily driver and I am screwed without it.

worked great

QPR30.80_64_6_2
https://mega.nz/file/2UMGDb7B#4OZmO_DMUXiJnSkuyf4Y1w3LHVxoXM-P7umpRUWqaAQ

LinuxAndroid4evr said:
Not sure If I'm in the rightr thread or not but need serious help !!! I had twrp on my phone was trying to reboot system and hit a slot phone went black and will not boot into fastboot turn on, nothing! It is as dead as a dorrnail ie hard bricked . I have loaded all the drivers for phone and qualcomm. Computer only recognizes phone as Qualcomm 9008 mode not bulk mode. Anyone know how to restore phone at least to be able to get into fadtboot? Anyone help would be very much appreciated this is my daily driver and I am screwed without it.
Click to expand...
Click to collapse
i did the same thing, booting into slot b got me into the device normally

cbc0201 said:
QPR30.80_64_6_2
https://mega.nz/file/2UMGDb7B#4OZmO_DMUXiJnSkuyf4Y1w3LHVxoXM-P7umpRUWqaAQ
Click to expand...
Click to collapse
Hey man this is my current version as well, but it doesnt have the flashall bat file, do you know if i could just use one from the links in the OP? i am new to flashing roms in this manner and i dont really know how it works

Updated OP with build QPRS30.80.64.6.2

CorporalCactus said:
Hey man this is my current version as well, but it doesnt have the flashall bat file, do you know if i could just use one from the links in the OP? i am new to flashing roms in this manner and i dont really know how it works
Click to expand...
Click to collapse
Yeah using the old flash-all.bat file works with newer builds, just put all the flahsing files in /Recovery-Files/ with the flash-all.bat outisde that folder

Is any way to completely delete Metro PCS bloatware? I have rooted phone. No success to delete bloatware. Can I replace Metro PCS ROM with retail ROM? Is that possible? Any ideas? Thank you

Hello please I used the Moto g stylus as well, using MetroPCS with QPRS30.80-64-6-2, I want to know if this rom is unlocked , will it remove the sim lock on my device as the remote unlock fails. Thanks

Hi new guy here. Got couple moto g stylus (2020 pro). Mine Ive tried out arrow, havoc cr stag, bliss and resurrection. My wife's exact same phone she decided to have me install resurrection remix and magisk root it. ADB installed until last step which was fastboot -w. Had error about not auto formatting RAW format. I managed to fix that but still boot looped or twrp 35. Sofia will load but can't install any rom from zip. Stag logo bootlooeded.. hard to even explain.. damn. Anyway
Any suggestions?

Where is the flash-all.bat ?

MotoLindvall said:
Hi new guy here. Got couple moto g stylus (2020 pro). Mine Ive tried out arrow, havoc cr stag, bliss and resurrection. My wife's exact same phone she decided to have me install resurrection remix and magisk root it. ADB installed until last step which was fastboot -w. Had error about not auto formatting RAW format. I managed to fix that but still boot looped or twrp 35. Sofia will load but can't install any rom from zip. Stag logo bootlooeded.. hard to even explain.. damn. Anyway
Any suggestions?
Click to expand...
Click to collapse
If you still need to figure out the crazy flashing procedure for our device...best answer is make sure you are on STOCK Android 10...if you have updated to Android 11 you will not be able to flash custom ROMs or have a fully functional TWRP recovery...and Magisk root is not good with A11..You can flash GSI on Android 11 Stock firmware or use the DSU loader to install the Beta of Android 12...and the GSI situation is 50/50 if it will boot or not....what I do is flash the A10 stock final upload from the lionnet archive using the ever so awesome Moto flash tool...the tool does everything...and fixed your Beta partition so you can flash custom ROMs...once you finish with the tool reboot into STOCK recovery and format data..reboot to Stock Android 10 once you get to the Android setup welcome screen reboot to boot loader and flash TWRP recovery to both recovery slots...reboot to recovery...and format data...then reboot to fastbootd...your first custom install is recommended to be flashed from fastbootd on both slots...now when you finish reboot to Stock 10 recovery and format data...boot the rom first before and mods installed...then once you boot the rom you can flash mods with TWRP..get in a habit of after new system install format data in stock 10 recovery...now any custom ROM flash at this point forward do from TWRP and before flashing format data in TWRP after format again in stock 10 recovery...gapps install after first boot...Magisk install only after you fully go through the flashing procedure and setup the Rom make sure to enable dev options or it won't boot..and again flash Magisk after full setup and reboot..this procedure works...I keep a copy of stock recovery and TWRP recovery on my sdcard and platform tools on pc...you can flash stock 10 and TWRP in mobile if your rooted with any root kernel mgr so that way you don't have to use pc...the moto flash tool is the best way to setup the phone for custom ROMs.....

Related

Honor 7X Oreo Stock Recovery

Hi, I manually updated my honor 7x (BND AL10 INDIAN) to EMUI 8 following the other post in this forum and after that I went on to flash TWRP recovery again from another post "complete_twrp_ramdisk.img" so that I could take full Nand backups and what not. But Here's the problem, When I try to flash the stock recovery back "BND_RECOVERY_NOcheck" which I flashed during upgrading to EMUI 8, it says "size of image is large than target device"
I tried this using boot fastboot command "fastboot flash recovery_ramdisk recovery.img" and also using the TWRP. It doesn't work either way. So I'm basically stuck with TWRP. The reason I want stock recovery is because
1. I can install OTA UPDATES on EMUI 8 (I actually got one)
2. I may want to just be on complete stock like locked bootloader, sock recovery etc...
Could any one help?? Maybe I need the right stock recovery file ?
BTW It's my first post ever so please go easy if I did any mistakes.
Could you share your twrp? Thanks!
Thetpcguy said:
Hi, I manually updated my honor 7x (BND AL10 INDIAN) to EMUI 8 following the other post in this forum and after that I went on to flash TWRP recovery again from another post "complete_twrp_ramdisk.img" so that I could take full Nand backups and what not. But Here's the problem, When I try to flash the stock recovery back "BND_RECOVERY_NOcheck" which I flashed during upgrading to EMUI 8, it says "size of image is large than target device"
I tried this using boot fastboot command "fastboot flash recovery_ramdisk recovery.img" and also using the TWRP. It doesn't work either way. So I'm basically stuck with TWRP. The reason I want stock recovery is because
1. I can install OTA UPDATES on EMUI 8 (I actually got one)
2. I may want to just be on complete stock like locked bootloader, sock recovery etc...
Could any one help?? Maybe I need the right stock recovery file ?
BTW It's my first post ever so please go easy if I did any mistakes.
Click to expand...
Click to collapse
"BND_RECOVERY_NOcheck" is nouget stock recovery.
Oreo update replaces all the partitions, including the recovery that you flashed in order to install the update.
The stock recovery can be extracted from "update.app" , the one inside the oreo "updateL22.zip"
holds said:
Could you share your twrp? Thanks!
Click to expand...
Click to collapse
It's here https://forum.xda-developers.com/honor-7x/development/oreo-twrp-complete-backup-t3764500
mrmazak said:
"BND_RECOVERY_NOcheck" is nouget stock recovery.
Oreo update replaces all the partitions, including the recovery that you flashed in order to install the update.
The stock recovery can be extracted from "update.app" , the one inside the oreo "updateL22.zip"
Click to expand...
Click to collapse
Hi, I'm downloading that UPDATEL22.ZIP right now and Can I extract this with any unzip/unrar program? What will be the name of that recovery? is it going to be "recovery"? The thing is I've never extracted anything from a ROM so I have not idea.
Thetpcguy said:
Hi, I'm downloading that UPDATEL22.ZIP right now and Can I extract this with any unzip/unrar program? What will be the name of that recovery? is it going to be "recovery"? The thing is I've never extracted anything from a ROM so I have not idea.
Click to expand...
Click to collapse
you should already have the update.zip.
use same one you "manualy" installed.
winrar did not work for me but 7-zip did.
there is also rom extractor built into "multi-tool" and stand alone extractor around here some where.
I found it here
the name is just like the twrp you flashed and just like the partition that you flashed. (recovery_ramdisk.img)
Thetpcguy said:
Hi, I'm downloading that UPDATEL22.ZIP right now and Can I extract this with any unzip/unrar program? What will be the name of that recovery? is it going to be "recovery"? The thing is I've never extracted anything from a ROM so I have not idea.
Click to expand...
Click to collapse
Hi, so I figured Huawei update extractor app is the way to do it but I have a Mac and there doesn't seem to be a Mac version? is there a way to do it on android or Mac?
mrmazak said:
you should already have the update.zip.
use same one you "manualy" installed.
winrar did not work for me but 7-zip did.
there is also rom extractor built into "multi-tool" and stand alone extractor around here some where.
I found it here
the name is just like the twrp you flashed and just like the partition that you flashed. (recovery_ramdisk.img)
Click to expand...
Click to collapse
Hi, Thanks for all your replies. After doing a bit of search, I managed to get it extracted on my android using zarchiver app and I copied the recovery_ramdisk.img from that BNDL22.ZIP and when I tried flashing it using the fastboot command "fastboot flash recovery_ramdisk recovery.img" It went ok and It got installed but when I tried to boot into recovery, I got this screen "ERROR MODE" ATTENTION ETC.. I don't know where I'm going wrong?
Thetpcguy said:
Hi, Thanks for all your replies. After doing a bit of search, I managed to get it extracted on my android using zarchiver app and I copied the recovery_ramdisk.img from that BNDL22.ZIP and when I tried flashing it using the fastboot command "fastboot flash recovery_ramdisk recovery.img" It went ok and It got installed but when I tried to boot into recovery, I got this screen "ERROR MODE" ATTENTION ETC.. I don't know where I'm going wrong?
Click to expand...
Click to collapse
I dont know.
The new way to boot to recovery was written in other thread as "hold both volume buttons & power button"
not sure if it was a problem with extraction or not, but attached is the recovery I extracted. do not have it installed. I dont even have oreo installed., I'm still pulling files together and reading the update-scripts and trying to convince myself if it is worth trying it.
https://www.androidfilehost.com/?w=files&flid=262391
I have now jumped on board and did oreo conversion on L24, then flashed RR. I went and installed the oreo recovery, then back to this stock recovery. It worked fine for me.
mrmazak said:
I dont know.
The new way to boot to recovery was written in other thread as "hold both volume buttons & power button"
not sure if it was a problem with extraction or not, but attached is the recovery I extracted. do not have it installed. I dont even have oreo installed., I'm still pulling files together and reading the update-scripts and trying to convince myself if it is worth trying it.
https://www.androidfilehost.com/?w=files&flid=262391
I have now jumped on board and did oreo conversion on L24, then flashed RR. I went and installed the oreo recovery, then back to this stock recovery. It worked fine for me.
Click to expand...
Click to collapse
Hi Dude, Great man. Your recovery worked like charm. But I did extract it properly from BNDL22.ZIP and I still don't know why it failed but thanks a ton. I hope this helps out other people reading
Thetpcguy said:
Hi Dude, Great man. Your recovery worked like charm. But I did extract it properly from BNDL22.ZIP and I still don't know why it failed but thanks a ton. I hope this helps out other people reading
Click to expand...
Click to collapse
i am wipeiing my data it always show faild plss help my device is dead
Thetpcguy said:
Hi Dude, Great man. Your recovery worked like charm. But I did extract it properly from BNDL22.ZIP and I still don't know why it failed but thanks a ton. I hope this helps out other people reading
Click to expand...
Click to collapse
Which perticular file should i flash for stock recovery please. There are 4-5 files. Pl help. I am on RR and want to flash system.img to go back to oreo beta. But i think i do not have stock recovery as i had tried to flash twrp. Pl help
Thetpcguy said:
Hi Dude, Great man. Your recovery worked like charm. But I did extract it properly from BNDL22.ZIP and I still don't know why it failed but thanks a ton. I hope this helps out other people reading
Click to expand...
Click to collapse
Hey bro thefe are too many files there will it flash through fastboot or twrp and how to flash one by one pls help me
Hello all,
thanks for all the info in this thread.
I bricked my Honox 7x (BND-LC21) by trying to go Oreo.
The installation went halfway through, but now I can't complete (missing info howto flash bootloader / kernel) and I also can't go back as the partition layout has already changed to oreo style.
Steps done so far:
- unlocked boot loader
- installed twrp
- extract system image and recovery image from oreo update zip
getting the phone in fastboot mode i can successfully run
fastboot flash recovery_ramdisk recovery_ramdisk.img (i can also flash old recoveries this way, but none of them will successfully boot into recovery mode)
fastboot flash system system.img
either way, the system will not boot afterwards.
how do I manually flash bootloader / kernel on the oreo partition layout?
erecovery and hisuite won't recover my phone either...
Any hints appreciated
Aibiman
mrmazak said:
I dont know.
The new way to boot to recovery was written in other thread as "hold both volume buttons & power button"
not sure if it was a problem with extraction or not, but attached is the recovery I extracted. do not have it installed. I dont even have oreo installed., I'm still pulling files together and reading the update-scripts and trying to convince myself if it is worth trying it.
https://www.androidfilehost.com/?w=files&flid=262391
I have now jumped on board and did oreo conversion on L24, then flashed RR. I went and installed the oreo recovery, then back to this stock recovery. It worked fine for me.
Click to expand...
Click to collapse
Can I flash just the stock recovery to my phone and if so is it the recover_ramdis.img, or do I need to flash them all. I'm on mostly stock bnd-l24. Unlocked bootloader TWRP and magisk for root. There's a new update and i wanted to flash stock recovery so I could update.
kingd421 said:
Can I flash just the stock recovery to my phone and if so is it the recover_ramdis.img, or do I need to flash them all. I'm on mostly stock bnd-l24. Unlocked bootloader TWRP and magisk for root. There's a new update and i wanted to flash stock recovery so I could update.
Click to expand...
Click to collapse
Yes that is the recovery.
But if you have root, update not going to work
mrmazak said:
Yes that is the recovery.
But if you have root, update not going to work
Click to expand...
Click to collapse
Will uninstalling magisk fix that or does the boot image have to be reflashed. Thank you for the quick response
kingd421 said:
Will uninstalling magisk fix that or does the boot image have to be reflashed. Thank you for the quick response
Click to expand...
Click to collapse
From magisk manager app should be a restore images option
mrmazak said:
From magisk manager app should be a restore images option
Click to expand...
Click to collapse
Sounds good. I appreciate it.
aibiman said:
Hello all,
thanks for all the info in this thread.
I bricked my Honox 7x (BND-LC21) by trying to go Oreo.
The installation went halfway through, but now I can't complete (missing info howto flash bootloader / kernel) and I also can't go back as the partition layout has already changed to oreo style.
Steps done so far:
- unlocked boot loader
- installed twrp
- extract system image and recovery image from oreo update zip
getting the phone in fastboot mode i can successfully run
fastboot flash recovery_ramdisk recovery_ramdisk.img (i can also flash old recoveries this way, but none of them will successfully boot into recovery mode)
fastboot flash system system.img
either way, the system will not boot afterwards.
how do I manually flash bootloader / kernel on the oreo partition layout?
erecovery and hisuite won't recover my phone either...
Any hints appreciated
Aibiman
Click to expand...
Click to collapse
can you in to TWRP?

Unofficial TWRP based on v4.88B - WiFi working, Magisk Rootable

*IT IS FOR UNLOCKED BOOTLOADERS ONLY*
Voila ..
Alas TWRP is working on Nokia 8 NB1 based on v4.88B kernel. Wifi and Magisk root both are working on my mobile. Please and report if it is working for you as well.
Download:
https://mega.nz/#!nRgVWKqB!fWx4zO1f19Shs_I8Thkw4ycsZMMMmSYP24cK0MHIBlM
Flash:
adb reboot bootloader
fastboot flash boot_a TWRP_NB1_boot_v2.img
fastboot reboot
Click to expand...
Click to collapse
If working well, also flash boot_a partition as well.
Then following below thread to root it using MagiskManager
https://forum.xda-developers.com/nokia-8/development/pre-rooted-boot-image-nokia-nb1-v4-88b-t3798063
Check Following Post for Update:
https://forum.xda-developers.com/showpost.php?p=77307135&postcount=74
WARNING: Don't change boot slot using TWRP . I am not responsible if you brick your phone.
Many thanks!
Does this mean if you have this IMG, you can flash after any other (even older) IMGs without verify check?
With fastboot and OST LA from here?
That would be a fantastic news!!! :good:
Overall, the fastboot doesn't seem to work on my device. Once I get my phone into bootloader state it says naturally DOWNLOAD MODE but any fastboot devices command ends up with <Waiting for devices>. I've switched drivers from Nokia's one to diffrent non device specific but nothing helps. Any idea on how to fix it ?
- edit -
Came out that the adb and fastboot drivers can't be outdated so be sure to use newest from SDK Platform Tools - otherwise u won't see the device.
head66 said:
Many thanks!
Does this mean if you have this IMG, you can flash after any other (even older) IMGs without verify check?
With fastboot and OST LA from here?
That would be a fantastic news!!! :good:
Click to expand...
Click to collapse
Didn't checked by flashing it. But, logically yes. Though system partition is still encrypted. That may cause an issue. But for custom ROM developers - it can be a start. Provided - your bootloader is unlocked.
KonikoO said:
Overall, the fastboot doesn't seem to work on my device. Once I get my phone into bootloader state it says naturally DOWNLOAD MODE but any fastboot devices command ends up with <Waiting for devices>. I've switched drivers from Nokia's one to diffrent non device specific but nothing helps. Any idea on how to fix it ?
- edit -
Came out that the adb and fastboot drivers can't be outdated so be sure to use newest from SDK Platform Tools - otherwise u won't see the device.
Click to expand...
Click to collapse
Hey,
maybe that can help u.
Fastboot need Admin permissions on windows open a CMD as Admininstator.
On Linux just login into user root.
WORKING
Image is working! Thanks a lot!
Magisk is also working after patch. (With WiFi)
KonikoO said:
Overall, the fastboot doesn't seem to work on my device. Once I get my phone into bootloader state it says naturally DOWNLOAD MODE but any fastboot devices command ends up with <Waiting for devices>. I've switched drivers from Nokia's one to diffrent non device specific but nothing helps. Any idea on how to fix it ?
- edit -
Came out that the adb and fastboot drivers can't be outdated so be sure to use newest from SDK Platform Tools - otherwise u won't see the device.
Click to expand...
Click to collapse
Did you checked if USB debugging is on in the developer settings?
Powered by View 10
KonikoO said:
Overall, the fastboot doesn't seem to work on my device. Once I get my phone into bootloader state it says naturally DOWNLOAD MODE but any fastboot devices command ends up with <Waiting for devices>. I've switched drivers from Nokia's one to diffrent non device specific but nothing helps. Any idea on how to fix it ?
- edit -
Came out that the adb and fastboot drivers can't be outdated so be sure to use newest from SDK Platform Tools - otherwise u won't see the device.
Click to expand...
Click to collapse
I have it problem on Windows 10 too. If you want very strong, download any Linux-based LiveCD, flash it on USB and load. After this install adb and fastboot from LineageOS site (delete space after "https://" https:// wiki.lineageos.org/devices/bacon/build) and run commands.
P.S.: I am sorry for my bad English, but I hope help you
Wow, you are a genius! So glad to see twrp on our Nokia 8 xD but with encrypted /system. Does it mean nandroid backup is not possible at the moment? Also, with your magisk patched kernel, can i flash over or do i need to first flash twrp then reroot with your method?
corpsegrinder62 said:
Wow, you are a genius! So glad to see twrp on our Nokia 8 xD but with encrypted /system. Does it mean nandroid backup is not possible at the moment? Also, with your magisk patched kernel, can i flash over or do i need to first flash twrp then reroot with your method?
Click to expand...
Click to collapse
Flash TWRP img, then re-root using Magisk method provided in the URL.
Created another version of TWRP. Now /data is browsable, but showing garbled file names So, nanodroid is still unachievable. Don't have a backup phone, so could not take the risk of loosing my data, else could have un-encrypt ICE filesystem encryption and could have build a stock based ROM without encrypted partition.
bidhata said:
Flash TWRP img, then re-root using Magisk method provided in the URL.
Created another version of TWRP. Now /data is browsable, but showing garbled file names So, nanodroid is still unachievable. Don't have a backup phone, so could not take the risk of loosing my data, else could have un-encrypt ICE filesystem encryption and could have build a stock based ROM without encrypted partition.
Click to expand...
Click to collapse
Thanks bro. You are making tremindous progress on this phone though. Hopefully you inspire other devs to jump the train on our N8
Does this work with a locked bootloader? And if so do I just follow the steps here? Or do I need OST LA?
thank you so much for your time and effort. Much appreciated. Can the stock recovery be backed up and restored Later? Is it advised to flash it on TA 1012 Nokia 8 unlocked? How can we revert to the original state? Does OEM Unlock help in this case? Is it an image of the whole OS like previous mod attempts?
iKillua said:
Does this work with a locked bootloader? And if so do I just follow the steps here? Or do I need OST LA?
Click to expand...
Click to collapse
You need an unlocked bootloader. Else fastboot not let you overwrite /boot partition. No OST LA required.
trandafirmd said:
thank you so much for your time and effort. Much appreciated. Can the stock recovery be backed up and restored Later? Is it advised to flash it on TA 1012 Nokia 8 unlocked? How can we revert to the original state? Does OEM Unlock help in this case? Is it an image of the whole OS like previous mod attempts?
Click to expand...
Click to collapse
There is no different partition for recovery. So, just flashing the original boot partition ( boot.img ) will be enough to restore. OEM unlocked is required to decrypt the /data partition. This one is just the boot.img modification.
bidhata said:
There is no different partition for recovery. So, just flashing the original boot partition ( boot.img ) will be enough to restore. OEM unlocked is required to decrypt the /data partition. This one is just the boot.img modification.
Click to expand...
Click to collapse
Is this img suitable for restore https://mega.nz/#!yYwUWKwC!5wb2EkDhFKE2QIhI5tW0SE_uqkn2UL2uEPkTM01G5Mg?0 I can't see any 1012 img's How can I backup the boot.img from my phone?
Thank you.
trandafirmd said:
Is this img suitable for restore https://mega.nz/#!yYwUWKwC!5wb2EkDhFKE2QIhI5tW0SE_uqkn2UL2uEPkTM01G5Mg?0 I can't see any 1012 img's How can I backup the boot.img from my phone?
Thank you.
Click to expand...
Click to collapse
It is the same image for TA 1004 / TA-1012 . Taken from v4.88B update.
I realized that after the download finished. I apologize for jumping the gun. Since I'll have to unlock my bootloader, is there a way to do a full system backup through adb or otherwise? Most likely, I have a locked bootloader and before I can figure out a way to unlock it, I will have to backup as much data as possible since unlocking it will most likely wipe all my data and do a factory reset.
You can not make a backup unfortunately.
could you and other people making useless threads put it in the thread title and OP so that 99.9% of nokia 8 owners that dont have a way of unlocking the bootloader dont waste our time by having the salt rubbed in, thanks

Haven't flashed in over 2 years. Missing anything?

I went to the dark side in April 2016, and haven't flashed anything in about 2 years. Wife's tablet (flo) needs an update, MM is getting laggy though the tablet has always been good to us.
Titanium was getting to be crap around the last time I used it, with problems mostly restoring, does that still hold true? Might just use it to back up a couple apps she uses a lot and just use Play Store to restore the rest. It's not really important, just curious.
Downloading the TWRP app, I know TWRP is installed but willing to bet it needs to be updated and the app can do that.
Tablet is near its EOL, not planning on rooting it if the ROM doesn't come pre-rooted. I have no idea what Magisk is.
So I'm gonna go into TWRP, wipe system, wipe data, wipe cache, wipe dalvik. Flash ROM (going with Lineage 15.1). Now at one point 2-3 years ago the common wisdom was starting to become "flash ROM, boot ROM, reboot to recovery and then flash Gapps." Y'all still doing that? Or can I just flash Gapps right after flashing ROM and reboot then?
Bit nervous as I haven't flashed in a while, but also kind of exciting.
We've got Android 8.1 Oreo now... Working perfectly on our Nexus 7... You should check it out...
Any suggestions for which are the most stable roms to try? I'm in the same boat. I'm on android 6.0.1, stopped flashing things a while ago and it might even be official! But mine's running like a dog so think I wanna try something to jazz it up!
You should try pure Nexus rom based on 7.1.2 for ultimate good battery life. Oreo is Good but battery isn't the greatest.
Well i have been rooting for a bit.
My N7 2013 Flo is not rooted. It is unlocked.
I thought i have via adb fastboot put latest twrp on it...but i turn it off (go into bootloader) toggle into recovery...tarp is not there (triangle with red 'i').....
I dont want to go ballistic but I never would have thought I am having such a hard time putting recovery image onto it.
It is stock 6.1
CF root doesn't exist anymore...some say use majisk....that's not working....
Without a recovery tool....(twrp) nothing can be flashed..
AM I MISSING SOMETHING
ganggreen777 said:
Well i have been rooting for a bit.
My N7 2013 Flo is not rooted. It is unlocked.
I thought i have via adb fastboot put latest twrp on it...but i turn it off (go into bootloader) toggle into recovery...tarp is not there (triangle with red 'i').....
I dont want to go ballistic but I never would have thought I am having such a hard time putting recovery image onto it.
It is stock 6.1
CF root doesn't exist anymore...some say use majisk....that's not working....
Without a recovery tool....(twrp) nothing can be flashed..
AM I MISSING SOMETHING
Click to expand...
Click to collapse
Firstly, your stock 6.1 is ancient and obsolete. Here are detailed instructions to install a modern Android, TWRP and root....
https://wiki.lineageos.org/devices/flo/install
ROM - https://download.lineageos.org/flo
native root solution, no need for CF, Magisk, etc. - https://download.lineageos.org/extras (install addonsu-14.1-arm-signed.zip and activate it in the developer options)
:good:
k23m said:
Firstly, your stock 6.1 is ancient and obsolete. Here are detailed instructions to install a modern Android, TWRP and root....
https://wiki.lineageos.org/devices/flo/install
ROM - https://download.lineageos.org/flo
native root solution, no need for CF, Magisk, etc. - https://download.lineageos.org/extras (install addonsu-14.1-arm-signed.zip and activate it in the developer options)
:good:
Click to expand...
Click to collapse
Thanks so much for responding back!!!!
Tonight I will follow the steps. I trust it will go fine.
Excited to do this. ......yep I waited this long to root this device
k23m said:
Firstly, your stock 6.1 is ancient and obsolete. Here are detailed instructions to install a modern Android, TWRP and root....
https://wiki.lineageos.org/devices/flo/install
ROM - https://download.lineageos.org/flo
native root solution, no need for CF, Magisk, etc. - https://download.lineageos.org/extras (install addonsu-14.1-arm-signed.zip and activate it in the developer options)
:good:
Click to expand...
Click to collapse
I did the 'install lineageOS on flo and installed TWRP latest. Seem like fastboot went into a slew of commands
and finished. I followed the steps to reboot into recovery and twrp is not there. Android dude opened with red triangle.
I have no clue whats up. I leave it sit, and it reboots into android splash screen and bootsup so i can use the tablet. I guess this is why I am soo perplexed. "Am i missing something?"
ganggreen777 said:
....twrp is not there. Android dude opened with red triangle.
...."Am i missing something?"
Click to expand...
Click to collapse
I think you have missed this step.... "Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install." - https://twrp.me/asus/asusnexus72013wifi.html
k23m said:
I think you have missed this step.... "Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install." - https://twrp.me/asus/asusnexus72013wifi.html
Click to expand...
Click to collapse
Thank you for 'helping me'......I have googled this combo everywhere and tried it all. Nothing is allowing the tablet to populate into twrp.....
Perhaps its really not fastbooting twrp into the device
Kevin_McLaughlin said:
Thank you for 'helping me'......I have googled this combo everywhere and tried it all. Nothing is allowing the tablet to populate into twrp.....
Perhaps its really not fastbooting twrp into the device
Click to expand...
Click to collapse
Wait, is Kevin_McLaughlin=ganggreen777 ?
Anyway, here is an alternative way:
- fastboot flash recovery twrp-3.2.3-0-flo.img (please copy the output and post it here)
- fastboot reboot-bootloader
- select recovery in the bootloader
That's it, but you must do it in this order or else TWRP will be gone again.
k23m said:
Wait, is Kevin_McLaughlin=ganggreen777 ?
Anyway, here is an alternative way:
- fastboot flash recovery twrp-3.2.3-0-flo.img (please copy the output and post it here)
- fastboot reboot-bootloader
- select recovery in the bootloader
That's it, but you must do it in this ordecr or else TWRP will be gone again.
Click to expand...
Click to collapse
Why u asking???? Have we chatted b4?¿?
I will do as stated above (I swear I am (thinking) I am doing it as above all the other times. (when you say copy output...is that from the fastboot dialogue? ) ...is it as easy as copy paste ...I dont remember how to copy via adb fastboot...
(Makes me wonder if twrp is really being fastbooted into the n7 2013
Thanks for helping.
k23m said:
Wait, is Kevin_McLaughlin=ganggreen777 ?
Anyway, here is an alternative way:
- fastboot flash recovery twrp-3.2.3-0-flo.img (please copy the output and post it here)
- fastboot reboot-bootloader
- select recovery in the bootloader
That's it, but you must do it in this order or else TWRP will be gone again.
Click to expand...
Click to collapse
So I did the steps and it appeared. THANKS!!!
I downloaded the latest nightly of the link you told me to go to. I tried to flash it......it didnt flash.
ganggreen777 said:
So I did the steps and it appeared. THANKS!!!
I downloaded the latest nightly of the link you told me to go to. I tried to flash it......it didnt flash.
Click to expand...
Click to collapse
Did you try a factory reset immediately prior to installing it?
Sent from my Asus P027 using XDA Labs
ganggreen777 said:
So I did the steps and it appeared. THANKS!!!
I downloaded the latest nightly of the link you told me to go to. I tried to flash it......it didnt flash.
Click to expand...
Click to collapse
You need to do the following in TWRP:
(Optional, but recommended): Select the Backup button to create a backup.
Select Wipe and then Advanced Wipe.
Select Cache, System and Data partitions to be wiped and then Swipe to Wipe.
Go back to return to main menu, then select Install.
Navigate to /sdcard , and select the LineageOS .zip package.
next install the addonsu-14.1-arm-signed.zip (root addon)
and finally GApps (Google Apps) from https://opengapps.org/ - select ARM 7.1 pico
"Note: If you want any Google Apps on your device, you must follow this step before the first boot into Android!"
:highfive:
beachfl said:
Did you try a factory reset immediately prior to installing it?
Sent from my Asus P027 using XDA Labs
Click to expand...
Click to collapse
Lol
Hell no....totally forgot.
I will do the next thing you posted....and check back.
THANKS
ganggreen777 said:
Lol
Hell no....totally forgot.
I will do the next thing you posted....and check back.
THANKS
Click to expand...
Click to collapse
BTW
I am great to go.....thanks very much for helping me thru
---------- Post added at 01:06 AM ---------- Previous post was at 01:04 AM ----------
k23m said:
You need to do the following in TWRP:
(Optional, but recommended): Select the Backup button to create a backup.
Select Wipe and then Advanced Wipe.
Select Cache, System and Data partitions to be wiped and then Swipe to Wipe.
Go back to return to main menu, then select Install.
Navigate to /sdcard , and select the LineageOS .zip package.
next install the addonsu-14.1-arm-signed.zip (root addon)
and finally GApps (Google Apps) from https://opengapps.org/ - select ARM 7.1 pico
"Note: If you want any Google Apps on your device, you must follow this step before the first boot into Android!"
:highfive:
Click to expand...
Click to collapse
BTW I am great to go... Thanks for sticking thru with me

Guide to root motorola g stylus

QUICK STEPS TO ROOT MOTOROLA MOTO G STYLUS USING MAGISK
Just Remember*I just want to warn you that, Rooting will void the warranty of your smartphone
Rooting will block the OTA updates
1.First of all, please download and extract the ROM on your computer.
https://r.tapatalk.com/shareLink/to...1&share_fid=3793&share_type=t&link_source=app
2:*Now, connect your moto g stylus with a micro USB cable, and copy only the boot.img file from the extracted folder to your Motorola moto g stylus device storage/memory.
3:*Now you need to Launch Magisk Manager.
4:*After that, you will see a popup window that will ask you to install Magisk.
5:*Finally please select INSTALL and choose to install it again.
6:*Now Please press on “Patch Boot Image File
7:*Navigate to internal storage and select your phone’s boot image that you transferred earlier.
8:*Wait for a couple of seconds. Magisk will start patching the boot image.
9:*Once the boot image has been patched, copy the “patched_boot.img” from the internal storage and replace it in the same extracted ROM folder on your PC.
10:*Now you can follow the second step to flash the patched boot image file.
Next, you need to enter the following commands step by step:
First of all, you need to Flash the “patched_boot.img” to install Magisk and root your Motorola moto g stylus: fastboot flash boot patched_boot.img
You can also use the devices with A/B partition system, with the following commands:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
After that, you need to replace [patched_boot.img] with the same boot image file that you have already downloaded with the .img.
Now you will see the flashing process have has started. Now, run fastboot and reboot
HOW TO VERIFY IF YOUR MOTOROLA MOTO G STYLUS HAS A SYSTEMLESS ROOT?
Download and install the Magisk Manager app APK, and launch it.
If you want to verify that you have a systemless root, check the top of the screen and if you see all options with Green Tick which means you have successfully rooted and bypassed SafetyNet.
Sent from my moto g stylus using Tapatalk
surprised to see no comments on this topic. I am thinking of getting this phone but only if there is a root method for it.
It definitely works for the metro by TMobile version.
himesh82 said:
surprised to see no comments on this topic. I am thinking of getting this phone but only if there is a root method for it.
Click to expand...
Click to collapse
I got root by using magisk to patch the boot image. I purchased the phone directly from Motorola's website. If you get a version where the bootloader can be unlocked (some carrier versions apparently cannot be unlocked) you can root without much trouble.
dafunk60 said:
I got root by using magisk to patch the boot image. I purchased the phone directly from Motorola's website. If you get a version where the bootloader can be unlocked (some carrier versions apparently cannot be unlocked) you can root without much trouble.
Click to expand...
Click to collapse
I am based in Uk and will order from their website.
How easy it is to use as It has been afew years i tried rooting and will need a super easy guide.
himesh82 said:
I am based in Uk and will order from their website.
How easy it is to use as It has been afew years i tried rooting and will need a super easy guide.
Click to expand...
Click to collapse
I found it to be super easy using magisk, provided you have a PC to flash the patched boot.img to the phone via fastboot. I use the Lenovo Rescue & Smart Assist software on the PC to download the ROM from Motorola. You need to ensure the ROM you're downloading is the same version running on your phone. Using a boot.img from a different version will cause issues.
1. Copy the boot.img to the phone.
2. On the phone, patch the boot.img you just copied over with Magisk Manager.
3. Copy the patched magisk_patched.img back to your PC.
4. Connect to the phone via adb. (There's an adb.exe in the Lenovo Rescue & Smart Assist install directory "C:\Program Files (x86)\Rescue and Smart Assistant".)
5 . Reboot the phone to the bootloader with the following command on the PC:
Code:
adb reboot bootloader
6. Flash the patched boot image with the following command on the PC:
Code:
fastboot flash boot magisk_patched.img
7. Reboot the phone with the following command on the PC:
Code:
fastboot reboot
Once rebooted you can use Magisk Manager to hide root, check the SafetyNet status, etc.
Thank you for your help on this. I rooted my moto x4 long time ago and the process has definately changed.
Still confused regarding your points
1 - where can i find the boot.img
2 - how do you patch using magisk
Also do you not need to unlock boot loader and bypass the verification and why do you need to hide root after?
Thank you
dafunk60 said:
I found it to be super easy using magisk, provided you have a PC to flash the patched boot.img to the phone via fastboot. I use the Lenovo Rescue & Smart Assist software on the PC to download the ROM from Motorola. You need to ensure the ROM you're downloading is the same version running on your phone. Using a boot.img from a different version will cause issues.
1. Copy the boot.img to the phone.
2. On the phone, patch the boot.img you just copied over with Magisk Manager.
3. Copy the patched magisk_patched.img back to your PC.
4. Connect to the phone via adb. (There's an adb.exe in the Lenovo Rescue & Smart Assist install directory "C:\Program Files (x86)\Rescue and Smart Assistant".)
5 . Reboot the phone to the bootloader with the following command on the PC:
Code:
adb reboot bootloader
6. Flash the patched boot image with the following command on the PC:
Code:
fastboot flash boot magisk_patched.img
7. Reboot the phone with the following command on the PC:
Code:
fastboot reboot
Once rebooted you can use Magisk Manager to hide root, check the SafetyNet status, etc.
Click to expand...
Click to collapse
himesh82 said:
Thank you for your help on this. I rooted my moto x4 long time ago and the process has definately changed......
Thank you
Click to expand...
Click to collapse
You're welcome.
himesh82 said:
1 - where can i find the boot.img
Click to expand...
Click to collapse
In the Lenovo software you can choose a download location. The default appears to be "C:\ProgramData\LMSA\Download". In that directory you'll see a "RomFiles" folder which contains folders for the different ROM versions it has downloaded. SOFIAP_RETAIL_QPR30.80_58_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml or SOFIAP_RETAIL_QPRS30.80_58_3_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml for example. You can find the boot.img file within those folders.
The QPRD30.80_58_3 boot.img file is located in "C:\ProgramData\LMSA\Download\RomFiles\SOFIAP_RETAIL_QPRS30.80_58_3_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml"
Some people share links to the ROM files but I prefer to get mine from Motorola.
himesh82 said:
2 - how do you patch using magisk
Click to expand...
Click to collapse
Google's your friend on this topic, https://www.xda-developers.com/how-to-use-magisk/
himesh82 said:
Also do you not need to unlock boot loader and bypass the verification and why do you need to hide root after?
Click to expand...
Click to collapse
You do need to unlock the bootloader, unless you have the private key Motorola uses to sign images . Just follow the instructions on the Motorola website. Unlocking the bootloader & rooting are two separate things. You need to unlock the bootloader to allow the hardware to boot unsigned images, such as a patched boot image. Root provides applications root access to the Android OS.
You typically want to hide root as some apps won't function if they detect root, mostly banking & video streaming services I believe. It's not a requirement however.
Thank you again. I will take a good look at the guide and then decide if it is something that I can attempt
Can someone help me idk what I'm doing wrong but when doing the steps mentioned above boot b is flashed automatically and when my phone reboots I have no service, my screen doesn't work, it hangs for minutes at a time and randomly reboots. Please help
Wait DOES THIS WIPE ALL THE DATA?? I CANT get a clear answer. Supposedly the "official" unlocking through Motorola does but this is the Magisk method and I'm hoping it doesn't wipe the user data or apps.
Also how do you root AFTER you unlock the bootloader?
---------- Post added at 06:43 PM ---------- Previous post was at 06:37 PM ----------
JimmyJurner said:
It definitely works for the metro by TMobile version.
Click to expand...
Click to collapse
Does rooting wipe all the user data and apps?
nokia4life2017 said:
Wait DOES THIS WIPE ALL THE DATA?? I CANT get a clear answer. Supposedly the "official" unlocking through Motorola does but this is the Magisk method and I'm hoping it doesn't wipe the user data or apps.
Also how do you root AFTER you unlock the bootloader?
---------- Post added at 06:43 PM ---------- Previous post was at 06:37 PM ----------
Does rooting wipe all the user data and apps?
Click to expand...
Click to collapse
I honestly don't know. When I did the steps from op I unlocked the bootloader then rooted. I never booted into system. I can't check now because I'm running havoc os gsi and the op method doesn't work on gsis. I tried and it didn't boot but when I flashed the stock boot.img all my setup was still the same. Hope that helps some.
Growking99 said:
Can someone help me idk what I'm doing wrong but when doing the steps mentioned above boot b is flashed automatically and when my phone reboots I have no service, my screen doesn't work, it hangs for minutes at a time and randomly reboots. Please help
Click to expand...
Click to collapse
Do you have a carrier model? You might be flashing the wrong boot.img although I'm not sure if theres anything different between then
No I bought the unlocked model from best buy cuz I know carrier models usually aren't rootable. Can some one post a link to the right boot.img
Here is my build number QPRS30.80-58-3 and my device info is in the pic TIA for any help
nokia4life2017 said:
Wait DOES THIS WIPE ALL THE DATA?? I CANT get a clear answer. Supposedly the "official" unlocking through Motorola does but this is the Magisk method and I'm hoping it doesn't wipe the user data or apps.
Also how do you root AFTER you unlock the bootloader?
Does rooting wipe all the user data and apps?
Click to expand...
Click to collapse
There are instructions on rooting in these forums, even in this thread.
Unlocking the bootloader forces user data to be wiped (aka factory reset).
Rooting with Magisk does not wipe user data.
Unlocking the bootloader and rooting are two separate things. Unlocking the bootloader allows unsigned images, such as a modified boot.img, to be run on the device. Rooting provides applications root level access to the Android OS.
---------- Post added at 02:19 AM ---------- Previous post was at 02:10 AM ----------
Growking99 said:
Can someone help me idk what I'm doing wrong but when doing the steps mentioned above boot b is flashed automatically and when my phone reboots I have no service, my screen doesn't work, it hangs for minutes at a time and randomly reboots. Please help
Click to expand...
Click to collapse
It sounds like the boot image you're flashing does not match the version of the ROM on the phone. From your subsequent post, it looks like you're running QPRS30.80-58-3. Where did you get the boot.img file that you patched? You can use the Lenovo Rescue software to download the ROM files right from Motorola. These will contain the entire ROM, including the original boot image. Details are in the posts preceding yours. Flash the original boot.img & see if the phone boots. If it does, patch that image with Magisk & flash to obtain root.
Growking99 said:
Can someone help me idk what I'm doing wrong but when doing the steps mentioned above boot b is flashed automatically and when my phone reboots I have no service, my screen doesn't work, it hangs for minutes at a time and randomly reboots. Please help
Click to expand...
Click to collapse
Try fastboot flash boot boot.img. When i did the stot a and b method i lost touchscreen etc
I bought a second stylus and the root method is different. So I fastboot flash the image (not to slots) and it worked but when the screen goes off the touch screen isn't responding.
I got it to work by using the assistant mentioned above. And using the fastboot flash magisk_patched.img or fastboot flash boot magisk_patched.img I can't remember which one at the moment but it automatically flashed both A and B slots with no problems. Also is TWRP available for the G Stylus?
Growking99 said:
Can someone help me idk what I'm doing wrong but when doing the steps mentioned above boot b is flashed automatically and when my phone reboots I have no service, my screen doesn't work, it hangs for minutes at a time and randomly reboots. Please help
Click to expand...
Click to collapse
i just had the same thing happen to me. But i went to the assistant software and tried to rescue my device and it failed. Did you get it to work and how exactly did you get it working?
Edit: I just got it rescued and Im back up and running. Now I just need to figure out how not to repeat whatever mistake I just made and to get my device rooted. Did you ever figure out what you did wrong?
JimmyJurner said:
It definitely works for the metro by TMobile version.
Click to expand...
Click to collapse
Without unlocking the Bootloader?
*edit*
Cancel that, Just Unlocked my MetroPCS Moto G Stylus's Bootloader
*edit* *edit*
FYI : There is a new build for the RETAIL Channel from 7/21 : mirrors.lolinet.com/firmware/moto/sofiap/official/RETAIL/
Growking99 said:
Can someone help me idk what I'm doing wrong but when doing the steps mentioned above boot b is flashed automatically and when my phone reboots I have no service, my screen doesn't work, it hangs for minutes at a time and randomly reboots. Please help
Click to expand...
Click to collapse
I am having the same issue while in fastboot, the device reboots bootloader every 20-30 seconds. I had to wait till the screen went off before hitting enter to get OEM Get_unlock_code.

Question Copy partition after msm?

Hi guys,
So I can't for the life of me get a rom installed. Drivers are fine, fastboot commands always ends up booting into the recovery, but it won't read or flash the rom. I've tried crdroid, pixel, nameless. For the hell of it tried lineage over pixel recovery and that installed?!
I've been seeing the odd post/comment about how msm restore only pertains to one boot and you should update twice so both boots are covered? I also see a copy partion zip floating around but is this a12 or a13 or work on both?
For what it's worth I've been able to root it successfully. Any thoughts or advice would be appreciated.
Edit: I'm. Coming from a msm restore
Thanks
chinbags said:
Hi guys,
So I can't for the life of me get a rom installed. Drivers are fine, fastboot commands always ends up booting into the recovery, but it won't read or flash the rom. I've tried crdroid, pixel, nameless. For the hell of it tried lineage over pixel recovery and that installed?!
I've been seeing the odd post/comment about how msm restore only pertains to one boot and you should update twice so both boots are covered? I also see a copy partion zip floating around but is this a12 or a13 or work on both?
For what it's worth I've been able to root it successfully. Any thoughts or advice would be appreciated.
Edit: I'm. Coming from a msm restore
Thanks
Click to expand...
Click to collapse
when I restore my device I tipically run copy partition just after I unlock bootllader
then you know every flash should boot, even flashing twice (on A and B partition) it shod be always safer, since starting condition is the same
Psk.It said:
when I restore my device I tipically run copy partition just after I unlock bootllader
then you know every flash should boot, even flashing twice (on A and B partition) it shod be always safer, since starting condition is the same
Click to expand...
Click to collapse
Do you run it once or do you run copy partition after each update?
Had trouble at first too. But the copy partitions file is just so that the same firmware is on both slots. If you follow this post for nameless, you shouldn't have any problems. Should be noted that you should be on the latest (c.63-66) and be using the latest dtbo.img, vendor_boot.img, and boot.img files from the links posted in that thread)
[ROM][OOS CAM][OFFICIAL][OnePlus 9 Pro][13.0.0_r41]Nameless AOSP[2023/05/09]
Nameless AOSP for OnePlus 9 Pro [lemonadep] Nameless AOSP is based on Android Open Source Project, inspired by Google Pixel. We offer a smooth and stable experience for your device with a selected set of amazing features that provide an...
forum.xda-developers.com
chinbags said:
Do you run it once or do you run copy partition after each update?
Click to expand...
Click to collapse
just the first time unlocking

Categories

Resources