Related
I have rooted many phones but DO NOT consider myself an expert in any way but after countless hours on the search, I am just STUCK And seriously frustrated. Here is my complicated story.
I was rooted but without a custom ROM. In the progress upgraded to 4.3 OTA. Since then my phone has been on the decline...the WI-FI does not turn on, the GPS is erratic, and now I cannot connect via USB to anything.
I have done everything imaginable and suggested to my PC (WIN8) as well as the phone. I cannot connect via ODIN nor KIES as I cannot get the USB to work.
In ODIN Mode I have:
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD: Yes (1 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: Enable
WARRANTY BIT: 1
BOOTLOADER RP SWREV: 1
I would prefer to downgrade although I have read this is not an option at this point.
to have functional Wi-Fi and USB connectivity would be great to have again.
Please help!!!
Is my phone considered to be SOFT-Bricked?
Try a new cable and/or a different USB port.
Also kies3 is required. The old kies will not connect to any 4.3 or higher android device. Make sure you have the latest drivers as well
Sent from my SCH-I535 using xda app-developers app
---------- Post added at 11:54 AM ---------- Previous post was at 11:51 AM ----------
Also make sure you have USB debugging on. Go to settings and about phone. Tap on the version several timea and it will bring out the developer options.
Sent from my SCH-I535 using xda app-developers app
Go on kies make sure your phone in UNplugged then click connection trouble shoot. Same thing was happening to me on windows 8 so I temporarily went back to 7. It looks like the drivers get messed up if you go from lets say the download mode drivers to the normal drivers. It seemed like every time before I connected my phone I had to do that.
---------- Post added at 02:00 PM ---------- Previous post was at 01:58 PM ----------
Kies 3 does not have the drivers for this phone
ThePagel said:
Go on kies make sure your phone in UNplugged then click connection trouble shoot. Same thing was happening to me on windows 8 so I temporarily went back to 7. It looks like the drivers get messed up if you go from lets say the download mode drivers to the normal drivers. It seemed like every time before I connected my phone I had to do that.
---------- Post added at 02:00 PM ---------- Previous post was at 01:58 PM ----------
Kies 3 does not have the drivers for this phone
Click to expand...
Click to collapse
Thanks for the reply and suggestions.
I have tried three different cables, installed Kies 3, two different computer and multiple ports on both systems with all the phone settings as suggested. I now get the following message when connected to the USB cable: USB Device not recognized. Device malfunctioned and Windows (8) does not recognize it. I have removed all software, reinstalled phone drivers.
Sooo frustrating!
ivndrago said:
Thanks for the reply and suggestions.
I have tried three different cables, installed Kies 3, two different computer and multiple ports on both systems with all the phone settings as suggested. I now get the following message when connected to the USB cable: USB Device not recognized. Device malfunctioned and Windows (8) does not recognize it. I have removed all software, reinstalled phone drivers.
Sooo frustrating!
Click to expand...
Click to collapse
Why do you want to connect to kies? It has 4.1.2 it will always fail the flash for us 4.3 people. Use the Verizon updater or odin. Just a fyi kies will never say it recognizes the phone in downloadmode.
ThePagel said:
Why do you want to connect to kies? It has 4.1.2 it will always fail the flash for us 4.3 people. Use the Verizon updater or odin. Just a fyi kies will never say it recognizes the phone in downloadmode.
Click to expand...
Click to collapse
My problem is I cannot get the computer to recognize the phone. I have tried using the code to get into Qualcomm PhoneUtils but I guess I am not sure if that applies to my model phone. This would allow me to confirm the USB settings (MTB?) of the phone.
At this point, any connection would be a HUGE step forward.
Thanks for your help.
ivndrago said:
My problem is I cannot get the computer to recognize the phone. I have tried using the code to get into Qualcomm PhoneUtils but I guess I am not sure if that applies to my model phone. This would allow me to confirm the USB settings (MTB?) of the phone.
At this point, any connection would be a HUGE step forward.
Thanks for your help.
Click to expand...
Click to collapse
You can boot up the phone to a useable state correct?
ThePagel said:
You can boot up the phone to a useable state correct?
Click to expand...
Click to collapse
Yes, the phone is operational; that is to say it makes and receives calls. The Wi-Fi does not turn on and the GPS is very erratic. I have not found any other problems yet, but I am sure that they must be others....
ivndrago said:
Yes, the phone is operational; that is to say it makes and receives calls. The Wi-Fi does not turn on and the GPS is very erratic. I have not found any other problems yet, but I am sure that they must be others....
Click to expand...
Click to collapse
That sucks at least you can make calls. Hope you figure it out. Maybe it has something to do with your warranty bit.
---------- Post added at 01:11 PM ---------- Previous post was at 01:01 PM ----------
Just one more thought. I know you said you tried everything but did you try a factory reset then on first login when Google asks to import saved data like WiFi settings uncheck the box?
Galaxy S3 on 4.3 with Samsung Custom ** FIXED **
This appears to be the fix to my problems.
http://forum.xda-developers.com/showthread.php?t=2586319
Thanks a ton to ThePagel
Hello peoples
On my htc one s (s4) I did something pretty stupid, as it turned out. I did a factory reset from bootloader. Now its pretty screwed.
Im on Hbot 1.15 and s-on, unlocked with htc's tool. Using TWRP 2,7
My pc wont recognize the handset, it comes up with error, and cant install drivers. The htc standard drivers wont work, nor does htc drivers from "here and there".
adb/fastboot cant find the device in bootloader/fastboot bevause of the drivers issue
In TWRP i cant find "internal_sd" nor "sdcard", and cant mount it to PC either.
So my handset is effectively without ROM, and without any mean to communicate with my pc for adb/fastboot (win8)
If anyone has any suggestions for getting communication between my handset and my PC, and/or get the "internal_sd" to mount, please share.
daABBA said:
Hello peoples
On my htc one s (s4) I did something pretty stupid, as it turned out. I did a factory reset from bootloader. Now its pretty screwed.
Im on Hbot 1.15 and s-on, unlocked with htc's tool. Using TWRP 2,7
My pc wont recognize the handset, it comes up with error, and cant install drivers. The htc standard drivers wont work, nor does htc drivers from "here and there".
adb/fastboot cant find the device in bootloader/fastboot bevause of the drivers issue
In TWRP i cant find "internal_sd" nor "sdcard", and cant mount it to PC either.
So my handset is effectively without ROM, and without any mean to communicate with my pc for adb/fastboot (win8)
If anyone has any suggestions for getting communication between my handset and my PC, and/or get the "internal_sd" to mount, please share.
Click to expand...
Click to collapse
Uninstall all usb drivers / HTC sync.
Then install this drivers --> LINK
LS.xD said:
Uninstall all usb drivers / HTC sync.
Then install this drivers --> LINK
Click to expand...
Click to collapse
Thanks for your reply
Tried uninstalling/reinstalling drivers as you suggested (actually 7th time I tried this..) No luck
Fired up my old laptop with fresh win7 and installed drivers. No luck
In both instances the PC's reports either that its something wrong with the handset, or that they cant find the correct drivers for the handset. Sometimes it comes up with "ville" sometimes not.
Either way neither fastboot or adb can communicate with the handset, (nor can HTC sync).
Is there a way to use the terminal on TWPR to write som magic code to restore what seems to be the reason behind all this: some error code which makes the handset unable to mount the "internal_sd"?
daABBA said:
Thanks for your reply
Tried uninstalling/reinstalling drivers as you suggested (actually 7th time I tried this..) No luck
Fired up my old laptop with fresh win7 and installed drivers. No luck
In both instances the PC's reports either that its something wrong with the handset, or that they cant find the correct drivers for the handset. Sometimes it comes up with "ville" sometimes not.
Either way neither fastboot or adb can communicate with the handset, (nor can HTC sync).
Is there a way to use the terminal on TWPR to write som magic code to restore what seems to be the reason behind all this: some error code which makes the handset unable to mount the "internal_sd"?
Click to expand...
Click to collapse
When it shows up "ville" you have to manually install the drivers.
---------- Post added at 04:24 PM ---------- Previous post was at 04:22 PM ----------
LS.xD said:
When it shows up "ville" you have to manually install the drivers.
Click to expand...
Click to collapse
The way to make your internal_sd usable again is to flash the stock recovery and perform " cöear storage" in bootloader mode. This will only work with stock recovery installed. Means you nead working fastboot to flash it.
LS.xD said:
When it shows up "ville" you have to manually install the drivers.
---------- Post added at 04:24 PM ---------- Previous post was at 04:22 PM ----------
The way to make your internal_sd usable again is to flash the stock recovery and perform " cöear storage" in bootloader mode. This will only work with stock recovery installed. Means you nead working fastboot to flash it.
Click to expand...
Click to collapse
Somehow I got it to work again today. First fastboot suddernly was responding,and eventually adb. Did some more or less random commands and flashed a couple of recoveries back and forth and pushed some different boot.img, then all of a sudden, my phone and my PC started talking again and I could format my internal_sd from PC. From there it was just the usual track
Happy to move my sim from my son's galaxy y back to my fresh cm11 ROM.
(I cant really say what did the trick, maybe connecting an old desire made some magic to my drivers, I dont know.)
Thanks for your efforts to help
Please help me out somebody. Whenever I connect my mate 7 with pc, it shows usb not recognised. Some info :
1. All drivers are fine . Nothing wrong in pc
2. Tried usb debugging on off but no effect.
3. Factory reset the phone. No effect. Currently I am on 4.4..4 firmware with cwm recovery installed.
4. I also got replaced its charging dock port but then also it is no working.
5. Changed usb cable too . no effect.
6. Actually I want to update my phone to 5.0 or 6.0 but for I should be on stock recovery which can only be flashed in fastboot mode . But as usb is not working cant flash it in fastboot mode.
So please tell me is there any way to flash stock recovery without using usb cable ?
Or any otherway I can update my phone to lollipop or marshmallow over kitkat without stock recovery and data cable ?
first phone model?
Sent from my HUAWEI MT7-TL10 using Tapatalk
---------- Post added at 07:01 PM ---------- Previous post was at 07:00 PM ----------
and your computer system operating sytem?in win8or 10 you make unknown device recognize
Sent from my HUAWEI MT7-TL10 using Tapatalk
demirozu69 said:
first phone model?
Sent from my HUAWEI MT7-TL10 using Tapatalk
---------- Post added at 07:01 PM ---------- Previous post was at 07:00 PM ----------
and your computer system operating sytem?in win8or 10 you make unknown device recognize
Sent from my HUAWEI MT7-TL10 using Tapatalk
Click to expand...
Click to collapse
Phone model is - MT7-TL10 international version.
And I have tried it in all os - windows xp, 7, 8 , 10 but in all it shows usb not recognised .
try this in win 8 or win 10:
http://forum.xda-developers.com/galaxy-nexus/general/tutorial-installing-adb-fastboot-t1982718
demirozu69 said:
try this in win 8 or win 10:
http://forum.xda-developers.com/galaxy-nexus/general/tutorial-installing-adb-fastboot-t1982718
Click to expand...
Click to collapse
I already know this thing. but the point is computer is showing usb not recognised not the driver issue. In device manager following message comes in front of my device .
"unknown usb device descriptor failed"
sachinwadhwa46 said:
Please help me out somebody. Whenever I connect my mate 7 with pc, it shows usb not recognised. Some info :
1. All drivers are fine . Nothing wrong in pc
2. Tried usb debugging on off but no effect.
3. Factory reset the phone. No effect. Currently I am on 4.4..4 firmware with cwm recovery installed.
4. I also got replaced its charging dock port but then also it is no working.
5. Changed usb cable too . no effect.
6. Actually I want to update my phone to 5.0 or 6.0 but for I should be on stock recovery which can only be flashed in fastboot mode . But as usb is not working cant flash it in fastboot mode.
So please tell me is there any way to flash stock recovery without using usb cable ?
Or any otherway I can update my phone to lollipop or marshmallow over kitkat without stock recovery and data cable ?
Click to expand...
Click to collapse
i am living same problem ... did you find any way to fix it?
cxc said:
i am living same problem ... did you find any way to fix it?
Click to expand...
Click to collapse
Did your phone charge at very slow rate with official data cable ?
Have you got your battery got replaced since you have buyed the phone ?
sachinwadhwa46 said:
Did your phone charge at very slow rate with official data cable ?
Have you got your battery got replaced since you have buyed the phone ?
Click to expand...
Click to collapse
it taking ~6 hour to charge, i didnt change battery. actually i used cheap charger while couple day then it didnt work when plug the computer. phone still have about 1 year warranty but i am not sure is it my fault or producer.
cxc said:
it taking ~6 hour to charge, i didnt change battery. actually i used cheap charger while couple day then it didnt work when plug the computer. phone still have about 1 year warranty but i am not sure is it my fault or producer.
Click to expand...
Click to collapse
The next big thing happened to me is one day it got off suddenly and after that it nvr got on. On charging only the red battery logo comes with red led blinking and nothing happens even if i leave it charging for whole day.
Then i by passed battery and then connected cable then boot animation comes for a second.
So i doubt it might be faulty battery in our case or a typical hardware issue.
Actually this phone was not released in my country so i have ordered battery and it is arriving within 2 days. And you have btter chance to get the phone rectified by huawei. Also ask them what was the fault , it might help me if battery did not works.
Hi everyone, I am a new person in the forums, so please understand if I'm not good at some stuff and if I'm posting this in the wrong place
Well, story is that I found my old Galaxy Tab 2 in my basement after 3 years, and I got it to turn on (no factory cable, 1€ chinese cable). Android version is 4.0.3.
Found a couple of roms in the forums for 6.0, and yes, I've done it before on my phones.
Computer cannot recognize the tab, only says "Unrecognized device", even though I've tried every driver there is to it. Tried kies, no help. Tried odin, no help.
Neither of those detect the tab either, so I rooted it from the tab itself with KingRoot.
Now the tab is rooted, and I tried to flash TWRP to install 6.0.
It says that the recovery is flashed, but when I try to reboot to recovery, it only restarts, with nothing.
It goes into download mode just perfectly, but when connected to the pc, it still doesn't detect it.
I do not have money to buy a new tablet, so I would really like some advice.
Thanks!
hello
go in download mod ( power & vol+ )
go back to origin
use cfautoroot (all needed in it odin + drivers + cfautoroot)
use a new cable
after that install twrp, os ( first cm12.1 )
regards
Hi, will try!
Don't set auto reboot in Odin.
Once TWRP is flashed wait 1 minute and unplug the tab.
Now directly boot into TWRP, else stock recovery get restored on boot.
You should update over OTA to 4.1 or 4.2 if available first, else you'll have to flash a newer bootloader using Odin to avoid graphics glitches at boot.
Android-Andi said:
Don't set auto reboot in Odin.
Once TWRP is flashed wait 1 minute and unplug the tab.
Now directly boot into TWRP, else stock recovery get restored on boot.
You should update over OTA to 4.1 or 4.2 if available first, else you'll have to flash a newer bootloader using Odin to avoid graphics glitches at boot.
Click to expand...
Click to collapse
Hi, thanks! Got it working!
It was a very good idea to ask xda for help
Can you tell me how you did it? Where to get origin? I have the same problem - please help.
dionex2k said:
Can you tell me how you did it? Where to get origin? I have the same problem - please help.
Click to expand...
Click to collapse
Read above, lol, he quoted it too
I did.... my computer does not even recognize my tab - I tried 3 different cables and 2 different computers.
Use the driver from here http://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
Android-Andi said:
Use the driver from here http://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
Click to expand...
Click to collapse
I installed the drivers from the link you provided - my laptop still does not recognize my tablet... any other suggestions?
dionex2k said:
I installed the drivers from the link you provided - my laptop still does not recognize my tablet... any other suggestions?
Click to expand...
Click to collapse
Tired a different cable? Different usb port?
dionex2k said:
I installed the drivers from the link you provided - my laptop still does not recognize my tablet... any other suggestions?
Click to expand...
Click to collapse
I have heard about a tool called "Forget Windows Use Linux (FWUL)" but I have not tried it. Maybe give it a shot
hello
cfautoroute gives odin, drivers, ...
regards
dionex2k said:
I installed the drivers from the link you provided - my laptop still does not recognize my tablet... any other suggestions?
Click to expand...
Click to collapse
Is your cable a data cable or just a charging cable?
UnavailableSurm said:
Is your cable a data cable or just a charging cable?
Click to expand...
Click to collapse
Yes I tried 3 cables they are for data and charging
---------- Post added at 06:55 PM ---------- Previous post was at 06:53 PM ----------
validatus said:
hello
cfautoroute gives odin, drivers, ...
regards
Click to expand...
Click to collapse
I tried that - did not work.
---------- Post added at 06:55 PM ---------- Previous post was at 06:55 PM ----------
Can someone try and help me via teamviewer? It would make me happy because I really want to use this damn tablet again.
Hi guys,
I have this phone (european dual sim version) and tried to update it via Newflasher. Now the phone doesnt start anymore, it is stuck in bootloop, just says sony and then it says that my phone is corrupt and it will not boot. I dont have enough battery to repair it via Companion. Is there any way to avoid going to the Sony Service?
I should mention that I tried to flash firmware 58.0.A.22.21 Europe Customized EEA. What should I flash to get it to start? Any idea is welcome.
Thank you.
leoking3 said:
Hi guys,
I have this phone (european dual sim version) and tried to update it via Newflasher. Now the phone doesnt start anymore, it is stuck in bootloop, just says sony and then it says that my phone is corrupt and it will not boot. I dont have enough battery to repair it via Companion. Is there any way to avoid going to the Sony Service?
I should mention that I tried to flash firmware 58.0.A.22.21 Europe Customized EEA. What should I flash to get it to start? Any idea is welcome.
Thank you.
Click to expand...
Click to collapse
Can you post a log of what newflasher says when you try to flash the EU rom?
TripodKnight said:
Can you post a log of what newflasher says when you try to flash the EU rom?
Click to expand...
Click to collapse
It flashes, finishes, phone is disconnected, then it doesnt start anymore. Please let me know what log are you talking about and how to get it?
leoking3 said:
It flashes, finishes, phone is disconnected, then it doesnt start anymore. Please let me know what log are you talking about and how to get it?
Click to expand...
Click to collapse
Copy all of the newflasher text into a notepad file and post it here so we can review it.
TripodKnight said:
Copy all of the newflasher text into a notepad file and post it here so we can review it.
Click to expand...
Click to collapse
Oh, ok , sure, in 10 minutes.
leoking3 said:
Oh, ok , sure, in 10 minutes.
Click to expand...
Click to collapse
Please see it attached
leoking3 said:
Please see it attached
Click to expand...
Click to collapse
Do you have ADB installed?
Yes I do
leoking3 said:
Yes I do
Click to expand...
Click to collapse
Try launching your phone into fastboot (plug in while holding volume up, wait for blue light)
Once in fastboot, try setting your active partition to partition a with the command below:
fastboot --set-active=a
The restart your phone and see if it loads.
TripodKnight said:
Try launching your phone into fastboot (plug in while holding volume up, wait for blue light)
Once in fastboot, try setting your active partition to partition a with the command below:
fastboot --set-active=a
The restart your phone and see if it loads.
Click to expand...
Click to collapse
it says: unknown option –set-active=a
leoking3 said:
it says: unknown option –set-active=a
Click to expand...
Click to collapse
This website shows the commands to use:
https://www.androidexplained.com/change-active-partition-slot/
Code:
fastboot --set-active=a
TripodKnight said:
This website shows the commands to use:
https://www.androidexplained.com/change-active-partition-slot/
Code:
fastboot --set-active=a
Click to expand...
Click to collapse
Thank you for being patient, unfortunately the device seems mega fu..ed. I dont know what could have happened sooo important that messed it up like this. I used the correct file,I followed the instructions... It goes to fastboot and it is recongnized by the PC, but the command doesnt work, it gives the response from my previous reply.. It seems that I am doomed to go to the service and that is it. Thank you very much man!
leoking3 said:
Thank you for being patient, unfortunately the device seems mega fu..ed. I dont know what could have happened sooo important that messed it up like this. I used the correct file,I followed the instructions... It goes to fastboot and it is recongnized by the PC, but the command doesnt work, it gives the response from my previous reply.. It seems that I am doomed to go to the service and that is it. Thank you very much man!
Click to expand...
Click to collapse
If your fastboot is not working properly then I agree. But I've never seen a fastboot get corrupted. Can you run any fastboot commands at all?
---------- Post added at 09:21 AM ---------- Previous post was at 09:19 AM ----------
leoking3 said:
Thank you for being patient, unfortunately the device seems mega fu..ed. I dont know what could have happened sooo important that messed it up like this. I used the correct file,I followed the instructions... It goes to fastboot and it is recongnized by the PC, but the command doesnt work, it gives the response from my previous reply.. It seems that I am doomed to go to the service and that is it. Thank you very much man!
Click to expand...
Click to collapse
For your information, I have been dealing with a bootloop the last few days. I have now just tried a new USB cable with a new USB port (not the official Sony cable) and have fixed my issues. Perhaps you could give that a try as well.
TripodKnight said:
If your fastboot is not working properly then I agree. But I've never seen a fastboot get corrupted. Can you run any fastboot commands at all?
---------- Post added at 09:21 AM ---------- Previous post was at 09:19 AM ----------
For your information, I have been dealing with a bootloop the last few days. I have now just tried a new USB cable with a new USB port (not the official Sony cable) and have fixed my issues. Perhaps you could give that a try as well.
Click to expand...
Click to collapse
I used the "fastboot devices" command and it worked, it showed me serial number of the phone. So it seems to be connected. But it doesnt want to change the boot partition. .... As for the cable, I first used a very old usb to usb c cable. Then I used one from my iqos charger. Because my laptop doesnt have a usb C port. So you really think the cable could f..k up things while flashing?? Should I try and find another one in the house maybe and try again?
leoking3 said:
I used the "fastboot devices" command and it worked, it showed me serial number of the phone. So it seems to be connected. But it doesnt want to change the boot partition. .... As for the cable, I first used a very old usb to usb c cable. Then I used one from my iqos charger. Because my laptop doesnt have a usb C port. So you really think the cable could f..k up things while flashing?? Should I try and find another one in the house maybe and try again?
Click to expand...
Click to collapse
Your ADB might be out of date and not have the A/B partition fastboot commands. Try updating through instructions here:
https://developer.android.com/studio/releases/platform-tools
I never thought a USB cable would be the issue either, but I tried a new USB port and quality cable and suddenly everything works fine.
Also confirm you're using newflasher to flash the correct firmware for your model. When I flashed the XQ-AS72 firmware on my XQ-AS52 I experienced bootloops like what you're experiencing.
If you still have issues, you can boot to recovery with these instructions and select "power off". You should be able to charge your phone to 80% to use the xperia companion app. https://www.mobilereset99.com/hard-reset-sony-xperia-1-ii/
TripodKnight said:
If your fastboot is not working properly then I agree. But I've never seen a fastboot get corrupted. Can you run any fastboot commands at all?
---------- Post added at 09:21 AM ---------- Previous post was at 09:19 AM ----------
For your information, I have been dealing with a bootloop the last few days. I have now just tried a new USB cable with a new USB port (not the official Sony cable) and have fixed my issues. Perhaps you could give that a try as well.
Click to expand...
Click to collapse
TripodKnight said:
Your ADB might be out of date and not have the A/B partition fastboot commands. Try updating through instructions here:
https://developer.android.com/studio/releases/platform-tools
I never thought a USB cable would be the issue either, but I tried a new USB port and quality cable and suddenly everything works fine.
Also confirm you're using newflasher to flash the correct firmware for your model. When I flashed the XQ-AS72 firmware on my XQ-AS52 I experienced bootloops like what you're experiencing.
If you still have issues, you can boot to recovery with these instructions and select "power off". You should be able to charge your phone to 80% to use the xperia companion app. https://www.mobilereset99.com/hard-reset-sony-xperia-1-ii/
Click to expand...
Click to collapse
Yes, unfortunately is the correct firmware.
I.will try all these solutions, thank you very very much!
leoking3 said:
it says: unknown option –set-active=a
Click to expand...
Click to collapse
You were right, it was to old to know the command. Now it takes the command but says it is not allowed in lock state
leoking3 said:
You were right, it was to old to know the command. Now it takes the command but says it is not allowed in lock state
Click to expand...
Click to collapse
Give your phone a charge and give the Xperia companion app a try.
If you use the included charger and cable, it will charge faster than it drains even if you leave it in bootloop. But you can also try powering down using recovery options.
Let me know if that works.
TripodKnight said:
Give your phone a charge and give the Xperia companion app a try.
If you use the included charger and cable, it will charge faster than it drains even if you leave it in bootloop. But you can also try powering down using recovery options.
Let me know if that works.
Click to expand...
Click to collapse
The issues is that I cannot enter the Recovery and see the options. So you are sayng that even if when I plug it in it keeps saying my phone is corrupt, it still charges?
leoking3 said:
The issues is that I cannot enter the Recovery and see the options. So you are sayng that even if when I plug it in it keeps saying my phone is corrupt, it still charges?
Click to expand...
Click to collapse
It should charge. You should be able to hold volume down on boot (green light top corner, black screen will happen) and try an xperia companion app restore by following the repair options (select "My device is not detected by computer". It should be charging as it restores from your computer as well.