Hi All,
I am currently in the phone repair business. Well i buy as much as i can fix and sell on. Its all fun. I have a very nice one currently and looking to see if anyone has ideas. All i want to do is boot to recovery that is my current goal.
So phone clearly has corrupt installation, likely a flash Rom or update gone wrong. It boots to Huawei logo then reboots and that's all it does. Tried de-powering and all sorts including removing battery cable but to no luck.
There is no recovery mode
No download mode
Can get to fastboot but unable to run commands it seems due to FRP lock. I am not worried about FRP lock at this time, i only want recovery back.
Tried:-
All flash commands and all fail
Any attempt to get to receovery or download mode fails
All three buttons to force SD card boot fails
Currently trying to boot using SD card but seems i need to change boot devices from within recovery. Well it has no recovery mode so no luck there.
So it is pretty much a brick at this point and could be a write off but before I give up does anyone have any other ideas? maybe a FB command i can run with FRP lock and bootloader lock on?
Thanks
Karl
Related
There's a TL;DR at the end !
Hi - I hope you will be able to help me !
I have a XT910 Motorola Razr from Rogers in Canada.
I've had a Nexus S for a long time and I guess I wasn't prepared for a phone that wasn't as friendly to modding and flashing.
Before trying to flash a version of CM10 found here in the forums, I installed CWM Touch and made a nandroid backup - standard stuff.
What I didn't realize until it was too late is that booting into recovery DOES NOT boot CWM Touch - but rather the regular android one - the one that does not allow you to do much other than to factory reset.
I found out about RSD Lite but not until my battery wasn't charged enough and couldn't do anything about the phone.
I searched for the longest time on a LOT on different forums about how I could fix this and resorted to getting a factory cable - which works.
So, now, I can flash stuff using fastboot. Great, right ? Well, I still can't get things working.
RSD Lite doesn't detect my phone, and I believe that's because ADB doesn't detect it as well - so I tried that alternative way to flash fastboot files provided by the eternity project.
I've tried various fastboot packages but to no avail.
The best I can do is to get past the motorola logo - then black screen. Otherwise, I get boot or flash failures and get sent back to fastboot.
When the phone is on the black screen and that I plug a USB cable to my phone, Windows sees the device but it doesn't recognize it - I assure you I've tried all the different drivers to try and get it to work. Nothing.
Worth mentioning - I often get errors "Preflash validation failure" when trying to flash stuff.
I really feel I could fix this issue by flashing an IMG version of CWM touch or some other sort of recovery so that I can recover using a nandroid but they are no where to be found ! I can't believe that all recovery options are installed by APKs.
Any ideas ?
TL;DR, XT910 went boot looping after trying to flash CM10 - resorted to getting a factory cable and even then, can't get the phone back into working condition. Phone is detected by fastboot but not ADB.
Thanks !
first... the battery is the problem
this article can help...
How to Boot your Phone on Low Battery with Fastboot Flash Failure
To boot your phone on low battery where you get stuck on fastboot flash failure, hold down Volume Up and Volume Down then plug in “AC” USB charger to your Droid Razr. This will give you the bootloader menu upon where you can choose “Normal Recovery” to boot. If your phone doesn’t boot here, it will at least re-charge the battery normally instead of being stuck on fastboot flash failure which will re-charge your phone “very very slowly”.
LG Escape running 4.1.2
here is the progression of events:
1. rooted device
2. root seemed successful and no malfunctions
3. backed up all apps and system data with Titanium backup
4. the lg escape has no way to unlock the bootloader, so I tried various other methods. one of which was entering recovery mode via terminal commands. this is basically a hard reset, and it wiped all my data
5. I restored all my apps and data from my external sd card with titanium
My best guess is this is where something went wrong
6. upon restoration it prompted me to reboot the device
7. reboot passes manufacturer logo, but resets when AT$T logo appears
8. as stated earlier, there is no way to enter recovery mode during boot.
9. there is a hard reset during boot, but mine will not work, as it requires touching buttons which do not seem to be active in my stage of the boot sequence
so, I understand this does NOT mean my phone is bricked, but I don't know how else to get it to boot back up, or what is even causing the boot loop, as I DO NOT HAVE ANY CUSTOM ROMS flashed. any help here is very appreciated!
EDIT: so I have attempted to use adb on my pc to reboot into recovery from there, but it occurred to me that while I was in recovery the first time, I never checked "usb debugging". as a result my adb console commands cant even see my device. any way to turn on usb debugging while locked in a boot loop?
also, I can get it to enter download mode. I was hoping I could just reflash the firmware to it without needing to enable usb debugging, but have no clue how to do that while locked out of the phone.
I realize this is a very specialized set of questions, but it is necessary to ask here as the most people will see it. im open to any ideas
whitechameleon said:
LG Escape running 4.1.2
here is the progression of events:
1. rooted device
2. root seemed successful and no malfunctions
3. backed up all apps and system data with Titanium backup
4. the lg escape has no way to unlock the bootloader, so I tried various other methods. one of which was entering recovery mode via terminal commands. this is basically a hard reset, and it wiped all my data
5. I restored all my apps and data from my external sd card with titanium
My best guess is this is where something went wrong
6. upon restoration it prompted me to reboot the device
7. reboot passes manufacturer logo, but resets when AT$T logo appears
8. as stated earlier, there is no way to enter recovery mode during boot.
9. there is a hard reset during boot, but mine will not work, as it requires touching buttons which do not seem to be active in my stage of the boot sequence
so, I understand this does NOT mean my phone is bricked, but I don't know how else to get it to boot back up, or what is even causing the boot loop, as I DO NOT HAVE ANY CUSTOM ROMS flashed. any help here is very appreciated!
EDIT: so I have attempted to use adb on my pc to reboot into recovery from there, but it occurred to me that while I was in recovery the first time, I never checked "usb debugging". as a result my adb console commands cant even see my device. any way to turn on usb debugging while locked in a boot loop?
also, I can get it to enter download mode. I was hoping I could just reflash the firmware to it without needing to enable usb debugging, but have no clue how to do that while locked out of the phone.
I realize this is a very specialized set of questions, but it is necessary to ask here as the most people will see it. im open to any ideas
Click to expand...
Click to collapse
i have now tried to flash the firmware while in download mode using a less than legitimately obtained lg R&D tool. however, i need V10F_00.kdz and i am facing a bit of censorship. any kind soul willing to host this file on dropbox or similar so i can download it?
Usually devices have a button combination to press when powering on to get into different modes. Maybe try searching for the button combination of your phone on Google? Try ' lg escape button recovery ' ?
J2270A said:
Usually devices have a button combination to press when powering on to get into different modes. Maybe try searching for the button combination of your phone on Google? Try ' lg escape button recovery ' ?
Click to expand...
Click to collapse
believe me i have. the only combo i can get to is download mode. there is a combo for a hard reset, but my touch buttons arent active during boot.
I apologize if this is in the wrong place, and I've really tried searching around, but nothing seems to work/ is tailored to the m8.
So, I just got an M8 new out of the box, rooted it and successfully installed cyanogenmod. Problem is, I was playing around with it, trying to get the GApp store and somehow (did what i think was) deleted my roms completely. Now upon booting up the phone I just get the "This build is for dev..." screen, and with the volume down+Power button to access recovery mode I constantly get put back to the fastboot screen. I tried flashing a custom recovery as in "Phone arena CWM flash recovery" guide, but no luck because my computer is reading the device as offline. I honestly have no idea what to do, and if anyone could help me I would be so greatful...
TL;DR: Stuck on boot screen, can't enter recovery mode, think i deleted all my roms, help please
On a scale of 1 - bricked, how bricked is my phone?
HUGE DEVELOPMENTS, GUYS! I've been able to access recovery mode again by re-flashing ClockWorkMod.
ctran1 said:
On a scale of 1 - bricked, how bricked is my phone?
Click to expand...
Click to collapse
On that scale, you are zero. If the screen comes on, you aren't bricked.
Hi there,
I need your help with my device which I just bricked in a peculiar way...
So, something I flashed was not correct. That resulted in an infinite reboot loop (the logo is shown for half a second and it reboots... endlessly). I just used the volume-up rocker to go into fastboot mode to fix the thing as I usually do. I booted into fastboot and this is where it become weird: I cannot do anything!
If I try to use fastboot continue, the phone reboots endlessly again.
If I try to boot to any img (TWRP or signed recovery or signed boot), the device tells me it cannot because it is locked.
If I try to unlock the bootloader (again, because it was), I am told that I am not allowed to do it. The problem is that I cannot boot into a ROM to go into dev mode to allow this.
If I try to flash things, it obviously doesn't work either as the bootloader is considered locked.
The worse here is that since my phone is "not" hard-bricked, I cannot go into qhsusb_bulk mode and use Qualcomm tools to unbrick the thing.
Can I still do something myself or am I screwed?
Lltp said:
Hi there,
I need your help with my device which I just bricked in a peculiar way...
So, something I flashed was not correct. That resulted in an infinite reboot loop (the logo is shown for half a second and it reboots... endlessly). I just used the volume-up rocker to go into fastboot mode to fix the thing as I usually do. I booted into fastboot and this is where it become weird: I cannot do anything!
If I try to use fastboot continue, the phone reboots endlessly again.
If I try to unlock the bootloader (again, because it was), I am told that I am not allowed to do it. The problem is that I cannot boot into a ROM to go into dev mode to allow this.
If I try to flash things, it obviously doesn't work either as the bootloader is considered locked.
The worse here is that since my phone is "not" hard-bricked, I cannot go into qhsusb_bulk mode and use Qualcomm tools to unbrick the thing.
Can I still do something myself or am I screwed?
Click to expand...
Click to collapse
Still you can do that hard brick recovery method it will work for sure..switch off your phone completely and try to connect qhsusb mode.
I had no idea that I could force the qhsusb mode. It worked indeed. Damn ARM devices with their non-standard way of doing anything...
So I recently got a Nexus 9. I think it was affected by the battery issues with android nougat. I rooted and used greenify and got much better battery life but decided I wanted to unroot and see if over a couple days the battery life would have gotten better. So I connected to my computer and stupidly sent the "fastboot flashing lock" command and now my Nexus is stuck in a boot loop because of TWRP. I knew that locking the bootloader would initiate a factory reset but didn't take into account that TWRP may affect that so now I can not use my Nexus. The device says it is a developer edition and not intended for personal use and I don't I know what to try. Just letting everyone know I only tried to sideloading and flash. I appreciate everyone who takes the time to read this and try to help.
Have you tried following instructions from google to flash a factory image ?
https://developers.google.com/android/images
I have but I can't flash due to the bootloader being locked and I can't sideloading because every time I tried it just errors or does nothing
AUSTIZ1997 said:
I have but I can't flash due to the bootloader being locked and I can't sideloading because every time I tried it just errors or does nothing
Click to expand...
Click to collapse
Did you try booting your nexus to fast boot and execute fastboot oem unlock?
I have, it just send me an error message
Update, I was able to finally get into the custom recovery and tried to flash the stock recovery and now it just boots into fastboot mode but I got rid of the custom recovery (as far as I know) and the boot screen that said the tablet was a developer device
Same problem here in May 2017, the OTA update prompted by Google sent the device into a bootloop. As the Bootloader was locked and there was no way to change to USB debugging mode it wasn't possible to use Recovery mode or to flash an OTA. Wiped data cache, tried all options in HBoot menu, tried flashing OTAs and full block OTA didn't work either. Just stuck in bootloop.
Repair shop encountered same problems so they then suspected the logic board. They heated it up to reflow the solder and success! Logic board may fail again through dry joint but I believe this risk can't be avoided by switching manufacturer as they all use the same component-to-board soldering practice.