Related
HI, How are you all ..
i am new here, last monday i bought xperia x1.
Now the Problem is I am unable to send Text Message (sms) I write message and send but after some time message appear " your message cannot be sent " I Check my Sim Card and try to another mobile and work fine,.. Only Problem in Xperia X1..
Only SMS Problem..
other function work fine,,,
Please solve my problem give me idea or suggestion or any trick
dukhi said:
HI, How are you all ..
i am new here, last monday i bought xperia x1.
Now the Problem is I am unable to send Text Message (sms) I write message and send but after some time message appear " your message cannot be sent " I Check my Sim Card and try to another mobile and work fine,.. Only Problem in Xperia X1..
Only SMS Problem..
other function work fine,,,
Please solve my problem give me idea or suggestion or any trick
Click to expand...
Click to collapse
1st: welcome to xda
I understand you are still on stock rom, did you install other apps? always helpful to add as many details as possible
did you update to latest version via SEUS?
read here and compare your settings
then i read somewhere a hard reset would help (will restore default settings), consider it
cheers
reply`
Thank you sir for reply
Actuelly i am using Windows Mobile first time i dont know about Rom. and i never upgrade mobile..
Last night i reset everything from
Setting --> System --> Clear Storage and enter password 1234 then mobile restart and everything come to default..
So please help me step by step because am new to window mobile.
am very thank full to you.
s
Nobody reply me
100 people view this page but only 1 answer .. no anyone here for help me. bye
don't get impatient and discouraged so fast, the response time is always variable
maybe you get an answer within minutes, maybe you don't get one for various reasons, help here is still optional and not mandatory, that's as it is
some here even have a real life
are you able to connect to internet in general, browse, read, whatever and only SMS don't work or is there a general connection setup problem? I would check that first (if not already done)
do you have a new X1? any idea about installed firmware (aka stock rom, when from SE)?
second thing you should consider is SEUS - the SE Update Service, you dl part of the connect software to your pc (go to SE home, support, select X1, ->update service, dl application) which then enables you to connect to SEUS
try to update to the latest firmware and retry sensing an sms
then drop some feedback
cheers
DrakenKorin said:
don't get impatient and discouraged so fast, the response time is always variable
maybe you get an answer within minutes, maybe you don't get one for various reasons, help here is still optional and not mandatory, that's as it is
some here even have a real life
are you able to connect to internet in general, browse, read, whatever and only SMS don't work or is there a general connection setup problem? I would check that first (if not already done)
do you have a new X1? any idea about installed firmware (aka stock rom, when from SE)?
second thing you should consider is SEUS - the SE Update Service, you dl part of the connect software to your pc (go to SE home, support, select X1, ->update service, dl application) which then enables you to connect to SEUS
try to update to the latest firmware and retry sensing an sms
then drop some feedback
cheers
Click to expand...
Click to collapse
Dear when i update the phone the following error appear !
Code:
The Phone contain manipulated software and is not supported by this application
i am not understand,,,
dukhi said:
Dear when i update the phone the following error appear !
Code:
The Phone contain manipulated software and is not supported by this application
i am not understand,,,
Click to expand...
Click to collapse
I should have asked earlier: is it a used X1? somehow doesn't sound like new...
search for software information, e.g under start - settings - system - about device (location depends on firmware version) and tell me what you find
get the device into bootloader and tell me what's displayed there, sounds like you are not on stock rom anymore
cheers
One simple thing. Did you check the sms service number? Its easy to forget this because nowadays it is common for smartphones (and dumb phones too) to get this number automatically from the sim card. Nonetheless I would check it to make sure you dont fall victim to such a basic detail. You can check it here: Phone\Settings\Services\Mailbox and SMS\
You can look for the correct number on your carrier's website (or you call them).
hello dear friends....I had some strange issue 2 days ago...my apps settings restore to time that I just installed them....
i would to hard reset my phone and it was a good time to doing it...so I did hard reset but after it another problem,call and SMS didn't work....some strange problems,so I Task 29 my phone but it hang on SE logo....
No way,I tried to SEUS my phone and this error appeared....
The Phone contain manipulated software and is not supported by this application
what I suppose to do???
First of all: Don't mess around with things like task 29 if you don't know what they actually do. Task 29 completely erases the rom section of your phone so it's no suprise your phone is no longer able to boot. Now you have to flash another rom in order to use your phone again.
Another remark, the fact that you use tools like task 29 and afterwards you try to use SEUS only confirms that you have no clue what you're actually doing. SEUS only works with original software, as soon as you change to a custom rom or even if you only install hard spl SEUS won't work anymore. So you need to read the corresponding tutorials (hard spl, back to spl, custom roms, task 29) and either get it done the right way or reverse to stock spl and rom. Good luck.
tnx dear friend for ur compelete answer,U are right,my mistake and I appriciate for ur guidence....
I have installed another ROM from SDcard and my problem is solved now,tnx again.....
Unfortunately, app has stopped in Marshmallow
Good morning in South Africa time to everybody !
I decided to post my situation in here since I can see that all of you are quite helpful and would be able to help me with my Lenovo K3 Note T3s, purchased recently
The strange thing is that I have older apps which I use but every, I mean every, ROM,for the T5, which I have installed to my Lenovo K3,and almost every app that I have installed, and when I run these apps,it returns an error stating...UNFORTUNATELY, xxx HAS STOPPED. Most of the apps do start, and when the error is displayed, i can still see the app in the background underneath the error text that is displayed, which seems that the app does start, but something is preventing it with displaying the error above, and shutting it down when I press on the OK text in the error
I have tried around five roms already, various ones, most from Needrom.com, made for the T5, and they all return the same error when running the newly installed app, its as if this phone has a built in security function that doesnt allow any apps to be installed and used! The original ROM was ok but too much of bloatware and chinese writing which required me to find a better rom
Currently as I type this, I am downloading a rom for the T3S from needrom.com, hoping that I dont receive this error anymore
I have installed an updated app on one of the roms and it worked and did not display the error, however, I use some apps that do not have a later updated version available which causes the error to be displayed.
Are there any ideas on what could be causing this ? I have tried a few things from what I have read via a google search but none has worked
Any ideas or help would be much appreciated!
PS: I will keep you guys informed of what happens from this time of writing as well, just in case I find the cause/solution and somebody out there is also going through the same problem.
Heres the latest update so far...
Installed Lenovo K3_Note_MTK6752_Android_5.0_20150513 ROM from http://www.teamandroiders.com/lenovo-k3-note-stock-rom-firmware/
Its Android version 5.0, and still the same problem, almost every app still gives me the same error.
Going to try a rom built for Lenovo K3 Note T3s and reply afterwards.
quetiano said:
Unfortunately, app has stopped in Marshmallow
Good morning in South Africa time to everybody !
I decided to post my situation in here since I can see that all of you are quite helpful and would be able to help me with my Lenovo K3 Note T3s, purchased recently
The strange thing is that I have older apps which I use but every, I mean every, ROM,for the T5, which I have installed to my Lenovo K3,and almost every app that I have installed, and when I run these apps,it returns an error stating...UNFORTUNATELY, xxx HAS STOPPED. Most of the apps do start, and when the error is displayed, i can still see the app in the background underneath the error text that is displayed, which seems that the app does start, but something is preventing it with displaying the error above, and shutting it down when I press on the OK text in the error
I have tried around five roms already, various ones, most from Needrom.com, made for the T5, and they all return the same error when running the newly installed app, its as if this phone has a built in security function that doesnt allow any apps to be installed and used! The original ROM was ok but too much of bloatware and chinese writing which required me to find a better rom
Currently as I type this, I am downloading a rom for the T3S from needrom.com, hoping that I dont receive this error anymore
I have installed an updated app on one of the roms and it worked and did not display the error, however, I use some apps that do not have a later updated version available which causes the error to be displayed.
Are there any ideas on what could be causing this ? I have tried a few things from what I have read via a google search but none has worked
Any ideas or help would be much appreciated!
PS: I will keep you guys informed of what happens from this time of writing as well, just in case I find the cause/solution and somebody out there is also going through the same problem.
Click to expand...
Click to collapse
Ok when you flash it the flash tools, you use the preloader.bin and lk.bin frome the original rom?
When you instal the new rom make recovery reboots betwen wipes? This last is for you make a clean instal and avoid problems like that you have it now, or meaby you can lost the imei number, or the keyboard miss it, i dont know many problem came if you dont make reboots betwen wipes
I hope be helpfull to you.
Enviado desde mi Lenovo K50-t5 mediante Tapatalk
Thank you for your reply.
I came across a website that had a guide to try, two options were available, the first option I have tried and it worked, havent tried the second option though. The first option was the Android System Webview app, where, by opening it under apps in settings, and choosing to uninstall the update, it should help fix my error, and it did. There were one or two apps that still gave me the same error but most of the apps began to work after doing this.
Hello.
My Nexus 6 is out of warranty, so I'm doing my best to get it working myself because I can't get it replaced for free.
So, several months ago, my Nexus 6 (running Android 6.0.1 MOB30O) restarted on its own and showed a "Device is corrupt" message before booting (information at g.co/ABH; red error). I was concerned about the security of my device, so I performed a factory reset. Upon trying to set the phone up again, I found that after connecting to Wi-Fi, the phone would loop indefinitely while periodically saying that Google Play Services has crashed. I once tried leaving it overnight while it was "Checking connection" or whatever, and it still did not move to the next phase of setup. I have tried this on several different networks, and when I intentionally use a wrong password, the phone doesn't connect. So, I have no reason to believe the Wi-Fi connection is the problem. I have tried performing a factory reset from Android Recovery dozens of times, and it still doesn't work. So, I'm effectively limited to the boot menu to interact with my phone (so, I can't access Developer Options because I can't set up my phone). Also, most of the times I boot up my phone, I still get that red error during boot.
So, I've been trying to reflash stock Android. I tried using Nexus Root Toolkit to do that several times, and it never works (I get to a part in the process where it says to set up the phone and enable Developer Options, but I still can't set up the phone). I then decided I would try to do it myself since that tool wasn't fixing the problem. I am able to get ADB connected using the "Apply update from ADB" option within Android Recovery, but whenever I try to sideload one of the Shamu factory images, I get a C++ (I think) error:
Code:
loading: 'C:\Users\dpowell\Downloads\shamu-mob30o.zip'...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
I just updated all the ADB-related stuff from within Android Studio, so it all should be up-to-date.
So, I don't know what to try next. I've used Nexus Root Toolkit to root my Nexus 7 successfully, but I've never tried to modify my Nexus 6 before it stopped working. Regardless of what images I try to put onto the Nexus 6, it always shows MOB30O as the current image in the bootload menu.
Any thoughts or suggestions? I really would like to get this device working again, and Motorola would charge me $170 to replace it because it's not under warranty anymore.
Thank you for your help.
dpowell11 said:
Hello.
My Nexus 6 is out of warranty, so I'm doing my best to get it working myself because I can't get it replaced for free.
So, several months ago, my Nexus 6 (running Android 6.0.1 MOB30O) restarted on its own and showed a "Device is corrupt" message before booting (information at g.co/ABH; red error). I was concerned about the security of my device, so I performed a factory reset. Upon trying to set the phone up again, I found that after connecting to Wi-Fi, the phone would loop indefinitely while periodically saying that Google Play Services has crashed. I once tried leaving it overnight while it was "Checking connection" or whatever, and it still did not move to the next phase of setup. I have tried this on several different networks, and when I intentionally use a wrong password, the phone doesn't connect. So, I have no reason to believe the Wi-Fi connection is the problem. I have tried performing a factory reset from Android Recovery dozens of times, and it still doesn't work. So, I'm effectively limited to the boot menu to interact with my phone (so, I can't access Developer Options because I can't set up my phone). Also, most of the times I boot up my phone, I still get that red error during boot.
So, I've been trying to reflash stock Android. I tried using Nexus Root Toolkit to do that several times, and it never works (I get to a part in the process where it says to set up the phone and enable Developer Options, but I still can't set up the phone). I then decided I would try to do it myself since that tool wasn't fixing the problem. I am able to get ADB connected using the "Apply update from ADB" option within Android Recovery, but whenever I try to sideload one of the Shamu factory images, I get a C++ (I think) error:
I just updated all the ADB-related stuff from within Android Studio, so it all should be up-to-date.
So, I don't know what to try next. I've used Nexus Root Toolkit to root my Nexus 7 successfully, but I've never tried to modify my Nexus 6 before it stopped working. Regardless of what images I try to put onto the Nexus 6, it always shows MOB30O as the current image in the bootload menu.
Any thoughts or suggestions? I really would like to get this device working again, and Motorola would charge me $170 to replace it because it's not under warranty anymore.
Thank you for your help.
Click to expand...
Click to collapse
Hello,
The error you get from adb is coming from a problem with latest ADB Rev.25.0.4
Check this: https://issuetracker.google.com/issues/37139736
In Android studio are you able to revert to a previous version, no?
Rev.25.0.3 should work...
I assume your bootloader is locked?!
Good luck...
5.1 said:
Hello,
The error you get from adb is coming from a problem with latest ADB Rev.25.0.4
Check this: https://issuetracker.google.com/issues/37139736
In Android studio are you able to revert to a previous version, no?
Rev.25.0.3 should work...
I assume your bootloader is locked?!
Good luck...
Click to expand...
Click to collapse
Yes, my bootloader is locked.
Thank you, that fixed the ADB problem. I just saw that they actually have a Rev.25.0.5 now, so I am using that.
I tried sideloading first one of the Android 7 images, and that didn't work. So, I tried MOB30O again, and that also didn't work. Here's the error I'm getting:
Code:
E:footer is wrong
E:signature verification failed
Installation aborted.
The Shamu files I was trying to flash are the ones found at https://developers.google.com/android/images#shamu. Is this not what I'm supported to be using?
I don't know how relevant this is, but again, I'm using the "Apply update from ADB" option in Android Recovery, and all I did from my command line is "adb sideload [file]".
Thank you.
dpowell11 said:
Yes, my bootloader is locked.
Thank you, that fixed the ADB problem. I just saw that they actually have a Rev.25.0.5 now, so I am using that.
I tried sideloading first one of the Android 7 images, and that didn't work. So, I tried MOB30O again, and that also didn't work. Here's the error I'm getting:
The Shamu files I was trying to flash are the ones found at https://developers.google.com/android/images#shamu. Is this not what I'm supported to be using?
I don't know how relevant this is, but again, I'm using the "Apply update from ADB" option in Android Recovery, and all I did from my command line is "adb sideload [file]".
Thank you.
Click to expand...
Click to collapse
Hey,
WTF
You can't sideload a factory image
Download a proper OTA here: https://developers.google.com/android/ota#shamu
And try again.
Good luck...
5.1 said:
Hey,
WTF
You can't sideload a factory image
Download a proper OTA here: https://developers.google.com/android/ota#shamu
And try again.
Good luck...
Click to expand...
Click to collapse
Yeah, I understand about 40% of what I'm doing. Thanks for helping.
So, I sideloaded N6F26Y, which is 7.1.1. Here is the debug info I got:
Code:
Installing update...
Target: google/shamu/shamu:7.1.1/N6F26Y/3821691:user/release-keys
Patching system image unconditionally...
E:unknown command [log]
E:unknown command [log]
Writing bootloader...
Writing radio...
script succeeded: result was [1.000000]
Install from ADB complete.
So, it looks to me like that worked, but at the top of my screen, it still says 6.0.1/MOB30O. Also, it always makes me slightly nervous to see error messages. Do I need to reboot to bootloader in order for changes to take effect? Does it look like anything went wrong?
I know that manually messing with the operating system is potentially risky, so I didn't want to continue from here without knowing if there's anything else I needed to do.
Thank you so much for your help.
dpowell11 said:
Yeah, I understand about 40% of what I'm doing. Thanks for helping.
So, I sideloaded N6F26Y, which is 7.1.1. Here is the debug info I got:
So, it looks to me like that worked, but at the top of my screen, it still says 6.0.1/MOB30O. Also, it always makes me slightly nervous to see error messages. Do I need to reboot to bootloader in order for changes to take effect? Does it look like anything went wrong?
I know that manually messing with the operating system is potentially risky, so I didn't want to continue from here without knowing if there's anything else I needed to do.
Thank you so much for your help.
Click to expand...
Click to collapse
Hey,
You know everyone has to start somewhere. 40% is not that bad. :good:
Factory reset once again, just in case. And reboot.
Should be good now (hopefully). Let me know...
Cheers...
5.1 said:
Hey,
You know everyone has to start somewhere. 40% is not that bad. :good:
Factory reset once again, just in case. And reboot.
Should be good now (hopefully). Let me know...
Cheers...
Click to expand...
Click to collapse
Dude. It works.
Man, this phone had been out of commission for months. I am so happy to have it working again.
Thank you very much for your help. I really appreciate it a bunch.
dpowell11 said:
Dude. It works.
Man, this phone had been out of commission for months. I am so happy to have it working again.
Thank you very much for your help. I really appreciate it a bunch.
Click to expand...
Click to collapse
Hey,
Great! I'm glad for you...
Keep reading on this site. There's plenty of usefully threads, infos, etc...
Enjoy your phone...
Cheers...
i have g441 compact xz1 european version, last firmware a.12a.179. i tried several times , but its not working with xperifix 2.5 last version
i attached some logs
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
06-6-2018_18-14-51 ===> List /system
the main reason is I supoosed that is not working properliy is because the device in twrp mode, adb es blocked and unathorized.
feel little bit desapointed after paying 20 euros and there is not official help at all from xperfix.com where i sent a couple of mail and tickets.
somebody is in my same situation?
best
Answered you here:
https://forum.xda-developers.com/showpost.php?p=76737481&postcount=17
PS: The problem isn't the fault of XperiFix, my programmed solution has the same error.
Xperifix not working with XZ1 Compact
Hi,
Firstly, apologies if this issue has already been addressed elsewhere; if it has, I wasn’t able to find it – or if this is not the correct place to post this.
I’m also having an issue regarding my XZ1 Compact and Xperifix. I purchased Xperifix and I tried to use it with my XZ1 Compact (G8441, 47.1.A.12.179) yesterday. Unfortunately, it did not work.
Unlike the online video which demonstrates the process, when my phone boots during the process, the white Sony intro screen remains visible for a long time. Then I get a message saying:
“It appears that TWRP is not booting. Please do it manually…” followed by instructions on how to do so. I follow these, eventually pressing volume down until TWRP appears, and then reconnecting the USB and pressing OK.
Although Xperifix indicates that it is continuing the process, TWRP remains on screen and nothing further happens. Eventually, I get the same “It appears that TWRP is not booting. Please do it manually…” message for a second time. Again, I follow there instructions.
As before, Xperifix seems to indicate that it is performing normally. I then get a message telling me to check my phone to check that all has worked correctly. Unfortunately, it has not.
I have now completed this process perhaps six or seven times and the same thing happens every time. Can anybody please advise as to what I may be doing wrong or what I need to do in order for the software to run as intended?
Thank you in advance
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?