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
Related
After trying to flash Superuser-r275 and failing all the time. As a result of error called(No MD5 file were found). i found Super Su 2.79.
i flash my phone with it and then it boot and works perfectly except for one thing, i cannot open the Gallery or access the internal storage in any way. So i tried to get the phone to stock and i failed as im not able to get to the internal storage. so i reboot in recovery and then to bootloader and i put the command "fastboot reboot oem relock xxxxxxxxx" and press yes to lock bootloader and twrp will be removed. i selected yes and the phone reboot into huawei eRecovery mode and never Recover.
i still cant get access to the internal storage and i have lost twrp recovery.
there is any way to get it working again ?
malik11111 said:
After trying to flash Superuser-r275 and failing all the time. As a result of error called(No MD5 file were found). i found Super Su 2.79.
i flash my phone with it and then it boot and works perfectly except for one thing, i cannot open the Gallery or access the internal storage in any way. So i tried to get the phone to stock and i failed as im not able to get to the internal storage. so i reboot in recovery and then to bootloader and i put the command "fastboot reboot oem relock xxxxxxxxx" and press yes to lock bootloader and twrp will be removed. i selected yes and the phone reboot into huawei eRecovery mode and never Recover.
i still cant get access to the internal storage and i have lost twrp recovery.
there is any way to get it working again ?
Click to expand...
Click to collapse
sorry,by saying access internal storage u mean thru system or thru twrp?have u tried to unlock BL again n reflash twrp?
malik11111 said:
After trying to flash Superuser-r275 and failing all the time. As a result of error called(No MD5 file were found). i found Super Su 2.79.
i flash my phone with it and then it boot and works perfectly except for one thing, i cannot open the Gallery or access the internal storage in any way. So i tried to get the phone to stock and i failed as im not able to get to the internal storage. so i reboot in recovery and then to bootloader and i put the command "fastboot reboot oem relock xxxxxxxxx" and press yes to lock bootloader and twrp will be removed. i selected yes and the phone reboot into huawei eRecovery mode and never Recover.
i still cant get access to the internal storage and i have lost twrp recovery.
there is any way to get it working again ?
Click to expand...
Click to collapse
Unlock bootloader, flash stock recovery, relock bootloader. I don't see how this will help you get stock back though. Or do you mean you can't access download mode again?
Anyway, relocking bootloader won't make your phone stock.
And did you decrypt before flashing SuperSU (Format Data in Twrp)?
ante0 said:
Unlock bootloader, flash stock recovery, relock bootloader. I don't see how this will help you get stock back though. Or do you mean you can't access download mode again?
Anyway, relocking bootloader won't make your phone stock.
And did you decrypt before flashing SuperSU (Format Data in Twrp)?
Click to expand...
Click to collapse
first of all i cant access the internal storage from the operating system. or from a computer.
if i open Gallery or Music in my phone i would get a massage saying "insufficient storage free some space blah blah blah" and it take to clean memory. and if i try that through a computer it says that the devices has been disconnected or no is unavailable.
Secondly, how can i get to bootloader again? the device show up when i plug it to my computer but i can't see it in terminal when i use adb. there is a way to access the device in this situation ?
malik11111 said:
first of all i cant access the internal storage from the operating system. or from a computer.
if i open Gallery or Music in my phone i would get a massage saying "insufficient storage free some space blah blah blah" and it take to clean memory. and if i try that through a computer it says that the devices has been disconnected or no is unavailable.
Secondly, how can i get to bootloader again? the device show up when i plug it to my computer but i can't see it in terminal when i use adb. there is a way to access the device in this situation ?
Click to expand...
Click to collapse
if there is a way and i get the bootloader unlocked again, can someone explain how to "decrypt before flashing SuperSU (Format Data in Twrp)?"
Thank you guys.
malik11111 said:
first of all i cant access the internal storage from the operating system. or from a computer.
if i open Gallery or Music in my phone i would get a massage saying "insufficient storage free some space blah blah blah" and it take to clean memory. and if i try that through a computer it says that the devices has been disconnected or no is unavailable.
Secondly, how can i get to bootloader again? the device show up when i plug it to my computer but i can't see it in terminal when i use adb. there is a way to access the device in this situation ?
Click to expand...
Click to collapse
First (If you don't have Developer Settings in Settings) go to Settings - About and tap on Build Number a few times until it says "You're now a developer". Go back and tap on Developer settings and turn on usb debugging. Now see if adb wants to work. If it does use "adb reboot bootloader", else hold Vol Down + Power, release power when phone has rebooted and vibrated again. Download mode should display kind of instantly. Try if fastboot works.
For root, follow this: https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986
i tried the to connect the phone to my computer and hold the power down. and i got into the bootloader mode but i could not flash twrp again or flash the phone to stock.. alos i found that FRP is locked. what to do in this case guys.
Enable oem unlock in developer settings, to disable FRP LOCKED in fastboot mode
the device does not boot at all
im stuck on the eRecovery page.
ok guys i have found a way out of the problem that i was stuck at, i open the phone through a an application called DC phoenix and i could boot the device
but now i would like to get my phone back to its stock Rom. how can i do that? i tried couple of different ways but i get error when it come to install the package|_type? any idea?
Please note that dc phonix has deleted the IMEI for the device and Serial Number
now i have like IMEI:000000000000 and serial number :0123456789ABCDE
please if anyone know a way let me know guys.
I'm in way over my head guys, so here's my situation:
I have no OS installed, for some reason I can't get into TWRP anymore (it goes to eRecovery instead).
I CAN get to bootloader screen (bootloader is unlocked).
adb does not recognize my device on device list command (it worked before, but now I can't get into the OS to turn on USB debugging and such...).
please help! I don't know what else to do!
liran96 said:
I'm in way over my head guys, so here's my situation:
I have no OS installed, for some reason I can't get into TWRP anymore (it goes to eRecovery instead).
I CAN get to bootloader screen (bootloader is unlocked).
adb does not recognize my device on device list command (it worked before, but now I can't get into the OS to turn on USB debugging and such...).
please help! I don't know what else to do!
Click to expand...
Click to collapse
I think the first step to fixing my phone is to get it recognized in the list of devices attached in adb.
how do I go about doing that?
In device manager I got it to recognize my phone as Android Phone > Android ADB Interface.
so I believe the drivers are updated, what else can I do to get my phone recognized in cmd adb?
If I need to provide any more details then please say, I am getting hopeless
Edit: I managed to get into TWRP. still no clue how to continue from here as I can't transfer any files from PC
I found a update.zip file on my phone's SD card, I can't remember which ROM version it holds, but when I try to flash it I get a few errors:
check_write_data_to_partition,write data error
E:unknown command [errno]
Update_huawei_pkg_from_ota_zip: update package from zip failed
Updater process ended with ERROR: 7
Error installing zip files '/external_sd/update.zip'
I think I managed to screw my phone up even more, I can no longer get into TWRP...
:crying:
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
Hey,
I installed GrapheneOS but want to return to stock rom.
Flash site doesn't work.
When in bootloader mode my phone is not detected. I know the drivers solution but Device Manager isn't even showing ANY device when in bootloader mode so I can't even change the drivers.
In recovery mode the phone IS detected but when sideloading the OTA file it stops at 47% (1xfer) and aborts the installation.
Flashboot doesn't work either, I get an error when trying to flash the bootloader img.
Flash-all doesn't work either, always fails at writing bootloader.
Android flash tool same problem, when the phone goes to bootloader mode Windows doesn't see the device anymore. No device to be found in device manager...
Anyone any idea. Really stuck now :s
Found the culprit... it was the cable... unbelievable :s
StarrOw said:
Hey,
I installed GrapheneOS but want to return to stock rom.
Flash site doesn't work.
When in bootloader mode my phone is not detected. I know the drivers solution but Device Manager isn't even showing ANY device when in bootloader mode so I can't even change the drivers.
In recovery mode the phone IS detected but when sideloading the OTA file it stops at 47% (1xfer) and aborts the installation.
Flashboot doesn't work either, I get an error when trying to flash the bootloader img.
Flash-all doesn't work either, always fails at writing bootloader.
Android flash tool same problem, when the phone goes to bootloader mode Windows doesn't see the device anymore. No device to be found in device manager...
Anyone any idea. Really stuck now :s
Click to expand...
Click to collapse
Sideload stopping at 47% is actually "normal". FYI.
JohnTheFarm3r said:
Sideload stopping at 47% is actually "normal". FYI.
Click to expand...
Click to collapse
Not when the next part is: installation aborted. It is normal when it is not a Google image.
StarrOw said:
Not when the next part is: installation aborted. It is normal when it is not a Google image.
Click to expand...
Click to collapse
Aborted installation happens quite often due to various reasons, it's very picky. NOT saying that aborted installations are normal, just saying sideload ending at 47% is "normal".
If you see log "xfer 1.0 successfull" after sideloading, everything is okey. If you don't see, i recommend you to use TWRP without "signature verification". Set this option off and try again.