[Q] Phone constantly reboots after optimising apps (CM12.1 Lollipop) - Xperia Z Q&A, Help & Troubleshooting

I am running Infected's CM12.1 ROM on my Yuga, and it's been working great, but just yesterday, my phone restarted without warning and optimised all the apps (200 of them), right when it says "starting apps", it restarts again and did this until the battery drained out.
I cannot enter recovery at all. I have TWRP installed on the FOTA partition, but I cannot access that. When I'm holding the volume down key on the reboot, it just skips straight to the CM logo.
While it's optimising apps, I can see the phone in adb, but it's unauthorised, so I cannot run any commands to it.
I can reboot the phone into fastboot, but apart from reflashing the boot.img (which I already did) I don't know what else to try.
I think all the buttons are working, but I saw that the water pads are red underneath two of them. I think there may be water damage, but am not sure.
I'm out of ideas and would very much appreciated if anyone can help me bring my beloved phone back.

Lohot said:
I am running Infected's CM12.1 ROM on my Yuga, and it's been working great, but just yesterday, my phone restarted without warning and optimised all the apps (200 of them), right when it says "starting apps", it restarts again and did this until the battery drained out.
I cannot enter recovery at all. I have TWRP installed on the FOTA partition, but I cannot access that. When I'm holding the volume down key on the reboot, it just skips straight to the CM logo.
While it's optimising apps, I can see the phone in adb, but it's unauthorised, so I cannot run any commands to it.
I can reboot the phone into fastboot, but apart from reflashing the boot.img (which I already did) I don't know what else to try.
I think all the buttons are working, but I saw that the water pads are red underneath two of them. I think there may be water damage, but am not sure.
I'm out of ideas and would very much appreciated if anyone can help me bring my beloved phone back.
Click to expand...
Click to collapse
Have you tried flashing stock FTF ?
You would need FTF from general section and also flashtool which you can get from here. Make sure the FTF is device specific or your would end up bricking up your phone
http://www.flashtool.net/index.php
You can search xda for how to use it. If you still have questions, quote me and I would be glad to help

Hi,
Thanks for helping me out. I tried reflashing a few different ROMs using flashtool, including stock, but nothing helped.
In the end, I bit the bullet and gave it up for dead. The good news was, since the cause seemed to be water ingress, it was covered by my insurance, and so I was given a replacement!
Thanks again for your help.
Hnk1 said:
Have you tried flashing stock FTF ?
You would need FTF from general section and also flashtool which you can get from here. Make sure the FTF is device specific or your would end up bricking up your phone
Click to expand...
Click to collapse

Lohot said:
Hi,
Thanks for helping me out. I tried reflashing a few different ROMs using flashtool, including stock, but nothing helped.
In the end, I bit the bullet and gave it up for dead. The good news was, since the cause seemed to be water ingress, it was covered by my insurance, and so I was given a replacement!
Thanks again for your help.
Click to expand...
Click to collapse
There's nothing sweeter than using a phone for a long time and getting a brand new !
Enjoy mate. No trouble. Just quote me again in case you have any query for me.

Related

need help dead phone

I was attempting to flash the ICS4 ROM. I had formatted /system and was done with installing the from from zip. Before I could do anything else, the phone just stopped being responsive. I pulled and restored the battery but the phone will not boot up. What to do now, short of going to my VZW store?
When you say it doesnt boot.. what exactly do you mean? Does anything come up on the screen?
nothing comes when you press the power button, screen remains blank.
ronaldheld said:
nothing comes when you press the power button, screen remains blank.
Click to expand...
Click to collapse
Did you try booting up into recovery and then going to fastboot and reinstalling the stock fxz file to see if that fixed it?
Sure the battery didn't die also?
The phone does not boot into recovery. Pressing the power button does nothing at all, as far as I can see.
I found out that the phone is literally fried. Whether the ICS4 ROM contributed is unknown.
You are most likely covered under manufacturer warranty - seems like a hardware failure. Never known of a ROM flash to fry a phone's board.
They also most likely won't know you even tried to flash a custom ROM.
That part is very good to know.
I will have restart again with rooting, and proceed with flashing Eclipse 2.2.
Is the place you live in very statically charged? When you touch metal do you get shocked alot?
If you touched the battery ports it could have discharged into the phones board and killed it.
Let us know what they do for you.
ronaldheld said:
That part is very good to know.
I will have restart again with rooting, and proceed with flashing Eclipse 2.2.
Click to expand...
Click to collapse
Compared to everything else we do here at XDA, the process to get rooted and flash a ROM is very basic. Getting the phone back up and running is the more difficult part.
What I can say to try is attempt to use a different battery. I had a problem once where both of my batteries functioned properly because I was able to test them in other phones. But when I placed that specific battery into my phone, it wouldn't boot up. I ended up using a different battery and was then able to boot into AP Fastboot and fxz to fix it. Then my "dysfunctional" battery worked properly again.

