Database Users

[WIP/TBD][5.0.1][LRX22C][YT2-830F][SleepyBear 830F: Feedback Needed!]

**NOTICE: Due to unforeseen circumstances - my car's starter died, and I had to return my Yoga 2 for emergency cash - ROM development is on hiatus. Best Buy has put back a brand new Yoga 2 for me when payday comes again, provided I can eek it out.
I thought of a GoFundMe to help pick one up, but I didn't feel comfortable doing this.
Updates will come as available. Again, I am so sorry.
This ROM is for the **LENOVO YOGA TABLET 2-830F ONLY!**. You are responsible for your device and its warranty, health, happiness, sanity, love and abuse. The initial release will come over the next couple of weeks. I wanted to throw up this post to get your feedback and get a few folks to beta test. I have been using it as my daily driver for over a week, and all has been well
Android Lollipop source (provided via Lenovo's Open Source documentation):
http://support.lenovo.com/us/en/products/tablets/yoga-series/yoga-tablet-2-830/downloads/DS102874/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SleepyBear - A gently modified and streamlined Lollipop ROM for the YT-830F This ROM is based off of Lenovo's stock Lollipop ROM for the YT-830F (.LRX22C.YT2-830F_USR_S100067_1507101258_WW52_ROW)
Introduction
Last year, I spent a lot of time pouring over the Dell Venue 7840, one of the first "mainstream" Intel x86-based Android tablets to hit the market (Intel Z3580 - Mooresfield). There was nothing in the way of custom ROMs available, so I maintained a KitKat 4.4.4 ROM for the handful of XDA folks that were using it. Fast forward - I have been using the Yoga Tab 2-830F for about a month, and its story is quite familiar - Intel Z3745 Baytrail, 64-bit Android, also one of Intel's premier devices pushed to devs for its foray into the Android market.
I have been using Android-based devices since 2010, and it's been nothing but fun - handsets, smartphones, tablets, media centers, USB system-on-a-chip and a couple of those tiny set top boxes that go well with XBMC/Kodi. I can't much deal with vendor UI overlays, bloat and the like. Thanks for the work of so many XDA comrades, I have received so much. In return, I'm trying to give some back.
Features
This ROM is based on Lenovo's stock Lollipop 5.0.1 update for the YT-830F (LRX22C/.YT2-830F_USR_S100067_1507101258_WW52_ROW). The image can be flashed via ClockworkMod using the Tethered CWM method. For now, I would all but recommend that you already have the Lenovo Lollipop OTA already in place and are comfortable. The finer points of that process might be malleable later.
ROM Details:
SleepyBear v1 - TBD December 2015
* Android 5.0.1 (modified Lenovo Lollipop stock ROM)
* ROOTed via SuperSU 2.52
* Xposed Framework v78
* NTFS/CIFS filesystem support
* Debloated (Nova Launcher beta instead of Lenovo's UI. The uptick in responsiveness is almost absurd)
* Deodexed
* Zipaligned
* BusyBox
* Init.d
* SD card write fix
* Stock kernel optimized (Interactive governor, cfq scheduler, 512KB read-ahead - Best balance of multitasking, performance and battery life)
* AdAway
* YouTube AdAway (Xposed module)
* YouTube Background Playback (Xposed module)
* Android Terminal Emulator​
Installation
1. SleepyBear v1 COMING LATER THIS DECEMBER. LINK WILL BE HERE.
2. Copy the folder to the microSD device of your YT-830F - more than likely /clockworkmod/backup
3. Boot the device to ClockworkMod Recovery using the instructions for the Tethered CWM method.
4.

:good:
From my LG-G4, Rooted running Stock 5.1

Nice stuff. I'm on the Yoga 10 inch (1050F) so I can't really test this ROM, but hopefully this is the start of custom ROMs for the Yoga range.

Wohoo :victory:
Thanks for your work! Finally the waiting for a custom rom is over :highfive:
I will definitely test this rom in the next few days, but first of all: Am I blind or where is the link for downloading the files?
And my second question: will it be possible to make a clean install with a flashable zip? Since the bootloader can be unlocked with the method ionioni provides in his thread it should be possible, right?

1subw00fer1 said:
Wohoo :victory:
Thanks for your work! Finally the waiting for a custom rom is over :highfive:
I will definitely test this rom in the next few days, but first of all: Am I blind or where is the link for downloading the files?
And my second question: will it be possible to make a clean install with a flashable zip? Since the bootloader can be unlocked with the method ionioni provides in his thread it should be possible, right?
Click to expand...
Click to collapse
@1subw00fer1 - correct, there is not yet a download link. I'd like to get some Yoga Tab 2 8-inch owners (YT-810F only for now) to test this out.
Now that I've gotten some sleep, I'm going to put my device back on KitKat, firmware and all, and flash this ROM to make sure both firmware and OS load correctly. It *should*, given that I am using a full ClockworkMod backup that contains boot, recovery, data and a couple of low-level partitions. If that works, then you could do the clean flash via tethered CWM.
I am also using NAndroid Manager to build a full, flashable ZIP that I'll be testing with tethered CWM. I don't see any impediments to doing this. We shall see.
I'll try this with both locked and unlocked bootloader. Details will be added to the main post.
@workdowg - care to test it on the 1050? - we could tweak the partition layout if need be.
Does that answer your questions?

F1Fanatic27 said:
Nice stuff. I'm on the Yoga 10 inch (1050F) so I can't really test this ROM, but hopefully this is the start of custom ROMs for the Yoga range.
Click to expand...
Click to collapse
@F1Fanatic27 - do you have unlocked bootloader on your 1050F? Are you you versed on using the Tethered CWM and doing system image backups, etc.? If so, I'd like some folks to try with this model.

1subw00fer1 said:
Wohoo :victory:
Thanks for your work! Finally the waiting for a custom rom is over :highfive:
I will definitely test this rom in the next few days, but first of all: Am I blind or where is the link for downloading the files?
And my second question: will it be possible to make a clean install with a flashable zip? Since the bootloader can be unlocked with the method ionioni provides in his thread it should be possible, right?
Click to expand...
Click to collapse
I have updated the Installation section with mention of ETA for the first release.

jumpup said:
@F1Fanatic27 - do you have unlocked bootloader on your 1050F? Are you you versed on using the Tethered CWM and doing system image backups, etc.? If so, I'd like some folks to try with this model.
Click to expand...
Click to collapse
Oh yes definitely willing to try it out. I reflashed Lollipop a few days ago so my bootloader's not unlocked at the moment, but I know how to do it so I can get it done in a jiffy. As for CWM, I've been using TWRP for a while now, but a few minutes with CWM and I should be re-accustomed.

F1Fanatic27 said:
Oh yes definitely willing to try it out. I reflashed Lollipop a few days ago so my bootloader's not unlocked at the moment, but I know how to do it so I can get it done in a jiffy. As for CWM, I've been using TWRP for a while now, but a few minutes with CWM and I should be re-accustomed.
Click to expand...
Click to collapse
@F1Fanatic27 - EXCELLENT! Here are a couple of preliminary tasks that will verify CWM:
1. Make a full CWM backup of your device.
2. Reboot and make sure your Android instance is still functioning
3. Perform a full restore of the CWM backup from Step 1.
4. Reboot once more, and make sure Android is still good.
Let me know if that's good.

jumpup said:
@F1Fanatic27 - EXCELLENT! Here are a couple of preliminary tasks that will verify CWM:
1. Make a full CWM backup of your device.
2. Reboot and make sure your Android instance is still functioning
3. Perform a full restore of the CWM backup from Step 1.
4. Reboot once more, and make sure Android is still good.
Let me know if that's good.
Click to expand...
Click to collapse
Well, almost good. The backup was fine, but after the restore the tablet hung on boot and after about 30 seconds loaded recovery instead. :crying:

F1Fanatic27 said:
Well, almost good. The backup was fine, but after the restore the tablet hung on boot and after about 30 seconds loaded recovery instead. :crying:
Click to expand...
Click to collapse
Really? Download and flash the your model's LL OS Loader from the first post.
Damn!
@F1Fanatic27
Was your bootloader locked or unlocked when testing this?

jumpup said:
Really? Download and flash the your model's LL OS Loader from the first post.
Damn!
@F1Fanatic27
Was your bootloader locked or unlocked when testing this?
Click to expand...
Click to collapse
Unlocked.

F1Fanatic27 said:
Unlocked.
Click to expand...
Click to collapse
I would reflash the OS loader for your device. Let's see if that fixes the issue. If this does not fix it, follow that up by locking your bootloader.
In the interim, download your device's last Lenovo OTA update and the Intel Flash utility

jumpup said:
I would reflash the OS loader for your device. Let's see if that fixes the issue. If this does not fix it, follow that up by locking your bootloader.
In the interim, download your device's last Lenovo OTA update and the Intel Flash utility
Click to expand...
Click to collapse
Well reflashing the OS loader and locking the bootloader haven't put me back on track. You mentioned the Intel flash tool and the OTA update which I already have. Anyway I can flash the update without losing data? I tried with stock recovery but it basically told me the build number was wrong (i.e. you're supposed to flash from KitKat to Lollipop, not Lollipop to Lollipop!!) and restoring the Kitkat bios hasn't changed the situation.

F1Fanatic27 said:
Well reflashing the OS loader and locking the bootloader haven't put me back on track. You mentioned the Intel flash tool and the OTA update which I already have. Anyway I can flash the update without losing data? I tried with stock recovery but it basically told me the build number was wrong (i.e. you're supposed to flash from KitKat to Lollipop, not Lollipop to Lollipop!!) and restoring the Kitkat bios hasn't changed the situation.
Click to expand...
Click to collapse
You mentioned previously that you had been using TWRP. For the sake of redundancy, I'd suggest making a full backup with it as well.
With either CWM/TWRP, try restoring only SYSYEM and DATA partitions. See if that help.
If you end up having to restore stock via Intel Flash utility, you can use an app called Online NAndroid Backup and NAndroid Manager to open up the image and manually choose which apps (and data) you want to restore.
You would restore this data after you reapplied the stock image to your system. The apps require root.
Moving forward, I'd also suggest investing in Titanium Backup. Always do a full backup of user, system apps and data. With that, you'd just root your fresh stock and restore with the TB app. I do that for multilayered protection.
I will post the app links later this morning. Gotta get in to the office right quick
Lastly, with the Intel flash util, have you tried restoring just boot and recovery? A partial restore. Don't forget the 'Sparcing' setting.

