Need help dm-verity error. SM-N920W8 PCT - Galaxy Note5 Q&A, Help & Troubleshooting

Hi everyone, I'm having a problem with my N920W8 which was running 7.0
My phone worked fine but i wanted to freshly install the ROM from stock so i downloaded the official ROM from my carrier Android 7.0
Before i did that i Backed Up everything from my phone to my usb using TWRP. EFS, data, system, etc...
After doing so I deleted everything; Internal Storage, System, data, cache, dalvik cache through TWRP and then went to ODIN and flashed the stock ROM but when i did that it gave me an error. DM-VERITY. So i downloaded another stock ROM but this time from another carrier that had a more up to date version. I installed it and still gives me the error. After that i downloaded another stock ROM with android version 6.0 from my carrier and it gave me an error when flashing through ODIN. I dont know to do at this moment but cry at the corner with a cold brick glass
I don't know if its possible but can I Install TWRP while having this error? Does flashing it make completely brick my phone?
Any answers will be helpful since this is my main phone and I'm a college student with little to no money to buy another phone :crying: :fingers-crossed:
Phone model N920W8 PCT
Has installed N920W8VLS5CRB1 Android version 7.0

Related

I9305t 4.3 wont boot

HI all,
Today I decide to update my i9305t to the 4.3 rom. I unrooted my phone and reset the custom counter and all was good. I flashed the telstra rom and all was good. Because of the locked dock Icons I thought I would flash a different unbranded rom. During the installation (via odin) it went skew if and froze. It sat there for ages but I ended up having to do a battery pull.
When I went to the download menu on the phone, knox had been tripped and there was 47 instances. Any way I reflashed the telstra firmware. It passed but now the phone gets stuck on the Samsung logo.
OK now I have already.....
Pulled the battery.
Removed all cards sim and sd.
Restored different firmwares.
factory reset, clear cahce etc.
Installed custom recovery and cleared devalk cache.
Googled for similar events.
Nothing I have read has worked.
I cant think of what else to do. When I restore a firmware via odin everything is OK, it passes but on the reboot it just stops at Samsung logo and goes no further.
I gather that because the phone can still get into recovery and download mode there must be something can sort this out.
Thanks in advance.
flash the original firmware from samsung.....the 4.3 since you updated it...
after it finishes and reboots it will enter a boot loop....IT'S NORMAL.....pull out the battery and start the phone in recovery mode(stock one) and do a wipe data - factory reset and wipe cache partition...it should work without a problem...did this many times...
after you updated to 4.3 you should have done a full wipe...
spiderman07 said:
flash the original firmware from samsung.....the 4.3 since you updated it...
after it finishes and reboots it will enter a boot loop....IT'S NORMAL.....pull out the battery and start the phone in recovery mode(stock one) and do a wipe data - factory reset and wipe cache partition...it should work without a problem...did this many times...
after you updated to 4.3 you should have done a full wipe...
Click to expand...
Click to collapse
Yeah I have done that. I have tried it about 10 times. Im going to give it another bash today as I am stuck using my wife's old Iphone and its horrendous.
try installing your firmware with a .PIT file and check repartition box...search for the pit file....
if this doesn't work i suggest going to local repair shop and let them have a look...
maybe something got broke when you flashed the unbranded firmware...
spiderman07 said:
try installing your firmware with a .PIT file and check repartition box...search for the pit file....
if this doesn't work i suggest going to local repair shop and let them have a look...
maybe something got broke when you flashed the unbranded firmware...
Click to expand...
Click to collapse
Thanks for the info. Im unsure what a PIT file is. Are they phone specific or just model specific.
Cheers
Pat
Filipiak said:
Thanks for the info. Im unsure what a PIT file is. Are they phone specific or just model specific.
Cheers
Pat
Click to expand...
Click to collapse
Found the pit file and read up on it. Tried to use it but it fails as soon as it starts.
Best of luck
Well I was in the same pickle
whicever 4.3 rom i flashed through odin i got stuck in boot logo or even if i recovered device from odin through emergency frimware and intillation
Also tried customs 4.3 roms stuck a boot logo
Here what u should try and what i did
1 flash philz recovery + 4.1.2 rom
if it works back up efs
2 Using Philz recovery wipe data factory reset + wipe cache + dalvik cache
3 in mount and storage section format everything ( THINK THIS IS THE MOST IMPORTANT STEP )
4 Used odin to flash a 4.3 stock package it worked ( note u may get knox from this u may try a modifed stock package if u dont have knox and dont want to get it )
AMoizK said:
Well I was in the same pickle
whicever 4.3 rom i flashed through odin i got stuck in boot logo or even if i recovered device from odin through emergency frimware and intillation
Also tried customs 4.3 roms stuck a boot logo
Here what u should try and what i did
1 flash philz recovery + 4.1.2 rom
if it works back up efs
2 Using Philz recovery wipe data factory reset + wipe cache + dalvik cache
3 in mount and storage section format everything ( THINK THIS IS THE MOST IMPORTANT STEP )
4 Used odin to flash a 4.3 stock package it worked ( note u may get knox from this u may try a modifed stock package if u dont have knox and dont want to get it )
Click to expand...
Click to collapse
Knox was tripped when the firmware install crashed. So knox tripping is no issue. Thanks for the information. I will have a go tommorrow.
I did manage to restore a cm9 backup but my IMEI is now gone and I cant get to the menu to restore my back up. Seems like Samsung has done a number on my phone. In all the years ive been fingering phones with custom firmware and modding I have never had anything stuff up this bad. Its rather amusing that it has happened flashing a stock rom that belongs to my phone.
AMoizK said:
Well I was in the same pickle
whicever 4.3 rom i flashed through odin i got stuck in boot logo or even if i recovered device from odin through emergency frimware and intillation
Also tried customs 4.3 roms stuck a boot logo
Here what u should try and what i did
1 flash philz recovery + 4.1.2 rom
if it works back up efs
2 Using Philz recovery wipe data factory reset + wipe cache + dalvik cache
3 in mount and storage section format everything ( THINK THIS IS THE MOST IMPORTANT STEP )
4 Used odin to flash a 4.3 stock package it worked ( note u may get knox from this u may try a modifed stock package if u dont have knox and dont want to get it )
Click to expand...
Click to collapse
AMoizK you are the ****en man. Worked. The part that worked for me was the format everything. IMEI restored as well. Phone is perfect. Now i dont need to use my wifes crappy old iphone.
WOOT!!!!
Filipiak said:
AMoizK you are the ****en man. Worked. The part that worked for me was the format everything. IMEI restored as well. Phone is perfect. Now i dont need to use my wifes crappy old iphone.
WOOT!!!!
Click to expand...
Click to collapse
Cheers
Filipiak said:
HI all,
Today I decide to update my i9305t to the 4.3 rom. I unrooted my phone and reset the custom counter and all was good. I flashed the telstra rom and all was good. Because of the locked dock Icons I thought I would flash a different unbranded rom. During the installation (via odin) it went skew if and froze. It sat there for ages but I ended up having to do a battery pull.
When I went to the download menu on the phone, knox had been tripped and there was 47 instances. Any way I reflashed the telstra firmware. It passed but now the phone gets stuck on the Samsung logo.
OK now I have already.....
Pulled the battery.
Removed all cards sim and sd.
Restored different firmwares.
factory reset, clear cahce etc.
Installed custom recovery and cleared devalk cache.
Googled for similar events.
Nothing I have read has worked.
I cant think of what else to do. When I restore a firmware via odin everything is OK, it passes but on the reboot it just stops at Samsung logo and goes no further.
I gather that because the phone can still get into recovery and download mode there must be something can sort this out.
Thanks in advance.
Click to expand...
Click to collapse
It happened to me once, i found that 4.3 won't boot if baseband and imei are unknown. when you were trying to flash with odin and your phone got stuck it probably has damaged or ( erased ) your imei partition. try flashing 4.1.1 ( the package file without bootloader files ) it will definitely work for you. the reason is simple , Samsung's stock 4.3 never boots if the imei is corrupt or unknown (baseband is then usually too ) so, flash 4.1.1 , root your phone and install Persus kernel +any modem / baseband file, this is the only solution as i dont know how but does repair your imei , but you will be stuck at 4.1.1.

