[Q] Bootloop, Whitescreen, Cannot Enter Recovery - Android Q&A, Help & Troubleshooting

All knowing and magical XDA DEVS....
My phone is in bootloop and ADB commands are not recognized.
The screen is going white and blurry, when I try to enter recovery mode, it doesn't work.
If I don't have access to recovery... I need to get the device to be recognized by ADB...
The computer makes the sound of USB connect when it reboots... so I have some hope...
but I don't know what to do if the device does not respond to ADB commands.
I installed the Project Doge Zip. Wiped Cache after install as instructed.
When I downloaded the ROM, it said it was compatible with Mediatek 65xxx chipsets... I guess not? :crying:
Device: Blu Studio 5.5
Rooted: Yes
ROM Installed before bootloop: Project Doge 1.4
Recovery: CWM-based
Backup of stock OS: Yes
ADB: device not found
I have not bricked any other device and I'm not about to start now. Any help is very much appreciated.
THANK YOU!

Related

[Q] Help Phone stuck in bootloader screen ZTE

I was upgrading the current Stock rom on my ZTE Nubia Z5s Mini, I went through the recovery mode to load the new rom and got a message saying that the rom installed correctly, I rebooted the device and now its stuck at the MIUI logo or if I try to load the recovery mode I get the Nubia logo just to load back to the miui logo again. I got the rom from the MIUI site its v5.
I've left the phone for over an hour hoping it was just loading up but no change, the phone heats up and even has a charger screen when plugged in.
Anyway to get back into the recovery mode to load the original rom again or any other way of fixing this? help :crying:
I've no idea how to help you with this but I'm bumping the thread because I know how you feel.
Sent from my HUAWEI Y536A1
I'm trying to flush the rom by using adb but with an issue, even thou my device is recognized as Nubia Z5s Mini in device manager it still gives a driver error "these have been installed" and in cmd adb it does not see the device.
Update : Got drivers for install from Clockwordmod website but it will only accept the drivers if I set the phone as a modem in device manager when installing them, still not recognized by adb using CMD.
Solved driver issue and qusb_download issue, ADB drivers are done through all drives in device manager pointing to the Google USB drivers and select adb interface then run CMD from within the Google SDK program folder in platform-tools to read the device.
Now using emmc but need to generate EMMCBLD.HEX & 7x30_msimage.mbn if anyone can help, I can enter adb using recovery mode but blocked from making changes in fastboot mode, currently in download mode which can see a drive H but need the two files to proceed any further.

Micromax Canvas Magnus stuck at boot logo

Hi,
My 2 year old Micromax Canvas Magnus A117 was working fine till I installed TWRP recovery yesterday. I installed TWRP recovery img file for my phone. The version was twrp-2.8.6.0-a117.img. It downloaded and asked me to verify the location of dev/recovery . I verified it and started the flashing process. At first it took a long ting but said flashing unsuccessful. It asked me to try a second time. I did it and it was successful. TWRP now told me to boot into recovery mode. I pressed the green 'Yes' button but nothing happened. (In the mean time I uninstalled some apps as TWRP ate about 350mb of internal storage during the flashing process.). Then I tried quick boot(reboot) app to boot into recovery. But then the problem started It switched of my phone and then booted but it got stuck at the micromax logo. I pulled out the battery to switch it off, put it in and restarted the phone using the power button. But it got stuck again at the boot micromax logo. I tried booting it in recovery mode (power+volume up) but it flashed off the screen and again booted but not in recovery mode.It got stuck again and agian. The recovery mode seems not to work.
Inthe meantime I connected my phone with adb. adb seems to recognize my device. But when I tried to push flash_image file to my device to flash it with twrp recovery via adb it says "failed to copy d:\flash_image' to /sdcard/flash_image' : Permission denied.
I used this command "adb push d:\flash_image /sdcard/" without quotes. I stored the flash_image file and twrp recovery and stock recovery imgs in the d drive. I also tried fastboot with commands " fastboot flash recovery d:\recovery.img" (I renamed the twrp-2.8.6.0-a117.img to recovery.img). This shows <waiting for any device>and nothing else. Also "adb remount" command says "operation not permitted".
I am at a loss to what to do now.. My recovery.img seems to be not working anymore not the stock neither twrp.
What are my options now? Is my device bricked? I really need a help here.
P.S- I rooted my phone using Framaroot 1.9.3 and it rooted fine installing supersu. And my android version is 4.2.1
Need sometime to get info on this, plz be patient :good:
Alright.
Is there any forum dedicated to my hone in xda?
rijuroy said:
Is there any forum dedicated to my hone in xda?
Click to expand...
Click to collapse
Try posting this post in XDA ASSIST
http://forum.xda-developers.com/general/xda-assist

Help in flashing recovery on gionee M3

