Develop Bugs

[Q] Gapps not working PLEASE HELP

Phone: Samsung-SGH-I747
Carrier: AT&T
Andriod Version: 4.1.2
CM: 10-20121206-NIGHTLY-d2att
CWM: recovery-clockwork-6.0.1.2-d2att
I am unable to find a compatible Gapps that works with this ROM, anytime I flash Gapps I get the
Unfortunately Android Keyboard (AOSP) Stopped
As well as "Connection Error "Retry" when trying to access Google Play.
I've tried wiping the cache within the AOSP Keyboard settings as well, but this seems to be a Gapps error as the Play store stops working.
I have tried gapps-jb-20121011-signed and gapps-jb-20121130-signed.
This is the method of install I have been doing:
1) Wipe data/factory reset
2) Wipe Cache Partition
3) Advanced -->Wipe Davlik Cache
4) Install 10-20121206-NIGHTLY-d2att
5) Install gapps-jb-20121011-signed
6) Reboot
Am I doing this right? Should I wipe cache/partition/davlik cache before gapps install? Whats going on here?
Is there a proper flashing process to make these work? Or is there is comparable stable ROM that has Gapps included and works (JB ONLY)?
I re-rooted my phone and did a clean install with I747UCDLK3_I747ATTDLK3_ATT then root66_ATT_I747UCDLK3 then ROManger CWM download to get where I'm at.
My whole reason to rooting was for Google Now, I've always liked CM's work but am willing to try something else if there are any other suggestions??
Please help, I feel like I've spent WAY too much time on something that seems so simple.

You're doing this right. I don't know what could be wrong.
As a last measure, try format instead of wipe. Format boot, system, data and cache, and flash CM and gapps 20121011 again.
Good luck!

marinierb said:
You're doing this right. I don't know what could be wrong.
As a last measure, try format instead of wipe. Format boot, system, data and cache, and flash CM and gapps 20121011 again.
Good luck!
Click to expand...
Click to collapse
And that did the trick.
Thanks

[SOLVED] Unable to install custom rom after modem upgrade

Hello,
I have a unique issue. I'm having a problem installing any custom rom on my t999 (tmobile). I have been using a custom rom for over a year. Always used TWRP. Started with Paranoid Android and for the last few months I've been using PAC-Man (nightly) roms. I was having gps lock issues, I decided to upgrade the modem to a leaked UVUEMJC, this fixed the gps lock issue. But after the reboot, I was stuck on bootloader screen. The only way I could get the rom to work was to backup the rom, flash the system and data, and after that, the rom would work until reboot. I did this a few times until it stopped working. My efs was corrupted, IMEI missing, To recover it, I went into download mode, and noticed in red Warranty bit =1. I used odin to flashed a rooted cf 4.3 samsung touchwiz rom (root66_TMO_T999UVUEMJC). All imei/efs issues were fixed. I decided to try installing a custom rom again, PAC-Man rom, it installed just fine, all EFS/IMEI info was intact, but at reboot, I got stuck on the CM bootlogo. This happens everytime. IF I recover a backup, it gets stuck on the boot logo. I'm using TWRP v2.6.3.
Anybody have any suggestions on how to fix this issue?
Thanks!

Install TWRP 2.6.3.1. Then take a Nandroid.
Next wipe /Data. Then flash your Custom Rom. Wipe Dalvik + Cache after the Flash. Reboot and report.

Perseus71 said:
Install TWRP 2.6.3.1. Then take a Nandroid.
Next wipe /Data. Then flash your Custom Rom. Wipe Dalvik + Cache after the Flash. Reboot and report.
Click to expand...
Click to collapse
Thanks for the reply Perseus71. I'll give it a shot!

acedik said:
Thanks for the reply Perseus71. I'll give it a shot!
Click to expand...
Click to collapse
Upgrading to the newest TWRP did the trick! Everything is working fine now. :good:
Thanks for the help!

I'm also having trouble flashing PAC-man.
SGH-T999LUVUBMK4
Factory reset everything, wiped SD card.
Tried latest TWRP and CWM.
Suggestions?
D

Donny Orbit said:
I'm also having trouble flashing PAC-man.
SGH-T999LUVUBMK4
Factory reset everything, wiped SD card.
Tried latest TWRP and CWM.
Suggestions?
D
Click to expand...
Click to collapse
You need to post info about the error
Sent from my SGH-M919 using Tapatalk

