Related
Hi all people,
first of all, I want excuse me for not my perfect English.
I have Honor 9 from few days. And I think to have bricked it.
I have unlocked bootloader correctly.
I have flashed recovery this TWRP recovery with the intention to proceed to root with Magisk or SuperSu. I accidentally and unconsiuosly do factory reset then the phone goes bootloop. (it power off and power on continuously) with the alert "your device has been unlocked and..etc".
Yesterday, reading this thread, I flashed, from fastboot console, boot, recovery and system, the phone resets two/three times then goes to eRecovery where I do a factory reset.
After a factory reset the phone works correctly and seems successfully unbricked. So I re-flash TWRP recovery.
But this morning, during the attempt to install from TWRP one between Magisk or SuperSu (I don't succeed to do it beacuse the phone was crypted and I don't see zip files from TWRP). I have reset the phone but goes bootloop again.
I tried to re-flash boot, recovery, system and cust more (that I don't have flashed yesterday). Now the phone goes eRecovery and ask me to connect to download latest version and recovery, but don't ask me to do a factory reset.
Now I don't know what I can do.
How I can solve this situation? I want only unlock bootloader (done!), install TWRP and have root permission. Now I don't think to change rom.
Something similar happened to me. It seems like the TWRP provided has some issue..... After installing TWRP I had a bootloop problem. I have resolved installing Magisk. It seems that Magisk patchs something. If you can access TWRP try to install Magisk (put the zip file on external sd). In other words: copy magisk zip on sd card - during the bootloop you have the chance to power off phone - Power off - Power on in recovery mode. If you have TWRP correctly installed Honor should go in recovery using TWRP . Install Magisk and see what happens...
unvisigoth said:
Something similar happened to me. It seems like the TWRP provided has some issue..... After installing TWRP I had a bootloop problem. I have resolved installing Magisk. It seems that Magisk patchs something. If you can access TWRP try to install Magisk (put the zip file on external sd). In other words: copy magisk zip on sd card - during the bootloop you have the chance to power off phone - Power off - Power on in recovery mode. If you have TWRP correctly installed Honor should go in recovery using TWRP . Install Magisk and see what happens...
Click to expand...
Click to collapse
I have tried to flash TWRP recovery again to do install Magisk from sd card. I have done it but the phone doesn't work fine.
So I have put rommco05 TWRP Backup into sd card then restored it from TWRP restore (boot and vendor img). Now the phone seems have bootloader locked, in fact I don't have bootloader warning at the power on. Now in fastboot mode the phone says me that I have Phone locked and FRP unlocked.
How can I exit from this situation?
Try this
Killus3 said:
Hi all people,
first of all, I want excuse me for not my perfect English.
I have Honor 9 from few days. And I think to have bricked it.
I have unlocked bootloader correctly.
I have flashed recovery this TWRP recovery with the intention to proceed to root with Magisk or SuperSu. I accidentally and unconsiuosly do factory reset then the phone goes bootloop. (it power off and power on continuously) with the alert "your device has been unlocked and..etc".
Yesterday, reading this thread, I flashed, from fastboot console, boot, recovery and system, the phone resets two/three times then goes to eRecovery where I do a factory reset.
After a factory reset the phone works correctly and seems successfully unbricked. So I re-flash TWRP recovery.
But this morning, during the attempt to install from TWRP one between Magisk or SuperSu (I don't succeed to do it beacuse the phone was crypted and I don't see zip files from TWRP). I have reset the phone but goes bootloop again.
I tried to re-flash boot, recovery, system and cust more (that I don't have flashed yesterday). Now the phone goes eRecovery and ask me to connect to download latest version and recovery, but don't ask me to do a factory reset.
Now I don't know what I can do.
How I can solve this situation? I want only unlock bootloader (done!), install TWRP and have root permission. Now I don't think to change rom.
Click to expand...
Click to collapse
https://forum.xda-developers.com/honor-9/help/bootloader-locked-help-to-enable-usb-t3683145
Rommco05 said:
Again unlock bootloader
Click to expand...
Click to collapse
I have unlocked bootloader again and do a factory reset from TWRP recovery, now the phone seems works correctly!!!:good:
Now I should try to root the phone with Magisk or SuperSu, right?
I have a question about TWRP. From TWRP's file manager I don't see the files that I put in the internal memory. It's because I have used finger print to lock the phone that encryptes files?
raw_jay said:
https://forum.xda-developers.com/honor-9/help/bootloader-locked-help-to-enable-usb-t3683145
Click to expand...
Click to collapse
This is to re-brand the phone from Chinese to EU version...I don't think is my case.
Rommco05 said:
Take a backup before make root. You don't see files because is some issue with decryption in TWRP. I achieved root with Magisk but I don't remember exactly steps
Click to expand...
Click to collapse
I think it's too late
Anyway I can re-flash all thing from begin.
Then I can't use TWRP with the phone encrypted ( PIN, password, fingerprint, etc...) ?
Rommco05 said:
I'm not sure about thatz Huawei roms are encrypted somehow by default
Click to expand...
Click to collapse
After I have installed Magisk (v14.0) now I have problem with google play services which don't download and do updates apps.
If I do a factory reset again I can solve it?
Update:
After I done a factory reset from TWRP recovery
and formatting data partition the phone seems working perfectly (I don't know why, but before format data the phone says me that I have only 150mb of memory space)
I say "seems" because there's something getting me in trouble, for example, I don't have anymore ringtones in the settings menu.
And I don't know if I have lost something else.
Exists a possibilty to restore all contents of the phone?
You could try this and flash your phone back to stock. But then you would need to unlock your bootloader and install TWRP again. Another way would be to unpack an image of your ROM and flash system and other parts via fastboot. Of course this could be risky and you could brick the device.
Meranico said:
You could try this and flash your phone back to stock. But then you would need to unlock your bootloader and install TWRP again. Another way would be to unpack an image of your ROM and flash system and other parts via fastboot. Of course this could be risky and you could brick the device.
Click to expand...
Click to collapse
If I understand it well...
I have 2 options:
1) Rebrand the phone and flashin, then at end I have back the phone stock.
2) Unpack the image of ROM (what it means?) and flash system and other parts via fastboot. (Which are those parts? How?) But this procedure is more hazardous then rebrand procedure?
I have understand right?
1. Yes, correct. I would recommend that. Everything is explained in the thread I linked. Of course everything you do could potentially harm your phone, but you should know that already.
2. Get an update.app file for your specific phone model (there are threads already here, just search a bit, or use Firmware Finder), open it with the Huawei Update Extractor and extract the parts you want to flash (like system or recovery). Then flash them via fastboot. I tried this because I was in a situation like yours, but it didn't work for me. But in theory it could, because you would replace the faulty parts of your firmware.
Killus3 said:
I have understand right?
Click to expand...
Click to collapse
Could you solve your problem?
Meranico said:
Could you solve your problem?
Click to expand...
Click to collapse
Hi, I don't say it because I have replaced the phone with another same.
Now I'm starting to unlock bootloader, installing recovery TWRP and rooting the phone.
I hope to avoid bootloop this time.
Goodmorning everyone!
Yesterday I have:
- Unlocked bootloader correctly!
- Installed TWRP correctly!
- Make a TWRP Backup of all partitions of the device, except data partition because TWRP gives me an error during backup attempt.
- Then I start the device.
- After start the device I go to recovery TWRP to install Magisk, but the phone goes bootloop.
After reboot 2-3 times on the screen appears for a few moments a message of eRecovery that have restored something but I don't know. Then the device shows me the eRecovery that asks me to make a factory reset.
At this point I shutdown the device, go in TWRP to flash Magisk unistaller and the device goes out bootloop and works fine but without root.
How I can solve this problem and install Magisk and have root finally?
Some question:
-When I flashed TWRP (via fastboot) and I configurate it, example language, hours, etc... TWRP don't save the settings, in fact when I go in TWRP again I do remake the settings. Why?
-Then I go in sdcard I don't navigate files, I see folders with casual characters. This is an effect of encryption of the device?
Killus3 said:
Goodmorning everyone!
Yesterday I have:
- Unlocked bootloader correctly!
- Installed TWRP correctly!
- Make a TWRP Backup of all partitions of the device, except data partition because TWRP gives me an error during backup attempt.
- Then I start the device.
- After start the device I go to recovery TWRP to install Magisk, but the phone goes bootloop.
After reboot 2-3 times on the screen appears for a few moments a message of eRecovery that have restored something but I don't know. Then the device shows me the eRecovery that asks me to make a factory reset.
At this point I shutdown the device, go in TWRP to flash Magisk unistaller and the device goes out bootloop and works fine but without root.
How I can solve this problem and install Magisk and have root finally?
Some question:
-When I flashed TWRP (via fastboot) and I configurate it, example language, hours, etc... TWRP don't save the settings, in fact when I go in TWRP again I do remake the settings. Why?
-Then I go in sdcard I don't navigate files, I see folders with casual characters. This is an effect of encryption of the device?
Click to expand...
Click to collapse
Answers to all your concerns go here mate---> TWRP doesn't decrypt data. Done.
Hence: weird folders in there, nowhere to store its settings prefs, about Magisk it's another story, if you want root go SuperSU latest beta.
Regards.
a basically did what that guy did, got root installed via TWRP but my google apps are all busted.
I tried flashing the update_data_full_public.zip and update_full_hw_usa.zip I found using the russian device lookup link switching trick but I the HW errored when I tried to flash it in TWRP and my play store still broken.
I want to root my poco f1 ....
But i have some questions regarding it
1. Will my data be format while rooting and installing twrp
2. How i will get ota update
3. Will installing ota update also format my data?
1. Your whole internal data needs to be wiped... To flash the force decryption enabler at first...
Even while installing twrp via fastboot.. Your data will be formated
2. You will get updates... But not via ota.... Yes you will get to download the updateds in some roms... But you need to dirty flash them.
3. While dirty flashing.... Formatting data is not required.
roxor101 said:
1. Your whole internal data needs to be wiped... To flash the force decryption enabler at first...
Even while installing twrp via fastboot.. Your data will be formated
2. You will get updates... But not via ota.... Yes you will get to download the updateds in some roms... But you need to dirty flash them.
3. While dirty flashing.... Formatting data is not required.
Click to expand...
Click to collapse
Does the twrp with working decryption also need to format my data?
You can root your device in two ways.
First, with twrp (OTA won't work afterwards)
Second, without twrp (OTA will work)
First method, unlock the bootloader (device will be wiped)>Grab the twrp with working decryption>Boot your device into fastboot and type fastboot flash recovery twrp.img (or whatever the recovery image name is)>Now type fastboot boot twrp.img (or whatever the recovery image name is)>Once booted into twrp, swipe to allow modification>Now download Magisk installer and copy into the device>Flash it?Reboot to system>Profit.
N.B. After flashing twrp, make sure to first boot into twrp before booting into system or else device will restore stock recovery. If you need to update in future, just grab the twrp flashable update package and flash it. That's it. No need for OTA.
Second method, this will also require an unlocked bootloader. Once the bootloader is unlocked, get the stock boot image of your current software (e.g. if you are on miui 10 with October security patch, make sure to grab the stock boot image for miui 10 october). Now install Magisk manager apk in your device. Now open magisk manager and go to install. You will find an option for patching stock boot image. Click on it and select the stock boot image. Magisk will patch the boot image and will place it in your internal memory. Now boot into fastboot mode and type fastboot boot patched_boot.img (or whatever the name is). Once device is booted into system, go to Magisk and click on Install>Direct install (recommended).Magisk will get flashed by itself and reboot. Once rebooted, go to Magisk manager and check. If you do everything correctly, you are rooted.
N.B. When you get an OTA update, open Magisk and go to Unsinatll and click on "Complete uninstall". It will uninstall magisk and revert your stock boot image back. Note that, if you play witgh system partition like modifying build.prop or change host file or bootanimantion or any such thing, you won't be able to get any further OTA update. In that case, you need to flash the complete fastboot rom through MiFlash tool.
For more information, please go to Magisk thread or search online.
So i had a hickup with updating magisk to v20.3.
The result was that after a reboot the device got stuck in fastboot mode.
I went to TWRP 3.3.0 recovery and backed up all offered partitions before then attempting to re-flash magisk.
Didn't work out.
Then i heard that if you extract the boot.img from the stock firmware and flash it with fastboot you can get back to a working state where you can install Magisk again.
So i thought.
Now after booting i am greeted by the miui first install wizard and the whole set of apps seems to be gone as well as my settings.
IIRC i only removed the dalvik cache which shouldn't affect this state.
Where in the procedure is the mistake and can i get the old pre-broken update state back? I am afraid something has been lost in the process
selemine said:
So i had a hickup with updating magisk to v20.3.
The result was that after a reboot the device got stuck in fastboot mode.
I went to TWRP 3.3.0 recovery and backed up all offered partitions before then attempting to re-flash magisk.
Didn't work out.
Then i heard that if you extract the boot.img from the stock firmware and flash it with fastboot you can get back to a working state where you can install Magisk again.
So i thought.
Now after booting i am greeted by the miui first install wizard and the whole set of apps seems to be gone as well as my settings.
IIRC i only removed the dalvik cache which shouldn't affect this state.
Where in the procedure is the mistake and can i get the old pre-broken update state back? I am afraid something has been lost in the process
Click to expand...
Click to collapse
Just install the latest stock rom then install recovery and restore all the backed up partitions.
Now install magisk and reboot.
If that doesn't work (u get into fastboot again) then just flash the boot.img file via fastboot and then reboot.
if i restore the backed up partitions and install magisk over it i get back to the non-booting , stuck in fastboot version. So something is wrong in the state of denmark.
selemine said:
if i restore the backed up partitions and install magisk over it i get back to the non-booting , stuck in fastboot version. So something is wrong in the state of denmark.
Click to expand...
Click to collapse
I looked at the /data backup from twrp and it is only 3mb, unless stuff got moved to /system or so, it seems to be gone forever.
Hell , i wil never update magisk again.
selemine said:
I looked at the /data backup from twrp and it is only 3mb, unless stuff got moved to /system or so, it seems to be gone forever.
Hell , i wil never update magisk again.
Click to expand...
Click to collapse
Don't install magisk with the rom, just restore the data, flash the stock boot.img file and then reboot.
After boot uninstall the magisk manager app and reboot to recovery and then flash magisk again.
Followed the instructions on several websites such as this one here at XDA:
https://www.xda-developers.com/how-to-install-twrp/
All goes well until I get to this line:
fastboot flash recovery recovery.img (latest TWRP image, renamed)
The command prompt window just sits there and says "(waiting for any device)"...
Most websites and forum threads seem to indicate that this is a problem with the drivers. Can anyone confirm?
FWIW, I did a total reflash of the latest stock ROM from this thread:
https://forum.xda-developers.com/ga...icial-stock-fw-update-odin-thread-xx-t3825204
so I currently have only the "stock" recovery.
I'd rather not root it quite yet. Help please?
P.S. The phone shows up in Device Manager and for "adb devices"; the phone's bootloader has been unlocked... can't see what I'm missing... I'm using a Windows 10 computer... I removed any screen locking mechanisms (PIN, fingerprint, etc.)...
Follow this instructions https://forum.xda-developers.com/galaxy-note-9/development/recovery-twrp-galaxy-note9-exynos-t4097441
Most samsung device use odin to install twrp
ACC18 said:
Follow this instructions https://forum.xda-developers.com/galaxy-note-9/development/recovery-twrp-galaxy-note9-exynos-t4097441
Most samsung device use odin to install twrp
Click to expand...
Click to collapse
Thanks. I'm trying it with 3.4.0-0
Do I flash this file while I'm still in TWRP? Or do I reboot the phone and go back *into* TWRP to flash it?
>After booting in TWRP download and flash no-verity-opt-encrypt-6.1 zip to disable data partition encryption
Edit: I tried flashing no-verity-opt while still in TWRP. Got the dreaded:
"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."
I *really* tried to follow the instructions exactly, and think I did.
Was it because I tried to flash 3.4.0-0...?
I am currently re-flashing the stock firmware again.
Dougmeister said:
Thanks. I'm trying it with 3.4.0-0
Do I flash this file while I'm still in TWRP? Or do I reboot the phone and go back *into* TWRP to flash it?
>After booting in TWRP download and flash no-verity-opt-encrypt-6.1 zip to disable data partition encryption
Edit: I tried flashing no-verity-opt while still in TWRP. Got the dreaded:
"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."
I *really* tried to follow the instructions exactly, and think I did.
Was it because I tried to flash 3.4.0-0...?
I am currently re-flashing the stock firmware again.
Click to expand...
Click to collapse
You need to format data after install twrp. This is avoiding internal data encrypted.
After twrp installed, do format data from twrp. Of course all of ur data on internal erased. And then take custom rom. I suggest devbase rom, this have "no verity encrypt" when u install this rom. Devbase is stock firmware for easy upgrade for rooted phone. And this is easy to install for beginner
Sorry for bad English
ACC18 said:
You need to format data after install twrp. This is avoiding internal data encrypted.
After twrp installed, do format data from twrp. Of course all of ur data on internal erased. And then take custom rom. I suggest devbase rom, this have "no verity encrypt" when u install this rom. Devbase is stock firmware for easy upgrade for rooted phone. And this is easy to install for beginner
Sorry for bad English
Click to expand...
Click to collapse
No worries. Thank you for your help.
I use Odin to install the Devbase ROM, right? Or can I use TWRP?
Edit: apparently it works just fine to install it with TWRP.
Thank you so much. This time TWRP works just fine for me and the new ROM is great.
I was running stock MIUI with root and TWRP recovery. After flashing the Pixel Experience Android 11 ROM, I didn't flash TWRP again. I tried many attempts (I haven't mentioned everything here to keep the post shorter) to install TWRP again, and I managed to do it successfully once. However, now when I boot into TWRP and select the A partition, it can't decrypt with my password and reboots the system, always opening the bootloader. When selecting the B partition, if I format the data and flash Magisk, it opens up the system (it opens the bootloader without flashing Magisk). But after booting into the system, if I boot TWRP again and reboot into the system without doing anything, my settings app and Bluetooth stop working. Then I have to boot into TWRP again, format the data, and flash Magisk again to boot the system normally. I can't install any Magisk modules either. However, the root is working.
Do you have any suggestions on what I can do?"
AhmedRadowan25 said:
Do you have any suggestions on what I can do?
Click to expand...
Click to collapse
flash stock miui according to your region with mi flash (don't lock the bootloader!)
this generally solves any problem and you can go back to custom roms after booting into miui.
Anyway , i recommend you to use the recovery provided with the rom itself as twrp can give issues sometimes.
AhmedRadowan25 said:
I was running stock MIUI with root and TWRP recovery. After flashing the Pixel Experience Android 11 ROM, I didn't flash TWRP again. I tried many attempts (I haven't mentioned everything here to keep the post shorter) to install TWRP again, and I managed to do it successfully once. However, now when I boot into TWRP and select the A partition, it can't decrypt with my password and reboots the system, always opening the bootloader. When selecting the B partition, if I format the data and flash Magisk, it opens up the system (it opens the bootloader without flashing Magisk). But after booting into the system, if I boot TWRP again and reboot into the system without doing anything, my settings app and Bluetooth stop working. Then I have to boot into TWRP again, format the data, and flash Magisk again to boot the system normally. I can't install any Magisk modules either. However, the root is working.
Do you have any suggestions on what I can do?"
Click to expand...
Click to collapse
Here's a complete explanation what I have done:
Initially, I was running stock MIUI with root access and TWRP recovery. However, I decided to switch to the Pixel Experience ROM. I downloaded the Pixel Experience Android 11 version and flashed it directly from TWRP since I didn't have access to a PC at that time. I only flashed the ROM file and didn't install the Pixel Experience recovery image, assuming that my TWRP would remain intact. But when I rebooted into recovery after the ROM installation, it booted into the Pixel Experience recovery instead. I couldn't find an option to flash the recovery image, only an option to apply an update through ADB sideload.
Fortunately, I managed to use a friend's computer and installed all the necessary ADB and Fastboot drivers. The computer could detect my phone in ADB sideload mode, but when I tried to boot into the bootloader, the PC couldn't detect my phone. Despite multiple attempts of booting into the Pixel Experience recovery and enabling ADB sideload, the PC couldn't recognize the fastboot mode. Strangely, every time I booted into the bootloader, my phone automatically powered off after displaying the Redmi logo. Holding the power button didn't help as it consistently powered off after showing the logo, without accessing the bootloader or recovery mode. I was afraid my phone had become completely unresponsive.
After numerous attempts, my phone unexpectedly booted into the bootloader again. This time, I connected my phone to another device using BugJagger, which successfully detected my phone. I used the command "fastboot flash recovery twrp.img" followed by "fastboot boot twrp.img" to open TWRP. However, I couldn't decrypt it using my password. I then flashed TWRP again and tried to boot into the system, but it always reverted back to the bootloader. I went back into recovery, selected partitions A to B, and flashed Magisk ZIP, DM variety ZIP, and LazyFlasher ZIP (without fully understanding their purpose).
Finally, my phone successfully booted into the system. However, upon rebooting into TWRP and then rebooting the system without any changes, my settings app and bluetooth stoped working. To resolve this, I had to boot into TWRP once again, format the data, and flash Magisk to restore normal operation.
alonsoj636MW said:
flash stock miui according to your region with mi flash (don't lock the bootloader!)
this generally solves any problem and you can go back to custom roms after booting into miui.
Anyway , i recommend you to use the recovery provided with the rom itself as twrp can give issues sometimes.
Click to expand...
Click to collapse
yes i am also thinking that it is the only solution.But I have tampered almost everything of my phone.Will flash stock miui rom can solve all problem?I have writen everything what i have done details in reply.you can read it if you want.
AhmedRadowan25 said:
yes i am also thinking that it is the only solution.But I have tampered almost everything of my phone.Will flash stock miui rom can solve all problem?I have writen everything what i have done details in reply.you can read it if you want.
Click to expand...
Click to collapse
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with miflash to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
alonsoj636MW said:
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with miflash to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
Click to expand...
Click to collapse
alonsoj636MW said:
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
Click to expand...
Click to collapse
Thank you very much.Flashing miui will solve all probem?what do you think?
AhmedRadowan25 said:
what do you think?
Click to expand...
Click to collapse
it should
at least when i mess up with my phone flashing stock fixes all problems
Hi mate! Did you resoved the problem? What about the rom? All good?
gabsvm1 said:
Hi mate! Did you resoved the problem? What about the rom? All good?
Click to expand...
Click to collapse
No.I am running pixel experience 11 rom with these problems.No problem will appear untill i boot into recovery.Sorry i can't check and tell you that if 13 rom's recovery can flash 11 rom.
AhmedRadowan25 said:
No.I am running pixel experience 11 rom with these problems.No problem will appear untill i boot into recovery.Sorry i can't check and tell you that if 13 rom's recovery can flash 11 rom.
Click to expand...
Click to collapse
No problem mate, besides that everything is working good? You have tried a13 roms before?
gabsvm1 said:
No problem mate, besides that everything is working good? You have tried a13 roms before?
Click to expand...
Click to collapse
No
Who told you to flash DM Verity and Lazy Flasher
We don't need these things in our device
Don't mess up with Active Slot
If you try to change your Active slot into Inactive slot, once you Reboot to system, you will go straight to fastboot
You need Android Bootloader Interface to detect your phone in bootloader and ADB Composite to detect your phone in ADB, such as : Google USB Driver r13
Why you don't ask before doing anything, we have global community chat in telegram, for sure, we will help you in possible way
I assume you need back to stock rom to fix this issue
hit me on tele t.me/super_img