Okay so my GPS is super dodgy on CM 12 roms. Sometimes locks after 5 minutes, sometimes not at all and never stays locked. When using google maps, all I hear is "GPS SIGNAL LOST" over and over.
I've done a lot of research and apparently these two things work for a lot of people:
1. Flash a stock rom (4.X), get a GPS fix, then reflash 5.0x rom
OR
2. Use these commands in fastboot:
fastboot erase modemst1
fastboot erase modemst2
Could anyone please make a .zip to be flashed for solution number 2?
I can't get fastboot working and I've tried heaps of things. (FYI adb works over camera mode when the phone is on, but I can't get fastboot devices to work and adb stops working in bootloader mode.)
I've found that Minimal ADB and Fastboot works better for me than the other. Have you tried it? You can find it here.
knightandroid said:
I've found that Minimal ADB and Fastboot works better for me than the other. Have you tried it? You can find it here.
Click to expand...
Click to collapse
Yup, tried that. I dno what's going on. Maybe some driver issues.
I was hoping to find a way to erase those files without using fastboot. I imagine this is possible?
Removed the link, i believe its not worth to download and flash, please read below.
ATTENTION:
It makes the signal quality better but also erases the lte band20 which is not a good thing for X720! I am sorry because i havent checked this issue before. I apologize from the people who flashed this file and lost b20 at the end. But the solution is really easy.
Please download and flash via TWRP the original chinese x720 baseband/modem file (23s) below
https://goo.gl/wMhqLJ
And then from fastboot via fastboot commands below :
fastboot erase modemst1
fastboot erase modemst2
and boot the phone. The all bands are back and locked. See the attachment.
<Mod Edit>
Thread closed by OP request.
I flashed it a hour ago, I will test it tomorrow and maybe the next days Got no problems after flashing it (AICP 8.1 ROM)
Firmware 28S not flashed the modem. This modem is from Cool Changer S1. It was their custom ROM 28S Sister Xia
Sorry for my bad English
You mean the modem i shared is for cool changer s1? Maybe thats right. But both devices are %99 similar as haedware. including the bands. I think thats why it works well on x720 too
Don't flash this if you don't want to lose LTE band 20. I flashed just NON-HLOS.bin instead of whole zip and the band was missing after that.
Had to restore my phone from backup. Also checked few sources and Cool Changer S1 does not support band 20, so it makes sense.
You are right. It is giving a stronger signal quality but erasing the band 20.
But there is a solution. No need for a backup even.
From this link flashing X720 chinese 23s baseband/modem from TWRP
https://goo.gl/wMhqLJ
And then from fastboot via fastboot commands :
fastboot erase modemst1
fastboot erase modemst2
and boot the devices. The all bands are back and locked.
After neonncz's post, i also found out after flashing this modem, we are losing the band20 which is not a good thing. Allthough this baseband/modem makes the signal quality a bit better, its not nice to lose this lte band especially for european users.
The solution is here
Download the 23s chinese/original modem file and flash via Twrp
https://goo.gl/wMhqLJ
And then from fastboot, follow commands below:
fastboot erase modemst1
fastboot erase modemst2
and boot the phone. The all bands are back and locked.
I am really sorry because i didnt check this issue before. i apologize
After neonncz's post, i also found out after flashing this modem, we are losing the band20 which is not a good thing. Allthough this baseband/modem makes the signal quality a bit better, its not nice to lose this baseband, especially for european users.
The solution is here
https://goo.gl/wMhqLJ
And then from fastboot via fastboot commands :
fastboot erase modemst1
fastboot erase modemst2
and boot the phone. The all bands are back and locked.
I am really sorry because i didnt check this issue before. i apologize
Here's what I've learned far about the E6:
Mostly from Treble Info app from Hackintosh Five
VNDK-28
Arm32 BINDER64
It's actually AB, according to it having System As Root.
No Seamless upgrade.
Binder64-AB/A64-AB GSIs work on this device.
Quack GSI should be the first we focus on.
TO INSTALL:
Code:
fastboot -w flash system <gsiname.img>
BOOTS
Quack GSI (AOSP 10, bb)!
Will list others as I come across them.
This is awesome.
I got LOS 16 bvn to boot.
The ril must be off or something, it had no connection.
I've got stock rom with encryption disabled and verity disabled, full magisk root living inside the boot.img..
And got twrp with touch adb and mtp working...
But it looks a lil funny cause the port has slightly smaller image so it doesn't fully fill screen.
But everything seems to work, including flashing zips..
Should that be a thread by its self?
LgPWN'd said:
This is awesome.
I got LOS 16 bvn to boot.
The ril must be off or something, it had no connection.
I've got stock rom with encryption disabled and verity disabled, full magisk root living inside the boot.img..
And got twrp with touch adb and mtp working...
But it looks a lil funny cause the port has slightly smaller image so it doesn't fully fill screen.
But everything seems to work, including flashing zips..
Should that be a thread by its self?
Click to expand...
Click to collapse
Yes, please! it's very nice that u did that, I'll link it in the main post when u do
For a working recovery see this
https://forum.xda-developers.com/moto-e6/development/development-team-looking-testors-t4120171
tried:
>fastboot flash system <image.img>
for all the 3 Quack GSI: system-quack-arm32_binder64-ab-gapps.img.xz, system-quack-arm32_binder64-ab-go.img.xz and system-quack-arm32_binder64-ab-vanilla.img.xz
The system just keeps looping the andriod logo...
Anyone knows of a twrp version that works with this moto e6?
soulmaker2207 Did you do the -w in fastboot after you installed the gsi? If you didn't it is definitely worth a try Beware it will erase all data including the internal sd
soulmaker2207 said:
tried:
>fastboot flash system <image.img>
for all the 3 Quack GSI: system-quack-arm32_binder64-ab-gapps.img.xz, system-quack-arm32_binder64-ab-go.img.xz and system-quack-arm32_binder64-ab-vanilla.img.xz
The system just keeps looping the andriod logo...
Anyone knows of a twrp version that works with this moto e6?
Click to expand...
Click to collapse
Alongside the fastboot -w advice, try renaming every img you download to "system.img." I have had way more success doing that than using long img names.
Also, I noticed that for a lot of GSIs, USB Tethering does not work.
Just installed latest phusson aosp android 11 gsi, over latest stock pie, using fastboot -w option, of course. Boots great, working VoLTE, sms, etc. Super fast performance. Usb tethering greyed out. That's the only problem I sound so far.
scottyrick2 said:
Just installed latest phusson aosp android 11 gsi, over latest stock pie, using fastboot -w option, of course. Boots great, working VoLTE, sms, etc. Super fast performance. Usb tethering greyed out. That's the only problem I sound so far.
Click to expand...
Click to collapse
Yeah USB Tethering doesn't seem to work for ANY GSI ROMs.
I am running Android 11 AOSP now using phhusson gsi rom V300.l. For your phone calling and sms to work properly, you need to follow this guide every time you reboot or power off/on. I mean every time.
[Razer Phone 2/as of v300.l/non-Verizon] IMS still needs some manual intervention to re-enable after reboot. · Issue #1681 · phhusson/treble_experimentations · GitHub
I have done this often enough now that I can do it in under 30 seconds. Hopefully, this issue will be fixed soon, but it is not that difficult to fix yourself.
scottyrick2 said:
I am running Android 11 AOSP now using phhusson gsi rom V300.l. For your phone calling and sms to work properly, you need to follow this guide every time you reboot or power off/on. I mean every time.
[Razer Phone 2/as of v300.l/non-Verizon] IMS still needs some manual intervention to re-enable after reboot. · Issue #1681 · phhusson/treble_experimentations · GitHub
I have done this often enough now that I can do it in under 30 seconds. Hopefully, this issue will be fixed soon, but it is not that difficult to fix yourself.
Click to expand...
Click to collapse
How odd. I can't get any Android 11 GSI to work on my E6
Are you trying to update from Android 10? I don't think you can.
scottyrick2 said:
Are you trying to update from Android 10? I don't think you can.
Click to expand...
Click to collapse
Yes I was trying to update from Android 10
I am running phhusson aosp 11 v300.l gsi rom right now. Super fast. Amazing, really.
If you are on the T-Mobile system, you need to do 3 things in order to make VoLTE and sms work properly. Hopefully, this will not be needed in future updates, but it might be.
1. using a root file explorer (I use 3C) to locate and move the org.codeaurora.ims folder from /data/app to /system/app
2. reboot
3. using *#*#4636*#*# on the dialer to open "phone information menu", change the band to GMS/WCDMA/LTE, and close the menu.
That's it. I hope this helps you to consider moving up to gsi roms. They are truly amazing.
Greetings people and like minded friends of the internet (and fellow trashman) I come bearing great gifts of flashing goodness. For the XT2005-5, I needed a nice de-Googled imaged phone for usage. As most of you probably have found in searching, finding TWRP and getting it to work has been a tedious journey. Never fear, there is a way to drop images on this phone. I will give you my experience and steps I took, in hopes it may help you save a bit of time.
1.) Download the factory image for the device found here
https://mirrors.lolinet.com/firmware/motorola/surfna/official/RETUS/ I used this one https://mirrors.lolinet.com/firmwar...-DEFAULT_regulatory-XT2005-5-SKU6_CFC.xml.zip Use a program like 7-Zip to extract it to a folder of your liking and you will use this folder later in the process. Of course, you're welcome to stop here and just flash the factory image and be done. But after all, why would you be reading this post if you wanted to just stop here, right?!
2.) Now find a GSI system image of your liking for flashing to the phone. I used the following system image from PHH (KUDOS FOR THE MAN WHO ROCKS GREAT ANDROID SKILLS) https://github.com/phhusson/treble_experimentations/releases For this phone you can you ARM32/Binder64/AB and I decided to go with
system-roar-arm32_binder64-ab-vndklite-vanilla.img.xz as I wanted no GAPPS. You will need to use 7-Zip again to extract the image from the archive file you've download. You can extract this file anywhere for the time being.
3.) Rename the extracted image from step 2 to system.img (just for simplicity) and put the file in the same directory you've created from step1.
4.) Now create a flashfile2.bat with the following and put this .bat file in the same directory as Step1
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase userdata
fastboot erase cache
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
5.) You will notice that I modified the .bat to flash the system.img that was downloaded in Step 2. Keep in mind, this method will re-write your system and you will LOSE ALL OF YOUR DATA so ensure you have YOUR DATA BACKED UP.
Run the flashfile2.bat file after you've connected your USB cable and you're at the bootloader screen
You already unlocked the bootloader, right? Hopefully, you're at least to BL screen, right after you've researched a bit about your phone .
b00ster23 said:
Greetings people and like minded friends of the internet (and fellow trashman) I come bearing great gifts of flashing goodness. For the XT2005-5, I needed a nice de-Googled imaged phone for usage. As most of you probably have found in searching, finding TWRP and getting it to work has been a tedious journey. Never fear, there is a way to drop images on this phone. I will give you my experience and steps I took, in hopes it may help you save a bit of time.
1.) Download the factory image for the device found here
https://mirrors.lolinet.com/firmware/motorola/surfna/official/RETUS/ I used this one https://mirrors.lolinet.com/firmwar...-DEFAULT_regulatory-XT2005-5-SKU6_CFC.xml.zip Use a program like 7-Zip to extract it to a folder of your liking and you will use this folder later in the process. Of course, you're welcome to stop here and just flash the factory image and be done. But after all, why would you be reading this post if you wanted to just stop here, right?!
2.) Now find a GSI system image of your liking for flashing to the phone. I used the following system image from PHH (KUDOS FOR THE MAN WHO ROCKS GREAT ANDROID SKILLS) https://github.com/phhusson/treble_experimentations/releases For this phone you can you ARM32/Binder64/AB and I decided to go with
system-roar-arm32_binder64-ab-vndklite-vanilla.img.xz as I wanted no GAPPS. You will need to use 7-Zip again to extract the image from the archive file you've download. You can extract this file anywhere for the time being.
3.) Rename the extracted image from step 2 to system.img (just for simplicity) and put the file in the same directory you've created from step1.
4.) Now create a flashfile.bat with the following and put this file in the same directory as Step1
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase userdata
fastboot erase cache
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
5.) You will notice that I modified the .bat to flash the system.img that was downloaded in Step 2. Keep in mind, this method will re-write your system and you will LOSE ALL OF YOUR DATA so ensure you have YOUR DATA BACKED UP.
Run the .bat file after you've connected your USB cable and you're at the bootloader screen
You already unlocked the bootloader, right? Hopefully, you're at least to BL screen, right after you've researched a bit about your phone .
Click to expand...
Click to collapse
ARM32/Binder64/AB = a64 a/b OR potentially a64bvN/a64bvS
Something to make it easier on others.
There was a link for TWRP on this post but had to remove it because the link is dead. I'll explore other options before re-updating this post
koyo said:
Some things to add to this post to make it easier
1) ARM32/Binder64/AB = a64 a/b OR potentially a64bvN/a64bvS
2) I prefer doing it via this method rather than flashing stock files: - E6 AIO ToolKit Mod Release- | XDA Developers Forums (xda-developers.com)
This has a TWRP for E6 which allows you to flash things like magisk, universal encryption disabler, gapps, et cetera. Things that might not be built into the native ROM.
Click to expand...
Click to collapse
The links are all broken, and I see no TWRP available.
b00ster23 said:
The links are all broken, and I see no TWRP available.
Click to expand...
Click to collapse
Ugh oops. This is the result of going off of memory from months ago rather than checking to see if everything's up to date.
The developers that made that TWRP have an OrangeFox recovery to download on their telegram
Telegram: Contact @android_general_chat
t.me
koyo said:
Ugh oops. This is the result of going off of memory from months ago rather than checking to see if everything's up to date.
The developers that made that TWRP have an OrangeFox recovery to download on their telegram
Telegram: Contact @android_general_chat
t.me
Click to expand...
Click to collapse
Yeah, I don't see any links to the OrangeFox recovery img... Keep in mind this is for the XT2005-5 variant (SURFNA) unless OrangeFox is universal
b00ster23 said:
Yeah, I don't see any links to the OrangeFox recovery img... Keep in mind this is for the XT2005-5 variant (SURFNA) unless OrangeFox is universal
Click to expand...
Click to collapse
Telegram: Contact @Android_General_Chat
t.me
#UPDATEWARNING
WARNING DO NOT UPDATE TO V11.0.3.0
V11.0.3.0.QFQMXTC (not QFQMIXM one where MI=Global) is rolling out to the Mi A3 global users.
There was a serious bug in the latest update, so DO NOT UPDATE!!
https://c.mi.com/thread-3204184-1-0.html
Apparently Xiaomi has rolled out an incorrect build for our device. After flashing, it splashes "Telcel" logo (which is a Mexican carrier), and only SIM1 seems to work post update. If you see any updates, just ignore and do NOT flash.
If you have already updated, just open fastboot and use below command
Unlock your bootloader if you haven't already (You're going to lose all your data so backup first!)
Boot your device into fastboot and type this in the cmd window on your pc.
fastboot flashing unlock (it's going to erase, unlock and boot)
Reboot to fastboot again
fastboot flashing unlock_critical
After it boots up reboot to fastboot again
In cmd window on your pc type:
fastboot set_active a
Replace 'a' with your current inactive slot
Can anyone confirm this works?