[Q] Help needed for GT-I9295

Hello, i've updated my i9295 to 4.4.2 using the official stock rom for netherlands with odin. (sammobile.com/firmwares/3/?download=30085)
Model: GT-I9295
Model name: GALAXY S4 Active
Country: Netherlands
PDA: I9295XXUCNE5
The phone started after flash and worked very well, but then after a shutdown, it doesn't work telling me that system process is shutdown, after some seconds it reboots and keep on samsung logo..i've tried to wipe cache etc on recovery, but it works only one time, after one boot and shutdown it does the same. I can't understand why this firmware is not working
The CSC of my phone is different from the one i updated from, and i can't be able to downgrade back to 4.2.2 because of knox restriction..
what can i do to restore a working firmware?
does this unworking depends from CSC Code that needs to be changed?
I've seen that also the PDA code of the firmware is different from the original phone one (I9295XXUBMK3)
If i wait for 4.4.2 firmware with the same PDA, will it be working again? Or there is something else i can do?
waiting for an answer,
Thanks
no one can tell me something about this problem?
Hi
Normally CSC don't make troubles.
I advise you to first perform a full wipe in recovery, if this not solve your problem or you want to disable knox, flash super su in CWM.
When you'll launch supersu, it will ask you if you want to disable knox.
thanks for reply,
the recovery full wipe and format for data doesn't help,
but how can i flash super su in CWM? root is needed to use supersu,
Anyway i think i cannot downgrade cause 4.4.2 to 4.2.2, because bootloader block downgrade, or if i disable knox i can downgrade?
If you root your present rom you'll be able to de-knox.
Step by step.
1-install ClockWorkMod trough odin
2-Download supersu.zip, place in your phone memory and in CWM go to "install zip" and install supersu
3-reboot and open your brand new app "supersu", it will say you knox was detected and ask if you want to disable.
4-Your phone is rooted and de-knoxed
You can find all these tools in this forum but here they are.
Unzip CWM and flash
don't modify supersu and place it to the root of your phone's internal memory
thank you, i was able to do this procedure, getting root and deknoxing using supersu tool,
but i was not able to reistall 4.2.2 firmware cause bootloader still block my attempt when i try to replace the bootloader with the old one
My problem is that i cannot run 4.4.2 cause after 1 boot and 1 shutdown of the device, it doesn't boot anymore, getting stuck on Samsung logo.
I have to wipe data and cache every time i want to run..and so I cannot use the phone
I would like to find a way to return to 4.2.2 stock, or to get this 4.4.2 working more then 1 time after device restart
Is this possible in some way?
Just to remember, i used a firmware with different PDA code from the official of my phone, could it be the cause of the samsung logo after 1 boot?
Thanks
mmmmh pretty strange, look like your bootloader is locked like I537.
The CSC do nothing normally, my phone come with a non european CSC and I flash a nordic rom in france.
Did you perform a wipe of dalvik cache (in CWM "advanced" "wipe dalvik") plus the other wipes.
To make a good one, you have to wipe 3 things and the cache is not the most important.
The files build.prop stay in dalvik cache (if my memory's good) and load the new version only when wipe dalvik.
The build.prop is a kind of ID card (maybe the source of your trouble).
It doesn't helped, i wiped dalvik but the dalvik folders seems to be not present as i can saw in the logs of recovery...
But when you flashed your firmware, you used the same PDA or different? Have you ever used a different PDA?
To be precise, the second time i try to boot after shutdown it teels me that system process has crashed, the phone do not respond on touch, and then it reboots automatically and get stuck on samsung logo on next boots
I don't know what could be the cause of this, are present log files to investigate what fails in the boot of the system?
The only thing i have doubt is about PDA code of the firmware
i have the same problem
hi. i have the same problem with my s4 active i9295. region TTT
Phone: Samsung S4 Active
Model: GT-I9295 (unlocked)
OS: Android 4.2.2 (J.B.)
AP: I9295VJUBMK4
CP: I9295VJUBMK4
CSC: I9295UUBBMK1
Build #: JDQ39.I9295VJUBMK4
Kernel: 3.4.0-2045428
[email protected] #1
Tues Nov 19 20:37:24 KST 2013
i am now on a boot lop and cannot install back 4.2.2. what is the ideal rom that is compatible with my phone region???
thanks in advance

[Q] Lollipop on Samsung Galaxy GT-S6012

Please help me in Installing Android 5.0 Lollipop on Samsung Galaxy GT-S6012.
Any other latest working Version of Android that i can install ??
Am willing to root my phone.
Please help.
And thanks a ton for your help !!!
sunnynanade said:
Please help me in Installing Android 5.0 Lollipop on Samsung Galaxy GT-S6012.
Any other latest working Version of Android that i can install ??
Am willing to root my phone.
Please help.
And thanks a ton for your help !!!
Click to expand...
Click to collapse
Hello. I'm sorry but actually there's no lollipop for our device, however there is cm 11 with kitkat 4.4.4 but it isn't 100% stable. There's also cm 10.1, the android version maybe be a little old but it's more stable.
To flash this roms, you need this CWM
And for rooting, I think the easiest way is using Cydia Impactor
Boot loop..
Hi. I got a Samsung GT-S6012 that keeps rebooting the Samsung logo and doesn't start. At first I got the phone stuck on the very first logo with Samsung model name. So I did some search. Downloaded Odin and latest 4.1.2 official firmware for that phone model flashed it. Everything worked for a few days but then the battery ran out and phone shut down and when I turned it on again it got stuck on the very first logo and nothing. Then I flashed the same firmware again to get it running and when I checked it the flashing didn't really fully wiped the internal memory cause the data in it was still in tact. So I thought I need full wipe to fix the phone. So installed custom recovery, rooted it and flashed CM 10.1 on it. It was running very smooth everything seemed okay but I wanted the stock rom. So I went to recovery wiped whatever was possible and flashed the stock firmware in download mode again. And now I got stuck on the second Samsung logo and it keeps rebooting it self. I recognize that I cannot wipe data/factory reset and wipe cache in now stock recovery cause it gives me android logo within it a red flag. The wipe cache supposed to fix boot loop problem but it's not an option for me anymore. All I can do now is just enter Download mode. I'm downloading 4.0.4 firmware and gonna try to flash that one see if it works but I doubt. Can anyone suggest me a way to fix it? Please I'm really desperate.

S3 mini locked in startup screen

Hello, I have a problem with my phone and I need some help.
I tried to install Kit Kat 4.4.4 using recovery mode (CWM), the install process ran smoothly but it had some issues so I tried to install Lollipop 5.1.1 (CyanogenMod 12.1) 20150412 stable from novafusion using TWRP (v.2.8.1.0) but apparently I made some mistakes, I used the Advanced Wipe tool and deleted (Dalvik cache, System, cache, data, internal storage) after this I can not install any moded ROM.
The phone stays on the "Samsung Galaxy s3 mini" screen.
Can somebody help?
My phone model is GT-i8190L
looks like you need to head over to http://http://www.sammobile.com/firmwares/, login & d/l original firmware for ur fone & region, then flash via odin, & start root,custom flash again.............carefully this time & be sure to make full nandroid backup before flashing so you can restore if problems occur......good luck & post again if you need more help
beerwolf-crowe said:
...
Click to expand...
Click to collapse
Friend but as I do if odin does not recognize my device?
Now install the drivers and still recognize it.

A cry for help

Hello all,
Firstly I would like to thank all the great people here, I've been struggling for hours with my dead Xperia Z and the amount of dedication and support I've found so far across all the members here is really impressing.
Let me first illustrate my case.
Firstly, I came here to root my phone and install a custom rom ships with Android N 7.1.2 (Resurrection Remix), I did went through all the newbies/how to threads and I did successfully ended up with Android N on my phone
Unfortunately, the device was not working probably in case of incoming or outgoing calls. No ringtone (already selected from Settings >Sound - played and heared), while in call it keeps ending the call unexpectedly, sometimes it feels very laggy that I couldn't even tap on anything. So I decided to give up until I found another rom that ships with Android N (XOSP), after successfully installing the rom, it starts out very smooth and I tested everything and it was ok, until yesterday the same issue still persists plus my device mic is not working no one can hear me while I'm talking neither from a headset mic nor the device mic. Finally I gave up and decided to rollback to the old lolipop stock rom.
Here's comes the current problem:-
1- I did flash 10.7.A.0.222 Customized MEA using flash tool and it's flashed successfully.
2- I'm now stuck with a dead black screen after sony logo.
I tried everything, changed the flashtool version, downloaded other ftf kernel file, used Xperia Companion and non of them worked for me. I did also tried what's listed in here https://forum.xda-developers.com/xperia-z/general/disaster-recovery-getting-z1-zu-z-zl-to-t2229250
I only can boot into fastboot or flashboot mode
I cannot copy files to my phone as it never appears as a storage media in my computer.
Any help will be much appreciated
Sorry for the long post
I never had this problem before, but have you try other ftf with lower android version like KK?
I see this problem on someone, everyone of them had this problem when they try to revert back to stock LP from N. Then someone suggest to flash KK ftf. You should try this if you haven't try this.
Sorry if my English is bad.
UPDATE:
when the first 7.0 nougat custom rom came, I'm on 5.1.1 rom with XZDual recovery. I made a backup for this rom and flash the 7.0 N rom only for trial then revert back to stock 5.1.1 that I backup before. Chippa's rom always came with latest built-in recovery so when I upgrade to nougat rom the XZDual recovery also lost (I don't have FOTA recovery, lol).
The step I made to revert back to stock is to do a FULL wipe of the phone (cache, davlik cache, data, system, AND internal storage), not a regular full wipe (without internal storage).
I put my backup stock rom file to my external sdcard (because the internal storage got wiped) and begin to flash, BUT NOT reboot into system, I reboot the phone to recovery instead (because I think the 5.1.1 rom works better with old TWRP so I reboot the phone to recovery first to get the old XZDual recovery).
After phone enter the old TWRP, I do a FULL wipe (cache, davlik, data, system, internal storage) once again to make sure everything OK, then flash the stock rom once again.
aand... it works. I did it 3-4 times to test new build of 7.0 n rom and never have any problem of reverting back.
But, I never test this method on newest 7.1.1 rom or 7.1.2 rom.
since you can't boot on LP rom, then try to flash KK rom.
Just install phone driver, flashtool, and download the KK ftf.
I'm sorry I can't provide you the full instruction because I never had this problem before, but you can search for this on N rom thread (the rom developed by Chippa). There is a guide made by someone on that thread.
Zerikwan said:
I never had this problem before, but have you try other ftf with lower android version like KK?
I see this problem on someone, everyone of them had this problem when they try to revert back to stock LP from N. Then someone suggest to flash KK ftf. You should try this if you haven't try this.
Sorry if my English is bad.
UPDATE:
when the first 7.0 nougat custom rom came, I'm on 5.1.1 rom with XZDual recovery. I made a backup for this rom and flash the 7.0 N rom only for trial then revert back to stock 5.1.1 that I backup before. Chippa's rom always came with latest built-in recovery so when I upgrade to nougat rom the XZDual recovery also lost (I don't have FOTA recovery, lol).
The step I made to revert back to stock is to do a FULL wipe of the phone (cache, davlik cache, data, system, AND internal storage), not a regular full wipe (without internal storage).
I put my backup stock rom file to my external sdcard (because the internal storage got wiped) and begin to flash, BUT NOT reboot into system, I reboot the phone to recovery instead (because I think the 5.1.1 rom works better with old TWRP so I reboot the phone to recovery first to get the old XZDual recovery).
After phone enter the old TWRP, I do a FULL wipe (cache, davlik, data, system, internal storage) once again to make sure everything OK, then flash the stock rom once again.
aand... it works. I did it 3-4 times to test new build of 7.0 n rom and never have any problem of reverting back.
But, I never test this method on newest 7.1.1 rom or 7.1.2 rom.
since you can't boot on LP rom, then try to flash KK rom.
Just install phone driver, flashtool, and download the KK ftf.
I'm sorry I can't provide you the full instruction because I never had this problem before, but you can search for this on N rom thread (the rom developed by Chippa). There is a guide made by someone on that thread.
Click to expand...
Click to collapse
Thank you so much for your reply. I will try it out. I really appreciate your contribution and I will keep you updated

Categories

Resources