[Q]Upper touchscreen not working - XPERIA X10 Q&A, Help & Troubleshooting

Hi everybody,
as I say, my upper screen (touchscreen) does no more respond (It may happened after a fall). I try all I can think which can solve the problem but in vain.
1. Flash, and reflash, original rom, baseband, kernel, custom rom, through SEUS, flashtool, CWM, etc...
2. I unmount the phone to see wether a cable was not connected.
So, I come here to see if soneone can solve it.

dmjb1981 said:
Hi everybody,
as I say, my upper screen (touchscreen) does no more respond (It may happened after a fall). I try all I can think which can solve the problem but in vain.
1. Flash, and reflash, original rom, baseband, kernel, custom rom, through SEUS, flashtool, CWM, etc...
2. I unmount the phone to see wether a cable was not connected.
So, I come here to see if soneone can solve it.
Click to expand...
Click to collapse
I am almost sure that you have broke the top part of digitizer - you have to replace it.

Hmm, ok, i'm seems to be bad news for me. Thanks for the answer.
PS: In the meantime, I bought another phone (acer iconia S300).

dmjb1981 said:
Hmm, ok, i'm seems to be bad news for me. Thanks for the answer.
PS: In the meantime, I bought another phone (acer iconia S300).
Click to expand...
Click to collapse
You can sell it for a replacement parts if other parts are working normally.
Or if you have some technical skills you can replace it. Digitiser module can be bought cheap on ebay. I could also provide you some more detailed infos if you want (I am repairing electronics).

Thanks Dude. I'll search one on ebay and I'll be back later.

Related

[Q] Bricked my phone?

