Related
Long story short, I bought my awesome Pixel 2 XL back in December, right away I unlocked the bootloader, installed TWRP Recovery and rooted it. Since then I have done nothing to the phone , besides app updates, but never updated top the latest security patches pr anything. Partly because being rooted can't take OTA updates, and didn't want to wipe anything flashing new updates.
Tonight, I wanted to get on the latest, I was currently on 3.2.1.0, so I downloaded the 3.2..1.2 zip, rebooted into Recovery, and flashed the zip, and rebooted into Recovery again, all good, on the latest current TWRP version.
I press reboot system, but it keeps going back into Recovery, every time, always reboots back into Recovery for some strange reason ? Doesn't load the system. So I select the other partition A, I was on B, I put it in A, select reboot system, and it just hangs on the white Goggle screen FOREVER. I then get back into Recovery, now I can't even get into Recovery, the swipe right feature not working, acting like it's not registering my input, I can't swipe the arrow to move it. Now it's just stuck on the opening page in Recovery.
Now what ?
Zorachus said:
Long story short, I bought my awesome Pixel 2 XL back in December, right away I unlocked the bootloader, installed TWRP Recovery and rooted it. Since then I have done nothing to the phone , besides app updates, but never updated top the latest security patches pr anything. Partly because being rooted can't take OTA updates, and didn't want to wipe anything flashing new updates.
Tonight, I wanted to get on the latest, I was currently on 3.2.1.0, so I downloaded the 3.2..1.2 zip, rebooted into Recovery, and flashed the zip, and rebooted into Recovery again, all good, on the latest current TWRP version.
I press reboot system, but it keeps going back into Recovery, every time, always reboots back into Recovery for some strange reason ? Doesn't load the system. So I select the other partition A, I was on B, I put it in A, select reboot system, and it just hangs on the white Goggle screen FOREVER. I then get back into Recovery, now I can't even get into Recovery, the swipe right feature not working, acting like it's not registering my input, I can't swipe the arrow to move it. Now it's just stuck on the opening page in Recovery.
Now what ?
Click to expand...
Click to collapse
Fastboot the boot.img from whatever build your on now and let it boot up. That will remove twrp, then you can go back and fastboot twrp again.
[delete
Badger50 said:
Fastboot the boot.img from whatever build your on now and let it boot up. That will remove twrp, then you can go back and fastboot twrp again.
Click to expand...
Click to collapse
Where do I get the December boot.img ?
Zorachus said:
Where do I get the December boot.img ?
Click to expand...
Click to collapse
Go here....https://developers.google.com/android/images
Download the December factory image, extract it, then extract the other zip you'll find, and in there you'll find the boot.img. Then place that in your platform-tools folder and run...fastboot boot boot.img
Then type fastboot reboot, and let the phone boot up. Then go back and fastboot the twrp.img
Once in twrp, flash the twrp installer zip, then custom kernel if you want, and then magisk for root if you want. Question, why are you still on the December build???
I think if you just flash magisk it will boot again. If you were rooted. Someone posted on the twrp thread. To get touch back on twrp just have to adb reboot recovery. Might worth a try.
Sent from my Pixel 2 XL using Tapatalk
Badger50 said:
Go here....https://developers.google.com/android/images
Download the December factory image, extract it, then extract the other zip you'll find, and in there you'll find the boot.img. Then place that in your platform-tools folder and run...fastboot boot boot.img
Then type fastboot reboot, and let the phone boot up. Then go back and fastboot the twrp.img
Once in twrp, flash the twrp installer zip, then custom kernel if you want, and then magisk for root if you want. Question, why are you still on the December build???
Click to expand...
Click to collapse
Ok I am downloading the 1.6GB December file. I will then extract that, and only need to grab the boot.img file from there ? What do you mean when you say "then extract the other zip you'll find" ?
And then connect my phone to my PC, and open Command Prompt, and run these lines. I need to be in fastboot mode I assume ?
"
Zorachus said:
Ok I am downloading the 1.6GB December file. I will then extract that, and only need to grab the boot.img file from there ? What do you mean when you say "then extract the other zip you'll find" ?
And then connect my phone to my PC, and open Command Prompt, and run these lines. I need to be in fastboot mode I assume ?
"
Click to expand...
Click to collapse
There's another large zip that you'll find after you extract the factory image. It is in that zip that you'll find the boot.img. And yes, you'll need to be in fastboot mode to install the boot.img :good:
Badger50 said:
There's another large zip that you'll find after you extract the factory image. It is in that zip that you'll find the boot.img. And yes, you'll need to be in fastboot mode to install the boot.img :good:
Click to expand...
Click to collapse
Ok so I extracted that 1.6gb December file. Inside the file I see the large 1.5GB file, I open that and see the boot.img, only like 40mb. or do I need to extract this 1.5GB file too ?
Zorachus said:
Ok so I extracted that 1.6gb December file. Inside the file I see the large 1.5GB file, I open that and see the boot.img, only like 40mb. or do I need to extract this 1.5GB file too ?
Click to expand...
Click to collapse
Yes, extract that file, then you can move the boot.img out of it :good:
Badger50 said:
Yes, extract that file, then you can move the boot.img out of it :good:
Click to expand...
Click to collapse
In Command Prompt I am typing " fastboot boot boot.img " and it says cannot load 'boot.img' : No such file or directory
Zorachus said:
In Command Prompt I am typing " fastboot boot boot.img " and it says cannot load 'boot.img' : No such file or directory
Click to expand...
Click to collapse
Ah crud, I messed up. How bout..fastboot flash boot boot.img
Does that work? And, is that boot.img in the platform-tools folder?
Badger50 said:
Ah crud, I messed up. How bout..fastboot flash boot boot.img
Does that work? And, is that boot.img in the platform-tools folder?
Click to expand...
Click to collapse
I moved that boot.img file into the Downloads section of my PC, and in Command Prompt typed cd Downloads, then once there the "fastboot boot boot.img" line, which that worked, and finished in 1.023s, and the phone rebooted, but now I'm back on that white G screen, and still just sitting there.
I have the "platform-tools" folder inside the Downloads folder, but now sure how to direct the Command Prompt to go there ?
EDIT: Silly me, easy to get Command Prompt to the platform-tools, just typed ' cd platform-tools ' and it's there. LOL. So I did that, and then 'fastboot boot boot.img' and the phone rebooted, but it's still hanging in that white G screen
Badger50 said:
Ah crud, I messed up. How bout..fastboot flash boot boot.img
Does that work? And, is that boot.img in the platform-tools folder?
Click to expand...
Click to collapse
Make sure your boot.img is in Android Tools folder along with fastboot.exe.
Then with phone in bootloader, type:
fastboot flash boot boot.img
---------- Post added at 07:31 PM ---------- Previous post was at 07:26 PM ----------
Zorachus said:
I moved that boot.img file into the Downloads section of my PC, and in Command Prompt typed cd Downloads, then once there the "fastboot boot boot.img" line, which that worked, and finished in 1.023s, and the phone rebooted, but now I'm back on that white G screen, and still just sitting there.
I have the "platform-tools" folder inside the Downloads folder, but now sure how to direct the Command Prompt to go there ?
EDIT: Silly me, easy to get Command Prompt to the platform-tools, just typed ' cd platform-tools ' and it's there. LOL. So I did that, and then 'fastboot boot boot.img' and the phone rebooted, but it's still hanging in that white G screen
Click to expand...
Click to collapse
This should cure your sticking at white screen: (wipes phone)
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Zorachus said:
I moved that boot.img file into the Downloads section of my PC, and in Command Prompt typed cd Downloads, then once there the "fastboot boot boot.img" line, which that worked, and finished in 1.023s, and the phone rebooted, but now I'm back on that white G screen, and still just sitting there.
I have the "platform-tools" folder inside the Downloads folder, but now sure how to direct the Command Prompt to go there ?
Click to expand...
Click to collapse
What happens if you do a hard restart using the power button?
Your platform-tools folder is where? I just leave mine in the SDK folder, then move my stuff from my files from the download folder. But hey, if it works, that's cool :good:
michaelbsheldon said:
Make sure your boot.img is in Android Tools folder along with fastboot.exe.
Then with phone in bootloader, type:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Ok the boot.img is in there, in my CD:\Downloads section in the folder named "platform-tools" , in that folder is all the fastboot.exe, and boot.img, adb stuff, etc...
I go back to Command Prompt typed in 'fastboot flash boot boot.img; phone rebooted, and still hanging in the white G screen
Ran that [TOOL] Deuces thing, unlocked bootloader and erased data, and other stuff, it does all this in fastboot mode it seems.
So after it's done, I am in fastboot mode still, I press the power button on the Green Start arrow. It boots up, then a black screen and bright circle animation and underneath says erasing, it reboots and goes to the white G screen, then reboots again, and I am in some weird screen now ?
Android Recovery, but this sure the hell isn't TWRP Recovery. It's some strange super tiny lettering hard to barely read, gives me two options;
-Try again
-Factory data reset
Above that it says "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset, and erase all your data stored on this device"
Zorachus said:
Ran that [TOOL] Deuces thing, unlocked bootloader and erased data, and other stuff, it does all this in fastboot mode it seems.
So after it's done, I am in fastboot mode still, I press the power button on the Green Start arrow. It boots up, then a black screen and bright circle animation and underneath says erasing, it reboots and goes to the white G screen, then reboots again, and I am in some weird screen now ?
Android Recovery, but this sure the hell isn't TWRP Recovery. It's some strange super tiny lettering hard to barely read, gives me two options;
-Try again
-Factory data reset
Above that it says "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset, and erase all your data stored on this device"
Click to expand...
Click to collapse
I don't mess with tool kits, so may want to post it in that thread. That's the stock android recovery. Your best bet is to factory reset. Then hopefully it'll boot up.
Looks like I'm ****ed. I pressed Factory Data Reset, it rebooted, went to the white G screen, then rebooted back again to that stock Android recovery, with the same options.
Zorachus said:
Looks like I'm ****ed. I pressed Factory Data Reset, it rebooted, went to the white G screen, then rebooted back again to that stock Android recovery, with the same options.
Click to expand...
Click to collapse
That sounds like outdated Android Tools.
Have you tried to flash the March image from Google yet?
If not, download newest Tools, https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Then download March image and follow these instructions: https://developers.google.com/android/images#taimen.
Hi all,
I installed TWRP on my Honor 7x, that went well.
Yesterday I decided to try to get Lineage working so:
- I installed EMUI 8, that went pretty smooth
- I installed Lineage OS 15.1. (without GApps)
- I flashed TWRP.
The issue I have now is that:
1) I can't install any APK in Lineage. Probably needs a factory reset/dalvik cache wipe.
2) I can't boot into TWRP. It stays stuck on the splash screen forever. This also means I can't install OpenGapps, SuperUser access (afaik), or anything else that requires root.
3) The bootloader is saying "FRP: Locked", which means I can't flash a new TWRP or a different ROM. When I try it fails with "command not allowed"
3) "fastboot oem unlock" fails saying I need to enable it in the developer options, but it's grayed out in the developer options because it's already unlocked.
4) I wanted to try the "dload" method but I can't find a good explanation on how to do it, and Huawei recently took all their downloads down, which means I can't find any UPDATE.app even if I knew how.
5) The other solution that *might* work is using "fastboot oem frp-unlock", but I need an unlock code for that (I assume the same one that you request for an OEM unlock from Huawei), and Huawei closed down the site that generated the codes.
So I'm stuck in a weird limbo where I can't move forward (install Gapps and use my phone as normal) nor backwards (go back to EMUI8).
Does anyone have any idea how I can fix this situation?
Shadowsalyer said:
Hi all,
I installed TWRP on my Honor 7x, that went well.
Yesterday I decided to try to get Lineage working so:
- I installed EMUI 8, that went pretty smooth
- I installed Lineage OS 15.1. (without GApps)
- I flashed TWRP.
The issue I have now is that:
1) I can't install any APK in Lineage. Probably needs a factory reset/dalvik cache wipe.
2) I can't boot into TWRP. It stays stuck on the splash screen forever. This also means I can't install OpenGapps, SuperUser access (afaik), or anything else that requires root.
3) The bootloader is saying "FRP: Locked", which means I can't flash a new TWRP or a different ROM. When I try it fails with "command not allowed"
3) "fastboot oem unlock" fails saying I need to enable it in the developer options, but it's grayed out in the developer options because it's already unlocked.
4) I wanted to try the "dload" method but I can't find a good explanation on how to do it, and Huawei recently took all their downloads down, which means I can't find any UPDATE.app even if I knew how.
5) The other solution that *might* work is using "fastboot oem frp-unlock", but I need an unlock code for that (I assume the same one that you request for an OEM unlock from Huawei), and Huawei closed down the site that generated the codes.
So I'm stuck in a weird limbo where I can't move forward (install Gapps and use my phone as normal) nor backwards (go back to EMUI8).
Does anyone have any idea how I can fix this situation?
Click to expand...
Click to collapse
small chance you enable root from developer options. (i think it will be adb only)
if so , maybe can use adb shell and "dd" to write recovery to correct partition.
problem is many of the available twrp do not boot on custom rom .
example code. (if you do wrong , it may be bad)
Code:
dd if=/ext_sdcard/twrp_Recovery_ramdisk.img of=/dev/block/mmcblk0p32
It seems like I'm allowed to use dd in ADB shell, but before I run it, what do you mean by " problem is many of the available twrp do not boot on custom rom . "? I thought recovery was independent of the ROM? And does it mean flashing twrp like that could brick my phone?
Shadowsalyer said:
It seems like I'm allowed to use dd in ADB shell, but before I run it, what do you mean by " problem is many of the available twrp do not boot on custom rom . "? I thought recovery was independent of the ROM? And does it mean flashing twrp like that could brick my phone?
Click to expand...
Click to collapse
Like what you have , twrp stuck on splash screen
I managed to unlock the FRP with DC-unlocker. Sucks that it costs money but it worked!
Now Im stuck in a TWRP boot loop though.
Shadowsalyer said:
I managed to unlock the FRP with DC-unlocker. Sucks that it costs money but it worked!
Now Im stuck in a TWRP boot loop though.
Click to expand...
Click to collapse
At this point you should have access to fastboot though, right? I'd try a different TWRP instead. Perhaps try this one: https://drive.google.com/file/d/1ZYo7Ndte3vlLcUSadD6jIgfBi1oxa0Pb/view?usp=drivesdk
Just to clarify, it gets stuck on TWRP splash screen. When I turn off the phone, it immediately boots up again into TWRP. I tried getting into fastboot mode with all kinds of combinations of button presses, but no luck. Not even Volume Up + USB cable works
smokinjoe2122 said:
At this point you should have access to fastboot though, right? I'd try a different TWRP instead. Perhaps try this one: https://drive.google.com/file/d/1ZYo7Ndte3vlLcUSadD6jIgfBi1oxa0Pb/view?usp=drivesdk
Click to expand...
Click to collapse
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
I have seen this happen before , solution was to wait for dead battery, or disassemble to unplug battery
---------- Post added at 04:51 PM ---------- Previous post was at 04:47 PM ----------
Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
This is because after the frp unlock, it needed to see a factory reset, and it usually needs to be done with stock recvery.
So will have to wait till battery is dead and and plug in usb while holding volume button. Should then load to fastboot. Where it is best to flash stock recovery to clear the recovery bootloop. The bootloop is do to the fact yo unlocked frp and now phone needs to wipe/data
Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
it sucks this happened to yu but im glad i am not the only one that dc-unlocker deleted my fastboot after i unlocked the frp and i cant boot fastboot for nothing if you find a solution please contact me. my phone is doing the exact same thing booting straight too twrp no mater what combinations i use
dcraffam said:
it sucks this happened to yu but im glad i am not the only one that dc-unlocker deleted my fastboot after i unlocked the frp and i cant boot fastboot for nothing if you find a solution please contact me. my phone is doing the exact same thing booting straight too twrp no mater what combinations i use
Click to expand...
Click to collapse
i just took mine apart and discconected the battery and still no luck that program deleted my fastboot
Please can you tell me the process to install twrp I have the L24
I waited all the way till the battery drained, stuck in the USB, and it booted to ROM! Sadly it immediately shut off again because the battery is dead (even with keeping the USB in). I'm going to keep trying though.
I can't get into fastboot mode. I can get into the ROM by letting the battery drain completely on the TWRP splashscreen, and then sticking in the USB cable. However, no button combination or "adb reboot bootloader" or rebooting to bootloader from the ROM brings me to the bootloader. I wonder if it's still there. Any ideas?
Shadowsalyer said:
I can't get into fastboot mode. I can get into the ROM by letting the battery drain completely on the TWRP splashscreen, and then sticking in the USB cable. However, no button combination or "adb reboot bootloader" or rebooting to bootloader from the ROM brings me to the bootloader. I wonder if it's still there. Any ideas?
Click to expand...
Click to collapse
Seems to be a f-up situation either way.
You have adb DD available, found out before.
Don't know if maybe flashing stock recovery is good idea at this point.
I think fastboot.img can be flashed with DD too, but don't try till someone can confirm.
If flash stock recovery clears the loops, maybe best to do full-ota manual flashing.
I managed to get an UPDATE.APP file and extract fastboot.img from it, as well as all the other .img files. If someone can tell me what to flash and how (with dd), I think Im set.
Shadowsalyer said:
I managed to get an UPDATE.APP file and extract fastboot.img from it, as well as all the other .img files. If someone can tell me what to flash and how (with dd), I think Im set.
Click to expand...
Click to collapse
Fastboot.img is the large part the bootloader. If flashing it goes bad, might be dead phone after, just rember that.
Will add a list of partition names and command s for you soon.
here is a list of oreo partitions and there /dev/blk/** number
and here is an example of code to save images with dd assuming you put the images on your extrnal-sdcard in folder called oreo-images
Code:
dd if=/dev/block/mmcblk0p5 of=/mnt/ext_sdcard/oreo-images/fastboot.img
Do that save first and compare the md5 of the file from update.app to this file.
or just check the md5 before making the copy
Code:
adb shell md5sum /dev/block/mmcblk0p5
If you are conviced you need to flash the images, here is example of writing the image assuming files are in sdcard folder oreo-update-images
Code:
dd if=/mnt/ext_sdcard/oreoupdate-images/fastboot.img of=/dev/block/mmcblk0p5
As I have said, this might be bad advise , I have not done fastboot.img flashing before. But on other devices it is same as lk.img or uboot.img, There is danger in flashing it incorrectly. That is why my suggestion was to flash no-check-recovery and do manael update with "echo -update_package" commands.
Along with the statement that fastboot.img is similar to lk.img or uboot.img on other phones, Your fastboot cannot be gone. because phone boots.
but do let us know how it goes.
I agree it would be better to flash recovery if possible. I assume I need the NoCheck-Recovery image from this thread? https://forum.xda-developers.com/honor-7x/how-to/manual-update-to-oreo-beta-emui-8-bnd-t3767044
And what partition do I have to flash it to? I'm guessing either /dev/block/mmcblk0p28 (erecovery ramdisk) or /dev/block/mmcblk0p32 (recovery ramdisk)? I'm not sure what the difference is between erecovery and normal recovery.
(didn't flash fastboot yet, wanted to see if recovery was doable).
Shadowsalyer said:
I agree it would be better to flash recovery if possible. I assume I need the NoCheck-Recovery image from this thread? https://forum.xda-developers.com/honor-7x/how-to/manual-update-to-oreo-beta-emui-8-bnd-t3767044
And what partition do I have to flash it to? I'm guessing either /dev/block/mmcblk0p28 (erecovery ramdisk) or /dev/block/mmcblk0p32 (recovery ramdisk)? I'm not sure what the difference is between erecovery and normal recovery.
(didn't flash fastboot yet, wanted to see if recovery was doable).
Click to expand...
Click to collapse
To recovery_ramdisk. 32
What about check md5 of fastboot partition, that will be helpful to know if it did get wiped out.?
Hmm seems like I'm not allowed to use dd after all:
HWBND-H:/ $ dd if=/storage/7C96-7E17/BND-RECOVERY-NoCheck.img of=/dev/block/mmcblk0p32
dd: /dev/block/mmcblk0p32: Permission denied
And here I was thinking I was close to solving it...
Also can't run md5sum on the fastboot partition, since that needs root as well.
I was following the steps on the rooting process with twrp and I got twrp to boot but i couldn't boot into the system and now it's just stuck in download mode is there any way to fix it
Djcall11 said:
I was following the steps on the rooting process with twrp and I got twrp to boot but i couldn't boot into the system and now it's just stuck in download mode is there any way to fix it
Click to expand...
Click to collapse
Download the factory images.
Run flasg_all.bat.
If you dont want your data partition to be formatted, then edit the .bat file and remove the line where it says "erase userdata". You can also remove tge last line that reads "fastboot reboot".
When rooting, i always boot into twrp using the image and flash both twrp zip and magisk zip in one go.
iliais347 said:
Download the factory images.
Run flasg_all.bat.
If you dont want your data partition to be formatted, then edit the .bat file and remove the line where it says "erase userdata". You can also remove tge last line that reads "fastboot reboot".
When rooting, i always boot into twrp using the image and flash both twrp zip and magisk zip in one go.
Click to expand...
Click to collapse
i have to edit the bat file and add -i 0x1532 to every command anyway for the command to work
so... the razer loading green effect is happening but it hasn't passed that it just keeps going
should I just put back the command to delete the user data
Have you unlocked the critical portion of the bootloader? (First thing I always ask)
If yes then yeah just wipe the whole thing.
Roxas598 said:
Have you unlocked the critical portion of the bootloader? (First thing I always ask)
If yes then yeah just wipe the whole thing.
Click to expand...
Click to collapse
welp the phone booted but it just stays on the loading screen and when I restart it just goes straight to download mode
I did unlock_critical and it just tells me that the device is already unlocked
I don't really know what else I can do from here
Of both bootloader portions are unlocked it should just be a case of running the flash all script from the factory images and you're good to go :S only other thing I can suggest to make sure there's nothing bad in there and in fastboot wiping user data again.
Roxas598 said:
Of both bootloader portions are unlocked it should just be a case of running the flash all script from the factory images and you're good to go :S only other thing I can suggest to make sure there's nothing bad in there and in fastboot wiping user data again.
Click to expand...
Click to collapse
I ran the script how it was and I just get stuck at the green effect loading I will try some other commands and I'm about to try the 7.1.1 mr3 rom to see if that work
so using the 7.1.1 mr3 worked i finally have my phone back thank guy for the help
Djcall11 said:
i have to edit the bat file and add -i 0x1532 to every command anyway for the command to work
Click to expand...
Click to collapse
Why is that? I didnt have to do that.
What does that command do?
Hello, I have unlocked my device and when I install twrp and reboot the official recover replaced with twrp. I have tried many times but after every reboot the stock recover is there. I need to flash twrp every time to use it.any reply ASAP will appreciate. Thanks in advance.
riyan65 said:
Hello, I have unlocked my device and when I install twrp and reboot the official recover replaced with twrp. I have tried many times but after every reboot the stock recover is there. I need to flash twrp every time to use it.any reply ASAP will appreciate. Thanks in advance.
Click to expand...
Click to collapse
Make sure are flashing it and not booting it
fastboot flash recovery recovery.img
Swipe to enable system modifications on first use
Full instructions on my twrp thread
https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737
TheFixItMan said:
Make sure are flashing it and not booting it
fastboot flash recovery recovery.img
Swipe to enable system modifications on first use
Full instructions on my twrp thread
https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737
Click to expand...
Click to collapse
At first time only I have done this process, but also it changed the recover with stock recover.
riyan65 said:
At first time only I have done this process, but also it changed the recover with stock recover.
Click to expand...
Click to collapse
Root your phone & use the root method via the twrp app
TheFixItMan said:
Root your phone & use the root method via the twrp app
Click to expand...
Click to collapse
How do I root my device without twrp???
riyan65 said:
How do I root my device without twrp???
Click to expand...
Click to collapse
Oh I thought you could boot to it but it doesn't stick
If you can't get into twrp at all it's user error
Follow my guide on the twrp thread
Make sure you rename the image recovery.img
Put your phone into fastboot mode - hold Vol down & power button
Then in a cmd prompt where you have recovery.img & fastboot type
fastboot flash recovery recovery.img
Then use the volume keys to select recovery and press power button to select
Post your cmd output but it should say write OK at the end
Ignore the error is not signed or corrupt that comes before that
Obviously I presume you have already unlocked your bootloader - just follow all the instructions on the twrp thread
Also you don't reboot the phone between flashing twrp and entering twrp for the first time
TheFixItMan said:
Oh I thought you could boot to it but it doesn't stick
If you can't get into twrp at all it's user error
Follow my guide on the twrp thread
Make sure you rename the image recovery.img
Put your phone into fastboot mode - hold Vol down & power button
Then in a cmd prompt where you have recovery.img & fastboot type
fastboot flash recovery recovery.img
Then use the volume keys to select recovery and press power button to select
Post your cmd output but it should say write OK at the end
Ignore the error is not signed or corrupt that comes before that
Obviously I presume you have already unlocked your bootloader - just follow all the instructions on the twrp thread
Also you don't reboot the phone between flashing twrp and entering twrp for the first time
Click to expand...
Click to collapse
Hey, I was able to boot it and run the latest twrp and install the supersu but the root process failed as it gives me ram extraction failed and end then I thought reboot and install magisk, so I install it and download the zip file then when I try to go in recovery mode, twrp is not available as stock recover is there. I don't know why recover change automatically. Do you know the reason behind it why it changed?? Or do I need to do something to keep it. At the time of nougat I was able to use it without any problem as recover doesn' change,but in Oreo it happening.
riyan65 said:
Hey, I was able to boot it and run the latest twrp and install the supersu but the root process failed as it gives me ram extraction failed and end then I thought reboot and install magisk, so I install it and download the zip file then when I try to go in recovery mode, twrp is not available as stock recover is there. I don't know why recover change automatically. Do you know the reason behind it why it changed?? Or do I need to do something to keep it. At the time of nougat I was able to use it without any problem as recover doesn' change,but in Oreo it happening.
Click to expand...
Click to collapse
Supersu is very old and outdated (the reason for that error is supersu can't install in systemless mode because the kernel ramdisk paths are not compatible) but since supersu is ancient now it's pointless trying to get it to work
Use magisk
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Flash in twrp
You may have to install the magisk manager app separately if its not in your app draw
Just download the apk and install it via any file manager
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).