Related
Hello everyone and thank you for your time in advance.
First of all, I'm relatively new to the Android OS so forgive me for any mistakes I make describing my problem. I'll try to give as many details as I can, mostly steps I took that I believe that might have led me to my problem, but please feel free to ask anything if you think it could help.
TL;DR version: My problem is this: I'm stuck in the Google Account signing in screen. The phone is requesting me to "Slide keyboard open to continue" while I don't have any keyboard and there is no box on the screen where I would press and the digital keyboard would appear.
So, I have a Sony Xperia X10 mini (i guess its short name is x10i?). A year or more ago I firstly rooted my phone, used xRecovery to flash Cyanogen Mod on it. I'm sure I had the 2.3 Gingerbread version of it. My first "problem" is that when I first looked into the rom's settings (CM Settings) it had many options with the HTC abr in front of it. I didn't tweak most of the options that had that HTC tag on them, only those concerning the keyboard. When I tried to type, it showed different versions of a keyboard on screen, but it always showed a keyboard up. Keep this in mind.
Now, 2 months ago, a friend of mine did something to his android (a galaxy one, cant remember which) and he said the applications were running smoother. He is kinda more informed about Androids than I am so I trusted him and we tried to do the same thing to my phone. It was about Fixing Permissions or something. I deleted the cache he told me through xRecovery (after I backed up ofc) and then booted the phone, only to find my settings and user data lost. The backup I made that day was possibly not complete or something, because when I tried to restore it, it failed and so I lost my SMS/contacts etc. I restored a much older back up and it DID work but I decided to run the most recent one anyway.
From that day on, my phone somehow decided to return all calls as busy. Whenever someone called me, it gave them the busy message and after a while I got a message that they called me. Sometimes for a single call (or irrelevant to calling SMS they sent at another time) I recieved many exact same SMSes. I put up with this situation for a while and tonight I decided to reset my phone and get a new mod in it, or even refresh the same - I didn't really care. So I exported my contact list which was all I cared to save to a file in my sd card (which file I backed up) and tried to see if my xRecovery worked, because my friend told me that it all may have to do with it being corrupt or something.
The result is that I couldn't even get to the Recovery. Not with pressing the power button, choosing to reboot from recovery. Not even with the power button and back button pressed, or repeatedly pressed. Then, I decided I just wanted to reset the phone so I foolishly thought of a factory reset so I could reroot if needed and do the process from scratch. I chose the option, it rebooted. After the Sony Ericsson logo though the Cyanogen Mod logo started to load, which made me wonder why since I thought it would just load the firmware it had when I bought it. And then it started with the press the Android to begin (after the PIN request) and now I'm stuck in the google account set up.
Please help me out, I apologize for the wall of text. It would certainly be fine with me to somehow reset the phone to the state it was when I bought it using SEUS or something like that. I tried doing that tbh, but then all this firmware came up and I didn't know which one to choose plus I can't find a working link to download SEUS, PC Companion etc. Otherwise just please help me out with the rom i used and how to fix this keyboard problem cause I'm thinking the rom wasn't good for my x10mini. Also is there any way to see my sd card's contents via USB with the state my phone is in?
You can skip the google-account setup in the setup wizard ( I think there's three buttons below each other, just press the bottom one and it will guide you through the wizard without actually having to type something
A factory reset just resets all values to factory (or custom ROM) values and deletes all user-data (except the stuff on your sd-card), it won't restore the original ROM.
If you want to start over, do a repair with SEUS (SUS nowadays) of PC Companion, which will give you stock 2.1 back, after which you can go through root etc. again to get your current ROM back..
Or you can give me a pm and i'll provide you with stock firmware which can be flashed using flashtool.. I assume you are still on the stock kernel, ie, you haven't unlocked your bootloader?
ps: the x10 mini is the E10(i or a) or Robyn, the x10 (the big one) is the X10(i or a)
Thread moved. Please post all questions here in Q&A in future.
Thanks
AvRS
Ok, so I have a serious problem... My phone is locked and when I touch the text bar to enter the password, no keyboard comes up. Important information:
- I just upgraded to jelly bean (the official one that came out today)
- as far as I can tell, everything is working fine, i just can't unlock it
- when I touch the text bar, it makes a noise, but no keyboard comes up
- was working fine immediately after the upgrade
- I got done fixing some settings and locked the screen
- this may have something to do with changing the default keyboard to Google Keyboard (it was acting a little funny immidiately after, like it was crashing)
- I have Android Lost installed, the unlock function isn't working, but others do work
- phone is encrypted
Unless someone has some ideas for me within the next couple hours, I'm going to wipe the phone. Obviously, I would prefer to not do that.
==========================
EDIT:
I've managed to use Android Lost to make some backups of some stuff, but I'm still trying to figure out how to unlock the screen. I've found that I'm able to install apps remotely from google play if that gives gives anyone some ideas.
=============================
EDIT2:
I had another idea. If this is a problem with the keyboard, is there a way for me to change it remotely? Can I install another one via the store?
Alright... I gave up on trying to get passed the lock screen and tried doing a factory reset. I was afraid of the super brick issue, so instead of doing a wipe in recovery mode, I used Kies to reflash it. However, that did nothing. The phone started back up and acted like nothing happened. It asked me for the same password, then got to the lock screen and had the same keyboard issue.
I've tried various roms, but nothing seems to wipe the encrypted information properly. At some point, I got it to forget the password, but it still thinks that one exists. I even rooted it and tried shostock3, but when it boots, it asks for a password. The old password doesn't work, so I can't get passed it. I tried entering the "wrong" password many times and it said it would wipe the phone, but it just restarted to the SAMSUNG boot screen and just sat there. I pulled the battery after half an hour...
I should note that stock gingerbread seems to work fine...
Does anyone have any ideas on how to wipe the encrypted data?
If you can push apps to it, try pushing an app like no lock or something.
Short answer: No.
It is probable that encryption information is stored in the efs (encrypted file system) folder. That's where the imei and other critical stuff is stored. I don't believe anyone who posts here in the I777 forum really has a grasp on how phone encryption works though. I've only seen one other person post here who had an issue with an encrypted phone, and he was unable to solve his problem as far as I know.
If you have a proper backup of the efs partition from before the phone was encrypted, it is possible that you could solve the problem by restoring that partition. But I'm not even sure you could write to that section of the phone memory with adb with the phone in it's current state. Edit: if you can boot into stock gingerbread normally, then you can restore an efs backup, if you have one.
I'm guessing you could send it to Samsung and they could fix it for you probably.
I finally got it working. I'm not sure what combination of things did it, but I had to restore it to stock jelly bean (via kies) to get it to wipe the encryption. I guess the stock rom knows how to properly wipe it when you keep entering the wrong password. After I got it all cleaned up, I put shostock3 back on. When the battery charges back up, I'm going to try encrypting it again (in shostock).
However, now I found another issue (may or may not be a real problem). I wanted to check if the phone was still unlocked, so I dialed *#SIMLOCK# and it says "Connection problem or invalid MMI code."
Tada!
Creepy, my good friend, would be referring to me and as you know SCIU I didn't ever get it to unlock the phone. Oddly enough a stock ICS rom (my mom now has my phone right up the road so I may try this to see if it will work and then go back to ShoStock3) works fine. I have nothing hidden from the phone storage, everything shows up, it is actually unlocked and rooted though not a custom bios err firmware/ROM because when that is put on there the encryption issues come back and the password is asked for. If the correct password is entered (and my KEYBOARD comes up but I didn't change it from the Android/Samsung one) it proceeds to enter whatever it is supposed to (my guess is the POST area like on a computer when it is entering Windows/Linux, etc.) but the screen stays black (ShoStock logo doesn't even appear if I remember correctly or it does show then goes to black loading screen with the Samsung logo and that is it, perm stuck). However I did try flashing back to Gingerbread ROMs and ICS ROMs though not through official KIES.
SCIU I may have to give this a try if my mom don't mind it and see if that helps fix the problem. Thanks for starting this thread. I am sorry I didn't respond to the PM you sent me (my LGOG, Triple OG, OG, TRIPLE OG, Optimus G AT&T Phone has screen cracked twice and is unresponsive on two different phones so I sent that in to warranty repair [rapid heating and cooling issues]) and haven't been on XDA for a week. If there is anything else you need to ask or bounce ideas off of me then I am all for it.
As far as encryption goes, the process works the same as any other encryption algorithms used (MD5/HASH/SHA-!, etc.) using a basic replica of most file systems although mobile storage tends to work a tad differently. Unfortunately, the freezer trick, brute force, nor any other cracking methods I was able to try at home worked to get it to open up. I tried getting into the EFS area of the phone but never could get to the directory or have it display.
Again thanks SCIU and as I stated I may give this a try if my mom don't care.
Eagle
i've the same problem here but i cann't use kies when my phone is locked .... so what can i do??
rawan-omer said:
i've the same problem here but i cann't use kies when my phone is locked .... so what can i do??
Click to expand...
Click to collapse
You can get the full stock jelly bean Odin flashable tar in the Download Repository. See link in my signature. According to sciguy125, flashing stock jb and then inputting repeatedly the wrong password will clear it. I'm not sure how many times it takes, 5 or 10 I think. I've never worked with an encrypted phone. I'm just repeating what I have read others say. I've seen the above posted by at least one other person. You should be able to flash the stock firmware using Odin. The one you want is I777UCMD8
my phone screen is locked (with word password) , Huawei, and the keyboard doesnt show up when i click the box? tried reseting it, cant go to settings whatsoever! i didnt damage my phone in any way either. need help asap!!
moselyy said:
my phone screen is locked (with word password) , Huawei, and the keyboard doesnt show up when i click the box? tried reseting it, cant go to settings whatsoever! i didnt damage my phone in any way either. need help asap!!
Click to expand...
Click to collapse
Friend, this is the forum for the S2 (Samsung), so you won't find anything about Huawei devices here - best to ask your question in the forum for your device.
That being said if you are rooted and have a custom recovery, simply power the device off and boot into recovery and perform a factory reset from there. If that doesn't work do a full wipe (this means wiping /system), then re-flash the ROM/gapps.
me too!!! do you have some tips for me?? i almost fainted when i knew that the keyboard isnt working.... i do have a lot of important files in my phone.
Easy, you fools! JUST KIDDING lol Connect an external keyboard. Restart the phone with the keyboard plugged in and you'll have one chance to input the pass every time you restart. Good luck, bosses!
my phone screen is locked (with word password) , SAMSUNG GALAXY TAB 3V, and the keyboard doesnt show up when i click the box? tried reseting it, cant go to settings whatsoever! i didnt damage my phone in any way either. need help asap!
My sumsang keyboard has stopped I cannot do nothing because is secure by password can you help please
I got the same problem but everything on my phone is fine except it doesn't let me enter the password I dnt wanna factory reset it cause I got important pictures in it any suggestions on how to get my keyboard working.
Solution that worked for me
Hello all,
I usually don't post things around, but something told me to do this, since I don't see any threads talking about this solution.
My solution was the following:
Went to google play store on my computer via chrome. Logged in to the user attached to my play store and re-installed all keyboard apps I have.
That worked beautifully and hope this helps other people!!
Good evening all, my apologies in advance if i am asking a stupid or already answered question,
i have looked through this forum and many others along side through google and i am unable to find a solution or solved post in regards to fixing this phone.
I recently purchased a second hand s2 from ebay, not the best move but it was cheap, and i was in need of a phone.
the phone came with damaged screen, so i ordered a replacement and thought no more.
after receiving the screen i replaced it fitted it and was in the belief that the phone would be up and running, no no no this is not the case...
upon fitting the screen i found that the phone would lag as such, as if two fingers were placed on the screen, with motions being very sticky also requiring a large amount of force to respond when trying to use it. normal androids will switch between home screens effortlessly and relatively fluid.
Seeing this issue i thought a simple firmware upgrade would suffice and id have a usable phone. upon upgrading via kies i was unable to install the MTP drivers and so switched to the program odin for the update.
i downloaded what i believe to be uk firmware from samsung-updates,
firmware I9100XWMS2_I9100BULS3_I9100VODLSF_HOME
which has also caused the phone to boot in what looks to be spanish. although e3 and cwm show in english.
after the update the phone seems to be in a soft bricked state, the phone will repsond to input from soft keys, go into recovery and download mode accept all firmwares i have tried 9 times out of 10. but when reaching the android home screen is completely frozen, no response from touch or soft keys, except only for volume up and power to reset the device.
thinking the recently purchased LCD was the culprit i have sent it back and had a replacement, still the issue is present.
I have tried many different roms/kernels in the hope to solve this problem and i am at my wits end!
any help in bringing this thing back to life would be of great help as i am without a phone, or enough money to replace it again...
thanks for any response
cheers Ansell2k12
Hopper8's 'Odin troubleshooting' thread stickied in the General section; in particular flashing the 3 part firmware (this will wipe your phone). Also try everything in that thread for as long as you have the patience for it. These cases tend to be fixed by perseverance, or not at all. There's no easy fix. It's either a hardware issue(s), NAND corruption, or something really obvious being missed here. If it's the latter, hopefully the stuff in Hopper's thread helps you fix it. If it's either of the other two, I'd be cutting my losses.
Ansell2k12 said:
Good evening all, my apologies in advance if i am asking a stupid or already answered question,
i have looked through this forum and many others along side through google and i am unable to find a solution or solved post in regards to fixing this phone.
I recently purchased a second hand s2 from ebay, not the best move but it was cheap, and i was in need of a phone.
the phone came with damaged screen, so i ordered a replacement and thought no more.
after receiving the screen i replaced it fitted it and was in the belief that the phone would be up and running, no no no this is not the case...
upon fitting the screen i found that the phone would lag as such, as if two fingers were placed on the screen, with motions being very sticky also requiring a large amount of force to respond when trying to use it. normal androids will switch between home screens effortlessly and relatively fluid.
Seeing this issue i thought a simple firmware upgrade would suffice and id have a usable phone. upon upgrading via kies i was unable to install the MTP drivers and so switched to the program odin for the update.
i downloaded what i believe to be uk firmware from samsung-updates,
firmware I9100XWMS2_I9100BULS3_I9100VODLSF_HOME
which has also caused the phone to boot in what looks to be spanish. although e3 and cwm show in english.
after the update the phone seems to be in a soft bricked state, the phone will repsond to input from soft keys, go into recovery and download mode accept all firmwares i have tried 9 times out of 10. but when reaching the android home screen is completely frozen, no response from touch or soft keys, except only for volume up and power to reset the device.
thinking the recently purchased LCD was the culprit i have sent it back and had a replacement, still the issue is present.
I have tried many different roms/kernels in the hope to solve this problem and i am at my wits end!
any help in bringing this thing back to life would be of great help as i am without a phone, or enough money to replace it again...
thanks for any response
cheers Ansell2k12
Click to expand...
Click to collapse
lcd may be the culprit but also the firmware is crashed flash it again properly after a factory reset from e3
Progress...but not as id hoped...
first off thanks to you mistahbungle & bhavstech,
unfortunately im only little further forward.
After the flash using 3 part file firmware the phone is now running in English language on an updated firmware, but still appears to be frozen/ crashed.
updates on appearance, maybe its still salvageable?
Clock now updates after reboot
English language
charge icon does not change when unplugging/replugging charger/data cable but is recognized by the PC - MTP is now installing, but requires reboot, after reboot of the PC, MTP installs again and request reboot again... and continues to do so.
clock doesn't update at home screen, again appears to be frozen/crashed
still no response to touch, touch buttons or soft keys - only phone rest volume up and power.
when phone is at samsung splash screen i get notification of voice mails/texts on the phone.
Thanks again Ansell2k12
Ansell2k12 said:
first off thanks to you mistahbungle & bhavstech,
unfortunately im only little further forward.
After the flash using 3 part file firmware the phone is now running in English language on an updated firmware, but still appears to be frozen/ crashed.
updates on appearance, maybe its still salvageable?
Clock now updates after reboot
English language
charge icon does not change when unplugging/replugging charger/data cable but is recognized by the PC - MTP is now installing, but requires reboot, after reboot of the PC, MTP installs again and request reboot again... and continues to do so.
clock doesn't update at home screen, again appears to be frozen/crashed
still no response to touch, touch buttons or soft keys - only phone rest volume up and power.
when phone is at samsung splash screen i get notification of voice mails/texts on the phone.
Thanks again Ansell2k12
Click to expand...
Click to collapse
Your issue of a semi frozen state is very familiar to me but the reasons can be many and one of those are the /sdcard partition not mounting properly and likewise it could also be a failure of the other major partitions but if the device booted and made it to the lockscreen then you may have some hope, first if you have a external card plugged try booting without it, if the issues repeat try swapping the ext card with the internal /sdcard by flashing a modified vold.fstab file for your firmware which swaps the partitions effectively making the device mount the ext card as the /sdcard partition. I am expecting you have gone through the default troubleshooting methods like a clean flash etc.
Sent from my GT-I9100 using Tapatalk
king_below_my_lord said:
Your issue of a semi frozen state is very familiar to me but the reasons can be many and one of those are the /sdcard partition not mounting properly and likewise it could also be a failure of the other major partitions but if the device booted and made it to the lockscreen then you may have some hope, first if you have a external card plugged try booting without it, if the issues repeat try swapping the ext card with the internal /sdcard by flashing a modified vold.fstab file for your firmware which swaps the partitions effectively making the device mount the ext card as the /sdcard partition. I am expecting you have gone through the default troubleshooting methods like a clean flash etc.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Yes i have done multiple flashes, tried another sd card as the original was unreadable by the phone but picked up the second faultlessly, although flashing a custom firmware failed when trying to load in cwm.
as for a modified vold.fstab file,this is new to me. Could i ask how its modified or where i would get the file? im guessing id use odin to flash it to the device?
thanks for the response
Ansell2k12
Ansell2k12 said:
Yes i have done multiple flashes, tried another sd card as the original was unreadable by the phone but picked up the second faultlessly, although flashing a custom firmware failed when trying to load in cwm.
as for a modified vold.fstab file,this is new to me. Could i ask how its modified or where i would get the file? im guessing id use odin to flash it to the device?
thanks for the response
Ansell2k12
Click to expand...
Click to collapse
There are some threads in which I myself detailed about swapping memory its done via a custom recovery and not using Odin.
Sent from my GT-I9100 using Tapatalk
??
king_below_my_lord said:
There are some threads in which I myself detailed about swapping memory its done via a custom recovery and not using Odin.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
any chance you could point n the right direction?
i have had a look at the stuff to edit vold, and it seems i am unable to do so as my phone isnt usable once booted
cheers Ansell2k12
Phone has gone in the bin cheers guys, thanks for the help
....
You could easily flash a edited vold.fstab file by generating a flashable zip file. That's why I said via recovery or if you are clever enough you can easily use recovery flashable Aroma file manager to overwrite the file.
Sent from my GT-I9100 using Tapatalk
I have the GT-S7560M through Solo (Bell) and I rooted it shortly after purchase last year. I've been happy with the phone and for the last few weeks an upgrade notice has been appearing but would fail when applied. Some searching suggested the root was interfering. At first I started to look into un-rooting the phone, but then thought that a factory reset would be the simplest, least-risky solution. I had done a factory reset on my last Galaxy phone without a problem so it seemed like a safe choice. I backed up the contact info, etc with Kies (I don't use many apps so I didn't go all out ie Titanium Backup) and removed my SD card.
Now the phone boots to screen asking me to pick a language and press Start. Then it moves on to a black screen with the info bar at the top (clock, cell strength, data xfer) and nothing else. It is auto-rotating. The phone does react to touches with the buttons lighting up, but I can't get anywhere. Kies can see the phone, the phone number, the firmware version and all that. It reports Internal Memory as 84.83MB used of 1.58GB. I can navigate through the phone using Windows Explorer. I did a Restore with Kies but it doesn't seem to have had any relevant effect.
I am able to boot into CWM Recovery. I don't remember doing a back-up with it, and when I ask it to restore from either the SD card or the interal SD it says it can't mount.
At this point I would start thinking about taking the phone back to the store, but a flash counter appears during start-up and I'd rather they didn't see that for obvious reasons.
When I google I just get people who have bricked their phones. I just want my phone to work again. I'm not worried about modifying it further to achieve that.
Yoqui said:
I have the GT-S7560M through Solo (Bell) and I rooted it shortly after purchase last year. I've been happy with the phone and for the last few weeks an upgrade notice has been appearing but would fail when applied. Some searching suggested the root was interfering. At first I started to look into un-rooting the phone, but then thought that a factory reset would be the simplest, least-risky solution. I had done a factory reset on my last Galaxy phone without a problem so it seemed like a safe choice. I backed up the contact info, etc with Kies (I don't use many apps so I didn't go all out ie Titanium Backup) and removed my SD card.
Now the phone boots to screen asking me to pick a language and press Start. Then it moves on to a black screen with the info bar at the top (clock, cell strength, data xfer) and nothing else. It is auto-rotating. The phone does react to touches with the buttons lighting up, but I can't get anywhere. Kies can see the phone, the phone number, the firmware version and all that. It reports Internal Memory as 84.83MB used of 1.58GB. I can navigate through the phone using Windows Explorer. I did a Restore with Kies but it doesn't seem to have had any relevant effect.
I am able to boot into CWM Recovery. I don't remember doing a back-up with it, and when I ask it to restore from either the SD card or the interal SD it says it can't mount.
At this point I would start thinking about taking the phone back to the store, but a flash counter appears during start-up and I'd rather they didn't see that for obvious reasons.
When I google I just get people who have bricked their phones. I just want my phone to work again. I'm not worried about modifying it further to achieve that.
Click to expand...
Click to collapse
You have posted in wrong section
BTW your solution is just flash stock Rom via ODIN , your problem will get solved.
BTW your solution is just flash stock Rom via ODIN , your problem will get solved.
Click to expand...
Click to collapse
I've just finished doing that, and it appears to have worked.
For anyone else with a similar problem who finds this thread:
- Go to the FAQ here: http://forum.xda-developers.com/showthread.php?p=45767157#post45767157
- Download Daver18qc's root kit at the link provided (you'll have to scroll down to the second post). You want this to get Odin; don't worry about the zip's other contents.
- Go here: http://www.sammobile.com/ and register. It's free and all it wants is an e-mail and your country.
- Go here: http://www.sammobile.com/firmwares/ and type s7560m in the search box. The list will automatically update. I'm a Solo customer and chose 'Canada (Bell Mobile)'. When I first tried this in Firefox I would get a screen telling me I wasn't logged in. I tried it in IE (which I never use and so is 'clean') and the download went through.
- Go back to the FAQ http://forum.xda-developers.com/showthread.php?p=45767157#post45767157 and scroll down to 'Short Tutorials' and 'How to Flash with Odin:'.
- One thing it leaves out is that when you boot into Download Mode, you will first get a warning screen that asks you to either press Volume Up to continue or Volume Down to abort and reboot. Not a big deal but it caught me off guard. Odin will not detect the phone until you get past this screen.
- Continue with the Tutorial. After it is done you will have to setup the phone again. But at least it's working now.
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!!!!