I am having trouble with certain ROMs (nameless, carbon) where I do not have LTE or a cell phone signal. I also have no IMEI number when I dial *#06# on these ROMs.
The weird thing is if I flash AOKP or SlimRom I have signal and an IMEI everything works fine, it wouldn't be an issue except AOKP take 20 minutes to boot up every time and SlimRom keeps randomly rebooting on it's own and runs slowly.
What I tried was this: Flashed SlimRom > downloaded Terminal Emulator > ran "su" then "reboot nvbackup" > then once it rebooted I went back to recovery and installed Carbon > again installed Terminal Emulator > ran "su" then "reboot nvrestore" > after that it got stuck on the GS3 splash screen until I wiped and reinstalled a ROM. Still no fix.
What do I need to do to fix this proper?
P.S. The only *#xxx# number I could get to work was the *#06#, the rest do nothing on my phone.
Nobody?
Related
A few days ago I went from stock 4.1.2 Touchwiz on my Verizon S3 to Cyanogenmod 10.2 Stable.
Since then I've run into the following issues:
It shutdown and restarted itself once in the middle of typing a reply to someone in Facebook
Roughly 40% of the time when I choose to restart or when I shutdown and then restart by holding the power button, it will get to the CM loading screen (spinning arrow around the head) and then shutdown and reboot a second time before actually loading fully
Roughly the same amount of times as above, when I reboot and actually get into my phone I will not have a connection to 4G/LTE (The bars show up but I have no data connection). I have to either reboot again or disable data and then re-enable it through the options.
Once after an automatic double reboot, it said my baseband version was unknown. This only happened once and "fixed" itself after another reboot. It usually shows as I535VRBMF1
My flash steps from stock Touchwiz 4.1.2 to CM10.2 was as follows:
Rooted, unlocked bootloader, and installed CWM using the CASUAL method
Updated CWM through Rom Manager to 6.0.4.3
Booted into recovery and made a NANDroid backup
Wiped the data through CWM
Installed CM10.2 stable from the file on the CM website after placing it on my phone's memory card at root
Installed Gapps labeled 20130813 after placing it on my phone's memory card at root
Booted into Cyanogenmod 10.2
Rebooted into recovery and cleared the cache and dalvik after the first random restart occured roughly 12 hours after the initial flash of 10.2
I'm at a loss here. Did I miss a step somewhere or is there something I did wrong? How can I possibly fix this so that I have a reliable reboot and reliable data connection?
Hi Guys,
I have been running WCDMA Only on my N5 with 4.4.2 for some time and every time I rebooted, the setting stuck. Now after the upgrade to 4.4.3, the setting doesnt seem to stick.
*#*#4636#*#*
Phone Information and change to WCDMA Only. Hit home button and the setting sticks, but everytime I reboot now, its gone.
Any help on how to get it to stick. I did do a complete Wipe and installed the factory image including the new modem. I reverted to the old modem but nothing helped. Did a factory reset, went back to 4.4.2 and it sticks there.
Tried a new 4.4.3 pre rooted rom, but still nothing.
If you're rooted you could use tasker. But just normally I don't know that you can change it. I'm surprised it stayed before. Didn't use to in older versions when I used to do that
Yep I am rooted. The settings stick on another N5 here on 4.4.2 with the same setup. It just seems odd I cant get mine to stick after reboot. Any build.prop edits anyone knows?
Bump. Hoping someone could help me out here.
SOLVED:
If you cant get the setting to stick do the following.
1) IF you want to run ART then.
a) Switch to Dalvik, Install xposed framework, install Intelli3g from Playstore
b) Reboot and run Intelli3G, make the network change
c) Reboot and see the setting stuck by going to *#*#4636#*#*
d) If so, then uninstall xposed framework via the installer
e) Reboot to see if the setting stuck by going to *#*#4636#*#*
f) Switch to ART and see if the setting stuck. It should have.
IF you dont run ART, do all the above besides uninstalling xposed. Stop at step C.
Hi,
I flashed liquid smoth ROM and when it booted it started getting an error every few seconds: the process.com.android.systemui has stopped.
I powered off the phone and attempted to boot into recovery but I couldn't. The phone seemed to be bricked. I had to press the two volume keys and the power button to unlock it.
It booted into recovery, I wiped everythig even internal storage and flashed CyanHacker Rom and gapps after. It booted and surprisely I got the same error: the process.com.android.systemui has stopped.
Now I am trying to boot into recovery again but the only thing I get is the capacitive buttons flashing for a few seconds.
Any idea?
Thanks!
I connected the phone to the computer and I was able to use the adb shell so that I rebooted the phone and it booted normally. After selecting the wifi network I get this error again
Try disabling wi-fi, reboot, then goto Settings > Status Bar > Signal Strength > Hide, reboot and enable wifi.
The settings for signal strength feature maybe located in a different place or have a different name depending on the rom you're using.
Rkr87 said:
Try disabling wi-fi, reboot, then goto Settings > Status Bar > Signal Strength > Hide, reboot and enable wifi.
The settings for signal strength feature maybe located in a different place or have a different name depending on the rom you're using.
Click to expand...
Click to collapse
Will try flashing one of those again and see if that fixes it.
Later edit5: Tried to restore my nandroid backup and TWRP froze. Had to hard reboot the phone...
Later edit4: It started working. It f***** started working. Out of nowere. Last night, the last thing i tried was this: https://forums.oneplus.net/threads/fix-for-sudden-death-and-boot-loop.146107/
I rebooted the phone and it didn't work. I gave up.
This morning I turned it back on and ... surprise, surprise... it started working (optimizing apps and actually booting into cos12.1).
My happiness didn't last because as soon as the phone started updating some apps, it crashed, and entered a boot loop again. Good thing i managed to copy one of my previous backups.
Can someone explain this behavior?
Later edit3: my phone is still stuck in a bootloop. Neither roms are working.
Things I've tried:
- flash new roms
- erase/ flash persist
- flash color os
Nothing works!
Later edit2: while on cm13, i plugged it in to recharge. While connected to wall plug it did nothing(working fine, as it should be). As soon as i unplugged it started rebooting over and over again... a boot loop. This phone is starting to look like one of the biggest mistakes i ever made. I regret purchasing it.
Later edit: now it just turned off, and pressing the power button won't turn it back on. Had to press it for about 10 - 15 seconds. ANNOYING!
OP: I've been experiencing random reboots on my oneplus ONE since I've had it.
When i first got the phone, i was so excited about it and started flashing custom roms, just for fun and to see which one suites me. I messed up the phone (my camera wouldn't work anymore. All the roms gave me the same message"Camera has stopped working" ) and sent it back to warranty, here in my country, at the shop from which i've bought it. After two weeks they sent it back to me with the note "restored to factory settings". I've checked the "About" section and it was running cos12.1, 1 jan 2016 security patch, kernel 3.4.67.
So I've decided to stick with this rom because I didn't want to mess it up again. But, out of nowhere it rebooted. First i thought that it was an app that needed the phone to reboot. I didn't mind it. I've left my phone over the night and in the morning it was saying "enter pin" as it has rebooted.
Long story short, ever since it reboots at least 1 time a day, and it is getting really frustrating! Sometimes when i'm in an app, sometimes when it just lays around.
Reasons it rebooted:
- no reason, just siting and it rebooted
- opened waze app
- browsing chrome
- tried to connect to a saved wireless network, it rebooted and afterwards the network was not recognized anymore and had to retype the password
- no reason!!! just sitting!!
- fresh install of cos 12.1, i queued about 20 apps to install... it rebooted and continued installing after reboot.
- sometimes i heavily use it and it runs perfectly, but when i stop using the phone and lay it down it reboots. (this only happend one time)
Things I've tried:
- factory reset
- clear cache and dalvik cache
- power cicle the phone
- new rom
None of these worked.
Today I installed sultans CM13, with his 3.4.0 - sultan - caf kernel, hoping that my problems would disappear. (I installed TWRP 2.8.7.0.5, flashed the rom, cleared the cache, flashed the gapps, cleared the cache and reboot.)
It ran flawlessly. I've installed all my apps, played a little with it, configured it as I pleased and I've left it the table for about 15 minutes. When i picked it up, it rebooted(AGAIN!) out of nowhere.
What could it be? As I read through the forums i found out that a log with the exact problem is impossible to get because it gets deleted.
Could it be the wireless network? Could it be the sim card I am using or the phone modem? Could it be because of the launcher?
(for now, i've disabled my sim pin so when my phone reboots i don't miss phone calls if i don't notice it has rebooted)
Please help, as this problem is getting more and more frustrating...
Reboot log
Quickly after a reboot i reconnected the phone, opened cmd and typed adb logcat.
This is the log. 22:17 is the time when the phone rebooted so i extracted only that fragment of the log.
I am going to flash the stock cm13 nightly with the "stock" version of gapps. (until now i always flashed "nano").
Hi, I am hariharan. I need help guys. i restored my nexus 5 from cyanogenmod 13 to stock android 6.0.1 by wiping my device completely and format data option in TWRP. Everything went fine during formating the data except one error
"flash image /dev/block/platform/msm_sdcc.1/by-name/metadata /dev/zero process ended with error: 225"
And normally i restored my device with stock android 6.0.1. My device booted up normally.
After skipping the initial setup i made a call to my dad,it went dialing for 20 seconds with out any ringing sound and ended. When others tried to call me they heard that my phone was switched off.
I rebooted and once again tried no change. I changed the SIM to another mobile and checked the SIM was fine. I tried every stock rom released for nexus 5 but no luck. I also tried many roms but still no change. I also installed modems from the thread http://forum.xda-developers.com/goo...t/modem-nexus-5-flashable-modems-efs-t2514095 no luck in it.
But the data is working.
How could i solve this?
It could not be a hardware problem, as everything worked before the whole mess started up.