Related
So I messed. Accidentally formatted my phone and now it's screwed. Tried to use fastboot to put boot.img on, but my computer won't recognize my phone when I do "fastboot devices" or any commands. It won't boot or anything. I dunno what to do, kinda need a phone. Any help would be greatly appreciated and rewarded duly.
Cynicsatire said:
So I messed. Accidentally formatted my phone and now it's screwed. Tried to use fastboot to put boot.img on, but my computer won't recognize my phone when I do "fastboot devices" or any commands. It won't boot or anything. I dunno what to do, kinda need a phone. Any help would be greatly appreciated and rewarded duly.
Click to expand...
Click to collapse
so no signs of life at all? can you get to the bootloader? how exactly did you format your phone?
the XDA brains trust is going to need a bit more info.
codeprimate said:
so no signs of life at all? can you get to the bootloader? how exactly did you format your phone?
the XDA brains trust is going to need a bit more info.
Click to expand...
Click to collapse
Sorry, there are signs of life. I can get to the bootloader and recovery. And I honestly clicked the wrong button, that's what happens when you don't sleep and decide to try to flash a new rom.
Are you sure you didn't flash a new Rom
Cynicsatire said:
Sorry, there are signs of life. I can get to the bootloader and recovery. And I honestly clicked the wrong button, that's what happens when you don't sleep and decide to try to flash a new rom.
Click to expand...
Click to collapse
If you can get to bootloader and recovery, you're not bricked. You just need to flash a new rom, this time remembering to flash the boot.img in fastboot like the instructions say.
Oops I thought he Saud there are no signs of life..Elvis spots all
iElvis said:
If you can get to bootloader and recovery, you're not bricked. You just need to flash a new rom, this time remembering to flash the boot.img in fastboot like the instructions say.
Click to expand...
Click to collapse
the problem is my computer isn't registering the device when i do fastboot.
Cynicsatire said:
the problem is my computer isn't registering the device when i do fastboot.
Click to expand...
Click to collapse
If 'fastboot devices' returns nothing, then you are most likely missing drivers. Easiest way to get drivers is install HTC Sync Manager. It will install the app and the drivers, you can safely uninstall the app later and still have the drivers stay installed
Sent from my One X
reboot to fastboot, but do not select bootloader (it should say "Fastboot" in red writing just underneath the green text and above the orange text.
connect it via usb to your pc, and it should say "fastboot usb", then you should be able to use fastboot commands. if it doen't allow you to use fastboot commands, try a different usb port, or reinstalling the drivers.
codeprimate said:
reboot to fastboot, but do not select bootloader (it should say "Fastboot" in red writing just underneath the green text and above the orange text.
connect it via usb to your pc, and it should say "fastboot usb", then you should be able to use fastboot commands. if it doen't allow you to use fastboot commands, try a different usb port, or reinstalling the drivers.
Click to expand...
Click to collapse
Did this, now it's stuck at the htc screen. Any suggestions?
Cynicsatire said:
Did this, now it's stuck at the htc screen. Any suggestions?
Click to expand...
Click to collapse
Hmmm, when it rebooted it stopped at the htc screen? This sounds like it's not going to the fastboot mode. Reboot with the volume held down. That should get to the fastboot mode.
codeprimate said:
Hmmm, when it rebooted it stopped at the htc screen? This sounds like it's not going to the fastboot mode. Reboot with the volume held down. That should get to the fastboot mode.
Click to expand...
Click to collapse
After I push the boot.img through fastboot, when I reboot it just sticks on the HTC boot screen. I can get to the fastboot screen but I already have the boot.img on there. What next? should it work?
Cynicsatire said:
After I push the boot.img through fastboot, when I reboot it just sticks on the HTC boot screen. I can get to the fastboot screen but I already have the boot.img on there. What next? should it work?
Click to expand...
Click to collapse
go to your recovery and flash the ROM (the boot.img is just the kernel) if you haven't done that.
codeprimate said:
go to your recovery and flash the ROM (the boot.img is just the kernel) if you haven't done that.
Click to expand...
Click to collapse
Oh. That makes sense. It works now. Thanks a million. I owe you one.
A few days ago I tried getting my phone to s-off using the "[how to] manually achieve s-off,simunlock,supercid for Inspire 4g/DHD" guide on the Android forums. (Sorry, I can't post direct links.)
I got to the part where I was supposed to type in "fastboot flash boot boot.img" to the command line but I accidentally skipped that part and typed in "fastboot boot recovery recovery.img". I stopped everything and tried to start over but when I turned my phone back on I was stuck in a boot loop. Going to hboot and trying to choose Recovery or Factory Reset only results in more boot looping.
I've tried putting PD98IMG.zip on the SD card and booting it, but it only reads it and says "Parsing..." before doing nothing. Attempting to enter recovery mode after this makes it enter the boot loop again.
I've also tried using the HTC Sense and RUU from AT&T on my computer to fix the issue. My phone can connect to my PC after choosing fastboot from the hboot menu. The RUU can see the device and it starts recovering it, as my phone shows a black background with HTC on it. But the RUU stops after trying to update the signature saying "The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again." I am 99% positive I am using the correct RUU.
I've searched high and low on the internet for a similar situation, but everyone else seems to have their problems solved using either of these steps. Thanks for any help.
Without knowing what you did (since you haven't given us a step-by-step and can't post links), we don't know how to help.
Sorry about that. I'll try to explain what I did the best I can.
Before using the guide, I managed to root my phone and used it for a few days, so everything was fine then. I later decided to s-off it so I could flash a custom ROM to it. Using the guide I mentioned above, I created a mini-adb directory in my C: drive with the ace-tools.zip that I downloaded. Using the command line I copied my stock boot image, though to where I do not know. (I feel like a fool for doing all this without being sure of what I was doing exactly. I deserve what came to me.) Then, using the command line I made my SD card a gold card. After that I changed the "misc version" (?) to allow installation of the downgrade firmware, and then relocked the boot loader and booted back into fastboot. Then I flashed the downgrade software and unlocked it again. It's here that my phone was supposed to be unable to boot, and I was supposed to flash the boot image but skipped that step.
Now I'm unsure of what I have to do, and I only want to get my device working again.
I wish I could post the link to the exact topic, but since I can't I guess you'd have to search the topic name to see exactly what the directions were trying to get me to do.
Thanks again.
Can you boot the phone into fastboot and flash the boot.img from fastboot?
No, with the PD98IMG.zip file it simply says "Parsing..." and stops there. With any other boot image it doesn't acknowledge it at all. Even though the computer makes the sound that it's connected to the device when it's in fastboot, adb can't recognize that's it's there in the command line.
SammichMonster said:
No, with the PD98IMG.zip file it simply says "Parsing..." and stops there. With any other boot image it doesn't acknowledge it at all. Even though the computer makes the sound that it's connected to the device when it's in fastboot, adb can't recognize that's it's there in the command line.
Click to expand...
Click to collapse
Wait. What? Not PD98IMG.zip from hboot. Extract the boot.img and flash from fastboot, not adb.
Ah, thanks for the clarification. I'm supposed to extract the boot.img to the SD card and enter fastboot on my phone, correct? Because I've just done so and nothing happened. I have the options Bootloader, Reboot, Reboot Bootloader, and Power Down, and the Bootloader option only takes me back to the hboot screen.
Sorry if I've misunderstood you.
SammichMonster said:
Ah, thanks for the clarification. I'm supposed to extract the boot.img to the SD card and enter fastboot on my phone, correct? Because I've just done so and nothing happened. I have the options Bootloader, Reboot, Reboot Bootloader, and Power Down, and the Bootloader option only takes me back to the hboot screen.
Sorry if I've misunderstood you.
Click to expand...
Click to collapse
No, the boot.img needs to be on your computer. Your phone needs to be in fastboot mode. From the folder where the boot.img is saved,
Code:
fastboot flash boot boot.img
I can't use the command prompt to connect with the device because it can't see it. I always get an "error: device not found" instead.
Is your phone in fastboot mode?
Yes. It's odd: the RUU software identifies it and knows it's there, but can't actually fix the issue. The command prompt just doesn't notice it at all.
SammichMonster said:
Yes. It's odd: the RUU software identifies it and knows it's there, but can't actually fix the issue. The command prompt just doesn't notice it at all.
Click to expand...
Click to collapse
So you're booting into hboot, navigating to fastboot with the volume buttons, and selecting it with the power button? What does fastboot devices say?
I'm assuming by "fastboot devices" you mean what it says in the command prompt.
...Well what do you know, it recognized it. I was typing in "adb devices" instead of "fastboot devices". So it can recognize it after all.
I'm assuming I have to load the boot.img now?
Hey hey, wa-hey!
That was much easier than I thought it would be! A simple "fastboot flash boot boot.img" followed by a fastboot flash recovery recovery.img" using some image files I made before messing everything up did the trick. Thank god I did so.
Everything's back to normal; my phone escaped the boot loop. And last but not least, I don't have to buy a new phone.
Thanks so much for helping me out, even if it was clearing a few things up for me. I appreciate it.
SammichMonster said:
...Well what do you know, it recognized it. I was typing in "adb devices" instead of "fastboot devices". So it can recognize it after all.
Click to expand...
Click to collapse
That's what i figured you were doing, so that's why I clarified.
SammichMonster said:
Hey hey, wa-hey!
That was much easier than I thought it would be! A simple "fastboot flash boot boot.img" followed by a fastboot flash recovery recovery.img" using some image files I made before messing everything up did the trick. Thank god I did so.
Everything's back to normal; my phone escaped the boot loop. And last but not least, I don't have to buy a new phone.
Thanks so much for helping me out, even if it was clearing a few things up for me. I appreciate it.
Click to expand...
Click to collapse
You're welcome. You could also have fastboot flashed any custom recovery image, flashed a ROM from recovery, and fastboot flashed that ROM's boot.img. So you weren't too badly off.
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
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 ?
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