Develop Bugs

[Q] samsung keypad + font installer hangs

I have a small problem i installed font installer from the market and now after uninstalling the keyboard is stuck on the font that was last installed by the app. I have gone through the root of my sd to find the apk from which the keyboard is installed and cannot for the life of me find it. I thought maybe if i could find it wiping cache and data on that apk would remove it. If there is anyone out there that may be able to help i would greatly appreciate it.
As seen in pic its only the keyboard. Also kote that swype keyboard and gingerbread keyboard are both the same as the system font for some reason its only this keyboard and that is it.
Sent From My BloodyS2

Flash your last back up from cwm?
Or try to install the app again and set it to the default font then uninstall it.
In the future use the built in flipfont.
Deebo took your bike too?

Hey there everyone. Here is the story in list format.
- Got first Galaxy S2 (Tmobile)
- after a few days rooted the phone using odin
- uninstalled bloatware via titanium back up pro
- installed a few apps(fb, twitter, swift key x, mobli, two different font changers)
- everything was running smoothly until i actually installed a font and the app prompted for a reboot.
- i reboot and the booting process freezes at the bootloader logo (tried countless times)
- i enter recovery mode to wipe phone.
- wipe phone.
- same issue.
- i thought then that the phone had some sort of issue in itself.
- i take the phone to tmobile a few days later and tell em some bs.
- get my new phone.
- root it again same way.
- uninstall all the bloatware i want gone and install all the apps i want.
- again SAME thing happens when i install this font changing program.
the program downloads previews for 146ish fonts. you select one. it actually downloads it and reassigns the default font with the font you download and after a reboot it should work.
except i get a frozen bootloader screen. so this time around i am convinced of the app somehow messing with the bootloader settings (etc...)
soooo...i decide to flash "SGH-T989 UVKID // Insecure // Root // Busybox" by bubby323.
odin says its successful, but still same freezing issue at bootloader.
help please.

Your problem is with the ROM. Boot into recovery, mount USB, put the ROM on your SD card and flash it from recovery.
Also, stop using that app

The_Biz said:
Flash your last back up from cwm?
Or try to install the app again and set it to the default font then uninstall it.
In the future use the built in flipfont.
Deebo took your bike too?
Click to expand...
Click to collapse
I will try thanks for ur response
Edit... Reinstalling app did not work but reflashing backup did thanks ... Idk why i didnt think of reflashing
Sent From My BloodyS2

i do not have an external sd card, so is there any other method? i can always go and purchase one tomorrow. there is no way for me to put the file onto the internal sd memory because windows never recognizes the phone because it never boots up.
and trust me, i learned my lesson....never downloading that program again.

jeikazou said:
i do not have an external sd card, so is there any other method? i can always go and purchase one tomorrow. there is no way for me to put the file onto the internal sd memory because windows never recognizes the phone because it never boots up.
and trust me, i learned my lesson....never downloading that program again.
Click to expand...
Click to collapse
There are drivers posted in the dev section, be sure to try and download them again.
Your phone's "/sdcard/" location is actually an internal SD card. So when you use CWM to mount the sdcard, it will mount both the internal, and external SD card if it can. So you should still be able to do it.

as you said i was able to mount and copy over the rom, but after i copied over the rom file, it does not show on the android cwm file menu. maybe if i restart the phone?ill try it now.

still no go the rom file is not showing, the drivers have been installed. i reinstalled them JUST in case.
maybe i'm doing something.
- i mount usb storage
- copy over rom tar files
- unmount and look for it in the apply update from sd card and install zip from sd card selections but both show no files.

alright well after a few hours of trying a million different things...the only thing that worked was eaglesblood rom via cwm mount. thanks romanb for helping.

[Q] Warning - There is not enough space in your device?

