yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Mik-el:
INSTRUCTIONS for ROM 2.0.1

Many thanks for the instructions you just provided to the other users @io2345 !

@io2345 has helped me with the boot.img part too!

io2345, I think that the fully unrooted boot.img you just uploaded is the one I've already replaced inside the ROM. (the magisk patched one).

At this point we could just upload the other boot.img in case someone a boot.img with Root-Tools preinstalled (I don't think so).

Anyway correct me if I'm wrong :)

Thanks for the feedback!

I've also put the ROM files inside a .7zip archive to speed up downloads :)

A new video? :D
[Android Software Development] sandr2010:
Thank
[Android Software Development] io2345:
@Mik-el : In fact the boot.img-file I provided in post #162 is the unpatched one. The file included in the ROM is already Magisk-patched, which probably won't make any difference to a normal user. Just in case you want to Magisk-patch the file in future versions, you'll need the original version.

Not working in Magisk is the "MagiskHide"-Feature. This is due to the limitations of the currently used kernel (more information on this here) and can only be overcome, if an able developer will provide a new kernel.
[Android Software Development] sandr2010:
Can I re-upload to another exchanger and post a link to 4pda?
[Android Software Development] Mik-el:
Thanks for the clarification io2345.

Yes you were right to reiterate that "Magisk-Hide" can't be used on both the 2 boot.img files.

This is a message I posted some time ago on my Galaxy Ace Rom thread, sorry for the copy-paste:

<< I use that file host for many reasons: it does not waste my google drive space, it's safe, It doesn't spam ads or adult stuff, it allows me to know how many people download my works and their nationality.

Moreover reposts could be bad because if my files register 0 downloads in 2 months (or something like that) they'll be lost forever, and I don't have access to other people's accounts on Android File Host and so on.

>>

Anyway if you say to me that downloads are painfully slow, I'm reuploading the file just now on another file hosting service, I'm posting the link on 4pda too (I already have an account, but I think you know that).

The problem with 4pda is the language (my translated Russian is not so good) and the fact that the text can't be formatted in the posts, I think the moderators should be less rigid.

Anyway I'll post the link there asap. :)
[Android Software Development] YuriRM:
Remember that in Portugal most owners of EStar Takee 1 are female!

It is crucial to demo how easily EStar Takee 1 is updated to Android 7.1.2.

Showing step-by-step the full procedure of phone backup and instalation of Mik-el's custom ROM.

This will remove many fears and reassure female owners that they can do it by themselves.

Like president Barack Obama said... "Yes, we can!"
[Android Software Development] YuriRM:
The link to Dimonikod's video on Android 7.1.2 has expired at 4pda. Have you got a copy? I would like to watch his video.

Can you ask Dimonikod to make a new video on the latest version (ROM 2.0.1), please?

It would be nice to post his new video on YouTube.

This helps many owners of EStar Takee 1 discover Android 7.1.2.

Let us promote the great work of the team behind

Mik-el Android for Takee 1​

ROMs, TWRP recoveries, Holographic 3D videoplayer
[Android Software Development] Mik-el:
@YuriRM the video is still online, but you need a 4pda account to watch it :) the video could be re-uploaded on YouTube by me or Dimonikod (but I'll need a confirmation from him)
[Android Software Development] YuriRM:
Version 1.1 of the ROM is not good enough to showcase the very best of

Mik-el Android for Takee 1​

We must release a video on the latest version 2.0.1
[Android Software Development] io2345:
Just found, that the Google-Apps-Installer included in the 2.0.1 package doesn't run from TWRP (probably some mis-spelled directory name in the installer script). Maybe Mi-kel finds the time to correct the error in the installer and will re-upload the package.

If you don't want to wait for that, here is the most simple solution: Open the file "G_Apps_2021_most_lightweight_Mik-el.zip" from the package, go to directory "system" and extract the file "gapps.zip" to the same directory from where you install the ROM (like a SD-Card in your phone).

So if you want to have Google-Apps installed together with the ROM, first install the ROM "Mik-el_Android_2.0.1_unrooted.zip" and after that (without rebooting) the "gapps.zip".

If you want to have root access, install the "MagiskCanary22006.apk" after full boot-up and open the App "Magisk" - it will tell you, that it has to do some additional setup and reboot the phone - select "OK".
[Android Software Development] Mik-el:
Ok thanks @io2345 !

Now that I can run the Gapps Installer I made, I can get the error from TWRP and fix the updater-script file according to it.

(I won't re-upload a new ROM just for that, I'll update the latest link :) )
[Android Software Development] YuriRM:
[Guide-Tool][Linux] Projekt ScriBt v2.2.1 [Build-A-ROM][Newbie-Friendly]​

