My Mother in law, ended up with her phone going through a bootloop.
She could not start anything and just kept showing google screen and restarting.
Then ended getting one of our backup phones to use.
Well as some people with technology she never ended up backing up any of her pictures that she has on her phone..
I myself have rebooted into bootloader and still cannot get anything off phone.
My windows pc does not see the nexus device, except my Honor 8 program , but that doesnt let me connect to it.
Adb sees the phone as well.
When looking at fastboot mode, it says secure boot enabled, and devices state locked.
Anyone have a good idea how to get the internal SD data ?
Thank you,
I was able to somehow get the phone to boot. Really not sure how.
Either way I ended up getting developer option up and connected PC,
Moved all the video and pictures to the PC.
Now on to seeing what I have to do to repair the phone, possibly custom recovery .
The boot loop could be due to a power button problem.
Related
Basically I was using TWRP to wipe my TF700T and I wiped the OS. Luckily I made a recovery on my SD, but the problem is that I can't get it to boot back into TWRP in order to run it. All the Power + Volume Down does is just cause the device to rumble. Powering on the device just lets it sit in the bootscreen. If I can get into the bootloader I can basically fix the machine. Problem I have remaining is that I can't seem to get into the bootloader.
The device calls itself APX when plugged into my computer now, if that means anything. I'm gonna try to drain the battery by leaving it on over night without the flash card. Maybe that'll do something.
Any suggestions on how to unbrick this thing? Or did I just succeed in turning a very expensive tablet into a very expensive paperweight?
JunoZXV said:
Basically I was using TWRP to wipe my TF700T and I wiped the OS. Luckily I made a recovery on my SD, but the problem is that I can't get it to boot back into TWRP in order to run it. All the Power + Volume Down does is just cause the device to rumble. Powering on the device just lets it sit in the bootscreen. If I can get into the bootloader I can basically fix the machine. Problem I have remaining is that I can't seem to get into the bootloader.
The device calls itself APX when plugged into my computer now, if that means anything. I'm gonna try to drain the battery by leaving it on over night without the flash card. Maybe that'll do something.
Any suggestions on how to unbrick this thing? Or did I just succeed in turning a very expensive tablet into a very expensive paperweight?
Click to expand...
Click to collapse
Im having exactly the same problem, did you find a solution to this?
So far no results yet. I tried hitting the reset button on the side but all that did was lead me back to the boot screen. I read something about undoing the the hard boot using a series of override programs. But the problem is the documentation is so cluttered that I can't fathom the instructions (I'll try it again just in case.)
Bump update: So I called Asus and it turns out it's gonna cost 288$ to get the thing fixed by them. So I'm not doing that. I'm looking into other ways of recovery. I've got other multiple options I'm exploring at the moment. Like looking for a recycling program or a way to use the technology in a new way.
UPDATE X2
So I talked to a friend and the very fact that it sits at APX was a tipoff. Basically it means the recovery is shot but the Bootloader is OK. Meaning that the device isn't as bricked as I thought. What needs to be done is to download the android ADT bundle (google it) and from there get into the platform tools under command prompt, type "adb" then "adb devices" and finally "adb reboot recovery"
if it works the recovery should reflash and then using the backup restore the OS.
Granted I'm having trouble getting my comptuer to say "APX has been connected" due to a faulty data cable but I should be home free after this
JunoZXV said:
UPDATE X2
So I talked to a friend and the very fact that it sits at APX was a tipoff. Basically it means the recovery is shot but the Bootloader is OK. Meaning that the device isn't as bricked as I thought. What needs to be done is to download the android ADT bundle (google it) and from there get into the platform tools under command prompt, type "adb" then "adb devices" and finally "adb reboot recovery"
if it works the recovery should reflash and then using the backup restore the OS.
Granted I'm having trouble getting my comptuer to say "APX has been connected" due to a faulty data cable but I should be home free after this
Click to expand...
Click to collapse
Unfortunately if you can only get to APX mode and you don't have nvflash specific blobs for your device you are hard bricked...
Luckily I make a recovery file in my SD card wayy back when I did my first Cromi mod. It should still work if the forced recovery restores TWRP. Otherwise, yes, I might be hard bricked.
My friend, however, thinks there might be another way to force a OS past this block though. I'll have to see how this plays out.
JunoZXV said:
Luckily I make a recovery file in my SD card wayy back when I did my first Cromi mod. It should still work if the forced recovery restores TWRP. Otherwise, yes, I might be hard bricked.
My friend, however, thinks there might be another way to force a OS past this block though. I'll have to see how this plays out.
Click to expand...
Click to collapse
Sorry it really doesn't look good, Maybe i can corrected but the device will fallback to APX mode if the bootloader is corrupted, without a bootloader you cant install/fix a recovery and without NvFlash blobs you cant fix the bootloader. Your two options are buy a new motherboard and replace it yourself or send it in for repair with Asus
JunoZXV said:
Luckily I make a recovery file in my SD card wayy back when I did my first Cromi mod. It should still work if the forced recovery restores TWRP. Otherwise, yes, I might be hard bricked.
My friend, however, thinks there might be another way to force a OS past this block though. I'll have to see how this plays out.
Click to expand...
Click to collapse
As JTR says I'm pretty sure you can't fix this without replacing the hardware now. I don't think your friend really understands what APX mode is. YOu can't access the bootloader nor recovery. Without NVflash backup blobs you can't recover anything, there is no way to get your TWRP backups back on to the device and even if you could you have no working bootloader......
Hello there, recently I tried to get TWRP for my LG G2, and I kept trying over and over again to where my phone's booting got stuck in a loop and began making a lot of drives. Luckily, I found http://forum.xda-developers.com/showthread.php?t=2582142 and got to the point where I could get into TWRP. The problem is, now I can't boot up into the normal rom, which I'm guessing has been erased through TWRP and my own stupidity. So I have no roms to flash either, and in addition, my screen is screwed up, and while I can navigate TWRP, I have a very hard time doing it. Also, whenever I plug my phone in to my computer, it just shows up as 'g2' in the device manager, and is an unknown device. I have tried adb sideloading a rom but it always gives me 'error:closed'.
So let's round that up since I kinda rambled there.
Screwed my phone up by trying to get TWRP and it ended up booting in a loop and making a ton of drives.
Was able to fix this and am now able to get into TWRP, but the touch screen is going crazy and I have a hard time navigating TWRP
Whenever I try to use adb with my phone, command prompt says 'error:closed'
The device manager calls my phone 'g2' and thinks it's an unknown device.
I swear, if anyone here can help me get this phone to where it's booting up correctly again, you are incredible.
Thanks!
whynottry said:
Hello there, recently I tried to get TWRP for my LG G2, and I kept trying over and over again to where my phone's booting got stuck in a loop and began making a lot of drives. Luckily, I found http://forum.xda-developers.com/showthread.php?t=2582142 and got to the point where I could get into TWRP. The problem is, now I can't boot up into the normal rom, which I'm guessing has been erased through TWRP and my own stupidity. So I have no roms to flash either, and in addition, my screen is screwed up, and while I can navigate TWRP, I have a very hard time doing it. Also, whenever I plug my phone in to my computer, it just shows up as 'g2' in the device manager, and is an unknown device. I have tried adb sideloading a rom but it always gives me 'error:closed'.
So let's round that up since I kinda rambled there.
Screwed my phone up by trying to get TWRP and it ended up booting in a loop and making a ton of drives.
Was able to fix this and am now able to get into TWRP, but the touch screen is going crazy and I have a hard time navigating TWRP
Whenever I try to use adb with my phone, command prompt says 'error:closed'
The device manager calls my phone 'g2' and thinks it's an unknown device.
I swear, if anyone here can help me get this phone to where it's booting up correctly again, you are incredible.
Thanks!
Click to expand...
Click to collapse
Hey Pal try -> http://forum.xda-developers.com/showthread.php?t=2663369 but you will wipe everything on your phone but at least you can start with a 100% working G2 D800!
Crap I forgot to mention I can't go into download mode. Sorry about that..
atmxpert said:
Hey Pal try -> http://forum.xda-developers.com/showthread.php?t=2663369 but you will wipe everything on your phone but at least you can start with a 100% working G2 D800!
Click to expand...
Click to collapse
Hello!
I purchased my HTC One M8 from Verizon about a month and a half ago. I love the phone, and it hasn't caused me any issues at all - until a few days ago. I went to pick up my phone and the screen was off; I couldn't turn the phone on.
After fidgeting with the power/up+down buttons, I got it to load the boot loader. I tried almost every option on the menu in there, and I seem to be stuck in a boot loop. When I try hooking up my phone to my PC, HTC Sync loads but says there is no device connected. My PC doesn't recognize the device, either. I've never tried to root the device or anything, so it's "Locked" with S-ON.
I am trying to figure out if I can get my photos off of the device before I send it into Verizon for a replacement. I (stupidly) thought that the photos were being automatically backed up on Google, and I never put my SD card into the phone.
Does anyone know if or how I can do this? I'm not a developer, but I'm pretty technical, so any step-by-step advice would help!
Thank you!
You may be able to issue an "adb pull" of the data partition if you have adb setup on a computer. You should Google it and see if you can get adb up and running.
cntryby429 said:
You may be able to issue an "adb pull" of the data partition if you have adb setup on a computer. You should Google it and see if you can get adb up and running.
Click to expand...
Click to collapse
Thank you! I'll let you know if I can get in that way.
So this was what happen, i have been trying to format my phone this day to put a rom and i had an issue (that which never happend to me) my phone was always getting an error either on Parse, or Vendor check, i kinda decided to install TWRP on bootloader as i thought i could go around, but figure out i had to download the files, since i didnt want to lose time what i actually did, was flashing the phone again to see if the phone could go further.. but the phone didnt want to pass to that phase.. i was getting impatient.. i disconnected the cable or "how we can say i closed the program multiple time betwen a flash.
I was on 1909. My bootloader was detected everything was detected the phone everything, but since i thought that windows 10 version 1909 might had something with it, i thought "well why not download a recent version" take in mind i have no option, i have no recovery, i tried already to acess it by pressing and hold POWER UP, it returns right away to fastboot, my phone name isnt detected under device manager, nor when i do adb devices, fastboot devices detects it, and i tried already some commands like passing the TWRP to it, but it doesnt overwrite anything, sometimes i get the error"No devices or emulators found" .
Im lost i think i lost my phone, im desperate
Any expert here that can help me with this?
Im gonna try to go back to an early windows 1809, which i used to format this phone a lot to other rom
Meanwhile i need some help on this
Hi all,
Im in a desperate and urgent need of help.
My Mrs pixel 7 pro is stuck in a boot loop that restarts 5 seconds after the google writing appears when starting. I wasn't home when it happened but she doesnt really make sure her phone has some battery before turning it on, as soon as she sees 2% she starts it, so im guessing maybe she bricked it while the phone was trying to apply an update when turning it on as she said that the external battery didnt have any juice left inside.
Anyway,
I know i can wipe the phone from recovery mode and make it into a factory reset phone. The issue here is we have over 6000 photos and videos of our son in that phone that she hasnt copied to the external hard drive i gave her for months due to her not liking that her little laptop is slow.
I tried recovery mode Reboot, i tried going into safe mode (no luck as it will go straight into fastboot mode). She doesnt care about a lot of things and obviously she never unlocked the developer setting or bootloader so device state is also locked.
I am begging you, anything any info or advice on how i can get those pictures out of the phone. Is there any way i can flash the stock firmware just to make the phone start and copy them after?
Any possibility or chance or retrieval?
I am willing to pay anyone that can guide me in the right direction as there are over 6 months worth of photos and memories.
Thanks in advance and may the luck be on my side.
andyysk said:
Hi all,
Im in a desperate and urgent need of help.
My Mrs pixel 7 pro is stuck in a boot loop that restarts 5 seconds after the google writing appears when starting. I wasn't home when it happened but she doesnt really make sure her phone has some battery before turning it on, as soon as she sees 2% she starts it, so im guessing maybe she bricked it while the phone was trying to apply an update when turning it on as she said that the external battery didnt have any juice left inside.
Anyway,
I know i can wipe the phone from recovery mode and make it into a factory reset phone. The issue here is we have over 6000 photos and videos of our son in that phone that she hasnt copied to the external hard drive i gave her for months due to her not liking that her little laptop is slow.
I tried recovery mode Reboot, i tried going into safe mode (no luck as it will go straight into fastboot mode). She doesnt care about a lot of things and obviously she never unlocked the developer setting or bootloader so device state is also locked.
I am begging you, anything any info or advice on how i can get those pictures out of the phone. Is there any way i can flash the stock firmware just to make the phone start and copy them after?
Any possibility or chance or retrieval?
I am willing to pay anyone that can guide me in the right direction as there are over 6 months worth of photos and memories.
Thanks in advance and may the luck be on my side.
Click to expand...
Click to collapse
If you can enter recovery mode try to sideload the same exact ota package of the rom she's running, maybe that can help. Good luck!
andyysk said:
Hi all,
Im in a desperate and urgent need of help.
My Mrs pixel 7 pro is stuck in a boot loop that restarts 5 seconds after the google writing appears when starting. I wasn't home when it happened but she doesnt really make sure her phone has some battery before turning it on, as soon as she sees 2% she starts it, so im guessing maybe she bricked it while the phone was trying to apply an update when turning it on as she said that the external battery didnt have any juice left inside.
Anyway,
I know i can wipe the phone from recovery mode and make it into a factory reset phone. The issue here is we have over 6000 photos and videos of our son in that phone that she hasnt copied to the external hard drive i gave her for months due to her not liking that her little laptop is slow.
I tried recovery mode Reboot, i tried going into safe mode (no luck as it will go straight into fastboot mode). She doesnt care about a lot of things and obviously she never unlocked the developer setting or bootloader so device state is also locked.
I am begging you, anything any info or advice on how i can get those pictures out of the phone. Is there any way i can flash the stock firmware just to make the phone start and copy them after?
Any possibility or chance or retrieval?
I am willing to pay anyone that can guide me in the right direction as there are over 6 months worth of photos and memories.
Thanks in advance and may the luck be on my side.
Click to expand...
Click to collapse
As @acuicultor said;
Here's Googles official OTA updates and instructions etc.
From what i've read briefly and as far as i can gather (still running a stock pixel 7 pro - for the first phone in god knows how long, so i'm not well read on this device but...) if you can sideload the latest OTA update via sideload then you should in theory be able to save the data and boot again. But if you flash full firmware then your device will be wiped in the process (if that's even possible with a locked bootloader).
Very best of luck
EDIT: hmm thinking about it, you won't have enabled USB debugging in dev options, hang on, i'll reboot direct to recovery to see if i can get the device recognised without USB debugging enabled. Sorry to be vague (hopefully someone more experienced with this device will chime in with more advice), like i say, i'm not rooted, flashed with custom rom - nothing, just plain old stock so i've not read up much on proceedures for this device. Bare with me!!
Had another thought, do you or have you been using Google photos to view your images on the device. If so, did you enable backup photos online when you first set the app up? If so, they could be backed up automatically...
Edit: my bad..
Try this link
If that fails just Google 'Google photos sign in'
Just tried from recovery to run some adb cmd's, no joy without enabling debugging 1st
There may be hope... If your photos aren't backed online already from above link...
EDIT:
1. From power off state (make sure the device is charged before apply any ota update) Press vol down and power together. As soon as it boots to google logo, let go of vol down, then power. That will put you in fastboot mode where you use the vol up/down to navigate to Recovery mode and power button to select.
2. Then when you have the screen that says 'no command', press power button and CLICK vol up (releasing vol up straight away but keeping power pressed). That'll take you a blue menu at top of screen.
3. Use vol buttons to navigate to 'apply update from adb'. I have checked using 'adb devices' and 'adb reboot sideload' cmd's on PC and the device is now recognised...
Will write further instructions shortly. (no guarantees this will work tho without losing data...or even if it'll work at all - i suspect the OTA update with just fail to transfer)
OR there is another option, using the same instructions above (1) in fastboot mode use the volume buttons to navigate the menu, power button to select Rescue mode. Then contact your service center for support who will advise/offer support - hopefully, which may end up having to send the device in and still offers no guarantee of preserved data
reg66 said:
@acuicultor said;
Here's Googles official OTA updates and instructions etc.
Click to expand...
Click to collapse
Following the link it's all explained there:
- no USB-Debugging needed
- booting recovery by key combo
- no loss of any data when using the OTA files
Also turning on USB-Debugging in developer options is not necessary for the recovery. It's enabled by default and moreover the recovery doesn't consider any system settings like disabled/enabled USB-Debugging.
WoKoschekk said:
Following the link it's all explained there:
- no USB-Debugging needed
- booting recovery by key combo
- no loss of any data when using the OTA files
Also turning on USB-Debugging in developer options is not necessary for the recovery. It's enabled by default and moreover the recovery doesn't consider any system settings like disabled/enabled USB-Debugging.
Click to expand...
Click to collapse
Ahh cool. I obviously didn't read much of it! Dunno what's happened to the chap, maybe his wife has killed him lol
reg66 said:
Ahh cool. I obviously didn't read much of it! Dunno what's happened to the chap, maybe his wife has killed him lol
Click to expand...
Click to collapse
yes, maybe...
FYI: Stock recovery only uses a minimal adbd with a very limited set of commands. That's why some known ADB commands won't work.
minadbd