Database Users

[Q] Sense vs stock sms

Here's the only thing keeping me away from sense roms. I've read a few posts regarding this as well, but they were all id's, not solutions.
After firing up a sense build, restoring sms from stock results in two separate threads per person (one for sent, another for received).
My guess is if I just wipe everything, all should be fine. My need is, of course, not having to lose all my precious 3000+ messages.
Anyone have any idea?

bump........

no one has any idea? :/

error message after the first installation, and then wont reboot.
i keep getting this error message:
differnces: (offsetriginal/backup)
65:01/00
not automatically fixing this file
/dev/block/mmcblkop1: 3531 file, 390986/485936 cluster failed
failed to find rootfs on sd card. you may need to unzip a rootfs zipfile to the root of your sd card
/bin/sh: cant access tty: job control turned off
#
then it take so long doing bunch of number in a very slow rate
then it take so long doing bunch of number in a very slow rate
i have: mattcfroyosense1.7, radio: 2.15.50.14,and omega v17 wwe..
it work the 1st time with mattcfroyosense 1.7 and froyo android 2.2
getting frustrating, keep taking battery off and trying again but still get stuck on the same spot.
it does it to all android that i use. do u have a solution?

What are you using to restore sms?
Sent from my HTC HD2 using XDA App

i got it boot up now by placing the files in the android folder. that work for a bit.
now when i boot up i get a green screen. what do i do now?

Mic gain and "scratchy sound" / default.acdb (Not the robo error)

A issue that need som attention:
In all the latest kernels I have used, the mic gain is to high on the HD2.
To fix this we previously could rename or delete default.acdb. The downside whit this fix now is that i get an "system has stopped" error after rebooting and i dont know if this affects other parts of the build/kernel as well.
I know this is a issue that several other have as well but as it seems not everybody.
Maybe this issue is something the great devs of XDA should adress? Great work by the way.
The thread with the previous fix:
http://forum.xda-developers.com/showthread.php?t=805002&highlight=default.acdb

I've had this fix (renaming/deleting default.acdb) done on many builds and it never showed me an error message or any evidence of a problem.
Maybe you're passing data.img file from build to build and not starting with a new fresh
one?

Always fresh when changing build/kernel.
But strange if its only me that get the error.
If this should be looked at by devs offcourse depends on how many that this issue conserns.
I know the default.acdb is to find in at least two places:
/system/etc/firmware (this is the location I renamed default.acdb)
"and"
/etc/firmware
I have tried to rename the file in the other location as well but that really made my phone go crazy.

I only rename the one at: /system/etc/firmware
This is just to solve for me the mic gain so that others won't think I am in some factory.

hey oyvpet. you are the only other person that seems to have the same issue i have. I posted the same question in the mdj revolution 1.7 build thread because it was the first build that gave me this issue but now it's happening in mdj's desire hd 4.0 build as well. i guess it's not build specific but it does not happen on all builds for me.
no one else seemed to have the same issue so i figured out a way to fix it by trying a number of things and i actually did come up with a working solution. just renaming default.acdb gives a force close at start-up, as does deleting/moving the file completely. What seems to work for me is replacing it with a dummy file.
step 1 - download the installation file "es file explorer.apk" and put it on your SD card.
step 2 - using root explorer for the rest of the steps, delete default.acdb from system/etc/firmware.
step 3 - rename "es file explorer.apk" - "default.acdb"
step 4 - drag your "new" default.acdb from your sd card location to system/etc/firmware.
step 5 - full restart back to WM (not hot restart)
android will now boot up normally, without a force close error and your friends will not complain about you talking to them on your phone, in the shower with the water running.
i don't know if other apk's work. i did try root explorer.apk too and it did fix the force close at start-up but i still had the loud echo on the other end.
good luck.

[FIX] Bad sound/Mic Gain and high volume in call
[FIX] Bad sound/Mic Gain and high volume in call

Can't find my 2.3 update

I was out of the country and used my phone on wifi. Of course as soon as I am gone, I get the notification for the 2.3 update. I downloaded it (160 megs or so) over wifi, but didn't install it since I wasn't sure if it would turn off my airplane mode and I would get slammed by tons of txt which add up $$ quick. It was always in my notification bar for the update and when I cleared all notifications it was still there under "ongoing". I landed back in the US and turned on the cell. A few minutes later I looked in the notifications and the update was gone. Anyone know where the file was saved on my phone so I can go ahead and run the update? Thanks in advance. I checked the "about" screen and I am still running 2.2 (was hoping it automatically updated without me knowing it).