Projekt ScriBt, is a Bash Shell Script which helps a Aspiring Developer to build an Android ROM, in an understandable way

Only for Serious students

Umm, you're in Chef Central right ? :D

It is recommended to view this thread in a Browser (Web/Mobile)

https://xdaforums.com/t/guide-tool-linux-projekt-scribt-v2-2-1-build-a-rom-newbie-friendly.3503018/
[Android Software Development] zdomjus:
Hi guys, while you were all engaged in the design of a new amazing ROM, I had to cope with the sudden death of my battery. It was 6 years old and the doctor said that any attempt to keep her alive would unnecessarily prolong the pain, so I opted for a lethal injection. I saved the frame, which contains a BMS for future use, and bought a generic 3.7V 2500mAh li-po battery. I couldn't judge if it was the best choice, but it works and, being very light, it made my Takee much lighter. I am attaching a photo, the battery specifications are readable from the photo itself. As you can see, the SIM is missing. Lost telephone calling a long time ago. If anybody wants to share a NVRAM backup, it will be much appreciated, my IMEI is still readable under the battery.
[Android Software Development] io2345:
Battery looks perfect. Just don't understand why you soldered it to the phone's contacts, if you saved the frame of the old battery...

For a fresh battery it's probably a good choice. We tried it already with an older Zopo-Model "BT55t", which is a little larger but can be cut to fit, as the frame is LD-plastic. Advantage is, that the contacts-field of this model is identical to the Takee-battery.
[Android Software Development] zdomjus:
The frame is too thin to allow the usage of a soldering iron. Since the li-po battery has got its own BMS, i think it's safe enough to solder it to contacts directly. The model I bought fits well and firmly (4mm thickness, 60mm width). I'm going to measure the discharge time and estimate the capacity and time to recharge. It can be more than a temporary solution.
[Android Software Development] Mik-el:
Wow! The Takee 1 community continues to evolve, at this point we all are hardware hackers too :D

Yeah on telegram I also posted a photo of the batteries that @io2345 and I adapted for the phone. I also have photos showing the process, but I haven't posted them yet, if anyone is interested just let me know, so I'll upload them, adapting is quick and easy.
[Android Software Development] Mik-el:
ROM 2.0.1 - Updated Download (20 april 2021)​

Hey, if you have already downloaded the last 2.0.1 ROM, maybe you should download something again!

The 2 optional installers I made for the ROM ( SuperSU and Google apps) seem not working for me, but...

-DISCLAIMER-

you should consider that a few days ago, before flashing my ROM, I reflashed the stock September 2015 ROM for development reasons and unfortunately I get a partition problem (that could be causing other bugs ton my configuration too).

So maybe the SuperSU and GApps installations could be successful for you!

You should test the installers and let me know.

I didn't make a new release for the ROM cause I just fixed some things.

-UPDATES-

1) Everything is

clear

in the Download Section of this thread. (2nd post as always)

2) Now the download is a

Download folder

! You can choose which files to download!

3) SuperSU installation

Updated

to v2.46! And Installation from recovery works every time.

4) If you want SuperSU instead of Magisk: use the correct boot.img, explained in the 2nd post

