Lenovo Vibe P1Ma40 HARDBRICKED - Lenovo Vibe P1m Questions & Answers

I did everything stated to flash custom rom but phone got bricked!
I know its only my fault but any help would be appreciated!
What's happening:-
only charging led turning on
no usb connection possible
nothing happens when any button is pressed
not detected by spflash tool
Nothing is happening
EDIT! FIXED IT!
opened up the phone as it was last thing to do.
Removed battery for a while..
Put everything back in.
Plugged into the pc via usb with fingers crossed!
And wow! It was detected as com port.
But disappeared in a second ie it entered meta mode.
But it means it could be saved.
Downloaded stock rom, flashed it with sp flash tool.
And now it's back to life.

Related

[Q] Can't get out of emergency mode (NO USB DEBUGGING MODE)

Hello all,
I have big problems with my L7 P700.
I rooted it two month ago, even that time I was stuck at yellow emergency mode, but using some instruction (disable LG modem) I was able to boot phone again.
Today I believe I have totally different problem.
What I did, I found stock firmware 4.1.2 and LG drivers, I installed it. Restarted phone and pressed Volume UP + Power. Phone went to yellow emergency mode, ok... Then I tried to use KDZ_FW_EN, phone was not seen. I restarted it and it booted ok to system. Turned of again, went to emergency mode than I opened KDZ_FW_EN again. I tried to read phone information, the program chrashed. I opened it again and tried to flash firmware. There were errors, and I am pretty sure phone wasn't even properly connected to PC!
So if you don't understand me I will repeat again.
I went to emergency mode WITHOUT USB DEBUGGING ON (I disabled it one day, I remember, this time I forget to turn it on). So Under device manager I see only USB composite device and LG Modem, disabling modem isn't a fix (like two month ago when I rooted). This time I can't use any of flashing tools cos I am not in debugging mode =(. The only thing I don't understand is how I was able to destroy my phone if it wasn't even flashing it (port number was -1, some wparam 100-1000 errors, i closed program in the middle but it wasn flashing if I wasn't in debug mode?)
Phone is rooted and stuck at emergency mode, without usb debugging and hard reset bring the emergency on (BOTH VOLUME BUTTONS + MENU)
Anyone?
Yes, I had the same problem a few months ago. Try install firmware stock V20D without battery and then connect phone via cable USB to PC but turning on Emergency Mode. Next, 3GQCT and CS EMERGENCY. Of course you can change port USB. Try reinstall KDZ and drivers. If you have Windows Vista then that's the problem. I'm sure that this situation will be resolve.
Ok I made it!
Don't know how, maybe it was working all the time. I've seen that phone is connected thru Ports (COM & LPT). Opened KDZ again, even that the install for firmware usb driver failed. I again tried to flash, again there were errors (wparam,...) and port -1?, I just left phone connected, yesterday I unplugged it! After 10minutes phone restarted and here is 4.1.2 and all the data is here!
Don't know what I was doing =)
Thread can be closed now!
Great!

Bricked Jiayu S3 Advanced help!

Yesterday i flashed my Jiayu S3 to lolipop (i tought) and i just bricked my phone!
After reboot it was just dead.. when i plug into pc with USB i hear the connect sound and after 2 seconds the disconnect sound. This keeps on going until i pull the USB plug. When i look in DeviceManager i see it refresh after every sound, but nothing pops up (unknown device or whatever). I deletet all usb drivers with usbdeview, restart pc but still no changes.
I tried with or without battery, but without it does nothing at all.. i tried holding Vol+ or - or both or with power button, but nothing.
Read some threads about unbrick and install correct usb driver for jiayu s3, but all the options they came with does not work on my device!
I'm a little despered now and don't know what to do.. i get the feeling that my 2 weeks old phone is dead? :'(
My pc has windows 7
Did the flash with SP Flashtool 5.1516
Did not untick preload in flashtool, i guess i got the wrong preload or something??
Please help!
No one..? :crying:
Lowrida said:
Yesterday i flashed my Jiayu S3 to lolipop (i tought) and i just bricked my phone!
After reboot it was just dead.. when i plug into pc with USB i hear the connect sound and after 2 seconds the disconnect sound. This keeps on going until i pull the USB plug. When i look in DeviceManager i see it refresh after every sound, but nothing pops up (unknown device or whatever). I deletet all usb drivers with usbdeview, restart pc but still no changes.
I tried with or without battery, but without it does nothing at all.. i tried holding Vol+ or - or both or with power button, but nothing.
Read some threads about unbrick and install correct usb driver for jiayu s3, but all the options they came with does not work on my device!
I'm a little despered now and don't know what to do.. i get the feeling that my 2 weeks old phone is dead? :'(
My pc has windows 7
Did the flash with SP Flashtool 5.1516
Did not untick preload in flashtool, i guess i got the wrong preload or something??
Please help!
Click to expand...
Click to collapse
so you cannot boot into recovery or fastboot either?
Lowrida said:
Yesterday i flashed my Jiayu S3 to lolipop (i tought) and i just bricked my phone!
After reboot it was just dead.. when i plug into pc with USB i hear the connect sound and after 2 seconds the disconnect sound. This keeps on going until i pull the USB plug. When i look in DeviceManager i see it refresh after every sound, but nothing pops up (unknown device or whatever). I deletet all usb drivers with usbdeview, restart pc but still no changes.
I tried with or without battery, but without it does nothing at all.. i tried holding Vol+ or - or both or with power button, but nothing.
Read some threads about unbrick and install correct usb driver for jiayu s3, but all the options they came with does not work on my device!
I'm a little despered now and don't know what to do.. i get the feeling that my 2 weeks old phone is dead? :'(
My pc has windows 7
Did the flash with SP Flashtool 5.1516
Did not untick preload in flashtool, i guess i got the wrong preload or something??
Please help!
Click to expand...
Click to collapse
Just flash it again, but this time with "Firmware upgrade " in SP Flashtool instead of "Download". Change from KK to LL needs reepartitioning, so firmware upgrade.
The reason why you don´t "see" the S3 any longer on the pc is, that the USB storage mode from KK, which is driverless for windows, don´t work right now on LL.
Once flashed to LL you will need to install a driver, for windows to connect to the S3.
@ Dior DNA:
No i can't. Phone does nothing with the buttons. Only diference if i hold Vol - then time from connect sound and disconnect sound is a little longer.. about 10 seconds. But still nothing happens.
@1testi:
Flashtools can't see my phone. I tried it a hundred times. With battery, without battery, with Vol - and with Vol +.
When i connect the USB cable i hear the connect sound and after 2 a 3 seconds i hear disconnect sound. This goes on and on until i pull the USB cable out. In devicemanager i see a refresh going on, but nothing pops up.
I'm realy despered on what to do now?
Lowrida said:
@1testi:
Flashtools can't see my phone. I tried it a hundred times. With battery, without battery, with Vol - and with Vol +.
When i connect the USB cable i hear the connect sound and after 2 a 3 seconds i hear disconnect sound. This goes on and on until i pull the USB cable out. In devicemanager i see a refresh going on, but nothing pops up.
I'm realy despered on what to do now?
Click to expand...
Click to collapse
Why the SP Flashtool isn´t working any longer? You didn´t deinstalled the driver, did you? Just try to flash again with "Firmware Upgrade".
I don´t know a way to reinstall the driver in windows without the preloader. The only thing you can do, as far as i know, is to use a linux
pc to flash again. Linux don´t need a driver for SPF, only some rules.
Lowrida said:
@ Dior DNA:
No i can't. Phone does nothing with the buttons. Only diference if i hold Vol - then time from connect sound and disconnect sound is a little longer.. about 10 seconds. But still nothing happens.
(
Click to expand...
Click to collapse
Booting into recovery or flashtool I meant regardless of pc and/or spflashtool.
If I recall correctly:
hold volup and power boots recovery
hold voldn and power boots flashtool
If you can boot recovery then which one is it? Maybe you can restore something or manually flash preloader bin from there.
After the flash i reboot and then the connect and disconnect sound appears. So i tried differend things, but could not connect. I wanted to flash again, but flashtool did not reconice the phone and nothing in DeviceManager. That's why i thought to remove the driver and try to re-install it. But that did not help..
Holding Vol - or + button with power button or both Vol buttons with power button does nothing.. i tried to hold all combinations at least 30 seconds, but nothing at all.
I have no Linux pc or any knowhow to make a Linux pc.. or a pc to install Linux on..
One last thing you can try: remove the battery, wait a little, insert the battery again. Hold vol+ key, keep holding it and press power
button, while still holding the vol+. If you don´t see anything happening then you bricked the phone.
You will need help from a professional or at least from someone with a linux machine, sorry.
I'll try that.
You have any idea what could have caused the brick?
As i wrote above, moving from KK to LL with wrong parameter "Download" in SPF.
....and a not working recovery.
You should try this method :
darmowyinternet.net/forum/temat-poradnik-jak-uruchomic-uceglony-telefon-po-wgraniu-zlego-romu-test-point_383
unfortunately you have to translate before
Ok i tried that site with google translate and i could a little make up what they are saying.
But that is a very drastically operation, and i would like to give it some other tries before dismantling my phone.
So i googled and googled.. came here: http://forum.xda-developers.com/showthread.php?t=889128
Had enough electronics lying around from my former 27mc hobby, so searched for the right resistors,
cut up a micro usb cable and give it a try... well.. nothing! Tried for about an hour and gave up.
Then i googled on Unbrick Jigs, but for what i read they are only for Samsung phones, so i gues the trick
with the resistors were also?
So googling again... came here: http://forum.xda-developers.com/showthread.php?t=2454004
Reading the tread and the comments, someone mentioned a download for "Mediatek Driver Auto Installer".
Downloaded that and installed the drivers. Plugged in my phone and... whoohoo!! Something is happening! :silly:
My devicemanager saw an "Alcatel single RNDIS interface". I unplugged and plugged my phone a few times to
be sure it was my phone. Sooo... one step further! :good:
Then i googled on this device.. came up with all sorts of network devices, not helpfull. Then googled on Jiayu with
this device. Came up with this tread: https://www.china-devices.com/topic...vcomm-drivers-onto-your-pc-win-7vistaxp-only/
It's a tread about bricked Jiayu G3 devices, but i thought, 'What the heck, lets give it a try!'.
I downloaded the "MTK Megapack - All Tools Here!" and unpacked. Wend back to device manager and manually updated the driver
of the Alcatel device. Show all devices - browse - wend to Megapack map and there were MTK drivers for the 65xx device.
And yess.. when i plug in my phone there's the device: " MTK USB Port (COM7) "
SP Flashtools sees my phone again! :good:
Tried to flash a stock preloader, but got an error: "BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032) – [EMI] Enable DRAM failed!"
But for now that's a problem for tomorrow.. it's almost 2:30 and i have to got some sleep!
(sorry for the misspellings or telling things not clear, i'm tired and english is not my main language)
Grats!
You can google the error. This leds you in the right direction.
It's alive!!!!!! :laugh::silly::victory:
Because the kitkat stockrom i downloaded gave me the same error over and over i searched for something else.
So i downloaded TF Extreme lolipop 5.1 this morning and give it a try. And all went well. I pulled the usb plug and
pushed power button.. only vibration but nothing. Then pulled the battery and after few seconds put it back in
and try power again. Only 1 vibration.. then tried Vol + and - combinations but nothing. (dammn!)
Then plug the usb in and i saw the battery icon.. it was total empty! (because of a week trying).
So now it's charging and i hope it starts, can't wait!!
Thanx all for the effort in helping me out! :good:
Edit: Ok, so i could not wait and hit power! It shows green screen with Jiayu S3 logo and text "New Load". So i guess it's prepairing for first startup!
my s3 basic is not charging when on.. also when connected to pc thru usb, ipc shows device malfunctioning ,and there is no indication on phone..I try to connect to sp flash tool also no success..same error"usb device not recognized pops up every 2s.everything else is fine..Any method to upgrade to 5.1 now on official kk
Kinda need help, happened something similar
It happened something similar to me.
I flashed the whole ROM, bootloader included, I was very sure that my model, Jiayu S3 3GB ROM + 32GB RAM, was the correct, but still bricked my phone.
There's no problem at all when I plug it into my PC, I installed the lastest MTK drivers on windows 10, having to disable the signature enforcement.
The problem comes when I start flashing. I only mark the bootloader, then I press "Download" (on the lastest version of SP Flash Tools), and plug the phone, with the battery in it (I've tried without battery, pressing all possible combinations and does nothing), when I plug it in with the battery and pressing no buttons, the driver is detected as MTK USB Port. That's a good thing I guess. But It does not pass from the red bar, and gives me the known error "Enable DRAM Failed".
I've tried to google any possible solutions, reinstalling other version of the MTK drivers, on different versions of Windows, with other versions of official ROMs, and the result is always the same.
The only thing that's left to try is flashing it with an Ubuntu machine, which is something I do not expertise to be honest, but I'm gonna gather some info and try to do it.
However, if someone has any idea of what I might be doing wrong (excluding the part when I flashed the bootloader, I'll never do it again), I would be really grateful for any kind of help.
Thank you!
Kiei said:
It happened something similar to me.
I flashed the whole ROM, bootloader included, I was very sure that my model, Jiayu S3 3GB ROM + 32GB RAM, was the correct, but still bricked my phone.
There's no problem at all when I plug it into my PC, I installed the lastest MTK drivers on windows 10, having to disable the signature enforcement.
The problem comes when I start flashing. I only mark the bootloader, then I press "Download" (on the lastest version of SP Flash Tools), and plug the phone, with the battery in it (I've tried without battery, pressing all possible combinations and does nothing), when I plug it in with the battery and pressing no buttons, the driver is detected as MTK USB Port. That's a good thing I guess. But It does not pass from the red bar, and gives me the known error "Enable DRAM Failed".
I've tried to google any possible solutions, reinstalling other version of the MTK drivers, on different versions of Windows, with other versions of official ROMs, and the result is always the same.
The only thing that's left to try is flashing it with an Ubuntu machine, which is something I do not expertise to be honest, but I'm gonna gather some info and try to do it.
However, if someone has any idea of what I might be doing wrong (excluding the part when I flashed the bootloader, I'll never do it again), I would be really grateful for any kind of help.
Thank you!
Click to expand...
Click to collapse
Oeps it might be the same problem with the 32GB version as I have.
See http://forum.xda-developers.com/showpost.php?p=68036678&postcount=295
I am waiting for a stock ROM backup.
I have learned to never flash the original preloader again.
xtyphoon said:
Oeps it might be the same problem with the 32GB version as I have.
See http://forum.xda-developers.com/showpost.php?p=68036678&postcount=295
I am waiting for a stock ROM backup.
I have learned to never flash the original preloader again.
Click to expand...
Click to collapse
You're right, with the 32GB rom version (which is still unavaliable for public use) it worked! I still got it here, so anyone feel free to ask me the link too.
Thanks to xtyphoon and Dior DNA and everyone who made this possible, if you ever come to Girona city, I'll buy you a drink ;D
Kiei said:
[...]if you ever come to Girona city[...]
Click to expand...
Click to collapse
I was around there few weeks ago

Note 4 N910C sudden USB Hardbrick, no charge, still booting fine into Android

Hello XDA, my virtual phone heros, i appreciate your good work, i am reading here for a few years as a ghost and today i signed up because i am lost with a serious problem on my Note4 N910C (English is not my native language)
THE CONDITIONS AND ENVIRONMENT:
My Phone was first running on stock Lollipop 5.1.1 when i rooted it over ODIN 3.10.6 with space X kernel and CF Autoroot, SuperSU then i flashed the latest TWRP...
After that i flashed a Custom Rom: Sweet_ROM_V17.1_COJ2_N910C...
Everything was running flawlessly for about 2 weeks...I installed Titanium Backup, Xposed, Xprivacy Pro, Busybox and a lot more and made a complete TWRP Backup then, it was running like a charme...The backup is fine because when i messed up my phone through trying harder xprivacy parameters and other tweaking i needed to set it back by TWRP into the old state...
Nothing happened after that, it was running 100% for over a week of heavy usage...
THE PROBLEM:
The one morning i took it from the charger with 100% Battery and went to work...
Before the error occured I did some searching on the internet, used chats. movies, nothing special this day, USB Debugging was On, i remembered something messed up my chrome browser like this ad hijackers, i set it back by erasing data,cache of chrome in the app menu, then there was nothing else strange i remembered, my AF Firewall was closed, only Whatsapp and Browser were allowed to going through...
The same day in the afternoon i tried to use my car charger to recharge my Note 4 as usual, but this time it wasnt recognizing the charger and my first thought was that the charger is faulty or the cable, so i turned off the phone by the androids power menu...I retried loading my battery In the phones off state but when i plug in the charger, the battery symbol came up for short and then it remained dead, it s the same scenario until today, so i used my powerbank to try charging, because the powerbank has an indicator to show the loading state and everytime i plugged it in, it came up for short, battery symbol shows up for a few seconds, but no percentage or animation is showing as usual and no red LED, then its switching off, the powerbank LED indicator stops the loading state after a few seconds, so the loading current stops...
At home i tried the stock charger and it remained the same, since that, i have to charge the battery outside the phone...
The strange thing is:
The Rom is still booting fine, TWRP is booting, but its not going into download mode from Androids Power Menu like before, its always just rebooting back into android if i choose download mode and i have to take the battery out and back in and hit the download mode pattern Vol- Home Power, to enter Download Mode and even the booting into Download mode from TWRP gives the same strange results:
On my Laptop i started the device manager to see the USB hardware string parameters after a windows popup was telling me something like "Device not recognized"
The USB Driver ID dont fit the old right driver ID, it seems to be empty and the port is not communicating anymore
since the charging bug occured,( Everything worked fine the day before.)
I tried my Laptop to narrow down the bug with the same driver i used for flashing phones (S6,910F,910C) over ODIN and my Lappy has USB 2.0 and USB 3.0 ports.
I always used the same USB 2.0 port for ODIN and other MTP stuff, but since the bug showed up the 910C is not recognized at the USB 2.0 Port anymore, seems to be dead in the devices manager table, only the USB 3.0 Port shows it as unknown device with a strange empty ID --> I tried the other devices like the N910F and G920F that are still recognized by ODIN on the same USB2.0 and 3.0 Ports both with the same USB hardware strings, its just the N910C that isnt recognized anymore, in no mode, no ADB, MTP, no download mode, everywhere the same, USB is bricked! Windows finds no driver and says its no info avaiable on this device so I tried to force the right driver to run with the wrong buggy driver ID but its not communicating, ODIN indicator and log remains unchanged...So it seems to be the same situation like other people getting from killing the bootloader by bad flashing, the only difference is that my phone is still booting fine into recovery and even Android but with no charging. My USB Port is totally useless now, its like if Samsung or Google OTA update has overwritten my bootloader or something hidden in the rom that woke up to kill my mods i dont know and now.
PS: Things i tried so far with no results on fixing my issue....
1. Complete fresh reinstall of Sweetrom, 2. Flashing another kernel...
3. Roll back to my TWRP Backup of perfect running ROM but with no USB support anymore:
The Phone remains in unknown state, not affecting ODIN to switch into flash mode
I am sure its the bootloader, since its battery bug is still occuring while the phone is in off state...
Unable to tell the charger the right ID without USB communication...
i was wondering if there is a solution to make a bootloader hotflash from out of Android or something like getting me back on stock first with download mode, forcing the USB ID or communication with a tool out of android, SD card boot image like on note 3 whatever, please tell me! I cant find something related to my USB and Charging ISSUE
PLEASE HELP ME, I am lost
Still the same. It's booting fine, USB2.0 no reaction on the laptop in Fastboot/Adb/Mtp ... On USB 3.0 Device remains unknown with strange Device ID String in windows 10 hardware Manager... Forced the old formerly working driver, but Odin can't find it anymore... Adb, Mtp, fastboot don't work, no communication... USB Cid is hard bricked, Charging never works in no state, just showing up for a few seconds in off state while plugging it in for short.... Bootloader must be damaged, fastboot and twrp can be started with dead USB... So is there a way to run a boot image to fix my bootloader from SD card, Aroma, or like OTA Updates are flashing? If Samsung and Google apply bootloader updates over OTA and simply restart, why we can't do that??? I need a new bootloader, is there any way without USB?
Greetings,
Thank you for using XDA Assist.
I have moved your question to your device's Q&A forum. You'll receive expert advice here. Good luck!
Fixed!
The problem is the USB Connector Port itself, figured it out after bending the inner contacts up with a flat screwdriver and cleaned them. Before that i always tried the same gently with no change, but please do it at your own risk only. After searching for many hours about possible reasons for the problem, I came to the conclusion to even compromise the Port and heavy bending it up, now it's charging! I will exchange the port soon and change the frame too to have it back like as new... OK, if anyone in the future have problems with the bootloader or USB hardbrick n910c, feel free to ask me, I upgraded my knowledge on many causes now
Thank you very much
My 2cents stick to one charger. Do not share that charger with others.
The worst culprit are the cheap china car chargers.
I went thru two USB ports on my first phone to figure this out.
Ever since I have adopted the policy of using only one cable. Never had this issue.

Need Help with hard brick

Well. First things first. the root of the issue is probably a bad usb port i guess as it's very unstable it even sometimes reboots into download mode on its own when i plug my phone to charge or even gives a Not charging state until i replug it many times then it gives the normal charging (AC) so it's a really messy one.
that's the usual anyway i was rooted and flashed a lollipop rom normally then bugged some apps so i decided to reflash stock kitkat rom however like i said it's a bad usb connection so sometimes the flashing goes slowly and i have to replug the cable for it got smoothly again.
this time i noticed this at 15% and instead of staying in download mode stuck at that the phone rebooted and ofcourse this time only a black screen no download mode no recovery no nothing i guess a typical hard brick? this is my first time dealing with a hard brick so i didn't know what to do at all so i'm still figuring out stuff anyway i installed Qcomm drivers and checked the device manager it's the 9006 one not the 9008 and it shows many drives on my pc (windows 7 64-bit) but no partitions in windows xp 32-bit on another pc and on the laptop it gives no drives i think. i tried with SRK tools it says everything as it should but when it's done i unplug the cable then reboot however still shows many partitions and no download mode.
I don't use my phone alot however i don't own another one so i kinda need help fast please so if anyone has any ideas don't hesitate please.
Thanks in advance.:good:
Update: After following the linux method i now don't have a black screen only stuck on lg logo and still no download mode.
the phone isn't recognized by the pc at all not even 9006 or 9006
the recovery gets stuck at processing and it doesn't say fastboot either on the logo screen.
Croshio said:
Well. First things first. the root of the issue is probably a bad usb port i guess as it's very unstable it even sometimes reboots into download mode on its own when i plug my phone to charge or even gives a Not charging state until i replug it many times then it gives the normal charging (AC) so it's a really messy one.
that's the usual anyway i was rooted and flashed a lollipop rom normally then bugged some apps so i decided to reflash stock kitkat rom however like i said it's a bad usb connection so sometimes the flashing goes slowly and i have to replug the cable for it got smoothly again.
this time i noticed this at 15% and instead of staying in download mode stuck at that the phone rebooted and ofcourse this time only a black screen no download mode no recovery no nothing i guess a typical hard brick? this is my first time dealing with a hard brick so i didn't know what to do at all so i'm still figuring out stuff anyway i installed Qcomm drivers and checked the device manager it's the 9006 one not the 9008 and it shows many drives on my pc (windows 7 64-bit) but no partitions in windows xp 32-bit on another pc and on the laptop it gives no drives i think. i tried with SRK tools it says everything as it should but when it's done i unplug the cable then reboot however still shows many partitions and no download mode.
I don't use my phone alot however i don't own another one so i kinda need help fast please so if anyone has any ideas don't hesitate please.
Thanks in advance.:good:
Update: After following the linux method i now don't have a black screen only stuck on lg logo and still no download mode.
the phone isn't recognized by the pc at all not even 9006 or 9006
the recovery gets stuck at processing and it doesn't say fastboot either on the logo screen.
Click to expand...
Click to collapse
You must have flashed wrong version of the rom .
After trying the linux method, if you cant get into fastboot mode, recovery or not in download mode, then try this : http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
This requires you to open your phone so be cautious .
Thanks I followed that guide. Download mode after. Using the Windows tool instead of Linux then flash tool normally.

No USB connectivity and phone is soft-bricked

Hello everybody, I own an Xperia XC and a couple of months ago I’ve rooted it and I flashed 34.1.A.1.198 firmware, Advanced Stock Kernel and TWRP-recovery. All worked fine, until two weeks ago it lost suddenly the USB connectivity. I tried different USB-cables on different PC’s but neither the phone, nor the PC’s act in any way. Even in fastboot- or flashmode it doesn’t appear in the device manager of the PC’s. I made for a couple of times factory reset, I even changed the phone’s USB charging port with a new one, but nothing changed. I could load the phone only over a power strip with USB-power-supply. I tried to flash the firmware 34.1.A.1.198 again using flashfire (I made a pre-rooted .zip-file with PRFCreator) but now I get a boot-loop. The phone starts till Sony-Logo and after a few seconds it turns off and boots again. Trying to get in recovery mode has no effect (pressing volume up or down and Power-button).
Has anyone any idea, how can I solve this problem? Is there any possibility to make a hard reset without USB-connection?
man why did mess with your phone when you knew you cant use usb connection???
try this: press all buttons and hold them to turn the phone off then try to get access to twrp(or any recovery on your phone) then use a usb type-c flash memory with your phone to flash another zip and hopefully just bring the phone back to life
Kianush said:
man why did mess with your phone when you knew you cant use usb connection???
try this: press all buttons and hold them to turn the phone off then try to get access to twrp(or any recovery on your phone) then use a usb type-c flash memory with your phone to flash another zip and hopefully just bring the phone back to life
Click to expand...
Click to collapse
Thanks for your ansver Kianush, but it seems the phone can't handle any connected devices at the USB-port. Besides of that, when I try to connect it in flash- or fastboot mode, the LED goes green or respectively blue, but none of my PC's doesen't recognize it as a connected device in any way.
I tested the PC connection with an other Xperia XC (my daughter's), it worked without any problems. It was shown in the dewice manager as an "SOMC Flash Device".
It seems like some USB-kernel drivers are lost (?)
I think an option could be using s1tool, but I don't find something for Xperia XC and I don't know yet where the testpoint is for this phone.

Categories

Resources