Related
Tried fixing my oppo find 7
Did all those Fastboot wipe .
Fastboot flash recovery and flash LOGO and stuffs
but im still stuck on logo ... WHUT
kevzwenhao said:
Tried fixing my oppo find 7
Did all those Fastboot wipe .
Fastboot flash recovery and flash LOGO and stuffs
but im still stuck on logo ... WHUT
Click to expand...
Click to collapse
Did you unlock bootloader?
1. Connect the device to the computer through USB.
2. From a terminal on a computer, type the following to boot the device into fastboot mode (or restart pressing power+vol up):
Code:
adb reboot bootloader
3. Once the device is in fastboot mode, verify your PC sees the device by typing:
Code:
fastboot devices
4. From the same terminal, type the following command to unlock the bootloader:
Code:
fastboot oem unlock
If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked.
5. Then you can flash the recovery what you want. In fastboot mode, type in terminal:
Code:
fastboot devices
6. And flash the recovery. Type:
Code:
fastboot flash recovery your_recovery_image.img
Good luck
roi_xordo said:
Did you unlock bootloader?
1. Connect the device to the computer through USB.
2. From a terminal on a computer, type the following to boot the device into fastboot mode (or restart pressing power+vol up):
Code:
adb reboot bootloader
3. Once the device is in fastboot mode, verify your PC sees the device by typing:
Code:
fastboot devices
4. From the same terminal, type the following command to unlock the bootloader:
Code:
fastboot oem unlock
If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked.
5. Then you can flash the recovery what you want. In fastboot mode, type in terminal:
Code:
fastboot devices
6. And flash the recovery. Type:
Code:
fastboot flash recovery your_recovery_image.img
Good luck
Click to expand...
Click to collapse
Hi, is it wrong to wipe the system partition before flashing a custom rom? Coming from stock ColorOS, I've wiped all dalvik cache, cache, system, and data, then flash a custom rom but it ended up getting endless bootanimation unable to boot into the custom rom.
I did unlock the bootloader with the adb code, flashing a temporary recovery was a success but endless bootanimation happened after flashing a custom rom. The custom rom was successfully installed according to TWRP's log.
Pls advice, thanks in advanced
P.s: I was referring to my friend's device X9076
Hi, i tried in the past some roms than not works, phone stuck in boot animation. The roms wich works for me and my x9076 with r63419 are:
Omnirom (6 or 5) THE BEST
Project Spectrum
Cyanogen 13 (modified version for new panel: http://community.oppo.com/en/forum.php?mod=viewthread&tid=44907&extra=)
Miui
If you install CM13, you need to flash unified partition script for CM13 (you can find it in the same post from the forum Oppo Community)
For the other roms i dont need to flash anything else than rom and gapps.
Now i give a chance to CM13, but i think that i will get back to Omni if developers dont fix the mobile radio issue.
Cheers
Can anyone guide me please, 1st time i bought MTK phone Oppo F7, its update automatically but suddenly dead like stuck on logo and restarting again and again, i didnt ever flash MTK phone, neither i have any android tool like MRT dongle or any other flash USB or Box... Kindly guide me step by step how to flash with which tool only USB cable and PC... Thanks in advance
Hy
I had an unlocked bootloader phone. Yesterday I flashed the new Android 6, Europe version from the Huawei blog forum, no beta, on my Huawei GX8. I used the method, dload on SD card, Phone off an the press Volume down+volume up+Power button.The flashing was normaly.
Now the phone starts normaly but I can´t start fastboot. When the phone is off and i press Vol down + Power the phone start the android system and the Huawei logo is coming not the fastboot Modus. I can see my phone and the order under Windows but i can not control my phone with the fastboot command. (example: fastboot device. the answere ist searching devices, but it comes no resolution) I loaded the last version of Fastboot, but the problem is the same.
Please can you help me. What can i do? Many thanks for your help!
Should be connect the charger cable to the phone.
charger or computer
excuse me for bad english
No i use a data cable, debugging is on. I can copy data from my phone to PC or from PC to phone, but fastboot does not found my device.
bertl237 said:
No i use a data cable, debugging is on. I can copy data from my phone to PC or from PC to phone, but fastboot does not found my device.
Click to expand...
Click to collapse
And when you use adb to reboot to bootloader, what happen? Do you have "Minimal adb and fastboot tool" installed?
krispin said:
And when you use adb to reboot to bootloader, what happen? Do you have "Minimal adb and fastboot tool" installed?
Click to expand...
Click to collapse
Sorry for my question, what´s the differents about adb and fastboot tool? I have install the last version of minimal adb and the fastboot tool, also the Windows driver for the phone. Debugging is on. I try to connect my phone about the fastboot terminal. When i try to set the phone into the bootloader mod with the fastboot terminal and the equivalent command, fastboot say´s "searching phone". My phone does not react.
bertl237 said:
Sorry for my question, what´s the differents about adb and fastboot tool? I have install the last version of minimal adb and the fastboot tool, also the Windows driver for the phone. Debugging is on. I try to connect my phone about the fastboot terminal. When i try to set the phone into the bootloader mod with the fastboot terminal and the equivalent command, fastboot say´s "searching phone". My phone does not react.
Click to expand...
Click to collapse
So, you connect your phone, open minimal adb and fastboot too, run "adb devices", you see device id? If yes, run "adb reboot bootloader" . Phone shoult reboot to fastboot mode. Then run "fastboot devices" to see if it is connected properely.
i did it, like you described, but i see not my device id. Only the note "seach device"
Is it possible that TWRP is defect on my device? Is TWRP necessary for fastboot or only for root?
bertl237 said:
i did it, like you described, but i see not my device id. Only the note "seach device"
Is it possible that TWRP is defect on my device? Is TWRP necessary for fastboot or only for root?
Click to expand...
Click to collapse
No, you should be able to use adb and fastboot with stock recovery.
After first adb command you shoult approve authorization on your phone.
Here is screenshot from minimal adb...
Phone must be in MTP mode.
And here is phone in fastboot
Many thanks for your help, now I m in my bootloader.
2 problems i had.
1. My daemon was not started correctly, i have not seen my device.
2. I used the wrong command. I started with fastboot, not with the command adb device. I tap „fastboot reboot-bootloader“,but the correct command is “adb reboot-bootlader“
Now i have seen my phone is unlocked, i hope i can root my android 6.
bertl237 said:
Many thanks for your help, now I m in my bootloader.
2 problems i had.
1. My daemon was not started correctly, i have not seen my device.
2. I used the wrong command. I started with fastboot, not with the command adb device. I tap „fastboot reboot-bootloader“,but the correct command is “adb reboot-bootlader“
Now i have seen my phone is unlocked, i hope i can root my android 6.
Click to expand...
Click to collapse
Just reboot to fastboot and flash surdu-petru version of TWRP recovery 3.0.2 with command "fastboot flash recovery xxxxx.img". And than reboot to recovery and flash supersu zip.
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.
So, a few months ago I rooted my device with twrp and then installed magisk manager... A few days later the manager stopped working and I got tired of not being able do do nothing so I tried to unroot. I used mi flash to flash the daisy rom and it didn't work so I tried to load to the twrp app and flash through there. Didn't work either. From then on every time I boot the device it shows the message "the system has been destroyed" and Bc of that I searched for solutions. I kinda found one. I boot to fastboot mode and with the platform tools I write on the command line ". /fastboot devices" and then it shows my device. After I write ". /fastboot boot continue" and it starts booting the device and it has worked for like 2 months but 2 days ago I had to reboot my device Bc it started to freeze but when I load to fastboot mode and plug it to the pc it show a prompt saying "the device is not recognized" and the device reboots to the message "system has been destroyed". Pls help, I've searched everywhere and didn't find any solution
Are you have your bootloader unlocked? I guess no, the most "easy" solution for your problem is test point , never fail, you need to download Qualcomm drivers (search in Google) open your device connect your device, your phone need to be recognized like 9008 in manager drivers of your PC then flash stock room in mi flash (flash all option) my recommendation is flash 10.0.13.0 or 10.0.18 version of stock rom, good luck.
Os_Herdz said:
Are you have your bootloader unlocked? I guess no, the most "easy" solution for your problem is test point , never fail, you need to download Qualcomm drivers (search in Google) open your device connect your device, your phone need to be recognized like 9008 in manager drivers of your PC then flash stock room in mi flash (flash all option) my recommendation is flash 10.0.13.0 or 10.0.18 version of stock rom, good luck.
Click to expand...
Click to collapse
Yes, my bootloader is unlocked, and is not recognized on the miflash tool.
I cant't even boot the phone to edl mode
0flip3 said:
Yes, my bootloader is unlocked, and is not recognized on the miflash tool.
I cant't even boot the phone to edl mode
Click to expand...
Click to collapse
you are trying to get to edl mode by typing command "fastboot oem edl" when phone is in fastboot?
I newly installed PE ( based A12 ) with orangefox recovery, but now whenever I go to the recovery it never gets past the orangefox logo. My device was not rooted, and from what I've read it looks like this was caused because the recovery was not " FBE ". Then I tried flashing TWRP, but the device won't stay on fastboot mode, with or without the USB connected, I would put it on fastboot (tried from both cmd and volume down + power button) and it will stay on fastboot for a few seconds (about 30 seconds) then shut down.
I tried different ports and reinstalled platform tools and appropriate drivers, those did not fix the problem, so I thought this might be because of some app that I might have installed, so I reset the phone, and now it does not have a ROM. The device is still not booting into recovery or staying in fastboot.
Some other info on the device-
- I had an unlocked bootloader before doing this and also had no problems with the recovery.
- I also did a clean install for the ROM.
- The device had no problems in getting detected on the PC. I also had USB debugging enabled.
Update: I've fixed it.
how did you fix it?
i'm having same problem since yesterday.
please help me fix this issue
So firstly, the device not being recognised when I typed ' adb devices ' and shutting down after a few seconds of being on fastboot with usb attached.
To fix this, I had to go to ' device manager ' on my pc and then connect the phone via USB ( in my case the phone was only in fastboot for a few seconds before it shut down and I also did not have any rom installed, and could not go into recovery ), then in device manager, the device name would be shown ( under portable devices ), right click > update driver > browse for drivers your computer.
doing this fixed the problem where the device was not staying in fastboot.
Then I had to fix where the device won't load into recovery and will be stuck on the start screen forever ( I had orange fox recovery installed )
To fix this, I went to fastboot on my device and then I had to type the following command: fastboot -w ( This command erases everything from the device )
After doing these, everything was pretty much done, all I had to do next was go to fastboot, install a recovery and flash a rom.
Dynamo01 said:
So firstly, the device not being recognised when I typed ' adb devices ' and shutting down after a few seconds of being on fastboot with usb attached.
To fix this, I had to go to ' device manager ' on my pc and then connect the phone via USB ( in my case the phone was only in fastboot for a few seconds before it shut down and I also did not have any rom installed, and could not go into recovery ), then in device manager, the device name would be shown ( under portable devices ), right click > update driver > browse for drivers your computer.
doing this fixed the problem where the device was not staying in fastboot.
Then I had to fix where the device won't load into recovery and will be stuck on the start screen forever ( I had orange fox recovery installed )
To fix this, I went to fastboot on my device and then I had to type the following command: fastboot -w ( This command erases everything from the device )
After doing these, everything was pretty much done, all I had to do next was go to fastboot, install a recovery and flash a rom.
Click to expand...
Click to collapse
thanks bro. fastboot -w fixed everything