Wassup aliens!
So I got this gionee M3 and I rooted it with iRoot and tried to flash recovery in nearly every way possible....... I tried using Flashify, Rashr, TWRP manager..... Nothing worked.
1) On Flashify: I kept selecting Flash recovery but the message I get every time is "Error copying the file, please send me the log file".
2) On Rashr and TWRP Manager: They both say they flashed the file but when I boot into recovery all I see is gray screen with a gionee logo. I also lost my stock recovery this way.
3) On PC: My PC never detects my phone as an adb or VCom device........To check for VCom I tried SP Flash Tools..... didn't detects the device. For Adb I tried Adb devices in command prompt but the devices list is empty.
Some info:
I have USB debug mode enabled.
I have stock 5.0.2 android rom with no recovery just factory safe mode through which I can perform some tasks.
If you need any pics or any info just tell me in the comments.
I hope you guys help me.... Been trying for the last 6 days.
HELP ASAP SOS
Love,
Justin Biebar
Tarun0101 said:
Wassup aliens!
So I got this gionee M3 and I rooted it with iRoot and tried to flash recovery in nearly every way possible....... I tried using Flashify, Rashr, TWRP manager..... Nothing worked.
1) On Flashify: I kept selecting Flash recovery but the message I get every time is "Error copying the file, please send me the log file".
2) On Rashr and TWRP Manager: They both say they flashed the file but when I boot into recovery all I see is gray screen with a gionee logo. I also lost my stock recovery this way.
3) On PC: My PC never detects my phone as an adb or VCom device........To check for VCom I tried SP Flash Tools..... didn't detects the device. For Adb I tried Adb devices in command prompt but the devices list is empty.
Some info:
I have USB debug mode enabled.
I have stock 5.0.2 android rom with no recovery just factory safe mode through which I can perform some tasks.
If you need any pics or any info just tell me in the comments.
I hope you guys help me.... Been trying for the last 6 days.
HELP ASAP SOS
Love,
Justin Biebar
Click to expand...
Click to collapse
Hey i have the same problem. Can you suggest me something regarding this.
A very big question
Hello! I have an argentine copy of the M3, called Hyundai Ultra Energy, same processor, same storage, camera quality, all in the same place. My question is how do I install a custom rom and how do I flash the recovery at first. I use adb commands, but I know that I have to do it with spflash. How is the process? I download the rom, charge the scatter and tilt only in recovery? Would be dangerous? Is more safe to root with King Root?

Recovery Loop with broken recovery

Hello! I am Madhav here. I am struggling with my Samsung GALAXY Grand 2 G7102. I am stuck in the recovery mode and I cannot access the bootloader or the OS. The recovery mode boots up every time and shows a blank screen. I am devoid of the recovery function too. But my device shows up in adb as "List of devices attached----$PHONE_SEREIAL recovery." I cannot flash the stock firmware using adb sideload as it is failing all the time, with whatsoever error. Please guide me how can I flash the firmware and the recovery in the phone so that I can use it again. I think that I have flashed an incompatible recovery over the OS.
Please help me. Thanks in advance!
Any further information will be readily provided by me.

Stuck in bootloop and cannot get into recovery

Hi,
I've got a problem where my phone is stuck in bootloop and I cannot go into recovery mode. All I can get into is fastboot mode. I know there's a way to get into recovery from fastboot mode using ADB but I do not know what to do or what steps to follow as I really don't know much about modding phones apart from flashing a ROM that I wan't to use via recovery (which I assume even a ten year old would be able to do effortlessly after seeing it being done once or twice).
I am using the global 4/64 Redmi Note 4 running the latest version of Android Open Source Illusion Project.
Any help would be appreciated. Thank you.
laneofmagic said:
Hi,
I've got a problem where my phone is stuck in bootloop and I cannot go into recovery mode. All I can get into is fastboot mode. I know there's a way to get into recovery from fastboot mode using ADB but I do not know what to do or what steps to follow as I really don't know much about modding phones apart from flashing a ROM that I wan't to use via recovery (which I assume even a ten year old would be able to do effortlessly after seeing it being done once or twice).
I am using the global 4/64 Redmi Note 4 running the latest version of Android Open Source Illusion Project.
Any help would be appreciated. Thank you.
Click to expand...
Click to collapse
Did you try combo key? Holding Power and Volume+ buttons?
If this doesn't works, you have to set up ADB bridge on your PC. Here is the guide: https://www.xda-developers.com/install-adb-windows-macos-linux/
When you do that, type the command via ADB while being in fastboot mode:
fastboot reboot recovery
This should take you into the recovery mode.
Any help please Im stuck in a boot loop and recovery and fastboot are inaccessible, so i cant send any commands? im forking on Mac OS but even ive installed a virtual PC to try some of the countless programs but no seams to work since the phone is not recognized.

Categories

Resources