Affichage des articles dont le libellé est Corrupt. Afficher tous les articles
Affichage des articles dont le libellé est Corrupt. Afficher tous les articles

mardi 25 mars 2014

[Q] defy plus code corrupt help! topic




Hello

I'm trying to get a Defy and this problem is new to me. I installed the Retail Room, when the battery died in the process. Actually the battery is bad contact (discovered it today) and that every time I turn the phone gives the message:

Bootloader
09.10

Code Corrupt

Battery Ok
Ok to program
Connect USB
Data Cable


I tried to flash the rom retail again, and RDS Lite is only the message "SW Update In Progress .." ..

Stay long until the battery dies again, which I carry in another defy up to 100% and try again.

What can this be guys? What I have to do to burn the right rom? I've tried some Chinese rooms but without success.

Thanks to al ! !!





lundi 10 mars 2014

[Q] Will OTA update corrupt my IMEI again? topic




Hi!

I recently got my IMEI fixed after unsuccessful update to 4.3 via ODIN. Now, when I try to update via OTA, I get a pop-up that my phone has been modified (due to root, obviously).
My question is: will my IMEI corrupt (again...) if I unroot my phone and try to update to 4.3 via OTA? Anyone tried? Anyone knows? Any answer appreciated.

If answer your is YES, is there any 100% sure way to update without corrupting my IMEI?
Thanks for help.

Greetings,
echowave





samedi 8 mars 2014

[Q] How to fix corrupt database? topic




Hello,

When I try to recover my Whatsapp messages on my new phone after I have copied the Whatsapp folder from my old phone to the SDcard, it suddenly crashes after 10 seconds: "Whatsapp has stopped working" :eek:

I looked into the System Log to find some clues about this crash. It looks like it has something to do with SQLite and the msgstore.db (or msgstore.db.crypt) file which says that the msgstore.db file is corrupt.

Can somebody help me to unravel this mistery? :confused: I really want to copy my old messages to my new phone and continue using the app on my new phone.

How can I fix the corrupt msgstore file? Or see what part of the file is corrupt (the exact cause)

NOTE: I added some screenshots of the System Log file to give you more information








Attached Thumbnails


Click image for larger version<br/><br/>Name:	Screenshot_2014-03-07-20-19-09.jpg<br/>Views:	N/A<br/>Size:	208.9 KB<br/>ID:	2619943
 

Click image for larger version<br/><br/>Name:	Screenshot_2014-03-07-20-25-53.jpg<br/>Views:	N/A<br/>Size:	213.6 KB<br/>ID:	2619944
 

Click image for larger version<br/><br/>Name:	Screenshot_2014-03-07-20-26-24.jpg<br/>Views:	N/A<br/>Size:	211.5 KB<br/>ID:	2619946
 

Click image for larger version<br/><br/>Name:	Screenshot_2014-03-07-20-27-42.jpg<br/>Views:	N/A<br/>Size:	207.1 KB<br/>ID:	2619947
 
















vendredi 7 mars 2014

[Q] [WHATSAPP] Unable to recover message history: Corrupt Database topic




Hello,

Whatsapp problem! I want to copy my chat history from my Samsung Galaxy S1 (2.3.6) to my new Nexus 5 (4.4.2).

I copied my entire Whatsapp folder to my Nexus 5 (/sdcard/Whatsapp/) and then installed Whatsapp. It asked me if I would like to recover my history chat messages. After clicking yes it started recovering but after 10-20 seconds it shuts down and an error message comes forward saying that Whatsapp had stopped working. I tried it multiple times.

When looking in my System Log file it says that it has something to do with SQLite. These are some lines in the Log file concerning Whatsapp:
  1. "E/DefaultDatabaseErrorHandler (3784): Corruption reported by sqlite on database: /data/data/com.whatsapp/databasesmsgstore.db"

  2. "E/AndroidRuntime (3784): java.lang.AssertionError: android.database.sqlite.SQLiteDatabaseCorruptExcep tion: Database disk image is malformed (code 11), SQLiteConnection.java,-2"

  3. "E/SQLiteLog (3784): (14) cannot open file at line 30191 of [00bb9c9ce4]"

  4. "E/SQLiteDatabase (3784): Failed to open database '/data/data/com.whatsapp/databases/msgstore.db' "

  5. "E/SQLiteDatabaseException: unknown error (code 14): Could not open database"

  6. "I/sqlite_db_corrupt (3784): /data/data.com.whatsapp/databases/msgstore.db"

:confused:
Can someone tell me how to fix this problem or how to find what the error causes in my database file? :crying:

NOTE: I added screenshots of System Log














Attached Files





File Type: zip sqlitecorrupt.zip -
[Click for QR Code]
(2.60 MB)









[Q] [WHATSAPP] Unable to recover message history: Corrupt Database topic




Hello,

Whatsapp problem! I want to copy my chat history from my Samsung Galaxy S1 (2.3.6) to my new Nexus 5 (4.4.2).

I copied my entire Whatsapp folder to my Nexus 5 (/sdcard/Whatsapp/) and then installed Whatsapp. It asked me if I would like to recover my history chat messages. After clicking yes it started recovering but after 10-20 seconds it shuts down and an error message comes forward saying that Whatsapp had stopped working. I tried it multiple times.

When looking in my System Log file it says that it has something to do with SQLite. These are some lines in the Log file concerning Whatsapp:
  1. "E/DefaultDatabaseErrorHandler (3784): Corruption reported by sqlite on database: /data/data/com.whatsapp/databasesmsgstore.db"

  2. "E/AndroidRuntime (3784): java.lang.AssertionError: android.database.sqlite.SQLiteDatabaseCorruptExcep tion: Database disk image is malformed (code 11), SQLiteConnection.java,-2"

  3. "E/SQLiteLog (3784): (14) cannot open file at line 30191 of [00bb9c9ce4]"

  4. "E/SQLiteDatabase (3784): Failed to open database '/data/data/com.whatsapp/databases/msgstore.db' "

  5. "E/SQLiteDatabaseException: unknown error (code 14): Could not open database"

  6. "I/sqlite_db_corrupt (3784): /data/data.com.whatsapp/databases/msgstore.db"

