Database Info

[Q] Nexus S - can't mount anything! - stuck on Google Logo

Hello!
Okay, so the weirdest thing has happened with me. My Nexus S (i9023) was working absolutely fine till last evening when it ran out of battery. After I came back home, I put it for charging and switched it on.
For the first few time, nothing would show except the USB connected/ disconnected screen which appears everytime you plug your phone in. I thought maybe it was just being weird, so I took out the battery and booted it up again. This time I am just stuck at the Google Logo! It is not going ahead.
I can enter CWM Recovery. However, I cannot mount sd card or usb storage or anything for that matter. If I try and install through .zip it says 'e can't mount sd card'. I can't format my sd card either, same problem of can't mount. I thought if I tried pushing a ROM in by ADB that might work.. It did transfer the file it showed that in the cmd window. However, CWM refuses to mount my sd card or my usb storage.
So basically, in essence, I'm locked out of my Nexus! Please please help. I'm really lost and confused now.
Thanks so much.
Alex

Similar problems below in this thread with solutions.
Let your phone sit for an hour with the battery out, Download Wug's Nexus Toolkit from the development section, download drivers from there and install stock boot img then re-root.
I have never seen it before but seems like this prob is coming up a lot lately. It can be fixed. Good luck.
Sent from my Galaxy Nexus using Tapatalk 2

Nexism said:
Similar problems below in this thread with solutions.
Let your phone sit for an hour with the battery out, Download Wug's Nexus Toolkit from the development section, download drivers from there and install stock boot img then re-root.
I have never seen it before but seems like this prob is coming up a lot lately. It can be fixed. Good luck.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks for your reply. I'm starting now. I have a doubt, how do I install stock? Since I can't seem to be able to mount anything..
"It can be fixed" - few words have given me this much hope in my life! Thanks a lot!
EDIT: I guess you mean flash through ADB right? Okay, let me try that. I really hope you are right. Some of those other problems lead to paying up! Ouch.

Hey! I just tried using WUGS.. for some reason it does not make the final boot and instead says: 'Fastboot Status - FAILWrite Fail' -- oh god.. I'm trying it again now..
Is there any other way out? :/

Okay, so now my recovery is also gone after using WUGS.. oh man. And the phone isn't starting up. Please please please help? I'm getting really desperate now.
EDIT: And it sucks that I can't post in the WUGS thread (http://forum.xda-developers.com/showthread.php?t=1766475) because I have less than 10 posts! fml.

can you boot into fastboot? If so then itnwasnthe same prob I had when I wiped my phone and SD in recovery. If you can boot into fastbootnthen makensurenyou leave the batt out format least an hour. If you installed Wug's drivers the bottom left corner ofnfastboot should give a message.
Sent from my Galaxy Nexus using Tapatalk 2

Nexism said:
can you boot into fastboot? If so then itnwasnthe same prob I had when I wiped my phone and SD in recovery. If you can boot into fastbootnthen makensurenyou leave the batt out format least an hour. If you installed Wug's drivers the bottom left corner ofnfastboot should give a message.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yes, I can get into fastboot - i'm leaving the battery out now - do you think i should try
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
and then flash everything again?
There is always a way to recover the nexus right? Even if it is hardbricked, right?
I really really appreciate your help.

I too have this problem but after a lot of battery pulls it does eventually start up. It just started happening all of a sudden. Ive heard that heating it up with a hair dryer or heatgun can help and also re-locking and un-locking the boot loader can help as it wipes the card. Could be worth a try.

Any luck Someone? I know it sux big time to feel like your phone is bricked. I am not a dev or expert but it sounds like the prob I had last week, when I posted no one replied so I ordered a GNex thinking all was lost. Before I activated my new phone I felt like I had to fix my nexus before getting started on my new phone and that's my situation. I don't want you to feel like the community has forgot you and thats why I'm trying to help. Were you able to get Wug's Toolkit to recognize your phone after leaving the batt out? I don't know why but I think that's the key. I had to leave mine overnight 'cause I don't have a PC and the next day at my friends house when I plugged the USB in I got that message at the bottom of fast boot "system normal" or something to that effect. Once recognized the stock boot IMG is what you need.
ANY ONE ELSE WHO HAS HAD THIS OR A SIMILAR ISSUE PLEASE GIVE SOME ADVICE. LET'S NOT LEAVE A COMMUNITY MEMBER WITH A LIFELESS PIECE IF PLASTIC. THANKS FORUM.
To set your mind at ease yes, I believe as long ad you have access to fastboot your nexus can be saved.
Sent from my Galaxy Nexus using Tapatalk 2