4) for Gapps installation, I still face problems. Personally I don't use Gapps, but If you need a fixed installer without bugs, I can work on it and put it in the new Download Folder, so you can download it without re-downloading the ROM and so on.

Meanwhile, I'm reverse engineeringing EStar apks to port 3D.

Enjoy!
[Android Software Development] io2345:
That's right Mikel, SuperSU installer doesn't work. No big problem, as Magisk is the better choice anyway. The boot.img in your installer already contains modifications necessary for Magisk, so the one and only thing you have to do is installing the magisk-apk from within running system and you're done.

GApps installation: Wouldn't be bad to fix this installer. For experienced users it may not be a problem to extract the gapps.zip from the installer-zip. For others this might be already a task too high.
[Android Software Development] Mik-el:
Hi @zdomjus sorry but I forgot about your IMEI question, here I am. If I'm not wrong the easiest way to recreate the IMEI is by using the MobileUncleTools app that requires root. (You should find the link for the apk in the TWRP posts of this thread too).

I lost IMEI on one of my Takee but I haven't recreated it yet. There are several guides on the internet, let us know if you succeed!
[Android Software Development] zdomjus:
Hi @Mik-el thank you for your help. I'll give your suggestion a try.
[Moto G7 Play Guides, News, & Discussion] fossyfosser:
Success verbatim for the stock image on XT1952-6 (United states, Metro PCS carrier) purchased at a store a week ago.

CHANNEL_RETAIL_9.0_PPYS29.105-134-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml

Only hiccup was

fastboot flash boot boot.img

Sending 'boot_a' (32768 KB) OKAY [ 0.887s]

Writing 'boot_a' (bootloader) Image signed with key bad key

But that's expected as motorola doesn't sign any official images :/

This did not unlock my SIM, but it does give me the boot.img I'll need to patch with magisk in order to have a recovery based root... not ideal, but it'll do.

Update:

The G7 Play has no "Recovery" partition. Recovery mode is just an argument to the boot.img and some signature checks disabled. So flash your patched image to the boot partition.

Update 2:

Don't flash retail images, specially the modem, to the Metro Phone!!! you may experience temporary LTE bans
[Moto G7 Play Guides, News, & Discussion] xtermmin:
I have a XT1952-T, got it both bootloader and SIM unlocked, and flashed the RETUS XT1952-4 firmware on it about a month ago. No more carrier bloatware.
[Moto G7 Play Guides, News, & Discussion] JohnSmith8786:
XT1952-4 is meant for Sprint, so that could be the issue. Flash XT1952-3 instead.[/QUOTE]

Can you post a link to that file? The only XT1952-3 I seem to find are for vzw :confused:
[Moto G7 Play Guides, News, & Discussion] xtermmin:
Can you post a link to that file? The only XT1952-3 I seem to find are for vzw :confused:[/QUOTE]

Go to the firmware link in the OP: https://mirrors.lolinet.com/firmware/moto/channel/official/

Scroll down and click on RETUS (Retail US)

EDIT: Whoooops, I said XT1952-3 earlier, I meant the RETUS version of XT1952-4! Moto makes this so confusing... What I linked to above is the unlocked model's firmware.
[Moto G7 Play Guides, News, & Discussion] JohnSmith8786:
[/QUOTE] EDIT: Whoooops, I said XT1952-3 earlier, I meant the RETUS version of XT1952-4! Moto makes this so confusing... What I linked to above is the unlocked model's firmware.[/QUOTE]

I flashed it anyway against my better judgement lol (over the lastest unlocked RETUS version) lost my (the wife's) IMEI when I flashed back to the RETUS not entirely sure why. Had a heck of a time trying to register the Sim card, flashing back to stock TMO firmware didn't work either. I even fastboot flashed by cmd line with no luck. Flashed the VZW firmware and I had signal.... So I flashed the lastest RETUS and the modem files from the VZW firmware and I'm fine (This is strange to me because it's a TMO revvlry not a VZW branded phone) The question I'm indirectly asking is why did I lose my IMEI? I stayed on PIE... Also curious to know if anyone has had this happen before and how they fixed if they did.
[Moto G7 Play Guides, News, & Discussion] muhahsan2004:
Moto G7 play Stock image required

