Develop Bugs

[Q] gapps REMAINS no matter what i do (cyanogen 6)

First of, to not make everyone dismiss this question...
This is NOT another problem involving missing gapps.
The problem is, no matter what i do (factory reset/clear cache/clear dalvik + remove ANY TRACE of the google apps from the sdcard, and then reboots before installing a basic version of cmod6), i still cant get rid of those damn google apps.
Seems right not that they are installing on their own from absolutely nowhere(!)?
Doesn't matter what i do, have tried to look at every possible scenario from where the cmod flash-process finds, installs, and puts a copy in system/apps-folder without any success at all.
Posted this issue a few days ago, got no answer and then i marked it as solved, but it weren't. Just one single time did i manage to get the flashing to leave a clean copy, but haven't been able to reproduce that since then.
It is car home, gmail, latitude, maps, navigation, places and voice that is stuck in there. Does anyone have any idea of what to do?
Have, except the above, tried to clean out the sdcard completely, plus download+md5check the latest rom...didn't work. Also tried with verification and script assets ON when flashing directly from clockwork, and have tried to flash from rommanager aswell. same results.
Gonna buy a new sdcard tomorrow since im using the stock one which isn't that great (so it needs to be changed sometime anyway), because all i can think of now is if the card itself is bad and clockwork cant read from it properly. Longshot, but im just that badly out of ideas.
Sorry about this wall of text, but that pretty much explains every aspect i tried with no success of removing them. Desperately seeking for help about this now.

You might be able to wipe the system partition completely via fastboot although I don't know if this is a smart thing to do. Than you would be able to do a clean install without Gapps.
You can also try to flash a different rom boot up and then flash cyanogen mod again or you can manually delete the apps from the system partition either with root explorer or with adb while in recovery.
And are you absolutely sure that there are no Gapps in the rom file?

The install script of all CyanogenMods have a backup function for the gapps lol
So also if u wipe all and reflash the rom, the installer backup the gapps, then format system, then install rom and restore gapps..
If u want remove all gapps, just format the /system partition from the clockworkmod recovery (the option its under mounts and storage)..After that, install the rom zip

TheGhost1233 said:
You might be able to wipe the system partition completely via fastboot although I don't know if this is a smart thing to do.
Click to expand...
Click to collapse
'fastboot erase system' is completely safe to do, and a very good idea
andQlimax said:
If u want remove all gapps, just format the /system partition from the clockworkmod recovery (the option its under mounts and storage)..After that, install the rom zip
Click to expand...
Click to collapse
If you want to do this from Amon's recovery (no clear system option), flash the attached update (unsigned).

andQlimax said:
If u want remove all gapps, just format the /system partition from the clockworkmod recovery (the option its under mounts and storage)..After that, install the rom zip
Click to expand...
Click to collapse
Sorry for being such a slow replyer lol, have completed the personalized rom-package and are about to flash it right about now (...or when i got an answer).
First of, before doing it...that answer were really awesome, just curious, there is no way that will brick the base filesystem in any way? In other words, formating /system trough cwork is "completely safe"?
I ofc know things always can go wrong, like the phone bursts into fire or my apartment gets blown away by nuclear war...but it wont mess with anything by default making a restoration towards working state a pain in the lower back?
EDIT: Thought this could make me sound like a damn nervous user, which im not...but the hate i would have at not being able to use my phone during workhours exceeds all measurements known to man. it would get really really boring, not kidding.

Stuck on "starting apps" after OTA. I was on a rooted stock rom.

Hey guys I need help. Anyone have a link to the latest rooted stock rom? How is cynogenmod these days? Is it worth making the switch? Whats the most popular rom these days?

jkj said:
Hey guys I need help. Anyone have a link to the latest rooted stock rom? How is cynogenmod these days? Is it worth making the switch? Whats the most popular rom these days?
Click to expand...
Click to collapse
Freeza always has the latest stock rooted ROM over in this thread. It's always updated shortly after each OTA is dropped (currently at MB1).
You can see my setup in my sig. I like it a lot!
CM10.1 nightlies are good, and a lot of the AOSP (4.2.2) ROMs are really stable. There are a lot of reasons to stay with TW ROMs and a lot of reasons to move over to AOSP, AOKP, and other ROMs (MIUI, etc). My recommendation would be to update your recovery to the latest (see my sig for the link to the latest TWRP, search for the latest CWM) and just flash away. As long as you stick to Sprint ROMs and nandroid up whenever you can, it's getting difficult to brick your phone.

