Hello,
My friend just dropped off his phone that is stuck in bootloops. When you go into recovery it throws the error "dm-verity verification failed". His phone was stock, unrooted so not sure what happened. He said he was typing a text, it froze, and rebooted and started bootlooping. Is there anything I can try to bring it back. Unfortunately he did not back up his photos and that is all that he wants (he already bought a new phone). Would flashing with Odin perhaps work and retain the contents in user storage? Someone told him performing a system wipe/factory reset in recovery would lose all of the photos. That does not sound right to me but I am not sure with this device, been out of the game for a while. Any other ideas? Being that he is stock he has stock recovery so no adb there.
Thanks for any help!
-Syco54645
Related
I was busy trying to install a mod which didn't go very well. Shouldn't be a big problem, just go back to the recovery and put back the backup.... But there things went wrong....
I reïnstalled the rom, but after that I ended up in a bootloop, but what's even worse is that the recovery also reboots the whole time. For a split second I see the recovery screen but then it reboots again.
So now I can't even get into the recovery. I can get into the bootloader and fastboot, so the solution to this problem but be there somewhere.....
The Factory reset options also doesn't work, because therefore it has to go into the recovery, which reboots... So until now I'm in a sort of never ending circel. Who can help me out of this?
edit:
Found the official RUU here on XDA, so I rebooted the phone into fastboot, and started the RUU update. It's installing now.... fingers crossed...
(doing this update, because maybe in the future it might be helpfull to others).
edit2:
Hmmm getting an error that the phone can't be updated...
edit3:
I had to shut down the phone and reboot, according to the problem solver of the RUU updater... Did that, but the phone rebooted again, after that it tried to enter the recovery again, but this time it actually did. So no recovery reboot. At this moment I'm trying to reinstall by previous made backup.
edit4:
REstoring the backup gave me 1 little error, so I also ran the rom installer again. The phone seems to reboot in a normal way now. Android is booting up again.
Hi all,
I really need your guys help. Out of nowhere today my phone restarted and then got stuck in a bootloop. When I went into recovery, it gave me the "android is updating" pop-up. I knew there was no update and within 20 seconds or so it said "no command". I went through to wipe the cache, and after rebooting it back up, strangely it didn't give me the "android is updating" screen that occurs after wiping cache. I went ahead and tried to factory reset through recovery and everything was fine until I got a msg "E: could not mount (file or directory could not be found) or something a long those lines. I'm assuming the EFS is fried? I rebooted it after and even at the "Welcome Screen" it started boot looping again. I'm stock lollipop unrooted. I never rooted this phone or flashed any ROMs. I called T-Mo and they will send me a replacement but I still want to see if this can be fixed. I also don't have a replacement phone so..there's that. Would anyone be able to help?
Edit: The only thing I haven't tried is flashing the stock firmware via odin. Would this trip the knox counter though? I really want to avoid that especially since I am having these issues and I don't want tmo/samsung to think I caused this issue.
Bad phone. Ur new phone will be good to go.
BAD ASS NOTE 4
ok, I think I know the answer, but checking for any other ideas. For some reason my phone was trying to unlock in my pocket, and of course it failed 10 times, and says it is going to wipe phone. It reboots to recovery, but fails dm verification, I assume because it is rooted. I select reboot and it goes back to welcome, says sd card is removed, and it is going to wipe phone because of failed login, and reboots again. Question is best way to get out of this loop. If I do factorey reset from system recovery, will I lose root? Can I get it again? or do I need to refresh my brain and remember how to odin and install a rooted stock rom? any ideas on what would be easiest?
Just did factory reset, kept root, even kept all my blacked out apps
Just run repair assistant
joe12401 said:
ok, I think I know the answer, but checking for any other ideas. For some reason my phone was trying to unlock in my pocket, and of course it failed 10 times, and says it is going to wipe phone. It reboots to recovery, but fails dm verification, I assume because it is rooted. I select reboot and it goes back to welcome, says sd card is removed, and it is going to wipe phone because of failed login, and reboots again. Question is best way to get out of this loop. If I do factorey reset from system recovery, will I lose root? Can I get it again? or do I need to refresh my brain and remember how to odin and install a rooted stock rom? any ideas on what would be easiest?
Click to expand...
Click to collapse
Just did factory reset from the computer, just run repair assistant, Its a very easy way.
Reggards
I'm a complete newbie to android phone modding, and I was really proud of myself when I was able to install the Cyanogen 12.1 and Google Apps onto my Samsung S3 Mini. However, I made the mistake of trying to put my work email on it, which requires that my phone be encrypted. Well, I guess the encryption and rooted phone didn't want to play nice together, so I got the error message that my phone would be factory reset. Boo! Well, it got worse. Instead of a factory reset, my rooted phone now is stuck in what I have now learned is called a bootloop. Basically I turn my phone on, and the Cyanogen start screen (with the text "TEAMWIN") just infinitely flashes on the screen until I pull the battery.
I have tried using Odin 3.07 and cm12.1_golden.nova.20160210.ODIN_TWRP.tar.md5. I do the three button system boot, connect the usb, run Odin, get the phone recognized, and then install the .md5 in the PDA section of Odin. It tells me that it succeeded, but when I restart my phone it's still the same bootloop. I also tried swearing, but that didn't help either.
Has anyone else out there had experience with Cyanogen and this particular error? I would love to get this phone working again... preferably with either a Lollipop version of android or back to Cyanogen 12.1.
Any info would be greatly appreciated! Thanks everyone.
So I've got an update if anyone's interested... I can't call it progress, but it's a different problem now.
I was able to download and use Odin to do what was shown on this link: http://forum.xda-developers.com/showthread.php?t=2122548&highlight=root
Everything worked in Odin, the phone rebooted, and went to the Team Win Recovery Project diagnostics screen, rebooted again, and then to the samsung logo. However, it immediately goes to the "Encryption Failed" error screen, and the only option is to 'reset device'. Of course, doing this just reboots the phone and it then has the Team Win loading screen, Team Win Recovery Project diags screen, Samsung logo, and back to the 'Encryption Failed' screen again. So now I have a new infinite loop to solve. *sigh*
any thoughts?
Have you been able to get into TWRP? If you are, maybe you could wipe everything from there and flash the recovery version of your ROM.
I was able to put the stock bootloader onto the phone using Odin, download the original tar from here: http://live.samsung-updates.com/index.php?device=GT-I8190, then used the stock bootloader to install it from the sd card. Everything went fine, but now when I boot the phone it just hangs on the Samsung Galaxy S3 mini GT-i18190 start screen indefinitely. Is this progress, or have I created a new problem now?
You're playing around with heavy stuff. I won't recommend using an upgrade flash (CM over Odin) as an full flash. Please try flashing a stock image.
If you did something wrong to the partitioning, then it's likely to not allow you to do a successfull factory reset. Maybe you can try re-flashing a stock Odin image with PIT repartitioning.
Remember to try to backup the EFS folder, doing that kind of flash might wipe it.
Trying to give the mother in law my old N6. It was rooted / bootloader unlocked. First attempt was to factory reset from within the OS. That worked fine, until I rebooted... it wouldn't boot.
I then downloaded the Shamu factory images from Google's website (shamu-n6f27m-factory-bf5cce08) and ran the flash-all.bat script. Multiple errors showed up during the script... but I chalked it up to ADB looking for boot slots etc, whereas this one has none.
Phone booted fine. Installed apps, set up the phone, power cycled it and promptly entered a bootloop.
Ran flash.all again, phone booted fine. Flashed TWRP, booted into recovery, checked things out in there (didn't do anything but flash the TWRP) tried to reboot, phone bootloops.
Flashed TWRP, booted into Recovery, tried to erase system, etc.... multiple errors again. Booted into bootloader, ran Flash-all... phone boots. Installed some apps, rebooted phone and bootloop again.
Then I did something REALLY stupid, I locked the bootloader from ADB. Now I'm on the bootloader, but can't OEM unlock because it's asking me to boot into the OS and enable the ability from Developer options.
I've no idea why this phone is doing this - booting fine into the OS once and then getting into a bootloop every time thereafter.
If anyone can shed some light on this, I'd appreciate it. Also, how in the hell do I unlock the bootloader now that I've locked it and I can't boot into the OS or run the Flash-all.bat anymore since it's locked?
Is your recovery stock? If it is, sideload the last OTA from Google and that should get you back into Android so you can toggle the OEM Unlock button.
Thanks. I was getting the "no command" on Stock recovery. Finally fixed this freaking issue after multiple flashes and wipes and everything else I could think of. Finally got it sorted.
usafle said:
Thanks. I was getting the "no command" on Stock recovery. Finally fixed this freaking issue after multiple flashes and wipes and everything else I could think of. Finally got it sorted.
Click to expand...
Click to collapse
So did you finally figure out what it could have been that you were doing wrong?
Strephon Alkhalikoi said:
So did you finally figure out what it could have been that you were doing wrong?
Click to expand...
Click to collapse
No. I could only assume I had messed something up when I was using it back in the day and really hosed something up. System wouldn't wipe, cache wouldn't wipe, userdata wouldn't wipe in "fasboot" just kept getting "unable to find XXXX".
So multiple flashes into TWRP and bootloops trying to really REALLY wipe the device finally fixed it. I just kept erasing / wiping every partition I could find in Stock Recovery, TWRP, and with fastboot commands. Finally I got them all wiped/cleared and was able to flash the stock OS back on and have it 'stick'.