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.
Related
I just wanted to try the latest CM9 after locking bootloader for a return. It unlocked, flashed fine, rebooted a few times. I was going to relock it so I used "reboot to bootloader". It was charging, it shut down and never turned back on. Removing the battery didn't help either. When I connect it to the PC, it recognizes OMAP4400 but doesn't install any drivers. I don't see how it can be bricked as I just rebooted to bootloader. It's been charging for a few hours and I haven't touched it since. I'm going to try the USB Jig soon, any additional help would be greatly appreciated..
If you're unlucky, you've hard-bricked it, somehow...
Try pressing (Just) Volume down + power...
That also gets you into Oding mode...
If that don't work, then sorry... I wouldn't know any other solution. Try the jig, if you want, but it's not put, that it'll work.
Well, best of uck!!
Hope you fix it!
LG familyguy59
Jig doesn't work, volume down+power doesn't, fastboot doesn't. Anything I do to it, it still shows as OMAP4440 in device manager. Even without the battery in. It must be in some kind of special recovery mode, but how the hell does it work with no battery. I'll leave it without battery over night, it's charged for sure so that can't be the problem.
The phone will work plugged in without the battery in under normal conditions, and that it's showing up at all is a good sign.
Have you used fastboot before successfully? You may need to load drivers manually. This thread links a few different options you can try:
http://rootzwiki.com/topic/12013-welcome-to-rootzwiki-editionstep-by-step-oem-unlock-and-root/
freemini said:
Jig doesn't work, volume down+power doesn't, fastboot doesn't. Anything I do to it, it still shows as OMAP4440 in device manager. Even without the battery in. It must be in some kind of special recovery mode, but how the hell does it work with no battery. I'll leave it without battery over night, it's charged for sure so that can't be the problem.
Click to expand...
Click to collapse
My guess is that if it is showing as OMAP, it is a sign that bootloader is not working at all, I've seen some topics of panda boards (that use the same processor) with the same symptons when bootloader was lost...
Yes I did use fast boot successfully before. I just don't see how it could corrupt the bootloader by simply restarting in it.. It doesn't make sense to me at all.
freemini said:
Yes I did use fast boot successfully before. I just don't see how it could corrupt the bootloader by simply restarting in it.. It doesn't make sense to me at all.
Click to expand...
Click to collapse
Well, I have this thought: You last used fastboot (With success), you maybe flashed a ROM, opr something.
You then restartet the phone, whilst it was still updating some internal files.
Maybe, if you did do that (willingly or not), you buggered the bootloader, like that...
familyguy59 said:
Well, I have this thought: You last used fastboot (With success), you maybe flashed a ROM, opr something.
You then restartet the phone, whilst it was still updating some internal files.
Maybe, if you did do that (willingly or not), you buggered the bootloader, like that...
Click to expand...
Click to collapse
It was not syncing or downloading anything, I've been using CM9 for about an hour before choosing reboot to bootloader. The only thing the phone was doing was charging.. I just don't understand how a simple command to reboot in bootloader can screw it up, it just doesn't make sense to me. It seems it's in a loop, Device Manager shows OMAP4440 refreshing about every second. It eventually disappears but if I plug it back in it does it again. I'm guessing the bootloader is gone
freemini said:
It was not syncing or downloading anything, I've been using CM9 for about an hour before choosing reboot to bootloader. The only thing the phone was doing was charging.. I just don't understand how a simple command to reboot in bootloader can screw it up, it just doesn't make sense to me. It seems it's in a loop, Device Manager shows OMAP4440 refreshing about every second. It eventually disappears but if I plug it back in it does it again. I'm guessing the bootloader is gone
Click to expand...
Click to collapse
Well, it may be gone, but OMAP normally means, that there is no firmware present...
This happened to me, whilst flashing a new firmware, onto the Wave, of my Dad...
I'll have a look, inside my Devman, and see, what I can find ^^
familyguy59 said:
Well, it may be gone, but OMAP normally means, that there is no firmware present...
This happened to me, whilst flashing a new firmware, onto the Wave, of my Dad...
I'll have a look, inside my Devman, and see, what I can find ^^
Click to expand...
Click to collapse
Thanks but I sent it back now. I hope they take it, there's a chance they won't obviously.. Let me know if you find anything, but it seemed hopeless to me.
freemini said:
Thanks but I sent it back now. I hope they take it, there's a chance they won't obviously.. Let me know if you find anything, but it seemed hopeless to me.
Click to expand...
Click to collapse
Well, I wish best of luck, in that matter!
I still think, it's an unwanted brick, though...
I've looked, but can't find anything, whilst the phone is booted in Android, so, I'll restart it in a minute, and then have a look ^^
I am devastated as i cant find the source of this problem. i tried changing rom, kernel and it still happens everytime. Whenever i lock my screen it just shuts down n i need to boot up again. if i boot up for too many times, it keeps popping up error "android.acore is not responding" which is very very annoying... n i have to reflash everything!! It happens just starting from ytd...
Surprisingly when i nandroid back to old base the problems seems to be resolved... can someone please help? thanks...
stephen2282 said:
I am devastated as i cant find the source of this problem. i tried changing rom, kernel and it still happens everytime. Whenever i lock my screen it just shuts down n i need to boot up again. if i boot up for too many times, it keeps popping up error "android.acore is not responding" which is very very annoying... n i have to reflash everything!! It happens just starting from ytd...
Surprisingly when i nandroid back to old base the problems seems to be resolved... can someone please help? thanks...
Click to expand...
Click to collapse
Do you do a full wipe before reflashing? Perhaps try relocking the bootloader and flashing the RUU then start from scratch.
I had this exact issue the other day, the problem was coming from SetCpu. Dunno if you have it or maybe a similar program installed? I was trying to underclock it but it keept rebooting whenever I offed the screen.
dr9722 said:
Do you do a full wipe before reflashing? Perhaps try relocking the bootloader and flashing the RUU then start from scratch.
Click to expand...
Click to collapse
I always full wipe before flashing... I think its the governor settings n underclocking that cause the problems. Still experimenting.
Johnny0906 said:
I had this exact issue the other day, the problem was coming from SetCpu. Dunno if you have it or maybe a similar program installed? I was trying to underclock it but it keept rebooting whenever I offed the screen.
Click to expand...
Click to collapse
Come to think of it I used system tuner to tweak my CPU abit... Maybe the kernel now still doesnt. Support underclocking.. glad to hear someone's experience as I am so scared that my power button or hardware might have some problems..
I am experiencing the same problem that my screen doesn't come back to life at times after it gets locked and i need to reboot it... You guys got any solution or would it be a better idea to claim my warrany?
Good evening everyone,
I come to you guys with a very particular problem. The LG G4 in question is an H815T (Asian variant). Let me clarify right now, it was not bootlooping. This one was getting STUCK at the LG logo, it didn't restart to it multiple times, it just got stuck there one day after turning off by itself. It did go into the download mode, though.
It went into the first part of the recovery, but when you selected that you wanted to factory reset, it got stuck there. The only way to get it out of the logo or the stuck recovery was taking the battery out. Interestingly enough, the phone DID charge at the stuck logo, albeit not so much due to the screen being constantly on at full brightness.
An even more interesting fact... I managed to fix it! I flashed the KDZ corresponding to the latest LP for the H815T, after the process was done, it did bootloop. I found the YouTube video about flashing a certain file to deactivate most of the cores and said "what the hell have I got to lose?"
Flashed the KDZ and.... VOILA! It showed the Recovery Android doing its job at Format Resetting !
Something even crazier... The phone booted into AndroidLP, I was worried about the cores thing, but the phone seemed to work at full speed... I was surprised to run HWmonitor and notice that all of the cores were active. The phone was fully working!!! Or so I thought... Now I have TWO problems:
I cannot update to MM. If I try to update from the phone itself (because it does say there's a new version available) I go back to being stuck at the LG logo.
When I make a call the screen goes off... nothing I do will turn it on, and if the other person does not hang up, the phone will remain locked. However, if I plug in a headset everything works normally.
Is there anything I can do about these two problems? Please, leave your comments and questions, I think this phone is pretty weird and I found nothing else like it on YouTube or here on XDA.
Take care :good:!
Idk for the call but for the mm you could try using something like lg mobile update tool... Something like that.
Be warned cuz i dont know if it will bootloop.
PhillipDSX said:
Good evening everyone,
I come to you guys with a very particular problem. The LG G4 in question is an H815T (Asian variant). Let me clarify right now, it was not bootlooping. This one was getting STUCK at the LG logo, it didn't restart to it multiple times, it just got stuck there one day after turning off by itself. It did go into the download mode, though.
It went into the first part of the recovery, but when you selected that you wanted to factory reset, it got stuck there. The only way to get it out of the logo or the stuck recovery was taking the battery out. Interestingly enough, the phone DID charge at the stuck logo, albeit not so much due to the screen being constantly on at full brightness.
An even more interesting fact... I managed to fix it! I flashed the KDZ corresponding to the latest LP for the H815T, after the process was done, it did bootloop. I found the YouTube video about flashing a certain file to deactivate most of the cores and said "what the hell have I got to lose?"
Flashed the KDZ and.... VOILA! It showed the Recovery Android doing its job at Format Resetting !
Something even crazier... The phone booted into AndroidLP, I was worried about the cores thing, but the phone seemed to work at full speed... I was surprised to run HWmonitor and notice that all of the cores were active. The phone was fully working!!! Or so I thought... Now I have TWO problems:
I cannot update to MM. If I try to update from the phone itself (because it does say there's a new version available) I go back to being stuck at the LG logo.
When I make a call the screen goes off... nothing I do will turn it on, and if the other person does not hang up, the phone will remain locked. However, if I plug in a headset everything works normally.
Is there anything I can do about these two problems? Please, leave your comments and questions, I think this phone is pretty weird and I found nothing else like it on YouTube or here on XDA.
Take care :good:!
Click to expand...
Click to collapse
U already had flashed a firmware so check for sensors use an app called phone doctor plus download from playstore run its all sensors test see if it shows error and also is ur phone refutbished did u bought the phone new or used... U can also take it lg service center see what they have to say avout it
PhillipDSX said:
Good evening everyone,
I come to you guys with a very particular problem. The LG G4 in question is an H815T (Asian variant). Let me clarify right now, it was not bootlooping. This one was getting STUCK at the LG logo, it didn't restart to it multiple times, it just got stuck there one day after turning off by itself. It did go into the download mode, though.
It went into the first part of the recovery, but when you selected that you wanted to factory reset, it got stuck there. The only way to get it out of the logo or the stuck recovery was taking the battery out. Interestingly enough, the phone DID charge at the stuck logo, albeit not so much due to the screen being constantly on at full brightness.
An even more interesting fact... I managed to fix it! I flashed the KDZ corresponding to the latest LP for the H815T, after the process was done, it did bootloop. I found the YouTube video about flashing a certain file to deactivate most of the cores and said "what the hell have I got to lose?"
Flashed the KDZ and.... VOILA! It showed the Recovery Android doing its job at Format Resetting !
Something even crazier... The phone booted into AndroidLP, I was worried about the cores thing, but the phone seemed to work at full speed... I was surprised to run HWmonitor and notice that all of the cores were active. The phone was fully working!!! Or so I thought... Now I have TWO problems:
I cannot update to MM. If I try to update from the phone itself (because it does say there's a new version available) I go back to being stuck at the LG logo.
When I make a call the screen goes off... nothing I do will turn it on, and if the other person does not hang up, the phone will remain locked. However, if I plug in a headset everything works normally.
Is there anything I can do about these two problems? Please, leave your comments and questions, I think this phone is pretty weird and I found nothing else like it on YouTube or here on XDA.
Take care :good:!
Click to expand...
Click to collapse
I also got the same problem! How do you managed to flash KDZ when the phone is stuck at LG logo?
jinderation said:
U already had flashed a firmware so check for sensors use an app called phone doctor plus download from playstore run its all sensors test see if it shows error and also is ur phone refutbished did u bought the phone new or used... U can also take it lg service center see what they have to say avout it
Click to expand...
Click to collapse
Got it! The sensors thing was definitely it for the screen problem. I also read this is very common with many screen protectors in 5.1.
Do you have any ideas regarding the issue updating to MM?
willy792003 said:
I also got the same problem! How do you managed to flash KDZ when the phone is stuck at LG logo?
Click to expand...
Click to collapse
All good, Willy! Even is you're stuck at the LG logo, take your battery out, or it back in BUT DON'T TURN IT ON... Instead, try to access DOWNLOAD MODE. If you're able to do it, you can flash any KDZ you want, but be careful.
Sent from my GT-N8010 using Tapatalk
Yes ur right using a heavy screen protector will block all the sensors so ya try removing it... No issues in MM u can try OTA through wifi
PhillipDSX said:
Got it! The sensors thing was definitely it for the screen problem. I also read this is very common with many screen protectors in 5.1.
Do you have any ideas regarding the issue updating to MM?
All good, Willy! Even is you're stuck at the LG logo, take your battery out, or it back in BUT DON'T TURN IT ON... Instead, try to access DOWNLOAD MODE. If you're able to do it, you can flash any KDZ you want, but be careful.
Sent from my GT-N8010 using Tapatalk
Click to expand...
Click to collapse
your screen protector had the sensors covered . you need one with the cut out in the speaker and sensors..
So like many of you have experienced, I recently suffered from the LG G4 infamous bootloop crash. LG has admitted this is a hardware problem and is fixing affected devices. Also like many of you, I had my boot-loader unlocked & I was rooted, which 'can' void warranty. I am fortunate enough to be on T-Mobile in the US, so my boot-loader is re-lockable.
Anyway, back on point, my G4 crashed and I was never able to get past the loading screen. I tried getting into TWRP to do a backup and it crashed there too, I wasn't even able to get into it at all. After several hours of research where I came across someone who said putting it in the Oven at 400 degrees F (Which I couldn't bring myself to do) I did try putting it in front of a heater to see if that helped (It made it worse), I eventually gave up at about 3 am.
I arose the next morning and thought 'What the Hell' and I tried to turn it on, and to my sheer disbelief, the phone actually loaded the software up (Briefly before crashing again). I pulled the battery and tried a couple of more times, each time it got progressively worse after the phone got warmer and warmer. Then after getting frustrated and being pissed off at myself for not being more diligent at Nandroid Backups I thought maybe it just needs some cooling help.
So I through the damned thing in the Freezer! Left it there for 10 minutes, and then turned it on. IT BOOTED UP! I was able to play with the software for a bit too, and it lasted for about 5 minutes. Put it back in the freezer, let it cool down and I booted into TWRP, ran a Nandroid while it was still cool in the freezer. It was successful and I was pumped! I was extatic at my discovery because it allowed me to backup my data, restore it back to stock Rom, and re-lock the boot-loader so I could warranty it though T-Mobile. I wanted to share the tip with you all and maybe save some lives!
TL;DR If your G4 Crashes, try putting it in the freezer to cool it off. It might get it to boot up long enough to get some stuff backed up.
Disclaimer stuffs - Obviously I don't accept any responsibility should you freeze your phone unusable if you do this. None of the damage is my fault, I'm simply sharing what helped me. Try at your own discretion.
The Freezer advice didn't worked for me. Temp was too cold.
However I managed to backup my data with the phone put on the air vents of an A/C set up at 22°C: I was able to boot into the recovery and mount the storage to launch the backup of internal memory on my computer.
Harmtan2 said:
So like many of you have experienced, I recently suffered from the LG G4 infamous bootloop crash. LG has admitted this is a hardware problem and is fixing affected devices. Also like many of you, I had my boot-loader unlocked & I was rooted, which 'can' void warranty. I am fortunate enough to be on T-Mobile in the US, so my boot-loader is re-lockable.
Anyway, back on point, my G4 crashed and I was never able to get past the loading screen. I tried getting into TWRP to do a backup and it crashed there too, I wasn't even able to get into it at all. After several hours of research where I came across someone who said putting it in the Oven at 400 degrees F (Which I couldn't bring myself to do) I did try putting it in front of a heater to see if that helped (It made it worse), I eventually gave up at about 3 am.
I arose the next morning and thought 'What the Hell' and I tried to turn it on, and to my sheer disbelief, the phone actually loaded the software up (Briefly before crashing again). I pulled the battery and tried a couple of more times, each time it got progressively worse after the phone got warmer and warmer. Then after getting frustrated and being pissed off at myself for not being more diligent at Nandroid Backups I thought maybe it just needs some cooling help.
So I through the damned thing in the Freezer! Left it there for 10 minutes, and then turned it on. IT BOOTED UP! I was able to play with the software for a bit too, and it lasted for about 5 minutes. Put it back in the freezer, let it cool down and I booted into TWRP, ran a Nandroid while it was still cool in the freezer. It was successful and I was pumped! I was extatic at my discovery because it allowed me to backup my data, restore it back to stock Rom, and re-lock the boot-loader so I could warranty it though T-Mobile. I wanted to share the tip with you all and maybe save some lives!
TL;DR If your G4 Crashes, try putting it in the freezer to cool it off. It might get it to boot up long enough to get some stuff backed up.
Disclaimer stuffs - Obviously I don't accept any responsibility should you freeze your phone unusable if you do this. None of the damage is my fault, I'm simply sharing what helped me. Try at your own discretion.
Click to expand...
Click to collapse
i been asking alot of people and no one has answer.. do you still have the phone ..please can you unlock it and relock it. with video? many people say it cant be relock... thats whats keeping me from unlocking..
am on TMO too so. i dont care about data.. i care about unlocking bootloader, if get hit by bootloop then relock it then flash stock firmware and send for repair... would you record that it can acttually be relock . please.. :fingers-crossed:
interesting, I havent seen anyone mention phone overheating in any other bootloop threads before.
raptorddd said:
i been asking alot of people and no one has answer.. do you still have the phone ..please can you unlock it and relock it. with video? many people say it cant be relock... thats whats keeping me from unlocking..
am on TMO too so. i dont care about data.. i care about unlocking bootloader, if get hit by bootloop then relock it then flash stock firmware and send for repair... would you record that it can acttually be relock . please.. :fingers-crossed:
Click to expand...
Click to collapse
I unfortunately don't have the phone, I sent it back to Tmobile. From my understanding, the Tmobile version is the only one that is relockable. However, I will be doing the same thing with my wife's G4. I'll see what I can do about a video for you.
kenitec said:
The Freezer advice didn't worked for me. Temp was too cold.
However I managed to backup my data with the phone put on the air vents of an A/C set up at 22°C: I was able to boot into the recovery and mount the storage to launch the backup of internal memory on my computer.
Click to expand...
Click to collapse
Nice! At least you got it to boot up long enough. Idk maybe my experience was unique.
Levent2101 said:
interesting, I havent seen anyone mention phone overheating in any other bootloop threads before.
Click to expand...
Click to collapse
I never saw anything about it either, but it worked! I'll consider it an act of God or something.
Harmtan2 said:
I unfortunately don't have the phone, I sent it back to Tmobile. From my understanding, the Tmobile version is the only one that is relockable. However, I will be doing the same thing with my wife's G4. I'll see what I can do about a video for you.
Click to expand...
Click to collapse
you think it can be relock in bootloop state?
raptorddd said:
you think it can be relock in bootloop state?
Click to expand...
Click to collapse
If you can get it to boot up yes... When I put mine in the freezer I was able to get it booted up just long enough to do what I needed to with it. That's why I posted this in the first place. Cooling the phone off helped unboatloop it temporarily. That's when I re-locked the bootloader.
It's not a guarantee though, I was just sharing what worked for me.
Harmtan2 said:
If you can get it to boot up yes... When I put mine in the freezer I was able to get it booted up just long enough to do what I needed to with it. That's why I posted this in the first place. Cooling the phone off helped unboatloop it temporarily. That's when I re-locked the bootloader.
It's not a guarantee though, I was just sharing what worked for me.
Click to expand...
Click to collapse
really it must boot up to get it relock.????? then am not sure i want to unlock just yet... i saw user ENZO made a kernel that will disable the 2 big core but for h815... i tought it didnt have to boot up to os.
raptorddd said:
really it must boot up to get it relock.????? then am not sure i want to unlock just yet... i saw user ENZO made a kernel that will disable the 2 big core but for h815... i tought it didnt have to boot up to os.
Click to expand...
Click to collapse
Cooling down the phone (with the freezer or A/C methods) really helps to boot in the recovery or normally. If the re-lock method is really working and is fast to apply, i presume that yes, you may be able to relock the bootloader.
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.