Related
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.
Hi Guys,
I think I have no lucky these days...
I was testing a new ROM and when a returned the backup with TWRP android asked me a patteren for unlock.
The patter I usauly use dont work.
I found a help that say to erase some files in /data/system but it doenst work...
I had a idea to block the cell with my google account and set a new PIN for unnlock... It doenst work
Now I have the cell blocked by google and its impossible to access the internal memory with TWRP...
I need help... I dont know what to do...
Please !!!!
Sounds like your only way back is to format/delete all your data and start from scratch. You can use fastboot to do this.
I think this is the way... but I never did this before...
Do you know a step by step to do this !?
If I understand rightly you have a Google locked phone. I have not tried this on the OP3T but if you are able to reach the boot up screen where Google asks you for the password/pattern lock, you can try inserting an OTG drive of any capacity into your device. The phone will ask for changing storage. After clicking 'OK' you will be taken to the storage section. Go to 'Apps' and from there to 'Setting'. If you are able to reach this far, do a complete reset from that 'Settings' section and you would be able to recover your phone. I repeat, I have not tried this on the OP3T but have successfully tried this on some other phones. Best of luck and hope you get back your toy.
Let me also add that you won't be able to recover a Google blocked phone by factory resetting from recovery. The only way to do this is to reset it from the settings section of the OS itself after you have booted up.
shantanil said:
If I understand rightly you have a Google locked phone. I have not tried this on the OP3T but if you are able to reach the boot up screen where Google asks you for the password/pattern lock, you can try inserting an OTG drive of any capacity into your device. The phone will ask for changing storage. After clicking 'OK' you will be taken to the storage section. Go to 'Apps' and from there to 'Setting'. If you are able to reach this far, do a complete reset from that 'Settings' section and you would be able to recover your phone. I repeat, I have not tried this on the OP3T but have successfully tried this on some other phones. Best of luck and hope you get back your toy.
Let me also add that you won't be able to recover a Google blocked phone by factory resetting from recovery. The only way to do this is to reset it from the settings section of the OS itself after you have booted up.
Click to expand...
Click to collapse
Perfect!
I did exactly this and now I recovery the cell...
Thanks a lot!
You save my day!
Hi everybody, I don't know if this will help all you but this is what worked for me (Android 6.0.1):
1. On the setup wizard (after factory wipe), connect to internet (wifi/data)
2. Select "Emergency call"
3. Call to any valid number (112 for example)
4. When the calls start swipe to the left on the dialing screen and you will see message and browser displayed (in my case the message method doesn't works).
5. Select browser.
6. Go to google.
7. Search for Package Disabler Pro 9.8
8. Download it and install it.
9. Open it and search for "Samsung account".
10. Click on Clear Data and then Disable.
11. Go back to google and search for QuickShortMaker
12. Install it and open it.
13. Search for "Setup Wizard", it will expand.
14. Select the one with ".setupwizards.SetupExitActivity"
15. Done! You can now use the phone and restart.
Ok after this you can go and check that there is no Samsung account displayed (Settings>Accounts), buuuuut, you can't add it . What I did was:
1. Go back to Package Disabler Pro and enabled "Samsung Account".
2. Then go to Settings>Back up and reset
3. Factory data reset
4. Asked for Samsung account and I inserted my real account.
5. Done, now I can sync with my account.
The oooooooonly issue that I can't figure out it's the way to remove the "Reactivation lock" from Settings>Lock screen and security>Find my mobile.
Well that's all hope it works for you guys.
If this doesn't work for you, you can check out unlockjunky, they will definitely be able to do it.
Good luck!!
xxspokiixx said:
Hi everybody, I don't know if this will help all you but this is what worked for me (Android 6.0.1):
4. When the calls start swipe to the left on the dialing screen and you will see message and browser displayed (in my case the message method doesn't works).
Click to expand...
Click to collapse
when i'm calling i cannot swipe to the right. Is there anyother way to open the browser?
112
What ever you do, absolutely do not dial for example ( 112 )
Turns out 112 will connect you to your local emergency dispatch.....
Ask me how I know...
please change your number in the above post for newbies who may be trying to learn and have no clue what these phones are capable of...
Thanks
xxspokiixx said:
Hi everybody, I don't know if this will help all you but this is what worked for me (Android 6.0.1):
Click to expand...
Click to collapse
Mate, you are an absolute legend! I've been searching for 8hrs looking for a solution after hard resetting my phone and being unable to get past the Samsung Account lock afterwards (even though I had the right username & password!) About fifty useless/outdated YT videos & a few hundred websites/forums later - none of which were helpful, I finally stumbled across your post, despite it not showing up 8hrs ago when I came straight to XDA hoping to find a solution first.
I have an improved method for #2, 3 & 4 of your post and will add all relevant info soon (just need some kip now that the panic is over). I'll also expand a little on some details and include further options which worked in my particular case, but all n'all - you're an absolute legend mate and I'd be screwed & still panicking without your shared info. Huge thanks...
Nice meme dude ya got me
Nomak1835 said:
What ever you do, absolutely do not dial for example ( 112 )
Turns out 112 will connect you to your local emergency dispatch.....
Ask me how I know...
please change your number in the above post for newbies who may be trying to learn and have no clue what these phones are capable of...
Thanks
Click to expand...
Click to collapse
AGREED!!!!!!!!! DO NOT DIAL 112!!!!!! It switches to 911... not a funny joke
Nomak1835 said:
What ever you do, absolutely do not dial for example ( 112 )
Turns out 112 will connect you to your local emergency dispatch.....
Ask me how I know...
please change your number in the above post for newbies who may be trying to learn and have no clue what these phones are capable of...
Thanks
Click to expand...
Click to collapse
You have to dial an emergency number or this trick doesn't work. Its not practical for most folks but if you are worried about dialing an emergency number I'd recommend using a SIM out of a tablet that isn't phone number enabled.
its working for j7 prime bypass samsung account
Hi, First of all thanks for this thread. i made it to #8 but when i download the apk and i cant figure out how to install it to complete steps 9 and 10. Maybe i'm over looking something im not sure but i need help.
TIA
Beasy936 said:
Hi, First of all thanks for this thread. i made it to #8 but when i download the apk and i cant figure out how to install it to complete steps 9 and 10. Maybe i'm over looking something im not sure but i need help.
TIA
Click to expand...
Click to collapse
Look for Aptoide apk download it to sd card and search for package disabler in this app and install it or download and copy Pachkage disabler you your sd card and run via file explorer or download and run ES File manager as I did.
when i make the call my wifi gets turned off and wont come back on till i restart the phone. i managed to open the browser but the wifi is off so i cant do anything after that except cry.
stock 5.0
Did you get it figured out I got the edge 6 plus to work fine now it was one of the tougher ones and I've done a few on some newer models what are you stuck on?
I thought the Combination Firmware would reset the FRP lock by default after being installed.
first thank you for sharing ur experience and i want to add
that i done it step by step and it works nicely but still cant remove the reactivation
and here is how iv done it after i bypassed it using ur method
i flashed a lower modem file from stock rom N910VVRU2BOG5 which is 5.0.1
at this point my imei went off
so i went for full flash by N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME. which is 5.1.1 and did full hard reset
then i just signed in with the last Samsung account i used with ur method earlier and it passed so now i can easly remove reactivation mark , unlock and root then make it Arabic .
thx again
Did you ever post up the suggested steps to replace #'s 2-4 in the original post above? I'm not seeing them anyplace. This would be a big help. Thanks.
When I call I can't swipe to the right is there another way to open browers
I successfully used this to gain access to my phone but I believe that if I power cycle it I will be locked out again. Is there any way to remove or change the samsung account now that I am in? The options are greyed out in settings.
ADB and Root.
Hey, I have been working on these for a while keep finding new things each time I try to remove Reactivation Lock. However I was wondering if I show you guys how to enable ADB with RSA Key, and Root the device. Could someone show me how to remove the Reactivation Lock using root. I used other methods on older and newer models, but these S5's are the only ones giving me issues.
After weeks of going mad trying different solutions I've found online, here's what worked 100% for me just last night:
Login to Samsung Account on other device, select Password & Security, enter password then choose Devices. LOG-OUT of your S6 Edge if listed, confirm. Next change password - doesn't matter what, can even change it back afterwards.
Flash Lollipop (I used G925VVRU4BOK7)
Wipe Data/Cache
Boot fresh Stock firmware, enter/confirm network details, at Reactivation Lock prompt, enter user & updated password. Sign-in....
Settings -> Lock Screen & Security -> Find My Mobile. Unselect Reactivation Lock and enter password... voila!
Works for anybody else??
when i made the call the wifi turn of
Using Odin files to update a Samsung AT&T model will almost always result in a factory reset being performed, and I've also seen the same thing happen when trying to update via OTA zip in Recovery. I'm providing this package for anyone still using the S5, to be able to update software without needing to do a factory reset. I have personally verified that these files will perform the update without wiping any data. These files will update you to the Build/Baseband ending in QD1, Android 6.0.
My zips are compressed extra small for space and bandwidth savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc.
Happy flashing!
https://www.androidfilehost.com/?fid=1899786940962576350
Worked great..Thanks! But....
You are theman for this! I have a 900A AT&T and have struggled for days to get it unlocked, upgraded and working without tripping the secure software alert. I started with a 4.X maintenance OS, then rooted, SafeStrapped then pushed this update via ODIN and it worked. Now, the only issue i am having is apps crashing continuously. Started with google play and play services now spreading. I ASSUME this is due to apps not getting updated in the update to 6.X. Correct me if I am wrong. I have updated those via APKs along with others to new versions yet it still happens. Now its also Chrome, File manager etc. Is this maybe a code bug, or am I missing something here? Thanks again
3rdRockfromSun said:
You are theman for this! I have a 900A AT&T and have struggled for days to get it unlocked, upgraded and working without tripping the secure software alert. I started with a 4.X maintenance OS, then rooted, SafeStrapped then pushed this update via ODIN and it worked. Now, the only issue i am having is apps crashing continuously. Started with google play and play services now spreading. I ASSUME this is due to apps not getting updated in the update to 6.X. Correct me if I am wrong. I have updated those via APKs along with others to new versions yet it still happens. Now its also Chrome, File manager etc. Is this maybe a code bug, or am I missing something here? Thanks again
Click to expand...
Click to collapse
No idea. Can't really diagnose app crashes - too many possibilities.
Also: hopefully you're now aware that you're not rooted any longer and (probably) can't ever root it again
iBowToAndroid said:
No idea. Can't really diagnose app crashes - too many possibilities.
Also: hopefully you're now aware that you're not rooted any longer and (probably) can't ever root it again
Click to expand...
Click to collapse
Yeah I saw that, but thats ok. My biggest objective is to get it unlocked from AT&T so I can use it (this whole venture has just turned into a learning/fun toy to play with now) on my carrier. That is yet TBD. Any thoughts on that?
3rdRockfromSun said:
Yeah I saw that, but thats ok. My biggest objective is to get it unlocked from AT&T so I can use it (this whole venture has just turned into a learning/fun toy to play with now) on my carrier. That is yet TBD. Any thoughts on that?
Click to expand...
Click to collapse
https://www.att.com/deviceunlock/
Thanks in advance for any help, short version at top, details below.
-- Short version:
Please help me recover my data, and phone if possible.
I need the data, esp texts and notes, for both personal (some family members have passed on) and business.
I have a new Galaxy S21 and / or PC Smart Switch ready to receive data backup if we can evacuate it from the S5.
ODIN flash seems to pass but has 'Resizing Data' fail, and phone still won't boot past AT&T logo screen.
All web searches seem to say Factory Reset is my last option, but I don't want to lose the data.
Please share ANY advice on how I can recover the data.
-- More details:
Phone = SM-G900A Samsung Galaxy S5 AT&T
Use = pristine, never rooted, modded, or unfortunately backed up
Status = will not boot, passes screen 1 'Galaxy S5', screen 2 'Samsung script', then stops on screen 3 'AT&T globe logo'
More details = Used clean for ~7 years, then on day x, saw phone automatically complete a system update (green screen, sprockets, "your phone is updating"), which was surprising as it's years after it is no longer supported by AT&T. After that update, I continued to use the phone that day, but it then rebooted automatically and stuck on the AT&T globe logo.
Attempts to fix = soft reset, battery pull, can't get into SAFE MODE, can get into and out of recovery mode, found this firmware (THANKS @iBowToAndroid), used multiple ODIN (Odin3 v3.13.3_3B_PatcheD, Odin3 v3.14.1_3B_PatcheD) to flash it (my first Android flashing experience). On flashing process, ODIN on PC shows 'PASS' and log shows "<OSM> All threads completed. (succeed 1 / failed 0)", but phone shows 'Resizing Data' failed:
"
Supported API: 3
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Successfully installed package.
-- Resizing Data...
Can't open dir '/data/user/0/com.sec.knox.bluetooth' (Permission denied)
E:failed the resizing-data
"
PFA screen shots
Martin2019 said:
Thanks in advance for any help, short version at top, details below.
Click to expand...
Click to collapse
Trying the "wipe cache partition" is the only thing I can think of
iBowToAndroid said:
Trying the "wipe cache partition" is the only thing I can think of
Click to expand...
Click to collapse
Short version:
THANKS for the quick reply, very much appreciate your help.
Am I really left with only a Factory Reset and then trying to use Data Recovery software to get ‘some’ data back?
I really don't want to give up on the data, so I'm still trying anything I can think of in research and repeated attempts.
More details:
I have tried the recovery mode 'Wipe cache partition' option before and after using ODIN.
I've tried doing it 'twice' per recommendation of some of the web advice I've read in trying to research this.
I've noticed that sometimes the colored highlight of the 'Reboot to bootloader' option then turns background green instead of usual blue, but I don't know why, or if that matters.
Still, the ODIN flash effort always returns the permission error, and the boot always sticks on the AT&T logo.
The string seems to indicate a 'user data' permission error?
Is there any way to debug the logic of the firmware or slog through the 'Recovery Logs' to determine and resolve the cause of the permission error?
When the problem began, I had an SD card and SIM card loaded.
I've since removed both in trying to address this, also per 'web advice'.
Any chance putting them back in helps somehow?
Any other options available via apply update from SD card or ADB?
Any way to setup the Android OS as a secondary drive to another machine to pull data out that way?
I've done similar things with Windows OS in PC environment, but I'm not seeing anyone trying that with Android.
If I am really stuck with factory reset, are there any data recovery programs I could try afterward that work with the G900A?
So far I've looked at Dr Fone, Tenorshare, EaseUS, FonePaw, and D-Back, and none seem to work with the AT&T model variant.
Maybe that's just because they don't have access to AT&T firmware available to install, but if I clear the stuck boot via FR, they then might be able to get some of my data back via drive scan - whatever data is not truly overwritten by the FR?
Martin2019 said:
Short version:
THANKS for the quick reply, very much appreciate your help.
Am I really left with only a Factory Reset and then trying to use Data Recovery software to get ‘some’ data back?
I really don't want to give up on the data, so I'm still trying anything I can think of in research and repeated attempts.
More details:
I have tried the recovery mode 'Wipe cache partition' option before and after using ODIN.
I've tried doing it 'twice' per recommendation of some of the web advice I've read in trying to research this.
I've noticed that sometimes the colored highlight of the 'Reboot to bootloader' option then turns background green instead of usual blue, but I don't know why, or if that matters.
Still, the ODIN flash effort always returns the permission error, and the boot always sticks on the AT&T logo.
Click to expand...
Click to collapse
I own and run a business that performs SIM unlocking and other software-related services for mobile devices, so we see situations like yours quite a bit. And I don't know of anything else that you can do. From reports, we've heard that none of those "recovery services" actually work to recover any data, after a reset
iBowToAndroid said:
I own and run a business that performs SIM unlocking and other software-related services for mobile devices, so we see situations like yours quite a bit. And I don't know of anything else that you can do. From reports, we've heard that none of those "recovery services" actually work to recover any data, after a reset
Click to expand...
Click to collapse
Disappointing to hear bad news, but appreciate your effort and insight in providing it, thanks.
I've learned alot in researching it.
I just wish I'd known it before the problem, which I'm sure you also hear quite a bit.
Please let me know if you think of anything else I can try.
Martin2019 said:
Disappointing to hear bad news, but appreciate your effort and insight in providing it, thanks.
I've learned alot in researching it.
I just wish I'd known it before the problem, which I'm sure you also hear quite a bit.
Please let me know if you think of anything else I can try.
Click to expand...
Click to collapse
You can never trust a mobile device 100%, especially not one that's 7 years old. That's why anything that's that important needs to be backed up at all times
iBowToAndroid said:
You can never trust a mobile device 100%, especially not one that's 7 years old. That's why anything that's that important needs to be backed up at all times
Click to expand...
Click to collapse
Totally agree, and totally on me for not having a backup.
I was just foolish enough to not know yet how easy it is to back up.
Give me 10 minutes of life again now in this phone, I use Smart Switch to backup, and I'm off to a new phone, or even FR on this one and reload.
Now where did I put my Delorean...
iBowToAndroid said:
You can never trust a mobile device 100%, especially not one that's 7 years old. That's why anything that's that important needs to be backed up at all times
Click to expand...
Click to collapse
Have you ever tried a 'combination key' approach to get data access?
As in...
Smart Switch on PC won't connect, but ODIN does show 'Added'.
I don't understand the granular details, but hoping you might...
Could we use both Smart Switch and ODIN in some combination sequence that would allow Smart Switch to pull the data off to a Smart Switch PC backup that I could then throw onto a new phone?
When it's in Downloading (firmware flashing) mode, a modem port is used. The modem port is also there when the device is booted up in Normal mode, but that's not useful for extracting any data off of it. I don't know what Smart Switch uses, but I would assume File Transfer (MTP) and/or ADB. And those aren't fully functional until the device fully boots up.
Do you have a screen lock on the device?
iBowToAndroid said:
When it's in Downloading (firmware flashing) mode, a modem port is used. The modem port is also there when the device is booted up in Normal mode, but that's not useful for extracting any data off of it. I don't know what Smart Switch uses, but I would assume File Transfer (MTP) and/or ADB. And those aren't fully functional until the device fully boots up.
Do you have a screen lock on the device?
Click to expand...
Click to collapse
No lock on device, just swipe to go from 'lock screen' to home screen, prior to this boot problem obv.
One of the data recovery sw that I tried (EaseUS I think) did reach a screen asking me to enable USB debugging to continue, but I don't think I can do that without booting up.
I 'think' I remember that screen saying something like 'MTP device' connected, when it asked me to do that.
Any way to sneak into MTP mode from that?
Martin2019 said:
No lock on device, just swipe to go from 'lock screen' to home screen, prior to this boot problem obv.
One of the data recovery sw that I tried (EaseUS I think) did reach a screen asking me to enable USB debugging to continue, but I don't think I can do that without booting up.
I 'think' I remember that screen saying something like 'MTP device' connected, when it asked me to do that.
Any way to sneak into MTP mode from that?
Click to expand...
Click to collapse
Any 3rd party software will require ADB to be enabled. Smart Switch is the only one that *might* work just over MTP, but I'm pretty sure MTP doesn't fully load until the device is booted. Even if it did, you would likely need to allow on the popup message. Does the phone show up as a device/drive when it's plugged in while sitting on the AT&T logo?
I think you're asking "does the phone show up as a device/drive" in something like a windows file explorer, and the answer is unfortunately no, or at least not that I've found yet - I've tried several times now, and I'm still trying any combinations I can.
For now...
I can get EaseUS to show 'MTP USB device' per the pic attached in my last, but can't really get it to connect past that point, as it asks for USB Debugging, which it appears I can't do due to stuck in boot loop.
Smart Switch seems to try to connect for awhile, then says it failed to connect, so I think I'm then left with 'Samsung Smart Switch Emergency Software Recovery' (PFA).
Do you have experience using it?
Do you know if it could work to reload the firmware / OS without wiping the data?
AT&T Advanced Technical Support guy says it gives you an option to choose whether or not using it resets the phone (wipes your data), so he thinks (hopes) that would work, but he didn't sound certain at all.
I understand your point on the pop up message user prompt for File Transfer Mode. I used that mode many times in the past, so I'm hoping it might default on the phone so we wouldn't need to answer the pop up prompt to reach that status , but I'm obv not sure about that.
Per the speculation in my last, do you know of any combination approach we might use to get the desired result, like maybe... use ADB somehow to change 1 parm value to reach MTP mode, then use that progress step to enable Smart Switch to connect so we could offload the data?
Thanks again for your help
1. MTP is the same as File Transfer. So when the phone is turning on, it starts loading that connection. You might see "MTP USB Device" or something similar in your Windows Device Manager
2. But if the phone never shows up as a device/drive (would show up under "Portable Devices" in Windows Dev Man), then it's not loading fully - and it normally doesn't do that until it boots past the carrier splash screen.
3. Even if it did boot fully and showed up as a device/drive, the MTP pop-up prompt shows up every single time you connect the device. There's no way around that. So the device would show as empty, with no files or folders, until you tapped "Allow" on the popup.
4. No, there's nothing else you can do to turn on any other connection modes
iBowToAndroid said:
1. MTP is the same as File Transfer. So when the phone is turning on, it starts loading that connection. You might see "MTP USB Device" or something similar in your Windows Device Manager
Click to expand...
Click to collapse
Device Manager does show an entry for the phone connected via USB cable:
Under 'Disk Drives' as
SAMSUNG MZMTE256HMHP-000MV
Under 'Universal Serial Bus Controllers' as
SAMSUNG Mobile USB Composite Device
Please tell me that helps us somehow?
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!