Hello everyone...
I always flash new roms to my GN...most of them were working fine...but some of the roms seems have some problems....
After I flashed a new rom, it always works perfectly...i can reboot/ restart and restore the apps without any problem....but few days later....it reboots automatically...and stuck at boot screen...but even i search the thread of the custom roms...seems no one got this problem....I can boot to CWM ....and i tried to fix it ....even i install the rom again...it still stuck at the boot screen....and i finally wipe the data....then it can boot normally again....then i restore my apps once again....everything return normal..........for few days only....and it stuck at boot screen again....therefore....i can only enjoy the rom for few days (maybe 3-4 days)..work perfectly for few days....but it will crash accidently without any symptom..........
Then i tried other roms...........some roms dont have this problem (mostly aokp/aosp base)...and some roms usually have this problem (non-aokp/aosp base)....after suffer this problem several times for different roms.....i just think that it may not the rom's problem..but i cant figure out why this will happen....I reli want to know is there anyone got this problem too or any method to tackle this problem...
Thx alot and sorry for my poor english....
Exactly which ROMs reboot
Is it jellybean touchwiz ROMs?
Sent from my Nexus 7 using Tapatalk 2
Yes..Touchwiz roms....for example...AmniX"-Xperia Note , SlimWizz5 Tablet...
Only work fine for 3-4 days....:crying:
You should reinstall apps from the market, restoring apps from backup may leave your phone in a strange state especialy in JellyBean.
you should also flash the JellyBean bootloader.
Hope that helps.
Good day all, first timer posting but have been reading the forms for a while now.
I have a major problem with my galaxy note GT- N7000. I have browed through the forms and have not seen a problem like mine. I really need help with my phone.
Problem:
The phone is rooted with paranoid android rom; current version PA_n7000-3.60. I have been using this for over a year with no problem, when all of a sudden the phone goes into android update screen and ever since been on that screen whatever I do. I never tried to update the rom or anything when this happened, just found it like that. All auto update are turned off.
I have tired installing the rom again using CWM and even tried installing the latest update still the problem persists.
I don’t want to format the phone because I have some very important information I will lose if I do. Cannot back up using CWM, getting error messages, cannot get access to phone via connection to my computer. I am in a jam and really need help with this.
Thanks.
Hi all, love this forum but dont post often.
Heres the problem: My HTC One m7 (international version) is acting strange:
* Sometimes when I turn on the display I have to enter my sim pin, as if it had rebooted itself, only I know it hasnt. It also happens regurarly when Im using the phone *poff* all of a sudden "enter sim pin".
* When switching from wifi to 3g/LTE it lags for minutes. It drops all connections, including regular gsm, and I have to enter sim pin maybe half the time I swith from wifi. Switching from 3g/LTE to wifi doesnt present the same issues.
* Its extremely laggy when these things happen, otherwise it works fine.
What I have tried so far:
* Old backup of Liquidsmooth 4.4. Works fine for a few days then these same problems starts occuring.
* Uninstalling apps. Thought I was onto something when I uninstalled SwiftKey and it worked perfectly for about 3 days! But then the problems came back...
* Tried other roms but I usually end up with the "unfortunately the process com.android.systemui has stopped" when the rom is up and fully booted. Its a loop that just continues (when pressing ok) so I cant do anything but reboot and try again. I tried probably 5 versions of Liquidsmooth but also Beanstalk and other aosp roms, even Lollipop versions (the liquidsmooth one worked but the same sim pin problems occurred). Havent tried any sense based roms. Also tried several versions of TWRP, official and unofficial. Still ends up with the com.android.systemui problem.
* Tried resetting permissions, wipe cache/dalvik and also wiped the entire sdcard. Used adb/flash to transfer new rom for installation.
So I'm basically out of ideas and pondering going back to stock and sending it in for repair, unless someone here has some tips since I'd rather try myself first.
Thanks for any help or input!
koolkeith said:
Hi all, love this forum but dont post often.
Heres the problem: My HTC One m7 (international version) is acting strange:
* Sometimes when I turn on the display I have to enter my sim pin, as if it had rebooted itself, only I know it hasnt. It also happens regurarly when Im using the phone *poff* all of a sudden "enter sim pin".
* When switching from wifi to 3g/LTE it lags for minutes. It drops all connections, including regular gsm, and I have to enter sim pin maybe half the time I swith from wifi. Switching from 3g/LTE to wifi doesnt present the same issues.
* Its extremely laggy when these things happen, otherwise it works fine.
What I have tried so far:
* Old backup of Liquidsmooth 4.4. Works fine for a few days then these same problems starts occuring.
* Uninstalling apps. Thought I was onto something when I uninstalled SwiftKey and it worked perfectly for about 3 days! But then the problems came back...
* Tried other roms but I usually end up with the "unfortunately the process com.android.systemui has stopped" when the rom is up and fully booted. Its a loop that just continues (when pressing ok) so I cant do anything but reboot and try again. I tried probably 5 versions of Liquidsmooth but also Beanstalk and other aosp roms, even Lollipop versions (the liquidsmooth one worked but the same sim pin problems occurred). Havent tried any sense based roms. Also tried several versions of TWRP, official and unofficial. Still ends up with the com.android.systemui problem.
* Tried resetting permissions, wipe cache/dalvik and also wiped the entire sdcard. Used adb/flash to transfer new rom for installation.
So I'm basically out of ideas and pondering going back to stock and sending it in for repair, unless someone here has some tips since I'd rather try myself first.
Thanks for any help or input!
Click to expand...
Click to collapse
maybe your sim is faulty. try to get a new one from your provider. or it just has a bad contact in your phone.
about the lagging: did you try a clean flash? is your storage full? my phone gets pretty laggy when my storage is nearly full..
Hey thanks for your reply! However I dont think its the sim card, and as I mentioned I clean flashed several times with several twrp version and also twice with wiping all data on my sdcard...
Sorry if I can't offer a concrete solution, but I had similar issues (especially the first one, but also lag when switching networks) on my HOX+. Turns out it was the sim.
Try to test another sim before returning, and at least try a sense based rom. Since you say that it works without problem for a few days with Liquidsmooth 4.4, and then it starts breaking again, it may be rom (aosp?) related. But then again, it may be just random.
Hope you figure it out soon
Thanks akpe! I ordered a new sim card, if that doesnt help I suppose its something hardware related...
Well, the new sim card didnt help. My problem seem very similar to this: http://www.androidpolice.com/2013/0...rops-on-some-nexus-4-handsets-fixes-in-sight/
Basically my whole radio disconnects and restarts itself when turning off wifi. Reading that androidpolice thread leads me to thinking about flashing an earlier firmware, from 4.2.2. I have no idea which one, or if I can use the one in that thread or not.
Any suggestions? I'd appreciate it, googling for hours and reading catlogs for days isnt getting me anywhere..
HELP!
Hmm wasn't that a Google issue which got fixed by HTC in the latest OTA? Try a ROM which has the hotfix (like latest ViperOne, 7.0.2) and see if you still get this
akpe said:
Hmm wasn't that a Google issue which got fixed by HTC in the latest OTA? Try a ROM which has the hotfix (like latest ViperOne, 7.0.2) and see if you still get this
Click to expand...
Click to collapse
Hi akpe! I took your advice and am now running ViperOne 7.0.2 and so far it WORKS! So it seems it was indeed that google bug. HUGE THANKS!
Is it possible to have the aosp lockscreen when at the same time using a pin? I can't seem to figure that out.
Thanks again!
Glad it worked
As for the lockscreen, no idea mate, I'm using the stock one :/ Ask around in the ViperOne thread, maybe someone there knows
Ok, thanks again!
Another thing I cant find is profiles? Need it to make whatsapp notification sound silent when listening to music..
Hi Guys. I have searched the forum but havent found anything that applies to my problem. I have the HTC One M7 sprint version. I have been trying to sim unlock it but the phone came on an android version higher than 4.3. This is one of a batch of 4 so at this point I cant even remember the original os. My problem is that I need to be on an android os lower than 4.3 to unlock. I have been following the tutorial here: http://forum.xda-developers.com/showthread.php?t=2586704 .Only roms at kitkat or higher are stable enough to use and not even all the kitkat ones are stable.
The issue:
The phone boots and the rom loads but I am unable to do anything with it. The lockscreen shows as normal but anytime I unlock the screen I get a white screen with HTC in green letters. On some roms I am able to access the settings menu but that is it. It just stays like that forever. On some roms it will stay on but most reboot in roughly 2-3 minutes. Most of the roms that are stable go into a handsfree activation loop where I cant get past that screen. I read a tutorial about deleting the htc setup apk but that works only some of the time and then the roms are mostly unstable.
My phone is S-Off and I have attempted to downgrade to stock 4.1.2 using the official ruu.. The process was successful but the stock os is unstable. Reboots every 2-3 minutes. I have flashed the firmware separately and then run the ruu. I have run the ruu on its own. I have done factory reset with both stock and custom recoveries after running the ruu.
I have tried pretty much every sprint rom I have come across and still no love. I've been at this for nearly a month and my HTC Rom folder is about 25gb if a list is needed I am willing to provide it but I really just want to be on stock 4.1.2 or a sense rom lower than 4.3 for the purpose of unlocking the gsm sim. I have been told that the issue could be hardware but then I have roms that run without issues except that the phone isnt unlockable in that state.
Hi guys and gals.
I've been flashing roms for years and I've soft bricked my devices dozens of times and have always been able to recover, except this time.
I was running Cyanogen mod 12.1 and all the problems started happening after a nightly update. Basically, the phone got super laggy and eventually started random rebooting. I thought it was a bad flash or something was wrong with the latest update so I did a clean wipe and flashed another rom, same thing happened. Eventually I Odined back to stock and it ran fine for a few days but the problems came back. Now the phone won't even finish boot anymore. I used NAND erase all in odin and and reflashed again, it seems to be better since it wont reboot its self anymore but I can't get past the T-mobile splash screen. Last night I tried reformating the NAND using a PIT file but I kept getting "Secure check fail : PIT". I was starting to thing the problem is hardware related but it won't RR in download mode and I think its too big of a coincidence that it happened after the Cyanogen update. Any ideas?
My first and always main advice is that if you are unsure about your hardware the first step is to Odin back to stock. The reason is because it is a bit for bit rewrite back to the way the phone was intended to be run as long as you do a factory reset from Stock Android Recovery before it boots. This is how your phone was when it came out of the box and it is a great way to check if it has a hardware issue by looking for bad behavior when using the original drivers.
If you flash back to stock completely clean and your phone is still acting crazy you might have bad blocks on your NAND, you might have issues with your RAM/CPU, or it might just be a loose hardware connection from heat or impact. But you can only truly diagnose those from Touchwiz because the drivers are first-party, not reverse engineered to be compatible. If you can reinstall all your apps and use it normally for a week then your hardware is good and CM was the problem and you should try another AOSP build.
I am on the 09/09 Nightly for CM and I can tell you that I have no lag or issues on my device at the moment for what that is worth. Good luck!
Thanks. I might just send it into samsung and see what happens.