sounds to me like a hardware issue, since you haven't changed software and it seems like a brick. try flashing stock rom via fastboot, you should be able to google around how you can do that.

Blo0dyyy said:
sounds to me like a hardware issue, since you haven't changed software and it seems like a brick. try flashing stock rom via fastboot, you should be able to google around how you can do that.
Click to expand...
Click to collapse
Hi, if I'm not wrong essentially what WUG does automatically is what you do by fastboot (erase bootloader, cache, system.. and then flash all of them back) in both system fails to wipe and refuses to be flashed again (flashwrite error).
I don't want to lock it and then unlock it again because I read in other threads that it might lead to a permanent lock with an error for subsequent unlocking - that would leave me completely out.
Anyway, let's see - I've given it to someone to check it up. I'll keep you guys posted. He said he wanted to repartition the sd card.
My intuition says: hardware problem!

So I tried Odin today - and that also did not work it refused to flash the ROM. In the process I somehow managed to mess up the bootloader such that the phone would have some two lights on randomly when I switch on. It doesn't go into download mode either. I next plan to use JTAG to get the bootloader back and then reflash everything. Hopefully, that should sort things out. The Resurrection tool is amazing! I'll keep you guys posted.

Get it going someone?
Sent from my Galaxy Nexus using Tapatalk 2

I have the same problem as you, with the added difficulty of my phone not being recognized by anything other than fastboot. No ADB commands will function. It was charging, rebooted itself into a bootloop, and I have been struggling with it ever since. It is currently a worthless piece of plastic, my favorite phone ever, gone.
I can wipe and re-write recovery all that I want, but it seems as if the sdcard partition that /system and some other stuff writes too is either corrupted or physically damaged. Every time I flash it all via fastboot it all goes as stated, but gives me a fail message on the last two partitions and never allows me to actually write a new ROM or boot image. I wanted to try ODIN but can't seem to get it to recognize my phone in download mode...
Let me know if you have any success or progress!

