Good afternoon.
I would like to install TWRP recovery on my phone so I could root it. Unfortunately, I can not put it in fastboot mode because when I use the command "adb reboot bootloader" i get this error message : "device offline". How can I solve this issue ?
Best regards.
I found the solution. I updated fastboot and now it's OK.
Related
Hi guys,
I'm trying to unlock the bootloader on my H815. I can reboot the bootloader but when I try the "fastboot oem device-id" command I just get "<waiting for device>". After that I need to pull the battery to reboot.
Has anyone else had this problem, any idea how to get past it?
**Corrupt zip removed**
syztemlord said:
Hi guys,
I'm trying to unlock the bootloader on my H815. I can reboot the bootloader but when I try the "fastboot oem device-id" command I just get "<waiting for device>". After that I need to pull the battery to reboot.
Has anyone else had this problem, any idea how to get past it?
Click to expand...
Click to collapse
Download and install the ADB & fastboot setup file I have attached. Allow admin rights at prompt and enter Y twice when prompted for ADB and fastboot, allow install with system wide support; close command prompt.
Reopen command prompt and re run "fastboot oem device-id" command.
Loggsie
Hi,
Thanks for that. Could you re-upload the file though. Says zip is corrupt.
syztemlord said:
Hi,
Thanks for that. Could you re-upload the file though. Says zip is corrupt.
Click to expand...
Click to collapse
I'll remove the corrupt zip.
Try a download from Google, search for "adb-setup-1.3.zip" it should be the top link for Google Drive.
Loggsie
hi all, sorry if this has beeen posted before but its bugging me as i spent literally 4-5 hours lastnight trying to sort it, i havee rooted 4-5 android phones in the past but im just having no luck with this one
i installed adb / fastboot minimal, enabled what needed to be enabled in developer options on the swift, booted the swift into fastboot mode, then when i run adb on my computer, the first command works 'fastboot oem unlock' but after that its constantly saying 'waiting for devices' whenever i try the next phase of commands ie. fastboot -i 0x2970 oem unlock-go etc it just wont detect the device at all in windows on adb, is there any suggestions anyone could throw out there before i end up sending it back and getting an alternative android phone thats easier to root? the only thing i can think off is its a usb driver issue? but i installed the gloogle usb drivers and it picks up the phone for file transfer etc so im not sure if this is the issue. many thanks!
yodjone1 said:
hi all, sorry if this has beeen posted before but its bugging me as i spent literally 4-5 hours lastnight trying to sort it, i havee rooted 4-5 android phones in the past but im just having no luck with this one
i installed adb / fastboot minimal, enabled what needed to be enabled in developer options on the swift, booted the swift into fastboot mode, then when i run adb on my computer, the first command works 'fastboot oem unlock' but after that its constantly saying 'waiting for devices' whenever i try the next phase of commands ie. fastboot -i 0x2970 oem unlock-go etc it just wont detect the device at all in windows on adb, is there any suggestions anyone could throw out there before i end up sending it back and getting an alternative android phone thats easier to root? the only thing i can think off is its a usb driver issue? but i installed the gloogle usb drivers and it picks up the phone for file transfer etc so im not sure if this is the issue. many thanks!
Click to expand...
Click to collapse
Hi,
I had the same issue. When that happens, do commands without the -i 0x2970 bit. So for example:
fastboot -i 0x2970 erase recovery
becomes:
fastboot erase recovery
Hope this helps
-Jev
I tried this but it still says 'waiting for any device' My initial command worked for fastboot oem unlock, but then I just couldnt do the following commands, and as a result whenever i tried to install a custom recovery / rom it gave me the error along the lines of 'unable to verify....'
edit: when i missed out the -i part, then said its already unlocked. however i still am not able to install supersu or the recovery as it still gives me the error 'signature verification failed'
yodjone1 said:
I tried this but it still says 'waiting for any device' My initial command worked for fastboot oem unlock, but then I just couldnt do the following commands, and as a result whenever i tried to install a custom recovery / rom it gave me the error along the lines of 'unable to verify....'
edit: when i missed out the -i part, then said its already unlocked. however i still am not able to install supersu or the recovery as it still gives me the error 'signature verification failed'
Click to expand...
Click to collapse
Hi,
OK, what recovery are you trying to install? I would recommend TWRP 3.0.2 by Beroid (in the development section) because it's easy to use and it works. Get the image and put it in your adb folder is. Make sure you are in fastboot. Then run commands
- fastboot erase recovery
- fastboot flash recovery (name of file).img
Disconnect the device from your computer. Then remove the battery. Then replace the battery and press VOLUME DOWN and POWER to rebbot in to recovery mode to verify the installation.
You should now be in the recovery. You can flash custom roms and supersu within this new recovery.
Hope this helps
-Jev
my device came with unlocked bootloader, so I tried to flash twrp but every time i type "fastboot flash recovery C:\adb\twrp-3.2.1-3-whyred.img" and hit enter, the device seems to disconnect from pc and there is "press any key to reboot" in fastboot on my phone.
How can I solve this issue?`
Phone gets detected by adb/fastboot tool so its not a driver problem. I tried different cables and usb ports aswell.
Firmware is latest global stable.
Nazukii said:
my device came with unlocked bootloader, so I tried to flash twrp but every time i type "fastboot flash recovery C:\adb\twrp-3.2.1-3-whyred.img" and hit enter, the device seems to disconnect from pc and there is "press any key to reboot" in fastboot on my phone.
How can I solve this issue?`
Phone gets detected by adb/fastboot tool so its not a driver problem. I tried different cables and usb ports aswell.
Firmware is latest global stable.
Click to expand...
Click to collapse
try upgrade your android sdk on your pc
Nazukii said:
my device came with unlocked bootloader, so I tried to flash twrp but every time i type "fastboot flash recovery C:\adb\twrp-3.2.1-3-whyred.img" and hit enter, the device seems to disconnect from pc and there is "press any key to reboot" in fastboot on my phone.
How can I solve this issue?`
Phone gets detected by adb/fastboot tool so its not a driver problem. I tried different cables and usb ports aswell.
Firmware is latest global stable.
Click to expand...
Click to collapse
Well if you already had adb in your pc, rename the twrp file to recovery, you don't have to move the twrp from download folder, open download folder press shift and right click then select open cmd here, on cmd type "adb device" to see if your device connected, then after that type this "fastboot flash recovery recovery.img" press enter than after that type "fastboot boot recovery.img" TEAMWIN logo should appear on your device and then you can unplug your device. Hope this useful
i am trying to flash twrp there is no folder called adb i have installed the 15 second adb and all so i have got this minimal adb flashboot and i tried with that and got this ---- FAILED (remote: Flashing is not allowed in Lock State). i have granted all usb and oem unlocking. please help with this
Phone shows unlocked during the boot?
I had the same Problem,after a Factory Reset works for me.
I am on Miglobe-Rom Miui10 8.6.28.
Minimal ADB is enough.
Or use this from Attachment.
Unpack with Win.zip and copy Twrp in this Folder.
Conect the Phone with your Pc ,boot into Bootloader and click "cmd-here.exe"
Use this Command
fastboot flash recovery twrp-3.2.1-3-whyred.img
@Nazukii - Quick question - any chance you could try running GameBench on your device, and see if our background service dies when the device is disconnected from the PC? I don't have a Note 5 Pro to test, and I've got some user complaints. Any assistance would be awesome!
J
gamebenchjake said:
@Nazukii - Quick question - any chance you could try running GameBench on your device, and see if our background service dies when the device is disconnected from the PC? I don't have a Note 5 Pro to test, and I've got some user complaints. Any assistance would be awesome!
J
Click to expand...
Click to collapse
Have you fixed your app to run on Magisk-SU ?
otonieru said:
Have you fixed your app to run on Magisk-SU ?
Click to expand...
Click to collapse
Hey Otonieru,
Not yet, but I've got one of the engineers working on it - hopefully it'll be up in the next 30 days or so
Same problem here after updating my gcam was not working was enabling hall again but it is not booting into twrp
Redmi Note 5 pro
So my Bootloader is locked,
My phone stuck in MI recovery idk how.
I cant install MIUI via fastboot. Im stuck ..
Can anyone please help me here not sure how to proceed further.
If you have made sure that you have all the drivers installed and still have not solved, you need to use an Intel-based PC / notebook and use a usb 2.0.
”Well if you already had adb in your pc, rename the twrp file to recovery, you don't have to move the twrp from download folder, open download folder press shift and right click then select open cmd here, on cmd type "adb device" to see if your device connected, then after that type this "fastboot flash recovery recovery.img" press enter than after that type "fastboot boot recovery.img" TEAMWIN logo should appear on your device and then you can unplug your device. Hope this useful”
i did that but it is showing failed（too many links）and "press any key to reboot" showing on my phone's fastboot screen
Fastboot boot recovery.img flashing problem on Redmi note 5 pro
My bootloader is unlocked and my oem as well as usb deb is on. After i connect my phone in fastboot mode to my pc. The cmd shows fastboot devices but when it comes to fastboot boot recovery.img flashing device get disconnected. Plzzzzzz let me know a solution for this. A solution for this will be highly appreciateable.
Hi,
After several ROM flashings, my A2 Lite is in bootloop mode.
To try to recover my phone, I did followings.
Installed adb, fastboot, miflash.
Executed 'fastboot oem edl' - successful
Miflash of 'daisy_global_images_V9.6.10.0.ODLMIFF_8.1' gives 'SUCCESS' message, however still in bootloop mode.
I opened the back cover and successfully put the phone in edl mode.
Miflash again with the same ROM folder with 'SUCCESS' message , however still in bootloop mode
When I tried 'fastboot flashing unlock' or 'fastboot flashing unlock_critical' command, it produced - 'Failed, remote unknown command' message.
When I try ' fastboot boot twrp_for_daisy.img' , successfully executed . however the phone can not boot in recovery mode.
I would appreciate very much if somebody provides me any help.
Best regards,
Moricelo said:
Hi,
After several ROM flashings, my A2 Lite is in bootloop mode.
To try to recover my phone, I did followings.
Installed adb, fastboot, miflash.
Executed 'fastboot oem edl' - successful
Miflash of 'daisy_global_images_V9.6.10.0.ODLMIFF_8.1' gives 'SUCCESS' message, however still in bootloop mode.
I opened the back cover and successfully put the phone in edl mode.
Miflash again with the same ROM folder with 'SUCCESS' message , however still in bootloop mode
When I tried 'fastboot flashing unlock' or 'fastboot flashing unlock_critical' command, it produced - 'Failed, remote unknown command' message.
When I try ' fastboot boot twrp_for_daisy.img' , successfully executed . however the phone can not boot in recovery mode.
I would appreciate very much if somebody provides me any help.
Best regards,
Click to expand...
Click to collapse
Try changing boot slots via fastboot command
Hi, I want to move to a custom ROM on my A2 Lite. But before anything else, I need to backup my phone.
1st step : TWRP recovery.
On the PC, ADB driver is installed. Phone powered and connected, I have no problem to send ADB command to phone. "adb reboot bootloader" for example.
But once the phone is in fastboot (logo on screen), it is not recognized by PC (no driver) and I can"t send Fastboot command.
Any hint ?
Thanks.
Ok, I found a solution.
Downloading Google USB Driver but installation procedure is wrong, I should FORCE it and manually assigne the driver "Android Device / Bootloader" to be able to connect in Fastboot mode.
fastboot oem unlock
-> Reboot with the warning message but wipe all data. It's the only I found to unlock the bootloader :/
fastboot oem edl
-> Not the solution to flash the new ROM
fastboot boot twrp*.img
-> Way better to get the recovery flashed