So I had previously rooted my SGSII, and decided to try installing CM7 on it. I used CWM Recovery and ran it off the SD card, and everything appeared to work fine. I think I had a bad/not fully functioning CWM or something, as it didn't list an option to backup anything (I'm guessing because I flashed the stock kernel after rooting?) Anyway, it will no longer boot. I can access download mode, but Odin fails everytime I try to flash anything back on there. When I try to boot my phone, I just get a "Firmware upgrade encountered an issue" error.
EDIT: I just tried again as I was writing this, after rebooting, reinstalling my drivers and rebooting my computer. I was able to get the Firmware to flash properly in Odin. Now I have my phone booting and getting stuck on the "Samsung Galaxy SII GT-I9100 splash screen... Doesn't seem to go any further than that though, unfortunately.
Any ideas what I can do? Is it possible that I need re-flash a bootloader or something ??
Any help would be supremely appreciated!
So I was just trying to re-install the Kernel, using the CF unsecured kernel, and it failed, but when I try to go into recovery mode, it looks as though it managed to install CWM Recovery. I have no idea what to do from here, and am sort of afraid to do anything for fear or bricking the phone completely...
I'm hoping someone out there knows how to fix this, I feel like such a tool
As long as you can get into download-mode, your phone isn't bricked.
If you switch from or to a TouchWiz-based ROM, you have to do a full-wipe in the recovery.
Sent from my GT-I9100 using XDA App
Go back to stock first via download mode via odin
Nah you're good. Similar thing happened to me at my first flashing attempt. Get your stock firmware from Intratech's thread, put the phone into download mode & flash the firmware via Odin.
Then maybe have another go at rooting the phone with the matching CFRoot kernel.
Porkchops said:
So I was just trying to re-install the Kernel, using the CF unsecured kernel, and it failed, but when I try to go into recovery mode, it looks as though it managed to install CWM Recovery. I have no idea what to do from here, and am sort of afraid to do anything for fear or bricking the phone completely...
I'm hoping someone out there knows how to fix this, I feel like such a tool
Click to expand...
Click to collapse
yes, if you can still go in download mode it's no so difficult..this "small brick" it's on of "Android things to do" once in your SGS2 life
Hi guys. I'm in a worst situation. As my phone after a failed ODIN downgrade from Android 2.3.6 to one stock kernel is completelly dead - it doesn't boot anymore - not even managed to put it back into download mode or revert to fact defaults (no keys, no lights not even battery charging displayed when pluged in) - tryed the USB jig also. Nothing worked.
The question is: Will Samsung manage to repair and how much will it cost - an average ammount offcourse. Because I guess it's out of the question to be considered a warranty issue. I guess it will be visible somebody have done smth to the ROM by a software approach....
This is the short story because I would bore you to discuss all the things I have been through - it was only my faoult out of stupidity
HELP!
I don't see why Samsung wouldn't fix it ? As to how much they'll charge you, I think you'll find that will vary from country to country (labour costs being variable, etc). No, I don't think you'll be able to have it repaired under warranty.
You might want to look at having it JTAG repaired by someone other than Samsung. This will possibly be cheaper than having Samsung repair it. Do a search on here/Google.
alexdonc said:
The question is: Will Samsung manage to repair and how much will it cost - an average ammount offcourse. Because I guess it's out of the question to be considered a warranty issue. I guess it will be visible somebody have done smth to the ROM by a software approach....
HELP!
Click to expand...
Click to collapse
Thank you very much. I have searched alot to actually understand - unfortunatelly for me it will cost... I saw on youtube a JTAG in action right now (cannot post the link yet). I understand now it is the only way. I'll keep you posted guys. Tomorrow I'll go to service.
I'm sorry it's going to cost Alex. A difficult thing to happen, I know
Here's a link for a JTAG repairer in the US who is also a member here, tho I see you've already found one. I'm sure doing it this way will be cheaper/probably faster than having Samsung do the repair as well.
alexdonc said:
Thank you very much. I have searched alot to actually understand - unfortunatelly for me it will cost... I saw on youtube a JTAG in action right now (cannot post the link yet). I understand now it is the only way. I'll keep you posted guys. Tomorrow I'll go to service.
Click to expand...
Click to collapse
Thax. Funny thing is that this is exactly the thing I found - the same mobiletechvideos in US Now I allready have an ideea of how much should cost that. Hopefully I'll find a local GSM repair shop with the posibilitty to unbrick it cheep - or at least not much than 50USD - in local currency ofcource.
I'm still thinking if it is possible to use an ATMEL copy process - like in the old times for EEPROMS - I have done that in the past. In theory it might work but I will never do it - alredy scared about what happened to my beloved droid.
Thx again Mistah and have a gr8 day and a wonderfull new 2012!
Yeah I've seen a report or two on here from people who have used his service & have been happy. Must admit I found his page when thought I'd bricked my phone after my first flash attempt messed up. Yeah you might be able to get it done cheaper somewhere local, and that will mean less time without the phone for you without the phone in mail from you to the US & back again.
Let us know how you get on, your experience will be a good guide for people in future who have the same problems as you.
No probs man, happy to give you the little help I did. You too Alex Hope you have a great year & you get your phone back & working soon
alexdonc said:
Thax. Funny thing is that this is exactly the thing I found - the same mobiletechvideos in US Now I allready have an ideea of how much should cost that. Hopefully I'll find a local GSM repair shop with the posibilitty to unbrick it cheep - or at least not much than 50USD - in local currency ofcource.
I'm still thinking if it is possible to use an ATMEL copy process - like in the old times for EEPROMS - I have done that in the past. In theory it might work but I will never do it - alredy scared about what happened to my beloved droid.
Thx again Mistah and have a gr8 day and a wonderfull new 2012!
Click to expand...
Click to collapse
Hello again. Solved right now. The service didn't charged me at all - I was kind of lucky after all. Unfortunately there are still some issues I have from the start. I'll keep on digging - software related.

Touchscreen not Working after rooting

