Greetings. My Nextbit Robin one day powered off. I had developer mode on before. Now whenever I try and boot the phont it simply goes through the animation and right when it should boot me into android os, it crashes back to a black screen. I cannot flash or fastboot or sideload anything as I do not have adb nor oem unlocked since the device itself is locked and cannot be unlocked without typing in the password in android OS. My goal is only to save the files stored in the phone not the phone itself. Any and all help would be appreciated.
IMO as long as phone isn't accessible via ADB ( and phone's Android got rooted ) there's no chance to fetch user-data stored on phone.
jwoegerbauer said:
IMO as long as phone isn't accessible via ADB ( and phone's Android got rooted ) there's no chance to fetch user-data stored on phone.
Click to expand...
Click to collapse
Thanks for the reply, do you know if its possible to extract the data using hardware, like phyiscally solder out the memory?
Related
So, Ive tried to boot into fastboot and recovery on my xperia z3 and I get nothing but a black screen. Is this normal? Ive tried the adb commands to reboot into fastboot and recovery and still nothing but a black screen. Ive tried volume up and plugging in the USB cable and get the blue LED and a black screen. Ive tried the powering on and pressing volume up and down repeatedly and still nothing.
I have the T Mobile International supposedly Factory Unlocked version 6603.
Also, whats the point in having a SD card to expand memory if you cant install any apps to it? I understand that you can put music and such on there but if you start installing any large games the 16GB internal is gone quick and you cant put any apps on the SD Card.
This phone is great but cant install to the SD, cant change the install location as its not supported in Kit Kat. Sony's ROM doesn't allow move to SD anymore, cant boot to fastboot to flash can view recovery..perhaps there is something I have not read about this phone yet in the forums.
Anybody have any sugestions?
J
There is no stock recovery on xperia devices, you need to install one yourself. Also, there is no UI on the phone when in fastboot. You can just send fastboot commands from a terminal on your PC
Currently the only was to do that is to unlock the bootloader (Just google "Sony unlock bootloader" to find out how to do that) then flash a custom kernel from the development sections to get recovery and root
Terminal doesn't show any devices connected. Can't start a shell nothing in fastboot. I have not tried to use the command to flash the kernal I guess that works?
There is really no fastboot menu just a black screen huh? Strange
Jason0071 said:
Terminal doesn't show any devices connected. Can't start a shell nothing in fastboot. I have not tried to use the command to flash the kernal I guess that works?
There is really no fastboot menu just a black screen huh? Strange
Click to expand...
Click to collapse
Yes just a black screen.
Have you unlocked the bootloader? Have you installed ADB and fastboot drivers?
No I've not done these things yet. I was thinking there was something wrong with my device. It seems it's functioning correctly. I'll proceed with unlocking the boot loader and see how it goes
Jason0071 said:
No I've not done these things yet. I was thinking there was something wrong with my device. It seems it's functioning correctly. I'll proceed with unlocking the boot loader and see how it goes
Click to expand...
Click to collapse
Make sure you read the warning first
What's the worst besides bricking the phone?
Jason0071 said:
What's the worst besides bricking the phone?
Click to expand...
Click to collapse
You will loose some of what makes Sony camera so good on this phone + some audio / video post processing.
Myself, I have rooted immediately after getting this phone since coming from HTC phones I did not expect any noteworthy disadvantages only to learn later that I have reduced the phone's functionality forever.
I still like a phone a lot; but it bothers me that a lot of functionality in this phone is based on software wizardry rather than hardware quality.
Being so used to flash custom ROMs often I am beginning to realize that Sony might not be such a great choice, although, once again Z3 (dual) I own has a lot going for it compared to current HTC phones.
Agreed opted not to root
Hello everyone!
My OPO can't boot into CM12 anymore and I can only get it into fastboot. USB Debugging is disabled and the bootloader is locked, basically it is completely stock.
I want to save my media though... I tried using adb pull but I can only use fastboot.
What do I do? Really important pictures on my phone...
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.
I've got a Galaxy S6 that was previously authorised for ADB debugging so I can still view the screen using scrcpy and access it via the adb command. However, when viewing it on scrcpy it is stuck on the Android is starting... screen and says Starting apps.
I've left it on and connected for 2 days and can't get past this screen, even after trying to start it in safe mode. I can't clear any cache or anything as I can't access the device in recovery mode.
I have two essential authenticators on this (AWS and one other) that I need access to so I can transfer them to another device, so I can't lose the data that's on the device either.
Does anyone have any suggestions? I'm desperate at this point.
geekoid said:
I've got a Galaxy S6 that was previously authorised for ADB debugging so I can still view the screen using scrcpy and access it via the adb command. However, when viewing it on scrcpy it is stuck on the Android is starting... screen and says Starting apps.
I've left it on and connected for 2 days and can't get past this screen, even after trying to start it in safe mode. I can't clear any cache or anything as I can't access the device in recovery mode.
I have two essential authenticators on this (AWS and one other) that I need access to so I can transfer them to another device, so I can't lose the data that's on the device either.
Does anyone have any suggestions? I'm desperate at this point.
Click to expand...
Click to collapse
have you reflashed stock firmware?
youdoofus said:
have you reflashed stock firmware?
Click to expand...
Click to collapse
No, I have not flashed any firmware. The device crashed one time previously and since then it's been like I described above every time I start it.
geekoid said:
No, I have not flashed any firmware. The device crashed one time previously and since then it's been like I described above every time I start it.
Click to expand...
Click to collapse
boot to d/l mode and reflash the factory firmware from sammobile.com/firmwares
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?