Hey guys. It's been awhile since I've tinkered with the M8, and I guess I'm a little out of touch. (no pun intended)
The phone was dropped and I have insurance with it from AT&T through Asurion, so I put a claim in for it and I guess they don't have M8s at the moment because they're getting me an M9, which is cool. I don't know what their policy is on sending back rooted phones. I mean it's insurance....not a warranty necessarily, so idk if it's a big deal or not.
....anyway,
I'm working from a Windows 7 PC. It's a different win 7 then when I originally rooted the M8 and put the recovery on, but it'll sync up alright. I I type in "adb reboot bootloader" and it restarts fine, but once I get to the bootloader, I type in "fastboot flash recovery recovery.img" and I get a message saying it can't be loaded. When I go to type in the command "adb reboot bootloader" from the bootloader to restart it, it says the device <null> isn't connected. I can run the "fastboot flash recovery recovery.img" command when the phone is booted to the rom, and it seems to take it, but it gets hung up and just says "waiting on device"
So I'm not sure. I've reinstalled the drivers a few times but I'm still getting the same results. I just wanted to put it back to the way it was so I don't catch any flack from the insurance company, but for all I know they probably won't even care. Any advice would be appreciated. I'm going to keep messing around with it, but I don;t seem to be getting anywhere.
Thanks, guys.
The phone was dropped and I have insurance with it from AT&T through Asurion, so I put a claim in for it and I guess they don't have M8s at the moment because they're getting me an M9, which is cool. I don't know what their policy is on sending back rooted phones. I mean it's insurance....not a warranty necessarily, so idk if it's a big deal or not.
....anyway,
I'm working from a Windows 7 PC. It's a different win 7 then when I originally rooted the M8 and put the recovery on, but it'll sync up alright. I I type in "adb reboot bootloader" and it restarts fine, but once I get to the bootloader, I type in "fastboot flash recovery recovery.img" and I get a message saying it can't be loaded. When I go to type in the command "adb reboot bootloader" from the bootloader to restart it, it says the device <null> isn't connected. I can run the "fastboot flash recovery recovery.img" command when the phone is booted to the rom, and it seems to take it, but it gets hung up and just says "waiting on device"
So I'm not sure. I've reinstalled the drivers a few times but I'm still getting the same results. I just wanted to put it back to the way it was so I don't catch any flack from the insurance company, but for all I know they probably won't even care. Any advice would be appreciated. I'm going to keep messing around with it, but I don;t seem to be getting anywhere.
Thanks, guys.
Aucun commentaire:
Enregistrer un commentaire