It says
E: Error executing updater binary in zip '/external
Error flashing zip '/external_sd/pac_d2tmo-night
I tried flashing the Rom that doc fixed specifically for the T999LTE for the CM10.1.2 also with no avail.
Same problem.
D

wipe Dalvik and Cache before trying the rom again. If

Help...Soft bricked?

Hi all, today my phone was acting very strange so I decided to do a factory wipe.
Afterwards I tried to boot my phone and it just sat on the samsung screen.
I then decided to wipe everything and restore a back-up of a different rom.
The install of the back-up failed.
I tried to install a fresh rom and it failed.
I am getting these errors in twrp.
E: error opening ' /data/data/com.sec.spen.flashan
E: error: I/O error
E: error opening ' /data/data/com.sec.spen.flashan
E: error: I/O error
E: error opening ' /data/data/com. samsung. android
E: error: not a directory
E: error opening ' /data/data/com. samsung. android
E: error: I/O error
I am not sure what to do at this point.
I was on Smoothest Note 2/3 Rom and running twrp.
Any help is GREATLY APPRECIATED.

You need to read the last few pages of the thread.
1. Possibly billiards factory reset
2.philz recovery
3. Lots of wiping..
Read the thread.. Last few pages at least. Post if you are still hung up.

Ron36 said:
Hi all, today my phone was acting very strange so I decided to do a factory wipe.
Afterwards I tried to boot my phone and it just sat on the samsung screen.
I then decided to wipe everything and restore a back-up of a different rom.
The install of the back-up failed.
I tried to install a fresh rom and it failed.
I am getting these errors in twrp.
E: error opening ' /data/data/com.sec.spen.flashan
E: error: I/O error
E: error opening ' /data/data/com.sec.spen.flashan
E: error: I/O error
E: error opening ' /data/data/com. samsung. android
E: error: not a directory
E: error opening ' /data/data/com. samsung. android
E: error: I/O error
I am not sure what to do at this point.
I was on Smoothest Note 2/3 Rom and running twrp.
Any help is GREATLY APPRECIATED.
Click to expand...
Click to collapse
Twrp does not backup or restore tw 4.3 or any 4.4 properly. Best bet is install philz 6.07.9 and flash fresh.
Sent from my SPH-L900 using XDA Premium 4 mobile app

jlmancuso said:
Twrp does not backup or restore tw 4.3 or any 4.4 properly. Best bet is install philz 6.07.9 and flash fresh.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks to all who replied.

Ron36 said:
Thanks bud.
I am looking for the philz download for my device but I dont see it here.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
You think you could assist a bit more?
EDIT.. is it this file? philz_touch_6.07.9-l900.zip
Thanks to all who replied.
Click to expand...
Click to collapse
That link looks right "L900" except it looks like this "l900"
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/l900

ColeTrain! said:
That link looks right "L900" except it looks like this "l900"
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/l900
Click to expand...
Click to collapse
I installed philz and installed a ver of jellybomb and Im again stuck on the samsung screen.
what should I do?

Ron36 said:
I installed philz and installed a ver of jellybomb and Im again stuck on the samsung screen.
what should I do?
Click to expand...
Click to collapse
Ron.
The thing that is probably going on is that bits of data are left over. We need to clean.
Process A is this link. And we should still do process B but, this is the deep clean
http://forum.xda-developers.com/showthread.php?t=2086769
Process B.
-Install philz. Some people have luck, i didn't. I don't think it works with 4.3
-"format " select data, cashe, sdcard. Not sdcard1 (cuz that is your external) and etc
Reboot recovery
Wipe cashe, wipe dalvidec, wipe for new rom, wipe factory reset.
Don't restore anything old that isn't 4.3... Or flash new 4.3
If you want to try process B first, it may be all you need. But if it doesn't work, do all of it.
Jlmancuso is your goto if that doesn't work. The samsung screen does take a few minutes, be patient.
I hope this helps.