I have a XT1952-2, purchased from local supplier. I need to know which stock image is form my G7 play.

Build number: channel-userdebug 9 PPY29.68-23 2de9intcfg.test-keys
[Moto G7 Play Guides, News, & Discussion] JohnSmith8786:
Can you elaborate on "temporary LTE bans"
[Moto G7 Play Guides, News, & Discussion] thetojo:
Did you find out what he meant by the LTE bans?
[Moto G7 Play Guides, News, & Discussion] JohnSmith8786:
No, never did...
[Moto G7 Play Guides, News, & Discussion] thetojo:
Well twas worth a shot thanks
[Moto G7 Play Guides, News, & Discussion] Spaceminer:
What he really meant to say is loss of LTE. Different carriers use different radio bands for service, so if you flash the wrong modem you'll have signal problems.
[Moto G7 Play Guides, News, & Discussion] ggg777:
Hello everyone,

I tried flashing stock, but get some problems.

Device:

XT1952-1

RETEU

I have downloaded this stock:

XT1952-1_CHANNEL_RETEU_9.0_PPYS29.105-134-7_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

Spaceminer told me, that before TWRP etc. I have to look that A and B are not empty so I tried flashing stock to get it safe (am I right that flashing stock would both partitions flash?)

PC-System:

Linux debian

Problem:

$ fastboot flash modem NON-HLOS.bin

target reported max download size of 536870912 bytes

sending 'modema' (65280 KB)...

OKAY [ 2.669s]

writing 'modema'...

(bootloader) Invalid partition name modema

FAILED (remote failure)

finished. total time: 2.670s

--------

$ fastboot flash fsg fsg.mbn

target reported max download size of 536870912 bytes

sending 'fsga' (11120 KB)...

OKAY [ 0.456s]

writing 'fsga'...

(bootloader) Invalid partition name fsga

FAILED (remote failure)

finished. total time: 0.457s

--------

There is always a "a" at the filenames.

modem -> modema

fsg -> fsga

How should I handle this?

Thanks for your help :)
[Moto G7 Play Guides, News, & Discussion] Spaceminer:
[MENTION=10625799]ggg777[/MENTION]

Use the latest fastboot from the Android sdk or use the latest fastboot portable from xda. If you already are, then try specifying the slot with boot_a or boot_b.
[Moto G7 Play Guides, News, & Discussion] ggg777:
Thanks, I will try that
[Moto G7 Play Guides, News, & Discussion] hassanmuj:
Hi. I tried flashing a couple of different versions of XT 1952-2 (such as RETAIL, RETBR) on my phone but everytime i try to run my phone the accelerator sensor seems to be inverted.

I've searched all over and most of the forums say that it happens probably because the proper version of the stock rom wasn't flashed.

The first time I got this phone it had loads of probably developer-esque apps such as battery tracer, bugs2go (if that's what it's called), etc.

Another interesting thing is that my bootloader is in engineering mode and i suspect that might be the reason my accelerator seems to be inverted.

I also tried to root my phone hoping i could modify some related files but everytime i flashed magisk, it doesn't root the phone.

Here's the bootloader if that explains something....

AP Fastboot Flash Mode (Not Secure)

BL:MBM-2.1-channel_retail-6bae60c-190618

Baseband: M632_17.61.01.99p CHANNEL_LATAMDSDS_CUST

Product/Variant: channel XT1952-2 32GB DVT1A

I've been super frustrated with this and any response would be more than appreciated. Thanks.
[Moto G7 Play Guides, News, & Discussion] ForForkSake:
When you say you magisk...have you tried to reboot to recovery mode from bootloader screen?..

My device...

