Related
Hello Xda community, I open this thread after two days of reading and trying different ways to solve my problem.
My Nexus 5 runs Android 5.1.1 which I got OTA, I've never Rooted, installed any ROMS or done anything that might violate the system or the warranty.:angel:
Few days ago I downloaded some crappy program to my PC called Wondershare Dr.Fone (BURN IN HELL !!!) that was suppose to recover my deleted photoes from the Nexus, during the process of syncing etc.. it asked me to open developer settings and turn ON debugging mode.. which I did... and after about 30-40 minutes of "working" I realized it FROZE
The program didn't have any "Abort" button, and it was already late, so I just disconnected my Nexus, and after a moment it restarted and went into Bootloop
First I waited about an hour to realize it was infinite, then I tried going into Recovery Mode and deleting Cache Partition then restarting... it also didn't help, whenever I tried to turn it off, it was just turning on again, showing the Google Logo and then bashing those infinite Spinning Google Ballz in my face (I can turn off the phone using the Bootloader which works just fine, but it doesn't helps with the bootloop)...
The next whole day I was trying to at least recover my photos and videos, hoping that I can use the ADB to Pull the Camera folder out... I tried to install maaaany Google USB drivers following the steps of dozen tutorials, downloaded the SDK Manager and tried to install them thru Google server, and even Installed Naked Drivers with Windows 8.1 Signature Check Disabled... and tried it on 3 different PCs (win 8.1 and 7) the result was the same: Nexus 5 remained invisible until I Clicked in recovery mode "ADB Sideload.." in which case my Nexus 5 appeared in Device manager under Other Devices section (which let me install the drivers) otherwise it was invisible for my PCs...
The problem: whenever I was lunching the ADB from it's folder and typing "adb devices" I saw some sort of serial number, and "Sideload" next to it (while in other tutorials people have the word "Device" instead) and every command such as "adb usb" or "adb pull /sdcard/" or "adb pull /Camera/" result in "Error: closed" :crying:
In despair I tried to Factory reset my Nexus, and after about an hour of wiping, it allowed me to reboot which ended up in another infinite Bootloop....
I don't know what to do now, I don't live in the States and don't have warranty, I feel it's really unfair how after preserving my Nexus and it's Stock OS for so long... some Dr.fone bull**** broke it...
Please help me save my Nexus
Yea well... I knew nobody would give a crap in here... >.>
iJutsu said:
Yea well... I knew nobody would give a crap in here... >.>
Click to expand...
Click to collapse
[sarcasm]Way to stay positive.[/sarcasm]
You said you've tried doing a factory reset and that your system detects your device while in sideload mode on the stock recovery, correct? If so, have you at least tried sideloading the stock system update? Could be worth a shot at least.
Or with the driver issues, have you looked into opening device manager and see if it reads any kind of connection when hooked up not under sideload?
When adb is in sideload mode, you cant use any of the normal adb operations, like pull or push.
davehasninjas said:
You said you've tried doing a factory reset and that your system detects your device while in sideload mode on the stock recovery, correct? If so, have you at least tried sideloading the stock system update? Could be worth a shot at least.
Or with the driver issues, have you looked into opening device manager and see if it reads any kind of connection when hooked up not under sideload?
Click to expand...
Click to collapse
Factory reset didn't give any results, just destroyed any hope of recovering the photos I had onboard...
The system did detect my device for some time only when I activated the "ADB Sideload.." in the Recovery mode, but it wasn't same as in most guides and tutorials I've seen... When I typed the command "adb devices" it showed "4bd...serial.. Sideload", while according to tutorials it should be detected as "4bd.... Device"... Also I think the phone should get detected even without pushing the "Adb Sideload"... but the main problem is that every command results in "Error: Closed" so I can Pull or Push or Sideload anything since it's always same error"... which made me think perhaps the drivers aren't Okey, but I tried every Nexus 5/Google driver I could find, and I really doubt it's the drivers fault.
As I said the device remains invisible both in Device Manager and in Devices and Printers, until I click the Adb Sideload on the Nexus...
Factory Reset didn't work even tho I've never did any root or install Stock ROM or Kernel or anything of that sort, makes me wonder if that Dr.Fone crap app actually bricked my phone...
Thanks for trying to help
beekay201 said:
When adb is in sideload mode, you cant use any of the normal adb operations, like pull or push.
Click to expand...
Click to collapse
Aw... that's what I suspected... But activating the ADB sideload is the only way to make my Nexus 5 visible when I type "adb devices".... Does the fact that my PC can see it during ADB Sideload means that the Drivers are installed correctly? what may be the problem then? uff..
Have u tried this
Since you dont mind losing your data, I guess u already did a factory reset, I seriously suggest trying this guide. Read carefully. It worked perfectly for me which was in bootloop after 5.1.1 update.
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632
So when I was trying to unlock my phone via my fingerprint, i didn't have my finger on there correctly 1 to many times and locked my phone. I couldn't remember my passcode and had to log into it via my google account. It then restarted and now won't boot. Gives me the "custom binary blocked by FRP lock" Tried flashing the root tar file and TWRP tar file with no luck. Don't know what to do as I have never came across this before. Any help is appreciated. Phone is rooted but stock.
They holding volume up, home and power when the phone is off. Should get you into recovery. Then do a factor reset. Not sure if this will work though.
Sent from my SM-N920P using Tapatalk
CBRRider said:
So when I was trying to unlock my phone via my fingerprint, i didn't have my finger on there correctly 1 to many times and locked my phone. I couldn't remember my passcode and had to log into it via my google account. It then restarted and now won't boot. Gives me the "custom binary blocked by FRP lock" Tried flashing the root tar file and TWRP tar file with no luck. Don't know what to do as I have never came across this before. Any help is appreciated. Phone is rooted but stock.
Click to expand...
Click to collapse
The phone is rooted so flashing the tar file for root or TWRP is useless because its already rooted. The problem is you locked the phone with your fingerprint. Did you make a backup? You can restore that and you should be good beause it resets the device completely. However, if you did not, then flash the stock tar file in Odin and you'll be good to go. You can find the stock tar file here...http://forum.xda-developers.com/showpost.php?p=62536311&postcount=1
I can confirm it works. You will just have to reroot because it returns the phone to stock out the box.
Due to FRP (Factory Reset Protection) by Google, You won't be able to flash any custom files to phone, it'll always fail, To be able to flash any custom files, You have to enable "allow OEM unlocking" from developer menu, which will disable the FRP lock, But this is not possible in your case since you can't access the menu, But since you're rooted, i assume that you enabled "USB Debugging", So now connect the phone to PC and run CMD and try the following commands one by one,
adb devices # this should list your device
adb shell
su
cd data/system
ls #this will list all files in that dorectory
rm *.key #to delete all .key files which contains the lock
and you're done.
Sent from my iPhone 6 using Tapatalk.
mirosaw2 said:
Due to FRP (Factory Reset Protection) by Google, You won't be able to flash any custom files to phone, it'll always fail, To be able to flash any custom files, You have to enable "allow OEM unlocking" from developer menu, which will disable the FRP lock, But this is not possible in your case since you can't access the menu, But since you're rooted, i assume that you enabled "USB Debugging", So now connect the phone to PC and run CMD and try the following commands one by one,
adb devices # this should list your device
adb shell
su
cd data/system
ls #this will list all files in that dorectory
rm *.key #to delete all .key files which contains the lock
and you're done.
Sent from my iPhone 6 using Tapatalk.
Click to expand...
Click to collapse
How does one use ADB when its stuck like this?
hshah said:
How does one use ADB when its stuck like this?
Click to expand...
Click to collapse
He just said his phone is rooted, And i assumed that USB Debugging is enabled, So if you have the same case, You can connect your phone to PC and start using ADB as normal, Then you can follow my guide to get rid of any kind of screen security there, Simple like that.
Sent from my iPhone 6 using Tapatalk.
mirosaw2 said:
He just said his phone is rooted, And i assumed that USB Debugging is enabled, So if you have the same case, You can connect your phone to PC and start using ADB as normal, Then you can follow my guide to get rid of any kind of screen security there, Simple like that.
Sent from my iPhone 6 using Tapatalk.
Click to expand...
Click to collapse
I connected the phone to the PC whilst it was in Download Mode (that is the only mode I can boot into and it wouldn't see it).
Too late now anyway, as I've just flashed stock through ODIN
hshah said:
I connected the phone to the PC whilst it was in Download Mode (that is the only mode I can boot into and it wouldn't see it).
Too late now anyway, as I've just flashed stock through ODIN
Click to expand...
Click to collapse
If your phone doesn't boot to system, Then you can't use my method, My method was all about saving the data on the phone, And if the data wasn't important to you, you can always flash the stock FW for your phone, Or even wipe the phone from recovery, And i can see you had no option since system doesn't boot up.
Sent from my iPhone 6 using Tapatalk.
mirosaw2 said:
If your phone doesn't boot to system, Then you can't use my method, My method was all about saving the data on the phone, And if the data wasn't important to you, you can always flash the stock FW for your phone, Or even wipe the phone from recovery, And i can see you had no option since system doesn't boot up.
Sent from my iPhone 6 using Tapatalk.
Click to expand...
Click to collapse
Interestingly I have just recovered it by flashing stock through ODIN and all I lost was root and Xposed. All my data etc is still there! :highfive:
hshah said:
Interestingly I have just recovered it by flashing stock through ODIN and all I lost was root and Xposed. All my data etc is still there! :highfive:
Click to expand...
Click to collapse
Good for you, And that's because you've flashed an One-Package FW (AP only) which is simillar or newer than the one you had, In that case all your of your settings and data will be still there, And that applicable also for the screen security, Which you'll notice it being there if you had one before your phone got stucked at boot screen, Now i see what your problem was, Before now i thought it was about security. :highfive:
Sent from my iPhone 6 using Tapatalk.
mirosaw2 said:
Good for you, And that's because you've flashed an One-Package FW (AP only) which is simillar or newer than the one you had, In that case all your of your settings and data will be still there, And that applicable also for the screen security, Which you'll notice it being there if you had one before your phone got stucked at boot screen, Now i see what your problem was, Before now i thought it was about security. :hoghfive:
Sent from my iPhone 6 using Tapatalk.
Click to expand...
Click to collapse
I actually didn't have any screen security. I know I had turned on OEM and USB Debugging, so not sure how OEM got turned off.
Anyways glad its sorted! Just finished re-rooting and I am back up and running!
odin flash fails
Hey ..
I have a sprint note 5..I was trying to root my phone but somehow the instructions I was following didn't have anything about developer options and lock off from setting..
Now after I restarted I cannot boot up my device .and get the
Frp lock error .
I tried refreshing custom rom through odin, but it keeps failing..
Please help.
mevj said:
Hey ..
I have a sprint note 5..I was trying to root my phone but somehow the instructions I was following didn't have anything about developer options and lock off from setting..
Now after I restarted I cannot boot up my device .and get the
Frp lock error .
I tried refreshing custom rom through odin, but it keeps failing..
Please help.
Click to expand...
Click to collapse
You need to flash stock ROM, not custom ROM.
hshah said:
You need to flash stock ROM, not custom ROM.
Click to expand...
Click to collapse
where can i find this stock rom
mevj said:
Hey ..
I have a sprint note 5..I was trying to root my phone but somehow the instructions I was following didn't have anything about developer options and lock off from setting..
Now after I restarted I cannot boot up my device .and get the
Frp lock error .
I tried refreshing custom rom through odin, but it keeps failing..
Please help.
Click to expand...
Click to collapse
I have the exact same problem and tried flashing a stock rom but it fails as well.
did you have any luck??
mine is stuck too i turned off oem unlock and resarted phone now it wont boot i tried odin to stock oi6 but i did ota to oj6 which i see isnt released yet, so does anyone know if and when they are going to release OJ6 FW? and does anyone know how to fix this problem
How did you do it?
hshah said:
I connected the phone to the PC whilst it was in Download Mode (that is the only mode I can boot into and it wouldn't see it).
Too late now anyway, as I've just flashed stock through ODIN
Click to expand...
Click to collapse
How do you get it to flash via odin? I keep trying and get a failure of the lock. Is there a specific method you did that i am not doing right?
Please help if you can. I don't want to have to go to warranty and pay a hefty fee.
I too am suck in FRP lock. I also can't get into TWRP or can't flash it on the phone.
I would really appreciate it.
psychokrod said:
How do you get it to flash via odin? I keep trying and get a failure of the lock. Is there a specific method you did that i am not doing right?
Please help if you can. I don't want to have to go to warranty and pay a hefty fee.
I too am suck in FRP lock. I also can't get into TWRP or can't flash it on the phone.
I would really appreciate it.
Click to expand...
Click to collapse
Try flashing this one in Odin http://forum.xda-developers.com/showthread.php?t=3273483
hshah said:
I connected the phone to the PC whilst it was in Download Mode (that is the only mode I can boot into and it wouldn't see it).
Too late now anyway, as I've just flashed stock through ODIN
Click to expand...
Click to collapse
Did THE stock flash worked for you? cause i can only boot in download mode also. I didnt know about this lock.... Is it so i have to walt for 3 days to use my phone?
liobeir said:
Did THE stock flash worked for you? cause i can only boot in download mode also. I didnt know about this lock.... Is it so i have to walt for 3 days to use my phone?
Click to expand...
Click to collapse
Yes it did. Download the stock firmware from Sam Mobile and just flash it through ODIN whilst in Download mode. It kept all my apps and settings too.
I have a Verizon Galaxy S6 that keeps rebooting. It will allow me to get to the home screen for about 30-45 seconds before it reboots again. During that very short interval, I was able to turn on developer options in settings. With another reboot, I was able to quickly accept ADB permissions from my laptop. I am getting ready to RMA the device, but first I need to get my pictures off. I tried installing TWRP so that I can do a backup, but the device is NOT rooted, and the DM security will not let me install a new recover image. The phone will stay on forever when in bootloader mode, but fastboot cannot "see" any attached devices. Is there any other way to get to my device's hard drive when this thing won't stay on long enough?
Any advice/suggestions are greatly appreciated.
baddison said:
I have a Verizon Galaxy S6 that keeps rebooting. It will allow me to get to the home screen for about 30-45 seconds before it reboots again. During that very short interval, I was able to turn on developer options in settings. With another reboot, I was able to quickly accept ADB permissions from my laptop. I am getting ready to RMA the device, but first I need to get my pictures off. I tried installing TWRP so that I can do a backup, but the device is NOT rooted, and the DM security will not let me install a new recover image. The phone will stay on forever when in bootloader mode, but fastboot cannot "see" any attached devices. Is there any other way to get to my device's hard drive when this thing won't stay on long enough?
Any advice/suggestions are greatly appreciated.
Click to expand...
Click to collapse
Download the exact same stock firmware you are currently on from Sammobile.com that way you almost eliminate your chances of a bootloop
for your device and flash it in odin in ap /pda slot as long as you don't wipe in recovery or do a nand erase your data should still be there
Sent from my SM-G900V using Tapatalk
[email protected] said:
Download the exact same stock firmware you are currently on from Sammobile.com that way you almost eliminate your chances of a bootloop
for your device and flash it in odin in ap /pda slot as long as you don't wipe in recovery or do a nand erase your data should still be there
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
thanks...will go ahead and give this a try.
baddison said:
thanks...will go ahead and give this a try.
Click to expand...
Click to collapse
did not work...turns out the harddrive is bad. device doesn't even stay on long enough to boot up after the firmware install. even opened it up and swapped out the battery. ended up resetting to factory default, which also did not complete successfully, cause the device keeps rebooting and doesn't stay on long enough for the reset to complete....
thanks anyway.
Hi All,
First, thanks for clicking into my question! This is my first post, but I've been lurking here since I used to flash new roms on my original Nexus on a frequent basis, and a Gen1 Kindle Fire before that.
My fiancee is in a bind with her Pixel 2, so I'm hoping you all can help me out.
Her Pixel 2 threw a bunch of app errors over the course of two days, so she opted to reboot -- unfortunately it now locks up at the loading screen, with the Google 'G' and a loader bar (she's running the latest 8.1, pre-Pie) and hangs there, overheating until the battery runs out and we shut it down. We can get into the Recovery menu, but none of the reboot options there seem to help, and there is only the Factory Reset option remaining that we haven't tried.
This happened in the middle of a huge camping excursion as her Bachelorette, so there was limited WiFi and data access to back anything up -- so locked behind that endless boot sequence is a lot of irreplaceable images and video.
What are my options to pull the user data out of there before a factory reset? Is it possible on a (stock, non-root, Google sourced) phone to flash the Pie update? Would that restore functionality?
Can I get to the data somehow through ADB without the phone booting up and unlocked?
Maybe something crazy, like a take a full image of the phone that I then shove on the replacement Pixel 2 that Google is sending us?
Any guidance would be much appreciated!
You could try booting to TWRP with "fastboot boot <filename here>". Then copy the files from there. I'm not sure if this will work if she had the screen locked beforehand though. You could also try flashing the latest factory image but make sure your remove the "-w" from the flash-all.bat file before running the script so it will not wipe user data. Both of these options might not be possible though if you do not have the boot-loader unlocked.
cynnican said:
Hi All,
First, thanks for clicking into my question! This is my first post, but I've been lurking here since I used to flash new roms on my original Nexus on a frequent basis, and a Gen1 Kindle Fire before that.
My fiancee is in a bind with her Pixel 2, so I'm hoping you all can help me out.
Her Pixel 2 threw a bunch of app errors over the course of two days, so she opted to reboot -- unfortunately it now locks up at the loading screen, with the Google 'G' and a loader bar (she's running the latest 8.1, pre-Pie) and hangs there, overheating until the battery runs out and we shut it down. We can get into the Recovery menu, but none of the reboot options there seem to help, and there is only the Factory Reset option remaining that we haven't tried.
This happened in the middle of a huge camping excursion as her Bachelorette, so there was limited WiFi and data access to back anything up -- so locked behind that endless boot sequence is a lot of irreplaceable images and video.
What are my options to pull the user data out of there before a factory reset? Is it possible on a (stock, non-root, Google sourced) phone to flash the Pie update? Would that restore functionality?
Can I get to the data somehow through ADB without the phone booting up and unlocked?
Maybe something crazy, like a take a full image of the phone that I then shove on the replacement Pixel 2 that Google is sending us?
Any guidance would be much appreciated!
Click to expand...
Click to collapse
ADB sideload the latest OTA zip in stock recovery, that should get you up and running again without needing a wipe
crixley said:
ADB sideload the latest OTA zip in stock recovery, that should get you up and running again without needing a wipe
Click to expand...
Click to collapse
Thank you! I'll be giving this a try as soon as she's home on Monday.
Does recovery mode automatically enable the USB Debugging that ADB uses?
cynnican said:
Thank you! I'll be giving this a try as soon as she's home on Monday.
Does recovery mode automatically enable the USB Debugging that ADB uses?
Click to expand...
Click to collapse
Yep you can sideload without needing it toggled in developer mode
crixley said:
Yep you can sideload without needing it toggled in developer mode
Click to expand...
Click to collapse
This worked perfectly, thank you!
cynnican said:
This worked perfectly, thank you!
Click to expand...
Click to collapse
I'm glad to hear! Nothing worse than having to wipe and losing important things you can't get back. I've had that happen a few times. Happy to help.
I'm not very technical - please keep this in mind with my query below.
I have a Pixel 2 which overnight stopped working - my guess is that it rebooted due to an automated software update.
I now only get the page with the robot on it's back.
Options in green on this page are Barcodes, Power Off, and Start.
After reading a lot online I've tried all the usual key press combinations to no avail.
I've also downloaded ADB and FASTBOOT to my Mac.
ADB doesn't see the phone when plugged in via USB (ie. ADB DEVICES doesn't return anything)
FASTBOOT DEVICES does, however, show the serial number as listed on the page with the robot on it's back (and the -l option adds "usb:" plus an 8 digit number and the letter "X"
FASTBOOT REBOOT restarts the phone and brings me back to the robot on it's back page.
Other information on the Robot on it's back page include -
Product Revision: walleye MP1
Boot-slot: b
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: locked
Advice online suggests I need to unlock the phone, so I've tried FASTBOOT FLASHING UNLOCK, and FASTBOOT OEM UNLOCK but neither work.
When I try these I get "FAILED (remote: Flashing Unlock is not allowed)"
An article on Android Police suggests this may have been a bug on the Pixel 2 originally and that it's now resolved.
Unfortunately, my cat 22 situation seems to be that I need to do a factory reset, but the steps I've found as to how to do a factory reset all lead back to the Robot on it's back page, so I can't see how to move forward to with recovering my phone?
Can anyone help please?
Really frustrated that my new phone can put itself into this state without me having done anything and that it's seemingly impossible to recover from this state now that it's in it.
At very least I'd like to wipe all data from the phone so I can send it off for repair.
Thanks in advance.
Anyone, please help, I charge the phone overnight at normal, wake up in the morning the phone is in bootloop Forever!
(It's Samsung A51 Global version, A515F with the 5/18 firmware stock ROM, NO rooting, No custom ROM)
I even try Reiboot's repair function multiple times and it didn't work. It did re-apply the latest Firmware to the phone for me but still cannot boot to android.
The phone is able to boot to recovery mode only, I cleaned up the dust of the internal also as it has no warranty at all.
I am not attempting to fix the phone, I just wanna pull all the files of the internal memory back before I can factory reset it in Recovery mode.
I have the USB debugging activated. Any questions or details please ask, I can replace it with a new phone, but at least I can pull the data out, or better yet, able to boot it to the android system, I tried the safe mode method NOT working.
Any helps appreciated, from my history of android phones start with the Nexus One, only experiences with broken screens, touch screen not working...... never experience like this cannot access anything before
To pull out data out from phone requires you can access phone in ADB mode. My guess is this isn't possible at all due of phone's boot-looping, what means a stable ADB connection can't get established.
jwoegerbauer said:
To pull out data out from phone requires you can access phone in ADB mode. My guess is this isn't possible at all due of phone's boot-looping, what means a stable ADB connection can't get established.
Click to expand...
Click to collapse
I can access Download mode is that enable the ADB, or when it's in download mode if I plug it to a PC, it'll detect the system like a thumb drive?