Hello,
I am looping for assistance and advices.
I wanted to upgrade the phone of my son, for a game, Xperia sp was in 4.3 official Sony, I read several tutorial and I had the idea to pass it into 6.01. So firstly, I did a safeguard with PC software companion but impossible to install it without error (failure configuration) I triée to use titanium as sight in several tutorial, but impossible to use it because it needs that the phone is rooted. I search for a rooter and I find the towelroot application which I install on the phone, and which I launch. I again launch titanium to control that the phone is rooted and it is the case. I start the safeguard of the applications and it is there that begins my problems, the screen remains blocked and the progression of the safeguard remains to zero % and the tactile does not answer any more. I wait a little but nothing changes. I rebooted on the first time with the button power but nothing happens, then with power + volume+ always nothing and finally with the button off in the back of the phone. It shut down, I turn it on it thinking that it was ok but after a few seconds it is blocked again. I tested several times and I always have the same problem.
I dont know what to do anymore.
is the phone recoverable, so yes how?
can I still recover the data of the phone?
I think of a solution, it is to try to install twrp with Fastboot to carry out wipes but if I could have advices before making other mistakes.
I will add that I am beginner on Android (I think that you understood it), I have iPhones of my job.
thank you in advance for your Advices.
Sorry for my bad english.
problem solved.
It is the card SD which blocked the phone
So i suppose you wanted to do a backup of data right? And what do you mean "Blocked"? Phone cannot be turned on?
The phone starts correctly with access to the applications and after a few seconds the screen jams. Solved problem it was the card SD which did not appreciate the use of titanium.
Related
Hello I recently smashed the screen on my Xperia z. Is there anyway to unlock the phone without using the screen at all? Please can someone help me ive been digging for hours. All i need is to unlock the phone so i can access the data on it via my PC.
The data does not show in windows or via any sony pc apps while the phone is locked.
I read a thread that was to do with the same problem but it was with a NEXUS 7, The post is very old.
Is it possible to do it with an xperia z? I will be so grateful if anyone can help
Ive downloaded SDK already in preparation.
Thank you.
You can't see anything at all?
jakesm20 said:
Hello I recently smashed the screen on my Xperia z. Is there anyway to unlock the phone without using the screen at all? Please can someone help me ive been digging for hours. All i need is to unlock the phone so i can access the data on it via my PC.
The data does not show in windows or via any sony pc apps while the phone is locked.
I read a thread that was to do with the same problem but it was with a NEXUS 7, The post is very old.
Is it possible to do it with an xperia z? I will be so grateful if anyone can help
Ive downloaded SDK already in preparation.
Thank you.
Click to expand...
Click to collapse
There's an app called magic unlock that you can unlock your phone by swiping the proximity sensor but the thing is I don't know how you gonna download and set it since you can't unlock the phone now lol.
Sent from my C6603
DrKrFfXx said:
You can't see anything at all?
Click to expand...
Click to collapse
Nope nothing of any real value just heavily distorted colours. cannot touch anything on screen
OK, so after a while trying to access user partition via adb shell, pull, adb file explorers, etc. With no luck, I found that if:
You turn of your phone, hard power it off in your case since you can't confirm the on screen dialog (volume up + volume up until it vibrates three times).
Now that the device is turned off, plug both ends of the usb cable to the pc and phone, it should beep whatever, and then the charging animation should come up.
Turn on the device and let it boot without unplugging the USB.
When the device gets to the sim unlock screen, the PC should recognize the internal memory and you can access to it, since it probably hasn't load the pattern unlock stuff.
Give it a try. I've just done it several times and can access my data partition entirely.
DrKrFfXx said:
OK, so after a while trying to access user partition via adb shell, pull, adb file explorers, etc. With no luck, I found that if:
You turn of your phone, hard power it off in your case since you can't confirm the on screen dialog (volume up + volume up until it vibrates three times).
Now that the device is turned off, plug both ends of the usb cable to the pc and phone, it should beep whatever, and then the charging animation should come up.
Turn on the device and let it boot without unplugging the USB.
When the device gets to the sim unlock screen, the PC should recognize the internal memory and you can access to it, since it probably hasn't load the pattern unlock stuff.
Give it a try. I've just done it several times and can access my data partition entirely.
Click to expand...
Click to collapse
Thankyou so much for your help, I wish I could say it worked but it hasn't. I did exactly what you said and my computer starts to recognise the phone but stalls on loading up data. it stops access to ''MY COMPUTER'' until the phone is removed at which point a dialog window pops up saying ''sony xperia z connected'' but of course now its been disconnected i cannot access anything regardless of the dialog window telling me my phone is connected
any other ideas? I really appreciate you putting in the time to help me
Just got it to work!!!! Thank you so much for your help. After I realised that the problem for loading extensions may be coming from my PC I ran AVG tuneup which fixes all hidden errors and it worked Instantly.
I recommend AVG tuneup to everyone, especially if you play a lot of games or install a lot of programs. Whenever Ive noticed sluggish performance on my PC i've ran a full scan and it has always fixed any issues.
Thank you so much again for the great help, very impressed with this community and its great attitude toward helping others.
So it was a drivers issue of some sort. Did my method worked in the end? I found it randomly. I call it a security issue though, this time came in handy.
Glad you could fix your problem.
Hi, it's my first post, and I need your help.
I have a Sony Xperia SP C5302, untouched Android 4.1.2 (12.0.A.2.254)
Last day I rebooted the device and it didn't turn on, and I haven't installed anything, just normal use. I tried several things and I could turn it on first with the reset hole on the back (10 seconds), then pressing volume down + power, and the device turned on ok. Later I realize the pc (with PC Companion) doesn't recognize the phone. It's the same pc I always use without issues, and with the original cable. Tried on a different pc, but it's the same, luckily I can charge the phone without problem.
Today I made the factory reset, and the only good thing I got is that now I don't need to do the 10 seconds on the back hole, but I must press volume down + power to turn it on, in fact if I just press power (and not volume down), it vibrates but it doesn't turn on, and it won't turn on again unless I do the 10 seconds on the back. The PC still doesn't recognize the phone.
If it helps, phone was rooted and I was using GravityBox for some tweaks, but it was like that for quite a long time, without any issue.
I'd really appreciate your help!
In your position, I would consider this: (back up important data)
Flash full 254 afresh without rooting or recovery.
Test it. If it works, re-root and install whatever you had previously, and enjoy.
If not - send it to sony centre - probably hardware issues...
Thank you for your help!
I thought the same, but then I realized there's no USB connection, so I can't flash the phone. Even worst, I have the 266 update pending, so I tried that over wifi, but i don't know with it says there was an error, the update never installs, I tried twice.
It's incredible, I had the phone for 4 months, and just like that, it's broken.
Again, thank you for your time, and if there is anything you think I can try, your welcome!
I had a similar problem my solution was to factory reset restore all the system apps I had removed basicly make it look like it had never been rooted then use the unroot and cleanup option in superSU and sent it to Sony who replaced it
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Remove all drivers that you have installed related to android on your computer.
Reinstall all of them.
Try to change from MTP to MSC in USB settings to see if your USB port is still working.
Guys, thank you all for your help, I guess I'll have to live without usb, and forget about flashing. I really liked sony phones
Ok guys,
as the title says Lumia 710 is bricked.
It had last factory update and everything was working fine. Then i had to mess with it and to try to install Rataplan V9.1.
The process was working ok. By default, bootloader was in DLOAD mode, so in order to install custom ROM i needed to upgrade to Qualcomm. I have upgraded it and installed Rataplan .nb rom to the phone with NSSPro V0.54.
This is when my problems start.
The phone starts with one long vibration followed after few seconds with one short virbtation and thats it. No screen, no system, zip!
When i try to connect it again by usb to check it with NSSPro, it always starts in NAND disk mode. It does not matter do i start it normally on power button or with volume up. Its always in NAND. And it is always stuck. While the phone is connected to USB i can see Qualcomm CDMA Technologies MSM device in device manager but it has yellow mark like the driver is not installed.
I have tried several other roms, and NSS always shows that the rom is successfully installed, but the phone (other than vibration and NAND mode) is dead.
I have also tried all the solutions i could find on the net but no help. Tried, nokia recovery tool, WP recovery tool, Chimera e.t.c. Nothing works. Now i have a problem with NSS. It keeps stucking and beeing unresponsive for every option except Custom OS flash. Whatever else i click it either says tha phone is not detected or the app stucks and shuts itself down.
Is there other tool i can try?
Can i do anything to recover this phone or did i kill it?
PLEASE HELP!!!
Well that sucks and it sucks no one has tried to help here. I'm fair with Android but too new to WP's to probably be much help. Can you pull the battery out of the phone? Might pull it and leave it out a couple minutes then retry. You also might try from a different computer in case something has gone wrong on your computer in terms of port communication or maybe even a virus of some sort. Good luck.
droidzer1 said:
Well that sucks and it sucks no one has tried to help here. I'm fair with Android but too new to WP's to probably be much help. Can you pull the battery out of the phone? Might pull it and leave it out a couple minutes then retry. You also might try from a different computer in case something has gone wrong on your computer in terms of port communication or maybe even a virus of some sort. Good luck.
Click to expand...
Click to collapse
Tried allready every solution that i could find or think of, including things You described. Nothing. I was left with no other option but to send phone to service. They have a box unit with which they should be able to recover phone.
That was 2 days ago. today is third day so i am thinking that my phone has gone beyond repair. Only thing i can do is to wait and see...
Why not...?
Why not send it in real life to a windows phone expert. There should be a place to get phones repaired But, if they say that it isn't possible for them you may have rendered your phone useless. Google should be your mighty friend in this case :crying: I wish you very good luck.
I have a Moto G6 XT1925-5 (64GB version) which doesn't want to start up. It's all totally stock, been updated to Android Pie.
It gets as far as the boot animation, and does that for about 2 minutes, then it boot loops and starts all over again. When it bootloops it gets stuck at the first Moto logo screen (not the animated one) for about 3 minutes before carrying on to the boot animation...
This happened once or twice before, we left it overnight and eventually it started up normally. But it's now been five days and it still hasn't started.
I'm not very experienced with Android hacking/modding, etc but willing to try anything. I managed to get into recovery mode and at the top it says (I presume this indicates the firmware version):
motorola/ali_retail/ali
9/PPSS29.55-37-7-6/16c5a7
Unfortunately USB debugging is not enabled. Is there anything that we can do to recover the data that was on the phone before we wipe it - or is there another method we can try to get it to start up? I saw there's a command adb logcat which looks like it might be useful to diagnose the problem but that also requires USB debugging.
Thanks in advance for any suggestions
There is no chance for you to recover your data in this mode.
WoKoschekk said:
There is no chance for you to recover your data in this mode.
Click to expand...
Click to collapse
Thanks for getting back to me so quickly.
There are several other modes available from the bootloader BP Tools, QCOM, etc but I can't work out how any of them are supposed to work.
One question - on the recovery menu, there is an option 'Mount /system'.
I pressed it and it says at the bottom /system mounted, but then there don't seem to be any obvious ways to access anything.
Is there a way to use this to access OS/kernel logs which might give a clue as to what is going wrong?
Thanks again
Step by step...
The first level of the system, which is accessible for you, is called bootloader menu (fastboot menu). From here you can boot into recovery, system, bootloader itself and some other options you mentioned in your post.
None of these options would help you to solve your problem. These are developer's options.
This level is more or less a one way data connection. The main advantage of this menu is to flash single partitions of your device. But there is no way to get a data output of any partition.
In recovery menu you find the options to wipe your data and to mount /system. Mounting /system won't help you, too. This partition doesn't store anything of personal data. It's read only and not writable for anyone. To be honest, nobody knows exactly the meaning of it in this context. Also you won't access any logs from here.
Generally you can't access the system logs. These informations are only buffered data which is cleared with every reboot. The error message of e.g. the kernel log produced by your system when having a bootloop, is only accessible while your device is looping/freezing. The next reboot erases the logs. They aren't stored somewhere on your device. Even for developers it's very tricky to view the log in such cases.
But what would you do if you get the reason for looping? You are not able to access any system partition. You need root user permissions for that. But rooting your phone will erase all data.
Apart from all that your data is encrypted and remains encrypted until you unlock your screen by fingerprint, PIN or password. No chance to get any useful data as a "third person" outside. It would take several years to decrypt it without the matching key for it.
Thanks so much for this detailed explanation, I really appreciate that you took the trouble to answer the questions in detail and explain what the various options are for.
phone5774 said:
Thanks so much for this detailed explanation, I really appreciate that you took the trouble to answer the questions in detail and explain what the various options are for.
Click to expand...
Click to collapse
No problem!
Maybe you'll find some of your personal data in your Google Drive account...
How the story ended
Thought I'd come back and post in case it's useful for anyone else:-
Due to a religious festival, we left the phone switched off for three days. After the festival ended, we switched it on, and immediately it did the same thing that it had been doing all along (spend a long time on the initial boot screen then a while on the boot animation before boot looping). Bizarrely even though it had been off it did not prompt for the PIN code.
We then held the power button as though to turn it off (but for some reason, throughout the usual power button never actually turn the phone off, it always attempted to restart immediately) and then next time it came on it asked for the PIN and started up normally!
So all in all that was a grand total of 9 days after the problem first happened. Very inconvenient not to be able to use it for 9 days, but it's now working again. We haven't dared to try to restart it since!
Some closing thoughts:
The storage is very full (99%), we wonder if that had something to do with this problem
We have now enabled USB debugging and bootloader unlocking to make recovery easier in future
phone5774 said:
Thought I'd come back and post in case it's useful for anyone else:-
Due to a religious festival, we left the phone switched off for three days. After the festival ended, we switched it on, and immediately it did the same thing that it had been doing all along (spend a long time on the initial boot screen then a while on the boot animation before boot looping). Bizarrely even though it had been off it did not prompt for the PIN code.
We then held the power button as though to turn it off (but for some reason, throughout the usual power button never actually turn the phone off, it always attempted to restart immediately) and then next time it came on it asked for the PIN and started up normally!
So all in all that was a grand total of 9 days after the problem first happened. Very inconvenient not to be able to use it for 9 days, but it's now working again. We haven't dared to try to restart it since!
Some closing thoughts:
The storage is very full (99%), we wonder if that had something to do with this problem
We have now enabled USB debugging and bootloader unlocking to make recovery easier in future
Click to expand...
Click to collapse
When I read this last post, I immediately think of a sticky power button, because if you keep holding the power button after the phone has booted it will turn off again, and start up again. And it would also explain the weird behavior you just described of not turning off but rebooting straight away. I'd say: see if you are able to clean de button with a very thin needle or a crafts- or surgical knife around the edges, is might just solve your problem...
mcremco said:
When I read this last post, I immediately think of a sticky power button...
Click to expand...
Click to collapse
Thanks for that suggestion. Interesting, not something I'd thought of.
For now the phone is working perfectly, provided that have to restart it (i.e. we make sure not to shut it down or let the battery run out) but I'll definitely bear this in mind if the issue happens again.
The power button is working normally to turn the screen on or off meanwhile.
Thanks again for your input which is really appreciated.
First time trying to restart after the above
Since posting the above messages the phone has been kept on all the time and not restarted.
Today for the first time we accidentally let the battery run out and the phone shut itself down.
We nervously plugged it in and tried to switch it back on... and it started properly first time, so perhaps the underlying problem was simply that the storage somehow got too full (in the meanwhile we have transferred many photos and other media to the computer and deleted them off the phone to free up space).
Posting this in case it helps someone else experiencing a similar problem.
Hey, everybody!
I got a problem and hope to find help in here:
I recently got my Mi 11 Ultra (12GB / 512GB) from Tradingshenzhen. I bought an unmodified chinese version. After setting up my phone a few days ago the only things I did was changing the language of the Play Store using Morelocale 2 and deleting 2-3 (really unnecessary) apps using ADB. I didn't flash anything, didn't unlock the bootloader or didn't even start the unlocking process.
Everything worked fine for a 2-3 days now. Tonight I realized that the phone was off. As I was thinking that the battery was empty (there was a message a while before that the battery was low) I connected the phone to the charging cable and did a long press on the power button trying to turn it on. I put the phone aside and went to bed.
Today in the morning I took the phone and saw that it was obviously in some kind of menu I hadn't seen before. It says " Main Menu MIUI Recovery 5.0". There are three options: reboot, wipe data and connect to MiAssistant. When I am choosing "reboot" the phone tries to reboot but ends up in Recovery Mode again. And again. And again.
How is this possible? Anyone knows what happened here? As I said...I didn't flash any ROM or opened the bootloader.
Unfortunately there is one photo on the device that I need and haven't uploaded to any cloud yet.
Thanks in advance!
Can't see any other options that will work without losing that photo.....
Maybe an expert could help you but I'm not sure you will be able to reflash yourself without Data wipe....
Thanks!
I actually wiped the data and reset the phone. Works now again but the photo is lost.
There is a way to retrieve data from a board but it involves taking the whole phone apart , which is risky, and connecting a couple of wires to some points on the circuit board....
Not for the feint of heart and I haven't seen it done yet on this model but there's a YouTube video of it being done on an older xiaomi phone....