Question What are problems my phone root - Redmi Note 9T

1. Copy the boot.img and Magisk apk into the internal storage of my phone.
2. Install Magisk and patch boot.img then I get the file such as magisk_patched.img.(The file name is different, I changed it to magisk_patched.img.)
3. Copy the magisk_patched.img and past in the ADB folder.
4. In ADB floder open command prompt and phone connect to PC.
Type to enter fastboot mode.
5. Check current slot of the device :fastboot getvar current-slot
It's will show a or b here but it's show
6. Type fastboot flash boot magisk_patched.img into terminal window.(type fastboot flash boot_a(b) magisk_patched.img but my phone can't.)
7. Reboot and phone will be root successful.
All done then my phone is repeated starts and now I only boot to fastboot mode, can't boot to recovery mode. ROOT FAILED
What are problems? How to do? Ty All

Rom is V12.5.8.0 RJEMIXM and Android 11

Related

OpenBeta 8 twrp not working anymore

for some reason i can't seem to boot to twrp anymore, tried the custom one found on xda and the official one(from the oneplus website) non of them seem to boot i allways get stock recovery when booting to recovery.
drivers:
https://www.androidfilehost.com/?fid=24591020540821930
-extract and install
minimal adb
https://www.androidfilehost.com/?fid=457095661767103465
-create a folder and extract it
modded twrp
http://forum.xda-developers.com/attachment.php?attachmentid=3875375&d=1473889816
-extract
-rename the img file to recovery.img
-move the recovery.img file to your minimal adb folder
Install instructions
-boot your phone to fastboot mode (power and + key)
-open command window at minimal adb folder with shift key on your keyboard and right mouse button
-type in
fastboot devices
fastboot oem unlock
fastboot reboot
-boot back into fastboot
-open command window
-type in
fastboot devices
fastboot flash recovery recovery.img
fastboot reboot

Unable to boot img in bootloader

Hello whenever i try to use the fastboot boot twrp.img command on adb the img wont load it gets stuck on the fastboot logo.
Try
fastboot flash recovery twrp.img
elwholo said:
Hello whenever i try to use the fastboot boot twrp.img command on adb the img wont load it gets stuck on the fastboot logo.
Click to expand...
Click to collapse
Rename ur boot image file to twrp.img
And then in adb type
1. fastboot devices (see if you are connected or not... If connected type 2nd command)
2. fastboot flash recovery twrp.img
After that by using power up button navigate to RECOVERY MOD and press power key
DONE
U will be running twrp recovery
flash magisk via recovery to maintain root
Enjoy

[Flashing STOCK ROM from Custom Rom] [No Recovery Mode, Fastboot accessible]

I followed these steps and now my Asus zf2 (ze551ml) is back alive! For the issue mentioned below, I didn't find much anywhere so I thought I'd put here what helped me.
Issue: Only fastboot mode accessible, can't enter recovery. (Also my bootloader was locked, MM bootloader, No OS). After selecting recovery mode from bootloader, again it enters fastboot, i.e the process in video above couldn't install the recovery (This must be because my bootloader was locked). I tried unlocking the bootloader by the .bat files available on XDA but since I'd not enabled OEM unlocking, unlocking failed everytime. My OS got wiped out, so only fastboot mode was accessible.
Solution:
I believe you have installed Minimal ADB and fastboot on your PC.
Download the raw file from the XDA thread.
Now first of all, change extention of the .raw firmware file to .zip.
Then just extract all files from it into adb and fastboot folder.
Now in folder (where you placed files from raw firmware and adb and fastboot tool folder) at empty place anywhere in folder hold Shift on computer keyboard and right click with mouse. Now click open command window here.
Perform the following commands one after another:
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again, if USB debugging was on then this will definitely work)
2. fastboot oem erase_osip_header
3. fastboot oem start_partitioning
4. fastboot flash /tmp/partition.tbl partition.tbl
5. fastboot oem partition /tmp/partition.tbl
6. fastboot erase system
7. fastboot erase cache
8. fastboot erase data
9. fastboot erase APD
10. fastboot erase ADF
11. fastboot oem wipe splashscreen
12. fastboot oem stop_partitioning
13. fastboot flash splashscreen splash_sign.bin
14. fastboot flash token MFG_BOM_Full.bin
15. fastboot flash ifwi ifwi-prod.bin
16. fastboot flash boot boot_sign.bin
17. fastboot flash recovery recovery_sign.bin
18. fastboot flash fastboot droidboot_sign.bin
19. fastboot flash APD APD.img
20. fastboot flash system system.img
21. fastboot reboot
Phone will successfully reboot into system. Don't worry, first boot gonna take a little longer time.
Download raw file
Hello,
From where I can download raw file? Can you please provide a link?
Thanks in advance
bb04 said:
Hello,
From where I can download raw file? Can you please provide a link?
Thanks in advance
Click to expand...
Click to collapse
OP forgot to post link from he copied commands.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
sukhwant717 said:
OP forgot to post link from he copied commands.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
FYI, I didn't add the links because one can't add external links in their first posts.
mukunds11 said:
FYI, I didn't add the links because one can't add external links in their first posts.
Click to expand...
Click to collapse
it could be better if you would have removed or edited last line while copying commands
help. my phone condition is just like this. at first when i connected my phone to computer, powershell detected it, but then after a while, my phone disappeared from powershell. can someone help me ?
edit, i just did the thing and its doing fine even though my phone look like it is not detected

