Related
Hello,
Last night I rooted my device using this (http://forum.xda-developers.com/showthread.php?t=1265429) method and file from zedomax and everything worked great except when I booted my device there was a yellow triangle with a black “!” in it. I figured that just indicated the device was rooted or running a 3rd party kernel so I didn’t worry about it.
Today I launched my camera app and it failed to load the interface but showed the image from the camera momentary then crashed back to the home screen. I restarted my device and when the device restarted it was very slow and unresponsive and after unlocking it my live wallpaper was gone replaced with the last background I used before selecting a live background a couple weeks back. No icons or widgets loaded and I am unable to open the settings tray. The only things I am able to do with the phone is pull down the notification bar, respond to text messages, adjust the volume and hold power to restart the phone. All of which are very slow and delayed.
When I connect the device to my computer windows is no longer able to load the drivers and Kies is unable to connect with the device. I am not sure what caused this or how to resolve this issue so any advice or known fixes would be fantastic! I am unable to get to clockwork mod to restore my backup and I am unable to get to Kies or the phone settings to do a factory reset so I really don’t know what to do they were supposed to be a last resort and now I don’t even think I can do them. I am an experienced techie but I am new to android and this is the first device I have rooted so any advice would be great no matter how basic it may be.
UPDATE: I just connected the phone via USB to my laptop at work and it was able to discover and install everything it needed to connect with the phone. I am installing Kies now so at least there is hope of a factory restore, although I really hope it doesn't come to that!
Boot into download mode and flash the stock eg30 tar file from crawrj.
Sent From My Evo Killer!!!
Thanks Already started doing that waiting for it to download now
Still no touchwiz... great!
Try flashing a stock rom via clockworkmod.
efarley said:
Still no touchwiz... great!
Click to expand...
Click to collapse
You can root again and restore your backup, or go to this website www.lostandtired.com (midnight roms blog) click on android development and download and flash the sprint bloat and TW restore zip. Hope that helps.
I flashed the stock rom which didn't change anything so then I used clockworkMod to do a factory reset which ended up trapping me into a boot loop. I could use Odin to flash new roms but the device would never go past the 4G logo
I ended up taking the device back to Best Buy and since the loading screen showed the stock rom and they couldn't get past the 4G logo I just had to say it wasn't rooted and they gave me a new one.
I would love to know if anyone has any idea of what went wrong here so that I can feel comfortable rooting again. Also if anyone has some basic articles handy that teach basics of rooting that would be great, I didn't even know about clockwork mod until after I had this problem so knowing things like that earlier would have helped a lot I think. I'll be spending the weekend looking up everything I can find on the subject so any reading you guys can suggest would be fantastic.
efarley said:
I flashed the stock rom which didn't change anything so then I used clockworkMod to do a factory reset which ended up trapping me into a boot loop. I could use Odin to flash new roms but the device would never go past the 4G logo
I ended up taking the device back to Best Buy and since the loading screen showed the stock rom and they couldn't get past the 4G logo I just had to say it wasn't rooted and they gave me a new one.
I would love to know if anyone has any idea of what went wrong here so that I can feel comfortable rooting again. Also if anyone has some basic articles handy that teach basics of rooting that would be great, I didn't even know about clockwork mod until after I had this problem so knowing things like that earlier would have helped a lot I think. I'll be spending the weekend looking up everything I can find on the subject so any reading you guys can suggest would be fantastic.
Click to expand...
Click to collapse
If you a clockwork and "stock rom" you were still rooted...Doing a factory reset will send you into bootloop when rooted. Trying to flash other roms on a bootloop is not going to work. You need to have grabbed a backup such as Zedo has on his post and put the backup in clockwork folder on your phone. Then flash that in CWM. Would of brought you out of bootloop to a stock rom with his kernal. Now you can flash Roms and kernals or could of flashed crawf or anyone else FULL stock rom and been back to stock kernel and rom and not rooted.
dallastx said:
If you a clockwork and "stock rom" you were still rooted...Doing a factory reset will send you into bootloop when rooted. Trying to flash other roms on a bootloop is not going to work. You need to have grabbed a backup such as Zedo has on his post and put the backup in clockwork folder on your phone. Then flash that in CWM. Would of brought you out of bootloop to a stock rom with his kernal. Now you can flash Roms and kernals or could of flashed crawf or anyone else FULL stock rom and been back to stock kernel and rom and not rooted.
Click to expand...
Click to collapse
Ohhhh that's what happened! Awesome thanks. I will be much better prepared with backups out the wazoo this time haha.
Now if only I could figure out why Touchwiz died in the first place hmmm....
I hope you can figure it out, just postin here to say that when I saw this thread, it reminded me of the thread over in the EVO forums about the guy who claimed that sprint removed his Sense from his phone.
Khilbron said:
I hope you can figure it out, just postin here to say that when I saw this thread, it reminded me of the thread over in the EVO forums about the guy who claimed that sprint removed his Sense from his phone.
Click to expand...
Click to collapse
haha SPRINT removed it?! So that person thinks sprint monitors every device and has a team of techies on staff to hack your phone and brick it if you break their rules?... yeah that totally makes more sense than a file got corrupted when you were messing with the kernel.. some people maybe shouldn't be rooting their devices in the first place haha
Hi all,
this is the 3rd time this is happening to me with different ROMs. The problem is:
The phone boots up normal, I can swipe to unlock, enter my PIN, but after pressing OK it won't unlock the SIM. If I lock the screen it won't come back on. It stays black whatever I do. After some time the phone reboots (soft reboot) and everything starts from the beginning.
The first time this happened I was using Modacos Ir9. I had the phone switched off over night and switched it on. Only thing that seemed to help was completely unrooting the phone and rerooting it again.
The second time I was using codeworkx CM9 Builds and tried to update. I restored my nandroid, but it kept happening. Flashing the XXKK1 Radio did the trick here.
Now it is happening again. This time I installed dropbox and the phone froze on the setup wizard...
I don't want to unroot the phone, it takes forever to restore the SD card.
Any advice on this one?
Update:
- Flashed the following radio images without any success: XXKL1, KRKL1, UGKL1 and XXKK1
- Used my older nandroids from CM9 and Modaco Ir10. NOT WORKING
- Wiped every nandroid. NOT WORKING AT ALL
- Reflashed CM9 and Ir10. Still NOT WORKING
I'm so lost I'm going to revert to stock and unroot... and try how far I can throw an 1 month old GNx from the fourth story.
I don't know much on the development part so I don't know why its doing that I can only suggest using odin and going back to stock.
Sent from my Galaxy Nexus using xda premium
I had similar problems with mine once. Only thing that helped me out wasn't unrooting though. A complete factory reset was enough to make me go on again.
I posted a thread here then to ask people if anyone experianced the same but got no reaction what so ever zo I guess "we" are a dark minority.
I don't know what it caused it or what the solution might be but a Factory reset did it for me.
Good Luck!
C-4Nati said:
I don't know much on the development part so I don't know why its doing that I can only suggest using odin and going back to stock.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Last time it was working again after reverting to stock. But I bought it to use Custom Roms
I would say go back to stock w/ odin, Wipe everything and start again.
Diger36 said:
I had similar problems with mine once. Only thing that helped me out wasn't unrooting though. A complete factory reset was enough to make me go on again.
Click to expand...
Click to collapse
Factory Reset wasn't helping unfortunatly.
Flashed the original factory image through fastboot. Now everything is working again. I'm restoring my SD backup now and will try to get CM9 working again.
If it would keep failing in stock I could return the phone. Now I'm left with "hopefully it isn't happening a fourth time" and "My phone doesn't work I need 4 hours to get ich working"
the_alien said:
Factory Reset wasn't helping unfortunatly.
Flashed the original factory image through fastboot. Now everything is working again. I'm restoring my SD backup now and will try to get CM9 working again.
If it would keep failing in stock I could return the phone. Now I'm left with "hopefully it isn't happening a fourth time" and "My phone doesn't work I need 4 hours to get ich working"
Click to expand...
Click to collapse
Fastboot flash stock google images. And your phone isn't bricked. Stop using the term wrong. It's most likely a software issue or you're doing the rom flash procedure incorrectly.
A bricked phone is a phone that is unaw to go into bootloader and recovery mode and cannot start android.
Sent from my Galaxy Nexus using xda premium
zephiK said:
Fastboot flash stock google images. And your phone isn't bricked. Stop using the term wrong. It's most likely a software issue or you're doing the rom flash procedure incorrectly.
A bricked phone is a phone that is unaw to go into bootloader and recovery mode and cannot start android.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Sorry for using the term wrong, I thought it just referes to broken phones.
The ROM flash is correct and it runs for some time and the problem occours after a few days... the only thing that helped was reverting to factory images and after that restore the nandroid from the "broken" Rom.
So the Rom works... than keeps crashing, I do a nandroid backup and only a factory image stops the crashes. But the Rom keeps working after I restore it.
I can't see why this could be a hardware issue. And I can't see how I should explain it to the store "Yes, it is working but not with custom roms, and I bought the Nexus because of custom roms..."
the_alien said:
Sorry for using the term wrong, I thought it just referes to broken phones.
The ROM flash is correct and it runs for some time and the problem occours after a few days... the only thing that helped was reverting to factory images and after that restore the nandroid from the "broken" Rom.
So the Rom works... than keeps crashing, I do a nandroid backup and only a factory image stops the crashes. But the Rom keeps working after I restore it.
I can't see why this could be a hardware issue. And I can't see how I should explain it to the store "Yes, it is working but not with custom roms, and I bought the Nexus because of custom roms..."
Click to expand...
Click to collapse
I'm willing to bet an app is causing it.
Sent from my Galaxy Nexus using xda premium
One of my colleagues had this issue with an early CM9 build on his Nexus S - turned out it was an app that is incompatible with ICS. Every time it tried to launch a notification, poof. So I would have to side with Josh in the post above mine.
A way for you to verify / discredit this theory would be : When you say it works with the stock ROM, are you re-installing everything you have when you are on stock? My understanding from what you've written above is that you're only getting your full suite of apps back when you restore your (presumably custom ROM) nandroid backup...
Potterified said:
One of my colleagues had this issue with an early CM9 build on his Nexus S - turned out it was an app that is incompatible with ICS. Every time it tried to launch a notification, poof. So I would have to side with Josh in the post above mine.
A way for you to verify / discredit this theory would be : When you say it works with the stock ROM, are you re-installing everything you have when you are on stock? My understanding from what you've written above is that you're only getting your full suite of apps back when you restore your (presumably custom ROM) nandroid backup...
Click to expand...
Click to collapse
It can't be any app or ROM because IF it happens, it happens on all ROMs, regardless of wipe or not.
It just happened again and i wiped everything and tried using AOKP MS 3. Wasn't working... So I tried using the phone without the SIM card, because the hell only breaks loose after entering my PIN. And it worked. I could use the phone...
I put it back in and it worked...
I'm restoring my CM9 nandroid right now. I'm hoping it works...
edit: Nope, ripping out the SIM doesn't work. I'm reverting to stock and wait what happens. If it crashes again I'm trying to return it.
So here's the situation and this is literally the 3RD time this phone has done this. I'll be on a ROM on my rooted unlocked galaxy nexus, and randomly I'll be opening my texts or contacts or something and my phone will reboot. No big deal right? But then it just boot loops. Endlessly. If I try to restore a nandroid from a different ROM, it'll get almost done then won't be able to restore /data. I know it's not a bad nandroid backup cuz I switch back and forth between them all the time. I can't flash any rom, it'll be a boot loop, can't restore a nandroid,so I always have to end up flashing a stock image and start from scratch again.
I've seen this problem before after it happened the first time and found that flashing stock img fix. I have two questions: Why does it do this randomly every month? It's like my bootloader goes MIA or something for no reason. What would cause it to do this and literally, almost once every 30 days?
Second question: Is this a stable phone? I'm coming from the nearly unbrickable Captivate and I've done some crazy stuff to that phone and always managed to recover it, a couple times when it shouldn't have even worked at all. But yet this thing breaks down almost every month. Didn't flash anything new, didn't flash anything incompatible, nothing. Everything was running smooth. Then all of a sudden reboot, boot loop, backups dead, roms on SD card are useless.
Can someone please fill me in on what's going on with this? lol this is my 5th rooted android phone, not a developer or a themer or anything, but I know quite a bit about what would cause a phone to do whatever. Any insight would be great. Thanks guys!
Wich roms are you trying? Wich rooting methods? Wich flashing method? Are you using adb and fastboot?
Edit: does the issue happens on stock?
So far my phone its rock solid stable and buttery smooth fast after 3/4 months
Galaxy Nexus AOKP m5 Franco kernel m3
It first happened on liquid rom. I rooted via Samsung gnex toolkit. It happened again on gummy 1.2.0 honestly I wasn't on stock long enough to see how stock ran lol I don't use adb or fastboot often. Just to root and recently, to flash a stock image every time this happens
Sent from my Galaxy Nexus using XDA
I'd try rooting properly by using fast boot and flashing a superuser.zip. It may be that the toolkit is not working properly and you have a bad recovery. Something is wrong if this is happening. Its not too hard...
Sent From My Sprint Galaxy Nexus via XDA Premium
Hey! I'd like to start off that I'm new to this forum but I do have a problem with my A100 though.
After getting my Galaxy Note 2, I decided to give my old A100 some new life by rooting it and installing the Jellytime ROM. I'd like to thank the creators of the ROM (pio_masaski & others) because it was the fresh look I wanted on the tablet, however, something happened. Recently, my parents wanted to use the tablet a lot more, so I offered to just give them my tablet but only after undoing everything else I did to it. So on my way to undo everything, I had the stock recovery at hand and the full stock rom at hand on an SD card. I wiped everything and installed the stock recovery, and since it was successful, I proceeded with the stock rom (update.zip) but my tablet was hung up after it installed it. When I say this, I mean it was stuck on the Android loading screen (and it wouldn't stop flashing and looping). So I tried again, wiping one more timing but it produced the same result.
I did look around and I have reason to believe that I just bricked my tablet, maybe because of the flash controller but I'm not sure. If anyone could drop by and tell me what they think of this, it would be awesome. Also, if you have a way of undoing it if possible?
-Thanks in advance!
xdtnguyenx said:
Hey! I'd like to start off that I'm new to this forum but I do have a problem with my A100 though.
After getting my Galaxy Note 2, I decided to give my old A100 some new life by rooting it and installing the Jellytime ROM. I'd like to thank the creators of the ROM (pio_masaski & others) because it was the fresh look I wanted on the tablet, however, something happened. Recently, my parents wanted to use the tablet a lot more, so I offered to just give them my tablet but only after undoing everything else I did to it. So on my way to undo everything, I had the stock recovery at hand and the full stock rom at hand on an SD card. I wiped everything and installed the stock recovery, and since it was successful, I proceeded with the stock rom (update.zip) but my tablet was hung up after it installed it. When I say this, I mean it was stuck on the Android loading screen (and it wouldn't stop flashing and looping). So I tried again, wiping one more timing but it produced the same result.
I did look around and I have reason to believe that I just bricked my tablet, maybe because of the flash controller but I'm not sure. If anyone could drop by and tell me what they think of this, it would be awesome. Also, if you have a way of undoing it if possible?
-Thanks in advance!
Click to expand...
Click to collapse
Its likely bricked, but I would try to flash the update.zip again, power on holding the volume closest to the power button, hold power until it vibrates then let go, it should pick it up and try to flash again, let us know any messages, like failed to mount errors, if any, that show up.
Tapatalked from my GNex - JBSourcery 4.5.6
I normally dont post without searching first but I am late for work,need my phone and the backup uses the older large SIM that i no longer have.
This morning I woke up to the annoying frozen black screen, it has been happening more often, i just pull the battery. this time it gets stuck between the samsung and Tmobile screens. I have had the phone since mid febuay, its rooted on a stock rom. team win recovery
please help, is there any way to fix without a wipe? ill be searching while i wait for a reply. hope I dont need to wipe
duh i was in download wiipe cash no help
i guess old nandroid next
Will it go to download mode ? If so flash stock rom via odin .
Sent from my HTC One X
thanks
i believe so
is odin preferred over flashing via recovery
hard to type with this keypad haha
Did u delete your old rom .zip ? If not, go to recovery and full wipe then flash the rom.
Sent from my HTC One X
Spoo76 said:
I normally dont post without searching first but I am late for work,need my phone and the backup uses the older large SIM that i no longer have.
This morning I woke up to the annoying frozen black screen, it has been happening more often, i just pull the battery. this time it gets stuck between the samsung and Tmobile screens. I have had the phone since mid febuay, its rooted on a stock rom. team win recovery
please help, is there any way to fix without a wipe? ill be searching while i wait for a reply. hope I dont need to wipe
Click to expand...
Click to collapse
Did you fix it ?
Sent from my SGH-T889 using xda premium
just got home
what a long day with no phone haha
going to work on it now but should i just flash the rom via recovery
had my phone since mid feb and thought i had 4.1.2 but the uppload date is two days ago
Spoo76 said:
just got home
what a long day with no phone haha
going to work on it now but should i just flash the rom via recovery
had my phone since mid feb and thought i had 4.1.2 but the uppload date is two days ago
Click to expand...
Click to collapse
odin from this post http://forum.xda-developers.com/showthread.php?t=1975560 EDIT: Do you back up your apps with titanium or similar?
Its a stock shipped rom rooted with teamwin recovery, And yes I always titanium backup, though I need to start backing up some system folders as well for complete backups. I thought I was on 4.1.2 from 1/28, but after flashing I see some updated buttons. Anyway I was able to get into recovery and flash a factory rom as normal without losing anything and its snappy like new. Im not sure why it was locking up so much and then got stuck in a boot loop but from now on I know to nandroid factory roms as often as custom roms.
Time to backup and try out some sense roms. I never thought I would like an Android overlay.
What Sense rom are you running on your Note II??
Ratlegion said:
What Sense rom are you running on your Note II??
Click to expand...
Click to collapse
Im pretty sure this guy has no idea what he is doing and is one step away from a paperweight lol