Hello. Before installing the Build 8 & 9 Paranoid Android rom from TonyP (or attempting to install it), I installed the P999 rom from Kashamalaga successfully, although it has no wifi-calling and it also has the battery drain. I wanted to circumvent the battery drain, so I have tried to switch to builds 8 & 9 by wiping the cache & dalvik cache, then flashing the zip with the rom, the gapps and the new baseband zip one after the other. I turn it on and everything is fine except for receiving calls. Am I doing something wrong with the baseband, or anything else? I have tried doing full wipes, but they have not fixed the issue. Thanks in advance.
EDIT: I have been using ClockworkMod Recovery v5.0.2.0 and I have been doing the following:
wipe cache->yes->advanced->wipe dalvik->yes->install zip from sd card->choose zip from sd card (3 times)->pa jb rom buildx->newbaseband.zip->gapps.zip->reboot
EDIT2: It works now. Did a full wipe and I believe I did newbaseband->build9->gapps. Someone correct me if I should do it otherwise but I'm currently testing it to make sure everything else is working (calls fixed).
EDIT3: The battery is still a bit wonky even after doing a battery stats wipe, but it has extended battery life for the most part
Related
Hi all,
I've recently tried to update the Matr1x kernel to the 9.0 CFS version on my already installed NSCollab 1.0.50 mod. Unfortunately, this didn't seem to go so well, because my Nexus S (i9023) entered an infinite reboot loop. I was a bit surprised since a lot of people seemed to have no problems with this kernel, and even though I'm new to this stuff, I tried to follow all the guides & tutorials around.
Anyways, here's what I did:
- I downloaded the kernel on my phone from this forum;
- I used ROM Manager, selecting the "Install ROM from SD Card" option;
- I let the "Wipe Dalvik Cache" option enabled.
Once I experienced the reboots, I dropped into recovery and tried to re-wipe the cache & the dalvik cache several times, with no luck. I then proceeded to restore the backup I made before doing this...
Did I do something wrong or stupid?
try flashing the rom(gapps if needed) then the kernel, then reboot.
simms22 said:
try flashing the rom(gapps if needed) then the kernel, then reboot.
Click to expand...
Click to collapse
Does this mean I have to wipe my data again?
I've never used ROM Manager to flash anything (I prefer to be hands-on and do it myself), but if you told ROM Manager to install a ROM from zip and fed it a kernel file, I can't see how that can possibly have a positive outcome hahaha.
Go into CWM, do a factory reset/full wipe and reinstall NSCollab 1.0.50. Once you've installed that, you can immediately install a custom kernel. Reboot, wait for it (the first boot always takes longer) and you should be fine.
Greetz
PS: Remember to always make backups with Titanium Backup, or even Nandroid backups if you're not sure about the actions you're about to do.
mux_ said:
Does this mean I have to wipe my data again?
Click to expand...
Click to collapse
no. go to recovery(dont use rom manager), flash your rom(and gapps), flash the kernel, reboot.
Well, since my system was still fully functional (as I said, I had done a backup from ROM Manager previously and restored it), I tried the manual method first; that is dropping into recovery, wiping dalvik cache, and using 'install zip from sdcard'.
Everything went just fine, and I'm running the Matr1x 9.0 CFS kernel without any issue for now!
Thanks a lot for the help.
Hello,
I was running the CM10 Alpha 2 for my GSII. Alpha 3 came out so I decided to update. I installed the newest CWM and the alpha 3 package, gapps and darkside wipe.
When installing I had no problems that I noticed. Everything said it worked fine. However, once rebooting the phone after darkside wipe finished, I couldn't boot up my phone. I can get past the Samsung screen, but I don't even make it to the CM animation boot screen.
I decided to pull the battery after waiting a while and go back into recovery. I did this and decided to restore my backup. My phone is stuck on "Restoring .android_secure" right now and will not work.
I can use Odin to flash back to ICS and how to came but I'm wondering why it didn't work? I know I did the procedure right, as I did it when flashing CM10 alpha 1, 1a and 2. I read about needing the latest CWM for it so I got that, too. A bit of a weird issue that I'd post in the CM10 thread if I had over ten posts.
Thanks in advance to those who can help!
Droid111 said:
Hello,
I was running the CM10 Alpha 2 for my GSII. Alpha 3 came out so I decided to update. I installed the newest CWM and the alpha 3 package, gapps and darkside wipe.
Click to expand...
Click to collapse
I followed basically the same pattern and didn't have an issue, aside from the fact that I didn't Darkside wipe (if you are using the latest clockwork touch I don't think it's necessary anymore). I also flashed the instigator kernel (6.2.1) but that was after I rebooted without issue.
Sidenote, the instigator 6.2.1 seems to possibly have some overheating trouble, so I am running the Darkside Hercules kernel for the moment, and it seems to be working well.
Phizban said:
I followed basically the same pattern and didn't have an issue, aside from the fact that I didn't Darkside wipe (if you are using the latest clockwork touch I don't think it's necessary anymore). I also flashed the instigator kernel (6.2.1) but that was after I rebooted without issue.
Sidenote, the instigator 6.2.1 seems to possibly have some overheating trouble, so I am running the Darkside Hercules kernel for the moment, and it seems to be working well.
Click to expand...
Click to collapse
Yeah, reading the thread it seems like a pretty rare problem. Somebody actually posted something similar yesterday that I missed and nobody really knew. I wasn't sure if I should Darkside wipe or not so I chose to anyways. I haven't tried flashing a new kernal but as I said I can't even get to the boot animation.
Droid111 said:
Yeah, reading the thread it seems like a pretty rare problem. Somebody actually posted something similar yesterday that I missed and nobody really knew. I wasn't sure if I should Darkside wipe or not so I chose to anyways. I haven't tried flashing a new kernal but as I said I can't even get to the boot animation.
Click to expand...
Click to collapse
I would stay away from the darkside wipe, it has been reported through many threads that it can sometimes lead to problems when installing a rom. Your best bet is to just wipe data, format system, wipe dalvik cache, either format /cache or use Darksidewipe.cache not the darkside wipe that's wipes everything. Then install rom and gapps. Reboot phone and let it sit for 5 to 10 minutes, (i usually let it sit 10). From there you can decide if you want to flash one of the two available kernels, results may very with the two.
mjwhirly said:
I would stay away from the darkside wipe, it has been reported through many threads that it can sometimes lead to problems when installing a rom. Your best bet is to just wipe data, format system, wipe dalvik cache, either format /cache or use Darksidewipe.cache not the darkside wipe that's wipes everything. Then install rom and gapps. Reboot phone and let it sit for 5 to 10 minutes, (i usually let it sit 10). From there you can decide if you want to flash one of the two available kernels, results may very with the two.
Click to expand...
Click to collapse
Thanks for the help. I'm going to try it within the next few days. Right now I have SKY-ICS going fine but I'll definitely try that.
What do the different kernels do?
Droid111 said:
Hello,
I was running the CM10 Alpha 2 for my GSII. Alpha 3 came out so I decided to update. I installed the newest CWM and the alpha 3 package, gapps and darkside wipe.
When installing I had no problems that I noticed. Everything said it worked fine. However, once rebooting the phone after darkside wipe finished, I couldn't boot up my phone. I can get past the Samsung screen, but I don't even make it to the CM animation boot screen.
I decided to pull the battery after waiting a while and go back into recovery. I did this and decided to restore my backup. My phone is stuck on "Restoring .android_secure" right now and will not work.
I can use Odin to flash back to ICS and how to came but I'm wondering why it didn't work? I know I did the procedure right, as I did it when flashing CM10 alpha 1, 1a and 2. I read about needing the latest CWM for it so I got that, too. A bit of a weird issue that I'd post in the CM10 thread if I had over ten posts.
Thanks in advance to those who can help!
Click to expand...
Click to collapse
I used TWRP and flashed over CM9 with no problems. Did it as an upgrade. Wipe system> install CM10> install gapps> Wipe cache
Several people have reported that TWRP worked for them.
Hi. I got a problem with my One S after installing ParanoidAndroid.
System:
ParanoidAndroid
Kernel:
Fusion Ultimate v2.1 (OC Version)
How I installed:
1. Wiped everything, even SD Card.
2. Installed kernel by flashing with fastboot.
3. Installed from ParanoidAndroid ZIP with TWRP (2.3.1.0) recovery
4. Installed gapps (gapps-jb-20121011-signed) with TWRP (2.3.1.0) recovery
5. Wiped cache and dalvik cache.
6. Reboot into system, everything went clean.
Problem:
Everything almost is working great, there is just two problems.
WIFI and Camera is not working.
The Camera app says there is not connection to the camera.
The WIFI just won't turn on no matter what.
I've already searched around with google and found nothing.
So how can I solve this problem?
i've had the same issue with custom kernels on PA (and various other combinations of roms and kernels) full wipe, reinstall PA and gapps without flashing the new kernel should fix the wifi. possibly will fix camera issue as well. i've never tried the camera when the wifi wasn't working after a new kernel. i like the tablet mode and other options of PA more than i care about OC the device so i just stick with the stock kernel and run PA
HidaKureku said:
i've had the same issue with custom kernels on PA (and various other combinations of roms and kernels) full wipe, reinstall PA and gapps without flashing the new kernel should fix the wifi. possibly will fix camera issue as well. i've never tried the camera when the wifi wasn't working after a new kernel. i like the tablet mode and other options of PA more than i care about OC the device so i just stick with the stock kernel and run PA
Click to expand...
Click to collapse
You helped me tremendously. I was able to identify the Kernal as the wifi inhibitor. ElementalX does NOT work with PA 3.99 as of 01/10/2013.
I'm just wondering if my procedure for updating my ROM is correct, as I've only owned a smartphone for about a month, and have only flashed once.
Basically before I was running AOKP build 2 and Franco kernel r79 (or thereabouts) on my Nexus 4. I wanted to upgrade to AOKP build 3, so I backed stuff up, booted up in recovery, wiped my data, cleared the cache, then cleared the Dalvik cache before rebooting. Then it took me back to the initial setup screen, but I got confused when AOKP and Franco Kernel was still installed. I figured I should just open up the browser, download build 3 to the device (since everything is wiped), and then I'll flash that on top of build 2.
Am I supposed to flash back the stock ROM and kernel, or does it not matter since I will be running the same custom ROM?
Likewise, if I wanted to change my custom ROM (like install PA3 or something), then I would definitely need to flash back the stock rom and kernel before proceeding, am I right?
Smeghead_ said:
I'm just wondering if my procedure for updating my ROM is correct, as I've only owned a smartphone for about a month, and have only flashed once.
Basically before I was running AOKP build 2 and Franco kernel r79 (or thereabouts) on my Nexus 4. I wanted to upgrade to AOKP build 3, so I backed stuff up, booted up in recovery, wiped my data, cleared the cache, then cleared the Dalvik cache before rebooting. Then it took me back to the initial setup screen, but I got confused when AOKP and Franco Kernel was still installed. I figured I should just open up the browser, download build 3 to the device (since everything is wiped), and then I'll flash that on top of build 2.
Am I supposed to flash back the stock ROM and kernel, or does it not matter since I will be running the same custom ROM?
Likewise, if I wanted to change my custom ROM (like install PA3 or something), then I would definitely need to flash back the stock rom and kernel before proceeding, am I right?
Click to expand...
Click to collapse
Well since I really only have experience with a tablet and older cell phone I can only speak of my experiences with those. My tablet runs 4.2.2 and the phone 2.2. With both devices I have never had to flash them back to stock to flash an update. Usually a data and cache wipe was sufficient although I will wipe the whole system when flashing a huge update on the tablet.....like from GB to JB.
What helpful people told me when I asked the same question was...
When going to a very different (including the same ROM going to a new android version, ie 4.1 => 4.2) ROM (as in, not just doing a small update on the current one) :
Wipe both caches, wipe /system, wipe /data, and wipe internal sd card and factory reset.
Then flash what you want - ROM => Kernel (if desired) => GAPPs
Wipe caches again.
Done!
I don't know about your particular phone and those ROMs. Is AOKP 2 to 3 a big change ? If so, simply writing 3 over 2 could cause some major problems. I totally messed up and did something like that once and while it wasn't a huge deal I had to start over and do it again because it wasn't usable.
In regards to your description of what you did, you didn't wipe /system, so you didn't wipe your system and so it was still installed like you saw. You'll need to "start over" and wipe everything again. Since the N 4 doesn't have an external SD, I'm guessing you guys wipe /system and like, push the ROM to be flashed to the internal storage ? Maybe ? I have no idea - I've always had an external SD, but since it's a Nexus device I'm sure the procedure is well-covered !
My Kindle Fire tablet also does not actually have an SD card either.....the 8GB memory has been partitioned and originally I would have 5GB available out of 8 which would act as the SD card and 1.09GB for internal or "phone" memory. I have mine even more scrapped down as this one has the ability to either boot into CM7(GB) or the newest CM10.1(JB).
Say for example I went from Android 4.1.2 to 4.2.2.....that's a pretty big update......I would do a full wipe meaning doing it in this order: factory reset, wipe cache, wipe dalvik, and wipe system.
If I wanted to flash a little update of my current 4.2.2 where only some slight tweaks were applied I would just wipe cache and dalvik only. There are times when this simple flash wipe technique WON'T work and you'll probably realize it real quick. There could be any one of a million bugs that could occur and usually they are pretty noticeable. If that happens (sometimes it will, sometimes it won't) the worst case scenario is just going ahead and doing the full wipe.
I'm not knowledgeable on AOKP ROMs so I don't want to venture there. Boot loops are a whole different story and you might want to educate yourself as much as possible because they can happen. I had a couple occurances with a boot loop not too long ago as I was messing with a system font editor and it caused a boot loop. I didn't panic.....I already researched how to handle them so getting it back online was quite easy.
Hope my rambling has helped even a little bit.....
As long as you are just updating the same Rom, you can usually just flash it over (unless the Rom-maker says different).
If there are some fundamental changes in the Rom update, or you are switching to another Rom, then you should wipe it all.
To make it all a bit easier, you can use the Megawipe script:
http://forum.xda-developers.com/showthread.php?t=1832326
Along with the Aroma installer, it's just a few clicks to clean it all up, and ready for a fresh install
I rooted phone per instructions and installed CWM recovery. Everything seemed to go fine. After trying to install the debloated ROM, it gets to the SAMSUNG screen and then stalls. I'm concerned my screw-up was, after rooting, I installed an old SD card and booted into recovery. I selected format SDCard (not format external SDCard). What is on the "internal" SDCard? Any ideas on what to try? Thanks
Edit: I just installed the CM Rom and it installed fine. I would like to have wifi calling, so if anyone has any ideas why the other rom wouldn't work, please let me know.
afaik, wifi calling only works on stock rom
Did you wipe data and cache on the stock rom? What version of the stock rom did you have before rooting?
what nightly did you install. I can't get anything after the 20th of october to work stuck at the samsung screen and loops. cleared cache and dalvic and I'm coming from the 14th of october. i have flashed one nightly a week since the beginning.