Hi guys I am having an interested issue,
I want to install custom rom in my phone
I have downloaded in depth test and applied for un depth test
my mobile do connect to computer when it prompt to select mod I do select file transfer and my mobile do connect to laptop
and it shows in "adb devices" but when it goes into bootloader mod my mobile gets disconnected I have done everything I could
I have install every possible driver i got from articles but non worked is it the issue with my windows 10 ? or driver issue I have spent my whole night on this but couldn't find the way
fastboot devices
0purple said:
fastboot devices
Click to expand...
Click to collapse
what does it mean ?
when i connect my phone it prompt me with this and usb debugging is on
i tried adb devices but it didn't showed anything but when i chose transfer file it do connect to the laptop and shows in adb devices
najam489 said:
what does it mean ?
Click to expand...
Click to collapse
Try it once you are in fastboot
wow its showing
najam489 said:
wow its showing
Click to expand...
Click to collapse
0purple said:
Try it once you are in fastboot
Click to expand...
Click to collapse
i have another problem now my device is showing with fastboot devices but my devices status is locked when i tried this command "fastboot flash recovery recovery.img" it didnt work i am follwing this article https://www.guidetoroot.com/root-realme-3-pro/
thank you for your help my bootloader wasn't unlock it is now thanks a lot
It appears your device's bootloader is locked. Try:
fastboot oem unlock
fastboot flashing unlock
If that doesn't help, search for a guide on how to unlock bootloader for your specific brand.
It also looks like don't really know what you are doing. Make sure you are following trusted guide. If no, I'll be happy to help.
0purple said:
It appears your device's bootloader is locked. Try:
fastboot oem unlock
fastboot flashing unlock
If that doesn't help, search for a guide on how to unlock bootloader for your specific brand.
It also looks like don't really know what you are doing. Make sure you are following trusted guide. If no, I'll be happy to help.
Click to expand...
Click to collapse
well i did installed custom roms few time but i dont know much, i did unlock bootloader now the problem is i do install custom recovery twrp and it do installed and rom manager shows that custom recovery is installed but pressing volume down + power button just shows fastboot logo and it restart my phone, and with command "
adb reboot bootloader" i am able to boot into fastboot mood and when i go to recovery from their it open stock recovery instead of twrp
Stolen from my guide:
7. Go into fastboot mode
8. fastboot flash recovery recovery.img
9. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
10. fastboot reboot recovery
12. Sometimes recovery doesn't want to stick as a permanent one. To test it, hold the power button and select "Reboot to recovery". If you reboot to TWRP, you can move on, but if you reboot to stock one, flash recovery using fastboot again and from recovery flash recovery again (sounds crazy, right?). I won't give you instructions on this, research it yourself. Make sure guide you will find is for your device and your recovery.
Related
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 having trouble rooting my Galaxy J7 Prime sm-j727t
Every Odin version I use with every TWRP tar file I try to use doesn't work. They either Fail or Odin stops responding when I try to load the tar file into the AP.
I've tried just using the CF Auto Root and those fail as well.
Any ideas what the issue is? I've been trying for two days with no success
Is your bootloader unlocked?
Emir Çetin said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
I thought Samsung phones come with bootloader unlocked already??
BramaKnox said:
I thought Samsung phones come with bootloader unlocked already??
Click to expand...
Click to collapse
You can check bootloader with dialer (search it).
Of phone has fastboot mode you can check bootloader with fastboot commands (search it too)
Emir Çetin said:
You can check bootloader with dialer (search it).
Of phone has fastboot mode you can check bootloader with fastboot commands (search it too)
Click to expand...
Click to collapse
When I put the phone in FastBoot mode I have the following options
Reboot System Now
Reboot to Bootloader
Apply update from ADB
Apply Update from SD card
Wide data/factory reset
Wipe Cashe partition
Mount /system
View recovery logs
Run graphics test
Power off
Lacking storage booting
1-Install your phones drivers on your PC.
2-Install adb and fastboot tools. https://www.addictivetips.com/android/download-adb-and-fastboot/
3-Reboot to fastboot.
4-Connect your phone with USB cable.
5-Open command prompt in adb and fastboot folder
6-Type fastboot devices (If you don't see your device there is a problem in drivers or fastboot)
7-Type fastboot oem device-info
You can check your bootloader status in that screen.
Emir Çetin said:
1-Install your phones drivers on your PC.
2-Install adb and fastboot tools. https://www.addictivetips.com/android/download-adb-and-fastboot/
3-Reboot to fastboot.
4-Connect your phone with USB cable.
5-Open command prompt in adb and fastboot folder
6-Type fastboot devices (If you don't see your device there is a problem in drivers or fastboot)
7-Type fastboot oem device-info
You can check your bootloader status in that screen.
Click to expand...
Click to collapse
Am I doing something wrong here ? see attached for screnshot
Emir Çetin said:
1-Install your phones drivers on your PC.
2-Install adb and fastboot tools. https://www.addictivetips.com/android/download-adb-and-fastboot/
3-Reboot to fastboot.
4-Connect your phone with USB cable.
5-Open command prompt in adb and fastboot folder
6-Type fastboot devices (If you don't see your device there is a problem in drivers or fastboot)
7-Type fastboot oem device-info
You can check your bootloader status in that screen.
Click to expand...
Click to collapse
I tried a some other steps. Tried using the video on youtube on a tut. When I get to the oem unlock I just get stuck with a msg sayng "waiting for any device" my device is plugged in, from what I know I have updated the samsung drivers (from previous attempt of other methods) the adb bootloader cmd did put my phone into fastboot mode
(White box, blue arrow point down with a straight line under the point)
(Blue screen with Downloading...)
do not turn off target
What am I missing here?
I tried rooting TWRP 3.2.3. with Odin on the phone again and it still failed
Does anyone else have any more insight to a possible solution?
Have you checked bootloader with dialer?
BramaKnox said:
I am having trouble rooting my Galaxy J7 Prime sm-j727t
Every Odin version I use with every TWRP tar file I try to use doesn't work. They either Fail or Odin stops responding when I try to load the tar file into the AP.
I've tried just using the CF Auto Root and those fail as well.
Any ideas what the issue is? I've been trying for two days with no success
Click to expand...
Click to collapse
Witch android you are?
I tried to much with installing diffent ROMs and now nothing's working anymore.
My poco starts only to fastboot but I can't connect with adb. Any other possibilities?
Drivers are all ok on the PC, because my second poco is normaly recognised.
Thanks for help.
Given unlocked bootloader, If you can only boot to fastboot maybe your recovery was deleted. You probably need to install twrp:
1.get twrp here:
https://forum.xda-developers.com/poco-f1/how-to/recovery-official-twrp-t3883736
2. If fastboot is working then:
https://www.xda-developers.com/how-to-install-twrp/
If you can boot to twrp then flash a custom rom
Note that I'm unsure if above will work, only guessed
Can't flash twrp because in adb mode it shows < waiting for any device >
gartmann said:
Can't flash twrp because in adb mode it shows < waiting for any device >
Click to expand...
Click to collapse
What happens if you type fastboot devices
Hi,
Would like some help with a little issue i'm having,
Got a HD1910 model of the phone running the global rom and it seems to be stuck in 'fastboot' mode. Every time the phone reboots or pressing 'start' it will return back to fastboot mode.
Extra details:
It's locked and the developer tools were never enabled.
Occasionally it has shown `qualcomm crash dump mode` with no extra details.
Using this MSM tool it completes successfully but still continues booting into fastboot mode.
All buttons and ports are working.
Using ADB `fastboot reboot` reboots the device but still into fastboot mode
It started to happen after I woke up from installing the latest OTA official oneplus update.
Any help would be appreciated
funnycube said:
Hi,
Would like some help with a little issue i'm having,
Got a HD1910 model of the phone running the global rom and it seems to be stuck in 'fastboot' mode. Every time the phone reboots or pressing 'start' it will return back to fastboot mode.
Extra details:
It's locked and the developer tools were never enabled.
Occasionally it has shown `qualcomm crash dump mode` with no extra details.
Using this MSM tool it completes successfully but still continues booting into fastboot mode.
All buttons and ports are working.
Using ADB `fastboot reboot` reboots the device but still into fastboot mode
It started to happen after I woke up from installing the latest OTA official oneplus update.
Any help would be appreciated
Click to expand...
Click to collapse
Try this might work need to download full ROM
1.Boot into recovery
2.Tap on upgrade from USB
3.Go to your computer and open a command window
"Click Shift and Right click simultaneously"
4. Type the following command
Adb sideload file name.zip
5.Wait for the process to complete
6.Reboot your device
jaythenut said:
Try this might work need to download full ROM
1.Boot into recovery
2.Tap on upgrade from USB
3.Go to your computer and open a command window
"Click Shift and Right click simultaneously"
4. Type the following command
Adb sideload file name.zip
5.Wait for the process to complete
6.Reboot your device
Click to expand...
Click to collapse
Thanks for the reply, but it seems entering into recovery just reboots back into fastboot mode.
Hmm, seems from your description as if your recovery is broken. You could flash a stock recovery in fastboot with the "fastboot flash recovery <filename.img>" command, for download of recoveries you could take a look at this thread and find one suitable for your device/regional version. Once you got a working recovery you can proceed as written above...
Good luck !
s3axel said:
Hmm, seems from your description as if your recovery is broken. You could flash a stock recovery in fastboot with the "fastboot flash recovery <filename.img>" command, for download of recoveries you could take a look at this thread and find one suitable for your device/regional version. Once you got a working recovery you can proceed as written above...
Good luck !
Click to expand...
Click to collapse
Thanks,
But it seems the requirements state it requires a `unlocked bootloader` which mine is not. :/
funnycube said:
Thanks,
But it seems the requirements state it requires a `unlocked bootloader` which mine is not. :/
Click to expand...
Click to collapse
You can try to reboot into stock recovery instead of flash it
"fastboot reboot recovery recovery.img"
And then follow the other steps explained on 2nd post
Hello everyone !
I updated my tablet to android 9, during the update an error occured and now my tablet can't boot (it's stuck on LENOVO screen forever).
My tablet is Lenovo TB-X605F.
I tried:
- Wipe/data (recovery mode)
- Wipe/cache (recovery mode)
- Fastboot (my bootloader is locked so I can do nothing)
Note: I don't have TWRP or custom recovery, I have the default one .
I don't know what can i do please help me !
XX_MRBEAN_XX said:
Hello everyone !
I updated my tablet to android 9, during the update an error occured and now my tablet can't boot (it's stuck on LENOVO screen forever).
My tablet is Lenovo TB-X605F.
I tried:
- Wipe/data (recovery mode)
- Wipe/cache (recovery mode)
- Fastboot (my bootloader is locked so I can do nothing mSpy reviews)
Note: I don't have TWRP or custom recovery, I have the default one .
I don't know what can i do please help me !
Click to expand...
Click to collapse
I am sorry to say that but I guess nothing could be done to fix your tablet. I would be happy to proven wrong and see some solutions in this thread.
@XX_MRBEAN_XX
The mostly overlooked command
Code:
adb sideload <ROM / MOD>
may help: Get device's Stock ROM and flash it this way.
jwoegerbauer said:
@XX_MRBEAN_XX
The mostly overlooked command
Code:
adb sideload <ROM / MOD>
may help: Get device's Stock ROM and flash it this way.
Click to expand...
Click to collapse
Windows detect my tablet only when It's in fastboot. I don't know why
When I do recovery --> apply update from adb it's say "E: failed to open driver control: Permission denied"
And in my pc, ADB don't recognize my tablet (only fastboot recognize)
Btw, i downloaded my stock tablet rom
XX_MRBEAN_XX said:
Windows detect my tablet only when It's in fastboot. I don't know why
When I do recovery --> apply update from adb it's say "E: failed to open driver control: Permission denied"
And in my pc, ADB don't recognize my tablet (only fastboot recognize)
Btw, i downloaded my stock tablet rom
Click to expand...
Click to collapse
1. Looks to me that the ADB-driver you use isn't suitable: Download and install the correct driver for your Lenovo. tab:
https://devsjournal.com/download-lenovo-usb-drivers-adb.html
2. Wondering why then you didn't flash this Stock ROM by means of Fastboot ?
Code:
fastboot devices
fastboot erase boot
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot flashall <STOCK-ROM-IMG>
fastboot reboot
jwoegerbauer said:
1. Looks to me that the ADB-driver you use isn't suitable: Download and install the correct driver for your Lenovo. tab:
2. Wondering why then you didn't flash this Stock ROM by means of Fastboot ?
Code:
fastboot devices
fastboot erase boot
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot flashall <STOCK-ROM-IMG>
fastboot reboot
Click to expand...
Click to collapse
Well, i think i am ****ed because when i do these fastboot command, it's saying "FAILED (remote: 'device is locked. Cannot erase.')
And adb still don't recognize my system.
Thank you for your help
XX_MRBEAN_XX said:
Well, i think i am ****ed because when i do these fastboot command, it's saying "FAILED (remote: 'device is locked. Cannot erase.')
Click to expand...
Click to collapse
Oh man
become familiar with Fastboot-driver and its subcommands available!!!
Anyway, unlock tab's boot-loader by means of Fastboot before you carry out the commands previously shown
Code:
fastboot devices
fastboot OEM unlock
FYI: I no longer participate with this thread.
jwoegerbauer said:
Oh man
become familiar with Fastboot-driver and its subcommands available!!!
Anyway, unlock tab's boot-loader by means of Fastboot before you carry out the commands previously shown
Code:
fastboot devices
fastboot OEM unlock
FYI: I no longer participate with this thread.
Click to expand...
Click to collapse
I tried fastboot oem unlock
It's say "unknow commands"
Anyway thank you for your help !
I think we can't do something for this tablet.
Thank you very much
XX_MRBEAN_XX said:
Hello everyone !
I updated my tablet to android 9, during the update an error occured and now my tablet can't boot (it's stuck on LENOVO screen forever).
My tablet is Lenovo TB-X605F.
I tried:
- Wipe/data (recovery mode)
- Wipe/cache (recovery mode)
- Fastboot (my bootloader is locked so I can do nothing)
Note: I don't have TWRP or custom recovery, I have the default one .
I don't know what can i do please help me !
Click to expand...
Click to collapse
To rescue a bricked Lenovo device, download their LMSA tool to a Windows PC. Use the Rescue option.
Have a look on the TWRP thread for the unlock commands. They will only work if you had already enabled Developer Options and OEM unlocking before the device bricked.
Yahoo Mike said:
To rescue a bricked Lenovo device, download their LMSA tool to a Windows PC. Use the Rescue option.
Have a look on the TWRP thread for the unlock commands. They will only work if you had already enabled Developer Options and OEM unlocking before the device bricked.
Click to expand...
Click to collapse
Holy crap. My hero! Can I buy you a beer dude?