HELP - "dm-verity verification failed..." recovery message and no cell service
Background Info:
Was rooted on OE2 via pingpongroot and supersu and froze some bloatware with Titanium Backup, nothing else done to the phone. Flashfire was on there but never used. Phone has worked fine this way for about 7 months.
This past Friday I suddenly lost all network connectivity and was very sporadic in connecting to the LTE network. Also lost ability to send text messages.
These are the steps I did:
1. Went to the ATT store, verified IMEI was ok, and got a new SIM card - nothing
2. Tried *#*#4636#*#* dialer code to see the network settings - nothing
3. *#0011# diagnostics dialer code - nothing
4. Tried different APN settings as well as APN reset - nothing
5. Factory reset - nothing (could not factory reset from UI, had to do it from recovery - "dm-verity verification failed..." message seen in recovery)
6. Removed pingpongroot app and uninstalled root via supersu, verified with rootchecker - nothing
7. Did another factory reset without root - nothing (could not factory reset from UI, had to do it from recovery - "dm-verity verification failed..." message seen in recovery)
8. Somehow the texting message center digit code was changed, so I did some googling and changed it back to +13123149810 from 313133127 - FIXED TEXT MESSAGING
9. Spent an hour with tech support verifying there were no network restrictions or limitations with my device - nothing
10. Attempted an OTA update on the phone - update failed (dm-verity verification failed.... message in recovery)
I didnt find too much on the dm-verity verification failed... message in recovery. It seems it has something to do with system files being modified, or something with the EFS. I cannot figure out what is going on with no network service, so an option is to either replace the phone under warranty from a service center, or to try and flash stock firmware via ODIN. Phone doesnt have knox tripped and says official under status, so I dont think I would have a problem replacing with them.
Questions:
1. Will "dm-verity verification failed..." cause issues with Odin and going back to stock recovery? Last thing I want is a brick when I could return it.
2. Can anyone think of anything else I could try in terms of trying to get my cell signal back? It connects to LTE in high populated places, but in places where it used to have fine reception (work, home) it gets nothings. This combined with the fact that my message center code was changed makes me think something deep in the network settings was also changed, but I have no idea where to look.
Thanks.
Do you still have frozen bloatware? You might want to try un freezing everything, and seeing if that helps. Perhaps you locked something up that's in need of an update / conflicting now.
AoN
anneoneamouse said:
Do you still have frozen bloatware? You might want to try un freezing everything, and seeing if that helps. Perhaps you locked something up that's in need of an update / conflicting now.
AoN
Click to expand...
Click to collapse
Everything should be unfrozen after I did the factory reset, as I saw all of the ATT bloatware pop up again.
I am receiving reception again!
1. Odin back to stock. In this case it was OE2
2. Factory reset - this removed the "dm-verity verification failed..." message in recovery
3. Took the OTA update to OI2 ROM version
4. Factory Reset
5. Took the OTA update to OJ7 ROM version
6. Now have reception again in areas where it suddenly dropped off.
I do notice that my IMEISV number changed between OTA updates, and there are some extra network options in the secret dialer code menu. Not sure if that had anything to do with it, or the fact that I did not take any OTA updates since receiving the phone 7 months ago.
Anyway, hope this helps some people who may have suddenly lost reception in places they used to have it.
orlandoxpolice said:
I am receiving reception again!
1. Odin back to stock. In this case it was OE2
2. Factory reset - this removed the "dm-verity verification failed..." message in recovery
3. Took the OTA update to OI2 ROM version
4. Factory Reset
5. Took the OTA update to OJ7 ROM version
6. Now have reception again in areas where it suddenly dropped off.
I do notice that my IMEISV number changed between OTA updates, and there are some extra network options in the secret dialer code menu. Not sure if that had anything to do with it, or the fact that I did not take any OTA updates since receiving the phone 7 months ago.
Anyway, hope this helps some people who may have suddenly lost reception in places they used to have it.
Click to expand...
Click to collapse
Sorry bro, as you installed the old program?
I believe it's because you are on Of4 firmware, but restored the oe2 files? To get back you need the flash the files in Odin from the muniz of4 update thread.
Nevermind, I see you updated already.
Related
Hello all,
please forgive me first of all because I've had very little sleep due to this issue. And its a long thread, but more detail is better generally I believe.
First, some background, and unfortunately, it starts with my wifes phone.
My wife has a Galaxy S GT-i9000 on Orange in the UK. She has had it, probably about a year maybe at most. She has a few apps that she has downloaded but nothing major and on first looks when I got it nothing I expect would cause this issue, just facebook etc.
My wife came home and said, my phone keeps coming up with a message saying force close. Ahh, I thought, some apps gone nuts, but alas, it appeared to be many apps including Maps, Google Upload (I assume this is a system process), Facebook Katana and many more, probably about 20 Force Close messages pop up one after the other and it lags whilst trying.
Odd, I thought, I also noticed the icon for one of the apps on her homescreen had changed to the default White and Green one with the android on it.
I suspected something had gone wrong (obviously), I asked if she had rebooted it and she said she had. So, I rebooted it again, just incase. Same problem.
I then thought it might need an update, it was running official Kies 2.3.3 (or was it 2.3.4, I forget) so I plugged it into my netbook and ran Kies, had to update that as it didn't have the latest application update. I then started the firmware update, after backing up the phone using Kies.
Halfway through the update, Kies popped up a message saying something went wrong and that I had to unplug the phone, take out the battery and reboot. Odd, I thought as the phone was telling me to not doing anything. I waited a minute, nothing further happened, so I did this. Then I got the Black Screen of Death with the phone, the dots and the computer screen.
Crap!!! I thought, I managed to get into Download mode, and reflash it using what I believe was an official ROM using Odin. I then rebooted, and found that it STILL had the data on it and it STILL was doing the force close. At least I had it back to "working" though so I was mildly happy.
I then did a factory reset using the menu system, erased the USB storage (there is no external SD card in her phone) and rebooted, still force closing but prompting me to setup again. Weird. I went through the setup slowly, as every second or so a force close would popup, then when I completed the setup (which still had the wifi settings, account settings etc in it) the System Setup crashed with Force Close. I then rebooted and got to the Home Screen, but still crashing.
I rebooted and used the recovery screen to clear the cache and factory reset, despite the warnings I will lose everything, nothing was wiped.
I tried to update using Kies again but it tells me that the firmware/device is not supported. I am now trying to see if I can use Odin to install a Kies supported firmware. So that I can then try an update using that again.
Anyone got any suggestions, at present, my thoughts are, I was going well within the realms of warranty up until I reflashed it using Odin to try and get back in as I'd only used Kies to update and the issue "just started happening" without my missus doing anything.
There are no signs of damage on the phone and she tells me it was just sat on her desk all day.
So, my question is, what now? I'm of the opinion based on the above that if I can't reflash a warranty supported Kies update, then maybe a custom ROM will be worth a shot to see if its a hardware failure or if its software. I just have never had an issue like this with my HTC Desire and I've ran many custom ROMs and standard ROMs on it.
I do have the .tmp file of the update Kies downloaded, and I also have a Binary folder which has some file inside a couple more folders but its not a .tar or a .zip because when I try renaming it (after a copy) it won't open.
So, suggestions on a postcard, thanks if you got this far through this nightmare. All help massively appreciated.
Edit: it appears to be the same issue as this: http://forum.xda-developers.com/showthread.php?t=822238
I'll try some of their suggestions. Today I also did the *2767*3855# today which I found after a bit more searching. Same problem after a reboot. Force close and data still there.
I've tried and tried again to do various solutions for this, I've even ran a logcat using adb to see if I can see the problem. I suspect its a Dalvik Cache issue in that its unable to write to it for some weird reason.
I've downgraded it to Froyo following this guide: http://forum.xda-developers.com/showthread.php?t=1100906
It now detects in Kies and offers me a firmware upgrade. I suspect it will die again though if I try due to this Dalvik problem.
Wiping cache does not wipe the cache. Everything still appears to be there on reboot as mentioned above.
Here is a copy of the LogCat with Java errors all over it: http://leenukes.co.uk/downloads/logcat1.txt (its quite long)
I guess nobody knows. Today I will speak to Orange to try and get it fixed or replaced.
Sent from my HTC Desire using Tapatalk
We've been told it is beyond repair. We will see what they say when we go back into the shop. Its still in warranty so I don't see why they won't replace it.
Sent from my Galaxy Nexus using Tapatalk
I have a friend with a Galaxy S from Orange Romania and suddenly the phone kept showing Force Close on every App. He had 2.2.1 if I remember right. He whent with the phone to an Orange Shop and they only do a factory reset but data was not wiped.
So what i have done for him:
- start the phone in Download Mode
- start Odin with repartition check and XXJVT (2.3.5) firmware with 3 files (code, phone and CSC) + pit file .512
- after reflashing the phone does have all tha data, so i resarted in Recovery Mode and done a Factory Reset and a Cache Wipe
- i flashed Speedmonde Kernel k16.10 and do again from Recovery Mode a Factory Reset, Cache Wipe and Davlick Wipe.
On reboot the phone was CLEAN. No force closes for a week now.
Sorry for my English hope it helps!
ZiDanRO said:
I have a friend with a Galaxy S from Orange Romania and suddenly the phone kept showing Force Close on every App. He had 2.2.1 if I remember right. He whent with the phone to an Orange Shop and they only do a factory reset but data was not wiped.
So what i have done for him:
- start the phone in Download Mode
- start Odin with repartition check and XXJVT (2.3.5) firmware with 3 files (code, phone and CSC) + pit file .512
- after reflashing the phone does have all tha data, so i resarted in Recovery Mode and done a Factory Reset and a Cache Wipe
- i flashed Speedmonde Kernel k16.10 and do again from Recovery Mode a Factory Reset, Cache Wipe and Davlick Wipe.
On reboot the phone was CLEAN. No force closes for a week now.
Sorry for my English hope it helps!
Click to expand...
Click to collapse
Sound advice there mate, other thing I would have done is in recovery mode before the ODIN flash I would have format sdcard, making sure you have removed BOTH the external sd and the sim card, as it can wipe them as well.Then flash through ODIN as per instructions above.
Using JVT I would flash either speedmod or semaphore 2.1.1 which I personally use.
Happy flashing!!
turns out it was water damage and some parts corroded.
Its going to be claimed for on insurance.
Sent from my Galaxy Nexus using Tapatalk
Hello all,
the phone came back from repair yesterday, yay!
the phone now however, doesn't appear to lock onto a mobile signal for very long. Boooo!!!
After sending off for repair using insurance, we got the phone back yesterday but it now appears to be broke in another way. It won't lock on to a mobile signal, wireless is fine but data network and sometimes just mobile signal is patchy and keeps dropping.
I've just reset it to factory defaults, same problem. What I did notice, which is odd is that since it came back from repair, its now unlocked and I can put another networks SIM card in it, same issue there too so I know its the phone now.
I'm going to scour the forums to see if anyone else had/has issues like this, it is running the latest firmware now and a full wipe really did fully wipe it this time, as opposed to last time with its issues due to water damage. One step forward, two steps back?
Its going back to the insurance company. Especially as Orange were suggesting that we pay £70 for a new handset.
Absolute fool I had on support today, yesterday I at least had someone sensible.
Sent from my Galaxy Nexus using Tapatalk
SGS force close problem
Hey guys i m facing a similar solution in my samsung galaxy s. After deleting all the contents and uninstalling the applications, I m getting them back after rebooting and all applications has to be force closed after rebooting.
Please help me to solve this problem
Signal issues
leenukes said:
Hello all,
the phone came back from repair yesterday, yay!
the phone now however, doesn't appear to lock onto a mobile signal for very long. Boooo!!!
After sending off for repair using insurance, we got the phone back yesterday but it now appears to be broke in another way. It won't lock on to a mobile signal, wireless is fine but data network and sometimes just mobile signal is patchy and keeps dropping.
I've just reset it to factory defaults, same problem. What I did notice, which is odd is that since it came back from repair, its now unlocked and I can put another networks SIM card in it, same issue there too so I know its the phone now.
I'm going to scour the forums to see if anyone else had/has issues like this, it is running the latest firmware now and a full wipe really did fully wipe it this time, as opposed to last time with its issues due to water damage. One step forward, two steps back?
Click to expand...
Click to collapse
Sounds like a modem issue, where the techs at Orange put in the wrong modem for your firmware. I did the same thing when I upgraded from Froyo to Gingerbread.
Alternately, it could be a broken external antenna connection as a result of the corrosion from the water damage. Google "no signal fix" and look for a site that ends in .uk
Just a thought for others who come across this problem.
I
Hi friends,
I have a T-599N from MetroPCS that I previously rooted using Cydia Impactor for Link2SD purposes. I unrooted upon not needing this option anymore, and have become extremely paranoid after seeing that my device status is still custom. Here's what I've tried so far:
-Factory data reset
-Cache wipe
-TriangleAway
-Removing the SD card/battery and rebooting
Now the good news:
-My counter never changed and is at 0 (was shocked to see this when I went to unroot and used TriangleAway the first time)
-My binary is still listed as Samsung Official. On that note, I never installed any custom firmware. So whenever I reset, I get Metro's original firmware - complete with the bloatware.
-I can't do a software update from the phone itself obviously, but when plugged in with Kies, it seemingly recognizes the firmware and tells me there's no update available.
So is there anyway to fix this, or am I just forever stuck with "Custom" status? I'm just paranoid because I already had to replace my phone once, and I'm not sure what Metro's policy is. I'm unrooted... but yeah. (I know; my dumb a** should've waited for my warranty to expire before rooting, but I really needed the space at the time )
Any help would be appreciated!
Here is my situation (this started a couple weeks ago and I am a little fuzzy with some exact details).
My phone was running a little slow, so I restarted it. After the phone rebooted, it no longer worked. I can't remember for certain if the error message "sim not allowed: mm#3" was showing at that time, but I do remember that not only was the phone not working, but the phone's imei had been replaced with a meid. I found this out when going into settings, then about device, and then into status. I don't remember when exactly the meid dissappeared and the phone started showing its imei again, but yes the imei has returned. Even though that issue cleared up, the phone still isn't right.
What's going on now.. Sometimes I get the error message "sim not allowed: mm#3" and sometimes I don't. When the message does show, maybe 50% of the time with a simple restart of the phone the message will go away and the phone will partially work (making calls/text but no data.. wifi works). The other 50% of the time I can typically get it to accept the sim by entering the code "*#*#4636#*#* and then changing the preferred network type (the same network type does not always work). When the phone will work (again, that's only partially working) it will now only use the edge:2 network type.
It goes without saying that everything I have done attempting to fix this issue has failed. I have us.d odin to reflash the firmware packs and even the modem file. The list of files I flashed are G900A_Downgrade_to_NCE.tar.md5, AP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5, CP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5
CSC_ATT_G900AATT1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5,
and these files did all flash successfully. I attempted to flash G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5 but the process failed. Unfortunately I don't remember the error message when it failed, but I will be happy to reflash it so I can get the error code for you.
I even went as far as flashing the ported tmobile rom and then flashing back to at&t, and yet again the problem was not fixed.
Just before starting this post I followed the steps listed in http://forum.xda-developers.com/galaxy-note-3/help/sim-allow-mm3-solution-t2921741 hoping this may work, and it doesn't appear to have made any difference.
fix for sim not allowed mm#3
rooted the phone, preformed a nv item rebuild and the issue seems to be fixed.... phone is running 4g currently. no repeat of the error code yet
My new P20 Pro (Canadian Telus) is having issues updating to CLT-L04 8.1.0.109(C792) from CLT-L04 8.1.0.107(C792).
The Problem is that the device simply will not update no matter the method.
My device is unrooted at this point.
What Happens.
When going through each of the scenarios,
1) The firmware is downloaded,
2) The phone then boots into firmware installation mode,
3) Firmware supposedly is updated
4) Phone Boots
5) Upon checking in phone status the phone is still on CLT-L04 8.1.0.107(C792)
Methods I have Used to Update
A) OTA Update (result: not updated)
B) Factory reset the device and then trying to OTA Update. (result: not updated)
C) Update via HiSuite (result: not updated)
At this point, I am unsure why this is happening and how I can update to the new firmware.
Any advice or guidance is greatly appreciated!
Did you factory reset? After the last attempt? Is your bootloader unlocked? Have you tried eRevovery?
I have the same issue: new P20 Pro from Koodo (single SIM version), out of the box it prompted me to update, after I did this, I had for example a corrupted Settings app (name was a mix of letters and numbers and same name corruption with Chinese characters within). After this happened I did a factory reset, was back on 107 and was prompted to update again in the morning, which I did. Same outcome as above, after apparently successful installation and restart, I was still on 107 ...
Just got off a chat with Huawei Canada and apparently technicians are aware of the issue and are working on a hot fix that should resolve the update issue.
ccwestcliff said:
I have the same issue: new P20 Pro from Koodo (single SIM version), out of the box it prompted me to update, after I did this, I had for example a corrupted Settings app (name was a mix of letters and numbers and same name corruption with Chinese characters within). After this happened I did a factory reset, was back on 107 and was prompted to update again in the morning, which I did. Same outcome as above, after apparently successful installation and restart, I was still on 107 ...
Click to expand...
Click to collapse
You issues are very similar to mine.
I also had a corrupted settings app as well (mix of letters and numbers with Chinese characters)
Still no fix for the 107 to 109 update to report on.
So I had a chat session with a rep on Huawei Canada's site, he mentioned that my phone was 'Not Ready' for the update and hence why it was not updating.
I opted into an email notification through the rep for when the update becomes available.
I would recommend anyone else with this issue to bring it up to Huawei Canada and opt into a notification when the issue is resolved.
aglbz said:
So I had a chat session with a rep on Huawei Canada's site, he mentioned that my phone was 'Not Ready' for the update and hence why it was not updating.
I opted into an email notification through the rep for when the update becomes available.
I would recommend anyone else with this issue to bring it up to Huawei Canada and opt into a notification when the issue is resolved.
Click to expand...
Click to collapse
Well, given the corrupted Settings app that I (and seemingly others) had, I would say that "not ready" is rep speak for "we screwed up, please wait until we fix it" ...
Was delighted to see that CLT-L04 8.1.0.111(C792) showed up as update on my phone this morning and I hit the install button right away. Sadly (and really really annoyingly) the behaviour is the same as with the 109 update: the update seems to work but after restart the Settings app is corrupted and system shows still to be on 107. Immediately after the restart I was told to update to 111 which I tried once more, only to got a "Update couldn't be installed" fail message.
I then downloaded 111 again, wiped the cache partition and tried another installation. This time, the installation happened a lot faster (given the amount of update data, unrealistically fast) and I got the Update success message again. However, upon restart, I was still on 107 - this is pathetic!
Just to add to this story, I had to send my phone in for repair and apparently (according to repair report) the mainboard was replaced?! I am on .111 now and sincerely hope that future updates will perform as intended ...
ccwestcliff said:
Just to add to this story, I had to send my phone in for repair and apparently (according to repair report) the mainboard was replaced?! I am on .111 now and sincerely hope that future updates will perform as intended ...
Click to expand...
Click to collapse
Why u had to send it to repair?? is it because of the 'Update' not really updating issue? If you got any further solution for this,please let me know. I am also having the same problem.
Has anyone had any success with updates yet? I am still stuck on 107 and it say 114 is ready but always goes back to 107. No updates have installed, had the Telus p20 pro since July .
I haven't had any success yet. This is my last phone from them
I received the OTA notification this afteroon for Aug. update for my AT&T Note 9. Everything was fine and normal until 'after reboot'. It looked like everything was fine, and the 'after reboot stuff' seemed to be nearly finished but an "Install Interrupted: the software could not be installed" message displayed in the place of the "success" message.
In all my years of OTAs, I think this may be my first failure. What is happening here?
(EDIT) I just manually checked and found the update, downloaded/installed/rebooted/errored again; same message.
Potentially Helpful info: I'm currently on the July 1 ETG1 - I ODIN'd the Xfinity ETG1 from Sammobile.
Any tips or advice are welcomed and appreciated. Hoping to avoid ODIN.
TeldenW said:
I received the OTA notification this afteroon for Aug. update for my AT&T Note 9. Everything was fine and normal until 'after reboot'. It looked like everything was fine, and the 'after reboot stuff' seemed to be nearly finished but an "Install Interrupted: the software could not be installed" message displayed in the place of the "success" message.
In all my years of OTAs, I think this may be my first failure. What is happening here?
(EDIT) I just manually checked and found the update, downloaded/installed/rebooted/errored again; same message.
Potentially Helpful info: I'm currently on the July 1 ETG1 - I ODIN'd the Xfinity ETG1 from Sammobile.
Any tips or advice are welcomed and appreciated. Hoping to avoid ODIN.
Click to expand...
Click to collapse
I did the same as you and the OTA worked. I can't remember where I found the files I used but it wasn't from sammobile if that could make any difference. I know the size of the file and time it took to install seemed really long for a small file.
I've finally made time to backup - Factory Reset - restore, and then I tried up OTA the Aug AT&T update. I got the same Install Interruption error message from the OP...
I've tried plugging my phone into my computer and forcing the install with SmartSwitch... SmartSwitch sees ETG1 (July) as 'most up to date', and won't let me try to update.
Anything else I could try?