Baseband Version: M632_26.100.01.120.01R CHANNEL_SUPER_CUST
Kernel Version: 4.9.112-perf+ hudsoncm@ilclbld162 #1 32-bit
Java Virtual Machine: ART 2.1.0
Android Version: 9
Build Number: PPYS29.105-134-9 (cd8e0)
Build Fingerprint: motorola/channel_reteu/channel:9/PPYS29.105-134-9/cd8e0:user/release-keys
Build Description: channel_reteu-user 9 PPYS29.105-134-9 cd8e0 release-keys
Build Date: Mon Feb 10 12:39:21 CST 2020

Just patched mine

A useful trick when updating magisk version.... Patch the stock boot img in magisk manager, use the Flasher within ex kernel manager app to flash new boot img.... Reboot recovery... Saves all the fastboot stuff you do first time round
[Moto G7 Play Guides, News, & Discussion] Spaceminer:
If anyone gets ahold of the Android 10 soak test let me know because I want it. I got approved for it, but I'm unable to download it. The last ota "160-4" will break your ability to grab it. Stay on 160. The official build releases in 30 days if everything goes well.
[Moto G7 Play Guides, News, & Discussion] POOH TOTO:
I turn on the phone, the start is in the RECOVERY MODE not ANDROID

Hi, how are you doing?

I have a moto g7 play bought in the USA, which I wanted to test if I could release the antenna lock to use it in my country by installing the local fireware .... it did not work, keep asking for unlock PIN.

Originally I had the factory version XT1952-6 (United states, Metro PCS carrier), I installed the version XT1952-2 (ARGENTINA) ... as I continued to reject the SIM I opted to return to the original version that the cell phone had (the XT1952-6)

Now, my problem is that every time I turn on the phone, the start is in the RECOVERY MODE, not ANDROID.

How do I get ANDROID to start directly and not in RECOVERY MODE? :confused:

Excuse me, my English is very bad. Thanks in advance.
[Moto G7 Play Guides, News, & Discussion] Spaceminer:
You probably left it in OEM mode. Try holding Vol ↓ + Power until you get into fastboot. Then run the command...

fastboot oem fb_mode_clear
fastboot erase DDR
fastboot reboot
[Moto G7 Play Guides, News, & Discussion] QueenLizzy:
I have Germany G7 play, still 9 on it no update ota. Yet when it come? April 1 2020 last update.
[Moto G7 Play Guides, News, & Discussion] Viva La Android R.I.P.:
The Android 10 OTA has began rolling out to device owners in Brazil and some Retail variant owners in the US. Motorola Mobility has not listed an official schedule on when the update will be rolling out to its other regional Moto G7 Play variants.
[Moto G7 Play Guides, News, & Discussion] mickem:
Any updates for the XT1952-6? Can it be able to update to android 10 or to get root access?
[Moto G7 Play Guides, News, & Discussion] Spaceminer:
If you can unlock your bootloader, then the answer is a solid yes.
[Moto G7 Play Guides, News, & Discussion] mickem:
I already unlocked the bootloader and boot twrp vía fastboot, so i tried to Flash twrp permanently installing recovery ramdisk, all appears like did it succesfully but when reboot, twrp stay in bootloop, also, Magisk 20.4.zip flashed ok but system don't show any channges in magisk manager and root checker. Any recommendation?
[Moto G7 Play Guides, News, & Discussion] QueenLizzy:
Ok thanks Ill just wait i guess for OTA!!
[Moto G7 Play Guides, News, & Discussion] elBass:
Phone boots with the old firmware after "successfully" flashing a new one

Hello !

My Moto g7 play is running android 10 with the XT1952-2 (RETLA) channel. According to my carrier in Canada, I need the XT1952-4 channel to enable wifi calling.

I tried a few options (that just did not ran through) before getting to this post, so my bootloader is unlocked, but not rooted (I never successfully flashed twrp and other options failed as well).

Now I flashed the latest (android 10) RETCA firmware found on the link from this post. All commands ran smoothly, but the phone somehow reboots with the same old RETLA firmware... Any idea why? and how I could actually boot with the newly flashed firmware?

