Hello friends!
I have been trying to install new Rom to Note 5 Sprint, used ODIN and after installing was successful, my phone went to "Android Recovery"
it says DM-Verity Verification Failed Need to check DRK first..
When i try to connect with my PC nothing happens, it cant see the device.
On my phone when i try to APPLY UPDATE FROM ADB- it says "Update from external storage is disabled"
Please help...
install a custom kernel.
What about if you are OEM locked? My device won't boot. Give the DRK message. What are my options? Is there any way to OEM unlock when the device won't boot. I can't flash a recovery or kernel unless it is stock. I have backup files for the EFS but my device won't connect to ADB. Help me please. Lol
Hello,
A few days ago I found my Motorola Moto G Turbo, model MERLIN XT1557 , turned off. When I switched it back on, it did not boot successfully but instead redirected to the bootloader with the message:
"Your device didn't start up successfully. Use the Software Repair Assistant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant."
"AP Fastboot Flash Mode (Secure)"
"failed to validate boot image"
"ERROR: Failed to pass validation, backup to fastboot"
"Fastboot Reason: Fall-through from normal boot mode"
"CID Read Failure"
"Invalid CID status 0x69"
I have not unlocked the bootloader or tried to install any custom firmware. As far as I can tell, this occurred spontaneously and without warning (my best guess would be an update that went wrong). For this reason, I have not enabled USB debugging either, so the phone doesn't even let me unlock the bootloader.
Recovery mode does not work, this merely gives the message "failed to validate recovery image". Nor do "Factory", "BP Tools" or "QCOM" do anything (barcodes works). Thus even if I wanted to perform a hard reset, I cannot seem to do it.
Strangely, I seem to be able to access two different types of bootloader interfaces, one with just text and another with a picture of an android. Neither seem to be of much help, however interestingly the one with the android picture states "Software Status: Official" while the pure text one sometimes (not always for some reason?) states "Software Status: Modified". Again, just to reiterate, I haven't performed any custom android modifications.
After all i tried to flash stock firmware, it installed successfully without even a single error and then again the same thing starting to happen, firmware installed but didn't solved the problem, same dual bootloaders menu start appearing.
ok, at last i am able to just boot into my phone,
used
fastboot oem config bootmode factory
Click to expand...
Click to collapse
and reboot. Phone opened in factory mode but still recovery is not accessible.
Working on figuring how can i get into recovery. Flashed twrp, didn't booted in recovery, flashed stock recovery, same result..
Hi everyone,
so I have an Honor 8 with stock ROM, USB Debugging disabled, locked Bootloader and it is stuck in a boot loop after an update.
ADB does not recognize the device, fastboot does, but rejects any command.
The recovery screen shows in green letters "phone locked".
I suppose that's the worst case scenario.
E-recovery failed with the usual errors "getting package info failed" and "device is not supported".
I have two questions:
1. Is it in any way possible to access the internal storage, e.g. DCIM to download media files?
2. If 1 is not possible, can I rollback the update or flash a new ROM to get the phone running again?
I read "solutions" to factory reset the phone and then run some data recovery tools to reconstruct the data, but I would like to avoid wiping the data partition if it can be avoided.
Thanks for any answer and kind regards,
Martin
I went through the process of using Smali and Magisk on my phone. Everything was good. Since I was doing this for PoGo, I decided to "clean-up" by disabling some of the settings. I turned off OEM unlocking, reboot the phone in to the bootloader and did a adb flashing lock. I rebooted the phone and not get the error "Can't find a valid operating system". I can boot in to the bootloader with the power button + down volume but I can't unlock the bootloader with ADB and fastboot.
Am I screwed?
I'm also not able to boot in to recovery. I also get the error "Can't find valid operation system"
Well probably too late to reply.
I'm not an expert, i'm newbee but when i installed my custom rom i met some problems to reboot. I solved them by re-installing firm operating system. You can do it by connecting your device with a good usb cable and go to google website : android flash tool
This will reinstall a new an clean system (but erase your data if not saved before).
After that you can install a custom rom from the begining.
Hello everyone,
I need some help with the following situation:
Using Odin I successfully flashed my Galaxy A32 5G with Android 13 (as indicated by the green PASS in Odin).
When the phone tries to reboot, I get the dreaded error message, "Can't load Android system. Your data may be corrupt....."
On my PC I issued the command, >adb devices, but no devices were found.
This is probably because I did not enable USB debugging, when the phone was still working.
I'm trying to avoid doing a factory reset, because I don't want all my data wiped.
According to the following article, you can flash an OTA file using "adb sideload" command, even without enabling USB debugging.
However, everything else I've read says that adb commands work only when USB debugging is enabled.
Fix “Can’t Load Android System Your Data May Be Corrupt” Without Resethttps://www.droidwin.com/fix-cant-load-android-system-your-data-may-be-corrupt-without-reset/
Can someone perhaps clarify whether or not USB debugging is required for using adb commands?
Thank you very much,
Peter
plee12 said:
Hello everyone,
I need some help with the following situation:
Using Odin I successfully flashed my Galaxy A32 5G with Android 13 (as indicated by the green PASS in Odin).
When the phone tries to reboot, I get the dreaded error message, "Can't load Android system. Your data may be corrupt....."
On my PC I issued the command, >adb devices, but no devices were found.
This is probably because I did not enable USB debugging, when the phone was still working.
I'm trying to avoid doing a factory reset, because I don't want all my data wiped.
According to the following article, you can flash an OTA file using "adb sideload" command, even without enabling USB debugging.
However, everything else I've read says that adb commands work only when USB debugging is enabled.
Fix “Can’t Load Android System Your Data May Be Corrupt” Without Resethttps://www.droidwin.com/fix-cant-load-android-system-your-data-may-be-corrupt-without-reset/
Can someone perhaps clarify whether or not USB debugging is required for using adb commands?
Thank you very much,
Peter
Click to expand...
Click to collapse
I think, In stock recovery only the adb sideload command works so it don't need USB Debugging to be turned ON.
aiSanaul said:
I think, In stock recovery only the adb sideload command works so it don't need USB Debugging to be turned ON.
Click to expand...
Click to collapse
Thanks for your input. Encouraged by your input, I read the article again and realized that I have to put the phone in sideload mode first.
So, I went back to the stock recovery mode and selected the menu item, "Apply update from ADB". Then I see the message on the phone, "Now send the package you want to apply....with adb sideload <filename>". Now that I thought the phone was in sideload mode, on the PC I entered ">adb devices". This time it recognized the device and displayed the device name. However, it also displayed the word, "unauthorized", after the device name. According to the article, if sideload is properly entered, it should display the word, "sideload".
Anyway I tried entering ">adb sideload update.zip", and I got the error message, "device unauthorized".
So, any idea how to get the phone to be authorized?
If this is not possible, I was thinking of replacing the stock recovery with a custom recovery like TWRP. This way I can at least back up all my data first before doing a factory reset. However, I believe installing TWRP requires the bootloader to be unlocked, which automatically wipes all data. So, this defeats the purpose of installing TWRP in the first place
Is there some trick to install TWRP without unlocking the bootloader?
Thank you
plee12 said:
Thanks for your input. Encouraged by your input, I read the article again and realized that I have to put the phone in sideload mode first.
So, I went back to the stock recovery mode and selected the menu item, "Apply update from ADB". Then I see the message on the phone, "Now send the package you want to apply....with adb sideload <filename>". Now that I thought the phone was in sideload mode, on the PC I entered ">adb devices". This time it recognized the device and displayed the device name. However, it also displayed the word, "unauthorized", after the device name. According to the article, if sideload is properly entered, it should display the word, "sideload".
Anyway I tried entering ">adb sideload update.zip", and I got the error message, "device unauthorized".
So, any idea how to get the phone to be authorized?
If this is not possible, I was thinking of replacing the stock recovery with a custom recovery like TWRP. This way I can at least back up all my data first before doing a factory reset. However, I believe installing TWRP requires the bootloader to be unlocked, which automatically wipes all data. So, this defeats the purpose of installing TWRP in the first place
Is there some trick to install TWRP without unlocking the bootloader?
Thank you
Click to expand...
Click to collapse
As you already know this is not possible without unlocking bootloader, I will explain further more to make it easy to understand.
If you don't unlock your bootloader and try flashing TWRP on your phone using ODIN Flash Tool then maybe your phone get into an veification error and your phone will end up in a softbrick. You can repair your phone by flashing your phone's stock firmware using ODIN Flash Tool, eventually you will wnd up loosing all your data.
Also unlocking bootloader in Samsung devices is so easy by turning OEM Unlocking in Developer options, but you don't seem to have access to your phone.
An Unlocked Bootloader is the PASS, which allows you to do custom thing to your phone. So without it, this won't work, maybe that is why you got that error “Can’t Load Android System Your Data May Be Corrupt”.
ALTERNATIVELY you can try flashing your phone's OLD original Stock Firmware using ODIN Flash Tool and see what happens. You can also try flashing TWRP through ODIN Flash Tool. Only flash OFFICIAL TWRP made for your device (if any), otherwise you don't have options I guess.
also Why didn't you Unlocked Bootloader before flashing a custom rom? because of warranty?
aiSanaul said:
As you already know this is not possible without unlocking bootloader, I will explain further more to make it easy to understand.
If you don't unlock your bootloader and try flashing TWRP on your phone using ODIN Flash Tool then maybe your phone get into an veification error and your phone will end up in a softbrick. You can repair your phone by flashing your phone's stock firmware using ODIN Flash Tool, eventually you will wnd up loosing all your data.
Also unlocking bootloader in Samsung devices is so easy by turning OEM Unlocking in Developer options, but you don't seem to have access to your phone.
An Unlocked Bootloader is the PASS, which allows you to do custom thing to your phone. So without it, this won't work, maybe that is why you got that error “Can’t Load Android System Your Data May Be Corrupt”.
ALTERNATIVELY you can try flashing your phone's OLD original Stock Firmware using ODIN Flash Tool and see what happens. You can also try flashing TWRP through ODIN Flash Tool. Only flash OFFICIAL TWRP made for your device (if any), otherwise you don't have options I guess.
also Why didn't you Unlocked Bootloader before flashing a custom rom? because of warranty?
Click to expand...
Click to collapse
Thanks very much for your detailed explanations and for your continued support.
Let me answer your question first about why I didn't unlock the bootloader before flashing a custom ROM. Let me backtrack and explain how this problem came about in the first place. My phone was doing an automatic system update two weeks ago (Android 13). After downloading and installing, it tried to boot up. That's when it got stuck in an infinite rebooting loop. At that point, I had no way to change any settings on the phone.
Also, to clear up any confusion, I was not trying to flash a custom ROM. I was simply trying to flash the stock ROM (Android 13), supposedly the same firmware version as the OTA that broke my phone after the automatic system update. I was thinking that perhaps there was an internet glitch during the automatic system update process, which corrupted the OS. So, I was just trying to re-install the same version as the OTA to see if that would solve the problem.
I had also thought about flashing the original version that came with the device (Android 11). But, I think I read somewhere that either Samsung phones do not allow the user to downgrade, or even if it does allow you do so, the downgrading process will wipe out the existing data on the phone. Perhaps you can confirm that or not?
In the meantime, as you suggested, I will look into how to flash TWRP.
Thank you