Related
I have flashed my at&t tilt 2 with core cell evo v1.2 & it was working fine for awhile but now my screen is just black i can hear the phone make sounds and all but can't see the screen at all i really need help fixing this as this is the only phone i have any help or suggestions will be greatly appreciated thanks in advance.
i may be wrong but from what u have described... ur having a Sleep of Death (SOD) problem. have u tried takin out the battery or soft reseting the phone?
heres a link to a potential problem solver. Try to stay away from CHT lock and auto update apps!
sagarc88 said:
i may be wrong but from what u have described... ur having a Sleep of Death (SOD) problem. have u tried takin out the battery or soft reseting the phone?
Click to expand...
Click to collapse
yes i have done both and after the phone reboots i can hear sounds but i am still unable to see anything on the screen
Edit - I take that back, if it's still not working after a reboot
Have you tried entering the bootloader and re-flashing with the stock ROM?
If you can't see anything at all on the screen, no splash screens etc, even after soft-reset or entering the bootloader, then it sounds like you have a hardware problem (screen failure).
steviewevie said:
If you can't see anything at all on the screen, no splash screens etc, even after soft-reset or entering the bootloader, then it sounds like you have a hardware problem (screen failure).
Click to expand...
Click to collapse
i can't even tell if i can enter the bootloader screen because i can't see anything on the screen is there any way to tell if it's in the bootloader screen without being able to see the screen at all & if i do have a hardware problem (screen failure) how can i put stock spl & stock rom back on the phone to get it serviced
steviewevie said:
Edit - I take that back, if it's still not working after a reboot
Click to expand...
Click to collapse
if its still not working after a reboot then what? please help me i need a solution to fix this because if i can't even fix this how can i even send it in to get fixed i won't be able to because it has been flashed & has hardspl on it
"PLEASE HELP"
It's a tricky situation. So if you hold down Volume Down (and keep it held down) and press the reset button, then you still don't have anything come up on the screen ?
How about if you try a hard reset, does anything come up then ? You can hear the phone making sounds, so it seems like it's just the screen ?
Putting the charger in doesn't help, does it ?
You could try flashing a stock ROM from SD card and seeing what happens.
You might well have to send it back under warranty with HardSPL still on. In that case, if it was me, then if they tried to say the warranty was void just because of HardSPL I would argue very strongly against that and ask them to prove it - e.g. how can HardSPL stop your screen working ? I don't know what country you're in, but in the UK I think our consumer protection laws would have something to say about that.
steviewevie said:
It's a tricky situation. So if you hold down Volume Down (and keep it held down) and press the reset button, then you still don't have anything come up on the screen ?
How about if you try a hard reset, does anything come up then ? You can hear the phone making sounds, so it seems like it's just the screen ?
Putting the charger in doesn't help, does it ?
You could try flashing a stock ROM from SD card and seeing what happens.
You might well have to send it back under warranty with HardSPL still on. In that case, if it was me, then if they tried to say the warranty was void just because of HardSPL I would argue very strongly against that and ask them to prove it - e.g. how can HardSPL stop your screen working ? I don't know what country you're in, but in the UK I think our consumer protection laws would have something to say about that.
Click to expand...
Click to collapse
how can i flash anything if i can't see the screen?
Doo Doo said:
how can i flash anything if i can't see the scrren?
Click to expand...
Click to collapse
I've never flashed via SD, so I could be wrong on this. But I thought it was still possible. I see that the instructions (in the sticky on flashing ROMs) say to put it into the bootloader and "follow the on-screen instructions". I wonder if it's possible to just wait for a while and then press the appropriate key ? Though I don't know what the "appropriate key" is.
Perhaps someone who has flashed via SD can comment further, e.g. as to whether it's possible to do this without seeing the screen ?
steviewevie said:
I've never flashed via SD, so I could be wrong on this. But I thought it was still possible. I see that the instructions (in the sticky on flashing ROMs) say to put it into the bootloader and "follow the on-screen instructions". I wonder if it's possible to just wait for a while and then press the appropriate key ? Though I don't know what the "appropriate key" is.
Perhaps someone who has flashed via SD can comment further, e.g. as to whether it's possible to do this without seeing the screen ?
Click to expand...
Click to collapse
man i really need to fix this maybe you can ask around for me since i'm new here & really don't know anybody on this board
I know it's frustrating, I'd be kinda worried if I had an apparently-non-working screen too. But please be patient, and wait for more people to see your posting. The folks in the US will be coming online around this sort of time, so there will be more people looking in and hopefully someone can help further.
Flash without seeing the screen
Enter boot loader even if you can not see the screen. You can flash your phone to stock then enter boot loader again and hard spl. I had a similar situation and was able to complete the process and warranty repair with AT&T no problems, or you can pay to have it fixed at an outside shop. I was quoted 150 and refused to spend that muck so I flashed the phone without seeing the screen...
I saw your post over on Sergio's thread but decided to answer you here.
You do have a blown screen, no doubt there. How that happened is not really relevant.
My best advise is to connect your phone to your PC and wait for the activesync connection to come up. Once that happens you know you have a good connection and can flash. Run the RUU (or exe) for your stock ROM, the on screen (PC Screen) prompts will let you know if it can't proceed. Once the stock ROM is back on it, follow the same procedure and put the stock SPL back. Then send it off to get the screen replaced.
Hope that helps
Russ
Russ741 said:
I saw your post over on Sergio's thread but decided to answer you here.
You do have a blown screen, no doubt there. How that happened is not really relevant.
My best advise is to connect your phone to your PC and wait for the activesync connection to come up. Once that happens you know you have a good connection and can flash. Run the RUU (or exe) for your stock ROM, the on screen (PC Screen) prompts will let you know if it can't proceed. Once the stock ROM is back on it, follow the same procedure and put the stock SPL back. Then send it off to get the screen replaced.
Hope that helps
Russ
Click to expand...
Click to collapse
well when i plug my phone to the computer activesync is not popping up what can i do to get activesync to recognize my phone
can somebody please help me i need to reflash my phone but i am unable to see anything on my screen when i plug it up to my computer activesync is not working so what can i do please i really need help with this
Flashing witout screen
Step 1
Enter boot loader mode (* Remove the back cover from the phone.
* Hold the Volume Down button.
* Use the stylus to press the reset hole.
* Or if the device was powered off, press the power button whilst holding down the Volume Down button.)
and attach to computer. (wait 30 to 60 seconds)
Step 2
Check device manager for HTC mobile sync under mobile devices.(Active sync will not work in boot loader mode)
Step 3
Flash using Rhodium CustomRUU on your PC. (use original ROM from At&T.
Step 4 repeat for Radio
Step 5 Use Stock_SPL_Restore_087.zip from http://forum.xda-developers.com/showthread.php?t=550131 repeat the process with it.
This should work it did for me. Let me know if you run into problems.
So, hey guys, i've used this site a lot in the past, but now i need some help / advice, so i've registered. The following isn't going to be pretty but i'll explain it as best as i can.... infact, i can paste the email i sent to Sony asking for advice, it was this morning, i don't know if they operate or care
Hello people at Sony, my stupid head appears to have bricked my Xperia Arc S Android phone, it was still under warranty until i decided to unlock the bootloader, then i was having trouble restoring it back to stock android, this resulted in me trying to lock the bootloader. But alas, nothing now happens except a lonely green light flashing every so often, if i hold down menu, a blue light appears, which is charming, but then it dissipates and im left lonely again. With just a bricked phone and little dignity.
What are my options, by rules, it's void of warranty, can it be fixed? Can i pay for it to be fixed? Will my Natwest Insurance cover it on the grounds of Accidental damage (My stupidity) and Breakdown due to electrical fault, that being, no electrical softwareness is been transitorized.
I decided to go custom due to the wait for the Xperia update for my phone, out of the 273 S-I variant versions of the Arc S, 246 have gotten the update, but not mine, months had gone by, day turned to night, night turned to day, and i got desperate, i decided to root... for the first time. (And now last)
What i did learn, apart from technology will rise up and defeat us all, is JellyBean works very well to some degree on this phone, HOWEVER, the lack of Flash player caused bad results when playing content, im not sure what piece of code on the JellyBean CM10/Paranoid Android release was rendering it, but if you can get past the lack of flash for this and render images in its mobile bravia engineness then it will work a treat, and i mean it, it really did run well, obviously it was customness, but i digress...
Can anything be done? I do so love my Arc S, and just so you know, if it can't be repaired and I have to change phones, it will still wear the brand logo... Sony Ericsson... and if its your newer phones, that lack Eric's Son, i shall scribe his name proudly across the top with a sharp implement with pride. (With the care of an Adult, or someone equally minded)
Thank you lovely people over at Sony.
Stuart Herrington
Click to expand...
Click to collapse
So, basically it doesnt boot, apart from it does vibrate with button holds and the LED flashes. I tried flashing it with flashtool and stock ROM, but flashtool came back saying it needed unknown sources and debugging mode activated, which makes me think, it could be salvagable and not bricked, however how can i change those settings if i can't get into the phone itself, is there a bypass?
On a side note, i can Hold Menu, plug the phone into my computer and it goes into blue light mode, i cant remember the term for this
but its what i was using for flashboot, you reckon i could flashboot out of this? I was trying so many different methods to try and custom rom my phone that everything got confusing, which was best to use etc, and on another note the phone never booted when i tried to relock it, so im unaware if it finished, it didnt boot at all, and this is the point im at now.
Fortunately i picked up a Xperia U for £135, second hand, actually cheaper than my Arc S second hand, crazy really, but you can see why with the size difference and a couple of small spec differences.
Any help would be appreciated. This isn't obviously the best situation but i'm wondering if anyone has encountered this stupid mistake i've cast upon myself XD
Thanks in advance.
Wait...
I've checked the fastboot status of my phone using Flashtools, and it says my phone needs to be rooted first... hmmm it was rooted, maybe it got undone with the bootloader thing, i guess i can try but i can't access the phone to debugg or allow unknown sources.
Hi Stu15,
The fact that you can boot holding down the menu button is good.
You can probably flash a custom kernel onto your phone this way using the following command.
Code:
fastboot flash boot boot.img
If you have a rom that you want to use, then it usually comes with a custom kernel (called boot.img most of the time) inside the rom's zip file.
Most custom kernels have CWM recovery built-in, and here's the trick to enter recovery -
After you turn on the phone, wait for the hardware keys to light up.
Just in case you miss this, the coloured led will light up purple at the same time
When this happens, press (and release) the "volume down" button once or twice.
Then you should see CWM recovery in a few seconds.
So what you do is copy the rom to your sd card (just plug the card into your computer to do this).
Then flash the custom kernel that came with the rom.
Then boot into CWM and flash the rom (you should clear the cache and the dalvik cache before flashing the rom).
If you don't have a preferred rom, then have a look at this thread - http://forum.xda-developers.com/showthread.php?t=1653188
It has lotd of helpful links, near the bottom of the 1st post are a few roms you can try.
I hope that you come right.
Take care,
Hotfingers
Thanks for the info, ive tried this and apparently my phone isnt rooted anymore, it must've locked itself why i tried to undo the rom install, my recovery wasnt working so i was left with little choice. I can try and root the phone but i dont think it will be possible without accessing debugging mode, which is in the phone.. doh
im going to try adb commands to try and work something, then insurance claim. woop :/ lol
[EDIT] IM BACK, im in lol, i managed to find the command to unlock the bootloader, so now im back into CWM, the problem is the recovery doesnt work, so im reinstalling the original package, go into the phone, usb debugging and unknown sources, then i will flash it with stock ROM, should work. best work, i dont know why i did this in the first place... guess i had to learn XD
stu15 said:
Thanks for the info, ive tried this and apparently my phone isnt rooted anymore, it must've locked itself why i tried to undo the rom install, my recovery wasnt working so i was left with little choice. I can try and root the phone but i dont think it will be possible without accessing debugging mode, which is in the phone.. doh
im going to try adb commands to try and work something, then insurance claim. woop :/ lol
[EDIT] IM BACK, im in lol, i managed to find the command to unlock the bootloader, so now im back into CWM, the problem is the recovery doesnt work, so im reinstalling the original package, go into the phone, usb debugging and unknown sources, then i will flash it with stock ROM, should work. best work, i dont know why i did this in the first place... guess i had to learn XD
Click to expand...
Click to collapse
cool, well done. :good:
I rooted my HTC One X and unlocked the bootloader with HTCDev earlier this year. Recently I have had this problem with the phone where it bugs out. Sometimes in the middle of using the phone the screen will turn off and on showing the unlock screen while the Home buttons pulsate white.
So I did a factory reset and the phone seemed to work quite well not as buggy. After I had to revive it by leaving it on the charger for a couple hours.
I also have clockwork recovery still installed and I made a back up image that you guys talk about. The boot.img which I made after I rooted and facotry reset it. I don't think you can even get the boot img without it have that recovery program.
My question is should I try and mess with it some more? Should I re root it? I just want it function with out breaking now is my goal.
And is there any way to hide that whole "This is HTC software... do not distribute " message that comes up when I boot the phone? Because I know this voided my warranty but if I could get rid of that message my warranty is through a third party so I might be able to get a replacement if I can get that boot message off.
After re rooting it it seemed to calm down and the frequency of restarting was down significantly.
Now after a week, it is starting to restart again. Should I of flashed the kernel? I see that throw around a lot here in these forums but I don't know if it pertains to my situation. Anything help would be appreciated.
TheZander said:
I rooted my HTC One X and unlocked the bootloader with HTCDev earlier this year. Recently I have had this problem with the phone where it bugs out. Sometimes in the middle of using the phone the screen will turn off and on showing the unlock screen while the Home buttons pulsate white.
So I did a factory reset and the phone seemed to work quite well not as buggy. After I had to revive it by leaving it on the charger for a couple hours.
I also have clockwork recovery still installed and I made a back up image that you guys talk about. The boot.img which I made after I rooted and facotry reset it. I don't think you can even get the boot img without it have that recovery program.
My question is should I try and mess with it some more? Should I re root it? I just want it function with out breaking now is my goal.
And is there any way to hide that whole "This is HTC software... do not distribute " message that comes up when I boot the phone? Because I know this voided my warranty but if I could get rid of that message my warranty is through a third party so I might be able to get a replacement if I can get that boot message off.
Click to expand...
Click to collapse
delete
matt95 said:
delete
Click to expand...
Click to collapse
delete what? am I posting wrong? is there some kind of forum rule or format for asking questions or something?
Hello,
just some hours ago my Galaxy Nexus (SC-04D) rebooted while lying on the table next to me. After several sings of vibration I noticed that the phone doesn't boot completely.
When switching on the phone I get the turn-on-vibration, then the google letters are displayed. Most times the word "google" flickers from left to right over the screen (only the line where the word is supposed to be). Sometimes it boots further and I get the colored "X" displayed. This symbol starts flickering, too and if it went so far it reboots.
Here are two pictures I took from the phone failing to boot:
picpaste.com/img_0001_01-Rmm7kDYb.jpg
picpaste.com/img_0001-eoLqVoiM.jpg
The phone is running stock Android from Docomo. The phone is about 14 months old and has never been unlocked, rooted, modded, taken a bath, ... 'til now.
I tried starting with and without SIM-card, with and without charger attached and let it lie around for several minutes without battery between my tries.
Is there any chance to get my data from the phone or even get it fixed? Please give me a hint what I can do.
Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix. This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery
Thanks GPFboy for your fast response,
GPFboyJS said:
Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix.
Click to expand...
Click to collapse
As far as I understand a factory reset results in a complete loss of data on the phone, right? So without root/unlock there's no chance to get my data from the phone? That would be really bad.
GPFboyJS said:
This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
Click to expand...
Click to collapse
What is "too many"? I think there are about 35 apps installed atm. By the moment the problem arose wifi and 3g-data,BT,GPS were disabled and just a minute before I took a look how late it was. So nothing special.
GPFboyJS said:
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery
Click to expand...
Click to collapse
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?
BrainSD said:
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?
Click to expand...
Click to collapse
thats stock recovery.
is your bootloader already unlocked or no?
Zepius said:
is your bootloader already unlocked or no?
Click to expand...
Click to collapse
It's still locked.
you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.
Zepius said:
you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.
Click to expand...
Click to collapse
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?
BrainSD said:
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?
Click to expand...
Click to collapse
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Well if I was him I would be more worried about my expensive phone instead of data. Maybe a lesson for later to have a backup
Sent from my Galaxy Nexus using XDA Premium HD app
beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Yes exactly this is the point. Since I don't have a current data backup the first thing to try is getting my data from the phone. I already tried temporary loading the clockwork recovery through fastboot - with the galaxy nexus toolkit and by hand(sdk) - but it failed ("Bootloader locked").
What I'm wondering about is the fact that the phone seems to behave normally in odin and fastbood mode but going nuts the moment it's expected to boot. Besides the flickering google logo and the "matrix-modded" dead android it even ended up in a totally green screen one time.
At the moment I don't dare trying to unlock/flash the phone because of being afraid getting stuck and ending up with the phone being in some kind of undefined / totally broken state. Initially I was in hope of being able to rescue my data but now i will try my luck with docomo support first.
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
I will try to get through 1 to 4 of the guide first and see how far I get.
If this won't work I might try to unlock, recover and try to "undelete" what's possible. (http://forum.xda-developers.com/showthread.php?t=1994705)
Does this order make sense?
Btw, having a dead phone is bad, of course, even when I got it new for 2300Yen but loosing some pictures i really liked and having no phone atm currently hurts more. Especially when knowing that I was thinking of copying all photos to my computer only one day before when I pulled only some minor important ones from the phone I needed for work and planned to do a full backup and unlock this weekend when I get back my 'Milestone' currently lent to someone else.
Once again something I learned. Backup! Even you phone.
BrainSD said:
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
Click to expand...
Click to collapse
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.
It will unlock your bootloader, bypassing fastboot. Still, it's not for the faint hearted. I refered to omapflash because its a low level tool, it doesn't require the bootloader to be unlocked, and is able to restore the bootloader to working state, and I got there because you mentioned you see graphical glitches/flickering which may indicate bootloader partition failure and/or consequent corruption.
I think that's your best shot at trying to get your data back. After unlock, boot to fastboot and 'fastboot boot custom_recovery.img', and grab your stuff (if you can) from /data/.
beekay201 said:
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.....
Click to expand...
Click to collapse
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems
BrainSD said:
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems
Click to expand...
Click to collapse
Great, so far so good.
Yeah, they're ext4 images, but sparse images i believe - link
Hi Guys.
I replaced a screen of a D5503. Knew the pattern to unlock the phone (friends) but messed up and thought it does not matter if it resets to factory settings after 7 attempts.. But Bootloop. Country choice appears shortly and screen goes to grey. Repair with companion gives no change. Sometimes it is possible to select country and go one screen further and then it goes grey again. Is this bootloop ?
searched web and forum for similar problems and decided finally it must be bootloop?
Of course i did not make a back up.. phone is coupled to google account of friend , so if I can get the screen to normalize and not disappear that would also be an option.
i downloaded Flashtool Emma. Most links are dead. For neccesary files, unlocking etc.
I have a sony unlock code.
(locked bootloader)
The firmware is (1279-1792) 14.6A.1.236-R2D
Can anybody direct me to the right link to follow ?
Or commands are not downloadable anymore, or I don't know what tft file to use etc.
Can anybody direct me in the right direction ? Please?
Help is appreciated. I flashed and rooted a Z1 mini once before. years back.
If you can flash stock firmware with sony compagnon with sucess 100%, it means that it's not a firmware problem.
Are you sure new screen is good? Did you replace touchscreen and LCD or only one of them?
did you test with old screen to check if system boot is ok?
I replaced both in one. Screen with digitizer asssembly. And initially the phone booted fine to lockscreen with pattern. So screen is working fine.
I messed up trying 7 times the pattern upon which the phone by itsself booted to factory settings. Since then the phone is stuck. I tried repair with companion but that made no difference.
But the adb commands to unlock bootloader don't seem to be downloadable anymore. Not even from the link provided from the sony site. from which I optained the unlock key.
Can you boot phone in recovery mode ?
foxyone0809 said:
Can you boot phone in recovery mode ?
Click to expand...
Click to collapse
Yes ; if I hold the volume button up when phone is powered off, and connect the usb to the phone the powerled goes blue and the pc gives a messaga that fastboot is on. Phonescreen stays black.
pinkeltje2 said:
Yes ; if I hold the volume button up when phone is powered off, and connect the usb to the phone the powerled goes blue and the pc gives a messaga that fastboot is on. Phonescreen stays black.
Click to expand...
Click to collapse
I don't talk about fastboot mode.
I talk about stock recovery mode, where you can reset system to factory
foxyone0809 said:
I don't talk about fastboot mode.
I talk about stock recovery mode, where you can reset system to factory
Click to expand...
Click to collapse
If the phone boots up, for a second the language choice screen pops up and screen goes to grey. I cannot acces anything on the phone itsself.
pinkeltje2 said:
If the phone boots up, for a second the language choice screen pops up and screen goes to grey. I cannot acces anything on the phone itsself.
Click to expand...
Click to collapse
Do you know the keys to boot automatic in recovery mode ?
foxyone0809 said:
Do you know the keys to boot automatic in recovery mode ?
Click to expand...
Click to collapse
well, it should be volume up and power button. But that only gets me to fastboot. No lights blincking at the supposed ledlight at all.
So the screen freezes at language choice page. that only appears shortly. sometimes just long enough to make a choice and then the screen goes grey. The only option to communicate seems to be fastboot. Since the pc recognices the phone as being in fastboot.
So how to proceed ?
pinkeltje2 said:
well, it should be volume up and power button. But that only gets me to fastboot. No lights blincking at the supposed ledlight at all.
So the screen freezes at language choice page. that only appears shortly. sometimes just long enough to make a choice and then the screen goes grey. The only option to communicate seems to be fastboot. Since the pc recognices the phone as being in fastboot.
So how to proceed ?
Click to expand...
Click to collapse
Try to flash firmware.tft file with flashtool for xperia devices
It seems you have lock bootloader.
---------- Post added at 04:07 PM ---------- Previous post was at 04:02 PM ----------
http://www.flashtool.net/downloads.php
Or
https://github.com/Androxyde/Flashtool
Here is a list of FTF files of official firmwares for the Sony Z1c:
https://boycracked.com/2019/10/08/official-sony-xperia-z1-compact-d5503-stock-rom-ftf-for-flashtool/
Latest version ever released is 14.6.A.1.236; Download a FTF and flash it with Flashtool from www.flashtool.net;
Make sure the ticks to wipe data and cache are enabled when you flash the firmware.
marsa47 said:
Here is a list of FTF files of official firmwares for the Sony Z1c:
https://boycracked.com/2019/10/08/official-sony-xperia-z1-compact-d5503-stock-rom-ftf-for-flashtool/
Latest version ever released is 14.6.A.1.236; Download a FTF and flash it with Flashtool from www.flashtool.net;
Make sure the ticks to wipe data and cache are enabled when you flash the firmware.
Click to expand...
Click to collapse
Tnx. back when this was still somewhat a current model I knew what version it contained and with patience I rooted and flashed a X1c. Got a Flashtool download now branded Emma. . Looks weird in my eyes. But the .net page gives a virus error in the torrentfiles still being used in those days. Hence my loss. ? Emma version did give detailed info about the phone and the firmware and that bootloader is locked. Then can get unlock key from sony site, but adb files I can't get. And when I finallly can get them I am asked for admistrator password,. My stupid attempt to make an offline non google account pc, the other way around. And while only a few days ago I forgot that password hahaha. Dont't ask. strangers in tha house Gonna see if I have the old files still on the old brick (pc) and see if I can manage from there. -) tnx for answering and patience. I have a few bricks. maybe first create a dualboot. and be sure.
I'll report back if I get that old fart to life again thanks to your input.
Thanks again and enjoy and have fun
pinkeltje2 said:
Tnx. back when this was still somewhat a current model I knew what version it contained and with patience I rooted and flashed a X1c. Got a Flashtool download now branded Emma. . Looks weird in my eyes. But the .net page gives a virus error in the torrentfiles still being used in those days. Hence my loss. ? Emma version did give detailed info about the phone and the firmware and that bootloader is locked. Then can get unlock key from sony site, but adb files I can't get. And when I finallly can get them I am asked for admistrator password,. My stupid attempt to make an offline non google account pc, the other way around. And while only a few days ago I forgot that password hahaha. Dont't ask. strangers in tha house Gonna see if I have the old files still on the old brick (pc) and see if I can manage from there. -) tnx for answering and patience. I have a few bricks. maybe first create a dualboot. and be sure.
I'll report back if I get that old fart to life again thanks to your input.
Thanks again and enjoy and have fun
Click to expand...
Click to collapse
So ? Do you succeed to boot system ?
This guy seams to be mad.... Lol