No sound after screen off - TouchPad General

I've tried several different ROMs and this problem keeps recurring :
Sound works fine when I first boot, then after the screen times out or is turned off manually the sound stops working. Both external speaker and headphones.
I've tried Butta, ClassicNerd, LnT, and now the latest AOKP/CM9 from the Device forums. Clean installs, cache wipes, etc. Still no luck.
Sound works fine in WebOS, fwiw.
Any suggestions? Thanks!
Matt
Sent from my aokp_tenderloin using xda app-developers app

That is really strange, I have heard of static when the screen is off. In fact that used to happen to me with the older CM9 ROM's... But no sound all together after the screen is off is strange... I know some system settings can persist between ROM's in the /data partition. Maybe you want to try a Nandroid backup, and then wipe everything including /system and /data. Sorry to hear about your troubles...
PS, how long has that been happening for? Did it always do that?

-SGA- said:
That is really strange, I have heard of static when the screen is off. In fact that used to happen to me with the older CM9 ROM's... But no sound all together after the screen is off is strange... I know some system settings can persist between ROM's in the /data partition. Maybe you want to try a Nandroid backup, and then wipe everything including /system and /data. Sorry to hear about your troubles...
PS, how long has that been happening for? Did it always do that?
Click to expand...
Click to collapse
Thanks for verifying my hunch that this is something unusual!
I don't recall if it's always done this - the first few ROMs I tried back in April/May of this year were pretty flaky and I remember having sound problems with all of them.
I've tried doing backups and wiping /system and /data directories, to no avail.
Could it be something kernel related? (I don't know if Touchpad ROM's typically include kernels.)
Another strange quirk I'm experiencing is that I can only get things to boot up correctly if I choose "Cyanogenmod" on moboot. AOKP fails and gives me something about an invalid size uImage and Classicnerd boots but wifi doesn't work. Perhaps there's something messed up with my boot image?
Thanks again,
-Matt

memckimmy said:
Thanks for verifying my hunch that this is something unusual!
I don't recall if it's always done this - the first few ROMs I tried back in April/May of this year were pretty flaky and I remember having sound problems with all of them.
I've tried doing backups and wiping /system and /data directories, to no avail.
Could it be something kernel related? (I don't know if Touchpad ROM's typically include kernels.)
Another strange quirk I'm experiencing is that I can only get things to boot up correctly if I choose "Cyanogenmod" on moboot. AOKP fails and gives me something about an invalid size uImage and Classicnerd boots but wifi doesn't work. Perhaps there's something messed up with my boot image?
Thanks again,
-Matt
Click to expand...
Click to collapse
I would say, yes, absolutely! You should delete the uimage files you are not using and flash a fresh ROM. I bet getting all those out of the way will help with your sound issue. I know that things get messed up when the touchpad no longer is associating the right uimage with the ROM.
Do you know how to do that?

In the meantime. The work around is boot TP wish headphones jacked in. Wait for device to go to sleep. Wake up device, remove jack. Fixed. A known issue with some 32GBs
-SGA- said:
I would say, yes, absolutely! You should delete the uimage files you are not using and flash a fresh ROM. I bet getting all those out of the way will help with your sound issue. I know that things get messed up when the touchpad no longer is associating the right uimage with the ROM.
Do you know how to do that?
Click to expand...
Click to collapse

Thanks for the headphones tip, I'll give it a try and report back.
I tried wiping out old boot files and reinstalling but that didn't seem to help.
Sent from my ADR6425LVW using xda app-developers app

Good news - sound is now working! I think the headphone trick, combined with having cleaned out the boot files, took care of it.
Thanks, all, for your help in resolving this problem.

Related

[Q] power shutoff mid-lagfix - what to do?

