Related
Hi guys.
My issue: I had TWRP 3.0.2.1 on my honor and decided to update to latest version. Big error.
I have the TWRP app installed and I followed the procedure to flash recovery with that app. It seemed everything was fine, because it said ""recovery flashed".
Now when I try to enter recovery, my phone gets stuck at logo "your device is booting now".
I have to reboot in EMUI recovery to go out from that stuck page and to load normally the phone.
So I decided to flash recovery in the old ADB fashioned way: now when I get to "fastboot flash recovery twrp.img", the phone tells me "FAILED (remote: Command not allowed)"
Practically now I have no TWRP and I do not know how to proceed.
Some good Samaritan out there?
Thanks.
My firmware is latest Nougat (BLN-L21C432B360).
I tried to flash TRWP 3.1.1. Before this try, I had version 3.0.2-1 as written above. I flashed twrp when I still had Android 6 with EMUI 4.
Regarding the way to enter TWRP, yes, I know the method and I do it.
The problem is my phone don't enter twrp but remain stuck at logo.
It seems that the recovery is not present or has problems.
I've tried even to reflash the old recovery, just in case. Nothing.
Try this-
flash stock recovery for your model.
boot normally.
flash TWRP latest.
Now I try and post later.
What a mess. I should leave the old 3.0.2 which was working good...
I was already on nougat and the 3.0.2 was still working perfectly. I had flashed that twrp when I was still on 6.0 and after the update with firmware finder it was still working.
Moreover I used the official TWRP app to update and it failed miserably even if it said flash successful at the end of operation....
Then I used the classic way with ADB and still nothing.
I can see on the Windows shell "failed: command not allowed"
Rommco05 said:
Frp in fastboot is unlocked?
Click to expand...
Click to collapse
AFAIK, Factory Reset Protection is linked to account protection in case someone steals the phone. In this way it should be more difficult to wipe completely the phone and use it.
Anyway, just checked in fastboot and no, FRP is locked. I just had a look in developer options and I noticed that "Enable OEM unlocked" is greyed out. But it should not have nothing to do with flashing the recovery.
Or not?
Let's see
Diamantes said:
Hi guys.
My issue: I had TWRP 3.0.2.1 on my honor and decided to update to latest version. Big error.
I have the TWRP app installed and I followed the procedure to flash recovery with that app. It seemed everything was fine, because it said ""recovery flashed".
Now when I try to enter recovery, my phone gets stuck at logo "your device is booting now".
I have to reboot in EMUI recovery to go out from that stuck page and to load normally the phone.
So I decided to flash recovery in the old ADB fashioned way: now when I get to "fastboot flash recovery twrp.img", the phone tells me "FAILED (remote: Command not allowed)"
Practically now I have no TWRP and I do not know how to proceed.
Some good Samaritan out there?
Thanks.
Click to expand...
Click to collapse
Unlock your boot loader
Bootloader is unlocked.
For some reason, my "OEM unlocked" option turned greyed out, and FRP is locked again.
I will try this eve to lock bootloader again and restart the unlocking operation from scratch.
Will see
Diamantes said:
Bootloader is unlocked.
For some reason, my "OEM unlocked" option turned greyed out, and FRP is locked again.
I will try this eve to lock bootloader again and restart the unlocking operation from scratch.
Will see
Click to expand...
Click to collapse
In emui 5 OEM unlock option is not there and can only be found in MM or Emui 4.x
you mean that even if I can't access TWRP, this should be still there and I cannot lock bootloader?
And you advice to do a factory reset first.
If this doesn't work? Then?
shashank1320 said:
In emui 5 OEM unlock option is not there and can only be found in MM or Emui 4.x
Click to expand...
Click to collapse
You mean that I couldn't even see the option?
I have nougat and emui 5, the option is present but greyed out
Diamantes said:
You mean that I couldn't even see the option?
I have nougat and emui 5, the option is present but greyed out
Click to expand...
Click to collapse
Yeah exactly. See SS
This was there till emui 4
So how can I solve the problem?
Someone told me the only way is to lock bootloader in order to have again this option available to be turned on... And so start the process again.
At the moment I cannot access TWRP nor flash it through ADB. Practically even if bootloader is unlocked, I have a rooted phone with no possibility to do anything else... Regarding flashing of course.
Thank you for your replies.
Anyway I really know now that I cannot buy honor for flashing.
I just tried a factory reset from advanced options.
After all the pin request etc, the phone rebooted and get stuck on the initial window (your phone has been unlocked and cannot be trusted-your phone is booting now...).
So I had to press usual buttons to enter in emui recovery, the only way I can get the rebooting option from this state.
Of course the phone is not reset.
I give up. This crappy phone is taking too much time of my life.
I will keep it like this. And I'm not sure at all I will get future OTA update.
I never EVER had these issues with Samsung phones or HTC, and believe me that I was flashaholic... I flashed tens and tens of ROMs, I rooted and unlocked all my previous phones with no glitches or whatever..,
This time I tried honor for the price.
Never again for flashing or playing around.
Just for normal, classic phone use, hoping it will last some other month before I purchase another brand.
Thank you all.
Of course my thoughts about this ****ty phone were all right.
I received the ota update for version b365, downloaded and OF COURSE STUCK at boot logo after automatic restart...
I will never be able to install anything else because the recovery is corrupted.
I am condemned to stay with b360 until this cursed phone will die for natural causes...
No comment
Diamantes said:
Of course my thoughts about this ****ty phone were all right.
I received the ota update for version b365, downloaded and OF COURSE STUCK at boot logo after automatic restart...
I will never be able to install anything else because the recovery is corrupted.
I am condemned to stay with b360 until this cursed phone will die for natural causes...
No comment
Click to expand...
Click to collapse
But recovery can be changed mate. Try twrp with new thread in my signature and follow steps, it won't be a trouble. Try once in free time as i know you already are frustrated with trying all ways.
The TWRP on official TWRP site sadly won't work for our berlin devices, i neither know why it is still there sincerely. Personally i can't recommend the usage of TWRP official app for our phone as it downloads a wrong version... you have to get the OpenKirin edition from here https://forum.xda-developers.com/honor-6x/development/twrp-t3583413 and flash that via adb fastboot. Be sure to have "USB debug" on by developer options menu, and to have installed HiSuite (just to have all the functional drivers)
I thank you all for your patience and replies.
But as Shashank said, I'm really frustrated because I tried everything in the past.
Now I'm rooted (luckily) but with FRP locked. It seems the reason why I cannot flash nothing.
In any case I will try again the suggestion of redskull. The last hope!
Thanks.
I spent all day trying to find a way to root my phone after moving from Lineage OS to Oxygen OS 10.01. Namely, https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853.
The problem is that the information given is out of date as of a few days ago, and installing the patched bootloader broke wifi, calling, and probably all sorts of other things.
I want to make sure this is as simple as possible for people having the same issues!
Before You Download
You MUST be running Oxygen OS 10.01 exactly.
You MUST be on a OnePlus 6 (not a OnePlus 6T)
You MUST have an unlocked bootloader (Google for instructions, "fastboot oem unlock", this will require a factory reset)
Install ADB and Fastboot on your computer (Google for instructions)
Installation Instructions
Make sure you're running Oxygen OS 10.01 for the OnePlus 6. If you're on an earlier version and need to install, download HERE and install it as a local upgrade (Google for instructions).
Download and install Magisk Manager. I'm using Version 7.40.
Download my modified boot image here
Put your OnePlus 6 in Fastboot mode and plug it into your computer (Google for instructions)
Place my boot file, new_boot_image_xda.img, in the same folder Fastboot is running
Run fastboot flash boot new_boot_image_xda.img
Run fastboot reboot or otherwise reboot your phone.
If you want to do this on other devices:
Extract boot.img from your ROM's zip file's payload.bin using Payload Dumper 64 (I can't post external links, Google it)
Place boot.img in your phone's local storage
Open Magisk Manager on Android, then "Install Magisk" -> "Patch a File" -> select boot.img
Move the modified boot image (magisk_patched.img) to your computer
Enter the fastboot commands from above, replacing new_boot_image_xda.img with your modified boot image
May be a dumb question: Do I lose data? There's no step of wiping, but I'm afraid this may be necessary.
Oh, and another question: how about updates? Will I lose my data on further updates?
And I'm sure I need to unlock my bootloader before.
jacdelad said:
May be a dumb question: Do I lose data? There's no step of wiping, but I'm afraid this may be necessary.
Oh, and another question: how about updates? Will I lose my data on further updates?
And I'm sure I need to unlock my bootloader before.
Click to expand...
Click to collapse
Unlocking the bootloader triggers a factory reset (nothing in internal storage is lost, but you lose apps and settings), and you need to do this before rooting. If your bootloader is unlocked, you shouldn't have to wipe anything unless you miss an instruction or install it on the wrong version. You won't be able to update OTA without losing root.
If you're new to rooting, just be prepared to lose your data no matter what, because it's incredibly easy to follow the wrong advice and end up bricked. There have been times where the only thing my OP6 can do is display a white LED because with the wrong command, I wiped everything from the boot partition, recovery partition, and internal storage. For that reason, you might wait a week or so for more documentation on rooting this phone with this version of OOS.
mouthofrandom said:
Unlocking the bootloader triggers a factory reset (nothing in internal storage is lost, but you lose apps and settings), and you need to do this before rooting. If your bootloader is unlocked, you shouldn't have to wipe anything unless you miss an instruction or install it on the wrong version. You won't be able to update OTA without losing root.
If you're new to rooting, just be prepared to lose your data no matter what, because it's incredibly easy to follow the wrong advice and end up bricked. There have been times where the only thing my OP6 can do is display a white LED because with the wrong command, I wiped everything from the boot partition, recovery partition, and internal storage. For that reason, you might wait a week or so for more documentation on rooting this phone with this version of OOS.
Click to expand...
Click to collapse
Nah, no problem. I have this phone since it came out and use custom ROMs since then, do not really new. I know that unlocking the bootloader resets my phone. I was just wondering if I can install your image without unlocking, because I'm currently locked (had a problem with the latest Syberia update and choose to stay with OOS). And how to update when OOS 10.0.2 arrives.
I tried it and it worked fine, but today after uninstalling some blotware and rebooting I am stucked on the bootloader warning page which takes me to the fastboot mode after a minute or so (this is what used to happen to me whenever I flash a magisk patch boot file) Now I'm downloading the stock rom to get the stock boot.img.
This one video is for oneplus 6t
Pretty clean guide
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.
hi guys,
my op6 is running stock oos with magisk as root. My phone worked fine for several months. Today I tried switching magisk from the stable version to canary by first upgrading the manager app and then hitting the direct install option. This failed several times and I got an error saying:
! Unable to unpack boot image
I thought this could be fixed by a reboot, but well... it wasn't. Now the phone only boots into the bootloader. I booted into twrp and tried to uninstall magisk via the uninstall.zip. This fails with error
-Unpacking boot image
! Unsupported/Unknown image format
- Unmounting partitions
cd /tmp/repackorig/ && /sbin/magiskboot unpack -h '/tmp/repackorig/boot.img' process ended with ERROR: 1
Error unpacking image
I don't really know what this means. I'm guessing my boot.img is corrupted?
Is there any way I can solve this problem without a factory reset? Can I just flash the stock boot.img via fastboot?
Do you have any idea what went wrong here, so that I can avoid the error next time?
Yesterday I broke op5 during the magisk update. The repair was simple, flash stock boot.img as boot partition.
I flashed it from TWRP.
Try dirty flashing your ROM without flashing magisk.
I'm also facing the same issues. Tried updating from the Magisk App. Didn't receive any error messages. After reboot I'm stuck in fastboot mode and I cannot access recovery. I do not have a backup of the data on this phone.
Is there any way I can still (temporarily) access the data? I'm panicking a little bit. My OOS is stock and rooted and hasn't been updated in about a year. I'm not sure if I can still figure out the specific OOS version that is installed.
EDIT:
Have been trying to flash the stock boot.img with fastboot. I've tried both 10.0.1 and 10.3.0 so far. Both resulted in the "BOOTLOADER UNLOCKED" warning and got stuck there. 10.3.1 is my last option, because I don't think I've updated this device since. Would it make a difference if I tried to do it from twrp?
EDIT2:
I do however have access to the recovery mode now. If I'm not mistaken this means I might be able to extract the data.
EDIT3:
The recovery mode is not asking me for my unlock pattern (which I think it should be doing) and is not showing up under 'adb devices'. I've tried flashing the boot.img of all OOS versions I can think of with fastboot, nothing will let me boot back in or let me access adb through the recovery. Am I ****ed?
MoresM said:
I'm also facing the same issues. Tried updating from the Magisk App. Didn't receive any error messages. After reboot I'm stuck in fastboot mode and I cannot access recovery. I do not have a backup of the data on this phone.
Is there any way I can still (temporarily) access the data? I'm panicking a little bit. My OOS is stock and rooted and hasn't been updated in about a year. I'm not sure if I can still figure out the specific OOS version that is installed.
EDIT:
Have been trying to flash the stock boot.img with fastboot. I've tried both 10.0.1 and 10.3.0 so far. Both resulted in the "BOOTLOADER UNLOCKED" warning and got stuck there. 10.3.1 is my last option, because I don't think I've updated this device since. Would it make a difference if I tried to do it from twrp?
EDIT2:
I do however have access to the recovery mode now. If I'm not mistaken this means I might be able to extract the data.
EDIT3:
The recovery mode is not asking me for my unlock pattern (which I think it should be doing) and is not showing up under 'adb devices'. I've tried flashing the boot.img of all OOS versions I can think of with fastboot, nothing will let me boot back in or let me access adb through the recovery. Am I ****ed?
Click to expand...
Click to collapse
Maybe it's worth trying change the slot and see if it will start? Of course from the fastboot level.
MoresM said:
I'm also facing the same issues. Tried updating from the Magisk App. Didn't receive any error messages. After reboot I'm stuck in fastboot mode and I cannot access recovery. I do not have a backup of the data on this phone.
Click to expand...
Click to collapse
I managed to fix it as well by flashing the stock boot.img for my software version to both slot_a and slot_b using fastboot. I left the active slot setting alone otherwise.
Afterwards I booted into twrp through fastboot and installed blu spark twrp and magisk 21.4 from there as a user suggested on the Magisk github: https://github.com/topjohnwu/Magisk/issues/3924
Note that github link also has a solution to flawlessly upgrade to latest Magisk without data loss but I haven't had the time to look at it.
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