So i recently tried flashing a new kernel and for whatever reason my pixel 2 did not like that at all. Upon reboot after flashing it now just goes into the download mode where i have the option to reboot bootloader go into recovery and go into download mode. Normally not a big issue at all but this time when i go to load into recovery or load into Download mode its says Operation Denied. Upon a reboot or trying to reboot into safe mode it says ERROR: Slot unbootable: Load Error. Will ADB still work to flash this? not really sure what to do at this moment.
EDIT: Solved it by using Fastboot and flashing the stock firmware without the -w so far everything is back to normal....know to get that dern kernel again
gears177 said:
So i recently tried flashing a new kernel and for whatever reason my pixel 2 did not like that at all. Upon reboot after flashing it now just goes into the download mode where i have the option to reboot bootloader go into recovery and go into download mode. Normally not a big issue at all but this time when i go to load into recovery or load into Download mode its says Operation Denied. Upon a reboot or trying to reboot into safe mode it says ERROR: Slot unbootable: Load Error. Will ADB still work to flash this? not really sure what to do at this moment.
Click to expand...
Click to collapse
First off, does fastboot recognize the device?
DuckRuckus said:
First off, does fastboot recognize the device?
Click to expand...
Click to collapse
It does not under adb devices nothing shows up. In device manager it does show up as Android bootloader interface
gears177 said:
It does not under adb devices nothing shows up. In device manager it does show up as Android bootloader interface
Click to expand...
Click to collapse
ADB=system. Fastboot=boot. You can't boot your phone, so you're not in android, thus no ADB devices. Type "fastboot devices" and see if it's recognized.
DuckRuckus said:
ADB=system. Fastboot=boot. You can't boot your phone, so you're not in android, thus no ADB devices. Type "fastboot devices" and see if it's recognized.
Click to expand...
Click to collapse
Ah nice didnt even realize its recognized under fastboot ive tried flashing the stock recovery but it just gives me an error
gears177 said:
Ah nice didnt even realize its recognized under fastboot
Click to expand...
Click to collapse
Good news! So, your best bet at this point would be to re-flash your current factory image, with /w removed. If you still want that same kernel, flash it before Magisk.
Just out of curiosity, what method did you use to flash it in the first place?
DuckRuckus said:
Good news! So, your best bet at this point would be to re-flash your current factory image, with /w removed. If you still want that same kernel, flash it before Magisk.
Just out of curiosity, what method did you use to flash it in the first place?
Click to expand...
Click to collapse
Flashed it through twrp aroma installer.
What does the -w do in the fastboot command just curious
Nevermind got it flag responsible for deleting userdata thanks alot for the help appreciate your time
gears177 said:
Flashed it through twrp aroma installer.
What does the -w do in the fastboot command just curious
Click to expand...
Click to collapse
It wipes all your data, that's why you remove it from the flash-all.bat script, unless you need to perform a full wipe. Telperion has an excellent guide for installing the lastest software, if you haven't already read it.
I've heard users having back luck flashing kernels in TWRP, as the kernel has something to do with recovery. I always use the method of booting the TWRP image in fastboot, use ADB to push the files to /tmp, and then do an ADB shell TWRP install of those files. TWRP, kernel, then magisk, in that order. I always reinstall all three, just to be on the safe side, and have never had any issues. Takes a little while, but not as long as redoing the whole freaking thing:silly:
Looks like you figured it out, before I finished my reply
Related
So... Anyone have any experience getting sticky bit turned off on fastboot? My phone boots to it anytime I try to reboot or do a regular boot up.
fallnSaint said:
So... Anyone have any experience getting sticky bit turned off on fastboot? My phone boots to it anytime I try to reboot or do a regular boot up.
Click to expand...
Click to collapse
Mine did that for a short while after I screwed up a flash, I reflashed boot and while running tossed the adb command to get into fastboot and then left it properly. Haven't seen it since.
KitsunePaws said:
Mine did that for a short while after I screwed up a flash, I reflashed boot and while running tossed the adb command to get into fastboot and then left it properly. Haven't seen it since.
Click to expand...
Click to collapse
To clarify... Flash boot from recovery, while that is running adb reboot bootloader? If that is the case I have a different set of problems to "boot", I can't get my pc to recognize the phone while in recovery. Everything else is recognized, even reinstalled drivers to be certain, pc doesn't even try to install a driver for recovery. Tried both TWRP & CWM.
fallnSaint said:
To clarify... Flash boot from recovery, while that is running adb reboot bootloader? If that is the case I have a different set of problems to "boot", I can't get my pc to recognize the phone while in recovery. Everything else is recognized, even reinstalled drivers to be certain, pc doesn't even try to install a driver for recovery. Tried both TWRP & CWM.
Click to expand...
Click to collapse
Memory is fuzzy but I'm pretty sure I did it from fastboot, this happened to me about the time shabby was trying to fastboot boot boot.img and I ended up flashing it instead.
KitsunePaws said:
Memory is fuzzy but I'm pretty sure I did it from fastboot, this happened to me about the time shabby was trying to fastboot boot boot.img and I ended up flashing it instead.
Click to expand...
Click to collapse
I had this same issue when porting TWRP ^^^.
I can't seem to find my posts on it right now, but someone just said do a clean flash. No problems since
how did you do this please!
fallnSaint said:
So... Anyone have any experience getting sticky bit turned off on fastboot? My phone boots to it anytime I try to reboot or do a regular boot up.
Click to expand...
Click to collapse
Okay, this will probably help you...while your device is in Sticky Bit Factory Fastboot, open up a command prompt and connect to your device (given you know how to do so in your folder containing your fastboot app and drivers). Then type "fastboot oem fb_mode_clear" This command will allow your device to boot into system normally. Problem is (I think) when a failed flash occurs sometimes it sets your device in that mode and the above command clears it. Another way to manually place a device in the same state you described is to enter this command using fastboot: fastboot oem fb_mode_set. I believe that is how RSD Lite automatically reboots your device into factory fastboot mode after flashing partitions (.mbn) on your system so that it may resume flashing the boot, recovery, and system images, etc. Let me know if it helps.....
Sent from my XT897 using xda premium
I have a TF300t that I have been doing custom ROMs on for over a year now. Not to long ago it messed up and I ended up doing a ADB side load of the the current software from ASUS to recover it. I wanted to try CM11 so I followed the directions to get the right version of TWRP installed. I noticed that it was really slow at stuff like wiping cache and dalvik, so I decided to reflash TWRP through ADB instead of a zip file.
All went well and I got into android and went into TWRP to see if everything went okay. I'm in TWRP, but I cannot do anything. Only system will mount and it says I am not rooted and wants to install supersu. If I reboot or power off it just goes back into recovery. Doing the power + vol down will not get me into the bootloader and will instead just power cycle at the ASUS logo.
Any idea on how to fix this, or did I just royally brick my tablet?
tjk639 said:
I have a TF300t that I have been doing custom ROMs on for over a year now. Not to long ago it messed up and I ended up doing a ADB side load of the the current software from ASUS to recover it. I wanted to try CM11 so I followed the directions to get the right version of TWRP installed. I noticed that it was really slow at stuff like wiping cache and dalvik, so I decided to reflash TWRP through ADB instead of a zip file.
All went well and I got into android and went into TWRP to see if everything went okay. I'm in TWRP, but I cannot do anything. Only system will mount and it says I am not rooted and wants to install supersu. If I reboot or power off it just goes back into recovery. Doing the power + vol down will not get me into the bootloader and will instead just power cycle at the ASUS logo.
Any idea on how to fix this, or did I just royally brick my tablet?
Click to expand...
Click to collapse
When you first reboot back into TWRP, try running fastboot commands. You may be able to reflash your recovery, or follow Buster's recovery method from there on.
cmendonc2 said:
When you first reboot back into TWRP, try running fastboot commands. You may be able to reflash your recovery, or follow Buster's recovery method from there on.
Click to expand...
Click to collapse
I just get stuck at waiting for device. Is there a section I am supposed to be in? Or do I do it from the home screen for twrp? I checked device manager and it does have Transformer listed in other devices.
tjk639 said:
I just get stuck at waiting for device. Is there a section I am supposed to be in? Or do I do it from the home screen for twrp? I checked device manager and it does have Transformer listed in other devices.
Click to expand...
Click to collapse
Use the reset pin on the SD card side and then reboot back into TWRP and try with "fastboot devices"
cmendonc2 said:
Use the reset pin on the SD card side and then reboot back into TWRP and try with "fastboot devices"
Click to expand...
Click to collapse
Where do I find "fastboot devices"?
tjk639 said:
Where do I find "fastboot devices"?
Click to expand...
Click to collapse
As in the command:
Code:
fastboot devices
Else you could try:
Code:
adb reboot bootloader
from the ADB in TWRP and then try fastboot commands.
cmendonc2 said:
As in the command:
Code:
fastboot devices
Else you could try:
Code:
adb reboot bootloader
from the ADB in TWRP and then try fastboot commands.
Click to expand...
Click to collapse
It's not finding anything and ADB sideload fails. I'm doing the fastboot commands from the fastboot folder I have been using with other fastboot stuff for the TF300.
tjk639 said:
It's not finding anything and ADB sideload fails. I'm doing the fastboot commands from the fastboot folder I have been using with other fastboot stuff for the TF300.
Click to expand...
Click to collapse
hmm idk. Im guessing you flashed the wrong version of TWRP, which has ended up in a brick for most users, but they had fastboot access and could later recover it using this: http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12. You dont seem to have either ADB or fastboot, and TWRP is in a non working state. You could try reinstalling your fastboot and ADB drivers with the universal naked drivers, and then retrying ADB reboot bootloader and fastboot.
All fixed!
Here is what I did.
1.) Installed naked drivers following the guide at the link provided above. This allowed me to get into the bootloader, but I was unable to successfully flash anything.
2.) So, I followed this guide: http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Probably lost all my user data, but worth it for a working tablet.
HUGE thanks to cmendonc2 for the help and ultimately leading me to the correct solution.
tjk639 said:
All fixed!
Here is what I did.
1.) Installed naked drivers following the guide at the link provided above. This allowed me to get into the bootloader, but I was unable to successfully flash anything.
2.) So, I followed this guide: http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Probably lost all my user data, but worth it for a working tablet.
HUGE thanks to cmendonc2 for the help and ultimately leading me to the correct solution.
Click to expand...
Click to collapse
No problem, glad I could help!
so, i recently updated my oneplus one from cm11 to cm12.1 and when cm12 loaded in, i got a repeated message that com.android.phone has stopped and the quick settings bar displayed that i had no sim card in. so i tried reflashing, and the same problem. i redownloaded and reflashed... same problem.
so, i went into twrp and performed a full wipe, thinking that i'd push a new zip using twrp's mount function. the problem is, when i went to mount, no drive appeared on my computer. and when i went to fastboot to flash it manually, fastboot said that 'Image is not a boot image' . the same thing happens whenever i try to re-flash recovery as well. so how can i get an os back on the system if fastboot won't cooperate and twrp is essentially useless?
tldr; no os on oneplus one, fastboot wont flash boot image, twrp mount and twrp adb wont do anything. What do?
ItsDeadEnd said:
so, i recently updated my oneplus one from cm11 to cm12.1 and when cm12 loaded in, i got a repeated message that com.android.phone has stopped and the quick settings bar displayed that i had no sim card in. so i tried reflashing, and the same problem. i redownloaded and reflashed... same problem.
so, i went into twrp and performed a full wipe, thinking that i'd push a new zip using twrp's mount function. the problem is, when i went to mount, no drive appeared on my computer. and when i went to fastboot to flash it manually, fastboot said that 'Image is not a boot image' . the same thing happens whenever i try to re-flash recovery as well. so how can i get an os back on the system if fastboot won't cooperate and twrp is essentially useless?
tldr; no os on oneplus one, fastboot wont flash boot image, twrp mount and twrp adb wont do anything. What do?
Click to expand...
Click to collapse
What's the exact command you're using with fastboot? Are you only attempting to flash the boot.img? If so, why only that?
Heisenberg said:
What's the exact command you're using with fastboot? Are you only attempting to flash the boot.img? If so, why only that?
Click to expand...
Click to collapse
I am using "fastboot flash boot [zip]" i also tried "fastboot update [zip]", neither of which worked
ItsDeadEnd said:
I am using "fastboot flash boot [zip]" i also tried "fastboot update [zip]", neither of which worked
Click to expand...
Click to collapse
You didn't answer my question, why are you giving that command? There are a dozen or so commands that you're meant to give when flashing with fastboot. The only time you use that command is when you're just trying to flash a kernel.
Heisenberg said:
You didn't answer my question, why are you giving that command? There are a dozen or so commands that you're meant to give when flashing with fastboot. The only time you use that command is when you're just trying to flash a kernel.
Click to expand...
Click to collapse
what commands would you suggest i do then? because those are the only things i used other than the wipe command
ItsDeadEnd said:
what commands would you suggest i do then? because those are the only things i used other than the wipe command
Click to expand...
Click to collapse
Well it depends on what you're trying to do. As I said, the "fastboot flash boot boot.img" command will only flash a kernel. You really shouldn't be messing around with fastboot if you don't actually know what you're doing, that's how phones get bricked. Go to my guide and follow the instructions in section 8:
http://forum.xda-developers.com/showthread.php?t=2839471
[SOLVED]
apparently sometime between me instlling cm11 and installing cm12, my oem got re-locked. which prevented me from flashing anything new.
i ran:
fastboot oem unlock
and fastboot flash boot boot.img
and voila
help thread for those with the same problem
http://forum.xda-developers.com/show....php?t=2839471
thank you for the help!
So I bought my shield tablet back in March, used it until about may I think. Was browsing the internet then it suddenly crashed and got stuck on the Nvidia boot screen. tried to reboot several times. Nothing. So I forgot about it and thought I would just google the reset option later when I had time. Now since June I have tried everything! From factory reset to fast boot and adb my pc won't even recognize my tablet. Also I never turned on usb dbugging cause I didn't even know what that was. I even gave it to the IT guys at work and they couldn't fix it. Now after reading everything there is to read on this problem and trying to fix it myself I'm stuck on the no command screen with the dead android robot. And now I hear there is a recall do to the battery, I can't even check what type I have. So if someone can please help me I would be much appreciative. Also this happened after updating to the latest OS.
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Can you flash twrp and boot to it?
Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Hello,
Did you use "Fastboot flash recovery.img" as your command line??
I believe it is "Fastboot flash recovery recovery.img"
If you were able to unlock bootloader you're on the right track.
Sent from a Locked Bootloader
Yes I used "fastboot flash recovery recovery.img" but every command after that keeps telling me "failed to write file"
danjull said:
Can you flash twrp and boot to it?
Click to expand...
Click to collapse
I'm a complete noob when it comes to this stuff, what is twrp? Haha
Ace0169 said:
I'm a complete noob when it comes to this stuff, what is twrp? Haha
Click to expand...
Click to collapse
TWRP (Team Win Recovery Project) is a custom recovery that you can flash on your device. You can flash it like the stock recovery over fastboot. With TWRP you can make full system backups, installing roms or other stuff, wipe partitions and more. Keep trying to install the drivers on your pc. Try to use another usb slot or boot your pc into test mode to install the driver. If you can still access the bootloader, you have really good chances to rescue your device.
Okay will try that. Thanks man.
Ace0169 said:
Okay will try that. Thanks man.
Click to expand...
Click to collapse
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5
Mojar7070 said:
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5
Click to expand...
Click to collapse
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader
Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
Those official nVidia recovery images come with smaller .img files such as recovery.img, system.img, etc. You'll need to flash those one by one ("fastboot flash recovery recovery.img", then run "fastboot flash system system.img", etc. etc.) or you can just run the flashall script that I think is included in the nVidia images.
Otherwise, if you want to flash TWRP, you'll need to download the TWRP recovery (you can rename it to "twrp-recovery.zip"). Then you'll need to "fastboot flash twrp-recovery.zip" in order to flash the twrp recovery to your tablet.
Mojar7070 said:
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader
Click to expand...
Click to collapse
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.
Ace0169 said:
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.
Click to expand...
Click to collapse
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5
Mojar7070 said:
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5
Click to expand...
Click to collapse
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?
Ace0169 said:
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?
Click to expand...
Click to collapse
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.
koop1955 said:
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.
Click to expand...
Click to collapse
Select "fastboot protocol"? Is that correct?
Ace0169 said:
Select "fastboot protocol"? Is that correct?
Click to expand...
Click to collapse
So i selected "fastboot protocol" it blipped for a second then brought me back to the bootloader. tried flashing again and once i reached the fastboot flash system system.img it said write failed again. did it not engage the "fastboot protocol"?
Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.
koop1955 said:
Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.
Click to expand...
Click to collapse
@Ace0169 Same, not sure what else to tell you. Sorry sir.
Sent from a Locked Bootloader
Hey guys this is my first thread, I hope it's in the right section
Here's my problem:
Yesterday my Moto G 2013 with CM12.1 just froze (I could turn the screen on and off but that was it)
I tried opening the reboot menu, which worked, but it got stuck on "rebooting", so I just holded the power key until it turned off.
After that I got to the boot logo, but nothing happened from there, not even the boot animation showing up.
Next I tried to boot into TWRP, but it only got to the TWRP boot logo and nothing happened after that, so I flashed CWM, which I could access, but when trying to flash something it just doesn't progress. When I press "reboot to bootloader" on CWM it just freezes there aswell.
In another thread I read that flashing the gpt.bin should fix everything but it didn't help.
I don't really want to perform a factory reset, because of the data loss, but I think this would be my only option.
My question is:
How can I fix my phone (preferably without a factory reset), for example by getting TWRP to work again, because I have a Backup of my system and a zip of CM12.1 on it?
Btw another thing to mention is that when being in Recovery/System USB doesn't really work, but if my phone is turned off or in bootloader it works just fine.
Try "fastboot boot twrp.img" (or whatever the exact name of your TWRP image is). If it gets at least to the curtain screen, run "adb pull /tmp/recovery.log".
_that said:
Try "fastboot boot twrp.img" (or whatever the exact name of your TWRP image is). If it gets at least to the curtain screen, run "adb pull /tmp/recovery.log".
Click to expand...
Click to collapse
When I try "fastboot boot twrp.img" it reboots and get's stuck at the boot logo of android (Motorola logo) and I can hear the "Device disconnected" sound of windows.
But I flashed TWRP into recovery and it get's to the curtain screen. But it doesn't recognize my phone which might have to do with that as soon as it boots into a system USB just won't work
The following command will get TWRP working: fastboot erase userdata
lost101 said:
The following command will get TWRP working: fastboot erase userdata
Click to expand...
Click to collapse
But this will delete everything like my pictures folder, right? Isn't there a way to backup these files ?
@Ju43
adb pull /sdcard/ c:/motog_backup/
lost101 said:
@Ju43
adb pull /sdcard/ c:/motog_backup/
Click to expand...
Click to collapse
But adb only works in recovery mode in android, which I can't access right now without deleting everything, right ? And if I delete userdata, will my TWRP backup be deleted, too ? (It's just a backup of my system)
(sorry for asking so many questions, but I really don't wan't to lose all my photos and stuff)
Ju43 said:
But adb only works in recovery mode in android, which I can't access right now without deleting everything, right ? And if I delete userdata, will my TWRP backup be deleted, too ? (It's just a backup of my system)
(sorry for asking so many questions, but I really don't wan't to lose all my photos and stuff)
Click to expand...
Click to collapse
Yes, you do need at least access to recovery mode for adb to work. Try testing TWRP even if it is only partially loading. Also try CWM.
Everything will get erased on internal storage, photos, TWRP backup etc. Unfortunately, you may be left with no alternative.
lost101 said:
Yes, you do need at least access to recovery mode for adb to work. Try testing TWRP even if it is only partially loading. Also try CWM.
Everything will get erased on internal storage, photos, TWRP backup etc. Unfortunately, you may be left with no alternative.
Click to expand...
Click to collapse
Okay, thanks for your answer, but as I mentioned before, as soon as I boot into something like recovery or android, USB doesn't really work anymore (though it seemed to work again in android). Will erasing user data fix this (as it seems to be a software problem) or even better fixing it before erasing userdata, so I can backup my files? And if I erase user data and TWRP/CWM/whatever works, but USB won't then I can't really put a system on it, can I ?
Ju43 said:
Okay, thanks for your answer, but as I mentioned before, as soon as I boot into something like recovery or android, USB doesn't really work anymore (though it seemed to work again in android). Will erasing user data fix this (as it seems to be a software problem) or even better fixing it before erasing userdata, so I can backup my files? And if I erase user data and TWRP/CWM/whatever works, but USB won't then I can't really put a system on it, can I ?
Click to expand...
Click to collapse
Recovery mode ADB can take some effort to make work depending on the version of Windows. Since you obviously want to backup your files, you can try booting into Linux (a livecd will work) and installing adb. Linux adb works without the need for drivers so it may give you access.
If using Ubuntu, the command to install adb/fastboot is:
sudo apt-get install android-tools-adb android-tools-fastboot
lost101 said:
Recovery mode ADB can take some effort to make work depending on the version of Windows. Since you obviously want to backup your files, you can try booting into Linux (a livecd will work) and installing adb. Linux adb works without the need for drivers so it may give you access.
If using Ubuntu, the command to install adb/fastboot is:
sudo apt-get install android-tools-adb android-tools-fastboot
Click to expand...
Click to collapse
I see what you mean but I got adb to work most times when android was still working (just not in recovery) but I also had problems with charging when the phone was turned on, so I assume it's a problem with android, but I'll search for a Ubuntu Live CD that should be layng around somewhere here (lol) and I'll try it
@lost101
Ok, I installed adb and fastboot, but now it doesn't even find my phone in bootloader...
Ju43 said:
@lost101
Ok, I installed adb and fastboot, but now it doesn't even find my phone in bootloader...
Click to expand...
Click to collapse
Use: sudo fastboot devices
lost101 said:
Use: sudo fastboot devices
Click to expand...
Click to collapse
Thanks, I didn't think abut that :highfive: fastboot works now, but adb doesn't (again when using fastboot boot TWRP.img the terminal shows that it worked but the phone just reboots and is stuck on the Motorola logo and if I flash TWRP it doesn't work either). Maybe I should mention, that I have that screen flickering and like scanline thingy going on when I boot into recovery.
Ju43 said:
Thanks, I didn't think abut that :highfive: fastboot works now, but adb doesn't (again when using fastboot boot TWRP.img the terminal shows that it worked but the phone just reboots and is stuck on the Motorola logo and if I flash TWRP it doesn't work either). Maybe I should mention, that I have that screen flickering and like scanline thingy going on when I boot into recovery.
Click to expand...
Click to collapse
Can you fastboot boot TWRP.img, then adb pull /sdcard/ ?
lost101 said:
Can you fastboot boot TWRP.img, then adb pull /sdcard/ ?
Click to expand...
Click to collapse
Nope, because as I mentioned it doesn't get to the TWRP logo at all
Ju43 said:
Nope, because as I mentioned it doesn't get to the TWRP logo at all
Click to expand...
Click to collapse
Try CWM.
lost101 said:
Try CWM.
Click to expand...
Click to collapse
Same thing except it started vibratng and didn't stop until restarting after a few seconds 0.o
Ju43 said:
Same thing except it started vibratng and didn't stop until restarting after a few seconds 0.o
Click to expand...
Click to collapse
Maybe you can get the phone booting into Android by fastboot flashing the system.sparsechunks from the Factory Firmware Image for your phone.
lost101 said:
Maybe you can get the phone booting into Android by fastboot flashing the system.sparsechunks from the Factory Firmware Image for your phone.
Click to expand...
Click to collapse
Downloading it right now, could you please exactly tell me what to flash with which command ?