I have a problem and hope somebody have a solution.
My S3 was updated to JB. Then i uses CF Auto Root to root it. After Odin, the phone rebooted and the Samsung S3 wording started to flicker and get disorientated from the screen. Then it went blank. I tot it freezes and removed the batt. Then i redo again. The same thing happen and i leave it there then after about 8-10s, the phone reboot and started off from the languge selection. But touchscreen died.
So i install the stock rom again thinking is FW corrupted, Problem still there. I try root with CF Root 6.4, Problem still there. I install stock ROM again. Problem still there. Now my FW is official but counter is 11. I see a problem with bring back to Samsung.
I also removed batt, remove sim and all sorts of stuff but problem still exist. Bascially stuck at the start up languge selection screen and touchscreen dead
So hopefully somebody got a solution before i take the last action of bring back to samsung. Thks
Mine too!!!
Did you use the correct version of CF root??? I accidentally flashed the wrong one because it was right next to the correct one. The exact same thing happened to me!!!!!!!!!!!! I think the touch screen controller is dead. I am going to look at the Log to see what's happening. Does yours also take a while to boot or to load recovery?!!
CryptXus said:
I have a problem and hope somebody have a solution.
My S3 was updated to JB. Then i uses CF Auto Root to root it. After Odin, the phone rebooted and the Samsung S3 wording started to flicker and get disorientated from the screen. Then it went blank. I tot it freezes and removed the batt. Then i redo again. The same thing happen and i leave it there then after about 8-10s, the phone reboot and started off from the languge selection. But touchscreen died.
So i install the stock rom again thinking is FW corrupted, Problem still there. I try root with CF Root 6.4, Problem still there. I install stock ROM again. Problem still there. Now my FW is official but counter is 11. I see a problem with bring back to Samsung.
I also removed batt, remove sim and all sorts of stuff but problem still exist. Bascially stuck at the start up languge selection screen and touchscreen dead
So hopefully somebody got a solution before i take the last action of bring back to samsung. Thks
Click to expand...
Click to collapse
Hi
I am also in the same boat, any solution for this problem ?
Best regards
Sounds like u fried ur LCD touch. Hope u have insurance.
Sent from my SCH-I535 using xda app-developers app
Odp: Touchscreen not Working after rooting
I suppose wrong version used.
Sent from my washing machine...straight from the tumbler...
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
My working solution
Hi, I had the same problem and the only one solution I've tested is changing the touch driver on the touch module. All you need is a broken touch (the donor) and a lot of patience.
Step1. Disassemble the working phone.
Step2. Carefully take out the touch module (here you need a lot of patience and time). DON'T TRY to change the driver on the assembled phone because the display will be destroyed. I speak from experience.
Step3. After the module is out unplug the touch panel from the display and blend out the driver.
Step4. Now you can change the driver. NEVER try to change the driver when it is on the display.
Step5. After finished changing the driver repeat all the steps in the reverse order.
It is working 100%.
Sup
lores79 said:
Hi, I had the same problem and the only one solution I've tested is changing the touch driver on the touch module. All you need is a broken touch (the donor) and a lot of patience.
Step1. Disassemble the working phone.
Step2. Carefully take out the touch module (here you need a lot of patience and time). DON'T TRY to change the driver on the assembled phone because the display will be destroyed. I speak from experience.
Step3. After the module is out unplug the touch panel from the display and blend out the driver.
Step4. Now you can change the driver. NEVER try to change the driver when it is on the display.
Step5. After finished changing the driver repeat all the steps in the reverse order.
It is working 100%.
Click to expand...
Click to collapse
So u must pay to buy a new touch module?
Dewasatya said:
So u must pay to buy a new touch module?
Click to expand...
Click to collapse
Pay yes unless its under warranty and root voids warranty .
OP self inflicted damage nothing to do but pay and learn .
jje
Root your Device
To Reset binary counter when touch is Dead Click here
Now Flash with a Stock Rom
And CLAIM Your Warranty

[Q] X10mini Pro completely dead!