:confused:
Can someone tell me how to fix this problem or how to find what the error causes in my database file? :crying:

NOTE: I added screenshots of System Log





mardi 18 février 2014

[Q] Corrupt serial number and model ID topic




So I can't seem to find a solution to my specific issue. A little background first. I was on Modaco switch beta 13 and decided I'd move on to something else because 1) hadn't been an update for quite a while and 2) I really didn't switch back to Sense except when I wanted to play around with Zoe. I restarted into CWM recovery and tried to flash CM 11. It gave me an error and I realized I was downlevel on CWM recovery. I tried to flash an updated CWM and now only have access to fastboot. When I try to boot to recovery it gives me the HTC splashscreen and hangs. I tried TWRP, CWM, and stock with the same results.

Checking fastboot getvar I noticed some really strange entries. serialno and modelid were corrupt. Here is the output of fastboot getvar all


Code:


# fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.1540.3
(bootloader) version-misc: UNKNOWN SHIP S-OFF
(bootloader) serialno: ߞ�X�C
w\        `2�#
(bootloader) imei: xxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: �
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4222mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Value too large for defined data type))
finished. total time: 5.063s

# fastboot getvar mid
mid: �
finished. total time: 0.002s

# fastboot getvar serialno
serialno: ߞ�X�C
w\        `2�#
finished. total time: 0.002s


I read the following post to recover my serial number
http://forum.xda-developers.com/show....php?t=1724475

I don't believe I had the ENG hboot so I get the following:


Code:


fastboot oem writemid PN07120
...
(bootloader) [ERR] Command error !!!
OKAY [  0.012s]
finished. total time: 0.012s

# fastboot oem writeserialno 1234567890
...
FAILED (status malformed (0 bytes))
finished. total time: 1.000s


I tried flashing the ENG hboot, but....


Code:


# fastboot flash zip ENG_hboot.zip
sending 'zip' (475 KB)...
OKAY [  0.242s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 0.648s


Yep, catch 22. Corrupt model ID, so it won't flash.

Another interesting thing I noticed was the 2nd line on the display in fastboot


Code:


**** UNLOCKED ****
M7_UL UNKNOWN SHIP S-OFF RH
CID=BS_US001
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
...


Anyway one of the messages in the forums said that once they resolved the model ID and serial number everything worked.

Unfortunately this is my main phone and I'd like to use it. Not very useful right now. Anyone have any ideas?





mercredi 29 janvier 2014

Unable to save pictures or screenshots: possibly due to corrupt storage? topic




tl;dr: I cannot save pictures or screenshots on my phone, as well as a few other small quirks, can someone help?


Hello XDA, I've just recently encountered a strange issue with my Nexus 5 and I was hoping one of you might be able to help me out. I'd like to have screenshots to break up the text wall, but due to the nature of my issue, that's out of the question.

So my big problem started about two days ago, when I wanted to flash the omnirom nightly (1/27 to be exact) to my phone.

While doing the factory reset before flashing the rom, TWRP got stuck (and I'm talking about 10 minutes) formatting /data not including internal media. I was left with no choice but to hold volume down and power and hope for the best. This is what I bet screwed things up. After that I tried again, and the formatting worked, and omnirom booted, but with the error message of something about device UIDs being inconsistent and recommending I format my data partition.

Well since the rom was a nightly, I felt like ignoring the message, but I did notice issues: I could install and uninstall apps, but none of them could really access the internal storage (for example, any attempts to save a picture, like through chrome, would fail. I also couldn't restore from titanium backup. Connecting to my pc would not display my files).

Dismayed, I obeyed the message and did a full wipe of the data partition and tried again (not just the factory reset one, but the full wipe of /data, and don't worry, I could still backup using ADB pull so I haven't lost anything). This caused the UID error message to go away but I still had issues-not as bad as before-but still issues. Titanium backup worked, so I used that to restore successfully, but I couldn't make new backups. I was frustrated and blamed my issues on using a nightly so I did another full reset and went back to stock.

Now, I wasn't given another UID message, and ALMOST everything works, but I am left with the issue that is the reason I post this thread. I can't take pictures, video, or screenshots and a select few apps fail to recognize the internal sd card (reddit sync, for example, will fail to save pictures when I try to download them, but other apps, like chrome, will succeed to do so, so it is a non-issue. I could also connect to pc again, yay!).

The camera (app and hardware) will still work, and I can tell it takes the picture because the little thumbnail that slides to the side after taking a picture appears. It just fails to save the picture. When I swipe to view the picture, it shows up only as a dark gray box. If I view it in the photos app, I am greeted with the message "media not found." When I try to take videos, Camera will force close the moment I press record.

I've tried a few things, like clearing the camera's data, but that was unsuccessful. Different camera apps (I tried Focal) result in the same problem. Using the Root File Browser app, I also made sure that permissions weren't locking access to that folder. I've also tried deleting the DCIM folder by connecting to PC and then taking another picture, but that still did nothing.

I don't know what else I could do besides another /data format, but I already did that and I don't feel like another format would really do anything since I already did one. I'm left with little that I could think would fix this, but I'm sure someone here could help me.

It is late now and I have school in the morning, so I'll check back on this thread in about 16 or so hours when I'm done with that. Then if anyone has a potential fix, I could try it. If I don't see a fix, I could post a video describing my problem or any more information you might find useful. Thank you all and goodnight.