DMC78 said:
I was out of the country and used my phone on wifi. Of course as soon as I am gone, I get the notification for the 2.3 update. I downloaded it (160 megs or so) over wifi, but didn't install it since I wasn't sure if it would turn off my airplane mode and I would get slammed by tons of txt which add up $$ quick. It was always in my notification bar for the update and when I cleared all notifications it was still there under "ongoing". I landed back in the US and turned on the cell. A few minutes later I looked in the notifications and the update was gone. Anyone know where the file was saved on my phone so I can go ahead and run the update? Thanks in advance. I checked the "about" screen and I am still running 2.2 (was hoping it automatically updated without me knowing it).
Click to expand...
Click to collapse
here, download THIS FILE, and rename it to "PD15IMG.zip"
place it in the root of your sdcard, reboot into hboot/bootloader by holding power +volume down buttons, then follow the onscreen instructions.
good luck

That file saranhai gave you is exactly what you need. Do as he says, and you'll get what you are wanting. Its the least dangerous flash you can make to your phone. If you walked into T-mobile and asked for the update they would pop in an sd card with that file and follow the same procedure.
BTW, its important that the name be all caps.
Sent from my HTC Glacier using XDA App

Correct me if I'm wrong, but I believe doing this manual install will wipe your device's memory. Just a heads up as a reminder to backup your data beforehand.

Yeah, it will. Sms backup & restore will save your sms messages at least.
Sent from my HTC Glacier using XDA App

Thanks for the help. Is there any way to run the update that I already downloaded ? I assume that it is stored somewhere, and wanted to see if anyone had an idea where.

Hello,
I really dont know if the file has the same name but you can try using find.
Something like that :
Code:
adb shell find / -name PD15IMG.zip
Regards

n00b help! Tombstone problem [fixed]

Yesterday I flashed maniac103's latest CM7 build. Before that I used a couple of Euroskank builds, after several months using Quarx/Eppy 7.1-11-11-11.
Today I have run into the Tombstone problem with no free space on the phone. I moved a couple of apps to SD, but the tombstone immediately fills out any empty space that I can create.
I've searched and the general advice is "delete the tombstone file". Great... except I can't find it? When I browse /data there is nothing there. Is this a permissions issue? Any advice on how to solve the problem and prevent it recurring?
I would be extremely grateful for some help, in simple english and with big pictures and chewable pages ideally...

Ok, I have managed to fix it myself. For any other challenged users, here it is
My problem was that the standard file manager could not see anything in /data
I tried using terminal, but equally that would not allow me to do an ls in /data (view a list of the files in /data).
This came down to a permissions issue.
Earlier on I had deleted Adobe Flash player, which seems to be regarded as the root cause of the tombstone problem. However, I still had no free space (at all - 0.00MB available). After removing Flash player, I uninstalled another app (google+ simply because I don't use it and it's big - 22MB). After uninstalling I had 14MB showing free, which allowed me to install Yaffs explorer. This allowed me to browse with superuser enabled - now I could see the contents of /data, and find the /data/tombstones folder, and find the 905MB file that was causing all of the problem. Deleting that file (tombstone_09 in my case) solved the issue.
Hopefully this will be of help to someone equally as clueless as I.

I just had this exact same issue. Inside the tombstone folder I had tombstone_00, tombstone_01, tombstone_02 and tombstone_03. The first 3 were about 60 Kb each, but the fourth one had 885 Mb. Deleted it and it's back to normal.
This is the first time having this issue, I was using CM 7.1 for almost a year and switched to CM 7.2 last month.

Thank you so much, had this issue, without your post I wouldn't know what to do
Sent from my MB525 using xda premium

Well, the problem has reoccurred, although I now have the tool to fix it.
So my next question...
What causes the problem? How do we stop it happening again?

maniac had been looking into it and told us, that he maybe screwed up on something when he compiled the build that was supposed to fix this issue.
The builds from yesterday on should limit the filesize of tombstones to 1MB correctly.
If it doesn't work, don't blame maniac for this, because it's Adobe's fault. maniac is simply not able to look into code from 3rd party apps.
I also had big tombstones especially when watching flash-videos in the browser. So far they're gone. But you could try to trigger a tombstone that way...
Greetz, Unr3aL67
Sent from my Defy via Tapatalk

I'm not blaming maniac103 - I am extremely appreciative of the work he has done along with that of Quarx, Epsylon and others.
Last night I updated to 16th may build from Maniac, so will keep an eye on things.

[Q] Touchscreen doesn't respond after using bogus photo recovery software

