I followed the steps given in a post ( not able to post url) and after installing the Supersu the phone is stuck on the boot loop.
I saw posts where the users want to go back to the stock image however i need the phone to be rooted, any suggestions what might be causing the boot loop and how i can fix it.
PS: I have twrp backup and last resort will be to give up rooting and restrore from it. Appreciate your expertise in advance!
Atul Chadha said:
I followed the steps given in a post ( not able to post url) and after installing the Supersu the phone is stuck on the boot loop.
I saw posts where the users want to go back to the stock image however i need the phone to be rooted, any suggestions what might be causing the boot loop and how i can fix it.
PS: I have twrp backup and last resort will be to give up rooting and restrore from it. Appreciate your expertise in advance!
Click to expand...
Click to collapse
URL: http://www.androidinfotech.com/2016/12/root-huawei-honor-7-marshmallow-twrp.html
Atul Chadha said:
URL: http://www.androidinfotech.com/2016/12/root-huawei-honor-7-marshmallow-twrp.html
Click to expand...
Click to collapse
That is way outdated man. And avoid following guides from 3rd party sites. Always search here in XDA. You flashed an outdated TWRP. Flash THIS latest version. Restore your backup for the moment, then flash the latest SuperSU. 2.82. The site you gave both give outdated TWRP and SuperSU.
Sent from my Honor 8 using XDA Labs
adriansticoid said:
That is way outdated man. And avoid following guides from 3rd party sites. Always search here in XDA. You flashed an outdated TWRP. Flash THIS latest version. Restore your backup for the moment, then flash the latest SuperSU. 2.82. The site you gave both give outdated TWRP and SuperSU.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
Lemme try the above, will keep you posted.
Atul Chadha said:
Lemme try the above, will keep you posted.
Click to expand...
Click to collapse
Alright.
Sent from my Honor 8 using XDA Labs
Atul Chadha said:
Lemme try the above, will keep you posted.
Click to expand...
Click to collapse
I was able to run the supersu however the phone is not booting and says "Attention, please update system again"
Error!
Func No: 10 ( Boot image)
Error No: 2 (load Failed)
adriansticoid said:
Alright.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
I was able to run the supersu however the phone is not booting and says "Attention, please update system again"
Error!
Func No: 10 ( Boot image)
Error No: 2 (load Failed)
Atul Chadha said:
I was able to run the supersu however the phone is not booting and says "Attention, please update system again"
Error!
Func No: 10 ( Boot image)
Error No: 2 (load Failed)
Click to expand...
Click to collapse
Did you restore your backup first?
adriansticoid said:
Did you restore your backup first?
Click to expand...
Click to collapse
I restored my backup and then put the new supersu package in sd card. I have a backup however now i am not able to access TWRP.
Atul Chadha said:
I restored my backup and then put the new supersu package in sd card. I have a backup however now i am not able to access TWRP.
Click to expand...
Click to collapse
To add: I also cleared the cache and data and it was successful. The Supersu mentioned something about writing on boot loader and said it would reboot the phone.
After that, the phone didnt came up
Atul Chadha said:
To add: I also cleared the cache and data and it was successful. The Supersu mentioned something about writing on boot loader and said it would reboot the phone.
After that, the phone didnt came up
Click to expand...
Click to collapse
i think you flashed wrong su ,
venugopalu007 said:
i think you flashed wrong su ,
Click to expand...
Click to collapse
How can i get the right one ( How do i decide the correct version, i am using honor 7 running B360 version bought from flipkart if it makes any difference)
Atul Chadha said:
How can i get the right one ( How do i decide the correct version, i am using honor 7 running B360 version bought from flipkart if it makes any difference)
Click to expand...
Click to collapse
I installed SuperSU-v2.82-201705271822
Atul Chadha said:
I installed SuperSU-v2.82-201705271822
Click to expand...
Click to collapse
Still in bootloop? Dafuq.
Sent from my Honor 8 using XDA Labs
adriansticoid said:
Still in bootloop? Dafuq.
Click to expand...
Click to collapse
So i restored the backup i had because i needed my phone. Is there a specific version of twrp and supersu i need for honor 7.
Here is what i am trying:
I have my supersu on sd card.
I restart phone to goto twrp
i go-to wipe>advanced>wipe the cache
Go back to twrp main menu and hit install
Locate supersu and install it
reboot
Am i missing any step ?
EDIT: I tried using "SuperSU-v2.82-201705271822" latest version and same results. The phone is in rescue mode with error
Error! Func No: 10 ( Boot image) Error No: 2 (load Failed)
Atul Chadha said:
So i restored the backup i had because i needed my phone. Is there a specific version of twrp and supersu i need for honor 7.
Here is what i am trying:
I have my supersu on sd card.
I restart phone to goto twrp
i go-to wipe>advanced>wipe the cache
Go back to twrp main menu and hit install
Locate supersu and install it
reboot
Am i missing any step ?
EDIT: I tried using "SuperSU-v2.82-201705271822" latest version and same results. The phone is in rescue mode with error
Error! Func No: 10 ( Boot image) Error No: 2 (load Failed)
Click to expand...
Click to collapse
EDIT2: I flashed the stock ROM and tried the same thing again.
Same results, either i am doing something wrong or its sheer luck i guess!
Atul Chadha said:
EDIT2: I flashed the stock ROM and tried the same thing again.
Same results, either i am doing something wrong or its sheer luck i guess!
Click to expand...
Click to collapse
Actually man I have no idea why it doesn't boot when it should. How about Magisk? Can you try that?
adriansticoid said:
Actually man I have no idea why it doesn't boot when it should. How about Magisk? Can you try that?
Click to expand...
Click to collapse
Trying it now.
Atul Chadha said:
Trying it now.
Click to expand...
Click to collapse
No luck , same results. I guess i should try to restore the backup and give in for now. There is something wrong with the boot sequence which i cant seem to figure.
The rooting apps write on the boot sequence and then it gives the error i mentioned. I really appreciate your help though, if you find something interesting please update here.
Atul Chadha said:
No luck , same results. I guess i should try to restore the backup and give in for now. There is something wrong with the boot sequence which i cant seem to figure.
The rooting apps write on the boot sequence and then it gives the error i mentioned. I really appreciate your help though, if you find something interesting please update here.
Click to expand...
Click to collapse
I will man. I'm really sorry for this.
Sent from my Honor 8 using XDA Labs
Related
Now supports among other things back up to pc. I've installed and tested and works.
https://dl.twrp.me/ailsa_ii/twrp-3.1.0-0-ailsa_ii.img
Edit: the original article https://www.xda-developers.com/twrp...-support-for-adb-backup-ab-ota-zips-and-more/
Edit: seems flashing via TWRP image flash is providing better success than via TWRP app. Recommend updating via TWRP flash.
thanks
Do not work.
Get a black screen if i try to Boot in to twrp.
Must go back to 3.0.4.1..
Eller1987 said:
Do not work.
Get a black screen if i try to Boot in to twrp.
Must go back to 3.0.4.1..
Click to expand...
Click to collapse
u sure ur bl is unlocked?
MaxRink said:
u sure ur bl is unlocked?
Click to expand...
Click to collapse
Yes.
I am in LOS 14.1 and twrp 3.0.4.1. works fine.
Flashed 3.1.0.0. whit Flashify.
Worked great for me! I always flash in TWRP, I guess that a I am old school. Thanks for pointing out the new version. I will have to try out the new ADB backup feature later. Although I am not sure if we are still having problems restoring backups like we used to on this phone. I haven't been able to keep up with the forum's lately.
Wrong thread, this needs to be in General
Mod please move.
I flashed the image file in recovery and I still ended up with a black screen.
borijess said:
I flashed the image file in recovery and I still ended up with a black screen.
Click to expand...
Click to collapse
Weird man i got it working flashing it feom twrp it self
borijess said:
I flashed the image file in recovery and I still ended up with a black screen.
Click to expand...
Click to collapse
Maybe you should also write from which TWRP version you come and which Axon 7 model(US/Chinese/European?) you own?
redandr said:
Maybe you should also write from which TWRP version you come and which Axon 7 model(US/Chinese/European?) you own?
Click to expand...
Click to collapse
i have a A2017G and come from twrp 3.0.4.1..
Which partion must i flash for the update to 3.1.0.0.?
I flashed this 3.1 on my chinese b13 with twrp 3.0.4-1 and everything is fine. Flashed it thru twrp btw.
---------- Post added at 11:26 AM ---------- Previous post was at 11:25 AM ----------
Eller1987 said:
i have a A2017G and come from twrp 3.0.4.1..
Which partion must i flash for the update to 3.1.0.0.?
Click to expand...
Click to collapse
Flash it in twrp install and choose img. Flash it for recovery partition.
redandr said:
maybe you should also write from which twrp version you come and which axon 7 model(us/chinese/european?) you own?
Click to expand...
Click to collapse
twrp 3.0.41 axon 7 us version.
Ok I flashed TWRP through fastboot and it worked. I think my first DL was bad. It was half the size of the second one I downloaded.
Success here too. Thank you.
Its all ok with Axon Zte A2017 Chinese.
The last TWRP I conscioulsy installed was 3.0.4.1 but it now shows 3.0.N1-1, what is that? Could it have been updated automatically from the TWRP app?
Also, before I noticed that my boot partition disappeared from TWRP, I can no longer make backups of it or restore the ones I had. Why could that happen? I get something like "unable to locate boot". Thanks
0Kajuna0 said:
The last TWRP I conscioulsy installed was 3.0.4.1 but it now shows 3.0.N1-1, what is that? Could it have been updated automatically from the TWRP app?
Also, before I noticed that my boot partition disappeared from TWRP, I can no longer make backups of it or restore the ones I had. Why could that happen? I get something like "unable to locate boot". Thanks
Click to expand...
Click to collapse
I am guessing you used EDL mode to install TWRP as that is the modified version, as I saw that too. I used TWRP to flash the 3.0.4-1 image and all is normal.
EDIT: TWRP 3.0.4-1 on A2017U Running modified Stock B15 (lots of APKs frozen). Flashing TWRP 3.1 both from TWRP and from "Official App" results with black screen for Recovery. TWRP 3.0.4-1 re-flashed OK from app.
N1-1 is from unjustified devs bootstack.
lafester said:
N1-1 is from unjustified devs bootstack.
Click to expand...
Click to collapse
N1-1 & 3.0.4-1 both work fine, but 3.1 boots to black screen. Why?
Twrp 3.1.0 worked fine on my Axon 7 US version A2017U
Flashed via fastboot over stock recovery.
Will edit this thread and report back if issue is discovered.
Hello everyone! I'm new on XDA and this is my first thread.
So, I've been messing around with my Honor 7 lately. I've flashed a custom recovery (TWRP), flashed a custom ROM (Unofficial CM13 for Honor 7: https://forum.xda-developers.com/honor-7/development/unsupported-cyanogenmod-13-honor-7-plk-t3542627) and root (SuperSU) and I've started to regret all of my decisions so I would like to take a fresh start (AKA flashing the STOCK ROM/Firmware)
Now, before anyone starts redirecting me to other (similar) threads, I've tried a lot. I tried to flash the stock recovery (a lot of different versions) but still when I try to boot into the stock recovery, my phone just reboots. I tried to do the force update thing (holding both power + & - buttons: http://www.gogorapid.com/flash-stock-rom-huawei-honor-7/), but this combination just boots my phone into TWRP. Could it be that I'm doing something wrong or that I'm missing something, like some requirements that are not being met? Please help me, I would appreciate it a lot! Thanks in advance.
LoRikU said:
Hello everyone! I'm new on XDA and this is my first thread.
So, I've been messing around with my Honor 7 lately. I've flashed a custom recovery (TWRP), flashed a custom ROM (Unofficial CM13 for Honor 7: https://forum.xda-developers.com/ho...upported-cyanogenmod-13-honor-7-plk-t3542627) and root (SuperSU) and I've started to regret all of my decisions so I would like to take a fresh start (AKA flashing the STOCK ROM/Firmware)
Now, before anyone starts redirecting me to other (similar) threads, I've tried a lot. I tried to flash the stock recovery (a lot of different versions) but still when I try to boot into the stock recovery, my phone just reboots. I tried to do the force update thing (holding both power + & - buttons: http://www.gogorapid.com/flash-stock-rom-huawei-honor-7/), but this combination just boots my phone into TWRP. Could it be that I'm doing something wrong or that I'm missing something, like some requirements that are not being met? Please help me, I would appreciate it a lot! Thanks in advance.
Click to expand...
Click to collapse
It seems that you didn't flash the stock recovery properly.
Sent from my Honor 8 using XDA Labs
adriansticoid said:
It seems that you didn't flash the stock recovery properly.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
Thanks for the reply!
Could it be? I booted my phone into bootloader (unlocked) and flashed stock recovery with adb using the command "fastboot flash recovery recovery.img". I tried a variety of versions (from B100 up to B330 I think), but none of them seemed to work. What am I doing wrong?
LoRikU said:
Thanks for the reply!
Could it be? I booted my phone into bootloader (unlocked) and flashed stock recovery with adb using the command "fastboot flash recovery recovery.img". I tried a variety of versions (from B100 up to B330 I think), but none of them seemed to work. What am I doing wrong?
Click to expand...
Click to collapse
did you tried the offical TWRP of ypur device?
venugopalu007 said:
did you tried the offical TWRP of ypur device?
Click to expand...
Click to collapse
Hey,
Sorry for the slow reply, I'm currently on vacation. Euh I already have TWRP installed right now, I just don't know how to install the stock recovery.
LoRikU said:
Hey,
Sorry for the slow reply, I'm currently on vacation. Euh I already have TWRP installed right now, I just don't know how to install the stock recovery.
Click to expand...
Click to collapse
Download stock recovery and boot your phone to fastboot and
in command --- Fastboot flash recovery xxxfilenamexxx.img
LoRikU said:
Hey,
Sorry for the slow reply, I'm currently on vacation. Euh I already have TWRP installed right now, I just don't know how to install the stock recovery.
Click to expand...
Click to collapse
Grab the stock recovery file for your device. You can flash inside TWRP itself.
adriansticoid said:
Grab the stock recovery file for your device. You can flash inside TWRP itself.
Click to expand...
Click to collapse
Koriki extract the firmware using huaweiupdateextractor
venugopalu007 said:
Koriki extract the firmware using huaweiupdateextractor
Click to expand...
Click to collapse
Koriki?
Sent from my Honor 8 using XDA Labs
adriansticoid said:
Koriki?
Click to expand...
Click to collapse
Loriki is user name of op
Sorry my keyboard auto corrected it to koriki
venugopalu007 said:
Download stock recovery and boot your phone to fastboot and
in command --- Fastboot flash recovery xxxfilenamexxx.img
Click to expand...
Click to collapse
I tried that, read my second post on this thread. It didn't work, I didn't know which version I had to use. I ended up with a bootloop on various versions as mentioned in one of my first posts.
adriansticoid said:
Grab the stock recovery file for your device. You can flash inside TWRP itself.
Click to expand...
Click to collapse
Alright, I will try this. As soon as I get back home since the wifi here sucks.
venugopalu007 said:
Koriki extract the firmware using huaweiupdateextractor
Click to expand...
Click to collapse
I planned on doing this though I don't know where I can get the firmware for my H7... Could you perhaps provide me a link? It would be very kind of you (+ The wifi here sucks, so I will try downloading firmwares when I get home)
As you know, TWRP still doesn't support FBE, so in-case if you wanna flash another system.img the Wipe data/factory reset in TWRP wouldn't work (at least didn't work for me).
That would force you to get back to stock recovery, which allows a successful factory reset.
Steps are pretty straight forward, if you already have a backup of your stock recovery just do the below steps, if else you could download one from the below link.
Put the device into fastboot mode. There are two ways to do that.
1)By long pressing the power button and volume down button whilst the USB is connected.
2)Just do a adb reboot bootloader command if you could boot into the system.
Then just do
Code:
fastboot flash recovery_ramdisk recovery_ramdisk.img
Then disconnect the USB and long press the power and volume up button until you see the "The device is booting now" message.
Downloads
- Stock recovery for BKL-L09
Thanks, you saved me.
Thanks
Just created a md5sum of your recovery and my backed up recovery. It's exactly the same size but the md5sum is different.
A quick look with a hex editor also shows some big differences. Is that expected?
Copperhead100 said:
Just created a md5sum of your recovery and my backed up recovery. It's exactly the same size but the md5sum is different.
A quick look with a hex editor also shows some big differences. Is that expected?
Click to expand...
Click to collapse
MD5 hash wouldn't possibly match, because the backup was taken using dd and there might be some config files modified or added when I used the stock recovery once. But, hey the thing would work if you have BKL-L09 device
Thanks. This works!
shihabsoft said:
As you know, TWRP still doesn't support FBE, so in-case if you wanna flash another system.img the Wipe data/factory reset in TWRP wouldn't work (at least didn't work for me).
That would force you to get back to stock recovery, which allows a successful factory reset.
Click to expand...
Click to collapse
Mate, will this stock recovery work in Indian model(BKL-L09-C675)?
atf2m4 said:
Mate, will this stock recovery work in Indian model(BKL-L09-C675)?
Click to expand...
Click to collapse
Ofc it does
shihabsoft said:
Ofc it does
Click to expand...
Click to collapse
Mate, after restoring this recovery, will I be able to receive system update for the device. I have rooted with Magisk and twrp is installed. what to do to receive system update automatically?. please give detailed steps. Thank you.
atf2m4 said:
Mate, after restoring this recovery, will I be able to receive system update for the device. I have rooted with Magisk and twrp is installed. what to do to receive system update automatically?. please give detailed steps. Thank you.
Click to expand...
Click to collapse
Not sure, as it might check integrity before giving updates. Just download Firmware Finder app and check for updates constantly.
atf2m4 said:
Mate, after restoring this recovery, will I be able to receive system update for the device. I have rooted with Magisk and twrp is installed. what to do to receive system update automatically?. please give detailed steps. Thank you.
Click to expand...
Click to collapse
You will receive the updates but you won't be able to install them with TWRP. Simply flash the stock recovery and the updates will self install when they come. You'll have to root again with Magisk after the updates, but that's a simple process.
Sent from my Honor View 10 using XDA Labs
Hie,
How can I get back from lineage OS to stock using this? I guess I'm on the same boat as a lot of people out there and could really use some help here. I'm on Cosmos OS and can't go back to stock. I tried flashing this recovery.img but can't figure out a way back.
Reboot to bootloader, flash system recovery_ramdisk and ramdisk. Reboot to recovery wipe cache, reboot system enjoy.
Works every time fine for me
Powered by View 10
2WildFirE said:
Reboot to bootloader, flash system recovery_ramdisk and ramdisk. Reboot to recovery wipe cache, reboot system enjoy.
Works every time fine for me
Powered by View 10
Click to expand...
Click to collapse
Can you help me with the commands please?
---------- Post added at 09:20 PM ---------- Previous post was at 09:12 PM ----------
2WildFirE said:
Reboot to bootloader, flash system recovery_ramdisk and ramdisk. Reboot to recovery wipe cache, reboot system enjoy.
Works every time fine for me
Powered by View 10
Click to expand...
Click to collapse
Wildfire, can you please help me with the commands? I believe there's an inclusion of ramdisk in the commands now.
---------- Post added at 09:52 PM ---------- Previous post was at 09:20 PM ----------
2WildFirE said:
Reboot to bootloader, flash system recovery_ramdisk and ramdisk. Reboot to recovery wipe cache, reboot system enjoys.
Works every time fine for me
Powered by View 10
Click to expand...
Click to collapse
Apparently, there isn't any system.img file in the Indian firmware I downloaded. The rest are there but not the system.img.
Someone please help me out
I can't flash system.img as I was told in an earlier reply, it returns me an error that says 'Error: Cannot load System.':crying: I tried using -P and 256M commands to see the space divided and none of these worked either. CAN SOME PLEASE HELP ME OUT WITH THIS?
I cannot find system.img in the Indian firmware either, that is making things tough for me.
ankan1993 said:
I can't flash system.img as I was told in an earlier reply, it returns me an error that says 'Error: Cannot load System.':crying: I tried using -P and 256M commands to see the space divided and none of these worked either. CAN SOME PLEASE HELP ME OUT WITH THIS?
I cannot find system.img in the Indian firmware either, that is making things tough for me.
Click to expand...
Click to collapse
You should have made a backup before you started "tinkering" with your device. Lesson learned, hopefully.
Sent from my Honor View 10 using XDA Labs
Einwod said:
You should have made a backup before you started "tinkering" with your device. Lesson learned, hopefully.
Sent from my Honor View 10 using XDA Labs
Click to expand...
Click to collapse
Indeed! Can you please help me this one time?
ankan1993 said:
Indeed! Can you please help me this one time?
Click to expand...
Click to collapse
I cannot help you as I do not have your firmware or know anything about the Indian version. Where did you get this firmware from?
Einwod said:
I cannot help you as I do not have your firmware or know anything about the Indian version. Where did you get this firmware from?
Click to expand...
Click to collapse
I downloaded this from https://www.getdroidtips.com/huawei-honor-view-10-b160-oreo-firmware/#Downloads.
ankan1993 said:
I downloaded this from https://www.getdroidtips.com/huawei-honor-view-10-b160-oreo-firmware/#Downloads.
Click to expand...
Click to collapse
What device do you have exactly?
My Mi 8 Lite had stock, rooted (Magisk) MIUI Oreo and I dirty flashed MIUI Pie with TWRP 3.2.3. It booted up again with no problems and everything works but when I boot into recovery it now asks for a password to decrypt the data partition. Needless to say, the PIN for unlocking the screen is not accepted by TWRP. I'm hoping I won't need to wipe the data partition to fix this. Any ideas?
Thanks
<bump> anyone?
Sent from my MI 8 Lite using Tapatalk
If you are using the wzsx150 TWRP, notice that versions 1003/1203 are for Oreo only. You need to upgrade to versions 0121, 0212 or 0330 for Pie.
chan200606 said:
If you are using the wzsx150 TWRP, notice that versions 1003/1203 are for Oreo only. You need to upgrade to versions 0121, 0212 or 0330 for Pie.
Click to expand...
Click to collapse
Thanks a million, that fixed the problem. This information should be made available on the existing TWRP posts. I had a job finding the updated recoveries to download but came across a Google Drive folder that someone had posted https://drive.google.com/drive/folders/1780TJvn-ZHPBtgDdNjrN8i9YRlqPy38v - I went with the 0330 version which seems to be working fine.
dwl99 said:
Thanks a million, that fixed the problem. This information should be made available on the existing TWRP posts. I had a job finding the updated recoveries to download but came across a Google Drive folder that someone had posted https://drive.google.com/drive/folders/1780TJvn-ZHPBtgDdNjrN8i9YRlqPy38v - I went with the 0330 version which seems to be working fine.
Click to expand...
Click to collapse
I had the same problem (TWRP asking for password to decrypt data partition) and I have the 1003 version. So I am going to flash 0121, 0212 or 0330. Which do you recommend?
0330
Sent from my MI 8 Lite using Tapatalk
When I flashed 0330 the touchscreen is not working in twrp. How do I fix this?
tuytel said:
When I flashed 0330 the touchscreen is not working in twrp. How do I fix this?
Click to expand...
Click to collapse
This device has 3 different touchscreen panels (that I know of) and one of them is not fully supported. Which seems to be the one you have. To fix the problem the recovery needs some additions on source and then compiled. I suggest connecting to a pc and copying what you need off the internal storage and then use a recovery that your touchscreen works with and format the data partition using the option that asks you to type yes. This will remove encryption and allow you to access data no matter what recovery you use.
Maybe it's a stupid question bud wat is soue8and ?
tuytel said:
Maybe it's a stupid question bud wat is soue8and ?
Click to expand...
Click to collapse
My arthritis is bad today and it causes some issues with phone keyboard. It should say "source and". I went back and corrected it.
tuytel said:
When I flashed 0330 the touchscreen is not working in twrp. How do I fix this?
Click to expand...
Click to collapse
If you are not encrypted, flash OrangeFox recovery using the adb/fastboot method.
DarthJabba9 said:
If you are not encrypted, flash OrangeFox recovery using the adb/fastboot method.
Click to expand...
Click to collapse
Link to download OrangeFox?
I see: https://sourceforge.net/projects/orangefox/files/platina/OrangeFox-R9.0-2-platina.zip/download
MelvinGt5 said:
Link to download OrangeFox?
I see: https://sourceforge.net/projects/orangefox/files/platina/OrangeFox-R9.0-2-platina.zip/download
Click to expand...
Click to collapse
Yes, that is the correct download link.
I tried to flash this TWRP several times : TWRP-3.2.3-1003-XIAOMI8LITE-CN-wzsx150.img
but asks me for the password to decrypt the partition
later I read this trhead and tried to flash 0330 but now it returns the following error: Sending 'recovery' (63448 KB) FAILED (Write to device failed (Invalid argument))
What is the problem ?
Thank you
redblack68 said:
I tried to flash this TWRP several times : TWRP-3.2.3-1003-XIAOMI8LITE-CN-wzsx150.img
but asks me for the password to decrypt the partition
later I read this trhead and tried to flash 0330 but now it returns the following error: Sending 'recovery' (63448 KB) FAILED (Write to device failed (Invalid argument))
What is the problem ?
Thank you
Click to expand...
Click to collapse
Looks like you typed something wrong
cidxtc said:
Looks like you typed something wrong
Click to expand...
Click to collapse
it seems that adb / fastboot command no works
not even FASTBOOT ERASE CACHE
with FASTBOOT DEVICES the phone is seen
the phone runs normally
do I do a factory reset?
redblack68 said:
it seems that adb / fastboot command no works
not even FASTBOOT ERASE CACHE
with FASTBOOT DEVICES the phone is seen
the phone runs normally
do I do a factory reset?
Click to expand...
Click to collapse
Do you have root access in rom? If so you can flash rhe recovery image with an app called flashify. You can use the free version from playstore.
cidxtc said:
Do you have root access in rom? If so you can flash rhe recovery image with an app called flashify. You can use the free version from playstore.
Click to expand...
Click to collapse
No, no root. I would like to flash twrp to root with magisk
redblack68 said:
No, no root. I would like to flash twrp to root with magisk
Click to expand...
Click to collapse
Your bootloader was unlocked with mi unlocker?
cidxtc said:
Your bootloader was unlocked with mi unlocker?
Click to expand...
Click to collapse
Yes exactly
but now if i turn on my phone in fastboot, when i give an adb / fastboot command, the screen goes black and in the top left there is a very very small image " any key to shutdown". The same if i connect my phone in fastboot mode with mi unlocker
Hi everybody,
I'm trying to root my OnePlus 7t Pro with android 11 installed, but I can't figure out a way how to do so...
I read some other posts/threads and tried to root it installing Magisk canary but it still didn't work (it got stuck in the booting process, and I had to flash the stock boot image to get it working again). Does anybody have an other idea of something I could try? Magisk doesn't same to get it patched regardless of which version I use...
Thank you in advance for your help!
T4gB0t said:
Hi everybody,
I'm trying to root my OnePlus 7t Pro with android 11 installed, but I can't figure out a way how to do so...
I read some other posts/threads and tried to root it installing Magisk canary but it still didn't work (it got stuck in the booting process, and I had to flash the stock boot image to get it working again). Does anybody have an other idea of something I could try? Magisk doesn't same to get it patched regardless of which version I use...
Thank you in advance for your help!
Click to expand...
Click to collapse
You said it got stuck in booting process, was this after a fastboot flash patchedboot.img?
Hw4ng3r said:
You said it got stuck in booting process, was this after a fastboot flash patchedboot.img?
Click to expand...
Click to collapse
Yes, exactly... Sorry for not specifing. I patched the image, flashed it and than my phone stopped booting correctly and I had to flash the stock image to make it work again. I searched a little bit and found out that it was Magisk's fault and read that I had to try with the canary version, so I did but it still did not work and I was stuck on the same point as before.
T4gB0t said:
Yes, exactly... Sorry for not specifing. I patched the image, flashed it and than my phone stopped booting correctly and I had to flash the stock image to make it work again. I searched a little bit and found out that it was Magisk's fault and read that I had to try with the canary version, so I did but it still did not work and I was stuck on the same point as before.
Click to expand...
Click to collapse
Have you tried just fastboot boot patched.img and doing a direct install through Magisk?
I know some people reported their phones borking after trying to fastboot flash.
Hw4ng3r said:
Have you tried just fastboot boot patched.img and doing a direct install through Magisk?
I know some people reported their phones borking after trying to fastboot flash.
Click to expand...
Click to collapse
Sorry, I'm not really sure if I understood what you meant....
I thought that maybe I could try to downgrade to android 11 to then root and upgrade while remaining root. What do you think about this idea? And do you know how I could downgrade my phone? I did some research but did not find anything useful...
T4gB0t said:
Sorry, I'm not really sure if I understood what you meant....
I thought that maybe I could try to downgrade to android 11 to then root and upgrade while remaining root. What do you think about this idea? And do you know how I could downgrade my phone? I did some research but did not find anything useful...
Click to expand...
Click to collapse
So you would take your stock Android 11 boot.img and patch it like you would in Magisk Manager. Save the patched.img to your computer. Reboot to bootloader and apply command fastboot boot patched.img. this should restart your phone using the patched.img. once it starts, go into Magisk Manager and click Install > Direct Install > Reboot when asked.
You could certainly go back to A10 from A11 but you will lose all your data. The method above does work. Where did you get the stock boot.img?
Hw4ng3r said:
So you would take your stock Android 11 boot.img and patch it like you would in Magisk Manager. Save the patched.img to your computer. Reboot to bootloader and apply command fastboot boot patched.img. this should restart your phone using the patched.img. once it starts, go into Magisk Manager and click Install > Direct Install > Reboot when asked.
You could certainly go back to A10 from A11 but you will lose all your data. The method above does work. Where did you get the stock boot.img?
Click to expand...
Click to collapse
I downloaded the software from the official website and used payload dumper to extract the boot image. To be sure that I understood everything... you suggested to use "fastboot boot patched.img" instead of "fastboot flash boot patched.img", and once the phone restarted to go to magisk manager and click direct install.
Do I need Magisk Manager canary or the normal version for this to work and do I have to mantain the canary version or can I install the normal version once it is rooted?
Either 22.1 or Canary works for A11
Hw4ng3r said:
Either 22.1 or Canary works for A11
Click to expand...
Click to collapse
Okay thank you very much, I'll try and tell you. Thank you for your awesome help
T4gB0t said:
Okay thank you very much, I'll try and tell you. Thank you for your awesome help
Click to expand...
Click to collapse
One last question, is it normal that the "unlocked bootlader message" when booting shows up for almost two minutes? When I had Android 10 it did not take that much...
T4gB0t said:
One last question, is it normal that the "unlocked bootlader message" when booting shows up for almost two minutes? When I had Android 10 it did not take that much...
Click to expand...
Click to collapse
Yes for some reason, I noticed that as well on my device.
FYI, the patched boot may only work with Magisk canary
Hw4ng3r said:
Yes for some reason, I noticed that as well on my device.
FYI, the patched boot may only work with Magisk canary
Click to expand...
Click to collapse
So not Magisk v.23 but Magisk canary?
I know that there was rooting issues back at the end of last year, but I'm not sure exactly what version of Magisk it was at the time.
If you want to pass safety net on A11, I've read success posts with canary and Magisk hide
Hw4ng3r said:
I know that there was rooting issues back at the end of last year, but I'm not sure exactly what version of Magisk it was at the time.
If you want to pass safety net on A11, I've read success posts with canary and Magisk hide
Click to expand...
Click to collapse
Okay thanks, I'll try with v.23 first and If that does not work than I'll try with the canary one. Thank you very much!!!
Hiya, just use this TRWP. Decryption works on Android 11 (only tested on lineage).
Reboot to fastboot and use
fastboot flash recovery_a recovery.img
And
fastboot flash recovery_b recovery.img
And reboot to recovery.
Releases · Systemad/android_device_oneplus_hotdog
TWRP tree for OnePlus 7T/Pro (Hotdog/hotdogb). Contribute to Systemad/android_device_oneplus_hotdog development by creating an account on GitHub.
github.com
Wacko1805 said:
Hiya, just use this TRWP. Decryption works on Android 11 (only tested on lineage).
Reboot to fastboot and use
fastboot flash recovery_a recovery.img
And
fastboot flash recovery_b recovery.img
And reboot to recovery.
Releases · Systemad/android_device_oneplus_hotdog
TWRP tree for OnePlus 7T/Pro (Hotdog/hotdogb). Contribute to Systemad/android_device_oneplus_hotdog development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Okay thank you, I'll try if the other method does not work
T4gB0t said:
Okay thank you, I'll try if the other method does not work
Click to expand...
Click to collapse
Decrypt does not work on OOS and you do not need TWRP to Magisk.
Hw4ng3r said:
Decrypt does not work on OOS and you do not need TWRP to Magisk.
Click to expand...
Click to collapse
I'm sorry to bother you again, but I tried with "fastboot boot patched.img" and it still did not work. It got stuck while booting again with "unable to parse kernel log" as error message. Do you have any other suggestions?
P.S. I got a full backup with "adb backup -apk -all -shared -f /path/to/location" today and thought about just doing a factory reset, trying to root the phone, restore the backup. Do you think that might actually work? Thank you for your help!
How exactly did you patched your boot.img?
FSadino said:
How exactly did you patched your boot.img?
Click to expand...
Click to collapse
I tried doing it with magisk (both v.23 and canary)