jkj said:
I downloaded the stock odexed zip and odin but it doesnt seem like the right file type for odin to flash?
Click to expand...
Click to collapse
First off, you're going to need to have a custom recovery, if you don't already have one (most people do after they originally flash their phone). There are many guides to do this, just follow one of qbking77's great tutorials. I'd recommend using TWRP, but the latest CWM works well also.
Now that you have a custom recovery, you can try the following and it might get you out of the bootloop:
In the custom recovery, clear (wipe) both cache and dalvik cache. Then reboot the phone (reboot menu -> system).
If the above doesn't work to get you through the bootloop, try the instructions below:
Now that you have a custom recovery, you need to get the files onto your phone. Since you cannot turn your phone on to download it or connect through USB, you'll have to do it through recovery. Since I use TWRP, I'll walk you through the menu's for that (CWM should be similar).
Connect USB cable to computer -> Mount Menu -> Mount USB Storage.
Now your computer should see a "removable disk" with the contents of your SD Card on it. Now you can copy the ROM you downloaded over to the SD Card.
Now that the file is actually on the phone, you can flash the ROM zip in recovery. Whenever you do this, it's best to do what is called a "full wipe" in the recovery. You'll lose all your apps, settings, etc but it's much better than having a paperweight. In TWRP, what I always do is the following:
1) Nandroid backup: I normally name it something along the lines of "2013-03-14 - ROM NAME - ROM VERSION." This way, when I look through my backups, I can easily see what I was running (what I'm restoring when I want to restore).
2) Wipe Menu - Factory Reset. This will wipe all custom data off of the phone. For me, this is a must before flashing any new ROM. Other people will "dirty flash" Roms on top of each other. For me, that's a recipe for disaster, as any leftover settings/code will inevitably interfere with the new ROM and will mess things up.
3) Wipe Menu - Dalvik Cache and Cache: If I recall correctly, the Factory Reset does both of these, but it doesn't hurt to do it again.
4) Install: This is where you find the ROM zip file you downloaded and install it. Should take less than a minute, but some larger ROMs could take a little longer (not 10 minutes, though).
3) Wipe Menu - Dalvik Cache and Cache: Again, not technically required, but I tend to wipe the cache and dalvik cache very often.
3) Reboot Menu - System: Pretty self-explanatory, but it'll reboot your phone and you can set it up all over again.
In the future, it's best to have Titanium Backup to back up apps and data (For me it's worth the cost to upgrade to Pro). I have mine set up to backup all data every night at 3 am, with a maximum of 5 backups per app. This gives me almost a week of backups that I can restore for every app I have installed. The only thing to keep in mind with TiB is that you can backup/restore system apps that won't work with a new ROM. For example, if I backed up the Samsung Connection Optimizer on the stock rooted ROM and tried to restore it to LiquidSmooth (a 4.2.2 AOSP ROM), it wouldn't work. In fact, it could mess things up on my new ROM. So you might want to pick and choose system apps (RED items) carefully when you're restoring. Next time you want to try out a new ROM (or if you need to restore again because of a bootloop), you can just restore your apps/settings through TiB and not go through 2 hours of setting up all your settings again (for me I like that I can restore all the wifi access spots settings... saves me from explaining why I need my friend's WEP key for the fifth time this month).
Anyways, this post has turned into a novel. Please let me know if you have any more questions (and CNexus or anyone else can correct anything that's wrong)

I got it going by wiping cache and data. I should've tried with just cache wiped. Its annoying to have to redo everything but better than a brick.

Now for some reason my wifi wont turn on. Reflashed again now I'm good to go.

[Q] Installing a rom

Ok, completely new with this. I did a basic root, got superuser cwm and busybox from my understanding. I used Samsung Galaxy Toolkit v7.0.0
I would like to install the MoAR onto my phone. But I'm not 100% sure how to do so. I have Odin v3.4, I was going to do it as a PDA file. But I don't see anything that says it's a .tar file.
If someone could point me in the right direction, or a video would be great.

jrodcamaro said:
Ok, completely new with this. I did a basic root, got superuser cwm and busybox from my understanding. I used Samsung Galaxy Toolkit v7.0.0
I would like to install the MoAR onto my phone. But I'm not 100% sure how to do so. I have Odin v3.4, I was going to do it as a PDA file. But I don't see anything that says it's a .tar file.
If someone could point me in the right direction, or a video would be great.
Click to expand...
Click to collapse
I'm going to assume you're able to boot into a custom recovery (CWM). I persoanlly use TWRP, but either will work well for this. If you can't go through the root process again, based on qbking77's thread. Check out the videos and learn how to use Odin to gain root and a custom recovery. (always good to take a refresher course).
Here are directions on how to flash a Rom below. The instructions will be for TWRP, but CWM has similar options/settings
Make sure the zip of the Rom you downloaded is on your externalSD Card or the root directory of your internal memory.
Turn your phone completely off (hold down power for 3-5 seconds)
Boot your phone into recovery. Hold Up, Menu, and Power for a few seconds (until SAMSUNG appears on your screen and the phone vibrates)
Make a Nandroid backup. I can't emphasize this enough. In flashing, it's a certainty that at least one time, something will mess up. When that happens, you want to be able to restore a backup. In TWRP, just go into Backup Menu and choose where you want it (internal vs. External storage). It takes my phone a few (5-10) minutes to completely backup my data.
In TWRP, click the wipe button, then system. This will completely wipe the Rom from your phone. Doing this will allow you to get a "clean" install, without any settings or leftover files from your old Rom getting in the way. Instead, you could only wipe data (factory reset), which is good enough for most Roms. I'd still recommend a system wipe, though, as you never know exactly what might be left over from your old Rom (especially when going from 4.1.X to 4.2.X or vice-versa).
Also while in the Wipe menu, wipe Cache and Dalvik Cache (can't hurt).
Go back to the TWRP main menu.
Click Install, then find your Rom zip file (may have to switch from internal to external storage).
Let TWRP do it's thing.
MOAR rom already installed. If, in the future, you flash an AOSP Rom, you should now flash the correct gapps package from goo.im. Make sure you're flashing the correct one, as if you don't, your google apps will force close upon use.
Reboot into system and give it time to boot (first boot sometimes takes a couple of minutes).
Set up your phone the way you like.
These should be the directions to follow whenever you flash a new Rom. Some Roms (such as the MOAR Rom) have the Aroma installer, so you'll have more options once you choose to flash the Rom zip, but those are typically easy to follow (and vary from Rom to Rom, so I won't be able to give you a good guide on that).
Hope this helps!

I could tell you but from what you're asking, honestly I think it's better not to and to force you to read a lot more. I am pretty new to this stuff too, joined this site in like march but I did about 3 weeks worth of reading before I rooted and flashed my first ROM. I'm not trying to be mean here but the question you're asking will be the least of your worries once you read a little more. I recommend you read this Q&A thread, it's also at the top of the Q&A forum.
Edit: It seems good guy topherk here gave you the info, I stand by what I said though, from a fellow newbie to another

jrodcamaro said:
Ok, completely new with this. I did a basic root, got superuser cwm and busybox from my understanding. I used Samsung Galaxy Toolkit v7.0.0
I would like to install the MoAR onto my phone. But I'm not 100% sure how to do so. I have Odin v3.4, I was going to do it as a PDA file. But I don't see anything that says it's a .tar file.
If someone could point me in the right direction, or a video would be great.
Click to expand...
Click to collapse
Download the rom on your pc and transfer it to your sd card or internal sd card on your phone. Don't put the rom zip file in any folders as it's easier to find, commonly referred to as the root of your sd card. Power off your phone if your still on stock, after it shuts down hold the volume up button+the home button and then hold power button, this will take you to your custom recovery. First thing to do once in your recovery is make backup of your current rom, make sure you have at least 3GB free space on either your sd or internal sd, some backups can be even bigger, if you don't have space it should tell you. After your backup is done, wipe cache, dalvik cache, factory reset and then flash your rom, after it's done and you see it was successful, fix permissions and reboot...you should be good to go at that point. If all is running well you can boot back into cwm, select restore and only restore /data, to get all your apps and their data back, fix permissions again and reboot. You can use titanium backup or my backup root /pro to restore apps and data but personally I don't prefer those methods. If you have any issues, restore your backup and try again.
I see I was slow again as topherk said everything and then some lol...still posting this just in case it helps at all.
Edit; just to throw it out there I'll tell you how I do things, once your more experienced this could make flashing roms, kernels, tweaks ect, easier. I always make a backup first before I switch roms. Then I simply wipe cache, dalvik cache, flash new rom and fix permissions....reboot and enjoy, this is known as a dirty flash, some roms don't dirty flash well, some work great.
Also I always 100% of the time download roms, kernels ect straight from my phone, never had a bad download that I'm aware of, I don't check md5 sums, I just verify the size of the dl matches what I dl'd. My dl's go to my download folder on my ext sd card so when I go into recovery, I know to look in my download folder on the ext sd card.
Other things to note about dirty flashing if you choose to do it, figure out your rom issues quietly and it can't hurt to try dirty flashing if you always remember rule#1.....make a backup first. If you get stuck in a boot loop, just pull the battery, put it back in and 3 button boot to recovery and restore your backup.

Yeah, the main reason I prefer a clean flash is that when people dirty flash, any and all problems will not be supported by the developer. And since the person is asking how to flash a Rom, I doubt that they'd know what to do with a FC. I'd prefer if they would do a clean flash until they get used to it. I do all my app backups in Titanium Backup, and even then I have to be careful not to restore something that might mess up the new Rom.
Anyways, I really liked your advice with the backups: if you're ever stuck in a bootloop, you can just restore your backup. I recently tried out a new Rom that I wasn't too fond of, and in a few minutes was back to my LiquidSmooth. No sweat.
Sent from my SPH-L710 using xda app-developers app

[Guide]Fix your ROM issues that other's are not having before posting for support.

Ok I wrote this for the OP of my ROM because the issues some people were PMing me about were just plain out dumb, This phone has been out quite a long time and still almost every thread I goto, you got people flashing in way's I didn't even know were possible and posting weird issues that were not being reproduced by the community. so I'm just gonna post this guide for all the developers sake and in hopes the people that actually need this information, receive it before posting and clogging up development threads
If you're having issues on rom's that no one else is reporting, or the DEV has not reproduced on his phone, read the following.
1) Full wipe
2) Do not restore System data or data from CWM
3) Do not dirty flash from other ROM's
4) When was the last time you did a odin to stock? this is important in my opinion and I'm not saying you need to do one but I just want to explain that custom zip's that I make and other dev's make in the shape of "roms" only affect
a few partitions on your device, other's do not get touched and can get messy/corrupt over the months (This explains why the GPS icon disappears in some peoples cases during rom switch) and this is why I get posts in this thread about people wondering why their baseband hasn't been updated after flashing my rom when my post states "MF1"
With this being said my personal rule of thumb is to odin to stock latest and then boot into stock recovery and factory reset, wipe cache/dalvik (BACKUP YOUR SD CARD TO YOUR COMPUTER), this gives your phone fresh partitions everywhere, a fresh system to root and the latest bootloader (which you need for any AOSP 4.2 rom). This is also a good time to unlock your phone if you have not already, then reroot and install custom recovery, update the recovery if need be and flash again on a brand new system. here are my steps
1) backup all user apps and data with titanium backup, DO NOT BACKUP SYSTEM APP'S
2) backup internal storage onto PC
3) Odin to stock latest
4) wait for phone to boot then reboot into stock recovery and full wipe and clear all cache
5) reboot and root the phone and custom recovery
6) flash away and put what you need on your internal storage back onto your phone via usb, see my 2nd set of instructions below
this fixes more issues then you will realize. some of the way people flash rom's on XDA and complain to me with problems is rather funny considering I have the install instructions in the OP, not to mention many of you rooted your phone when you first got it in the ICS 4.0.4 day's and haven't done an odin to stock jellybean to update all your partitions including your bootloader, now I will go over my every day flashing step's.
1)backup all USER APPS/DATA with titanium backup, DO NOT BACKUP SYSTEM APP'S (skip this if you did a odin flash to stock)
2)reboot recovery
3)nandroid (skip this if you did a odin flash to stock)
4)factory reset, wipe system, wipe both cache/dalvik
5)install rom
6)boot system
7)*(OPTIONAL) reboot to install a kernel now if needed, always wipe cache/dalvik and fix permissions after installing a kernel
8)setup phone and download titanium backup from the market
9)restore all user apps and data (you will have to put the titanium backup folder that is backed up on your computer back onto your internal storage via usb first)
Every 6 months, backup internal storage to PC and I odin to stock, much like formatting a computer
6 months is actually a long time considering how much I flash, but this device can take a beating let me tell you =P
I DO THIS WITH EVERY ROM I INSTALL, AOSP or TW