Hello, ladies and lads!
Here's a short version of where I'm at: after installing Wondershare' s dr.phone Recovery on my mom's PC and using it on her phone:
its screen won't respond to touch (can't enter SIM card's PIN nor open screen lock)
the On/Off button won't turn off the phone on long press (maybe due to screen lock)
on restart there's a yellow text that reads "Set Warranty Bit : kernel"
the physical buttons still work
I can see the phone's files and folders only through PC's command prompt, using ADB ('This PC\Galaxy Grand Prime' folder in Win Explorer says it's empty).
Ideally I want to keep her data (FB Messenger, Skype, Chrome, WiFi passwords, etc), and her phone to function again. What do you think I should do?
I think I need an advice and suggestions from someone more experienced than me - I don't even know trusted sites where to download the firmware roms from.
The phone's details are (I'm afraid you'll have to walk me through to get more details to this list, as I'm new to the forum):
Phone: Samsung Grand Prime
Model name: SM-G530FZ
Firmware version: G530FZXXS1BQC2 (Android 5.0.2 with Baltic bloatware, I guess)
Now in detail:
My knowledge and experience regarding the smartphone software & restoration is very basic (I've only restored the firmware to a LG-L70 once some years ago, and that's it).
Before the problem I lost some over 600 media files from that phone by Cutting and Pasting a folder from phone's internal SD to PC's disc. Now I learned never to Cut-Paste important or irreplaceable files. The files ended up on the phone, because a folder with over 800 files couldn't be uploaded to the Google Drive (the camera's folder had over 1k files in it, so I moved some of them to another folder, which the phone created on the internal partition rather than the SD Card, where the original folder was from).
Instead of using a trusted software, I foolishly Googled a photo recovery program for phones, using my mom's PC. A list of bogus recovery program sites appeared (had to look them up on her PC, as I found only legit, widely trusted programs now, using my laptop. Those darn Google's personalized search result algorithms!).
Before using the dr.fone Recovery software I synced most of the data to her account.
Used the "free" dr.fone Recovery software as per its site's instructions, the phone did a restart and the touchscreen went unresponsive to touch. Later the software showed the lost files it found, and offered to restore them for a sum. Naturally I declined.
The software said that to return the phone to normal I need to disconnect the USB cable. I did so, but the phone's screen remained unresponsive to touch, even after restart (long-press [Pow] + [Vol-]).
I tried connecting an USB mouse via the dongle, but the mouse cursor didn't appear (maybe this phone doesn't have this functionality).
Now, after using that FAIL-covery program, I was overly cautious not to make things even worse.
I wanted to make a copy of the phone's internal SD state (or is it called a phone's hard drive?), to get the media files from the clone and to have a backup of mom's files.
But I failed: I downloaded APK, ncat, KingoRoot and BusyBox. Tried to follow the steps in this video: youtu[dot]be/KKkvkCgMeMA. Got stuck at "busybox not found" at about 10:27 mark in that video ("dd if=/dev/block/mmcblk0" "busybox nc -l -p 8888"). Turns out you need to run some of the apps from that phone prior to that step, and I don't know any workarounds.
Then I remembered that the files were on the external SD in the first place. Well duh! I then connected the Micro SD card to PC's reader via a Micro SD adapter. To make a copy of the SD card's 1s & 0s, and to restore the media files from said copy I used ZAR (Zero Assumption Recovery) z-a-recovery[dot]com/. The backup creation (an .ISO file or some such) and media recovery are free of charge.
Now I only need to remove duplicates and blurry pics (I think I had a Moleskinsoft's Clone Remover from an old PC magazine's CD lying around somewhere for the latter). Oh, and I better not forget to run a malware scanner on her PC and remove the mr.fone installed services and folders from it. Went a bit off-topic here, sorry!
Last I pulled a wifi passwords file with "adb pull /data/misc/wifi/wpa_supplicant.conf" command as per instructions on this page: mashtips[dot]com/see-wifi-password-android/. I don't know whether putting the file back on that phone will do the trick or not.
That's pretty much all.
I hope the situation can be resolved and I appreciate your input! :fingers-crossed: Maybe someone has come across a similar post, has constructive commentary or knows something obvious that I haven't come up with? Thank you in advance!
Edit 30 Jan '19: Got the phone working. Accessed the phone with a Chrome browser extension (name here). All accounts except some mail account were gone. WiFi didn't work.
Found a stock ROM here: (address here).
Found the Odin3 tool here: (address here). It came with a different locale ROM.
Flashed the 1st ROM with Odin. The screen started to work.
Flashed the 1st ROM with Odin again. The WiFi started working.
I'll update this with links soon.

