Hello, this is my first post here and ofcourse I have a problem...
So yesterday I was rooting my Xperia Z, unlocked the debug mode and was able to access the recovery mode a few times. So I flashed my device to 4.2 version with a computer then I copied the 4.2.2 .tft file and the Kernel into my phones internal memory, turned my phone off, turned it on again, turned on the recovery mode, did the "Wipe data/Factory reset", wiped the catche partition, wiped the Dalvik cache, formated the system, formated the data and the cache. So then I went to install the prerooted ROM but my phoned seemed not to find it in the internam memory so I selected to reboot my device and since then it is acting all weird...
So the phone then tried to reboot but freezed at the Sony logo, the battery was about 89% and the phone started heating like it was working on its max, the phones battery died after about 2 or 3 hours, so ofcourse I tried connecting it to my PC to try to charge it but it just started to boot loop, I could hear the computer making a notification sound that the device is connected and after a few seconts it just disconnects. It seems that the phone isnt charging at all because after leaving the phone to charge for the whole night with a regular charger the phones LED was still red and was giving me 3 blinks when I tried to turn the device on. I think that if I could to access the recovery mode again I would be able to fix everything from there on my own...
Any help to fix this problem is welcome, I can provide more information about the problem if there are some questions
P.S. I already tried to remove the microSIM and microSD cards
flash the ftf file you have using flashtool
Richy99 said:
flash the ftf file you have using flashtool
Click to expand...
Click to collapse
I noticed a really weird thing. It looks like it might be both technical and software problem. So earlyer I had the rooted 4.4.2 version but it started to bootloop when I turned on the camera, the device turned off when it was at about 60% battery. So I though to hell with this version and wiped everything again, installed the 4.4 version with flashtool but then the bootlooping started again, it went no further than the Sony logo, after about 2 hours of trying to get the damn thing on I took my fathers Galaxy S4 charger and pluged it into my phone, for my surprise the phone started charging and was displaying that battery icon in the middle of the screen, so now its about at 30% battery and trying to turn it on wont work, almost gets to the main screen and then instantly turns off. Ill try to charge it to about 80% battery and then try to turn it on. I suspect that the device thinks its battery is empty when it is actually at about 60%
FerretXing said:
I noticed a really weird thing. It looks like it might be both technical and software problem. So earlyer I had the rooted 4.4.2 version but it started to bootloop when I turned on the camera, the device turned off when it was at about 60% battery. So I though to hell with this version and wiped everything again, installed the 4.4 version with flashtool but then the bootlooping started again, it went no further than the Sony logo, after about 2 hours of trying to get the damn thing on I took my fathers Galaxy S4 charger and pluged it into my phone, for my surprise the phone started charging and was displaying that battery icon in the middle of the screen, so now its about at 30% battery and trying to turn it on wont work, almost gets to the main screen and then instantly turns off. Ill try to charge it to about 80% battery and then try to turn it on. I suspect that the device thinks its battery is empty when it is actually at about 60%
Click to expand...
Click to collapse
Try flashing 4.3 Stock rom from flashtool
androidtweaker1 said:
Try flashing 4.3 Stock rom from flashtool
Click to expand...
Click to collapse
Still boot looping, when I flashed it into 4.3 and it started up for the first time i got the message "process system isnt responding"
Related
i am currently using the Xperia Z LTE with version .244, LOCKED BOOTLOADER.
After HEAVY flashing with the previous Z1 camera ports and the existanZ roms, my phone shut down randomly. Its getting more shut downs recently, the screen Just blacked and i need to turn on the phone again. I even have problem starting up, example it shuts down immediately during booting up, sometimes during normal usages. I have tried re flashing using flash tool , erasing everything flashing a new firmware, still no luck, using PC companion to repair. I even try NOT to root it, but it still shutdowns, only way to prevent it was to PLUG IN THE POWER WHILE USING.. no shut downs then. After unpluging, the shutdown come back. Anyone has this issue too? Any help?
Maybe your battery is mostly empty, or gets recognized as empty.
This could help you:
Let the phone charge for 24h while it's on. Then flash Stock Rom with PCC or FT.
Sent from my Dualbooted XZ
Tried but still no luck, anyone any more ideas?
finoqq84 said:
i am currently using the Xperia Z LTE with version .244, LOCKED BOOTLOADER.
After HEAVY flashing with the previous Z1 camera ports and the existanZ roms, my phone shut down randomly. Its getting more shut downs recently, the screen Just blacked and i need to turn on the phone again. I even have problem starting up, example it shuts down immediately during booting up, sometimes during normal usages. I have tried re flashing using flash tool , erasing everything flashing a new firmware, still no luck, using PC companion to repair. I even try NOT to root it, but it still shutdowns, only way to prevent it was to PLUG IN THE POWER WHILE USING.. no shut downs then. After unpluging, the shutdown come back. Anyone has this issue too? Any help?
Click to expand...
Click to collapse
battery or the battery circuit problem.
first try with replacing the battery.
Hello!
Earlier, I rooted my new Xperia V and flashed official CM 10.2 (stable). Everything worked fine. Later, I tried a few times the CM11 nightlies. 1-2x I get back to CM10.2 with a previous CWM backup. Yesterday, I changed back to CM10.2 again, after I got a few blue screen reboots with CM11. But after I restored CM10.2, I noticed that I am still getting blue screen reboots with CM10.2 too. :-O I didn't understand it, so I wiped everything, formatted my SD card and tried a full clean install. After the first gapps updates via play store, I got a blue screen reboot again. I was angry and formatted system, data, cache, sdcard0, sdcard1 via CWM and power off. I copied the needed install zips to my SDcard with a card adapter, put it back to my phone and tried to turn on, but nothing happened at all. I also tried to connect to my PC and start in fastboot, but the blue LED also did not come and nothing happened. Totally dark everything, even after some minutes with removed battery. Only I get a blinking red LED when I remove the battery and connect to the charger (which stops, when I am pushing the power button), but apart from this, completely nothing. (( I am really scared now, help somebody. :$$$
Best regards,
Zalan
EDIT: sorry, DUPLICATE - http://forum.xda-developers.com/showthread.php?t=2572334
banciii said:
Hello!
Earlier, I rooted my new Xperia V and flashed official CM 10.2 (stable). Everything worked fine. Later, I tried a few times the CM11 nightlies. 1-2x I get back to CM10.2 with a previous CWM backup. Yesterday, I changed back to CM10.2 again, after I got a few blue screen reboots with CM11. But after I restored CM10.2, I noticed that I am still getting blue screen reboots with CM10.2 too. :-O I didn't understand it, so I wiped everything, formatted my SD card and tried a full clean install. After the first gapps updates via play store, I got a blue screen reboot again. I was angry and formatted system, data, cache, sdcard0, sdcard1 via CWM and power off. I copied the needed install zips to my SDcard with a card adapter, put it back to my phone and tried to turn on, but nothing happened at all. I also tried to connect to my PC and start in fastboot, but the blue LED also did not come and nothing happened. Totally dark everything, even after some minutes with removed battery. Only I get a blinking red LED when I remove the battery and connect to the charger (which stops, when I am pushing the power button), but apart from this, completely nothing. (( I am really scared now, help somebody. :$$$
Best regards,
Zalan
Click to expand...
Click to collapse
Does your pc recognize it in flashmode? If so, flash the kernel from your cm10.2 via flashtool
St.Jimmy90 said:
Does your pc recognize it in flashmode? If so, flash the kernel from your cm10.2 via flashtool
Click to expand...
Click to collapse
No, it doesn't recognize my device in any mode. I tried simple connect, volume up push connect, volume down push connect, but nothing at all.
Same as me. Only red LED blinking (the normal one does not, it's can enter to fastboot even if not on the battery).
Hope you find the solution soon.
Atm, I am checking this guide: http://forum.xda-developers.com/showthread.php?t=1849170
I hope I can find something, somewhere... :SSS
Try this maybe
Open up flashtool.
Hold vol down and plug in
Leave it plugged for a while(a couple of minutes) with red LED blinking.
see if it changes into green or blue ( last time it changed into green for me
then if it has changed flash stock ftf.
if nothing happens take the battery off and try again.
Something similar happened to me last time, send it to fix and lost warranty....fixed it myself after it was back
Allen Hu said:
Try this maybe
Open up flashtool.
Hold vol down and plug in
Leave it plugged for a while(a couple of minutes) with red LED blinking.
see if it changes into green or blue ( last time it changed into green for me
then if it has changed flash stock ftf.
if nothing happens take the battery off and try again.
Something similar happened to me last time, send it to fix and lost warranty....fixed it myself after it was back
Click to expand...
Click to collapse
No LED blinking or any other LED actions at all. Flashtool or my PC doesn't recognize the phone at all.
edit: it blinks (red) only if I connect to the charger or the PC with removed battery
Too Bad... couldn't help you...
It may be a faulty battery. Your simptoms are pointing to that. What about leave it to charge for 12 hours?
Sent from my LT30p using xda app-developers app
Moon_Fire said:
It may be a faulty battery. Your simptoms are pointing to that. What about leave it to charge for 12 hours?
Sent from my LT30p using xda app-developers app
Click to expand...
Click to collapse
Nothing helped. The problem was that I formatted every /partition on the phone, so there was nothing to start. The service could not fix my phone in 3 months, so finally they give me a new one with 70% discount because of the long waiting time. (No warranty because of the root ofc.)
Hey everyone:
HTC One M7 (AT&T variant). Unlocked bootloader & s-off. TWRP 2.7.0.0. HBoot 1.44.
I had Maximus 30.00 ROM on my phone up until last night. Then I downloaded Whats app plus on a questionable site application; it looked like it was taking forever to finish; so I went ahead and restarted the phone. That was a bad mistake.
The phone started boot looping. I tried in vane to reinstall the same ROM and then whatever ROM. It turned out the /data/ partition was corrupted. So I reformatted it with mkfs4 thanks to these instructions. Then I was able to install Maximus 40.00 and got the phone unbricked (yay). But I found two problems:
1) The phone battery wouldn't charge past 77%... nor did it seem to discharge.
2) The phone battery wouldn't charge when I first turned the phone off. The amber LED light would just hold constant.
I tried running that ROM with elementx kernel with no results. So I installed the latest version of this ROM (Android Revolution 71.0) with a full wipe of everything. /data/system/cache/dalvik cache etc. Still had both problems.
Then I tried installing ElementX kernel (with the fast charging option checked) with this ROM which led to the second problem going away. However the first problem still exists. I also tried clearing battery stats with no effect. Also tried doing a fastboot erase cache with no effect.
I'm not sure if the battery is really at 77%; but I have turned off the phone and am watching it charge with the same charger I've always had that charged it to 100% before... but its been going for 15-20 minutes without going up one percentage.
Any idea how I can try to get rid of this quite annoying problem? Thanks very much in advance! I would be happy to provide any additional information you might need.
Hi, i own a sony xperia sp and have a big problem: my phone works perfectly only when connected to usb or charge.
When the phone is off and i try to turn it up it will boot to OS only if the battery is at 100%. if it's not 100% the phone will try to boot but will crash at some point.
but as said before if i power it up while connected to usb or charge the phone will boot normally and will work fine. by the way even if i can boot, when i disconnect the cable the phone will crash and shut down after some time.
i' ve checked the battery status and it says Good, no need to replace it. uAh: 2367000.
i've tried to wipe data, upgrade\downgrade firmware but nothing worked.
May someone help me with this?
johnnyjjohnson said:
Hi, i own a sony xperia sp and have a big problem: my phone works perfectly only when connected to usb or charge.
When the phone is off and i try to turn it up it will boot to OS only if the battery is at 100%. if it's not 100% the phone will try to boot but will crash at some point.
but as said before if i power it up while connected to usb or charge the phone will boot normally and will work fine. by the way even if i can boot, when i disconnect the cable the phone will crash and shut down after some time.
i' ve checked the battery status and it says Good, no need to replace it. uAh: 2367000.
i've tried to wipe data, upgrade\downgrade firmware but nothing worked.
May someone help me with this?
Click to expand...
Click to collapse
My guess : Kernel problem if its not a kernel thing then your hardware has problems
Dear all,
I have a Samsung Galaxy Tab S2 8.0 WIFI purchased last year (exactly to the day) in Cali. I believe it came with 5.1.1 XAR version.
A month later, my troubles began. I flashed with 6.0 Samsung WIFI ROM from some other country and the tab soon started to randomly turn off while being used. I am not sure if this is coincidental or not. When restarted, it would sometime fully boot, only to turn off while doing any mundane task surfing etc. and at other times, start and turn off as soon as the SAMSUNG logo comes. Weirdly, when I wait a day or two, it would start fully and work for a few minutes to half an hour
When I put it to charge, only rarely does the green battery logo came up, but most frequently I got a flashing thunderbolt sign.
I sent it to Samsung and it came back apparently with the correct firmware installed and the repair note said, faulty data cable replaced. But in a week of usage, the same problems started. I don't live in the US currently and so I don't have local warranty and don't have any means to send it back to Samsung USA. I've tried all remedies I could find, charging it to 100%, holding volume down and power for 15-30 seconds to simulate a battery reset, etc. to no avail. These days. it wouldn't even stay on long enough to access recovery mode, before turning off.
Yesterday, I installed Nougat 7.0 ROM from XAR on it and tried to start it. same problem. It says updating applications xx out of 26, and then turn off. When I try to access recovery, I got the android logo and when it gets to "Erasing", it would turn off. Then now that the warranty has expired, I installed TWRP (twrp_3.1.0-1_sm-t710_13317.tar) and this time I somehow goto to TWRP recovery mode, I just left it on there to see how long it would last, instead of immediately erasing the caches and restarting.
After that once, I couldn't get it to stay on long enough to access recovery. So I tried to go back to OEM ROM using Smart Switch, but to no avail once again. The Download mode still says Custom even after Smart Switch emergency recovery
I have tried flashing various other things (5.1.1 Samsung ROM, 6.0 ROM from UK with AP, BL and CSC files, TWRP 5.1.1 permissive ROM, TWRP), in various jumbled orde,r out of frustration. Nothing worked. here's a list of ROMs I've tried:
T710XXU2DQCL_T710UVS2DQC1_EON
SM-T710_1_20170406180713_vd28gnex7t_fac
SM-T710_1_20170330211239_qkurg70e9y
5.1.1_T710XXU1BOH7_T710XAR1BOH7_XAR
twrp_2.8.7.1_LL_5.1.1_t710
twrp_3.1.0-1_sm-t710_13317
t710_5.1.1_boot
Right now, the only thing I can access is Download mode and it says Current Binary: Custom, System Status: Custom, AP SWREV B:2 K:0 S:0 and worse than before, the tab turns off at the Powered by Android logo and when I plug it in, it doesn't charge but I get this boot loop (with the just the powered by android screen flashing)
would it help to re-partition and nand erase all and install a fresh ROM with a PIT file, if so can someone please share me their PIT file for this model??
I am out of ideas, and ready to break this expensive brick
appreciate any help,
thanks
V
vvsarana said:
Dear all,
I have a Samsung Galaxy Tab S2 8.0 WIFI purchased last year (exactly to the day) in Cali. I believe it came with 5.1.1 XAR version.
A month later, my troubles began. I flashed with 6.0 Samsung WIFI ROM from some other country and the tab soon started to randomly turn off while being used. I am not sure if this is coincidental or not. When restarted, it would sometime fully boot, only to turn off while doing any mundane task surfing etc. and at other times, start and turn off as soon as the SAMSUNG logo comes. Weirdly, when I wait a day or two, it would start fully and work for a few minutes to half an hour
When I put it to charge, only rarely does the green battery logo came up, but most frequently I got a flashing thunderbolt sign.
I sent it to Samsung and it came back apparently with the correct firmware installed and the repair note said, faulty data cable replaced. But in a week of usage, the same problems started. I don't live in the US currently and so I don't have local warranty and don't have any means to send it back to Samsung USA. I've tried all remedies I could find, charging it to 100%, holding volume down and power for 15-30 seconds to simulate a battery reset, etc. to no avail. These days. it wouldn't even stay on long enough to access recovery mode, before turning off.
Yesterday, I installed Nougat 7.0 ROM from XAR on it and tried to start it. same problem. It says updating applications xx out of 26, and then turn off. When I try to access recovery, I got the android logo and when it gets to "Erasing", it would turn off. Then now that the warranty has expired, I installed TWRP (twrp_3.1.0-1_sm-t710_13317.tar) and this time I somehow goto to TWRP recovery mode, I just left it on there to see how long it would last, instead of immediately erasing the caches and restarting.
After that once, I couldn't get it to stay on long enough to access recovery. So I tried to go back to OEM ROM using Smart Switch, but to no avail once again. The Download mode still says Custom even after Smart Switch emergency recovery
I have tried flashing various other things (5.1.1 Samsung ROM, 6.0 ROM from UK with AP, BL and CSC files, TWRP 5.1.1 permissive ROM, TWRP), in various jumbled orde,r out of frustration. Nothing worked. here's a list of ROMs I've tried:
T710XXU2DQCL_T710UVS2DQC1_EON
SM-T710_1_20170406180713_vd28gnex7t_fac
SM-T710_1_20170330211239_qkurg70e9y
5.1.1_T710XXU1BOH7_T710XAR1BOH7_XAR
twrp_2.8.7.1_LL_5.1.1_t710
twrp_3.1.0-1_sm-t710_13317
t710_5.1.1_boot
Right now, the only thing I can access is Download mode and it says Current Binary: Custom, System Status: Custom, AP SWREV B:2 K:0 S:0 and worse than before, the tab turns off at the Powered by Android logo and when I plug it in, it doesn't charge but I get this boot loop (with the just the powered by android screen flashing)
would it help to re-partition and nand erase all and install a fresh ROM with a PIT file, if so can someone please share me their PIT file for this model??
I am out of ideas, and ready to break this expensive brick
appreciate any help,
thanks
V
Click to expand...
Click to collapse
Well i hve the same problem like you.. idk wht should i do with this condition.. bootloop.. always restart until logo.. :crying:
Please anyone help to solve our problem..
Your issue seems related to power. It seems your device doesn't charge correctly and is turning off due to running out of battery.
What does TWRP report as the charge state?
Do you get the same issue when the device is plugged in to the mains?
ashyx said:
Your issue seems related to power. It seems your device doesn't charge correctly and is turning off due to running out of battery.
What does TWRP report as the charge state?
Do you get the same issue when the device is plugged in to the mains?
Click to expand...
Click to collapse
hi ashyx, I am pretty sure that battery isn't the issue here. even though the grey battery logo with a thunderbolt flashes while turned off and plugged in for charging, after a while it does charge anyhow. I can get it to 100%. Plugging in makes no difference.
I am thinking it could be a power button problem or a faulty usb port perhaps, if it is indeed a hardware fault?
vvsarana said:
hi ashyx, I am pretty sure that battery isn't the issue here. even though the grey battery logo with a thunderbolt flashes while turned off and plugged in for charging, after a while it does charge anyhow. I can get it to 100%. Plugging in makes no difference.
I am thinking it could be a power button problem or a faulty usb port perhaps, if it is indeed a hardware fault?
Click to expand...
Click to collapse
Did you ever resolved this issue? Curious if you have a solution.