Great explanation and should really help out with those with issues. Thanks!
Sent from my SAMSUNG-SGH-T999 using Tapatalk 2

TheKucho said:
Great explanation and should really help out with those with issues. Thanks!
Sent from my SAMSUNG-SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
It is great advice, but here's the problem.
Every new thread pushes this farther down the list. And if no one comments, eventually it's gonna be on the back door of this thread.
The OP may want to consider getting this stickied, or maybe copying it to each one of his rom threads.
Like I said, it's really great info, but will do no one any good on page 4 or farther back.
jus' my one cent worth (government took the other penny for taxes)
Sent from my SGH-T999 using XDA Premium HD app

Blank App?

I have a blank App in my app drawer since I flashed my custom ROM and now they're 3 of them. When I tap on the app info it says I need a broader app to view it. I included a screenshot. Anyone know what these are?
Also, my phone keeps randomly rebooting.

@newbrooster89
Looks like apps left from maybe a backup of whatever launcher you were using on your previous setup. Shows the partial icons but not the whole app because they are not installed now. That's what it appears to be. I use nova prime and, I can hold down (long press) an icon and it gives me options and one is playstore and you can select that and it takes you to play store to the app. See if you can long press and maybe select "search" or something that will take you to the app. If not just swipe em off your screen. Its nothing to be worried about. Just something from a past launcher backup/restore.
Edit/added:
Explain how you installed? What rom, what gapps package... What did you wipe in twrp recovery?
I always wipe data and system and cache unless whoever made the rom states not to in their op. (original post) Ex: Lineage 17 The dev says to only wipe data in twrp so that's what I do... otherwise I wipe data, system, cache flash rom, flash twrp installer zip reboot system. Then I boot back into twrp and install gapps and magisk zip for root and reboot system. That's my usual method for installing a rom.
I recommend a factory reset either through your phones settings or fastboot or twrp. See if that stops your reboots ..

