So, I have an XT1053 that I unlocked and got to 4.4.4 using the T Mobile stock ROM.
Everything was fine, I rooted it, it went all fine.
Then I installed the XPosed framework, got me some modules, and it was fine.
Then I got the Gravity Box to tweak my stuff.
Rebooted to activate it, and it was all fine and dandy until I changed setting that required a further reboot, like "show network activity indicators on WiFi/signal bars" and the navbar customizer.
I was hoping to come back and do some sweet customizations but instead, at reboot, my phone wouldnt get service, even though the SIM is detected, I have an IMEI and my SIMs phone number shows up on the About phone > status screen.
WiFi wont turn on, neither does bluetooth.
I disabled and uninstalled all the xposed components and modules but it stayed the same.
So I figured out all I had to do was come back to my clean, 4.4.4 stock nandroid backup.
No luck, issue persists. Did a factory reset (with the TWRP recovery might I add) but no such luck.
Downloaded both the AT&T and Verizons 4.4.4 versions, but I cant flash them using RDS lite, apparently the preflash verification fails, it mentions the gpt. I guess I need to flash the TMobile 4.4.4, but there is no such file at sbf developers, only 4.4.3, Will flashing this brick my phone?
This guy https://forums.motorola.com/posts/41d92959b1 has the same symptoms as me, but as you all can see, no follow up.
Any idea what can I do to fix this?
I totally place blame on the gravitybox network activity indicators settings, but who knows.
Added screenshots, edited out some stuff.
Thanks in advance, Ive spent most of my morning trying to figure this out.
No one?
:c
no_un_bot said:
So, I have an XT1053
WiFi wont turn on, neither does bluetooth.
I disabled and uninstalled all the xposed components and modules but it stayed the same.
So I figured out all I had to do was come back to my clean, 4.4.4 stock nandroid backup.
No luck, issue persists. Did a factory reset (with the TWRP recovery might I add) but no such luck.
Click to expand...
Click to collapse
Well, at first I thought maybe your phone somehow got stuck in airplane mode that for some reason wouldn't let go. So I put my phone in airplane mode to compare Status. It looks very similar except mine still shows WiFi Mac address and my voice and data shows radio off not out of service. signal strength looks the same.
A few suggestions:
- whenever you suspect Xposed might be responsible for something serious, you should usually do a full uninstall by flashing the Xposed Disabler zip that was automatically placed in your storage (check the Xposed folder in /sdcard/android/data or in just /sdcard or do a search).
- since you already tried FDR and nandroid restore, clearly something has been messed up that wasn't backed up before and that persists thru fdr. if you read around you'll notice there are some partitions, like the persist partition, that don't usually get backed up in a twrp or cwm nandroid. if you haven't already, read thru the thread (start post 5) that discusses recovering Wi-Fi and Bluetooth by manually restoring files in the persist folder. http://forum.xda-developers.com/moto-x/moto-x-qa/moto-x-xt1060-issues-wifi-bluetooth-t2813308
FYI it seems philz touch recovery can provide a more complete backup that includes those pesky partitions http://forum.xda-developers.com/moto-x/development/xt10xx-philz-touch-t2612149
- so yeah I'd attack the problem that way, see if you can restore WiFi and Bluetooth, then see what you can do with your signal strength and voice/data service. they could all be related to persist partition.
dtg7 said:
Well, at first I thought maybe your phone somehow got stuck in airplane mode that for some reason wouldn't let go. So I put my phone in airplane mode to compare Status. It looks very similar except mine still shows WiFi Mac address and my voice and data shows radio off not out of service. signal strength looks the same.
A few suggestions:
- whenever you suspect Xposed might be responsible for something serious, you should usually do a full uninstall by flashing the Xposed Disabler zip that was automatically placed in your storage (check the Xposed folder in /sdcard/android/data or in just /sdcard or do a search).
- since you already tried FDR and nandroid restore, clearly something has been messed up that wasn't backed up before and that persists thru fdr. if you read around you'll notice there are some partitions, like the persist partition, that don't usually get backed up in a twrp or cwm nandroid. if you haven't already, read thru the thread (start post 5) that discusses recovering Wi-Fi and Bluetooth by manually restoring files in the persist folder. http://forum.xda-developers.com/moto-x/moto-x-qa/moto-x-xt1060-issues-wifi-bluetooth-t2813308
FYI it seems philz touch recovery can provide a more complete backup that includes those pesky partitions http://forum.xda-developers.com/moto-x/development/xt10xx-philz-touch-t2612149
- so yeah I'd attack the problem that way, see if you can restore WiFi and Bluetooth, then see what you can do with your signal strength and voice/data service. they could all be related to persist partition.
Click to expand...
Click to collapse
Welp, somehow my persist folder is completely blank.
Guess I´d need for someone to upload theirs right?
An would an XT1060 persist folder work?
Thanks a bunch man, this has helped me lots.
no_un_bot said:
Welp, somehow my persist folder is completely blank.
Guess I´d need for someone to upload theirs right?
An would an XT1060 persist folder work?
Thanks a bunch man, this has helped me lots.
Click to expand...
Click to collapse
Totally empty looks fishy...are you sure you're running ES File Explorer with root permissions. If you don't give it root it will open that folder (and any other root read folder) as empty. check /data folder if it's empty you haven't set ES as root capable. You can do so from Fast Access -> Tools -> Root Explorer.
Yeah you can post a Request thread for the xt1053 persist files. a helpful person has already posted xt1060 persist folder on post #3 here ( http://forum.xda-developers.com/moto-x/moto-x-qa/wifi-isnt-t2760479 ) and he thinks it's probably the same for all variants. But keep in mind that post is from May so obviously it's before 4.4.4. On the other hand persist clearly persists, so it might also persist through updates. So I'd wait to see if anyone posts for xt1053 on 4.4.4 (try asking in that thread also) and only use the old upload if desperate. if you do use it worst case scenario if you encounter worse problems like boot loop or something you should be able to use your custom recovery's file manager to delete the files. make sure you read that thread all the way through though, taking note of the permissions you have to set. and also refer to the thread mentioned previously.
dtg7 said:
Totally empty looks fishy...are you sure you're running ES File Explorer with root permissions. If you don't give it root it will open that folder (and any other root read folder) as empty. check /data folder if it's empty you haven't set ES as root capable. You can do so from Fast Access -> Tools -> Root Explorer.
Yeah you can post a Request thread for the xt1053 persist files. a helpful person has already posted xt1060 persist folder on post #3 here ( http://forum.xda-developers.com/moto-x/moto-x-qa/wifi-isnt-t2760479 ) and he thinks it's probably the same for all variants. But keep in mind that post is from May so obviously it's before 4.4.4. On the other hand persist clearly persists, so it might also persist through updates. So I'd wait to see if anyone posts for xt1053 on 4.4.4 (try asking in that thread also) and only use the old upload if desperate. if you do use it worst case scenario if you encounter worse problems like boot loop or something you should be able to use your custom recovery's file manager to delete the files. make sure you read that thread all the way through though, taking note of the permissions you have to set. and also refer to the thread mentioned previously.
Click to expand...
Click to collapse
Boy oh boy was I wrong.
I fixed it, going to post what I did.
Turns out the /persist folder was not empty, root explorer showed everything was ok. he I thought, "Hey, XPosed + GravityBox caused (afaik) this mess, maybe it will get me out of it too. Maybe, as pointed out, xosed touched some partitions not normally accessible, lets see if they can do it again". So I installed those apps again, did the very same I did las time, and then uninstalled using the Xposed disabler .zip. Didnt work.
It was time to try and flash another stock ROM.
As Ive said before, I originally got into 4.4.4 with TMobiles ROM (my keyboard tilde key is broken, so bear with me), and attempting to flash AT&T/Verizon/BR Retail etc 4.4.4 stock ROMs would fail because of a security downgrade as far as gpt.bin goes.
I "fixed" this taking the gpt.bin file out of TMobiles OTA zip (the one that upgrades 4.4.3 to 4.4.4) and replacing the one on the ROM I was trying to flash with this. Meaning, I flashed the BR Retail 4.4.4 having replace gpt.bin with TMobiles OTA one.
Everything flashed ok, and, at the very last step, instead of using the command
Code:
fastboot oem config carrier vzw
like every guide out there says, I went for
Code:
fastboot oem config carrier ghost_retail
as per this page: https://github.com/CyanogenMod/android_device_motorola_ghost .
Phone rebooted with his Brazilian version and lo and behold, it was NOT working. Same symptoms.
I dug deeper, and the I remembered how someone with the same issues on another phone model fixed it by swapping his SIM for a friends, then using his again. I had already tried this, I even bough a SIM (because no one close to me uses a nano SIM) and it hadnt worked, but it did gave me some insight, maybe some sort of registration was not getting done.
Looking up stuff, I stumbled upon the "secret" testing menu on our Moto X, accessible by dialing *#*#4636#*#*
There I saw, to my horror, how my IMEI was 0.
Before giving up, I looked up how to fix this, turns out the BR modem was not quite right for Mexico. I flashed my country modem, getting he files from this video description (its in spanish, and the files are for Mexicos bands, but someone might find it useful): https://www.youtube.com/watch?v=oNSVRGvaKfY .
Rebooted, and to my relief, I had an IMEI again, though still no service, no wifi and no bluetooth.
Now, this special menu had some toggles that intrigued me, for they referenced to a possible registration, so I decided I should give it a go.
The toggles are pictured on the attached screenshot. These toggles, minus the CellInfoListRate, are only on and off.
I switched them so they would read "Turn radio off" (meaning it was on), "Turn off IMS regisration required" (meaning it was on, and my #1 suspect), "Turn off SMS over IMS" (seemed logical). I didnt play with the other 2 toggles.
Since I was cleaning, I left my phone on a table while I was sweeping, when suddenly the notification ringtone, one I hadnt heard in th past 2 days, sounded. I ran to my phone, and as angelic choirs played somewhere, I finally had signal bars, and an SMS had just gotten in.
Feeling relief, I was a bit let down when I still wasnt able to turn neither WiFi nor Bluetooth services. I called my brother, and when the call actually connected, I decided I might as well set my google account before anything else happened.
Now I had my contacts and data connection. I decided to turn the toggles that fixed this whole ordeal back to what I thought should be (thus now being as pictured on my screenshot) before rebooting.
Holding my breath, I rebooted and guess what: WiFi and bluetooth ould now be turned on, and connect.
This is the story of how I fixed this, hoping to help somebody out there.
Thanks to everyone who tried to help.
Moto X, you are a wild ride, but I love you.
Related
I've got everything unlocked and rooted and useing twrp latest version as my recovery.
I have been trying to install android L on my device, and was told to setup dvice as NEW device, That screen is after the google account log in along with the apps, the only way I know this is I have looked at install of android L screen shots.
Here is where the problem comes in, During setup I I do not get those screens ever....I have this same issue on an s3 and this moto X.
I have NO gps at all....when I use device only it shows no gps at all and will sit at a blank maps page forever. When I use high accuracy it then bounces around the map and does not lock onto my position at all, but just bounces around from positon to position. The Bouncing is common of using triangulation only, an no gps/gps assist IE: physical gps chip, but instead uses the data connection.
During setup I get every screen except the apps screen and the setup as new device. I have never once ever seen those screens ever after numerous installs on either the s3 or the moto X.
The steps I have done are as follows:
-In Twrp
Go to the wipe tab, and I have tried both ways, ether factory reset and slide the bar, I have also done the selecting of each item in the list, other than OTG or xternal usb at all, but I have wiped everything else.
After that I go back to the main menu, to install, pick the rom, then pick the gapps then flash. I have tried multiple gapps packages as well.
During setup I see every screen as I said, except for the apps screen, therfor I cannot setup as a new devivce because I just never see it, it's like it doesn;t exsist and goes directly to the OS.
As a side note everything on stock 4.4.3 works fine.
So I guess in short, why is it I don't see the apps section of the setup?
I use gps for my job a lot.
I'm in desperate need of help if anyone has any suggestions at all.
You posted in the wrong section. This belongs in q&a. But try flashing stock ROM. Get a GPS lock before flashing aosp.
PLEASE POST IN THE PROPER SECTIONS!
Also, just reboot into bootloader and run the follwing commands to resolve the issue.
fastboot erase modemst1
fastboot erase modemst2
athulele said:
PLEASE POST IN THE PROPER SECTIONS!
Also, just reboot into bootloader and run the follwing commands to resolve the issue.
fastboot erase modemst1
fastboot erase modemst2
Click to expand...
Click to collapse
Yeah I found that solution late last night and was going to post in here. That was the fix it now works, and gps works as well, so I get the window during setup as well as gps fixed.
Thankyou
5.0.2 Dialer / SMS prefix mismatching
I have CM12 official fresh clean install on Andys CWM Touch. I hope this is a problem others have seen with a simple solution - though I have looked hard!
Have a persistent issue with the dialer and sms not recognising numbers that are in my phone book unless they are in 1 format.
+44xxxxxxx vs 01xxxxxxx
In all prior versions dialing one or the other was recognised as the same number, no more.
Result is unknown callers and sms without names of people in phone book. Any ideas for a fix?
Go to Settings > Apps > (scroll to) All. Clear the Data/Cache on Contacts, Contacts Storage, and the Phone app. Then wait for your google account to re-sync is what worked for me
IEcansuckit said:
Go to Settings > Apps > (scroll to) All. Clear the Data/Cache on Contacts, Contacts Storage, and the Phone app. Then wait for your google account to re-sync is what worked for me
Click to expand...
Click to collapse
BOOM! Worked.
Saved me many days of head scratching with something that should have been an obvious fix!
Hi guys, I got a big big problem with my K3 Note, I think I went too far with wiping partitions before installing a new rom, here are the folders I wiped:
data, cache, system, protect_f, protect_s, dalvik cache.
After reboot my phone worked just fine but it didn't see the simcard, I thought it's the OS issue and wiped and flashed several times more.
Now when I got into the issue I noticed *#06# returns "invalid imei", after a little bit research I found out it's a common issue with MTK phones and found multiple possibilities for solving the problem, none of which worked for me though, for no known reason ;( What I've tried so far is: chamelephon app, MTK Engineer mode commands, flashable ZIP with the IMEIs, writing it with SN write tool and another program named something like Mauri? if I remember correctly, all done on the stock rom flashed with flashtool, now I'm retrying all of above on a custom rom.
I read somewhere that missing basebands can be an issue for MTK engineer mode, but I couldn't find any more info on the topic
I don't know if it is connected but the stock rom worked much worse than I remember when I first got the phone, it freezes completely(doesn't react to power button, keeps the led light after unconnected from charger, completely no response, I have to take out the battery each time) about once every 3-5minutes.
Another thing is, does anybody have any idea what the protect_f and _s folders are? I think I shouldn't have wiped them...
Any help would be much appriciated, I don't need another bricked phone... ;(
can you access bootloader mode and reflash with flashtools? i assume you dont have a backup? as far as i know the first partitition is responsible for the connection through USB so as far as i know if im not wrong you could reflash these partitions. dont know much however over these mtk devices
---------- Post added at 11:46 PM ---------- Previous post was at 11:41 PM ----------
freezes and shutdowns, even in lenovo stock recovery are a common problem i have found out. this has nothing to do with partitions in this case however dont know if this can be valid in your case. however in my example it is a fault within some lenovo stock roms. hope anyone can help you with more information
I do can flash with flashtool, at least thats how I flashed the stock rom, but I dont have a backup. Is it possible to use my IMEI with a different backup?
with my limited knowledge over the subject. preloader is the recovery since you can get a connection, what is safe to try without tinkering to much is flashing the latest vibe 3.0 45 dev rom over at needrom.com, since this rom also affects other partitions. once you have done this completely wipe every partition manually sometimes in TWRP i have seen some partitions dont function fully until you change partition format from ext4 to f2fs and back to ext4 and then wipe and repair in my case it has been for example.
as for the IMEI i havent been handson with these subjects so it is better for someone else to inform. This tip can be tried without risk as hopefully the dev rom will restore partitioning, at least it is worth a try.
---------- Post added at 02:56 PM ---------- Previous post was at 02:50 PM ----------
i cant answer your question on the IMEIs since lack of experience on the subject. however what i can say is that freezing and shutdown in stock k3 notes is a common problem and it is not hardware related. Does this problem also occur with a custom rom such as AOSP
Just to give you my total view on fixing the issue hopefully what i would try is:
1. flashing twrp
2.through twrp flashing the latest dev rom
3.reformatting every partition (meaning cache,dalvik cache,system,data,internal storage)
4.flashing a rom such as androim through twrp
5.trying the lost IMEI patch, input your info
6.to be sure use xposed framework uninstaller cause of performance gains
7.eventually using some tweaks such as l speed to get your device optimal
If the issue of freezing and random shutdown was of the same nature it should be solved 100%
http://forum.xda-developers.com/and...ed-thread-lenovo-k3-note-k50-t3158522/page117 latest dev rom
Damn, the official roms are unusable, they keep crashing after like 2-3mins.
Thanks for the link to the rom! I was looking for it for some time. Well, it installed without further complications, now I just need to find out how to restore my IMEIs... Hope at least one of all the methods will work this time.
I've found the answer to all my problems. I need a backup from another K3 Note, manually overwrite the IMEIs with mine and voila, it's supposed to work, at least works on other MTK phones.
If anybody here is willing to help me out please contact me, if you're afraid of sharing your IMEI numbers I can send you mine with an instruction on how to overwrite them, you could save me my phone and some money.
https://www.reddit.com/r/lenovok3no...ei_is_gone_after_installation_of_phoenix_rom/
http://forum.xda-developers.com/k3-note/general/organized-thread-lenovo-k3-note-k50-t3158522
refer this
Hi all,
My lenovo also having same problem..
anyone have a working solution..
pls help..
TQ
invalid imei number problem solved
1. flash new stock rom in ur device.
2. now you have two options
a. you can update your device. ( do all the updates of lollipop but don't upgrade it to marshmallow )
b. you can use the current rom that you have got after flashing.
3. root your device using kingroot app that you can easily find on net.
4. after rooting install chamelephon app on your device from play store.
5. remove the battery and note down the imei numbers written on back of the device.
6. plugin the battery and switch on your device.
7. open chamelephon app.
8. enter the imei numbers.
9. Hit apply new imei option.
10. wait for 1 min.
11. switch off your phone and then switch it on.
12. your sims are ready to work.....
Note ( do not update the device to marshmallow as kingroot app is not able to root lenovo vib marshmallow updated devices.)
Nechoya said:
Hi guys, I got a big big problem with my K3 Note, I think I went too far with wiping partitions before installing a new rom, here are the folders I wiped:
data, cache, system, protect_f, protect_s, dalvik cache.
After reboot my phone worked just fine but it didn't see the simcard, I thought it's the OS issue and wiped and flashed several times more.
Now when I got into the issue I noticed *#06# returns "invalid imei", after a little bit research I found out it's a common issue with MTK phones and found multiple possibilities for solving the problem, none of which worked for me though, for no known reason ;( What I've tried so far is: chamelephon app, MTK Engineer mode commands, flashable ZIP with the IMEIs, writing it with SN write tool and another program named something like Mauri? if I remember correctly, all done on the stock rom flashed with flashtool, now I'm retrying all of above on a custom rom.
I read somewhere that missing basebands can be an issue for MTK engineer mode, but I couldn't find any more info on the topic
I don't know if it is connected but the stock rom worked much worse than I remember when I first got the phone, it freezes completely(doesn't react to power button, keeps the led light after unconnected from charger, completely no response, I have to take out the battery each time) about once every 3-5minutes.
Another thing is, does anybody have any idea what the protect_f and _s folders are? I think I shouldn't have wiped them...
Any help would be much appriciated, I don't need another bricked phone... ;(
Click to expand...
Click to collapse
Himanshu Gusai said:
1. flash new stock rom in ur device.
2. now you have two options
a. you can update your device. ( do all the updates of lollipop but don't upgrade it to marshmallow )
b. you can use the current rom that you have got after flashing.
3. root your device using kingroot app that you can easily find on net.
4. after rooting install chamelephon app on your device from play store.
5. remove the battery and note down the imei numbers written on back of the device.
6. plugin the battery and switch on your device.
7. open chamelephon app.
8. enter the imei numbers.
9. Hit apply new imei option.
10. wait for 1 min.
11. switch off your phone and then switch it on.
12. your sims are ready to work.....
Note ( do not update the device to marshmallow as kingroot app is not able to root lenovo vib marshmallow updated devices.)
Click to expand...
Click to collapse
hi himansu,
can you tell me which stock rom you use.
i try already your solution, but still not working for my phone.
Please help
Dear Nechoya,
I got the exact same problem as I followed your footsteps of wiping too much.
Now my K3 note has NO IMEI and sim says NO SIM CARD INSERTED. I have tried all the usual methods mentioned on various threads but nothing is working for me. Can you please clarify what worked for you with some details. I am not a pro and anything from your side or any of the members reading it will be of immense help.
Thank you.
PS I Dont have any kind of backup
Try lord Arcadius' method.
somyaverma1891 said:
Dear Nechoya,
I got the exact same problem as I followed your footsteps of wiping too much.
Now my K3 note has NO IMEI and sim says NO SIM CARD INSERTED. I have tried all the usual methods mentioned on various threads but nothing is working for me. Can you please clarify what worked for you with some details. I am not a pro and anything from your side or any of the members reading it will be of immense help.
Thank you.
PS I Dont have any kind of backup
Click to expand...
Click to collapse
Never mind... I eventually found LordArcadius method here- https://forum.xda-developers.com/android/help/guide-how-to-fix-unknown-baseband-t3096927
And it is so simple working method that solved this IMEI problem.
Thanks.
I went and did it. I bricked my new phone. I'm in a pickle here and need help desperately. I know I messed up the carrier folder. I have a backup of it, but don't know how to go about restoring it.
The phone turns on and tells me "Unfortunately, the process com.android.phone has stopped" followed by many more apps force closing.
Wifi, data, and signal all do not work. The phone reboots itself before I can do anything.
If I placed the carrier folder inside the system.img that I have backed up and ran the dd command from download mode, would it restore it?
That's just an idea I had that probably won't work. I really freaking out over this.
I've tried using the dd command on my system image already but the problem is still there. Any help would be greatly appreciated.
Edit: Could maybe flashing someone's carrier image work? If anyone has one I would greatly appreciate it. Please help me, I know I can't be the only person whose had this problem.
Edit 2: My wifi is actually working, I somehow didn't see the icon. But no signal barks appear for the cellular connection.
Try doing the TOT method. Completely puts everything back the way it was. if you're on android M use the ZV9 file and if youre on lollipop use the ZV6 one.
Restore with the TOT... there is a thread with instructions in the forums dev section.
From my experiences with the carrier folder. Files in the carrier folder does not get modified/restored when restoring from a tot file. It stays the same from one rom to the next. I had an issue with activation and updating my prl after doing the sim unlock from http://forum.xda-developers.com/sprint-g4/general/guide-sim-unlock-t3229801 but I fixed that issue by changing the permission of node.db and node.db-journal to rwrwrwrw.
Ok, Ladies and Gentleman I need some deep thought processing here for some help with a Motorola Nexus 6. In brief here is what the problem is, a while back when flashing Pure Nexus rom, I experienced a loss of my IMEI. I can restore my IMEI but if and when I do, I lose any 4g and LTE connectivity. The phone functions in 3g with data and phone etc... just slow as molasses but if I restore my IMEI to the one that doesn't show up my IMEI correctly I get back LTE/4g and all works fine also. I've tried going all the way back to the original firmware which was saved to computer and restoring it. Same thing, I have IMEI but no LTE/4g. restore bad efs and get LTE/4g back. I've tried going through all the factory firmware's and flashing by ADB and or TWRP and nothing firmware wise will allow me to restore the IMEI and have LTE/4g signal. If I restore the bad efs and get OOOOOOOO for IMEI when using the *#06# on any firmware version, I regain LTE/4g functioning! I am using Pure Nexus 7.1 now and can still see the 00000000 as a IMEI, if I restore my efs and get IMEI back showing correctly, no LTE/4g signal! My phone can only function as it should as long as the IMEI doesn't show correctly! I have tried just flashing base bands and other segments of any rom and still the problem persist! I have even tried restoring an EFS from another nexus 6 and still no help. It's not the sims because I've tried AT&T sims and Verizon sims from other phones and it does the same thing! I've tried flashing with a sims in the phone and without. Any ideas??? It's like somehow a correlating segment of a file is not being recognized when the correct IMEI is present, like some thing some where in the efs, IMEI, and radio are not taking to each other so to speak, unless it shows the zero's! Brain waves come on and help me out here!!
Have you tried doing a fresh install of a complete factory nexus image? (i.e. entirely wiping the device)
jbaumert said:
Have you tried doing a fresh install of a complete factory nexus image? (i.e. entirely wiping the device)
Click to expand...
Click to collapse
Thanks, and Yes, about 30 different times, using Google developer site original factory firmware, using ADB and or TWRP all the way back to original image, which I have saved as I said in the original post! I don't have a problem restoring IMEI it's just if I do, the phone will not connect to LTE/4g no way no how. I have to have a "0" IMEI for the phone to function as it should actually function and the LTE/4g radio to work, something strange is a miss!
TheWacoKid said:
Thanks, and Yes, about 30 different times, using Google developer site original factory firmware, using ADB and or TWRP all the way back to original image, which I have saved as I said in the original post! I don't have a problem restoring IMEI it's just if I do, the phone will not connect to LTE/4g no way no how. I have to have a "0" IMEI for the phone to function as it should actually function and the LTE/4g radio to work, something strange is a miss!
Click to expand...
Click to collapse
Alrighty, no need to yell.... The factory image is flashed with "fastboot" NOT adb or TWRP. Just wanted to clarify how you were returning the phone to stock.
jbaumert said:
Alrighty, no need to yell.... The factory image is flashed with "fastboot" NOT adb or TWRP. Just wanted to clarify how you were returning the phone to stock.
Click to expand...
Click to collapse
Yes I said thanks because I was yelling! Jezz, get a grip THIS IS YELLING! ADB/Fastboot both tools are used to flash, extract etc.. with your computer, so obviously one cannot flash/restore etc... without using the proper tools via computer!
Try this:
1) Install "Change APN" app from Google store
2) Open ChangeAPN and click the "option" ( the 3 vertical dots) in the upper right-hand corners.
3) click "reset to default"
4) exit the app
5) perform carrier reset ##3282#
6)If needed: after the phone reboots, perform PRL/Device config update. That's it and you should have LTE data.
Dixon Butz said:
Try this:
1) Install "Change APN" app from Google store
2) Open ChangeAPN and click the "option" ( the 3 vertical dots) in the upper right-hand corners.
3) click "reset to default"
4) exit the app
5) perform carrier reset ##3282#
6)If needed: after the phone reboots, perform PRL/Device config update. That's it and you should have LTE data.
Click to expand...
Click to collapse
Thanks! Ok, Itried that, restored my IMEI, "reset APN to default" Tried Carrier reset ##3282# and it says "NO Cellular Network" even though I am showing my network and 3G. So, I rebooted and same thing, went to PRL and tried to update and it says "update error" but it will refresh!
TheWacoKid said:
Yes I said thanks because I was yelling! Jezz, get a grip THIS IS YELLING! ADB/Fastboot both tools are used to flash, extract etc.. with your computer, so obviously one cannot flash/restore etc... without using the proper tools via computer!
Click to expand...
Click to collapse
You clearly don't know the difference between a recovery, the bootloader and the operating system.
ADB is used when the phone is on and is not how you flash a factory image. Fastboot is used in the bootloader and is the proper method of restoring to factory.
admiralspeedy said:
You clearly don't know the difference between a recovery, the bootloader and the operating system.
ADB is used when the phone is on and is not how you flash a factory image. Fastboot is used in the bootloader and is the proper method of restoring to factory.
Click to expand...
Click to collapse
No, I guess not, that's how I've been flashing, restoring and unbricking cells for years, I just don't understand anything!
TheWacoKid said:
No, I guess not, that's how I've been flashing, restoring and unbricking cells for years, I just don't understand anything!
Click to expand...
Click to collapse
You know some magic we don't? There is no way you've flashed a ROM with ADB...
@admiralspeedy
I was very gratified when I noticed that I'd overnight become a Senior Member - until I realised that it had nothing to do with the wisdom I'd imparted in my posts, but only that I'd posted 100. So seniority doesn't imply knowledge, which I think you're beginning to demonstrate in this thread as well as in another where I've seen this same strange unnecessarily belligerent attitude.
TheWacoKid is asking for help, which I'd be happy to offer if I had any ideas. I feel absolutely no desire to tell him that he has no idea what he's doing. And nor should you.
Stop trolling and become a properly-active member of the community.
dahawthorne said:
@admiralspeedy
I was very gratified when I noticed that I'd overnight become a Senior Member - until I realised that it had nothing to do with the wisdom I'd imparted in my posts, but only that I'd posted 100. So seniority doesn't imply knowledge, which I think you're beginning to demonstrate in this thread as well as in another where I've seen this same strange unnecessarily belligerent attitude.
TheWacoKid is asking for help, which I'd be happy to offer if I had any ideas. I feel absolutely no desire to tell him that he has no idea what he's doing. And nor should you.
Stop trolling and become a properly-active member of the community.
Click to expand...
Click to collapse
Actually, I wouldn't have jumped on him like that if he hadn't come out swinging with snarky comments when people tried to help him.
admiralspeedy said:
You know some magic we don't? There is no way you've flashed a ROM with ADB...
Click to expand...
Click to collapse
Look, I came on here to discuss a situation and or problem, which is what I thought this web site was known for, which I havent run into before, in that way not only do I get some help and or suggestions which might help me but help others at the same time who might have the same problem and or will have in the future and find possible solutions! If you don't have anything positive to add to the conversation/situation/problem at hand you are wasting my time, others time and most of all just making a fool out of yourself being childish and immature. Most on here come for solutions not looking to nitpick and try and belittle others like they know everything, which you don't, otherwise you would have given a solution! So you can continue to act like a troll or just leave the situation be and by the way, you ever hear of ADB Sideload??
Use method 2 , you will get everything definitely
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
TheWacoKid said:
Look, I came on here to discuss a situation and or problem, which is what I thought this web site was known for, which I havent run into before, in that way not only do I get some help and or suggestions which might help me but help others at the same time who might have the same problem and or will have in the future and find possible solutions! If you don't have anything positive to add to the conversation/situation/problem at hand you are wasting my time, others time and most of all just making a fool out of yourself being childish and immature. Most on here come for solutions not looking to nitpick and try and belittle others like they know everything, which you don't, otherwise you would have given a solution! So you can continue to act like a troll or just leave the situation be and by the way, you ever hear of ADB Sideload??
Click to expand...
Click to collapse
I'm "belittling" you because your first two replies to someone who tried to help you were snarky and rude. In your own words, get a grip.
admiralspeedy said:
Actually, I wouldn't have jumped on him like that if he hadn't come out swinging with snarky comments when people tried to help him.
Click to expand...
Click to collapse
Time for you to go back and read some more...
You can flash a ROM with adb... Now unless you can help him... Shaddyup
rignfool said:
Time for you to go back and read some more...
You can flash a ROM with adb... Now unless you can help him... Shaddyup
Click to expand...
Click to collapse
No, you can use ADB sideload to flash a ROM which requires you to be in the recovery. Standard ADB cannot be used to flash a ROM.
admiralspeedy said:
I'm "belittling" you because your first two replies to someone who tried to help you were snarky and rude. In your own words, get a grip.
Click to expand...
Click to collapse
Amazing to any one with half a brain how you a Troll can think from typed response that someone is yelling, swinging, snarky and rude but your the one with an attitude that is all the above because like I said your a childish troll! I can't believe this site would even allow someone like you to be a member paid or otherwise! Your attitude is all your own and based on your own weak assumptions! Now go back to playing with your legos!
drmuruga said:
Use method 2 , you will get everything definitely
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
Thanks, I've used both of those methods, I have even tried just flashing individual parts all by themselves to see if just one part would give an error of some kind while flashing, no errors on any flash of any kind, the only difference being that if I read them correctly that on those methods it said to wipe data factory reset in recovery, before reboot, the Flashall bat file reboots automatically into image just flashed, I usually reboot as last command, if that makes any difference, I've even tried wiping then just flashing the new bootloader after a wipe, because it basically acts like a security checkpoint and partition manager, then rebooting and flashing the rest of one of the google firmware versions for the nexus 6.
TheWacoKid said:
Thanks, I've used both of those methods, I have even tried just flashing individual parts all by themselves to see if just one part would give an error of some kind while flashing, no errors on any flash of any kind, the only difference being that if I read them correctly that on those methods it said to wipe data factory reset in recovery, before reboot, the Flashall bat file reboots automatically into image just flashed, I usually reboot as last command, if that makes any difference, I've even tried wiping then just flashing the new bootloader after a wipe, because it basically acts like a security checkpoint and partition manager, then rebooting and flashing the rest of one of the google firmware versions for the nexus 6.
Click to expand...
Click to collapse
So was there a solution? The thread just ended. I also have this problem but I'm no where as technical as thewacokid.
But I do know how to follow steps
Hey guys, recently I broke my A2's screen (again) and ordered a replacement from China.
I installed it, booted the system and updated to Android 10 immediately.
Everything seemed to be working, but I noticed that the GPS is now useless.
I mean, it manages to pinpoint exactly at my house, but If I set a route, it just doesn't work, it remains stuck.
If I leave the house (and, therefore, begin to rely on mobile data), the precision vanishes completely and it just won't find me.
This behaviour is strange, since mobile data is working normally, and he can pinpoint my location at home quite precisely, compass apparently working, but outside it won't work at all, it can't detect any kind of movement, even if placing me somewhere else.
I have two hyphotheses:
1) The sensor broke?
The screen broke in the bottom of the phone, nasty break, but it wasn't a fall. An item pressed against it in a purse.
Maybe this time the sensor broke? Is it possible to buy parts and fix it?
2) Could this have something to do with this update? I reseted the phone to factory, but it's still Android 10...
Any other report like this? I should try downgrading to Android 9 right?
What do you guys think?
Just some updates:
I tried Android 9 and GPS still doesn't work.
The sensor is probably fine, but something happened while changing the screen.
I saw a report that says that changing back to old screen fixed the GPS issue. I can't do this because I throwed the broken screen in the trash.
Hey guys, can anyone say which replacement piece must be used to fix this issue?
Could it be the lower dock board, or the mainboard, or a single module? I could try to buy it from aliexpress and repair the phone...
Both GPS and Bluetooth don't work. I need to know which part of the hardware is related to these functions. Can't find anything online.
Edit: bluetooth is ok actually.
valp88 said:
Hey guys, can anyone say which replacement piece must be used to fix this issue?
Could it be the lower dock board, or the mainboard, or a single module? I could try to buy it from aliexpress and repair the phone...
Both GPS and Bluetooth don't work. I need to know which part of the hardware is related to these functions. Can't find anything online.
Click to expand...
Click to collapse
when you change from pie to Q(10) your gps / compass or other sensors don't work correctly because your persist partition that controls how these hardware sensors interact with rom.gets corrupted
search my older posts around related to restoring your persist partition and it will likely start working
ive never heard of any gps or compass attached to the screen or digitizer ...
it's not impossible that a hard jarring knock to break the connection to your compass or gps i guess
you can "locate" at home because google location history remembers where you were when last connected to your home wifi ... Google is "locating" you using the wifi at your house ...when you go walkabout and your wifi connection gets lost google doesn't know where you've gone
if you had to go to advanced settings and allowed wif, Bluetooth and mobile scanning in advanced location settings google would probably find you even with a broken gps and compass as long as you have some mobile data
but anyway restore your persist
if it fails
live with mobile data as location method
or go visit your local phone repairman and give him your money
KevMetal said:
when you change from pie to Q(10) your gps / compass or other sensors don't work correctly because your persist partition that controls how these hardware sensors interact with rom.gets corrupted
search my older posts around related to restoring your persist partition and it will likely start working
ive never heard of any gps or compass attached to the screen or digitizer ...
it's not impossible that a hard jarring knock to break the connection to your compass or gps i guess
you can "locate" at home because google location history remembers where you were when last connected to your home wifi ... Google is "locating" you using the wifi at your house ...when you go walkabout and your wifi connection gets lost google doesn't know where you've gone
if you had to go to advanced settings and allowed wif, Bluetooth and mobile scanning in advanced location settings google would probably find you even with a broken gps and compass as long as you have some mobile data
but anyway restore your persist
if it fails
live with mobile data as location method
or go visit your local phone repairman and give him your money
Click to expand...
Click to collapse
I see. Even a stock update from 9 to 10 could've broken my persist data then?
I went back to Pie stock and had no luck, then stock-updated to 10 again.
If this were software/corruption related, then going back to Pie stock would've fixed right?
I'll try to flash that persist data, but I have no backups.
I searched for your posts and couldn't find your guidance, but found this:
https://forum.xda-developers.com/mi-a2/how-to/how-to-fix-sensors-camera-stock-pie-10-t3914885
I'll give it a try.
KevMetal said:
when you change from pie to Q(10) your gps / compass or other sensors don't work correctly because your persist partition that controls how these hardware sensors interact with rom.gets corrupted
search my older posts around related to restoring your persist partition and it will likely start working
ive never heard of any gps or compass attached to the screen or digitizer ...
it's not impossible that a hard jarring knock to break the connection to your compass or gps i guess
you can "locate" at home because google location history remembers where you were when last connected to your home wifi ... Google is "locating" you using the wifi at your house ...when you go walkabout and your wifi connection gets lost google doesn't know where you've gone
if you had to go to advanced settings and allowed wif, Bluetooth and mobile scanning in advanced location settings google would probably find you even with a broken gps and compass as long as you have some mobile data
but anyway restore your persist
if it fails
live with mobile data as location method
or go visit your local phone repairman and give him your money
Click to expand...
Click to collapse
By the way, can I restore the persist from the file you provided in https://forum.xda-developers.com/mi...mi-a2-4-32-t4100729/post82612405#post82612405
in the latest OTA (11.0.6 if I'm not mistaken)? Or could that mess up the system?
valp88 said:
By the way, can I restore the persist from the file you provided in https://forum.xda-developers.com/mi...mi-a2-4-32-t4100729/post82612405#post82612405
in the latest OTA (11.0.6 if I'm not mistaken)? Or could that mess up the system?
Click to expand...
Click to collapse
sure go ahead , doesn't touch system nor data
KevMetal said:
sure go ahead , doesn't touch system nor data
Click to expand...
Click to collapse
Hi, I have encountered the same issue here : I finally replaced my LCD screen on a Xiami Mi A2 (6/128), and made attention that everything was in place when reassembling the device, a couple of weeks ago.
Due to the lockdown I didn't use the GPS for monthes, but realized last sunday that the GPS couldn't "FIX" position, I always have 0 | 56 satellites. As if it didn't want to "connect" to the satellites, so the GPS accuracy is from more than 1Km to 23m depending if I'm near a WiFi network... My wife has the Mi A1 version and still she didn't succeed in getting an accurate GPS location (she finally got one nearly 1h later), so this made me think that the GPS issue might indeed be caused by a corrupted persist partition when applying the official OTA Android 10 update... :crying:
I've tried everything (from various GPS rescue apps from the Play Store, to factory reset my stock ROM), and finally switched to a custom ROM (AICP, Android Ice Cold Project, which is really nice BTW), but nothing changed regarding my GPS fix issue.
I've followed this thread and patched the persist good.zip file in TWRP, and even if it might have somehow helped with 4G/LTE mobile network connection, I still can't get a proper GPS location... maybe I should try with the "persist" of another version of stock ROM (I'm on Android 10 BTW)?
Anyway, I'll keep on trying to fix this as I'm really satisfied with this phone. So, just to say, you're not alone @valp88, and thank you all (especially @KevMetal) for your help!
---------- Post added at 02:13 PM ---------- Previous post was at 02:04 PM ----------
Maybe I should just retry on stock Pie ROM? As explained here on step 1 : https://forum.xda-developers.com/mi-a2/how-to/how-to-fix-sensors-camera-stock-pie-10-t3914885
PsK2010 said:
Hi, I have encountered the same issue here : I finally replaced my LCD screen on a Xiami Mi A2 (6/128), and made attention that everything was in place when reassembling the device, a couple of weeks ago.
Due to the lockdown I didn't use the GPS for monthes, but realized last sunday that the GPS couldn't "FIX" position, I always have 0 | 56 satellites. As if it didn't want to "connect" to the satellites, so the GPS accuracy is from more than 1Km to 23m depending if I'm near a WiFi network... My wife has the Mi A1 version and still she didn't succeed in getting an accurate GPS location (she finally got one nearly 1h later), so this made me think that the GPS issue might indeed be caused by a corrupted persist partition when applying the official OTA Android 10 update... :crying:
I've tried everything (from various GPS rescue apps from the Play Store, to factory reset my stock ROM), and finally switched to a custom ROM (AICP, Android Ice Cold Project, which is really nice BTW), but nothing changed regarding my GPS fix issue.
I've followed this thread and patched the persist good.zip file in TWRP, and even if it might have somehow helped with 4G/LTE mobile network connection, I still can't get a proper GPS location... maybe I should try with the "persist" of another version of stock ROM (I'm on Android 10 BTW)?
Anyway, I'll keep on trying to fix this as I'm really satisfied with this phone. So, just to say, you're not alone @valp88, and thank you all (especially @KevMetal) for your help!
---------- Post added at 02:13 PM ---------- Previous post was at 02:04 PM ----------
Maybe I should just retry on stock Pie ROM? As explained here on step 1 : https://forum.xda-developers.com/mi-a2/how-to/how-to-fix-sensors-camera-stock-pie-10-t3914885
Click to expand...
Click to collapse
my suggestion is using the recovery image(,twrp) i provided and not any other
reason: because it will allow you to flash an image directly to persist..
furthermore the correct or best procedure is to download a fastboot stock rom of whatever version STOCK not custom is on your phone but that matches exactly ..then unzip with 7zip and take the persist.img file ..put it on your pc or internal storage and flash with the recovery i provided by choosing
install ..select image option ..browse to image ...select persist partition
failing this (error message) the ACTUAL and best solution that works ?% but is not easy is to take a fastboot stock rom and then using fastboot put your phone into edl mode :
fastboot oem edl
then flash the whole stock rom using Xiaomi miflash ..in fastboot mode miflash doesn't have the required permissions to flash secure partitions ..in oem edl mode ( Qualcomm) it is deep flash .. NOW the bigger problem and difficult part is that xiaomi themselves modified the flash xml ( that tells miflash what to flash NOT to flash persist EVEN if there is a persist.img in the folder ) so you need to manually modify certain lines in the xml so miflash flashes the persist img files
**although the flashable persist restorer zip works occasionally it has failed in others or worked only temporarily and if you went from pie to Q the chances of failure are even higher
and by the way if the persist restore is done successfully it does fix gps issues
as a workaround ...if gps works but not well ..use magisk gps module to replace global gps file ..
if gps shows 0 action you need to do the miflash option ..there is always also the possibility that you damaged hardware while replacing screen or that you disconnected something and failed to reconnect it properly ..
---------- Post added at 02:17 PM ---------- Previous post was at 02:02 PM ----------
so 100% fix ... following on my previous post do this using a pie fastboot stock rom for your device together with my miflash
Download XiaomiADBFastbootTools.jar https://github.com/Saki-EU/XiaomiADBFastbootTools/releases/tag/3.0.2 Credits: Saki-EU
Java run-time environment is required https://java.com/en/download/
Now extract the fastboot rom and locate rawprogram0.xml inside images folder. Edit it with Notepad++ and search for persist. You will see it among line 57 with filename="" . Add persist.img inside quotation marks. So final will be like filename="persist.img"
Now save it.
Now power on the phone while pressing volume down button in order to get into fastboot menu.
While in fastboot menu, connect your phone to pc and run XiaomiADBFastbootTools.jar
Click on menu--> Check for device , when device is found click menu-->Reboot device to edl
Now run XiaoMiFlash.exe and press refresh. device will be detected as com , where n is the port number. If device is not detected, click on driver menu on miflash and reinstall driver.
Now select the extracted fastboot rom folder. click clean all and click flash.
It takes some time to flash and when flashing is done reboot device by long pressing power button for 10-20 Seconds.
---------- Post added at 02:21 PM ---------- Previous post was at 02:17 PM ----------
***keep in mind that the phone only starts working correctly after 4-5 reboots and a 1 day or 2 after restoring persist and so random sensor stuff is usual ...give it a day or so and be patient with random behaviour for a day ..like reboots and wifi or gps trouble ...this is regardless of the root you took
PsK2010 said:
Hi, I have encountered the same issue here : I finally replaced my LCD screen on a Xiami Mi A2 (6/128), and made attention that everything was in place when reassembling the device, a couple of weeks ago.
Due to the lockdown I didn't use the GPS for monthes, but realized last sunday that the GPS couldn't "FIX" position, I always have 0 | 56 satellites. As if it didn't want to "connect" to the satellites, so the GPS accuracy is from more than 1Km to 23m depending if I'm near a WiFi network... My wife has the Mi A1 version and still she didn't succeed in getting an accurate GPS location (she finally got one nearly 1h later), so this made me think that the GPS issue might indeed be caused by a corrupted persist partition when applying the official OTA Android 10 update... :crying:
I've tried everything (from various GPS rescue apps from the Play Store, to factory reset my stock ROM), and finally switched to a custom ROM (AICP, Android Ice Cold Project, which is really nice BTW), but nothing changed regarding my GPS fix issue.
I've followed this thread and patched the persist good.zip file in TWRP, and even if it might have somehow helped with 4G/LTE mobile network connection, I still can't get a proper GPS location... maybe I should try with the "persist" of another version of stock ROM (I'm on Android 10 BTW)?
Anyway, I'll keep on trying to fix this as I'm really satisfied with this phone. So, just to say, you're not alone @valp88, and thank you all (especially @KevMetal) for your help!
---------- Post added at 02:13 PM ---------- Previous post was at 02:04 PM ----------
Maybe I should just retry on stock Pie ROM? As explained here on step 1 : https://forum.xda-developers.com/mi-a2/how-to/how-to-fix-sensors-camera-stock-pie-10-t3914885
Click to expand...
Click to collapse
duh stupid ...i forgot to mention that if you have jasmime 2x of all partition ...you need to flash the persist in both A&B slots
so after flashing in slot A select slot b in reboot section..reboot to RECOVERY ..then flash persist again ...the in reboot section select slot A amd revoot to recovery then when you are now safely back in slot A choose reboot to boot your phone normally
i failed to mention this because im on wayne which is the same phone but with a A only partition ..
:silly:
Yeah I think I did flash the persist on both A and B slots, anyway, I tried it again, but even if it seems to flash I have an error 'unable to mount storage', maybe it's due to the "twrp-3.3.1-5-jasmine_sprout-unofficial.img" I'm booting on (I boot from the img file, with fastboot boot command).
If I still have the GPS fix issue, I'll try flashing persist on both slots but this time using the default twrp (twrp-3.3.1-3-jasmine_sprout.img).
Again, thank you for your time!
PsK2010 said:
Yeah I think I did flash the persist on both A and B slots, anyway, I tried it again, but even if it seems to flash I have an error 'unable to mount storage', maybe it's due to the "twrp-3.3.1-5-jasmine_sprout-unofficial.img" I'm booting on (I boot from the img file, with fastboot boot command).
If I still have the GPS fix issue, I'll try flashing persist on both slots but this time using the default twrp (twrp-3.3.1-3-jasmine_sprout.img).
Again, thank you for your time!
Click to expand...
Click to collapse
if your gps problem continues I would suggest flashing the whole stock rom in edl mode with xml modified to flash persist and then it will definitely work but as we're both aware that is a mission you probably don't want to have to do d
the reason the unofficial twrp exists is because the official one has problems and has never "officially" been fixed entirely to support encryption on both pie and Q
I'm also pretty certain it can't "see" nor backup or mount and definitely not write to the persist partition but i haven't checked recently
if you go to the backup tab or mount tab and persist doesn't appear as an option the recovery can't write or flash anything to that partition usually
the recovery i linked was modified by a Russian over at 4pda to specifically support .img files and also mount and write to persist partition
you can change the language from Russian in the settings tab ..second from the bottom right
Hey, after reverting back to Stock Pie (with flashing the persist from the official stock image thanks to @KevMetal's instruction), I still didn't got a good GPS reception (0/40 satellites) and noticed that bluetooth reception was weaker than before I replace my screen.
I then dediced to disassemble the phone again to check the antenna and other connections, and then realized : some parts were missing in the replacement frame I bought!
As you can see on the picture, some metallic contacts were were missing on the new screen support frame (old frame below the new one), I just got them off my broken screen support, stick them in the new support frame and BOOM : I FINALLY GOT BACK GPS SIGNAL + awesome bluetooth signal too!