hi, here goes my problem:
i had flashed stock oreo firmware (posted here on xda) together with a magisk-patched bootloader, all done via fastboot. my bootloader is unlocked, the device drivers on my win10 pc were working back then and i was able to boot the bootable twrp img.
i also had used one magisk module, namely app systemizer. but after updating it and rebooting, something went wrong (probably fault of magisk or the module), and i can't boot into system, it always gets stuck o the M logo.
i've still got fastboot, my pc correctly detects the phone is in fastboot and connected, and the phone sees the connection too. i am able to send commands like reboot, but whenever i try to tell it to boot a boot.img from my pc (stock img, magisk patched img, or twrp img), it always either gets stuck on loading the file, or straight up says that it failed - (remote: unknown command). the same happens with commands like erase and flash.
can anyone help me get it working again?
thanks
Hey.... I experienced the same thing yesterday.
Have you got it fixed cause this thread is 10 days now.
The solution was to go to the recovery and factory reset and the phone will work. Weirdly, it still had root and magisk app worked without a hitch. I restored all the apps and started working from today morning.
None of the commands were working in Fastboot mode, cant send files or execute something. Someone here has to explain this or we have to revert it back to stock image (which will kaput the root of course) and then try the flashing and see if it will work out.
After busting my head for 6 plus hours i am back again with the phone with root. I installed 4 modules and used the latest Magisk.
Tommylee567 said:
Hey.... I experienced the same thing yesterday.
Have you got it fixed cause this thread is 10 days now.
The solution was to go to the recovery and factory reset and the phone will work. Weirdly, it still had root and magisk app worked without a hitch. I restored all the apps and started working from today morning.
None of the commands were working in Fastboot mode, cant send files or execute something. Someone here has to explain this or we have to revert it back to stock image (which will kaput the root of course) and then try the flashing and see if it will work out.
After busting my head for 6 plus hours i am back again with the phone with root. I installed 4 modules and used the latest Magisk.
Click to expand...
Click to collapse
i got it fixed the same way.. my issue was caused by a bug in the shell app systemizer module, i reported it to the dev.... still really strange that it'd render fastboot unusable
No Solution
I still didn't find a solution to the fastboot problem in Windows. but using Linux system (present i have Manjaro linux installed) had solved it as i entered the commands step by step and flashed it.
And still I am having partial letters missing in reply I get from fastboot commands.
Ex: fastboot boot boot.img i will get something like suffix-slo:not found..... etc with missing letters on the screen.
So using the fastboot flashing script for Moto phones i flashed a stock firmware and started fresh with a good ol' stock boot.img file and still the fastboot commands work here and there. After few times of rebooting it works well. Then goes back to the same problem.
I don't know what is the matter with it but I learned my lesson of backup and never am gonna miss that step out (at least I had Titanium Backup done before the first shot).
BTW, i found what was the problem in Magisk module. It froze up in the Magic Charging Switch module. So re-flashed everything and back to normal.
Rooted and Magisk running well again.
I hope there won't be any flashing necessary soon for me :laugh:
I have what seems the same problem: "fastboot boot twrp.img" fails, either hanging on downloading, or simply failing with "remote: unknown command". I am also rooted with Magisk, no modules.
The kink is that on a different PC, it works fine. As far as I can tell, same software setup: Minimal ADB and Fastboot 1.4.3 + drivers installed by Motorola Device Manager 2.5.4 on both (Win10) PCs. So I'm not inclined to factory reset.
Frustrating.
edhaswell said:
I have what seems the same problem: "fastboot boot twrp.img" fails, either hanging on downloading, or simply failing with "remote: unknown command". I am also rooted with Magisk, no modules.
The kink is that on a different PC, it works fine. As far as I can tell, same software setup: Minimal ADB and Fastboot 1.4.3 + drivers installed by Motorola Device Manager 2.5.4 on both (Win10) PCs. So I'm not inclined to factory reset.
Frustrating.
Click to expand...
Click to collapse
Do you guys now if the error occur on a AMD "Ryzen" CPU?
I have both Amd and Intel desktops and on the intel works just fine on ever try, on the amd cpu I have no sucess till now.
btotta said:
Do you guys now if the error occur on a AMD "Ryzen" CPU?
I have both Amd and Intel desktops and on the intel works just fine on ever try, on the amd cpu I have no sucess till now.
Click to expand...
Click to collapse
In my case the non-working machine is a new Ryzen build, while the one that works is an older Intel. Shouldn't matter, but hmm...
edhaswell said:
In my case the non-working machine is a new Ryzen build, while the one that works is an older Intel. Shouldn't matter, but hmm...
Click to expand...
Click to collapse
Yeah, I think the same, but the problem it's with the USB drivers on the Windows 10 for ryzen. If you run windows 7 with the USB drivers from AMD will work normally.
I have done some research about it and find some guys that manage to install the drivers from windows 7 on windows 10, but for me just broke everything and I have to format the PC.
Tommylee567 said:
I still didn't find a solution to the fastboot problem in Windows. but using Linux system (present i have Manjaro linux installed) had solved it as i entered the commands step by step and flashed it.
And still I am having partial letters missing in reply I get from fastboot commands.
Ex: fastboot boot boot.img i will get something like suffix-slo:not found..... etc with missing letters on the screen.
Click to expand...
Click to collapse
I have similar issue with the same error message.
But in my case, the issue shows up on Ubuntu Linux. It works fine on another PC with Windows 7. Both are using fastboot r28.
The issue still persists even after re-stock, I still need to use Windows 7 (for any fastboot operation). Both PCs are Intel.
I also had a lot of errors with fastboot, which used to work perfectly some time ago. I too was frustrated and was searching for it. Just as a test case, I decided to use an older version of platform tools and voila all fastboot commands ran smoothly without a single error. I was getting all kinds of errors with platform-tools_r28.0.1-windows (downloaded directly from https://developer.android.com/studio/releases/platform-tools.html). I used older version 27.0.1 and everything working perfectly. I use win 7 x64 (intel). Maybe this will help some of you, or maybe I was just lucky and fastboot version is not the issue but something else, but as long as older version is working for me, I will be using it.
Cheers.
anonyo said:
I used older version 27.0.1 and everything working perfectly. I use win 7 x64 (intel).
Cheers.
Click to expand...
Click to collapse
linux r27.0.1 doesn't work for me. I don't think any version would work for my linux pc.
Was the final fix for this to just factory reset? I'm tempted to try booting to the recovery image on my home machine first but didn't want to mess with it if there's no point.
Update: since recovery was still accessible (Lineage OS recovery), I was able to ADB sideload TWRP, which then allowed me to push a new OS.
I have had this same problem since I got the phone. Fastboot works on my ryzen desktop, doesnt work on intel laptop. both are running latest linux mint
Related
So I flashed this bootloader here and have had issues with fastboot ever since. Windows 8 tells me that something has malfunctioned. When I go on windows 7 it'll give me the error "remote failed". Any ideas? Everything else seems to work ok. ADB works, I've updated my recovery (via flashify) but I cannot get the bootloader to work. Any ideas? I should also mention that prior to this flash fastboot was working (i had darkboot)
So apparently posting here does the magic trick. Finally, on a fifth system I was able to get fastboot and everything to install/run properly. Good lord. MODS, please close. Thanks.
Hi guys, I got a new XT1900-7 today, tried to install TWRP but I'm not able to boot it with "fastboot boot boot.img".. Yes the bootloader is unlocked, cmd is running as admin, adb and fastboot stuff is correctly installed, motorola drivers are installed, tried different cables and ports... I don't get it why it does not work and I'm absolutely NOT new to this business... Additional info: Running OPWS27.2.4, patch level August 1, 2018.
See the cmd screenshot below, it freezes there... Any help is much appreciated, absolutely don't know what is going wrong here!
Zokhii said:
Hi guys, I got a new XT1900-7 today, tried to install TWRP but I'm not able to boot it with "fastboot boot boot.img".. Yes the bootloader is unlocked, cmd is running as admin, adb and fastboot stuff is correctly installed, motorola drivers are installed, tried different cables and ports... I don't get it why it does not work and I'm absolutely NOT new to this business... Additional info: Running OPWS27.2.4, patch level August 1, 2018.
See the cmd screenshot below, it freezes there... Any help is much appreciated, absolutely don't know what is goind wrong here!
Click to expand...
Click to collapse
What's the file size of your boot.img? It should only be about 30 mb. It's not frozen it's still attempting to transfer the img to your device.
ptn107 said:
What's the file size of your boot.img? It should only be about 30 mb. It's not frozen it's still attempting to transfer the img to your device.
Click to expand...
Click to collapse
Thanks for your reply, the file sizes are correct, I tried these from twrp download page: twrp-3.2.3-1-payton.img (29.5M) and twrp-3.2.3-0-payton.img (25.9M) - same result.
Zokhii said:
Hi guys, I got a new XT1900-7 today, tried to install TWRP but I'm not able to boot it with "fastboot boot boot.img".. Yes the bootloader is unlocked, cmd is running as admin, adb and fastboot stuff is correctly installed, motorola drivers are installed, tried different cables and ports... I don't get it why it does not work and I'm absolutely NOT new to this business... Additional info: Running OPWS27.2.4, patch level August 1, 2018.
See the cmd screenshot below, it freezes there... Any help is much appreciated, absolutely don't know what is goind wrong here!
Click to expand...
Click to collapse
I have a laptop that doesn't work with fastboot, but adb is fine. Same cable and phone on a different computer and fastboot works. Maybe try a different computer?
gee one said:
I have a laptop that doesn't work with fastboot, but adb is fine. Same cable and phone on a different computer and fastboot works. Maybe try a different computer?
Click to expand...
Click to collapse
Will give this a try tomorrow, thanks a lot!
Edit: Still no luck. Tried it with linux mint and even there the same sh!t... wtf
Ensure Motorola drivers are up to date and even try a different USB port.
With Windows, does it see the phone in device manager while in fastboot?
Neffy27 said:
Ensure Motorola drivers are up to date and even try a different USB port.
With Windows, does it see the phone in device manager while in fastboot?
Click to expand...
Click to collapse
Latest drivers from Motorola Device Manager are installed and phone is properly recognized in device manager (used usb 2.0, 3.0 and 3.1 ports, nothing changes, same behavior). I tried it now with mfastboot but still nope..
Are you using minimal or full sdk (by Google) platform tools?
Neffy27 said:
Are you using minimal or full sdk (by Google) platform tools?
Click to expand...
Click to collapse
Minimal, I have also a Moto G5 and I don't face this kind of problems - only with Payton.
I recommend switching to full sdk. You don't have actually download all the packages, just the platform tools and it keeps itself updated. I stop encountering these random issues when I switched from minimal two phones ago. Issues like yours are; 9 out of 10, driver issues.
---------- Post added at 06:13 PM ---------- Previous post was at 06:13 PM ----------
The very next thing to try, would be reflash everything.
Good luck.
Neffy27 said:
I recommend switching to full sdk. You don't have actually download all the packages, just the platform tools and it keeps itself updated. I stop encountering these random issues when I switched from minimal two phones ago. Issues like yours are; 9 out of 10, driver issues.
---------- Post added at 06:13 PM ---------- Previous post was at 06:13 PM ----------
The very next thing to try, would be reflash everything.
Good luck.
Click to expand...
Click to collapse
Unfortunately still no progress with full sdk and latest platform-tools, I'm giving up (for now).. I don't get it man, I'm not able to do anything in bootloader... for example when I try "fastboot flash partition gpt.bin" it freezes at sending OR it throws instant failed, the bootloader log menu shows that something is downloading but nothing happens... I relocked the bootloader (locking and unlocking is no problem) again and I am going to use it for a while... otherwise I will do a mistake somewhere and will brick it... Thanks for taking the time to help me haha
I'm having this same exact issue, just got this phone (XT1900-1) for my wife and she wants a custom rom, my own phone booted into twrp no problem.
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
Maybe try the fastboot in that link. I read through the thread and no specific reason why they suggest that version but it allowed people to flash back to stock. I used it last week to go back to stock before Lineage.
No effect still stuck on "downloading 'boot.img'..." but thank you, should I try flashing TWRP without booting? Would that even work?
or maybe an alternative way to get TWRP like a rooting method or the such?
Edit: Im going to try a factory reset, who knows maybe itll work?
^Nope
Edit 2: ERRR ota update is also failing to install, all I did was unlock the bootloader, havnt been able to do anything else.. wtf is going on.. What should I do from here, lock the bootloader and try ota again?
Edit 3: Something strange is going on, the fastboot commands are failing randomly I just noticed, see the attached image... Im spamming the same exact command once every second and it intermittently works.
Sorry, beyond my expertise. Maybe it's USB c port on the phone issue? Intermittently dropping the connection? Or have to tried flashing the 8.1 sick from the thread I posted? Maybe the factory ROM is messed up some how. I honestly don't know and those suggestions aren't based in any real knowledge.
Code:
fastboot version 1:7.0.0+r33-2
Android Debug Bridge version 1.0.40
Version 4986621
In linux mint do you have the same versions of the tools as above?
Slayer5934 said:
No effect still stuck on "downloading 'boot.img'..." but thank you, should I try flashing TWRP without booting? Would that even work?
or maybe an alternative way to get TWRP like a rooting method or the such?
Edit: Im going to try a factory reset, who knows maybe itll work?
^Nope
Edit 2: ERRR ota update is also failing to install, all I did was unlock the bootloader, havnt been able to do anything else.. wtf is going on.. What should I do from here, lock the bootloader and try ota again?
Edit 3: Something strange is going on, the fastboot commands are failing randomly I just noticed, see the attached image... Im spamming the same exact command once every second and it intermittently works.
Click to expand...
Click to collapse
Had exactly the same behavior like you (especially Edit 3), I tried it on a different computer from 2013 with usb 2.0 ports and it worked..
No other cable, no usb port, no adb and fastboot changes and no other drivers - just put all the stuff on a other computer and run the commands from there :good:
ptn107 said:
Code:
fastboot version 1:7.0.0+r33-2
Android Debug Bridge version 1.0.40
Version 4986621
In linux mint do you have the same versions of the tools as above?
Click to expand...
Click to collapse
Yeah, I'm on 1:7.0.0+r33-2 too.. I guess it has something to do with my mainboard or usb controller, weird weird weird
A different pc solved the issue.. wtf.. thank you..
I have the exact same issue, random commands are failing. I tried 2 different computers, Linux and Windows. It just hangs at downloading boot.img. Flashing either immediately fails or hangs and I can't ctrl-c to kill the process, have to disconnect my phone.
dirktacular said:
I have the exact same issue, random commands are failing. I tried 2 different computers, Linux and Windows. It just hangs at downloading boot.img. Flashing either immediately fails or hangs and I can't ctrl-c to kill the process, have to disconnect my phone.
Click to expand...
Click to collapse
Yeah I wish we knew the exact problem and solution but you might just be stuck trying new computers for eternity sadly..
Hello to everyone.
I hope somebody to help me, last night i tried to update mi Lineage OS 16 (from erfanoabdi).
My device is unlocked bootloader, and i used the rom from nightly build (2018-21-09), it works fine and everything, the issue becomes when i look what was avaible a new update, so downloaded and install the new rom.
I do full wipe, after that i install the new rom, at this point everything its working fine, but after that when i changed the partition slot from A to B.
When i started to install the gapps they closed because it says what i am running Android 8.0, but its a mistake so i think that reboot the phone without install the gapps. So the phone starts well, so i decide again to boot into recovery (TWRP) to install the missing gapps.
When the device reboot in fastboot and i chosee the recovery option, the surprise was that TWRP was reemplaced by the stock recovery, and when i tried to flash the TWRP.img my device wont appear in fastboot mode, stays finding device and Windows wont recognized my phone.
I think the rom still no have usb adb support, so i cant flash TWRP
My device its unlocked and i was running the rom (but another nightly) .. without issues for a week ago... until i flashed this one
Now i have Lineage OS without GAPPS, without USB mode... Like the update from OPW 27 or 28 idk remember.
Its possible to fix? or my phone its ****ed, or there is one form to installl the gapps from anoter form?
Thanks for read this i hope somebody can help me.
My device its a XT1900-4 in Android 9.0 without google apps, only have the essencial apps like phone dialer , sms, the very very essencials app. Like an phone from 2008 jhaha
i offer some pay.
Update:
I attach some information photos from the Rom that im running:
(System Running) fine thanks
https://ibb.co/bXC7ye
(ADB is switched on, but no appears nothing)
https://ibb.co/exGpBz
(I tried with everyone of the opcions
https://ibb.co/ekv5jK
and this is my currently fastboot:
AP Fastboot Flash Mode (Secure)
BL: MBM-3.0-uefi-641a15b-180224
Baseband: M660_7042.27.01.74R PAYTON_LATAM_CUST
Product/Variant: payton xt1900-4 32GB P4
CPU: SDM630 1.0 (6)
Console [NULL]: null
Tools Mode Config: DISABLED
POWER OK
flashing_unlocked
Software status: Official
Transfer Mode: USB Connected
At this point my windows so says to my device is Error in a request for the USB device descriptor.
i tried last_usb_google driver.
Motorola Device manager 2.5.4
Minimal adb fastboot 1.4.2
and nothing works fine.
In my recovery appears this:
Android Recovery
motorola/payton/payton
8.0.0/OPW27.57.25-6-10/12
user/release-keys
Use volume to...etc and then i used the (Apply update from adb)
says:
Supported API: 3
Stopping adbd. . .
Now send the package you want to apply to the device with "adb sideload <filename>"
Help me pls:crying:
I have a Nokia 7 plus which is also a A/B device. I have observed many times that the fastboot mode isn't detected by the pc. Sometimes when I have a bootloop during experimentation, I force reboot into bootloader mode but it's not recognised. I reboot into recovery and select "reboot to bootloader", and this time it's recognised. Maybe these issues are related to A/B system, I'm not sure.
I think you should have the Motorola device manager installed if you're working on Windows. It contains the necessary drivers. I can't remember if it contains adb and fastboot executable files, but if it does then try using them (launching command prompt from there).
Broadcasted from Zeta Reticuli
Gravemind2015 said:
I have a Nokia 7 plus which is also a A/B device. I have observed many times that the fastboot mode isn't detected by the pc. Sometimes when I have a bootloop during experimentation, I force reboot into bootloader mode but it's not recognised. I reboot into recovery and select "reboot to bootloader", and this time it's recognised. Maybe these issues are related to A/B system, I'm not sure.
I think you should have the Motorola device manager installed if you're working on Windows. It contains the necessary drivers. I can't remember if it contains adb and fastboot executable files, but if it does then try using them (launching command prompt from there).
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
thanks for quicky reply, but i tried that and it doesnt work for me... :c
the motorola device manager its installed correctly, but i think the usb in the Android 9 it´s no working on running s.o and even in fastboot.
vmmiguel said:
thanks for quicky reply, but i tried that and it doesnt work for me... :c
the motorola device manager its installed correctly, but i think the usb in the Android 9 it´s no working on running s.o and even in fastboot.
Click to expand...
Click to collapse
My windows cmputer says that my device doesnt works properly, i read all night about this and i think when i some point i made wipe /system so i delete the twrp and the rom doesnt have usb adb i think so hahaha, i think now my x4 will stuck on only aosp 9.0 without g services :crying::crying::crying:
id start with a flash all of the latest stock firmware to clean it up. then start over
edufur said:
id start with a flash all of the latest stock firmware to clean it up. then start over
Click to expand...
Click to collapse
I tried but i have only stock recovey, and the usb adb it's not working, i think that i need to flash stock rom from stock recovery, but i dont know...
vmmiguel said:
I tried but i have only stock recovey, and the usb adb it's not working, i think that i need to flash stock rom from stock recovery, but i dont know...
Click to expand...
Click to collapse
You have to flash stock rom from fastboot. Try removing "fastboot erase userdata" from script flash-all.
Comby_sk said:
You have to flash stock rom from fastboot. Try removing "fastboot erase userdata" from script flash-all.
Click to expand...
Click to collapse
Hello Buddy, i tried that but doesnt work, recently i discover that my usb default mode is gray so i think i cant switch beetwen the usb option, and i tried ADB over network, in terminal emulator to run adbd service but it crash :c
@erfanoabdiadbi plz you cant help me, i really i was enjoying you excelent deveploment, but now in stuck in this without essencial apps like whatsapp, my smartphone works like only phone without been smart jajaja:crying::good:
Anyone?
vmmiguel said:
Anyone?
Click to expand...
Click to collapse
Read through this thread carefully...
https://forum.xda-developers.com/moto-x4/development/rom-lineage-16-0-developer-preview-t3849699
I have more or less the same problem.
I am stuck in LineageOS 15.1 and for some reason Windows does not recognize my phone (it does with other x4 phone from a friend).
I also don't have GApps installed and also don't have root access. Since I can't connect my phone, I can't root or flash some custom recovery.
I really need some help.
Hi all,
First of let me start by saying I have a Mi 9T and I know that it has its own forum, but I didn't find a solution to my problem there, so I thought I'd ask in this forum as well, since the devices look a lot like each other but here are more people.
So my problem is I got stuck in a bootloop which I can't seem to get out of. I can boot into fastboot mode and adb fastboot AND Miflash recognize my device, so I'm able to flash things, but the bootloop still stays.
I started on global rom, and then installed twrp. Then I flashed the latest 9.7.25 ROM from mi-globe for MI 9T. It booted up fine, but my TWRP was removed and I couldn't install it anymore like the first time. For some reason I did a factory reset then. And tried to flash a new ROM by using MiFlash. It said it was succesfull, but it only took 1 second and it didn't automatically boot (it stayed in fastboot mode). I tried again and it said anti-rollback error.
So that didn't work, so I tried flashing boot.img, recovery.img and system,img seperately by using adb fastboot. That worked and it booted normally. I went through the startup configuration like selecting wifi network and gmail,etc. But after trying to set a fingerprint, the screen went completely black but the phone was still on. I could reboot it normally, but when the lockscreen came up or I tried to use fingerprint scanner it went black completeley every time.
I was desperate, so I used 'fastboot erase system -w' in adb fastboot, which is a factory reset apparently. Then I flashed the 3 .img files like I did before, but this time it didn't boot, but went into bootloop.
I also tried 'fastboot boot twrp.img' which also didn't get me into twrp, it just goes to bootloop again.
So to summarize: I CAN get into fastboot and adb fastboot and miflash DO recognize my device, but I can't get out of bootloop no matter what I flash.
Does anyone know a solution for this problem? I would be very thankful.
I also don't understand why flashing or booting TWRP doesn't work, while it worked the first time. I also don't understand why flashing the 3 .img files doesn't work this time, like it used to work the first time.
Btw my anti getvar is 1.
Are you using windows 10? Had same issue with MiFlash and had to use a laptop with earlier version of Windows to get it working
DaveHTC200 said:
Are you using windows 10? Had same issue with MiFlash and had to use a laptop with earlier version of Windows to get it working
Click to expand...
Click to collapse
I do, but I don't have anything else than that. Are you sure that was the problem and not something else?
Rapydax said:
I do, but I don't have anything else than that. Are you sure that was the problem and not something else?
Click to expand...
Click to collapse
I've not had your issue but that was causing the flash tool to just carry out the task in 1 second, which isn't possible
i have the same situation here. did your issue solve?
Hello there.
Just like title says - I've got my hands on new Redmi 9 (lancelot) nfc 4/64 version. I've unlocked it from Mi stuff successfully yesterday and wanted to install there twrp, magisk and titanium backup to clean a bit and maybe to have foundations for further change of rom.
However, my phone gaves answers, that I do not understand correctly.
Firstly - after first instalation of twrp via adb it booted into this. However, after choosing option to boot to system from it, power off via ui and then another try to enter recovery...it gave me stock miui recovery again. When I've tried the same steps for second time, phone finished, but after restart it entered bootloop. I've followed steps from this guide - https://miui.blog/redmi-9/download-install-twrp-and-root-redmi-9-codename-lancelot/
After some time I've managed to make low-level rom instalation again (12.0.4 official lancelot rom, dated 31st of Mar, 21) to at least being able to communicate with it (done with usage of miflash 2018 version and rom in *.tgz file). This time, I've used help from this page - https://www.getdroidtips.com/guide-flash-miui-rom-xiaomi-devices/ - had some troubles with mediatek based phones before in my life, so it wasn't from scratch, but some time to understand it were needed.
Phone is working again, but this rom is based on Android 10 (which I would like to keep, if it won't cause too much trouble). And I think because of that fastboot mode changed now into fastbootD mode, where old commands from adb does not recognize the device, thus no flashing recovery action etc can be taken.
Is there a workaround here? I've stumbled across some articles about installing clean Generic System Image with Android 10 on this phone (since it has been released with android greater, than number 8), but again - this requires to have custom recovery, prefeably twrp. I cannot do anything about it, because I got back to stock recovery (which now at least works, yesterday phone was so twisted at one point, that he cannot even load this recovery, but somehow managed to open system and fastboot modes normally (!!!)).
Is there a way to work it out? Older miui version, older android version, then twrp, then update via twrp? Or an alternative method, since google changed something in partitions again (not sure, if I get it right, but it might be it)? I would actually like to stay somewhere around miui (at least let it be official with ota support without too much issues), but without twrp I cannot do anything. I also do know, that there aren't any official twrp/pbrp yet (just betas). Could it also be the issue with troubles with installing it and staying it on the phone?
buczek0711 said:
Hello there.
Just like title says - I've got my hands on new Redmi 9 (lancelot) nfc 4/64 version. I've unlocked it from Mi stuff successfully yesterday and wanted to install there twrp, magisk and titanium backup to clean a bit and maybe to have foundations for further change of rom.
However, my phone gaves answers, that I do not understand correctly.
Firstly - after first instalation of twrp via adb it booted into this. However, after choosing option to boot to system from it, power off via ui and then another try to enter recovery...it gave me stock miui recovery again. When I've tried the same steps for second time, phone finished, but after restart it entered bootloop. I've followed steps from this guide - https://miui.blog/redmi-9/download-install-twrp-and-root-redmi-9-codename-lancelot/
After some time I've managed to make low-level rom instalation again (12.0.4 official lancelot rom, dated 31st of Mar, 21) to at least being able to communicate with it (done with usage of miflash 2018 version and rom in *.tgz file). This time, I've used help from this page - https://www.getdroidtips.com/guide-flash-miui-rom-xiaomi-devices/ - had some troubles with mediatek based phones before in my life, so it wasn't from scratch, but some time to understand it were needed.
Phone is working again, but this rom is based on Android 10 (which I would like to keep, if it won't cause too much trouble). And I think because of that fastboot mode changed now into fastbootD mode, where old commands from adb does not recognize the device, thus no flashing recovery action etc can be taken.
Is there a workaround here? I've stumbled across some articles about installing clean Generic System Image with Android 10 on this phone (since it has been released with android greater, than number 8), but again - this requires to have custom recovery, prefeably twrp. I cannot do anything about it, because I got back to stock recovery (which now at least works, yesterday phone was so twisted at one point, that he cannot even load this recovery, but somehow managed to open system and fastboot modes normally (!!!)).
Is there a way to work it out? Older miui version, older android version, then twrp, then update via twrp? Or an alternative method, since google changed something in partitions again (not sure, if I get it right, but it might be it)? I would actually like to stay somewhere around miui (at least let it be official with ota support without too much issues), but without twrp I cannot do anything. I also do know, that there aren't any official twrp/pbrp yet (just betas). Could it also be the issue with troubles with installing it and staying it on the phone?
Click to expand...
Click to collapse
After to flash TWRP you have to flash the vbmeta.img and then boot to TWRP not through commands but manually with hardware buttons, don't allow device to boot to system before to boot to custom recovery otherwise this will be overwritten again.
I've done that with this vbmeta, one and only difference might be that I was trying to get into twrp by commands (however, it did not work XD). Overwritten isn't an issue in my opinion, since I do have booted to recovery after installing it yesterday and then from it choose option "reboot to system". After poweroff from system and then trying to get into recovery, then stock showed.
I'm currently trying this - https://c.mi.com/oc/thread-3312019-1-0.html
After putting this command to cmd - bcdedit /set testsigning on lancelot shows somewhere, but I cannot install it (most likely due to this issue about encrypted drivers). I'll try to overcome it now.
Yea, well, I've tried this method from link listed above, phone still enters fastbootd mode, still is not-visible from cmd started from google platform tools folder (which a subfolder to working adb). Not sure what to do now.
buczek0711 said:
I've done that with this vbmeta, one and only difference might be that I was trying to get into twrp by commands (however, it did not work XD). Overwritten isn't an issue in my opinion, since I do have booted to recovery after installing it yesterday and then from it choose option "reboot to system". After poweroff from system and then trying to get into recovery, then stock showed.
I'm currently trying this - https://c.mi.com/oc/thread-3312019-1-0.html
After putting this command to cmd - bcdedit /set testsigning on lancelot shows somewhere, but I cannot install it (most likely due to this issue about encrypted drivers). I'll try to overcome it now.
Click to expand...
Click to collapse
No, this is not the method to boot to recovery from what I pointed out, you don't have to firstly power off device but from fastboot commands you can type either fastboot or fastbootd reboot and inmediately press the volume up till the TWRP logo appears, the fastboot/d command will act same as it be the power button.
The thread explains how to install unsigned drivers in Windows, not to set it on your Redmi but is for your PC. If you succesfully get the drivers installed then you have to reboot your PC entering again in safe mode (not normal mode) and from there the commands through fastbootd are generally the same than those for fastboot.
buczek0711 said:
Yea, well, I've tried this method from link listed above, phone still enters fastbootd mode, still is not-visible from cmd started from google platform tools folder (which a subfolder to working adb). Not sure what to do now.
Click to expand...
Click to collapse
Just to be sure you are doing fine and not missing something the adb commands work while device is on and fastboot/d commands work only in fastboot mode.
Can you attach some SS to see what you are typing and the error that brings the cmd?
Hm, you say, that I can type fastbootd into cmd and this will be recognised? It seems that it cannot be recognised in this case, when I'm trying to type fastbootd powershell says "unknown command".
Typing fastboot /d devices results in "waiting for device", despite phone being in fastbootd all the time.
I'll attach ss tomorrow - it is time to sleep for me now, gotta wake up early. Then we will also know something else, when it comes to behavior after restart pc (once again, I've done it all in one sit, it might be an issue here).
PS. if you want english errors, I'll have to use powershell - cmd is in my native language (polish). Found out, that it doesn't really matter, which program you use, powershell simply can do more, while cmd dates back 30 years or so.
Anyway - phone is still booting to miui 12 and android 10 normally, I do not set there google acc or lock yet, so don't know if there's any issue with it (most likely no).
I've also stumbled across some dude from indonesia, who had the same phone, miui 12.0.1 with android 10 and he installed successfully twrp, then magisk, but he also put some small img - misc misc.img. Could it be the issue?
I'm giving link to this material on YT -
FROM WHAT I SEE IN THE THUMBNAIL, this version of twrp is even the same (code number and english translated from chinese), that once worked here (md5 of the file might be different, though).
There's also an option to reinstall again whole adb, platform tools, drivers from official miunlock app etc, but since I do not had ANY android-related problems on this pc with previous phones, I'm not sure if this is worth our time.
And I think that if I would misspell something in cmd program would give me error instantly, instead of behaving like it was nothing - i've made tons of errors before and cmd/powershell always informed me about it in first line of their texts.
buczek0711 said:
Hm, you say, that I can type fastbootd into cmd and this will be recognised? It seems that it cannot be recognised in this case, when I'm trying to type fastbootd powershell says "unknown command".
Typing fastboot /d devices results in "waiting for device", despite phone being in fastbootd all the time.
Click to expand...
Click to collapse
Yes, fastboot works normally while in cmd, this is intended for that, no problem to enter firstly toi Power Shell but you can switch to cmd from PS just typing cmd and all the commands from here will be for cmd, doesn´t matter at all how many old is, cmd can work inside PS keeping the same aspect.
buczek0711 said:
I'll attach ss tomorrow - it is time to sleep for me now, gotta wake up early. Then we will also know something else, when it comes to behavior after restart pc (once again, I've done it all in one sit, it might be an issue here).
PS. if you want english errors, I'll have to use powershell - cmd is in my native language (polish). Found out, that it doesn't really matter, which program you use, powershell simply can do more, while cmd dates back 30 years or so.
Anyway - phone is still booting to miui 12 and android 10 normally, I do not set there google acc or lock yet, so don't know if there's any issue with it (most likely no).
I've also stumbled across some dude from indonesia, who had the same phone, miui 12.0.1 with android 10 and he installed successfully twrp, then magisk, but he also put some small img - misc misc.img. Could it be the issue?
I'm giving link to this material on YT -
FROM WHAT I SEE IN THE THUMBNAIL, this version of twrp is even the same (code number and english translated from chinese), that once worked here (md5 of the file might be different, though).
There's also an option to reinstall again whole adb, platform tools, drivers from official miunlock app etc, but since I do not had ANY android-related problems on this pc with previous phones, I'm not sure if this is worth our time.
And I think that if I would misspell something in cmd program would give me error instantly, instead of behaving like it was nothing - i've made tons of errors before and cmd/powershell always informed me about it in first line of their texts.
Click to expand...
Click to collapse
You don't need to reinstall nothing, just from the downloaded SDK platform do all that you want to avoid misspelling path and folder directories, I mean place the files you need to use in the same directory and open terminal prompt (PS) in the same folder where adb/fastboot binaries are, pressing right mouse button and shift at same time.
I feel you are missing something simply here, not so hard to do.
The misc.img partition that you mentioned is just to restore something that went wrong in the process.
But if you are happy with this Miui ROM then great. No hurry to answer that, give your time to rest.
I also feel, that there is something simply to overcome, Only the fastbootd is new Stuff to me. However, any time I was doing something with Snap, i was long after finish by the current time (almost a month with It and 3rd day with fastbootd issue).
I don't get it. Now when I've tried to enter fastboot mode...phone entered it (fastboot, not fastbootD). Then I've installed pitch black recovery and sucessfully booted into it by restarting phone and then pressing vol up. Now I'm trying with magisk and another entry to pbrp.
Second try gave me stock recovery again. What is wrong with it XD?
something is wrong. Installing twrp resulting in nothing (stock recovery is still there), installing pitch black resulting in successfully boot into new recovery. However, this recovery does not see any zip (magisk zip, to be exact, that I've put there before it to root phone). After boot into system and then power it off to boot into recovery...phone boots into stock recovery. Should I downgrade system to miui 11 to be able to get over it? Or should I wait until miui 12.5 enters redmi 9?
My tries of installing it has been done by using cmd with admin rights, if it does make any difference.
buczek0711 said:
something is wrong. Installing twrp resulting in nothing (stock recovery is still there), installing pitch black resulting in successfully boot into new recovery. However, this recovery does not see any zip (magisk zip, to be exact, that I've put there before it to root phone). After boot into system and then power it off to boot into recovery...phone boots into stock recovery. Should I downgrade system to miui 11 to be able to get over it? Or should I wait until miui 12.5 enters redmi 9?
My tries of installing it has been done by using cmd with admin rights, if it does make any difference.
Click to expand...
Click to collapse
I think you are not following the right direction, if you want consider what I pointed out; you don't have to power off device prior to boot to recovery for first time but you have to type from fastboot (no matter fastbootd) and inmediately from there boot to the custom recovery, when you succesfully booted to custom recovery then flash the recovery zip if there is one (PBR and OFR have one) and if not a zip then flash the image again to the recovery partition, also check if there is some installer apart from the image that can fix it in the ramdisk partition, at this point your issue is solved, next step is to reboot device to system normally, if you don't have any issue on that then OK but if you can´t there some steps more that you should do, but let this for last.
Ok, let's group it.
I do not think that particular matter of how do I restart phone matters here (at least, I do not believe it, that it does anything).
Option to restart to recovery from adb still not working.
Trying to find magisk.zip in main directory of internal storage still fails under pitch black recovery project.
From new stuff - I now got an error message, while opening pbrp, most likely with the issues about system being read-only (not sure though, since I do not remember it now, might look into it once more). I have the options to mount partitions, available from main menu, but since I do not used it at all before, I do not know, how to deal with it.
Also - my system boots normally, it must have overwritten recovery (or at least header of it) sometime during boot, since custom recovery is unavailable to access after first full reboot.
I'll try now to install newer version of twrp from yt that I've posted days back. I would also try with orange fox (however, i cannot find img for it, just source code, don't get it).
Is there someone, who can and will to help me?
Situation looks this - on this 12.0.4 MIUI with android 10 I'm unable to install ANY recovery (either phone do not restart to recovery after proper command from cmd or it boots into it, but after visiting system and then to recovery again it shows stock (even without any operations or updates from ota).
I cannot force to work either twrp 3.4.2b, twrp 3.5.2, pitch black recovery 3.0.0 beta.
After trying to install magisk 21.4 zip from twrp 3.4.2b phone entered bootloop, because f**k you, user, I cannot even get it to fastboot mode now (btw, fastboot now works, fastbootD is luckily a long-gone crap).
All cmd's have been run with admin rights. There are NO SUCH THING, as misspelling (cmd and adb would not execute command ,if it is misspelled, either command or filename). I've installed drivers once again and used cmd from dedicated folder with adb fastboot portable version (runned as admin, of course).
Now I'm downloading older version of rom for fastboot (miui 11.0.9) with android 10. Something has to finally work on this piece of junk.
Writting each time is success (cmd says "OKAY" nad displays time, it took to do so), downloading recovery image to start from it also works, there aren't any errors in cmd, yet phone still isn't working.
Where's the issue with it? Apart from being mediatek, which seems to somehow enormously hardened any flashing? I did not encounter anything like this with qualcomm, yet mediatek still manages to pisses me off with their really weird implementations and working (???) of their stuff.
another update from battlefield. Managed to finally get mediatek verify bypass in smart phone flashing tool, however it ended with forcing me to format anything in the phone (if not, program would not let me install anything).
Second problem is forcing me to disable verify, yet command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img put in fastboot mode (yes, it works now) does not work, because adb says, that "--disable-verity" is not a recognised command.
SPFT cannot properly download images from phone and welcomes me with error about download exception, happening either in recovery part or in boot part. SInce I do have access to fastboot now, I can overcome it (I think).
Old miflash tool to install roms via fastboot says it cannot flash rom in locked stage (I might have lost unlocked status, but I'm not sure about it). Do you know ways to overcome it?
It is me again (inb4 use edit). Had to unlock phone again by using miphone unlocker (it went ok). Still cannot flash using SPFT, miflash started showing idiotic errors like "no file in directory" or "cannot access to directory" (it could before, I did not changed name of it). Will continue reporting of progress (or the so-called "progress").