I tried flashing PixelBlaster on my realme 3 pro with no extra reseach (my fault) using TWRP. After flashing, i tried to reboot but it bootloops on realme logo (android). Fast boot is working, unlocked bootloader but turned off USB Debugging i guess because it does not show in adb. Tried other phone and turned on USB debugging and the device is listed. So now I have a realme 3 pro with NO RECOVERY, NO ROM, UNLOCKED BOOTLOADER, USB DEBUGGING OFF. When trying to boot to recovery it boots back to fastboot. When trying to boot normally, shows realme android logo then restarts.
quasar28 said:
I tried flashing PixelBlaster on my realme 3 pro with no extra reseach (my fault) using TWRP. After flashing, i tried to reboot but it bootloops on realme logo (android). Fast boot is working, unlocked bootloader but turned off USB Debugging i guess because it does not show in adb. Tried other phone and turned on USB debugging and the device is listed. So now I have a realme 3 pro with NO RECOVERY, NO ROM, UNLOCKED BOOTLOADER, USB DEBUGGING OFF. When trying to boot to recovery it boots back to fastboot. When trying to boot normally, shows realme android logo then restarts.
Click to expand...
Click to collapse
Also tried flashing twrp using adb but device not showing when used command ./adb devices in powershell
Related
I had my Oneplus One running Lineage OS and TWRP Recovery. I tried installing Oxygen OS and the device seemed to work but then the screen became all black.
I restarted the device and its been stuck in Bootloop for over an hour.
I've tried rebooting it in recovery mode and fastboot but all that does is restarts the device.
I've also tried using adb but it doesnt recognize the device, I think I have all the drivers installed. When I plug the device to the PC it sounds as when you connect something, but its recognized as Android Device. There is nothing on Computer, no storage no nothing.
The device isn't rooted, but the bootloader was unlocked, as I had to flash TWRP to install Lineage OS.
I need some hElp plz
hi..
Greetings to every Android Magicians out there...!
Device:- MiA1 (Never rooted)
1.USB debugging was enabled and OEM is not enabled.
2.Hence Boot loader is Locked.
3. Adb drivers installed in my laptop.
4.Windows driver signature are disabled.
5. Xaiomi flash tool and drivers installed.
6. Qualcom HS-USB Diagnostics 900E installed.
7. Can be enter in fastboot mode and edl mode as well.
The problem:- My MiA1 was never rooted (USB debugging was enabled and OEM is not enabled.).
All apps are force stopped suddenly while using the phone so tried to reboot my devices,
and there it begins.. it stuck at boot logo.
Things i have tried:
1. Fastboot Mode:
Since the boot loader is locked i cant flash Any ROM through fastboot so i tried to enter in EDL mode through CMD.,But failed.
so i just open the back panel & however entered in EDL mode by Testpoint.
(and i've tried in fastboot through cmd { fastbooot oem unlock } it says successful but when i check the status through
{fastboot oem devices-info} but the bootloader is still locked).
2. Test Point Method:
I tried to flash MiA1 official global version ROM's (7,8,9 as well) through Xaiomi Flash tool(2015,2016,2017 versions) by test point Methods.
i have encountered the problems like AKC don't match and Cant receive Hello packets.
However i have got solved this Prolems by using Beta version of Xaiomi Flash tool.
3. When i flash (tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794) flashing was successful but devices still stuck at
Androidone logo.
Tried to flash other versions of ROM (tissot_images_V10.0.4.0.PDHMIXM_9.0) flashing was successful but devices still stuck at
Androidone logo.
By the way i have tried it using different type C cables and different ports (COM5, COM20,COM40 etc) and and different laptop as well but No luck.
i hope you guys do some Magic and help me out.
Thank you so Much for reading this thread.
Hello, I have doogee s40 phone stuck in bootloop. I do not have unlocked bootloader or enabled usb debugging. I can flash custom rom via SP Flash tools but it does not help.
When I choose recovery mode it just restarts after a while and does not go to the recovery.
I can choose fastboot mode, but since I do not have usb debugging enabled I cannot do anything.
Is there something I can do?
I have a tecno wx4 phone and I tried to install the TWRP recovery thought adb, and it all went how it should have. But when I tried to boot it I got the this screen:
"Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds"
And I've googled about it but all solutions I found required the phone to actually boot into the OS or the recovery mode, and this phone just keeps on rebooting to this screen every 5 seconds, and it does that even when I try to boot into recovery mode, just sends me back to that screen, and the adb terminal can't detect the phone on this state.
If anyone has had a problem like this and found a solution, please help me because I ran out of ideas...
PS: I did everything I needed prior to this, enabled adb debugging, unlocked OEM through the OS first, but once I unlocked through fastboot I kept having that screen.
Hello all,
I am stuck in this problem. Would appreciate any help.
Working in LINUX ubuntu 18.
Got a MI pad 1 with locked bootloader.
flashed TWRP recovery using fastboot. Booted into TWRP successfully.
Flashed the files from this
https://www.techeia.com/2018/10/best-custom-rom-for-mi-pad-1-2018.html
Everything flashed successfully.
Rebooted only to be stuck into MI logo screen. Bootloop probably because of locked bootloader.
Hence, I decided to wipe the bootloader itself
got the hint from here https://forum.xda-developers.com/mi-pad/how-to/fix-fastboot-bootloop-fix-xiaomi-mi-pad-t4008653
but I didn,t wiped recovery. but erased everything else. Then powered off to boot into previously installed TWRP recovery.
From there, I am trying to boot into fastboot or TWRP but the screen is showing blank. I am using the key pattern for fastboot or recovery and trying to detect the device into any mode through ubuntu terminal using
sudo fastboot devices and
adb devices
but its not detecting the device there also. USB debugging was enabled already.
Any clues for how can I boot into fastboot or TWRP from this.
Regards
Hiteshkartik
@hiteshkartik
A device with erased boot-loader never can work: you simly get a black screen. You no longer can communicate with it - neither via ADB nor via Fastboot.
Can I have a way around ?? I mean installing bootloader or somehow booting into fastboot or TWRP directly with any toolkit or terminal.