[Q] Rootet galaxy nexus freeze and reboot. - Samsung Galaxy Nexus

I have a big issue. I have rootet my phone. Install aopk rom build 21. It`s work perfect. Today i upgrade to build 22. And then the problems start. The phone is only freeze and reboot. It`s work fine until i enter my pin. It`s freeze and reboot.
I try another rom,. same issue. I try to install a new kermel. But still the same.
Anyone have a solution for me? I`s verry frustrated now... I hate my phone at this time.

If you made a nandroid backup of stock, restore that and see if the problem persists.
Did I help you? Click the thanks button!
Phone: Galaxy Nexus
ROM: GummyNex
Kernel: Franco

elboco said:
I have a big issue. I have rootet my phone. Install aopk rom build 21. It`s work perfect. Today i upgrade to build 22. And then the problems start. The phone is only freeze and reboot. It`s work fine until i enter my pin. It`s freeze and reboot.
I try another rom,. same issue. I try to install a new kermel. But still the same.
Anyone have a solution for me? I`s verry frustrated now... I hate my phone at this time.
Click to expand...
Click to collapse
Yea, definitely restore your Nandroid factory backup...Im assuming you did one of those immediately after rooting your G-Nex? This is the most important thing you can do after rooting so you always have a safety net if things go wrong like you have been experiencing....If you do not have one you will have to do an SBF to a stock image

Related

[Q] Random reboots and bootloop even after fullwipe

Hi there!
I installed
http://forum.xda-developers.com/showthread.php?t=1912187
with basbeand 77 instead of the recommended ones, and it appeared to work just fine for two days.
Today, I installed the LBE Guard, and so my Desire was stuck in bootloop, which I could get out of after a fullwipe and a new install.
So, then, I installed the LBE privace Master (v4.3.2738),
http://forum.xda-developers.com/showthread.php?t=1422479
because I read it was okay for JB. While configuring it, my phone crashed, and I was again stuck in a bootloop. I tried to make a fullwipe again, and a new install, but I have still these random (but appearing soon after booting) crashings and then a bootloop. It even appears when I use the Aroma Installer, but not in the CWM.
So my question is - what went wrong and more importantly, how do I get my phone to work again?
Thanks for replying.
The part with the baseband is wrong - that was my other phone.
I am quite the noob-cookie, I also have the problem with random reboots and freezes. I have been messing around with the new Nikez 4.2 Jellybean Rom, i thought that could be the reason why. But now I am also experiencing it with the old Nikez 4.1 Rom that used to be very stable for me. Anyone know a good solution? I have done several full wipes..
Cheers!

[Q] What is wrong with my Gnex?

