Database Develop

[Q] Stuck on Bootloader and Google splash

So I seem to have made the mistake of formatting data - don't ask me why, I wasn't thinking. Now I cannot get past the bootloader or the Google splash screen. On Windows BTW.
Things I've attempted:
ADB and Fastboot - When I ran the command to unlock, it said I already was. :good:
CF's root - Rooted
Wug's toolkit - Tried returning back to stock img, but says ADB device was not found. Step 1 was to enable USB debugging, but I cannot boot into the ROM so that is a no-go. I am using the original OEM cord. I've tried using another USB port as well... nothing.
If I am missing something, please let me know. The drivers should be good to go since I upgraded them 2 days ago.

Update: Dowloaded TWRP and installed via Fastboot. Restarted bootloader, booted into recovery, and the TWRP splash screen popped up. Shortly after that, the Google screen came up and is hung.
I found this thread http://forum.xda-developers.com/nexus-6/help/help-nexus-6-stuck-bootloader-t2949817. When I type fastboot devices, it shows my device's serial number.

Are you sure you didn't delete data? Formatting should not cause that issue. You can flash the stock userdata.img back and stock boot.img
Sent from my Nexus 6 using XDA Free mobile app

or, while in twrp, adb push/sideload a rom(and gapps) to your phone and flash it in twrp recovery.

[Q] 1092 TWRP on 5.0 bootloop, stuck in recovery [SOLVED]

Hi,
I was on 5.0, running stock recovery and rooted. Today, installed TWRP for 5.0 on my device. I tried to flash the droid command center widget on my phone usng twrp, and it failed. I also hit the fix permissions option. After that the phone does not boot up, simply flashes the unlocked bootloader sign and shows the moto boot animation for a second or two before shutting down.
I can boot into recovery, and the computer detects the phone. But adb doesn't detect the device. I have the 1092 5.0 OTA on my computer and saved it on the phone in an attempt to flash it thru TWRP, but that failed with the message shown in the img attached. I also tried flashing stock 4.4.4, but that gave an error "Updating partition details" failed.
Can someone help me get back into my phone? :crying: ADB doesn't seem to be detecting my phone, else I'd have tried to install a rom via fastboot.
I have multi-tool v4.1 installed, would I be able to flash a rom (stock unrooted and full wipe is perfectly fine too) via that considering adb does not detect my phone, but the computer does?

Well, that looks annoying.
I've found myself in similar situations when I've accidentally flashed something I shouldn't have. The good news is that if you can boot to recovery you can also probably boot to the bootloader and use fastboot.
Have you tried wiping everything and going back to stock? It's time consuming but at least you'll end up with a working phone.
I had to do this when I put the wrong recovery on a phone and it mangled partitions. Device wouldn't boot.
There are instructions for the moto x here
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657

oldcynic said:
Well, that looks annoying.
I've found myself in similar situations when I've accidentally flashed something I shouldn't have. The good news is that if you can boot to recovery you can also probably boot to the bootloader and use fastboot.
Have you tried wiping everything and going back to stock? It's time consuming but at least you'll end up with a working phone.
I had to do this when I put the wrong recovery on a phone and it mangled partitions. Device wouldn't boot.
There are instructions for the moto x here
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Click to expand...
Click to collapse
Thanks for the reply! Color me silly, but would I be able to use fastboot given that when I run adb the 'adb devices' command does not show my phone?

