Related
can you help me fix this problem
after wipe all data, cache and anotherthing wipe (it's name very hard to remember ).
I cant use recovery mode, my phone can open fastboot and bootloader, but can't open recovery mode (it's only show a android logo when i press "recovery")
please help me (
I could be wrong, but you should be able to use adb to push a new recovery on to your phone.
Try plugging your phone thru USB cord to your computer to see if you can run any adb commands. If you can I think you should be able to push a new recovery to your phone.
justflikwalk said:
I could be wrong, but you should be able to use adb to push a new recovery on to your phone.
Try plugging your phone thru USB cord to your computer to see if you can run any adb commands. If you can I think you should be able to push a new recovery to your phone.
Click to expand...
Click to collapse
can you show me more, i dont know adb commands, and push new recovery is "recovery clockwork" and "recovery RA". I tried apply them, but it's not work,may be i wrong in some thing, it's the first time i use android phone . throught usb, i have "fastboot usb"
please help me
http://wiki.cyanogenmod.com/wiki/Nexus_One:_Full_Update_Guide
but my phone cant connect with PC, atlthough i installed google usb driver.
i might be wrong but cant you just flash a original ruu, than root and reinstall recovery
#1)Go and download yourself a recovery.img file that is compatible with your device and put the image on the root of your SD card (that means on the main directory and not in a folder)
#2)Make sure you have a terminal emulator application installed from the market on your phone. If you don't...install one now.
#3)Open up your terminal and type in
Code:
su
to gain root access. If you are root the next line should show the
Code:
# symbol
#4)At the next line type in
Code:
flash_image recovery /sdcard/name-of-recovery.img
you will need to replace the code that says name-of-recovery.img with the exact name of the file on your SD card.
#5)Hit enter, wait a few seconds and viola ! you have a recovery again.
Good luck man.
hxq88 said:
but my phone cant connect with PC, atlthough i installed google usb driver.
Click to expand...
Click to collapse
Try the driver from this thread.
It helped me set up my ADB for the N1
http://forum.xda-developers.com/showthread.php?t=613217
#2)Make sure you have a terminal emulator application installed from the market on your phone. If you don't...install one now.
you mean install terminal from android market? my phone stop working in android logo screen, i cant do anything in android OS, include enable debugging?
I need restore my recovery mode, and my prolem is Pc cant see phone
hxq88 said:
#2)Make sure you have a terminal emulator application installed from the market on your phone. If you don't...install one now.
you mean install terminal from android market? my phone stop working in android logo screen, i cant do anything in android OS, include enable debugging?
I need restore my recovery mode, and my prolem is Pc cant see phone
Click to expand...
Click to collapse
Did you have ADB working before? Try using the driver from the link I posted.
Have you tried the passimg method?
baseballfanz said:
Did you have ADB working before? Try using the driver from the link I posted.
Have you tried the passimg method?
Click to expand...
Click to collapse
i typed ADB devices on command prompt, it'show
View attachment 763802
and it's my driver after update from your link
View attachment 763803
what is passimg method, is the way rename room.zip => PASSIMG.zip
You did have debugging turn on correct?
Not sure what else to suggest except the passimg method, worth a shot.
Sent from my Transformer TF101 using Tapatalk
And... if you try to install a stock rom? When starts the HBOOT automatically detect the rom and ask to install. One time you've installed the rom, root & install recovery
I think that work because, It happens to me 1 week ago.
I tried everything, downloaded new adb , new cable, I tried win 8 and win 7 but nothing usb drivers and adb drivers are installed correctly , in device manager I see my usb driver (not yellow one)
When ever I put adb devices I can see my device and if I put adb shell it works but if I try adb push it says error device not found
I used to have sony xperia s, every thing used to work normally on it like fastboot and adb commands
Please help me it is so weird
Locked bootloader?
GROGG88 said:
Locked bootloader?
Click to expand...
Click to collapse
yes
i rooted my phone by flashing older kernel and rooting then upgrade to the newer kernel , nothing happened while i was flashing all went right , no errors , but the problem at adb is still there , can't push any file , also flash tool sends a file to a rooted phone called : ftkit the first time u connect your phone with root , it didn't push the file to the phone ,
very weird problem
elias234 said:
i rooted my phone by flashing older kernel and rooting then upgrade to the newer kernel , nothing happened while i was flashing all went right , no errors , but the problem at adb is still there , can't push any file , also flash tool sends a file to a rooted phone called : ftkit the first time u connect your phone with root , it didn't push the file to the phone ,
very weird problem
Click to expand...
Click to collapse
Have you granted superuser access to adb?
GROGG88 said:
Have you granted superuser access to adb?
Click to expand...
Click to collapse
yes i granted superuser access to adb
i want to ask a question .
when i need to push files to my phone i directly enter the commend " adb push "
ot first i need to enter adb shell ?
Push is not used within shell. Shell is basically used to start a terminal emulator. Push/pull is used within cmd or terminal to treat your device as a remote location.
Sent from my C6603 using XDA Premium 4 mobile app
I rooted my HTC one after downloading a custom Rom it left me in a bootloop I tried adb sideload from twrp but my pc doesnt detect my device. I do have adb drivers installed. also tried the fastboot option also doesn't detect my phone. Pls help
If you can boot into TWRP, try to mount your internal storage as MTP (see here for a description). You could then load a different ROM onto the phone and then flash it.
To get fastboot to work, download the latest HTC Sync program, install it, but then uninstall it leaving the drivers. When you boot your phone into fastboot and plug it in, it should switch from "fastboot" in red to "fastboot usb" and hopefully it will then be recognized.
maybe he needs to flash the boot.img, if he's s-on, just my 2 cents
shooter7201 said:
I rooted my HTC one after downloading a custom Rom it left me in a bootloop I tried adb sideload from twrp but my pc doesnt detect my device. I do have adb drivers installed. also tried the fastboot option also doesn't detect my phone. Pls help
Click to expand...
Click to collapse
What rom are you trying to flash? If it's not from the Sprint forum it's most likely a GSM rom and does not have Sprint support.
That will cause your phone to react like you are talking about.
ADB Sideload 99 time out of 100 will not work.
Use adb push FileName.zip /sdcard/ to move files to your phone while in recovery.
As for the drivers try this:
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Hi,
My One M7 started malfunctioning all of the sudden and now cannot boot android and stuck at HTC splash screen.
I would like to recover contacts and data(pdfs, images) from the phone.
The device is not-rooted, locked(as it seems in bootloader) and stock rom is installed.
On my PC drivers are installed(ADB mode) and ADB, FastBoot up-to-date.
When I'm in HBOOT 1.61 I choose fastboot mode and I plug the phone via USB2 to the Win10 machine.
I can see fastboot USB in red and send the command
Code:
fastboot devices
it returns the serial of my device.
But when i try
Code:
adb devices
command i get empty list.
So i cannot backup.
I also tried to
unplug USB and plug it back in
Code:
adb kill-server
Code:
adb start-server
Code:
adb devices
But still get empty list of devices.
Also tried the recovery option in bootloader but I get empty list of devices for both
Code:
fastboot devices
Code:
adb devices
How can I backup my data?
Is it possible to unlock the device from bootloader install custom recovery(with backup features) without losing data?
Any help is much appreciated!
minamoto19 said:
Hi,
My One M7 started malfunctioning all of the sudden and now cannot boot android and stuck at HTC splash screen.
I would like to recover contacts and data(pdfs, images) from the phone.
The device is not-rooted, locked(as it seems in bootloader) and stock rom is installed.
On my PC drivers are installed(ADB mode) and ADB, FastBoot up-to-date.
When I'm in HBOOT 1.61 I choose fastboot mode and I plug the phone via USB2 to the Win10 machine.
I can see fastboot USB in red and send the command
Code:
fastboot devices
it returns the serial of my device.
But when i try
Code:
adb devices
command i get empty list.
So i cannot backup.
I also tried to
unplug USB and plug it back in
Code:
adb kill-server
Code:
adb start-server
Code:
adb devices
But still get empty list of devices.
Also tried the recovery option in bootloader but I get empty list of devices for both
Code:
fastboot devices
Code:
adb devices
How can I backup my data?
Is it possible to unlock the device from bootloader install custom recovery(with backup features) without losing data?
Any help is much appreciated!
Click to expand...
Click to collapse
You don't say what version of ADB you're using. Try this version, worked for me on W10
http://minimal-adb-and-fastboot.software.informer.com/1.1/
http://external.informer.com/forum.xda-developers.com/showthread.php?p=42407269#post42407269
Adb works ONLY in booted ROM or custom recovery. So, you can only use fastboot when in bootloader. Also, unlocking bootloader will erase all your data, so that's not a good idea
minamoto19 said:
Hi,
My One M7 started malfunctioning all of the sudden and now cannot boot android and stuck at HTC splash screen.
I would like to recover contacts and data(pdfs, images) from the phone.
The device is not-rooted, locked(as it seems in bootloader) and stock rom is installed.
On my PC drivers are installed(ADB mode) and ADB, FastBoot up-to-date.
When I'm in HBOOT 1.61 I choose fastboot mode and I plug the phone via USB2 to the Win10 machine.
I can see fastboot USB in red and send the command
Code:
fastboot devices
it returns the serial of my device.
But when i try
Code:
adb devices
command i get empty list.
So i cannot backup.
I also tried to
unplug USB and plug it back in
Code:
adb kill-server
Code:
adb start-server
Code:
adb devices
But still get empty list of devices.
Also tried the recovery option in bootloader but I get empty list of devices for both
Code:
fastboot devices
Code:
adb devices
How can I backup my data?
Is it possible to unlock the device from bootloader install custom recovery(with backup features) without losing data?
Any help is much appreciated!
Click to expand...
Click to collapse
Like said above, ADB commands only works from a custom recovery or from a booted rom with USB debug turned on.
Unlocking the bootloader will wipe the phone for obvious security reasons: anyone could simply unlock the bootloader and flash a recovery to extract data from anyone's phone.
If the phone isn't booting to the OS and your bootloader wasn't already unlocked, your data are lost, sorry. Thats why you should sync your important files or make regular backup on a computer.
You might be able to recover your phone using a RUU or by unlocking the bootloader and flashing a recovery + rom but again your data is lost.
alray said:
Like said above, ADB commands only works from a custom recovery or from a booted rom with USB debug turned on.
Unlocking the bootloader will wipe the phone for obvious security reasons: anyone could simply unlock the bootloader and flash a recovery to extract data from anyone's phone.
If the phone isn't booting to the OS and your bootloader wasn't already unlocked, your data are lost, sorry. Thats why you should sync your important files or make regular backup on a computer.
You might be able to recover your phone using a RUU or by unlocking the bootloader and flashing a recovery + rom but again your data is lost.
Click to expand...
Click to collapse
Well I somehow made it to kernel.
When the device boots it show me a message of:
"Please wait while android is updating" or something similar.
After 10 secs or less the android boots as normal but after a couple of minutes the phone freezes like the first time.
The good thing is that adb devices returns the device id.
I tried to:
Code:
adb backup -f backup.ab -all
I can see that the backup starts but it cant finish before the device hangs.
It freezes around 1GB of filesize. I turn it off by pushing the power button for 10-15 secs and after that the device wont turn on at all.
I have to wait for a couple of hours before the device responds again.
Next try was:
Code:
adb backup -f backup.ab -shared -nosystem
Although the phone hangs and not responding the backup was complete.
Now I'm ready to do a factory reset, but I would like to know whats included in "shared" option for a non-rooted phone.
Will I lose the contacts and gallery after all or have been backed up?
minamoto19 said:
Now I'm ready to do a factory reset, but I would like to know whats included in "shared" option for a non-rooted phone.
Will I lose the contacts and gallery after all or have been backed up?
Click to expand...
Click to collapse
I never had to use adb backup commands since I always make regular backups using twrp. Maybe someone else can answer this one.
Here is a guide that I just found, might give you some info you are looking for.
http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351
alray said:
I never had to use adb backup commands since I always make regular backups using twrp. Maybe someone else can answer this one.
Here is a guide that I just found, might give you some info you are looking for.
http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351
Click to expand...
Click to collapse
Thanks for the link.
The first post is pretty much explaining the adb manual (adb help command)
Some of the posters reported that -shared option backed up the contacts.
Anyway I'll have to check it myself.
I have ran into a bit of an odd problem due to me messing up a root and then messing my phone up even more while trying to fix it.
my phone is fully bricked and only boots into fastboot mode. i tried to fix it with the one-plus fixer (idk its official name) but i got an error 7. I now need to re flash an older version of TWRP and try a diffrent method but i cant as my phone no longer is recognized in fastboot using the ADB tool. I have the USB driver installed on Windows. On Linux i ran the .sh script as root and it still doesn't work.
I have both Ubuntu and Windows installed on my PC so i can do whatever you suggest me to do regardless of the os.
Thank you to anyone that can help in advanced
Malte
This is not a hardbrick; a hard one wouldn't boot at all and give no sign of life (except when plugged to PC).
Try an unbrick tool to revert to official OOS. On Windows 7+ remember to disable signed driver enforcement.
You mention fastboot and adb. Which one are you using?
Just to make sure: While in the bootloader (fastboot mode), adb does not work. You have to use the fastboot commands. Installing TWRP would be:
Code:
fastboot flash recovery <name-of-img-file>
If that's what you're already trying, just ignore this post.
I want to be able to do that but if i do adb devices it no longer finds my phone
Didgeridoohan said:
You mention fastboot and adb. Which one are you using?
Just to make sure: While in the bootloader (fastboot mode), adb does not work. You have to use the fastboot commands. Installing TWRP would be:
Code:
fastboot flash recovery <name-of-img-file>
If that's what you're already trying, just ignore this post.
Click to expand...
Click to collapse
I want to be able to do that but if i do "adb devices" in the cmd/terminal it no longer finds my phone. so my goal is to be able to execute that command. However, i may be mistaken that it doesnt need to find my phone i can just execute that command
Ive done this but it didnt fix my phone.
przemcio510 said:
This is not a hardbrick; a hard one wouldn't boot at all and give no sign of life (except when plugged to PC).
Try an unbrick tool to revert to official OOS. On Windows 7+ remember to disable signed driver enforcement.
Click to expand...
Click to collapse
I did this last night but it never fixed my phone. it boots and then says "md5 checksum error" so im needing to try a diffrent approach but i cant because i cant flash anything onto it due to adb not finding my device now
Bandella said:
I want to be able to do that but if i do "adb devices" in the cmd/terminal it no longer finds my phone. so my goal is to be able to execute that command. However, i may be mistaken that it doesnt need to find my phone i can just execute that command
Click to expand...
Click to collapse
Like I said, the adb commands won't work while in the booloader (that's why it's called fastboot mode). You need to use fastboot commands... The equivalent command would be:
Code:
fastboot devices
Bandella said:
I did this last night but it never fixed my phone. it boots and then says "md5 checksum error" so im needing to try a diffrent approach but i cant because i cant flash anything onto it due to adb not finding my device now
Click to expand...
Click to collapse
I had the same issues with md5, all you have to do is try a different USB port. I suggest the ones on your motherboard if you're on a PC. Then run the tool as administrator. I hope this helps, good luck!
P.S if it still doesn't work, try a different PC, I'm 100% sure it'll work
Bandella said:
I want to be able to do that but if i do "adb devices" in the cmd/terminal it no longer finds my phone. so my goal is to be able to execute that command. However, i may be mistaken that it doesnt need to find my phone i can just execute that command
Click to expand...
Click to collapse
As Didgeridoohan touched upon, adb and fastboot (while related) are different. They have different requirements and applications.
adb won't work while the device is in fastboot mode. Conversely, when the device is able to use adb, fastboot commands won't work.
adb: only works booted to OS or alternately in TWRP. Debugging must be enabled
fastboot: only works in bootloader-fastboot mode. Debugging is not required to be enabled.
For flashing TWRP, it's fastboot that you need. Well, there is a way to do it with adb, but fastboot is by far the more common way.
When in fastboot mode, adb command won't work, and there fore it is completely expected that "adb devices" yields not response. Try "fastboot devices" (no quotes) and if you get the phone's ID in response, you are in business.
Bandella said:
...
my phone ... only boots into fastboot mode...
Click to expand...
Click to collapse
I've had this happen to me when I've triggered dm-verity. Instead of getting the dm-verity warning display the phone would simply boot straight back to fastboot.
My solution was to:
- flash the latest TWRP using
Code:
fastboot flash recovery <recovery file. img>
- reboot into recovery (use the volume keys on the phone to select recovery and then press the power key)
-flash the full stock image I was using before the problem started
This would clean up any changes made to the boot and system images and allow me to boot the system normally.
Note: because this leaves you with a stock kernel you'll end up with the stock recovery after you boot the system.
Sent from my OnePlus3T using XDA Labs
boot your PC into Ubuntu and install adb/fastboot (tons of guides available off the 'net). then boot your 3t to dl mode and connect it to your PC. as mentioned already "fastboot devices" should list your 3t and you should now be able to flash to your heart's content. no need for drivers, unlike under Windows. i have a bootable linux usb drive primarily for this reason. curious what script you're trying to run though..