Related
My g2x keeps rebooting over and over again! This happened after i mounted it to my pc. it tries to read my sd card then just reboots over and over again. I have nv flash and tried to restore old back up but still does it. can any one help im thinking i need to flash stock.
you need to do a factory reset if your nandroid backup doesn't work. if that doesn't work reflash the rom.
I already did a factory reset and wipe and tried to re install the rom. it just continues to reboot. It starts up and if quick i can get into my lock screen and access things but within seconds it reboots and continues to do that
What rom are you using?
jcbofkc said:
What rom are you using?[/QUOTE
I was on a stock rooted rom when the problem happened. so i then i did a restore. when that didnt work i reflashed the stock rom that was posted on forum. i think it has something to do with my internal memory which i cannot access. this all happened when i was trying to back up my sd card while in usb and it just got an error when i unplugged it enless reboot.
Click to expand...
Click to collapse
I was hoping it was something simple like undervolting with a custom rom. I wish I could help. It sounds like you tried everything I would recomend. Maybe one of the real Android techie type guys can help you. I am still learning myself.
jcbofkc said:
I was hoping it was something simple like undervolting with a custom rom. I wish I could help. It sounds like you tried everything I would recomend. Maybe one of the real Android techie type guys can help you. I am still learning myself.
Click to expand...
Click to collapse
Thanks anyway! I even when as far as to re-flash stock recovery and then try to factory reset it but still did not work. I just dont know what the heck happened. So today I went to t-mobile and they r sending me a new phone and for know I have a loaner 10 days until I get the new phone they said it was backordered. oh well
Good day all, I recently got a Nexus S for free from my brother becuase it keep's restarting its self. The phone was rooted with Cyanogen rom, and from what he told me has been dropped a couple of times. With this all being said, he went ahead and flashed a fresh rom on there (unk which one) and wiped everything etc.. Anyone exp this type of problem before and if so what can be done to fix it?
King350z said:
Good day all, I recently got a Nexus S for free from my brother becuase it keep's restarting its self. The phone was rooted with Cyanogen rom, and from what he told me has been dropped a couple of times. With this all being said, he went ahead and flashed a fresh rom on there (unk which one) and wiped everything etc.. Anyone exp this type of problem before and if so what can be done to fix it?
Click to expand...
Click to collapse
Lol I think you over clocked it on the minimum ... try the minimum at 800m ... or if anything flash a new rom.. its probably the rom itself
Sent From In between Your Moms Boobies
Try another (stable) rom? (no development rom)
Wipe everything.
And yes, probably its underclocked/overclocked too high.
I would like to flash a rom but once I turn it on it keeps force closing everything and I am unable to do anything on the phone, It boots into recovery mode just fine though
Sent from my HTC Vision using XDA App
King350z said:
I would like to flash a rom but once I turn it on it keeps force closing everything and I am unable to do anything on the phone, It boots into recovery mode just fine though
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Good news, you flash your ROM from recovery. Download the package, boot into recovery. Mount the SD card and push or push using adb push. Flash the zip from CWM.
my friend purchased the phone yesterday and he is on the latest Official version (2.3.6) and the phone keeps rebooting!!!
is this normal?? there must a problem!
3mar84 said:
my friend purchased the phone yesterday and he is on the latest Official version (2.3.6) and the phone keeps rebooting!!!
is this normal?? there must a problem!
Click to expand...
Click to collapse
Wipe data/factory reset from recovery if it's a used phone.
If he just bought it return it... thats easy
If he rooted it and changed the rom -- put it back to stock or put a new rom on it
I personally found that most of my restarts were due to me trying to pull the stock launcher into an unfamiliar rom. Make sure (if you are using Titanium backup) to only load apps not system *unless you are trying to go back to the same rom*
good luck
First check if he overclocked too much or underclocked too much. Put it to normal.
Alternatively you can just flash another rom. Before flashing remember to wipe everything
Goodluck!
I tried to flash cm10 rom and it never would get past starting apps. I used the new recovery that I beleive beans had reated to install cm9. Then when I tried to reboot i got the verizon non authorized software message. I went back and odin back to root66 and could not get network connection. i have tried factory reset and doing over and over again with now luck. does anyone know why its not letting me on network
pitmanr2003 said:
I tried to flash cm10 rom and it never would get past starting apps. I used the new recovery that I beleive beans had reated to install cm9. Then when I tried to reboot i got the verizon non authorized software message. I went back and odin back to root66 and could not get network connection. i have tried factory reset and doing over and over again with now luck. does anyone know why its not letting me on network
Click to expand...
Click to collapse
where did you get cm10 for the vzw phone? I thought it was for all of the other phones but vzw? Try going back to stock non root. try flashing the modems in the thread about this one.
phillyphill39 said:
where did you get cm10 for the vzw phone? I thought it was for all of the other phones but vzw? Try going back to stock non root. try flashing the modems in the thread about this one.
Click to expand...
Click to collapse
if you go to goo app its in his folders of roms i beleive. i have tried that. i switched to my wifes sim card and got same results, so must be something on the phone
pitmanr2003 said:
I tried to flash cm10 rom and it never would get past starting apps. I used the new recovery that I beleive beans had reated to install cm9. Then when I tried to reboot i got the verizon non authorized software message. I went back and odin back to root66 and could not get network connection. i have tried factory reset and doing over and over again with now luck. does anyone know why its not letting me on network
Click to expand...
Click to collapse
Flash the stock tar.md5 from here: http://samsung-updates.com/device/?id=scH-i535
Whatever you flashed put a custom kernel on there, and that's why you get that message.
pitmanr2003 said:
I tried to flash cm10 rom and it never would get past starting apps. I used the new recovery that I beleive beans had reated to install cm9. Then when I tried to reboot i got the verizon non authorized software message. I went back and odin back to root66 and could not get network connection. i have tried factory reset and doing over and over again with now luck. does anyone know why its not letting me on network
Click to expand...
Click to collapse
I don't mean to be rude, but development is not for questions
timothydonohue said:
I don't mean to be rude, but development is not for questions
Click to expand...
Click to collapse
no offense taken, but with only one question and answer section and that for all cell services could make this question a little different
pitmanr2003 said:
no offense taken, but with only one question and answer section and that for all cell services could make this question a little different
Click to expand...
Click to collapse
I have d2hackers cm10 up and running on my device...click link in sig!
i have tried new modem and fully stock rom. no luck. I was running dual boot before that if that could of caused issue. I am lost now.
pitmanr2003 said:
i have tried new modem and fully stock rom. no luck. I was running dual boot before that if that could of caused issue. I am lost now.
Click to expand...
Click to collapse
I am lost. i have tried everything and i am now where a beginner when it comes to android. Im afraid that if i take it back they will see it has been rooted.
pitmanr2003 said:
I am lost. i have tried everything and i am now where a beginner when it comes to android. Im afraid that if i take it back they will see it has been rooted.
Click to expand...
Click to collapse
wipe data then odin a factory stock image
droidstyle said:
wipe data then odin a factory stock image
Click to expand...
Click to collapse
tried that still wants to roam.
pitmanr2003 said:
tried that still wants to roam.
Click to expand...
Click to collapse
I have tried to odin stock and then wipe. still showing no data connection, and same thing when I put my wifes sim in. IM thinkiing it has something to do with the dual boot i had set up before. is there a way to repartion the internal sd card or emmc?
This seems to be happening to a lot of people flashing AOSP ROMs....this is why they warn you they are not responsible for what happens to your phone...especially with Betas.
There are many threads on this and several on how to get a workaround until someone figures out how to fix this.
Try doing a search on losing IMEI or roaming after flashing CM10...it is happening a lot...that is why I am just using rooted stock with VZW apps and TW frozen.
this problem I was having with no data or radio in CM10.
I used ODIN to go back to stock rooted (root 66).
When I did that I was boot looping in the puking rainbows 4GLTE boot animation.
I eventually figured out how to fix that by booting into recovery (press volume up, home button, and power button at the same time till phone boots). I then did a wipe data/factory reset.
My phone then booted fine into stock root.
I then proceeded to punch in *2767*3855# into my dialer immediately when I got stock root working. That did some sort of a factory reset / format. It all happened so quick I could barely read what it told me. The phone rebooted after a while.
I then downloaded EZ-Recovery for VZW Galaxy S3 app from the Play store.
I installed the custom recovery from Dhacker's CM10 post over on the droidhive forums using EZ recovery.
I also downloaded the CM10 file to flash and the Jelly Bean Google Apps file.
Rebooted into recovery, Wiped data/cache/dalvik.
Installed the CM10 file.
Installed the Jelly Bean apps.
Reboot.
Profit.
I now have a largely functional CM10 (as far as I can tell there are some camera issues). Data 3G/4G is working, so are calls and text and everything is dandy.
Did the *27 bla bla thing posted above and back to normal. Thanks everyone
Sent from my SCH-I535 using XDA App
I've been trying to fix this problem for 2 days now, I tried installing back to stock, reroot and unlocked. I slapped Cleanrom on and it hasn't fixed the issue. I was hoping if the problem could possibly be fixed, or if its a hardware issue i want to know what steps i can take to deal with it. As of right now i cant make any calls without it foreclosing on me.
Thanks
Weird. Tried clearing cache? Did you have this problem when u first got the phone? When did all start?
It was 2 days ago. I tried almost everything, but still a no go. I have pmed some people who have experienced it in the past, but their on 2.20 now, so i might consider it if its going to fix the issue. I rather not though
I'm getting that same problem too, also i can't properly add phone numbers to my phone or sim. This is getting frustrating, hopefully someone can elaborate on this..
Do you have any accounts syncing? Maybe if you delete all the accounts that sync contacts? Maybe try it without a SIM card in?
If you are using CWM and flashed CleanROM (and maybe other ROMs), then that is why you are having this issue. Its a known issue, and it clearly says in the CleanROM top post to not use CWM, and to use TWRP.
Also, this is a double post. Somebody posted a fix in your other thread. Go look at it. Now see why double posts are confusing and annoying?
solution
It happened to me too and now I have a solution.it happened to me when I installed a rom(don't want to mention the name).ok do this
Root ur phone unlock bootloader and install cwm not twrp.now clear cache,data,system everything and install any rom(even stock)using TARP(dont forget to clear everything in twrp also).
It worked seriously for me and believe me.if I helped u please hit thanks button
saketh91 said:
It happened to me too and now I have a solution.it happened to me when I installed a rom(don't want to mention the name).ok do this
Root ur phone unlock bootloader and install cwm not twrp.now clear cache,data,system everything and install any rom(even stock)using TARP(dont forget to clear everything in twrp also).
It worked seriously for me and believe me.if I helped u please hit thanks button
Click to expand...
Click to collapse
I tried this method, installed CWR over TWRP and installed cleanrom 4.5, then my phone would reboot continuously. Did you experience this?
Are u guys doing FULL wipes as stated above?? Do a full wipe, cache, dalvik, system, factory reset/data. Flash a rom and dont restore anything. Just boot it up and see. Im fairly certain it wont mess up after that.
Did you flash KingCobra then started having this issue? I have the same problem as well right now, there is a FC.zip fix he's made that you can flash but I'm getting an error right now. Its a awesome rom tho!
as i mentioned you need to clear data,cache,system.. in cwm then switch to twrp and install a rom.installing cr4.5 or any latest roms in cwm will cause bootloop
Hello First post here so hopefully in the right place! I've got a nexus 5, UK model purchased around January time. I had rooted, running stock with SuperSU installed and a few apps installed with xposed mod.
It was running perfectly fine, until a few days back where I was required to reboot, it then got stuck at the Google screen and wouldn't go past that, I turned the phone off for a while and eventually could get into it.. Great, until it happened again.. I spoke to a friend who said perhaps it was the xposed which was causing it, so I flashed back to factory, ran it for a while and it was fine, so went back to root and tested it, was stable so I reinstalled xposed.. It then got stuck in the bootloop again, so flashed to factory certain that it was xposed causing issues. I'm now running factory, however the phone will still get stuck in bootloop but will also randomly reboot itself now.. Has anyone experienced this? After scanning the forums I can't find anything so hopefully someone can help!! My boot loader is still unlocked.
Thank you, Jordan.
arsenaljordan said:
Hello First post here so hopefully in the right place! I've got a nexus 5, UK model purchased around January time. I had rooted, running stock with SuperSU installed and a few apps installed with xposed mod.
It was running perfectly fine, until a few days back where I was required to reboot, it then got stuck at the Google screen and wouldn't go past that, I turned the phone off for a while and eventually could get into it.. Great, until it happened again.. I spoke to a friend who said perhaps it was the xposed which was causing it, so I flashed back to factory, ran it for a while and it was fine, so went back to root and tested it, was stable so I reinstalled xposed.. It then got stuck in the bootloop again, so flashed to factory certain that it was xposed causing issues. I'm now running factory, however the phone will still get stuck in bootloop but will also randomly reboot itself now.. Has anyone experienced this? After scanning the forums I can't find anything so hopefully someone can help!! My boot loader is still unlocked.
Thank you, Jordan.
Click to expand...
Click to collapse
Are you able to flash a custom recovery? like TWRP, PHILZ, CWM? try it.
if successful, flash a custom Rom. just to discard the possibility of emmc failure.
GUGUITOMTG4 said:
Are you able to flash a custom recovery? like TWRP, PHILZ, CWM? try it.
if successful, flash a custom Rom. just to discard the possibility of emmc failure.
Click to expand...
Click to collapse
I am able to flash a custom recovery and so forth, so wouldn't think it to be emmc failure.
arsenaljordan said:
I am able to flash a custom recovery and so forth, so wouldn't think it to be emmc failure.
Click to expand...
Click to collapse
It doesn't really exonerates emmc from being bad yet. now, wipe and flash a Rom, a stock/aosp based one
GUGUITOMTG4 said:
It doesn't really exonerates emmc from being bad yet. now, wipe and flash a Rom, a stock/aosp based one
Click to expand...
Click to collapse
I have already flashed the stock recovery and ROM back to the device