Dear Android Geek,
My Verizon ellipsis 8 qtaqz3 tablet is bricked, and I can't find the original or new Firmware/ROM or anything to flash. It does not have ADB debugging enabled either.
Please share the original Firmware, if you have, and please kindly help solve the problem. Thank you in advance.
I did the factory reboot and I wiped the cache, but it still boots only to a black screen after the ellipsis screen.
and I don't know how to enable USB debugging.
USB-debugging ( AKA ADB ) can only get enabled when phone works properly, means before it becomes bricked for whatever reason.
So you even can't reflash phone's Stock ROM via ADB Sideload method.
You have to restore phone's Stock ROM by means of a suitable Flash Tool.
Related
Hello Friends,
Now i m going to tell you everything which everyone should keep in mind to avoid bricking our beloved Moto G.
I have unlocked my bootloader to enjoy full root features in my mobile.So rooted it on lollipop stock rom.
And found that some old Gameloft HD games like 9MM,tintin etc shows incompatible handset.So tried to change build.prop file in /system folder to convert my mobile name to Samsung Galaxy S2 to install the incompatible games and then messed up everything and my phone won't restart but however bootloader, recovery is working.
In this step I should have tried to restore my original build.prop file by using adb commands or fastboot commands.But I didn't knew this and tried factory reset in recovery menu which didn't help and adb commands failed to work.
Then I searched online and used fastboot commands to flash to 4.4.3 Stock Rom and it worked fine.
I should have left my mobile in this Rom.
But official 4.4.4 system OTA file didn't let me do that which in turn made my mind to download and install 4.4,4 OTA
and here goes my problem,Downloaded successfully and tried to intsall but it didn't
My phone won't boot,no recovery,no bootloader,no adb ,atleast no fastboot commands
except qhsusb_bulk shown in devices and sometimes usb input device or vmware usb device with white led light blinking
Anyone faced similar problem and got solution .Please Help
Reserved for any solutions
This could help
Hi!
I'm on the same problem but with a Moto X 2014. I've found this page (shown below). I tried the qboot program but I've got a fail while starting fastboot. I was thinking that the problem might have been windows 10. Now I'm back to windows 7 and I'm trying to get the qhsusb_bulk device detection.
allfreeperks.in/2015/01/unbrick-how-to-repair-and-recover-from_9.html
by the way, have you found any solution? I'm still trying to get the qhsusb_bulk device recognized by windows 7 and I don't know why I can't get there.
androidsatti said:
Hello Friends,
Now i m going to tell you everything which everyone should keep in mind to avoid bricking our beloved Moto G.
I have unlocked my bootloader to enjoy full root features in my mobile.So rooted it on lollipop stock rom.
And found that some old Gameloft HD games like 9MM,tintin etc shows incompatible handset.So tried to change build.prop file in /system folder to convert my mobile name to Samsung Galaxy S2 to install the incompatible games and then messed up everything and my phone won't restart but however bootloader, recovery is working.
In this step I should have tried to restore my original build.prop file by using adb commands or fastboot commands.But I didn't knew this and tried factory reset in recovery menu which didn't help and adb commands failed to work.
Then I searched online and used fastboot commands to flash to 4.4.3 Stock Rom and it worked fine.
I should have left my mobile in this Rom.
But official 4.4.4 system OTA file didn't let me do that which in turn made my mind to download and install 4.4,4 OTA
and here goes my problem,Downloaded successfully and tried to intsall but it didn't
My phone won't boot,no recovery,no bootloader,no adb ,atleast no fastboot commands
except qhsusb_bulk shown in devices and sometimes usb input device or vmware usb device with white led light blinking
Anyone faced similar problem and got solution .Please Help
Click to expand...
Click to collapse
langelog said:
Hi!
I'm on the same problem but with a Moto X 2014. I've found this page (shown below). I tried the qboot program but I've got a fail while starting fastboot. I was thinking that the problem might have been windows 10. Now I'm back to windows 7 and I'm trying to get the qhsusb_bulk device detection.
allfreeperks.in/2015/01/unbrick-how-to-repair-and-recover-from_9.html
by the way, have you found any solution? I'm still trying to get the qhsusb_bulk device recognized by windows 7 and I don't know why I can't get there.
Click to expand...
Click to collapse
Nope
No solution till now
well i scrwred my phone , did a factory reset, wiped cache, and messing about like an idiot did some messing wiht the mount /unmounting. obviosuly deleted some important system files. now its stuck in bootloop. it just stays on the logo. MY phone is huawei g620s L01 was running kitkat 4.4.4. i have cwm recovery on it. i have unlocked the bootloader. i have installed all the drivers for my device on windows. i can get into fastboot or recovery. i have downloaded a stock rom but when i type command adb sideload "nameofrom620s.zip" it starts but finishes saying install aborted/??? no explanation ...so i am really stuck, any ideas. i know it connects becasue when i type fastboot dvices, it lists a device number. when i type adb devices a few lines come up one of which is the device number and says recovery. Please can u help? is there some other software i need like a flashing tool or odin(ihave never used odin and know nothingn= about it). I should also mention that although it connects via adb/fastboot, when i check devices in windows, its not listed!? PLEASE please can someone show me the way forward? thanks.
Hi, thank you for using XDA assist. I've found this which may help you get your phone working again, http://forum.xda-developers.com/android/help/restoring-broken-huawei-smartphones-t3047748
No response. Thread closed.
HI,
First time posting, but read a lot of great info on here in the past. just made a bit of a stupid mistake tho... I'd rooted my XT1039, and then flashed the custom recovery back as well as the stock 4.4.4 eu retail gb. I was getting the 5.1 OTA update, but the install was failing. In my eagerness, I downloaded the GPe Lollipop 5.1 update from here - http://forum.xda-developers.com/moto-g/general/gpe-lollipop-5-1-1click-installer-t3075522 - and tried to flash that, missing that it is for a different phone. Now I'm stuck at the bootloader menu, with the error "fall-through from normal boot mode." Any attempt to select normal powerup, recovery, etc results in a black screen with "Google" written on it and an unlocked padlock symbol.
I was going to try and flash the stock 4.4.4 image I had, but when connecting the phone to the PC via USB, fastboot isn't recognising it as attached, even though the phone detects that USB is connected...
Any help would be seriously and massively appreciated!!
Thanks in advance!
Hey man, I have a similar problem as you. Maybe I can give you a little hand, but its better if somebody who understan everything well give you the hand, becouse I'm a "starter" with this of Moto G.
Your device is charged? With my XT1040, the bootloader didnt connect with the PC via USB if the batery was low. Other thing, which version of bootloader do you have?
Thanks! Yes, the phone is charged! Not sure what version of the bootloader it is...
Start fastboot mode with "Pwr" + "VolDwn" and in the top of the screen says:
Code:
AP Fastboot Flash Mode (S)
41.xx [COLOR="Red"]<--- version of bootloader[/COLOR]
It's 41.19...
Try flashing the CWM Recovery again ClockWorkMod Recovery by Somcom3X with fastboot.
Then mount USB storage and upload an Lollipop's backup/system for your XT1039.
Finally, try to install the Lollipop's zip. If the instalation finish succesfull, wipe data and cache. Then try to start your device normaly (first option of CWM (restart))
Anyway, yesterday I made a thread explaining what happened to me with my XT1040 and how I solve it. Read it if you have time, maybe helps with your problem XT1040 - Reviving bad Lollipop flash/downgrade/bootloader 41.18
Note: I think that XT1039 and XT1040, both can work with the same Lollipop but I'm not sure, ask arround before try with a XT1040 backup.
Hi,
Thanks for that info. Unfortunately I can't do any of that, because fastboot doesn't see the phone any more. When I plug the phone in by USB, windows recognises it, and the phone says that USB is connected, but "ADB devices" in fastboot doesn't see it... So I don't know if it is completely bricked! Selecting any option in the bootloader menu gives me a screen with "Google" on it and a padlock sign...
It has enough battery? If not, Moto G dont allow you to use ADB comands for safety. If not that, really I have no idea. Hopefully someone who knows more than me pass by your thread
Yes, the battery is fully charged... ok, thanks for your help anyway!
Hello,
I am currently in a situation where USB debugging was not enabled, CROM service status is set to "Locked". This is causing an issue on my International Galaxy S6 Edge (g9250) -- It is stuck in a boot loop and the android OS that was previously installed was wiped on accident through the stock android recovery mode.
I am unable to flash TWRP recovery to the phone, I am unable to use Odin to flash a stock ROM image to the phone, or perform any data transfer between my Windows machine to the phone. Now I am sure this is because I never enabled developer mode and turned on USB debugging, and also because this CROM service is set to lock. When I attempt to sideload using ADB I get error:closed. When using the Skipsoft Unified Android Toolkit any task performed stops at: "Waiting for USB debugging".
Is there any solution for this? I've looked all over the internet and haven't been able to solve my issue -- I'm stuck at a perpetual boot loop because there is no Android OS on the device's partition, and also am unable to flash the stock ROM using ODIN or sideload using ADB.
Is there is a way to turn on USB debugging when stuck in a bootloop? Or a way to disable CROM service on the phone to be able to flash or transfer files?
As of right now the device is completely useless and I have been researching for the past 5 days
Any help is very appreciated, please let know if there is more information needed.
mellobc said:
Hello,
I am currently in a situation where USB debugging was not enabled, CROM service status is set to "Locked". This is causing an issue on my International Galaxy S6 Edge (g9250) -- It is stuck in a boot loop and the android OS that was previously installed was wiped on accident through the stock android recovery mode.
I am unable to flash TWRP recovery to the phone, I am unable to use Odin to flash a stock ROM image to the phone, or perform any data transfer between my Windows machine to the phone. Now I am sure this is because I never enabled developer mode and turned on USB debugging, and also because this CROM service is set to lock. When I attempt to sideload using ADB I get error:closed. When using the Skipsoft Unified Android Toolkit any task performed stops at: "Waiting for USB debugging".
Is there any solution for this? I've looked all over the internet and haven't been able to solve my issue -- I'm stuck at a perpetual boot loop because there is no Android OS on the device's partition, and also am unable to flash the stock ROM using ODIN or sideload using ADB.
Is there is a way to turn on USB debugging when stuck in a bootloop? Or a way to disable CROM service on the phone to be able to flash or transfer files?
As of right now the device is completely useless and I have been researching for the past 5 days
Any help is very appreciated, please let know if there is more information needed.
Click to expand...
Click to collapse
Greetings and welcome to assist. Can you get into download mode ? If you can does smartswitch emergency firmware recovery work
Regards
Sawdoctor
Hi, I was trying to revert back to realme UI stock from Pixel Experience ROM on my Realme 5i device(RMX 2030 EX). So, first I tried to install stock recovery through Orange fox. But after installing the recovery, my phone got bricked and now it's not even being detected by the pc nor I can access fastboot mode. As PC is not detecting my phone, I can't use Realme Flash tool or cmd to change my recovery. What can I do? Please if you know, give me a fix. I would be so grateful to you. Thanks for your time.
Here are some methods that might work for you.
How to Access an Android Phone with a Broken Screen
Dealing with a broken screen on your Android phone is a hassle. Although phone screens are pretty tough, one nasty drop can shatter them completely. Given that most people have a lot of irreplaceable content on their phones, it is
www.alphr.com
@Aranya Kishor Das
My POV: If on Android device side neither adbd ( requires USB Debugging got enabled ) nor fastbootd ( requires OEM unlock got enabled ) is accessible although the device's matching OEM USB driver got installed on Windows computer, then it's recommended to take phone to authorized service center and let them try to fix it.