Bell i9000m Users with SD Failure following JK4 - Galaxy S I9000 General
If you had an SD Failure following the JK4 update, please post extensive informations here, like:
1) Hard reset BEFORE (Yes/No)?
2) Hard reset AFTER (Yes/No)?
3) Wipe cache BEFORE (Yes/No)?
4) Wipe cache AFTER (Yes/No)?
5) How long did you last before having the SDCard Failure?
6) Did you ROOT the device BEFORE (Yes/No)?
7) Did you remove it before update?
8) Did you ROOT the device AFTER (Yes/No)?
9) Did you apply LagFix BEFORE (Yes, Wich one/No)?
10) Did you remove it befure update?
11) Did you apply LagFix AFTER (Yes, wich one/No)?
12) What is the manifactured date (Behind the battery)?
13) If you did not hard reset before, please post a list of apps installed.
UPDATE:
Spreadsheet was created here:
https://spreadsheets.google.com/ccc?key=tei8JqsvXKolFRuhsOLMEVw&hl=en#
Code:
Question Yes No Other Info
Hard reset Before 11 1
hard Reset After 10 2
Wipe Cache Before 7 4
Wipe Cache after 6 5
under a week Under 2 weeks 2 weeks and more
Time Before Issue 8 4
Root Before 7 7
Root After 5 7
Lagfix Before 5 7
LagFix after 12
10.08 or less 10.09 or more N/A
Manif. Date 8 4
Update from post 19
UPDATE:
Just checked out, I've been running JK4 pre-release since Dec. 2nd, so it's been 19 days so far. Build date is 10.09
my detailed problem here
http://forum.xda-developers.com/showpost.php?p=9958351&postcount=33
1) Y
2) Y
3) Y
4) Y
5) hmm... few hours less than 24 hrs
6) Y
7) N, because the new rom install wipes away the root
8) Y
9) N
10) Not Applicable due 9
11) N
12) it has nothing to do with the battery, but the phone was from the August 11th batch ( stamped on the original Box )
13) too many to list according to TitaniumBackup 365+ apps/games installed
I don't entirely trust this new thread. I think the OP is looking to blame the end-user for the problems with the Galaxy S. I hope I'm wrong about this.
The OP posted this in another thread:
"I know well enough how people tend to blame everything but themselves on many cases, and on many cases, the informations relevant to a case is withold from the users themselves...
My Theorie on the failure rate is basicaly this: Most users don't want to "lose their data" so they don't hardreset the thing and clean the caches up before and after a flash, making it more prone to issues (installing any os as an "upgrade" on top of another OS is always buggy at least). "
If it takes a hard reset before/after/whatever for the update to work right then the update process should do it.
I was actually surprised that the JK4 update didn't wipe everything, it came up with my home screens reset but all of my apps and data intact. The last update (JH2 I think) wiped everything. I was all backed up and ready for JK4 to do the same.
After some glitches in the few days following the update I did a reset/format myself. Things were working great for a few more days until I got the dreaded internal SD card failure last night. Blaming the users for this mess is preposterous.
1) Hard reset BEFORE : Yes
2) Hard reset AFTER : Yes
3) Wipe cache BEFORE : No
4) Wipe cache AFTER : No
5) How long did you last before having the SDCard Failure : 8 days
6) Did you ROOT the device BEFORE : No
7) Did you remove it befure update : doesn't apply
8) Did you ROOT the device AFTER : No
9) Did you apply LagFix BEFORE : No
10) Did you remove it befure update : doesn't apply
11) Did you apply LagFix AFTER : No
12) What is the manifactured date : don't know... phone's under repair
13) If you did not hard reset before, please post a list of apps installed : doesn't apply
1) Hard reset BEFORE (Yes/No)? Yes
2) Hard reset AFTER (Yes/No)? Yes
3) Wipe cache BEFORE (Yes/No)? No
4) Wipe cache AFTER (Yes/No)? No
5) How long did you last before having the SDCard Failure? 27 hours
6) Did you ROOT the device BEFORE (Yes/No)? Yes
7) Did you remove it befure update? No
8) Did you ROOT the device AFTER (Yes/No)? Yes
9) Did you apply LagFix BEFORE (Yes, Wich one/No)? Yes OCLF, removed it a few months earlier
10) Did you remove it befure update? Yes
11) Did you apply LagFix AFTER (Yes, wich one/No)? No
12) What is the manifactured date (Behind the battery)? 10.08
13) If you did not hard reset before, please post a list of apps installed. N/A
1) Hard reset BEFORE : Y
2) Hard reset AFTER : Y
3) Wipe cache BEFORE : Y
4) Wipe cache AFTER : Y
5) How long did you last before having the SDCard Failure?: Dec 10th - Dec 19th, 9 Days
6) Did you ROOT the device BEFORE : y
7) Did you remove it before update : Y
8) Did you ROOT the device AFTER : Y
9) Did you apply LagFix BEFORE : Y , RyanZAEXT2LagFix BETA 2-3
10) Did you remove it befure update : Y
11) Did you apply LagFix AFTER : N
12) What is the manifactured date (Behind the battery) : Sorry cant check as the phone is in for repair
13) If you did not hard reset before, please post a list of apps installed.
jpaik said:
I don't entirely trust this new thread. I think the OP is looking to blame the end-user for the problems with the Galaxy S. I hope I'm wrong about this.
The OP posted this in another thread:
"I know well enough how people tend to blame everything but themselves on many cases, and on many cases, the informations relevant to a case is withold from the users themselves...
My Theorie on the failure rate is basicaly this: Most users don't want to "lose their data" so they don't hardreset the thing and clean the caches up before and after a flash, making it more prone to issues (installing any os as an "upgrade" on top of another OS is always buggy at least). "
Click to expand...
Click to collapse
In my defense, I would say that I followed to the letter Bell instructions on how to update to 2.2. Nowhere does it states that a hardreset is necessary.
http://support.bell.ca/en-on/Mobili...amsung_smartphone_software_using_Samsung_Kies
If I would have rooted my phone and played with custom rom I would agree that it would have been entirely my fault however, my phone was running custom 2.1
1) N
2) N
3) N
4) Y
5) 1 week after the upgrade to 2.2.
6) N
7) N/A
8) N
9) N
10) N/A
11) N
12) (in repair at the moment)
13) Too many to list
1) Hard reset BEFORE (Yes/No)? Yes
2) Hard reset AFTER (Yes/No)? Yes
3) Wipe cache BEFORE (Yes/No)? Yes
4) Wipe cache AFTER (Yes/No)? Yes
5) How long did you last before having the SDCard Failure? 15 min as it happened downloading CoPilot Maps after JK4 install.
6) Did you ROOT the device BEFORE (Yes/No)? Yes
7) Did you remove it befure update? No as I did a format to factory default
8) Did you ROOT the device AFTER (Yes/No)? No as I didn't have the chance
9) Did you apply LagFix BEFORE (Yes, Wich one/No)? Yes Voddoo
10) Did you remove it before update? No see 7.
11) Did you apply LagFix AFTER (Yes, wich one/No)? No
12) What is the manifactured date (Behind the battery)? 10.08 but is on repair as of today.
13) If you did not hard reset before, please post a list of apps installed. N/A
Under the battery (you have to remove it first) , you have the date besides the last codebar. On mine it states 10.09
AllGamer said:
my detailed problem here
http://forum.xda-developers.com/showpost.php?p=9958351&postcount=33
1) Y
2) Y
3) Y
4) Y
5) hmm... few hours less than 24 hrs
6) Y
7) N, because the new rom install wipes away the root
8) Y
9) N
10) Not Applicable due 9
11) N
12) it has nothing to do with the battery, but the phone was from the August 11th batch ( stamped on the original Box )
13) too many to list according to TitaniumBackup 365+ apps/games installed
Click to expand...
Click to collapse
This is not about trust or blame, a theory is to be proven right or wrong. To prove or disprove a theory you must gather data.
jpaik said:
I don't entirely trust this new thread. I think the OP is looking to blame the end-user for the problems with the Galaxy S. I hope I'm wrong about this.
The OP posted this in another thread:
"I know well enough how people tend to blame everything but themselves on many cases, and on many cases, the informations relevant to a case is withold from the users themselves...
My Theorie on the failure rate is basicaly this: Most users don't want to "lose their data" so they don't hardreset the thing and clean the caches up before and after a flash, making it more prone to issues (installing any os as an "upgrade" on top of another OS is always buggy at least). "
Click to expand...
Click to collapse
This is not intended to blame or to wine, this is intended to find the reason why and advise the user and maybe provide the builder with something more than what is provided as of now.
My main theorie consist of either
-Build Date (issue got fixed after hardware revision) (so far, all I can see is the august built)
-Application installed after (wich caused corruption on the SD after it installs itslef, so it must be data needy)
-The way the user updates the thing. (this theory is already disproven AFAIK)
-Updating without HardReset (this theory is already disproven AFAIK)
-Updating without Cache cleaning (this theory is already disproven AFAIK)
1) Hard reset BEFORE (Yes/No)? Yes
2) Hard reset AFTER (Yes/No)? Yes
3) Wipe cache BEFORE (Yes/No)? Not sure
4) Wipe cache AFTER (Yes/No)? Not sure
5) How long did you last before having the SDCard Failure? About 1 week
6) Did you ROOT the device BEFORE (Yes/No)? Yes
7) Did you remove it before update? No
8) Did you ROOT the device AFTER (Yes/No)? No
9) Did you apply LagFix BEFORE (Yes, Wich one/No)? Yes
10) Did you remove it before update? Yes
11) Did you apply LagFix AFTER (Yes, wich one/No)? No
12) What is the manifactured date (Behind the battery)? 10.08
13) If you did not hard reset before, please post a list of apps installed.
Just some additional info.
After I got the phone (Aug 2010) I applied a lag fix (OCLF) and the phone stopped working about 2 weeks later. I did a hard reset and the phone worked. Since that hard reset I only rooted the phone (no lagfix however I did install OCLF just to root). Then I updated to JK4 (with Kies, official release). 1 week later many apps started to force close. Hard reset and it works again but it seems to be much more laggy than before the last hard reset.
EDIT: Now completely dead.
1) Hard reset BEFORE (Yes/No)? - Yes.
2) Hard reset AFTER (Yes/No)? - Yes.
3) Wipe cache BEFORE (Yes/No)? - Yes.
4) Wipe cache AFTER (Yes/No)? - Yes.
5) How long did you last before having the SDCard Failure? - 5 days.
6) Did you ROOT the device BEFORE (Yes/No)? - Never.
7) Did you remove it befure update? - N/A.
8) Did you ROOT the device AFTER (Yes/No)? - No.
9) Did you apply LagFix BEFORE (Yes, Wich one/No)? - Never.
10) Did you remove it befure update? - N/A.
11) Did you apply LagFix AFTER (Yes, wich one/No)? - No.
12) What is the manifactured date (Behind the battery)? - before Aug 1st since the phone is from the very first batch.
13) If you did not hard reset before, please post a list of apps installed. - N/A.
t1mman said:
Under the battery (you have to remove it first) , you have the date besides the last codebar. On mine it states 10.09
Click to expand...
Click to collapse
one says 10.07 (Jul 2010)
another says 10.08 (Aug 2010)
the ones that were already sent out for repair ... i wont know until they come back
and the one that just came in from the postal office is also from 10.07
1) Hard reset BEFORE (Yes/No)? Yes
2) Hard reset AFTER (Yes/No)? No
3) Wipe cache BEFORE (Yes/No)?No
4) Wipe cache AFTER (Yes/No)? No
5) How long did you last before having the SDCard Failure? 4 days
6) Did you ROOT the device BEFORE (Yes/No)? yes
7) Did you remove it befure update? yes
8) Did you ROOT the device AFTER (Yes/No)? no
9) Did you apply LagFix BEFORE (Yes, Wich one/No)? Yes
10) Did you remove it befure update? Yes
11) Did you apply LagFix AFTER (Yes, wich one/No)? No
12) What is the manifactured date (Behind the battery)? Its gone for repairs
13) If you did not hard reset before, please post a list of apps installed.
Angry birds, and thats it.
Original Poster,
Can you gather all the answers people replied and put up a a up to day total stat info in your first post?
Thanks.
I thnk using Google Docs Poll would have been easier.
1) Hard reset BEFORE (Yes/No)? Yes
2) Hard reset AFTER (Yes/No)? Yes
3) Wipe cache BEFORE (Yes/No)? Yes
4) Wipe cache AFTER (Yes/No)? Yes
5) How long did you last before having the SDCard Failure? 36 hours
6) Did you ROOT the device BEFORE (Yes/No)? No
7) Did you remove it befure update? N/A
8) Did you ROOT the device AFTER (Yes/No)? Yes
9) Did you apply LagFix BEFORE (Yes, Wich one/No)? No
10) Did you remove it befure update? N/A
11) Did you apply LagFix AFTER (Yes, wich one/No)? No
12) What is the manifactured date (Behind the battery)? Some time in July, first day phone
13) If you did not hard reset before, please post a list of apps installed. N/A
1) Hard reset BEFORE (Yes/No)? Yes
2) Hard reset AFTER (Yes/No)? Yes
3) Wipe cache BEFORE (Yes/No)? Yes
4) Wipe cache AFTER (Yes/No)? No
5) How long did you last before having the SDCard Failure? 10 days
6) Did you ROOT the device BEFORE (Yes/No)? Yes (temporary root only)
7) Did you remove it befure update? Yes
8) Did you ROOT the device AFTER (Yes/No)? Yes
9) Did you apply LagFix BEFORE (Yes, Wich one/No)? No
10) Did you remove it befure update? N/A
11) Did you apply LagFix AFTER (Yes, wich one/No)? No
12) What is the manifactured date (Behind the battery)? 10.08
13) If you did not hard reset before, please post a list of apps installed. N/A
t1mman said:
If you had an SD Failure following the JK4 update, please post extensive informations here, like:
1) Hard reset BEFORE (Yes/No)?
2) Hard reset AFTER (Yes/No)?
3) Wipe cache BEFORE (Yes/No)?
4) Wipe cache AFTER (Yes/No)?
5) How long did you last before having the SDCard Failure?
6) Did you ROOT the device BEFORE (Yes/No)?
7) Did you remove it befure update?
8) Did you ROOT the device AFTER (Yes/No)?
9) Did you apply LagFix BEFORE (Yes, Wich one/No)?
10) Did you remove it befure update?
11) Did you apply LagFix AFTER (Yes, wich one/No)?
12) What is the manifactured date (Behind the battery)?
13) If you did not hard reset before, please post a list of apps installed.
Click to expand...
Click to collapse
I am wondering why any of these steps matter? For 500 bucks the phone should work even if these steps are done or omitted.
1) Hard reset BEFORE Yes
2) Hard reset AFTER Yes
3) Wipe cache BEFORE Yes
4) Wipe cache AFTER Yes
5) How long did you last before having the SDCard Failure? 2 Weeks
6) Did you ROOT the device BEFORE No
8) Did you ROOT the device AFTER No
9) Did you apply LagFix BEFORE No
11) Did you apply LagFix AFTER No
12) What is the manifactured date July 2010
Other notes:
Froyo seemed to fix most lag but would get occasional serious hangups and force closes where the phone would become unresponsive for a bit and then vibrate several times coming out of it.
xxgg said:
Original Poster,
Can you gather all the answers people replied and put up a a up to day total stat info in your first post?
Thanks.
I thnk using Google Docs Poll would have been easier.
Click to expand...
Click to collapse
Will do, doing as of now!
From now, the constants are:
-the built date of August and before. I have yet to see one with Manif. date of 10.09
-Don't last longuer than 2 weeks (well... the update was available since 2 weeks...I can't remember when I did mine, but it's before the official release (I'll check my posts to see) and it still works
bartybet said:
I am wondering why any of these steps matter? For 500 bucks the phone should work even if these steps are done or omitted.
Click to expand...
Click to collapse
Please take a long and exhaustive note on this, because this thread is not about anything else than gathering data to try to get a constant from and for users, per instance; Manif. date 10.08 and less and won't last 2 weeks.
For any comments or what-not, please refer to another thread or contact samsung/bell
Related
KalimGinger - GPS problem
Hello, First of all, I'd like to thank Kalimucho a lot for his great work If you stop by Toulouse, FR, let me know, and let's have a beer I've got a problem with GPS on that Rom... I can't get a signal. GPS is activated, but does not seem to catch a satellite... I've already flash to Froyo roms, and have activated GPS on it (it works). But that does nothing on ginger... I can't flash a 1.6 rom, because of Clockworkmod recovery 3.0.0.5... (and some error about edify script...) So, how can I solve that problem? because everyone seems to have GPS working... Thanks in advance. And thanks again Kalim
share my experience 1. download Kalim's froyo to your sd card 2. go to recovery mode , backup the whole system 3. wipe all the user data, cache twice (ensure all deleted) 4. choose kailm's froyo and gapps to update your system , reboot it 5. enable GPS in kailm's froyo (test the GPS now), if ok, not disable it, reboot to recocvery mode. 6. wipe all the user data, cache twice (ensure all deleted) 7.choose kailm's gingerbread and gapps to update your system, reboot it. 8. test the GPS now. 9. if everything ok. reboot it to recovery mode and then choose advance restore to restore the "user data" (don't restore cache, boot and system). This is working for me. Sorry for my English.
As eim2148 says, GPS must be activated when you flash to the Gingerbread ROM.
Yes, you're right, but I thought I had done that when flashing back to froyo and then ginger again... I'll follow eim21048's instructions, and I hope it works.
eim21048, I followed every exact step of your instructions, and it seems to work. I think I made a mistake before. Thanks a lot
Thank you eim21048 for the tutorial. It worked fine for me.
[Q] Bought a used dexter modded Elocity A7 and having issues
I am pretty tech savy with Windows but this is my first Android device. My device states: Model number: A7-040 Firmware version: 2.2 Kernel version: 2.6.32.9 [email protected]#1 Serial number: 2638016300029 Build number: Dexter's ElocityA7 Mod v1.42 EC version: 0.14 1st issue: Cannot read my 8Gb Centon Pro USB thumb drive (could be because it's formatted using exFat instead of FAT32) Status of thumb drive remains "checking for errors" underneath "Preparing external storage" 2nd issue: Superuser app has been installed and every once in a while pops up and states that some unknown app is asking for some kind of permission 3rd issue: Factory restore (settings>privacy>Factory data reset) does not seem to reset anything (downloaded apps, wifi keys and ssids, desktop shortcuts all remain afterward) 4th issue: System update does not seem to work (states that "update.zip" is missing). And why does the kernal version have what seems to be someone's email address on it? I need to know if the info in "About device" seems right or if I need patches or additional mods or updates. Or maybe I need to know how to reset this thing to complete factory settings (factory ROM).
1. To read exFAT kernel must have library supporting exFAT. Have to advice - format your USB thumb drive to FAT 4. System updates do not work at custom ROM, may be Dexter turned it off to prevent erasing all custom modifications.
2. kinda scary if an app you can't identify is getting su permissions. 3. Maybe related to 5[Strogino]'s answer for #4 The random su access woul scare the crap out of me, I'd download a new rom and start from scratch. For the factory reset and updates, I have always taken care of those tasks in recovery, never from inside the rom.
Thanks to both of you for your replies. I appreciate your time. So I guess exFat is not supported. I'll try and figure out the rest for myself.
1. android has no exFAT support, even if i included it with the custom kernel. 2. alway just re-install a clean 1.42 mod and do a factory reset in recovery menu, then you are 100% its safe. 3. custom rom issue, never gonna work. 4. same as 3. and with a customer kernel the compiled date + hostname + user will always be embedded according to custom kernel and linux revision standard in the linux code. you cannot get around that, except if you remove it the code. factory reset (press POWER ON for 1sec and release, again press and HOLD POWER until screen says loading recovery, you will see info on screen saying hold 5 seconds to boot recovery) press "HOME" to see menu in recovery otherwise you just see "!" sign.
[Q] HTC HD2 resets on its own
I've been having this problem with the ROM I want to use, hoping someone can help. I always perform a fresh wipe on the phone using Wipe (Task29), erasing everything using the HD2 Toolkit. In order, I always: -Reinstall the Radio_Leo_2.15.50.14 -Reinstall MAGLDR 1.13 -Repartition to 285MB and the cache size to 2MB -Install NexusHD2-JellyBean-CM10 V1.3a (Unable to provide link) After a week or two, the phone will randomly reset itself and go back to the installation screen, doing so every time I choose to manually reset or if I turn off the power. I've lost more than enough important data because of this and I'm not really sure what I'm doing wrong, I had reset problems whenever I ran MIUI before, but it was never this bad. Any help would be appreciated.
Root went wrong and restoring original firmware made no difference.
Hi everyone, just tried to root my i9507 S4 for the first time. Went really awful. I used the Chainfire Auto Root from his website for Android Lollipop (this one to be precise) and attempted to get it up and running through the included Samsung Odin. It booted in successfully and I could reach the home screen. I had SuperSU and could open it - but I think something stopped working along the way and everything crashed at once after just a few moments (whether I opened SuperSU or not). Google Play didn't open. I attempted to do a full-install from SuperSU, which got rid of SuperSU but the problems remained, awesome. Rebooting now changed nothing. So I went to Sammobile and downloaded the correct firmware (this one), and I attempted to restore with Odin using the same method as I did rooting. Everything seemed to be going to plan with Android "updating" and the like, and SuperSU is still gone, but the same problem remains. As expected all of my data remained. I'm tempted to do a full-reset at this point but I'd like you guys' opinion first. I'm new to all this - as you have probably guessed! - so please be nice-ish (I deserve some of the flack I'm sure). Thanks guys
Just attempted clearing cache thru recovery (stock) - no changes.
Full wipe then install firmware with Odin.
Through recovery I presume?
Do this: open Odin, uncheck everything except f reset time. Flash ROM. When you see the word reset in the Odin status window, remove USB cable from the phone, remove battery, replace battery, boot into stock recovery, perform a data/factory reset, reboot. This method will wipe all of your data.
audit13 said: When you see the word reset in the Odin status window, remove USB cable from the phone... Click to expand... Click to collapse Would this not brick the device? Thanks though.
You only see the word reset if the firmware was flashed. I do this for the note 1, note 2, note 3, s2, s3, and s4.
Verification Failed, Unable to restart your device.
This dreadful error: "Verification Failed, Unable to restart your device. The Integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data." And a "Reset" button. Nothing seems to have caused this. One minute phone was sitting on my desk happily, the next it rebooted itself (I assume) and this error appeared. Given that I'm not interested in losing my data I haven't pressed the factory reset button... because that's just silly. - Phone is S5 Neo (W version). Rooted (CF-autoroot) with TWRP installed. Has been this way for months. - Software updates are turned off - ADB is disabled but I can access terminal using TWRP. - Data partition is encrypted What I've done so far: - Backed up my Data partition using DD; but as it's encrypted I can't access the data - Attempted terminal "twrp decrypt mypassword" using the password I used to unlock encryption at boot (result: "Failed to decrypt data") What do I do now? Is there any way to decrypt this partition on my PC (I have linux and windows available to me) to at least rescue my data? Thanks in advance...
I just had the same thing happen to me with the exact same model with the exact same settings as well today about a couple hours ago EXCEPT I never rooted the phone like yourself. So it isn't developer mode or anything like that. That can be ruled out. It's such f**king BS! I heard rumors about nonsense like this years ago and the only way to supposedly fix the problem is to send the phone into samsung where they fiddle with the phone, never fix it, keep it (for whatever reason ??), and send a new phone back out IF we fall into warranty. With all the corruption in the world and the shady happenings with government and businesses, why in the hell would any logical person send their phone back in to an OEM after it's been used? I'm a good person and come from a good family and all that, but ever since I had my information stolen from me a little over 5 years ago I really don't want to send my phone in and have my life in shambles again. No damn chance! I'm thinking about calling in but I want all my info! I have important work related documents on here! Only thing I am going to ask you is what software did you use to back it up (DD?)
Do these exact steps, Do not miss. 1. Reboot to recovery. 2. Do a data wipe (WIPE>FORMAT DATA) And Say "Yes" 3.Go to Reboot and Reboot back to recovery. 4.Download DM Verify Disabler https://build.nethunter.com/android-tools/no-verity-opt-encrypt/, Get the latest. 5.Copy in to the phone and flash it. 6.Go to Reboot and Reboot back to recovery. 7.Now Flash any rom as you wish. 8.Make Sure to Wipe Dalvik, Cache after. Enjoy!!
Shameera_N said: Do these exact steps, Do not miss. 1. Reboot to recovery. 2. Do a data wipe (WIPE>FORMAT DATA) And Say "Yes" 3.Go to Reboot and Reboot back to recovery. 4.Download DM Verify Disabler, Get the latest. 5.Copy in to the phone and flash it. 6.Go to Reboot and Reboot back to recovery. 7.Now Flash any rom as you wish. 8.Make Sure to Wipe Dalvik, Cache after. Enjoy!! Click to expand... Click to collapse Shameera_N you sound pretty smart....but why didn't you read the comments we posted and actually try and answer what we asked? WE DO NOT WANT TO WIPE OUR DATA and there is no way that wiping is part of the solution.
For this do we need a rooted phone?
This happened to me on a completely stock SM-G903F with data encryption enabled. So it has nothing to do with custom recoveries or root. It seems that the encryption method is flawed. I don't think there is a way to get out of this one, so I wiped it. I don't have all that much stuff on the internal SD of my phone except for apps and messages. Your SD card won't get formatted, so if you save your photos there, they should be safe. It's a pain, but this means you can't really safely use data encryption unless you regularly take backups (and even then, factory resetting a phone is no fun), even if errors like this only happen once in a blue moon.
This happend to me on my SM-G920P. I just odin flashed stock rom and back to new no data wipe or loss.
Same problem with a samsung galaxy s5 neo. Envrypted partition, Stock firmware, no root and updated. At least i understood what caused it. I was listening to a youtube video. While the video was playing, i pressed the power button and switched off. When i switched on, i could not start android anymore
Shameera_N said: Do these exact steps, Do not miss. 1. Reboot to recovery. 2. Do a data wipe (WIPE>FORMAT DATA) And Say "Yes" 3.Go to Reboot and Reboot back to recovery. 4.Download DM Verify Disabler https://build.nethunter.com/android-tools/no-verity-opt-encrypt/, Get the latest. 5.Copy in to the phone and flash it. 6.Go to Reboot and Reboot back to recovery. 7.Now Flash any rom as you wish. 8.Make Sure to Wipe Dalvik, Cache after. Enjoy!! Click to expand... Click to collapse Thanks for the link, do you know who built this? Need update for 7.0...
githyanki said: Thanks for the link, do you know who built this? Need update for 7.0... Click to expand... Click to collapse You can use same for 7.x.x Use latest version from the link
I know this isn't exactly related to the issue in this thread, but I'm not having much luck elsewhere. My completely stock J3 (2017 model, J327A) was hit with verification failed. From what I've seen, I can fix my issue merely by flashing the original OS back into my phone. I have the files and programs I need to do this. But I can't get the phone into download mode. I can boot it up to the warning screen. It tells me to press VolUp to enter download mode, or VolDn to cancel and restart the phone. However, neither pressing nor holding either of them does anything. I know they aren't broken, as I can boot into recovery mode as well, which requires VolUp. The buttons just don't respond when I'm at the warning screen. Is this something I can work around, or something I have to be patient with, or something I can't fix? (Data partition is encrypted, though. Not sure if that will affect this.)
Simply long press the Shut Down Button !!!!!!!! I simply pressed the shut down button and restarted my phone and it worked !!!!!
A light at the end of the factory reset error tunnel! Well I had an encounter with that dreaded 'factory reset losing all data' message and I'm telling you I was furious! Anyways, after a few seconds of gasping and wondering how the heck am I gonna retrieve all of my data and stuff, the thought came to me to try some 'old school tactics' which involved removing the battery and pressing the power button to drain any residual power remaining on the phone's circuit board and then try powering up after reinserting the battery. Low and behold, the phone booted up with no issues at all. I was able to log in and access my phone as if nothing happened. It's funny how that one message can just change your whole outlook on things. I just hope that folks out there will try this and perhaps it will work for them instead of losing all their data and jumping through all sorts of hoops. Most importantly, BACK THAT THING UP!! You never know what next will come out of the woods at any given time!
Resolved error without loss of data Hi, I came across this problem today as soon as I woke up today, but was able to solve it. I have a Samsung J5 prime phone and did the following steps: Why this occurs? The system thinks you wish to root your phone. How to solve this? 1) when you have the verification failed screen, press "power" button + "Home" button + "Volume Down" button. you'll be presented with a new screen which gives you 2 options-first, installing a custom OS and second, canceling it. NOTE: I did not want to root my phone. 2) Hence, I chose the 2nd option and after that, my phone restarted with no loss of data. Hope this helps!
if u can boot into recovery, go ahead and wipe cache/dalvik cache and reboot this worked for me without any loss (i used twrp recovery to wipe and my device is SM_C900F /INS variant)
zay2046 said: This happend to me on my SM-G920P. I just odin flashed stock rom and back to new no data wipe or loss. Click to expand... Click to collapse Sir, can you guide me a bit further ? it just happened with my J7 prime and i don't want to loose data.
Same Problemo I Jst Had The Same Issue, Bit I Fixed It Straight Away, Jst By Restarting It, Hold Both "Up & Down Volume", "Power Button" and "Home Button", And It Restarted & Worked
This works! This worked with my daughters J7. THANK YOU! udit_e said: Hi, I came across this problem today as soon as I woke up today, but was able to solve it. I have a Samsung J5 prime phone and did the following steps: Why this occurs? The system thinks you wish to root your phone. How to solve this? 1) when you have the verification failed screen, press "power" button + "Home" button + "Volume Down" button. you'll be presented with a new screen which gives you 2 options-first, installing a custom OS and second, canceling it. NOTE: I did not want to root my phone. 2) Hence, I chose the 2nd option and after that, my phone restarted with no loss of data. Hope this helps! Click to expand... Click to collapse
Shameera_N said: Do these exact steps, Do not miss. 1. Reboot to recovery. 2. Do a data wipe (WIPE>FORMAT DATA) And Say "Yes" 3.Go to Reboot and Reboot back to recovery. 4.Download DM Verify Disabler https://build.nethunter.com/android-tools/no-verity-opt-encrypt/, Get the latest. 5.Copy in to the phone and flash it. 6.Go to Reboot and Reboot back to recovery. 7.Now Flash any rom as you wish. 8.Make Sure to Wipe Dalvik, Cache after. Enjoy!! Click to expand... Click to collapse Came here to thank you with all my heart, this worked. I've been using TWRP for years on several phones, and I never knew that Wipe > Format Data did something different than Wipe > Advenced Wipe > Selecting Data > Swiping. I thought it served the same purpose. I don't know if the script did anything, though (because I used it before, but without formating data, and it didn't help at all). Anyway, thank you so much!
how to remove Verification Failed or root in the TWRP file manager without losing data