NewbRooter89 said:
I have a blank App in my app drawer since I flashed my custom ROM and now they're 3 of them. When I tap on the app info it says I need a broader app to view it. I included a screenshot. Anyone know what these are?
Also, my phone keeps randomly rebooting.
Click to expand...
Click to collapse
if you flashed anything other than lineage you deserve what you are getting

flash713 said:
@newbrooster89
Looks like apps left from maybe a backup of whatever launcher you were using on your previous setup. Shows the partial icons but not the whole app because they are not installed now. That's what it appears to be. I use nova prime and, I can hold down (long press) an icon and it gives me options and one is playstore and you can select that and it takes you to play store to the app. See if you can long press and maybe select "search" or something that will take you to the app. If not just swipe em off your screen. Its nothing to be worried about. Just something from a past launcher backup/restore.
Edit/added:
Explain how you installed? What rom, what gapps package... What did you wipe in twrp recovery?
I always wipe data and system and cache unless whoever made the rom states not to in their op. (original post) Ex: Lineage 17 The dev says to only wipe data in twrp so that's what I do... otherwise I wipe data, system, cache flash rom, flash twrp installer zip reboot system. Then I boot back into twrp and install gapps and magisk zip for root and reboot system. That's my usual method for installing a rom.
I recommend a factory reset either through your phones settings or fastboot or twrp. See if that stops your reboots ..
Click to expand...
Click to collapse
I just ended up deleting everything and flashing a whole new ROM. I was on Lineage 17 but kept having so many bugs that I decided to try a different one. Thanks for the advice though.