HAXTREME said:
Thanks for the reply! Color me silly, but would I be able to use fastboot given that when I run adb the 'adb devices' command does not show my phone?
Click to expand...
Click to collapse
Because fastboot mode can start on your device even before Android loads (and can even run when Android isn't installed at all), fastboot mode is useful for updating the firmware quickly, without having to use a recovery mode.
Adb relies on android booting and usb debugging being enabled and the computer being authorized for debugging (L feature). Fastboot does not. Try booting into the bootloader and then run "fastboot devices" . Mine shows up. I suspect yours will too. If it doesn't then I'm out of my depth here.

oldcynic said:
Because fastboot mode can start on your device even before Android loads (and can even run when Android isn't installed at all), fastboot mode is useful for updating the firmware quickly, without having to use a recovery mode.
Adb relies on android booting and usb debugging being enabled and the computer being authorized for debugging (L feature). Fastboot does not. Try booting into the bootloader and then run "fastboot devices" . Mine shows up. I suspect yours will too. If it doesn't then I'm out of my depth here.
Click to expand...
Click to collapse
Ah yes. For some reason, my fastboot file had gotten deleted from the folder and so the command didn't run. Everything went smooth once I noticed that. Had to downgrade to 4.4.4., but w/e. Thanks @oldcynic

Cannot connect to fastboot through ADB

Hi guys. I've had my HTC one for a while now and it had TWRP flashed on it. About a week ago I flashed the android revolution rom, worked well but my camera went really weird if I looked back at some recordings. So I wanted to revert back to stock everything. I flashed a stock recovery for the M7, after that I had the problem of not being able to connect my device to the computer when I fastboot mode. Simply wouldn't pick it up when I typed ADB devices in cmd. My device wouldn't show up after installing stock recovery. And it doesn't want to restore any roms either in stock recovery mode. I can't even access my folders in that mode to flash any roms. I click either apply from sd card, apply from phone storage. Says for a split second check CID failed or something and reboots itself.
I cannot flash TWRP back cause my computer since it can't pick it up. I've tried everything. Changing USB ports, uninstalling my drives for htc. Changing computers, unlocking, relocking bootloader. No result. I'm screwed cause I'm stuck on this android revolution rom, rooted. Just wanna flash custom recovery. I can connect it to my computer, access folders and add things to it but soon as I turn it off and go into fastboot mode it says fastboot usb and can hear the noise when its connected but it doesn't show up in adb devices and when I flash the TWRP it starts send then comes up with FAILED. Help please, would be appreciated!

Stevo001457 said:
Hi guys. I've had my HTC one for a while now and it had TWRP flashed on it. About a week ago I flashed the android revolution rom, worked well but my camera went really weird if I looked back at some recordings. So I wanted to revert back to stock everything. I flashed a stock recovery for the M7, after that I had the problem of not being able to connect my device to the computer when I fastboot mode. Simply wouldn't pick it up when I typed ADB devices in cmd. My device wouldn't show up after installing stock recovery. And it doesn't want to restore any roms either in stock recovery mode. I can't even access my folders in that mode to flash any roms. I click either apply from sd card, apply from phone storage. Says for a split second check CID failed or something and reboots itself.
I cannot flash TWRP back cause my computer since it can't pick it up. I've tried everything. Changing USB ports, uninstalling my drives for htc. Changing computers, unlocking, relocking bootloader. No result. I'm screwed cause I'm stuck on this android revolution rom, rooted. Just wanna flash custom recovery. I can connect it to my computer, access folders and add things to it but soon as I turn it off and go into fastboot mode it says fastboot usb and can hear the noise when its connected but it doesn't show up in adb devices and when I flash the TWRP it starts send then comes up with FAILED. Help please, would be appreciated!
Click to expand...
Click to collapse
Adb only works if you'te booted to OS or custom recovery. Command you're looking for in bootloader menu is "fastboot devices"

Fala Puno. Ja sam raditi sada. I'm of Croatian decent in Australia. I'll try this later when I return home

Fixed it! I'm an idiot, I didn't realise I was flashing the m8 twrp instead of m7. That's why it failed. Lol. Anyway thanks

Can't root P8 Lite

Hello everyone, I am new to this forum so please forgive if I misplaced this thread
The problem is next:
I want to root my P8 Lite (and convert to dual sim but first things first). I have read some threads here, also that mega-thread, did everything step by step.
First I have requested unlock code from Huawei and successfully unlocked bootloader (fastboot shows it's unlocked and booting in bootloader shows Phone UNLOCKED).
Second, I installed ADB drivers, HiSuite recognizes my phone, adb devices shows it, everything runs smoothly. I downloaded and tried bat file that automatically roots it (the lazy way ) but not success so far. Then I rebooted completely and did everything step by step using cmd.
1. adb reboot bootloader (OK)
2. fastboot flash recovery recovery.img (OK)
3. fastboot reboot (OK)
4. adb push UPDATE_SuperSU-v2.46.zip /su.zip (OK)
5. adb shell /sbin/recovery --update_package=/su.zip (SEGMENTATION FAULT)
I am stuck at step 5, clearly. Also I tried commands one by one:
adb shell
/sbin/recovery
But that returns Permission Denied.
Tried that again through Minimal and ADB Fastboot, through SDK, but no success so far. Thought that Windows 10 may be the problem, but the same was on laptop with Windows 7.
I would appreciate any help here.

I don't know. In my opinion, you can put the SuperSU flashable zip into your phone through USB, and boot into TWRP Recovery, mount /system, then flash it.I'm not sure about it. Maybe it can help.
P.S.: You can see https://forum.xda-developers.com/p8...de-to-unlock-bootloader-t3150616/post61708277this post, find the UPDATE-2.
Sent from my HUAWEI CHM-TL00H using XDA Labs

I can't boot into recovery, it shows nothing. There is a sound that usb is connected but screen remains black, I can't install twrp over stock recovery. Is sd card necessary or this can be done just with phone memory?

popcorn91 said:
I can't boot into recovery, it shows nothing. There is a sound that usb is connected but screen remains black, I can't install twrp over stock recovery. Is sd card necessary or this can be done just with phone memory?
Click to expand...
Click to collapse
I had some problems installing TWRP and SU after my update to B588.
I used Xepeleato's TWRP edition with the 2 zip SU installation (I have so many files, that I cannot remember where I got them ).
So, flashed TWRP, then connected via usb (if I am not mistaken) and then via adb rebooted into recovery. Then flashed both of the files for the SU.

I will try doing that with install from sd card, from service menu, otherwise I can't install over stock recovery.

Also can't root it. I soft bricked my phone 3 times and then had to flash Cust, Boot and all the other images using a script I found on the Megathread and set it up all over again. I have an unlocked bootloader but can't root it and I am too scared to try again.

That's my problem, first time softbricked it, then I flashed stock recovery and fixed it, bootloader unlocked but can't root.

Just in case you are on B588: I had problem with the official recovery of the build (don't know for sure if it is different from the others) and flashed the one extracted from B584 and then flashed TWRP.

I'm on B585

if I were you, i'd flash twrp, through adb and then boot into recovery through adb also and flash the 2 zip SU files at once. clear cache and dalvik and reboot.

spirto82 said:
if I were you, i'd flash twrp, through adb and then boot into recovery through adb also and flash the 2 zip SU files at once. clear cache and dalvik and reboot.
Click to expand...
Click to collapse
How did you flash the one from B584?
EDIT: Nevermind, I did it. I booted to recovery through adb and TWRP was working

Did it, found some chinese twrp that worked for me. Now other problem came up
I tried to downgrade to Lollipop and setup was successfull. When phone restarted display wasnt showing anything,just bars and flashes and pixels etc, startup sound is there but no preview. Fastboot system flash returns failed, also erase.

popcorn91 said:
Did it, found some chinese twrp that worked for me. Now other problem came up
I tried to downgrade to Lollipop and setup was successfull. When phone restarted display wasnt showing anything,just bars and flashes and pixels etc, startup sound is there but no preview. Fastboot system flash returns failed, also erase.
Click to expand...
Click to collapse
1) let your phone charge - in case you don't have enough battery.
2) Try to download your desired build.
3) download Huawei extractor and with this, extract boot, recovery, cust and system.
4) search a bit on the big thread (root, unbrick convert etc) on how to enter fastboot. I cannot remember the exact steps, but there is a way for sure.
5) initiate adb and flash all the 4 images you extracted.
This is in general what you have to do.
Wishing you good luck!
If I find something more I'll let you know.
PS : when I had mine bricked I entered bootloader by following these steps if I am not mistaken :
Connect phone to pc
Keep Pressing the power button and when the screen turns off, press and hold the volume up (while pressing the power button).
When the phone vibrates, release the power button.

