Database Users

Which ROM to install now on YB1-X90F (android)

Hi. I've never really liked the Android version in my Lenovo but I am now facing an annoying issue with Play Store downloads getting stuck and delayed and going to have to reinstall.
At this point I am ready for a root and changing the ROM but I am rather lost in what android distribution are working and tested at the moment as after reading for a while there are some which are only for the Win version. I also see some references to X90L on threads about rooting and installing twrp but I am assumming these would work the same on my F version.
So the question is, what updated current ROMs are working fine and are worth (better than the official one) after root and TWRP on the Android version?
Also, once unlocked and changed bootloader, where can you get the official ones again?
Thanks for any help.

"Also, once unlocked and changed bootloader, where can you get the official ones again?"
You don't need it if you flash YB via Intel Flash Tool with oryginal rom.

Problems with Moto G5 Plus

I'm worried that I've permanently messed up my phone. I didn't make a backup of my stock firmware when I first flashed Lineage OS, and then I was having issues with that, so now I'm using the stock one again, but it's not official. I used fastboot to flash it and then flashed twrp and magisk. That should of been sufficient to factory reset it right? It just keeps having little problems that it didn't have before, like internet loading things slowly and bugs and crashing apps. The reason I switched off the Lineage OS rom is because it had little problems like that too. I just don't know what to do anymore.
Relevant Info:
Device: Moto G5 Plus Unlocked US version
Carrier: T-Mobile

lumbo7333 said:
I'm worried that I've permanently messed up my phone. I didn't make a backup of my stock firmware when I first flashed Lineage OS, and then I was having issues with that, so now I'm using the stock one again, but it's not official. I used fastboot to flash it and then flashed twrp and magisk. That should of been sufficient to factory reset it right? It just keeps having little problems that it didn't have before, like internet loading things slowly and bugs and crashing apps. The reason I switched off the Lineage OS rom is because it had little problems like that too. I just don't know what to do anymore.
Relevant Info:
Device: Moto G5 Plus Unlocked US version
Carrier: T-Mobile
Click to expand...
Click to collapse
What exactly are your problems? Check the thread of the custom ROM you installed and look for fixes there, maybe you installed an outdated version and your problems have been fixed in the updates. Good luck.

lumbo7333 said:
...now I'm using the stock one again, but it's not official. I used fastboot to flash it and then flashed twrp and magisk.
Click to expand...
Click to collapse
What do you mean with "stock but not official"?
Where did you get it from?
There are some sources for official firmwares signed by Motorola here on XDA so what makes you think the one you use isn't official?
If so that could be for sure the reason for problems for I have to say that I haven't seen unofficial stock ROMs except TWRP flashables (you said you flashed using fastboot so it can't be this) or debloated stock ROMs.

Wolfcity said:
What do you mean with "stock but not official"?
Where did you get it from?
There are some sources for official firmwares signed by Motorola here on XDA so what makes you think the one you use isn't official?
If so that could be for sure the reason for problems for I have to say that I haven't seen unofficial stock ROMs except TWRP flashables (you said you flashed using fastboot so it can't be this) or debloated stock ROMs.
Click to expand...
Click to collapse
I mean it didn't come officially from Motorola. I got it from this:
getdroidtips.com/moto-g5-plus-stock-firmware-collections-updated (It's not allowing me to post outside links because I'm a new user, so just add www to that)

lumbo7333 said:
I mean it didn't come officially from Motorola. I got it from this:
getdroidtips.com/moto-g5-plus-stock-firmware-collections-updated (It's not allowing me to post outside links because I'm a new user, so just add www to that)
Click to expand...
Click to collapse
If you can flash the firmware by fastboot it's most likely an official signed firmware that was leaked. To be on the safe side use the firmware found here on XDA like this source:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Just make sure to use the same firmware you we're on or a newer one that fits to your region.
I recommend to reflash the latest stock firmware, maybe something went wrong the first time.
And remember to always make a backup before you flash anything that could cause problems.

It the latest stock firmware different from the stock rom I flashed?

You can also try the repair function in Lenovo Moto Smart Assistant app.
https://support.motorola.com/us/en/solution/MS126499

Hmm. Now my security updates are failing.

goodjuju said:
You can also try the repair function in Lenovo Moto Smart Assistant app.
https://support.motorola.com/us/en/solution/MS126499
Click to expand...
Click to collapse
Will doing that use official firmware?

lumbo7333 said:
It the latest stock firmware different from the stock rom I flashed?
Click to expand...
Click to collapse
lumbo7333 said:
Will doing that use official firmware?
Click to expand...
Click to collapse
Sure. The firmwares from Moto Smart Assistant are the same like the ones I've posted above, I compared the hash files.
Would be interesting to know what firmware you're on at the moment.