Note: Runnning ./fastboot getvar all, I remember something weird with slot B, being locked or not properly accessed or something.

Thanks a lot!
[Moto G7 Play Guides, News, & Discussion] muhahsan2004:
Dear @ hassanmuj

Have you resolved accelerator sensor inverted problem?
[Moto G7 Play Guides, News, & Discussion] QueenLizzy:
I noticed on the Germany website says moto g 7 play

The introduction of Android ™ 10 began on June 18, 2020.

Should i have it by now in OTA??? if so.. anywhere i can download the firmware?......PPYS29. 105-134-12
[Moto G7 Play Guides, News, & Discussion] thommy181:
I have Android 9 build from April 2020 in Moto G7 Play XT1952-1. I can't to update to Android 10. I try many images from Retail folder and Reteu too. After update process I have loop boot to fastboot mode. I can't flash my smartphone correctly. When I want use this I must back to Android 9. Usally retail builds are good for me. I don't know what's wrong ? Some links are expired in forum so I use repository mirrors. I Can't find there correctly install image for me. I have the Motorola Moto G7 Play from Poland EU.
[Moto G7 Play Guides, News, & Discussion] Spaceminer:
If you've tried RETEU builds and they don't work then you probably need RETEU_RS, which is used for Russia and Germany iirc. Try this out. If it goes into fastboot with a "could not boot" kind of warning and gives you the option to format data, then you need to format data. I went through this on RETUS, so I'm just throwing that out there as an FYI.

https://mirrors.lolinet.com/firmwar...EFAULT_regulatory-XT1952-1-NON-EU_CFC.xml.zip
[Moto G7 Play Guides, News, & Discussion] HiPlzHelp:
hello so i have the XT1952-4 from boost mobile which i recently sim unlocked i wanted to get android 10 on it so since its sim unlocked and i dont even have boost mobile with it anymore can i use the firmware from the us unlocked variant/retail us version
[Moto G7 Play Guides, News, & Discussion] JohnSmith8786:
You should be fine
[Moto G7 Play Guides, News, & Discussion] HiPlzHelp:
hello so i did all the files on my device and i did the step by step and i accidentally flashed system_b file to system_a i did all the other files correctly this is what i did ( C:\Users\jaden\Downloads\platform-tools_r30.0.4-windows\platform-tools>fastboot flash system C:\Users\jaden\Downloads\moto\system_b.img_sparsechunk.0

(bootloader) is-logical:system_a: not found

Sending 'system_a' (257876 KB) OKAY [ 5.924s]

Writing 'system_a' OKAY [ 4.844s]

Finished. Total time: 10.805s

now my device just says N/A when i turn it on is there a way i can restart the process or fix it
[Moto G7 Play Guides, News, & Discussion] JohnSmith8786:
RSD lite
[Moto G7 Play Guides, News, & Discussion] HiPlzHelp:
EDIT: Whoooops, I said XT1952-3 earlier, I meant the RETUS version of XT1952-4! Moto makes this so confusing... What I linked to above is the unlocked model's firmware.[/QUOTE]

I flashed it anyway against my better judgement lol (over the lastest unlocked RETUS version) lost my (the wife's) IMEI when I flashed back to the RETUS not entirely sure why. Had a heck of a time trying to register the Sim card, flashing back to stock TMO firmware didn't work either. I even fastboot flashed by cmd line with no luck. Flashed the VZW firmware and I had signal.... So I flashed the lastest RETUS and the modem files from the VZW firmware and I'm fine (This is strange to me because it's a TMO revvlry not a VZW branded phone) The question I'm indirectly asking is why did I lose my IMEI? I stayed on PIE... Also curious to know if anyone has had this happen before and how they fixed if they did.[/QUOTE]

what is rsdlite??

---------- Post added at 11:32 PM ---------- Previous post was at 11:31 PM ----------

i got the device on and working but when i go into settings it says software channel after flashing retus firmware?? is there a way to change that