Related
Hello,
I am having an issue with my SGS since this morning.
I write all details:
1) I was using my phone normally and testing different apps to lock the phone in case the SIM card is changed.
2) I wanted to check if those apps make my phone slower and I use the "Quick System Info Pro" app to check the processes.
3) I chose the "Application" tab and I applied a sort by data... From that moment it freezed...
4) The screen was black for more than 5 minutes. I couldn't do anything so I removed the battery in order to make my phone restart.
5) After restarting my phone, it asked my pattern lock as usually. But then the screen stays black... Then a message tells me that the system process had a problem and propose me either a force close or waiting that the process is available... Even if I wait or I do a force close, it restarts to show me the pattern lock screen and shows that the system process crashes. I have noticed that the battery icon and mobile network icon is not displayed at all.
I don't use a custom ROM and my phone is not rooted. I don't use any special fix neither.
Does someone had this same issue ? Is there a way to solve it without formatting the data ?
I am waiting for your answers.
Franklin
hope your 3 button download/recovery mode works because i think i see a firmware flash in your future.
androiderer said:
hope your 3 button download/recovery mode works because i think i see a firmware flash in your future.
Click to expand...
Click to collapse
Thank you for your answer.
I had no solution. I had to use the recovery mode... Now it works better as all apps are removed.
Hi. Just a few hours ago while I was on my way home, I was browsing some news feeds with my SGS and I noticed some lag so I thought of restarting it, but to my surprise.. it was not booting anymore and it was stucked displaying the "S" screen then after a while it will go black although the buttons are still lighting up but there is no response or any activity in the screen and the only way to turn it off is to pull out the battery.
Upon getting home, I browsed the internet to find similar cases with most of the suggestions on how to "fix" this was to bring it back to Samsung Service Center and I'm not ready yet to do that so I dug in deeper to research. I just want to share the steps I have done to UNBRICK my almost Semi-bricked SGS.
First of all, my SGS doesn't have access to the 3 button mode recovery (Volume up + Power + Home) thus basically leaving me helpless because I cant reformat my phone from there and worst, in this case, my phone wont even boot up.
Secondly, it was fortunate that i had my phone rooted prior this.
Now, the process:
You should atleast have:
* KIES installed
* Android SDK
* USB Cable
First thing I did was:
* Connect my phone to the USB cable
* Turn phone on
* Wait for KIES to detect it and for windows to install necessary USB drivers (my phone was detected by KIES even if it was hanging in the "S" screen)
* When everything is done, go to COMMAND prompt in windows
* Locate where you initially placed the ANDROID SDK then Tools folder by typing it, example: (C:\Android-sdk\tools)
* when you are already in the right folder type in ADB REBOOT RECOVERY
* Check your SGS and it should be rebooting to the RECOVERY MODE wherein you will now be able to select format options
* move your selection by pressing up and down volume keys
* confirm your selection by pressing home key
* then reboot again and presto.. your phone should be up and running again
Anyway, if you cannot access the recovery mode by using the 3 button process, it could probably because your operator intentionally locked this feature out. There is a fix I found from XDA that works search for : 3 button mode fix
Hope this helps and drop me a message if you have queries.
By the way, i'm trying to restore my apps again so ciao for now.
-Charles
you forgot to mention something
You must have USB Debugging mode set to enabled before hand, before all of that happened, else if you simply plug the USB cable to the PC with the 3 button disabled, there is no way for it to accept the ADB Reboot Recovery command
The next best thing is as many have commented before
It's to use a hair drier to heatup the phone to get access to the 3 button recovery, for those that got stuck before installing the 3 button recovery fix
also forgot to mention that this has been asked, posted, discussed many many times already. i am glad, however, that you got your phone to work
but he has it listed in a very nice an easy to read format, compared to the other ones we have seen previously
my phone did that a lil while back but i have an early ship date phone there fore i have the hard ware recovery option but this is late coming how is it that every one always says to use odin to recover a bricked phone yet i guess im totally noobish but what good is a back up recovery tool if you cant mount storage
reycharlesconrad said:
Hi. Just a few hours ago while I was on my way home, I was browsing some news feeds with my SGS and I noticed some lag so I thought of restarting it, but to my surprise.. it was not booting anymore and it was stucked displaying the "S" screen then after a while it will go black although the buttons are still lighting up but there is no response or any activity in the screen and the only way to turn it off is to pull out the battery.
Upon getting home, I browsed the internet to find similar cases with most of the suggestions on how to "fix" this was to bring it back to Samsung Service Center and I'm not ready yet to do that so I dug in deeper to research. I just want to share the steps I have done to UNBRICK my almost Semi-bricked SGS.
First of all, my SGS doesn't have access to the 3 button mode recovery (Volume up + Power + Home) thus basically leaving me helpless because I cant reformat my phone from there and worst, in this case, my phone wont even boot up.
Secondly, it was fortu
Click to expand...
Click to collapse
This is the exact thing that happened to me
but I don't have USB debugging enabled
so how can I use ADB recovery ?
http://forum.xda-developers.com/showpost.php?p=7193770&postcount=8
somebody also help me
hey guys, im seriously in need of help.
my samsung galaxy s is disabled 3 button recovery mode. so i cannot go to recovery or download mode.
now my mobile cannot boot. i can only see samsung galaxy s and after sometime it blink but not booting. and i cannot use adb as i cannot go to desktop of my mobile.
please help me someone
nashaib said:
hey guys, im seriously in need of help.
my samsung galaxy s is disabled 3 button recovery mode. so i cannot go to recovery or download mode.
now my mobile cannot boot. i can only see samsung galaxy s and after sometime it blink but not booting. and i cannot use adb as i cannot go to desktop of my mobile.
please help me someone
Click to expand...
Click to collapse
Dont worry and use the searcher, you will find a easy and quick solution.
Build a JIG : Look at the wiki its a reference thread.
oh man, last few night, i could not sleep. i'm tired to search on google for all the nights.
nashaib said:
oh man, last few night, i could not sleep. i'm tired to search on google for all the nights.
Click to expand...
Click to collapse
Look the one that I made working:
http://www.youtube.com/watch?v=zoDUB1L9UIo
and the thread to see how to build it:
http://forum.xda-developers.com/showthread.php?t=819551
PD: It's just a phone, sleep is more important.
Help please
Hello guys
I was trying to unlock my vibrant(i was messing with my nv_data.bin) and then all of a sudden it rebooted and i couldnt connect to my service. It keeps going on off on off. My data doesn't work too.
Any thoughts on how to fix this?
THANKS (
Just restore the backup you made of nv_data.bin. You did back it up before you messed with it didn't you?!
Thanks vincler.....
you solved my problem. i made the jig after 2 months but i did it.
i combined the resistors with no solders and just touch the pins with my hands and i got download modes.
thanka again.
i must see how u did this witout soldering
nashaib said:
Thanks vincler.....
you solved my problem. i made the jig after 2 months but i did it.
i combined the resistors with no solders and just touch the pins with my hands and i got download modes.
thanka again.
Click to expand...
Click to collapse
i must see how u did this without soldering
It worked to recover my I9000 that was stuck in the "S" startup screen!
Thanks for sharing the idea; I didn't even thought that adb would work if the phone was stucked there (I thought it wouldn't finish loading it)
oh man mine wont even boot PLEASE HELP!!!!
This odd thing happened yesterday... I was using the latest ADW Launcher, I was pressing on my screen, suddenly one folder from another screen moved to the screen where my finger was on... The phone vibrated. Then I noticed that I can't drag the folder back to the previous screen, but after a while, I managed to drag it back to where its place was. After that, the phone started to be weird... It froze during start ups, after restarts and shut downs...
1. The live wallpaper that I set changes whenever I restart or turn off my smartphone. (Or is this just a common trait of the official ICS?)
2. I stated on the title that my phone freezes and somewhat reboots... What actually happens is, after the phone freezes for a few seconds (on start up), everything reloads - live wallpaper and widgets (they reload again even after they have been loaded on start up).
3. Suddenly, it seems like it heats up pretty quick.
NEWS FLASH: samsung kernels that brick the phones, http://forum.xda-developers.com/showthread.php?t=1633938
DO NOT use recovery
try writing to /system (with a root privileged file explorer) to see if it is writable, if it is writable then use PC ODIN go back to GB stock
I read the post in the link you posted. There it stated affected kernels of the ICS update... And it also stated, "DO NOT FLASH OR WIPE USING ANY ICS REPACK OR STOCK KERNEL"... I didn't flash or wipe any ICS repack or stock kernel, I updated through Samsung Kies...
Specifically, regarding those bad kernels, what are its "symptoms"?
- Hard, unrecoverable bricks.
- Unrepairable bad blocks in your flash memory -> probably something that you need got damaged.
You are using an affected kernel.
It COULD be the cause of your problem. If so,
I suggest warrenty repair
Yeah, could be. Will be monitoring it. Good thing I still have like more than 7mos. warranty on my phone.
Just for clarification: if I get an official ICS update for my phone (either OTA or through Kies) should I also NOT upgrade to ICS yet?
yuea said:
This odd thing happened yesterday... I was using the latest ADW Launcher, I was pressing on my screen, suddenly one folder from another screen moved to the screen where my finger was on... The phone vibrated. Then I noticed that I can't drag the folder back to the previous screen, but after a while, I managed to drag it back to where its place was. After that, the phone started to be weird... It froze during start ups, after restarts and shut downs...
1. The live wallpaper that I set changes whenever I restart or turn off my smartphone. (Or is this just a common trait of the official ICS?)
2. I stated on the title that my phone freezes and somewhat reboots... What actually happens is, after the phone freezes for a few seconds (on start up), everything reloads - live wallpaper and widgets (they reload again even after they have been loaded on start up).
3. Suddenly, it seems like it heats up pretty quick.
Click to expand...
Click to collapse
try using stock launcher.
My Verizon Wireless Droid 3 stopped booting normally on Tuesday evening. It has not been rooted or anything like that. When I boot it now, once the boot sequence has finished instead of displaying the home screen it stays stuck on the red animated boot screen for a little while and then goes completely blank. I cannot do anything with the phone - none of the buttons work. I can hear some audio notifications however so it seems to be booted completely, but locked to any user input. I get the same behavior when booting it in safe mode. If I call my cell phone from a landline, it receives the call, displays the incoming call on the screen, and I can accept or reject it using the normal screen swipe motions. When the call is answered, I can talk/hear as well as use the in-call dial pad. I cannot, however, use any of the 4 buttons at the bottom of the phone or access the notification bar at the top of the screen. As soon as the call ends, the screen becomes unusable/blank again.
Once booted in this state, after a couple of minutes it sort of resets, in that it sounds/displays the "Droid" message, followed by the red animated boot screen. However, if connected to my computer when this happens, the two external drives do not disappear, which seems to indicate that the phone is still at least semi-booted during this time? If left alone, that cycle repeats and repeats (every few minutes it sounds/displays "Droid" then the red animated boot screen).
When I connect a USB cable to my computer while the phone is up in this state, it displays two empty external drives.
Through research on this forum and others I have downloaded/installed adb and the Android SDK. I cannot get adb to recognize the phone, presumably because I'm quite sure USB Debugging was not enabled on my phone before it started acting up.
When booting via FastBoot and connecting via USB it recognizes a "Android ADB Interface" device in device manager, however adb itself still does not recognize the device.
Doing a factory reset is not an option at this point due to encrypted files/photos on the phone/sd card. I had to turn encryption on in order to use my corporate e-mail on the phone.
The boot menu gives me these options:
Normal Powerup
Recovery
AP Fastboot
BP SBF Flash
BP Only
BP HW Diag & Boot AP
BP Tools
Can anyone give me some advice on gaining access to the phone via adb or anything else? I've seen mention of Early USB Enumeration on some other androids, but am not seeing this option on my phone anywhere.
Forgot to mention that I also tried wiping the phone's cache via the recovery menu, but to no avail.
jessman1128 said:
My Verizon Wireless Droid 3 stopped booting normally on Tuesday evening. It has not been rooted or anything like that. When I boot it now, once the boot sequence has finished instead of displaying the home screen it stays stuck on the red animated boot screen for a little while and then goes completely blank. I cannot do anything with the phone - none of the buttons work. I can hear some audio notifications however so it seems to be booted completely, but locked to any user input. I get the same behavior when booting it in safe mode. If I call my cell phone from a landline, it receives the call, displays the incoming call on the screen, and I can accept or reject it using the normal screen swipe motions. When the call is answered, I can talk/hear as well as use the in-call dial pad. I cannot, however, use any of the 4 buttons at the bottom of the phone or access the notification bar at the top of the screen. As soon as the call ends, the screen becomes unusable/blank again.
Once booted in this state, after a couple of minutes it sort of resets, in that it sounds/displays the "Droid" message, followed by the red animated boot screen. However, if connected to my computer when this happens, the two external drives do not disappear, which seems to indicate that the phone is still at least semi-booted during this time? If left alone, that cycle repeats and repeats (every few minutes it sounds/displays "Droid" then the red animated boot screen).
When I connect a USB cable to my computer while the phone is up in this state, it displays two empty external drives.
Through research on this forum and others I have downloaded/installed adb and the Android SDK. I cannot get adb to recognize the phone, presumably because I'm quite sure USB Debugging was not enabled on my phone before it started acting up.
When booting via FastBoot and connecting via USB it recognizes a "Android ADB Interface" device in device manager, however adb itself still does not recognize the device.
Doing a factory reset is not an option at this point due to encrypted files/photos on the phone/sd card. I had to turn encryption on in order to use my corporate e-mail on the phone.
The boot menu gives me these options:
Normal Powerup
Recovery
AP Fastboot
BP SBF Flash
BP Only
BP HW Diag & Boot AP
BP Tools
Can anyone give me some advice on gaining access to the phone via adb or anything else? I've seen mention of Early USB Enumeration on some other androids, but am not seeing this option on my phone anywhere.
Click to expand...
Click to collapse
Since you said you can receive calls, during a call, place in speakerphone mode and hit the HOME button. It should background the call to the notification bar and unlock sliding down the notification bar and take you to the home screen. (using AT&T I can do this to stay in call and browse/do whatever on data while in a call).
Have someone (or you) call the phone, press home, then hit Menu > Settings > Applications > debugging and enable USB debugging. This should get you ADB, do NOT hang up during this just in case.
Skreelink said:
Since you said you can receive calls, during a call, place in speakerphone mode and hit the HOME button. It should background the call to the notification bar and unlock sliding down the notification bar and take you to the home screen. (using AT&T I can do this to stay in call and browse/do whatever on data while in a call).
Have someone (or you) call the phone, press home, then hit Menu > Settings > Applications > debugging and enable USB debugging. This should get you ADB, do NOT hang up during this just in case.
Click to expand...
Click to collapse
I can place the call in speaker mode, but the home button (plus the other 3) still do not work, nor does the notification bar (although I can see the notification bar). At some point it did delegate the call to the notification bar (although not immediately after placing it in speaker mode), but at that point the rest of the screen went black and only the notification bar was visible (but not accessible). I did receive a message this time, right before answering the call, that process Home Screen was stuck or something and it prompted me to either force close or wait. I told it to wait. And now it just initiated a partial reboot, even though I was still in-call.
Also, in case it's relevant, I am using LauncherPro as my home screen.
jessman1128 said:
Also, in case it's relevant, I am using LauncherPro as my home screen.
Click to expand...
Click to collapse
Sounds like something may have happened to LauncherPro, and since it's your default launcher, the home button isn't going back to regular motorola home. Try booting the phone and (hoping) if it has a data connection, on your PC go to https://play.google.com/apps login, it should display your devices, click on your Droid 3, find LauncherPro, and uninstall remotely. It should be the small trash-can next to where it says 'installed'
OR you can try installing another launcher, such as ADW, Go Launcher, etc. and remotely installing it, then hitting home, which SHOULD reprompt for default launcher/home.
Maybe do a combination of the two, just to insure you're not stuck without a launcher at all, though not rooting, MotorolaHome shouldn't have been affected.
Skreelink said:
Sounds like something may have happened to LauncherPro, and since it's your default launcher, the home button isn't going back to regular motorola home. Try booting the phone and (hoping) if it has a data connection, on your PC go to [] login, it should display your devices, click on your Droid 3, find LauncherPro, and uninstall remotely. It should be the small trash-can next to where it says 'installed'
OR you can try installing another launcher, such as ADW, Go Launcher, etc. and remotely installing it, then hitting home, which SHOULD reprompt for default launcher/home.
Maybe do a combination of the two, just to insure you're not stuck without a launcher at all, though not rooting, MotorolaHome shouldn't have been affected.
Click to expand...
Click to collapse
You are a lifesaver. You rock. You are awesome. I'd click Thanks on your post one thousand times if it would let me. I have my phone back!
I followed both suggestions - I loaded the Play store on my computer and installed ADW as well as removed Launcher Pro plus a few other apps. It took I think 3 boot cycles before it finished making all of those changes on my phone (because it would only stay up for 1-2 minutes each time), but once it was done I had my phone back.
I could access my pics on my phone then, but not on my computer. Due to them being encrypted you have to connect in PC Mode for it to decrypt them properly when copying to the computer, but in PC Mode it wasn't registering the right drivers. Took me awhile to track down the proper ones online (I was looking at Verizon when it was actually Motorola drivers I needed), but I finally found them and installed them and just finished copying over all my pics to my computer - and verified they decrypted properly.
In recent weeks I've been kicking around the idea of rooting my phone and installing a custom rom. Thinking this might be a good time to try it now that I have everything copied off of my phone now. I don't know much about custom roms though. Do you happen to know if any of the available ones for D3 will support corporate e-mail?
jessman1128 said:
I could access my pics on my phone then, but not on my computer. Due to them being encrypted you have to connect in PC Mode for it to decrypt them properly when copying to the computer, but in PC Mode it wasn't registering the right drivers. Took me awhile to track down the proper ones online (I was looking at Verizon when it was actually Motorola drivers I needed), but I finally found them and installed them and just finished copying over all my pics to my computer - and verified they decrypted properly.
Click to expand...
Click to collapse
Good news. But, do yourself a favor - try activating a service that automatically uploads all photos, such as Google+ or Dropbox or Sugrasync. That way if you ever get to a point where you need to factory reset you'll have copies of your photos somewhere else.
jessman1128 said:
You are a lifesaver. You rock. You are awesome. I'd click Thanks on your post one thousand times if it would let me. I have my phone back!
I followed both suggestions - I loaded the Play store on my computer and installed ADW as well as removed Launcher Pro plus a few other apps. It took I think 3 boot cycles before it finished making all of those changes on my phone (because it would only stay up for 1-2 minutes each time), but once it was done I had my phone back.
I could access my pics on my phone then, but not on my computer. Due to them being encrypted you have to connect in PC Mode for it to decrypt them properly when copying to the computer, but in PC Mode it wasn't registering the right drivers. Took me awhile to track down the proper ones online (I was looking at Verizon when it was actually Motorola drivers I needed), but I finally found them and installed them and just finished copying over all my pics to my computer - and verified they decrypted properly.
In recent weeks I've been kicking around the idea of rooting my phone and installing a custom rom. Thinking this might be a good time to try it now that I have everything copied off of my phone now. I don't know much about custom roms though. Do you happen to know if any of the available ones for D3 will support corporate e-mail?
Click to expand...
Click to collapse
Most likely any roms that are built on the D3 source will unless they stripped it. I use Maverick rom 4.0 myself, it is based on 906 with enhancements, debloat, themed, etc. There are still many bugs to work out on AOSP built roms (cyanogenmod, aokp, etc. Any ics/jb roms). I would suggest sticking with a stable gb rom if it is your business phone.
doogald said:
Good news. But, do yourself a favor - try activating a service that automatically uploads all photos, such as Google+ or Dropbox or Sugrasync. That way if you ever get to a point where you need to factory reset you'll have copies of your photos somewhere else.
Click to expand...
Click to collapse
That sounds like a good idea. I wonder, though, if those services would upload the encrypted or decrypted version of the photos. I'll have to test it and see.
Skreelink said:
Most likely any roms that are built on the D3 source will unless they stripped it. I use Maverick rom 4.0 myself, it is based on 906 with enhancements, debloat, themed, etc. There are still many bugs to work out on AOSP built roms (cyanogenmod, aokp, etc. Any ics/jb roms). I would suggest sticking with a stable gb rom if it is your business phone.
Click to expand...
Click to collapse
Hmm, ok. I'll have to give it some more thought then. It's my personal phone, but I do have my work e-mail setup on it and access it fairly regularly. I don't absolutely need to have my work e-mail on my phone, but it's certainly very helpful to have it setup there.
I've also been thinking about doing a factory reset, as the phone in general has gotten progressively slower as time goes on. Thinking the factory reset might help in that regard. I wonder if there's any way to remove some of the stock Verizon apps I never use when doing a factory reset. I'll have to look into that. I guess I should go search these forums again!
jessman1128 said:
That sounds like a good idea. I wonder, though, if those services would upload the encrypted or decrypted version of the photos. I'll have to test it and see.
Click to expand...
Click to collapse
I setup FolderSync to upload my photos to Google Drive and it is successfully uploading them in decrypted form. Thank you for the suggestion!
Hi guys,
My phone is in a permanent state of rebooting. I have searched these forums and other websites, but none of the solutions I found apply to my situation. I am going to provide as many details as I can here, even if they seem irrelevant.
My phone when it crashed
Sony Xperia V, stock firmware 9.2.a.1.210. (Which is the second latest. Couldn't get latest because neither Sony PC Companion or Update App found updates. This was BEFORE rooting.)
Rooted this morning using Towelroot.
(EDIT) Then I installed latest version of SuperSU.
Unless Towelroot somehow unlocks bootloader, I have a locked bootloader.
Deleted some pre-installed apps (which is why I rooted in the first place). Using Clean Master, I removed:
Google Play Movies
Google Play Books
Google Play Magazines
Sony Select
Sony Music Unlimited
Sony Xperia Link (Not sure about name. Used to view stuff like messages on other devices. Purple icon.)
I think that is all. I'm pretty sure I didn't remove anything vital. (My knowledge of Android is limited, and so I didn't go on a killing spree.)
Using Xperia Smart Connect, (I decided to try it after all), I set up an event. (When connecting to my TomTom Go, switch off Wifi. Afterwards, Switch on Wifi. The TomTom was turned off.)
Everything was fine after that.
The crash
Later on, I wanted to take a picture using the stock app. The app launched and worked for a few seconds, displaying what the camera registered. Then, the screen froze. After some time, I tried turning off my phone, to no avail. So I removed the battery. Re-inserted battery, pressed power button. Since then, my phone keeps on rebooting.
What happens exactly
After I insert the battery and press the power button, the phone vibrates and seems to boot normally. I get the colorful boot animation, followed by the lock screen. A lot of systems seem to be functioning correctly:
The lock screen looks normal. It displays the background I have set (from the stock Winter theme, I think) and shows the authentication dialog (more on that later).
The displayed time was correct after the first few boots, before I removed the battery for longer than a few seconds. After that, it was wrong a couple of times, before getting it right again a few boots later.
Other icons being shown in the status bar: Bluetooth (grayed out, which is normal if there's no connected device), no SIM card, no network, battery status (correct) and Wifi (best reception with constant up and down arrows).
The notification LED works. (Changes with battery status.)
"Battery almost empty" sound when applicable.
My phone never registers any input on the touch screen, save for one time, when it registered the first digit of my PIN code. After a while of displaying the lock screen, the whole screen turns a certain color (I've seen different colors on different occasions: red, purple, ...) like some kind of color filter is being applied. (The image is visible, but in one color.) After, that it fades into black and reboots.
What I have tried
Charging the phone for about an hour. The power led is orange when charging, meaning the battery has a decent amount of juice.
Removed the battery several times (one time for over fifty minutes). After I re-insert it, I need to press power button to get it to boot, which is of course normal. (As opposed another thread I've read, where the phone would boot as soon as the battery was inserted.)
Connecting to PC using USB cable and Sony PC Companion (SPC). SPC can't connect, most likely because the phone reboots before it can finish detection process.
Tried a forced reboot by pressing and holding power+volume up. Has no effect.
After a few reboots, I removed SIM and SD cards. The only effect that had: instead of the enter PIN code dialog, I get the "connect the dots" dialog. (Which makes sense.) No input is being registered. The pattern (dots) used to be my secondary authentication method, the primary being facial recognition. My phone doesn't seem to initiate facial recognition.
Let it reboot repeatedly. I estimate it has rebooted 15-20 times now.
On flashing
If flashing is my only option, I want to try Cyanogenmod instead of Sony firmware. I'd rather not flash at all, though, since I have no experience. All of my data has been backed up, so an internal wipe is no deal breaker.
If I do have other options, I'd prefer the quickest and simplest method of getting my phone operational. Provided there is one...
Phone is acting very irregular. Was able to unlock lockscreen using dot pattern twice, but froze after loading some home screen elements. Didn't get past lock screen on other occasions.
After crashing, sometimes forgot battery level. Claimed almost empty while almost full seconds before that.
Etc etc.
So! Want to flash to Cyanogenmod using this guide.
Downloaded and installed ADB here.
Flashtool drivers here. Installed following drivers from package:
Flashmode Drivers
Fastboot Drivers
Common drivers Blue3.0 board (Xperia V, T, TL, ...)
And a bunch of device specific drivers, since Xperia V wasn't literally listed. ("Xperia VL" came closest but didn't do the trick - ADB couldn't find device.)
Backed up current boot image (ROM) and system. (Couldn't mount \data). I don't think I'll be missing these files?
When trying to push Cyanogenmod zip, adb gives "error device not found".
Download additional drivers here (Sony Xperia VL drivers).
Still not doing the trick. Windows shows a device "Xperia V" with inadequate drivers and won't accept the VL drivers.
Can't seem to find fitting drivers anywhere.
Never mind. Bypassed the entire problem by inserting SD into PC, copying zips I needed to push manually, re-inserting SD into phone, rebooting ("fastboot reboot" from console) and installing zips from recovery menu.
Just writing this down for anyone else who's struggling with this.
Sorry for the messy monologue. Been at this for the better part of the day now, and it's currently 1:47 at night here. So I'm kinda tired. But happy
Still would like to know how to get decent drivers ADB drivers for Xperia V, though.