Related
Please post here if your i780 was bricked.
1)Symptoms before brick
2)Name of firmware (PDA/Phone)
3)Kind of repair after.
Thank you for helping community to figure out how to avoid this future
28/01/2010 SOLUTION:
If you have suddenly (or) after flashing of new ROM strange things:
read this post.
i have one bricked i780
hi heniken78,my bricked i780 as follow
1.when flash your 28008 rom dated 13.12.09,it cann't get into desktop suceesefully,and system goes very slow
2.firmware is PDXIB1
3.noway,because i cann't get in bootloader.even plug in charge cable,the led couldn't light on.
sunnyjiang said:
hi heniken78,my bricked i780 as follow
1.when flash your 28008 rom dated 13.12.09,it cann't get into desktop suceesefully,and system goes very slow
2.firmware is PDXIB1
3.noway,because i cann't get in bootloader.even plug in charge cable,the led couldn't light on.
Click to expand...
Click to collapse
have you tried hardreset(red+green+power) or emergency(b/w+enter)mode?
might you can solve this way =)
hashtowent said:
have you tried hardreset(red+green+power) or emergency(b/w+enter)mode?
might you can solve this way =)
Click to expand...
Click to collapse
No when led is not on anymore- you cant get in bootloader.
heineken78 said:
Please post here if your i780 was bricked.
1)Symptoms before brick
2)Name of firmware (PDA/Phone)
3)Kind of repair after.
Thank you for helping community to figure out this BLACK future.
Click to expand...
Click to collapse
My phone was bricked two times
1) The phone rest stuck to Samsung screen when I open it
2) PDXIB1
3) Samsung Center changed the motherboard of the phone
Symptoms:
Every application will respond with message: Application is not signed or missing components (or something else). Only soft reset worked - but phone did a hard reset every time. Sometimes after hard reset contacts stayed as it was (everything else was deleted). These troubles last for 3 days for me until my phone died. Board is damaged and repair will cost 310,- €.
ROM version:
28205 @96 DPI made by ironeagle
Repair:
To buy a new board and a new battery (cause the old one has been damaged too - or just use a second battery instead).
how to execute emergency mode
hashtowent said:
have you tried hardreset(red+green+power) or emergency(b/w+enter)mode?
might you can solve this way =)
Click to expand...
Click to collapse
i donn't know how to getin emergency mode,can you explain what i should to do
emergency mode is the mode u use when u flash a new rom
fn+enter+power(5 seconds).
Anyway, when my device bricked...it was almost 6 months back.
I used quite a bit of wifi, and left my device on the charger with wifi on accidentally. When i woke up a couple hrs later...the device seemed like it was in standby charging. Pulled off the charger, but the charging LED was still glowing! Device didnt respond to anything, pulled the battery out and put it back in....and boom! went totally dead...tried different batteries, tried soft reset, format mode, emergency mode...nothing. no sign of life!
mobo had to be replaced....got it done free as it was just abt 15 days old when this happened
I think its more of a hardware fault....some units being faulty waiting to blow in your face!
Just spoke to Samsung service about bricked phones: From their experience they have changed mobo only once, when 780 wasnt charging, but was working.
But they told that in case of fault of bootloader - thay DONT restore it, just replacing motherboard!
So there is chance to repair you phone by JTAG tool.
I hope trizzio that helps.
heineken78 said:
Just spoke to Samsung service about bricked phones: From their experience they have changed mobo only once, when 780 wasnt charging, but was working.
But they told that in case of fault of bootloader - thay DONT restore it, just replacing motherboard!
So there is chance to repair you phone by JTAG tool.
I hope trizzio that helps.
Click to expand...
Click to collapse
hey dude - where could I get that JTAG tool?
trizzo said:
hey dude - where could I get that JTAG tool?
Click to expand...
Click to collapse
Dude I advise you to visit http://www.omnia-repair.com/ and ask on forum if someone can do this for you. Tool is about 300 EUR and Omnia is top brick phone, so you should find services that already have it, it does support i780.
tip: use google search for more options.
Hey guys,
my phone was bricked: I'd flashed heineken's "i780 WM 6.5.3 ver.28205 DPI 96" rom. After two days some errors appeared and I flashed (&hardreset) the rom again. While connecting to ActiveSync the connection was broken after some minutes. Then I have disconnected the USB-Cable and the phone was frozen. No reaction. No hard-reset keys, no LED reaction while power-connector.
So... I'm not shure whether this problem is because of heineken's rom. But the good news are: Samsung support switched the motherboard because of 24month guarantee
SAM-123 said:
Hey guys,
my phone was bricked: I'd flashed heineken's "i780 WM 6.5.3 ver.28205 DPI 96" rom. After two days some errors appeared and I flashed (&hardreset) the rom again. While connecting to ActiveSync the connection was broken after some minutes. Then I have disconnected the USB-Cable and the phone was frozen. No reaction. No hard-reset keys, no LED reaction while power-connector.
So... I'm not shure whether this problem is because of heineken's rom. But the good news are: Samsung support switched the motherboard because of 24month guarantee
Click to expand...
Click to collapse
Im sorry SAM.
This first version was really weird, I have changed algorythms of compile again in version 2.
But there is always way when you get starnge glitches before you get brick - to flash offical rom to avoid a brick.
As for me I never had any of symptoms..flashed 1001 time.
About bricks...
I have experienced described situations (sudden out of memory, unable to run any app becouse of errors, dissapearing data and so on) around ten times during my cooking/flashing adventures, with different ROMs from different developers. Sometimes at the begining, when weird behaviors of my i780 started, I tried flashing device with other unoficial images, but problems remained. I think I even posted about my problem somewhere...
And I could always recover my device doing one simple thing.
Flashing official PDXIB1.
But important thing is that YOU SHOULD USE OFFICIAL UPDATER from Samsung site (in my case Vista version), not a .bin under Mirage!!
I know it is stupid, but it works better (and if something looks stupid and works better, then it is not stupid any more; Murphy`s law)
In my case Mirage not always proved to be a sollution.
SO every time when that situation emerge, thats what I would do very quick:
1. Hard reset.
2. Flashing oficial Samsung Updater (tutorial on Samsung site)
About reasons bricks happens; I have found no pattern. It happens with WM6, WM6.1 and WM6.5 or WM6.5.x. Sometimes one and the same ROM works perfect two weeks and flashed next time generates bricks.
As someone noticed previously, it is probobly a hardware-software problem, some kind of memory /filesystem/ FAT? damage and it is possible to revert that by flashing official ROM..
I am not a computer scientist, but thats only pattern/mark I can see..
Hey guys,
I have a very annoying and reproducible problem with my Desire. Everytime I connect the phone via USB (no matter if dock, laptop, wall) it reboots ~2 seconds after removing the USB cable from the phone.
I have had this problem for about 2 weeks now, across 4 or 5 Custom Roms (Sense and Non-Sense) and right now I am on CM6.1 Nightly 214.
It just annoys the crap out of me, for example when I got the Desire in the dock next to my desk and I receive a call, I can only accept the call handsfree, because removing it from the dock would cause a reboot and I would lose the call...
Please give me some kinda advice, I just flashed the latest radio and it worked twice without rebooting and now I'm back to square 1.
All the best,
Paul
Sounds like a faulty battery or some kind of defect at the power supply.
I suggest you try this with another battery, maybe from a friend.
You should check the usb connector on the phone too for some sort of deformation or smudge.
I thought that it could be the usb cable you are using, but since it does the same with the dock, it's not it.
The easiest and the most not likely way to fix it is with the calibration of the battery, if you have luck maybe it's just the OS that errs.
Thanks for your thoughts on my problem. Right now I am waiting for an important call but I got a spare battery from a friend of mine already and will later check and see if the problem occurs with the spare battery as well.
But the other point you mentioned was a calibration of the battery: how exactly do I do that? Just AmonRA Wipe Battery Stats or are you talking about another method?
Cheers for the advice!
this is for the calibration of your battery.
http://forum.xda-developers.com/showthread.php?t=755903
Hi, hope it works with the other battery, otherwise you'll have to send it for repair.
The battery thing I mentioned, has a minimal chance of working, but at least when I am desperate I try things that have even the smallest chance of fixing it. So in essence the process is: charge untill full when powered on; disconnect charger (which will automatically reboot your phone in your case);
don't let it boot, enter hboot for example and turn it off; then charge till full again; now boot into recovery wipe stats; and finally just boot into android.
Another thing worth checking I think is the pins where the battery connects to the phone, they should look clean (I wipe pins with rubber for a pencil) and intact.
Edit:Well seems like Marios already posted a link but mine is specific for your situation
did you solve the problem?
i have the same thing... very strange.
calibrating the battery didn't help.
No, I still haven't found a solution. Strangely though, it doesn't reboot anymore if I charge it via USB on my laptop. On my desktop and via the wall charger it still reboots every time I unplug it. Sorry I can't be of more help
my phone reboots when disconnecting from my laptop too.
even when in recovery, very strange...
have you tried to try the unbricking process with the misc.img?
Actually, I haven't tried that one. Can you give me a link to what you're talking about?
IT WORKED!
http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/
just flashed the update.zip and i can copy the files to/from my laptop using the usb cable.
and it doesn't reboot when unpluging too
Got the same issue, tried modaco´s workaround, same thing... it started happening after i flashed CWM3.0x wich reovery do u use?
gonna try flashing Ra again and see what happens....
Solved It
Like i said, happened after flashing cw3.x finnaly i got home, flashed RA-desire-v2.0.0-CM again, then flashed update.zip from modaco´s thread, and for now it stoped....
just gonna see what happens when the battery get fully charged....
EDIT: Fully charged 4192mV removed it, and.... nothing happened...
Unfortunately it didn't work for me. Now my phone freezes every now and then when I unplug it
EDIT: IT WORKED, IT WORKED!!!
congrats
powlemann said:
Unfortunately it didn't work for me. Now my phone freezes every now and then when I unplug it
EDIT: IT WORKED, IT WORKED!!!
Click to expand...
Click to collapse
NICE....
How did u solved it, u never know.....
I tried all things listed in this thread and some more, too.
But, it still reboots when removing from power supply (pc connection works now).
Perhaps you tried some things not listed here?
I am not sure when the problem started for me.
I installed cm7 nightlies with no reboot-problem, also switched from alpharev1.5 to alpharev1.8 and from cwm2 to cwm3.
All in a few days.
Somewhere along these days the problem appeared.
Btw.:
I got reboots on both kinds of usb connections (PC/power supply).
Debugging connection (adb, fastboot) worked.
Accessing the phone as usb storage device worked, too.
So this may be a little bit different from the cases described in the thread.
To solve the issue, I tried several things:
First I restored older backups (versions of cm7) with no success.
Then I restored my last backup of cm6 nightly from just before cm7, and it didn't work either.
As I was 100% sure that this worked before, I now concentrated on the remaining parts, recovery and boot loader.
So I first tried downgrading to clockworkmod2.
Then I tried updating to a newer alpharev1.8 (as it was a little bit newer than my installed version).
After finding this thread, I became a little happier again...
I applied the fastboot oem ... thingy (hmm, what does it do exactly?).
Then I calibrated my battery, which seemed to work well, as it shows 99% now, which it didn't before.
And at the end I installed the fixmisc-update.zip as linked above.
Between each step I checked if the issue disappeared.
Nothing of those steps completely solved the problem.
However, when disconnecting from PC, the reboots don't appear anymore, so at least something has changed.
So, powlemann, ferreinf and others being successful with the steps above, which configurations do you use now?
Can you tell me which change solved the issue for you?
Do you use alpharev1.5 or 1.8 (and the later from which date) or none of them?
Did you install cwm3 again after solving the problem and did the problem re-appear?
Good News for you, hg42!
I am 99% sure you can fix the problem when first flashing AmonRA recovery and then do Mocados Usb Brick rickrolled.
Do you know how to flash a different recovery?
I fixed it with modaco's zip, that was very annoying!!
Hello.
This my first thread. I have done some reading, but I can't find a similar problem, so I really hope that this is posted in the correct location...
I have an odd problem with my phone. I did a flash a few months ago, and I also (attempted to) update the modem and bootloader. After the reboot, I had to begin pulling the battery to get the phone to power back on after the power was off or after a restart. I've replaced the battery, charger, and installed SEVERAL new roms, but the problem persists. I don't know if I need to do something else, or if the phone is damaged...
But if it IS a programming problem, and not physical damage, then here's the real problem...
I have installed the latest version of CWM. I am running CM 11 with Kitkat 4.4.2. I would like to just flash the stock rom and see if that fixes it, but I have read that once you are running a 4.3 or beyond bootloader, you WILL brick your phone if you try to downgrade. So that stops that.
Another issue is that if I try to install a different/newer bootloader in CWM, it fails every time. I also cannot flash another version of CWM or TWRP. About halfway through the process, Odin says it has failed, no matter what version of Odin, CWM, or TWRP I am using.
So the short version of this is, based on what I've listed, how do I fix this rebooting issue?
I know that this is a long post, but I'm trying not to leave anything out. If anyone has any ideas, please feel free to let me know.
Thank you in advance
biga72112 said:
Hello.
This my first thread. I have done some reading, but I can't find a similar problem, so I really hope that this is posted in the correct location...
I have an odd problem with my phone. I did a flash a few months ago, and I also (attempted to) update the modem and bootloader. After the reboot, I had to begin pulling the battery to get the phone to power back on after the power was off or after a restart. I've replaced the battery, charger, and installed SEVERAL new roms, but the problem persists. I don't know if I need to do something else, or if the phone is damaged...
But if it IS a programming problem, and not physical damage, then here's the real problem...
I have installed the latest version of CWM. I am running CM 11 with Kitkat 4.4.2. I would like to just flash the stock rom and see if that fixes it, but I have read that once you are running a 4.3 or beyond bootloader, you WILL brick your phone if you try to downgrade. So that stops that.
Another issue is that if I try to install a different/newer bootloader in CWM, it fails every time. I also cannot flash another version of CWM or TWRP. About halfway through the process, Odin says it has failed, no matter what version of Odin, CWM, or TWRP I am using.
So the short version of this is, based on what I've listed, how do I fix this rebooting issue?
I know that this is a long post, but I'm trying not to leave anything out. If anyone has any ideas, please feel free to let me know.
Thank you in advance
Click to expand...
Click to collapse
Edit: --> I was able to install TWRP using Mobile Odin. Now I'm going to change the bootloader and see if that fixes the problem.
biga72112 said:
Hello.
This my first thread. I have done some reading, but I can't find a similar problem, so I really hope that this is posted in the correct location...
I have an odd problem with my phone. I did a flash a few months ago, and I also (attempted to) update the modem and bootloader. After the reboot, I had to begin pulling the battery to get the phone to power back on after the power was off or after a restart. I've replaced the battery, charger, and installed SEVERAL new roms, but the problem persists. I don't know if I need to do something else, or if the phone is damaged...
But if it IS a programming problem, and not physical damage, then here's the real problem...
I have installed the latest version of CWM. I am running CM 11 with Kitkat 4.4.2. I would like to just flash the stock rom and see if that fixes it, but I have read that once you are running a 4.3 or beyond bootloader, you WILL brick your phone if you try to downgrade. So that stops that.
Another issue is that if I try to install a different/newer bootloader in CWM, it fails every time. I also cannot flash another version of CWM or TWRP. About halfway through the process, Odin says it has failed, no matter what version of Odin, CWM, or TWRP I am using.
So the short version of this is, based on what I've listed, how do I fix this rebooting issue?
I know that this is a long post, but I'm trying not to leave anything out. If anyone has any ideas, please feel free to let me know.
Thank you in advance
Click to expand...
Click to collapse
If the phone powers on itself immediately the battery is replaced, i.e. without you having to press the power button, chances are 99% you have a stuck power button problem. It's not uncommon with this device and can be routinely fixed at any repair shop or by DIY if you have the right tools and technical resources.
If the phone is working OK (other than the booting issue), I'd stay off flashing bootloaders to avoid bricking
Larry2999 said:
If the phone is working OK (other than the booting issue), I'd stay off flashing bootloaders to avoid bricking
Click to expand...
Click to collapse
Thank you very much for the reply!
No its not a power button issue. I DO have to hold the power button to power on. Here's what happens when the restart fails...
I have to:
1) pull the battery
2) sometimes, I have to hold the power button WITHOUT the battery in for a few seconds (I've had laptops that have this issue before. I think it's a static buildup of some sort.)
3) reinsert the battery
4) hold the power button, and
5) if I'm lucky, the phone will boot up.
This is only about 50% successful. Sometimes I have to do this 3-4 times.
Now, I don't know if this is a hardware issue, or a firmware/software issue. If it IS a hardware problem, then I may just replace the phone. If it's a firmware/software problem, then hopefully it can be fixed. If it's a problem with the bootloader, and a fix isn't possible, then I'll just keep on truckin' till I get a new phone.
biga72112 said:
Thank you very much for the reply!
No its not a power button issue. I DO have to hold the power button to power on. Here's what happens when the restart fails...
I have to:
1) pull the battery
2) sometimes, I have to hold the power button WITHOUT the battery in for a few seconds (I've had laptops that have this issue before. I think it's a static buildup of some sort.)
3) reinsert the battery
4) hold the power button, and
5) if I'm lucky, the phone will boot up.
This is only about 50% successful. Sometimes I have to do this 3-4 times.
Now, I don't know if this is a hardware issue, or a firmware/software issue. If it IS a hardware problem, then I may just replace the phone. If it's a firmware/software problem, then hopefully it can be fixed. If it's a problem with the bootloader, and a fix isn't possible, then I'll just keep on truckin' till I get a new phone.
Click to expand...
Click to collapse
It's almost certainly an hardware issue. Very unlikely a firmware problem would cause this and even more likely the bootloader would. With a bootloader issue, your phone likely wouldn't even boot at all. Power button problems present in several ways and a loose power button could cause the kind of issues you've described. I'd take it to a local tech shop for a quick look before giving up on it.
Larry2999 said:
It's almost certainly an hardware issue. Very unlikely a firmware problem would cause this and even more likely the bootloader would. With a bootloader issue, your phone likely wouldn't even boot at all. Power button problems present in several ways and a loose power button could cause the kind of issues you've described. I'd take it to a local tech shop for a quick look before giving up on it.
Click to expand...
Click to collapse
I may just wait and get me a new phone in a few months. I'm expecting a bonus from work, and I'll likely just get the new S5. Thanks for the information
Nearly At the end of every month my my phone gets into some kinda software problem (example : Google has stopped working then process.android has stopped working and some other random **** which is quite annoying) whenever this happens the phone restarts on its own and never turns on,i mean it does but is stuck on loading screen.(note: I dont do anything stupid which might harm my phone. )So i have to flash my phone with spflashtool it.This time when i flashed the phone it didnt turn, i held the button for long but it was of no use, so i thought it might be the low on battery,but when i put it on charge nothing popped up... it wasnt charging. Then I thought it was the battery but my battery wasnt swollen and the day before I flashed it,it was running fine with full charge. , there was no sign of battery problem anytime i used it the consumption was normal.
Please help me fix this problem, and I also want a permanent fix to the software problem too.
Any senior member please help..
TIA
:fingers-crossed:
Update:I flashed the phone with new files but results were the same :'(
Saad6459 said:
Nearly At the end of every month my my phone gets into some kinda software problem (example : Google has stopped working then process.android has stopped working and some other random **** which is quite annoying) whenever this happens the phone restarts on its own and never turns on,i mean it does but is stuck on loading screen.(note: I dont do anything stupid which might harm my phone. )So i have to flash my phone with spflashtool it.This time when i flashed the phone it didnt turn, i held the button for long but it was of no use, so i thought it might be the low on battery,but when i put it on charge nothing popped up... it wasnt charging. Then I thought it was the battery but my battery wasnt swollen and the day before I flashed it,it was running fine with full charge. , there was no sign of battery problem anytime i used it the consumption was normal.
Please help me fix this problem, and I also want a permanent fix to the software problem too.
Any senior member please help..
TIA
:fingers-crossed:
Update:I flashed the phone with new files but results were the same :'(
Click to expand...
Click to collapse
same happens to me bro my android one is also dead same problem as yours when i tried with sp flash tool its end up with this error..... scr shot attached
☹
Bro,I flashed it thrice after but it didn't give any errors,but sadly it just wont turn on
If it were permanently bricked then it wouldn't have detected the phone...and bro lemme give you a suggestion,try changing it to firmware upgrade instead of download only.
Thanks for the reply
simmilar issue
same problem pls help in my case when i charge not charging the battery indicator just pops up and out i think its a battery error put in a new battery try to boot up nothing try to go in recovery nothing i have nothing to boot up from i think ill still try using fastboot and/or flashing and reporting back(ima try dead usb flash using spflash tool)
okay flashing works perfectly now i just need for figure out if the problem is with the charging/battery or the phone is dead
Same Problem
Bro, i have run into exact same problem. I even went to gallery and gave them the phone, they said they will charge 1500 as motherboard is dead but after one month they returned to me the phone saying that motherboard is not available. They are taking almost 14 days to return money so i have to visit again on 3rd june. But coming back to problem i have tried flasing with and without battery for 3-4 times. every times it shows success but the phone wont start. Even memory test was all fine. cant figure out what's the problem. i have tried both download only and format+download mode but nothing seems to work, If anyone finds a way to fix the phone please tell ASAP.
Same problem as the OP, mine's bricked as well after it began showing random FCs. Flashed KK and LP firmwares using SP Flash Tool but to no avail. The flash was successful tho but the phone never booted up
I'm kinda stuck in a similar situation. Let's start from the beginning -
When I got my Redmi Note 3 I stopped using my Canvas A1 and vaguely i remember that it was having software issues, rather than fixing it I just kept it away for a lot of months, and vaguely I remember that it just needed some flashing of rom and it would've gotten fixed.
And after all these months i'm need of this phone again. I don't remember much in depth details of the processes involved with it like flashing stuff etc. But I gathered as much knowledge as I could from the docs I had stored as backup & from the internet.
And IMO I think the flashing process was successful, but the screen is not turning on. Only once when I connected it to PC, the charging battery sign appeared(flashing thrice) but that was it. Nothing after that. And whenever I connect it to PC it detects the phone.
For now I've given it to a repair guy but I don't have much hope. He was saying that it could be just software problem, but I don't agree. If a smart person could comment on this thread so that we all could get some benefit out of it, in order to solve the situation or at least in my case I could research on something specific in the meantime.
Hi guys, I've a big problem, and it's very strange:
today I've updated lucky patcher, after installed it, the phone showed screen of the turning off. I started again the phone, but at the start screen, showed again the turn off screen. I tried to wipe and restore backup, samre problem. I tried to flash a stock firmware but after the sony logo i've a black screen with phone on. I really don't know what to do, I need your help. thanks a lot :crying::crying::crying:
ULT][MO said:
Hi guys, I've a big problem, and it's very strange:
today I've updated lucky patcher, after installed it, the phone showed screen of the turning off. I started again the phone, but at the start screen, showed again the turn off screen. I tried to wipe and restore backup, samre problem. I tried to flash a stock firmware but after the sony logo i've a black screen with phone on. I really don't know what to do, I need your help. thanks a lot :crying::crying::crying:
Click to expand...
Click to collapse
If you have revovery, you can just delete Lucky Patcher apk from /system or /data, (wherever it is). It's not a hard brick...
levone1 said:
If you have revovery, you can just delete Lucky Patcher apk from /system or /data, (wherever it is). It's not a hard brick...
Click to expand...
Click to collapse
Very bad news: I tried to flash a stock L, after flashed I started it, but it shutted down at waves bootanimation. I putted it on charge and showed this message "your device turned off due to overheating ,charging will continue once the device cools down".
An expert technician said to me that's a processor's cooling problem and, in his opinion, it is impossible to fix it. except sendind it directly to sony. But it should be very very expensive...
ULT][MO said:
Very bad news: I tried to flash a stock L, after flashed I started it, but it shutted down at waves bootanimation. I putted it on charge and showed this message "your device turned off due to overheating ,charging will continue once the device cools down".
An expert technician said to me that's a processor's cooling problem and, in his opinion, it is impossible to fix it. except sendind it directly to sony. But it should be very very expensive...
Click to expand...
Click to collapse
Did you already try waiting until it cools down and restarting? I would try that, or also try reflashing after cool down. First boot after flash is very long, and phone does get hot. If you were already overworking it with bootloops and stuff, and then tried to flash a rom, it might be a bit much...
levone1 said:
Did you already try waiting until it cools down and restarting? I would try that, or also try reflashing after cool down. First boot after flash is very long, and phone does get hot. If you were already overworking it with bootloops and stuff, and then tried to flash a rom, it might be a bit much...
Click to expand...
Click to collapse
Thanks levone for your answer, and sorry if it's passed a lot of time.
Unfortunately i tried everything coud be possible. tomorrow I'll try with an expert friend to open it and see the problem. A technician said to me that probably it's a cooling problem. Processor can't be cooled and phone shut off, or probably is (again) a battery problem. Soon i'll write if i've found a solution, also to try to help someone who could have a similar problem (i hope not).
How can the "processor" not be cooled? There is no cooling hardware that could stop working.. It could still be another hardware defect, yeah.. Have you wiped it or did you just flash system/baseband/kernel/etc ?
levone1 said:
Did you already try waiting until it cools down and restarting? I would try that, or also try reflashing after cool down. First boot after flash is very long, and phone does get hot. If you were already overworking it with bootloops and stuff, and then tried to flash a rom, it might be a bit much...
Click to expand...
Click to collapse
I've used Z1C in sauna (where is 100°C degrees) and the phone becomes so hot it is untouchable to hold and even struggling to play video playback (under clocking). Then i know it is too hot and take it out.
It takes ~1 min and it is cooled enough where is it fast and smooth again. Never has it said too hot, shutting off or something similar. Then again i'm using KitKat which doesn't maybe have that function?
I'd say issue related to battery or software as i had same problem after installing Lucky Patcher. Got bootloop after restarting.
I also used restoring and it succeeded but somehow Lucky Pather was still present but bootloop problem was cured.