Thanks again. I already reflashed KitKat and then updated to Lollipop before I saw your post, but the online Nandroid Manager thing sounds shockingly useful!! I'll see about restoring the apps from the backup.
Meanwhile I should probably start using Titanium Backup with this tablet, somehow never thought of doing so as I am with my LG G4.

F1Fanatic27 said:
Thanks again. I already reflashed KitKat and then updated to Lollipop before I saw your post, but the online Nandroid Manager thing sounds shockingly useful!! I'll see about restoring the apps from the backup.
Meanwhile I should probably start using Titanium Backup with this tablet, somehow never thought of doing so as I am with my LG G4.
Click to expand...
Click to collapse
So, you were able to restore your Yoga tablet with the Intel flasher and OWA. Is that correct?
Thanks for boldly going where no Yoga user has gone before.
I am keeping notes on everything and will update you all after I test a few scenarios and options.
For all reading, the following are important prerequisites for a project like this where no custom recovery and the like make the scenario different:
- Titanium Backup: Make a full apps+data backup in Android with this app
- Make a full backup with tethered CWM
-Make another backup with tethered TWRP
I still need direct 830F testers or models close to this.

jumpup said:
So, you were able to restore your Yoga tablet with the Intel flasher and OWA. Is that correct?
Click to expand...
Click to collapse
Yep, Intel flasher for Kitkat and then standard OTA update for Lollipop. Can't wait for the ROM!!

F1Fanatic27 said:
Yep, Intel flasher for Kitkat and then standard OTA update for Lollipop. Can't wait for the ROM!!
Click to expand...
Click to collapse
And, to confirm, you were running Lollipop at the beginning of all this, right?
Sent from my SM-N910T3 using Tapatalk

Status Update: I am working with a few of the better deodex/zipalign/etc dev apps to find one that's a good feel for the Yoga. Things like the following:
http://forum.xda-developers.com/showthread.php?t=2360670
Anyone familiar with these tools that prefer any one over the other?

Stock ROMs Factory v6.1 , v8.3 , v8.4 , v8.5 , v8.7, V9.0, V9.2-patch : v21

