Hello all,
I'm new to the whole rooting scene with my Pixel 3 and found myself stuck in fastboot as a result of this Guide: https://forum.xda-developers.com/pixel-3/how-to/guide-patching-boot-img-magisk-canary-t3964359. I realize that's because the firmware was old.
I then followed this video to reset everything: https://www.youtube.com/watch?v=zQmK5KwN5dk.
However, I am still stuck in the loop. I can now at least get to recovery mode but it just brings me right back to fastboot. I could really use some help getting my phone working again
update
averagejoe13579 said:
Hello all,
I'm new to the whole rooting scene with my Pixel 3 and found myself stuck in fastboot as a result of this Guide: https://forum.xda-developers.com/pixel-3/how-to/guide-patching-boot-img-magisk-canary-t3964359. I realize that's because the firmware was old.
I then followed this video to reset everything: https://www.youtube.com/watch?v=zQmK5KwN5dk.
However, I am still stuck in the loop. I can now at least get to recovery mode but it just brings me right back to fastboot. I could really use some help getting my phone working again
Click to expand...
Click to collapse
I was able to get it to move further by putting in the boot.img but now I get stuck on what I belive is the rescue screen. It says at the bottom of my screen "waiting for rescue commands...". I found online that it will now take adb commands but when I reboot or anything of the sort it just takes me back to the beginning
Put it into fastboot mode. Flash the full factory image with the flash-all bat file. But first edit the flash all bat file and remove the -w near the end. That will save your data.
TonikJDK said:
Put it into fastboot mode. Flash the full factory image with the flash-all bat file. But first edit the flash all bat file and remove the -w near the end. That will save your data.
Click to expand...
Click to collapse
When I downloaded the files from the google site all I found was flash-all.sh. Is that the same?
When I do fastboot flash flash-all.sh, I get the error "cannot determine image file name"
averagejoe13579 said:
When I downloaded the files from the google site all I found was flash-all.sh. Is that the same?
When I do fastboot flash flash-all.sh, I get the error "cannot determine image file name"
Click to expand...
Click to collapse
So I re-extracted everything and found it. Kept getting stuck but now the reason it is saying I'm in fastboot is no valid slot to boot. Any advice?
averagejoe13579 said:
So I re-extracted everything and found it. Kept getting stuck but now the reason it is saying I'm in fastboot is no valid slot to boot. Any advice?
Click to expand...
Click to collapse
Make sure you have the latest platform tools.
Related
Hey folks, yesterday i made a serious mistake trying to root my nokia, that resulted in my phone not being able to boot android.
I tried several guides trying to install trwp, but everytime i tried to flash using fastboot like this:
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
It kept complaining that twrp file was to large. So i did some random searches and ended up using the following command from a random noob, which i never shouldn't have done because after it my phone hangs on splash screen
This is the command i did use:
fastboot flash system twrp.img
Click to expand...
Click to collapse
Using this command my phone seemed to flash, but it wont boot anymore.
Does anyone know how to repair my nokia and flash twrp without complaining that twrp.img file is to large? Is there a way to recover my phone from the mistake i have made? Any tips, hints or help is highly appreciated.
Greets,
Autonomus
Autonomus said:
Hey folks, yesterday i made a serious mistake trying to root my nokia, that resulted in my phone not being able to boot android.
I tried several guides trying to install trwp, but everytime i tried to flash using fastboot like this:
It kept complaining that twrp file was to large. So i did some random searches and ended up using the following command from a random noob, which i never shouldn't have done because after it my phone hangs on splash screen
This is the command i did use:
Using this command my phone seemed to flash, but it wont boot anymore.
Does anyone know how to repair my nokia and flash twrp without complaining that twrp.img file is to large? Is there a way to recover my phone from the mistake i have made? Any tips, hints or help is highly appreciated.
Greets,
Autonomus
Click to expand...
Click to collapse
Ouch! I think you flashed your system partition. Can you still enter fastboot mode? If so should be able recover. your phone using OST. Get instructions here:
https://forum.xda-developers.com/nokia-3/development/nokia-3-official-firmware-india-uae-t3674320
i've followed the instruction, ost launched as it should and it did recognise phone. That ost tried to reboot bootloader, and then it stopped working completly. It now only has a black screen and vibrates every now and then.
Also ost doesn't recognise the phone anymore ... :cry
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
Pixel 2 XL is soft bricked at the moment and I can't for the life of me think of what I need to do to recover it. I unlocked my bootloader and rooted when I switched to Pie, (I saw people we're already able to use Android pay on a rooted device again and I just couldn't help myself.) I installed twrp accidentally tried to flash TWRP not realizing I needed to temporary boot it and pushing the zip over erasing the recovery I proceeded to just fastboot it and carry on with the normal procedure with my phone. after getting Magisk installed I had my phone all set up until the next time I turned it on and back off again It said I forgot my PIN which I know I didn't I think this was because a glitch with smartlock I just setup so I go to my recovery and wipe the Dalvik cache, cache, Internal storage, and data and low and behold my phone bootloops never making past the final stage before it gets to the lockscreen. I go to Fastboot screen on my phone and my mac can't list my phone as a device in adb and now I am having issues getting back into recovery which I think might be because I am on the stock kernel my Fastboot screen on my phone says Product Name - Taimen, Variant - MSM USF:SAMSUNG(64gig) DDR:SAMSUNG, Bootloader version - TM220j, Baseband version - g899800253-1805232234, my Serial number, Serure boot - Yes, Device status - Unlocked, Vart console - Disabled, HW version - rev_10
I can't get it to stop bootlooping and just turn off.
bump
xda Zed said:
bump
Click to expand...
Click to collapse
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.
robocuff said:
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.
Click to expand...
Click to collapse
I stopped my endless bootloop! Now it says my device is corrupt and cannot be trusted and may not work properly when I tried to start it I couldn't get past the google screen. When I plug it into charge now it doesn't automatically going into a bootloop that can only be stoped by going into the fastboot mode or running out of battery, but the the charging symbol on the screen won't go away. I might have wiped system when I was in TWRP when I couldn't boot back after the first wipe. And I accidentally tried fastbooting Telstra img first. Anyway to get past this white Google screen? Also when I trey to go to recovery now it's the android laying on it's back with a red triangle and it says no command. Should I execute the flash-all script?
Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now
xda Zed said:
Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now
Click to expand...
Click to collapse
Glad to hear you got it working again. As for the recovery screen that say no command, that't the way it works with the stock recovery. When you see that screen, press and hold power and volume up. That will get you into recovery. If you happen to try rooting again and get stuck in a bootloop or some such thing, just flash the stock boot image.. That should get you going again.
Hi,
My Pixel 3 was rooted with Magisk. After uninstalling it, I lost root, tried to re-root with Magisk and ended up stuck in fastboot mode with "error boot prepare" and now can't exit or power down.
I assume I won't be able to save my data, is there any way to reset/flash stock image?
adb fastboot devices show my Pixel 3
adb fastboot reboot works but goes right back to fastboot mode.
If I'm posting in the wrong forum, can you please direct me to the appropriate one.
Thanks
Martha.
krakheadmartha said:
Hi,
My Pixel 3 was rooted with Magisk. After uninstalling it, I lost root, tried to re-root with Magisk and ended up stuck in fastboot mode with "error boot prepare" and now can't exit or power down.
I assume I won't be able to save my data, is there any way to reset/flash stock image?
adb fastboot devices show my Pixel 3
adb fastboot reboot works but goes right back to fastboot mode.
If I'm posting in the wrong forum, can you please direct me to the appropriate one.
Thanks
Martha.
Click to expand...
Click to collapse
I assume your bootloader is unlocked? Have you tried flashing the factory image with fastboot? I'd first try using the flash-all batch file with the -w removed. That way you might be able to save data.
jd1639 said:
I assume your bootloader is unlocked? Have you tried flashing the factory image with fastboot? I'd first try using the flash-all batch file with the -w removed. That way you might be able to save data.
Click to expand...
Click to collapse
Thanks for your reply.
After countless tries to flash-all with fastboot as well as flashing different options nothing worked...
I originally rooted my phone from a Mac with no issues. I could still run fastboot reboot and other commands but it would revert back to the fastboot mode.
I finally loaded up Parallels and tried fastboot flash-all from Windows and managed to reset on the first try.
Not sure why it didn't work with my Mac... but I'll always use Windows from now on.
***SOLVED!***
krakheadmartha said:
Thanks for your reply.
After countless tries to flash-all with fastboot as well as flashing different options nothing worked...
I originally rooted my phone from a Mac with no issues. I could still run fastboot reboot and other commands but it would revert back to the fastboot mode.
I finally loaded up Parallels and tried fastboot flash-all from Windows and managed to reset on the first try.
Not sure why it didn't work with my Mac... but I'll always use Windows from now on.
***SOLVED!***
Click to expand...
Click to collapse
I'm not very familiar with mac's. You need to use the .sh file, which I'm pretty sure you know. But you also need to edit the batch file. Command lines that start with / need to be changed to ./ Or something like that. I don't remember exactly.
Hi! My old phone is booting into fastboot mode, when I try to boot normally I get a black screen, the "Power off" button appears when I hold the power button. The bootloader is not unlocked and the phone was never rooted. Wiping the user partition does not help. It is visible in fastboot mode and I can enter stock recovery, though trying to adb sideload a stock rom returns an error (footer is wrong; signature verification failed). Trying to fastboot boot twrp or recovery.img doesn't work either. I've ran out of ideas, what should I do to get this phone to work?
Try flashing the stock ROM with fastboot. I'm pretty sure ADB doesn't let you flash onto your phone because using your phone with ADB means that it's still powered on - which can cause some issues. You can also try and unlock your bootloader through fastboot, and then flash a recovery and custom ROM.
Both failed. I attached the errors I recieved.
crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try "fastboot bootloader unlock", maybe. Also: Is there a flashall.bat in the stock ROM folder? If there is: Connect your device while in fastboot, and double-click it.
crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try this maybe. I know you can't wipe through the stock ROM, so, try the command: "fastboot -w". That'll wipe everything off the device.
[INDEX][Osprey][Merlin] Moto G Factory Firmware Images
Disclaimer: I am not responsible for anything that happens as a result of flashing these files. Your destiny is your own. Moto G (3rd Gen) Factory Firmware Images - Provided by Firmware TEAM - Please report broken links. New Mirrors welcome...
forum.xda-developers.com
I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.
crepper4454 said:
I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.
Click to expand...
Click to collapse
Try this: https://forum.xda-developers.com/t/guide-osprey-fastboot-flashing-factory-firmware-images.3187750/
It says there that the "preflash validation failed" error occurs when the firmware being flashed is older than the one already installed. I will try downloading a newer version and flashing it. Will update here.
Update: I have dowloaded a newer rom and tried to flash it. This time got different errors (picture attached, this went for every sparsechunk). I think I know the reason but I do not know how to solve it. This might not be the exact stock rom of this phone so I cannot flash it with a locked bootloader. Could someone help me finding the correct rom or suggest a different solution?
Yooooo. I have the Moto e5 Cruise and so does my wife. We bought them in 2018 from Cricket and last night hers went to emmc failure, also known scientifically as 'no worky' mode.
The phone would only load in fastboot and had tried to use my Moto RSD tool to reflash but the phone would not detect in anything but fastboot mode.. Here's where it gets interesting....
There is a piece of software called the Lenovo (which now owns Moto) Rescue and Smart Assistant that can reflash your phone back to factory, no matter your sub-variant (cricket, metro, etc). Without having a fresh backup on hand, you're going to be beholden to the last cloud sync or manual backup you have because all data will be wiped in the below process.
BTW: Just run the assistant as it seems to be the easiest 'back-to-stock/working' tool I can find. Going to fastboot alone yielded weird errors since i didn't have the unlock code for the 'fastboot oem unlock [code goes here]' command.
**RESTORATION PROCESS**
This will apply to multiple Lenovo/Moto Mobility devices. Unknown at this time how many have been impacted by this seemingly pre-planned failure on Lenovo's part.
If your phone is stuck in fastboot mode where MTK download mode does not load, nor does adb, follow these simple steps:
(NOTE: BACKUP YOUR FILES IF POSSIBLE)
1. Click the link above to be directed to the Lenovo software download page and run the installer on your PC (Sorry Mac users :'().
2. The software, once installed, will require you to sign up for OR link a google, fb, g+, etc account to it for purposes of creating a Lenovo ID. Once signed in, click on 'Rescue Now'.
3. With your phone in fastboot mode, allow the software to download the firmware for your phone.
4. Once the firmware has finished downloading and validating, click on 'Rescue Now' once again. Your phone will begin the reflashing process.
That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .
crepper4454 said:
That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .
Click to expand...
Click to collapse
No problemo! Glad it worked!