sudoxd said:
if you flashed anything other than lineage you deserve what you are getting
Click to expand...
Click to collapse
That's what I was using and I had so many bugs and issues with it.

NewbRooter89 said:
That's what I was using and I had so many bugs and issues with it.
Click to expand...
Click to collapse
Then something was wrong on your end because lineage 17 is very close to being flawless. I've used it several times and always worked great for me.
Flash latest factory image & let it wipe (fastboot -w) at the end don't remove the fastboot -w in the script, if you did. I know many people do that ...
Boot twrp and Wipe data, flash lineage 17 w/gapps
Flash twrp installer (I use 3313) reboot system ...
Boot twrp, flash magisk root zip reboot system.
That's how I've always installed lineage and works great. Sounds like you had something interfering with it. Maybe residue from a past install or something but it was most definitely user error. Reflash factory image and wipe data and install it and it will be close to flawless. If not get logs and post them on lineage thread and someone there can tell you exactly what's going on. 11/30 build is not buggy.

flash713 said:
Then something was wrong on your end because lineage 17 is very close to being flawless. I've used it several times and always worked great for me.
Flash latest factory image & let it wipe (fastboot -w) at the end don't remove the fastboot -w in the script, if you did. I know many people do that ...
Boot twrp and Wipe data, flash lineage 17 w/gapps
Flash twrp installer (I use 3313) reboot system ...
Boot twrp, flash magisk root zip reboot system.
That's how I've always installed lineage and works great. Sounds like you had something interfering with it. Maybe residue from a past install or something but it was most definitely user error. Reflash factory image and wipe data and install it and it will be close to flawless. If not get logs and post them on lineage thread and someone there can tell you exactly what's going on. 11/30 build is not buggy.
Click to expand...
Click to collapse
you dont even need to flash the factory image, will work fine flashing from whatever they have now

