Related
Pardon for the long post but my Nexus One has been out of comission for a few days now so I'll list everything I've tried to make it work in an attempt someone might be able to help me!
Okay, here goes.
A couple days ago I removed the battery on my phone to install an invisible shield. Prior to that I had owned the Nexus One brand new for about a week, had it rooted first thing with the HTC Desire ROM...it was running perfectly
After the installation of the shield was complete I reinserted the battery and hit the power button. The phone booted straight to the bootloader (aka white Robots on Skateboards screen). Funny thing, I was unable to navigate the bootloader (vol up/down) without fiddling with the trackball first by pressing it a couple times) Anyway if I would reboot the phone via bootloader it would return...power off the phone it wouldn't power off just reboot to bootloader.
In this mode I could still use fastboot perfectly and I could enter the restore screen. At this point I kept attempting a reboot and it actually went through at one point and did a full boot to the OS...when I powered down and booted up again however, it was back to the same issue.
On the modaco forum they suggested I flash an alpha2boot.img as the boot image replacement for r21 desire rom as a fix, I tried this method with no success. Since, I've factory reset the phone several times replacing it with various ROMs (currently running stock) none of it fixed the problem.
I also found a way to brute force the phone into safe mode via the fastboot command in prompt: fastboot-windows reboot Using this command the phone successfully reboots, albeit into SAFE MODE. In safe mode the phone works perfectly in every way. I'm just limited in that I can't install any applications and I can't reboot properly (without a computer and command prompt).
I was doing some research on the forums and read the problem could be with the trackball. It would make sense that the phone could only boot to bootloader if the phone had the key press for the trackball triggered somehow. That said, the trackball functions perfectly when operating the phone in safe mode so I doubt this is the issue.
Another idea is that the phone is stuck in some state in the SPL or bootloader...I was wondering if there was anyway to reflash the SPL or bootloader to see if I could resolve the issue that way. (how I would do this, I have no idea)
Any help, suggestions, or advice is very appreciated. As I already unlocked my phone I have a feeling I am out of luck for warranty though I would pay for HTC to repair it if they could. I would prefer to fix it in the software however and not send it in.
Reflash the stock ROM and see if that helps.
mortzz said:
Reflash the stock ROM and see if that helps.
Click to expand...
Click to collapse
He said he's running stock rom...
@ OP, if everything was absolutely perfect before putting the shield on, and everything to crap immediately after finishing the shield, then obviously something went wrong during the install.
The obvious yet unfortunate conclusion is that some solution got inside or something, most likely inside the trackball. =\
Detail exactly what you did when you installed the invisible shield.
Did you get you phone wet at all?
Got the front of the phone a little wet and I'm guessing some did get in the trackball. That said, I do invisi shields every day for my job and never had an issue with any phone...wouldn't it be ironic that mine was the one that got screwed up.
I think it's interesting to note that the trackball still works perfectly when the phone is running in safe mode, no double clicks or anything like that...possibly a sensor was tripped?
Got the front of the phone a little wet and I'm guessing some did get in the trackball. That said, I do invisi shields every day for my job and never had an issue with any phone...wouldn't it be ironic that mine was the one that got screwed up.
I think it's interesting to note that the trackball still works perfectly when the phone is running in safe mode, no double clicks or anything like that...possibly a sensor was tripped?
So I called it quits on fixing this phone and I'm sending it out to HTC does anyone know how I go about getting restore back to factory settings?
Well you can't relock the bootloader, but if you can use fastboot when your phone's on the booatloader, you can use that to wipe the phone.
Oh wow, sorry to hear it.
If your phone will not boot without the help of fastboot, I wouldn't worry to much about what state Android is in (factory, or custom rom). HTC will attempt to boot the phone, toss it in a bin, and then send you a replacement.
Or that is my assumption anyways. A friend had a similar issue; he unlocked his phone and decided after flashing the Desire rom, that he wanted to stay stock with what came on his Nexus for a while. After flashing the stock images back, his phone looped into bootloader. Off to HTC it went and within a week he had a new phone.
Best of luck!
Sorry to post in such an old thread, but I'm having the exact same issue. Even the part with the invisible shield. Didnt install it myself, the idiot at best buy used too much of the liquid I guess. Did you send yours in or what? I managed to get the phone to work for about a month then it started acting up again today. Wont boot into anything other than safe mode, or fastboot. When it boots into safe mdoe, the phone turns off within a few seconds then goes straight to the boot animation. Would love to get this issue settled, really annoying
i am having same problem. fasboot doesnt even find my phone. i got into safe mode but when i turned it off and back on it went back to fastboot
Same
I am getting the same problem! this really sucks. I think the phone might have gotten a little bit wet, just a few drops of water, and that may have caused this. Should I just call HTC and send it in?
btw, the phone was working fine, even with the very little moisture that was wiped from it. But, I took out the battery when I got home, and this happened.
so is this because on invisibleshield? cuz i just ordered mine today!!
I think its from a little bit of moisture getting into the trackball. I've been doing many "tests" trying to figure out the problem, and my almost final conclusion is the trackball not working good. Most of the time I try to start-up the phone i get into safemode, and once I have gotten into the normal way of things, but the trackball wasn't working well. I think I might have to cal htc, and that sucks because I am going out of the country in 4 days... I won't be able to take my nexus if I can't come up with a way to fix it myself.
I DID IT!
Well, I think I did.
My theory that moisture was the cause of this bootloader stuckness is quite correct. I took a towel, and rubbed the trackball to it for a good 5-10 min, then I did it for another 5-10 min wiping while pressing down on the trackball. I'm very sure that there was some moisture extracted from the device. The trackball is working now. I now do not have to call HTC or send it in.
I kept on booting into fastboot and then recovery, being unable to press buttons, but then I rebooted again into safe mode, where the trackball wasn't working either. I kept moving around the trackball, and then I figured it out, because I felt a slight bit of moisture. Now, it boots up normally, I can access the recovery, and all selection is working.
But, I have a bad feeling that this problem will come back to haunt me. It's good for now though.
Phone is working great as usual.
Can confirm the same issue.
Drop of water on the trackball.
Rebooted into an unresponsive fastboot.
Fastboot reboot command from the computer got me into safemode.
Rolling the trackball while pressed fixed it, the phone boots properly now.
Hey everyone, First time poster here and it seems my captivate is bricked. I'm fairly new to android but I caught on with ROM/kernel/etc.. flashing and all seemed to be going well. I saw the new 3.5 update for precision and wanted to update from 3.0. I did my usual thing and restored to stock with ODIN instead of flashing over. Rooted all over again, downloaded ROM manager and flashed clockwork recovery. I selected the ROM when I was in CWrecovery and rebooted.. but for some reason the phone never gets past the boot screen. The ATT logo shows up, then the suckerpunch logo (as suckerpunch is included in the precision ROM) and then the precision logo.. but it just keeps starting over from there. I thought I did a clean flash but something went wrong obviously.
Ive tried the three button combo and anything that has been stated before on here about the three button combo timing and whatever. So it seems that I cant get in recovery or download by using the traditional methods.
I'm guessing my phone is soft-bricked, which should be relatively easy to fix, but I can't get into any mode at all. Ive seen plenty of threads with people having boot loop issues but they seem to have been solved my some combination of buttons used or the ODIN usb download mode technique. Ive seen mention of using adb commands to get into download mode, but I think I have to have usb debugging enabled which I can't enable, clearly.
Any help would be appreciated, especially since in the meantime I'll have to use my old 903sh.
CCDillon said:
Hey everyone, First time poster here and it seems my captivate is bricked. I'm fairly new to android but I caught on with ROM/kernel/etc.. flashing and all seemed to be going well. I saw the new 3.5 update for precision and wanted to update from 3.0. I did my usual thing and restored to stock with ODIN instead of flashing over. Rooted all over again, downloaded ROM manager and flashed clockwork recovery. I selected the ROM when I was in CWrecovery and rebooted.. but for some reason the phone never gets past the boot screen. The ATT logo shows up, then the suckerpunch logo (as suckerpunch is included in the precision ROM) and then the precision logo.. but it just keeps starting over from there. I thought I did a clean flash but something went wrong obviously.
Ive tried the three button combo and anything that has been stated before on here about the three button combo timing and whatever. So it seems that I cant get in recovery or download by using the traditional methods.
I'm guessing my phone is soft-bricked, which should be relatively easy to fix, but I can't get into any mode at all. Ive seen plenty of threads with people having boot loop issues but they seem to have been solved my some combination of buttons used or the ODIN usb download mode technique. Ive seen mention of using adb commands to get into download mode, but I think I have to have usb debugging enabled which I can't enable, clearly.
Any help would be appreciated, especially since in the meantime I'll have to use my old 903sh.
Click to expand...
Click to collapse
Can you describe exactly which three button methods have you performed? The one that always seems to work to get to download mode is hold both volume up and down and plug in USB cable to the computer and you should be able to get into download mode (of course after taking out the battery, shutting off your phone first). You should have ODIN open before this, then after that just press start on ODIN.
I believe people with captivates who have problems with 3 button combos have batch 1008. Please tell if you can't use the method above then we can check your batch.
koreancanuck said:
Can you describe exactly which three button methods have you performed? The one that always seems to work to get to download mode is hold both volume up and down and plug in USB cable to the computer and you should be able to get into download mode (of course after taking out the battery, shutting off your phone first). You should have ODIN open before this, then after that just press start on ODIN.
I believe people with captivates who have problems with 3 button combos have batch 1008. Please tell if you can't use the method above then we can check your batch.
Click to expand...
Click to collapse
I appreciate the fast response.
Ive tried the above method and it didn't work. Ive also tried plenty of others like holding the power button with the two volume buttons (to try recovery) Ive also held the buttons down for certain amounts of time to see if my timing is just off, and pretty much a few other generic three button combos that are performed when this sort of thing happens. Instead of getting into download mode, it of course just shows the battery charging.
If the phone is plugged in while it is doing its rebooting cycle then ODIN actually detects it, but I still wouldn't be able to do anything I'm sure.
Ive read through many posts about this but I just cant find anything to work at all, maybe buying a jig would be the final solution. :/
EDIT: If it helps, before flashing my captivate for the very first time a month back, i was told to check to see if I could enter into download mode and recovery safely, which I could and this was on stock rom. Ive been able to get into download/recovery with other ROMs as well, idk what's up now though
CCDillon said:
I appreciate the fast response.
Ive tried the above method and it didn't work. Ive also tried plenty of others like holding the power button with the two volume buttons (to try recovery) Ive also held the buttons down for certain amounts of time to see if my timing is just off, and pretty much a few other generic three button combos that are performed when this sort of thing happens. Instead of getting into download mode, it of course just shows the battery charging.
If the phone is plugged in while it is doing its rebooting cycle then ODIN actually detects it, but I still wouldn't be able to do anything I'm sure.
Ive read through many posts about this but I just cant find anything to work at all, maybe buying a jig would be the final solution. :/
EDIT: If it helps, before flashing my captivate for the very first time a month back, i was told to check to see if I could enter into download mode and recovery safely, which I could and this was on stock rom. Ive been able to get into download/recovery with other ROMs as well, idk what's up now though
Click to expand...
Click to collapse
If you could get into download before, I don't know why you wouldn't be able to do it now. The fact that you can see the battery charging icon indicates that you should easily be able to get into download mode. Can you double check your methods and if neither work, you could always go for JIG.
you may need to buy this to get into download mode:
http://cgi.ebay.com/ws/eBayISAPI.dl...69977&ssPageName=STRK:MESELX:IT#ht_623wt_1139
just to clearify and add one more thing to try...
you are experiencing a boot-loop not brick..
ive heard of boot loop problems sometimes getting into download mode by:
remove battery
plug in usb
hold volume buttons
put in battery
(slight change on usual method)
EDIT: you may also want to try the AIO captivate toolbox in the Dev section, it can try to put your phone into download mode
I had this happen before. I did what Tresselo said and it worked.
Sent from my SAMSUNG-SGH-I897 using XDA App
plug in your usb cable. let the phone reboot and see if the comp recognizes the phone at any point during your boot loop. if it does - your in luck, sort of... I had this problem as well with the same ROM. idk if its the ROM or just me screwing up (probably me screwing up) anyhow, type this command into a command prompt (must have the android sdk and adb installed) get into the tools folder where ever that may be at for me its C:\android\tools
from this dir type this: adb reboot download - do this as soon as the comp recognizes your phone - should work.... IF the comp is seeing the phone. If its not you WILL need a JIG which can be made fairly easy.
Try adb if you haven't already. Instructions are in the stickies in the Dev section.
Sent from my Captivate using XDA App
Thanks for all the replies guys, got a good community here. Sadly no suggestions have worked at all.
jgc121 said:
plug in your usb cable. let the phone reboot and see if the comp recognizes the phone at any point during your boot loop. if it does - your in luck, sort of... I had this problem as well with the same ROM. idk if its the ROM or just me screwing up (probably me screwing up) anyhow, type this command into a command prompt (must have the android sdk and adb installed) get into the tools folder where ever that may be at for me its C:\android\tools
from this dir type this: adb reboot download - do this as soon as the comp recognizes your phone - should work.... IF the comp is seeing the phone. If its not you WILL need a JIG which can be made fairly easy.
Click to expand...
Click to collapse
I downloaded the android SDK and installed all the necessary components, as soon as I hit the right directory (for me C:\Program Files\Android\android-sdk-windows\platform-tools>adb reboot download) and I get "error: device not found". So adb seems to be running right and I may just have to get my timing right, but as of trying a good ten times I'm not having any luck.
When booting up my cap while plugged into the computer, the noise that signals a usb connection sounds and when going into device manager and looking at usb connections, its says samsung android device. Seems like I could get into download, but I guess I'll just keep trying to time it exactly right even though Ive hit the command near the connection noise every time.
I'm not losing hope, but I went ahead and ordered the jig off of ebay that mengbo posted, I'm really hoping that the jig could solve my problem for good. From your perspective guys, would the jig DEFINITELY work? Or is it just a kinda one shot, hope for the best thing?
The JIG is a pretty sure thing seeing as how you are just in a boot loop.
CCDillon, Im in the same boat as you. Same thing happened to me. I have tried a jig and it did not work for me. Hopefully it works for you. I have tried ADB also and it could not find the device. I really hope there is something out there that can help us.
aw man, that's not good at all.. hope you can find a way. Did you make a jig and were you using the same ROM?
Hopefully its just mine and the jig works for you. I didnt mean to scare you. I made a jig at first, and it kept booting the phone. Thought I didnt make it correctly so I got one off of ebay, thinking it had to work. That one did the same thing. Thought maybe it was a faulty jig and the guy I got it from ('mengbo' on this forum) sent me another one to see if that was it. The new jig he sent (that worked on his phone) did the same thing. So, something else is going on.
I was going from Phoenix 4.5 to Supernova ROM and it gave me the same error you got. Now it Boots the ATT screen then loops the Phoenix ROM logo over and over. 1 vibrate followed by 2 more
I'm hoping the JIG works for mine, otherwise I'm not sure what to do. I admit it does scare me a bit to see that you've tried all these different things with no result. I was scanning the precision thread and it seems one of the avid users/posters got caught in a boot loop and it looks like they have gotten out of it, I sent a PM so maybe I can see what that user did, though part of me is thinking that the three button method worked for him but for some reason not for me. This is very frustrating and I'll keep an update on everything, the JIG should be here in about 3 days or so.
Also, you think it may have something to do with how many times our phones have been flashed? Ive looked up to see if flashing is bad for the phones "health" but it seems flashing won't really hurt anything, nor have I really flashed too much. Btw, my phone acts the same you described as well, with the random vibrating and everything.
My mind just seems to be jumping to any random possibility, it just sucks not having a working phone.
Hope SOMETHING works for you
Seriously - you guys are all worked up over a boot loop. the JIG will put you into dl mode just fine... only time it has high chance of NOT working is if you only see black screen - no power up at all.... you can make a JIG by getting 3 - 100k ohm resistors and a 1k ohm resistor from radio shack for about $1.25... its simple.
I removed my 3 button combo accidentally by flashing att 1 click, theres an att 1 click with 3 button fix, flash that when you can get into download mode.
If you can connect with adb use it to go to download, if not, you need a jig... it works, I have been down your path!
jgc121 said:
Seriously - you guys are all worked up over a boot loop. the JIG will put you into dl mode just fine... only time it has high chance of NOT working is if you only see black screen - no power up at all.... you can make a JIG by getting 3 - 100k ohm resistors and a 1k ohm resistor from radio shack for about $1.25... its simple.
Click to expand...
Click to collapse
+1. Learn how to make the JIG you need HERE...
Or buy one from me HERE... < Shameless plug.
I was in the same situation as you guys after i had a bad flash and the loop on the bootanimation. I bought a jig online and it worked. The trick is to take out your microsd, and simcard and leave out the battery for 15 seconds. Then put back ONLY the battery in, and plug in the jig. It should turn back on and be put into download mode then flash with one click odin.
odin one click WITH 3 button fix....... saftey first.
Hey Guys
Hope, some of you can help me. The problem is:
i bought a new HTC One Mini 2. Cause i had a Cyanogen 10.1 on my previous phone, i thought, that i should install a new CyanogenMod for this phone again. So i unlocked und flashed the Phone. As custom recovery i used TWRP 2.8.5.0... Found that one here in a Thread. After i flashed cm-12-20150411-NIGHTLY-memul.zip on it. After all, i started my phone again and all worked fine. i thought....
So yesterday i powered off my phone, plugged it to the charging-cable and went to sleep. In the morning i got up, picked my phone and wanted to turn it on. What i saw, was the charging screen, blink led is standing on orange and thats it. Cant power it off again, cant boot to recovery... nothing...
And the point is, i dont have the ultilities and the skill to open the phone and remove the battery to see, if that is the problem.
Do you have any ideas for that?? Thanks for leave an answer
lol
peacer95 said:
Hey Guys
Hope, some of you can help me. The problem is:
i bought a new HTC One Mini 2. Cause i had a Cyanogen 10.1 on my previous phone, i thought, that i should install a new CyanogenMod for this phone again. So i unlocked und flashed the Phone. As custom recovery i used TWRP 2.8.5.0... Found that one here in a Thread. After i flashed cm-12-20150411-NIGHTLY-memul.zip on it. After all, i started my phone again and all worked fine. i thought....
So yesterday i powered off my phone, plugged it to the charging-cable and went to sleep. In the morning i got up, picked my phone and wanted to turn it on. What i saw, was the charging screen, blink led is standing on orange and thats it. Cant power it off again, cant boot to recovery... nothing...
And the point is, i dont have the ultilities and the skill to open the phone and remove the battery to see, if that is the problem.
Do you have any ideas for that?? Thanks for leave an answer
Click to expand...
Click to collapse
I works again. was some buggy thing, i guess. A friend took my phone, did same combination that i did to boot in recovery mode and BOOM it reboots and work properly. So, i can't tell u a real solutions, but if you got same problem, keep trying with the POWER-Button and the VOLUME_DOWN-Button. Worked in my case.
Thread can get closed.
peacer95 said:
I works again. was some buggy thing, i guess. A friend took my phone, did same combination that i did to boot in recovery mode and BOOM it reboots and work properly. So, i can't tell u a real solutions, but if you got same problem, keep trying with the POWER-Button and the VOLUME_DOWN-Button. Worked in my case.
Thread can get closed.
Click to expand...
Click to collapse
What he did was a hard reboot, accomplished by holding the power and vol-up buttons for about 10 seconds. Just wanted to add this.
Hey guys,
any solution to this problem??
Got the same issue. unlocked bootloader with htcdev, installed TWRP Recovery and rooted phone, everything worked fine yesterday.
Today I installed xposed framework, then I plugged-in the charging cable and turned off the phone because I wanted to flash xposed in Recovery. But when the phone turned off, it only showed the charging screen with the message ("This build is for development purposes only Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action.") and didn't react to any button pressings until the battery finally died.
Then I plugged in charging cable again. Now I have again the charging screen, only difference is that the LED doesn't flash permanently but it now blinks. Computer recognizes phone but I can't send fastboot commands since it is turned off.
Any help would be appreciated!
EDIT: After a lot of tries, I finally also managed to fix it with 10 seconds power + volume up....
I'll try to make this short.....
I am using N910T3. Phone was charging in car while using (stop by roadside). Out of sudden it shutdown and went into reboot loop and the phone is extremely hot. I took the battery out for soft reset and try to turn on again. Phone will freeze at different screen (Lock Screen, Home Page, Samsung Logo, Powered by Android) and give two separate vibration before reboot.
I thought it is battery problem so I bought a new battery to try, but still the same problem. So I went on to backup all file before I perform hard reset. While doing that, I find out the phone can be use for longer before reboot if it was stay off for a long time. So I have this crazy idea: put it in a fridge. Surprisingly it works! The phone will not reboot anymore and I can manage to backup all file before doing anything else. Also, the phone will not charge if you plug in right after a few reboot.
Then, along with the fridge method, I perform factory reset through normal android setting. Now it will just stuck at powered by android screen while in reboot loop. I then try to flash with Odin, multiple times. Flash by Odin is complete, phone restart, then it freeze and reboot, at different screen (Installing system update, Erasing, powered by android).
Out of frustration I try with the fridge method to flash, and IT WORKS AGAIN!!!. The phone can now boot to welcome screen where you first setup your phone. However, it will then freeze again and reboot while doing so.
There was only this one time, where I left the phone off for a day after flash with a previous stock ROM, turn it on and skip as much setup as I can, finally reach the homepage screen, then will stay on without any reboot issue. I thought I finally fix it. I then power off the phone, put in my Sim Card and SD Card, power it on, then again, reboot issue appear.
I tried flash with latest stock ROM, previous stock ROM (one updates away), flash any stock ROM with pit file. I sometimes will get error code on device after flash (can't remember the exact error). I also cannot boot into recovery mode without flashing a twrp. Sometimes if success, I will get straight to Lock Screen without going through the phone welcome setup process. But again, none of these I tried can solve the reboot loop.
I may went too far and mix up all steps to the phone. Does anyone have any idea how to fix this? Or is my phone, as I believe, has a faulty motherboard that cause the reboot loop? Thanks in advance for reading through my problem!
Hello there, I had a Tmo Note 4 which I loved it until the end, it's a hardware problem and there is no fix for it unless you replace the board, by the time you buy the board and what you need to pay for labor you're going to expend a few hundred dollars, I also tried the freezer method but it finally the phone gave up, it does not turn on anymore. That was my experience. Good luck bud.
oscarmaldonado said:
Hello there, I had a Tmo Note 4 which I loved it until the end, it's a hardware problem and there is no fix for it unless you replace the board, by the time you buy the board and what you need to pay for labor you're going to expend a few hundred dollars, I also tried the freezer method but it finally the phone gave up, it does not turn on anymore. That was my experience. Good luck bud.
Click to expand...
Click to collapse
Seems like that's the case I guess.....But if anyone has any suggestion please do tell so I can give it a shot.
jackgan said:
Seems like that's the case I guess.....But if anyone has any suggestion please do tell so I can give it a shot.
Click to expand...
Click to collapse
Try a firmware flash before newsest. Then take the ota
anyone know if a 910t3 mother board will fit in a 910t frame? Asking cuz I wanna switch them out.
I have got my Asus ROG Phone II for about 8 months and I have recently got some problems with the software. The phone suddenly turns off on it's own, when I am using it and stucks at the restarting process with Asus Logo and the loading bar on the lower side but doesn't open, even if I wait for a full whole hour. I have to press volume down + power off button to make it work again. I wanted to ask if any of you guys have got the same problem, or any clues how to solve it?
Well I had rooted my phone after a month of it's use and unrooted it. For about 2 Months before, my charging port stopped working and Asus Service Center fixed it, and I guess they somehow flashed my Phone, as I not don't have to download and install the new firmware. It was good in a way but I feel it is getting some lag during the use of certain apps and the problem which I mentioned earlier. I would be thankful and grateful for your replies.
Wishing all to stay safe and healthy
Fantasticooo said:
I have got my Asus ROG Phone II for about 8 months and I have recently got some problems with the software. The phone suddenly turns off on it's own, when I am using it and stucks at the restarting process with Asus Logo and the loading bar on the lower side but doesn't open, even if I wait for a full whole hour. I have to press volume down + power off button to make it work again. I wanted to ask if any of you guys have got the same problem, or any clues how to solve it?
Well I had rooted my phone after a month of it's use and unrooted it. For about 2 Months before, my charging port stopped working and Asus Service Center fixed it, and I guess they somehow flashed my Phone, as I not don't have to download and install the new firmware. It was good in a way but I feel it is getting some lag during the use of certain apps and the problem which I mentioned earlier. I would be thankful and grateful for your replies.
Wishing all to stay safe and healthy
Click to expand...
Click to collapse
Don't know what the problem is, but you've posted this in the wrong section!
I think I am in a similar situation. My phone's problem is that it kind of crash while booting up (stange lines shows on the screen like some glitch) , it doesnt boot up normally and it loops 3 to 4 times until it's left on a black screen. I am not sure of its status at this point for it is not responsive even to force restart (Vol down + Power) but it does work only once in a couple of minutes and proceeds to bootloop and back again to the black screen. I haven't rooted it but i did flash it from CN to WW which was successful and was using it perfectly for 4 months up until this situation. I dont know what exactly is the problem. Can anyone help me?
Same with me bro... Mines already bricked because of flashing it to the original version
Same here