Related
My moto z before using RSD lite flash NPL 25.86-30, then OTA updated to NPL25.86-30.3. It seems that bootloarder is also updated. now I want to re-use RSD lite to flash NPL25.86-30. But RSD has shown an error in flashing GPT.bin, show "FAIL"
Who can help me?:crying:
You can't go back, if the Bootloader got updated.
jump the step of flashing gpt by editing the xml file(delete the line)
Now my device have a very strange question, if I use the battery mod, is unable to shutdown, automatically enter the bootloarder. Do not use the module can shutdown, but the connection charger will automatically enter the bootloarder,can not be charged in the shutdown state.
Sorry,my english is bad.
rakee said:
Now my device have a very strange question, if I use the battery mod, is unable to shutdown, automatically enter the bootloarder. Do not use the module can shutdown, but the connection charger will automatically enter the bootloarder,can not be charged in the shutdown state.
Sorry,my english is bad.
Click to expand...
Click to collapse
start fastboot in the cmd and start the following command
fastboot oem fb_mode_clear
this should solve your bootlader at reboot issue...
treibstoff said:
start fastboot in the cmd and start the following command
fastboot oem fb_mode_clear
this should solve your bootlader at reboot issue...
Click to expand...
Click to collapse
Its work for me,thanks man!:highfive::highfive:
treibstoff said:
start fastboot in the cmd and start the following command
fastboot oem fb_mode_clear
this should solve your bootlader at reboot issue...
Click to expand...
Click to collapse
After the last OTA (july) update has failed, I got an issue very similar, but in my case, everytime I restart or turn off the device, it gets to twrp recovery and I need do restart it on fastboot mode then choose START on side menu to get boot properly. Can you help?
When I'm try to boot in fastboot mode the fastboot mode (volume down+power) will only display for about 10 seconds and then it will reboots itself into charging mode. doesn't matter if i use the key, or even use adb commands to get there. it will still reboot itself in short period of time.
why is this happening? i just want to unlock my bootloader thats all...
Please help me... thanks in advance....
Smart Sujoy said:
When I'm try to boot in fastboot mode the fastboot mode (volume down+power) will only display for about 10 seconds and then it will reboots itself into charging mode. doesn't matter if i use the key, or even use adb commands to get there. it will still reboot itself in short period of time.
why is this happening? i just want to unlock my bootloader thats all...
Please help me... thanks in advance....
Click to expand...
Click to collapse
Your computer is unable to detect the phone in fastboot mode. Uninstall and reinstall the fastboot drivers, the proper ones. If successfully detected it should not be rebooting.
Cheers
ArK96 said:
Your computer is unable to detect the phone in fastboot mode. Uninstall and reinstall the fastboot drivers, the proper ones. If successfully detected it should not be rebooting.
Cheers
Click to expand...
Click to collapse
I just try this...but nothing happened...
Smart Sujoy said:
I just try this...but nothing happened...
Click to expand...
Click to collapse
That ten seconds when phone is turned on in fastboot and connected to computer quickly type this command in command prompt without the quotes
" fastboot devices "If a device with device number shows up fastboot drivers are installed correctly or else if nothing shows up fastboot drivers are not installed properly..so check them.
Smart Sujoy said:
When I'm try to boot in fastboot mode the fastboot mode (volume down+power) will only display for about 10 seconds and then it will reboots itself into charging mode. doesn't matter if i use the key, or even use adb commands to get there. it will still reboot itself in short period of time.
why is this happening? i just want to unlock my bootloader thats all...
Please help me... thanks in advance....
Click to expand...
Click to collapse
i actually watched this video, to unlock my bootloader
https://youtu.be/dDRC-J-cLlE
Smart Sujoy said:
When I'm try to boot in fastboot mode the fastboot mode (volume down+power) will only display for about 10 seconds and then it will reboots itself into charging mode. doesn't matter if i use the key, or even use adb commands to get there. it will still reboot itself in short period of time.
why is this happening? i just want to unlock my bootloader thats all...
Please help me... thanks in advance....
Click to expand...
Click to collapse
Im having this issue now on my redmi note 4x.
Do you have a solution? Thanks
Man, you need adb bootloader interface installed properly.
Open device manager, and you'll see something popping out when you connect your device to pc on fastboot mode, there you can see what's wrong. So all you need is update that wrong driver (the one that popped out once you connect your device in fastboot mode) and install redmi note 4x driver, just ignore your disappearing fastboot mode in your device, keep install it. You should have your redmi note 4x driver prepared btw, you can google it.
Good luck!
use USB2 port, do not use USB3
Smart Sujoy said:
When I'm try to boot in fastboot mode the fastboot mode (volume down+power) will only display for about 10 seconds and then it will reboots itself into charging mode. doesn't matter if i use the key, or even use adb commands to get there. it will still reboot itself in short period of time.
why is this happening? i just want to unlock my bootloader thats all...
Please help me... thanks in advance....
Click to expand...
Click to collapse
Update your redmi note 4 driver in PC through a software called driver booster.... It's free
AtheistZ said:
Update your redmi note 4 driver in PC through a software called driver booster.... It's free
Click to expand...
Click to collapse
NO ADS!!!!
and2nckiko said:
Im having this issue now on my redmi note 4x.
Do you have a solution? Thanks
Click to expand...
Click to collapse
That is because your computer does not make any connection with your phone. Are you sure that you have all drivers installed. You can install fastboot drivers with mi flash tool but before that write this command in an admin cmd - bcdedit /set TESTSIGNING OFF and reboot. Now you can now install the fastboot driver from mi flash tool and try your luck
ArK96 said:
That ten seconds when phone is turned on in fastboot and connected to computer quickly type this command in command prompt without the quotes
" fastboot devices "If a device with device number shows up fastboot drivers are installed correctly or else if nothing shows up fastboot drivers are not installed properly..so check them.
Click to expand...
Click to collapse
Bro my bootloader is already unlocked but my phone still restarts after 10 second i did not connected to any usb still it restarts i updated magisk today and now nothing is working in my phone no call incomming and outgoing audio is fully disabled when i turn on audio in any app it crashes or freezes i tried to factory data reset my phone but nothing works plzz help me broo
Leeeop90 said:
Bro my bootloader is already unlocked but my phone still restarts after 10 second i did not connected to any usb still it restarts i updated magisk today and now nothing is working in my phone no call incomming and outgoing audio is fully disabled when i turn on audio in any app it crashes or freezes i tried to factory data reset my phone but nothing works plzz help me broo
Click to expand...
Click to collapse
My root is also lost
JustExperimentingRedmi said:
That is because your computer does not make any connection with your phone. Are you sure that you have all drivers installed. You can install fastboot drivers with mi flash tool but before that write this command in an admin cmd - bcdedit /set TESTSIGNING OFF and reboot. Now you can now install the fastboot driver from mi flash tool and try your luck
Click to expand...
Click to collapse
So drivers are needed for fastboot flashing a xiaomi phone?
Why I didn't need drivers to use fastboot with other phone manufacturers?
In these phones (oppo, op) the phone stays in fastboot mode until you exit or shut it down.
I think xiaomi did a bad move with this.
───────
EDIT: It works in debian without any additional drivers.
Fastboot recognizes the xiaomi phone with "fastboot devices" command.
So it was as you said.
Hello everyone, this is my first post on the forum.
I have a xiaomi redmi note 4 snapdragon with bootloader unlocked and when I try to install TWRP by ADB it installs it, but when I put the command "flashboot boot twrp.img" it stays in the fastboot logo.
Try using power and volume + to enter the recovery, but enter the original recovery
Can anyone help me? Thank you
Merli- said:
Hello everyone, this is my first post on the forum.
I have a xiaomi redmi note 4 snapdragon with bootloader unlocked and when I try to install TWRP by ADB it installs it, but when I put the command "flashboot boot twrp.img" it stays in the fastboot logo.
Try using power and volume + to enter the recovery, but enter the original recovery
Can anyone help me? Thank you
Click to expand...
Click to collapse
Which output do you get in ADB after you type in the command?
Merli- said:
Hello everyone, this is my first post on the forum.
I have a xiaomi redmi note 4 snapdragon with bootloader unlocked and when I try to install TWRP by ADB it installs it, but when I put the command "flashboot boot twrp.img" it stays in the fastboot logo.
Try using power and volume + to enter the recovery, but enter the original recovery
Can anyone help me? Thank you
Click to expand...
Click to collapse
Could be possible due to old drivers.
Try these platform tools
https://drive.google.com/file/d/13Sjej5zIJPm_yiJQOVR4rEocwbhDc9oh/view?usp=drivesdk
Noter2017 said:
Which output do you get in ADB after you type in the command?
Click to expand...
Click to collapse
downloading 'boot.img'...
OKAY [ 0.792s]
booting...
OKAY [ 0.558s]
finished. total time: 1.353s
After that, it disconnects from the PC and stays in the fastboot logo
MyNameIsRage said:
Could be possible due to old drivers.
Try these platform tools
Try and it does not work, the same thing happens :S
Click to expand...
Click to collapse
MyNameIsRage said:
Could be possible due to old drivers.
Try these platform tools
Click to expand...
Click to collapse
Try and it does not work, the same thing happens :S
Merli- said:
Try and it does not work, the same thing happens :S
Click to expand...
Click to collapse
What process do you follow?
I happened to do it, by copying the recovery file inside the platform tools folder.
Then inside the folder hold shift and right click. It will show an option to open command prompt window or open powershell window here. From there i wrote the commands, fastboot flash recovery recovery.img , and then manually booted to twrp by holding the vol up and power
MyNameIsRage said:
What process do you follow?
I happened to do it, by copying the recovery file inside the platform tools folder.
Then inside the folder hold shift and right click. It will show an option to open command prompt window or open powershell window here. From there i wrote the commands, fastboot flash recovery recovery.img , and then manually booted to twrp by holding the vol up and power
Click to expand...
Click to collapse
I followed that process and it did not work, try two different versions of Twrp and it still did not work. I resigne myself, and try to install the RedWolf recovery with the same process, and this time it works! :fingers-crossed: I could finally install another rom. Thanks for the help
Same problem here, really strange. First time I've this kind of problem.
Edit : Ok, problem solved. There is 2 things to do in addition of the main installation process (found here : https://wiki.lineageos.org/devices/mido/install#installing-a-custom-recovery-using-fastboot )
Firstly, you have to enable OEM Unlocking in Developer option menu. And not only enable USB Debugging. To enable it, click twice on the button "OEM Unlock" (if you click once, it will disable automatically when exiting Dev' menu).
Secondly, once you ran
Code:
fastboot flash recovery twrp-x.x.x-x-mido.img
, you also have to ran
Code:
fastboot boot twrp-x.x.x-x-mido.img
in order to reboot in recovery mode. Otherwise default recovery will automatically erase and replace TWRP.
These 2 steps are quite never documented, but are mandatory for Mido (Redmi Note 4) !!
Skip88 said:
Same problem here, really strange. First time I've this kind of problem.
Click to expand...
Click to collapse
In my case the problem appeared since repair and replace the screen. The unique twrp I could install from ADB was twrp RedWolf
Merli- said:
In my case the problem appeared since repair and replace the screen. The unique twrp I could install from ADB was twrp RedWolf
Click to expand...
Click to collapse
I've edited my post. There is 2 missing steps to be able to install TWRP correctly (then LineageOS^^).
thanks a lot u r a lifesaver.....
Skip88 said:
Same problem here, really strange. First time I've this kind of problem.
Edit : Ok, problem solved. There is 2 things to do in addition of the main installation process (found here : https://wiki.lineageos.org/devices/mido/install#installing-a-custom-recovery-using-fastboot )
Firstly, you have to enable OEM Unlocking in Developer option menu. And not only enable USB Debugging. To enable it, click twice on the button "OEM Unlock" (if you click once, it will disable automatically when exiting Dev' menu).
Secondly, once you ran
Code:
fastboot flash recovery twrp-x.x.x-x-mido.img
, you also have to ran
Code:
fastboot boot twrp-x.x.x-x-mido.img
in order to reboot in recovery mode. Otherwise default recovery will automatically erase and replace TWRP.
These 2 steps are quite never documented, but are mandatory for Mido (Redmi Note 4) !!
Click to expand...
Click to collapse
Thanks a lot u r a lifesaver.....trying it since last 2 days...now finally it worked after i followed ur above mentioned steps...now i just to wait to see if it isnt in bootloop and then i ll check my root status....thanks
I am trying to root my OPPO A72. After successfully configuring the adb and USB Debugging I was trying to fastboot it using 'adb reboot bootloader', because 'adb reboot fastboot' reboots it to recovery, which I do not want. After rebooting the phone using 'adb reboot bootloader' for half a second there is chinese text with the text 'FASTBOOT', then it just reboots the phone into android. The OEM Unlocking option does not help. Any ideas why that is / how to fix?
randomizedhex said:
I am trying to root my OPPO A72. After successfully configuring the adb and USB Debugging I was trying to fastboot it using 'adb reboot bootloader', because 'adb reboot fastboot' reboots it to recovery, which I do not want. After rebooting the phone using 'adb reboot bootloader' for half a second there is chinese text with the text 'FASTBOOT', then it just reboots the phone into android. The OEM Unlocking option does not help. Any ideas why that is / how to fix?
Click to expand...
Click to collapse
The A72 cannot be rooted at the moment.
with phone on if you enter adb reboot fastboot , it takes you too a screen similar to the recovery screen but you can access phone by fastboot devices etc ... BUT it's a very limited fastboot and hardly any use at all , and will not allow you to unlock bootloader.
linccracker said:
The A72 cannot be rooted at the moment.
with phone on if you enter adb reboot fastboot , it takes you too a screen similar to the recovery screen but you can access phone by fastboot devices etc ... BUT it's a very limited fastboot and hardly any use at all , and will not allow you to unlock bootloader.
Click to expand...
Click to collapse
I can't even get into this limited fastboot. Any idea why?
Bobgle said:
I can't even get into this limited fastboot. Any idea why?
Click to expand...
Click to collapse
Have you tried adb reboot fastboot
linccracker said:
Have you tried adb reboot fastboot
Click to expand...
Click to collapse
What happens when you type this command
linccracker said:
What happens when you type this command
Click to expand...
Click to collapse
It reboots immediately. No device detected by fastboot or adb during that.
Bobgle said:
It reboots immediately. No device detected by fastboot or adb during that.
Click to expand...
Click to collapse
What firmware version is it running
linccracker said:
What firmware version is it running
Click to expand...
Click to collapse
v1.2, but I just managed to get into fastbootd mode. It seems like there are no commands available though, just as you said. Is EDL worth anything? What would be the steps to flashing this phone if there is no support by OPPO?
HI to all
I got my phone back from service, latest version installed (DN2103_11_A.14 EU).
I will flash TWRP and root, so do I need A.14 vbmeta or can I just use vbmeta from same post I will download TWRP?
If I need A.14 vbmeta, does anyone have it?
Thanks
There is no difference, the same one can be used for all versions.
you can use the vbmeta from TWRP Thread.
Zombnombs said:
There is no difference, the same one can be used for all versions.
Click to expand...
Click to collapse
HI and thank you.
HofaTheRipper said:
you can use the vbmeta from TWRP Thread.
Click to expand...
Click to collapse
HI and thank you.
How do you enter fastboot mode? There is no option from power button, and when I use adb reboot bootloader, I go to a black screen with font size 1 that says we are in fastboot mode, and this is for developers only, press power up + power to exit.
In recovery there is no "Advanced" option to reboot to fastboot.
krugm0f0 said:
I use adb reboot bootloader, I go to a black screen with font size 1 that says we are in fastboot mode, and this is for developers only, press power up + power to exit
Click to expand...
Click to collapse
That's exactly what fastboot mode is. Your phone is in fastboot mode. Use your poershell terminal on the pc to start sending fastboot commands. Eg "fastboot devices" to test the connection.
If you phone is not responding to fastboot commands, try adding "./" to the start of every fastboot command instead, eg "./fastboot devices"
Zombnombs said:
That's exactly what fastboot mode is. Your phone is in fastboot mode. Use your poershell terminal on the pc to start sending fastboot commands. Eg "fastboot devices" to test the connection.
If you phone is not responding to fastboot commands, try adding "./" to the start of every fastboot command instead, eg "./fastboot devices"
Click to expand...
Click to collapse
It's just that it looks nothing like the fastboot mode on my OP2, OPX, OP5T or OP Nord 5G. And it's not recognized by fastboot devices, and does not accept any commands. <waiting for device>
krugm0f0 said:
It's just that it looks nothing like the fastboot mode on my OP2, OPX, OP5T or OP Nord 5G. And it's not recognized by fastboot devices, and does not accept any commands. <waiting for device>
Click to expand...
Click to collapse
Seems like you just don't have the right drivers installed. Sure it looks different but that doesn't mean it has to work differently.
Windows can get the drivers automatically for you, connect in fastboot mode, then check for updates in windows, then they should either get installed or show up in optional updates as Mediatek ADB something.