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 ?
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!
Well, I was using an app called screen dimmer, and did pressed the button to dim the screen when all of a sudden it froze. It was like this for a while so I restarted it, it is able to go in fastboot, but nothing else. When i start It it hangs on the boot loader screen and can stay like that all day. if I go into recovery the screen goes black and the display is only backlit. I was going to try to to use the adb to factory reset it, but I could not get it to recognize the nexus 5 as a device. I used a bunch of different drivers. I did root my phone, and have the exposed framework but this was done a long time ago and I had no problems since. no idea how to fix this any help?!?!? Sorry if this is the wrong place to put this I'm new to this site.
2point said:
Well, I was using an app called screen dimmer, and did pressed the button to dim the screen when all of a sudden it froze. It was like this for a while so I restarted it, it is able to go in fastboot, but nothing else. When i start It it hangs on the boot loader screen and can stay like that all day. if I go into recovery the screen goes black and the display is only backlit. I was going to try to to use the adb to factory reset it, but I could not get it to recognize the nexus 5 as a device. I used a bunch of different drivers. I did root my phone, and have the exposed framework but this was done a long time ago and I had no problems since. no idea how to fix this any help?!?!? Sorry if this is the wrong place to put this I'm new to this site.
Click to expand...
Click to collapse
You need to find a driver that works so it'll recognize the device. Once you do this, you need to flash boot.img to restore the recovery since not working. Then, redo the ROM or restore from backup if you can. Flashing a new recovery boot.img should fix the issue.
2point said:
Well, I was using an app called screen dimmer, and did pressed the button to dim the screen when all of a sudden it froze. It was like this for a while so I restarted it, it is able to go in fastboot, but nothing else. When i start It it hangs on the boot loader screen and can stay like that all day. if I go into recovery the screen goes black and the display is only backlit. I was going to try to to use the adb to factory reset it, but I could not get it to recognize the nexus 5 as a device. I used a bunch of different drivers. I did root my phone, and have the exposed framework but this was done a long time ago and I had no problems since. no idea how to fix this any help?!?!? Sorry if this is the wrong place to put this I'm new to this site.
Click to expand...
Click to collapse
Hi, In first place, You are in the right place to get help:good:
2. ADB won't work on fastboot nor in a damaged recovery.
3. fastboot works:victory: Try to flash recovery once again (fastboot flash recovery recoveryname.img)
4. if 3 works, wipe system, caches. Flash the Rom you want, don't use that app anymore.
GUGUITOMTG4 said:
Hi, In first place, You are in the right place to get help:good:
2. ADB won't work on fastboot nor in a damaged recovery.
3. fastboot works:victory: Try to flash recovery once again (fastboot flash recovery recoveryname.img)
4. if 3 works, wipe system, caches. Flash the Rom you want, don't use that app anymore.
Click to expand...
Click to collapse
Thanks! got to recognize any way to do this without loosing data?
2point said:
Thanks! got to recognize any way to do this without loosing data?
Click to expand...
Click to collapse
There is a chance to keep your data + storage contents. If you manage to flash and boot into recovery, in 'wipe' menu manually check-mark "cache,system"
don't mark internal "storate and data", nothing will happen to your media and apps data.
2point said:
Thanks! got to recognize any way to do this without loosing data?
Click to expand...
Click to collapse
May be able to dirty flash but most likely, since you had the screen dimmed too much, you'll have to wipe data in order to override/remove the problem. You can try this way but may just send you back through this whole process if problem reoccurs. I'd just wipe the data to be safe.
2point said:
Well, I was using an app called screen dimmer, and did pressed the button to dim the screen when all of a sudden it froze. It was like this for a while so I restarted it, it is able to go in fastboot, but nothing else. When i start It it hangs on the boot loader screen and can stay like that all day. if I go into recovery the screen goes black and the display is only backlit. I was going to try to to use the adb to factory reset it, but I could not get it to recognize the nexus 5 as a device. I used a bunch of different drivers. I did root my phone, and have the exposed framework but this was done a long time ago and I had no problems since. no idea how to fix this any help?!?!? Sorry if this is the wrong place to put this I'm new to this site.
Click to expand...
Click to collapse
Oy vey! You shouldn't have been tinkering as you clearly don't know what you're doing.
[TUTORIAL] How to flash a factory image | Return to stock | Unroot your Nexus 5
2point said:
Thanks! got to recognize any way to do this without loosing data?
Click to expand...
Click to collapse
No, and if you had done your homework you would know that. If the data is so important, back it up before modding.
GUGUITOMTG4 said:
There is a chance to keep your data + storage contents. If you manage to flash and boot into recovery, in 'wipe' menu manually check-mark "cache,system"
don't mark internal "storate and data", nothing will happen to your media and apps data.
Click to expand...
Click to collapse
When I do fastboot boot recovery.img I get the android bot with a red exclamation but nothing else I might just do flashall
2point said:
When I do fastboot boot recovery.img I get the android bot with a red exclamation but nothing else I might just do flashall
Click to expand...
Click to collapse
Reflash the recovery.img
2point said:
When I do fastboot boot recovery.img I get the android bot with a red exclamation but nothing else I might just do flashall
Click to expand...
Click to collapse
The general idea is that your recovery is broken.
So, you need to flash a new recovery by placing a recovery.img file into your fastboot folder in the computer(recommend twrp). Like you did the first time you fladhed a recovery.
Then, turn off the phone, press volume down+ power button and it will boot into bootloader. Make sure it is on fastboot mode. After that, on the computer open cmd on the fastboot folder and and type:
fastboot flash recovery nameofrecoveryfile.img,
press enter.
It should flash a new recovery image if done correctly. Then, poweroff the phone, boot again into bootloader, choose recovery and it will reboot into recovery. Then follow. The steps of my first post.
jd1639 said:
Reflash the recovery.img
Click to expand...
Click to collapse
GUGUITOMTG4 said:
The general idea is that your recovery is broken.
So, you need to flash a new recovery by placing a recovery.img file into your fastboot folder in the computer(recommend twrp). Like you did the first time you fladhed a recovery.
Then, turn off the phone, press volume down+ power button and it will boot into bootloader. Make sure it is on fastboot mode. After that, on the computer open cmd on the fastboot folder and and type:
fastboot flash recovery nameofrecoveryfile.img,
press enter.
It should flash a new recovery image if done correctly. Then, poweroff the phone, boot again into bootloader, choose recovery and it will reboot into recovery. Then follow. The steps of my first post.
Click to expand...
Click to collapse
Did that and get a
C:\Users\nkkou_000\programs\adt-bundle-windows-x86_64-20131030\sdk\platform-tool
s>fastboot flash recovery openrecovery-twrp-2.6.3.4-hammerhead.img
sending 'recovery' (13272 KB)...
OKAY [ 0.620s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 44.593s
C:\Users\nkkou_000\programs\adt-bundle-windows-x86_64-20131030\sdk\platform-tool
s>
But I can do fastboot boot openrecovery-twrp-2.6.3.4-hammerhead.img and will will boot into the recovery just fine
And that twrp says that i have no os installed
2point said:
But I can do fastboot boot openrecovery-twrp-2.6.3.4-hammerhead.img and will will boot into the recovery just fine
And that twrp says that i have no os installed
Click to expand...
Click to collapse
You have a couple of options depending on how much data you can afford to lose on your phone. The least intrusive is to adb push a Rom on to your phone when you're in twrp Then flash that rom in twrp
The easier, but you'll lose all data on your phone is to flash the flash-all.bat file in fastboot
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
2point said:
But I can do fastboot boot openrecovery-twrp-2.6.3.4-hammerhead.img and will will boot into the recovery just fine
And that twrp says that i have no os installed
Click to expand...
Click to collapse
Then, it seems recovery now is good. If you have rom zip in the storage. Just wipe system and cache, flash the rom and see what happens
When in the twrp I can't get fastboot to recognize it as a device, or adb either
2point said:
When in the twrp I can't get fastboot to recognize it as a device, or adb either
Click to expand...
Click to collapse
Your adb drivers aren't setup correctly. They're different than the fastboot ones. Try Google tool adb fastboot drivers xda.
jd1639 said:
Your adb drivers aren't setup correctly. They're different than the fastboot ones. Try Google tool adb fastboot drivers xda.
Click to expand...
Click to collapse
When you are on twrp. You dont need to use fastboot nor adb. Just flash a rom if have one to flash
GUGUITOMTG4 said:
When you are on twrp. You dont need to use fastboot nor adb. Just flash a rom if have one to flash
Click to expand...
Click to collapse
How do i do that?
2point said:
How do i do that?
Click to expand...
Click to collapse
Have you flashed roms before? And do you have one on your internal sdcard? If so flash it in twrp
jd1639 said:
Have you flashed roms before? And do you have one on your internal sdcard? If so flash it in twrp
Click to expand...
Click to collapse
I have the factory image from google for my nexus 5
Hi guys,
I have a rooted Device with CM and TWRP installed, but someting happenend using the device and my Moto G got stuck on startup logo and Recovery TWRP logo, with adb I have acess to adb shell but everything else like adb reboot bootloader etc doesn't seems to work, with adb shell I have realized that the TWRP wasn't running 'cause when I use the interface on shell I get this message
$twrp wipe cache
"TWRP does not appear to be running. Waiting for TWRP to start"
Is there any way to install a new recovery via adb shell or reinstall a new rom, factory reset or something like that to make my cellphone work again?
Thanks,
If you are okay to wipe internal storage, the following fastboot command will probably make TWRP load again:
fastboot erase userdata
fastboot flash recovery newrecovery.img - is a way to reflash recovery, however the above command may still be required.
The problem is that with fastboot the device is not recognized, only when I open the recovery mode...
The logo freezes but the device is reconigzed with adb devices...
gconsentini said:
The problem is that with fastboot the device is not recognized, only when I open the recovery mode...
The logo freezes but the device is reconigzed with adb devices...
Click to expand...
Click to collapse
What OS are you using? Maybe try the ADB commands:
adb shell
wipe data
lost101 said:
What OS are you using? Maybe try the ADB commands:
adb shell
wipe data
Click to expand...
Click to collapse
It's the latest CM
I'll try, but the last time I got this message.
"TWRP does not appear to be running. Waiting for TWRP to start . . .
Press CTRL + C to quit."
EDIT
using
adb shell
twrp wipe data
happened the same above
gconsentini said:
It's the latest CM
I'll try, but the last time I got this message.
"TWRP does not appear to be running. Waiting for TWRP to start . . .
Press CTRL + C to quit."
EDIT
using
adb shell
twrp wipe data
happened the same above
Click to expand...
Click to collapse
I meant what OS on PC are you using. Stop adding the phrase 'twrp' - type the command as I wrote it.
lost101 said:
I meant what OS on PC are you using. Stop adding the phrase 'twrp' - type the command as I wrote it.
Click to expand...
Click to collapse
Sorry, I'm using Windows 10, if I use only wipe data, the command wipe is not reconigzed.
Can you enter fastboot mode by holding vol down and powering phone on?
lost101 said:
Can you enter fastboot mode by holding vol down and powering phone on?
Click to expand...
Click to collapse
yes, but when I connect the phone usb and use fastboot devices
it has no devices on the list
gconsentini said:
yes, but when I connect the phone usb and use fastboot devices
it has no devices on the list
Click to expand...
Click to collapse
There are many threads on Win10 and usb driver issues. If you don't want to try to fix fastboot on Windows, you could boot into a Ubuntu Linux LiveCD and install fastboot there.
lost101 said:
There are many threads on Win10 and usb driver issues. If you don't want to try to fix fastboot on Windows, you could boot into a Ubuntu Linux LiveCD and install fastboot there.
Click to expand...
Click to collapse
Yes, I thought about that too =x
SOLVED
Guys the problem was that I've not installed the drivers before, after doing this, I just installed the stock rom from motorola.
Thanks
gconsentini said:
SOLVED
Guys the problem was that I've not installed the drivers before, after doing this, I just installed the stock rom from motorola.
Thanks
Click to expand...
Click to collapse
Hey i'm having the same issue, would you mind telling me how you re-flashed the Motorola rom, Thanks
thomasswan5547 said:
Hey i'm having the same issue, would you mind telling me how you re-flashed the Motorola rom, Thanks
Click to expand...
Click to collapse
Install the Minimal Fastboot & ADB package and the Motorola USB drivers, use the mfastboot package and install the stock ROM as per the instructions provided, but ignore the disassembly part, unless you have your phone does not respond to keypresses.
https://forum.xda-developers.com/showpost.php?p=71328823&postcount=915
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