Related
Alright, this issue has seriously driven me insane over the last few days, and today it's gotten to the point where I'm going to do something I'll regret if somebody can't help me out. As you can tell, I'm pretty desperate.
Using Fresh 3.5.0.1, I've encountered more reboots than I can count. Whether it's checking an email or playing Asphalt, the phone frequently decides it doesn't want to cooperate and restarts itself. I decided to try to get rid of the reboots for good today with a complete wipe and new rom.
First, I made a nandroid backup, followed by a data/system wipe and cache/dalvik cache wipe. Afterward, I flashed the ZenDroid 1.1.0 kernel in case that was the issue. I then proceeded to flash CyanogenMod 7 RC1 with gapps.
That worked for all of three minutes, and then it got even worse. The phone started restarted itself when I wasn't even doing anything, up to the point where it would restart on the CM7 boot animation. I took my rage out on a nearby pillow and decided to try something else.
I downloaded the final release MIUI rom and used Calkulin's format all to wipe my phone as instructed. This time around I flashed Savage-Kernel 1.6 along with MIUI. Lo and behold, after rebooting I was finally able to swipe through the home screens again.
And then I wasn't. It started rebooting on the boot animation again. At the moment it's even worse, rebooting three seconds into the damned splash screen. I've tried keeping the battery pulled for half an hour with the HTC battery and two after market batteries. I wiped the ext partition on the micro sd card. I even physically removed the card itself. This effing phone is still rebooting on the splash screen.
I'm at the end of my wits. All I want is for my Evo to WORK, without any constant reboots or force closes that make it utterly unusable outside. If anyone could help me out with this issue, I'd be extraordinarily grateful.
Mecha2142 said:
Alright, this issue has seriously driven me insane over the last few days, and today it's gotten to the point where I'm going to do something I'll regret if somebody can't help me out. As you can tell, I'm pretty desperate.
Using Fresh 3.5.0.1, I've encountered more reboots than I can count. Whether it's checking an email or playing Asphalt, the phone frequently decides it doesn't want to cooperate and restarts itself. I decided to try to get rid of the reboots for good today with a complete wipe and new rom.
First, I made a nandroid backup, followed by a data/system wipe and cache/dalvik cache wipe. Afterward, I flashed the ZenDroid 1.1.0 kernel in case that was the issue. I then proceeded to flash CyanogenMod 7 RC1 with gapps.
That worked for all of three minutes, and then it got even worse. The phone started restarted itself when I wasn't even doing anything, up to the point where it would restart on the CM7 boot animation. I took my rage out on a nearby pillow and decided to try something else.
I downloaded the final release MIUI rom and used Calkulin's format all to wipe my phone as instructed. This time around I flashed Savage-Kernel 1.6 along with MIUI. Lo and behold, after rebooting I was finally able to swipe through the home screens again.
And then I wasn't. It started rebooting on the boot animation again. At the moment it's even worse, rebooting three seconds into the damned splash screen. I've tried keeping the battery pulled for half an hour with the HTC battery and two after market batteries. I wiped the ext partition on the micro sd card. I even physically removed the card itself. This effing phone is still rebooting on the splash screen.
I'm at the end of my wits. All I want is for my Evo to WORK, without any constant reboots or force closes that make it utterly unusable outside. If anyone could help me out with this issue, I'd be extraordinarily grateful.
Click to expand...
Click to collapse
hmm...
i don't know what kernel fresh comes with, but both of the other kernels are more aggressive ones, and i would guess your phone doesn't like them. i would try this:
Wipe twice using calk, wipe again using recovery, flash mikfroyo or stock rooted (stock kernel). If you still get reboots... unroot and take your phone back in because its a hardware problem.
I had this problem. Drove me insane. Ultimately just unrooted and got a new one from sprint. Not one reboot since I got the new one.
Sent from my PC36100 using XDA App
Well I'm still super new to the whole flashing of the ROM's. But from what you have explained the only thing I can think of is that you missed a step when you rooted your phone. Because of this that is why your phone keeps brick. You should go and check out HTC EVO Hacks (go Google it) and the guy who runs the site made a sweet video & write-up on how to root your phone. Just re-do everything and follow directions, then when your done just flash Kings Unleashed. And when you check out the HTC EVO hacks root page look for the link to the XDA root forum which has more info on how to root your HTC the proper way.
Sent from my PC36100 using XDA App
aimbdd said:
hmm...
Wipe twice using calk, wipe again using recovery, flash mikfroyo or stock rooted (stock kernel). If you still get reboots... unroot and take your phone back in because its a hardware problem.
Click to expand...
Click to collapse
Yeah, I guess I should try the stock rooted rom. If I'm only able to use that instead of any other custom rom, though, I'm going to lose it. There's something inherently frustrating about a device refusing to work for no apparent reason.
chickut123 said:
I had this problem. Drove me insane. Ultimately just unrooted and got a new one from sprint. Not one reboot since I got the new one.
Click to expand...
Click to collapse
I'm sort of hoping I won't have to do that, considering I'll likely get a refurbished unit.
Fredrow425 said:
But from what you have explained the only thing I can think of is that you missed a step when you rooted your phone. Because of this that is why your phone keeps brick. You should go and check out HTC EVO Hacks (go Google it) and the guy who runs the site made a sweet video & write-up on how to root your phone. Just re-do everything and follow directions, then when your done just flash Kings Unleashed. And when you check out the HTC EVO hacks root page look for the link to the XDA root forum which has more info on how to root your HTC the proper way.
Click to expand...
Click to collapse
I'm pretty sure that isn't the case at all. If there was an issue with the way I rooted my phone, it would have been present eight months ago when I bought it. This rebooting issue is relatively new, and it isn't bricked. I appreciate the advice, though.
It could be just a defective phone - memory isn't immortal or impervious to defects.
I'd downgrade to a Sprint ROM, and keep it stock and see how that works. You have to rule out bad hardware first, and that's the only way to do it.
I agree on all of your guys suggestions but one thing i noticed was that he said he wiped data then dalvic cache then he said he flashed the kernel then the rom. Maybe he should try and rewipe everything with calk format all then flash the rom and reboot. Then go back into recovery and flash your new kernel then reboot again and see whats up from there.
Have you tried repartitioning your SD card and formatting? I was getting random reboots on every single rom I tried, and every single kernel. Turns out my partitions somehow got messed up on my SD card and that was causing it randomly. Now I have no reboots.
akrod2as said:
Have you tried repartitioning your SD card and formatting? I was getting random reboots on every single rom I tried, and every single kernel. Turns out my partitions somehow got messed up on my SD card and that was causing it randomly. Now I have no reboots.
Click to expand...
Click to collapse
Yes, I first formatted the sd card in Windows and then partitioning it on the phone's recovery. Still no luck.
Yeah... Sprint rom or if you go through with the unrooting process (I forgot how...) then you can figure out if it is hardware.
But yeah, endless reboots are frustrating.
If Sprint rom is giving you troubles, then just return it and get a new one. It's gotta be hardware then.
Also you could try running stock rooted without any downloaded market apps. Just run what came with the phone.
You can also try stock rooted eclair 2.1
Mine started the reboot bs after the december update. Mine seems to reboot when I use it heavily even though I'm not overclocked (heats up). Before the 2.2 update, it was very fussy being outside during the summer. I would like to exchange mine for another, even though I don't use it anymore. It would be nice to have a fully functioning backup. My gf's daughter wants the evo very much. Even if I would do that, which I wouldn't, I wouldn't let someone use a possibly unstable phone. If an emergency happened, and the phone started it's rebooting bs, it would be very bad to not be able to use the phone when you need it the most.
I am guessing I would have to reactivate the evo, run it for a month or so, unroot and lock it, then take it to a service center and see if I can make it start rebooting like crazy. Maybe I will get lucky and they would give me another one. I don't care too much if it is a refurb as long as it is in good shape and works good.
Try removing the SD card and booting.
Sent from my PC36100 using XDA App
rebooting
I had this same problem with my evo. Sometimes it would be ok, but then others it wouldnt stop doing it, didnt matter what I did. It could be sitting by itself and I would hear it rebooting. Drove me mad!!!
My first evo was awesome, it was a hardware ver 3. My camera lens cracked and the gave me a refurb, hardware version 2. This is when my reboots started happening.
After 3 batteries from Sprint and two more refurbs I finally blew in front of a store full of customers telling them that either give me a NEW evo, hardware version 3 like I originally had with no problems or it was going against their wall.
I havent had one problem since.
I wasnt rooted yet so cant comment along those lines but if you take it back to stock and it still does it I recommend throwing it at one of Sprints walls. No need to do any drywall patching at your place LOL.
I hope you get it resolved as I can feel your pain!
It may not be hardware. Did you restore any apps using any back up app (Titanium Backup) after flashing the AOSP roms? If so, make sure you did NOT restore any system apps or data. This is especially important when you go from Sense to AOSP.
The test is what everyone is suggesting. Flash back to Sprint rom and see what happens.
Also, you need to flash the kernel after flashing the rom, otherwise you'll just get the kernel packaged with the rom. I usually reboot and art least try the default kernel unless I know that my phone hates it.
bigmoogle said:
It may not be hardware. Did you restore any apps using any back up app (Titanium Backup) after flashing the AOSP roms? If so, make sure you did NOT restore any system apps or data. This is especially important when you go from Sense to AOSP.
The test is what everyone is suggesting. Flash back to Sprint rom and see what happens.
Also, you need to flash the kernel after flashing the rom, otherwise you'll just get the kernel packaged with the rom. I usually reboot and art least try the default kernel unless I know that my phone hates it.
Click to expand...
Click to collapse
No, I haven't even been able to get to the stage of installing any apps before the rebooting cycle starts again. I tried installing the stock Sprint rom this morning with the stock radios and kernel and it was stable for about five minutes. It's back to rebooting again, though.
Do you guys think it's time to unroot and go to the Sprint store for an exchange?
Mecha2142 said:
No, I haven't even been able to get to the stage of installing any apps before the rebooting cycle starts again. I tried installing the stock Sprint rom this morning with the stock radios and kernel and it was stable for about five minutes. It's back to rebooting again, though.
Do you guys think it's time to unroot and go to the Sprint store for an exchange?
Click to expand...
Click to collapse
If it was me, I would take it back. I just downloaded the newest ruu and will flash it later tonight. The only thing I'm worrying about is they won't be able to reproduce the problem. I really have to be multitasking a lot and pushing the phone hard. Actually the last time it had rebooting fits was with wireless tether running. The back of the phone was warm. I put it in front of the ac vent in the car for a minute or two and that seemed to help it stop rebooting.
herbthehammer said:
If it was me, I would take it back. I just downloaded the newest ruu and will flash it later tonight. The only thing I'm worrying about is they won't be able to reproduce the problem. I really have to be multitasking a lot and pushing the phone hard. Actually the last time it had rebooting fits was with wireless tether running. The back of the phone was warm. I put it in front of the ac vent in the car for a minute or two and that seemed to help it stop rebooting.
Click to expand...
Click to collapse
Well, it looks like I'll be taking it to the store after all. I just finished unrooting my phone with the RUU, so it's as if I had never touched the software. Lo and behold, the damned thing still rebooted a minute into using the phone.
I guess that in some sick way, I can consider myself more 'fortunate' than you, seeing as how my phone doesn't even need to be used in order to begin rebooting. It's ridiculous that I have to part with my Evo because of this bs.
Mecha2142 said:
Well, it looks like I'll be taking it to the store after all. I just finished unrooting my phone with the RUU, so it's as if I had never touched the software. Lo and behold, the damned thing still rebooted a minute into using the phone.
I guess that in some sick way, I can consider myself more 'fortunate' than you, seeing as how my phone doesn't even need to be used in order to begin rebooting. It's ridiculous that I have to part with my Evo because of this bs.
Click to expand...
Click to collapse
Did you even try removing the sd card and booting the phone?
Same thing happend with my old evo it started after i install one of the first cm safe roms not nightlies not saying tyat was the cause, i tried evverything wiping unrooting botting without sd, ive been on android sice g1 and i tried everything nothing worked, ended up going to sprint and getting another refurnished it was prolly hardware issue maybe cpu overheating or something, anyways not sure why ppl are so scared of refurnished phones i believe they do a lot more tests on those phone than retail ones lol
akrod2as said:
Did you even try removing the sd card and booting the phone?
Click to expand...
Click to collapse
Yes. I've already said I tried booting the phone without the sd card several times now without success.
Hey guys I have a mytouch 4g that has been rooted to 2.3.3 (gingerbread) (I bought it like this) and when I try to go to the camera/camcorder/ or any other camera using application its just a black screen. I don’t know how to fix it, please help thanks!
Try to flash another ROM and see if it works then. I don't know if you are familiar on how to do that, but in the Mytouch 4G android development section there are plenty of ROMs to choose from with instructions. Make sure you make a back up. I suggest royalginger 2.1
thanks for the response,
i actually dont know how to change the ROM, does that mean changing from gingerbread? thanks for your help,
Nope, there are plenty of roms that are gingerbread. The link I am posting is the resource bible located in the development forum. It has basically everything you need to know. http://forum.xda-developers.com/showthread.php?t=866175
I suggest you go to the android market, look up rom manager, an download it. Also go to cynogenmods website an find the mytouch 4g, go to the wiki part of it. It well show you there how to download an install a new rom.if you still need help send me a private message, cause I change roms bout once every few days.
Sent from my HTC Glacier using XDA Premium App
Since his phone is already rooted with a custom rom, I am willing to bet he has ROM Manager on his phone...
thanks guys i am a little confused, but yeah it does have a rom manager but im not sure how to use it, its my first android and i didnt know it was rooted when i bought it lol
i might be asking for too much, but can anyone break it down for a 1st timer, i just want a stable phone with the camera to work lol
Make sure you have recovery installed,rom manager can install it. Its the very top in the app.Open rom manager,select download rom,pice the rom you want.make sure you also download gapps(google apps). Wait for it to download. Once it downloads rom manager will ask you,to wipe cache,dalvik,an back up rom. Do all three of them. Select ok. You should now reboot into recovery,use your track pad,to find install zip,select that then find choose zip,from sd card. Look for either rom manager or cynogenmod(not,sure which it is). Find the rom you downloaded,select it. Itll ask you if you want to install,select yes. Then repeat the process in,recovery to install a rom,for gapps. One you done that,hit the back button an,reboot your phone.
Sent from my HTC Glacier using XDA Premium App
Hey, guys i finally got a new ROM! but the bad news is that the camera still doesnt work? any other suggestions.... the weird thing is that the camera has worked before, and then it goes black again
I think the camera on that phone, is probably messed up. Maybe a bad connection.
Sent from an android,thats makes steve jobs jelous.
Hopes this works for you.
Ive been having the same prob for months. Then tonight I did something unusual. I called T-mobile to see if they had a solution, and by golly it worked! The tech mentioned that the black screen may be due to an issue with the sd card. She said that if I used to much memory, the camera will not allow anymore videos and pics to be taken(why it doesnt just flash a note that says memory overload or something, IDK) So she said to remove the sd card and reboot and try to access the camera. If the phone allows you to do that then there is an issue with the card. Remove all saved data to another device and reboot.
I actually did it a little different. I remembered that the last time it worked, I was at a concert and took several videos, so I was hoping I had just used to much memory. So before rebooting I simply deleted all the videos from that concert(you can dump files on another device).Then I tried to start my cam, got the black screen. So I powered the phone down, removed the SD card and battery, reinserted the battery sans the SD card and rebooted phone. Activated the cam, still got a black screen. Powered down again, re-inserted the SD card, and rebooted. Started the camera and......it worked.
No more black screen!
Sorry about the post as this may not be the best place for it.
My phone got low on memory so was trying to clear stuff, it rebooted then on the loading screen (Myn RLS 5) perpetually restarted. So went into recovery
and tried to do a backup (so could format as my last backup was old) and it threw an error in mid -backup (did write it down, doh!!)
Now the phone does the 5 vibration thing and does boot. Also SD won't mount get " /dev/block/mmcblk0p1" error. Also I now notice the phone reset to "S-on" I had a long time ago rooted with unRevoked Forever.
I have read several posts about this , but confused on the best way (instructions) to get a img file on and reinstalled. I have used adb before but only basically , unfortunately my computer at work doesn't have adb installed so cannot test things now.
So if anyone has a good one or two methods for me to try tonight, would be much appreciated. Also totally surprised that security went to "on" so probably have to address that first.
Oh phone is EVO, HBOOT 0.93 , Radio 2.15.00.05.02 . If I should post this somewhere please feel free to direct me there.
EDIT: I have ClockworkMod Recovery 2.6.01 installed and can get into it.
Thanks so much.
Kevin
First I woud try the sd card fix found here:http://forum.xda-developers.com/showthread.php?t=695243&highlight=sd+card+won't+mount Then I would downgrade your radio to 2.15.00.11.19 using a flashable pc36.img file.All radio versions can be found in the development section.If the first 2 steps are successful,run a 3.70 ruu(can also be found in development).If that is successful,reroot using unrevoked forever and you should be good to go.I' not sure if the radio downgrade will work with s-on,but I think if you use the flashable pc36.img version it will go thru,if it doesn't,you can still try the 3.70 ruu.I ran into some incompatability issues with trying to run the 2.15.00.5.02 radio with older software and hboot versions.
@BrianBusby2038,
Thanks for the post, good information I will give it a try. Interestingly the phone did eventually boot into Myn for a few minutes before the 5 vibrations of death started again.
So looked and it def. doesn't see the SD. So hopefully can recover.
I am wondering if the AData SD card I have is not reliable. Thankfully have the original 8GB card so hopefully can get things going again.
Anybody have a good recommendation for a 16GB microSD that is fast (buying from Newegg) ?
thanks again
No problem,hope it works out ok.
Sent from my PC36100 using XDA App
I had this same problem a few days ago and I had to get a replacement ordered (a 2.3 preloaded replacement ). Make sure that your USB is still working, because both my SD card and USB stopped working, S-ON went on, and the five vibrations/green light shut down problem happened. I was able to get S-Card operational, but USB was no go. I could not log in as super user and could not enter the commands necessary to fix usb. No USB = No root = no fix for USB. Now I'm stuck with a 2.3 evo, at least its shiny and new .
Hope you fix yours, I wonder how this problem has happened to so many of us randomly. PS: when you take it to sprint store, don't complicate matters and revert to stock.
Crude, fastboot on PC throwing driver error, how do I tell if the right driver is installed.
This is really sucking, Ive only ever installed one driver and could connect with adb.
So not sure what to do.
EDIT: says can't start because AdbWinApi.dll is missing
@robertsaurus,
not sure how I could go to stock if I cant re-image. Yeah definitely don't want to make a fuss, ugh
I lost clockwork mod and ended up only being able to access default Android recovery menu. I think an option on there will restore the factory Rom and make it look like it was never rooted. I know people have been able to fix theirs but I gave up after a days worth of trying
Sent from my PC36100 using XDA App
Well I had partial success. I restored a signed Sprint Rom, but phone keeps rebooting and USB doesn't work. the 5 vibrations seemed to have gone away. Though since I can get usb to work I can't do a RUU install and remove clockwork.
I did talk to Sprint and they are willing to early upgrade me and buy the EVO back for 125 so long as it boots and it does .
So going to give that a whirl , I have 30 days so may give a few other things on the evo a try before I return. Doing the upgrade I just lose out on some of the rooting so we'll see how that impacts me.
I had the exact issue. I think if you do a wipe from the boot menu (power and vol down) it will get rid of it all. And then take it to sprint and play dumb . Worked for me, new shiny evo lol
Sent from my PC36100 using XDA App
yeah I played dumb, but since it was out of warranty 1month and 10 days. they wouldn't replace . But at least get upgrade and buy back on the EVO which is not bad.
Though I am over the next couple of days try and get the EVO rescued, so long its still bootable I can take advantage of the buyback
yeah I played dumb, but since it was out of warranty 1month and 10 days. they wouldn't replace . But at least get upgrade and buy back on the EVO which is not bad.
Though I am over the next couple of days try and get the EVO rescued, so long its still bootable I can take advantage of the buyback
That sucks, hope it works out for you
Sent from my PC36100 using XDA App
robertsaurus said:
That sucks, hope it works out for you
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Interestingly I could get the 5 vibrations thing to go away if I applied unrevoked forever s-on. the phone will still reboot and usb not functioning yet. Going to try and get a shell script running to fix usb , or try and do a re-rooting via the auto root, maybe hboot usb will work (fastboot did)
I did get the photon (we'll see how it works, though miss my rooting and evo)
so if like hopefully they will unlock the bootloader.
Well, I first of all was using TWRP 2.0 as my recovery. However, i did not know that it was known to cause bricks. Anyway, I was doing a routine clean flash of a new rom i wanted to try, the aokp build 22 rom. I wiped everything, making sure to hit wipe system as well in twrp, then i put my phone to mount the sd card, transfered the rom, flashed it and its gapps then i reboot. Now all my phone can do is reboot endlessly, So I got into the bootloader and selected recovery, still, just keeps bootlooping. So then I decide to find an RUU and flash it through fastboot. It flashed everything correctly but when it got to step 4, (system) the phone would say error and it would fail to flash the system. After this I was still at bootloop. I dont know what it is, I even tried flashing Amon_Ra through fastboot, and ive been able to get to recovery once or twice but just to find it completely unresponsive and it wont read/mount my SD card even though i checked and the sd card was fine. All in all, I took it over to sprint and since i have TEP they agreed to get me a new one, though it was backordered so now im a week without a phone. Anyway just wanted to share my story, if anyone else knows of a way to fix it, im all yours.
TWRP kills. Good luck. Sorry you didn't follow up regularly on the thread of the product you were using. If anyone can help you, it might be Captain Throwback, but I think he's been a bit busy lately (i.e. been absent). Good luck, but TWRP fncks you.
sent from AOKP heaven
TWRP2.0 is an evo killer as far as I know there is no fix for a TWRP brick I'm pretty sure it messes up something in the partitions possibly boot or system partition which is why it bootloops
We are legion, for we are many
Unfortunately your phone is toast. Had the same problem, and really there is no way to recover. You should have bit the bullet in used insurance instead of going through Sprint since the Evo is past EOL. You maybe waiting a long time to get a replacement where as going through Ausion (sp) you either would have gotten either a new Evo, a refurb'ed Evo, or a new Evo3D (most likely).
Sent from my ICS-less Transformer TF101 using Tapatalk
Art2Fly said:
Well, I first of all was using TWRP 2.0 as my recovery. However, i did not know that it was known to cause bricks. Anyway, I was doing a routine clean flash of a new rom i wanted to try, the aokp build 22 rom. I wiped everything, making sure to hit wipe system as well in twrp, then i put my phone to mount the sd card, transfered the rom, flashed it and its gapps then i reboot. Now all my phone can do is reboot endlessly, So I got into the bootloader and selected recovery, still, just keeps bootlooping. So then I decide to find an RUU and flash it through fastboot. It flashed everything correctly but when it got to step 4, (system) the phone would say error and it would fail to flash the system. After this I was still at bootloop. I dont know what it is, I even tried flashing Amon_Ra through fastboot, and ive been able to get to recovery once or twice but just to find it completely unresponsive and it wont read/mount my SD card even though i checked and the sd card was fine. All in all, I took it over to sprint and since i have TEP they agreed to get me a new one, though it was backordered so now im a week without a phone. Anyway just wanted to share my story, if anyone else knows of a way to fix it, im all yours.
Click to expand...
Click to collapse
scottspa74 said:
TWRP kills. Good luck. Sorry you didn't follow up regularly on the thread of the product you were using. If anyone can help you, it might be Captain Throwback, but I think he's been a bit busy lately (i.e. been absent). Good luck, but TWRP fncks you.
sent from AOKP heaven
Click to expand...
Click to collapse
It's been a busy week for me, but I am still alive, and still using my previously-soft-bricked device .
I can link you to what I was able to do to get mine working (HERE), but if you can't get the device to boot up at all, you might be in dire straits. What is your HBOOT status? (version, NAND status)
hey Cap'n, you need some kind of superhero shield in your user icon
sent from AOKP heaven
When I first got my phone ((Without a simcard)) My phone rebooted like maybe twice in the 3 days. But ever since I put my simcard in ,after about 4 hours ish. I notice it rebooted and just after about 10 seconds or less it reboots again. It did it yesterday about 5 times in a row before I turned off my phone booted into recovery and cleared my cahce and dalvik, removed the sim, booted my phone and put the sim back in. No problems after that.
Then today morning It did it again rebooting back to back, removed the simcard out.
Does anyone know what is going on? Is it my simcard? I also have a case on, could that be? I can't rma cause I don't live in the states.
Adding on. It was my old phones simcard and hard to get cut. On android 6.1 running elementalx
Bump. I am thinking of going back to factory. What is the best way to do it? Using the one in settings or should I reflash googles stock image and unroot using nexus toolkit.
try a properly cut simcard. like one actually meant for the phone
Soulfly3 said:
try a properly cut simcard. like one actually meant for the phone
Click to expand...
Click to collapse
It doesn't look like it has anythin to do with the sim. I left my phone without the sim and it rebooted 2-3 times. Booted into safe mode and rebooted once.
do you have any crappy apps on the phone, or did u edit things while being rooted, that maybe you shouldnt have
Soulfly3 said:
do you have any crappy apps on the phone, or did u edit things while being rooted, that maybe you shouldnt have
Click to expand...
Click to collapse
I did change my governor options to something called ghostpepper settings from another thread, maybe its that? But like I said it all started happening yesterday. I have managed to get my bugreports. I could attach them.
Which method is best? Factory rest from the android settings or flashing stock image using nexus tool kit.
xringo said:
I did change my governor options to something called ghostpepper settings from another thread, maybe its that? But like I said it all started happening yesterday. I have managed to get my bugreports. I could attach them.
Which method is best? Factory rest from the android settings or flashing stock image using nexus tool kit.
Click to expand...
Click to collapse
I don't believe in toolkits, but feel free to use it.
I'd reflash the stock image, personally.
bump
You won't much support here for tool kits. They can cause trouble to begin with. Try flashing stock image and use Heisenberg's guide in doing so. If you successfully return to stock (not using a toolkit) and you still have issues I would say you have a hardware issue.