Related
UPDATE: PROBLEM SOLVED
Hello,
I recently flashed a rom with a custom gapps that had themes, but one of the apps, G+, did not work since it was outdated. In an attempt to take the easy way out, I installed a "system app uninstaller"-app and used it to remove G+. It removed it, but I could not install G+. I decided to reboot the phone, but it took an abnormally long time amount to turn back on, stuck at the "Google" logo screen. I decided to reflash one of my previous backups.
My phone uses ClockworkMod Recovery v6.0.1.0 currently. After wiping data/factory reset and wiping the cache partition, I decided to restore one of my recoveries. It restored boot, system, but then failed to restore the /data with "Error while restoring /data!" popping up. I tried these steps again but with another backup, and the previous one before that, and none of them worked.
I did some research online, and learned that I could flashboot a stock recovery to my phone, so I attempted to do that; I noticed that when using the "adb devices" in the command prompt, no devices were listed.
If it makes a difference, I did not install the proper drivers for use of ADB since this computer is new. As of now, I can not boot my phone, and I can not access the files on my phone when connected through USB when attempting to use the "Mounts and Storage Menu" in CWM. Because of this, I can't use Fastboot to flash a stock recovery image from my current knowledge and self-research.
I now come to you guys for assistance; what other steps can I take that I haven't tried? Or perhaps have I done something incorrectly in my method?
If there is any other info needed, please let me know so I can reply with that information.
TL;DR - Can not use CWM to restore my backups (stuck at /data), cannot use fastboot because my GNex isn't listed on the adb devices, what should I do now?
Thank you for your time. (And sorry if this is not in the correct section)
Okay, so, first we need to fix your driver issue. I'm assuming you're on windows.
1. Boot to recovery, connect your device to the computer.
2. Download the driver here http://forum.xda-developers.com/showthread.php?t=1766220
3. Start menu>Right click computer> Properties> Device manager>Find your phone, right click, properties> Uninstall driver if any, then install the driver you downloaded.
4. Your phone should now appear as an ADB interface. Try ADB devices.
5. Now that ADB should be working, backup your SDcard. Type "adb pull /data/media/ SD". This will backup your SDcard to a folder named "SD" in the directory your ADB file is.
6. Now it's time to reflash the phone. Use ODIN. I'm sure someone can link you to ODIN images. If not, I can let you directly download them from me in the morning. I used the 4.0.2 images
7. Boot to odin (Phone powered off, hold Volume Down and power. Phone will say "Downloading...."
8. Flash the ODIN images with the ODIN program. Flash a PDA and PHONE file.
9. Once the phone boots up, turn it off, boot to the bootloader (Phone off, then Vol up and down, with power).
10. in your CMD, use "Fastboot devices". If the phone isn't detected, then update the driver of the device detected to the driver you downloaded.
11. If fastboot works, type "Fastboot oem lock", then reboot the phone.
12. Allow the 4.0.4 OTA to install.
13. Go back into the bootloader, and do "Fastboot oem unlock", then flash your recovery to CWM. (Download the .img from the website, and use "Fastboot flash recovery <filename>")
14. Boot the phone. Let it fully boot, then shut down and load bootloader again.
15. Boot to recovery, and restore your SDcard by typing "adb push SD /data/media/"
Once that wall of text is done, your phone should be fully functional, and ready to flash. That is how I solved all of my issues when I experienced the same thing.
I know I was short with a how-to on ODIN, but I'm super tired. ODIN is easy, and I'm sure you can find guides.
With your help I have managed to fix the drivers and my phone is now listed in adb devices. I downloaded Odin3 v.1.85 and I have downloaded the odin 4.0.4 images from the sticky'd threads. What I downloaded was a .tgz and contains a .tar. I do not know how to use these files with Odin however; when I try using ODIN with the .tar file the ODIN executible crashes.
Also, "adb pull /data/media/ SD" yields "remote object '/data/media/sd; does not exist". Is it correct to assume this is because the Galaxy Nexus does not have a removable SD card? Or is this method supposed to back up the internal storage?
I'm really appreciative of your help, thank you.
"ADB_Pull_/data/media/_SD" You have a space where the underscores are, right? And this is a method to backup the internal storage. It is located in /data/media/. Whenever you "Factory reset", the phone's /data/ partition is wiped, but the media folder is exempt. Always.
And as for ODIN crashing.. that's weird. I haven't had an issue. I'll upload my 4.0.2 images and executable to mediafire and PM it to you.
You'll want to make sure you backup your SD data, because ODIN will erase it.
---------- Post added at 09:36 AM ---------- Previous post was at 09:25 AM ----------
Oh wait. I just remembered there are multiple variants of the phone. What Gnex do you have? Maguro, Toro, or Toroplus? I'm uploaded images for Toro.
Looking at this thread is making my head spin.
What are you trying to do exactly? Flash a stock ROM without losing your files stored in /sdcard?
If so, then:
1) If you don't care about losing your files in /sdcard, just follow the steps in this thread.
2) If you DO want to keep the files in /sdcard, then follow the same steps, but skip flashing the userdata partition and the recovery partition. Instead of flashing the stock recovery, flash CWM 5.5.0.x. Once you have flashed all the partitions (except userdata), just reboot into CWM, and wipe data and cache. Done.
Other suggestions:
1) you should not use Odin unless you really need it. You can brick your device with Odin. Fastboot will do everything you need in most cases, and you canNOT brick your device.
2) Use CWM 5.5.0.x instead of the newer ones. The 5.5.0.x recoveries are extremely stable, and won't mess anything up.
3) You should read up a bit on fastboot and ADB. They are not related, as you seem to be implying in your OP (and they also need separate drivers). See here for a little introduction.
efrant said:
1) you should not use Odin unless you really need it. You can brick your device with Odin. Fastboot will do everything you need in most cases, and you canNOT brick your device.
Click to expand...
Click to collapse
People have bricked with ODIN? I haven't heard of that. Also, I experienced the same issue when I tried going over to JellyBean for the first time. I ****ed my Jellybean up, and my data partition was not functional. There were other users who had the issues too. We were only able to fix it through ODIN.
Edit: Adding that we experienced our issues after flashing the non-AOSP Jellybean.
Ryands991 said:
People have bricked with ODIN? I haven't heard of that.
Click to expand...
Click to collapse
Yup, they have. If you'd like, I can search and post the links.
But if your bootloader is messed up and you can no longer use fastboot, you have no choice but to use Odin.
Nah don't worry about searching for it. I'll take a peak later. I'm interested. Thank you!
---------- Post added at 10:32 AM ---------- Previous post was at 09:57 AM ----------
If you still want to try ODIN, here is a mirror of the Toro 4.0.2 files
http://www.mediafire.com/?31kevti8p2pnb62
Again, this is for Verizon/Toro/SCH i515
Don't use with any other version. If you don't have Verizon, this isn't the file you need.
efrant said:
Looking at this thread is making my head spin.
What are you trying to do exactly? Flash a stock ROM without losing your files stored in /sdcard?
If so, then:
1) If you don't care about losing your files in /sdcard, just follow the steps in this thread.
2) If you DO want to keep the files in /sdcard, then follow the same steps, but skip flashing the userdata partition and the recovery partition. Instead of flashing the stock recovery, flash CWM 5.5.0.x. Once you have flashed all the partitions (except userdata), just reboot into CWM, and wipe data and cache. Done.
Other suggestions:
1) you should not use Odin unless you really need it. You can brick your device with Odin. Fastboot will do everything you need in most cases, and you canNOT brick your device.
2) Use CWM 5.5.0.x instead of the newer ones. The 5.5.0.x recoveries are extremely stable, and won't mess anything up.
3) You should read up a bit on fastboot and ADB. They are not related, as you seem to be implying in your OP (and they also need separate drivers). See here for a little introduction.
Click to expand...
Click to collapse
I didn't manage to save my userdata but I did manage to return my phone to stock w/root using the method described in the thread you directed me too. Thank you efrant for your help
And thank Ryands991; I'll keep the ODIN method in mind if I ever encounter a problem using fastboot. Oh, and with regards to the spaces; I did have them, but it was stuck at 0% and never pushed my userdata. I am fine with losing my userdata however, so I went ahead and did a full wipe.
Hoping someone here can give me some help. Sometime last night my phone crashed - had an error message on the screen asking me if i wanted to restart - basically the android version of a blue screen.
I rebooted and when it started up it tried to activate but failed. Tried it a few times, never activated. I called sprint and they had me type in 2 different codes:
##72786# which didn't get an error but didn't help anything
They had me try a 2nd 6 digit number, which I'm not sure if it's unique to my phone or not so I wont post it here but that did nothing at all - typed in the ##______# and nothing happened. They claimed it was because the phone is rooted, but the phone is ONLY rooted. I haven't installed a new OS it's the stock rom as far as i can tell.
Anyone have any ideas whats going wrong here or how to fix it?
thanks
edit: and apparently now I wiped the OS from the phone since it wont go past the LG logo. Is there some way for me to either copy a rom onto the phone from TWRP or copy a backup onto the phone? I've got a couple of TWRP backups saved on my pc, but since the phone wont start up I don't have any way of copying them onto the phone - damn non-user removable sd cards.
merkk said:
Hoping someone here can give me some help. Sometime last night my phone crashed - had an error message on the screen asking me if i wanted to restart - basically the android version of a blue screen.
I rebooted and when it started up it tried to activate but failed. Tried it a few times, never activated. I called sprint and they had me type in 2 different codes:
##72786# which didn't get an error but didn't help anything
They had me try a 2nd 6 digit number, which I'm not sure if it's unique to my phone or not so I wont post it here but that did nothing at all - typed in the ##______# and nothing happened. They claimed it was because the phone is rooted, but the phone is ONLY rooted. I haven't installed a new OS it's the stock rom as far as i can tell.
Anyone have any ideas whats going wrong here or how to fix it?
thanks
edit: and apparently now I wiped the OS from the phone since it wont go past the LG logo. Is there some way for me to either copy a rom onto the phone from TWRP or copy a backup onto the phone? I've got a couple of TWRP backups saved on my pc, but since the phone wont start up I don't have any way of copying them onto the phone - damn non-user removable sd cards.
Click to expand...
Click to collapse
Can you boot to recovery?
If you can, then flash a newer TWRP build, they have MTP support, you can mount it while connected to your PC, copy a ROM zip over (there is a stock on in these threads somewhere), flash it from recovery, wipe everything first. Then you should be able to boot into a working device.
Yes I can boot into twrp, but I'm not sure how to copy files that way. I tried using adb but it couldnt find the phone. Can you give me some tips on how to copy a new ROM or twrp backup to the phone?
Thanks
merkk said:
Yes I can boot into twrp, but I'm not sure how to copy files that way. I tried using adb but it couldnt find the phone. Can you give me some tips on how to copy a new ROM or twrp backup to the phone?
Thanks
Click to expand...
Click to collapse
Yes, first thing is to flash this.
http://cubegamemc.de/kevinjoa/lollipop/recovery-geehrc/twrp/
You can flash it through fastboot.
follow these steps:
1. Download and place the file on your PC.
2. Reboot your device into Fastboot Mode. To do that, simply hold down the Volume DOWN+Power buttons together.
3. Once inside the Fastboot mode, connect your device to your PC via USB cable.
4. Launch a Command Prompt Window in the folder you saved the recovery image to. You can do that by holding down the Shift button on your keyboard and right-click on any blank area on the screen, then select Open command window here.
4. Enter the following command into the Command Prompt Window. You need to replace recoveryfilename.img with the actual name of the Recovery Image you downloaded.
Code:
fastboot flash recovery recoveryfilename.img
5. Once it is done, reboot your device
Code:
adb reboot recovery
should do it. If not, just hold down the power button, and get back to recovery.
at that point you should have the newest recovery. This recovery has MTP enabled so you can transfer files just like you can if you had a running device.
Once it shows up on you PC you can transfer a ROM zip or a backup to the internal SD. From there you I am sure you know how to flash a zip or restore a backup. It is the same as an older version. MTP should be under the "MOUNT" section of TWRP. I don't remember because I have a different device now.
Good luck!
If this doesn't work, follow the thread here: You would need the super big full bin file if you do though because you do not have a working ROM or zip currently on your internal SD card and this contains a very old recovery, but it does work.
http://forum.xda-developers.com/showthread.php?t=2230106
edit: I altered the directions from the source here for the att version. Don't worry, I changed them to suit your current need.
http://theunlockr.com/2013/03/26/how-to-install-twrp-recovery-on-the-lg-optimus-g-att/
My phone seems to behave a little differently than what you describe. Holding down the volume down and power button just turns it on. Holding vol up and power puts me into a screen with the android bot on it with the option to restart bootloader, go into recovery, or power off. and at the bottom there's some text indicating fastboot mode is on.
I was able to use the fastboot command to load the newer recovery. But for some reason, none of the adb commands work on my phone.
I'm copying a twrp backup to the phone now and i'll restore that. Hopefully that'll fix the issue of the phone not booting and if i am really lucky, fix the issue of the phone not being activated, but I'm not too hopeful about that.
Thanks again for all your help
hey - just wanted to say thank. Got my phone to boot back up again. Unfortunately the backup restore doesnt seem to have fixed my initial problem. Phone is back to saying it needs to be activated. Any ideas about that? It's also showing zero bars - not sure if that's what it's supposed to show when it's not activated.
Thanks again for your help
merkk said:
hey - just wanted to say thank. Got my phone to boot back up again. Unfortunately the backup restore doesnt seem to have fixed my initial problem. Phone is back to saying it needs to be activated. Any ideas about that? It's also showing zero bars - not sure if that's what it's supposed to show when it's not activated.
Thanks again for your help
Click to expand...
Click to collapse
EDIT:: TRY THIS FIRST<
Do a full wipe of the system and data, not internal. GO to recovery, select wipe, then factory reset. Then boot your phone. You will have to setup everything again but it might help. If it does not, you can always restore your backup again.
^^^^^^^^^^^^^^^^^^^^^^^
Interesting that your phone was the opposite for the buttons. Maybe I had it backwards, or maybe my source did. Either way I am glad you have a device that boots now.
Check this...
Go to the about section and see if your imei and other information are blank or have 0's. I am almost certain that there are 0000's.
If that's the case then you lost your EFS some how. and there is a way to recover that as long as you have a backup somewhere. You should have one somewhere if you used freegee to unlock your phone in the beginning. If not, perhaps an earlier backup you had of your device. A lot of the recoveries for this device make a backup of the EFS.
well i just dropped the phone off at a sprint repair store to see if they could do anything with it now that it actually boots. If they can't fix it, I'll try what you suggested. Although i already tried a factory reset and that didn't help.
well you are right about the esn/meid/IMEI - they are all zeros
I did a restore and then used freegee to restore the efs. Will free tell you if there is no backup of the EFS? Because i restored it, it finished pretty much instantly, and then i restarted the phone just be safe. Unfortunately it didn't fix it.
Phone still says searching for service, and now there's a little red x over the bars. Before the bars were blank but there was no red x. Not sure if that makes any difference.
Also, something else weird is going on now. I just tried copying a newer backup to the phone to try and restore the newer one. I don't seem to be able to copy files now. When i drag the folder windows , it says the device has stopped responding. If i try and copy each individual file in the backup folder, it starts to copy, and then just sits there like it froze, or like it's copying so slowly it might as well be frozen. I had to reflash twrp to the newer version and then I'm able to copy files.
Reloaded the efs backup again but still can't activate/have all zeros.
I think I've done goofed my nexus.
Yesterday, I made a backup of my phone, and then booted it up. Everything was working fine prior to the backup, but as soon as I booted it after making the backup, it got stuck on the google logo. I tried restarting it several times, but it's just been stuck in a bootloop ever since. I've tried numerous things, like formatting it, flashing factory images, and so on, but it turns out fastboot won't detect my device. ADB detects my device fine, but only in recovery. As far as I know, I don't have usb debugging enabled (since I formatted it). It currently has no OS since I formatted it. I've tried installing stock android since formatting it but it still gets stuck in a bootloop.
All my drivers are correct (I've re-installed them probably 10 times by now), and the images aren't corrupted (as far as I know).
I've run out of ideas, as I've been trying to figure this out for the past 2 days with no success. Any help would be appreciated.
I've had a similar issue a couple times after doing something stupid (ADB or FASTBOOT could not detect the phone). The fix was to look in Windows Device Manager and make sure the phone really was detected and a driver installed. Windows would say that it could not find a driver but telling it to install manually did the trick..... as I recall there were a couple driver choices, so it might be trieal and error. Might not be the issue in your case since it does sound like the hardware has a problem, but worth looking into?
Paul
pgoelz said:
I've had a similar issue a couple times after doing something stupid (ADB or FASTBOOT could not detect the phone). The fix was to look in Windows Device Manager and make sure the phone really was detected and a driver installed. Windows would say that it could not find a driver but telling it to install manually did the trick..... as I recall there were a couple driver choices, so it might be trieal and error. Might not be the issue in your case since it does sound like the hardware has a problem, but worth looking into?
Paul
Click to expand...
Click to collapse
I've re-installed the drivers a couple of times now, and it doesn't seem to be fixing the problem.
I don't think it's a hardware problem, because I don't see what making a backup would do to the hardware of the phone (of course, I don't really know much about the hardware, so I might be wrong.) Thanks for the help, though!
ItsMason said:
I've re-installed the drivers a couple of times now, and it doesn't seem to be fixing the problem.
I don't think it's a hardware problem, because I don't see what making a backup would do to the hardware of the phone (of course, I don't really know much about the hardware, so I might be wrong.) Thanks for the help, though!
Click to expand...
Click to collapse
Hi, since you're communicating with the device via ADB and can boot to recovery, I'm pretty sure you can still do something about it. I've had this issue and I can recommend starting to read up on Ubuntu or some type of Linux with a decent user interface. It's easier for starters.
You see, if you don't detect the device via the 'fastboot devices' command, then you have one of two big problems:
a) drivers are messed up - it implies you uninstall everything from Device Manager related to ADB / Bootloader interface. After that, shut off the phone, connect your type-c usb cable, boot up the phone into bootloader and let it install the drivers again (I didn't have much success with this but I read others have. Worth a try)
b) something messed up deeper, as in device permissions. When I had the issue, I used Mint (a Debian distribution) and installed all the drivers via the command line there. After that, when I ran fastboot devices, I got something. It was my lost N5x showing with 'no permissions' and no serial ID. I ran 'sudo fastboot devices' and lo' and behold, I saw the device. After that, I just used sudo fastboot flash recovery/system/etc with it and that was it.
exige34 said:
Hi, since you're communicating with the device via ADB and can boot to recovery, I'm pretty sure you can still do something about it. I've had this issue and I can recommend starting to read up on Ubuntu or some type of Linux with a decent user interface. It's easier for starters.
You see, if you don't detect the device via the 'fastboot devices' command, then you have one of two big problems:
a) drivers are messed up - it implies you uninstall everything from Device Manager related to ADB / Bootloader interface. After that, shut off the phone, connect your type-c usb cable, boot up the phone into bootloader and let it install the drivers again (I didn't have much success with this but I read others have. Worth a try)
b) something messed up deeper, as in device permissions. When I had the issue, I used Mint (a Debian distribution) and installed all the drivers via the command line there. After that, when I ran fastboot devices, I got something. It was my lost N5x showing with 'no permissions' and no serial ID. I ran 'sudo fastboot devices' and lo' and behold, I saw the device. After that, I just used sudo fastboot flash recovery/system/etc with it and that was it.
Click to expand...
Click to collapse
I made some progress: my device is now detected in fastboot. I have literally absolutely no clue what happened. I guess it was a bit of randomness or luck or something (maybe wacky and goofy). I've done some flashing - I've flashed system, boot, recovery, cache, data, and radio, but it's still stuck in a bootloop. I don't know what's going on it with it now, but it seems like I haven't made any progress with fastboot.
ItsMason said:
I think I've done goofed my nexus.
Yesterday, I made a backup of my phone, and then booted it up. Everything was working fine prior to the backup, but as soon as I booted it after making the backup, it got stuck on the google logo. I tried restarting it several times, but it's just been stuck in a bootloop ever since. I've tried numerous things, like formatting it, flashing factory images, and so on, but it turns out fastboot won't detect my device. ADB detects my device fine, but only in recovery. As far as I know, I don't have usb debugging enabled (since I formatted it). It currently has no OS since I formatted it. I've tried installing stock android since formatting it but it still gets stuck in a bootloop.
All my drivers are correct (I've re-installed them probably 10 times by now), and the images aren't corrupted (as far as I know).
I've run out of ideas, as I've been trying to figure this out for the past 2 days with no success. Any help would be appreciated.
Click to expand...
Click to collapse
Do you use 3.02.1. Twrp
Since you mention ADB works fine from recovery, have you tried to adb push a rom zip, and then flash it from your recovery?
Code:
adb push "/path/to/rom.zip" /data/media
ItsMason said:
I made some progress: my device is now detected in fastboot. I have literally absolutely no clue what happened. I guess it was a bit of randomness or luck or something (maybe wacky and goofy). I've done some flashing - I've flashed system, boot, recovery, cache, data, and radio, but it's still stuck in a bootloop. I don't know what's going on it with it now, but it seems like I haven't made any progress with fastboot.
Click to expand...
Click to collapse
Good. I see you mention flashing system, boot, recovery, cache(?), data(?) and radio. What do you mean by flash cache&data? You mean you've cleaned it? Formatting data is not usually a thing you have to do to recover from a bootloop.
What ROM have you flashed? Are you flashing stock? It's important you give more details so I can help you.
Have you flashed vendor.img? If you have been on a ROM that had it's own vendor.img and you went back to stock, then the vendor.imgs are different enough to cause a bootloop.
If all and all fails, we just want to see your system running so I'd recommend drop everything you are doing and follow these steps:
1. Access recovery (make sure you're using v 3.0.2.2)
2. Tap Wipe - > Advanced Wipe - > And check:
Dalvik / ART Cache
System
Internal Storage
Cache
3. Go to -> Pixel ROM (7.1.1) Get V 3.0 which was just uploaded recently. Please note it comes preconfigured with Gapps so no need to get that
4. You have to unzip the archive and you will see all the necessary img files (includes boot/vendor which are critical for boot). I strongly recommend manually flashing them. You can open the flash-all.bat file with a .txt editor and just follow the steps there.
After you have finished these steps, you should be free of a bootloop. From there, it is your decision where you. Either stay on a stock ROM or flash safely and always remember that you can make a backup and flash that backup in case you bootloop.
Good luck.
EDIT
Decay3 said:
Since you mention ADB works fine from recovery, have you tried to adb push a rom zip, and then flash it from your recovery?
Click to expand...
Click to collapse
I think his problem is deeper than a /system error. I'm guessing the wrong boot/vendor is flashed for the ROM he is trying to install and trying to guess which ROM would work on his current config would take more time than just starting from a clean flash.
Thanks for the help guys, but I gave up. I contacted Google and they sent me a replacement. Sorry for kind of wasting time.
Dear XDA, I could really use your help.
I have a stock LG Nexus 5x (bullhead/7.1.1) which recently started to fail to boot properly as it never loads past the coloured animations on startup and often stops. This sounds like it may be the boot-loop problem.
I have not rooted the phone, unlocked the boot-loader or flashed any recoveries. I have not enabled USB debugging and can't now because it won't boot.
I am looking at my options to recover the data from this phone.
I can get to the fastboot screen (where the fastboot command line tools see the device, but adb does not). I can proceed to the recovery screen and have tried clearing the cache with no luck.
I am considering trying:
Booting a fastboot recovery image
(eg fastboot boot recovery TWRP.img)
Applying a rescue OTA image
Will these methods void the phones warranty?
Will these methods even work (given the bootloader is locked)?
Can the images be recovery images like TWRP or does it have to be some stock/non-custom image?
Does the rescue OTA require adb/usb-debugging to be operational?
Will the data on the phone still be intact using these methods?
As I am cautiously working may way through this to firstly recover my data, secondly recover my phone., any advice would be greatly appreciated.
Sorry to hear that! I'm assuming your files weren't backed up to Google drive.
I don't know a way to recover your data! If you flash a OTA image, it might help fix your phone boot up problem and it will preserve your phone data.
This sucks because the phone is encrypted by default (did you use to enter a password in the middle of phone booting up and the it would continue booting after your password was accepted? If yes, encryption is on). So flashing TWRP won't mean you can see your data.
And it also has USB debugging disabled by default, which means you probably can't mount the internal memory through ADB.
So I would flash a full OTA image before anything else and keep my fingers crossed. Don't flash a full factory image because it will wipe the data and continue!!!
https://developers.google.com/android/ota
Sent from my Nexus 5X using XDA-Developers Legacy app
Commodore 64 said:
Sorry to hear that! I'm assuming your files weren't backed up to Google drive.
I don't know a way to recover your data! If you flash a OTA image, it might help fix your phone boot up problem and it will preserve your phone data.
This sucks because the phone is encrypted by default (did you use to enter a password in the middle of phone booting up and the it would continue booting after your password was accepted? If yes, encryption is on). So flashing TWRP won't mean you can see your data.
And it also has USB debugging disabled by default, which means you probably can't mount the internal memory through ADB.
So I would flash a full OTA image before anything else and keep my fingers crossed. Don't flash a full factory image because it will wipe the data and continue!!!
Click to expand...
Click to collapse
Unfortunately I had not set-up any syncing/backup process on the phone. In the future I will.
Although I don't recall what encryption settings were originally configured, I didn't have to enter a password in the middle of boot, and was only prompted to swipe in. So I think it wasn't encrypted.
So I attempted to sideload an OTA image via:
adb sideload bullhead-ota-n4f26i-06953aec.zip
then rebooted, however the phone still does not successfully boot any further. I must have really broken this one!
Are there any data recovery methods if a factory reset is applied? if I take it in to a repair agent under-warranty, do they typically wipe your data anyway?
Also, do I need to remove this OTA image if I am to return it for repair under warranty?
In a futile/desperate attempt to try to further recover my data, I have attempted to load my Nexus 5X into the stock recovery mode, then experimented with adb when using the 'apply update from adb' option. This exposed a subset of adb commands which appeared to work (eg adb devices, adb sideload etc). I was hoping to be able to run adb shell or adb pull remote local and recover some data... however I only encountered errors.
./adb shell
error: closed
./adb pull /storage/emulated/ /backup
adb: error: connect failed: closed
I assume this is expected (due to the stock recovery adb limitations, but thought it was worth a shot). I am considering exploring the fastboot options (eg fastboot boot recovery recovery.img) I suspect these are also likely to fail/wipe data. Has anyone got any suggestions/ideas or am I just wasting my time?
This just happened to me yesterday, and I got the single file I needed off the phone today. I fought with the thing for hours yesterday. First you have to clear the cache and sideload a new bullhead zip file (as documented elsewhere). That isn't all, though. After several tries, I noticed that I got farther along in the boot if I let the phone sit for a while. So, on the theory that there's a loose solder connection somewhere and/or heat buildup, I put the phone in the freezer for a few hours (not my idea; found it on reddit). This worked, but only if I also tapped the back of the phone with my knuckle before booting. As I said, success today and I'm all smiles. I hope this helps someone else.
The phone, by the way, is bricked as far as I can tell. And my backups are going to be a lot more comprehensive from here on.
Hi.
Apologies if this is a very naive question, I am not particularly familiar with mods, roms and so forth.
I have rooted another phone in the past, but that is all.
The situation:
- Samsung Galaxy Nexus
- Not rooted/unlocked. Stock android automatically updated to the latest Android version supported
- Android developer option NOT set in settings
- Stuck in a boot loop: boots to android and then after a few seconds reboots, so no time to do anything
- Not sure how it happened, I had it for years, it was in my pocket and suddenly started doing that.
- Android fastboot and recovery loads up no problem
- I have tried anything I could find online to fix it: deleted cache, rebooted in safe mode, removed battery for 10 hours
- Nothing seems to fix it, it keeps rebooting
- I want to try a factory reset, but my family photos are in the phone
- Google synch seems to have stopped functioning for this device a year ago, all my 2016-17 photos and videos are locked in the phone.
Admitting there is nothing to do about the loop problem:
Is there any way I can copy photos and videos via usb while in recovery mode?
After I will reset the phone via recovery menu, hoping it will fix it. IF that does not fix it, I will flash another rom in. But I really do not want to wipe my data before backing them up.
I am assuming the answer is no, you cannot access the internal memory in fastboot/recovery unless your phone is rooted.
But I would like an expert opinion before I resolve to wipe one year of photos and videos which I will regret losing.
@mcaldo DON'T DO FACTORY RESET, EVERYTHING WILL BE LOST
which recovery are you using..?
if it's TWRP, then it's easy..
- boot into TWRP recovery
- go to "Mount" tab
- find "enable/disable MTP" button at lower options.. (enable it )
then connect your phone to that PC, where you always connected in past, ( to eliminate driver installation stage, all drivers will be preinstalled )
Regards
____Mdd said:
@mcaldo DON'T DO FACTORY RESET, EVERYTHING WILL BE LOST
which recovery are you using..?
if it's TWRP, then it's easy..
- boot into TWRP recovery
- go to "Mount" tab
- find "enable/disable MTP" button at lower options.. (enable it )
then connect your phone to that PC, where you always connected in past, ( to eliminate driver installation stage, all drivers will be preinstalled )
Regards
Click to expand...
Click to collapse
Thanks for your reply!
By recovery, I meant 'android system recovery'
It gives me the following options:
reboot system now
apply update from ADB
apply update from USB drive
wipe data/factory reset
wipe cache partition
Is any of the above useful?
Unfortunately, I do not have any alternative recovery software available
Edit: Googling I found this: "Apply update from ADB: The Android Debug Bridge allows you to plug your device into your PC and issue commands from there. "
If I can issue commands through ADB, perhaps there is a command to copy data from my phone to my computer?
mcaldo said:
Thanks for your reply!
By recovery, I meant 'android system recovery'
It gives me the following options:
reboot system now
apply update from ADB
apply update from USB drive
wipe data/factory reset
wipe cache partition
Is any of the above useful?
Unfortunately, I do not have any alternative recovery software available
Edit: Googling I found this: "Apply update from ADB: The Android Debug Bridge allows you to plug your device into your PC and issue commands from there. "
If I can issue commands through ADB, perhaps there is a command to copy data from my phone to my computer?
Click to expand...
Click to collapse
Yes, you can copy through adb commands..
Get and extract Minimal ADB and Fastboot from here: https://forum.xda-developers.com/showthread.php?t=2317790
From PC, run CMD to extracted folder directory.
Connect phone to PC, go to update from ADB(in recovery),
Type "adb device" , it will show serial number and connected..
Then "adb pull /sdcard " (if you know particular directory of data then write it like /sdcard/photos,, otherwise writing /sdcard will copy all folders from your phone. )
it will start copying to same adb folder ..
____Mdd said:
Yes, you can copy through adb commands..
Get and extract Minimal ADB and Fastboot from here: https://forum.xda-developers.com/showthread.php?t=2317790
From PC, run CMD to extracted folder directory.
Connect phone to PC, go to update from ADB(in recovery),
Type "adb device" , it will show serial number and connected..
Then "adb pull /sdcard " (if you know particular directory of data then write it like /sdcard/photos,, otherwise writing /sdcard will copy all folders from your phone. )
it will start copying to same adb folder ..
Click to expand...
Click to collapse
Thanks for the advice.
I followed the instructions closely, and nearly got there.
adb devices returns
#serialnumber sideload
so all good
but adb pull /sdcard returns
adb: error connect failed: closed
I tried several other commands with no success
kill-server and start-server work fine but do not solve the problem
adb usb returns
error closed
So, I am starting thinking that the problem is in the bootloader being locked.
However, if I unlock it, it will be wipe all my data, I understand?
Googling about it, I found this:
The behavior is status-by-design. Your stock recovery is not designed to grant shell access. Your only choice here is to somehow manage to flash a custom recovery. – Firelord Dec 30 '15 at 14:19
3
To achieve something similar to what @FireLord suggested: TWRP can be booted on many devices without being installed. For that, find a matching image, then boot to the bootloader and run fastboot boot twrp.img. Btw: you can check with fastboot devices resp. adb devices whether a device is visible to the corresponding tool. – Izzy♦ Jul 8 '16 at 19:40
So I understand one could boot TWRP without installing it, but I am not sure if that means I could do that with the bootloader locked?
I found WugFresh nexus root toolkit which seems to do that, among many other things, but again it warns that the phone must be unlocked (using the android build "Android *.* Any", I did not know what else to choose, not sure if that makes any difference as for locked/unlocked requirements)
EDIT: my fastboot screen reads "FASTBOOT STATUS - Failbootloader locked" as the last line, when trying to run TWRP without installing.
Yes, unlocking bootloader will wipe everything..
What actually you did ? Why it went into bootloop ???
I have also read that about boot into TWRP without installing.. and it worked for many one without unlocking bootloader... Don't know why not on GNex.
____Mdd said:
Yes, unlocking bootloader will wipe everything..
What actually you did ? Why it went into bootloop ???
I have also read that about boot into TWRP without installing.. and it worked for many one without unlocking bootloader... Don't know why not on GNex.
Click to expand...
Click to collapse
What actually you did ? Why it went into bootloop ???
Click to expand...
Click to collapse
A very good question, to which I have no answer, unfortunately.
The phone was used by my wife for 2 years and then by me for other 2. I recently changed the battery.
Never rooted or unlocked. No unusual apps installed. I am a very basic user, as you might have guessed, and being my only phone at the moment, I really would not risk experimenting with it.
It went very slow over the last 4 months, so I was planning to reset it.
I put in my coat pocket for a few hours, when I took it out it had a train ticked stuck to the screen and was quite warm and on the lock screen. It froze, so I took the battery out and restarted it. From then on it is stuck in a loop, not sure why really.
I have also read that about boot into TWRP without installing.. and it worked for many one without unlocking bootloader... Don't know why not on GNex
Click to expand...
Click to collapse
That's good to know. I'll research more than.
It seems there might be a problem with the fastboot drivers on my computer, even selecting them from device manager did not work. Win7 refuses to install. The ADB drivers in theory work fine though.
If you have done nothing modification to system, then wiping data should work, but i have doubt if it also wipes personal data too, on TWRP it wipes data excepting /data/media/ which contains all personal data.. but don't know about wiping on stock recovery...
I hope you will find solution as soon as possible..
Regards.
PS. I can install stock recovery and try wiping /data.. and check what things get wiped.. but i need little time for that experiment...
____Mdd said:
If you have done nothing modification to system, then wiping data should work, but i have doubt if it also wipes personal data too, on TWRP it wipes data excepting /data/media/ which contains all personal data.. but don't know about wiping on stock recovery...
I hope you will find solution as soon as possible..
Regards.
PS. I can install stock recovery and try wiping /data.. and check what things get wiped.. but i need little time for that experiment...
Click to expand...
Click to collapse
Thanks so much.
Looking at google's documentation on the nexus:
You can remove data from your Pixel phone or Nexus device by resetting it to factory settings. Resetting to factory settings is also known as formatting the device or doing a "hard reset".
If you're factory resetting your device to fix an issue, make sure that you've tried all other troubleshooting options first. Find out how to troubleshoot your issue.
Important: Performing a factory reset will erase all data from the device.
Click to expand...
Click to collapse
It would seem that indeed all data will be removed.
This point, I will research a bit more into drivers, in case that is what it's preventing adb pull from working.
I really need a working phone, so if that fails I will hard reset, then unlock, root, flash in an alternative bootloader and perhaps a rom, and put ubuntu touch in dual boot. That will hopefully prevent me from loosing data in the future.
Sorry, this is out of topic to my question, but, , could you suggest any stable, solid rom for the nexus?
I read good things of CM12, and I ran into one which seemed to do to quite well with split windows, but I do not remember the name right now.
EDIT: I remember the name of the rom now, it's https://omnirom.org/about/
A last question if you can..
I tried to solve my boot loop problem by sideloading an update from google (maguro yakju yakju-jwr66y-factory-4cadea65.zip)
It loaded it fine but then failed because the installation it says it is not signed.
Basically, being a stock bootloader recovery from Samsung, it will only sideload OTAs from samsung, not the stock ones from google..
I cannot find the samsung ones anywhere, not for the nexus anyway, just the newer devices..
By any chance do you know where I could download proper Samsung OTA zip updates for the nexus?
Well, I talked with an android developer who confirmed that, unless you have a friend working in criminal forensic technology or similar, there is no way to get around a lock on this phone to pull data out.
So, sadly, I have wiped my phone by unlocking it, flashed TWRP and then omnirom with gapps.
My photos are gone, including a bunch of stuff my kid had made and asked me to photograph for safeeping. Very safe indeed
He kept asking me why they make the lock like that, instead of allowing some kind of password, perhaps he has a point.
So, it is quite unlikely that somebody who knows as little as I did will ever read this *before* finding themselves in the same situation.
But if you do, back up your data, unlock and flash TWRP, clockworks or some alternative, and thank yourself if and when disaster strikes..
@mcaldo wiping data/factory reset in STOCK RECOvERY will wipe everything... There is very few chances to get backup...
And yeah i found something interesting..
You can flash system.img.. only system files will be corrected not anything else..
Get appropriate zip from here : https://developers.google.com/android/images
Now take system.img to ADB/Fastboot folder ( i assume you know how it works )
Just go "Fastboot flash system system.img"
It will rewrite system partition..
Another one:
See downloads on this thread..
One says NON-WIPE, if you want me to try that zip, i will again require time for that. See here : https://forum.xda-developers.com/galaxy-nexus/general/guide-restore-to-stock-unbrick-galaxy-t2065470
---------- Post added at 11:12 AM ---------- Previous post was at 11:09 AM ----------
I don't saw your reply, it was on next page.. its sad... Sorry i am late..