Hi there guys,
From my time being on Android, I've come across a few errors that say they don't have enough "space" and this is usually down to SD card errors - but in this instant I'm completely stumped. To the point I think it is a very very bad virus.
Mum's phone: Note 2 - SIM unlocked, bought outright - she's been using it for over a year now
Symptom: When trying to open ANY picture (be it screenshot ON or OFF the EXT SD card - the erro (attached) crops up.
Things I've tried:
-Changing folder location of the camera app
-Clearing cache for camera, my files and gallery
-Clearing dalvik and cache in recovery
-Removing EXT SD card (with safe to remove and pulling out suddenly)
One thing I've noticed: I CANNOT move the DCIM folder. It says it "cannot be copied/deleted/moved"
The DCIM folder in "My Files" in fact doesn't exist as a folder - looks like a .DAT file - and when trying to click for details on the folder - it force closes the "my files"
One thing that's curious is that she can get the photos OFF her phone and view them on her PC without any problems.
I thus think the phone has a virus (also because there was two apps installed on there, which I've never seen before - apps that are from the play store, but apps I've never installed nor imagine my mum installing them)
Any ideas?
My only trail of thought is:
TB up and factory reset the phone.
-Dubbed

(Dead zone) - no one care to help?
I just completely wiped the phone, even wiped the system - re-flashed the ROM from scratch - as I restore the apps - the "gallery FC" what the beep is going on - I've had enough of these crap Samsung phones!!!!!

[Q] Messed up with platform.xml, help needed

Hello there,
I bought a LG G3 D855 16GB, rooted it and once I tried to backup with Titanium Backup to my external sdcard, I noticed I had no write permission.
I´ve followed this thread to get the permission --> http://forum.xda-developers.com/showthread.php?t=2617921
After reboot, I can no longer save anything to my internal storage (cannot download, can take pictures but they won't save, can't run some apps and so forth).
But...If I use a file manager (root explorer, ES file explorer) I'm able to copy files from external sdcard to internal storage.
Besides that, after messing up with platform.xml, I can't connect my phone to PC with MTP method nor PTP.
What have I tried, so far:
1. restore backed up platform.xml --> problem persists
2. replace platform.xml with original from someone else --> problem persists
3. Hard reset --> problem persists
4. Use LG Flash tool to unroot and replace firmware (.tot + .dll) --> Didn't work. Tried with files from different sources but always ended up with "model information check fail"
5. Use LG Flash tool 2014 to unroot and replace firmware (.kdz method) --> Didn't work. Tried with files from different sources but always ended up with interruption during s/w upgrade.
I've been playing/reading about this issue for around 3 weeks and still haven't figured out the solution. I do think it is something simple that I'm missing and I hope there's someone out here who can point me to the right direction. :fingers-crossed:
Thanks in advance!

anyone?
Come on fellows,
there's no one to help me out?
No clue at all?:crying:

problem solved!
Just to let you guys know, my phone is working again.
First I tried lg support tool but it also did not work. Then I performed (again) a Hard Reset, but this time using buttons combination (vol- and power). After this hard reset, I restore apps with Titanium Backup and everything is working fine!! :victory::victory:
Will play for I while with the phone and on the weekend try the unroot methods (.tot and .kdz) again to see if now they will work.

Junk Ware Self Installs Need Help!

I'm having issues with my DE Note 4. The issues I am having are as follows:
-Junkware Self Installing (go90, empire, cookie jam, panda pop, sugar smash, magic rush, and retail me not)
-Roms will not Clean install
I have gone through the following steps (not in exactly in order) to attempt to fix this:
=Odin Flash of two seperate Firmwares 1. https://www.androidfilehost.com/?fid=24052804347796802 (Only link I can find through Morom Rom Page [http://forum.xda-developers.com/not...m-lollipop-tw-deodexed-lp-oaf-5-0-1-t3094727]) and 2. http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3178148 (Found on the Jasmine Rom Page [http://forum.xda-developers.com/note-4-verizon/development/rom-jasminerom-v1-0-t3113771])
=Switched Out and Formatted the SD Card.
=Redownloaded fresh files (From Jasmines page files, and From Morom page files after Jasmines didn't fix it) and transferred to the new clean SD Card.
=In Recovery I completely wiped everything on the phone except the MicroSD Card and flashed the Rom.
=Wiped Cache and Divak (SP)
=Rebooted phone went through setup wizard. **SET UP AS A NEW PHONE** So no apps were "recovered"
=Once the phone was set up the crapware installed itself again... I have no idea where its coming from.
=I still have apps that should have been removed by the Custom Rom as well. Such as Hancom Office, Hangouts, Milk, Verizon Message+ which sounds like a dirty install but I am wiping EVERYTHING how is it a dirty install?
Please help I need to get rid of this stuff and have tried everything I can think of. I've searched for this problem but no one else using these files seem to have the same issue. Thanks in advance.
Additional Info:
Model SM-N910V (Developer Edition)
Android 5.0.1
Baseband N910VVRU2BOG5
Kernel 3.10.40 (MultiSystem #1)
Build Number Morom_6.4_OG5
Knox None
Configuration Ver B14.SAM.SMN910V.0
I'm going to attempt to update to the Morom 6.5 and will update.

armyofsquirrels said:
I'm having issues with my DE Note 4. The issues I am having are as follows:
-Junkware Self Installing (go90, empire, cookie jam, panda pop, sugar smash, magic rush, and retail me not)
-Roms will not Clean install
I have gone through the following steps (not in exactly in order) to attempt to fix this:
=Odin Flash of two seperate Firmwares 1. https://www.androidfilehost.com/?fid=24052804347796802 (Only link I can find through Morom Rom Page [http://forum.xda-developers.com/not...m-lollipop-tw-deodexed-lp-oaf-5-0-1-t3094727]) and 2. http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3178148 (Found on the Jasmine Rom Page [http://forum.xda-developers.com/note-4-verizon/development/rom-jasminerom-v1-0-t3113771])
=Switched Out and Formatted the SD Card.
=Redownloaded fresh files (From Jasmines page files, and From Morom page files after Jasmines didn't fix it) and transferred to the new clean SD Card.
=In Recovery I completely wiped everything on the phone except the MicroSD Card and flashed the Rom.
=Wiped Cache and Divak (SP)
=Rebooted phone went through setup wizard. **SET UP AS A NEW PHONE** So no apps were "recovered"
=Once the phone was set up the crapware installed itself again... I have no idea where its coming from.
=I still have apps that should have been removed by the Custom Rom as well. Such as Hancom Office, Hangouts, Milk, Verizon Message+ which sounds like a dirty install but I am wiping EVERYTHING how is it a dirty install?
Please help I need to get rid of this stuff and have tried everything I can think of. I've searched for this problem but no one else using these files seem to have the same issue. Thanks in advance.
Additional Info:
Model SM-N910V (Developer Edition)
Android 5.0.1
Baseband N910VVRU2BOG5
Kernel 3.10.40 (MultiSystem #1)
Build Number Morom_6.4_OG5
Knox None
Configuration Ver B14.SAM.SMN910V.0
I'm going to attempt to update to the Morom 6.5 and will update.
Click to expand...
Click to collapse
You need to either open the rom.zip file and delete the folder system/priv-app/IgniteVerizon before you install the ROM or use a root browser to delete it on your phone. I would delete it from the zip file before it gets installed. That way DTIgnite won't get installed on your phone and add all the junk apps in the first place. The folder system/priv-app/IgniteVerizon should have been removed from the ROM in the first place because it is spyware.

Misterxtc said:
You need to either open the rom.zip file and delete the folder system/priv-app/IgniteVerizon before you install the ROM or use a root browser to delete it on your phone. I would delete it from the zip file before it gets installed. That way DTIgnite won't get installed on your phone and add all the junk apps in the first place. The folder system/priv-app/IgniteVerizon should have been removed from the ROM in the first place because it is spyware.
Click to expand...
Click to collapse
Thank you. I will try this right away.

Will a Build Update repair a Bluetooth issue?

Let me start over and explain, a little background might help you understand what I am trying to do.
I have 4 S3 SPH-L710's / Software version L710VPUDNJ2 / Hardware version L710.14 / Android 4.4.2 / Baseband version L710VPUDNJ2 / Kernel version 3.4.0-2851177/ Build number 2.02.11.0701 ((and here is where one of them is different,, one of the S3's has a Build number 2.01.11.0505)), all from FreedomPop(which is a Sprint device) and all bought at the same time. They all have TWRP recovery & SuperU installed from FreedomPop.
The 3 with the Build number 2.02.11.0701 have working Bluetooth on them, but the one with the Build number 2.02.11.0701 does not have Bluetooth working, since that is the only difference I have found and I have tried multiple factory resets to fix it I wanted to update that one phone to the matching build of the other three to see if that fixes it.
Can I use the ROM/OS from one of the working S3's by backing it up some how and then using it to flash the non working S3?

Mr Stewart said:
Let me start over and explain, a little background might help you understand what I am trying to do.
I have 4 S3 SPH-L710's / Software version L710VPUDNJ2 / Hardware version L710.14 / Android 4.4.2 / Baseband version L710VPUDNJ2 / Kernel version 3.4.0-2851177/ Build number 2.02.11.0701 ((and here is where one of them is different,, one of the S3's has a Build number 2.01.11.0505)), all from FreedomPop(which is a Sprint device) and all bought at the same time. They all have TWRP recovery & SuperU installed from FreedomPop.
The 3 with the Build number 2.02.11.0701 have working Bluetooth on them, but the one with the Build number 2.02.11.0701 does not have Bluetooth working, since that is the only difference I have found and I have tried multiple factory resets to fix it I wanted to update that one phone to the matching build of the other three to see if that fixes it.
Can I use the ROM/OS from one of the working S3's by backing it up some how and then using it to flash the non working S3?
Click to expand...
Click to collapse
[SOLVED]
Here is what I did and it worked.
Bad phone = phone I want to flash/fix - - - - Good phone = phone I want take backup from
On Samsung Galaxy S3 you boot to TWRP by holding volume up + center home button then press and hold power button too untill you see some blue words at the top left of the screen, then release all three buttons.
Folder paths will be the same on your SD card but folder names will be different, see the note at the bottom about file names and folder paths.
What I did is run a backup on the bad phone in TWRP to the ext SD card in case anything went wrong. After it finished I turned the phone off and removed that SD card, then I turned the phone back on and ran a factory reset on the bad phone, when it finished and was at the first screen where you chose your language I turned the phone off. Then I inserted the SD card in my PC and found a folder with the file path TWRP>BACKUPS>551f9321>2016-03-03--18-28-10_2.01.11.0505 so I copied it to a folder on my PC and then deleted the last folder, the one that has a date for the name that had the backup files in it. Leaving the empty folders on the SD card TWRP>BACKUPS>551f9321
On the good phone I ran a backup in TWRP to the ext SD card, after it finished I turned off the phone removed the SD card and inserted the SD card in my PC, on the SD card I found folders with a file path like this TWRP>BACKUPS>9817290e>2013-12-31--18-55-59_2.02.11.0701, so I copied that to my PC(so I could return that phone back to its original state when this was all done) then deleted the dated folder off the SD card, leaving the empty folders TWRP>BACKUPS>9817290e on the SD card. With the SD card OUT of the phone I ran a factory reset on the good phone, when it finished and was at the first screen where you chose your language I turned the phone off. I booted in to TRWP and ran a backup to the ext SD card, when it finished I turned off the phone and removed the SD card and inserted it in to my PC, I copied the the dated folder TWRP>BACKUPS>9817290e>2013-12-31--18-55-59_2.02.11.0701 , to my PC and deleted it off the SD card, Then I took the original backup I made for this phone and returned it to the SD card so I could use it to restore the good phone in TWRP.
Back to the bad phone: I inserted the SD card in to my PC and copied the second backup I made from the GOOD (the backup I made AFTER the factory reset) phone to the folder file path TWRP>BACKUPS>551f9321>2013-12-31--18-55-59_2.02.11.0701 (this is the newer build number I am hoping fixes the Bluetooth issue on my phone) then I put the SD card back in to the bad phone and booted in to TWRP and ran a restore from the ext SD card, when it finished I was at the language selection screen!! I went thru the setup and let all my apps update from Google Play Store - entered my accounts in settings - and after all the updating I restarted my phone and tested Bluetooth.......................IT WORKS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! And I checked the Build number in Settings>More>About device>Build number shows 2.02.11.0701 = SUCCESS !!
Hardest parts:
1. Keeping track of which SD card is which(I used the phone cases I took off of each phone to hold the respective SD cards while not in use to keep them separated, I also noted the brand name of each just in case)
2. Keeping the backups organised - there will be a total of three backups, a backup of each phone and the backup made after the factory reset you use to flash the bad phone.
A word about file names and paths:
The first time I tried this I copied the entire folder path from the good phones backup to the bad phones backup, AND it didn't work. Problem is that the folder path has a unique number for each phone in it EXAMPLE -> TWRP(this folder name will be the same on all phones)>BACKUPS(this folder name will be the same on all phones)>9817290e(this folders name is UNIQUE for each phone)>2013-12-31--18-55-59_2.02.11.0701(this is the dated folder that contains the backup)