sudoxd said:
you dont even need to flash the factory image, will work fine flashing from whatever they have now
Click to expand...
Click to collapse
That's correct you don't have to flash factory image but that's what I would do. There's always more than one way to do something.

flash713 said:
That's correct you don't have to flash factory image but that's what I would do. There's always more than one way to do something.
Click to expand...
Click to collapse
yes but why? just sounds like wasted time to me, our lives are short remember. that time could be spent with friends and family but no here you are flashing factory image before rom

sudoxd said:
yes but why? just sounds like wasted time to me, our lives are short remember. that time could be spent with friends and family but no here you are flashing factory image before rom
Click to expand...
Click to collapse
But I love to flash factory image. Jkjk. ?? The reason I had initially posted that on my comment was because I thought if anything wasn't right on his setup it would square it away or if something was left from another past install on sdcard it would clear it all up. Sure a format data in twrp will do same I just thought of that as an easy thing to say that had a zero % chance of being misunderstood. And what if he was on 9.0? ? That's just how I thought at that moment when I commented that. I know Lineage 17 build for Marlin is damn near flawless. I've been using it off and on since it came out. I see you are the dev who makes that kernel. Saw your link to your work. I remember you from long ago (i used to have another user name but had my account deleted a while back) on some Nexus device everyone and their mom owned. Maybe the 5 or 5x or the Gnex idk but I remember your kernel because it was bad ass.

It probably was something on my end. This is the first phone I've rooted with the A/B slots. I also did it through adb sideload because I was having issues with TWRP. I was also stuck in a bootloop when I installed it. Maybe I'll give it another shot. I did really like having Android 10 and my battery life was much better with lineage.