ColeTrain! said:
Ron.
The thing that is probably going on is that bits of data are left over. We need to clean.
Process A is this link. And we should still do process B but, this is the deep clean
http://forum.xda-developers.com/showthread.php?t=2086769
Process B.
-Install philz. Some people have luck, i didn't. I don't think it works with 4.3
-"format " select data, cashe, sdcard. Not sdcard1 (cuz that is your external) and etc
Reboot recovery
Wipe cashe, wipe dalvidec, wipe for new rom, wipe factory reset.
Don't restore anything old that isn't 4.3... Or flash new 4.3
If you want to try process B first, it may be all you need. But if it doesn't work, do all of it.
Jlmancuso is your goto if that doesn't work. The samsung screen does take a few minutes, be patient.
I hope this helps.
Click to expand...
Click to collapse
thanks bud!!
I was finally able to install the latest smooth rom w/o aroma but I am getting this error when the phone boots up.
UIDS on the system are inconsistent, you need to wipe your data partition or your device will be unstable. with a tab that say im feeling lucky. I selected that and all seems fine but i cannot turn on my wifi.
sorry to be a pain, but what should I do?
EDIT........
I found the wifi fix and it is now working, but I am still getting the error on start up about the data partition.
what should I do?

Ron36 said:
thanks bud!!
I was finally able to install the latest smooth rom w/o aroma but I am getting this error when the phone boots up.
UIDS on the system are inconsistent, you need to wipe your data partition or your device will be unstable. with a tab that say im feeling lucky. I selected that and all seems fine but i cannot turn on my wifi.
sorry to be a pain, but what should I do?
EDIT........
I found the wifi fix and it is now working, but I am still getting the error on start up about the data partition.
what should I do?
Click to expand...
Click to collapse
Follow the steps he provided. Proper wiping is super important.
Sent from my SPH-L900 using XDA Premium 4 mobile app

jlmancuso said:
Follow the steps he provided. Proper wiping is super important.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent you a pm.
Thanks some more!

Ron36 said:
Sent you a pm.
Thanks some more!
Click to expand...
Click to collapse
Here is how to do a clean wipe, just remember you r doing like format the comp. hard drive and install new OS. I see u have Philz now. Boot into Philz then go to Mounts and Storage and pick format /data and /data/media (/sdcard). Once done pick: format /system. done pick format /preload. Then go back and chose Wipe Cache Partition. Once it finish, pick Wipe Data/Factory Reset. First, pick Wipe Data/Factory Reset. When finish, pick Clean to Install a New ROM. Then Reboot back into RECOVERY and now you can install any rom of your choice in the external sdcard (showned as sdcard1 in Philz). If it's still not working, use Philz to install the back to unrooted stock MC2 by Billard412 and follow my steps in the other thread. The reason I said this because I have to note 2. Once is fine with whatever wipe. The other had to go back to MC2 and upgrade to MK4 then rooted through CF Auto Root and install TWRP then Philz then wipe everything in the above steps then everything is fine with a hitch.

na_tra said:
Here is how to do a clean wipe, just remember you r doing like format the comp. hard drive and install new OS. I see u have Philz now. Boot into Philz then go to Mounts and Storage and pick format /data and /data/media (/sdcard). Once done pick: format /system. done pick format /preload. Then go back and chose Wipe Cache Partition. Once it finish, pick Wipe Data/Factory Reset. First, pick Wipe Data/Factory Reset. When finish, pick Clean to Install a New ROM. Then you can install any rom of your choice in the external sdcard (showned as sdcard1 in Philz). If it's still not working, use Philz to install the back to unrooted stock MC2 by Billard412 and follow my steps in the other thread. The reason I said this because I have to note 2. Once is fine with whatever wipe. The other had to go back to MC2 and upgrade to MK4 then rooted through CF Auto Root and install TWRP then Philz then wipe everything in the above steps then everything is fine with a hitch.
Click to expand...
Click to collapse
Thanks for the help. I now have my note2 back up fully and I am back on a jellybomb rom. not sure if i will go back to a 4.3 rom as I never had this many issues on ANY phone on any rom on any OS.
Keep up the good work helping the slow members like myself.

Ron36 said:
Thanks for the help. I now have my note2 back up fully and I am back on a jellybomb rom. not sure if i will go back to a 4.3 rom as I never had this many issues on ANY phone on any rom on any OS.
Keep up the good work helping the slow members like myself.
Click to expand...
Click to collapse
Remember not to use TWRP to back up 4.3 and install it. It wont work. I always have the back to unrooted stock MC2 in the external sdcard just in case flashing the new rom wont work. I am glad you got your note 2 back. You should try out the Smoothest Note 2/3 1.3 tester. It is very stable and has alot of Note 3 features.