CAUTION TO NOT LOOSE TWRP
I read two posts that say v21, now again on V8.5, put the stock recovery back instead of twrp. This is probably a side effect of a fresh stock /system and wipe of /data.
As a preventive step, when done flashing and wiping reboot to recovery FIRST, before booting the system It will allow recovery to handle removing the recovery-from-boot.p that flashes stock recovery.
I just patched the modified V7.4.2 up to the newly released 8.3 now 8.4. 8.5, 8.7,9.0 -V9.2 Patch
New update has been made from V17 to V21 of the non prime version of R1-HD, Non prime is behind on security patch (2017-05-05)
Copied ROM from phone and made twrp install ROM from it.
* No preloader change (official updates change the preloader to block your ability to use sp flash tools for rom flashing)
* No lk.bin change __ this part is what allows you to choose boot options(boot menu when power and volume pressed together)
* No "FOTA" app Fota has now been left in to make it easier to get next update, if that ever happens.
* No opera browser
* No adds (removed in the modified 7.4.2)
* Custom boot logo (only done on v8.3, there was no interest in this so abandoned)
--Newer versions of rom left stock, Leaving mods up to user.
** while it is not necessary to do a wipe with this ROM, I still recommend it.
**Thanks:
** @vampirefo needed his patched v7.4.2 in order to apply this new 8.3 patch and again for 8.4
** @ColtonDRG OR @jasonmerc I do not remember which one made it: For the image used in the custom logo
and the modified zip is here .
Roms are rootable with SuperSU, flashed in twrp after install. Must be done in systemless mode. In order to patch system veridy in boot.img
Logo update did not work on original rom changing link to updated version
BLU rolled v8.3 back to v7.4.2 because of app compatability issues. V8.4 is there fixed release. Both 8.3 and 8.4 are modified prime roms with ads stripped
V21 is the non prime update.
Unmodified V6.1
==>NON-ROOTED-logo-not-replaced-modified-V8.3
==>Fixed Logo modified NON_ROOTED V8.3
==>>modified V8.4
==>>modified V8.5
==>>Full with Ads V8.7
==>>Full with Ads V9.0
==>>Patch For V9.2 must be flashed on top of fresh V9.0
****Run debloat ==>script to remove ads if you need/ want to, or remove from zip before flashing ****
alt. manual example: before reboot, while still in twrp. Select mount and put checkmark next to system. Then run these two commands in adb terminal
Code:
adb shell rm /system/priv-app/com.amazon.*/com.amazon.*.apk
adb shell rm /system/app/Adups*/*.apk
==>>Modified V21
** stand alone logo installs

I flashed this but I didn't get the custom boot logo.

mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
I had that happen to my second phone too.
I don't have an explanation yet.
I even made a separate update.zip , that one didn't make the logo change either. I did eventually change it with sp flash tool.
I tried with both recoveries.
and multiple /dev location formats. and for whatever reason my one phone did not accept the logo change from recovery.
And the other test phone it worked.

mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
Neither did I but it all seems to be working fine

Been using this for about a day now, likewise no custom boot logo, but that's fine. Otherwise, it's been running super well. A lot better than the previous mostly stock version did for me with the bloatware APKs removed after the install. A lot of the general idiosyncrasies of the previous version of the stock rom seem to have gone away for me. It seemed to have weird storage management issues, errors moving to SD, broken symlinks that prevent apps from moving or being reinstalled, and a lot of other little non-storage issues, but so far, none off that here.
Long story short, good work! I hope we eventually see proper 7.x roms through some of the efforts going on, but in the meanwhile, your work here has made life a little bit better on 6.

It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
**logo-update is same as composite but with alt updater-binary
**composite-logo screenshot is in op
**stock logo will return to original BLU logo

mrmazak said:
It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
Click to expand...
Click to collapse
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?

Serenitybs said:
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?
Click to expand...
Click to collapse
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )

linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
Somebody already tried this out

linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
It was just wishful thinking. I have no idea how all of this is done. All I know is @mrmazak has helped me to fall in love with my phone again with this V8.3. The 7.4.2 did seem a bit buggy for my phone but this update works beautifully and I didn't even root it. If this remains true I will be happy with this phone for awhile even on 6.0

Really confused right now.
I was browsing through the settings menus. And found in the Settings-security- menu a toggle labeled "quick boot" ( not to be confused with "fastboot") . I enabled it then rebooted to see if it booted quicker. Didn't seem to make much if any difference. So I went back to turn it back off. And it wasn't there. I checked in my other phone , it wasn't there on that one either.
Did any body see this menu item, and if so where is is it?
Edit 1:
Few more power off , power on cycles to compare times. With other phone and defiantly seems to have turned on some faster boot option.
This phone goes from off to on in 5-6 seconds other phone takes about 20.
Edit 2:
OK , I panicked for a minute.
Couldn't find the setting and thought that it was another way to block sp flash tool by preventing you from ever being fully powered off.
But the setting was in accessibility not security.

Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?

detroitredwings said:
Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?
Click to expand...
Click to collapse
The mode changer app is technically a security issue. I did have that warning a few times when using mode changer app from the XDA thread of the developer, then when I used the app downloaded from f-droid it worked with systemless root and didn't give the security warning.

The app downloaded from f-droid worked for me as well, many thanks!

Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.

Letitride said:
Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.
Click to expand...
Click to collapse
I also had an app that previously work, say is not compatible now.
Maybe has to do with apps that have links to pay accounts. And that has something to do with trustzone. (Tee1 & tee2)
Those sections I left out of the update. I will add it back in and test. Update when I do. It is also possible this problem is why Blu rolled back there update.
**EDIT**
well that didn't go well at all.
I flashed the new trustzone.bin files from the official update. Now phone no longer turns on and no longer connects to flash tool
**EDIT 2**
After much persistence and many failed attempts to get phone recognized in pc again. Finnaly got to a point that phone was cycling between "preloader" driver and "usb serial device", and with careful timing was able to start sp flash tool at just right time and the flashing back to original trustzone files seems to have recovered phone.
for the record i am not sure what steps made it work. But I was shifting back and forth between leaving phone sit on charge, then on charge with rubber band wrapped around power button, then not plugged in , and not plugged in with rubber band on power button.

Okay... persistence is key in customization, i guess! I am getting somewhere here!
mrmazak said:
The first link is needed to get phone unlocked so you can install twrp.
Click to expand...
Click to collapse
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!

OldSkewler said:
Okay... persistence is key in customization, i guess! I am getting somewhere here!
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!
Click to expand...
Click to collapse
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Many ways to do that.
Easiest is to copy to phone while phone is connected to PC.
Cam also download file from internet with your phone.
Bottom line is get zip file to the phone boot to recovery and install

Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3

mrmazak said:
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Easiest is to copy to phone while phone is connected to PC.
Bottom line is get zip file to the phone boot to recovery and install
Click to expand...
Click to collapse
Right on man! I am officially running 8.3 ROM with April 5th 2017 Security Patch Level! Geez.. it was not easy but I got this working!
MrMazak, I followed all your instructions on both links, so could you tell me what exactly I have on my phone? Is it rooted? Bootloader Unlocked? The phone seems to be working fine but I don't know what level of access I have. Honestly I don't even know exactly what the differences between all these terms are.
Also, do I have or not SU? One of the steps under the .bat I believe install it. How do I access it?
Thanks again!
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
Weasel0 said:
Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3
Click to expand...
Click to collapse
My install is pretty fresh, couple of hours, but as far as I can tell all is working fine with Wifi, As a matter of fact this is a new device only connected with Wifi and no SIM Card.... internet works fine.

Installing the best ROM nowadays for Defy (+)

Hello everybody I got brand new Motorola Defy+ and I want to have newest version of android on it. I am not familiar with rooting etc and unsure if this is possible theres instruction in videos description on youtube "How to Install Android Nougat on Motorola DEFY+ (Android 7.1.1/CM14.1)" ( I can not post links) If not I am curious what is the safest and easiest way to root the device and if theres available newer system than KitKat for my device
Moreover I wanted to install roehsoft ram expander as the phone got only 512 MB of RAM but test says it has to have compatible kernel from what I remember. Not sure if I have to install new operating system in the first place and then root the phone or the opposite and what kernel it has to have to work properly. As I said before I am not experienced android user its my first device with this system
Thank you in advance ppl peace!

Amazing, Motorola Defy+ is cool in its segment but can this slim hardware keep up with such a bulky Android version?
It's said in KittyKat threads here phone has a tendency to stutter with KK (as such a demanding OS), and how about Nougat?
Anyway it'd be nice if somebody adjust Nougat to work worth Defy+. Especially it is needed to optimize battery consumption in idle.

And about rooting, you can just run apk called FramaRoot and job is done
Afterwards run SndInitDefy_2.3 and you will have custom recovery installed (CWM), it is just as simple as it!
http://cloud.tapatalk.com/s/5965fe184202f/Framaroot-1.9.3.apk
http://cloud.tapatalk.com/s/5965fe43f2a32/SndInitDefy_2.3.apk
Afterwards, make a nandroid backup and, using already installed custom recovery CWM (which is clumsy, without touch support), you may want to flash TWRP. If so then flash defy_twrp_recovery_2.6.3.0.zip, e.g. from this link:
http://d-h.st/users/tejus.k.v
Although attention: this flashes recovery TWRP to the system partition (probably the phone's recovery partition is to small) overwriting the android system which is already there, so after doing this you must flash some ROM.
It is described in the second post of this KittyKat ROM thread: [ROM] [4.4.2] SlimKat (jordan) [STABLE 4.0] [Weekly 3.85] [Unofficial]
And see Installation Instructions section, good luck! ?

pawwaap said:
And about rooting, you can just run apk called FramaRoot and job is done
Afterwards run SndInitDefy_2.3 and you will have custom recovery installed (CWM), it is just as simple as it!
http://cloud.tapatalk.com/s/5965fe184202f/Framaroot-1.9.3.apk
http://cloud.tapatalk.com/s/5965fe43f2a32/SndInitDefy_2.3.apk
Afterwards, make a nandroid backup and, using already installed custom recovery CWM (which is clumsy, without touch support), you may want to flash TWRP. If so then flash defy_twrp_recovery_2.6.3.0.zip, e.g. from this link:
http://d-h.st/users/tejus.k.v
Although attention: this flashes recovery TWRP to the system partition (probably the phone's recovery partition is to small) overwriting the android system which is already there, so after doing this you must flash some ROM.
It is described in the second post of this KittyKat ROM thread: [ROM] [4.4.2] SlimKat (jordan) [STABLE 4.0] [Weekly 3.85] [Unofficial]
And see Installation Instructions section, good luck!
Click to expand...
Click to collapse
Thank you for your help! My phone dont want to turn on anymore. I've done everything carefully up to the following point"Wipe /data, /cache, and /system in TWRP or use defy_safewipe.zip" (after that I wanted to flash this: "Slim-mb526-4.4.2.build.4-UNOFFICIAL-20140407-2344.zip" cos its ROM right?), but and when it asked me to slide back to the right blue arrow to confirm, my phone booted up and then died after motorola logo. Green led lighted up before death. It seems that it wasnt safe thing despite the name. What to do now? Can I recovery it?
--
UPDATE: ok its working again :angel:, Ive tried combo "up volume" and "power" buton.
Now Ive got no idea what "Gapps" or "Slimroms addons you want" are, but after mad long startup (with SlimKAT logo on the screen), it seems that this system is working. Its much faster than befo I can see. It's RUNNING! :laugh:
--
UPDATE 2: Play Store refuses to open on this new system after I installed it. "Unfortunately, Google Play Store has stopped."

I have just flashed this ROM:
[Kitkat][Nightlies] CM11 Android 4.4 for the Defy(+), it is the most advanced so far as I can see, the freshest release is cm-11-20161124-NIGHTLY-mb52x so half a year old.
If you read instructions on this thread you can see it's installation is somewhat tricky.
It includes rearranging partitions layout and sizes.
If you really want experimenting with flashing Nougat you will probably need the technique to change partitions sizes, and you may edit the values inside the resize.zip according to individual needs (post #5595)
And the half of the links from the first post are empty, however in the middle of the thread there are still working links.
After all it's better to follow this version of installing instructions (post #5584)
Also you can find some files here: http://defy.svolkov.name/quarx2k.ru/
I have done partitions resizing, bootstrap, and managed to flash the first ROM, version: cm11.0-defy-newlife.zip,
however wrongly have done cache & Dalvik reset just after resizing (and before ROM flashing): the result is ROM is working well but cannot boot into recovery anyway (and can't recreate recovery anyway either, even doing:
Code:
cat /sdcard/bootstrap_ext3.img > /dev/block/mmcblk1p1
as suggested in the post: https://forum.xda-developers.com/showpost.php?p=57221743&postcount=6510)
And I'd like have the freshest version, the only way is to flash stock and do everything from a start again. Please if you can, how to flash stock? It is said elsewhere the most critical in it is choosing the right version of sbf file, choosing inappropriate would brick a phone irreversibly! And how to know which one to choose, tutorials here are so convoluted and discussions so chaotic! Afraid of touching anything though!
As far as the ROM itself, although it is the first only cm11.0-defy-newlife.zip it works amazingly well!
It boots quickly, is fast, RAM friendly, nice!
(It has little overclocked processor and this makes using the phone so comfortably, just little overclocked so hardware friendly too!)

pawwaap said:
I have just flashed this ROM:
[Kitkat][Nightlies] CM11 Android 4.4 for the Defy(+), it is the most advanced so far as I can see, the freshest release is cm-11-20161124-NIGHTLY-mb52x so half a year old.
If you read instructions on this thread you can see it's installation is somewhat tricky.
It includes rearranging partitions layout and sizes.
If you really want experimenting with flashing Nougat you will probably need the technique to change partitions sizes, and you may edit the values inside the resize.zip according to individual needs (post #5595)
And the half of the links from the first post are empty, however in the middle of the thread there are still working links.
After all it's better to follow this version of installing instructions (post #5584)
Also you can find some files here: http://defy.svolkov.name/quarx2k.ru/
I have done partitions resizing, bootstrap, and managed to flash the first ROM, version: cm11.0-defy-newlife.zip,
however wrongly have done cache & Dalvik reset just after resizing (and before ROM flashing): the result is ROM is working well but cannot boot into recovery anyway (and can't recreate recovery anyway either, even doing:
Code:
cat /sdcard/bootstrap_ext3.img > /dev/block/mmcblk1p1
as suggested in the post: https://forum.xda-developers.com/showpost.php?p=57221743&postcount=6510)
And I'd like have the freshest version, the only way is to flash stock and do everything from a start again. Please if you can, how to flash stock? It is said elsewhere the most critical in it is choosing the right version of sbf file, choosing inappropriate would brick a phone irreversibly! And how to know which one to choose, tutorials here are so convoluted and discussions so chaotic! Afraid of touching anything though!
As far as the ROM itself, although it is the first only cm11.0-defy-newlife.zip it works amazingly well!
It boots quickly, is fast, RAM friendly, nice!
(It has little overclocked processor and this makes using the phone so comfortably, just little overclocked so hardware friendly too!)
Click to expand...
Click to collapse
Again I want to thank you for your response. On the verion of system Ive installed I cant use my camera for video recording because of lack of some codecs it says and I cant watch YouTube. 'Google Services' crashes. The only way I could download some decent apps was from 'Aptoide'. 'Roehsoft Ram Expander' needed Google services so it wont open (ive download 'Kernel audiutor' however I dont have class 10 card yet so I dont know if its good at all). I wont be fighting with this anymore, I am going to try mentioned 'CM11 Android 4.4 for the Defy(+)'.
So I have to go "Recovery" in this secret startup menu before I install it? I mean do I have downgrade my system before instalation of new one? Or just follow the instructions straight from the beggining I dunno. But I dont want any complicated things you know..
--
The links are dead, but Ive found them files:
defy.7z
Now, you metrioned two rom's but which one is less tricky, cm11.0-defy-newlife.zip or cm-11-20161124-NIGHTLY-mb52x.zip?

You know, I have installed cm-11-20161124-NIGHTLY-mb52x.zip at last, after exciting night of attempting flashing any stock ROM and then following the procedure exactly from the first post of "[Kitkat][Nightlies] CM11 Android 4.4 for the Defy(+)"
and the updated files: new_bootstrap and resize, found here
It costed many efforts of blindly "trial and error" flashing one by one stock ROMs, until found the one which turned on my phone with anything else than black screen!
And everything it was to have possibility of flashing cm-11-20161124-NIGHTLY-mb52x.zip instead of already running cm11.0-defy-newlife.zip.
And you know what? The version cm11.0-defy-newlife.zip seemed running better than the freshest one!
It was, what is most important: faster!!!
And anything else seems the same (so far)!!!
Is the any rationale behind hustle and bustle of flashing the "NIGHTLY" and exactly for what?
Question of stability which user gets know only after some time?
Anyway the speed is everything in such thin hardware like Defy+ and i can't resist an impression cm11.0-defy-newlife.zip is way faster!
And what's more, you probably can flash cm11.0-defy-newlife.zip without the whole convoluted procedure of resizing partitions! (needs checking, if you want simplest way you had better resize partitions )
In fact this version of ROM is the same as:
Quarx said:
8. Install cm11.0-defy-newlife.zip (It's latest cm11 from 23sep with changes for new table)
Click to expand...
Click to collapse
but cm11.0-defy-newlife.zip was to try if the only resizing procedure itself worked at all (and for users to send feedback).
In fact resizing partitions is needed only for the next ROM versions (of which the freshest is cm-11-20161124-NIGHTLY-mb52x.zip):
"the nightlies AFTER 01 Oct are for the new partition table".
(Aha, cm-11-20161124-NIGHTLY-mb52x.zip probably is odexed, while cm11.0-defy-newlife.zip is deodexed, it needs confirmation)

And if you needed flashing stock and had doubts how, then write, I'd gladly help and share the knowledge painstakingly acquired this night.
It is amazingly simple and safe, there're few simple basic things but if you needed found them by yourself in this forum you would probably get panicked
It is about how simple things people can mess up! ?

pawwaap said:
And if you needed flashing stock and had doubts how, then write, I'd gladly help and share the knowledge painstakingly acquired this night.
It is amazingly simple and safe, there're few simple basic things but if you needed found them by yourself in this forum you would probably get panicked
It is about how simple things people can mess up!
Click to expand...
Click to collapse
Thank you my friend. Ive installed cm11.0-defy-newlife.zip. Its fine because my camera can now record videos but still it cant play it. :crying:
YouTube videos also wont load, however internet is fast and so on.
--
Google Play still dont work, same error. I kinda came to terms with it as I have Aptoide, but I want to use YouTube..

And what do you use to watch YouTube videos? Advise third party apps, e.g. SnapTube etc, instead of YouTube application. In fact forgot installing gapps at all and it makes me happy You only now made me think about it In such thin hardware it is better to have microG (μG) (for apps refusing running without Google Services) and/or Yalp Store for Play Market access
If you insist using bulky Google then try opengapps.org

pawwaap said:
And what do you use to watch YouTube videos? Advise third party apps, e.g. SnapTube etc, instead of YouTube application. In fact forgot installing gapps at all and it makes me happy You only now made me think about it In such thin hardware it is better to have microG (μGl) (for apps refusing running without Google Services) and/or Yalp for Play Market access
Click to expand...
Click to collapse
I guess gapps are apps for new software? Ok so now that I have downloaded SnapTube I still cant play any video. Its loading but wont start just like videos on my phone storage or just recorded
Hah I think its a bit off topic what we made here, I should change name of the tread
--
Ive read on some native forum that after codecs instalation he problem disappeared I try to find some

I have just recorded a video of my dog, sent it via email (AquaMail), received it in a mail to myself and played it with system player, pretty well!
It is possible freshest NIGHTLY ROM has issues solved, how to check it (without Google)?
And can you play videos self recorded with this phone?
OpenGapps.org provides you ability to choose what package, how complex (I always choose "pico"), and for what platform (yes, KittyKat is still supported) you download.

pawwaap said:
I have just recorded a video of my dog, sent it via email (AquaMail), received it in a mail to myself and played it with system player, pretty well!
It is possible freshest NIGHTLY ROM has issues solved, how to check it (without Google)?
And can you play videos self recorded with this phone?
OpenGapps.org provides you ability to choose what package, how complex (I always choose "pico"), and for what platform (yes, KittyKat is still supported) you download.
Click to expand...
Click to collapse
OK its seems that Google Play cant be downloaded straight to the phone (.apk) after installing new system but gapps worked for me and I got my Google Play working again now. Still no luck with videos on YouTube but vlc is working on files Ive recorded.

Tritius46 said:
Ive installed cm11.0-defy-newlife.zip.
Click to expand...
Click to collapse
And how have you installed this ROM: with partitions resizing first or on stock layout?
Tritius46 said:
Hah I think its a bit off topic what we made here, I should change name of the tread
Click to expand...
Click to collapse
Yes, you can change for e.g.
"Installing the best ROM nowadays for Defy (+)"
And it is said Defy and Defy+ is the same hardware, just plus is rebranded and has overclocked processor (to 1GHz) and bit bigger battery, see section "Facts" in [GUIDE] All-in-One Defy Beginner's guide
or "Yielding Defy competitive nowadays"
It is still phone unique on the market, searched something for summer, a little waterresistant phone which could suit to any even tiniest pocket. And found Defy is just the only one in this kind, nowadays producers offer big smartphones and if you want something little & watertight then you can buy modern smartwatch - thanx, prefer Defy: bigger battery, faster, and of incomparable comfort of usage, for peanuts! [emoji106]

pawwaap said:
And how have you installed this ROM: with partitions resizing first or on stock layout?
Click to expand...
Click to collapse
Ive just followed the steps here did exactly what is written step by step from the beggining.
I think now the only is playing videos. Videos I have recorded (on the phone) can be played back only in vlc but still with lags. Same for vids online, however if I choose mobile version of YouTube and try to play stream in vlc it worx but very poor quality. I tried many things without any success, for eg. Flash Fox but the problem is rather in system files than settings and apps itself.
In my custom system I could playback any video.

Tritius46 said:
Ive just followed the steps here did exactly what is written step by step from the beggining.
Click to expand...
Click to collapse
It's irrelevant for video playing but I think it is better to follow the first post from the thread and use the files:
new_bootstrap & resize (instead of PrepareZip_1 & PrepareZip_2),
new_bootstrap has different size than PrepareZip_1 and is newer, something has been changed.
Tritius46 said:
I think now the only is playing videos. Videos I have recorded (on the phone) can be played back only in vlc but still with lags.
Click to expand...
Click to collapse
You see, I play with phone system player any videos recorded with phone system camera application without any problem.
Is the newest NIGHTLY ROM better in the sense the issues have been ultimately repaired?
If so, make android backup of data partition, reboot into TWRP, wipe cache, Dalvik, data (factory reset), and flash the newest NIGHTLY!
(Yet if you enjoy playing with comparing the two system you may wait )
And maybe before flashing next ROM do these newer new_bootstrap.zip & resize.zip flashing (just in case: of avoiding extra issues).
Tritius46 said:
Ive just In my custom system I could playback any video.
Click to expand...
Click to collapse
And in Defy?

pawwaap said:
It's irrelevant for video playing but I think it is better to follow the first post from the thread and use the files:
new_bootstrap & resize (instead of PrepareZip_1 & PrepareZip_2),
new_bootstrap has different size than PrepareZip_1 and is newer, something has been changed.
Sent from my E2303 using Tapatalk
Click to expand...
Click to collapse
OK so I will try now cm-11-20161124-NIGHTLY-mb52x with new_bootstrap and resize. Do I have to just install them like before right? It will replace system I have now?
--
UP:
pawwaap said:
wipe cache, Dalvik, data (factory reset), and flash the newest NIGHTLY!
Click to expand...
Click to collapse
Ok I get it

If so, make nandroid backup of data partition, reboot into TWRP, wipe cache, Dalvik, data (factory reset), and only then (but immediately without rebooting after wiping) do these newer new_bootstrap.zip & resize.zip flashing!
The files you can find here
After flashing NIGHTLY successfully, boot it, follow the initial wizard etc, check if it works ok, and if so reboot into TWRP again to restore your data nandroid backup.
If you don't care about previous data give in with it and configure your Android anew

pawwaap said:
And in Defy?
Click to expand...
Click to collapse
Dont get me wrong, I meant my system version android which came to me with my phone purchase (android 2.3.6 or something dont remember). And its definitely not prob with camera but system video player, plus YouTube dont play too so definitely some playback issue..

Omg omg E:Error executing updater binary in zip '/sdcaed/kitkat 4.4/cm-11-20161124-NIGHTLY-mb52x.zip' 'FAILED' what todo? Reboot and try again?
Maybe file was corrupted

How to return everything to normal? I can not root

Hello friends.
In this post I want to relate a problem that is happening to me, I want to see if you can help me. For starters, I think I'm an idiot
9 months ago I bought a Moto G5 Plus from Amazon, it is not a Prime user, it is the version without advertising, as soon as I arrived I did this, unlock the bootloader, install TWRP (3.1) and ROOT.
I am a person who likes custom roms, however this is the first cell that managed to keep stock for so long. I did a search here in the forum to determine two custom roms I wanted to try and I chose this
https://forum.xda-developers.com/g5-plus/development/rom-resurrection-remix-v5-8-3-t3614992
And also
https://forum.xda-developers.com/g5-plus/development/8-1-x-miracledroid-1-0-magical-world-t3807224
I had 2 custom roms, I had the gapps downloaded, I lacked a reason, well, I explain, when I bought the cell phone I installed LINK2SD, with which I tried to remove apps from the factory and it was impossible even being a ROOT user, in fact I could only freeze them , added to this ROOT access for some options, some applications, but in others jumped messages "You are not ROOT user" or GameKiller example, ROOTchecker said that if it was ROOT, apart from this the ROM Stock from the beginning had been somewhat unstable, but nothing unbearable, but over time it was getting slow and was annoying already, aprobachando the excuse, I decided to update the TWRP with the PlayStore APP, as I noticed that the installed version was very slow, even took to start the TWRP, a Once updated, everything went very fast, everything in order.
I prepare to do the wipes, I start to think that here was my mistake, I frame the following options
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have always marked the option System, but now I have my doubts, first I passed RR, I gave an error, I said sure it was downloaded badly, I install the Miracle, it installs well, I proceed to install Open Gapps, clean cache and when restarting this appears .. In the TWRP the memories remained intact, the internal space had my files
I do not despair, I look for a solution (I still had access to TWRP, I do not know if that would have helped), but I find a firmware and I do the flash ... I run out of TWRP, it said "No Comand" in the recovery mode, I flash the TWRP, flash logo, but when trying to flash the SuperSu gave error, "unmount / data" and others, I realized that the internal space was 0 mb, I used a video to "repair" and change the file system, it worked, flash the SuperSu, stays in the logo, nothing you do removes the logo. I flash the firmware again, flash the twrp, flash logo, enter the TWRP and ask for an encryption password or something, I accept blank, I keep doing things, cleaning, etc ... when I restart the cell phone says something of the "decryption" incorrect"
I do the factory reset and it eliminates the TWRP ... I left it like this, I installed the apps and I'm using it that way, I would like to know if they can help me flash the correct rom (I think I installed the wrong one), repair the errors, make me root and install a custom rom.
I'm doing flash with this firmware POTTER_RETAIL_7.0_NPNS25.137-93-10_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
A friend who I sold the Amazon Prime version that I bought earlier than this one has the NPNS25.137-93-8, which is a patch from March 1, 2018, mine is from April, but in mine the variant is Retus, the one from he says Amz
We both have same baseband
Thank you very much

MrFloppy22 said:
Hello friends.
In this post I want to relate a problem that is happening to me, I want to see if you can help me. For starters, I think I'm an idiot
9 months ago I bought a Moto G5 Plus from Amazon, it is not a Prime user, it is the version without advertising, as soon as I arrived I did this, unlock the bootloader, install TWRP (3.1) and ROOT.
I am a person who likes custom roms, however this is the first cell that managed to keep stock for so long. I did a search here in the forum to determine two custom roms I wanted to try and I chose this
https://forum.xda-developers.com/g5-plus/development/rom-resurrection-remix-v5-8-3-t3614992
And also
https://forum.xda-developers.com/g5-plus/development/8-1-x-miracledroid-1-0-magical-world-t3807224
I had 2 custom roms, I had the gapps downloaded, I lacked a reason, well, I explain, when I bought the cell phone I installed LINK2SD, with which I tried to remove apps from the factory and it was impossible even being a ROOT user, in fact I could only freeze them , added to this ROOT access for some options, some applications, but in others jumped messages "You are not ROOT user" or GameKiller example, ROOTchecker said that if it was ROOT, apart from this the ROM Stock from the beginning had been somewhat unstable, but nothing unbearable, but over time it was getting slow and was annoying already, aprobachando the excuse, I decided to update the TWRP with the PlayStore APP, as I noticed that the installed version was very slow, even took to start the TWRP, a Once updated, everything went very fast, everything in order.
I prepare to do the wipes, I start to think that here was my mistake, I frame the following options
I have always marked the option System, but now I have my doubts, first I passed RR, I gave an error, I said sure it was downloaded badly, I install the Miracle, it installs well, I proceed to install Open Gapps, clean cache and when restarting this appears .. In the TWRP the memories remained intact, the internal space had my files
I do not despair, I look for a solution (I still had access to TWRP, I do not know if that would have helped), but I find a firmware and I do the flash ... I run out of TWRP, it said "No Comand" in the recovery mode, I flash the TWRP, flash logo, but when trying to flash the SuperSu gave error, "unmount / data" and others, I realized that the internal space was 0 mb, I used a video to "repair" and change the file system, it worked, flash the SuperSu, stays in the logo, nothing you do removes the logo. I flash the firmware again, flash the twrp, flash logo, enter the TWRP and ask for an encryption password or something, I accept blank, I keep doing things, cleaning, etc ... when I restart the cell phone says something of the "decryption" incorrect"
I do the factory reset and it eliminates the TWRP ... I left it like this, I installed the apps and I'm using it that way, I would like to know if they can help me flash the correct rom (I think I installed the wrong one), repair the errors, make me root and install a custom rom.
I'm doing flash with this firmware POTTER_RETAIL_7.0_NPNS25.137-93-10_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
A friend who I sold the Amazon Prime version that I bought earlier than this one has the NPNS25.137-93-8, which is a patch from March 1, 2018, mine is from April, but in mine the variant is Retus, the one from he says Amz
We both have same baseband
Thank you very much
Click to expand...
Click to collapse
First of all your data partition is encrypted out of the box so if you want to flash a custom ROM you have to format data in TWRP ( the wipe where you have to confirm with "yes", not just wipe) to decrypt it.
Also for flashing a 64 bit Oreo rom you have to flash a 64bit TWRP Version ,you can find it in " ROMs and kernels, Android development" for potter.
Also make sure that you have a full nandroid backup incl. EFS and persist. If you don't have these backups you won't be able to return to stock without losing voLTE,4G or IMEI, maybe all of them.
For rooting try magisk 16 instead of superSU which is dead in fact, no more development since chainfire retired about 9 months ago.
Amz devices are unlockable, retus/reteu/retin etc are not.
Sent from my Moto G5 Plus using XDA Labs

Thank you very much
Wolfcity said:
First of all your data partition is encrypted out of the box so if you want to flash a custom ROM you have to format data in TWRP ( the wipe where you have to confirm with "yes", not just wipe) to decrypt it.
Also for flashing a 64 bit Oreo rom you have to flash a 64bit TWRP Version ,you can find it in " ROMs and kernels, Android development" for potter.
Also make sure that you have a full nandroid backup incl. EFS and persist. If you don't have these backups you won't be able to return to stock without losing voLTE,4G or IMEI, maybe all of them.
For rooting try magisk 16 instead of superSU which is dead in fact, no more development since chainfire retired about 9 months ago.
Amz devices are unlockable, retus/reteu/retin etc are not.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
First of all, I am very grateful for your answer, I already understood that I did everything wrong, starting with the fact of not having any backup, although in fact I already placed the stock software as I said in the post, and I think I have not lost the imei since I use my cell phone in a normal way. In fact I just reviewed, I still have the imei, but if you mean to look for a downgrade or place the version that came from Amazon, because I do not give much importance, the phone is functional, what I want is to install the TWRP , be ROOT again and most importantly install a custom rom ... But what I'm not sure is if the problems that happened to me after installing the current stock, have to do with that the cell phone was something wrong in the partitions or If I am doing wrong steps, you would be so kind to help me and sorry for being annoying and taking your time. I'll be very greatful.
Forgive my English, I'm using the google translator :crying:

MrFloppy22 said:
First of all, I am very grateful for your answer, I already understood that I did everything wrong, starting with the fact of not having any backup, although in fact I already placed the stock software as I said in the post, and I think I have not lost the imei since I use my cell phone in a normal way. In fact I just reviewed, I still have the imei, but if you mean to look for a downgrade or place the version that came from Amazon, because I do not give much importance, the phone is functional, what I want is to install the TWRP , be ROOT again and most importantly install a custom rom ... But what I'm not sure is if the problems that happened to me after installing the current stock, have to do with that the cell phone was something wrong in the partitions or If I am doing wrong steps, you would be so kind to help me and sorry for being annoying and taking your time. I'll be very greatful.
Forgive my English, I'm using the google translator :crying:
Click to expand...
Click to collapse
The ROM you're using (POTTER_RETAIL_7.0_NPNS25.137-93-10_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip) is the correct one for a retus device.
Follow this guide exactly
https://forum.xda-developers.com/g5-plus/how-to/how-to-root-moto-g5-plus-t3579659/post74673573
but use the above 93-10 ROM to install it via fastboot, flash TWRP and magisk as rooting solution.
This should you bring to a rooted stock ROM with custom recovery TWRP installed.
At this point you can stay there or if you are really sure you want to flash a custom ROM make a full nandroid backup in TWRP first.
Then choose your preferred ROM and the fitting gapps (usually mentioned in the ROMs thread) download magisk 16 zip, wipe your device, format data and flash ROM,gapps and magisk.
If you have problems with the latest official TWRP https://twrp.me/motorola/motorolamotog5plus.html
(3.2.3.0) you can try one from this thread
https://forum.xda-developers.com/g5...ry-twrp-3-1-1-0-touch-recovery-t3701488/page8
but you should be good to go with the official one as it works with encrypted devices now.
Sent from my Moto G5 Plus using XDA Labs

Steps...
Wolfcity said:
The ROM you're using (POTTER_RETAIL_7.0_NPNS25.137-93-10_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip) is the correct one for a retus device.
Follow this guide exactly
https://forum.xda-developers.com/g5-plus/how-to/how-to-root-moto-g5-plus-t3579659/post74673573
but use the above 93-10 ROM to install it via fastboot, flash TWRP and magisk as rooting solution.
This should you bring to a rooted stock ROM with custom recovery TWRP installed.
At this point you can stay there or if you are really sure you want to flash a custom ROM make a full nandroid backup in TWRP first.
Then choose your preferred ROM and the fitting gapps (usually mentioned in the ROMs thread) download magisk 16 zip, wipe your device, format data and flash ROM,gapps and magisk.
If you have problems with the latest official TWRP https://twrp.me/motorola/motorolamotog5plus.html
(3.2.3.0) you can try one from this thread
https://forum.xda-developers.com/g5...ry-twrp-3-1-1-0-touch-recovery-t3701488/page8
but you should be good to go with the official one as it works with encrypted devices now.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Sorry to be so noob ... First, I follow the steps but with the firmware that I have already used?
Second: the backup of the nandroid can be in the internal memory? Currently I do not have a microSD ... In fact, the one I had passed to 0 mb, as well as the internal memory, I have not recovered it yet.
Third: how do I recover my microSD?
Fourth: Everything from the backup to the installation of custom rom can I do from the internal memory? Or do I need a microSD?
I have a USB OTG from where I tried to install the roms and gapps

MrFloppy22 said:
Sorry to be so noob ... First, I follow the steps but with the firmware that I have already used?
Second: the backup of the nandroid can be in the internal memory? Currently I do not have a microSD ... In fact, the one I had passed to 0 mb, as well as the internal memory, I have not recovered it yet.
Third: how do I recover my microSD?
Fourth: Everything from the backup to the installation of custom rom can I do from the internal memory? Or do I need a microSD?
I have a USB OTG from where I tried to install the roms and gapps
Click to expand...
Click to collapse
1. Yes use the firmware you mentioned POTTER_RETAIL_7.0_NPNS25.137-93-10_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
2. As the internal storage will be wiped by formatting data the backup would be erased.
You have to store it on external SD or an USB otg storage.
3. I don't know. Maybe you have to reformat the SD card because link2sd created an additional partition. Connect it to a PC and check if it's recognised. If yes save your data to PC and reformat it to ext4.
If it's not recognised it's maybe broken.
4. The backup should be on an external storage, SD or USB otg. Flashing a custom ROM/gapps/magisk can be done from internal but you have to be careful to not wipe internal storage by TWRP before flashing.
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
1. Yes use the firmware you mentioned POTTER_RETAIL_7.0_NPNS25.137-93-10_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
2. As the internal storage will be wiped by formatting data the backup would be erased.
You have to store it on external SD or an USB otg storage.
3. I don't know. Maybe you have to reformat the SD card because link2sd created an additional partition. Connect it to a PC and check if it's recognised. If yes save your data to PC and reformat it to ext4.
If it's not recognised it's maybe broken.
4. The backup should be on an external storage, SD or USB otg. Flashing a custom ROM/gapps/magisk can be done from internal but you have to be careful to not wipe internal storage by TWRP before flashing.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Hello Wolfcity,
Grateful for all the help you have given me, I still stand in my decision to install a custom rom, but the truth is I am somewhat undecided, today I have the microSD and I will follow the guide you recommended, but I am not sure to install the custom rom I said in my post.
Would you recommend any? I liked the customization of RR, but I would like to move to 8.1 ... But without having to go to 64 bits ... Some minimalist / modern, stable rom, good performance and low battery consumption? With the stock after a while had errors, such as a Coin Princess game, one day it did not open anymore and showed the message "the application stopped", the cell phone was sincerely heavy, slow, and the games or applications installed did not require so many resources to show those errors, a simple game like 42 in 1 (NES games) had this error after a while.
I need something light, fluid, stable, and with some performance in games (it's not everything).

MrFloppy22 said:
Hello Wolfcity,
Grateful for all the help you have given me, I still stand in my decision to install a custom rom, but the truth is I am somewhat undecided, today I have the microSD and I will follow the guide you recommended, but I am not sure to install the custom rom I said in my post.
Would you recommend any? I liked the customization of RR, but I would like to move to 8.1 ... But without having to go to 64 bits ... Some minimalist / modern, stable rom, good performance and low battery consumption? With the stock after a while had errors, such as a Coin Princess game, one day it did not open anymore and showed the message "the application stopped", the cell phone was sincerely heavy, slow, and the games or applications installed did not require so many resources to show those errors, a simple game like 42 in 1 (NES games) had this error after a while.
I need something light, fluid, stable, and with some performance in games (it's not everything).
Click to expand...
Click to collapse
I'm still on stock. I'm a big fan of custom ROMs and use different ones on all my devices and did so in the past but I never got a device with such a good ROM like the potter comes with. I never had problems like you mentioned, it's fluid, fast and battery friendly. This is the first reason that I'm still on 7.0 stock. The second thing are the risks of losing IMEI or 4G when you want to return from a 64bit custom ROM to stock firmware. I have a full nandroid backup including persist so I should be good to go but who knows?
Something in the actual custom ROMs (or maybe gapps) messes with the partitions of the Moto G5+.
I will wait for the offlcial stock Oreo update, also I think that the actual problems with custom ROMs will be sorted out when Motorola releases the Oreo kernel sources.
The developers will be able to fix things like HD and most probably also this losing IMEI thing.
So I can't recommend a custom ROM as I don't use one on potter. On my Moto G 2014 titan the Pixel Experience does a great job in performance and battery, also AEX runs good with more customazions but not such a good battery backup.
But this is for titan, I don't know how they work on potter.
If you want to go that route you will have to test it out. Another option would be a debloated stock like the one from Franco : https://franco28.github.io/stockrom
If your stock ROM has gotten slow and maybe faulty you could try to flash a clean stock firmware and make a fresh start. If it's not your hardware making problems your device should work good again. Sometimes there is just to much garbage or issues from installed software, tweaks and things like that making a device perform bad and a fresh start could help.
Whatever you do good luck!
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
I'm still on stock. I'm a big fan of custom ROMs and use different ones on all my devices and did so in the past but I never got a device with such a good ROM like the potter comes with. I never had problems like you mentioned, it's fluid, fast and battery friendly. This is the first reason that I'm still on 7.0 stock. The second thing are the risks of losing IMEI or 4G when you want to return from a 64bit custom ROM to stock firmware. I have a full nandroid backup including persist so I should be good to go but who knows?
Something in the actual custom ROMs (or maybe gapps) messes with the partitions of the Moto G5+.
I will wait for the offlcial stock Oreo update, also I think that the actual problems with custom ROMs will be sorted out when Motorola releases the Oreo kernel sources.
The developers will be able to fix things like HD and most probably also this losing IMEI thing.
So I can't recommend a custom ROM as I don't use one on potter. On my Moto G 2014 titan the Pixel Experience does a great job in performance and battery, also AEX runs good with more customazions but not such a good battery backup.
But this is for titan, I don't know how they work on potter.
If you want to go that route you will have to test it out. Another option would be a debloated stock like the one from Franco : https://franco28.github.io/stockrom
If your stock ROM has gotten slow and maybe faulty you could try to flash a clean stock firmware and make a fresh start. If it's not your hardware making problems your device should work good again. Sometimes there is just to much garbage or issues from installed software, tweaks and things like that making a device perform bad and a fresh start could help.
Whatever you do good luck!
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
I'll take your recommendation into account, although I repeat I DO NOT WANT a 64bit rom ?
But I will try to use the stock by adding greenify and other add-ons that help improve performance and performance.
Regarding the hardware issue, I was just afraid of that since it started with the problems, it was not the same in all the applications, only some, but the slowness if it was notorious (although with a chrome with +1200 tabs, I suppose it is normal ?). I hope it's not a problem related to hardware ? ... It's no longer guaranteed (I'm from Venezuela, besides, it would be hard to send it back).
And I tell you one of my experiences, when I just acquired it, I became root, downloaded link2sd ... but I did not uninstall the factory apps (although if I did the process), I could only freeze. Hence my doubts about system malfunction or SuperSu.
Maybe it was also due to the use I gave it, it was excessive, I work with my cell phone, I also play to distract myself and install many utilities, extra calculators, payment processors like PayPal, many messaging services, anyway, I maintain that 150 applications, and now that I'm in the stock ... with just the basics, there are only 57 applications, big difference ?
I have a titan with viper OS ... Excellent device, motorola is not the same as before, in my opinion, if it were not for the little ram, I would still continue with my G2.
Well, I'll be doing the process in a couple of hours, thank you very much, I'll tell you how it went.

Newbie bricked his phone, has solution but cannot implement it ,needs Linux help, PLZ

Howdy,
First the problem, then I will tell you what I have done to get here and what I have found to fix it........
The problem:
Adb sideload is saying:
sudo adb sideload OnePlus6tOxygen_34_OTA_20_all_1904032212b6154bb7f26.zip
loading: 'OnePlus6tOxygen_34_OTA_20_all_1904032212b6154bb7f26.zip'
* cannot read 'OnePlus6tOxygen_34_OTA_20_all_1904032212b6154bb7f26.zip' *>
What I did to get here:
I use MX Linux
Accidentally wiped my phone while playing around with unlocking the bootloader. Decided to install Lineage Unofficial. Installed TWRP, Lineage, GAPPS, Magisk. Everything booted and worked fine, but pretty much hated it because so many apps won't work. Found lots of work arounds, but the core communication apps I have to have won't work. Decided to flash Oxygen back on the phone.
My adb backup turns out is probably corrupt and won't install. ADB extractor can't seem to work on my system so I cant fix my extract and fix the back up.
Downloaded the factory zip.
Opened TWRP flashed the rom......and here is where I messed up.......instead of rebooting to recovery and reinstalling TWRP I reinstalled TWRP and MAGSIK then rebooted. Now I can only boot to TWRP
You can stop laughing now. I NOW realize my mistake and the solution seems to be to adb sideload the image and reboot to system.
Oh yeah, for some dumb reason I did a wipe somewhere in there without tucking the os image somewhere safe 1st, so it is no longer on the phone to install from TWRP.
When I try to sideload I get the above error message and all of the guides for solving that error message are for windows......a system I haven't used for almost 3 years.
My semi educated/guessing stab at the problem is the file size. from my reading adb tries to load the entire file into ram. I need to overcome the 2g ram limit ( from my reading ) but can't find any instructions on how to do that for Linux.
Solution 2 would be find a really small, lite ROM to load, get the phone where it will boot, set up TWRP again, download the OOS zip and flash from TWRP.....the right way, but I am clueless as to what rom would be small enough to not get the above error.
Thank you very much in advance, Glockdoc

PattayaGlock said:
Howdy,
First the problem, then I will tell you what I have done to get here and what I have found to fix it........
The problem:
Adb sideload is saying:
sudo adb sideload OnePlus6tOxygen_34_OTA_20_all_1904032212b6154bb7f26.zip
loading: 'OnePlus6tOxygen_34_OTA_20_all_1904032212b6154bb7f26.zip'
* cannot read 'OnePlus6tOxygen_34_OTA_20_all_1904032212b6154bb7f26.zip' *>
What I did to get here:
I use MX Linux
Accidentally wiped my phone while playing around with unlocking the bootloader. Decided to install Lineage Unofficial. Installed TWRP, Lineage, GAPPS, Magisk. Everything booted and worked fine, but pretty much hated it because so many apps won't work. Found lots of work arounds, but the core communication apps I have to have won't work. Decided to flash Oxygen back on the phone.
My adb backup turns out is probably corrupt and won't install. ADB extractor can't seem to work on my system so I cant fix my extract and fix the back up.
Downloaded the factory zip.
Opened TWRP flashed the rom......and here is where I messed up.......instead of rebooting to recovery and reinstalling TWRP I reinstalled TWRP and MAGSIK then rebooted. Now I can only boot to TWRP
You can stop laughing now. I NOW realize my mistake and the solution seems to be to adb sideload the image and reboot to system.
Oh yeah, for some dumb reason I did a wipe somewhere in there without tucking the os image somewhere safe 1st, so it is no longer on the phone to install from TWRP.
When I try to sideload I get the above error message and all of the guides for solving that error message are for windows......a system I haven't used for almost 3 years.
My semi educated/guessing stab at the problem is the file size. from my reading adb tries to load the entire file into ram. I need to overcome the 2g ram limit ( from my reading ) but can't find any instructions on how to do that for Linux.
Solution 2 would be find a really small, lite ROM to load, get the phone where it will boot, set up TWRP again, download the OOS zip and flash from TWRP.....the right way, but I am clueless as to what rom would be small enough to not get the above error.
Thank you very much in advance, Glockdoc
Click to expand...
Click to collapse
Msm tool

Thanks James, but that is a mcirosoft based solution.
I don't use windows.
I can't seem to find a linux version.

PattayaGlock said:
Thanks James, but that is a mcirosoft based solution.
I don't use windows.
I can't seem to find a linux version.
Click to expand...
Click to collapse
Then you're screwed...

Idk about your backups but why not just run Windows in a VM? From there you could easily run MSMTool or the stock fastboot adb option. I've never had success flashing OOS via twrp coming from a custom rom.

The plot thickens.......
Well James, thanks. LOL.. I am amazed how many android developer, hackers, tinkerers DON"T use linux.
Demon Lord, thanks for the USEFUL heads up. Thanks for paying attention to the post that mentioned I use Linux. I had entertained that as a very last resort. I have 1 machine that is dual boot windows so I probably would have used that one.
On to the next chapter. .....
I am up and running with Oxygen OS again. Still not sure exactly how.
I turned my phone off and was going to swap sims into another phone so I at least have a phone. Pull the phone out of the case and the damn thing booted into lineage!! All my downloads and files were still there. Not sure how after a wipe, but they were.
My guess is the case was holding down the volume button and this is why it kept booting to TWRP. No idea why Igot into lineage as I installed and wiped last night before my booting to recovery started. Since Lineage booted up,and the OOS zip was there, I booted into TWRP recovery and installed OOS from the zip.
I still don't know how all of this worked out like it did, but I am up and running. I still have to set up all my settings and apps( this time without signing into or using my google account ), but I am good to go.
The original problem still exists so I will leave the post open so others can reply with a fix.
Looks like this was a case of having a just enough knowledge about what I was doing to get in trouble!!
Thanks for responding to my problem.
JC

PattayaGlock said:
The plot thickens.......
Well James, thanks. LOL.. I am amazed how many android developer, hackers, tinkerers DON"T use linux.
Demon Lord, thanks for the USEFUL heads up. Thanks for paying attention to the post that mentioned I use Linux. I had entertained that as a very last resort. I have 1 machine that is dual boot windows so I probably would have used that one.
On to the next chapter. .....
I am up and running with Oxygen OS again. Still not sure exactly how.
I turned my phone off and was going to swap sims into another phone so I at least have a phone. Pull the phone out of the case and the damn thing booted into lineage!! All my downloads and files were still there. Not sure how after a wipe, but they were.
My guess is the case was holding down the volume button and this is why it kept booting to TWRP. No idea why Igot into lineage as I installed and wiped last night before my booting to recovery started. Since Lineage booted up,and the OOS zip was there, I booted into TWRP recovery and installed OOS from the zip.
I still don't know how all of this worked out like it did, but I am up and running. I still have to set up all my settings and apps( this time without signing into or using my google account ), but I am good to go.
The original problem still exists so I will leave the post open so others can reply with a fix.
Looks like this was a case of having a just enough knowledge about what I was doing to get in trouble!!
Thanks for responding to my problem.
JC
Click to expand...
Click to collapse
Just a fyi. OP6T uses the A/B partitioning scheme. Would explain how you could boot into lineage with everything intact after a wipe. Say OOS is on Partition A and lineage on B. When you boot into Twrp you should be able to see which slot you're currently on.

You want stock? Boot into twrp, flash stock rom, twrp installer. Go to reboot menu and see what slot you are on. Reboot into recovery. Note again which slot you are in. Reflash stock rom and twrp. Reboot to recovery and note what slot you are using. Flash Magisk.Go to wipe menu format data. Boot system. Note!! BEFORE DOING THIS COPY ALL YOUR IMPORTANT FILES ON PHONE TO YOUR PC SO YOU CAN RESTORE THEM AFTER FORMATING DATA..
Sent from my ONEPLUS A6010 using Tapatalk

I can't believe how many people jump straight to the MSM tool, this should not be the first thing you use. These phones are so easy to fix without using something that locks your bootloader. That should be your last resort.
Also a Linux user here, and I've recovered my phone using the link below, something to keep in mind in the future:
OP6T Fastboot ROM
Not sure what you had not working though in Lineage, odds are you didn't enable some permissions in the Trust Center / Privacy Guard or something though. Everything should just work.

Agreed
OhioYJ said:
I can't believe how many people jump straight to the MSM tool, this should not be the first thing you use. These phones are so easy to fix without using something that locks your bootloader. That should be your last resort.
Also a Linux user here, and I've recovered my phone using the link below, something to keep in mind in the future:
OP6T Fastboot ROM
Not sure what you had not working though in Lineage, odds are you didn't enable some permissions in the Trust Center / Privacy Guard or something though. Everything should just work.
Click to expand...
Click to collapse
I agree with you. I bricked my phone a couple weeks back, the same as op. But I manual fastboot flashed every .img and still to no avail. But then I flashed all .imgs again then booted to twrp>flashed twrp installer> factory reset> the wipe data> flash rom>reboot twrp > wipe data again then I was able to boot in oos 9.0.14 with no issues. So if your still having trouble follow the steps from the fastboot ROM thread that the person I quoted said to then continue with what I said above. You will be back up and running in no time. BTW it took me about an HR total.

PattayaGlock said:
Howdy,
First the problem, then I will tell you what I have done to get here and what I have found to fix it........
The problem:
Adb sideload is saying:
sudo adb sideload OnePlus6tOxygen_34_OTA_20_all_1904032212b6154bb7f26.zip
loading: 'OnePlus6tOxygen_34_OTA_20_all_1904032212b6154bb7f26.zip'
* cannot read 'OnePlus6tOxygen_34_OTA_20_all_1904032212b6154bb7f26.zip' *
Click to expand...
Click to collapse
Waaaaaaaaaaaaaay too much work involved on your side...
All you needed to do was copy the ROM to the phone while it is booted in TWRP. It has MTP capabilities. From there just flash the rom like normal. If your linux is being hard with MTP, although it shouldnt, you could also have done an ADB Push command.
The error you are getting seems like its being caused by an old version of ADB however, I dont know that for fact.
Done!

So 9.0.15 wasn't working out so well for me, and I did something bone headed downgrading.... Guess what I'm doing right now.... No MSM tool needed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

PattayaGlock said:
Thanks James, but that is a mcirosoft based solution.
I don't use windows.
I can't seem to find a linux version.
Click to expand...
Click to collapse
Windows garbage install via Virtualbox... works like a charm.