Hello, I have a problem with my Nexus 4.
Everything was working fine (Even the SIM card) under a MIUI ROM, obtained from the MIUI port team of XDA. I wanted to install Ubuntu Phone, so I wiped everything.
When I say everything, is everything: Cache, Data, Dalvik... And I formated everything too: System, Data, Sdcard... So the problems started. I wasn't able to flash the phone to go back to stock, with the Nexus Rootkit. I installed the 1.6.6, the last version, and after many attemps I have now a fully customizable phone again, which is able to go back to stock or to a custom ROM, if I want.
The problem is that the SIM is not working. I'm trying to flash to 4.2.2 Stock again (because I've tried it two times) to see if it fixes the problem, but I guess that again, it won't.
So, any ideas?
Thank you very much indeed.
EDIT: The 4.3 update arrived and it fixed the problem automatically.
Related
So ive had my n7 for a while and had over 10 different roms that i went through before landing on cookies and cream for 4.1.2 and cyanogenmod for 4.2.1
Well heres the problem. i was getting pissed off at all of the bugs and random reboots and incompatabilities so i fully wiped the device, minus bootloader, and flashed stock 4.1.2, it booted great
heres where it went wrong... i tried flashing cyanogenmod 10 via twrp, letting it use its stock kernel and even trying a different cm compatible kernel after booting failed.
when that didnt work i went back to stock, downloaded cookies and cream, wiped the rom, cache and dalvik cache. still bootloops
so i was like F**k it, and installed stock 4.2.1, booted fine.
tried again with the 2 latest cyanogenmod nightlies, which i know worked fine from before
still just bootloops with no idea how to fix it.
just to be clear, stock works, custom WILL NOT
bump guys, im kinda up **** creek without a paddle, emphasis on the kinda part
I have a similar problem(http://forum.xda-developers.com/showthread.php?t=2073977). Pretty much the only way I can get a ROM to stick is if I wipe /data as well. Not sure what's causing this, but I'm working on it. I think it could have something to do with the way that android stores some of it's /system data in /data at times
What's worked for me to flash a ROM other than stock, is to wipe the entire thing, and then use adb sideload to load the ROM.
Hey bro, i saw your thread before, by data, do you mean internal storage or just the system rom itself, because i wiped everything but the bootloader and started from scratch
I'm just talking about /data. An hour ago I noticed that as long as I use the Factory Reset option in TWRP, it will wipe it, and not touch the stuff on the sdcard(it could be just me though, my Nexus seems to be kinda weird). Then I wipe system, and flash whatever I need to.
Alright, one problem though, doing a factory reset deletes everything on the sdcard then when i try to use fastboot to flash cyanogenmod in a zip format it says stuff like android-product-info.txt is missing and whatnot, what do you do?
edit, dont read the part about wiping storage, i had a idiot moment there, ill give it a shot
I have been a lurker around here for some time, but never posted. So Howdy!
I am having some troubles with my LG G2. I have loved the phone so far, and has custom TWRP recovery and rooted. Other than that the device was stock with some very minor mods (xPosed framework, etc..
I stupidly forgot that I had TWRP installed, and I chose to take the recent T Mobile OTA. The phone wouldnt boot past recovery despite a factory data reset. I flashed the stock rom (tried both D80110C and D80110G) to no avail. factory data reset again, re root, installed TWRP again, cleared cache and dalvik, and everything was fine EXCEPT the knock on feature doesnt work. Knock on works just fine, but I cannot knock to wake the device. The power button wakes the device just fine.
Anyone have any thoughts?
Also,
I was considering flashing a rom, like Gummy rom. I don't really have any hypothesis behind this, as I have already flashed the stock rom kdz twice now.
sailoholic1234 said:
Also,
I was considering flashing a rom, like Gummy rom. I don't really have any hypothesis behind this, as I have already flashed the stock rom kdz twice now.
Click to expand...
Click to collapse
Hey, is your knock on issue resolved? also try CloudyG3 rom, its realy smooth.
Need some expert assistance. The problem is my phone keeps crashing with systemui errors when using custom roms. It always happens after a reboot and usually within 1-3 days, depends on WHEN I reboot the phone. Let me give you a little backstory.
A little over a month ago, I was running AICP on my phone, but decided to try SimpleAOSP and Hells doctor.. So I created a backup in TWRP, then flashed SimpleAOSP and HD. The next day day I started getting the errors. At the time, I thought it was the kernel or a Titanium Backup glitch.
So I wiped and reflashed SimpleAOSP without HD and without restoring from TB. But the next day, systemui failed to start. I thought it might be a rom issue so I restored AICP from my TWRP backup. And I couldn't believe it when the same systemui errors happened. So I restored the backup again. Again it was okay for a few days, then error.
After that I copied everything from my phone to the PC and wiped internal storage. Then installed the same rom version from AICP that I had been using for weeks prior to all this. Same error after a few days.
So next I tried wiping internal storage again and flashing stock 4.4.4. I used that for over a week with no system errors. So I did a TWRP backup of Google stock rom, Then installed AICP again but this time without modifying any systemui type settings, I left the rom as stock as it could come. Didn't even restore apps or anything. I then the rebooted the phone a couple of times to test and the error came back. This was the same day I installed it.
So I restored the stock backup and have been running fine all week. I want to get back on a custom rom though. Any suggestions?
Am I getting no replies because I'm missing something really obvious?
Or can no one think of anything that I haven't already tried?
By the way, right after posting the OP I installed the L preview and it's been working fine so far. I figured if I had to run stock android it may as well be the latest thing.
Sent from my Nexus 4 using Tapatalk
I don't have any answer to your question but I was wondering if this happens without installing a custom kernel on CM11 and AOSP custom ROMs.
Thanks for replying.
When I tried SimpleAOSP, it was with and then without an additional kernel. I saw no difference as far as the error is concerned. I have not tried a CM11 based ROM since this all started.
Maybe I should try a custom rom that doesn't have heavy modifications like AICP has.
Sent from my Nexus 4 using Tapatalk
Are you flashing a Gapps package? A couple weeks ago when I was trying different ROMs I was getting system crashes after flashing PA Gapps and they updated. I never narrowed it down, but after uninstalling a bunch of them (News/Weather, Talkback, Keep, Newsstand, some others) so they wouldn't update, I stopped getting system crashes.
Idk why I have the feeling your theme/icon pack has something to do with it. I run pa and whenever I try to use click ui icon pack it happens to me but if I just run veu I don't have a problem. Try not using themes for a bit to see what happens
Sorry, I missed your responses, I had kinda given up on the whole thing. Android L is running good for an unfinished product.
Getting back to the original issue, no theme or icon pack was installed.
Yes, I was using PA gapps mini from 9-23. Maybe that was it.
But that would be weird because I don't remember my first ROM running PA gapps, not 100% sure... that was a month ago.
I'll try to install without any gapps package and report back. Thanks.
Sent from my Nexus 4 using Tapatalk
from my past history, I'm facing issues when I did 3 things :
1. if I just dirty flash or factory reset only before flashing new rom.
2. Did restore backup from TB (which from your explanation above, you don't have any problem TB)
Nowdays I always use wipe dalvik, system, data, cache. Because someone once told me if you changing roms, if not it's possible that the system setting from old rom will crash with the new ones. and for the wipe system part (some roms included that command in their roms zip file and some didn't).
Good morning,
I'm stuck with a big problem on my Note 3 HLTE.
Here's the story : I was previously on the PAC Rom 5.1 and I wanted to change to get the CM13.0 that was just released. So I've performed the full wipe (dalvik, cache and factory reset) and then when I wanted to update the OS, it didn't work. I ended up with a phone in recovery, telling me that there was no OS installed on it.
after several attempts, I then tried to revert back to a stock ROM based on 4.4.2 with Odin. The installation went on without any problems, I was able to get through the first install with my Gmail account and then the phone rebooted, and that's where I got the bootloop curse.
what I did then, was to redo an install via Odin with my carrier stock rom, and I got a FAIL message. So, I retried an install with Odin by adding a PIT file and another ROM still based on 4.4.2. the install worked, as I was able to set up my Gmail account and so on. At this stage, I wasn't able able to get any signal for calls, 4G . In parameters, the baseband was identified as "Unknown". Then, the phone rebooted again, and I got the bootloop curse again...
My last attempt has been to install my carrier stock ROM after performing a full wipe, with ODIN. The install was successful and I got the phone rebooted to stuck on bootloop.
So, here's where I am, and I would like to solve this problem, please. What I think is that, due to the fact that I was on Lollipop, the bootloop might be due to the downgrade attempt to KK. So if there's any way to solve this problem, I'm eager to take it.
Thank you !
Hey Guys,
I've been able to resolve my bootloop problem.
I've installed TWRP with Odin, made a full wipe including data (I've saved them before), and I installed the CM12.1 by Temasek, and way to go, the phone is running fine ^^
Now, I'm just stuck with the lost IMEI thing and baseband. SO my question now is : if I want to install my operator stock ROM for getting back, should I just choose the Lollipop ROM, or can I take the KK one without getting stuck in bootloop again ?
Thank you !
Hello all,
I recently went through the process of installing CM 14.1 on my Verizon-Unlocked Galaxy S5.
Everything was working fine until about 3 weeks ago when I started messing with the system settings.
My phone started freezing and crashing, so I attempted to reinstall CM 14.1 multiple times.
I have wiped everything on the phone multiple times through TWRP (System, Data, SD Card, Everything...) and I am still having the same issue.
The phone boots fine, and I am able to get through the first two menus in the initial setup, but then the screen freezes and the phone restarts.
I have tried replacing the battery, thinking that would fix the problem, but it didn't...
Should I revert back to the stock ROM and start from there, rooting and such, until I make my way back to CM?
Thanks everyone, Luke
If youre still having problems, try reflashing your rom and then flash an older version of opengapps, I think I used the one from 01/16/17. The new opengapps were giving me the same exact problem.
Dang, I wish I would have seen this sooner... I went ahead and flashed back to the stock Verizon ROM with root. Thanks though! Maybe this can help someone else.