Hey folks,
While I was in the middle of ryanza's one click lagfix (v2.0), I happened to have a power outage in my house. Literally when it said it was in the middle of creating the ext2 partition via ADB.
Apparently my gmail still works, but pandora gets an error (most common apps for me basically). I'm not exactly planning to test all features mid-failure, but I was wondering was - what things I should be doing prior to when I try to re-run the lagfix and hopefully fix the ext2 partition? That will be tonight after work, so I've got time.
I'm just trying to think of worst case scenario/etc. Phone is rooted, still running, and not appearing bricked. yet.
Perform the un-lagfix first, then re-apply the lagfix - IIRC the lagfix creates a backup of your data directory, then replaces the data directory with the new ext2 filesystem (the lagfix's guts).
The unlagfixme.bat reverts this change, and should put everything back the way it was, from which you can re-apply the lagfix. Give it a shot and see if that works for you.
thank you for clarifying, that was what I thought too, but I wasn't 100%.
Undo and then redo worked
Sent from my Vibrant using xda app
designerfx said:
Undo and then redo worked
Sent from my Vibrant using xda app
Click to expand...
Click to collapse
How do you install Lag Fix? Thanks.
nguyenmd said:
How do you install Lag Fix? Thanks.
Click to expand...
Click to collapse
the instructions are in the topic Vibrant Deevlopment - there is a thread titled "ryanza's lag fix" or equivalent.

[UTILITY]EXT4 Formatter (CWM3 recovery package) UPDATED EC09 Gingerbread

THIS UTILITY IS FOR FASCINATE TOUCHWIZ FROYO/GINGERBREAD ONLY
UPDATED FOR EC09 GINGERBREAD
I have created a format utility that can be used from within CWM3 recovery. Just select the ZIP in CWM3 recovery, and the package will do ALL of the work for you.
These utilities come in two independent packages which will completely format your device with EXT4. As a bonus, it will create all directories and setup all ownership and permissions in accordance to the Fascinate.
Voodoo recovery does not currently allow you an option to select a format style, and furthermore does not truly format any partition unless it runs through the Voodoo "lagfix" transition upon booting the device.
There is one caveat in order to use EXT4: you need a kernel that supports it, and this would be using a "Voodoo" style kernel that has built in support. Luckily, most of the "good" kernels available have this ready to go.
Understand that this package will completely wipe your system, data, datadata (dbdata), and cache. This is a "full" wipe of the device. If you already have a ROM installed on your device and want to keep your device the way it is, and also want EXT4, then use the Voodoo method to switch to EXT4. The reason for this is because it backs up your data before it formats.
After you use this package, you can install any ROM of your choosing, as the package will already self-manage Voodoo's methods for "enabling" or "disabling" the "lagfix".
--------
Please report if the package is not working.
A good indicator of this is if you try to install the package and it only takes 1 second to work, then says it is finished. This means it is probably not working, however, if you are formatting the same type of file system over itself with no pre-existing data on the device, it will take the aforementioned 1 second to work.
To see if it worked: mount each partition in CWM3 recovery, then adb shell into your device and type the mount command, in the listing you should see what file system your partitions are using. If the big four all say EXT4, then the package install has been successful.
In order to assure that it will work correctly, use the latest version of a CWM3 recovery that you can find. I can personally vouch for nemesis2all's OTB CWM3 Recovery v3.0.2.8x.OTBv2. Unfortunately not all CWM3 recoveries are the same, and yours may not work with these utilities. If you find a recovery that works fine, post it here and I will update this.
--------
Packages updated: 6/28/2011 - 12:57PM EST
EXT4 Format ALL (formats everything): http://www.mediafire.com/?6hx7f8g7c8vv6xz
EXT4 Format CACHE: http://www.mediafire.com/?2621a888ydv41mg
EXT4 Format DATA: http://www.mediafire.com/?ck2bb340yybpe4z
EXT4 Format DBDATA: http://www.mediafire.com/?ahxzs8xsyyvemed
EXT4 Format FOTA: http://www.mediafire.com/?42ijpi67grdb6mm
EXT4 Format PREINSTALL: http://www.mediafire.com/?d42as1l3pdbhr2t
EXT4 Format SYSTEM: http://www.mediafire.com/?rgs46hhq8qd951t
--------------------
If you like my work, consider donating, or thanking me by clicking the thanks button
thanks for this
navenedrob said:
I have created two format utilities that can be used from within CWM3 recovery. Just select the type of file system you want to use, select it in CWM3 recovery, and the package will do ALL of the work for you.
These utilities come in two independent packages which will completely format your device with either RFS or EXT4. As a bonus, it will create all directories and setup all ownership and permissions in accordance to the Fascinate.
Voodoo recovery does not currently allow you an option to select a format style, and furthermore does not truly format any partition unless it runs through the Voodoo "lagfix" transition upon booting the device.
There is one caveat in order to use EXT4: you need a kernel that supports it, and this would be using a "Voodoo" style kernel that has built in support. Luckily, most of the "good" kernels available have this ready to go.
Understand that this package will completely wipe your system, data, datadata (dbdata), and cache. This is a "full" wipe of the device. If you already have a ROM installed on your device and want to keep your device the way it is, and also want EXT4, then use the Voodoo method to switch to EXT4. The reason for this is because it backs up your data before it formats.
After you use this package, you can install any ROM of your choosing, as the package will already self-manage Voodoo's methods for "enabling" or "disabling" the "lagfix".
Please report if the package is not working.
A good indicator of this is if you try to install the package and it only takes 1 second to work, then says it is finished. This means it is probably not working, however, if you are formatting the same type of file system over itself with no pre-existing data on the device, it will take the aforementioned 1 second to work.
To see if it worked: mount each partition in CWM3 recovery, then adb shell into your device and type the mount command, in the listing you should see what file system your partitions are using. If the big four all say EXT4 or RFS (depending on script used), then the package install has been successful.
In order to assure that it will work correctly, use the latest version of a CWM3 recovery that you can find. I can personally vouch for nemesis2all's OTB CWM3 Recovery v3.0.2.8x.OTBv2. Unfortunately not all CWM3 recoveries are the same, and yours may not work with these utilities. If you find a recovery that works fine, post it here and I will update this.
Click to expand...
Click to collapse
Ok, I think I'm having a complete idiot moment here so please be patient with me. What would be the benefits of me running this on my device that is currently running jt's CM7 with OTB 1.5 kernel and EXT4 (voodoo for those who don't know) already converted? Thanks in advance.
It would be of no use. Unless you need to format your entire device.
So this would be a good thing to flash in place of wiping between rom flashes? Does it have any benefits compared to a regular data and cache wipe when you are already converted to ext4?
It would be a good idea to flash it in that scenario, yes. Currently no ROM will do the job that this package will for you, which is why a lot of ROM's say not to wipe your device, because you'll run into major issues if you do. When you do your "wipes" through recovery it doesn't really do anything besides a recursive delete of files, so it doesn't really format anything (even though it says "format" in the menu system). The only time it actually does any formatting is during the Voodoo transition. When you do wipe those areas, it does not leave the file structure intact and also does not leave the ownership and permissions intact. These packages completely solve that problem. Also, these packages are focused on performance so everything is done that is possible to make sure that your file system is as fast as possible.
navenedrob said:
It would be a good idea to flash it in that scenario, yes. Currently no ROM will do the job that this package will for you, which is why a lot of ROM's say not to wipe your device, because you'll run into major issues if you do. When you do your "wipes" through recovery it doesn't really do anything besides a recursive delete of files, so it doesn't really format anything (even though it says "format" in the menu system). The only time it actually does any formatting is during the Voodoo transition. When you do wipe those areas, it does not leave the file structure intact and also does not leave the ownership and permissions intact. These packages completely solve that problem. Also, these packages are focused on performance so everything is done that is possible to make sure that your file system is as fast as possible.
Click to expand...
Click to collapse
Ok, so basically what you are saying is this would be ideal to use instead of data/cache/dalvik wipe for rfs to rfs and ext4 to ext4, correct? Thanks in advance.
That's correct.
I've teamed up with nemesis2all and we are thinking about adding all of these abilities to the OTB kernel, so you'll be able to choose different kinds of file systems and format options through CWM3 recovery instead of having to use these packages here. That will come when it comes, but for now this is the ideal solution.
EXT2/EXT3/EXT4/XFS/RFS etc...
Also, I've updated the attachments in the post.
navenedrob said:
That's correct.
I've teamed up with nemesis2all and we are thinking about adding all of these abilities to the OTB kernel, so you'll be able to choose different kinds of file systems and format options through CWM3 recovery instead of having to use these packages here. That will come when it comes, but for now this is the ideal solution.
EXT2/EXT3/EXT4/XFS/RFS etc...
Also, I've updated the attachments in the post.
Click to expand...
Click to collapse
Just to let you know, I ran the ext4 package and I got some serious lag issues after I installed my rom and it actually starting going into a soft boot loop. It began to act very weird and unstable. I booted back into recovery and I wiped everything the way I usually do and formatted the system/data/dbdata/cache manually in mounts and storage and reinstalled. It's better than it was but it still seems like it is kinda slower and more laggier than it was before I ran the package. Any ideas? Thanks man.
You'll need to give me more information than that to determine your problem.
What kernel are you using? What recovery are you using? What ROM are you running? What are the results of running the mount command with all partitions mounted?
navenedrob said:
You'll need to give me more information than that to determine your problem.
What kernel are you using? What recovery are you using? What ROM are you running? What are the results of running the mount command with all partitions mounted?
Click to expand...
Click to collapse
OTB 1.5, CM7. It's kinda weird. When I ran your package and then flashed cm7 and booted it, it was laggier than I have ever seen my phone and when I would try to do certain operations it would soft boot. At one point I couldn't even turn wifi on. So, I booted back into recovery and wiped and manually formatted everything and reinstalled everything. After that it was still kind of laggy but much better. I restored all of my apps and got my phone back to all my custom settings. Then I began to notice that it wasn't really lagging anymore, in fact it seemed pretty snappy. I ran quadrant to see if the numbers were the same as before to determine if I was in fact ext4 converted. Surprisingly the numbers were higher than normal. And I even noticed in titanium backup that some of my internal memory had been freed up. I can't explain it but everything seems to be running really good right now. It's almost like after running your package the phone had to be conditioned, and once it was conditioned it ran real good. But, that doesn't explain why it was soft booting and wifi wouldn't work. Who knows.
Not really sure exactly, it actually could have been a few different things causing the "issues". I'm going to try your exact scenario and see what happens.
kidserious said:
OTB 1.5, CM7. It's kinda weird. When I ran your package and then flashed cm7 and booted it, it was laggier than I have ever seen my phone and when I would try to do certain operations it would soft boot. At one point I couldn't even turn wifi on. So, I booted back into recovery and wiped and manually formatted everything and reinstalled everything. After that it was still kind of laggy but much better. I restored all of my apps and got my phone back to all my custom settings. Then I began to notice that it wasn't really lagging anymore, in fact it seemed pretty snappy. I ran quadrant to see if the numbers were the same as before to determine if I was in fact ext4 converted. Surprisingly the numbers were higher than normal. And I even noticed in titanium backup that some of my internal memory had been freed up. I can't explain it but everything seems to be running really good right now. It's almost like after running your package the phone had to be conditioned, and once it was conditioned it ran real good. But, that doesn't explain why it was soft booting and wifi wouldn't work. Who knows.
Click to expand...
Click to collapse
It's possible that since you wiped your market was trying to restore all your apps in the back ground which was taking all your memory up and making your phone lag. But after you restored all your apps it was all set
Coreyc1123 said:
It's possible that since you wiped your market was trying to restore all your apps in the back ground which was taking all your memory up and making your phone lag. But after you restored all your apps it was all set
Click to expand...
Click to collapse
What I meant was as soon as it booted (during setup wizard) it was super laggy. I download TB from the market by itself and it took forever to register. I was doing the GPS fix and it soft booted. I couldn't turn wifi on and it soft booted. All before I did a batch restore in TB. And I know that the market begins to sync automatically as it always does but this was much much different.
Sent from my SCH-I500 using Tapatalk
kidserious said:
What I meant was as soon as it booted (during setup wizard) it was super laggy. I download TB from the market by itself and it took forever to register. I was doing the GPS fix and it soft booted. I couldn't turn wifi on and it soft booted. All before I did a batch restore in TB. And I know that the market begins to sync automatically as it always does but this was much much different.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
I had these same symptoms one time that I installed kasonate v7, but after reflashing, the next time it didnt.
I know you're not talking about the same cm version, but they might be related and not related to the format utility.
Ok, I ran this package again to make sure that I didn't do something wrong and to see if I would get the same results. I ran the package, flashed cm7 then gapps then OTB GB 1.5. all from the recommended recovery in your post. Again I ended up in a soft boot loop and wifi was acting up again and was causing a boot loop. So once again I booted into recovery and wiped data/cache/dalvik normally and formatted manually via mounts and storage and reinstalled again and she's running like a dream. Very weird but I must say I am very happy with the results I ended up with, regardless of how I got them. So obviously, this was not your intention for it to be done this way but I do see an improvement in responsiveness, speed and memory being freed up. Before, my free internal memory was 1.49 and now it is 1.52. Thank you sir, I appreciate this.
Thanks for this utility! Works great. Went from Jt's cm7 to the miui/touchwiz rom and ran the utility in between. My phone is running faster than ever and no issues. Thanks again!
Sent from my SCH-I500 using XDA App
Yeah running this on mesmerize with heinz 57 best my phone has ever run quadrant of 2250s @ 1.5 ghz
Sent from my SCH-I500 using XDA App
stephenj37826 said:
Yeah running this on mesmerize with heinz 57 best my phone has ever run quadrant of 2250s @ 1.5 ghz
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
You're welcome, the utility enables a few nice options as far as file system performance is concerned, that Voodoo doesn't at this time.
Do tell oh and thanks a million
Sent from my SCH-I500 using XDA App

stuck on m boot logo

Ok so i was having some laggy issues w the x2 and all the sudden i started getting process not working for things like nova laucher and such. SO i went into BSR to wipe cache and fix the permissions. Did that and now the phone sits on the Big M boot screen. Why wont it boot up. I didnt wipe dat or try to flash anything. Any way to get the phone up and runnig again w/ o SBF'g
jeff5347 said:
Ok so i was having some laggy issues w the x2 and all the sudden i started getting process not working for things like nova laucher and such. SO i went into BSR to wipe cache and fix the permissions. Did that and now the phone sits on the Big M boot screen. Why wont it boot up. I didnt wipe dat or try to flash anything. Any way to get the phone up and runnig again w/ o SBF'g
Click to expand...
Click to collapse
Well what ROM are you using for starters.
that might be important right.. .sorry.. its aokp 6
Ok. Well if you can get back into BSR, try and wipe the dalvik cache in the advance settings. I never use the fix permissions option. Maybe that did something to your device.
did that too. Still on the boot logo. is a sbf in order
jeff5347 said:
did that too. Still on the boot logo. is a sbf in order
Click to expand...
Click to collapse
Well I wouldnt see why it would do that if you just wiped cache and fixed permissions. Did you have any other mods on there? Were you using the patched CM7 BSR and not the original one?
i was using the motodx2_bootstrap_signed.apk. Not sure if the cm7 or not. Ive used this on eclipse and aokp
jeff5347 said:
i was using the motodx2_bootstrap_signed.apk. Not sure if the cm7 or not. Ive used this on eclipse and aokp
Click to expand...
Click to collapse
That one is fine to use on Eclipse. But pretty much any other ROM we have (CM7, CM9, CM10, AOKP, Paranoid Android and I think even MIUI), you need to use the CM7 BSR named "MOTODX2_Bootstrap-CM7-signed.apk" which is found in the CM7 thread. That may have been the problem.
really... damn. i dl'd it so when i flash cm10 but did not install it for thw aokp. Just off your thoughts is the cm10 stable enough now to install. i have no prob putting aokp back on but im nott looking for stability problems. If cm10 isnt stable yet i van wait
jeff5347 said:
really... damn. i dl'd it so when i flash cm10 but did not install it for thw aokp. Just off your thoughts is the cm10 stable enough now to install. i have no prob putting aokp back on but im nott looking for stability problems. If cm10 isnt stable yet i van wait
Click to expand...
Click to collapse
I think CM10 is more stable than any of the ICS ROMs. But with the stability, there comes other small issues that the ICS ROMs dont have. Its a trade off. Main issues of CM10:
1. Messing with bluetooth may cause phone to crash durring calls. Reboot fixes it until bluetooth is messed with again. (Might be fixed with an update)
2. Storage is in a different location. Not really an issue but its also swapped back to the original 4gigs for the internal. All your files will be flipped after using other ROMs for so long. (not a huge deal)
3. Due to the storage being moved around, apps that are stored on the SD card will disappear after reboot. (will probably be fixed in the future)
4. Flashing ROMs in recovery wont work. If any update comes out, you have to either SBF and update or nandroid back to ICS and update. (again, not a huge issue)
Other than that, I cant really think of any bad stuff. Its faster and I have no random reboots. I recommend it if you can live with the issues I mentioned which are honestly not bad.
Also, with the BSR files, in case you dont know already. When you are on stock 2.3.4, you first use the original BSR. Then when you flash CM10, you install the CM7 BSR.
Thanks JS
1. I never use blue tooth so then i should be all set then.. correct?
2. didnt aokp have that. I know the eclipse rom had the flip flop in it to read right but aokp i had to move my music and such so wouldnt i still be in the same boat or is it different than oakp?
3. i have some apps.. such as thems i have downloaded off of xda. So once installed they will work but rebooting will make them dissapear? is there a way to put these on the phone memory? Also curious i have google drive and have some of these installed on the drive. Will they still work or do they just dl to the sd and still not work?
4 i dont have a problem sbf'g but wondering if i nandroid the a2, will i be able to sbf, install root, a3 ect and do a data restore to get my info back?
also i will take the cm7 bsr and remeber that. Thanks
jeff5347 said:
Thanks JS
1. I never use blue tooth so then i should be all set then.. correct?
2. didnt aokp have that. I know the eclipse rom had the flip flop in it to read right but aokp i had to move my music and such so wouldnt i still be in the same boat or is it different than oakp?
3. i have some apps.. such as thems i have downloaded off of xda. So once installed they will work but rebooting will make them dissapear? is there a way to put these on the phone memory? Also curious i have google drive and have some of these installed on the drive. Will they still work or do they just dl to the sd and still not work?
4 i dont have a problem sbf'g but wondering if i nandroid the a2, will i be able to sbf, install root, a3 ect and do a data restore to get my info back?
also i will take the cm7 bsr and remeber that. Thanks
Click to expand...
Click to collapse
1. I use bluetooth every now and then but I never turn it off. It seems that toggling the bluetooth on and off or visa versa triggers the issue and a reboot fixes it again.
2. I forget what Eclipse had. Its been so long. But ever since CM7, the flip flop mod has been included in all the ROMs which meant you got your SD card (which the droid X2 comes with 8GB) as internal storage and the actual 4GB internal storage was turned into the "external storage." CM10 reverted back to the original 4GB internal and 8GB external.
3. Everything you download and install on your phone will usually be installed on the internal storage. I think if you have apps over a certain size (which isnt very many. Mostly games), they are installed on your SD card. Those are the ones the system has a problem reading after a reboot. the actual files you have downloaded from XDA will still be there. Just installed apps might disappear.
4. Not really sure what you are asking here. But if you get A2 installed and up and running and A3 comes out, You will pretty much need to start over. But for me, thats fine. I use Titanium Backup and restore everything after a wipe anyway. What data are you referring to?
ok so this is the gapps md5
MD5sum: f62cfe4a827202899919fd932d5246d7
and gapps-jb-20120726-signed.zip
is this correct
jeff5347 said:
ok so this is the gapps md5
MD5sum: f62cfe4a827202899919fd932d5246d7
and gapps-jb-20120726-signed.zip
is this correct
Click to expand...
Click to collapse
Honestly, I dont even know what MD5sum means. I'm not that tech smart. lol. I know thats the right file name though. And if you got it from here: http://goo.im/gapps you should be fine.
hahaha neither do i lol yea thats where i got it.. again thank you
No problem. If you have any other issues, just reply here and I'll help out.
one last th. sbf'd. trying t oroot with petes like i always have but it wont recognize the phone i enables debugging and unknown sources. Am i forgetting something. havent done this in a bit
jeff5347 said:
one last th. sbf'd. trying t oroot with petes like i always have but it wont recognize the phone i enables debugging and unknown sources. Am i forgetting something. havent done this in a bit
Click to expand...
Click to collapse
Pete's can be a PITA... If usb debug is enabled and unkown sources is checked just keep trying. I've had to "one click" 5 or 6 times before it works right. Close the program between tries. Also make sure your phone isn't in PC charge mode or anything.
Sorry for not updating this. After trying for 2 hrs I started trying everything. It turned out I had to use the cable that came w the dx2. No other cables worked
Sent from my MB870 using xda premium
Ah, my bad I should have read the time stamp. Anyway yea, the cable is a big deal (even though that sounds crazy.)
---------- Post added at 10:54 PM ---------- Previous post was at 10:43 PM ----------
Lol oh and btw MD5 checksums are
"The MD5 checksum for a file is a 128-bit value, something like a fingerprint of the file. There is a very small possibility of getting two identical checksums of two different files. This feature can be useful both for comparing the files and their integrity control."

[Q] [Help] it is really weirdly weird!

I'm currently using sgs2 with stock gingerbread.
My problem is, my phone seems to be locked on a specific state dated march 3rd 2013.
whenever i format usb storage or reboot my phone, it always back the way it was
e.g. when i tried to un/install apps or deleting files (succesfully), and then i rebooted it, the apps or files are still there such way unharmed.
i remember its somewhat like deep frezee. but usually, something like this only works on settings right?
its really nonsense when i deleted 8 gigs of file then i do a format/reboot, the 8 gigs files came up again like nothing has happened.
Already tried factory reset and unchecked restore backup settings.
Never faced something like this before, help is much appreciated
Sound like a problem with the rom, best thing you can do is backup everything (data) and do a complete wipe through recovery and flash a clean rom again. Very strange but have never (in all my experiece of IT etc) come across stuck dates and data that wont dissapear.
Edit: maybe this is a damaged or corrupt filing system? Still, the fix for tha would to be a complete format.
jl10101 said:
Sound like a problem with the rom, best thing you can do is backup everything (data) and do a complete wipe through recovery and flash a clean rom again. Very strange but have never (in all my experiece of IT etc) come across stuck dates and data that wont dissapear.
Edit: maybe this is a damaged or corrupt filing system? Still, the fix for that would to be a complete format.
Click to expand...
Click to collapse
before this, a had an issue with the sd card, it suddenly went corrupt and cant be read anywhere. maybe this is one of the factors too?
i do planned reflashing it with jelly bean, but i'm still curios what has caused this so i can prevent and understand the problem..
my phone cant make new memories as well, new files are nowhere to be found after reboot.
thanks for the reply jl10101
btw this reminds me of memento

[Q] CWM Wipe cache - huge problem

Alright, I hope I have this in the right place. I just recently flashed the TerraSilent Kernel for the Galaxy Player 4.0 US version. The Flash went fine, but my device was running extremely slowly. A re-flash didn't solve it either. I figured that wiping the cache partition might solve the problem - I decided to do this before running a backup, since no important data is stored in the cache (...right?), and since I was worried that backing up while I had this problem could make things worse - so I went ahead into CWM and did just that. Then, it reboots, and I nearly get a heart attack. The stock wallpaper is back, it's using the default launcher again (I had LauncherPro installed), and pretty much only system apps work, all the others have an icon with an SD card on it, and when clicked on, it says something like "application not installed". I did some searching, and it seemed like a reboot might help (although I didn't find anyone with a problem like mine anywhere). The reboot didn't do anything, so now I have it shut down, so that nothing can happen. The odd thing is, it doesn't seem to me like the system messed up and did a full wipe instead, either, because a couple of things I have are still there - for example, some of my bookmarks I made on the homescreen while still using the default launcher are still there. I'm really confused because I have wiped the cache partition before, when I was still on an unmodified stock kernel, and everything stayed the same, the way I thought it was supposed to. And now this happens. What do I do now? I exported my absolute most important data (Astrid Tasks and Calendar) before I installed TerraSilent (but I obviously wasn't able to do a full backup because I wasn't rooted, I figured installing TerraSilent would root it), so my absolute most important data is on my computer. I also did a simple file backup of the internal USB storage and external SD card to another computer before flashing TerraSilent. However, there is still a good deal of data still need, and a lot of data that would just be a pain in the rear to recreate, not to mention my (valuable to me) game data. What did I do wrong - or did something in the system mess up? And - what do I do to get back to where I was before?
It happened to me when I was on gingerbread with terrasilent. It's a known issue with this kernel. In fact, you didn't wipe the data, but the recovery contain a bug wich format the data as soon as you do an operation wich mount the data partition(I think it's this but I can't remind) but it doesn't wipe the system or anythin else, so the icon, setting and everything else stay there but without anything attach to them. I don't remind what was causing it, I only stopped using cwm with this kernel unless I wanted to flash something or to wipe everything. Sorry but I can't help you more as I don't remind everything, it's been a while since I've been on gingerbread.
ti-pich said:
It happened to me when I was on gingerbread with terrasilent. It's a known issue with this kernel. In fact, you didn't wipe the data, but the recovery contain a bug wich format the data as soon as you do an operation wich mount the data partition(I think it's this but I can't remind) but it doesn't wipe the system or anythin else, so the icon, setting and everything else stay there but without anything attach to them. I don't remind what was causing it, I only stopped using cwm with this kernel unless I wanted to flash something or to wipe everything. Sorry but I can't help you more as I don't remind everything, it's been a while since I've been on gingerbread.
Click to expand...
Click to collapse
Wasn't that problem solved with a later version of the kernel though?
And, assuming that's what happened (what you describe sounds pretty much like what happened to me), would that mean that the only way to try and get it back would be by trying to recover the formatted data?
trainman261 said:
Wasn't that problem solved with a later version of the kernel though?
And, assuming that's what happened (what you describe sounds pretty much like what happened to me), would that mean that the only way to try and get it back would be by trying to recover the formatted data?
Click to expand...
Click to collapse
It was said to be resolved, but it happened to some peoples even thought. Maybe you can recover some of your data with your computer and some tools that let you get the erased data, but I can't guarantee the integrity of your data and you would need to replace every bit of data that was there before to get it running nicely. The easiest way would be to try to recover some of your important data, put it on your computer then wipe your player and start from scratch (wipe data/factory reset) and reinstall your apps. Then put back the save, or setting or files that you got back in your apps. Hope this help, I'm not a proffessional with data recovering or where to put it back after you got it, maybe someone else could further help you with this.
And the conclusion...
ti-pich said:
It was said to be resolved, but it happened to some peoples even thought. Maybe you can recover some of your data with your computer and some tools that let you get the erased data, but I can't guarantee the integrity of your data and you would need to replace every bit of data that was there before to get it running nicely. The easiest way would be to try to recover some of your important data, put it on your computer then wipe your player and start from scratch (wipe data/factory reset) and reinstall your apps. Then put back the save, or setting or files that you got back in your apps. Hope this help, I'm not a proffessional with data recovering or where to put it back after you got it, maybe someone else could further help you with this.
Click to expand...
Click to collapse
OK, my reply is late, but thanks for your help. I managed to copy the partition with all the deleted contents over to the computer, and I'll have to study the contents some other time, because I've spent about 24+ hours on this problem in total, and need my device for more important purposes - those for which the data I managed to copy before the custom kernel and everything else. For those of you who have a similar issue, this is how I managed to save (or that is I am 95% sure this will have saved at least some, as I said I haven't studied it yet) what I hope is a good chunk of my data.
Have you tried flashing a different kernel? Terrasilent also gave me some weird in that after a few days my device would boot into recovery by itself then wipe all my data in that only my system apps would remain. So it's a little different than what's happened to you. I ended up using klin's R3 kernel or Steven's kernel that fixed the issue.
Sent from my YP-G1 using xda app-developers app
obscuresword said:
Have you tried flashing a different kernel? Terrasilent also gave me some weird in that after a few days my device would boot into recovery by itself then wipe all my data in that only my system apps would remain. So it's a little different than what's happened to you. I ended up using klin's R3 kernel or Steven's kernel that fixed the issue.
Sent from my YP-G1 using xda app-developers app
Click to expand...
Click to collapse
I've got huge issue with steve's kernel. You can get into recovery, but once you booted in it will simply bootloop. Then you have to flash back with odin. So if you go with steve's kernel, don't boot into recovery. As for klin's kernel, I've never tried it, and will probably never as we have some really nice jellybean rom that I recommend you.
I never got that issue with steve's kernel.
Sent from my YP-G1 using xda app-developers app
obscuresword said:
Have you tried flashing a different kernel? Terrasilent also gave me some weird in that after a few days my device would boot into recovery by itself then wipe all my data in that only my system apps would remain. So it's a little different than what's happened to you. I ended up using klin's R3 kernel or Steven's kernel that fixed the issue.
Sent from my YP-G1 using xda app-developers app
Click to expand...
Click to collapse
Actually, with my problem, my system apps did remain, so it's almost the same problem, only my device didn't boot into recovery on its own (seriously, it booted into recovery on its own and wiped the data? ). I only installed the terrasilent kernel to be able to upgrade to JB, so I'm now on JB, running into different problem (the wrong settings are being backed up from google backup, they're restoring from my galaxy mini 2), but thanks anyway. I am really not having any luck at all with this whole update . But ti-pich, I agree with you, that JB rom is awesome
trainman261 said:
Actually, with my problem, my system apps did remain, so it's almost the same problem, only my device didn't boot into recovery on its own (seriously, it booted into recovery on its own and wiped the data? ). I only installed the terrasilent kernel to be able to upgrade to JB, so I'm now on JB, running into different problem (the wrong settings are being backed up from google backup, they're restoring from my galaxy mini 2), but thanks anyway. I am really not having any luck at all with this whole update . But ti-pich, I agree with you, that JB rom is awesome
Click to expand...
Click to collapse
Yes it did, after 1 week. I was like ???. I reflashed it again and it did the same exact thing, and it happened to me while I was at my college too.
I also had that same issue where it was restoring from the wrong device. I just had to reflash the rom, and install stuff manually because it was making my device horribly slow.
obscuresword said:
Yes it did, after 1 week. I was like ???. I reflashed it again and it did the same exact thing, and it happened to me while I was at my college too.
I also had that same issue where it was restoring from the wrong device. I just had to reflash the rom, and install stuff manually because it was making my device horribly slow.
Click to expand...
Click to collapse
Wow that is some scary stuff, now I know why every kernel/ROM/mod has a disclaimer at the beginning ... I'm glad I'm off that now and on a stable JB build now. I found a way to have it restore at least some of the stuff from when it was on gingerbread (mostly apps and appdata, no WiFi passwords or other settings - at least I'm pretty sure, I'm still working on getting all the stuff up and running) - go into a terminal, and type
Code:
bmgr list sets
It will probably have two different sets, one for when it was on GB and one for JB - or that is, if you had the problem, there will probably be a third set for a different device (maybe more). Then, choose the one you want to restore from, and type
Code:
bmgr restore xxxxxxxxxxxxxxxx
and replace xxxxxxxxxxxxxxxx with the apropriate ID from the command before. I'm having to type it several times in order to get it to work - I type it once, it restores some apps, then stops, I type it again, and it restores some more - but I'm hoping it gets as much possible onto the JB build. I guess this won't help you much, I've seen you saying on the ICS and JB threads that you've upgraded a while ago, but I guess if someone else comes along with the same problem, I hope it will help
trainman261 said:
Wow that is some scary stuff, now I know why every kernel/ROM/mod has a disclaimer at the beginning ... I'm glad I'm off that now and on a stable JB build now. I found a way to have it restore at least some of the stuff from when it was on gingerbread (mostly apps and appdata, no WiFi passwords or other settings - at least I'm pretty sure, I'm still working on getting all the stuff up and running) - go into a terminal, and type
Code:
bmgr list sets
It will probably have two different sets, one for when it was on GB and one for JB - or that is, if you had the problem, there will probably be a third set for a different device (maybe more). Then, choose the one you want to restore from, and type
Code:
bmgr restore xxxxxxxxxxxxxxxx
and replace xxxxxxxxxxxxxxxx with the apropriate ID from the command before. I'm having to type it several times in order to get it to work - I type it once, it restores some apps, then stops, I type it again, and it restores some more - but I'm hoping it gets as much possible onto the JB build. I guess this won't help you much, I've seen you saying on the ICS and JB threads that you've upgraded a while ago, but I guess if someone else comes along with the same problem, I hope it will help
Click to expand...
Click to collapse
hmmm. I'm about to try Terrasilent with my YP-G1 (US version) running 2.3.6. This is giving me second thoughts. Does this kernel still cause issues with SGP 4.0s running GB 2.3.6?? Maybe I should try the old Steves Kernel? I just want to use voodoo sound - thats really the only reason I want to root and get these kernels.

Categories

Resources