someone. said:
So I tried Odin today - and that also did not work it refused to flash the ROM. In the process I somehow managed to mess up the bootloader such that the phone would have some two lights on randomly when I switch on. It doesn't go into download mode either. I next plan to use JTAG to get the bootloader back and then reflash everything. Hopefully, that should sort things out. The Resurrection tool is amazing! I'll keep you guys posted.
Click to expand...
Click to collapse
I myself am experiencing the same problem.... Did your cell got fixed.....?? Did JTAG worked kindly keep us posted em really concerned about it... coz your solution might get me some where or else i hav completely lost my phone ;(

Get it going someone?
Click to expand...
Click to collapse
Hey Nexism! Sorry for the late reply - things've been busy.
The JTAG is giving an internal voltage for some reason - so I've sent it for repair. It'll be repaired by tomorrow or so.. I'm then going to set it back up. It's all already soldered and all, just waiting for the JTAG. I think I've understood how this thing works now. So yeah, I'm hoping it's all sorted. Thanks a lot for your concern man.
I have the same problem as you, with the added difficulty of my phone not being recognized by anything other than fastboot.
Click to expand...
Click to collapse
Well my phone went blank - no fastboot mode - no download mode - no nothing - when i'd put the battery in randomly two of the four front lights would come on.. JTAG is going to solve the problem hopefully.

someone. said:
Hey Nexism! Sorry for the late reply - things've been busy.
The JTAG is giving an internal voltage for some reason - so I've sent it for repair. It'll be repaired by tomorrow or so.. I'm then going to set it back up. It's all already soldered and all, just waiting for the JTAG. I think I've understood how this thing works now. So yeah, I'm hoping it's all sorted. Thanks a lot for your concern man.
Well my phone went blank - no fastboot mode - no download mode - no nothing - when i'd put the battery in randomly two of the four front lights would come on.. JTAG is going to solve the problem hopefully.
Click to expand...
Click to collapse
So ladies and gentleman, JTAG also failed - apparently something was wrong with the sd card only. I got my motherboard replaced - luckily the guy I went to knew someone and Samsung and charged me Rs. 4,000 as opposed to the Rs. 8500 quoted by the Samsung Service Centre. Oh well.
Back on my Nexus now. XD

someone. said:
So ladies and gentleman, JTAG also failed - apparently something was wrong with the sd card only. I got my motherboard replaced - luckily the guy I went to knew someone and Samsung and charged me Rs. 4,000 as opposed to the Rs. 8500 quoted by the Samsung Service Centre. Oh well.
Back on my Nexus now. XD
Click to expand...
Click to collapse
I am with the same problem here... I cant turn off my phone or it get stuck in pre-boot phase. Acess recovery and cant mout sd card. Using last stable cm 10.
I think my sdcar is dead.

Same problem here. Around 8 out of 10 times I get stuck on the Google logo, 8 out of 10 times in recovery I can't mount SD card as well. And if I successfully boot, Media wakelocks and my battery drains in sleep as fast as if the screen were on. Please help.

For me I first noticed that my apps weren't using the SD partition. Tried to mount normally (fully loaded ROM) (ROM is SlimBean Beta2), but it would not mount. Went into CWM and tried to mount in there, but it would not work. tried to "Format /sdcard" but "Error mounting /sdcard". My phone still boots and runs fine, but I just don't have access to the SD partition. I don't want to do anything because I need my phone for business. Is there any PROVEN way to fix this yet?

[Q] OPO Boot Loop/Hang After Drop

I accidentally dropped my OPO face first from about chest height earlier today. The screen didn't break but now my phone is acting weird.
First, it was okay but after a few minutes, it hanged up and was on a boot loop. I tried a factory reset but now I'm unable to get wifi (wifi button is off with a orange square around it) and the boot loop and hanging still persists. The phone does heat up and seems to go out of the loop if its cool enough. Hangs up if it gets hot.
Any help on fixing this? I'm going to try a fresh install in a few minutes but I'm kinda feeling this is a hardware issue already.

The fact that it still does it even after doing a factory reset is concerning. Try doing a complete factory restore as per this thread and then also try this. If both fail to resolve the issue i suspect your hardware has been damaged and i don't see you fixing the issue one your own unfortunately.

Yeah, unfortunately I did both already. Installed stock build and the Audio FX fix. The Audio FX bug is still showing up though. Not sure if I have done anything wrong in replacing persist.img

brutalpanda said:
Yeah, unfortunately I did both already. Installed stock build and the Audio FX fix. The Audio FX bug is still showing up though. Not sure if I have done anything wrong in replacing persist.img
Click to expand...
Click to collapse
You could also try flashing this. Though i think its unlikely to fix the issue, you don't have anything to lose at this point...this also re-flashes the reserve4 partition.

S M G said:
You could also try flashing this. Though i think its unlikely to fix the issue, you don't have anything to lose at this point...this also re-flashes the reserve4 partition.
Click to expand...
Click to collapse
Just an update, my phone is now dead. After rebooting several times this morning, it suddenly lost power. Not even charging helps. No response from power button and can't even fastboot. I guess the main board got affected when it fell and fried itself up in the process.
Crap. I'm really sad about this..I'll probably try opening it up and see if anything got dislodged. You think that's a good idea?

brutalpanda said:
Just an update, my phone is now dead. After rebooting several times this morning, it suddenly lost power. Not even charging helps. No response from power button and can't even fastboot. I guess the main board got affected when it fell and fried itself up in the process.
Crap. I'm really sad about this..I'll probably try opening it up and see if anything got dislodged. You think that's a good idea?
Click to expand...
Click to collapse
I sorry to hear that bro, its a bummer. You might as well open it up yourself and see if you can find anything obvious wrong with it, or you could try and get in contact with OnePlus and find out if they can do a repair of sorts, but i wouldn't get my hopes up on that though.

aa

brutalpanda said:
aa
Click to expand...
Click to collapse
S M G said:
I sorry to hear that bro, its a bummer. You might as well open it up yourself and see if you can find anything obvious wrong with it, or you could try and get in contact with OnePlus and find out if they can do a repair of sorts, but i wouldn't get my hopes up on that though.
Click to expand...
Click to collapse
Well, it seems there's power. The phone is slightly hot when touching it. I tried plugging via PC and Windows recognizes there's a USB device although after trying to install drivers, it prompted me that the device was not recognized. Not sure what to do at this point though.

brutalpanda said:
Just an update, my phone is now dead. After rebooting several times this morning, it suddenly lost power. Not even charging helps. No response from power button and can't even fastboot. I guess the main board got affected when it fell and fried itself up in the process.
Crap. I'm really sad about this..I'll probably try opening it up and see if anything got dislodged. You think that's a good idea?
Click to expand...
Click to collapse
brutalpanda said:
Well, it seems there's power. The phone is slightly hot when touching it. I tried plugging via PC and Windows recognizes there's a USB device although after trying to install drivers, it prompted me that the device was not recognized. Not sure what to do at this point though.
Click to expand...
Click to collapse
As what does Windows' Device Manager show/identify the device ?

S M G said:
As what does Windows' Device Manager show/identify the device ?
Click to expand...
Click to collapse
My phone is back but still boot looping. Would installing other ROMs solve the problem? I won't be able to RMA this so it's not an option.

brutalpanda said:
My phone is back but still boot looping. Would installing other ROMs solve the problem? I won't be able to RMA this so it's not an option.
Click to expand...
Click to collapse
It could perhaps, but lets start here: Can you boot into fastboot mode? If YES does it reboot itself while in fastboot or is it actually stable as in it stays in fastboot?

S M G said:
It could perhaps, but lets start here: Can you boot into fastboot mode? If YES does it reboot itself while in fastboot or is it actually stable as in it stays in fastboot?
Click to expand...
Click to collapse
It's actually quite stable. I had never seen it reboot when in Fastboot. It's also worth mentioning that if I'm in Recovery Mode (TWRP installed), the phone also doesn't reboot.
I also noticed that ever since the drop/boot loop/hangs, my phone reboots very long (around 2-3 minutes it it does boot into the system; which happens less frequently than the boot loop). Before it took probably a minute at most to reboot.

brutalpanda said:
It's actually quite stable. I had never seen it reboot when in Fastboot. It's also worth mentioning that if I'm in Recovery Mode (TWRP installed), the phone also doesn't reboot.
I also noticed that ever since the drop/boot loop/hangs, my phone reboots very long (around 2-3 minutes it it does boot into the system; which happens less frequently than the boot loop). Before it took probably a minute at most to reboot.
Click to expand...
Click to collapse
Another update. So here's what I found out. My phone needs to be super cooled for it to work. I tried putting it in front of the air conditioner. If it's really cool, WIFI works. When it gets slightly warm, my phone hangs up. When it reboots, I lose wifi. After that, if I still don't cool it down, boot loops happens.
I'm not sure what's happening but it seems that it's an overheating issue perhaps?

brutalpanda said:
Another update. So here's what I found out. My phone needs to be super cooled for it to work. I tried putting it in front of the air conditioner. If it's really cool, WIFI works. When it gets slightly warm, my phone hangs up. When it reboots, I lose wifi. After that, if I still don't cool it down, boot loops happens.
I'm not sure what's happening but it seems that it's an overheating issue perhaps?
Click to expand...
Click to collapse
Well that is possible, i suppose. Maybe the heat-spreader moved away ever so slightly of the CPU, or isn't making good enough contact with it anymore which would lead to it not properly dissipating the heat. Unfortunately that i wont be able to know.
Lets assume that this is a software issue for now. Have you tried this yet by any chance ?
If not it is definitely worth a shot. Before flashing it i recommend clearing cache partition & dalvik cache in TWRP first then reboot into bootloader mode and then run this as per the READ ME file which is included.
There are essentially 3 batch file you need to run and it will recreate all the partitions on your device etc.
PS: You need to register on the OnePlus forums to actually be able to view the thread.
PPS: If for some reason the download link is bad let me know and ill mirror it for you on my dropbox.

S M G said:
Well that is possible, i suppose. Maybe the heat-spreader moved away ever so slightly of the CPU, or isn't making good enough contact with it anymore which would lead to it not properly dissipating the heat. Unfortunately that i wont be able to know.
Lets assume that this is a software issue for now. Have you tried this yet by any chance ?
If not it is definitely worth a shot. Before flashing it i recommend clearing cache partition & dalvik cache in TWRP first then reboot into bootloader mode and then run this as per the READ ME file which is included.
There are essentially 3 batch file you need to run and it will recreate all the partitions on your device etc.
PS: You need to register on the OnePlus forums to actually be able to view the thread.
PPS: If for some reason the download link is bad let me know and ill mirror it for you on my dropbox.
Click to expand...
Click to collapse
Yeah, unfortunately I have the 16GB version. Any chance what's the difference? Is it just the userdata.img?

[Q] Bricked my One XL by flashing the wrong boot.img file

I was following Timmaaas 'How To' guide to a tee when I got to step #5 and and did the Reboot to find that my phone is now bricked. I was racking my brain trying to understand what I did wrong and I realize that I used the wrong Boot.img file when I flashed it!
I was having issues during the entire process and realized it was because I was using the CyanogenMod One X ROM instead of the XL. This was causing me to get an 'Error 7' until I switched to the XL and everything downloaded fine. However, I completely forgot to replace the Boot.img and ended up flashing my phone with the One X boot.img instead of the XL!
The phone is not responding at all. I did have it plugged into the computer and after it became bricked my computer downloaded the Qualcomm USB drivers for 9006 but its still not responding at all.
Is there anything I can do? It seems like all I need to do is change that one boot file and I would be golden. Please keep in mind this is my first Root so if you know of a way to fix I would really appreciate it if you can teach me in simple terms if possible.
Thanks so much! I really appreciate all you guys do at XDA you help an enormous amount of people. A donation from me is on the way! :good:
EDIT: I kept messing with the power button trying to boot it over and over and finally it launched to HTC one entry screen with the red text for a little less then 1 second but then shut back off. Maybe this gives some hope?

You're gonna need to get a jtag repair done. There's just no way for you to get the device to the bootloader in order to flash the right boot.img because it won't boot due to you borking the boot partition.
Transmitted via Bacon

BrickedAmbitions said:
EDIT: I kept messing with the power button trying to boot it over and over and finally it launched to HTC one entry screen with the red text for a little less then 1 second but then shut back off. Maybe this gives some hope?
Click to expand...
Click to collapse
Are you able to issue adb commands? If you're seeing the splash screen then you may not be completely bricked. If the device is still showing as qualcommUSB then you're likely out of luck though.

nem1yan said:
Are you able to issue adb commands? If you're seeing the splash screen then you may not be completely bricked. If the device is still showing as qualcommUSB then you're likely out of luck though.
Click to expand...
Click to collapse
No I can't issue any commands. I guess its toast, oh well. How do I get the jtag repairs done?

nem1yan said:
Are you able to issue adb commands? If you're seeing the splash screen then you may not be completely bricked. If the device is still showing as qualcommUSB then you're likely out of luck though.
Click to expand...
Click to collapse
There's no way the phone can get to the bootloader, it ain't gonna happen with a broken boot partition.
BrickedAmbitions said:
No I can't issue any commands. I guess its toast, oh well. How do I get the jtag repairs done?
Click to expand...
Click to collapse
You need to find a jtag repairer in your area.
Transmitted via Bacon

ANOTHER Bricked TF300T

Well guys i don't like to bother with this, i love to read and this isn't the first time i have problem with this tablet.
A beautiful fully functional TF300T just stopped working today.
Lost battery, now when i turn it on ASUS logo stucks, but NO with "device is unlocked" as happened to me with other devices, now the loading circle keeps looping.
I searched US drivers for my tablet (TF300T-US_epad-10_6_1_27_5-UpdateLauncher.zip), downloaded it and renamed to EP300_SDUPDATE.ZIP on a FAT 32 SD card.
When i press on + vol down, fastboot enables but RCK says ERROR.
Please, can anybody give me a quick hand? In a few hours i leave on my first vacations in ages and TF300T was goin to be a great member of the team.
THANKS.

I picked up a bricked one and with out too much reading I just did a factory reset with in the boot loader.. no 3 on the menu... what ever was wrong with the internal Rom seemed to come good and it booted.. So maybe you could read a little about this and try.. but bummer it happened before you go away as nothing more painful as you would have had it setup with movies and reading.. but anyway.. thats how I got this one to work... once I had it factory reset, then I flashed new Roms to it.. Actually it wasnt unlocked either and had to get Asus to reset thier database so I could unlock it..

dgcruzing said:
Actually it wasnt unlocked either and had to get Asus to reset thier database so I could unlock it..
Click to expand...
Click to collapse
sorry dear user but what do you mean with this =| ?

You can try to flash firmware through fastboot (try first without "erase" lines to keep Your data). Link

Oesterheld said:
sorry dear user but what do you mean with this =| ?
Click to expand...
Click to collapse
Yours you have indicated was unlocked so don't worry about that..
But there is plenty in the threads on it..

Code:
Graiden05 said:
You can try to flash firmware through fastboot (try first without "erase" lines to keep Your data). Link
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
That worked beautiful. Thanks very much.
Now i can finish a few scrips and watch the mentalist on my 8hs bus ride. THANKS.

I cannot even get into fastboot on mine. All it does is stay on the bootloader startup image. And then stays there. If anyone knows how to fix this please help me out. L

Oneplus One keeps rebooting

Recently my screen's digitizer broke, so I ordered a new screen and just got it today.
I replaced it and I tested it, it turned on and that, but when I try to boot it just come with the onplus logo and powered by android stuff in the bottom and that's the only thing it's showing with it just turns off and on basically rebooting
So I tested, can it go into fastboot it could so I tried flashing twrp on but didn't work keeps doing the same cannot even enter recovery just fastboot.
Anyone tried this before or, what can I do to fix it if there is a possible fix for it.

Have you tried flashing official images from fastboot? hopefully not a hardware issues

I'm having the same problem, also since today. My phone just got in a bootloop while powered on and running completely fine. Trying to boot into recovery also gets me a bootloop. Fastboot works, and when i try to flash anything it tells me it succeeds. Then when i try to power on again, still the same bootloop.
I've tried the Oneplus Recovery Tool, same thing. Everything succeeds, but I still end up with a bootloop. The logo on the fastboot page had changed, though, so I'm guessing the flash was successful, but something else is broken.
I'm actually really worried about my phone right now.

morreion said:
I'm having the same problem, also since today. My phone just got in a bootloop while powered on and running completely fine. Trying to boot into recovery also gets me a bootloop. Fastboot works, and when i try to flash anything it tells me it succeeds. Then when i try to power on again, still the same bootloop.
I've tried the Oneplus Recovery Tool, same thing. Everything succeeds, but I still end up with a bootloop. The logo on the fastboot page had changed, though, so I'm guessing the flash was successful, but something else is broken.
I'm actually really worried about my phone right now.
Click to expand...
Click to collapse
You tried one plus recovery tool cm11s?

Mr.Ak said:
You tried one plus recovery tool cm11s?
Click to expand...
Click to collapse
Yep, that's the one. Everything seems to work fine, all the bars are loading, and the device turns green. Unplugged the device, booted up, still a bootloop.
I tried the ColorOS guide (https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732) too, same thing. The boot logo did turn red though.

morreion said:
Yep, that's the one. Everything seems to work fine, all the bars are loading, and the device turns green. Unplugged the device, booted up, still a bootloop.
I tried the ColorOS guide (https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732) too, same thing. The boot logo did turn red though.
Click to expand...
Click to collapse
If even that tool couldn't solve it then it's definitely a hardware issue.

Mr.Ak said:
If even that tool couldn't solve it then it's definitely a hardware issue.
Click to expand...
Click to collapse
Damn. Well, too bad. I'm going to try to fix my phone for a bit more, not that I think it's still fixable. Thanks!

I also think it is a hardware issue but I don't want it to be :/
It's just funny but I think I found it, its the power button because apparently the button itself got off the wire so maybe I can sort it on again.
Or maybe it could be something else but cannot seem to find it.
I maybe u try to get my friend to sort a new storage chip on if I can get I contact with him wish me luck

morreion said:
Damn. Well, too bad. I'm going to try to fix my phone for a bit more, not that I think it's still fixable. Thanks!
Click to expand...
Click to collapse
Just get your device checked from a local source and then replace the decayed part yourself.
AFAIK,it can be either battery or Motherboard/Logic board.
---------- Post added at 09:07 PM ---------- Previous post was at 09:06 PM ----------
Melonendk said:
I also think it is a hardware issue but I don't want it to be :/
It's just funny but I think I found it, its the power button because apparently the button itself got off the wire so maybe I can sort it on again.
Or maybe it could be something else but cannot seem to find it.
I maybe u try to get my friend to sort a new storage chip on if I can get I contact with him wish me luck
Click to expand...
Click to collapse
Best of luck!

I am encountering the same problem. Out of nowhere my phone started rebooting. It reboots ok and after a minute it does it again...so it is working alright for a minute. However, my phone is completely stock Cyanogen OS...
I have tried this, but it did not work for me.

diosak said:
I am encountering the same problem. Out of nowhere my phone started rebooting. It reboots ok and after a minute it does it again...so it is working alright for a minute. However, my phone is completely stock Cyanogen OS...
I have tried this, but it did not work for me.
Click to expand...
Click to collapse
If it does work alright for a minute every time, I don't think you have the same problem as I have.