Related
Hi guys, I've had a look around for this, but I can only find the solution for bootloaders that are unlocked. I suspect my Ray WASN'T unlocked. I accepted the OTA 2.3.4 update, thinking it would be fine. But the phone now shows the exclamation mark. I can get into both the recovery and fastboot modes (green/blue LED).
None of the recovery solutions are working for me. Is there a way for me to fix this, or will the phone have to go to a Sony Ericsson shop.
The official PC software from SE won't restore it either.
it is wise to go to sony shop , they will fix it
Not sure if this will solve your problem, but it solved mine:
The problem was with the bootloader. So I tried FlashTool_0.2.9.1_FOTAUnbrick which brings a small firmware information to reset the bootloader.
The problem I was having was to be able to correctly connect the phone to the flash tool. My phone's USB connection was constantly going up and down. So I decided to uninstall all the tools and drivers and install them from scratch.
In short, here's what I did.
Installed Update_Service_Setup-2.11.10.7.exe from sony ericcsson in order to get the USB drivers to work.
Followed the instructions of the Update_Service and flashed the latest update available for my phone (2.3.4). This didn't solve the startup problem, just installed the latest update.
I ran the Update_Service again and restarted the process has if I was going to flash again, but after the Update_Service detected the phone I canceled the installation. (I did this just to make sure the phone was connected in FlashBoot)
Then I installed FlashTool_0.2.9.1_FOTAUnbrick.exe, opened the folder of the application and ran X10FlashTool.exe
Hit Flash button and the program opens a Firmware Selection window with a preloaded firmware with two reseting contents (loader.sin, preset.ta). Hit OK button and waited until the program indicated the flash process was finished. The process of flashing takes a few minutes and we need to be patient. It might even seem like it's doing nothing but we just have to wait.
After finishing the flash process the program invited me to disconnect the phone and turn it on. I did so and the phone took probably a minute or so to startup. At first I thought it didn't solve the problem, because it was taking so long to start, but it did solve! So I waited patiently and the Sony Ericsson logo showed up giving me a new hope. After that I had to wait another 4 or 5 minutes for the phone to finish applying the new firmware mentioned in point 2. (There's no visual information of the conclusion process so you might wonder the phone might have hung.) Just waited and everything got back to normal with the benefits of the new firmware 2.3.4 (instead of the previous 2.3.3).
I hope it helps someone having the same issue.
xperia ray said:
it is wise to go to sony shop , they will fix it
Click to expand...
Click to collapse
Might not fall under warranty.
http://forum.xda-developers.com/showthread.php?t=1568792, check my tutorial, there is a guide to unbricking.
Before the incident, I had root, no unlocked bootloader, stock JB, v20h.
What had happened was I was trying the Font Installer app in th Play Store because of the added customization that would have been nice.
I found a cool font, and I backed up my current fonts and then pressed install. SuperSU asked for permissions like normal and then my phone restarted.
Then it was so that my phone was stuck at the T-Mobile boot animation after the LG Logo. For about 15 minutes. This is where I believed something was starting to go very wrong. After contemplating for a few extra minutes, I decided to just take out the battery and restart. Same outcome. I thought of all the things that were on the phone thus far because I had just gotten it recently, and decided that it wouldn't hurt me to just do a hard reset by pressing home + vol down + power. Everything went smoothly. Except for the fact that even after I did that, it was leaving me at the T-Mobile screen.
I decided to look on the forums for development and tried to do the unbrick method, to no avail after about 3 hours now. I used the LG User Support Tool and since I hadn't updated to V20f, I decided to do that to see if it would solve my problem. It still didn't, and I'll be honest, I'm a little upset just typing this right now.
I also tried the Upgrade Recovery option and it warmed my heart to see that the process was actually starting. But right at the screen where it says that it is supposed to be downloading something, it freezes up and nothing happens no matter how long I wait. I saw somewhere that it should be a glowing red bar, but I do not see that anywhere, it is just frozen, saying Time Elapsed: 00:12. And before anyone asks, yes, I ran absolutely everything as an administrator.
Is there any possible way to bring this phone back? Any help would be immensely appreciated. Thank you in advanced.
anticlotto_ said:
Before the incident, I had root, no unlocked bootloader, stock JB, v20h.
What had happened was I was trying the Font Installer app in th Play Store because of the added customization that would have been nice.
I found a cool font, and I backed up my current fonts and then pressed install. SuperSU asked for permissions like normal and then my phone restarted.
Then it was so that my phone was stuck at the T-Mobile boot animation after the LG Logo. For about 15 minutes. This is where I believed something was starting to go very wrong. After contemplating for a few extra minutes, I decided to just take out the battery and restart. Same outcome. I thought of all the things that were on the phone thus far because I had just gotten it recently, and decided that it wouldn't hurt me to just do a hard reset by pressing home + vol down + power. Everything went smoothly. Except for the fact that even after I did that, it was leaving me at the T-Mobile screen.
I decided to look on the forums for development and tried to do the unbrick method, to no avail after about 3 hours now. I used the LG User Support Tool and since I hadn't updated to V20f, I decided to do that to see if it would solve my problem. It still didn't, and I'll be honest, I'm a little upset just typing this right now.
I also tried the Upgrade Recovery option and it warmed my heart to see that the process was actually starting. But right at the screen where it says that it is supposed to be downloading something, it freezes up and nothing happens no matter how long I wait. I saw somewhere that it should be a glowing red bar, but I do not see that anywhere, it is just frozen, saying Time Elapsed: 00:12. And before anyone asks, yes, I ran absolutely everything as an administrator.
Is there any possible way to bring this phone back? Any help would be immensely appreciated. Thank you in advanced.
Click to expand...
Click to collapse
did you hard reset? then turn off your phone disconnect the battery, connect to the pc holding the volume up button? then try the Update Recovery?
i would just go through that process over and over until it works, theres not really a way to brick this phone i've heard...
CROSSFREEZE said:
did you hard reset? then turn off your phone disconnect the battery, connect to the pc holding the volume up button? then try the Update Recovery?
i would just go through that process over and over until it works, theres not really a way to brick this phone i've heard...
Click to expand...
Click to collapse
Thank you for your reply! I have tried hard resetting multiple times, but I had removed some bloatware apps (I will quarantine them next time instead because I don't wanna go through this ever again) and I have tried the kdz method to only be stuck at 15% every time when I followed instructions to the pixel. I have tried to do it on windows 7 and windows 8. I have also tried the fastboot method by lelus, and that manages to "work" but I am still stuck at the tmobile boot screen afterwards. I have gotten the hang of the process of getting into the fastboot, but what do I do from there? I chose to flash ics xloader and uboot, but the process goes by so fast, I'm not even sure it is doing anything. The LG Tool has really gotten me nowhere, it just gives me a lovely error and then cannot continue the upgrade recovery process.
It said somewhere that after I flash through the fastboot I then have to try the kdz method, so I am going to do that now and see if it works. I don't know if there would be a difference between flashing a jb kdz or an ics kdz, but I will just do ics to be on the safe side.
I am quite happy to say that flashing the ics kdz was successful, and my phone is now up and running.
My p769BK is stuck on the LG screen. /: months
Sent from my LG-MS770 using xda app-developers app
im terrible with fastboot, i used the unlock the bootloader for noobs with an offline flash.
heres what i did to get out of bootloops....
alright, this is all from memory but the offline flash didnt work as well for me when stuck in weird bootloops.
Step one-going back to online flash---->
A---
the easiest way i found was to go to C:/windows/system32/drivers/ect/hosts
right click>open with notepad
there should be two lines at the bottom
"127.0.0.1 csmg.lgmobile.com
127.0.0.1 csmgdl.lgmobile.com"
i would cut them out and paste them in a text doc in the same folder for reference later...
but either way you should remove them from the hosts file and save
B----
Make sure your small server is closed! once you minimize it it should go down to your status bar (shttps)
Step two-LGMS---->
make sure you have LG mobile support installed or install it.
open lg mobile support
install needed drivers for your phone
power your phone off/remove the battery
put battery back in
connect it to your computer holding down the volume up button
S/W UPDATE mode should pop up, if it doesn't preform and hardreset and try again til it works (it will)
then in the top right corner there should be a button or two click them both until you see
"restore update" or Update restore or something to that effect
select that
and let it ride man
i got my phone ****ed many times and just had to keep redoing this until it worked. if your bootloader is truely unlocked you can probably go through all that again and get CM10 working, i did but im still working through kinks.....
GOOD LUCK feel free to ask any more Q's about this process if you run into any problems
Hello everybody,
as of yesterday I am in the Stone Age again using an old phone of mine.
What happend? No clue - the phone went off after recieving a SMS message in power saving.
When trying to put on: No reaction.
Connect to Energy Outlet: LED RED - leave hours - LED OFF
Retry on Button: No reaction.
Tryed following I read here: Press Red Reset before conecting to Laptop - It did something good! I hear the sound of connection. No Icons apear though! No recognition of device on the File Manager. Sound comes frequently, connect - disconnect - loop I guess.
Strange Symtoms received days before: I was in Japan on visit. Recieved about 30 messages of the program Google App, that it had to shut down. Asking confirmation. It never ended, so I turned phone of. After turning on, everything ok. Thought it had to do with local google in Japan.
Battery: loading felt very hot, phone felt hot. But after disconection worked.
Returning form Japan to home: google.app close down problem again. Endless confirmation. Stoped loop with disconection again.
Made reboot with red button on back.
PHONE lifeless.....no reaction, help! How to acces, so I can flash? or is it a battery problem? (ordered just one just to try)
Rom Installed: SLXROM_v11-Lenovo_P780 - in the year 2013.
101Maclaren said:
Hello everybody,
as of yesterday I am in the Stone Age again using an old phone of mine.
What happend? No clue - the phone went off after recieving a SMS message in power saving.
When trying to put on: No reaction.
Connect to Energy Outlet: LED RED - leave hours - LED OFF
Retry on Button: No reaction.
Tryed following I read here: Press Red Reset before conecting to Laptop - It did something good! I hear the sound of connection. No Icons apear though! No recognition of device on the File Manager. Sound comes frequently, connect - disconnect - loop I guess.
Strange Symtoms received days before: I was in Japan on visit. Recieved about 30 messages of the program Google App, that it had to shut down. Asking confirmation. It never ended, so I turned phone of. After turning on, everything ok. Thought it had to do with local google in Japan.
Battery: loading felt very hot, phone felt hot. But after disconection worked.
Returning form Japan to home: google.app close down problem again. Endless confirmation. Stoped loop with disconection again.
Made reboot with red button on back.
PHONE lifeless.....no reaction, help! How to acces, so I can flash? or is it a battery problem? (ordered just one just to try)
Rom Installed: SLXROM_v11-Lenovo_P780 - in the year 2013.
Click to expand...
Click to collapse
Seems to be a motherboard problem!
Hi stympy
Need to to identify if this is motherboard issur or ROM.
My phone purchased in Jan 2014. It has been updated to official rom 4..2.2 using OTA. No other unofficial ROM being install before. In Jan 2015 the screen broken so we send in to local repair shop.
Problem started here, after repaired (just change lcd screen) the phone behave restart/blank once a while. Due to different problem the workshop does not cover the warranty (due to different issue). But the workshop recheck if problem with connection of lcd and motherboard. No problem here. In March 2015 it become unusable because once power on P780 8GB (international version), it keep bootloop at lenovo startup and the logo yet to flip it gets reboot again.
In an attempt to revive it (hope it is ROM issue), hard reset done but still the same. Try to flash with v5 (manually install drivers MTK and USB) but v5 cant detect the phone. Device manager shows the driver installed successfully but with a warning sign. Properties says something like "the device does not start correctly". FYI, I cant access the phone's SD card from My Computer. Sometimes it appear a Lenovo logo to install some software (red icon)
So is there any "hard reset" i can do or it is the motherboard issue? Worse come to worse, Is it advisable to change motherboard?
expzero said:
Hi stympy
Need to to identify if this is motherboard issur or ROM.
My phone purchased in Jan 2014. It has been updated to official rom 4..2.2 using OTA. No other unofficial ROM being install before. In Jan 2015 the screen broken so we send in to local repair shop.
Problem started here, after repaired (just change lcd screen) the phone behave restart/blank once a while. Due to different problem the workshop does not cover the warranty (due to different issue). But the workshop recheck if problem with connection of lcd and motherboard. No problem here. In March 2015 it become unusable because once power on P780 8GB (international version), it keep bootloop at lenovo startup and the logo yet to flip it gets reboot again.
In an attempt to revive it (hope it is ROM issue), hard reset done but still the same. Try to flash with v5 (manually install drivers MTK and USB) but v5 cant detect the phone. Device manager shows the driver installed successfully but with a warning sign. Properties says something like "the device does not start correctly". FYI, I cant access the phone's SD card from My Computer. Sometimes it appear a Lenovo logo to install some software (red icon)
So is there any "hard reset" i can do or it is the motherboard issue? Worse come to worse, Is it advisable to change motherboard?
Click to expand...
Click to collapse
Hi. Before i give a verdict with your phone i need to see something. Can we do a team viewer sesion?
Send me an PM with id and pass in 7 hours from this message! .
I need an information about your PC or notebook. What windows do you use?
This happened to me several times exactly the same condition
What you have to do: Do not never charge it and left it for several days until the battery is discharged -With pressing the power button from time to time-
Then recharged I think this work
I advise you to use STOCK ROM
Hi sym,
We need another time to teamviewer. Just saw your reply.
But i believe u cant get anything as from my side i cant even get any respond from the phone with drivers installed.
u got pm
Welp,
I've gone & done it again. My 2nd z3v came from Amazon a few days ago, refurbished, like new. Got the 200GB card for it, went to Verizon & got the SIM, swapped it with my work phone (iPhone 4s) line.
(Now I have 2. But the 1st one was replaced for being in this same situation.)
Got home, swapped the phones back cause I really still wasn't sure I wanted to mess up this z3v with my job (landscaping = lots of dirt).
It had 4.4.4, and I let it update to the latest two part Lollipop to see what the hubbub was about (nothing).
Decided I wanted to make it basically a clone of my primary z3v, so I rooted from the update directly using GigaSPXs guide.
Successful rooted 509 achieved, but with one problem; it kept telling me I had no space left, even though the internal SD had 21 GB left. Peculiar.
Made a recovery file on my #1 z3v's SD. Copied everything from #1 SD to #2 SD, and attempted to "clone" #2 z3v by installing that latest zip copied from z3v #1, but Recovery kept saying "No File Found".
Checked all 5 recovery points I had on there, and each said the same thing. Checked other things on the SD card, and it showed them, but when I tried to open them, it said "No File Found".
Mounting problem? Made sure everything was mounted, etc. Still, same problem.
Tried wiping Dalvik 3 times, but also accidentally wiped System Cache.
Now it sticks at the SONY Xperia logo. I can get to the Sony Recovery options, but Factory Reset doesn't do anything.
Was it System Cache wipe that killed it, and can anything be done?
This time, I took some notes as I went. I was confident, but I've done this before (bricked), so I decided to list what I did as I went along. I highly recommend everyone take notes for when they screw up. LOL!
AddictedToGlass said:
Welp,
I've gone & done it again. My 2nd z3v came from Amazon a few days ago, refurbished, like new. Got the 200GB card for it, went to Verizon & got the SIM, swapped it with my work phone (iPhone 4s) line.
(Now I have 2. But the 1st one was replaced for being in this same situation.)
Got home, swapped the phones back cause I really still wasn't sure I wanted to mess up this z3v with my job (landscaping = lots of dirt).
It had 4.4.4, and I let it update to the latest two part Lollipop to see what the hubbub was about (nothing).
Decided I wanted to make it basically a clone of my primary z3v, so I rooted from the update directly using GigaSPXs guide.
Successful rooted 509 achieved, but with one problem; it kept telling me I had no space left, even though the internal SD had 21 GB left. Peculiar.
Made a recovery file on my #1 z3v's SD. Copied everything from #1 SD to #2 SD, and attempted to "clone" #2 z3v by installing that latest zip copied from z3v #1, but Recovery kept saying "No File Found".
Checked all 5 recovery points I had on there, and each said the same thing. Checked other things on the SD card, and it showed them, but when I tried to open them, it said "No File Found".
Mounting problem? Made sure everything was mounted, etc. Still, same problem.
Tried wiping Dalvik 3 times, but also accidentally wiped System Cache.
Now it sticks at the SONY Xperia logo. I can get to the Sony Recovery options, but Factory Reset doesn't do anything.
Was it System Cache wipe that killed it, and can anything be done?
This time, I took some notes as I went. I was confident, but I've done this before (bricked), so I decided to list what I did as I went along. I highly recommend everyone take notes for when they screw up. LOL!
Click to expand...
Click to collapse
Use Flashtool to flash it back to 4.4.4. After that, don't try to do your attempt again. They're two separate devices and they are both uniquely different internally.
OK, how do I use flashtool? The PC doesn't recognize the phone as anything hooked up to it. Flashtool doesn't recognize it's there.
AddictedToGlass said:
OK, how do I use flashtool? The PC doesn't recognize the phone as anything hooked up to it. Flashtool doesn't recognize it's there.
Click to expand...
Click to collapse
IIRC, hold down the down (or up) button and hook the phone to the computer. I think it should trigger recognition from there.
GigaSPX said:
IIRC, hold down the down (or up) button and hook the phone to the computer. I think it should trigger recognition from there.
Click to expand...
Click to collapse
If that doesn't work and you have connected your phone to your computer before try removing all related Sony drivers from the computer. If you are OK with registry edits you could look for any instances of your phone there too.
Komet1 said:
If that doesn't work and you have connected your phone to your computer before try removing all related Sony drivers from the computer. If you are OK with registry edits you could look for any instances of your phone there too.
Click to expand...
Click to collapse
Don't I need the drivers installed?
Yes,, reinstall them preferably from outside your computer. You are wanting the drivers on your computer to be overwritten by fresh drivers, even if they have the same version numbers. You want the computer to "think" this is the first time the phone has ever been connected to it.
Where do I get th drivers for re-installation?
AddictedToGlass said:
Where do I get th drivers for re-installation?
Click to expand...
Click to collapse
Try this. If you do take this route don't be discouraged if it doesn't work the first time. I have had something similar happen and on occasion it has taken a few tries. Windows doesn't like to let go of drivers that are already installed.
Xperia Z3 drivers
"Phone driver for Xperia Z3 (D6603, D6616, D6653, D6643, SOL26, D6708, SO-01G, and 401SO) (Microsoft Windows™ XP 32bit/64bit and later). Use drivers for debugging, or when erased from phone."
DLed the replacement drivers, but Flashtool isn't recognizing the z3v. I know I'm doing something wrong because it isn't recognizing my other (functioning) z3v, either.
So I Googled driver installation on Windows 8.1 because I remembered that it won't allow unsigned drivers without manual installation, and I needed a refresher course for all the steps. I am uncertain I successfully removed all of the previous ones, though. What I did find out, but did not know, was that putting 8.1 into that mode (where it'll install unsigned drivers) is a temporary situation. According to a poster on a blog (for whatever that's worth...), once the PC is restarted, it comes out of that "test mode", and unsigned drivers no longer work again. I usually keep the PC on, but it has restarted since I last messed with Flashtool.
Obviously I need to figure out where I'm going wrong on this to even begin work on the phone. (I miss XP.)
Details about the z3v behavior:
The screen is stuck on the SONY XPERIA logo.
Pressing the power button by itself has no effect, no matter how long I hold it.
Pressing the power button with the volume down will power it off, but it just powers back on by itself.
Pressing the power button and holding both the power button and the volume down while it cycles back on gets me into the Android Recovery menu.
From Recovery;
Selecting "Power Down" USUALLY powers it down, but sometimes it immediately restarts.
Selecting "Factory Reset" cycles it through the logo and into an attempt (Droid animation with blue bar rolling) for about 5-6 seconds, and then it restarts into the SONY XPERIA logo again.
Selecting "Safe Mode" simply restarts it the same way.
Selecting "Continue Power Up" obviously does the same.
All that is while not tethered to the PC. NO color LED comes on, except for an occasional orange while it's hooked to the PC.
Got a couple of suggestions about the PC connection:
Try a different USB cable.
Have you looked in Device Manager and removed any reference to the Sony there as well?
Here is a blog post about an Xperia S that wouldn't connect, the steps should be the same:
Connect the phone via USB and go to the Device manager on the computer. Check if you can locate the phone or any Unknown/New device that could be the phone or if you perhaps see the phone as a device. Right click it and select to uninstall.
Still in Device manager open the list for USB controllers (Universal Serial Bus Controllers) and right click each one of these controllers and select to uninstall.
When all of this is done reboot your computer and before connecting your phone again repeat step 2.
You should of course not have to do this every time you connect your phone to your computer but hopefully this could remove any error causing your phone not to connect properly.
I'M BACK!!!
And here's a lesson from one noob to all others; Never overlook the simplest things.
Komet1, your suggestion of trying a different cable struck me as desperate, but when I looked at what I had been using, I realized it was the cheap cable Amazon sent with the phone (It didn't come with a Sony charger and cable, just a crappy generic set).
I swapped cables and viola!, I now have 4.4.4 back.
I'll not be making the stupid mistake of swapping restores from one phone to another again.
Thanks all!
Important lessons for beginners...
Take notes. I'm glad I did this time because last time I bricked I couldn't remember what I had done to brick it, or what I had tried to unbrick it. It helps when you can provide detailed info, otherwise it becomes too frustrating for those who can help. It can also help keep you from panicking and going in circles.
AddictedToGlass said:
I'M BACK!!!
And here's a lesson from one noob to all others; Never overlook the simplest things...
Thanks all!
Important lessons for beginners...
Take notes. I'm glad I did this time because last time I bricked I couldn't remember what I had done to brick it, or what I had tried to unbrick it. It helps when you can provide detailed info, otherwise it becomes too frustrating for those who can help. It can also help keep you from panicking and going in circles.
Click to expand...
Click to collapse
Awesome! Been there, done that with the bricking. It's a wonderful feeling when you watch the phone respond and realize you just solved the problem.
Sure is!
DOH!!!!
Hello everyone.
So I successfully rooted the A10-70L ZA010062ZA using the simple tool: KingoRoot.
It was truly easy; just downloading and installing KingoRoot onto my laptop (I did not trust installing it on the tablet itself) and it turned out to be a big success with just one click of a button ("Root") after plugging the tablet into my laptop using USB (with USB debugging turned on ofcouse).
So here I went and downloaded Linux Deploy onto the tablet and spent a day TRYING to install Kali onto it. Honestly, there were so many issues and errors, I just got frustrated.
I honestly did not figure out how to do this yet; because why? The tablet thought to itself "What madness it this?!" and he shut down instantly, BOOM!
I was confused at first, holding my head with my hands in my hair when i then realised - Wow, okay.. It does NOTHING when i try to turn it on! I freaked when I realised that I have hard-bricked it.
After trying ONE LAST TIME to turn it on, holding the power button for almost a minute before losing hope, IT TURNED ON! But.. It got stuck in a boot loop, showing only the boot screen. I WAS RELIEVED!! I only soft-bricked it.
Now I am currently downloading the stock ROM, which I believe should work. I will post an update on this thread to keep you up to date on what I did and if it was successful.
Question: Is there maybe ANY custom ROM that is compatible with the A10-70L ZA010062ZA?
The stock ROM is cool and everything, but why not make the device a brutally epic device if the possibility exists?!
Xx
EgyptianCobra