na_tra said:
Remember not to use TWRP to back up 4.3 and install it. It wont work. I always have the back to unrooted stock MC2 in the external sdcard just in case flashing the new rom wont work. I am glad you got your note 2 back. You should try out the Smoothest Note 2/3 1.3 tester. It is very stable and has alot of Note 3 features.
Click to expand...
Click to collapse
I actually installed smoothest rom with TWRP with no issues until I started to use TWRP with Smoothest.
Ultimately it was my fault for not switching to Philz. I just had to many backups for TWRP and as I said I was able to install Smoothest from it so I thought all was good.
Is Philz compatible with the older roms or do I need to keep switching recoveries?

Ron36 said:
I actually installed smoothest rom with TWRP with no issues until I started to use TWRP with Smoothest.
Ultimately it was my fault for not switching to Philz. I just had to many backups for TWRP and as I said I was able to install Smoothest from it so I thought all was good.
Is Philz compatible with the older roms or do I need to keep switching recoveries?
Click to expand...
Click to collapse
you r fine to install any rom with TWRP. but if you use it for back up and then restore the MK4, it just wont work. I am not sure about Philz and older rom. So cant tell you.

na_tra said:
you r fine to install any rom with TWRP. but if you use it for back up and then restore the MK4, it just wont work. I am not sure about Philz and older rom. So cant tell you.
Click to expand...
Click to collapse
Philz is good for everything. It will work for every rom and it will even restore your twrp backups. If you used 6.07.9 the option for twrp is under backup/restore then misc options.
Sent from my SPH-L900 using XDA Premium 4 mobile app

Ron36 said:
thanks bud!!
I was finally able to install the latest smooth rom w/o aroma but I am getting this error when the phone boots up.
UIDS on the system are inconsistent, you need to wipe your data partition or your device will be unstable. with a tab that say im feeling lucky. I selected that and all seems fine but i cannot turn on my wifi.
sorry to be a pain, but what should I do?
EDIT........
I found the wifi fix and it is now working, but I am still getting the error on start up about the data partition.
what should I do?
Click to expand...
Click to collapse
You inspired me to start this thread. Still a work in progress.
http://forum.xda-developers.com/showthread.php?t=2648855

ColeTrain! said:
You inspired me to start this thread. Still a work in progress.
http://forum.xda-developers.com/showthread.php?t=2648855
Click to expand...
Click to collapse
Glad I could help. LOL

Ron36 said:
Glad I could help. LOL
Click to expand...
Click to collapse
Its finished. I have solicited some people more knowledgeable to proofread, are you up and running well?

ColeTrain! said:
Its finished. I have solicited some people more knowledgeable to proofread, are you up and running well?
Click to expand...
Click to collapse
I was last night, but now not so much. My phone is trying to hands free activate unsuccessfully and my data connection does not work. My GPS may not be working also.
I have tried a factory and data wipe and reinstalled the rom. I also called sprint for help but nothing they suggested worked.
I'm at a loss as what to do next. What do you suggest?

[Q] CM 11+ not flashing?

Hello! I'm new to the forums here. I have a T-Mobile Samsung Galaxy S 3 LTE (T999L) that i have rooted, (root 66), flashed custom recovery, ClockworkMod recovery (v6.0.4.5) and have installed CM 10.0. However when i downloaded CM 11, it wouldn't flash, I looked it up and found I needed to change the files by deleting all the Assert lines in the updater script, so I did, and compressed it, loaded it to my SD card and tried to flash it. (System wipe,wiped cache, dalvik ect...)
CWM gave me a Installation aborted. So I looked at the CWM log and it said: "using /data/media for /sdcard/0/clockworkmod/.last_install_path.
"Can't partition non mmcblk device: /devices/platform/msm_sdcc.3/mmc_host/mmc1 "
I don't know what to do from here, so if anyone can point me at the right direction that would be great. I'm like 20% sure that it's the kernel, but like I said, I'm not that sure. I have rooted 3 devices with no problems but I have never really run into this before.

