Hi,
I have Lenovo Vibe K5 Note (A7020A48).
Android Version - 6
Android Security Patch Level - 5th October 2016
Baseband Version - K.52.ROW.M.LWG.V46, 2016/11/25 09:19
Kernel Version - 3.18.22+, [email protected]#1
Build Number - A7020A48_S318_161128_ROW.
My phone was not working properly, it used to hang every now and then, so I decided to flash the ROM using,
Lenovo_A7020a48_S318_MT6755_20161128 firmware and SP_Flash_Tool_v5.1824_Win.
I followed the procedure as shown in the youtube video. However, as soon as the flash process starts I get the following error
ERROR : STATUS_SEC_INSUFFICIENT_BUFFER (0xC002004B)
[HINT]: Verified boot is Enabled. Please download signed image (md1img-verified.img) or disable verified boot.
Now My phone does not start at all (Hard Brick)
Is there any work around to solve the problem. Am I missing anything?
Regards,
Thanks in advance, Any Help is appreciated.
piyushdiyora said:
Hi,
I have Lenovo Vibe K5 Note (A7020A48).
Android Version - 6
Android Security Patch Level - 5th October 2016
Baseband Version - K.52.ROW.M.LWG.V46, 2016/11/25 09:19
Kernel Version - 3.18.22+, [email protected]#1
Build Number - A7020A48_S318_161128_ROW.
My phone was not working properly, it used to hang every now and then, so I decided to flash the ROM using,
Lenovo_A7020a48_S318_MT6755_20161128 firmware and SP_Flash_Tool_v5.1824_Win.
I followed the procedure as shown in the youtube video. However, as soon as the flash process starts I get the following error
ERROR : STATUS_SEC_INSUFFICIENT_BUFFER (0xC002004B)
[HINT]: Verified boot is Enabled. Please download signed image (md1img-verified.img) or disable verified boot.
Now My phone does not start at all (Hard Brick)
Is there any work around to solve the problem. Am I missing anything?
Regards,
Thanks in advance, Any Help is appreciated.
Click to expand...
Click to collapse
We have the same problem,, hahaha
piyushdiyora said:
Hi,
I have Lenovo Vibe K5 Note (A7020A48).
Android Version - 6
Android Security Patch Level - 5th October 2016
Baseband Version - K.52.ROW.M.LWG.V46, 2016/11/25 09:19
Kernel Version - 3.18.22+, [email protected]#1
Build Number - A7020A48_S318_161128_ROW.
My phone was not working properly, it used to hang every now and then, so I decided to flash the ROM using,
Lenovo_A7020a48_S318_MT6755_20161128 firmware and SP_Flash_Tool_v5.1824_Win.
I followed the procedure as shown in the youtube video. However, as soon as the flash process starts I get the following error
ERROR : STATUS_SEC_INSUFFICIENT_BUFFER (0xC002004B)
[HINT]: Verified boot is Enabled. Please download signed image (md1img-verified.img) or disable verified boot.
Now My phone does not start at all (Hard Brick)
Is there any work around to solve the problem. Am I missing anything?
Regards,
Thanks in advance, Any Help is appreciated.
Click to expand...
Click to collapse
Please post in the right section/forum of XDA. Here we talk only about Vibe K5 and K5 Plus. Thanks.
Sent from my Lenovo K5 Plus using XDA Labs
Related
Dear all,
I 've been always receiving updates whenever i was loading official 6.0.1 til to 7.0 which was the latest for my channel . I was on Lineage 7.1.2 for a couple of days and reverted back to 6.0.1 when I was informed that 7.1.1 came available on our channel ( reteu).
The problem this time is that I get " your device's software is up to date" when I am trying to update the sw.
Any help would be highly appreciated .
Model Number: Moto z play
Software Channel : reteu
Android Version : 6.0.1.
Android Security Patch Level: November 1, 2016
Baseband Version : M8953_10208.08.04.48R ADDISON_ROWDSDS_CUST
Build Number : MPNS24.104-49-4
Update : O flashed the stock 7.0 nougat file found here: https://forum.xda-developers.com/moto-z-play/how-to/moto-z-play-reteu-firmware-otas-t3557917.
Everything went all right and the phone booted normally. I got an update notification and let the system to boot so as to apply the update. After that the phone never booted and seems to be bricked!!!
YOU HELP ITS MUCH APPRECIATED!!!!
Now you have paperweight. Sad, but true.
No solution for unbrick yet.
Mike
sp5it said:
Now you have paperweight. Sad, but true.
No solution for unbrick yet.
Mike
Click to expand...
Click to collapse
Really?
No solution to unbrick the device??!
Yash24 said:
Really?
No solution to unbrick the device??!
Click to expand...
Click to collapse
You can try these methods:
http://www.aryk.tech/2017/07/moto-z-play-unbrick-solutions.html
The blank-flash was unsuccessful to all users. The Loader.img is being tested by some guys. (folks at ArykTECH managed to build a Loader.img that is supposed to work, unlike the ones we extract from our phones, as described by the "DIY" section)
Edit: please, post your feedback here:
https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492
It happened to me too. I had 4 variable rom choices for RETASIA. Only one of them was responsible to get my updates back. I had to try them all
Hello!
(First of all I'm not sure whether it's more device or ROM related so please move it if needed - I'm Lineage user so I post it here).
I'm using Lineage 15.1 for over a year now and I wanted to upgrade to 16.
Samsung Galaxy Note 3.
After upgrading to v16 I have "no baseband/sim/IMEI" issue.
Baseband version that works currently on Lineage 15.1 is N9005XXUGPQB1
I guess the same baseband will work on Lineage 16 (will it?) but unfortunately I don't have that installation file anymore.
So:
Does anyone have N9005XXUGPQB1 baseband available for download
OR is it possible to somehow "extract and reuse" it from my current 15.1 installation?
Thanks in advance!
Mikuda said:
Hello!
(First of all I'm not sure whether it's more device or ROM related so please move it if needed - I'm Lineage user so I post it here).
I'm using Lineage 15.1 for over a year now and I wanted to upgrade to 16.
Samsung Galaxy Note 3.
After upgrading to v16 I have "no baseband/sim/IMEI" issue.
Baseband version that works currently on Lineage 15.1 is N9005XXUGPQB1
I guess the same baseband will work on Lineage 16 (will it?) but unfortunately I don't have that installation file anymore.
So:
Does anyone have N9005XXUGPQB1 baseband available for download
OR is it possible to somehow "extract and reuse" it from my current 15.1 installation?
Thanks in advance!
Click to expand...
Click to collapse
Baseband does not get deleted when upgrading android version. Best idea is to ask in your debice/rom specific thread
Deleted or not - it's not there after upgrade.
You mean here: https://forum.xda-developers.com/galaxy-note-3/development/rom-lineageos-16-0-t3840244 ?
Deleted or not - it's not there after upgrade.
You mean here: https://forum.xda-developers.com/galaxy-note-3/development/rom-lineageos-16-0-t3840244 ?
Baseband
I have the same problem but with my moto G7 (river) I only have baseband with lineage os 16 but after upgrade to 17 I lose the baseband any solution?
Hello everyone,
I'm getting really frustrated hree as I can't flash any android 10 GSI. I either get bootloop, stuck on samsung logo or stuck on restarting on samsung logo.
Flashing different kernels seem to change the above behavior (instead of bootloop I get samsung logo and vice-versa).
I tried everything:
Doing the no-verity thingie...
Flashing stock files then GSI - nothing.
Flashing soldiers oreo kernel - nothing
Flashing endurance kernel - nothing
I can't find a vendor image that's compatible with any GSI on my phone. I also can't find any kernel that's compatible either.
So please, end my misery... if anyone managed to install android 10 GSI on this TREBLE COMPATIBLE DEVICE, please guide me through or provide any useful file (vendor img/kernel) that I might have been missed.
I wrote this because I couldn't find anything that could help... Thanks in advance!
EDIT:
I solved the problem with the kind help from phhusson and the guidance from Lanreallenjay (thanks, both of you!), so I'm trying to provide the solution for anyone that might be having the same problem as I had. So here it is:
For PIE GSI: use stock kernel/vendor (anything stock), flash the GSI, then flash Magisk -> it should boot fine now (only tested with phhusson's GSI. I had vibrating restart loops before, I wasn't installing magisk, that was my mistake)
For Android 10 GSI: same as above, but install the modded Magisk from phhusson's git (located @ v200 android 10 gsi post) instead of the normal one .
itShouldWork said:
Hello everyone,
I'm getting really frustrated hree as I can't flash any android 10 GSI. I either get bootloop, stuck on samsung logo or stuck on restarting on samsung logo.
Flashing different kernels seem to change the above behavior (instead of bootloop I get samsung logo and vice-versa).
I tried everything:
Doing the no-verity thingie...
Flashing stock files then GSI - nothing.
Flashing soldiers oreo kernel - nothing
Flashing endurance kernel - nothing
I can't find a vendor image that's compatible with any GSI on my phone. I also can't find any kernel that's compatible either.
So please, end my misery... if anyone managed to install android 10 GSI on this TREBLE COMPATIBLE DEVICE, please guide me through or provide any useful file (vendor img/kernel) that I might have been missed.
I wrote this because I couldn't find anything that could help... Thanks in advance!
Click to expand...
Click to collapse
What's your phone's specifications?
Lanreallenjay said:
What's your phone's specifications?
Click to expand...
Click to collapse
Hey, thanks for the interest!
I've got the S9 Exynos variant (SM-G960F, Europe), I unlocked the bootloader several days ago.
It's on android 9 right now, I flashed the stock firmware after I've tried everything to get android 10 treble to work and failed.
Current kernel version: 4.9.59-16947752 (stock)
Build number: PPR1.180610.011.G960FXXS7CSJ3
I can flash any rom available besides GSI (I've used lineage OS 16 for a couple of days).
If you need anything else more specific just ask, I don't really know what exactly can help with this situation.
Cheers!
itShouldWork said:
Hey, thanks for the interest!
I've got the S9 Exynos variant (SM-G960F, Europe), I unlocked the bootloader several days ago.
It's on android 9 right now, I flashed the stock firmware after I've tried everything to get android 10 treble to work and failed.
Current kernel version: 4.9.59-16947752 (stock)
Build number: PPR1.180610.011.G960FXXS7CSJ3
I can flash any rom available besides GSI (I've used lineage OS 16 for a couple of days).
If you need anything else more specific just ask, I don't really know what exactly can help with this situation.
Cheers!
Click to expand...
Click to collapse
Ask for help here
https://t.me/phhtreble/283195 <---
Read before any question ^^^
After flashing G960FXXS7CSJ3 November stock firmware I can no longer flash anything.
(can't mount data partition)
When I try downgrading to G960FXXU5CSF2 June firmware Odin fails and the screen says:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 7 BINARY: 5
November G960FXXS7CSJ3 seems to have upgraded the bootloader security, does anyone know a fix?
itShouldWork said:
Hello everyone,
I'm getting really frustrated hree as I can't flash any android 10 GSI. I either get bootloop, stuck on samsung logo or stuck on restarting on samsung logo.
Flashing different kernels seem to change the above behavior (instead of bootloop I get samsung logo and vice-versa).
I tried everything:
Doing the no-verity thingie...
Flashing stock files then GSI - nothing.
Flashing soldiers oreo kernel - nothing
Flashing endurance kernel - nothing
I can't find a vendor image that's compatible with any GSI on my phone. I also can't find any kernel that's compatible either.
So please, end my misery... if anyone managed to install android 10 GSI on this TREBLE COMPATIBLE DEVICE, please guide me through or provide any useful file (vendor img/kernel) that I might have been missed.
I wrote this because I couldn't find anything that could help... Thanks in advance!
EDIT:
I solved the problem with the kind help from phhusson and the guidance from Lanreallenjay (thanks, both of you!), so I'm trying to provide the solution for anyone that might be having the same problem as I had. So here it is:
For PIE GSI: use stock kernel/vendor (anything stock), flash the GSI, then flash Magisk -> it should boot fine now (only tested with phhusson's GSI. I had vibrating restart loops before, I wasn't installing magisk, that was my mistake)
For Android 10 GSI: same as above, but install the modded Magisk from phhusson's git (located @ v200 android 10 gsi post) instead of the normal one .
Click to expand...
Click to collapse
So from stock you flashed AOSP 10 GSI to system partition then phh's magisk (in TWRP) then it works for you?
rupert3k said:
So from stock you flashed AOSP 10 GSI to system partition then phh's magisk (in TWRP) then it works for you?
Click to expand...
Click to collapse
Yep, it does. Buuut the rom is not stable at all, I've got random reboots/ crashes when opening settings and such, not usable at all. I'm on ONE UI 2.0 beta now which is much more stable (daily driver stable actually).
rupert3k said:
After flashing G960FXXS7CSJ3 November stock firmware I can no longer flash anything.
(can't mount data partition)
When I try downgrading to G960FXXU5CSF2 June firmware Odin fails and the screen says:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 7 BINARY: 5
November G960FXXS7CSJ3 seems to have upgraded the bootloader security, does anyone know a fix?
Click to expand...
Click to collapse
Have you tried formatting data with TWRP (to the part when it asks you to write "yes") then flash no-verity?
You should at least be able to flash TWRP. If you can't, just download the proper USB drivers for your device, it might be the culprit.
Cheers!
itShouldWork said:
Yep, it does. Buuut the rom is not stable at all, I've got random reboots/ crashes when opening settings and such, not usable at all. I'm on ONE UI 2.0 beta now which is much more stable (daily driver stable actually).
Click to expand...
Click to collapse
Phh just hinted it's likely Pie vendor causing panics:
"First you need to flash stock rom. Then install magisk and then this gsi.
Though please note that on Pie vendor, S9 kernel panics and reboot every few minutes, so it is highly unusable."
itShouldWork said:
Hey, thanks for the interest!
I've got the S9 Exynos variant (SM-G960F, Europe), I unlocked the bootloader several days ago.
It's on android 9 right now, I flashed the stock firmware after I've tried everything to get android 10 treble to work and failed.
Current kernel version: 4.9.59-16947752 (stock)
Build number: PPR1.180610.011.G960FXXS7CSJ3
I can flash any rom available besides GSI (I've used lineage OS 16 for a couple of days).
If you need anything else more specific just ask, I don't really know what exactly can help with this situation.
Cheers!
Click to expand...
Click to collapse
I have tried Android 10 GSI , using latest Q update
ZoiraP said:
I have tried Android 10 GSI , using latest Q update
Click to expand...
Click to collapse
Is it usable? any random reboots/ annoying instability?
itShouldWork said:
Is it usable? any random reboots/ annoying instability?
Click to expand...
Click to collapse
I have tried it partly , nfc isnt working , camera quality is bad , Bluetooth working , audio working , magisk working . I'll use it a bit more and tell you.
ZoiraP said:
I have tried it partly , nfc isnt working , camera quality is bad , Bluetooth working , audio working , magisk working . I'll use it a bit more and tell you.
Click to expand...
Click to collapse
Camera quality might be fixed with Google cam, if you find a good port.
Not to derail the thread but I just noticed after installing Android 10 beta 2 Treble Info now reports my S9 supports Treble A/B, curious no?
rupert3k said:
Not to derail the thread but I just noticed after installing Android 10 beta 2 Treble Info now reports my S9 supports Treble A/B, curious no?
Click to expand...
Click to collapse
Wait what? That's interesting...
Can someone with more experience enlighten us about the differences between the A only and A/B?
A\B
itShouldWork said:
Wait what? That's interesting...
Can someone with more experience enlighten us about the differences between the A only and A/B?
Click to expand...
Click to collapse
No real experience but A\B devices have two slots ie double the partitions (OnePlus has 67) .
This allows updates to be installed while running from slot A while the updated system is copied to B.
Apparently Q requires A\B so now we're on Q may as well try that next time we're curious
Phh just released:
AOSP 10.0 v208
Fix suspend/dt2w for Samsung Q vendor
Fix backlight for Samsung Q vendor
Samsung Q's fine, love gestures but the bloat is killing me.
You can tell Q's going to be so much leaner without bixby & friends.
Glad we installed it to get compatible but I think now we probably stand a better chance with 10 GSI's, hopefully LOS17 & Pixel Experience get updated again soon.
Wondering whether to following the rooting instructions yet?
Phh did say "flash stock rom then magisk and then gsi"
https://forum.xda-developers.com/galaxy-s9/how-to/one-ui-2-beta-rooting-installing-twrp-t4012961
ZoiraP's wondering why we sooo slow lol!
Wow this looks good: https://forum.xda-developers.com/ga...-s9--s9-cross-device-development/rom-t4020939
hi ppl...
i am on stock 7.1.1 with unlocked bootloader.
can i update straight to custom pie, if so how ?
thanks in advance.
ps: i tried flashing a pie vendor image, getting tons of errors.
need a little help here...
tried installing omni rom.
flashing in slot a works fine, when switching to slot b i get error:
failed to mount /bt_firmware
failed to mount /firmware
You need to update the device firmware if your bootloader Is unlocked
You can search for the firmware and the tool yo flash It
Send me a pm
where can i find this firmware?
weird thing is, i found a way to get omni to run, even with those error in twrp.
paparansen said:
where can i find this firmware?
weird thing is, i found a way to get omni to run, even with those error in twrp.
Click to expand...
Click to collapse
You can find the firmware AND the tool here, justo look for tour model and variant.
If you are stuck ok 7.1.1 you have the chinese variant (00CN) same as i do (i've tried the same)
https://fih-firmware.hikaricalyx.com/hmd_en.html
This page Is from a senior member here on xda, however search your model and variant firmware, if you flash a firmware for other variant YOU WILL KILL YOUR DEVICE
Good luck me if you need further help send me a PM
ah ok... by firmware you mean stock rom ^^
i allready tried to flash the android 8 & 9 from that page
for ta-1054 - ost get stuck at "checking device status".
i was only able to flash the android 7 from that page.
paparansen said:
ah ok... by firmware you mean stock rom ^^
i allready tried to flash the android 8 & 9 from that page
for ta-1054 - ost get stuck at "checking device status".
i was only able to flash the android 7 from that page.
Click to expand...
Click to collapse
Wich variant do you have?
And what firmware are you tring?
like i wrote above: ta-1054 & android 8 & 9
paparansen said:
like i wrote above: ta-1054 & android 8 & 9
Click to expand...
Click to collapse
But is Android one variant? Check on settings where Is device info
In hardware should say somenthing like 00CN or 00WW
there is no android one variant on that page.
i got the china version of ta-1054
paparansen said:
there is no android one variant on that page.
i got the china version of ta-1054
Click to expand...
Click to collapse
Then download the firmware marked as PL2-347C-0-00CN-B04
On the bottom of the page there Is a tool called Generic flashing script (or somenthing like that)
Once you have downloaded both files uncompress the firmware un any folder and copy the tool on the same folder
Click on the tool icon and follow the instructions
Nokia Online Service Tools (Insufficient_Permissions).
I cant do Firmware Upgrade with Nokia Online Service Tools ver. 6.2.8.
Its shows me this Error Message:
(Insufficient_Permissions).
What should i do?
Is there any custom rom for the moto g7 play that is stable?
Chapie1 said:
Is there any custom rom for the moto g7 play that is stable?
Click to expand...
Click to collapse
What is the most current firmware? I can try to build one as long as you have twrp and root
Sent from my moto g(6) play using Tapatalk
Sands207 said:
What is the most current firmware? I can try to build one as long as you have twrp and root
Sent from my moto g(6) play using Tapatalk
Click to expand...
Click to collapse
there they are I use the xt1952-2 version
https://mirrors.lolinet.com/firmware/moto/channel/official/
Chapie1 said:
there they are I use the xt1952-2 version
https://mirrors.lolinet.com/firmware/moto/channel/official/
Click to expand...
Click to collapse
Code:
GENERAL INFO
Manufacturer: motorola
Brand: motorola
Phone Model: moto g(7) play / moto g(7) play
Device Type: channel
Product Name: channel_reteu
Country of Origin:
Manufacturing Date:
Knox Warranty Void:
Colour:
Internal Storage:
CSC INFO
Product Code: pH
Original CSC Code:
Firmware's CSC Code:
Active CSC Code:
Available CSC Codes:
CSC Country:
CSC Country ISO:
Mobile Operator: Virgin / 23430 / 23438
FIRMWARE INFO
Bootloader Version: 0xC111
PDA Version:
CSC Version:
Baseband Version: M632_26.100.01.120.01R CHANNEL_SUPER_CUST
Latest Firmware: N/A
Firmware Status:
Kernel Version: 4.9.112-perf+ [email protected] #1 32-bit
Java Virtual Machine: ART 2.1.0
OS INFO
Root Existence: Yes
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
Changelist:
HARDWARE INFO
Hardware: qcom
Board: msm8953 [32-bit]
Platform: msm8953
Chip:
GPU: Qualcomm Adreno 506
Modem Board:
Hardware Revision:
Total RAM: 1.79 GB
Screen: 5.63 inches, 720 × 1512 pixels, 293 ppi, 240 dpi
Camera:
Rear: 13MP
Front: 8MP
Sound Card: msm8953_-tas2560
Loudspeaker:
WiFi Chip: Motorola Mobility LLC, a Lenovo Company
GPS Chip:
Battery: Li-ion 3000 mAh, Health: Good
USAGE HISTORY
Battery Health: 99.4 %
Last saved on: 08-Apr-2020 00:53:49
Thanks, I'll get to work on a rom today!
Sent from my moto g(6) play using Tapatalk
I used this one for my XT1952-4...
The build is for XT1952-2 (posted by αℓ૯×12345) but I went ahead and tried it. So far (couple days now) it is working pretty well. I've connected it to my WiFi and I've been surfing the internet. Also, Google Play Store works.
Hope this is helpful:
https://forum.xda-developers.com/g7-play/development/gsi-lineageos-17-1-modified-t4075035
I followed the directions in that thread; I already had the bootloader unlocked (obviously, right?) I also had TWRP installed using the method in this thread:
https://forum.xda-developers.com/g7-play/how-to/how-to-successfully-install-twrp-g7-play-t3979701
Read down the thread a little bit. In the directions, Linuxassassin leaves out what turned out to be an important step for me, which is after I fastbooted the TWRP image linked to in that thread, I needed to select Wipe from the TWRP menu and then Format Data. I needed to do that to remove the encryption from the file system so that it was usable for the rest of the steps for installing TWRP. As already stated, it is working pretty well at the moment.
Edit...
FortunateFennec said:
The build is for XT1952-2 (posted by αℓ૯×12345) but I went ahead and tried it. So far (couple days now) it is working pretty well. I've connected it to my WiFi and I've been surfing the internet. Also, Google Play Store works.
Hope this is helpful:
https://forum.xda-developers.com/g7-play/development/gsi-lineageos-17-1-modified-t4075035
I followed the directions in that thread; I already had the bootloader unlocked (obviously, right?) I also had TWRP installed using the method in this thread:
https://forum.xda-developers.com/g7-play/how-to/how-to-successfully-install-twrp-g7-play-t3979701
Read down the thread a little bit. In the directions, Linuxassassin leaves out what turned out to be an important step for me, which is after I fastbooted the TWRP image linked to in that thread, I needed to select Wipe from the TWRP menu and then Format Data. I needed to do that to remove the encryption from the file system so that it was usable for the rest of the steps for installing TWRP. As already stated, it is working pretty well at the moment.
Click to expand...
Click to collapse
Sorry folks. New here; don't know how to edit my posts ...Edit: Now there's an edit button... huh. OK.
Ran into a little problem if you are rebooting from TWRP when the above stuff has been done.
When rebooting from TWRP using the TWRP image in the above thread, and it gives you the options to "Prompt to install TWRP app if not installed" and "Install as system app" be sure NOT to install them. Press the button that says "Do Not Install." If you do install them, it causes the boot to hang up on the "android" screen. I fixed the problem by going back into TWRP, wiping the system partition, and reinstalling the custom ROM image.
Anyway, hope this helps someone.
CFKod said:
Code:
GENERAL INFO
Manufacturer: motorola
Brand: motorola
Phone Model: moto g(7) play / moto g(7) play
Device Type: channel
Product Name: channel_reteu
Country of Origin:
Manufacturing Date:
Knox Warranty Void:
Colour:
Internal Storage:
CSC INFO
Product Code: pH
Original CSC Code:
Firmware's CSC Code:
Active CSC Code:
Available CSC Codes:
CSC Country:
CSC Country ISO:
Mobile Operator: Virgin / 23430 / 23438
FIRMWARE INFO
Bootloader Version: 0xC111
PDA Version:
CSC Version:
Baseband Version: M632_26.100.01.120.01R CHANNEL_SUPER_CUST
Latest Firmware: N/A
Firmware Status:
Kernel Version: 4.9.112-perf+ [email protected] #1 32-bit
Java Virtual Machine: ART 2.1.0
OS INFO
Root Existence: Yes
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
Changelist:
HARDWARE INFO
Hardware: qcom
Board: msm8953 [32-bit]
Platform: msm8953
Chip:
GPU: Qualcomm Adreno 506
Modem Board:
Hardware Revision:
Total RAM: 1.79 GB
Screen: 5.63 inches, 720 × 1512 pixels, 293 ppi, 240 dpi
Camera:
Rear: 13MP
Front: 8MP
Sound Card: msm8953_-tas2560
Loudspeaker:
WiFi Chip: Motorola Mobility LLC, a Lenovo Company
GPS Chip:
Battery: Li-ion 3000 mAh, Health: Good
USAGE HISTORY
Battery Health: 99.4 %
Last saved on: 08-Apr-2020 00:53:49
Click to expand...
Click to collapse
I downloaded your firmware as well as the sprint and the retus variants. It will take me a day or two to complete. are you willing to test?
Sent from my moto g(6) play using Tapatalk
Sands207 said:
I downloaded your firmware as well as the sprint and the retus variants. It will take me a day or two to complete. are you willing to test?
Sent from my moto g(6) play using Tapatalk
Click to expand...
Click to collapse
What ROM are you porting? Id be willing to test on my RETGB (XT1952-1 iirc) as the firmware is quite similar between devices.
00p513 said:
What ROM are you porting? Id be willing to test on my RETGB (XT1952-1 iirc) as the firmware is quite similar between devices.
Click to expand...
Click to collapse
It will be custom stock. I will grab your firmware as well. my upload is slow but it's now Wednesday, tonight I'll finish them and upload them. Are you able to flash zips with your recovery as of now? Any requests or suggestions on root?
Sent from my moto g(6) play using Tapatalk
Sands207 said:
It will be custom stock. I will grab your firmware as well. my upload is slow but it's now Wednesday, tonight I'll finish them and upload them. Are you able to flash zips with your recovery as of now? Any requests or suggestions on root?
Sent from my moto g(6) play using Tapatalk
Click to expand...
Click to collapse
we are currently having issues with magisk, but phh's su works on gsis. and yes i can flash zips in twrp
Sands207 said:
It will be custom stock. I will grab your firmware as well. my upload is slow but it's now Wednesday, tonight I'll finish them and upload them. Are you able to flash zips with your recovery as of now? Any requests or suggestions on root?
Click to expand...
Click to collapse
Ill test
I've been sick so I'm a little behind. I'll include the phh su for testing purposes until we can get magisk working. Expect an update on the ROM's soon. I'm building for 4 different models so it's taking me longer than i anticipated.
Sands207 said:
I've been sick so I'm a little behind. I'll include the phh su for testing purposes until we can get magisk working. Expect an update on the ROM's soon. I'm building for 4 different models so it's taking me longer than i anticipated.
Click to expand...
Click to collapse
Thank you.
Moto G7 PLAY with MicroG?
Any progress with this project?
I have the Moto G7 Play..
I would like to install TWRP, flash custom ROMs.. is this available yet?
In particular i would like a ROM that supports MicroG /signature spoofing..
https://www.youtube.com/watch?v=UXLo15l2i4c
I have seen this is possible, but i do not know how to achieve it.. any help?
i have the sprint/boost version. i have got twrp to work but ran into a problem with magisk. treble versus non treble. would be willing to pull anything that would help or try anything, this is an extra phone for me so would love to help someone.
bigsteve62275 said:
i have the sprint/boost version. i have got twrp to work but ran into a problem with magisk. treble versus non treble. would be willing to pull anything that would help or try anything, this is an extra phone for me so would love to help someone.
Click to expand...
Click to collapse
What twrp u use and is it decrypting phone properly
i used the twrp that spaceminer provided, followed that tutorial, can possible attach a copy and refer you to the tutorial. also used the dtbo that was provided also.
it wont let me attatch the twrp, sorry
if needs be i will write out exatcly what i have done and send you screen shots of everything. i will help however i can, you guys have been great. keeps me in paperweights lol