Hey. I was using a 5.0.1 GPE Rom on my M8 and decided to update both the firmware and the rom to 5.1
I Backed everything up and decided to, as usual, use adb to sideload the firmware to the phone. I did and everything went as expected. After I finished I rebooted to android. I get NFC service stopped working, System UI stopped working and I can't interact with the phone. My thought, well let's go to the recovery and flash a rom I have in my external SD card. No recovery to be found just a android guy belly up with a red ! sign on his belly.
So I thought, I lost my recovery due to the firmware flash, I had happened before, So i went online found a TWRP recovery and went to flash it. Reboot to fastboot USB mode, but then in adb I cannot see the device at all. "adb devices" shows and empty list. I tried my windows 7 laptop to the same result.
Can anyone PLEASE PLEASE help me, I'm kinda freaking out at this point and am running out of options
xsidex said:
..... Reboot to fastboot USB mode, but then in adb I cannot see the device at all. "adb devices" shows and empty list.
Click to expand...
Click to collapse
When in fastboot mode - run command fastboot devices
No adb when in fastboot mode
To flash a recovery (unlocked bootloader)
fastboot flash recovery nameofrecovery.img
ckpv5 said:
When in fastboot mode - run command fastboot devices
No adb when in fastboot mode
To flash a recovery (unlocked bootloader)
fastboot flash recovery nameofrecovery.img
Click to expand...
Click to collapse
Sometimes some outside thought can be just ridiculasly helpfull when you are stuck in a tiny issue.
Thank you so much Kind sir, my heart rate thanks you aswell.
What a silly mistake
Hi everyone,
I´ve been trying to install twrp recovery in my Huawei Ascend P6 via fastboot. I followed this "techglen adb and fastboot guide"
I already installed everything needed for adb conection.
So I connect my phone in MTP mode and use "adb devices" and my device appears normally, but the problem happens when I reboot into Bootloader/Fastboot mode and use "Fastboot devices" it appears a device conected but with a bunch of "?????" and a smiley face at the end like this:
C:\Fastboot>adb devices
List of devices attached
123456789 device --------> bunch of numbers appear normally
C:\Fastboot>adb reboot bootloader --------> Phone restarts into bootloader mode (shows huawei ascend logo)
C:\Fastboot>fastboot devices
????????_?_???_?<??????? fastboot ----------> WTF (this is exactly what appears)
I would like to know if there's something wrong with my phone
Should I proceed and flash the custom recovery?
I have stock android 4.4.2 (rooted with kingroot) and stock recovery.
I am a total noob at this so I need your help :crying: I dont want to do anything stupid. (If already did let me know lol)
I have the same issue. Problem is that phone is bricked, so I can only enter in recovery (official, unrooted, unlocked) and fastboot mode.
Have you managed to solve or have some hint?
I have experienced a inconsistency while using minimal adb and fastboot. While device not showing i could send command and the phone would respond. After going into bootloader and while my device wasn't shown in the list i could flash twrp without much trouble, helped me go back from being stuck on bootanimation. used the command fastboot flash recovery xxxx.img (where xxx is the name recovery name). If you can get into boot loader try fastboot reboot bootloader and if the phone responds you might be in the same situation i was.
Always remember: Messing with recoveries bootloaders and boot images might make your phone unusable so do it at your own risk
Have you actually tried to flash twrp? Did you put the img file of twrp to the minimal adb and fastboot folder? If so, try the commands 'fastboot flash recovery recovery_twrp.img(<-- use the name of twrp file here, so not the exact name wrote here) and reboot. My phone is a bunch of question marks as well and it flashed twrp just perfectly (I got it frome here: http://forum.xda-developers.com/showthread.php?t=2632542)
I've been trying to flash TWRP recovery to my rooted LG G3 D855 (running 4.4.2 KitKat). I used the "Bump" method (thread) since I don't have an unlocked bootloader.
I tried the ADB method in that thread, I tried the Flashify method, and I tried the Official TWRP App. Each time, the recovery flashed correctly. But when I attempted to reboot into recovery (using the method in the linked thread, or in the case of the apps, they prompted me to reboot into recovery), my phone didn't bring up TWRP recovery or even the stock recovery. It just brings up "fastboot mode started". It's not stuck though, it boots normally when I pull the battery and power on.
I also separately tried rebooting it into fastboot mode with it plugged into my computer. When I entered "adb devices" into the command prompt, the device came up. Then I rebooted it into fastboot mode and entered "fastboot devices" - then nothing came up. I entered some other fastboot commands and it said "< waiting for device >". So it appears I can't issue normal fastboot commands either.
Any thoughts on how I can succesfully flash TWRP? Thanks.
i have installed my TWRP via this app -- https://ulozto.sk/!lisJevpDG1oS/recovery-d722l-apk
try hope itll help you
Well, somehow you failed to install it. Upgrade to LP (preferably v21C) and try this
I feel so dumb right now. I searched XDA ... google ... updated drivers ... using the One Plus cord in various USB slots on the PC and now I'm lost.
I've got an unlocked Global 9Pro, but it's not rooted after updating to Android 12 (missed a step, derp!). Adb is able to see my device when plugged into the PC (adb devices returns my device number) and I can run the "adb reboot bootloader" command to get into fastboot, but then I'm DoA.
There's no Bootloader or Baseband Version in fastboot (product name = lahaina // variant = SM_ UFT // Serial Number (valid number) // secure boot = yes // device state - unlocked.
When I try running "fastboot boot twrp.img" (twrp.img on the root of my device and in my ADB location in Windows) it hangs at <waiting for device>
I rebooted to recovery and wiped device, but still get stuck at <waiting for device> in fastboot when trying to flash the newest version of twrp.
1) Is no bootloader or baseband version normal or should there be values there?
2a) If it's normal, cool ... any idea why I get stuck at <waiting for device>?
2b) If it's not normal, how do I get those values back when I can't run fastboot commands?
Any help would be greatly appreciated.
Icculus760 said:
I feel so dumb right now. I searched XDA ... google ... updated drivers ... using the One Plus cord in various USB slots on the PC and now I'm lost.
I've got an unlocked Global 9Pro, but it's not rooted after updating to Android 12 (missed a step, derp!). Adb is able to see my device when plugged into the PC (adb devices returns my device number) and I can run the "adb reboot bootloader" command to get into fastboot, but then I'm DoA.
There's no Bootloader or Baseband Version in fastboot (product name = lahaina // variant = SM_ UFT // Serial Number (valid number) // secure boot = yes // device state - unlocked.
When I try running "fastboot boot twrp.img" (twrp.img on the root of my device and in my ADB location in Windows) it hangs at <waiting for device>
I rebooted to recovery and wiped device, but still get stuck at <waiting for device> in fastboot when trying to flash the newest version of twrp.
1) Is no bootloader or baseband version normal or should there be values there?
2a) If it's normal, cool ... any idea why I get stuck at <waiting for device>?
2b) If it's not normal, how do I get those values back when I can't run fastboot commands?
Any help would be greatly appreciated.
Click to expand...
Click to collapse
It seems you haven't installed driver's correctly
Hello,
I hope this is the right section for this post.
I've been using a Note 8 Pro with zero issues until one week ago when I accidentally dropped the phone in the water.
After a few seconds submerged the display turned off and I felt an intense heat coming from the zone of the battery.
Having no chance to recover the phone (tried with Isopropyl Alcohol too) I decided to open it and manually dry/clean each component, having seen the situation inside gave me the phone is dead but I still want to recover some pictures/data from it.
Before opening the open Minitool was not detecting any device on my Windows Laptop, after cleaning each component Minitool is instead detecting the phone via USB, but I still can't extract any data because the "Usb debugging" option is not tuned on (and no the device is not rooted).
Is there any option to extract data from the phone? There's a way to turn on USB Debugging via ADB on a non-rooted phone?
Thanks,
Andrea.
how about trying your luck with a service ? most of the time they do have access to special programs, which have a better functionality than adb.
Thanks for the hint, but I am not happy with the idea of someone playing with my data
1. Try reboot phone to recovery
2. Connect it to your computer (download Platform-tools)
3. In the folder with Platform-tools open cmd
4. In cmd - adb shell
5. cd storage/emulated/0
6. ls
7. Now, using the commands, drag files from your phone to your PC
Thanks for your hint.
No luck so far, I think because the phone is not in recovery mode.
I can hear the phone starting up several times (hear the jingle) so I think it's in a reboot loop and I don't know how to boot it into recovery mode wo a working display (tried with power/volume up combination with no luck).
From the windows taskbar I can see that the phone is recognized for a few seconds before it restarts.
EDIT: trying to switch the phone on with the combination "power/volume down" brings to a kind of stable state and I can now see the phone in the windows taskbar recognized as a generic "android device". Still no luck when trying to access the phone as there's no device in windows and no device obtained through "adb devices" command.
EDIT1: I think that the phone is in "FASTBOOT" mode. If I type "fastboot devices" I can see it detected but still can't access it.
Any idea? Should I give up?
If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info
Yes it's popping up and down when it's booted in recovery mode whilst is stably connected when in fastboot mode but in this case I can't access the internal memory of the device.
I didn't get the purpose of logging the devices connecting to the USB as I can see the device connected for a while and correctly recognized as Redmi Note 8 pro but as it keeps popping out windows have no time to show it's folder.
As for the code you wrote: i will try asap but already tried with "fastboot devices" and I get the phone correctly listed but still can't access its memory as told.
Renate said:
If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info
Click to expand...
Click to collapse
After rebooting the phone in fastboot mode I can see it recognized as a generic android device from windows (still can't access the storage folder of the device).
fastboot devices----> I get the device listed with a series of numbers/letters
fastboot getvar all---> I get a list of information on token/token version/partition type and size/baseband/bootloader etc.
fastboot oem device-info----> FAILED (remote: unknown command)
So I think it's clear that the device is in Fastboot mode and instead is in a boot loop when started in revocery mode.
Is there a way to extract data from fastboot mode?
Thanks,
Andrea.
If you put a custom recovery on it in the first place you can try reflashing recovery from fastboot.
Fastboot doesn't allow you to read anything.
oem device-info is obviously an oem command that might not be on any device.
You've got a Mediatek processor. That has some low level equivalent to Qualcomm EDL, but I have no experience with that.
If you can get there you can download the user data partition, but it's probably encrypted. Also no experience with that.
The easiest is if you can get the system to mount/decrypt the partition.
You've tried the normal system too?
Is this A/B? Have you tried changing slots?
How much time does it stay up in recovery? Do you have ADB? Maybe try:
Code:
# stop recovery
Does that prevent it from looping?
So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?
Sephiroth79 said:
So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?
Click to expand...
Click to collapse
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons
MysticNoOb said:
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons
Click to expand...
Click to collapse
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?
You really want to boot the normal system because that's the best way to get decrypted data.
I realized that you don't have ADB enabled there.
You should look at B. Kerler's https://github.com/bkerler/mtkclient/
If you can pull the boot image off your device then I might be able to fix it so that you have ADB.
You'd have to flash it back in fastboot or mtkclient.
You can also pull a copy of userdata off the device with mtkclient.
As far as booting into recovery, there's a way.
Here's how, if you don't have A/B (that is you flashed TWRP into recovery and not recovery_a or recovery_b)
then you can fastboot flash a special file into the misc partition and it wil boot into recovery next reboot.
To return things to normal you have to flash the empty file to the misc partition.
Code:
C:\>fastboot flash misc misc-rec.img
C:\>fastboot reboot
Only do this if you don't have partitions that end in _a or _b
I really don't know if I have partitions A and B as you mentioned and I think there's no way to check actually.
I confirm I don't have "USB Debugging" active on the phone.
So if I understand correctly I should do the following:
- Flash misc-reg.img via Fastboot
- Boot into recovery just rebooting the system after flashing the above file;
- use MTKclient to dump userdata or boot image to enable ADB on (I will need help with mtkclient I suppose).
Is it correct?
EDIT: flashed TWRP first and misc-rec then rebooted via Fastboot/Reboot but nothing happens.
Sephiroth79 said:
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?
Click to expand...
Click to collapse
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.
Kirasu2080 said:
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.
Click to expand...
Click to collapse
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?
Sephiroth79 said:
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?
Click to expand...
Click to collapse
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.
Kirasu2080 said:
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.
Click to expand...
Click to collapse
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?
Sephiroth79 said:
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?
Click to expand...
Click to collapse
Use brp 3.5.2 v3.1 or V3.6 to decrypt Miui 12.5