Related
Trying some stuff and need to get to stock recovery. Can normally get there from the extended reboot menu or ADB, but hosed something so adb doesn't work. I know it's there, used it for factory reset a dozen times.
Tipe in console:
Su
Reboot recovery
getochkn said:
Trying some stuff and need to get to stock recovery. Can normally get there from the extended reboot menu or ADB, but hosed something so adb doesn't work. I know it's there, used it for factory reset a dozen times.
Click to expand...
Click to collapse
Gabboxxx said:
Tipe in console:
Su
Reboot recovery
Click to expand...
Click to collapse
Doesn't matter, I just reflashed, but I can't run SU, reboot recovery when ADB doesn't work as I clearly stated.
And if u reflash the ftf?
getochkn said:
Trying some stuff and need to get to stock recovery. Can normally get there from the extended reboot menu or ADB, but hosed something so adb doesn't work. I know it's there, used it for factory reset a dozen times.
Click to expand...
Click to collapse
Not via ADB commands ? Try a different cable ? Maybe you forgot to enable USB debugging? Enable unknown sources might help too
I had no problems booting via ADB
adb reboot recovery
I suppose try using a different PC and reflash a different ftf file. That might help as it will complete rewrite the recovery again in case you have screwed it
Check this post where I have successfully booted into recovery via ADB :
http://forum.xda-developers.com/showthread.php?t=2480590
the whole of this was my phone was softbricked. I wanted to get into recovery so I could use ADB to try to fix it. When it's softbricked, ADB won't start up, therefore I could use ADB.
Trust me, I know how to use ADB, I just wanted to know if there was a key combination to get our phones into recovery mode with ADB because ADB wouldn't work because my phone was softbricked. It had nothing to do with me not knowing how to use ADB or how to set it up, it had to do with my phone would brick it self before ADB started, so therefore I couldn't send any ADB commands.
getochkn said:
the whole of this was my phone was softbricked. I wanted to get into recovery so I could use ADB to try to fix it. When it's softbricked, ADB won't start up, therefore I could use ADB.
Trust me, I know how to use ADB, I just wanted to know if there was a key combination to get our phones into recovery mode with ADB because ADB wouldn't work because my phone was softbricked. It had nothing to do with me not knowing how to use ADB or how to set it up, it had to do with my phone would brick it self before ADB started, so therefore I couldn't send any ADB commands.
Click to expand...
Click to collapse
I am uploading drivers on a post. Will quote you to it. Install them. I hope that helps!
here you go
http://forum.xda-developers.com/showthread.php?p=46681107#post46681107
Ok, let me try to explain this.
It's not drivers.
It's not ADB.
It's not my PC.
I softbricked my phone trying something. I didn't want to wipe it, so I wanted to try to get into recovery, where a limited ADB works.
I couldn't boot into recovery from ADB because it was softbricked.
I just wanted to know if there was key to hold down on boot or something to get into the default recovery mode.
I don't need drivers, I don't help getting ADB going, it works fine on my PC. The point was the phone was softbricked, in a boot loop, ADB wouldn't respond, wanted a key command to get into recovery.
I apprecaite the help but people aren't getting what I was asking.
Is there a key command to press at the bootup to get into the stock recovery on this phone? All my other phones, I know the command, but this one I've tried all the combos and no recovery.
Please, no more help on ADB, I know how to use ADB just fine.
Just is there a keypress to do this?
Hi guys,
I have a rooted Device with CM and TWRP installed, but someting happenend using the device and my Moto G got stuck on startup logo and Recovery TWRP logo, with adb I have acess to adb shell but everything else like adb reboot bootloader etc doesn't seems to work, with adb shell I have realized that the TWRP wasn't running 'cause when I use the interface on shell I get this message
$twrp wipe cache
"TWRP does not appear to be running. Waiting for TWRP to start"
Is there any way to install a new recovery via adb shell or reinstall a new rom, factory reset or something like that to make my cellphone work again?
Thanks,
If you are okay to wipe internal storage, the following fastboot command will probably make TWRP load again:
fastboot erase userdata
fastboot flash recovery newrecovery.img - is a way to reflash recovery, however the above command may still be required.
The problem is that with fastboot the device is not recognized, only when I open the recovery mode...
The logo freezes but the device is reconigzed with adb devices...
gconsentini said:
The problem is that with fastboot the device is not recognized, only when I open the recovery mode...
The logo freezes but the device is reconigzed with adb devices...
Click to expand...
Click to collapse
What OS are you using? Maybe try the ADB commands:
adb shell
wipe data
lost101 said:
What OS are you using? Maybe try the ADB commands:
adb shell
wipe data
Click to expand...
Click to collapse
It's the latest CM
I'll try, but the last time I got this message.
"TWRP does not appear to be running. Waiting for TWRP to start . . .
Press CTRL + C to quit."
EDIT
using
adb shell
twrp wipe data
happened the same above
gconsentini said:
It's the latest CM
I'll try, but the last time I got this message.
"TWRP does not appear to be running. Waiting for TWRP to start . . .
Press CTRL + C to quit."
EDIT
using
adb shell
twrp wipe data
happened the same above
Click to expand...
Click to collapse
I meant what OS on PC are you using. Stop adding the phrase 'twrp' - type the command as I wrote it.
lost101 said:
I meant what OS on PC are you using. Stop adding the phrase 'twrp' - type the command as I wrote it.
Click to expand...
Click to collapse
Sorry, I'm using Windows 10, if I use only wipe data, the command wipe is not reconigzed.
Can you enter fastboot mode by holding vol down and powering phone on?
lost101 said:
Can you enter fastboot mode by holding vol down and powering phone on?
Click to expand...
Click to collapse
yes, but when I connect the phone usb and use fastboot devices
it has no devices on the list
gconsentini said:
yes, but when I connect the phone usb and use fastboot devices
it has no devices on the list
Click to expand...
Click to collapse
There are many threads on Win10 and usb driver issues. If you don't want to try to fix fastboot on Windows, you could boot into a Ubuntu Linux LiveCD and install fastboot there.
lost101 said:
There are many threads on Win10 and usb driver issues. If you don't want to try to fix fastboot on Windows, you could boot into a Ubuntu Linux LiveCD and install fastboot there.
Click to expand...
Click to collapse
Yes, I thought about that too =x
SOLVED
Guys the problem was that I've not installed the drivers before, after doing this, I just installed the stock rom from motorola.
Thanks
gconsentini said:
SOLVED
Guys the problem was that I've not installed the drivers before, after doing this, I just installed the stock rom from motorola.
Thanks
Click to expand...
Click to collapse
Hey i'm having the same issue, would you mind telling me how you re-flashed the Motorola rom, Thanks
thomasswan5547 said:
Hey i'm having the same issue, would you mind telling me how you re-flashed the Motorola rom, Thanks
Click to expand...
Click to collapse
Install the Minimal Fastboot & ADB package and the Motorola USB drivers, use the mfastboot package and install the stock ROM as per the instructions provided, but ignore the disassembly part, unless you have your phone does not respond to keypresses.
https://forum.xda-developers.com/showpost.php?p=71328823&postcount=915
Hi,'
I think I disabled google app on my nexus 5 (stock android) and since then my phone is stuck in boot loop. (My phone does not go past logo of marshmallow rolls or message saying starting apps 10 of 10). I have very important data that is not yet backed up and I need them to be recovered.
From various threads, I did following in recovery mode
1. Wipe cache option under recovery menu - as it was mentioned, that it would not delete any user data on my sdcard. (No help, still stuck with boot loop)
2. In recovery mode - there was an option to mount phone memory and I did that. My phone shows a message at the bottom of the screen that it is successfully mounted. But I am not familiar how to proceed further or to recover data from my phone.
My phone is running stock android and I think I have not disabled USB debugging. I am not familiar about ADB, but can follow your guidelines and execute them. When I connect my phone to windows laptop, I see my laptop trying to install the MTP device driver, but fails saying unable to find the driver.
I need to recover my data and Any help is greatly appreciated.
Is your bootloader unlocked? I'm guessing not.
Sent from my Nexus 5X using XDA Free mobile app
If the bootloader is unlocked, you could flash twrp and then mount the data partition from twrp. If the bootloader is not unlocked, you could try pulling the data from the phone using adb commands. Was debugging enabled in the rom?
I have not unlocked my boot loader. Is there a guide to use adb with stock android?
Only if you enabled debugging in developer options.
Today, I installed 15sec ADB installer and booted my device in to recovery mode by pressing power and volume keys.
Then under recovery menu there was an option called - Mount / System. I selected it by pressing power key and from ADB ran adb devices.
No devices was listed, when I ran ADB devices.
But I saw another option in my phone recovery screen - Apply update from ADB.
I got a message in phone - "Now send the pacakge you want to apply to the device with adb sideload filename".
Now, when I execute ADB devices in my PC cmd prompt, I see my device with its serial number.
then I tried to use ADB Pull /sdcard/ to recover files from PC command prompt. But I got a message - saying error closed.
Am I doing the right things? Can you guys guide me to recover files from this point.
My bootloader version is HHZ20h. Product - Hammerhead.
I noticed from below link a user has had luck with sideloading a launcher. Has anyone here tried it ? will it affect my data on phone?
https://code.google.com/p/android/issues/detail?id=64773#c22
Any guide to sideload google search app in recovery mode?
Have you considered side loading the OTA from Google? https://developers.google.com/android/nexus/ota Directions are on the site.
When you get to this point
(But I saw another option in my phone recovery screen - Apply update from ADB.
I got a message in phone - "Now send the package you want to apply to the device with adb sideload filename".), you send the ota zip. (Adb sideload <name of zip> ). You have to make sure the zip file is in the folder with adb files.
Sent from my Nexus 9 using Tapatalk
I tried to install OTA update and did the reboot. But it did not help.
Can anyone provide me a launcher that I can sideload in recovery mode? Reading from various threads, I think my phone is in this state because I disabled the google app, which is also the launcher.
Thank you
Try to flash system image without userdata wipe and wiping only cache
Sent from my fx-82MS CAF using Tapatalk
santi1993 said:
Try to flash system image without userdata wipe and wiping only cache
Sent from my fx-82MS CAF using Tapatalk
Click to expand...
Click to collapse
How to perform this flash without wiping my user data? Any guide for it?
Download the stock image from Google that matches the rom currently installed on the phone, extract system.img, boot phone into fastboot mode, and type fastboot flash system system.img at the command prompt, and reboot.
audit13 said:
Download the stock image from Google that matches the rom currently installed on the phone, extract system.img, boot phone into fastboot mode, and type fastboot flash system system.img at the command prompt, and reboot.
Click to expand...
Click to collapse
Let me try it. so far I have been able to execute only adb sideload commands, after choosing Apply update from ADB.
Let me try this - fastboot flash system system.img.
smartey said:
Let me try it. so far I have been able to execute only adb sideload commands, after choosing Apply update from ADB.
Let me try this - fastboot flash system system.img.
Click to expand...
Click to collapse
Boot ur phone in fastboot mode (From power off to vol down + power), then connect it to the pc and install latest_google_drivers for nexus devices, ull need to manually install them, after that ur fastboot will recognize ur device.
From that type fastboot devices, if u see ur device connected u simply need to get into the commands that the other user gave to you, i u are lucky ur device will boot.
if u had unlocked bootloader the thing was easy as installing twrp 3.0.2.0 and backup all ur data via MTP
Recently I installed a custom ROM that is meant to be installed on a Huawei P8, for my Huawei P8 lite as my new OS because I accidentally deleted my whole OS. When I plug my mobile phone to a power source it shows the Huawei logo, I cannot get it into fastboot/rescue mode. If I try the dload folder to sd-card method it will not do anything. Does anyone know what to do.
Flash the stock firmware. I'm 100% sure your problem would be solved.
munimjaffer said:
Flash the stock firmware. I'm 100% sure your problem would be solved.
Click to expand...
Click to collapse
How do I flash it without fastboot?
pim8181 said:
How do I flash it without fastboot?
Click to expand...
Click to collapse
What do u see when u try to enter fastboot?
munimjaffer said:
What do u see when u try to enter fastboot?
Click to expand...
Click to collapse
When I try to enter fastboot I just see the Huawei logo
pim8181 said:
When I try to enter fastboot I just see the Huawei logo
Click to expand...
Click to collapse
Ok can u enter into recovery mode?
munimjaffer said:
Ok can u enter into recovery mode?
Click to expand...
Click to collapse
Nope....
Your phone got hardbricked with flashing a wrong rom,hardbrick is really hard to unbrick,
i already have one phone that got hardbricked due to flashing a wrong rom,since now i can't find the solution to unbrick it,
hope you find the solution soon..
pim8181 said:
Nope....
Click to expand...
Click to collapse
Is the device recognized by PC? If not, what is device manager labeling the device as?
If it connects to PC and is recognized you can.........
Use adb to clear cache and dalvik/ART cache, then see if the device will boot to recovery or fastboot, if not then power the device off and remove the battery then reinsert the battery(if it has a removable battery). Then leave the device off and connect it to PC then open a adb terminal and type:
adb reboot bootloader (press enter, sometimes the deamon has to start, if nothing happens then type adb reboot bootloader a second time, some devices can be booted from a powered off state with adb)
If that doesn't work try typing:
adb reboot fastboot (press enter).
If none of that works to boot fastboot then try turning the device on, when it gets to the logo, connect the device to PC, open a adb terminal and type:
adb devices (press enter, if it returns a serial number the device is recognized)
Then type:
adb reboot bootloader (press enter and it may boot to fastboot)
Or type:
adb reboot fastboot (press enter)
Or type:
reboot fastboot (press enter)
If none of that gets you to fastboot and you can't boot it manually with the buttons then you're bricked, its not hardbricked though because it boots to logo so that means bootloader is at least there even if it is corrupted and whether anything else is there or works or not.
Whatever you flashed must have had some differences in partitions that flashed over your partitions in places that weren't correct for your device, its more than just the software not being for your device, it is structured completely different than your device.
You've got to get to fastboot someway to flash the stock firmware, that's the only thing I see being able to correct your partitions and put the .imgs in the places they are meant to go.
There is also the possibility that you can download your stock firmware, then extract the kernel(Zimage, its sometimes bundled with/called boot.img or recovery.img, depending on device and android version), the boot.img, the recovery.img and the system.img and then do some research on your device model number and find out which partition(mmcblk0) each of those imgs go in(I could tell you how to use adb to find the partitions but that wouldn't help if flashing the wrong things has screwed up their placements). Then, if adb is working with the device you can use the dd command to manually push the boot.img to its mmcblk0, the recovery.img to its mmcblk0 and the system.img to its mmcblk0.
I would start with dd-ing the recovery, then seeing if it will boot to recovery, if the recovery is a custom recovery and you have a nandroid backup or a correct ROM zip, try restoring or flashing. If it doesn't then dd the boot.img to its mmcblk0 and see if it boots to recovery, if not, dd the system.img to its mmcblk0, you can repeat this process with each of the .imgs in your stock firmware. Maybe if you can push enough to the device it will restore some functionality that will allow you to get booted to a state will allow you to completely reflash the device.
If the confused you then I might have confused myself typing it, lol.
i type in "adb reboot bootloader" but i just get put back to the system (i have access to recovery mode but there is nothing usefull [reboot system wipe data factory reset power off])
try "adb reboot fastboot" instead
hxudsh said:
try "adb reboot fastboot" instead
Click to expand...
Click to collapse
it doesn't do anything the phone is just a cheap alcatel anyway i think they just forgot at this point to put in a fastboot it's on a ancient version of android anyway i can just use root exploits