Moto g5s xt-1799-2 rr - Moto G5S Guides, News, & Discussion

Managed to succesfully port Ressurection Remix (7.1) to the Moto Green Pomelo (xt1799). Rom boots and all features work apart from Fingerprint reader.
Need help with fixing fingerprint

dmilz said:
Managed to succesfully port Ressurection Remix (7.1) to the Moto Green Pomelo (xt1799). Rom boots and all features work apart from Fingerprint reader.
Need help with fixing fingerprint
Click to expand...
Click to collapse
Sorry for mb inappropriate question: Do you have a physical device? If you do, did you unlock and root it (cos i have some issues with that)?

irewer said:
Sorry for mb inappropriate question: Do you have a physical device? If you do, did you unlock and root it (cos i have some issues with that)?
Click to expand...
Click to collapse
Yes i do..
I unlocked bootloader and rooted

dmilz said:
Managed to succesfully port Ressurection Remix (7.1) to the Moto Green Pomelo (xt1799). Rom boots and all features work apart from Fingerprint reader.
Need help with fixing fingerprint
Click to expand...
Click to collapse
Have you figured the problem out yet? Is there any other known custom ROMs working on Pomelo? Also how did you do it? I don't see Montana in Downloads section for the ROM.

sixtheninth said:
Have you figured the problem out yet? Is there any other known custom ROMs working on Pomelo? Also how did you do it? I don't see Montana in Downloads section for the ROM.
Click to expand...
Click to collapse
No, i didnt get the chance to figure it out as i broke my moto screen completely. There are no custom roms for the xt-1799-2, wish i had shared it. But if you are interested you can easily port the roms for any moto g5s over to your xt-1799-2

dmilz said:
No, i didnt get the chance to figure it out as i broke my moto screen completely. There are no custom roms for the xt-1799-2, wish i had shared it. But if you are interested you can easily port the roms for any moto g5s over to your xt-1799-2
Click to expand...
Click to collapse
Yeah, I am very interested. I tried RR, LineageOS, Viper for other montanas, all crashed after boot back into bootloader. Also I'd be interested getting Oreo based ROMs. So far I m stuck with chinese ZUI 3.1 which prevents me from flashing or installing Gapps.

sixtheninth said:
So far I m stuck with chinese ZUI 3.1 which prevents me from flashing or installing Gapps.
Click to expand...
Click to collapse
You can unclock (XT1799-2 may be 'secretly' unlocked already), root your device, flash custom TWRP (escpecially for Moto G5S XT1792/1794 and Green Pomelo XT1799-2) - and then you'll be able to install Open GApps via TWRP/root.
Also you can simply open special Lenovo App Store on your ZUI-based phone (look for it carefully!), install Google Store's apk from out there - and be enjoying with any GApps and other official apk's.
sixtheninth said:
Also I'd be interested getting Oreo based ROMs.
Click to expand...
Click to collapse
If you will flash bootloader version 07 (not 06 as you have on any available ZUI stock ROMs), you'll be able to flash distinct Oreo firmware (XT1792 for Brasil/India/EU) in straight way (thread 1; thread 2). BUT YOU'RE GOING TO LOSE NFC and SELFIE-CAMERA in cause of special drivers lack!!! And you will have no way for downgrading of firmware in cause higher version bootloader.
* also you would prefer to flash Moto G5s' stock Android 7.1.1 firmaware (XT1794) on your Green Pomelo (XT1799-2), using this manual.
** stock Green Pomelo's ZUI-based Android 7.1.1 firmware you can find here

