Sup, I got sick of waiting for OEM Unlock (at 13 days now on BRI CSC from never-msrp) and decided to try flashing another region.
Clearly, region is stuck with what you started with regardless of the firmware you flash.
Alright, so let's just erase efs (yeah, that little checkbox in Odin that's usually safe on every other device, or an empty or unsigned efs.img in the tar) then and pull SIM out and maybe it won't know what I started with and default to XEU.
Yeah, no, dm-verity errors from then on. Device completely unrecognizable by Kies & Smart Switch.
It gets into Download mode, it flashes, but it fails the Installing screen @ around 32% on the next boot and falls back to recovery showing dm-verity error.
So, any suggestions? I'm sure someone has experience here with wiped EFS on the S8 or Note 8.
By the way, this device, as you can tell by the first sentence, is in OEM LOCKED mode.
UPDATE: SEE LAST POST https://forum.xda-developers.com/showpost.php?p=75879640&postcount=20
That (32%) is the normal stop point for the binaries error at boot after flashing unofficial firmware, I'd try flashing the full smash, BL, CP, CSC, AP from a stock firmware all at once in Odin, it got me out of it.
Have you tried flashing the factory binary for N950F? I had almost the same, not flashing situation, and the factory binary allowed me to restore my phone following the steps I found for restoring EFS. Although I paid 10 dollars to be able to download the factory binary from a website. It is called COMBINATION file.
i23u8 said:
Have you tried flashing the factory binary for N950F? I had almost the same, not flashing situation, and the factory binary allowed me to restore my phone following the steps I found for restoring EFS. Although I paid 10 dollars to be able to download the factory binary from a website. It is called COMBINATION file.
Click to expand...
Click to collapse
Interesting, I found one for AQH9. I'll see what I can do with it! Thanks!
krabman said:
That (32%) is the normal stop point for the binaries error at boot after flashing unofficial firmware, I'd try flashing the full smash, BL, CP, CSC, AP from a stock firmware all at once in Odin, it got me out of it.
Click to expand...
Click to collapse
This is actually the first thing I tried.
jcadduono said:
Sup, I got sick of waiting for OEM Unlock (at 13 days now on BRI CSC from never-msrp) and decided to try flashing another region.
Clearly, region is stuck with what you started with regardless of the firmware you flash.
Alright, so let's just erase efs then and pull SIM out and maybe it won't know what I started with and default to XEU.
Yeah, no, dm-verity errors from then on. Device completely unrecognizable by Kies & Smart Switch.
It gets into Download mode, it flashes, but it fails the Installing screen @ around 32% on the next boot and falls back to recovery showing dm-verity error.
So, any suggestions? I'm sure someone has experience here with wiped EFS on the S8 or Note 8.
By the way, this device, as you can tell by the first sentence, is in OEM LOCKED mode.
Click to expand...
Click to collapse
Welcome to the N8 group. Can you specify What exactly is giving a dm-verity error? You say its able to get to recovery. Have you tried flashing your CSC?
EDIT: Other than that if you can find the Combo files for your model(you cannot use the n950U ones) then you could boot into the device using a similar method to the snapdragon root(using the abl.elf,devcfg,boot.img and recovery.img in a tar file flash with comsey odin and dm-verity on system should get disabled. That will allow you to at least boot. but since you wiped efs probably dont have service.
No success with factory binaries, they don't boot past the FACTORY BINARY >>>>>>>>> loading screen.
I think the modem is panicking early in boot process due to empty efs partition.
So if you try to flash efs.img unsigned with Odin, it will erase efs and then refuse to flash new one. I guess I'm screwed unless I can somehow find a signed efs.img to flash.
jcadduono said:
No success with factory binaries, they don't boot past the FACTORY BINARY >>>>>>>>> loading screen.
I think the modem is panicking early in boot process due to empty efs partition.
So if you try to flash efs.img unsigned with Odin, it will erase efs and then refuse to flash new one. I guess I'm screwed unless I can somehow find a signed efs.img to flash.
Click to expand...
Click to collapse
Try installing all stock FW then create a new tar with the files i mentioned above. See what happens then. You SHOULD also have adb on boot when using the combo files like that.
me2151 said:
Try installing all stock FW then create a new tar with the files i mentioned above. See what happens then. You SHOULD also have adb on boot when using the combo files like that.
Click to expand...
Click to collapse
yes, adb is unauthorized though so what's the point of it
also, i did try this, no success getting past samsung screen, which is the same case as factory binary system, just stuck on the logo forever with adb unauthorized
jcadduono said:
yes, adb is unauthorized though so what's the point of it
also, i did try this, no success getting past samsung screen, which is the same case as factory binary system, just stuck on the logo forever with adb unauthorized
Click to expand...
Click to collapse
Ok. Is your efs image sparse or regular img? According to a guy i know on S8 efs isnt secure boot checked and is flashable no issue in odin. just needs to be a sparse image and named efs.img.ext4
me2151 said:
Ok. Is your efs image sparse or regular img? According to a guy i know on S8 efs isnt secure boot checked and is flashable no issue in odin. just needs to be a sparse image and named efs.img.ext4
Click to expand...
Click to collapse
it is secure boot checked, i flashed a sparse ext4 efs.img (efs.img is what the partition layout says it should be named), it failed with the error that you can't flash unsigned files to this partition (on DL mode screen)
it also left the efs partition completely empty, so it zeros it out before even checking if the image sent is signed
the guy who said it wasn't secure boot checked probably had an OEM unlocked device
my sparse ext4.img file was an empty filesystem, it would have at least mounted if the flash worked
jcadduono said:
it is secure boot checked, i flashed a sparse ext4 efs.img (efs.img is what the partition layout says it should be named), it failed with the error that you can't flash unsigned files to this partition (on DL mode screen)
it also left the efs partition completely empty, so it zeros it out before even checking if the image sent is signed
the guy who said it wasn't secure boot checked probably had an OEM unlocked device
my sparse ext4.img file was an empty filesystem, it would have at least mounted if the flash worked
Click to expand...
Click to collapse
Crap. Forgot you were Exynos. Your Secure boot stuff is different. We are Snapdragon. Sorry.
Was looking into Octoplus or z3x as a solution, but unfortunately both require a rooted working phone, it seems the only way to possibly get past this error is to get EFS formatted somehow, or flash a signed sparse EFS in Odin. Maybe if engineering binary doesn't have verity on system it could be possible to replace an early system service with a shell script to format efs, and that might bring the device far enough to boot, but even then I would never have service until I bought some kind of Samsung EFS certificate and installed it with a z3x/octoplus.
This is way beyond me, so either I have to desperately plea with never-msrp, or Samsung Taiwan, or find someone in Taiwan willing to RMA the Note8 for me then ship the fixed one back to me
ebay and paypal say buyer's fault and won't let me open a case (told them it failed during firmware upgrade)
argued that the seller did not mention anywhere in ad that the phone was from a region that did not speak English and offered no manufacturer warranty (at least a UK or UAE Exynos phone can be RMA'd then forwarded by a friend, Taiwan cannot)
got nowhere
eBay says: The moment you accept a firmware upgrade on a smartphone, even if it is official/from the manufacturer, you forfeit your 30 day money back guarantee. This is because any modification done to an item after receiving it counts as altering the product and breaks the guarantee.
Me: Well, in that case just setting it up breaks the guarantee!
i can probably get $250 for it being sold for parts which is pretty painful when it's brand new without a single scratch and knox 0x0
if it were possible to purchase a motherboard for the phone i would do that, but that probably won't be possible for at least 2 years
update: never-msrp is trying to see if they can help me get it into taiwan rma through them
i tihnk i can fix inbox me
I once had a note 4 that where bricked and nothing I did could bring it back and no one on XDA was able to help so I thought it was dead beat.
I refused to give up as back then the phone was only a few months old and I paid full price on release date so I got online and started downloading stock Rom after stock Rom all from different countries and after a week of downloading and flashing I got it working.
Right after I got it working I flashed BTU stock and then I was a happy dude.
I don't know what caused the issue and I don't know how it was fixed other then the longest week of my life of downloading and flashing that got it working. Would maybe have taken half the time if the samfirmware downloading speeds wernt so damn slow.
I know ur issue is different and furthermore u understand what u r doing more then I ever will but maybe with a bit of luck and persistently trying it might work again.
jcadduono said:
No success with factory binaries, they don't boot past the FACTORY BINARY >>>>>>>>> loading screen.
I think the modem is panicking early in boot process due to empty efs partition.
So if you try to flash efs.img unsigned with Odin, it will erase efs and then refuse to flash new one. I guess I'm screwed unless I can somehow find a signed efs.img to flash.
Click to expand...
Click to collapse
Which version of Factory you flashed?
Someone who's hard brick try this. I msg guy and he said they haven't had chance to try with Note 8 yet. He has thousands of reviews and high stars. Dealt with him in the past.
https://rover.ebay.com/rover/0/0/0?mpre=https://www.ebay.com/ulk/itm/121826357738
Feel for ya hope you get it sorted
Sent from my SM-N950F using XDA-Developers Legacy app
Try the s8plus csc of rom.
Hey guys, so one day I came upon something in my facebook feed regarding G955F being "world first" /efs mount fail fixed.
This gave me some hella hope, so I contacted the guy who posted it.
He charged $75 USD via PayPal (I paid with "goods and services" option in PayPal to his email using my VISA)
Installed TeamViewerQS and Flexihub.
He logged in, and was able to use some tool from his side with Flexihub while my N950F/DS was in download mode and it somehow convinced the phone to recreate its EFS partition.
Once the EFS was back to life, I was FINALLY able to boot a factory binary, and this fixed the remainder of my phone.
He then flashed stock and it booted up and made it to setup wizard.
(there was about an hour or so during this that system was not flashing, and I had to switch PCs to get a USB 2.0 port. Apparently USB 3.1 was too fast for download mode to work correctly)
He says that my DRK is probably still corrupt so rebooting the phone will boot loop, but if I OEM Unlock it then I will be able to bypass DRK error.
Update: My phone reboots fine and is perfectly working! yay!
I have LTE and both of my IMEI are proper.
As for as I can tell everything is working perfectly and the device is still OEM ON FRP OFF and Official status.
I have not tried rebooting.
I cannot OEM Unlock my phone probably for another 2 weeks after adding my Samsung account, so gotta be careful not to let the battery die. :/
If you want his services, you can message him on his facebook account: https://www.facebook.com/baselalzoupi
Good luck!
Related
hello, i recently bought used droid 4, found it to be with some leftover data (sms, and such) so first thing i did was a factory reset only to
find it after a while in extact same state. weird thing is that when i factory reset it after removing some apps or changing anything at all it acts
as if i restored some backup instead of wiping device. it spams me with errors every few seconds too which is quite troublesome to say the least.
i searched the internet for an answer (still looking) to this problem but so far got nothing. i mean there are lots of ppl with similiar issue
but no real answer anywhere i looked. i thought maybe flashing some stock rom (dont wanna try anything custom yet since i got lapdock
too and havent checked if webtop works with custom roms yet). is it the right direction in my case or is there some simplier answer to my problem?
thanks in advance
update: cant root it, cant install official update through rsdlite, cant update through other unofficial ways,
it acts as if everything went fine and each time im back to square 1. it aint my first or second journey with rooting,
changing rom but im not really sure what else can i do. also rsdlite cant detect any information about device (imei,
os version, flex drm boot etc are all filled with N/A
install from sdcard also failed - signature verification failed. keeps gettin better. downloading another rom from
official moto website... not expecting anything though
wyklocnik said:
hello, i recently bought used droid 4, found it to be with some leftover data (sms, and such) so first thing i did was a factory reset only to
find it after a while in extact same state. weird thing is that when i factory reset it after removing some apps or changing anything at all it acts
as if i restored some backup instead of wiping device. it spams me with errors every few seconds too which is quite troublesome to say the least.
i searched the internet for an answer (still looking) to this problem but so far got nothing. i mean there are lots of ppl with similiar issue
but no real answer anywhere i looked. i thought maybe flashing some stock rom (dont wanna try anything custom yet since i got lapdock
too and havent checked if webtop works with custom roms yet). is it the right direction in my case or is there some simplier answer to my problem?
thanks in advance
Click to expand...
Click to collapse
uncheck restore data Hard Reset - DROID 4 by MOTOROLA - Verizon Wireless Support
update: cant root it, cant install official update through rsdlite,
Click to expand...
Click to collapse
updates.zips are not installed with rsdlite, XML/firmware is install with rsd lite, but adroid version can not be downgraded
cant update through other unofficial ways,
it acts as if everything went fine and each time im back to square 1. it aint my first or second journey with rooting,
changing rom but im not really sure what else can i do. also rsdlite cant detect any information about device (imei,
os version, flex drm boot etc are all filled with N/A
install from sdcard also failed - signature verification failed. keeps gettin better. downloading another rom from
official moto website... not expecting anything though
Click to expand...
Click to collapse
what official site? use files from my page How to Use RSD Lite to flash a .XML Stock Rom (firmware)
thanks for taking interest
tried factory reset with options You mentioned unchecked, same thing as before.
i did use xml with rsdlite and zip through built in recovery.
tried to find this page i downloaded files but theres too much in yesterdays history, trying those from Your link now.
also tried to update rom ota, but of course theres an error. oh my droid runs 4.0.4, i havent mentioned it before.
also, found in the net schematics for factory cable, was thinking if its worth a shot this way:
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable-4.html
Factory cable only allows you to power device with low battery/no battery
Sent from my Amazon OtterX using Tapatalk
---------- Post added at 10:33 AM ---------- Previous post was at 10:31 AM ----------
Update zips only update specific system versions, you have to use correct one, and must be complete stock.
Sent from my Amazon OtterX using Tapatalk
from what i read in this post about factory cable it says it boots phone different way than normal thats why i thought maybe
itll be able to successfully update with it. also after every reset of this droid its not a simple matter of apps coming back thru wifi.
wifi is disabled and theyre there right from the start. i can remove some widgets or apps from home screen, i can delete texts,
and after reset theyre all back where they were. its as if every change i made havent been saved. i dont even have to reset phone,
i just need to reboot it to have it all back
phone needs to be in AP Fastboot mode when flashing with rsd lite.
verify md5 checksum for xml file before flashing.
yes, it was in ap fatboot mode, didnt verify the md5 tho.
more importantly, file i downloaded from site You linked passed verification! guess what i found wasnt official updates after all...
i hope this works
wyklocnik said:
from what i read in this post about factory cable it says it boots phone different way than normal thats why i thought maybe
Click to expand...
Click to collapse
Factory/Fastboot cable only uses the alt power (4) pin to power device, there are several pre-made ones
itll be able to successfully update with it. also after every reset of this droid its not a simple matter of apps coming back thru wifi.
wifi is disabled and theyre there right from the start. i can remove some widgets or apps from home screen, i can delete texts,
and after reset theyre all back where they were. its as if every change i made havent been saved. i dont even have to reset phone,
i just need to reboot it to have it all back
Click to expand...
Click to collapse
try reformatting internal sd card, before wiping
---------- Post added at 10:58 AM ---------- Previous post was at 10:53 AM ----------
wyklocnik said:
yes, it was in ap fatboot mode, didnt verify the md5 tho.
more importantly, file i downloaded from site You linked passed verification! guess what i found wasnt official updates after all...
i hope this works
Click to expand...
Click to collapse
there are no official moto download sites, all moto firmware is pulled by people with special access, and reuploaded
try reformatting internal sd card, before wiping
Click to expand...
Click to collapse
is it any different than checking "erase internal storage" when reseting phone?
anyways did it but atm have to recharge battery before trying to wipe it again.
also rom was succesfully updated thru recovery with no errors and after reboot im... back to square 1...
wyklocnik said:
is it any different than checking "erase internal storage" when reseting phone?
Click to expand...
Click to collapse
formatting is different than wiping data, in menu>settings>storage>unmount>format
anyways did it but atm have to recharge battery before trying to wipe it again.
also rom was succesfully updated thru recovery with no errors and after reboot im... back to square 1...
Click to expand...
Click to collapse
did system version change?
same story after formating internal memory.
no changes whatsoever. same homescreen, same widgets/apps present. same system version.
and of course new error every 5 seconds. guess the phone is messed up good.
talk about luck. its second droid 4 i bought. first i bought over a month ago on auction site, it was new. i paid, guy never sent it.
now this one. its like a curse
formatting internal won't wipe, user data, but will wipe backup data.
tried xml with rsdlite now.
after first reboot its supposed to go into the recovery mode right?
it went back in to ap fastboot... and after rsd transfered all the files then it went to bootloader... and now program says reboot is in process while phone sits in recovery mode...
wyklocnik said:
tried xml with rsdlite now.
after first reboot its supposed to go into the recovery mode right?
Click to expand...
Click to collapse
it happens sometimes
it went back in to ap fastboot... and after rsd transfered all the files then it went to bootloader... and now program says reboot is in process while phone sits in recovery mode...
Click to expand...
Click to collapse
select wipe data, then select reboot
done, nothing changed.
also, when rsd works it acts as if it doesnt wait for the phone with operations.
it writes reboot, phone starts to reboot, and long time before it boots back either in ap fastboot mode or into recovery
rsd says its already transfering files, it says reboot again (before phone even gets into fastboot or recovery after 1st reboot) and so on.
wyklocnik said:
done, nothing changed.
also, when rsd works it acts as if it doesnt wait for the phone with operations.
it writes reboot, phone starts to reboot, and long time before it boots back either in ap fastboot mode or into recovery
rsd says its already transfering files, it says reboot again (before phone even gets into fastboot or recovery after 1st reboot) and so on.
Click to expand...
Click to collapse
which fastboot version? 0A.74 , 0A.77?
which xml file?
0A.74
cdma_maserati_9.8.2O-72_VZW-18-2_1ff.xml
looks like you have a failure to write data, don't think there is a fix.
could try my Unbrick Moto device with moto-fastboot.exe
but unlikely that it will work
Hi everyone, I'm having a lot of problems with my phone: last night, after it dropped to 0% battery life, it wouldn't charge. So i waited a while and ifinally managed to turn it on, but It wouldn't go past the Cyanogenmod logo. So i tried few things,first wiping cache, then factory reset from TWRP and I even tried the "Factory" option in the fastboot screen. Nothing worked, and it even got worse I think, TWRP says it's unable to mount /data partition and /storage partition. I don't know what caused it, and i don't remember the precise moment it became "unmountable" for the first time (since I've been trying to fix this thing for like 24 hours now).
Since i couldn't fix it via recovery, I tried looking for people who had the same problem on the internet, and I tried everything i could find. (like this: http://forum.xda-developers.com/showthread.php?t=2683787).
I then tried to go back to stock rom via adb and fastboot, but without success.
The main problem with fastboot is the fact that it doesn't change anything in my phone, it gives no errors when i try to flash the stock rom, but when i reboot my phone, nothing changes, or at least this is my opinion, since I still get the cyanogenmod logo, and TWRP doesn't get replaced (while it should go away, since when in the whole process of flashing the rom, i also flash recovery.img, which shouldn't be TWRP).
I tried a whole lot of other commands too, like "fastboot erase recovery", but TWRP is still there, and so is the cyanogenmod logo.
This is why i think fastboot is unable to write in my phone, but if that's the case, it should at least give errors.
So, wrapping up, my data partition seems to be corrupted, and flashing the stock rom still gets my into a bootloop (with the logo from the previous rom and TWRP still there).
Do you have any advice?
P.S: my phone is a xt1068
Are you able to pull logcat?
Logcat command works, i don't get errors in the terminal, but in the text file there's only this line : "/sbin/sh: exec: line 1: logcat: not found"
Dmesg works though, I don't know if it's helpful
"
dagrot said:
I then tried to go back to stock rom via adb and fastboot, but without success.
The main problem with fastboot is the fact that it doesn't change anything in my phone, it gives no errors when i try to flash the stock rom, but when i reboot my phone, nothing changes, or at least this is my opinion, since I still get the cyanogenmod logo, and TWRP doesn't get replaced (while it should go away, since when in the whole process of flashing the rom, i also flash recovery.img, which shouldn't be TWRP).
I tried a whole lot of other commands too, like "fastboot erase recovery", but TWRP is still there, and so is the cyanogenmod logo.
This is why i think fastboot is unable to write in my phone, but if that's the case, it should at least give errors.
So, wrapping up, my data partition seems to be corrupted, and flashing the stock rom still gets my into a bootloop (with the logo from the previous rom and TWRP still there).
Do you have any advice?
P.S: my phone is a xt1068
Click to expand...
Click to collapse
I have same phone, you mentioned you also tried to flash stock rom without success, did you flash the partition file aswell before flashing system and the rest of files ? Check the flashfile.xml file into the stock firmware folder to make sure you not missing anything.
Code:
fastboot flash partition gpt.bin
Good luck.
i'm on the same boat. It seems it's a NAND issue, but how come it happens randomly?
It seems to happen (its a bit rare, so don't get worried) when you let your battery drop to 0% and the phone suddently turn off, like what happened to the OP.
Sent from my XT1063 using XDA Free mobile app
Lynse said:
It seems to happen (its a bit rare, so don't get worried) when you let your battery drop to 0% and the phone suddently turn off, like what happened to the OP.
Sent from my XT1063 using XDA Free mobile app
Click to expand...
Click to collapse
If it's a bit rare, how come there are a rather interesting quantity of posts regarding that matter? I'd like to know WHY I can't write even with fastboot. There should be a way of unlocking the NAND / partitions. Even if I try to hard brick it, it's impossible.
PS: can we someone a look at this? http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2
Possibly if we can force the way to QHSUSB mode, phone can be saved.
jhonnyx said:
PS: can we someone a look at this? http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2
Possibly if we can force the way to QHSUSB mode, phone can be saved.
Click to expand...
Click to collapse
Unfortunately I didn't quite understand what that is about, if you happen to try it out let us know.
Anyway, if we don't manage to fix it, I guess I'm going to try and take it back to the store, since it is a common problem. Only problem is I'm on a custom rom and I can't even go back to stock and relock the bootloader, so I don't think they are going to replace it, but it's worth a try.
You can try by helping me to look for a circuit PDF from the board or trying it yourself.
I could try and disassemble it, but you're gonna have to wait a few days, I'm not at home and I'm gonna be back on the weekend.
As for the circuit pdf, I was only able to find videos and guides on how to disassemble it, unfortunately
Dude, no worries. Ive took the back out with all the screws, but I have nothng to make shorts with.... I'll come up with something. Take your time and keep me posted.
any news concerning this problem? i have tried searching for a manual but I did not succeed.
Anyways after finding the manual, we can short circuit the 2 capacitors there and the phone will be in qhsusb mode.
And after that ?
gbb14 said:
any news concerning this problem? i have tried searching for a manual but I did not succeed.
Anyways after finding the manual, we can short circuit the 2 capacitors there and the phone will be in qhsusb mode.
And after that ?
Click to expand...
Click to collapse
After that.... well.... after some research, we'll be needing singleimage.bin to use the blankflash utility for lollipop phones (mbm-ci 5.0 lollipop) so somebody can generate the singleimage.bin for us.
Once we have that, we can try to flash the phone at lowlevel to see what happens.
I will search the internets in hoping to find the schematics of this phone.
Keep me informed if you find it faster .
Cheers mate
we can connect through hangouts / etc.
look up for my user at gmail
So I have a very odd problem, and I'm fairly experienced with repairing, rooting, and reverting phones to stock which have custom roms, in this case I have a completely stock note 5 which was experiencing a boot loop error at the note 5 model number screen. Going through the motions I normally would, hard reset, nope, safe mode, nope, wipe cache, nope, master reset, nope, so I flash the firmware with a stock rom, which worked, but resulted in the same problem, rebooting at the model number screen just before the samsung logo every few seconds, tried 3 other firmware versions and downloads, also no. Not sure whats up with this thing, but anyone have any ideas? I personally know the user, family, phone wasnt physically damaged or exposed to water. I'm also getting no command just before entering recovery and failed to mount/ preload (no such file or directory) during the master reset. Its been forever sense I've meddled with a note 5 and cannot remember if these are normal, or related to the issue, I dont ever remember seeing these with my own note 5.
I ran into this exact same problem weeks ago on my S7. I tried flashing 7.0 on my 930V and for whatever reason the phone went into the exact same bootloop showing the Samsung logo every few seconds, vibrating, etc. I got back into download mode but wasn't able to fix it. Then went into Recovery and it only said in blue letters in the top left "Recovery rebooting" and kept flashing that message. Lucky for me I was under warranty and sent it to Samsung. They replaced it free of charge. I ended up trading for a Note 5. I kept running into issues with my S7 and network issues so I traded it.
Anyway, I'm like you in the fact I'm pretty comfortable rooting, repairing devices etc. But I still don't know what I did to mess up that S7 in Odin. Just wanted to share that I had a similar situation. Hope you were able to get a new phone or fix your issue.
sinkableelk said:
So I have a very odd problem, and I'm fairly experienced with repairing, rooting, and reverting phones to stock which have custom roms, in this case I have a completely stock note 5 which was experiencing a boot loop error at the note 5 model number screen. Going through the motions I normally would, hard reset, nope, safe mode, nope, wipe cache, nope, master reset, nope, so I flash the firmware with a stock rom, which worked, but resulted in the same problem, rebooting at the model number screen just before the samsung logo every few seconds, tried 3 other firmware versions and downloads, also no. Not sure whats up with this thing, but anyone have any ideas? I personally know the user, family, phone wasnt physically damaged or exposed to water. I'm also getting no command just before entering recovery and failed to mount/ preload (no such file or directory) during the master reset. Its been forever sense I've meddled with a note 5 and cannot remember if these are normal, or related to the issue, I dont ever remember seeing these with my own note 5.
Click to expand...
Click to collapse
My suggestion is this..
Download the latest version of TWRP
Boot to Download Mode
Odin flash TWRP
Boot to TWRP Recovery
Full wipe including internal storage x 2
Format DATA x 2
Odin flash the latest firmware for your device
(All 4 - BLUE, AP, CP, CSC)
OR
Use Smart Switch Emergency Recovery to restore the firmware.
Hope this helps. Good luck and happy flashing! Let's us know what happens.
Sent from my Samsung SM-G955U using XDA Labs
In this tutorial I will inform you on three different soft bricks, and how to fix them.
You must be able to boot into TWRP and/or Odin/Download mode!
1.) Verification Failed.
Method #1
This method will work with people whom can't reset their device, due to an unmountable /data partition, and those whom experience this error, who can reset but have valuable items, applications, videos, or photos that they don't want to lose. Must be able to boot into Odin/Download mode. (Volume Down+Home+Power)
The solution is actually pretty simple. Boot into Odin/Download mode. This has to be done correctly, not from TWRP recovery. When the prompt for "Volume Up = Continue" and "Volume Down = Cancel (Restart)" press volume down. You should no longer see verification failed, but instead be sitting on the T-Mobile logo. This is normal, and could take 30 seconds to 10 minutes, depending on the amount of data.
This method works all because of Knox. Knox is what Samsung uses to void your warranty. Companies are not allowed to void a warranty when rooting, installing roms, or recovery, unless they have direct evidence. Knox will trigger this when it isn't sure. It will try forcing you to bring it to Samsung, and they can directly find out why it was caused. This happens when it thinks that you cancelled.
Method #2
This one will require you to lose all your data, but is mainly intended for those whom cannot reset their device. Download the stock firmware from the links below. Open Odin (Jodin3 will not work! It is not fully functioning, do not try it.) and boot device into Download/Odin mode. On your computer, you should see 'Added' in the logs. If this does not show up download the Samsung USB Drivers. Select AP and then select the stock firmware. Now flash it. This can also be done through TWRP
For bootloop and frozen Android/Carrier logo just do Method 2. You usually will keep all your data.
FOR 'VERIFICATION FAILED' YOU CANNOT RESTORE FROM A BACKUP!
FOR BOOTLOOPS AND FROZEN STARTUP SCREEN, YOU CAN!
Downloads:
Samsung USB Drivers
7.1.1 Stock Firmware
Odin3 v3.12.10
Post any bricks below that you have encountered!
I'm interested in how many variations there are, and how common they are.
One weird error I'm getting all of a sudden is "Custom binary blocked by FRP Lock" when I tried to reboot my phone. Any ideas?
Hovo said:
One weird error I'm getting all of a sudden is "Custom binary blocked by FRP Lock" when I tried to reboot my phone. Any ideas?
Click to expand...
Click to collapse
Please describe this issue in further detail. Has this been happening out of nowhere, or did you just try flashing something via Odin/Download mode or TWRP.
Also, before flashing did you enable OEM unlock
This also happens when something flashed via Odin/Download mode is incompatible.
Are you still able to boot into the default system partition? If not safe mode?
TechNash said:
Please describe this issue in further detail. Has this been happening out of nowhere, or did you just try flashing something via Odin/Download mode or TWRP.
Also, before flashing did you enable OEM unlock
This also happens when something flashed via Odin/Download mode is incompatible.
Are you still able to boot into the default system partition? If not safe mode?
Click to expand...
Click to collapse
I should have updated my post, I'm not sure what happened but I flashed stock through Odin and the problem went away, after that I was able to flash twrp and root/install other roms.
It's still weird that the problem happened out of nowhere, not sure what triggered it.
It goes away when u log in to google with the last account that is associated with the phone
Hovo said:
I should have updated my post, I'm not sure what happened but I flashed stock through Odin and the problem went away, after that I was able to flash twrp and root/install other roms.
It's still weird that the problem happened out of nowhere, not sure what triggered it.
Click to expand...
Click to collapse
Probs OTA. It happened to me my first 3 tries. Ended up factory reseting, and installing fresh via Odin, didn't fix it.
I just turned off auto reboot on Odin, and then pulled my battery on my J7. Booted up straight to Recovery from there.
TechNash said:
Probs OTA. It happened to me my first 3 tries. Ended up factory reseting, and installing fresh via Odin, didn't fix it.
I just turned off auto reboot on Odin, and then pulled my battery on my J7. Booted up straight to Recovery from there.
Click to expand...
Click to collapse
It would make sense if it was an OTA update TY
Hi, I tried to root my phone and I got this error, I don't mind restarting the phone, but isn't there a way for me to backup my data (photos mainly) first?
Nightwinter said:
Hi, I tried to root my phone and I got this error, I don't mind restarting the phone, but isn't there a way for me to backup my data (photos mainly) first?
Click to expand...
Click to collapse
Sorry I didnt respond.
Looks like you didnt flash encryption breaker. Keep this on your SD Card as its a great way to recover from these errors, and you will need it when you flash ROMS.
Just boot in recovery, flash ashix no verity no encrypt, then reboot into system. You shouldnt have this error.
TechNash said:
Sorry I didnt respond.
Looks like you didnt flash encryption breaker. Keep this on your SD Card as its a great way to recover from these errors, and you will need it when you flash ROMS.
Just boot in recovery, flash ashix no verity no encrypt, then reboot into system. You shouldnt have this error.
Click to expand...
Click to collapse
Keep what in the SD card? the is no file in your quote.
Nightwinter said:
Keep what in the SD card? the is no file in your quote.
Click to expand...
Click to collapse
He's referring to the encryption breaker file ("no-verity-no-encrypt_ashyx.zip") in his first sentence. That is assuming you already had it and should be keeping it on your SD card all the time for flashing ROMs
graevon said:
He's referring to the encryption breaker file ("no-verity-no-encrypt_ashyx.zip") in his first sentence. That is assuming you already had it and should be keeping it on your SD card all the time for flashing ROMs
Click to expand...
Click to collapse
Thanks for explaining that to him.
TechNash said:
Thanks for explaining that to him.
Click to expand...
Click to collapse
how to remove Verification Failed or root in the TWRP file manager without losing data
Mujeeb64 said:
how to remove Verification Failed or root in the TWRP file manager without losing data
Click to expand...
Click to collapse
Flash ashyx-no-verity-no-encrypt.zip in twrp.
Reboot
TechNash said:
In this tutorial I will inform you on three different soft bricks, and how to fix them.
You must be able to boot into TWRP and/or Odin/Download mode!
1.) Verification Failed.
Method #1
This method will work with people whom can't reset their device, due to an unmountable /data partition, and those whom experience this error, who can reset but have valuable items, applications, videos, or photos that they don't want to lose. Must be able to boot into Odin/Download mode. (Volume Down+Home+Power)
The solution is actually pretty simple. Boot into Odin/Download mode. This has to be done correctly, not from TWRP recovery. When the prompt for "Volume Up = Continue" and "Volume Down = Cancel (Restart)" press volume down. You should no longer see verification failed, but instead be sitting on the T-Mobile logo. This is normal, and could take 30 seconds to 10 minutes, depending on the amount of data.
This method works all because of Knox. Knox is what Samsung uses to void your warranty. Companies are not allowed to void a warranty when rooting, installing roms, or recovery, unless they have direct evidence. Knox will trigger this when it isn't sure. It will try forcing you to bring it to Samsung, and they can directly find out why it was caused. This happens when it thinks that you cancelled.
Method #2
This one will require you to lose all your data, but is mainly intended for those whom cannot reset their device. Download the stock firmware from the links below. Open Odin (Jodin3 will not work! It is not fully functioning, do not try it.) and boot device into Download/Odin mode. On your computer, you should see 'Added' in the logs. If this does not show up download the Samsung USB Drivers. Select AP and then select the stock firmware. Now flash it. This can also be done through TWRP
For bootloop and frozen Android/Carrier logo just do Method 2. You usually will keep all your data.
FOR 'VERIFICATION FAILED' YOU CANNOT RESTORE FROM A BACKUP!
FOR BOOTLOOPS AND FROZEN STARTUP SCREEN, YOU CAN!
Downloads:
Samsung USB Drivers
7.1.1 Stock Firmware
Odin3 v3.12.10
Click to expand...
Click to collapse
I have a samsung j700t ud that had the 7.1.1 update installed from tmobile or samsung and it caused the to remain in a continual reboot loop until the battery of the phone dies. Will the methods above repair the issue?
Stuff I've tried:
1. Wipe cache
2. Called samsung and tmobile
3. Used samfirm to download firmware to use with odin that was successfully done but the reboot loop still remains.
smirk24 said:
I have a samsung j700t ud that had the 7.1.1 update installed from tmobile or samsung and it caused the to remain in a continual reboot loop until the battery of the phone dies. Will the methods above repair the issue?
Stuff I've tried:
1. Wipe cache
2. Called samsung and tmobile
3. Used samfirm to download firmware to use with odin that was successfully done but the reboot loop still remains.
Click to expand...
Click to collapse
Was the update sent out to you, or did you download it from SamMobile?
If the update was sent out to you I'm afraid I cannot help, but if you flashed it from SamMobile use an older version like Marshmallow or Lolipop.
EDIT: Make sure you factory reset device and wipe cache after installing from SamMobile.
TechNash said:
Was the update sent out to you, or did you download it from SamMobile?
If the update was sent out to you I'm afraid I cannot help, but if you flashed it from SamMobile use an older version like Marshmallow or Lolipop.
EDIT: Make sure you factory reset device and wipe cache after installing from SamMobile.
Click to expand...
Click to collapse
Id love to but i dont know how to get the marshmallow software and install it to the phone but id like to learn how.
How to recover from Verification Failed without losing data ?Does installing TWRP via Oddin Works and does it able me to transfer my data after installing TWRP ? I dare not try doing it as i have never did it b4
hello i wanted to install a stock rom on my note 10 lite live demo unit (ldu), once the flash ended via odin is displayed (pass) but when i restart the phone i get stuck on the samsung logo, i have already tried to reset and clear the cache it does not change anything, I flash the region of my region (XEF) in January and March but nothing works. Help me please
Hihi. said:
hello i wanted to install a stock rom on my note 10 lite live demo unit (ldu), once the flash ended via odin is displayed (pass) but when i restart the phone i get stuck on the samsung logo, i have already tried to reset and clear the cache it does not change anything, I flash the region of my region (XEF) in January and March but nothing works. Help me please
Click to expand...
Click to collapse
I'm note sure if any of this will work, but this is what I would try:
Redownload the correct stock ROM, making sure it matches the specific hardware (Samsung Exynos vs Qualcomm). Additionally, check the checksum to make sure the download wasn't corrupted.
Flash everything again using Odin, making sure to include all partitions (BL, AP, CRC, etc.) in their correct slots.
If that doesn't work, clear data and reboot.
If that doesn't work, retry with only the AP (somehow does things differently with the partition table).
If that doesn't work, then I'm out of ideas. Maybe some of the more advanced features of Odin could help, but I'm not sure how those work, and you can really mess up your device with them.
Note that the first boot after a full wipe will take significantly longer than normal, as a lot of preparations need to be done. If it passed the bootloader to the second Samsung logo, give it around 10-15 minutes to be sure it's not just taking long.