Tried everything, boot, recovery and cust flashed successfully but sytem "cant load system.img" even with using -S 512M or 1G or 256M. I took it for a repair, hope they will sort it out.

The guy from service did not succeed, he told me that he tried everything that I have, and that the phone can't be repaired. But I did.
I downloaded the latest firmware for my country, formatted SD card as FAT32, put it in my phone and rebooted, so folders Android, LOST.DIR and System Volume Information were created. I put the UPDATE.APP in dload folder on my SD card. Then I let phone charge fully until LED indicator was green. Plugged out the charger, and pressed Volume Up + Volume Down + Power. When the phone restarted, on startup vibration I let go power button and kept holding Volume Up and Down for about 3s. Then when I let them, display went completely black and nothing happened. I put the charger but it wasn't charging so I hoped that it started forced upgrade. Left it on the table and about 15min later it vibrated again on restart and - success!! Huawei logo on screen, booting up, EMUI optimizing device. So happy I solved it. Also thanks for answering guys!

Oneplus 3T will not boot into full recovery

I updated my oneplus and i got the TWRP decryption message, so i formatted it back to the stock format.
now all the phone does is boot into the bootloader but gets stuck on the boot screen of Blu Spark 3.1.1
my computer wont recognize it while its in the bootloader or while its stuck trying to boot in twrp
is there anything i can do or is my phone screwed at this point? i see a lot of threads that would answer parts of my issue but nothing that covers this as a whole. id rather ask for help now while there may be some hope.

nickhawkjones said:
my computer wont recognize it while its in the bootloader or while its stuck trying to boot in twrp
Click to expand...
Click to collapse
So no response to fastboot commands, while in bootloader-fastboot mode?

Are you sure you installed the right drivers for your pc? If all else fails, you can do this.
This is how I fixed my phone when i was stuck at a black screen. You can also try a different usb cord or port. Check device manager and see if it recognizes it when its plugged in. hope this helps!
https://www.youtube.com/watch?v=BvfA5WrVDQM

can you boot into fastboot? if your phone can boot to fastboot mode..just flash stock recovery image..then flash rom via adb shell (better flash the stock rom). if it works you can reinstall the custom recovery image or something. dont forget to erase everything via stock recovery..