First of all, I wanted to say hello since this is my first post here :victory: and also please if I am posting wrong or if this question has been answered before forgive me, but I have already searched on google and on this forum and found no related posts Ok now about my problem:
I have a "Sony Ericsson Xperia X10mini Pro" with MiniCM10-4.1.0-20130416(mimmi) and 2.6.32.60-nAa-jb-05 kernel installed. Yesterday I decided to go back to U20_nAa-14_2.6.29.6-nAa-14 kernel and MiniCM7-2.2.1-mimmi-UNOFFICIAL because of wifi problems. I have done the flashing process with flashtool a lot of times in the past and I can't be wrong with it this time.
The problem started after flashing my kernel. Flashtool flashed the U20_nAa-14_2.6.29.6-nAa-14 kernel fine and phone was OK ready to reboot, so I unplugged the USB cable to start it on recovery so I could install Minicm from SD, but since I unplugged the cable the phone is DEAD! No led and no charging! :crying: When I try to reflash it, flashtool doesn't recognize it, I am pressing the back button and plugging it in but the phone is not recognized. It is not charging when I am plugging it on the charger and its not even trying to boot. I tried different cables, different battery (from a friend with the same phone) and nothing. Is there a way to force flash it back? Please any help will be appreciated since I have tried everything I know...
This has happend to other users too reasently.
I'm not sure if it only happens when going from JB to GB or it also happens when going from GB to JB.
We need to investigate why/how it happens and how to prevent it.
I always recomend to do a battery stat whipe just before a planed kernel-flash. I had simular problem once (no charge, no boot, no nothing) after a kernel-flash. I solved it by putting in a battery from another Mimmi (my wife has the same model). For some reason everything worked fine doing so. After battery stat whipe, the phone worked with my own battery again.
Best advise for others is for now: When you want to flash new kernel, first do a SEUS/PC Companion repair
This should be written into all install-instructions and mentioned again and again to avoid same problem for others.
I'm not sure how the other users solved this. Was it only by JTAG?
Thank you for your answer! :good:
First of all, there was no battery wipe option on this release of the kernel As I said before I have done it a couple of times in the past and every time with battery wipe, except this one and besides, I already tried your solution with my friends battery with no luck... So probably I am looking for another solution.
And one last thing about your post, what is "JTAG"?? I have seen it on other posts before but without explanation as to what it is, the only JTAG I know of is on the xbox360 And if its a possible solution how can I possibly do it? Is there a post with instructions?? (I will search on my own too now, but a recommended guide from someone who knows better is much appreciated!)
Emperor.dk said:
This has happend to other users too reasently.
I'm not sure if it only happens when going from JB to GB or it also happens when going from GB to JB.
We need to investigate why/how it happens and how to prevent it.
I always recomend to do a battery stat whipe just before a planed kernel-flash. I had simular problem once (no charge, no boot, no nothing) after a kernel-flash. I solved it by putting in a battery from another Mimmi (my wife has the same model). For some reason everything worked fine doing so. After battery stat whipe, the phone worked with my own battery again.
Best advise for others is for now: When you want to flash new kernel, first do a SEUS/PC Companion repair
This should be written into all install-instructions and mentioned again and again to avoid same problem for others.
I'm not sure how the other users solved this. Was it only by JTAG?
Click to expand...
Click to collapse
zero2048 said:
Thank you for your answer! :good:
First of all, there was no battery wipe option on this release of the kernel As I said before I have done it a couple of times in the past and every time with battery wipe, except this one and besides, I already tried your solution with my friends battery with no luck... So probably I am looking for another solution.
And one last thing about your post, what is "JTAG"?? I have seen it on other posts before but without explanation as to what it is, the only JTAG I know of is on the xbox360 And if its a possible solution how can I possibly do it? Is there a post with instructions?? (I will search on my own too now, but a recommended guide from someone who knows better is much appreciated!)
Click to expand...
Click to collapse
I'm pretty sure he flashed the x10blrelock.ftf instead of the u20 kernel and that is why his phone went dead.
A JTAG for our phone will do basically the same thing as a JTAG for the xbox, it restores original phone-state, but you need special equipment to do it, which is quite expensive. Most repair-shops will have one.
SmG67 said:
I'm pretty sure he flashed the x10blrelock.ftf instead of the u20 kernel and that is why his phone went dead.
A JTAG for our phone will do basically the same thing as a JTAG for the xbox, it restores original phone-state, but you need special equipment to do it, which is quite expensive. Most repair-shops will have one.
Click to expand...
Click to collapse
Thank you for the answer about jtag, I also checked for myself and found about the expensive equipment and propably its not the way for me
But about the kernel I am pretty sure it was the right file...
I know that a dead phone means bad kernel but its a process that I have done before a lot of times with success on mine and other phones My best guess is that something interrupted the process (bad usb cable?) or corrupted downloaded kernel file If that's the case is there an alternative solution? :crying:
zero2048 said:
Thank you for the answer about jtag, I also checked for myself and found about the expensive equipment and propably its not the way for me
But about the kernel I am pretty sure it was the right file...
I know that a dead phone means bad kernel but its a process that I have done before a lot of times with success on mine and other phones My best guess is that something interrupted the process (bad usb cable?) or corrupted downloaded kernel file If that's the case is there an alternative solution? :crying:
Click to expand...
Click to collapse
Usually, whatever you flash, even if it goes bad, flashmode is still available because that doesn't get tampered with, the only true hardbrick i've ever seen is when flashing that x10blrelock.ftf, which happens quite a lot lately.
Just for fun i even formatted my entire phone once, no kernel, no rom, completely empty, and flashmode was still there so it could be recovered.
I noticed that in some older versions of flashtool you sometimes had to click the kernel you wanted twice in order to get it to pick up the right one. Normally there's not much difference you can spot (most .ftf's just contain a loader and a kernel), but i had full SE firmware in .ftf format, which contained other sections too, and that's where i noticed it didn't always pick it up right at the first time of clicking.
SmG67 said:
Usually, whatever you flash, even if it goes bad, flashmode is still available because that doesn't get tampered with, the only true hardbrick i've ever seen is when flashing that x10blrelock.ftf, which happens quite a lot lately.
Just for fun i even formatted my entire phone once, no kernel, no rom, completely empty, and flashmode was still there so it could be recovered.
I noticed that in some older versions of flashtool you sometimes had to click the kernel you wanted twice in order to get it to pick up the right one. Normally there's not much difference you can spot (most .ftf's just contain a loader and a kernel), but i had full SE firmware in .ftf format, which contained other sections too, and that's where i noticed it didn't always pick it up right at the first time of clicking.
Click to expand...
Click to collapse
I understand what you mean and its really easy to make the mistake!! But well, still I don't think I made it but I guess there is nothing more to do anyway Thank you both for your help and I hope soon to return the favor on this forum :victory:
Can you tell me an average cost about the recovery process according to your experiance in your country?? Is is expensive in general?
zero2048 said:
I understand what you mean and its really easy to make the mistake!! But well, still I don't think I made it but I guess there is nothing more to do anyway Thank you both for your help and I hope soon to return the favor on this forum :victory:
Can you tell me an average cost about the recovery process according to your experiance in your country?? Is is expensive in general?
Click to expand...
Click to collapse
Someone in this forum had it done in Latvia for next to nothing.
In the USA it will cost you, your right arm.
zero2048 said:
I understand what you mean and its really easy to make the mistake!! But well, still I don't think I made it but I guess there is nothing more to do anyway Thank you both for your help and I hope soon to return the favor on this forum :victory:
Can you tell me an average cost about the recovery process according to your experiance in your country?? Is is expensive in general?
Click to expand...
Click to collapse
I just had a look online for prices in my country, it seems to be around €25.
SmG67 said:
I just had a look online for prices in my country, it seems to be around €25.
Click to expand...
Click to collapse
Emperor.dk said:
Someone in this forum had it done in Latvia for next to nothing.
In the USA it will cost you, your right arm.
Click to expand...
Click to collapse
Emperor.dk how old are you?
SmG67 thank you again and I will delete x10blrelock.ftf just in case....
hi guys, i have the same problem too, when my rom is minicm10 and my kernel is jb-naa-05, i want to go back to MiniCM7 because of green screen camera in MiniCM10 so i go back to MiniCM7, I flashed the right kernel e10-2.6.29.6-naa-14 for my x10 mini via flashtool and after i flash the kernel, my phone does not booting up(5 mins no booting up) so i decided to use seus but seus does not recognize my x10 mini, i try flashtool, but flashtool is not recognize my x10 mini so i tried to flash my created stock 2.1.ftf(thanks to leajian) and selected x10 mini from device selection(my x10 mini is not recognize in flashtool), then i wait until it finish, when i tried to open my phone, it boots up and show sony ericsson logo and it boots up(sucess!!!)...
sorry for my english...
so for all MiniCM10 Users, Dont try to go back to MiniCM7 If your Rom is MiniCM10 because it will cause your phone to not booting up like my problem.
Renz29 said:
hi guys, i have the same problem too, when my rom is minicm10 and my kernel is jb-naa-05, i want to go back to MiniCM7 because of green screen camera in MiniCM10 so i go back to MiniCM7, I flashed the right kernel e10-2.6.29.6-naa-14 for my x10 mini via flashtool and after i flash the kernel, my phone does not booting up(5 mins no booting up) so i decided to use seus but seus does not recognize my x10 mini, i try flashtool, but flashtool is not recognize my x10 mini so i tried to flash my created stock 2.1.ftf(thanks to leajian) and selected x10 mini from device selection(my x10 mini is not recognize in flashtool), then i wait until it finish, when i tried to open my phone, it boots up and show sony ericsson logo and it boots up(sucess!!!)...
sorry for my english...
so for all MiniCM10 Users, Dont try to go back to MiniCM7 If your Rom is MiniCM10 because it will cause your phone to not booting up like my problem.
Click to expand...
Click to collapse
If you follow nAa's instructions properly, there is no problem.
What you have to do:
Wipe data/factory reset in CWM on the JB-kernel
Flash the GB-kernel
Format /system, /data en /cache, so they get back to the original sizes
Flash the GB-ROM, or restore a previous GB-backup you may have had
No problems at all...
And your phone still had flashmode available, unlike the OP of this thread, so you don't have the 'same' problem
zero2048 said:
Emperor.dk how old are you?
Click to expand...
Click to collapse
Why?
If you are asking me on a date? LOL, the answer is no :laugh:

[THL] W200s- Firmware- Please help!

Hello to everyone, I want to ask for your help!
First of all sorry for my bad english! I will try to explain the situation.
Last December (2014) I bought a THL W200s phone, from China. It's impossible for me to find the seller, because my uncle that was living in China for 1 year, ordered the phone via TaoBao but he doesn't remember to what seller.
Well, the phone was ok, till it fell down to the floor and the display broke.
I mean, the "outside" glass was ok, but the display wasn't.
I ordered a new phone screen in Aliexpress (ask for the link, I can't put any link here) and changed the screen.
The new screen works OK, but I've a problem. I can't get the touchscreen working.
I mean, I can see perfectly the main menu, but if I touch the screen, it doesn't "moves" or do anything, the touchscreen part isn't working.
I talked to the seller, and researched, and found out that might be a firmware problem. Something like that the screen was newer than the phone, or vice versa.
I downloaded and flashed almost all the firmwares/ROM's available in the Internet for THL W200s, that can be flashed by SP FlashTools (I can't use another method to flash because the touchscreen doesn't work), but no one worked completely.
I mean, with all the firmwares/ROM's I flash, I get the same result. Display works OK, but no touchscreen.
Except with this one : Needrom- W200S 4.4.2-KK-09/09/2014
With that one, I get the opposite result, I mean, my touchscreen works, but the display doesn't. The Phone turns on, but shows no image, it's all black, but I can feel the vibration when I press the screen and the touchscreen works OK.
I don't have experience flashing that things, or in basic Android, but I wanted to know if you can help me! I'm desperate!
I would have to "combine" the "part" or file that contains the touchscreen of that ROM (W200S 4.4.2-KK-09/09/2014) with another one, So I can finally get my display and touchscreen working.
Any ideas of how to do it? I tried replacing the lk.bin file of the ROM I mention, in some other ROM's that make my display works, but I don't get any good result.
Please, if this topic doesn't go in this forum, or if I've posted some link that can't be posted, I apologize!
Thanks for reading, if you don't understand something please ask!
PD: I've already asked to the seller for the suitable firmware, but the one that he provided, doesn't work.
Any never firmware should work. How you tried to install firmware? By FlashTool? Flash everything but preloader, it should work. To be on the safe side try latest JellyBean (4.2.2) from needrom. This could be some new screen revision but who knows. Please post your results.
miljenko said:
Any never firmware should work. How you tried to install firmware? By FlashTool? Flash everything but preloader, it should work. To be on the safe side try latest JellyBean (4.2.2) from needrom. This could be some new screen revision but who knows. Please post your results.
Click to expand...
Click to collapse
First, thanks for reading!
Yes, I've tried via SP FlashTools v5.1352.01, because I think I can't flash ROM's with CWM or TWRP because I can't get my touchscreen working, so I can't install them on my phone. If I'm not right, please correct me.
As I said, I tried almost every rom that is available in NeedRom for thl w200s that can be flashed using SP FlashTools. But I can't get any good result, touchscreen doesn't work. I'm sure it's only a firmware problem, because flashing the ROM that I describe in the topic, touchscreen works but display doesn't. And flashing any other ROM display works but touchscreen doesn't.
Could you recommend a ROM to try? I don't know what else to do. I'm afraid my phone is lost
What I did to flash all the ROM's I download, using SP Flash Tools, is to select the Android scatter, then in the sliding panel clicked in "Firmware Upgrade", click in Download, connect the phone without the battery, and wait the ROM to be flashed.
I don't know what is wrong !
I had the same problem when I changed my screen.managed to use my back up I made with mtk droid tools.before I changed my screen,I was on the 4.4.2 ROM which I could now no longer use(black screen), but for some reason I could now install the ROMs from need ROM (which I couldn't use before)and the backups on my phone would freeze when I used them.only the stock ROM I had and the ultimate ROM from need ROM would work.but now the mic no longer works(tested with the google apk,phone calls and sound recorder) and the vibrate does not work and the proximity sensor does not work(tested it by using the dialer but the screen stays dark so can't end the call.so I got a dialer apk from play and that works but in the end I used a xposed module to stop the proximity sensor. really had enough of this phone.
Sent from my W100 using XDA Free mobile app

Elephone P9000 Lite softbricked

Hi everyone,
This is my problem: yesterday while under charge my phone died. When I tried to reboot it, it just showed the white elephone logo without animation. I tried to reboot few times but nothing. I could access the recovery(TWRP) but it couldn't mount any partition, so I could not do anything like formatting or wiping anything. I tried to connect the phone to my PC and it was recognized, so I also tried to flash the stock rom (many times actually) with no luck... As a side note when I plug it to the power the battery icon shows up, but still with no animation...
Does anyone of you know what could possibly be the problem, or any viable solution?
Although I havent got a solution to your issue, HERE is a very similiar situation someone else had, unfortunately the thread doesnt end offering any solution but perhaps you can PM the OP of the thread and ask if he resolved it and how ? Hope you can get it sorted without having to resort to Elephone warranty support (we all know how bad that is)
jotei66 said:
Although I havent got a solution to your issue,HERE is a very similiar situation someone else had, unfortunately the thread doesnt end offering any solution but perhaps you can PM the OP of the thread and ask if he resolved it and how ? Hope you can get it sorted without having to resort to Elephone warranty support (we all know how bad that is)
Click to expand...
Click to collapse
Thanks for the reply, I contacted the OP, let's hope he will answer me... I also tried to flash in Firmware upgrade, with no results...
Just to update you, I have ordered a new battery as last hope, but with no results... eMMC fried I suppose. 8 months of life. I regret having bought this phone.
alexvago said:
Just to update you, I have ordered a new battery as last hope, but with no results... eMMC fried I suppose. 8 months of life. I regret having bought this phone.
Click to expand...
Click to collapse
Maybe the partitions gotcorrupted and you just need to repartition the drive, doing a format all on sp flash should work, but you will lose imei and you need to restore it later on. Then simply flash the stock rom for Lite version and done.

Categories

Resources