Related
I achieved the unlocked bootloader, at least I believe, per instructions via the HTC website. But I can't seem to be able to flash a recovery or achieve root. I can boot into HBOOT, when I try to click Recovery, it takes me to some page explaining software is not to be distributed, blah blah. Then it just boots up like normal?
I'm afraid I don't understand? Everything i've tried fails, why is that?
New Jer-Z said:
I achieved the unlocked bootloader, at least I believe, per instructions via the HTC website. But I can't seem to be able to flash a recovery or achieve root. I can boot into HBOOT, when I try to click Recovery, it takes me to some page explaining software is not to be distributed, blah blah. Then it just boots up like normal?
I'm afraid I don't understand? Everything i've tried fails, why is that?
Click to expand...
Click to collapse
You skipped right over the "can't seem to able to flash a recovery."
Please explain in detail the instructions you followed AFTER unlocking via HTCdev.com. This includes files you downloaded, where you put them, how you attempted to flash, etc.
These details will be very helpful. Don't worry, sounds like you're not in any serious trouble at all. Just don't go flashing anything you see.
Also, please post this to the Q&A forum or General next time. This development forum is intended for development posts ONLY (ie. ROMs, Kernels, Radio's, etc). Just a heads up. Welcome to the forums
Aahhh, forgive me!
And thank you for the patience and understanding!
I used the Hasooon2000 toolkit. I got as far as getting to the screen where HTC wants to confirm with me that I do want to unlock the bootloader, I clicked yes, and it rebooted. Then I tried to flash recovery. The CMD prompt will say it was pushed to the phone successfully, but when I try to reboot into recovery, I don't get very far. To my understanding, I can't apply perm root without getting to recovery, but with the bootloader unlocked, why can't I even flash one?
Moved To Q&A
Please post all questions in the Q&A section
New Jer-Z said:
Aahhh, forgive me!
And thank you for the patience and understanding!
I used the Hasooon2000 toolkit. I got as far as getting to the screen where HTC wants to confirm with me that I do want to unlock the bootloader, I clicked yes, and it rebooted. Then I tried to flash recovery. The CMD prompt will say it was pushed to the phone successfully, but when I try to reboot into recovery, I don't get very far. To my understanding, I can't apply perm root without getting to recovery, but with the bootloader unlocked, why can't I even flash one?
Click to expand...
Click to collapse
Ahhh, not to stir up the pot here, but you're getting vague again with what's going on. You say "when I try to reboot into recovery, I don't get very far". What do you mean by this? Details are extremely important in helping you. Sounds like you're saying that recovery was successfully pushed, but then I didn't get any details as to what's going on when you attempt to load recovery. Also, which recovery file did you use? Use this one
I'm not trying to get on to your case here, but you've got to be really specific when you say stuff doesn't work, because that doesn't help us diagnose your issue. When your recovery is done flashing, you should be able to access the bootloader by holding Pwr + Vol-Down for like 5 secs, then choose recovery (that or fastboot>recovery....I cant recall if recovery is a main menu item). What happens after you choose that? Mine shows the htc splash screen, with a development message in red, and then it boots Clockworkmod.
No, no, lol I totally understand, I guess I am being vague.
I was going to go into details, but I was at work. Interestingly enough, my phone died, and when I plugged it and let it charge for a little bit, the phone booted right into CWM touch - so odd! So I was like, ok, i've achieved root - well, no, cuz I opened ROM Manager and it says SU couldn't be found.
BEFORE, when I would do what you said I should do, it would take me to the HTC splash screen where it was in red text, some disclaimer about some proprietary information crap, then it would skip recovery and just boot into Android -___-
Let's see if I can replicate booting into recovery now. (What method are you using to flash your recoveries?)
EDIT: Well it looks like I can't get back into recovery. Same thing as mentioned above. I can get to the fastboot screen, but if I click recovery, it takes me to that HTC disclaimer screen, the little loading bar loads then - poof - screen goes blank and Android boots up.
I have the same problem -_-! Can someone help please
The recovery image was flashed succesfully from Hasoon2000's toolkit. But when i go to the bootloader and select Recovery, I get the red warning for from HTC about how this is for development purpose only... then the phone's screen goes black, then it boots into the stock ROM.
Cant flash recovery
Hello everyone.
I have a similar problem. I successfully proceeded with the bootloader, but now I can't install the recovery. It simply wont flash.
I was following the xda tutorial that's in this very forum, but i got stuck: In my desktop i downloaded the needed files (or so I believe), and so i have in my desktop a folder called "carpeta" (random name) with these files within: adb.exe, adbwinapi.dll, fastboot and 3 different recovery images i have tried to flash.
I use mac, so i open the command prompt for mac (terminal) and go to the "carpeta" folder and after that, I type "cd fastboot flash recovery xxxxx.img" (the xxx are the names of the recovery images that i have in the folder, one at a time) but it simply wont flash anything. I attach a screenshot to ilustrate what happens...
Please help me
http :// img710.imageshack.us/img710/6026/capturadepantalla201205.png
Guys it works if you flash the recovery manually through the command prompt. I think there might be a bug or something in the toolkit because the manual way worked for me.
Here is what I did:
(I am not a programmer so I can't guarantee this will work for you. Worked for me, but try at your own risk)
-Copied the recovery image to the same folder as abd
-Plugged in the phone with USB debugging on
-Opened command prompt
-navigated to the folder with adb with "cd folder_location"
-typed: "adb kill-server", then "adb devices"to make sure the device was connected
-typed "adb reboot-bootloader" to boot into bootloader
-typed "fastboot flash recovery recovery_file_name.img"
-Select bootloader>recovery using the vol up and down and pwr button
and voila recovery
Hope this helps
I'll give it a shot later tonight on my lunch break.
batiste93 said:
Guys it works if you flash the recovery manually through the command prompt. I think there might be a bug or something in the toolkit because the manual way worked for me.
Here is what I did:
(I am not a programmer so I can't guarantee this will work for you. Worked for me, but try at your own risk)
-Copied the recovery image to the same folder as abd
-Plugged in the phone with USB debugging on
-Opened command prompt
-navigated to the folder with adb with "cd folder_location"
-typed: "adb kill-server", then "adb devices"to make sure the device was connected
-typed "adb reboot-bootloader" to boot into bootloader
-typed "fastboot flash recovery recovery_file_name.img"
-Select bootloader>recovery using the vol up and down and pwr button
and voila recovery
Hope this helps
Click to expand...
Click to collapse
tried unsuccessfully.
on screen this is what I see in my htc one s:
***unlocked***
vle put ship s-on rl
radio- o.15.315018.19_2
opendsp-v21.1.0.32.0314
emmc-boot
mar 15 2012.23:37:23
fastboot usb
bootloader
reboot
reboot bootloader
powerdown
------------------
and each time i try to flash the recovery, i get a "not a directory" or "no such file or directory" message...
alexjuanes said:
tried unsuccessfully.
on screen this is what I see in my htc one s:
***unlocked***
vle put ship s-on rl
radio- o.15.315018.19_2
opendsp-v21.1.0.32.0314
emmc-boot
mar 15 2012.23:37:23
fastboot usb
bootloader
reboot
reboot bootloader
powerdown
------------------
and each time i try to flash the recovery, i get a "not a directory" or "no such file or directory" message...
Click to expand...
Click to collapse
Make sure that you navigate to the proper folder using the "cd" command.(for example" cd C:\Fastboot ", if your adb and recovery are in that location)
Make sure that the Clockwork Mod recovery file is in the same folder as the adb and make sure that you type the file name correctly
I used these file and put the recovery image inside the folder after unzipping
http://www.mediafire.com/?50baad8rykng2j0
Here is the recovery I used :
http://loadbalancing.modaco.com/download.php?file=r2-modaco-recovery-clockwork-touch-ville.img
But your running Mac so I don't know if the method I used will work for you because I'm on Windows
Doesnt work...
I have the bootloader (when i start in bootloader mode my phone says ***tampered*** and also ***unlocked***.
BUT
I've been 2 days trying to flash my recovery on my htc one s from my macbook, and after i use the command prompt to get to the folder where i have adb, fastboot, my recovery .img file,etc... this is what happens:
-----
MacBook-Pro-de-Alejandrolatform-tools alexjuanes$ fastboot flash recovery r2-modaco-recovery-clockwork-touch-ville.img
-bash: fastboot: command not found
MacBook-Pro-de-Alejandrolatform-tools alexjuanes$
-----
ive already updated all that i could in the sdk manager, or whatever its name is...
please some help?
batiste93 said:
Guys it works if you flash the recovery manually through the command prompt. I think there might be a bug or something in the toolkit because the manual way worked for me.
Here is what I did:
(I am not a programmer so I can't guarantee this will work for you. Worked for me, but try at your own risk)
-Copied the recovery image to the same folder as abd
-Plugged in the phone with USB debugging on
-Opened command prompt
-navigated to the folder with adb with "cd folder_location"
-typed: "adb kill-server", then "adb devices"to make sure the device was connected
-typed "adb reboot-bootloader" to boot into bootloader
-typed "fastboot flash recovery recovery_file_name.img"
-Select bootloader>recovery using the vol up and down and pwr button
and voila recovery
Hope this helps
Click to expand...
Click to collapse
This actually worked for me. I am rooted, and am now running a custom ROM.
Thanks so much for all your help!
Hey everyone
i seem to have made a very tiny bit of progress here since now i can type the commands and make it start, but only that... starting.
my command box is stuck in a "waiting for device" message that will start nothing, and my phone is just there, untouched.
i never thought flashing a recovery would give me this much of a long headache...
help anyone? how do i make my pc stop "waiting for device"?
Have you tried a different USB cable/port? I had a similar problem but moving to a different port worked.
Sent from my HTC VLE_U
I have the same problem i did everything as in the guide posted here http://forum.xda-developers.com/showthread.php?t=1583427
But when i flash recovery through fastboot ( fastboot flash recovery recoveryname.img) everything goes ok but when i want to boot into recovery i get stuck on the HTC screen.
Than i wanted to go to recovery trough fastboot ( fastboot boot recovery ) i get message cannot load recovery.
If you need more info for help i can provide you guys with the screenshots.
Thanks in advance Nikola.
Okay, first of all I know, I'm a total noob. I have followed these forums a long time and have successfully rooted a few phones. One of which was my nexus s 4g. I was trying to unroot the phone so I could get ics. This is when I ran into problems and right now I just want to be able to get my phone working again. Right now I am stuck on the Miui boot up screen and no matter how long I wait it stays on that screen. If I do a battery pull and hold down power and vol up I can get into the bootloader screen with the information as follows: fastboot mode, product name-Herring, HW Version Rev 34, Bootloader version-D720SPAKE1, Baseband version-D720SPAKE1, Carrier info, SPR, serial number-37308B81276A00EC, Lock State-locked. Then the different options I can choose are reboot bootloader, reboot, recovery, power off. If I choose reboot, it takes me back to the mius screen and stays there. If I choose recovery, I get the triangle with the exclamation point. I then hold power and up volume again and I get a screen that says Android system recovery <3e> with reboot system now, apply update from sd card wipe data/factory reset and wipe cache partition. I have tried all of these as well with no luck. When I go to apply update from sd card I get matrix-cfs_v15.5 zip, root.zip, update.zip and then what looks like apps such as Alarms/, Android/,MIUI?, etc. If I try to select any of the first ones such as matrix-cfs_v15.5 zip, I get Install /sdcard... , finding update package..., opening update package..., verifying update package..., E.signature verification failed, Installation aborted. Then it gives me the system recovery options again. Any help would be appreciated.
Did you try ADB fastboot method?
Not sure how to try that
I tried doing the adb, followed all directions and installed and when I go to the command prompt and type in anything, such as, adb reboot bootloader I get, adb is not recognized as an internal or external command, operable program or batch file.
ok I got that working now but when I type adb devices and press enter I get a message saying List of devices attached and then it doesn't show anything and I get the command prompt again saying:c:\android\android-sdk\platform-tools>
also since the phone is stuck in either the miui screen or bootloader I can't get into it to put it in usb debugging mode. I am trying on my own to get this going and am stuck any and all help would be very much appreciated.
TerryUK98 said:
Lock State-locked.
Click to expand...
Click to collapse
I think that means you have a locked bootloader.
And from what you're telling, I believe you have stock recovery.
Also, when you're in fastboot mode, I don't think adb commands apply. Use fastboot commands instead (i.e. fastboot devices).
Search for guides showing you how to install and use fastboot.
I did fastboot as well and the problem I think I am having is it's not recognizing my phone because usb debugging wasn't turned on before it locked up. How would I get it to recognize my phone or download an img to my phone if it is not being recognized. Sorry if this is a stupid question.
You don't need usb debugging in fastboot mode.
You either:
1. Don't have drivers installed.
2. Don't have fastboot installed correctly.
You really need to read a guide or two, through and thoroughly.
Bc it sounds like you have no clues.
Yeah dude. Take a step back and go over what you have installed and where you installed it.Yes, fastboot commands start with fastboot instead of adb. And you're on stock recovery.
Thanks for the answer that I don't need usb debugging in fastboot mode, I wasn't sure of that. I have downloaded and installed my drivers multiple times and when I use the device manager to update drivers it says I have the latest drivers installed already. Whenever I do fastboot commands I will type in fastboot devices and shouldn't my device serial number come up? It just gives me the line c:\android\android-sdk\platform-tools>
And is waiting on me to type a command in. And yes I have been looking at guides all night. I appreciate any help you guys might have and remember we were all noobs at one time.
The zip in this tutorial should help.
It has adb, fastboot, and the drivers needed.
And unlock the bootloader because it is locked.
Finally got it, I had everything downloaded that I needed already, but looking at different forums, etc, it seemed like everyone named it something different. So I just used the one link you gave me and did it exactly the same way and it worked. Thanks so much! and again thanks for your patience.
I just rooted my phone last night. I tried to flash cynanogen 10 and forgot to back up the the stock rom. I haven't done this since my last phone. But I got stuck at the cynanogen bootloader screen. I tried to get back to recovery mode but it won"t go. Can someone please help me and give very detailed instructions to get my phone unbricked pleeeeease? I don"t want to to buy another phone. Thank you.
How long did u wait at boot logo screen first boot can take a while and did u flash boot. Img? Are u t mob?
Sent from a man, using a mobile phone
1. Wipe
2. Flash
3. Wipe cache
4. Fastboot boot.IMG
5. Boot
6. Reboot
7. Flash gapps
8. Wipe cache
9. Enjoy the speed
Note this method will only work for hboot under 1.13
k1llacanon said:
How long did u wait at boot logo screen first boot can take a while and did u flash boot. Img? Are u t mob?
Sent from a man, using a mobile phone
Click to expand...
Click to collapse
All I know is that I downloaded the ROM from here, used CWM to flash it on, phone said update installed and rebooted the phone. I waited for an hour and it still did nothing past the bootload screen. Also, yes I'm t-mobile.
Fredfly said:
1. Wipe
2. Flash
3. Wipe cache
4. Fastboot boot.IMG
5. Boot
6. Reboot
7. Flash gapps
8. Wipe cache
9. Enjoy the speed
Note this method will only work for hboot under 1.13
Click to expand...
Click to collapse
If I can't get into recovery, how do I do this, or what can I use to do this?
Fredfly said:
1. Wipe
2. Flash
3. Wipe cache
4. Fastboot boot.IMG
5. Boot
6. Reboot
7. Flash gapps
8. Wipe cache
9. Enjoy the speed
Note this method will only work for hboot under 1.13
Click to expand...
Click to collapse
I have hboot 1.14
Can get ur phone into bootloader mode or fastboot...if yea...then u cn save ur phone...i faced the same problem some days back...and successfully recovered my phone and nw i am using energy rom...
Sent from my HTC VLE_U using xda app-developers app
Okay, let's try something.
Check your drivers on the PC, make sure you have ADB (from Android SDK or other sources).
Power on the phone, plug it in the PC.
Check if any drivers are installing/updating. Also check Device Manager to see if the device is seen in there.
If the PC sees the phone, open a cmd window and navigate to the directory where you have ADB (if using the android SDK, it should be in the tools folder of the installation directory).
In the cmd window, once in the directory containing the ADB, type "adb devices". You should see something about adb server stopping and starting, than, if everything alright, you should see the device as a number.
If you can see your phone, that means you're saved. Just run the command "adb reboot bootloader" and you're good to go.
If the phone cannot be seen by the PC, try and boot the phone holding vloume - pressed, try this with volume + too. Or simply google on how to boot the phone in bootloader mode.
Once in bootloader, again, you're saved. You can go ti fastboot usb mode and from there, do whatever you need to do.
Ruwin said:
Okay, let's try something.
Check your drivers on the PC, make sure you have ADB (from Android SDK or other sources).
Power on the phone, plug it in the PC.
Check if any drivers are installing/updating. Also check Device Manager to see if the device is seen in there.
If the PC sees the phone, open a cmd window and navigate to the directory where you have ADB (if using the android SDK, it should be in the tools folder of the installation directory).
In the cmd window, once in the directory containing the ADB, type "adb devices". You should see something about adb server stopping and starting, than, if everything alright, you should see the device as a number.
If you can see your phone, that means you're saved. Just run the command "adb reboot bootloader" and you're good to go.
If the phone cannot be seen by the PC, try and boot the phone holding vloume - pressed, try this with volume + too. Or simply google on how to boot the phone in bootloader mode.
Once in bootloader, again, you're saved. You can go ti fastboot usb mode and from there, do whatever you need to do.
Click to expand...
Click to collapse
Ok, I downloaded the sdk and my computer recognizes the phone, and I can get into recovery mode, I did a factory reset but it did nothing.
Ruwin said:
Okay, let's try something.
Check your drivers on the PC, make sure you have ADB (from Android SDK or other sources).
Power on the phone, plug it in the PC.
Check if any drivers are installing/updating. Also check Device Manager to see if the device is seen in there.
If the PC sees the phone, open a cmd window and navigate to the directory where you have ADB (if using the android SDK, it should be in the tools folder of the installation directory).
In the cmd window, once in the directory containing the ADB, type "adb devices". You should see something about adb server stopping and starting, than, if everything alright, you should see the device as a number.
If you can see your phone, that means you're saved. Just run the command "adb reboot bootloader" and you're good to go.
If the phone cannot be seen by the PC, try and boot the phone holding vloume - pressed, try this with volume + too. Or simply google on how to boot the phone in bootloader mode.
Once in bootloader, again, you're saved. You can go ti fastboot usb mode and from there, do whatever you need to do.
Click to expand...
Click to collapse
It keeps telling me device not ready
marcus8141981 said:
I just rooted my phone last night. I tried to flash cynanogen 10 and forgot to back up the the stock rom. I haven't done this since my last phone. But I got stuck at the cynanogen bootloader screen. I tried to get back to recovery mode but it won"t go. Can someone please help me and give very detailed instructions to get my phone unbricked pleeeeease? I don"t want to to buy another phone. Thank you.
Click to expand...
Click to collapse
I git it fixed. I thank everyone for their help.
marcus8141981 said:
It keeps telling me device not ready
Click to expand...
Click to collapse
Can you give me more details? Where do you see that message and when exactly? Maybe an ADB logcat?
If you can get into fastboot usb, you can easily google for flashing solutions using fastboot.
always good to say how you fixed it for others who may have similar issue--
Ruwin said:
Okay, let's try something.
Check your drivers on the PC, make sure you have ADB (from Android SDK or other sources).
Power on the phone, plug it in the PC.
Check if any drivers are installing/updating. Also check Device Manager to see if the device is seen in there.
If the PC sees the phone, open a cmd window and navigate to the directory where you have ADB (if using the android SDK, it should be in the tools folder of the installation directory).
In the cmd window, once in the directory containing the ADB, type "adb devices". You should see something about adb server stopping and starting, than, if everything alright, you should see the device as a number.
If you can see your phone, that means you're saved. Just run the command "adb reboot bootloader" and you're good to go.
If the phone cannot be seen by the PC, try and boot the phone holding vloume - pressed, try this with volume + too. Or simply google on how to boot the phone in bootloader mode.
Once in bootloader, again, you're saved. You can go ti fastboot usb mode and from there, do whatever you need to do.
Click to expand...
Click to collapse
I do that and my phone just keeps flickering and goes back in to cwm recovery. Please any ideas?
Hello.
Earlier today I wanted to try a new JB rom to replace ICS so I transfered it into SD card and tried to reboot into recovery.
Instead of getting to recovery, I got stuck in fastboot mode, so I'm assuming recovery has been damaged.
After a whole afternoon of researching this forum I tried for several times this tutorial in order to install a recovery and afterwards a ROM (http://forum.xda-developers.com/showthread.php?t=1088046) and similar ones in both Mac OS X and Windows 7 (tried both USB 2.0 and USB 3.0 so its not a problem from USB) and I didn't succeed at all.
When I am using Windows 7, when I use "fastboot erase recovery", I keep receiving this message "waiting device". If I write "fastboot devices", I don't get results.
When using Mac OS X, I can get via command line to the folder "platform-tools" where fastboot is located but if I write "fastboot erase recovery" or something, it says "command not found". I've read it could be because I have to set fastboot as an environmental variable, but I having trouble setting it (Mac OS Lion).
Thank you so much for reading. Please help me!!! Any clues would be really appreciated!
-----
UPDATE: I finally managed to communicate with the device.
I used the following commands from this tutorial http://androidforums.com/optimus-m-all-things-root/382525-guide-get-out-fastboot-mode-2.html
fastboot erase boot
fastboot erase recovery
fastboot erase system
fastboot flash recovery
The problem is, now I'm stuck at LG Logo, can't access fastboot... Please help, I think it's even worse now.
boot rom, pull out battery and boot normal, it does or not? if it does use terminal emulator or adb push to install custom recovery, adb will work in fastboot if you had checked android debugging
http://forum.xda-developers.com/showthread.php?t=1007244
http://forum.xda-developers.com/showthread.php?t=1146566
grigtm said:
boot rom, pull out battery and boot normal, it does or not? if it does use terminal emulator or adb push to install custom recovery, adb will work in fastboot if you had checked android debugging
http://forum.xda-developers.com/showthread.php?t=1007244
http://forum.xda-developers.com/showthread.php?t=1146566
Click to expand...
Click to collapse
I don't understand what you mean by boot rom. Every time I turn on the phone, (normal or as POWER+HOME+VOL DOWN) it goes into fastboot. When I pull out the battery, and power again it goes again into fastboot...
techdani said:
I don't understand what you mean by boot rom. Every time I turn on the phone, (normal or as POWER+HOME+VOL DOWN) it goes into fastboot. When I pull out the battery, and power again it goes again into fastboot...
Click to expand...
Click to collapse
ok, read here http://forum.xda-developers.com/showthread.php?t=1088046 do exactly what says in this thread
Hey folks!
Again a problem with my little phone.
Today I got similar reboots, after about 5 it got stuck at the bootscreen.
Tried to wipe cache+dalvik, booting it up again, but after it prepared all apps it stucks at the "Starting Apps" window..
Also flashed another kernel and recovery. Nothing worked so far..
Any help, because I don't want to wipe data because I made some important photos today and I don't wanna miss then..
Thanks in advance,
RS
RestlessScreams said:
Hey folks!
Again a problem with my little phone.
Today I got similar reboots, after about 5 it got stuck at the bootscreen.
Tried to wipe cache+dalvik, booting it up again, but after it prepared all apps it stucks at the "Starting Apps" window..
Also flashed another kernel and recovery. Nothing worked so far..
Any help, because I don't want to wipe data because I made some important photos today and I don't wanna miss then..
Thanks in advance,
RS
Click to expand...
Click to collapse
First of all you connect your phone to PC and try to copy all the content of /sdcard to your PC. If it doesn't work reboot your phone to fastboot and connect it to your PC with CMD (in fastboot folder) running and enter the command "adb pull /sdcard C:/" without quotes, Also you can replace C:/ to any address where you would like to copy all your SD data.
After that you can flash any ROM to get your device in working condition.
If you have any query do ask or you may end up losing all your data.
forgotter said:
First of all you connect your phone to PC and try to copy all the content of /sdcard to your PC. If it doesn't work reboot your phone to fastboot and connect it to your PC with CMD (in fastboot folder) running and enter the command "adb pull /sdcard C:/" without quotes, Also you can replace C:/ to any address where you would like to copy all your SD data.
After that you can flash any ROM to get your device in working condition.
If you have any query do ask or you may end up losing all your data.
Click to expand...
Click to collapse
Thanks for your tips, but like I said it's stuck in bootloop and I can't access it through pc.
Also adb won't work an yes, I've installed all drivers :b
RestlessScreams said:
Thanks for your tips, but like I said it's stuck in bootloop and I can't access it through pc.
Also adb won't work an yes, I've installed all drivers :b
Click to expand...
Click to collapse
Why don't you try the fastboot method.
Put your phone into Fastboot by pressing volume down+power button. Connect it to your PC, fastboot would recognize it for sure. You then enter the command. You can even use adb from fastboot.
forgotter said:
Why don't you try the fastboot method.
Put your phone into Fastboot by pressing volume down+power button. Connect it to your PC, fastboot would recognize it for sure. You then enter the command. You can even use adb from fastboot.
Click to expand...
Click to collapse
It just says "device not found" when using adb.
with fastboot I can flash things but can't pull or?
RestlessScreams said:
It just says "device not found" when using adb.
with fastboot I can flash things but can't pull or?
Click to expand...
Click to collapse
Is your boot loader unlocked, if not you'll have to unlock it first (but doing so will void your warranty).
Assuming that you have a unlocked device follow the steps below to get all your data. (I myself tried and it worked, so it must work on your device also)
1. Make sure you have installed drivers for your Moto G, if not then do it.
2. Download the adb file to access your phone during fast boot.
3. Download the TWRP recovery 2.7.0.0 by dhacker for falcon (Moto G) on your PC and copy it in the adb folder.
4. Rename the downloaded file to "recovery.img" without quotes.
5. Connect you phone in fastboot mode to your PC and flash the recovery by command "fastboot flash recovery recovery. img" without quotes.
7. On your phone then go to recovery option and press volume up key until phone vibrates. The phone will then go to recovery mode.
8. On your PC, in command prompt(adb) enter command "adb pull /data/media/0/ C:\Moto" without quotes. The process will start and may take hours depending on no's of file and their size.
P.S. I won't be able to answer any more of your question as I won't have data connection any more. I'm sure if you will follow all the steps properly, you will get all your data. If you can't understand anything then just Google it.
Phone doesn't proceed from boot animation!
Guys!
This would be my 1st time here. I've never faced any sort of problem with any of my android devices but this one.
My phone got lost a week back. So, I used "android device manager" to wipe/lock the phone but I think it didn't as the phone was switched off all this while.
So, some gentleman found my phone and returned it to me just today. I put it up for charging. It popped up 0% battery screen and turned on after 10-15min.
As soon as the boot animation(earth/buildings) finished it jumped to a black screen.
It has been on charging for last 3 hours.
So my questions are
1) Can I make back up of the data without turning it on/formatting it?
2) How can I make it to work?
Thanks a lot in advance!
vjsharma89 said:
Guys!
This would be my 1st time here. I've never faced any sort of problem with any of my android devices but this one.
My phone got lost a week back. So, I used "android device manager" to wipe/lock the phone but I think it didn't as the phone was switched off all this while.
So, some gentleman found my phone and returned it to me just today. I put it up for charging. It popped up 0% battery screen and turned on after 10-15min.
As soon as the boot animation(earth/buildings) finished it jumped to a black screen.
It has been on charging for last 3 hours.
So my questions are
1) Can I make back up of the data without turning it on/formatting it?
2) How can I make it to work?
Thanks a lot in advance!
Click to expand...
Click to collapse
@vjsharma89 :I have posted the answer in your thread.
And after you had backuped your data, factory reset your phone from fastboot by choosing factory option and then reboot it. Or should work fine.
delete this pls, wrong thread