I'm on OPSS28.85-17-2
I thought my firmware was unofficial since it was leaked. Also do you why I can't update?

lumbo7333 said:
I'm on OPSS28.85-17-2
I thought my firmware was unofficial since it was leaked. Also do you why I can't update?
Click to expand...
Click to collapse
Any firmware you'll find is leaked even the official ones. Motorola doesn't release any firmwares except the ones you can download with Lenovo Motorola Smart Assistant.
The link I posted https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
contains official firmwares too. The latest one for the US (85-17-4) can be found there too.
What happens exactly when your OTA fails?

Wolfcity said:
Any firmware you'll find is leaked even the official ones. Motorola doesn't release any firmwares except the ones you can download with Lenovo Motorola Smart Assistant.
The link I posted https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
contains official firmwares too. The latest one for the US (85-17-4) can be found there too.
What happens exactly when your OTA fails?
Click to expand...
Click to collapse
- I download the update the update
- It reboots and goes into TWRP for some reason
- I have to manually reboot to system from TWRP
- My phone boots to system and says update unsuccessful
(This is a security update by the way.)

lumbo7333 said:
- I download the update the update
- It reboots and goes into TWRP for some reason
- I have to manually reboot to system from TWRP
- My phone boots to system and says update unsuccessful
(This is a security update by the way.)
Click to expand...
Click to collapse
You can't take any system updates when you have TWRP installed!
For OTA you have to be on unrooted full stock ROM incl. stock recovery. This is a very important rule.
So you have to ways to handle this:
- Flash clean stock firmware and apply to the OTA afterwards (if you flash the latest firmware 17.4 you don't need the OTA anymore). You will loose your internal storage data or skip the "erase userdata" command.
Firmware from here: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
- Take a TWRP flashable build but be aware that you can't take OTA updates at all in the future which is not needed as the firmwares are up to date.
TWRP flashables here:
https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482

Wolfcity said:
You can't take any system updates when you have TWRP installed!
For OTA you have to be on unrooted full stock ROM incl. stock recovery.
So you have to ways to handle this:
- Flash clean stock firmware and apply to the OTA afterwards (if you flash the latest firmware 17.4 you don't need the OTA anymore). You will loose your internal storage data or skip the "erase userdata" command.
Firmware from here: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
- Take a TWRP flashable build but be aware that you can't take OTA updates at all in the future which is not needed as the firmwares are up to date.
TWRP flashables here:
https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482
Click to expand...
Click to collapse
Will flashing a new build delete my data?

YT9216BJ (MT8227L) Head Unit Root Question

So I bought this head unit and i am looking to root it. I'm accustomed to XDA and rooting and I also found the russian forum that disscusses these head units but I'm lost. It seems mine is newer(?) or more up to date than im seeing. It says android 10.1(it seems to be really 9) and is API 27.
Things i see seem to be giving root for my device but downgrading it. Is there any assistance I can receive on this? Attached some screenshots.

Reckerr said:
So I bought this head unit and i am looking to root it. I'm accustomed to XDA and rooting and I also found the russian forum that disscusses these head units but I'm lost. It seems mine is newer(?) or more up to date than im seeing. It says android 10.1(it seems to be really 9) and is API 27.
Things i see seem to be giving root for my device but downgrading it. Is there any assistance I can receive on this? Attached some screenshots.
Click to expand...
Click to collapse
Okay so having the newer Android shouldn't be a problem as your unit type and MCU are right for modding.
I've successfully modded a similar unit only a couple of weeks back. Backup your current ROM by exporting the full memory dump, just in case of brick.
You start with installing TWRP recovery. Normally only version 3.0.2 will work. If not, try newer then older versions. One of them will stick.
After TWRP it's an easy ride. Install SuperSU v2.79 and if it doesn't work, try newer then older versions.
Now you can install Viper4Android. I suggest you stick to version 2.5.0.
Now just configure everything you need.

Ok thanks for the reply. I did some searching today on the forum after reading your post but all I see is flashing a whole new rom.
Is there a guide to just install TWRP to my current stock rom(I actually like it) and then the usual SuperSU to obtain root priveleges?

Reckerr said:
Ok thanks for the reply. I did some searching today on the forum after reading your post but all I see is flashing a whole new rom.
Is there a guide to just install TWRP to my current stock rom(I actually like it) and then the usual SuperSU to obtain root priveleges?
Click to expand...
Click to collapse
I just posted this this guide that provides custom firmware and lots of improvements to YT9216BJ, that includes TWRP, SuperSU and much much more. You can of course stick with the stock firmware but there is an option of making your unit much more appealing

RFA: SM-T510 - Sourcing the factory image(s)?

New to Samsung platforms, excuse any ignorance..
Tried to source the factory image for a new-out-of-box SM-T510 with the following details:
==
T510XXU3BTFN
samsung/gta3xlwifixx/gta3xlwifi
10/QP1A.190711.020/T510XXU3BTFN
build date jun302020
buildid QP1A.190711.020.T510XXU3BTFN
Secpatch 2020-07-01
Android 10
Bootloader U3
==
If there's anything I'm missing let me know.
The usual suspects seem to list packages *later* than that reported on the device (from recovery anyway).
It hasn't yet been fully booted yet - in case there's a way to pull the factory image from recovery/download as a clean image.
I'm looking for that factory image assuming it would be needed in case my modding and experiments (as per our kind of thing) causes breakage.
I wouldn't ask if my efforts had been successful - posting is a last resort
Ta
EDIT:
Is the device ID "T510XXU3BTFN" a constant regardless of software revision/build?
Insofar as; the designator describes the platform; and all software applicable for the platform is referred to by this ID - regardless of software version/revision.
Where software is referred to by a platform designator, I assume there's no proper case where it is applicable to a different platform ID.
If I can get confirmation on this assumption it would help me narrow down exactly what I can use from what I can find on the source sites I have located.

benryanau said:
New to Samsung platforms, excuse any ignorance..
Tried to source the factory image for a new-out-of-box SM-T510 with the following details:
==
T510XXU3BTFN
samsung/gta3xlwifixx/gta3xlwifi
10/QP1A.190711.020/T510XXU3BTFN
build date jun302020
buildid QP1A.190711.020.T510XXU3BTFN
Secpatch 2020-07-01
Android 10
Bootloader U3
==
If there's anything I'm missing let me know.
The usual suspects seem to list packages *later* than that reported on the device (from recovery anyway).
It hasn't yet been fully booted yet - in case there's a way to pull the factory image from recovery/download as a clean image.
I'm looking for that factory image assuming it would be needed in case my modding and experiments (as per our kind of thing) causes breakage.
I wouldn't ask if my efforts had been successful - posting is a last resort
Ta
EDIT:
Is the device ID "T510XXU3BTFN" a constant regardless of software revision/build?
Insofar as; the designator describes the platform; and all software applicable for the platform is referred to by this ID - regardless of software version/revision.
Where software is referred to by a platform designator, I assume there's no proper case where it is applicable to a different platform ID.
If I can get confirmation on this assumption it would help me narrow down exactly what I can use from what I can find on the source sites I have located.
Click to expand...
Click to collapse
That is not the latest by far. Use frija.exe to get the latest stock ROM.

lewmur said:
That is not the latest by far. Use frija.exe to get the latest stock ROM.
Click to expand...
Click to collapse
Thanks for the response
Yes it's the as-shipped build, but before I try to work out which of the newer builds is appropriate and won't lock-out what I'm palnning to do with Ithe device..
I need (I expect so) that factory ROM as a file - to roll back to or restore if(when) I stuff something up in my next steps (TWRP/CWM, bootloader, magisk/root, rom version upgrade and/custom rom etc)
The earliest I can find seems like the latest, which isn't what I'm seeking

benryanau said:
Thanks for the response
Yes it's the as-shipped build, but before I try to work out which of the newer builds is appropriate and won't lock-out what I'm palnning to do with Ithe device..
I need (I expect so) that factory ROM as a file - to roll back to or restore if(when) I stuff something up in my next steps (TWRP/CWM, bootloader, magisk/root, rom version upgrade and/custom rom etc)
The earliest I can find seems like the latest, which isn't what I'm seeking
Click to expand...
Click to collapse
The latest is what you need to do all of the things you want. Earlier versions won't work. The only time you need an earlier version is when a new one has just come out and the devs haven't caught up with it yet. When you do, you can often find them on Sammobile.
edit: Also, if you let it, your tablet should update itself to the latest version. So if something goes wrong, the latest is what you'd need to get it back working.

Ah cheers, my concern was a new(er) release would block the ability to do some things to the device.
I kind of expected it AFAIK it's not uncommon and mostly assumed there's be issues with rollback fuses etc and stuff you can no longer do beyond version x.xx release (BL AP etc)
I might have seen reference to this being the case in the various info's I've read - basically if you want to do XYZ (multiboot, PXE, TWRP I don't know) you have to do it before a certain release.
**lwmr** I take it unlike other mfg's platforms I've worked on it's not an issue here so I can crash on ahead and it won't bite me?
edit:: I also found it strange I guess that the FW release history seems incomplete, Sammobile doesn't IIRC even list versions from around 2019 on these tabs. Unless samsung's volume of products and releases are too much to track I wonder dunno

benryanau said:
Ah cheers, my concern was a new(er) release would block the ability to do some things to the device.
I kind of expected it AFAIK it's not uncommon and mostly assumed there's be issues with rollback fuses etc and stuff you can no longer do beyond version x.xx release (BL AP etc)
I might have seen reference to this being the case in the various info's I've read - basically if you want to do XYZ (multiboot, PXE, TWRP I don't know) you have to do it before a certain release.
**lwmr** I take it unlike other mfg's platforms I've worked on it's not an issue here so I can crash on ahead and it won't bite me?
edit:: I also found it strange I guess that the FW release history seems incomplete, Sammobile doesn't IIRC even list versions from around 2019 on these tabs. Unless samsung's volume of products and releases are too much to track I wonder dunno
Click to expand...
Click to collapse
LOL, yeah, Samsung isn't like Amazon where they are constantly trying to find ways to keep you from blocking their advertising. Trying to downgrade to previous versions can be a problem, but only because of security issues. With these ROMs and recoveries, the devs attempt to keep up with the latest stock releases and will normally specify in the OP which stock ROM they are based on. So long as you aren't attempting to install an older version of a custom ROM based on Android 9 or earlier, having the latest stock version shouldn't be a problem.

(sigh) yep it's not just Amazon
Righto I got ya thanks for the info's I'll roll with that
cheers

Can't find twrp file that works for SM-350. Please help.

My apologies if I accidently broke the rules with this post. I haven't posted for a long time and I'm a bit rusty on use of this forum.
I have a Galaxy Tab A that I have been trying to load TWRP on, without success. I am convinced the reason is that the TWRP files ae for the wrong hardware.
After calling Samsung tech support here is the info I can provide to identify the tablet.
Samsung SM-T350NZWAXAR gt58wifi-gt58wifixx-smt350 Build number NMF26XT350XXU1CQJ5
Now when I search for the TWRP tar file, the only thing close to a match for the hardware is codename a8hplte . I selected the most recent TWRP file.
Well, I've flashed that tar file using Odin several times but I still get the stock recovery when I boot into recovery .
Is it possible that Samsung has a device for which TWRP doesn't work? I'm hoping someone out there has the same model and can tell me what I'm doing wrong.
Thanks in advance.

Forgot to mention, I sent an email query to TWRP. They didn't respond. No help whatsoever.

No idea where you were looking, but the 1st page of the rom, kernel + recovery subforum for the Samsung tab already has a thread with TWRP for the SM-T350.
Now it's not my specific tablet so idk if it works, but you can just read the thread and ask there.

Nimueh said:
No idea where you were looking, but the 1st page of the rom, kernel + recovery subforum for the Samsung tab already has a thread with TWRP for the SM-T350.
Now it's not my specific tablet so idk if it works, but you can just read the thread and ask there.
Click to expand...
Click to collapse
Thank you very much for taking the time to reply. I had been trying to get a image/tar file from the official TWRP website. Now, I also saw the page you provided a link to. When I read it, I saw that the version (
twrp_3.1.0-1_sm-t350_18317.tar) that was recommended is in a category labeled "for Marshmallow only). What I have is Nougat, and in that category there is no SM-350 TWRP file. So if you would please help me one more time; Should I be using the file from the Marshmallow only category, or the Nougat for SM-355 (which doesn't match what I have)? Thank you again for your assistance.​

BigZ1 said:
Thank you very much for taking the time to reply. I had been trying to get a image/tar file from the official TWRP website. Now, I also saw the page you provided a link to. When I read it, I saw that the version (
twrp_3.1.0-1_sm-t350_18317.tar) that was recommended is in a category labeled "for Marshmallow only). What I have is Nougat, and in that category there is no SM-350 TWRP file. So if you would please help me one more time; Should I be using the file from the Marshmallow only category, or the Nougat for SM-355 (which doesn't match what I have)? Thank you again for your assistance.​
Click to expand...
Click to collapse
Like I said - it's not MY device, so I suggest you ask in the linked thread as the users there will HAVE the device and know better

download ROM/firmware (lowest possible version) from https://www.sammobile.com according to your CSC, repair tablet with Odin3, and unlock bootloader first