[Q] Please help me, is my phone bricked?

I'm a complete noob in dire need of help. I wanted to root my phone, and read the 3 procedures mentioned in the sticky thread. The 2nd one (nvflash) seemed very well explained and was sure to work with 2.3.4 so I decided to use that. As I was in my friend's house I used his pc and installed the drivers while my phone was connected in apx mode. Then I double clicked the "install internal xp" batch file which resulted in a black window with some texts, but seeing this my friend freaked out and closed the window before the process was finished. I told him he shouldn't have done that. I then disconnected the phone and switched it on. It seemed to switch on properly. So I then switched it off again and pressed and held the power and vol down switches to see if I got cwm. This showed LG screen for a few seconds and then the screen went off.
Now whatever I try to do I can only see the LG screen for a few seconds and then the screens goes off. No power on, no recovery, no nothing. And I can only attempt to even power on once, after the screen goes off I must remove the battery before the power button does anything again.
I tried to freshly nvflashing the recovery many times, but it made no difference. Does this mean my phone is bricked? Please tell me how I can solve this as I'm really worried.
NVFlashing the recovery again *should* have worked. So we first need to make sure you're trying to start CWM the correct way.
1) Unplug phone
2) Remove battery for 10 seconds.
3) Insert battery
4) Hold volume-down, do not let go, keep pressing it.
5) Press power button, keep it pressed.
If/when you get the second LG-logo, bluish halo, you can release both buttons, not before.
Nope, that was exactly what I was doing to access the recovery. I tried it again just now and it didn't work.
It just displayed the regular LG logo and then the screen went off. I'm not sure the phone completely shuts down 'cause if I keep it like that it gets quite hot and I can't use the power button again to try to power up. Only removing and re-inserting the battery gives me another attempt.
Is there any chance this is a hardware issue?
Hardly any chance this is hardware related if it was working before the first NVFlash.
Good, next step will be to NVFlash a complete stock ROM. You will unfortunately lose any data you might have on it, but that's the price to pay.
Go here, follow the instructions precisely, skip installation of apx-driver. Report back.
http://www.modaco.com/topic/335474-25-mar-nvflash-stock-rom-release-v10b-dated-1300166062-15032011/
Ok, so I just download the 200mb file, connect in apx mode and double click flash.bat, right? And will this rom work regardless of country/region? I'm from India and was running stock 2.3.4 with v20* (can't remember the letter. God, I hate myself).
sean8000 said:
Ok, so I just download the 200mb file, connect in apx mode and double click flash.bat, right? And will this rom work regardless of country/region? I'm from India and was running stock 2.3.4 with v20* (can't remember the letter. God, I hate myself).
Click to expand...
Click to collapse
It works, yes, but is the original Froyo. This is just a way to get the phone up and running again.
Later you have a few choices. Either install CWM, then install you ROM of choice, or upgrade it to the latest for your region by using the LG Update tool.
EDIT. Oh, and btw, it is better to open a command-window and type the flash.bat command. If there are any errors you will still have them on-screen.
Thank you for all the help and support. I didn't get a chance to flash the rom till now (being on a vacation without a smartphone sucks). But I'll try it asap and report back.
So, how did it go?
TrymHansen said:
So, how did it go?
Click to expand...
Click to collapse
I haven't flashed it yet. I've decided to do it after I return home. I'm at my friend's house for 2 more days.
Ok, bad news. I flashed the stock rom you linked. The process went pretty smoothly. After the window got closed and the lg logo on the phone was visible 2 times, I unplugged it and installed the battery. But switching it on wasn't fruitful. It just displayed the LG logo for a couple of seconds and then the screen went off (just like before, only faster). I tried repeating the whole process, even tried to nvflash cwm once again, but nothing happened.
So is it a hardware issue? My phone is no longer in warranty period, so a hardware problem would be really bad...
So is it a hardware issue?
Click to expand...
Click to collapse
I don't know.
What would be helpful is to get a copy of the output you get when you NVFlash, it's simply the only way to verify that the flash process went ok. If you have an aborted flash it of course won't work, and may display the behaviour you describe.
EDIT: Btw, early on there were some ROMs which refused to boot properly unless the baseband was of an early variety as well.
If you feel confident the NVFlash has been successfull, smartflash an old baseband as well, see if it boots then.
Its hardly a hardware problem. As you dont have the warranty anymore, and the bootloader is probably corrupted, i would recommend a Jtag service.
Please, dont be afraid of hitting thanks
gabriel2anjos said:
Its hardly a hardware problem. As you dont have the warranty anymore, and the bootloader is probably corrupted, i would recommend a Jtag service.
Please, dont be afraid of hitting thanks
Click to expand...
Click to collapse
Now what's this "Jtag service"? (edit- I googled it and it seems to be a method of un-bricking stuff with specialized hardware or something, but I'm not sure I can have that done where I live)
Is there any way to fix the bootloader by myself?
@Trym- So, I should download a v10 baseband and flash it with this "smartflash" tool, right?
sean8000 said:
@Trym- So, I should download a v10 baseband and flash it with this "smartflash" tool, right?
Click to expand...
Click to collapse
Yeah, as a last-ditch effort. I haven't the slightest hope it'll help, but it can't hurt to try.
TrymHansen said:
Yeah, as a last-ditch effort. I haven't the slightest hope it'll help, but it can't hurt to try.
Click to expand...
Click to collapse
Ok, I'll try that when I have the time.
So do you know anything about this corrupted bootloader thing? Does this mean my phone's hard bricked?
sean8000 said:
So do you know anything about this corrupted bootloader thing? Does this mean my phone's hard bricked?
Click to expand...
Click to collapse
If it is you're only the second person in this forum to ever brick his phone. Anything's possible I guess. Some flash cells may have been damaged the first time the power was yanked. But then we should presumably get some verification errors during flashing.
Anyway, I'm at my wits end, and I really do hope you get it up and running, but I don't have anything more to contribute. Good luck.
Corrupted bootloader means that your cellphone simply don't know what to do when you hit the power button, due to the damage. As the cell phone can't turn, the pc can't recognize it. If your cell phone were a samsung, you could try to use a jig to have acesso to the download mode. But I don't know if it would work for a LG. You could try anyway.
And if you live at big city, usually it's common to have some jtag services.
Please, dont be afraid of hitting thanks
Please, dont be afraid of hitting thanks
Ok, so I took the phone to the service center today. The guys there said its battery terminals are messed up. They said replacement terminals are not easily available, but they'll try to find some. And of course I'll have to pay for it. I guess it's still better than using the phone as a paperweight.
What do you guys think?
Good luck I managed to mess up my phone like you too. I'm from India. But the difference was that I was covered by warranty. I managed to get a bunch of hardware replaced and was up and running again.

