I've been trying to root my Note 9T. The bootloader has been unlocked, and I've followed a guide from here: https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/
I'm now stuck in a bootloop.
Anyone been successful?
I additionally tried using a different version of TWRP, which wiped the "misc" partition. Can anyone provide an image dump of the misc partition so I can flash it back on? I can't find a copy of misc in the stock firmware file.
UPDATE 1:
I put the full stock image back on and am back to having a working unrooted phone, so I don't need the misc image. Would really like to get this thing rooted though.
I've installed the Magisk APK, patched the boot image, and flashed it. But this also results in a boot loop. If I flash the stock image back it works again. Any ideas what's going on here?
UPDATE 2:
I got it working! The key was to flash the stock vbmeta.img with fastboot functions to disable it.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Hiya. I've tried that and managed to get to the twrp page. However, when I go to install magisk via twrp, it just reboots into a bootloop. Any ideas?
Update: This seems to have worked.
[SOLVED] Phone gets stuck in bootloop if I try to install Magisk ZIP!
From the forum I followed these step to install magisk: - Patched my boot.img of my current rom using Magisk Manager and flashed via fastboot - After rebooting from fastboot it got stuck in recovery so had to wipe all data and it booted finally...
forum.xda-developers.com
Did you manage to get Magisk working after the reinstall of stock firmware, or you've just resolved the bootloop?
dsclee1 said:
I've been trying to root my Note 9T. The bootloader has been unlocked, and I've followed a guide from here: https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/
I'm now stuck in a bootloop.
Anyone been successful?
I additionally tried using a different version of TWRP, which wiped the "misc" partition. Can anyone provide an image dump of the misc partition so I can flash it back on? I can't find a copy of misc in the stock firmware file.
UPDATE 1:
I put the full stock image back on and am back to having a working unrooted phone, so I don't need the misc image. Would really like to get this thing rooted though.
I've installed the Magisk APK, patched the boot image, and flashed it. But this also results in a boot loop. If I flash the stock image back it works again. Any ideas what's going on here?
UPDATE 2:
I got it working! The key was to flash the stock vbmeta.img with fastboot functions to disable it.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
I'm interesting in at least rooting and if possible install TWRP .
Can you post i complete procedure to root the note 9 T ?
Thanks
I can have a go. But I'm not 100% sure what exact steps I took that got it working, as I flashed and re-flashed several times. Give this a try and let me know if it works or not?
WARNING: EXPECT TO LOSE ALL THE DATA ON YOUR PHONE!
Step 1
Obviously you need to unlock the bootloader first: https://en.miui.com/unlock/
If you haven't done this already, after your application it's likely you might have to wait 7 days before Xiaomi actually let you unlock.
Unlocking wipes your data.
Step 2
Start the phone normally. Copy the latest magisk apk (https://github.com/topjohnwu/Magisk/releases) over to the phone and install it.
Step 3
Find the correct original ROM for your device (https://xiaomifirmwareupdater.com/miui/cannong/). You'll need the full image. From the ROM extract the boot.img and vbmeta.img. Copy the boot.img over to your phone.
Step 4
In magisk choose the option to install and select "Select and Patch a File" (should be the only option anyway). Select the boot.img you copied over. This will produce a new file called something like "magisk_patched-22100_XXXXX.img". Copy this file off your phone and onto your computer.
Step 5
Boot your phone to fastboot mode (you should already know how to do this, as you would have had to have done it to unlock your phone in the first place - Hold down Volume Down and the Power button at the same time).
Step 6
Run the following commands (obviously replace the boot image with the correct magisk image, and use the vbmeta.img you took from the ROM):
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot magisk_patched-22100_XXXXX.img
Hopefully this will work. But I can't be 100% sure, as the disabling of "verity" could mean that your encrypted user data now can't be read (if you've only just unlocked the bootloader then you're not going to have any data anyway, so not too much of an issue). If this is the case it's likely you'll now need to factory reset the phone. Hold down Volume Up and Power on start to reach the stock recovery menu, and there's a selection for factory reset. You can also install TWRP at this point, and could then use it's factory reset function instead. I downloaded this version of TWRP: https://www.mediafire.com/file/ou8553psro9yyt2/3.4.2_redmi_note_9_5G.rar/file, which came from the other rooting guide (https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/ - which didn't work). Just flash that version of TWRP to the recovery partition (fastboot flash recovery recovery.img), and ignore all the steps given in the guide it came from.
Let me know how you get on.
sorry for the answer delay.
Adding my 2 cents about unlocking the bootlader .
In order to do it .
FIRST - do not try it from a virtual PC . It does not work (at least it did not work for me)
SECOND , before to run the xiaomi batch_unlock bootlader , don't forget to update google usb drivers
I hard some hard time to just connect the unlocker to my phone . Now i have to wait 167 hours to complete the process .
dsclee1 said:
I've been trying to root my Note 9T. The bootloader has been unlocked, and I've followed a guide from here: https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/
I'm now stuck in a bootloop.
Anyone been successful?
I additionally tried using a different version of TWRP, which wiped the "misc" partition. Can anyone provide an image dump of the misc partition so I can flash it back on? I can't find a copy of misc in the stock firmware file.
UPDATE 1:
I put the full stock image back on and am back to having a working unrooted phone, so I don't need the misc image. Would really like to get this thing rooted though.
I've installed the Magisk APK, patched the boot image, and flashed it. But this also results in a boot loop. If I flash the stock image back it works again. Any ideas what's going on here?
UPDATE 2:
I got it working! The key was to flash the stock vbmeta.img with fastboot functions to disable it.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
ive been trying for the last 4 hours to flash twrp on my redmi note 9T 5g global..can you please explain to me how you got it to work. i flashed the recovery.img and vbmeta.img file that i got from the unofficialtwrp.com download, when i flash boot recovery.img, it just reboots my phone into normal...and i missing something? My device is on Miui 12.0.8.0 andriod 10. should i be on the new update 12.5 andriod 11 for it to work. Please help.
dsclee1 said:
I can have a go. But I'm not 100% sure what exact steps I took that got it working, as I flashed and re-flashed several times. Give this a try and let me know if it works or not?
WARNING: EXPECT TO LOSE ALL THE DATA ON YOUR PHONE!
Step 1
Obviously you need to unlock the bootloader first: https://en.miui.com/unlock/
If you haven't done this already, after your application it's likely you might have to wait 7 days before Xiaomi actually let you unlock.
Unlocking wipes your data.
Step 2
Start the phone normally. Copy the latest magisk apk (https://github.com/topjohnwu/Magisk/releases) over to the phone and install it.
Step 3
Find the correct original ROM for your device (https://xiaomifirmwareupdater.com/miui/cannong/). You'll need the full image. From the ROM extract the boot.img and vbmeta.img. Copy the boot.img over to your phone.
Step 4
In magisk choose the option to install and select "Select and Patch a File" (should be the only option anyway). Select the boot.img you copied over. This will produce a new file called something like "magisk_patched-22100_XXXXX.img". Copy this file off your phone and onto your computer.
Step 5
Boot your phone to fastboot mode (you should already know how to do this, as you would have had to have done it to unlock your phone in the first place - Hold down Volume Down and the Power button at the same time).
Step 6
Run the following commands (obviously replace the boot image with the correct magisk image, and use the vbmeta.img you took from the ROM):
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot magisk_patched-22100_XXXXX.img
Hopefully this will work. But I can't be 100% sure, as the disabling of "verity" could mean that your encrypted user data now can't be read (if you've only just unlocked the bootloader then you're not going to have any data anyway, so not too much of an issue). If this is the case it's likely you'll now need to factory reset the phone. Hold down Volume Up and Power on start to reach the stock recovery menu, and there's a selection for factory reset. You can also install TWRP at this point, and could then use it's factory reset function instead. I downloaded this version of TWRP: https://www.mediafire.com/file/ou8553psro9yyt2/3.4.2_redmi_note_9_5G.rar/file, which came from the other rooting guide (https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/ - which didn't work). Just flash that version of TWRP to the recovery partition (fastboot flash recovery recovery.img), and ignore all the steps given in the guide it came from.
Let me know how you get on.
Click to expand...
Click to collapse
should I be on the latest version of Miui...12.5 android 11? for me to be able to install twrp. i downgraded back to Miui 12.0.8.0 android 10 as i didnt like my data folder been blocked in android folder. My device is global cannong redmi 9T 5g with diminsity 800u soc, can you please help if you can. thanks in advance
Android 10 is fine. You need to fastboot flash recovery recovery.img
To boot into it you need to turn the phone off, then hold vol up and power until you feel a buzz, then let go.
I have the same Problem as HighEndGamer:
if I enter 'fastboot flash recovery recovery.img', it sayes that everything worked OK in just a few seconds. But nothing realy happend!
If I enter 'fastboot boot recovery.img', phone boot just as normal.
If I enter 'fastboot oem device-info', it sayes "FAILED (remote: unknown command)'.
If I enter 'fastboot oem lock', it works and I have to start from the beginning..
I have MIUI Global 12.0.2.0{QJEEUMX)
chmick said:
sorry for the answer delay.
Adding my 2 cents about unlocking the bootlader .
In order to do it .
FIRST - do not try it from a virtual PC . It does not work (at least it did not work for me)
SECOND , before to run the xiaomi batch_unlock bootlader , don't forget to update google usb drivers
I hard some hard time to just connect the unlocker to my phone . Now i have to wait 167 hours to complete the process .
Click to expand...
Click to collapse
I confirm it does not work from a VM (and the need for latest drivers). There is something funky going on with the USB communication when running from a VM: the first call of the fastboot executable from the windows VM generally works fine, but any other call hang. So the batch_unlock tool cannot work (since it does call fastboot several times).
Related
HW_Version -
Bootloader Version - unknown
IFWI Version - 0094 - 1069
Serial Number - my #
Signing - ?
Secure_boot - ?
RESULT: FAILD (remote: flash_cmds error!)
Thats what my bootloader looks like. What happened was I tried to update from Stock .184 to the new MM build. I downloaded the file and got prompted the update in my phone. It installed or did something and when it rebooted I was stuck in a bootloop with no screen.
I ended up using xFSTK Downloader everything went fine, my phone turned on with 4 colored bars and brought me in to the bootloader. I proceed to use Asus Flash Tool to flash the raw file of .194 and that's where my problem started.
It was taking soo long so I took my dog out for a good 15-20 min walk came back and the flash tool was still doing its thing and the green bar was still moving and on my phone it said RESULT OKAY.
I ended up closing the Flash Tool because it was taking soo long. I rebooted my phone then it goes in a bootloop with the 4 colored bars on the screen. Then I just keep repeating these steps and can't get anywhere.
When I am able to get in the bootloader after using xFSTK Downloader I cant use some flashboot commands. I cant flash twrp because I get FAILD (remote: flash_cmds error!) .
I was going by this guide here. http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
EDIT: I just noticed that my phone doesnt come up as MOOREFIELD in device manager. when it turns on and goes in to the bootloader it shows for a second and goes away.
I'm very thankful for anyone that responds. Thx for reading.
I just had this problem after a bad flash~
The instructions of unbricking the phone was lacking some infos.
So I tried a lot of experiments just to unbrick this piece of crap XD
If you are successful on xFSTK procedure you'll end up on "fastboot" mode.
Then you'll proceed with the flashing tool. According to your description everything is just normal my mate~
Now this is the REAL DEAL.
You may notice an ENDLESS "Flash Image" on your flash tool.
Now look on your phone in the Fastboot mode. If you see that the "RESULT: OKAY" seems got stuck, its ok my friend its normal (it will take about 10-30mins depending on your PC).
• Unplug your phone, re-plug it in
• Close AFT
• End process "a500cgfastboot.exe" in the task manager"
Then do the FASTBOOT commands:
• fastboot flash splashimage splashimage.img
• fastboot fastboot flash droidboot.img
• fastboot flash boot boot.img
• fastboot flash recovery recovery.img
AND! you can now proceed on your recovery menu.
You may ADB Sideload the stock firmware by doing
• adb sideload UL-Z00A-WW-X.XX.XX.XX-user.zip (replace the "X" of what file version you want to flash)
And wait for it to reboot. I really hope this helps you mate~
#cheers!
Reflash in xfstk, press dload ...power plus vol + together till phone recycles and flash begins , check my signature below for tutorial, read whole thread and watch video.
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.
Just so you know why it happened. You HAVE to be at version 194 before you update to MM! Otherwise... Boom
Sent from my ASUS_Z00A using Tapatalk
This is not so, I sideloaded MM fine straight on .184
No problem sideloading
kenbo111 said:
Just so you know why it happened. You HAVE to be at version 194 before you update to MM! Otherwise... Boom
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
I wish they said that in the steps for updating on their site
Chrodechild said:
I just had this problem after a bad flash~
The instructions of unbricking the phone was lacking some infos.
So I tried a lot of experiments just to unbrick this piece of crap XD
If you are successful on xFSTK procedure you'll end up on "fastboot" mode.
Then you'll proceed with the flashing tool. According to your description everything is just normal my mate~
Now this is the REAL DEAL.
You may notice an ENDLESS "Flash Image" on your flash tool.
Now look on your phone in the Fastboot mode. If you see that the "RESULT: OKAY" seems got stuck, its ok my friend its normal (it will take about 10-30mins depending on your PC).
• Unplug your phone, re-plug it in
• Close AFT
• End process "a500cgfastboot.exe" in the task manager"
Then do the FASTBOOT commands:
• fastboot flash splashimage splashimage.img
• fastboot fastboot flash droidboot.img
• fastboot flash boot boot.img
• fastboot flash recovery recovery.img
AND! you can now proceed on your recovery menu.
You may ADB Sideload the stock firmware by doing
• adb sideload UL-Z00A-WW-X.XX.XX.XX-user.zip (replace the "X" of what file version you want to flash)
And wait for it to reboot. I really hope this helps you mate~
#cheers!
Click to expand...
Click to collapse
im gonna get some breakfest in my belly and have another go at it.. couldnt use have my phone at all yesterday and I tried fixing it for atleast 8-10 hour.. it sucks lol.
timbernot said:
Reflash in xfstk, press dload ...power plus vol + together till phone recycles and flash begins , check my signature below for tutorial, read whole thread and watch video.
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.
Click to expand...
Click to collapse
Ill watch you video and see if it helps. the instructions on the unbrick I was using was kinda hard to understand for the most part.
timbernot said:
This is not so, I sideloaded MM fine straight on .184
No problem sideloading
Click to expand...
Click to collapse
After a long day yesterday and the flsah process getting stuck, I uninstalled everything and reinstalled everything required for this process. When I finish with xfstk then move on to the flash tool it starts to flash then it stops says Flash image failure[FAILD [wrong image format]]
Im getting so fusturated with this phone its crazy.. I just got in a month ago too.
So now it seems I can use xFSTK and now im in the bootloader with the 4 color bars. But when I goto flash using the Flash tool my phone just sits on FASTBOOT CMD WAITING and the flash tool fails with FLASH IMAGE Failure[FAILED[wrong image format]]
I need some serious help :[
quarterbreed said:
After a long day yesterday and the flsah process getting stuck, I uninstalled everything and reinstalled everything required for this process. When I finish with xfstk then move on to the flash tool it starts to flash then it stops says Flash image failure[FAILD [wrong image format]]
Im getting so fusturated with this phone its crazy.. I just got in a month ago too.
Click to expand...
Click to collapse
well lot of people facing problem. as you told that you are able to get into fastboot after xFSTK process. and you are unable to flash raw firmware file!!!! well perform xFSTK again. get into fastboot and perform following steps:
very first of all. rename .raw firmware file to .zip file and extract all files in there.. now place all files in adb and fastboot folder. open command window here. ( where you places files from raw firmware and adb and fast boot tool folder) perform the following commands
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem erase_token
4. fastboot oem start_partitioning
5. fastboot flash /tmp/partition.tbl partition.tbl
6. fastboot oem partition /tmp/partition.tbl
7. fastboot erase system
8. fastboot erase cache
9. fastboot erase data
10. fastboot erase APD
11. fastboot erase ADF
12. fastboot oem wipe splashscreen
13. fastboot oem stop_partitioning
14. fastboot flash fastboot droidboot_sign.bin
15. fastboot flash token PROD_BOM_Full.bin
16. fastboot flash ifwi ifwi-prod.bin
17. fastboot flash splashscreen splash_sign.bin
18. fastboot flash boot boot_sign.bin
19. fastboot flash recovery recovery_sign.bin
20. fastboot flash APD APD.img
21. fastboot flash system system.img
22. fastboot reboot
hope it will work fine. hit thanks if helped. if any further question please post.
sukhwant717 said:
well lot of people facing problem. as you told that you are able to get into fastboot after xFSTK process. and you are unable to flash raw firmware file!!!! well perform xFSTK again. get into fastboot and perform following steps:
very first of all. rename .raw firmware file to .zip file and extract all files in there.. now place all files in adb and fastboot folder. open command window here. ( where you places files from raw firmware and adb and fast boot tool folder) perform the following commands
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem erase_token
4. fastboot oem start_partitioning
5. fastboot flash /tmp/partition.tbl partition.tbl
6. fastboot oem partition /tmp/partition.tbl
7. fastboot erase system
8. fastboot erase cache
9. fastboot erase data
10. fastboot erase APD
11. fastboot erase ADF
12. fastboot oem wipe splashscreen
13. fastboot oem stop_partitioning
14. fastboot flash fastboot droidboot_sign.bin
15. fastboot flash token PROD_BOM_Full.bin
16. fastboot flash ifwi ifwi-prod.bin
17. fastboot flash splashscreen splash_sign.bin
18. fastboot flash boot boot_sign.bin
19. fastboot flash recovery recovery_sign.bin
20. fastboot flash APD APD.img
21. fastboot flash system system.img
22. fastboot reboot
hope it will work fine. hit thanks if helped. if any further question please post.
Click to expand...
Click to collapse
Thx for the detailed post.. I got in to my phone finally after messing with it all day yesterday and I close to throwing it against the wall lol. It worked like a charm.. I wonder why the flash tool wouldnt work.
Now how would I go about side loading .194 and installing a recovery like twrp again so I can back this thing up once i get to mm.
quarterbreed said:
Thx for the detailed post.. I got in to my phone finally after messing with it all day yesterday and I close to throwing it against the wall lol. It worked like a charm.. I wonder why the flash tool wouldnt work.
Now how would I go about side loading .194 and installing a recovery like twrp again so I can back this thing up once i get to mm.
Click to expand...
Click to collapse
you can side load 194... works well... after 194 you can also install latest official marshmallow. but do not install custom recovery if you want to install lates MM. first install 194 then latest MM. then custom recovery
sukhwant717 said:
you can side load 194... works well... after 194 you can also install latest official marshmallow. but do not install custom recovery if you want to install lates MM. first install 194 then latest MM. then custom recovery
Click to expand...
Click to collapse
opps my bad. what you helped me with put .194 on my phone already. I ment am I able to download the MM rom and do the system update with it again. Or should I side load it? Im not sure how to side load. After I do get MM on what recovery do you recommend. I did have the latest TRWP before all this happend, Is that what caused this brick? because when it flashed mm before I think it brought me into trwp.
quarterbreed said:
opps my bad. what you helped me with put .194 on my phone already. I ment am I able to download the MM rom and do the system update with it again. Or should I side load it? Im not sure how to side load. After I do get MM on what recovery do you recommend. I did have the latest TRWP before all this happend, Is that what caused this brick? because when it flashed mm before I think it brought me into trwp.
Click to expand...
Click to collapse
posting new thread. do not update to official MM if you have custom recovery or you have rooted phone. though after install MM you can install custom Recovery afterwards. not tried but i think will not cause any issue
yes cause of brick is custom recovery
sukhwant717 said:
posting new thread. do not update to official MM if you have custom recovery or you have rooted phone. though after install MM you can install custom Recovery afterwards. not tried but i think will not cause any issue
yes cause of brick is custom recovery
Click to expand...
Click to collapse
I have no recovery installed I tried to get to bootloader with adb and it showed the android guy with a error. How do I go about flashing the new MM build. I really dont want to mess up my phone again lol. Only thing I have on its is .194 atm.
Is it ok to put the MM build on my internal storage and apply the system update from there?
quarterbreed said:
opps my bad. what you helped me with put .194 on my phone already. I ment am I able to download the MM rom and do the system update with it again. Or should I side load it? Im not sure how to side load. After I do get MM on what recovery do you recommend. I did have the latest TRWP before all this happend, Is that what caused this brick? because when it flashed mm before I think it brought me into trwp.
Click to expand...
Click to collapse
quarterbreed said:
I have no recovery installed I tried to get to bootloader with adb and it showed the android guy with a error. How do I go about flashing the new MM build. I really dont want to mess up my phone again lol. Only thing I have on its is .194 atm.
Click to expand...
Click to collapse
can you post screenshot.
hope you performed factory restore after installing Z00A-WW-2.20.40.194-
try adb reboot recovery
sukhwant717 said:
can you post screenshot.
hope you performed factory restore after installing Z00A-WW-2.20.40.194-
try adb reboot recovery
Click to expand...
Click to collapse
I didnt do a factory restore after installing .194 I'll do that now.
sukhwant717 said:
can you post screenshot.
hope you performed factory restore after installing Z00A-WW-2.20.40.194-
try adb reboot recovery
Click to expand...
Click to collapse
Im sure what you mean sorry. I have .194 on my phone with the help of your steps in fastboot. It booted and im in my phone and its updating all my apps and stuff..
Do you mean factory restore in bootloader? If so I tried adb reboot recovery the phone restarts and goes to a screen with https://i.ytimg.com/vi/wuixmZ11Kyc/maxresdefault.jpg Im guessing if i cant get in to recovery I cant do a factory restore?
in fastboot my bootloader doesnt have a version number it just says unknown
EDIT when the picture above showed up I held the power button and vol + to get into recovery and its performing a factory reset atm.
Anyone else bricked ?
Unbrick and into system with correct serial and imei numbers in 20 mins ..see my signature for zubes ..
PS, save yourself days of pain , after xfstk , flash an earlier raw ..
PMSL
---------- Post added at 08:22 AM ---------- Previous post was at 08:18 AM ----------
timbernot said:
Reflash in xfstk, press dload ...power plus vol + together till phone recycles and flash begins , check my signature below for tutorial, read whole thread and watch video.
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.
Click to expand...
Click to collapse
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.
Hello, I am currently rooted and on stock on pixel xl. I am trying to flash the pure nexus rom. I downloaded through the link in the op, factory reset and flashed through twrp (3.0.2rc1). When I went to reboot, it said OS not installed. Can anyone offer any assistance with this? Needless to say, I didn't reboot with that. I did however do a backup (of stock) prior to this. I decided to restore my backup but when it rebooted it said something about the vender image is not right with this system and to flash the correct image. This is exactly what its saying : Your vendor image does not match the system. Please flash the NOF27C vendor image for your device. I have managed to move the correct image file to the internal storage but from what i read, can only install through twrp.
And when it finished rebooting, now 90% of my apps are crashing, no fingerprint hardware, developer options are not available and I had to reboot back into recovery but its like twrp is gone, it looks like the stock recovery. Somehow it appears there are parts of my stock rom and pure nexus rom combined which is understandbly causing my issues. Right now I am trying to get back to having twrp but am stuck.
I have since tried to reinstall twrp but when I plug my xl into my pc, the pc recognizes it but no storage. I cant move a file from pc to xl because its saying disconnected or not responding. Tried to get a command prompt and when I shift/right click, there is no option. I don't know what else to do.
If anyone has any suggestions, please help. I am freaking over this. Can't use my phone in the state its in.
Sounds far from bricked.
Just entirely screwed up.
FASTboot the latest factory image and then refrain from tinkering for the weekend.
These are the steps i use.
I think a new ADB/FastBoot package was released yesterday you might want to install that.
Execute fastboot commands (assuming the bin is on your PATH)
fastboot flash bootloader c:\_PIXEL_XL_\bootloader.img
fastboot reboot-bootloader
fastboot flash radio c:\_PIXEL_XL_\radio.img
fastboot reboot-bootloader
fastboot flash boot_a c:\_PIXEL_XL_\boot.img
fastboot flash boot_b c:\_PIXEL_XL_\boot.img
fastboot flash system c:\_PIXEL_XL_\system.img
fastboot flash system_b c:\_PIXEL_XL_\system_other.img
fastboot flash vendor c:\_PIXEL_XL_\vendor.img
fastboot flash modem c:\_PIXEL_XL_\modem.img
fastboot reboot
To add TWRP and Root:
fastboot boot c:\_PIXEL_XL_\twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip
My Honor 7x (BND-L21) is totally bricked for the moment. I think there is Nougat and Oreo partitions at the same time because of Huawei Multi-Tool. Now I can't boot into recovery/eRecovery and the device stucks in the splash screen (bootloader unlocked). I think I have to rewrite all the partitions but I don't know how to do it... If anybody has a solution it will be greatly appreciated, I tried for 1 week!
If your device has a locked bootloader or frp follow these steps
First of charge your device for 1 hour in whatever mode it is..
https://www.androidfilehost.com/?fid=11050483647474828964
Then download the service rom from the above link
Extract the contents of the downloaded file. Copy the dload folder from the extracted files to a sdcard.. (Directly to it not on any directory)
Insert the sd card..
Press all the buttons until the emui logo comes.
After the flashing reaches 100 percent.. Reboot the device unlock the oem in developer option..
Step-2 (Computer)
Download adb drivers and fastboot and install them.
Download complete ota package for your device (make sure you have the correct build number because service rom has a different build number ) (download size will be above 2gb)
Extract all downloaded zip files. Then using huawei firmware extractor extract all contents of the update. app files.. (one update. App file in each zip files)
Copy
kernel. Img
Ramdisk. Img
System. Img
Cust. Img
Version. Img
Vendor. Img
And version. Img to the folder having adb files. And version and vendor files to sd card
//Make sure that the complete ota package you downloaded matches the os before the software brick(noughat or oreo) //
Open the adb folder and do shift plus right click to open command window there and connect your device in fastboot mode to pc
Use the below commands one by one each after completion
Fastboot devices(show your device if its connected)
Fastboot oem unlock (code obtained from huawei unlock page)
#factory rest occur
After tha enter fastboot mode again
Step-3
Fastboot flash ramdisk ramdisk.img
Fastboot flash recovery_ramdisk recovery_ramdisk. Img
Fastboot flash system system. Img
Fastboot flash cust cust.img
Flash twrp using
Fastboot flash recovery_ramdisk twrp. img
Boot your device to recovery mode.( Volume up plus power)
Flash version. Img to version partition and vendor. Img to vendor partition
If you want stock recovery back
Boot into fastboot mode
Enter the command
fastboot flash recovery_ramdisk recovery_ramdisk. Img
And do a reboot
Relock bootloader upto your wish..
Better keep oem unlocked in developer options
If you have both unlocked bootloader and frp follow from step 2
I heard huawei discontinued the unlock page
In that case use dc unlocker to find the code
It will cost some money
All credits to @mrmazak
Thank you I will try this but the dload method didn't worked when I tried 4 days ago...
I can't go into dload update mode (when I hold all the physical buttons the phone restarts and this appears (picture 1) and got stuck on this screen).
Also I don't know why but the phone doesn't charge, when I unplug it after 1h of charge, it shows the critical battery screen (picture 2) and it goes off...
Any help is reaaly appreciated!
Any other ideas?
gabrce said:
Any other ideas?
Click to expand...
Click to collapse
Though situation, if not charging. Bit to verify, try different cable and charging brick to make sure.
I changed twice the cable and nothing change...
Is there a method to factory reset the device in fastboot mode?
Maybe I should try HWOTA8?
gabrce said:
Maybe I should try HWOTA8?
Click to expand...
Click to collapse
Will need to de able to boot twrp for hwota to work.
So what should I do? Is there a method to flash twrp without fail? Because I can't boot into it...
gabrce said:
So what should I do? Is there a method to flash twrp without fail? Because I can't boot into it...
Click to expand...
Click to collapse
If battery is not charging, then it will not take a flash.
You can maybe try remove back cover and unplug battery, then reconnect see if it will take a charge.
As for your question about resetting with fastboot. You can wipe data, and maybe format system also. But I don't think that will help you.
My friend is asking help. His situation is similar. The phone is honor 6x.
My opinion is that something wrong with boot partition. you can ask some body extract the boot image from another phone. Then run "fastboot flash boot_ramdisk boot.img".
Hope it helps
Thank you for your answer.
This command didn’t work.
My phone got stuck for one month now...I’m desesperate...
gabrce said:
Thank you for your answer.
This command didn’t work.
My phone got stuck for one month now...I’m desesperate...
Click to expand...
Click to collapse
I try to help again.
Describe problem please
As I recall it is as follows
** Phone working,
** Attempts some backup or restore using multi-tool
** This made phone no longer boot
**Possible that nougat images flashes to Oreo partition tanle (or visa- versa)
**Now no recovery or erecovery will even boot.
**Also phone shuts off with low battery as soon as cable unplugged.
If this is the case, I see no way forward. Because the battery needs to hold something in order for flashing to complete
Hello, I have sent my phone to warranty and after that I received a phone with NO RPMB and after many frustrations I found (with help of many users and forums) how to workaround this..
To start:
Download boot image from here
Download twrp from the official website
Change the name to boot.img and twrp.img and put it in the platform-tools folder
Open the terminal there
Download your favourite rom
Enter fastboot mode on your phone
!!!!After this you will loose all of your data!!!!
Paste this to the terminal
fastboot oem unlock
(select yes on your phone)
fastboot flash boot boot.img
fastboot flash recovery twrp.img
fastboot format userdata
fastboot format cache
Reboot to recovery (if it doesn't enter at the first time enter download mode again and restart to recovery)
After that you have twrp and can flash every rom.. yay!!!
Wipe everything.
Copy the rom zip to your phone using MTP
Install your fancy new rom
If you want to install magisk:
Install the magisk manager.
On the app select install and select patch image file. (it will create a new boot image already patched)
After that install the new image (patched_boot.img) using twrp
Do a clean instalation of your ROM (recomended) or a Factory Reset first
Reboot to twrp
Select install
Click in install image
Select patched_boot.img
Select install to boot partition
Reboot.
Install magisk manager and do the sugested setup.
You now have magisk working
Thanks to all the users that helped me!!
I had real trouble getting twrp to work the last time I tried this a few months ago. Followed the steps here and am now on pixel experience with magisk. Thanks!
Hello, im in the same situation of NO RPMB. This procedure will permanently lets have bootloader unlocked?
About Magisk, i can install it in usual way once im in the recovery? (I mean download latest stable version for Bullhead and flash via TWRP).
Thanks.
sigibian said:
Hello, im in the same situation of NO RPMB. This procedure will permanently lets have bootloader unlocked?
About Magisk, i can install it in usual way once im in the recovery? (I mean download latest stable version for Bullhead and flash via TWRP).
Thanks.
Click to expand...
Click to collapse
My bootloader is still unlocked after following this guide
For Magisk:
-Install your custom ROM and boot it up (without root)
-Then extract the boot.img from the ROM zip file and save it on your phone storage.
-Install the Magisk manager apk
-In Magisk manager, select install Magisk> choose the patch boot image option and -Select the boot.img you previously saved.
Once it's done, reboot into twrp and flash the patched boot.img. When you reboot Magisk will be working.
I've had no issues with my bootloader, even after an ota update for pixel experience.
Thank you, i will try it.
Another question. I never tried dowload mode before, as i read in other post i should Plug USB cable into pc, Hold volume up and power at the same time and plug phone into usb that's already connected to pc, right?
When in download mode i can fire up fastboot commands like im in bootloader mode?
So then after do last command fastboot format cache i can reboot to recovery from terminal using adb reboot recovery or i can / should do it from device?
About twrp it's ok to use the latest 3.2.3.0 official version or the 3.2.1 4core version from here as someone suggested from Reddit? https://forum.xda-developers.com/nexus-5x/development/recovery-twrp-3-2-1-4-core-t3796656
sigibian said:
Thank you, i will try it.
Another question. I never tried dowload mode before, as i read in other post i should Plug USB cable into pc, Hold volume up and power at the same time and plug phone into usb that's already connected to pc, right?
When in download mode i can fire up fastboot commands like im in bootloader mode?
So then after do last command fastboot format cache i can reboot to recovery from terminal using adb reboot recovery or i can / should do it from device?
About twrp it's ok to use the latest 3.2.3.0 official version or the 3.2.1 4core version from here as someone suggested from Reddit? https://forum.xda-developers.com/nexus-5x/development/recovery-twrp-3-2-1-4-core-t3796656
Click to expand...
Click to collapse
The official twrp works for fine for me, haven't tried the 4 core version but it can't hurt to try if you need it.
Power off your phone then press and hold volume - and power to enter bootloader, then connect to your pc and follow the steps in the OP
So i have to enter in bootloader mode? At point 6 of OP there is written to enter in the download mode, this makes me confusing.
Can anyone explain me latest 2 commands why they are needed?
fastboot format userdata
fastboot format cache
sigibian said:
So i have to enter in bootloader mode? At point 6 of OP there is written to enter in the download mode, this makes me confusing.
Can anyone explain me latest 2 commands why they are needed?
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
This thread is fairly comprehensive;
https://forum.xda-developers.com/nexus-5x/general/moto-nexus-5x-sticky-roll-t3207487
Holding volume - and power takes you to fastboot mode (download mode essentially), theres also an option to reboot into recovery (selectable using the volume keys.)
Formatting user data and cache is necessary prior to installing a new rom (especially if moving from stock). You lose all data (back up first!) But a clean flash is the best place to start.
baddesthad said:
This thread is fairly comprehensive;
https://forum.xda-developers.com/nexus-5x/general/moto-nexus-5x-sticky-roll-t3207487
Holding volume - and power takes you to fastboot mode (download mode essentially), theres also an option to reboot into recovery (selectable using the volume keys.)
Formatting user data and cache is necessary prior to installing a new rom (especially if moving from stock). You lose all data (back up first!) But a clean flash is the best place to start.
Click to expand...
Click to collapse
Thanks for the explanation but for installing a new ROM usually you can do factory reset directly in TWRP, plus doing all the wipes, this should be enough.
About fastboot mode and download mode, they are completely different, fastboot mode: vol down + power, download mode for LG: Plug USB cable into pc, Hold volume up and power at the same time and plug phone into usb.
My question is what i can do in download mode? As OP says after entering download mode open terminal and use fastboot commands.
sigibian said:
Thanks for the explanation but for installing a new ROM usually you can do factory reset directly in TWRP, plus doing all the wipes, this should be enough.
About fastboot mode and download mode, they are completely different, fastboot mode: vol down + power, download mode for LG: Plug USB cable into pc, Hold volume up and power at the same time and plug phone into usb.
My question is what i can do in download mode? As OP says after entering download mode open terminal and use fastboot commands.
Click to expand...
Click to collapse
You need to use vol- and power to go into fastboot mode then connect to the pc. As for userdata and cache, if you don't clean them when coming from stock you will have issues (your data will be encrypted if you're on stock?). As I said this guide worked for me. The op was talking about fastboot mode in the 6th option (also there is much more information in the thread I linked above)
sorry for the confusing i wanted to say fastboot mode..
i knew the thread that you are saying but most people doesn't want to search so I made a little thread only with the needed parts..
I use it myself so I have a place to remember all the steps when I need to change the rom to a new one or when I make experiments and brick my phone XD
If anyone know anything else that should be in here just say, I really want to improve the post
Hi. I just went through the whole process several times (I have tried the different modified boot images from the dedicated post) and my device is still locked [emoji24] any suggestions?
fhartane said:
Hi. I just went through the whole process several times (I have tried the different modified boot images from the dedicated post) and my device is still locked [emoji24] any suggestions?
Click to expand...
Click to collapse
your device will always be locked this is a workaround to get twrp, new roms and magisk while it stays locked..
with twrp usable it won't matter if you are locked or not
PedroM.CostaAndrade said:
your device will always be locked this is a workaround to get twrp, new roms and magisk while it stays locked..
with twrp usable it won't matter if you are locked or not
Click to expand...
Click to collapse
Thanks for the answer. You mean that now I have twrp, I can flash custom Roms with my bootloader locked without any issue?
Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
Yes if you have TWRP you can install custom ROMs, custom Kernel's, magisk, super su, etc..
the locked bootloader only prevents you from using fastboot commands like the one needed for installing custom recovery
Now that you have TWRP you can use it for everything
Hello everyone, I also have a nexus 5x with motherboard that has been replaced under warranty and unfortunately I can't keep the bootloader unlocked.
I tried the procedure you have indicated, but at this point there is the problem, because after inserting the boot.img and twrp.img inside the phone, then when I go to do the unlocking procedure with 'fastboot oem unlock (select yes on your phone) 'in practice the memory is deleted on the phone, so I lose the previously uploaded files, and therefore I can no longer continue with the flash procedure of boot.img and twrp.img because they are no longer present in memory.
I hope I made myself understood, maybe I am wrong, or is there a way to solve this problem?
Fabiojoker said:
Hello everyone, I also have a nexus 5x with motherboard that has been replaced under warranty and unfortunately I can't keep the bootloader unlocked.
I tried the procedure you have indicated, but at this point there is the problem, because after inserting the boot.img and twrp.img inside the phone, then when I go to do the unlocking procedure with 'fastboot oem unlock (select yes on your phone) 'in practice the memory is deleted on the phone, so I lose the previously uploaded files, and therefore I can no longer continue with the flash procedure of boot.img and twrp.img because they are no longer present in memory.
I hope I made myself understood, maybe I am wrong, or is there a way to solve this problem?
Click to expand...
Click to collapse
fastboot is for the files on your PC not your phone
you need to put the files inside of platform-tools and then open cmd inside it and use the fastboot commands
fastboot will take the files of your PC
Hello, thank you for your information, since I haven't done modding on phones for a long time, I didn't remember exactly the procedure with fastboot and therefore I didn't understand where I had to put the files, but in the end I did it.
Thank you
PedroM.CostaAndrade said:
fastboot is for the files on your PC not your phone
you need to put the files inside of platform-tools and then open cmd inside it and use the fastboot commands
fastboot will take the files of your PC
Click to expand...
Click to collapse
Why is a custom boot image needed? I don't want to root.
Hello every body
i cant find the magisk_patched 10.3.3 (Indian version), i searched every were but unfortunately i couldn't find it, i also try to extracted the boot.img from the update zip through payload dumper and then batch it on old nexus 6 device which is retired as workaround solution then try to flash the file via fastboot but it keeps looping at fastboot screen
please help guy i need the magisk_patched 10.3.3 (Indian version) file so my phone work back to normal
any help is highly appreciated
God bless you all
suhb20 said:
Hello every body
i cant find the magisk_patched 10.3.3 (Indian version), i searched every were but unfortunately i couldn't find it, i also try to extracted the boot.img from the update zip through payload dumper and then batch it on old nexus 6 device which is retired as workaround solution then try to flash the file via fastboot but it keeps looping at fastboot screen
please help guy i need the magisk_patched 10.3.3 (Indian version) file so my phone work back to normal
any help is highly appreciated
God bless you all
Click to expand...
Click to collapse
from Next time do this,
Don't ever flash some random Boot image from Internet, just boot it -
In short -
Get a recently magisk patched boot image (either recent beta or recent stable build patched boot image)
Connect your phone to PC
now reboot to bootloader and run this command,
fastboot boot magisk_patched.img
Don't flash boot image
Install Magisk manager and from it select Install > Direct install
Reboot
But since you have already flashed the wrong one. Here , flash the magisk_patched boot img of 10.3.3 Indian Build -
https://androidfilehost.com/?fid=8889791610682876433
Note : I am not responsible if anything goes wrong, Flash it at your own risk.
Aswin08 said:
from Next time do this,
Don't ever flash some random Boot image from Internet, just boot it -
In short -
Get a recently magisk patched boot image (either recent beta or recent stable build patched boot image)
Connect your phone to PC
now reboot to bootloader and run this command,
fastboot boot magisk_patched.img
Don't flash boot image
Install Magisk manager and from it select Install > Direct install
Reboot
But since you have already flashed the wrong one. Here , flash the magisk_patched boot img of 10.3.3 Indian Build -
https://androidfilehost.com/?fid=8889791610682876433
Note : I am not responsible if anything goes wrong, Flash it at your own risk.
Click to expand...
Click to collapse
Thank you very much for your reply, allow me to explain what happened before i proceed to your solution
- After updating from 10.3.2 to 10.3.3 i was able to flash magisk_patched file but the problem is no WIFI & SIM
- after many attempts by flashing magisk_patched the device keeps looping to either fastboot mode or unlocked boot screen.
- I extracted the boot.img file from original full update file by using using Payload Dumper then i moved that boot.img file to an old NEXUS phone which is rooted so i can patched it by using magisk which i then flash it back to my OnePlus 7T but it keeps looping to fastboot mode
- By some how i was able to work after downloading from (https://drive.google.com/drive/folders/1MCfCPci7F7FGl5ZHVTNRKVq9j8RBCUih)
- when i reached home i wanted to update magisk (i select to inactive OTA slot) everything is missed up , but unfortunately the device keeps looping even though i used this file (https://forum.xda-developers.com/oneplus-7t/how-to/oos-10-0-11-magisk-patched-boot-img-t4106435)
- Suddenly the device shows "Qualcomm crash dump mode" which is a bad sign but after pressing Power + Vol UP + Vol DOWN i was able to get back the fastboot screen (which i think its a good sign)
- i flashed magisk_patched.img 10.0.11 but the device keeps looping to unlocked boot screen.
How can i find the correct magisk_patched.img for 10.3.3 ? i am using Titanium Back, is there a way that i can connect the phone to my PC and copy all my files before i flash a new Stock OS if this is the last solution !!
Question : If i use another solution by using "TOOL ALL IN ONE" then flash factory image ? will this fix the problem and keep my data
Note : i am very optimistic that my data is safe but its an issue of booting...... I hope so
Wating for your reply and thank you very much
suhb20 said:
Thank you very much for your reply, allow me to explain what happened before i proceed to your solution
- After updating from 10.3.2 to 10.3.3 i was able to flash magisk_patched file but the problem is no WIFI & SIM
- after many attempts by flashing magisk_patched the device keeps looping to either fastboot mode or unlocked boot screen.
- I extracted the boot.img file from original full update file by using using Payload Dumper then i moved that boot.img file to an old NEXUS phone which is rooted so i can patched it by using magisk which i then flash it back to my OnePlus 7T but it keeps looping to fastboot mode
- By some how i was able to work after downloading from (https://drive.google.com/drive/folders/1MCfCPci7F7FGl5ZHVTNRKVq9j8RBCUih)
- when i reached home i wanted to update magisk (i select to inactive OTA slot) everything is missed up , but unfortunately the device keeps looping even though i used this file (https://forum.xda-developers.com/oneplus-7t/how-to/oos-10-0-11-magisk-patched-boot-img-t4106435)
- Suddenly the device shows "Qualcomm crash dump mode" which is a bad sign but after pressing Power + Vol UP + Vol DOWN i was able to get back the fastboot screen (which i think its a good sign)
- i flashed magisk_patched.img 10.0.11 but the device keeps looping to unlocked boot screen.
How can i find the correct magisk_patched.img for 10.3.3 ? i am using Titanium Back, is there a way that i can connect the phone to my PC and copy all my files before i flash a new Stock OS if this is the last solution !!
Question : If i use another solution by using "TOOL ALL IN ONE" then flash factory image ? will this fix the problem and keep my data
Note : i am very optimistic that my data is safe but its an issue of booting...... I hope so
Wating for your reply and thank you very much
Click to expand...
Click to collapse
Did you try flashing the 10.3.3 boot image i have provided above?
And btw you can't get out the data in any other way without booting because of encryption.
Aswin08 said:
Did you try flashing the 10.3.3 boot image i have provided above?
And btw you can't get out the data in any other way without booting because of encryption.
Click to expand...
Click to collapse
Hello,
You know what today afternoon i was just getting the USB cable so i can connect my OnePlus 7T to my laptop when i just picked up my phone i noticed that its not on the Unlocked boot loader screen" its was just normal as before (every is was working fine...every thing) i was really astonished what happened when i checked the OS its 10.3.3 and every thing is working fine even root is working, what i need to do is update magisk (direct install) as you told me
I really don't know what happened but i am very happy for that
i really appreciate your prompt help and assistance even thought i didn't do any thing.
one question please ..what is the difference between :
- fastboot boot magisk_patched.img
- fastboot flash boot magisk_patched.img
Best regards and wishes
suhb20 said:
Hello,
You know what today afternoon i was just getting the USB cable so i can connect my OnePlus 7T to my laptop when i just picked up my phone i noticed that its not on the Unlocked boot loader screen" its was just normal as before (every is was working fine...every thing) i was really astonished what happened when i checked the OS its 10.3.3 and every thing is working fine even root is working, what i need to do is update magisk (direct install) as you told me
I really don't know what happened but i am very happy for that
i really appreciate your prompt help and assistance even thought i didn't do any thing.
one question please ..what is the difference between :
- fastboot boot magisk_patched.img
- fastboot flash boot magisk_patched.img
Best regards and wishes
Click to expand...
Click to collapse
boot command just boots that img temporarily, when you restart the phone 2nd time, your original img will be retained . If anything goes wrong you won't get into trouble.
flash is.. usual permanently flashing the boot image into your system.