My primary reference for this issue thus far has been the following thread:
Verification Failed, Unable to restart your device.
This dreadful error: "Verification Failed, Unable to restart your device. The Integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data." And a "Reset" button. Nothing seems to...
forum.xda-developers.com
With that said, I still have not found a resolution. To be clear the objective is to NOT LOSE DATA.
The device I am having this issue with is a customers phone which was previously operational save for the fact that the OLED had been physically damaged. The plan was to transplant the motherboard into a working OLED assembly with frame, boot, and back up data before wiping the device and keeping it for a refurb and sell. The device had not been rooted or modified in any way. I have tried everything from, switching out parts, to booting into recovery and wiping cache, to booting into the rom flashing mode and cancelling out. Just this morning I even successfully flashed the most up to date stock rom (correct baseband and everything) using Odin and still nothing.
I have two additional pieces of information that stuck out to me that may have some relevance.
1. In recovery mode, inbetween the yellow text (android recovery mode info and controls) and the blue text (operations that can be selected) there are three lines of red text that read as follows:
!! CAUTION !!
Not enough storage resource.
Perform "lacking storage booting"
Now I have tried to do some research on this " lacking storage booting" but to no avail, as that function is not listed in the recovery mode.
Is this an indication that the device's storage was too close to being full and somehow became corrupted?
2. In the bootloader mode, there are two lines of purple text at the top that reads as follows:
RPMB fuse blown
RPMB PROVISIONED
I was unable to find out much information on this but most forums suggested that this would cause issues with flashing roms. I however had no issue flashing the stock rom onto this device (I read somewhere that it might fix the issue and not lose data)
I am about to give up hope on the device so I thought I would put out a message for assistance in the off chance that there is anything else I have not tried.
Thanks in advance,
Related
My phone was working fine on Thursday morning. Around noon I went to check my phone and it was off. I turned it on and it gets stuck at the initial Samsung boot screen. With the research and testing I have done so far the current state of the phone is...
- Any attempt at normal boot results in getting stuck at the initial Samsung boot screen.
- I am NOT able to enter recovery mode by any method I've tried so far.
- I AM able to enter download mode by holding volume down or both volume buttons while inserting the USB cable.
- The phone DOES charge via USB.
- Connecting to the computer gives a "USB Device Not Recognized" error.
- I have tried cleaning the USB port with alcohol pads as best I can and it had no effect.
- ADB does NOT see the devices (and I know ADB/Drivers/USB Debugging/etc is configured correctly because I develop with this device)
- The phone is NOT rooted nor have I changed ANYTHING within the past few weeks.
- The device IS carrier unlocked (not that this should matter at all).
- The phone does have Google Voice with Groove IP Lite installed (and I remember news that the GV API would change around this time, maybe it broke something?)
- ODIN 3 v1.85 can SOMETIMES see the phone at 0:[COM3] (I'm still trying to figure this out. I THINK it only works if I put battery in, boot to download mode by inserting USB, then after it boots to download I remove and re-insert USB to re-connect the device on the computer, but I'm not certain yet)
I was going to replace the device next month anyways so I don't really care about the device itself. What I am trying to figure out is whether there is any way to recover certain data such as memo notes or game/app data from the device? If I tried to install a new rom via ODIN will that wipe out my app data and notes and stuff or would the data persist like it would for a carrier-pushed update? Can I somehow pull this data off the device from within download mode before I try to flash the device? Am I going in the wrong direction and should be trying something entirely different to begin with? What do you guys suggest? Thanks.
I was waiting to see if anyone else would pitch in with useful information about recovering your data. However, since no one has, I can say that I am pretty sure that you will not be able to recover anything currently in any of the system partitions. (System, kernel, data, preload, etc.) Once you recover your phone, you will still almost certainly have the information that was on your internal sdcard (USB Memory.)
Using Odin3, you should open Odin on the desktop of your pc first, then use the method that works for you to get into download mode, and Odin should recognize your phone.
I understand that you are not too concerned about the device. I would point out that a working I777 that is in good working condition with a clean esn is worth probably $100.00 to $125.00 on Swappa. It would be in your best interest to recover the phone. (Or if that's too much trouble, you can always send it to me, lol.)
Since the phone can enter download mode and be recognized by the computer, it is almost certainly recoverable. The only possible reason that it would not be recoverable is if the problem is due to damaged emmc memory in some part of the system partitions. When you flash the stock firmware, or any firmware, you will lose any possible access to the data partition. You will most likely be required to enter recovery after the flash to perform a wipe data/factory reset before the phone will boot into the system. The data will not persist as it would for an over the air or kies update. But again, as I said in the other thread, you may retain the game data if it is saved to the sdcard. Memo notes are definitely stored in the data partition, so those are lost.
The only thing you can do within download mode is flash firmware, nothing else is possible. I don't know of any other direction you could be going than what we have discussed so far.
As I said before, someone with good developer skills and understanding may be able to help, but as far as I know, no one with that level of skill hangs out in this forum, or has any interest in the I777 any more.
creepyncrawly said:
I was waiting to see if anyone else would pitch in with useful information about recovering your data. However, since no one has, I can say that I am pretty sure that you will not be able to recover anything currently in any of the system partitions. (System, kernel, data, preload, etc.) Once you recover your phone, you will still almost certainly have the information that was on your internal sdcard (USB Memory.)
Using Odin3, you should open Odin on the desktop of your pc first, then use the method that works for you to get into download mode, and Odin should recognize your phone.
I understand that you are not too concerned about the device. I would point out that a working I777 that is in good working condition with a clean esn is worth probably $100.00 to $125.00 on Swappa. It would be in your best interest to recover the phone. (Or if that's too much trouble, you can always send it to me, lol.)
Since the phone can enter download mode and be recognized by the computer, it is almost certainly recoverable. The only possible reason that it would not be recoverable is if the problem is due to damaged emmc memory in some part of the system partitions. When you flash the stock firmware, or any firmware, you will lose any possible access to the data partition. You will most likely be required to enter recovery after the flash to perform a wipe data/factory reset before the phone will boot into the system. The data will not persist as it would for an over the air or kies update. But again, as I said in the other thread, you may retain the game data if it is saved to the sdcard. Memo notes are definitely stored in the data partition, so those are lost.
The only thing you can do within download mode is flash firmware, nothing else is possible. I don't know of any other direction you could be going than what we have discussed so far.
As I said before, someone with good developer skills and understanding may be able to help, but as far as I know, no one with that level of skill hangs out in this forum, or has any interest in the I777 any more.
Click to expand...
Click to collapse
Yeah. It was worth a shot but I think I am out of luck on this.
I tried using Odin 3 v1.85 and also Odin 3 v3.09 from 2 separate computers with several cables in order to flash the PDA/AP from 'I777UCMD8_I777ATTMD8_I777UCMD8_HOME.tar.md5' but without any luck. After 10-20 minutes Odin says 'fail' and there is never any change on the phone screen at any point in the process. I also tried the 'I777UCKH7 OCD No BL.exe' one-click link from your signature links with a similar result. The program starts with factoryfs.img but the progress bar never moves and after 10-20 minutes it fails. The phone never shows any change at any point in the entire process.
I might be doing something wrong (perhaps with Odin I MUST flash the bootloader/phone/csc as well?) but it's looking more and more like the phone has a memory issue or something like that. Do you have any other suggestions? I'm willing to try anything at this point just to get the phone running for a few weeks while I decide on the next phone (hmmmm, Nexus 5, OnePlusOne, G3 or...)
Regardless of all that, thanks for all your help so far!
Both of those packages are complete in themselves. On the UCMD8 you only need the one tar in the PDA slot.
To discover if there is nand read/write corruption try this:
Instructions to clear nand read/write corruption. Instructions are specific. Do in order, and don't skip.
Odin3 v1.85 is recommended.
1) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning
2) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
3) If that is successful you are done. If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
For the record, no one writes those kinds of instructions as well as you do - both you and 4-2ndtwin have been great examples of how to help people for many years.
Thank you both for showing the rest of us how to convey help in an eloquent manner.
I tried your instructions with both v1.85 and v3.09 and although there was a brief glimmer of hope it looks like my device really is locked up beyond any further use. Odin shows the 'KERNEL' flash and the progress bar fills up in a second or two but then it goes to '<ID:0/003> NAND Write Start!!
' and like every other attempt it either hangs here indefinitely or fails after 10-20 minutes.
The only other things I can think of is to do a repartitioning or to physically disassembly the phone to look for any trouble spots (maybe a little dust or corrosion is shorting something) but of course being realistic there is virtually no chance of these having an effect.
I don't frequent the boards enough to know the standards here but I can say thank you for all the help you have provided. It's more than anyone can ask for such an old (but still good!) device.
Maybe it will take a jtag repair to get it going again, or perhaps there is actual eMMC damage, which can also be repaired. Whatever the problem is, a good option at this point would be the folks at Mobile Tech Videos repair shop. They have an excellent reputation here in the forum, and can do all sorts of repair.
This is a totally stock XT1527 - never been connected to a computer, never been connected to the Internet. I did a factory reset from the Backup & Reset menu. Now when starting the phone it takes me into fastboot. Checking the logs I see "Failed to validate boot image". I scroll to recovery and it takes me back to fastboot and I see "failed to validate recovery image" in the logs. The bootloader is currently locked and I'd like to keep it that way if possible, because in this case I would like a totally stock phone. What is my best course of action from here? Unfortunately, the phone has been sitting in it's box for over a month since I bought it, so I doubt if I can exchange it for a new one from Amazon.
Edit: I've obtained a copy of "SURNIA_RETUS_5.0.2_LXI22.50-24.1_cid9_subsidy-DEFAULT_CFC.xml.zip" which, if I understand correctly, I should be able to install without unlocking the bootloader. Does this file look correct for an XT1527 purchased from Amazon unlocked? I also notice one command in the installation process is "mfastboot oem config carrier vzw". This doesn't seem correct for my phone as it is GSM. Should I use this command, omit it, or replace vzw with something else?
Edit: Should I be worried about the hardware? As far as I can see there is absolutely no reason this should have happened. For the OS and Recovery to be wiped out during normal operation of a standard feature straight out of the box is pretty worrisome.
Update: This just keep getting stranger. After get thing error and rebooting the phone multiple times I decided to wait until later to do more work. I shut off the non-functional phone as well as an identical phone which did not have this problem. I put the phones in their original boxes and put them in my backpack. About seven hours later I take out the phones and they were both turned on and in the bootloader. I choose the start normally option and they both fully booted into the operating system. The phone which was previously reporting "failed to validate boot image" completely returned to the state it was in before I used the factory reset function. Can anyone explain what has happened here?
So i'm helping a buddy out that was having an issue with several Note 2's that were purchased from a company that restricted their employees access to a lot of things on the phone. My friend handed a couple off to me. The first one was not passcode locked and it was a breeze (Basically just enabled USB Debugging). It is up and running. The other ones are passcode locked and when you try to go into wipe the data/factory reset from recovery it says "MDM does not allow factory reset". The Note 2 I'm having issues with in particular has a locked bootloader on KitKat 4.4.2 through Verizon.
I've spent almost literally every waking moment trying to find a way around this issue. I may have compounded it though. I discovered ODIN, flashed the stock firmware in the hopes that it would clear the phone. It did not (password was still in place). I then decided to flash the stock firmware with the .Pit file for an SCH-I605 and made sure re-partition was checked as well as erase nand. After the process completed successfully and the phone rebooted it will no longer boot beyond the Verizon screen. I still have access to recovery and download mode but in recovery its throwing out a bunch of command lines such as E:failed to mount /data etc. I've tried to reflash the stock firmware with and without the .pit file to no avail.
In the mean time I've tried to unlock the bootloader, attempted auto root, and install custom recoveries to see if I could some how get around the MDM issue. I've also attempted to install or flash from ADB and its still the same deal.
Anyway I'm tired, kind of exhausted, and not really sure what avenues I have left. That's where I'm hoping some of you guys come in. If you have any questions for me let me know and I'll try to shed some more light on it for you. Data DOES NOT matter to me so if you can think of anyway I can get this thing completely wiped out it so I can start from scratch it would be greatly appreciated, Thanks.
Is it just one phone with this problem or several? The mounting issues are becoming more common around here, and seem to be internal memory failure.
http://forum.xda-developers.com/note-2-verizon/help/stuck-boot-file-exists-t3286946
Droid_Nut said:
Is it just one phone with this problem or several? The mounting issues are becoming more common around here, and seem to be internal memory failure.
http://forum.xda-developers.com/note-2-verizon/help/stuck-boot-file-exists-t3286946
Click to expand...
Click to collapse
Well tonight I'll be getting my hands on a couple other test SCH-i605 phones that are in the same situation (Password locked and no ability to wipe from recovery) and I'll put them through the paces to see if I wind up with the same issue and get back with you on it.
The basic issue with this phone is just after trying that repartition with the pit file it doesn't want to boot beyond the verizon logo anymore and thats when it started throwing those errors in recovery. It could be a coincidence I guess.
I've been messing with Heimdall today to see if I could get a custom recovery flashed that way but the phone fails protocol initialization. The only thing I can get to flash to this phone is 4.4.2 and the i605 pit file through ODIN. Nothing else will budge.
I guess the question I really need answered, is there another way to wipe data/factory reset without the option in the stock Samsung recovery and no access beyond the lock screen?
What I have to work with is ODIN mode and whatever is in recovery that is not wipe data/factory reset.
So I did get my hands on a couple other phones with passcode locks that have the MDM lockout within the stock recovery that still fails to flash anything in Odin except the stock 4.4.2 firmware. So I can eliminate the idea its hardware. I have 4 phones here 3 of which have the same issue and the 4th I was lucky enough to not have a passcode. Quick fix to get MDM removed that way.
Again any ideas that are slightly more outside the box would be appreciated. Thanks.
Edit: If this helps the phone that is working that I manage to clean all of that stuff off of also throws the same error in ODIN with or without USB debugging so it leads me to believe there is something I'm actually missing... Time to go read more.
Well, sound like it is more than coincidence. Maybe you should contact Samsung and see if they can help?
Yeah I might do that. I'd just hope they have a one size fits all solution because I have about 600 to 1000 phones to tackle... Hahaha.
The conundrum here is that for the MDM company to release the lock on the phone I have to be able to get beyond the lock screen for the phone to process the request. To get beyond the lock screen I need the psswords that the previous company allowed their employees to put on the phones that for some odd reason they didn't have remove.
Anyway if I get this figured out i'll let you guys know how I got it. Thanks for the suggestion.
((deleted))
When I had my Tab rooted, it would occasionally crash and fail to turn off properly or respond. I had to use the vol buttons and power button to turn off the Tab. Anyway, since I flashed stock rom and lost root and TWRP the Tab has been fine. Maybe my first root glitched something. I notivced when my tab was rooted it displayed three messages during the boot up process. The only one I could not read was on the top left corner and I think the text was red and had two lines but the message was only displayed for like half a second I am was never able to see what it said. Tthe next message I think was about bootloader being unlocked and then not running official FW (TWRP I guess). I think tghose two message were displayed at the same time.
For all those with rooted Tab does your Tab display that first message on the top left corner or just the bootlaoder and offical FW message?
The first warning you'll really see is that the bootloader is unlocked. The second warning in Red writing is a message about "Not using stock firmware" and is expected after installing TWRP because you've replaced stock recovery with custom recovery.
But... before either of them are loaded and shown, there is a flash of three lines of yellow text (which I believe you are referring to) which states as follows...
Set Warrenty Bit : vbmeta
Set Warrenty Bit : Kernel
Set Warrenty Bit : Dtbo
I imagine the above messages have something to do with Knox's security protocols.
Now, some quick Googling tells me Vbmeta is used for "Verified Boot" and basically tells you if the OS has been tampered with. So I guess it makes sense that it shows up since the system has been tampered with to provide Root privileges - or it could be flagged that TWRP has replaced stock recovery.
Kernel is pretty straight forward, you flashed a custom Kernel when you rooted, so like Vbmeta it is also flagged.
I'm unclear with exactly what Dtbo is, though it seems to be an acronym for "Device Tree Blob for Overlays". I'll leave it there, maybe someone who knows it's function can give us an ELI5 on it.
So, in summary, it is indeed present on my Tablet and wasn't the cause of your issues - Which is what I suspect you were really curious of?
I think you're probably right with the assumption that something did occur during your initial attempt at rooting which caused a corruption in the /System which lead to you having problems powering down. I too experienced some occasional random reboots on my first attempt at rooting, which haven't been present since I was forced to reinstall stock, then TWRP & root again after I corrupted /system and got stuck in Bootloop when messing with EdXposed.
Thanks! That's helped me out. I might re-root later on when i have time. Take care
I stumbled upon a peculiar message I've never faced before, right after my Note 9S has rebooted to OrangeFox recovery out of the blue. According to it, a particular thing had caused my phone to enter rescue mode (for additional information, look at the attached screenshots). I have absolutely no clue what could've been the culprit behind this disaster. All I did was trying to install an APK file that I'm convinced was not corrupted. Funny thing, the installation didn't even commence. I presume a few newer Telegram builds have a problem launching Package Installer the proper way (at least, that is on the current ROM I use). As far as I know, an app kept crashing in the foreground before the installation could've gone ahead.
Viable solutions around the problem are the following, with the risks escalating
1. Unmount SD card and transfer the Magisk uninstaller ZIP. After having unrooted the device, clean flash the ROM without any snags.
2. Embark on flashing with root access present. If something fools around reboot to recovery and start over.
3. Nothing special, attempt booting to system and see if the error message was a false alert (it could've been, considering Package Installer isn't an inherent part of the system).
Which one of these do you endorse? Maybe an alternative course of action?
PS: The filesystem doesn't seem to be corrupted. I haven't flashed anything so far, only created a backup of my files placed within Internal Storage. I haven't messed around with the PMIC but the battery percentage remains stagnant in OrangeFox when the screen turns off after having attained the timeout deadline; unsure if that's normal behaviour. I've installed Adreno Team Exclusive Thermals, anticipating to cut back on overheating (up to 39 °C) while charging.
It's crucial for me to act in a meticulous way, given that the phone might not boot up next time. I'm not at all conscious how bleak the situation is, though.
Randomly rebooted to recovery but still loading. I really hope it's not stuck there.
I'll see if fastboot commands work as soon as I get to use my computer wich has my phone authorised
Since no one has taken the trouble to guide me through the necessary steps, I attempted to do it on my own. Fortunately, my laptop recognized the device, allowing me to tackle with the boot loop. Before doing so, I sought to boot into system (it was the first time I've done this after being stuck in OrangeFox) and everything worked just fine. It was only a false alert.