Phone now boot into fastboot but not system

Hi
I was trying to install Lineage OS on my device, but I failed, now the phone does not have TWRP anymore, and when I power up, it goes into fast boot only.
I have done quite a lot of work to save my phone, and the last thing that I did was download the stock fastboot rom and run flash_all.bat from it.
(I can not get the Miflash tool working on my PC because when I startup the program, it asks me to download 5 drivers, but it failed to download and throw me an error)
luckyvictor said:
Hi
I was trying to install Lineage OS on my device, but I failed, now the phone does not have TWRP anymore, and when I power up, it goes into fast boot only.
I have done quite a lot of work to save my phone, and the last thing that I did was download the stock fastboot rom and run flash_all.bat from it.
(I can not get the Miflash tool working on my PC because when I startup the program, it asks me to download 5 drivers, but it failed to download and throw me an error)
Click to expand...
Click to collapse
First of all - if your phone boots to fastboot, there seems to be a problem with your bootloader or kernel.
To fix that, you need to reflash aboot.img and boot.img via fastboot.
Boot.img depends on the version, you want to install. Copy both files into your fastboot folder and
Code:
fastboot flash boot_a boot.img
Code:
fastboot flash boot_b boot.img
Code:
fastboot flash aboot_a aboot.img
Code:
fastboot flash aboot_b aboot.img
Now your phone shouldn´t stuck @ fastboot anymore.
Ok, to save your data, you could try to boot twrp:
Code:
fastboot boot twrp.img
If you´re lucky, it can decrypt your data - then you can backup data and internal storage...
If it´s not able to decrypt, you need to install twrp.
To install a fastboot rom without miflash look here
I suggest you to install caf-kernel via twrp. Sometimes your phone boots up with it - magic
Voodoojonny said:
First of all - if your phone boots to fastboot, there seems to be a problem with your bootloader or kernel.
To fix that, you need to reflash aboot.img and boot.img via fastboot.
Boot.img depends on the version, you want to install. Copy both files into your fastboot folder and
Code:
fastboot flash boot_a boot.img
Code:
fastboot flash boot_b boot.img
Code:
fastboot flash aboot_a aboot.img
Code:
fastboot flash aboot_b aboot.img
Now your phone shouldn´t stuck @ fastboot anymore.
Ok, to save your data, you could try to boot twrp:
Code:
fastboot boot twrp.img
If you´re lucky, it can decrypt your data - then you can backup data and internal storage...
If it´s not able to decrypt, you need to install twrp.
To install a fastboot rom without miflash look here
I suggest you to install caf-kernel via twrp. Sometimes your phone boots up with it - magic
Click to expand...
Click to collapse
Thanks, will give it a try.
Just for my knowledge, what are these boot_a and boot_b please? they relate to the two sim slot in this device?
luckyvictor said:
Thanks, will give it a try.
Just for my knowledge, what are these boot_a and boot_b please? they relate to the two sim slot in this device?
Click to expand...
Click to collapse
Boot.img from fastboot rom... To be flashed in partition boot_a and boot_b. Our device is a AB-device. That means all partitions are doubled (except of data). If your system breaks, you can switch to the other slot by "fastboot set_active a" or b if you are on a.... Btw perhaps that fixes your phone too! Boot twrp and you can see which slot is active (under reboot)

Get Stock boot image without flashing TWRP

Keep stock recovery and extract the boot image.
You'll need.
Unlocked bootloader as guided here
adb/fastboot and proper drivers on PC.
TWRP from here. Any recent build will do, just grab the latest one.
Steps:
Reboot to fastboot
Code:
adb reboot bootloader
In fastboot, verify it's working properly and get the current slot. The result is either a or b
Code:
fastboot devices
Code:
fastboot getvar current-slot
Now boot into TWRP temporarily. The touchscreen will NOT work(a known issue). Just leave the phone connected
Code:
fastboot boot Twrp_3.5.2-10_EduardoA3677-billie_OxygenOs11_Android11.img
adb should work now. Extract boot image(s).
Code:
adb devices
Code:
adb pull /dev/block/bootdevice/by-name/boot_a boot_a.img
Code:
adb pull /dev/block/bootdevice/by-name/boot_b boot_b.img
Now we have boot_a.img and boot_b.img in current folder. Both should be 96MB or 100,663,296 bytes.
Depends on the result from step 2,
if it's "current-slot: a" then use boot_a.img. if it's "b" use "boot_b.img".
Once done, reboot the phone.
Code:
adb reboot
Now with this boot image, follow the guide to root.

Categories

Resources