i went to boot up my transformer this morning and it just won't turn on...
Yes it is fully charged
and it only boots to recovery :S
what can i do to reset it all the way to factory settings as if its never been used ?
any help is much appreciated
thanks
is it a rootable version?
Sent from my Transformer TF101 using Tapatalk
First of all, I don't understand this new movement of being as vague as possible to keep the rest of us guessing. Can you imagine going to the doctor and then tell the doctor "I am sick, I won't tell you anything else, try to guess what's wrong with me!"?
First of all, do you have cwm installed? When you say only boots into recovery, which one? What does the screen look like? what options do you have?
But in short, it sounds like you got an apx bootloop, which is really bad. I've worked on a number of tegra 2 tablets with apx bootloop. Half of these are not recoverable. And no one have figured out what causes apx bootloop.
goodintentions said:
First of all, I don't understand this new movement of being as vague as possible to keep the rest of us guessing. Can you imagine going to the doctor and then tell the doctor "I am sick, I won't tell you anything else, try to guess what's wrong with me!"?
First of all, do you have cwm installed? When you say only boots into recovery, which one? What does the screen look like? what options do you have?
But in short, it sounds like you got an apx bootloop, which is really bad. I've worked on a number of tegra 2 tablets with apx bootloop. Half of these are not recoverable. And no one have figured out what causes apx bootloop.
Click to expand...
Click to collapse
why you so mean? be nice man
goodintentions said:
First of all, I don't understand this new movement of being as vague as possible to keep the rest of us guessing. Can you imagine going to the doctor and then tell the doctor "I am sick, I won't tell you anything else, try to guess what's wrong with me!"?
First of all, do you have cwm installed? When you say only boots into recovery, which one? What does the screen look like? what options do you have?
But in short, it sounds like you got an apx bootloop, which is really bad. I've worked on a number of tegra 2 tablets with apx bootloop. Half of these are not recoverable. And no one have figured out what causes apx bootloop.
Click to expand...
Click to collapse
APX Boot loop? Ive never heard of that but wouldnt that mean it would turn on then turn off without getting to recovery? I thought if you could get to recovery you could still hook it up and use nvflash to re write the memory?
mediumsteak said:
why you so mean? be nice man
Click to expand...
Click to collapse
I am nice. How else am I going to tell people to stop being so vague?
---------- Post added at 11:27 AM ---------- Previous post was at 11:25 AM ----------
Danzano said:
APX Boot loop? Ive never heard of that but wouldnt that mean it would turn on then turn off without getting to recovery? I thought if you could get to recovery you could still hook it up and use nvflash to re write the memory?
Click to expand...
Click to collapse
That's the scary thing about permanent apx bootloop. No amount of flashing or nvflashing will fix it.
mediumsteak said:
why you so mean? be nice man
Click to expand...
Click to collapse
I don't think that was mean. People need to provide more information if they want someone to help them. Anyways he sounds like he has experience with something similar so he really IS trying to help
firstly i apologise for being so vague...
Yes it is routable version
i dual booted linux on it if that helps ? which i know uses apx
strange thing is if i install a rom it will boot up to the rom fine until i turn off the transformer and try to turn it back on again where the power button does nothing ?
maybe i didn't uninstall linux correctly ? how would i go about doing this ?
goodintentions said:
I am nice. How else am I going to tell people to stop being so vague?
---------- Post added at 11:27 AM ---------- Previous post was at 11:25 AM ----------
That's the scary thing about permanent apx bootloop. No amount of flashing or nvflashing will fix it.
Click to expand...
Click to collapse
So if it goes into apx boot loop you would need to do a factory force flash which only asus can do and woulldnt because you have voided your warrenty that sucks !!!!!
Is there anyway we could develope something similar to what they have to force flash in worst case senarios or is it that bad ????
Also back to original question did you use the uninstall linux or the uninstall linux and blobs be gone because right there could be your whole problem.
Sent from my tf101 using xda premium 1.59Ghz
icow said:
firstly i apologise for being so vague...
Yes it is routable version
i dual booted linux on it if that helps ? which i know uses apx
strange thing is if i install a rom it will boot up to the rom fine until i turn off the transformer and try to turn it back on again where the power button does nothing ?
maybe i didn't uninstall linux correctly ? how would i go about doing this ?
Click to expand...
Click to collapse
Bad news for you. You are in permanent apx bootloop. In which case, you are screwed. Perhaps someone else who have dealt with permanent apx bootloop have figured out a way to fix it. I have not. And I've dealt with several such weird creatures.
Here is what you will do if no one else can help you.
Contact asus and tell them that your transformer has stopped turning on and get an RMA. Do not tell you them you have rooted it and other things. Just tell them one day it stopped turning on.
Nvflash back to stock. Boot it up once. Then turn off your transformer and try to boot up again. At this point, you are back in permanent apx bootloop. Send it in. After asus people play with it for a while, chances are they will send you a new device. This is the same advice I gave to a couple people, and at least one of them had a new device from asus.
If you are still within return period from whoever you bought this from, exchange it for another one.
Permanent apx bootloop is weird. There's been much discussion among those of us who have dealt with this strange phenomenon. No one I know of have been able to figure out a definate way to bring it out of this state. The successes I mentioned were done by doing random things to them.
Curious, how did you manage to get it into permanent apx bootloop? I'm still investigating this phenomenon. Can you be as specific as you can? So far, there seems to be no pattern whatsoever. Some people have described it as just waking up one morning and boom apx bootloop. Some people brought it to this state while trying to root. Some did this while using rom manager. Etc.
All tegra 2 devices are susceptible to permanent apx bootloop. I'm sure asus is aware of this.
---------- Post added at 01:47 AM ---------- Previous post was at 01:40 AM ----------
Danzano said:
APX Boot loop? Ive never heard of that but wouldnt that mean it would turn on then turn off without getting to recovery? I thought if you could get to recovery you could still hook it up and use nvflash to re write the memory?
Click to expand...
Click to collapse
That's why we call it permanent apx bootloop. It goes straight into apx mode instead of going through the normal booting process.
Can one get into a permanent apx bootloop even if the tf was never put into apx mode or is it one of those things that just happened?
I tried using easyflasher to return to a stock ROM. After it was completed it said to reboot. Now it is in permanent APX mode and I have tried multiple firmwares and nothing.
Sent from my DROID BIONIC using xda app-developers app
Related
i rooted it after the ics ota using vipermods root program (cant remember what its called) and now its stuck in CMW and wont reboot past that. i learned that this version of CMW for the transformer has those issues and found a thread thats like a support thread and has ways to fix it. i tried all the methods it gave me and non seemed to work. Im posting this here instead of on that thread cause im hoping for some more direct help. Any idea?
Also: I am a total noob at using ADB and stuff so youll have to bear with me.
Hold the volume down key immediately after pressing "Reboot now" in CWM. When the white letters start at the top left you can let go. Choose to boot to Android.
After that you should be able to connect using adb. That will be the key in using adb in CWM. Once you get adb running you can reboot, run the adb script to stop the reboot and fix that nasty boot issue.
Good luck.
Sent from my Transformer TF101 using xda premium
you wouldnt happen to be able to post that script would you?
SynysterSilence said:
you wouldnt happen to be able to post that script would you?
Click to expand...
Click to collapse
Go here
http://forum.xda-developers.com/showthread.php?t=1530337
this is actually the thread i was using before that wasnt working, but with the new info that wolftroy1 gave me ill give it another go and see if it works.
SynysterSilence said:
this is actually the thread i was using before that wasnt working, but with the new info that wolftroy1 gave me ill give it another go and see if it works.
Click to expand...
Click to collapse
If you can cold boot into the OS you can use Terminal emulator also if you're not good with ADB.
Do what wolftroy1 stated above, if you can't get it working that way just turn your tablet totally off.
Now push and hold VOl down plus power button
When you see words scrolling at top left
wait a bit till you see option to wipe data or cold boot
choose cold boot to see if you can get into the OS
im cold booting into linux (thats what it said when i chose Android when it gave me the option between Wipe Data and Android) and its been about 5 minutes. its still at that same screen. How long is this boot supposed to take?
It shouuldnt take more than 10 minutes or so.
Sent from my Transformer TF101 using xda premium
little help?
i'm having a really weird issue wondering if you blokes could help
I can boot my memo pad. like it starts normally without problems, however when I get to my unlock screen I get spammed with the messages "unfortantly system UI has stopped" and "unfortantly launcher has stopped" when i unlock it it freezes until i press power and lock it again
tried reinstalling launcher and UI from computer. same issue
bob mc bob said:
i'm having a really weird issue wondering if you blokes could help
I can boot my memo pad. like it starts normally without problems, however when I get to my unlock screen I get spammed with the messages "unfortantly system UI has stopped" and "unfortantly launcher has stopped" when i unlock it it freezes until i press power and lock it again
tried reinstalling launcher and UI from computer. same issue
Click to expand...
Click to collapse
Wrong forum, this is for TF101 - but sounds like corrupted apps
I would backup and factory reset
*Detection* said:
Wrong forum, this is for TF101 - but sounds like corrupted apps
I would backup and factory reset
Click to expand...
Click to collapse
tried that, do I need to reflash the rom? or is that going to far? I'm using the stock android 4.2.1
---------- Post added at 08:28 PM ---------- Previous post was at 08:15 PM ----------
*Detection* said:
Wrong forum, this is for TF101 - but sounds like corrupted apps
I would backup and factory reset
Click to expand...
Click to collapse
tried didn't help. do I need to reflash the rom? or is that a little overkill?
bob mc bob said:
tried that, do I need to reflash the rom? or is that going to far? I'm using the stock android 4.2.1
---------- Post added at 08:28 PM ---------- Previous post was at 08:15 PM ----------
tried didn't help. do I need to reflash the rom? or is that a little overkill?
Click to expand...
Click to collapse
If you have the ability to reflash, then yes, I would reflash if resetting has failed
So, Recently a family member of mine told me something was wrong with their transformer. I take a look at it and it's not turning on so i assume it's not charged. I plug in the charger and it does not boot up. The transformer only goes to the eeepad screen with the asus logo and shuts off again. Basically it's in a bootloop but problem is, the tf101 is not rooted or tampered with and on stock fw (Tf101 is a b90 model) Anything i can do to fix??? Couldn't have been any sort of virus either as this transformer was only used for video streaming/ listening to music...
http://www.youtube.com/watch?v=DgCRfgGpwBw&feature=youtu.be
It might need to be reflashed. You could try using the wheelie tool, but the internal storage will be wiped. Sounds like a softbrick.
Sent from my Transformer TF101 using xda premium
I had exactly the same problem this week . . . this solved it:
http://forum.xda-developers.com/showthread.php?t=1620758
Reflash with NvFlash. Best idea as of now
Hey there,
I have nearly the same problem but my transformer just gets the first screen and then it tries to reboot.
I tried to reflash it with EasyFlasher but it didnt work. Is there a chance that your way will work?
If you can get ADB peri Might work, but just manually do it with NvFlash.
thanks, i'll try that when I hit back home in three days...
It is possible to get it in APX mode, so just put it on and flash?
Do you know why such a big problem occurs? It was on stock firmware and rooted for the last 5 months...
I'm starting to think my issue is related to condensation.
I started leaving the transformer in my bedroom, since my wife gave her tablet to her mother and is now using my transformer to read.
I was happy on HC, stock, non-rooted. My tablet was working with no issues for 3 months, give or take.
But then I started having random reboots and boot loops. Tried almost all roms for the transformer, same issue. Worked fine on the day I installed, got me bootloops the next day.
Today I thought about condensation after getting another round of boot loops and noticing my tablet screen with a bit of humidity. The temperature difference from my bedroom with A/C to my living room with no A/C can get to 15 or 20 celsius.
So I got the bootloop again today and instead of nvflashing the hell out of it as I have been doing, I put it in APX mode (since I have no recovery ATM, so I couldn't power it off) and leave it resting for 3 hours in room temperature. After that I rebooted it and it is now stable again. I will try to confirm those suspicious, but right now it sounds a lot like it for me. It never slept in the bedroom during the 3 months I was in HC.
theares2014 said:
thanks, i'll try that when I hit back home in three days...
It is possible to get it in APX mode, so just put it on and flash?
Do you know why such a big problem occurs? It was on stock firmware and rooted for the last 5 months...
Click to expand...
Click to collapse
I'm really not sure, but yes just download a stock nvflashable fw (xdafileserver.nl has some good ones) and put in nvflash mode and run reflash_sbkv#.bat (be sure to import wheelie into the stock fw folder and overwrite)
--
Regarding condensation, that's odd, but mabye. ..
Thanks, i'll try this when I am at home.
It is in APX mode but the computer doesnt recognise it... it says unknown device...
What shall i do?
That means the drivers are wrong/bad. Did you install any? You need the Universal Naked Drivers. (Search the tf themes and apps forum)
I installed the Asus PC Suite which means that drivers are inclueded, but I am going to search here if you say they are here.
Anyways, I can not find them there...
No, asus drivers is not what you need, you want the universal naked drivers: http://forum.xda-developers.com/showthread.php?t=1514942&highlight=universal+naked
well, that sounds quite nooby but how to install this drivers... i see several different files but absolutley no exe...
it is so embarrassing...
pnputil -a android_apxdriver.inf (or whatever the inf is called)
then plug in the tf
I opened it but nothing changes... the transformer in apx mode is still an unknown device
Have you tried 'update driver' in device manager, then point to the folder with the apx driver?
sure...
same problem with rebooting
I have exactly same problem...! My TF101 is B70 model and NVFlash not work with this model and higher... How I can fix it? is Megatron 1.1.6 installed on tablet and I have rom on sdcard, but reinstall rom not helped me, also wipe + reinsatll...
any ideas?
---------- Post added at 11:53 PM ---------- Previous post was at 11:06 PM ----------
http://forum.xda-developers.com/showthread.php?t=1688012
this is helped me...!!!
Hello everybody,
I hope that someone can give me some advise to get my tf300t up and running again. I wanted to install cm10.2 but I wanted to install CWM first.
I unlocked my device first with the unlock app v8 from asus.
I tried to install CWM the first time but it did not work.
I went back into recovery mode but I wasn't paying attention and pressed wipe userdata
Now my tf300t only shows the ASUS logo and the text that the device is unlocked. I can't get back in recovery mode anymore. Is there a way the restore it back to default?
I hope that someone can help me out.
Thank you in advance for your time and effort.
Regards
Burner1977
burner1977 said:
Hello everybody,
I hope that someone can give me some advise to get my tf300t up and running again. I wanted to install cm10.2 but I wanted to install CWM first.
I unlocked my device first with the unlock app v8 from asus.
I tried to install CWM the first time but it did not work.
I went back into recovery mode but I wasn't paying attention and pressed wipe userdata
Now my tf300t only shows the ASUS logo and the text that the device is unlocked. I can't get back in recovery mode anymore. Is there a way the restore it back to default?
I hope that someone can help me out.
Thank you in advance for your time and effort.
Regards
Burner1977
Click to expand...
Click to collapse
Can you get to the menu with the recovery options, boot android, USB, and wipe data? You can use fastboot from there.
cmendonc2 said:
Can you get to the menu with the recovery options, boot android, USB, and wipe data? You can use fastboot from there.
Click to expand...
Click to collapse
thank you for your response. No I can't get in there. any suggestions?
thx for your advise
burner1977 said:
thank you for your response. No I can't get in there. any suggestions?
thx for your advise
Click to expand...
Click to collapse
If you cant get into there, you cant really use fastboot. Unless you made NvFlash Backups beforehand, I don't think there is much else you can do, since the recovery isn't working either.
cmendonc2 said:
If you cant get into there, you cant really use fastboot. Unless you made NvFlash Backups beforehand, I don't think there is much else you can do, since the recovery isn't working either.
Click to expand...
Click to collapse
I stupidly made no backups so what you are saying is that it is done.
burner1977 said:
I stupidly made no backups so what you are saying is that it is done.
Click to expand...
Click to collapse
I've spent a lot of time searching and it seems like that's it...
I'm on Asus screen, I can reboot it by either holding down pwr button until it reboots, or using reset switch with a paperclip. vol - does nothing, just reboots to asus screen...computer sees nothing. vol + goes into APX mode (blank screen)...computer detects with correct drivers. I've tried draining battery completely...disconnecting battery for a few days...same result.
If I had to speculate...maybe at some point someone will figure out how to use another's backup files and push them to the device in APX mode.
I've looked into replacing the motherboard...and have seen some for as low as 50$ on ebay. Personally, swapping them would be easy...but some may not have the caviler attitude with hardware swapping. Just gotta get the wife to agree to spend the $.
I'd die for a free fix, the kids really miss playing with the thing
coppervines said:
I've spent a lot of time searching and it seems like that's it...
I'm on Asus screen, I can reboot it by either holding down pwr button until it reboots, or using reset switch with a paperclip. vol - does nothing, just reboots to asus screen...computer sees nothing. vol + goes into APX mode (blank screen)...computer detects with correct drivers. I've tried draining battery completely...disconnecting battery for a few days...same result.
If I had to speculate...maybe at some point someone will figure out how to use another's backup files and push them to the device in APX mode.
I've looked into replacing the motherboard...and have seen some for as low as 50$ on ebay. Personally, swapping them would be easy...but some may not have the caviler attitude with hardware swapping. Just gotta get the wife to agree to spend the $.
I'd die for a free fix, the kids really miss playing with the thing
Click to expand...
Click to collapse
I'm on the same boat, this morning I was trying to install CyanogenMod following the instructions and wipped the tablet... I only have APX connection now with no backups...
Hey guys, I recently found my tf300t tucked away somewhere. Haven't used it for absolute months! And I remembered why, I kept having problems with CM somehow(I believe the last update was somewhere in June-July of 2013), so this time after charging it and wanting to do it all again, I figured I'd get it updated. Seeing as it's been nearly a year and so much crap has changed, I figured something was going to go wrong. Before I even DID ANYTHING, I told the tablet to reboot into recovery mode, and boom that's where I'm stuck. The Tablet rebooted and now only shows the Asus boot screen... Nothing else! Vol down+pwr didn't work, nothing. And If I hold the power button it shuts off but then turns right back on 1-2 seconds later. I'm not sure what this is, a soft brick? a Brick? just an error? Can anybody please help? I know this is probably the wrong section, but I'm just frustrated.
Thank you to anybody who can help in any shape or form.
PS: no bashing is needed, my tables already bashing my head for me.
Amirocassar said:
Hey guys, I recently found my tf300t tucked away somewhere. Haven't used it for absolute months! And I remembered why, I kept having problems with CM somehow(I believe the last update was somewhere in June-July of 2013), so this time after charging it and wanting to do it all again, I figured I'd get it updated. Seeing as it's been nearly a year and so much crap has changed, I figured something was going to go wrong. Before I even DID ANYTHING, I told the tablet to reboot into recovery mode, and boom that's where I'm stuck. The Tablet rebooted and now only shows the Asus boot screen... Nothing else! Vol down+pwr didn't work, nothing. And If I hold the power button it shuts off but then turns right back on 1-2 seconds later. I'm not sure what this is, a soft brick? a Brick? just an error? Can anybody please help? I know this is probably the wrong section, but I'm just frustrated.
Thank you to anybody who can help in any shape or form.
PS: no bashing is needed, my tables already bashing my head for me.
Click to expand...
Click to collapse
Does it respond to being plugged into a computer? Try pressing the reset button and then doing the vol down to get into fastboot.
cmendonc2 said:
Does it respond to being plugged into a computer? Try pressing the reset button and then doing the vol down to get into fastboot.
Click to expand...
Click to collapse
Nope, but I am running W8 and I read that W8 kinda sucks for this sort of thing. Like you need W7 or XP? Correct me if im wrong. Any other ideas? . I didn't do anything! Just told it to reboot into recovery, and now I'm stuck there. I held pwr+volume down and it still keeps stuck, and if I try to power it off then it just turns on again a few seconds later.
Amirocassar said:
Nope, but I am running W8 and I read that W8 kinda sucks for this sort of thing. Like you need W7 or XP? Correct me if im wrong. Any other ideas? . I didn't do anything! Just told it to reboot into recovery, and now I'm stuck there. I held pwr+volume down and it still keeps stuck, and if I try to power it off then it just turns on again a few seconds later.
Click to expand...
Click to collapse
I have the same issue more or less...
Mine will not go into fastboot
kingrat said:
I have the same issue more or less...
Mine will not go into fastboot
Click to expand...
Click to collapse
I also have this issue
??
So none of you can get to fastboot or recovery, but you do all get the stuck at Asus logo?? All your bootloaders are unlocked?? All of you got to this spot, the same way by not using the tablet for long periods of time???? What bootloader are you on?? What version of CM are you running??? What is the OS of your PC, If its not the top 3 please be specific......Are you using a stock asus data cable??
Sounds similar
From what your posts say, it sounds like something i came across. I struggled for hours trying to figure out this dilemma, but if you're in the same situation i was in then as long as you're in that screen even after trying to hold the power and -vol let it sit there, plug in and make sure you have all your files associated with fastboot platform installed and try pushing the new TWRP ( http://www.androidfilehost.com/?fid=23329332407569892 ) to your tablet, for some reason after a certain update after 4.1 i believe? CWM stopped working for me, so try pushing the new TWRP from that link there and possibly you should be able to gain control of your tablet again and start installing the new packets for CM 11. I found this to be very helpful http://forum.xda-developers.com/showthread.php?t=2570965 and thanks to "cmendonc2", 6 post down, he really cleared things up with his simple links. Hope you're in the same boat as i was. Good luck
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.