irewer said:
You can unclock (XT1799-2 may be 'secretly' unlocked already), root your device, flash custom TWRP (escpecially for Moto G5S XT1792/1794 and Green Pomelo XT1799-2) - and then you'll be able to install Open GApps via TWRP/root.
Also you can simply open special Lenovo App Store on your ZUI-based phone (look for it carefully!), install Google Store's apk from out there - and be enjoying with any GApps and other official apk's.
If you will flash bootloader version 07 (not 06 as you have on any available ZUI stock ROMs), you'll be able to flash distinct Oreo firmware (XT1792 for Brasil/India/EU) in straight way (thread 1; thread 2). BUT YOU'RE GOING TO LOSE NFC and SELFIE-CAMERA in cause of special drivers lack!!! And you will have no way for downgrading of firmware in cause higher version bootloader.
* also you would prefer to flash Moto G5s' stock Android 7.1.1 firmaware (XT1794) on your Green Pomelo (XT1799-2), using this manual.
** stock Green Pomelo's ZUI-based Android 7.1.1 firmware you can find here
Click to expand...
Click to collapse
Thanks a lot! I was unable to Flash Gapps 7.1 in TWRP due to incorrect architecture error. I see that Oreo original ROM will probably never arrive to this phone, so I'll stick to 7.1. What buzzes me the most is that there is no custom rom compatible with XT1799 without losing some of its extra functions. I wonder how hard it will be to port Lineage, RR or similar to enjoy. I've been always using custom roms and now I feel kinda left out
---------- Post added at 10:31 AM ---------- Previous post was at 10:23 AM ----------
sixtheninth said:
Thanks a lot! I was unable to Flash Gapps 7.1 in TWRP due to incorrect architecture error. I see that Oreo original ROM will probably never arrive to this phone, so I'll stick to 7.1. What buzzes me the most is that there is no custom rom compatible with XT1799 without losing some of its extra functions. I wonder how hard it will be to port Lineage, RR or similar to enjoy. I've been always using custom roms and now I feel kinda left out
Click to expand...
Click to collapse
Update, I just fastboot flashed the Firmware from the links provided, but managed to hard brick my phone!!!!!! ((( Don't know what to do now.

careful with flashing other moto g5s model roms on the xt-1799-2, its different and so you might get a brick. The best you can do is port like i said. You can unlock bootloader by "fastboot oem flashing" if that doesnt work for you try "fastboot oem unlock". I will be back on the pomelo xt-1799-2 soon as i am planning to order another one. Infact you guys will need a section dedicated to the xt-1799-2

sixtheninth said:
Thanks a lot! I was unable to Flash Gapps 7.1 in TWRP due to incorrect architecture error. I see that Oreo original ROM will probably never arrive to this phone, so I'll stick to 7.1. What buzzes me the most is that there is no custom rom compatible with XT1799 without losing some of its extra functions. I wonder how hard it will be to port Lineage, RR or similar to enjoy. I've been always using custom roms and now I feel kinda left out
---------- Post added at 10:31 AM ---------- Previous post was at 10:23 AM ----------
Update, I just fastboot flashed the Firmware from the links provided, but managed to hard brick my phone!!!!!! ((( Don't know what to do now.
Click to expand...
Click to collapse
Hope this helps to unbrick
http://motog5szuirom.blogspot.com/2018/01/zui-31-for-moto-g5s-stock-rom.html

dmilz said:
careful with flashing other moto g5s model roms on the xt-1799-2, its different and so you might get a brick. The best you can do is port like i said. You can unlock bootloader by "fastboot oem flashing" if that doesnt work for you try "fastboot oem unlock". I will be back on the pomelo xt-1799-2 soon as i am planning to order another one. Infact you guys will need a section dedicated to the xt-1799-2
Click to expand...
Click to collapse
I agree, a since it is a slightly different phone a independent section can be great. Now, I am not a developer, so things like porting ROMs is not in my skillset, but I understand that selfie cam and nfc will not work on any custom ROM even if ported simply due to driver issue. I have rooted my phone previously, so I was past unlocking. Problem was that I soft bricked moment I pressed 'factory reset' - the phone would just endlessly keep booting into recovery mode, which was strange as it had stock ROM updated by reseller into a global version. Then I tried to flash various custom ROMs without any luck. Pretty much tried any Montana ROM I could find, but as I said, I don't know how to port so I got stuck in recovery loop. Then I found out about Oreo project and tried to fastboot flash that. That was a major mistake. It upgraded bootloader to 7 without me realising this. I found out nfc and selfie camera not working, so I wanted to downgrade to stock chinese firmware and just install gapps manually. After I fastboot flashed the nougat firmware - my phone hard bricked and won't even respond it seems dead. Thus your link will not help. Anyway I am already on a mission to try to revive it using following method: https://forum.xda-developers.com/showpost.php?p=75932514&postcount=1
Thank you anyway and if by chance you stumble upon some cool compatible ROM or to be honest a ROM that works really good - I don't really need NFC, but fingerprint scanner, turbo charger, selfie camera and reasonable battery management (some ROMs apparently drain it too quickly) would surely be features to keep. Also, if you have at hand a guide on how to port these roms which I can learn, I'd be very grateful.
Thank you
Six

sixtheninth said:
Problem was that I soft bricked moment I pressed 'factory reset' - the phone would just endlessly keep booting into recovery mode ...
Click to expand...
Click to collapse
At the moment you could use TWRP menu* 'Reboot - Bootloader' to boot in Fastboot Flash Mode (yes, it's bootloader) - and then press Power button (with 'START' tag in front of it).
But you have preferred to experiment ... You lost bootloader in due of custom 'chinese suppliers' firmware (non-original ROM) and forbidden factory reset with it.
* if you had stock recovery, you need to change mode with Volume buttons to Fastboot Flash Mode - and do the next steps in the same way; also you would be able directly to boot in Fastboot mode (bootloader) using long press Power button + Volume Down button
sixtheninth said:
... Then I found out about Oreo project and tried to fastboot flash that. That was a major mistake. It upgraded bootloader to 7* without me realising this ... I wanted to downgrade to stock chinese firmware ... my phone hard bricked and won't even respond it seems dead ...
Click to expand...
Click to collapse
I warned you in straight way at that my post with a load of links to instructions and threads ('... you will have no way for downgrading of firmware in cause of higher version bootloader ...'). But you are bustler and illiterate, pardon me. By the way... do you know English or just use Google Translate?
* I have some unapproved info that OPP28.65-37[-2] firmware even uses bootloader version 12 (BL: BC12)
sixtheninth said:
Anyway I am already on a mission to try to revive it using following method: https://forum.xda-developers.com/showpost.php?p=75932514&postcount=1
Click to expand...
Click to collapse
Yes, it may be will help you to boot in Fastboot menu. Please, read all method instructions carefully (RTFM!!!), don't experiment on your own risk/luck.
On Russian forum we have some examples of 'reviving' XT1799-2 with XT1794 mmcblk0.img - but it's the question of bootloader version and disk partition. May be now you have either bootloader version 06 and partition again or corrupted/mixed software or something else, so may be you'll be need to use distinct XT1799-2 mmcblk0.img. I have it ('Repair' folder), but there aren't any proved mentions of it's compatibility / applicability / integrality - all our XT1799-2 'bricks' were re-covered with XT1794 mmcblk0.img finally.
If you know Russian language or wanna risk to translate with Google Tranlsate (omg, please, don't do that ) - you may use Russian 4pda forum because at this very moment it has the most full load of info about XT1799-2 flashing and repairing (yes, all Slavs are misers and adventurers) not in Chinese language.
dmilz, I sincerely beg your pardon for messing up in your RR port thread

irewer said:
At the moment you could use TWRP menu* 'Reboot - Bootloader' to boot in Fastboot Flash Mode (yes, it's bootloader) - and then press Power button (with 'START' tag in front of it).
But you have preferred to experiment ... You lost bootloader in due of custom 'chinese suppliers' firmware (non-original ROM) and forbidden factory reset with it.
* if you had stock recovery, you need to change mode with Volume buttons to Fastboot Flash Mode - and do the next steps in the same way; also you would be able directly to boot in Fastboot mode (bootloader) using long press Power button + Volume Down button
I warned you in straight way at that my post with a load of links to instructions and threads ('... you will have no way for downgrading of firmware in cause of higher version bootloader ...'). But you are bustler and illiterate, pardon me. By the way... do you know English or just use Google Translate?
* I have some unapproved info that OPP28.65-37[-2] firmware even uses bootloader version 12 (BL: BC12)
Yes, it may be will help you to boot in Fastboot menu. Please, read all method instructions carefully (RTFM!!!), don't experiment on your own risk/luck.
On Russian forum we have some examples of 'reviving' XT1799-2 with XT1794 mmcblk0.img - but it's the question of bootloader version and disk partition. May be now you have either bootloader version 06 and partition again or corrupted/mixed software or something else, so may be you'll be need to use distinct XT1799-2 mmcblk0.img. I have it ('Repair' folder), but there aren't any proved mentions of it's compatibility / applicability / integrality - all our XT1799-2 'bricks' were re-covered with XT1794 mmcblk0.img finally.
If you know Russian language or wanna risk to translate with Google Tranlsate (omg, please, don't do that ) - you may use Russian 4pda forum because at this very moment it has the most full load of info about XT1799-2 flashing and repairing (yes, all Slavs are misers and adventurers) not in Chinese language.
dmilz, I sincerely beg your pardon for messing up in your RR port thread
Click to expand...
Click to collapse
Well as irony had it, I did the operation literally seconds before I have read your warning. I was desperate of being stuck in either chinese rom or recovery loop. Anyway, I am amidst of transferring mmcblk0.img for XT1795 to my SD drive via Rufus. Problem is that it won't let me to choose GPT only MBR, so I hope that can still work. Another problem is that I don't how to check the actual bootloader version I am having there installed right now should I manage to get there.

sixtheninth said:
Another problem is that I don't how to check the actual bootloader version I am having there installed right now should I manage to get there.
Click to expand...
Click to collapse
The version of installed bootloader you can check in Fastboot Flash Mode (bootloader as actually, Power + Volume Down buttons pressing and so on).
The version of non-installed firmware you can find into special '.info' file, for example: file 'MONTANA_RETCN_NZS26.68-108_cid11_subsidy-DEFAULT_regulatory-DEFAULT_CFC_montana_retcn.info' inside ZUI-based MONTANA_RETCN_NZS26.68-108 ROM has this line:
Code:
MBM Version: BC.06

I used Win 10 and Rufus on XT-1799-2 using XT-1794 and 95 files, both holding power button for over 1min but screen remained black (

sixtheninth said:
I used Win 10 and Rufus on XT-1799-2 using XT-1794 and 95 files, both holding power button for over 1min but screen remained black
Click to expand...
Click to collapse
Because there were Android 7.1.1 images of mmcblk0 with corresponding partition and bootloader version (BC.07; and you may be need BC.08-BC.12 at this moment :shrugging: ).
Have you tried XT1799-2 mmcblk0.img (7.1.1)?
Have you ever found XT1794 Android 8.1.0-based mmcblk0.img ?

[/COLOR]
irewer said:
Because there were Android 7.1.1 images of mmcblk0 with corresponding partition and bootloader version (BC.07; and you may be need BC.08-BC.12 at this moment :shrugging: ).
Have you tried XT1799-2 mmcblk0.img (7.1.1)?
Have you ever found XT1794 Android 8.1.0-based mmcblk0.img ?
Click to expand...
Click to collapse
The results so far are underwhelming. I did the operation in Linux following https://forum.xda-developers.com/showpost.php?p=75932514&postcount=1 . Dowloaded both .img XT1794 and 95, checked the MD5 and flashed them on my sd card. Neither of them worked. Light was flashing at various intervals, but even after two minutes of holding the power button screen remained pitch black. I downloaded your image file for 1799-2, but ended with the very same result. I have not found XT1794 Android 8.1.0-based mmcblk0.img, yet. Would you know anything about it?

1799-2
Hello. I installed OREO 8.1 on MOTO 1799-22. The front camera and NSF do not work. No one will tell you the solution? Thank you friends.

nikolaiderho said:
Hello. I installed OREO 8.1 on MOTO 1799-22. The front camera and NSF do not work. No one will tell you the solution? Thank you friends.
Click to expand...
Click to collapse
But did you recover it from hard brick by using mmcblk0.img based on Oreo?

Have you done with your RR port for xt1799 yet?
I have purchased the xt1799 Green Pomelo,unlocked bootloader,and installed the twrp. I tried to flash many 7.1 Roms that were intended for g5s and always failed. please notify me if you are still working on the port.

Related

[Q] Moto G Bootloop

Hi,
I have moto g 2014 dual sim. today I tried to reflash the os but got "Failed to validate system image" upon reboot. So I unlocked the bootloader and again reflashed the os but got bootloop.. Please tell me how to boot my moto G 2014?
Read the instructions and flash it correctly with the correct firmware. Also post your question in the correct section.
If you have winrar or 7zip you can extract the firmware and take the "boot.img" file and flash it separate from the other firmware and it should work. That's how I do mine.
Sent from my Moto G using XDA Premium 4 mobile app
Sorry for posting in different section, but I need help
eksasol said:
Read the instructions and flash it correctly with the correct firmware. Also post your question in the correct section.
Click to expand...
Click to collapse
Let me tell you the series of events that led me to have bricked Moto G 2014:
1. I had X1068 Moto G 2-14
2. Wanted to reflash firmware and followed the steps provided in 4.2 section here http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
3. I got "Failed to Validate System Image" when I tried to reboot.
4. I was advised to unlock bootloader and reflash firmware. I did the same but got bootloop when I tried to reboot.
5. Now when I power on the phone, bootloader unlocked warning message comes and the screen blinks with the same message..
Please help Bro..
Who ever told you to unlock bootloader to flash firmware is giving bad advice. It is not required to unlock the bootloader to flash the factory firmware.
Make sure you're using the driver from here: http://www.mymotocast.com/download/MDM?platform=windows
(If you have other Android ADB drivers installed, uninstall them first, before installing this one.)
Make sure you are using mfastboot.exe, not the regular fastboot.exe.
Make sure your downloaded firmware is not corrupt and you got the correct version of the firmware for your device, there are different ones.
Download the firmware from here: http://sbf.droid-developers.org/phone.php?device=36
I believe your file is "Blur_Version.21.11.14.titan_retaildsds.retaildsdsall.en.03", but check on it.
After you reflash, make sure you boot into recovery mode and do a factory wipe.
The firmware for this phone is split into 3 files, so make sure you flash all three of them.
Issue Resolved
DillonFixDroids said:
If you have winrar or 7zip you can extract the firmware and take the "boot.img" file and flash it separate from the other firmware and it should work. That's how I do mine.
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks bro.. It was my mistake not to flash all files in the firmware folder.. apart from three system files (0,1,2), we also need to flash fourth system file (3) in the firmware folder... Thanks again bro...
MotoG 2nd Gen
Folks, I got a MotoG 2nd Gen (XT1068) I'm trying to root it but not successful. The main reason for rooting is that I want to record all my calls. Any solution?
Thanks,
Raj.
4dglobal said:
Folks, I got a MotoG 2nd Gen (XT1068) I'm trying to root it but not successful. The main reason for rooting is that I want to record all my calls. Any solution?
Thanks,
Raj.
Click to expand...
Click to collapse
Please be more presice, have you unlocked bootloader, before trying to flash the recovery?
Greetings from Venezuela. Just recently, I bought a new Moto G since my old S3 got severly damaged which made it unrepairable. I loved the reviews about de Moto G, but sadly since I got it I've had no luck with it.
While being connected to a WiFi connection, just looking around the celphone's settings, the phone required a system update straight off the bat. I had noticed before the update that the phone was instantly rebooting once the inactivity timer went off locking itself. Obviously after some time I did notice it by locking the phone manually (pressing the power button). I'm not that geeky or experienced in the Android field, but by doing some research on the web I've read some stuff that makes me not lose all hope on the phone, making me want to fix it.
I've tried factory resets, recoverys and nothing has worked. It has made me really frustrated not being able to fix the issue. All I've really done refering to flashing is unlocking bootloader, but still without flashing anything yet to make sure what I'm doing is the right thing to do.
Specs
Android version: 5.0.2
Baseband version: MSM8626BP_1032.3112.97.00R
RETUSA_AWS_CUST
Kernel version: 3.4.42-gf18cb80
System version: 22.46.12.titan_retuaws.retuaws.en.US retus
Need help with this, and I'll be eternally grateful with anyone that can help me.
P.S: new to the forums. In any case that I'm missing something, let me know.
joserodriguezv said:
Greetings from Venezuela. Just recently, I bought a new Moto G since my old S3 got severly damaged which made it unrepairable. I loved the reviews about de Moto G, but sadly since I got it I've had no luck with it.
While being connected to a WiFi connection, just looking around the celphone's settings, the phone required a system update straight off the bat. I had noticed before the update that the phone was instantly rebooting once the inactivity timer went off locking itself. Obviously after some time I did notice it by locking the phone manually (pressing the power button). I'm not that geeky or experienced in the Android field, but by doing some research on the web I've read some stuff that makes me not lose all hope on the phone, making me want to fix it.
I've tried factory resets, recoverys and nothing has worked. It has made me really frustrated not being able to fix the issue. All I've really done refering to flashing is unlocking bootloader, but still without flashing anything yet to make sure what I'm doing is the right thing to do.
Specs
Android version: 5.0.2
Baseband version: MSM8626BP_1032.3112.97.00R
RETUSA_AWS_CUST
Kernel version: 3.4.42-gf18cb80
System version: 22.46.12.titan_retuaws.retuaws.en.US retus
Need help with this, and I'll be eternally grateful with anyone that can help me.
P.S: new to the forums. In any case that I'm missing something, let me know.
Click to expand...
Click to collapse
SEE POST#3 USA AWS CARRIERS for latest update - READ INSTRUCTIONS
reefuge said:
SEE POST#3 USA AWS CARRIERS for latest update - READ INSTRUCTIONS
Click to expand...
Click to collapse
I followed the inscrutions, successfully flashing stock rom. But the bug is still there since the phone keeps rebooting once the screen is locked. Still need to know if there's any fix. Thanks for the help!
A New Problem
I recently got an ~138mb OTA update, tried to install it, after downloading it, but it failed at default recovery installer, rebooting with an error message saying "Update installation unsuccessful". Hence, I tried it with a custom recovery TWRP installed in my mobile, with TWRP manager app for android (with my phone rooted obviously) So after downloading update, on giving install, it goes to TWRP recovery main menu, from there I dont know how to install the downloaded update, or where it is available to browse to... Being unsure, I rebooted it to normal boot up, but no matter what I do now, the phone after turning on in the home screen, automatically powers down(switching off) to TWRP recovery main menu, I am stuck here please help me, someone.
I dont wanna lose all my data!! Give me a suitable solution
Goutham_SRIRAM said:
I recently got an ~138mb OTA update, tried to install it, after downloading it, but it failed at default recovery installer, rebooting with an error message saying "Update installation unsuccessful". Hence, I tried it with a custom recovery TWRP installed in my mobile, with TWRP manager app for android (with my phone rooted obviously) So after downloading update, on giving install, it goes to TWRP recovery main menu, from there I dont know how to install the downloaded update, or where it is available to browse to... Being unsure, I rebooted it to normal boot up, but no matter what I do now, the phone after turning on in the home screen, automatically powers down(switching off) to TWRP recovery main menu, I am stuck here please help me, someone.
I dont wanna lose all my data!! Give me a suitable solution
Click to expand...
Click to collapse
ota can only be installed to non rooted stock roms with stock recovery
tbh you need to minimum factory reset
but I believe you will need to install stock rom from scratch
---------- Post added at 06:54 PM ---------- Previous post was at 06:52 PM ----------
joserodriguezv said:
I followed the inscrutions, successfully flashing stock rom. But the bug is still there since the phone keeps rebooting once the screen is locked. Still need to know if there's any fix. Thanks for the help!
Click to expand...
Click to collapse
Never had or seen this all I can suggest is a factory reset twice and a few reboots to see if settles down
Guys i need help! I have the european Dual Sim Moto 2nd gen, locked bootloader and i tried to install Android Marshmallow via the indian zip (soak test) that i found in XDA. After installing the update via internal storage, it got stuck in optimizing 157 apps/158, it bootlooped and now it stucked it 1/1 optmizing ... What can i do???
Please, anything.

when i try to flash bluesparks twrp there only a white led no screen

The other problem i have is when i try to flash bluesparks twrp and go to recovery the sceen is blank and only the led glows but i can flash the officaial twrp and flash roms but they come with error 7 and when i flash a oxygen os it gets stuck in updating system image
ak_bagade said:
but i can flash the officaial twrp and flash roms but they come with error 7 and when i flash a oxygen os it gets stuck in updating system image
Click to expand...
Click to collapse
Error 7 often means you are trying to flash an Oreo ROM with an older version TWRP which does not support Oreo.
But we can't tell from the info provided by you. Always give version numbers and other details for TWRP (and blu_spark TWRP) you are having trouble with, as well as the ROMs you are trying.
Also, make sure you are using the right TWRP and ROMs for 3 versus 3T (another reason for Error 7).
redpoint73 said:
Error 7 often means you are trying to flash an Oreo ROM with an older version TWRP which does not support Oreo.
But we can't tell from the info provided by you. Always give version numbers and other details for TWRP (and blu_spark TWRP) you are having trouble with, as well as the ROMs you are trying.
Also, make sure you are using the right TWRP and ROMs for 3 versus 3T (another reason for Error 7).
Click to expand...
Click to collapse
its the latest bluesparks
ak_bagade said:
its the latest bluesparks
Click to expand...
Click to collapse
I said: always give a version number. "latest bluesparks" isn't a version number. I can't count how many times I've seen folks claim they flashed the "latest" recovery. And when prompted for more info, we find out that they aren't even close, sometimes flashing a version TWRP from 2 years ago or older! Not saying this is necessarily your case. But we don't know for certain, if you don't give us precise and accurate info to work with.
You also said you flashed official TWRP. What version number exactly?
You also need to tell us what custom ROMs (and versions) you tried to flash. And what version OOS did you try to flash?
Some friendly advice, try to take more than 5 seconds to type a response to questions we ask you. Provide as much detail as possible, and answer all the quesions. For that matter, when asking for help, posting 2 or 3 (poorly typed) sentences is rarely enough info to go on. Again, provide as much detail and specific info as possible.
this is mostly an outdated firmware issue, Always make sure you have the latest firmware for your device
Firmware 4.5.1/nougat/3T
Firmware 4.5.0/nougat/3
or you can try the Oreo ones
(Stable)
Firmware 5.0.0/Oreo/3T
Firmware 5.0.0/Oreo/3
(Open Beta)
Firmware OB20/Oreo/3T
Firmware OB29/Oreo/3
OP3T firmware thread https://forum.xda-developers.com/oneplus-3t/how-to/firmware-modem-collection-flashable-zips-t3565535
OP3 firmware thread https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
redpoint73 said:
I said: always give a version number. "latest bluesparks" isn't a version number. I can't count how many times I've seen folks claim they flashed the "latest" recovery. And when prompted for more info, we find out that they aren't even close, sometimes flashing a version TWRP from 2 years ago or older! Not saying this is necessarily your case. But we don't know for certain, if you don't give us precise and accurate info to work with.
You also said you flashed official TWRP. What version number exactly?
You also need to tell us what custom ROMs (and versions) you tried to flash. And what version OOS did you try to flash?
Some friendly advice, try to take more than 5 seconds to type a response to questions we ask you. Provide as much detail as possible, and answer all the quesions. For that matter, when asking for help, posting 2 or 3 (poorly typed) sentences is rarely enough info to go on. Again, provide as much detail and specific info as possible.
Click to expand...
Click to collapse
the bluesparks twrp which i flashed is 8.61 op-3t
and the official twrp which works is 3.2.1-0
so when i use the official twrp i have to remove the "assert" from the updater script and flash the rom or else i get the error 7
Something which has come up recently is that my homebutton/fingerprint sensor does not work (its like it doesnt exist) when i flash any rom from android 7-8.1.
So i came to stock by relocked the bootloader by the way like it happens when you hardbrick your device. now im in marshmallow.
Something you should know about is that i flash a lot of roms and locked and unlocked the bootloader a countless times and i think this has affected the files which might be related to the homebutton and fingerprint sensor .
The other funny thing is that when i called oneplus to help me with flashing the latest software there method helps me to get the bluesparks twrp but since i keep flashing i lose the twrp so thats the only way i can bliuesparks twrp
ak_bagade said:
Something you should know about is that i flash a lot of roms and locked and unlocked the bootloader a countless times and i think this has affected the files which might be related to the homebutton and fingerprint sensor .
Click to expand...
Click to collapse
Doesn't work like that, the home button, fp sensor "files" are not in TWRP, or managed by FW in any way. All of these are in the /system folder of the ROM that is installed. Which is why they don't work in TWRP.
Have you been on MM since you got this phone? If so, your firmware is heavily outdated, and that's why you end up with the White LED of Death. Try flashing the latest Open Beta over stock recovery. Make sure to unlock your bootloader first. Then flash any variant of TWRP you want, and then see if you still get the White LED of Death.
ak_bagade said:
Something you should know about is that i flash a lot of roms and locked and unlocked the bootloader a countless times and i think this has affected the files which might be related to the homebutton and fingerprint sensor .
Click to expand...
Click to collapse
You shouldn't be locking the bootloader if you are flashing custom recovery and custom ROMs, and you don't need a locked bootloader to flash official updates either. Really, there is no reason to lock the bootloader unless you are worried about security concerns; want a "full stock" conditions, etc. And for most xda users, an unlocked bootloader is going to be the highly preferable condition. Further, locking the bootloader requires be full stock (including stock recovery, not TWRP). And trying to lock the bootloader under any other condition, is asking for trouble.
I agree with the recommendation above, to flash the full zip of the Open Beta or official OOS update, which will put you on a fully "stock" baseline including firmware. Then go from there.
---------- Post added at 09:19 AM ---------- Previous post was at 09:07 AM ----------
ak_bagade said:
The other funny thing is that when i called oneplus to help me with flashing the latest software there method helps me to get the bluesparks twrp but since i keep flashing i lose the twrp so thats the only way i can bliuesparks twrp
Click to expand...
Click to collapse
If flashing the official zips with TWRP (including blu_sparks), you will always lose TWRP (overwritten with stock recovery) if you reboot after flashing the update. You can prevent this by flashing root (SuperSU, Magisk) or a custom kernel before rebooting (after the update).

GSI Questions

sorry if these are noob questions, however GSI's and custom roms confuse me, and I really don't want to brick my phone on accident
Preface:
I have a rooted moto g6 with an unlocked bootloader that supports project treble. as per getprop ro.treble.enabled running pie 29.55-24 Software channel Retail US
1. Can I flash a GSI on my phone
2. Where is there a good guide on how to flash a gsi
3. Will it factory reset my phone
4, Is there anything I should do beforehand
5. Are there any GSI's I can't flash
(What I think is 1:yes 2:If i knew i wouldn't be here 3:yes 4:backup system images 5: Yes
Thanks
Android Adam said:
sorry if these are noob questions, however GSI's and custom roms confuse me, and I really don't want to brick my phone on accident
Preface:
I have a rooted moto g6 with an unlocked bootloader that supports project treble. as per getprop ro.treble.enabled running pie 29.55-24 Software channel Retail US
1. Can I flash a GSI on my phone
2. Where is there a good guide on how to flash a gsi
3. Will it factory reset my phone
4, Is there anything I should do beforehand
5. Are there any GSI's I can't flash
(What I think is 1:yes 2:If i knew i wouldn't be here 3:yes 4:backup system images 5: Yes
Thanks
Click to expand...
Click to collapse
There are different types of treble devices you know. Only a couple GSI work on the g6.
GSI is a system image, so usually flash with fastboot.
Fastboot flash system system.img
Or in TWRP with the "install image" option.
The G6 does not have a b partition. So only try ones that say "arm A only". Meaning arm, not arm 64, and a - only, not a/b.
There is an entire section of this site devoted to it. Search "Project Treble". Without the quotes obviously
Here you go
https://forum.xda-developers.com/project-treble
Better yet here ya go
Built for the g6.
All GSIs are generic system images, so technically they can Flash on any device that has treble (with the correct CPU architecture and partitioning scheme) but when one gets built for your device most of the bugs have been worked out
madbat99 said:
There are different types of treble devices you know. Only a couple GSI work on the g6.
GSI is a system image, so usually flash with fastboot.
Fastboot flash system system.img
Or in TWRP with the "install image" option.
The G6 does not have a b partition. So only try ones that say "arm A only". Meaning arm, not arm 64, and a - only, not a/b.
There is an entire section of this site devoted to it. Search "Project Treble". Without the quotes obviously
Here you go
https://forum.xda-developers.com/project-treble
Better yet here ya go
Built for the g6.
All GSIs are generic system images, so technically they can Flash on any device that has treble (with the correct CPU architecture and partitioning scheme) but when one gets built for your device most of the bugs have been worked out
Click to expand...
Click to collapse
Thank you so much. I installed Lineage OS from https://forum.xda-developers.com/pr...i-lineageos-16-0-gsi-arm64-ab-how-to-t3908029 and my phone is working HOWEVER I can't read battery usage from setting but /data/system/batterystats.bin exists
Android Adam said:
Thank you so much. I installed Lineage OS from https://forum.xda-developers.com/pr...i-lineageos-16-0-gsi-arm64-ab-how-to-t3908029 and my phone is working HOWEVER I can't read battery usage from setting but /data/system/batterystats.bin exists
Click to expand...
Click to collapse
I would try the one I linked to. It is the most likely to have everything working. Descendant two dot two
The one you're trying to use says it's extremely specific to his device. Majorly buggy for others. Including A only devices.
Android Adam said:
Thank you so much. I installed Lineage OS from https://forum.xda-developers.com/pr...i-lineageos-16-0-gsi-arm64-ab-how-to-t3908029 and my phone is working HOWEVER I can't read battery usage from setting but /data/system/batterystats.bin exists
Click to expand...
Click to collapse
Did you ever manage to get battery to work? Mine doesn't either nor does the USB-C port
Sorry I need help installing the ROM GSi RR I get an error in the text of insufficient space and I get error 70 to someone else happens? And I tried to fix the problem and when I managed to install the gapps the phone did not start someone can help me?
ACM1PT said:
Sorry I need help installing the ROM GSi RR I get an error in the text of insufficient space and I get error 70 to someone else happens? And I tried to fix the problem and when I managed to install the gapps the phone did not start someone can help me?
Click to expand...
Click to collapse
Please link to the rom so I can try to help. describe what you're trying to do
Android Adam said:
Please link to the rom so I can try to help. describe what you're trying to do
Click to expand...
Click to collapse
Could you give me a guide on how to install with gapps? Sorry I have to write in English everything I did my language is Spanish sorry
ACM1PT said:
Could you give me a guide on how to install with gapps? Sorry I have to write in English everything I did my language is Spanish sorry
Click to expand...
Click to collapse
I need to know which rom you are using. Please post a link to it. Is this it https://www.google.com/amp/s/forum....urrection-remix-v7-0-arm64-32-b-t3891636/amp/
Android Adam said:
I need to know which rom you are using. Please post a link to it. Is this it https://www.google.com/amp/s/forum....urrection-remix-v7-0-arm64-32-b-t3891636/amp/
Click to expand...
Click to collapse
Are you using Oreo or pie
Android Adam said:
Are you using Oreo or pie
Click to expand...
Click to collapse
pie bro,
I will try to install again have it happen
ACM1PT said:
pie bro,
I will try to install again have it happen
Click to expand...
Click to collapse
I found the problem. The system partition is too small so GApps always fails. To solve it go to twrp adb push your rom, and flash it. Then go to format then system hit repair then resize and confirm. Of you are flashing a big GApps (Super) do it again. Flash GApps then Magisk (for root) then you're done

XT1965-T T-Mobile REVVLRY+ Stock rom

I got the T-mobile REVVLRY+ today, and naturally, I wanted to put the stock motorolla firmware on it. Partly to see if I could, partly to get rid of the T-Mobile bloat and see what Motorola features T-Mobile had removed.
Everything went swimmingly, I have PPW29.98-107 installed, I even have WIFI Calling. What I did lose, however, is VoLTE. I did use TWRP to perform a backup before flashing, so I tried restoring it to get a better look at how VoLTE works in the T-Mobile firmware. This is where things got hairy. I stupidly only backed up boot, system, and data. When I use TWRP to restore them, I get stuck in a boot loop. The built in boot loop fix in TWRP didn't help.
1. Any ideas on getting as close to stock as I can with only the boot, system, and data partitions?
2. Does anyone have access to a REVVLRY+ that would be willing to do a full backup that I may try to restore?
*Edit* SO I used the code *#*#4636#*#* and VoLTE provisioned is enabled, so maybe I do have VoLTE?
*Edit 2* Google Pay doesn't work, even after locking the bootloader. The device says that the operating system has been modified. Still trying to get it to restore.
FOUND IT!
I found a repo of firmware that has the TMO firmware! flashing now!
I can't share the external link yet.
BanterJSmoke said:
I found a repo of firmware that has the TMO firmware! flashing now!
I can't share the external link yet.
Click to expand...
Click to collapse
Where did you find it at? I would like to know because I'm trying to port Lineage OS to this phone. However, once I unlock the bootloader, I won't have an OS to use for it and i'll be screwed.
serris-chan said:
Where did you find it at? I would like to know because I'm trying to port Lineage OS to this phone. However, once I unlock the bootloader, I won't have an OS to use for it and i'll be screwed.
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/lake/official/TMO/
HOW to
Hi, I just picked up the Revvlry+. Do you have step by step to install the Stock Moto firmware? I miss some of the features of the Moto. Also, was it easy to restore the TMO firmware just in case?
did you make any progress into the volte research? im on a unlocked xt1965-2 and using metro but i dont get volte in any of the stock roms or custom roms. i have tried flashing the modem from the stock tmo rom which didnt really do anything. i will probably try to flash the entire tmo rom tonight and see if it boots. im thinking if i get volte in the tmo rom and backup the persist, vendor and efs. then if i restore them onto a working cutom rom with volte enabled, volte should work.
i have also read about different scenarios in where you have to install workarounds to enable volte on treble roms. like installing the ims.apk to route the calls to volte and flashing a volte enabler to inject the correct files into the vendor partition.
my other device is a moto g5 plus which has numerous volte issues when switching between stock and custom roms or between different versions of android.
Did you use the Moto G7 Plus TWRP? I just picked up a Revvlry+ and I'm looking to root to install lawnchair or pixel launcher as a system app.
successfully unlocked the bootloader of my t-mobile revvlry which is a rebranded moto g7 i did it using this method but i'm going to be a little cautious on rooting unless i know it's safe and won't brick i could use some help with this https://www.androidinfotech.com/root-moto-g7-plus-pie/ i have the revvlry not the plus i want to try multirom installer and install ubuntu touch on it but i don't want to screw up my only phone but the only way i can try it is if i had root permissions to do so to install linux tried userland but i couldn't get unity desktop to work i'd rather have full root instead of fakeroot update: i was able to boot twrp before but now it doesn't work i think my firmware updated cause now when i run fastboot boot twrp.img nothing happens and i end up with remote failed reboot the phone and it goes directly to recovery with the only option is to do a factory reset
ghostdogg49504 said:
successfully unlocked the bootloader of my t-mobile revvlry which is a rebranded moto g7 i did it using this method but i'm going to be a little cautious on rooting unless i know it's safe and won't brick i could use some help with this https://www.androidinfotech.com/root-moto-g7-plus-pie/ i have the revvlry not the plus i want to try multirom installer and install ubuntu touch on it but i don't want to screw up my only phone but the only way i can try it is if i had root permissions to do so to install linux tried userland but i couldn't get unity desktop to work i'd rather have full root instead of fakeroot update: i was able to boot twrp before but now it doesn't work i think my firmware updated cause now when i run fastboot boot twrp.img nothing happens and i end up with remote failed reboot the phone and it goes directly to recovery with the only option is to do a factory reset
Click to expand...
Click to collapse
Are you saying with a Tmobile Revvlry, you were able to just go to the Motorola bootloader unlock page, paste your unlock codes, and presto as if it was just a normal Moto phone? If so, that is awesome!
I am thinking of swapping my Moto G7 Play with a Revvlry because of the 3gb RAM and NFC (the size of the G7 Play is perfect, I don't want to be forced to carry around a giant phone), but would love to flash the stock Moto G7 Play ROM over the Tmobile version. Not sure I'm willing to risk it, but if anyone has tried, I'd love to hear about it.
Logged into my account for this. Sorry if this is a little offtopic, but I want to see if this phone is compatible(or rather, how compatible it is) not only with Stock ROMs, but also with custom ROMs. For those REVVLRY owners, what have been your experience with this?
ultracoolguy said:
Logged into my account for this. Sorry if this is a little offtopic, but I want to see if this phone is compatible(or rather, how compatible it is) not only with Stock ROMs, but also with custom ROMs. For those REVVLRY owners, what have been your experience with this?
Click to expand...
Click to collapse
Phone works great with stock ROMs. I haven't tested out any custom ROMs, but I do have root on my REVVLRY.
tri_cchan said:
Phone works great with stock ROMs. I haven't tested out any custom ROMs, but I do have root on my REVVLRY.
Click to expand...
Click to collapse
nice man
Relocking Bootloader
Would I do the OEM lockbootloader command to lock it back
Can confirm flashing Moto g7 play firmware on T-Mobile revvlry. Caveat, you can no longer take OTA's and NFC is broken. Also can be bootloader unlocked through the Moto website.
Wouldn't you need to flash the G7 plus firmware for NFC to work?
guitardoc64 said:
Wouldn't you need to flash the G7 plus firmware for NFC to work?
Click to expand...
Click to collapse
That makes sense, the SD632 is NFC capable however I'm on the G7 play not the plus (I know, I know wrong forum)
I can't get the stock rom to work. It just bootloops every time. I tried all 3 versions. Any ideas?
Hey friends, would one of you kind sould who own the Revvlry+ be kind enough to post this Wallpaper?
Thanks in advance!
BanterJSmoke said:
I found a repo of firmware that has the TMO firmware! flashing now!
I can't share the external link yet.
Click to expand...
Click to collapse
Did you manage to restore it with firmware? Because I have a bootloop and I'm looking for a solution
quiet boy
I just solved the problem I had like 4 crazy hours with solve bootloop, the problem that I commanded automatic flash, not flashing the vendor partition and then flashed the manual vendor partition
mfastboot flash vendor vendor.img and ready
edit:
for users with Revvlry+ variant (XT1965-T) use this Flash.bat

Need persist.img from latest global rom

Camera doesn't film horizontally. I thought the problem is with auto rotate so turned it on but camera still films vertically. Watched some videos but then the screen would stay horizontal even after exiting the video. Did some googling and found out that the sensors are not working and need to flash persist.img. Thanks in advance to whoever can help.
desertfoxtim said:
Camera doesn't film horizontally. I thought the problem is with auto rotate so turned it on but camera still films vertically. Watched some videos but then the screen would stay horizontal even after exiting the video. Did some googling and found out that the sensors are not working and need to flash persist.img. Thanks in advance to whoever can help.
Click to expand...
Click to collapse
If you want to do that , get the persist.img file from a fastboot rom or flash it via MIFLASH tool.
https://www.mifirm.net/model/olive.ttt
lolo9393 said:
If you want to do that , get the persist.img file from a fastboot rom or flash it via MIFLASH tool.
https://www.mifirm.net/model/olive.ttt
Click to expand...
Click to collapse
I have a similar problem, but there's no persist.img in the stock ROM zip
I've downloaded only firmware files too. No persist.img . I'm searching for the Willow version.
WinBug2 said:
I have a similar problem, but there's no persist.img in the stock ROM zip
I've downloaded only firmware files too. No persist.img . I'm searching for the Willow version.
Click to expand...
Click to collapse
You must download a FASTBOOT rom and not a ZIP.
Once unpacked Fastboot version let acces to all the rom content.
lolo9393 said:
You must download a FASTBOOT rom and not a ZIP.
Once unpacked Fastboot version let acces to all the rom content.
Click to expand...
Click to collapse
Hmm on Xiaomi's page are only zip files with stock roms. I don't understand what fastboot rom means. It's the third device I'm rooting and using customs roms etc. So I'm not totally newbie but fastboot rom?? I extracted the boot.img files for flashing it via fastboot. But....
Do you have a source for fastboot roms?
//Edit:
Found https://c.mi.com/oc/miuidownload/detail?guide=2
WinBug2 said:
Hmm on Xiaomi's page are only zip files with stock roms. I don't understand what fastboot rom means. It's the third device I'm rooting and using customs roms etc. So I'm not totally newbie but fastboot rom?? I extracted the boot.img files for flashing it via fastboot. But....
Do you have a source for fastboot roms?
//Edit:
Found https://c.mi.com/oc/miuidownload/detail?guide=2
Click to expand...
Click to collapse
you need to flash the zip from here through twrp since the fastboot commands dont support zips
I HAVE BEEN USING REALME 2 FROM PAST 2 YEARS THERE HAS BEEN NO PROBLEM.
Few weeks back I heard about Custom rom.
And Now My mind says install it you will get good battery and performance
On the Other My other part of my mind says you will get bugs l and you will brick it
I am totally terrified. Because there is a war going in my mind whether I should install custom rom or not.
Every morning I wake up I think about installing custom rom. I can't get rid of this thought.
I think I will go mad or something. Please Help me.
ANTROBAROTICS said:
I HAVE BEEN USING REALME 2 FROM PAST 2 YEARS THERE HAS BEEN NO PROBLEM.
Few weeks back I heard about Custom rom.
And Now My mind says install it you will get good battery and performance
On the Other My other part of my mind says you will get bugs l and you will brick it
I am totally terrified. Because there is a war going in my mind whether I should install custom rom or not.
Every morning I wake up I think about installing custom rom. I can't get rid of this thought.
I think I will go mad or something. Please Help me.
Click to expand...
Click to collapse
Well, installing custom roms has its own advantages and disadvantages.
(just like everything in life, so get over it)
Personally, I had to install twrp and a new miui ROM, because the message that miui says while updating "Do not power off your phone" was playing with my mind and i pulled the battery off
Then it blacked out and lit up on a screen saying "The system has been destroyed, hold the power button to shutdown"
Imagine how it could be
Either way a custom ROM is better than the default one.
But i dont recommend you to do it now because there might be an issue with SafetyNet right now if you install a custom ROM
You should do much more research before installing custom roms or rooting
What i recommend is that you wait some time more to get this issue out of the way.
P.S.: If you fail safetynet test you wont have any acces to Netflix and most banking apps
gabtit7 said:
Well, installing custom roms has its own advantages and disadvantages.
(just like everything in life, so get over it)
Personally, I had to install twrp and a new miui ROM, because the message that miui says while updating "Do not power off your phone" was playing with my mind and i pulled the battery off
Then it blacked out and lit up on a screen saying "The system has been destroyed, hold the power button to shutdown"
Imagine how it could be
Either way a custom ROM is better than the default one.
But i dont recommend you to do it now because there might be an issue with SafetyNet right now if you install a custom ROM
You should do much more research before installing custom roms or rooting
What i recommend is that you wait some time more to get this issue out of the way.
P.S.: If you fail safetynet test you wont have any acces to Netflix and most banking apps
Click to expand...
Click to collapse
But custom rom can be installed without rooting. So then also safety net will not work ?
Google realeased a new update that checks if the bootloader is unlocked
and the only way to lock it after flashing ROMs is to do a complete format and reinstall the original ROM, it replaces twrp or anything else with the original ROM (miui in our case)
So dont install roms
Okay. Thank you. I just wanted a reason not to install. Now is the end of custom rom I think majority will now no more root or install custom rom because of safety net. Copyright, Security & Privacy are now priority in today's world.
Some other members just found the solution but it supports only Android 10 & 11
[TUTORIAL] WORKING FIX FOR SAFETYNET / CTS PROFILE FAILED
Alright , here we go again . Steps to follow : 1. Open Magisk and select modules tab 2. Install Module for Android 11 - (https://t.me/XiaomiEUCloud/156) For Android 10 - (https://t.me/XiaomiEUCloud/158) from Storage 3. Reboot your Device Done . [emoji3544] UPDATE : NO NEED TO FLASH THIS ON...
xiaomi.eu

Categories

Resources