Hey the Problem is the following:
3-5 random reboots every day
restarts during every phonecall after 1-3 Minutes
freezes when in standby, cant turn back on -> need to take battery out
often slow, especially when switching apps. or when typing
I have tried stock 4.3, CM10.2 recently and before that CM10.1 for a while.
I already send it in but they only said my battery is broken.
Is it possible that all my problems come from this?
I rather think my flash memory is broken? What you think?
JonnyZaggi said:
Hey the Problem is the following:
3-5 random reboots every day
restarts during every phonecall after 1-3 Minutes
freezes when in standby, cant turn back on -> need to take battery out
often slow, especially when switching apps. or when typing
I have tried stock 4.3, CM10.2 recently and before that CM10.1 for a while.
I already send it in but they only said my battery is broken.
Is it possible that all my problems come from this?
I rather think my flash memory is broken? What you think?
Click to expand...
Click to collapse
Since yesterday I am facing the same problems you are describing. At first I thought it was a bad flash or something like that. Clean installed various 4.3 costum roms and it's always the same.
Right now I will look deeper into it since the phone is unusable in that condition.
If I find a solution I will comment.
Best regards
Edit: Okay, works again flawlessly. I simply flashed an nightly from carbon-rom and the lags were gone. Hope it helps. What exactly caused the lag I don't know. For now I am staying on 4.2.2 Carbon as it is my favourite rom anyway and I will wait till there are stable 4.3 from carbon.
Are you sure it's the phone and not an app?
chrisinsocalif said:
Are you sure it's the phone and not an app?
Click to expand...
Click to collapse
Not pretty sure, but it still occured after countless factory resets, wipe cache, wipe dalvic cache and wipe system via TWRP.
Have you tried a clean install without installing apps to see if you get a reboot to eliminate an app as a possible cause?
Sent from my Nexus 7 using Tapatalk 4
chrisinsocalif said:
Have you tried a clean install without installing apps to see if you get a reboot to eliminate an app as a possible cause?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Yes I did. I only flashed for example newest PA and their PA Gapps.
So far I resolved it by "downgrading" to a 4.2.2 nightly from carbon. The lags are completly gone. I will stay and wait till carbon has stable 4.3.
why dont people try stock when they are having problems? going from 1 custom rom to the next does not prove it is the phone.
please fastboot flash the stock rom and do not restore any apps/data other than say your google acct
Zepius said:
why dont people try stock when they are having problems? going from 1 custom rom to the next does not prove it is the phone.
please fastboot flash the stock rom and do not restore any apps/data other than say your google acct
Click to expand...
Click to collapse
Already did that.
I am having the same/similar problems with my GNex too. Specifically bullets [1-3] from the original post. I am running unmodified yakjuux and have tried with just my google account with no other apps and the same problem exists.
Mine makes a noticeable "click" sound with a vibration followed by a reboot.
It usually happens during calls and after it boots the phone call log shows no record of the incoming/outgoing call that just happened. Its like a blue screen of death for android!
I have sent the phone back to Samsung's warranty service 4 separate times and each time they reported no trouble found in the completion report. They just factory reset or put an older version of jelly bean back on the phone and send it back to me with some notes of PRL updates and other nonsense to make it seem like they did something to fix it.
Does anyone have any suggestions (logs, adb, etc) how I can help prove to Samsung/service absolute that the phone is a lemon (other than trying to video tape the phone hoping it reboots - because that is the last resort)?
I already escalated to executive customer service and they refused an exchange because the completion reports show no trouble found :crying:
Thx!
well... I also have this problem.
First happened when I flash Cm10.2 nightly (don't remember which one).
Then I flash PA, or whatever... Looks like the random reboot relating to notifications? It's usually happened when whatsapp notification coming in, but not always.
But a few weeks ago I flashed stock ROM rooted (via TWRP, not fastboot).
The problems solved. No random reboots anymore. Then today I tried latest CM10.2, and it happened again... Wonder why... Looks like it's a very rare problems.
Interesting to see someone having the same problem...
Now I want to flash stock ROM via fastboot to check if it'll fix.
Btw, I can flash directly to CM 10.2 from 10.1, can't I? Or I should flash 4.3 via fastboot first?
lonestrider said:
Btw, I can flash directly to CM 10.2 from 10.1, can't I? Or I should flash 4.3 via fastboot first?
Click to expand...
Click to collapse
I believe CM offers an upgrade option somewhere in the system settings. Unless you want to wipe your phone and flash directly to 10.2 in which case I do not think you need to flash stock 4.3 first. Maybe just do a reset within 10.1 before you flash CM10.2 via whatever recovery (clockwork etc) you are using but even that may be unnecessary.
My 1 year warranty expires this month so if I can't manage to get something out of Samsung I am going to play around with flashing stock 4.3 as you suggested. I have tried converting yakjuux to yakju in the past but still saw the problem then which made me revert back to yakjuux so I could send the phone back for service).

[Q] Unknown problems there...

First of all, my English is not that good, so I hope everybody understand me
I'm a flashoholic (i think this is the right expression); i flash a new ROM almost every two weeks. And, from some days ago to now i'm experiencing some problems. Here's my problem:
Problem: my phone "stucks" when I let it locked for more than some 5, 10 seconds. I lock it now, and... dead. I have to press the power button until it restarts. My phone is having trouble to find operator's network and it's EXTREMELY lagged too. It almost stucks when i try to write something on the keyboard, or draw/write my passwords on my lockscreen.
Here's my "ROM timeline", too:
ROM Timeline: MIUIBrazil v4 [4.1.2] >> P.A.C MILESTONE [4.2.2] >> TigraROM/Hurricane [4.3 leaked] >> MIUIAndroid v4 [4.1.2] >> MIUIBrazil v4 [4.1.2]
Underline = i think that this is the point
Bold = problem started
So, let me explain my history: flashing ROM's as always, I decided to change things a bit and go AOSP for a while. So I flashed P.A.C. Milestone. Actually, I've flashed first the Nightly version, but it was a bit unstable. I went to P.A.C and everything went fine. But, hey, where are the Samsung functionality? I missed it. So, after some trouble finding the right ROM to me, the 4.3 from Samsung leaked. I tried it, then. First the Hurricane, afterwards the TigraROM (Note 3 functions ). And it was ok, but was lagging a lot. Too much launchscreen redraws to handle, so I went back to MIUI (not the first MIUI on the timeline, because I've decided to go right from scratch), and then, i've noticed a lot of problems.
It was not booting up.
I've flashed A LOT of ROM's trying to solve this problem. What it was? EFS folder. I went to the TWRP file manager on Recovery and noticed that the EFS folder was empty. And no backup. I went crazy until i found an old backup stored on my PC. Restored it right away, and everything was fine for a while... until it started doing some strange things like extreme lag and dead when locked.
And, when I went to recovery to look again to the EFS folder, it was always empty... i restored it again, again and after locked... BAM, disappeared. But some strange things are happening, like:
My bluetooth doesn't turn on.
My IMEI was fine, even with this EFS showing and hiding like that.
I'm almost finishing. Let me put here some basic questions that I know everyone will ask:
Q: have you tried to wipe everything and go from zero?
A: yep. It didn't worked.
Q: is your IMEI ok?
A: yep. But some things that are on the EFS folder doesn't wok, like Bluetooth. The MAC address of the bluetooth is there, but it doesn't show up when I write *#*#232337#*# on my Phone app (this code shows up Bluetooth address and try to turn it on... to me it tries to turn on forever).
Q: do you know that thing about the new modems? Click here to go to the post
A: yes, but only read it when i've had the problem. But i've restore that backup, and it was from the original ROM. So it doesn't seem to be this, because the backup was before this leak. Very very very before, actually.
I hope you guys can help me, and that I don't need to go to the Samsung support with the phone wiped. Thanks,
~imatheussm
When you say you've tried from zero, do you mean you've flashed a stock rom?
Sent from my GT-N7105 using xda app-developers app
3vo3d said:
When you say you've tried from zero, do you mean you've flashed a stock rom?
Click to expand...
Click to collapse
When I had this problem, the second/third thing I did was flashing the stock ROM. But it was with these problems too, and with some other weird things: the S Note and the Samsung Keyboard giving FC almost every second.
~imatheussm
Well I guess if you're getting these issues when completely on stock I reckon you need the service centre?
Sent from my GT-N7105 using xda app-developers app
Have you try formatting your internal sd? I got similar problem too when flashing 4.3 mj5 leak.
Also got a uid mismatch when the phone start. I format my internal sd then flashing 4.1.2 firmware back.
Not a problem after that.

[Q] Xperia arc s wifi problem CM11

I have Arc S and CM11 on it. I don't have latest update since on latest messaging app is buggy. When i connect to open network everything works fine, but if i try to connect to protected network, it doesn't connect properly. I did not reflash CM11 to check if it fixes problem, nor factory reset. My friend told me it is wifi modules problem but i can't find any for this phone/ROM. Any help appreciated!
EDIT: I will reflash only if i need to (if it solved problem to anyone), cause i have many apps, accounts, etc...
DarkAnzy Kernel + AORP 4.4.2 RC1.2 - wifi not working
DjDexter5GHz said:
I have Arc S and CM11 on it. I don't have latest update since on latest messaging app is buggy. When i connect to open network everything works fine, but if i try to connect to protected network, it doesn't connect properly. I did not reflash CM11 to check if it fixes problem, nor factory reset. My friend told me it is wifi modules problem but i can't find any for this phone/ROM. Any help appreciated!
EDIT: I will reflash only if i need to (if it solved problem to anyone), cause i have many apps, accounts, etc...
Click to expand...
Click to collapse
I've installed DarkAnzul kernel 3.4 with custom ROM AORP 4.4.2 RC1.2 .
Everything is fine, except for wifi. I can't switch in ON.
I read in some thread that maybe installing wifi modules from DarkAnzu would arrange it. But just flashed it and it's not working either.
Any help would be appreciated.
Thanks.
Alex.
DjDexter5GHz said:
I have Arc S and CM11 on it. I don't have latest update since on latest messaging app is buggy. When i connect to open network everything works fine, but if i try to connect to protected network, it doesn't connect properly. I did not reflash CM11 to check if it fixes problem, nor factory reset. My friend told me it is wifi modules problem but i can't find any for this phone/ROM. Any help appreciated!
EDIT: I will reflash only if i need to (if it solved problem to anyone), cause i have many apps, accounts, etc...
Click to expand...
Click to collapse
If you get the problem connecting with protected network since the day you flashed your rom, reason may come from your rom or kernel. Try to reflash another kernel, if it does not help then you should try another rom. In case your wifi problem has just happened recently, factory reset or reflash, it's up to you.
Hope it help, you can wait for other suggestions!
tekieboy said:
I've installed DarkAnzul kernel 3.4 with custom ROM AORP 4.4.2 RC1.2 .
Everything is fine, except for wifi. I can't switch in ON.
I read in some thread that maybe installing wifi modules from DarkAnzu would arrange it. But just flashed it and it's not working either.
Any help would be appreciated.
Thanks.
Alex.
Click to expand...
Click to collapse
Have you tried to flash the kernel inside the AORP 4.4.2 RC 1.2 zip?
motlanvamaimai said:
If you get the problem connecting with protected network since the day you flashed your rom, reason may come from your rom or kernel. Try to reflash another kernel, if it does not help then you should try another rom. In case your wifi problem has just happened recently, factory reset or reflash, it's up to you.
Hope it help, you can wait for other suggestions!
Have you tried to flash the kernel inside the AORP 4.4.2 RC 1.2 zip?
Click to expand...
Click to collapse
I downgraded to CM 10.2 release version, it seems that its ok on it, so it is definitely problem with new cm 11.
DjDexter5GHz said:
I downgraded to CM 10.2 release version, it seems that its ok on it, so it is definitely problem with new cm 11.
Click to expand...
Click to collapse
Until now, CM11 is not really stable enough yet, however, our developers still keep working hard to make it better, just waiting.
motlanvamaimai said:
Until now, CM11 is not really stable enough yet, however, our developers still keep working hard to make it better, just waiting.
Click to expand...
Click to collapse
Older versions were much more stable than last few. I (almost) thought they would soon release it finally, until now...
It worked!
motlanvamaimai said:
If you get the problem connecting with protected network since the day you flashed your rom, reason may come from your rom or kernel. Try to reflash another kernel, if it does not help then you should try another rom. In case your wifi problem has just happened recently, factory reset or reflash, it's up to you.
Hope it help, you can wait for other suggestions!
Have you tried to flash the kernel inside the AORP 4.4.2 RC 1.2 zip?
Click to expand...
Click to collapse
I've just flashed the boot.img inside the .zip . Rebooted.
Wifi is working perfect!
AORP rom is the best 4.4.2 rom I've tried on my Arc S. It's fast, stable and now everything works.
Thanks motlanvamaimai for the help.
Wifi module
My wifi is not working. After flash Wifi module from Dark Kernel CM11.0 http://forum.xda-developers.com/showthread.php?t=2549742
It is working fine now. You may try it
Device: Xperia Arc S (LT18i)
Kernel: [Kernel][CM11]Vatsal's Kernel v3
ROM: [ROM][4.4.2][24/02/02/14] Unofficial [Arc/Arc S/PRO][1.3] AOSB Project - The End of The Line !

Rebooting Problem

Hi,
I'm new to this forum and hopefully someone can help.
I've just rooted my Samsung Galaxy s4 Mini (first time trying this), to CM 12.1 and I'm currently on kernel 3.4.0, version 12.1-20151020-NIGHTLY-serranoltexx, baseband I9195XXUCNJ6 and my phone seems to reboot near enough once every other hour. At the time it's not in use and when in use seems to work fine. I did read elsewhere to wipe both cache and dalvik cache, I done this but hasn't solved the rebooting issue. I have tried searching the threads for any advice but can't find anything. Can anyone help please?
Many Thanks in advance!
Unroot and use built in root. If it doesn't help You had to install something that crashing Your system. Just back to state before reboots.
Chamelleon said:
Unroot and use built in root. If it doesn't help You had to install something that crashing Your system. Just back to state before reboots.
Click to expand...
Click to collapse
Hi Chamelleon, Thanks for your reply. Yes, I think it's down to installing items that conflict. I installed Avast Battery Saver and I think it clashes with the system battery saver, since removed it hasn't rebooted. I also had a problem with a lock screen that I installed which froze my phone, than once I managed to remove it, the phone was fine. I originally installed the CM 12.1 root dated 30/09/2015 and installed the nightly from 21/10/2015, and have this morning installed the nightly update from 22/10/2015 and all seems fine. Again, thanks for the advise, it's much appreciated!

Categories

Resources