I've got the exact same problem after using Dr Fone app!
Hi there.
I've got the same problem with my Samsung Galaxy Grand Prime after using Dr Fone, like you. I contacted Wondershare website from which I downloaded the app but they haven't bothered replying. Not happy at all!!
I contacted Samsung's support team and after trying different things (the usual stuff: reboot; remove the battery and SIM card; restart in Safe Mode; etc) which didn't solve the problem, they ended up telling me to reset the phone to the factory settings but that didn't work either.
Now my phone is stuck on the Samsung Galaxy Welcome screen which asks me to choose the language I want on my phone. The touchscreen is still unresponsive.
How did you manage to fix the problem if the touchscreen was unresponsive?
Thanks in advance for your help!
Your-Mum said:
Hello, ladies and lads!
Here's a short version of where I'm at: after installing Wondershare' s dr.phone Recovery on my mom's PC and using it on her phone:
its screen won't respond to touch (can't enter SIM card's PIN nor open screen lock)
the On/Off button won't turn off the phone on long press (maybe due to screen lock)
on restart there's a yellow text that reads "Set Warranty Bit : kernel"
the physical buttons still work
I can see the phone's files and folders only through PC's command prompt, using ADB ('This PC\Galaxy Grand Prime' folder in Win Explorer says it's empty).
Ideally I want to keep her data (FB Messenger, Skype, Chrome, WiFi passwords, etc), and her phone to function again. What do you think I should do?
I think I need an advice and suggestions from someone more experienced than me - I don't even know trusted sites where to download the firmware roms from.
The phone's details are (I'm afraid you'll have to walk me through to get more details to this list, as I'm new to the forum):
Phone: Samsung Grand Prime
Model name: SM-G530FZ
Firmware version: G530FZXXS1BQC2 (Android 5.0.2 with Baltic bloatware, I guess)
Now in detail:
My knowledge and experience regarding the smartphone software & restoration is very basic (I've only restored the firmware to a LG-L70 once some years ago, and that's it).
Before the problem I lost some over 600 media files from that phone by Cutting and Pasting a folder from phone's internal SD to PC's disc. Now I learned never to Cut-Paste important or irreplaceable files. The files ended up on the phone, because a folder with over 800 files couldn't be uploaded to the Google Drive (the camera's folder had over 1k files in it, so I moved some of them to another folder, which the phone created on the internal partition rather than the SD Card, where the original folder was from).
Instead of using a trusted software, I foolishly Googled a photo recovery program for phones, using my mom's PC. A list of bogus recovery program sites appeared (had to look them up on her PC, as I found only legit, widely trusted programs now, using my laptop. Those darn Google's personalized search result algorithms!).
Before using the dr.fone Recovery software I synced most of the data to her account.
Used the "free" dr.fone Recovery software as per its site's instructions, the phone did a restart and the touchscreen went unresponsive to touch. Later the software showed the lost files it found, and offered to restore them for a sum. Naturally I declined.
The software said that to return the phone to normal I need to disconnect the USB cable. I did so, but the phone's screen remained unresponsive to touch, even after restart (long-press [Pow] + [Vol-]).
I tried connecting an USB mouse via the dongle, but the mouse cursor didn't appear (maybe this phone doesn't have this functionality).
Now, after using that FAIL-covery program, I was overly cautious not to make things even worse.
I wanted to make a copy of the phone's internal SD state (or is it called a phone's hard drive?), to get the media files from the clone and to have a backup of mom's files.
But I failed: I downloaded APK, ncat, KingoRoot and BusyBox. Tried to follow the steps in this video: youtu[dot]be/KKkvkCgMeMA. Got stuck at "busybox not found" at about 10:27 mark in that video ("dd if=/dev/block/mmcblk0" "busybox nc -l -p 8888"). Turns out you need to run some of the apps from that phone prior to that step, and I don't know any workarounds.
Then I remembered that the files were on the external SD in the first place. Well duh! I then connected the Micro SD card to PC's reader via a Micro SD adapter. To make a copy of the SD card's 1s & 0s, and to restore the media files from said copy I used ZAR (Zero Assumption Recovery) z-a-recovery[dot]com/. The backup creation (an .ISO file or some such) and media recovery are free of charge.
Now I only need to remove duplicates and blurry pics (I think I had a Moleskinsoft's Clone Remover from an old PC magazine's CD lying around somewhere for the latter). Oh, and I better not forget to run a malware scanner on her PC and remove the mr.fone installed services and folders from it. Went a bit off-topic here, sorry!
Last I pulled a wifi passwords file with "adb pull /data/misc/wifi/wpa_supplicant.conf" command as per instructions on this page: mashtips[dot]com/see-wifi-password-android/. I don't know whether putting the file back on that phone will do the trick or not.
That's pretty much all.
I hope the situation can be resolved and I appreciate your input! :fingers-crossed: Maybe someone has come across a similar post, has constructive commentary or knows something obvious that I haven't come up with? Thank you in advance!
Edit 30 Jan '19: Got the phone working. Accessed the phone with a Chrome browser extension (name here). All accounts except some mail account were gone. WiFi didn't work.
Found a stock ROM here: (address here).
Found the Odin3 tool here: (address here). It came with a different locale ROM.
Flashed the 1st ROM with Odin. The screen started to work.
Flashed the 1st ROM with Odin again. The WiFi started working.
I'll update this with links soon.
Click to expand...
Click to collapse