You should wipe cache partition, wipe dalvik cache, and reset data in Recovery. And then try flashing the new CM 11 ROM. Make sure it's compatible with your Phone.
If this fails then I recommend using Odin3 to flash to stock touchwiz ROM for your Samsung (getting the .md5 file or .tar ROM). Followed by wiping cache partition, wiping dalvik cache, and resetting the data in Recovery. Then flashing CM 11 in recovery by installing the CM 11 zip specifically for your phone.
Let me know the follow up.

Flashed back to stock (root 66), via Odin, flashed the same recovery, wiped system, cache, and dalkic in that order... And still got the "using /data/media for /sdcard/0/clockworkmod/.last_install_path.
"Can't partition non mmcblk device: /devices/platform/msm_sdcc.3/mmc_host/mmc1 "
Im using CM from d2tmo page. I know im using the right CM files...

Gravitylog said:
Flashed back to stock (root 66), via Odin, flashed the same recovery, wiped system, cache, and dalkic in that order... And still got the "using /data/media for /sdcard/0/clockworkmod/.last_install_path.
"Can't partition non mmcblk device: /devices/platform/msm_sdcc.3/mmc_host/mmc1 "
Im using CM from d2tmo page. I know im using the right CM files...
Click to expand...
Click to collapse
Try using different recovery. Try them all philz touch, TWRP, and Clockwork.
Sent from my SM-N900T

Gravitylog said:
Flashed back to stock (root 66), via Odin, flashed the same recovery, wiped system, cache, and dalkic in that order... And still got the "using /data/media for /sdcard/0/clockworkmod/.last_install_path.
"Can't partition non mmcblk device: /devices/platform/msm_sdcc.3/mmc_host/mmc1 "
Im using CM from d2tmo page. I know im using the right CM files...
Click to expand...
Click to collapse
I suggest stop using CWM (ClockworkMod recovery) simply because it's outdated. Please use TWRP. If you still have issues with the ROM then please check if you have the latest bootloader for your model to resume trying.

Wiped Internal Storage; now phone reboots on loading ROMs

Hey guys,
So last night I accidentally wiped internal storage in TWRP. I guess that messed up my partitions or something, I don't know. Anyway, I can still access recovery, and I've tried to do a restore (one that I made back when I was on stock 4.4.2 I think) but after that it tries to boot, gets to "Android is upgrading... Optimizing app Y of X." and once that operation completes it shows the lockscreen for about a tenth of a second, and the phone reboots.
I'm stumped. Anyone know what can I do?
Sorry if this has been asked a hundred times. For some reason the search function in the forums isn't working for me. And I've been looking for a solution all morning.
EDIT: FYI when I tried the restore I did only System and Data and not Boot, because I was afraid that'd cause more problems.

Did you try restoring and performing a factory wipe before booting the newly-restored ROM?

It seems that Marshmallow based roms aren't working, but Lollipop ones will boot. Not sure why as I didn't have any problem with the same MM roms in the past.
More info:
MM roms wont flash in TWRP; after the failed attempt, TWRP says system cannot be mounted until I either wipe or install a 12.1 rom.
Tried to install a stock rom (4.4.2) and it failed in TWRP. Just says "Error Flashing"

Are you performing a full wipe (system, Dalvik, cache, data) before installing or restoring a ROM? Is the phone running the latest version of TWRP?

audit13 said:
Are you performing a full wipe (system, Dalvik, cache, data) before installing or restoring a ROM? Is the phone running the latest version of TWRP?
Click to expand...
Click to collapse
Yes to full wipe. TWRP is 2.8.7.0, so yeah I think it's the newest? Not 100% sure.

Wiping internal storage should not affect the partitions. I'm not sure that TWRP even has the ability to change partitions.
Yes, 2.8.7.0 is the latester version of TWRP.
If you are on the nj2 bootloader, try flashing this in TWRP: http://forum.xda-developers.com/galaxy-s3-att/general/rooted-ucufnj1-stock-rom-t2985006

Welp, seems to be all good now. Not sure if I really did anything to fix it or not. I tried to install a stock ROM but it wouldn't boot (stuck on Samsung logo) but after that my CM13 ROM installed properly again. The one CM13 ROM I have still wont install at all - maybe that file became corrupt or something? Not sure if that's even possible.
Either way I'm all fixed up. Thanks for all your help.
Cheers

Glad you got it sorted out. If you do figure out what you did to get it working, post your answer as it may help others that are in a similar situation.