Xperia TX bricked (only showing sony logo then a triangle with an exclamation mark)

Please help me guys, I have no one else to turn to. My parents are gonna kill me if they find out what I did to my phone.
So my phone accidentally fell at school with the bluetooth still on.So I put the battery pack, power it on, but then it started to go on a boot loop i.e.
Sony logo-->Xperia Logo-->color animation-->black screen. But after 3-4 hours, it managed to do a complete boot! But I noticed that the bluetooth wasnt turning on. So stupid me, I restarted the device, then it started to go on a boot loop again. I got home and I tried it a couple of times more with the power and volume rocker combinations... didnt work either.
I even started using pc companion. didnt work (kept on doing the same thing
SUS --> same thing
NOW: I tried it using a different computer so I went to an internet shop and downloaded pcc and sus. I started pc companion... but halfway through the download... MY PHONE RAN OUT OF BATTERY and didnt finish the update. :'( Now, whenever I'm booting the phone, I only get the Sony logo and A TRIANGLE WITH AN EXCLAMATION MARK AND A PHONE UNDERNEATH.....
PLEASE HELP ME! My Phone is a Sony Xperia TX Lt29
Last Version before the crash: JB 4.1.2
No root (Noob here)
please... please. i dont know what to do. thank you in advance to anyone who can help me
calm down.
Charge the phone until it is fully charged.
Download PCCompanion and do a fresh install of it.
Run PCCompanion and choose software update.
Use the option to repair your phone, then follow the instructions.
Let us know how you get on
PS
This will only do a software repair, if something broke because you dropped it (Which it sounds like) you are going to have to come clean and tell your parents to get it fixed.
HI gregbradley '^^
gregbradley said:
calm down.
Charge the phone until it is fully charged.
Download PCCompanion and do a fresh install of it.
Run PCCompanion and choose software update.
Use the option to repair your phone, then follow the instructions.
Let us know how you get on
PS
This will only do a software repair, if something broke because you dropped it (Which it sounds like) you are going to have to come clean and tell your parents to get it fixed.
Click to expand...
Click to collapse
THANK YOU FOR YOUR REPLY!!! really thank you :'(
I already did something with the phone because I've been doing a lot of searching on the net lately...
I reinstalled the software using Sony Update Service (SUS) and it booted normally! (but sadly it was only during the FIRST BOOT UP) when I turned off the phone to re insert the sim card and micro sd, It started doing it again... but then, after 6 or 7 tries, it managed to skip past the sony logo-->xperia--> logo-->color animation? and do another complete boot
Now I decided to go to settings and do a complete factory reset cause I thought it would fix everything... but it didn't. It started doing the same thing, and I had to give it 10 or 12 tries before eventually booting up again. When it booted up normally, I was even able to play music with it and change the settings like brightness, volumes, equalizers, and even arrange widgets!
SITUATION NOW:I turn on the Wi-fi and it's in a boot loop again and I'm charging the phone up to 100%
(i did the vol.up vol down power combination before charging)
gregbradley, is it because of our slow internet connection??? (it took me like 4 nerve racking hours to finish the update) but sus was able to complete the download and install the software... what the f*ck is wrong with my phone (((( ohgod
AND:
I'll follow your instructions when the charge is complete...... and I'll be back to you with the results.God I hope this works.Thank you again.
Have you tried only partially flashing part of an ftf file. I know when my phone was on the brink of death I discovered that if I only flashed part of an ftf using flashtool that it would work. I think I would check everything that has exclude (ie: Exclude System) and it would work for me. Its not the end of the world though as the phone does work. Just a bootloop. If you can get it into flash mode then just exclude everything except System, Kernel, and baseband if I'm not mistaken.
hi Cammarratta '^^
Cammarratta said:
Have you tried only partially flashing part of an ftf file. I know when my phone was on the brink of death I discovered that if I only flashed part of an ftf using flashtool that it would work. I think I would check everything that has exclude (ie: Exclude System) and it would work for me. Its not the end of the world though as the phone does work. Just a bootloop. If you can get it into flash mode then just exclude everything except System, Kernel, and baseband if I'm not mistaken.
Click to expand...
Click to collapse
Thank you for the reply man '^^
um... to tell you the truth, I have no idea how to partially flash a tft file, let alone flashing. O_O (see how noob i am?) its saddening. So am I in the point right now where my phone's problem is unsolvable via pc companion or sony update service??? Plus I've been doing some searching here on xda and I saw this thread about xperia TX users updating to version b 167 and that their bootloaders are now locked.
This is what my phone is exactly doing whenever I try to boot it up:
Sony Logo---->Xperia Logo----> Color waves animation?---> FREEZE-->black screen then the Sony Logo again.
Whenever I try to boot up for the 2nd time this happens:
Sony Logo----> Black Screen---> Phone turns off---> Sony Logo again
(((
You have flashtool yes? If you load up like you're going to flash a ftf file. Once you click to load up the ftf file it'll pull a menu where you pick what you want to flash. On the right side of flashtool that's where the exclude part is. That's where you have to check the *exclude option. The same thing happened to me when I accidentally flashed a T cm10 rom on my phone. I had to partially flash a ftf file to get it to boot. It should work but since you're not familiar with flashtool its going to make it a bit harder for you in the end. :/
carloptimus3d said:
Please help me guys, I have no one else to turn to. My parents are gonna kill me if they find out what I did to my phone.
So my phone accidentally fell at school with the bluetooth still on.So I put the battery pack, power it on, but then it started to go on a boot loop i.e.
Sony logo-->Xperia Logo-->color animation-->black screen. But after 3-4 hours, it managed to do a complete boot! But I noticed that the bluetooth wasnt turning on. So stupid me, I restarted the device, then it started to go on a boot loop again. I got home and I tried it a couple of times more with the power and volume rocker combinations... didnt work either.
I even started using pc companion. didnt work (kept on doing the same thing
SUS --> same thing
NOW: I tried it using a different computer so I went to an internet shop and downloaded pcc and sus. I started pc companion... but halfway through the download... MY PHONE RAN OUT OF BATTERY and didnt finish the update. :'( Now, whenever I'm booting the phone, I only get the Sony logo and A TRIANGLE WITH AN EXCLAMATION MARK AND A PHONE UNDERNEATH.....
PLEASE HELP ME! My Phone is a Sony Xperia TX Lt29
Last Version before the crash: JB 4.1.2
No root (Noob here)
please... please. i dont know what to do. thank you in advance to anyone who can help me
Click to expand...
Click to collapse
just let it plug in with the charger and keep your phone on for day, usually that will fix it after a few hours with that logo running
Use a battery charger, charge for at least half the entire batt and then follow the thread on flashing, download some files while charging to minimize downtime
Sent from my LT29i using xda premium
Hey guys...... ))))
First and foremost, thank you for all your replies.. really helped me a lot (
It's okay now guys! '^^ I re installed the software via Sony Update Service and it worked. At first I thought the phone was a goner cause it didn't manage to do a complete boot right after the installation. (Phone was stuck on the Sony Logo) But then the next morning, I tried it again and it worked!!
BUT: What I fear now is that the phone might suddenly crash again if I turn on the WI-FI (just like what happened in my previous attempts) If the phone crashes, I fear that the phone would start going on a boot loop again.So basically, I'm just using the phone for media purposes only i.e. Walkman, Gallery,Camera, Movies.
Any thoughts on this, cool, awesome people of xda? '^^ (cant update my apps and google now f*ck)
just.. sad. I miss Flipboard,Modern Combat 4, My Daddy Was a Thief, Real Racing 3, DEAD SPACE (((
one question...
Did something broke inside my phone when it fell?? If yes... WHAT EXACTLY IS IT?? why is it behaving this way??? Why does it keep on boot looping??? should I go and let an expert open it????
carloptimus3d said:
First and foremost, thank you for all your replies.. really helped me a lot (
It's okay now guys! '^^ I re installed the software via Sony Update Service and it worked. At first I thought the phone was a goner cause it didn't manage to do a complete boot right after the installation. (Phone was stuck on the Sony Logo) But then the next morning, I tried it again and it worked!!
BUT: What I fear now is that the phone might suddenly crash again if I turn on the WI-FI (just like what happened in my previous attempts) If the phone crashes, I fear that the phone would start going on a boot loop again.So basically, I'm just using the phone for media purposes only i.e. Walkman, Gallery,Camera, Movies.
Any thoughts on this, cool, awesome people of xda? '^^ (cant update my apps and google now f*ck)
just.. sad. I miss Flipboard,Modern Combat 4, My Daddy Was a Thief, Real Racing 3, DEAD SPACE (((
Click to expand...
Click to collapse
If it's only when you start the wifi it's an hardware problem.
Send it to service
hello
Cammarratta said:
You have flashtool yes? If you load up like you're going to flash a ftf file. Once you click to load up the ftf file it'll pull a menu where you pick what you want to flash. On the right side of flashtool that's where the exclude part is. That's where you have to check the *exclude option. The same thing happened to me when I accidentally flashed a T cm10 rom on my phone. I had to partially flash a ftf file to get it to boot. It should work but since you're not familiar with flashtool its going to make it a bit harder for you in the end. :/
Click to expand...
Click to collapse
What version for ftf version for xperia tx should i flash???? the ics one??? the latest??? helppp
and should i check everything that's in the exclude option?
The latest one, and don't exclude anything
Sent whilst sat on the toilet.

[SOLVED] My Xperia t touchscreen suddenly doesn't work anymore

Yesterday I went to a party, nothing wrong with the xperia t. When I got home I let it recharge. I think it still worked at that moment. Pretty sure it did. Went to sleep. Woke up. My phone battery was empty lol. Still in the recharger. Did some stuff, let it recharge some more. Got it to boot up again. Now touch screen doesn't work anymore . Tried wiping cache, factory reset. Still not working.
I have cm-10.1.3-RC2-mint installed. I think I might have to update it. This could be the problem.
Any more tips for if it doesn't work? never had this problem before. I hope it is a software thingy.
I updated the firmware but still doesn't work. I think im gonna re-install the stock firmware, and flash a stock kernel which will unroot my mobile. Any tips? please? I can't use my phone at all atm. It just stays at the cyanogenmod install screen..
Reflash the touch firmware
read this
http://forum.xda-developers.com/showthread.php?t=2220290&highlight=touch+screen+not+working
especially post 11
gregbradley said:
Reflash the touch firmware
read this
http://forum.xda-developers.com/showthread.php?t=2220290&highlight=touch+screen+not+working
especially post 11
Click to expand...
Click to collapse
I would like to try that thing with adb, but as I have already reinstalled cyanogenmod, developer options/debugging is turned off. I can't use ADB. Unless you know another way.
So this is totally getting out of hand.. (and I don't know if that is also a english expression lol).
I tried reflashing a stock firmware. Worked, but touchscreen still doesn't work. Then I noticed, that I now don't have cwm anymore... how the f?
SO I probably forgot to exclude the kernel. So now I tried reflashing a kernel with cwm, but flashtool doesn't recognize the kernel files... I don't know what is going on..
Ah already found the problem. Got cwm back phewww..
So here is what needs to be done. I want to try gregbradleys adb shell fix but my usb debugging is off and this means that I can't use adb, as I don't have touchscreen.
So, is there any way, any way at all, to enable usb debugging without touching the screen? Maybe a kernel with that settings automaticly set?
Im getting a bit angry at my phone now.. I didn't even do anything to break it in the first place. Just tried recharging it, and that killed the touchscreen? lol. Help will be appreciated. Im out of ideas.
Get a usbotg cable and attach a usb mouse
Then use that to turn debugging on
When you flash a stock firmware you lose recovery.
Sent from my C6903 using xda premium
thanks, I'll get one tomorrow. I hope it will help. You've helped me before so im pretty confident that you fix my problem again haha. You are a boss.
A non responsive touch screen happened to me too after I flashed a wrong firmware. I flashed back the version that was on before, but it didn't help. Only after I flashed this (pretty old) version Xperia T - 7.0.A.1.303 Generic DE with Flashtool, the touch screen started to working again. I am not sure, maybe any ftf would work. But I know that I had success with this one.
You should try gregbradleys method first though. Funny, that your touch screen stopped working, without you modifying anything. Hopefully it's not a hardware problem.
gwodus said:
A non responsive touch screen happened to me too after I flashed a wrong firmware. I flashed back the version that was on before, but it didn't help. Only after I flashed this (pretty old) version Xperia T - 7.0.A.1.303 Generic DE with Flashtool, the touch screen started to working again. I am not sure, maybe any ftf would work. But I know that I had success with this one.
You should try gregbradleys method first though. Funny, that your touch screen stopped working, without you modifying anything. Hopefully it's not a hardware problem.
Click to expand...
Click to collapse
hmmm, I tried this and it worked. problem solved. I did however not have wrong firmware installed, but it was an rc2 version of cm. So it can be unstable and stuff, but this was kind of a big problem.
quinten96 said:
hmmm, I tried this and it worked. problem solved. I did however not have wrong firmware installed, but it was an rc2 version of cm. So it can be unstable and stuff, but this was kind of a big problem.
Click to expand...
Click to collapse
Hey, glad your phone is ok again. I remember when that happened to me. I just had the phone for a couple weeks. Shat my pants, thinking I wrecked it. It worked out at the end, though. Feels good to recover a bricked phone, doesn't it.
Sorry to bump
gwodus said:
Hey, glad your phone is ok again. I remember when that happened to me. I just had the phone for a couple weeks. Shat my pants, thinking I wrecked it. It worked out at the end, though. Feels good to recover a bricked phone, doesn't it.
Click to expand...
Click to collapse
I am having this exact problem! I'm sorry to awake this sleeping thread, but I have a locked bootloader and I tried a Sony PC Companion reset and it still has the problem. Is there anything else I can do?
jmm288 said:
I am having this exact problem! I'm sorry to awake this sleeping thread, but I have a locked bootloader and I tried a Sony PC Companion reset and it still has the problem. Is there anything else I can do?
Click to expand...
Click to collapse
I have the same problem... I changed touch panel, flex cable and update with pc-companion but it doesn't work

[Q] Cannot boot after flashing incorrect kernal.

Hello,
I'd like to preface this to say I've searched through this and other sites but have not found quite the same problem. I also apologise for the small wall of text. I just want to post everything that seems relevant.
Several weeks ago I unlocked my phone and flashed the latest stable Cyanogenmod. This has all gone fine. I decided today I wanted to try something else and settled on TeamAsylum's 4.4 rom.
Downloaded a whole bunch of stuff and was a little confused as the flashing process seemed a bit different and I didn't fully understand it. I booted into Clockwork Recovery and inadvertently flashed the raw kernel from here, which I downloaded in my searches earlier thinking I needed it. I rebooted the recovery but now I get nothing from the phone. No lights, no display, no vibrations.
I have tried a reset (Power+Volume UP). I have tried using SUS and Flashtool but both get to the same point and stop (hole Volume DOWN and plug USB in). Nothing happens after this. The only thing telling me the phone is alive is when I plug it in, Windows makes the detected sound. If it's plugged in when I hold power+Volume UP it repeats the detection sound as if the phone is trying to boot over and over.
I realise I have ****ed up by flashing the kernal of a different phone. I'm hoping someone can help me or guide me in the right direction.
Thank you.
Nightstaar said:
Hello,
I'd like to preface this to say I've searched through this and other sites but have not found quite the same problem. I also apologise for the small wall of text. I just want to post everything that seems relevant.
Several weeks ago I unlocked my phone and flashed the latest stable Cyanogenmod. This has all gone fine. I decided today I wanted to try something else and settled on TeamAsylum's 4.4 rom.
Downloaded a whole bunch of stuff and was a little confused as the flashing process seemed a bit different and I didn't fully understand it. I booted into Clockwork Recovery and inadvertently flashed the raw kernel from here, which I downloaded in my searches earlier thinking I needed it. I rebooted the recovery but now I get nothing from the phone. No lights, no display, no vibrations.
I have tried a reset (Power+Volume UP). I have tried using SUS and Flashtool but both get to the same point and stop (hole Volume DOWN and plug USB in). Nothing happens after this. The only thing telling me the phone is alive is when I plug it in, Windows makes the detected sound. If it's plugged in when I hold power+Volume UP it repeats the detection sound as if the phone is trying to boot over and over.
I realise I have ****ed up by flashing the kernal of a different phone. I'm hoping someone can help me or guide me in the right direction.
Thank you.
Click to expand...
Click to collapse
Try this:
Open flashtool
Hold volume up and insert usb cable( you will enter fastboot )
then select fastboot and flash a good kernel for CM.
let me know it this works
RaZieLRaH said:
Try this:
Open flashtool
Hold volume up and insert usb cable( you will enter fastboot )
then select fastboot and flash a good kernel for CM.
let me know it this works
Click to expand...
Click to collapse
Hi,
I tried what you said. When holding Volume UP and inserting cable, literally nothing happens. I don't even get a sound from Windows detecting it.
Whilst trying this several times though I did notice if I press Power the phone seems to stay on for 30-60 seconds. If I press Power and plug it in, Windows will make a sound. It will then make another sound after 30-60 seconds as if the device has been removed or turned off.
no clue then sorry can't help
Nightstaar said:
Hi,
I tried what you said. When holding Volume UP and inserting cable, literally nothing happens. I don't even get a sound from Windows detecting it.
Whilst trying this several times though I did notice if I press Power the phone seems to stay on for 30-60 seconds. If I press Power and plug it in, Windows will make a sound. It will then make another sound after 30-60 seconds as if the device has been removed or turned off.
Click to expand...
Click to collapse
Just for giggles, check your device manager to see if you have an unknown device... (you may need to install the fastboot drivers...) I've bootlooped my phone a couple of times while putzing with my phone... And can normally get back into flash mode and fast boot mode...
Sent from my Xperia ZL using Tapatalk
scifan said:
Just for giggles, check your device manager to see if you have an unknown device... (you may need to install the fastboot drivers...) I've bootlooped my phone a couple of times while putzing with my phone... And can normally get back into flash mode and fast boot mode...
Sent from my Xperia ZL using Tapatalk
Click to expand...
Click to collapse
I did check this. There are no unknown devices. I did install the Xperia Z/fastbot/flashboot drivers from the flashtool folder. When it does make the detection sound Device Manager does 'reset' as if something has connected as well, although I can't find the device.
Most other similar issues have an LED or some type of display and generally are responsive to flashmode.
Note1 boot partition is the XZ's SBL3 (bootloader) partition. So you have effectively flashed a Note1 boot.img to your bootloader. Phone will never boot again once bootloader is hosed. Sorry about your loss
Sent from my C6603 using xda app-developers app
Shoey is right, your Z is toast now, sorry; the only solution here is to replace the MoBo, and that costs a pretty penny.
But why did you download stuff from the n7000 forum? Didn't everything said there sound unfamiliar and therefore suspicious enough for you
to double-check which forum you were in exactly?
I thought as much. I dun goof'd
Thanks for your help.
@chasmodo: Well I started in the N7000 thread and downloaded all the stuff and copied it to my SD card. I then realised I was in the wrong forum and switched to the relevant thread. All the stuff for the N7000 and the Z were both on my SD card, so it was just a stupid mistake really. Everything on both forums sounded a little unfamiliar. As I mentioned I was a bit cofused on the TWRP section. I should done more research before proceeding.
Do you think there is any use for the phone now? Do you know of anywhere/anyone I can donate it to for spare parts or something?
Nightstaar said:
Do you think there is any use for the phone now? Do you know of anywhere/anyone I can donate it to for spare parts or something?
Click to expand...
Click to collapse
As I said, you can get it fixed by replacing the MoBo, but I don't know how much that costs in your country. Google a little, contact someone, get the info and then decide what to do.
chasmodo said:
As I said, you can get it fixed by replacing the MoBo, but I don't know how much that costs in your country. Google a little, contact someone, get the info and then decide what to do.
Click to expand...
Click to collapse
I did have a look around and had trouble finding a main board in particular. I contacted Sony as well and they said it was quite expensive to replace.
I contacted my carrier and it appears getting a new phone is a lot cheaper than anything I've looked into so far.
Thanks for your help.
The next time you decide to flash your phone , make sure your in the correct forum. Lesson learned
Sent from my C6603 using XDA Premium 4 mobile app

Categories

Resources