Install TWRP using Linux shell adb - Samsung Galaxy J5 Questions & Answers

Hi, I'm trying to get TWRP on my J530F (to install LineageOS and Gapps). Adb reboot bootloader results in rebooting Android. I've managed to get into recovery or download mode by holding buttons, but it's useless. Found something with heimdal, but dnf manager refuses to install it to my computer. How can I setup the TWRP? I use Fedora 64b.
Any advice appreciated.

sjiamnocna said:
Hi, I'm trying to get TWRP on my J530F (to install LineageOS and Gapps). Adb reboot bootloader results in rebooting Android. I've managed to get into recovery or download mode by holding buttons, but it's useless. Found something with heimdal, but dnf manager refuses to install it to my computer. How can I setup the TWRP? I use Fedora 64b.
Any advice appreciated.
Click to expand...
Click to collapse
I have tried a similar thing with adb and fastboot using Debian, I was trying to oem unlock.
adb reboot bootloader on my J530G results in rebooting to Download Mode but fastboot never recognizes the device. I don't know if fastboot is compatible with galaxy phones.

scroll-lock said:
I have tried a similar thing with adb and fastboot using Debian, I was trying to oem unlock.
adb reboot bootloader on my J530G results in rebooting to Download Mode but fastboot never recognizes the device. I don't know if fastboot is compatible with galaxy phones.
Click to expand...
Click to collapse
I guess, switching the OEM unlock option in developers section may do the bootloader unlock. Had some luck with adb reboot download, which resulted in rebooting to download mode saying sth like "ODIN mode". I did some research, found more info about ODIN, heimdal etc., but after some time I gave up, cos dnf package manager keep refusing to install Heimdal, saying
Code:
Problem: conflicting requests - nothing provides libusb1.0 >= 1.0.8
(already installed libusb-1, libusb-devel-1)
Anyone have advice? Thanks

Follow the instruction here to install twrp https://forum.xda-developers.com/ga...msung-j5-pro-twrp-3-1-10-v2-0-t3728233/page10
Then from twrp flash magisk from here https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/page5
That's how to properly root without bricking your device or losing your imei

Related

Unable to install TWRP

Hey guys, I'm at a lost here. I don't think I'm that stupid but I am following all steps from the guides to install TWRP without luck. I already managed to unlock my bootloader with Axon7Toolkit. I already certified that QUSB_Bulk driver is installed, I did it with Zadig, but when in EDL mode, even after killing adb, the axon7tool can't find it. I tried installing a zip with the toolkit but when I choose the package, the toolkit simply closes. Is that me? My phone?
Thank you!
gibawatts said:
Hey guys, I'm at a lost here. I don't think I'm that stupid but I am following all steps from the guides to install TWRP without luck. I already managed to unlock my bootloader with Axon7Toolkit. I already certified that QUSB_Bulk driver is installed, I did it with Zadig, but when in EDL mode, even after killing adb, the axon7tool can't find it. I tried installing a zip with the toolkit but when I choose the package, the toolkit simply closes. Is that me? My phone?
Thank you!
Click to expand...
Click to collapse
What software version are you on?
I was at latest nougat but I downgraded to B10
Doing it via fastboot never fails for me.
Get to fastboot put two img in adb folder (I rename it for ease of typing since I suck) rename to recovery.img
Type this cmd in adb
Fastboot flash recovery recovery.img
Reboot to recovery and root. Done deal
download 3.1.0.0 twrp into your download folder on your desktop enter fastboot into your phone open up your command prmt type fastboot devices, your phone should appear then type fastboot flash recovery then go to the twrp right click drag it into the command prmt air page and place it there. you should see the file then hit enter. It'll take like 5 seconds it's really fast then reboot t recovery. when in twrp it'll ask you to install it again say no and uncheck the to options. DONE.
After loads of stress and bangs on the table I managed to unlock, install TWRP, LOS and root. I removed every driver related to my cell phone, deleted everything I download from it and started from scratch. I installed TWRP via fastboot but wasn't able to enter recovery mode, than I mase the stupidity to lock the bootloader back and got stuck in that password screen. Then I gave another go with the toolkit, unlocked it again and, I don't know how or why, it finally booted TWRP. Now everything is OK. Glad to be back to "Nexus mode" after so many time.
Thank you!

Help please can't see my phone in adb

I've had my Essential two weeks i was on 8.1 beta.Today i unlocked the boot loader.Then installed twrp while in twrp i side loaded magisk.I went back to fastboot then hit start .The phone just went into a bootloop.I Was able to go back to twrp 2 times but now i can't get back to any type of recovery.I Can get back to fastboot mode ishow all the info and secure boot says yes and device state unlocked.My pc see essential phone fastboot in the device manager but i can't get adb to see it .Can anyone help me ?
forgot something
looks like i skipped this part . Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.Is there anything i can do?
videodave1 said:
I've had my Essential two weeks i was on 8.1 beta.Today i unlocked the boot loader.Then installed twrp while in twrp i side loaded magisk.I went back to fastboot then hit start .The phone just went into a bootloop.I Was able to go back to twrp 2 times but now i can't get back to any type of recovery.I Can get back to fastboot mode ishow all the info and secure boot says yes and device state unlocked.My pc see essential phone fastboot in the device manager but i can't get adb to see it .Can anyone help me ?
Click to expand...
Click to collapse
adb only works while phone is booted into system so nothing wrong there. If you're in the bootloader menu where you see that the status of your device is unlocked then you're already in fastboot mode. Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too. Go into install and press flash image file and find the stock boot image and then go into install again and change to flash .zip and flash magisk. After that, reboot into system.
WOW thank you so much'
Arju said:
adb only works while phone is booted into system so nothing wrong there. If you're in the bootloader menu where you see that the status of your device is unlocked then you're already in fastboot mode. Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too. Go into install and press flash image file and find the stock boot image and then go into install again and change to flash .zip and flash magisk. After that, reboot into system.
Click to expand...
Click to collapse
I was able to flash twrp i'll try the rest when i get home from work
sideloading stock img
videodave1 said:
I was able to flash twrp i'll try the rest when i get home from work
Click to expand...
Click to collapse
Do i need it to be zipped I've tried it as image that i downloaded from xda and I've tried a zip i got from Essential neither are working?
zip file
videodave1 said:
Do i need it to be zipped I've tried it as image that i downloaded from xda and I've tried a zip i got from Essential neither are working?
Click to expand...
Click to collapse
When i try i get invalid file format. This is using a zip i got from Essential.
Stuck twrp says no os installed . But i did learn how to push files.
just trying to get back to stock now 
videodave1 said:
just trying to get back to stock now 
Click to expand...
Click to collapse
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
thanks been there tried the Oreo beta that is what i was on when i started and tried the 1st build before the betas i get an error on both i'll try to download them on another pc my phone does show up when i type fastboot devices now just need an os now .
Okay got back to 8.1 bootloader still unlocked twrp not install and i don't have root.I may just wait until P comes out.I'll try and learn more about adb. Thanks for your help Arju.
thanks everyone.
videodave1 said:
Okay got back to 8.1 bootloader still unlocked twrp not install and i don't have root.I may just wait until P comes out.I'll try and learn more about adb. Thanks for your help Arju.
Click to expand...
Click to collapse
No problem. Thank you very much for the donation, that was really kind of you. Hey I'm sure you'll get the hang of it before android P drops. you did figure out what went wrong all by yourself so get a hold of the right boot.img and the rest is exactly as how you did it in the first place but flash the boot.img before magisk. Let me know if you want to give it a dive again.
I'm on 8.1 boot loader unlocked and ready to try to root again .Thanks for the help
This is the closest thread i could find to what is happening to my PH-1.
Like videodave1 I 'was' running the latest stock 8.1 and have my bootloader unlocked. In trying to root the phone I did this:
flash boot flash boot twrp.img
adb shell twrp sideload
adb sideload magisk.zip
All installations went well, but when trying to reboot from twrp it forced me to install the app. After that the phone went into boot loop.
* Note how I didn't sideloaded the Oreo 8.1 image before magisk.
By pressing all 3 buttons I can get the phone to reboot and releasing the volume up I can get to Fastboot. Just volume down and power doesn't work.
The problem now is that adb and fastboot no longer recognise the phone. adb devices just gives an empty list and fastboot only shows < waiting for device >
Trying to go into Recovery mode doesn't work either. Power off doesn't work and Restart bootloader, well, restarts the bootloader.
It might be relevant to mention that I'm running adb and fastboot from Terminal in a Mac and that this is my very first and frustrated attempt to root any phone.
For reference this is what the FastBoot Mode brings:
PRODUCT_NAME - Mata
VARIANT - OPENUS
BOOTLOADER VERSION - mata-aad8ac4
BASEBAND VERSION - 2.0.C4-M1.3.1
SECURE BOOT - yes
DEVICE STATE - unlocked
I might have to just resign myself to the ordinary land of unlocked full stock phones
Thanks very much
avocom said:
This is the closest thread i could find to what is happening to my PH-1.
Like videodave1 I 'was' running the latest stock 8.1 and have my bootloader unlocked. In trying to root the phone I did this:
flash boot flash boot twrp.img
adb shell twrp sideload
adb sideload magisk.zip
All installations went well, but when trying to reboot from twrp it forced me to install the app. After that the phone went into boot loop.
* Note how I didn't sideloaded the Oreo 8.1 image before magisk.
By pressing all 3 buttons I can get the phone to reboot and releasing the volume up I can get to Fastboot. Just volume down and power doesn't work.
The problem now is that adb and fastboot no longer recognise the phone. adb devices just gives an empty list and fastboot only shows < waiting for device >
Trying to go into Recovery mode doesn't work either. Power off doesn't work and Restart bootloader, well, restarts the bootloader.
It might be relevant to mention that I'm running adb and fastboot from Terminal in a Mac and that this is my very first and frustrated attempt to root any phone.
For reference this is what the FastBoot Mode brings:
PRODUCT_NAME - Mata
VARIANT - OPENUS
BOOTLOADER VERSION - mata-aad8ac4
BASEBAND VERSION - 2.0.C4-M1.3.1
SECURE BOOT - yes
DEVICE STATE - unlocked
I might have to just resign myself to the ordinary land of unlocked full stock phones
Thanks very much
Click to expand...
Click to collapse
Even though your phone does not show up its there wipe everything.Fallow what Arju said in his post.I got back to stock then took the 8.1 update i'm not rooted but my bootloader is still unlocked.Oh make sure you unlock critical
videodave1 said:
Fallow what Arju said in his post.
Click to expand...
Click to collapse
Thanks for coming back to me. I really appreciate it.
Arju said:
Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too.
Click to expand...
Click to collapse
I might be missing something hopefully obvious here. How can I flash twrp again if I my computer can't see the phone. With the USB phone plugged in and in the FastBoot screen I enter into Terminal:
fastboot flash boot twrp.img
and I get:
< waiting for any device >
How do I flash it from the FastBoot screen? BTW, going to Recovery mode just hangs at the Essential logo.
Thanks
avocom said:
Thanks for coming back to me. I really appreciate it.
I might be missing something hopefully obvious here. How can I flash twrp again if I my computer can't see the phone. With the USB phone plugged in and in the FastBoot screen I enter into Terminal:
fastboot flash boot twrp.img
and I get:
< waiting for any device >
How do I flash it from the FastBoot screen? BTW, going to Recovery mode just hangs at the Essential logo.
Thanks
Click to expand...
Click to collapse
are you able to get to the bootloader menu? where it says start on the top.
Arju said:
are you able to get to the bootloader menu? where it says start on the top.
Click to expand...
Click to collapse
Thanks Arju. If you are referring to the FastBoot menu where you can use the up and down volume keys to select Start, Restart Bootloader, Recovery mode and Power off Yes, but not much else unfortunately.
If I select Recovery mode I don't go to the screen with the blue buttons from twrp.
Thanks
avocom said:
Thanks Arju. If you are referring to the FastBoot menu where you can use the up and down volume keys to select Start, Restart Bootloader, Recovery mode and Power off Yes, but not much else unfortunately.
If I select Recovery mode I don't go to the screen with the blue buttons from twrp.
Thanks
Click to expand...
Click to collapse
What you need to understand is that twrp will not stick after you flash it. This device does not have a recovery partition and that's why you replace the boot partition with twrp and while you're in twrp you need to flash the boot.img back and whatever mods on top of that such as kernel etc.. If you flash a rom then it will replace the twrp with the boot.img found in the rom zip.
So now we need the computer to recognize you device. Could you unplug the cable and change the usb port on you computer. connect your phone while you're in the bootloader menu where it says start on the top.
The use use fastboot command: fastboot devices
See if the computer recognizes you device.

Relock bootloader B35

Here is my situation: I have a A2017U that was running on LOS 14.1 with an unlocked bootloader. The charging pins are wonky and I have to RMA the unit. I did find @DrakenFX files to restore to stock B35, but haven't been successful in relocking the bootloader using the toolkit and other methods. I tried downgrading to B19 using the toolkit but the phone is not recognized in EDL mode. Any help would be greatly appreciated.
@parmar.saab
after all that, what's your current situation?
* you still have twrp
* are you full stock
* did you install QCom drivers? (This is needed for the device to be seen in EDL mode)
post a screenshot of your windows machine " Device Manager " , AFTER booting to EDL
DrakenFX said:
@parmar.saab
after all that, what's your current situation?
* you still have twrp
* are you full stock
* did you install QCom drivers? (This is needed for the device to be seen in EDL mode)
post a screenshot of your windows machine " Device Manager " , AFTER booting to EDL
Click to expand...
Click to collapse
*Yup, I still have TWRP
*Yup, running stock B35 from your zip that I flashed in TWRP
*Installed the drivers from within the toolkit (picture attached)
parmar.saab said:
*Yup, I still have TWRP
*Yup, running stock B35 from your zip that I flashed in TWRP
*Installed the drivers from within the toolkit (picture attached)
Click to expand...
Click to collapse
Last 2 question and I'll give you a little guide to follow.
* You still have access to bootloader/fastboot mode? If so that's all you'll need for what I'm going to reply after your answer here.
* You have my :
- B35 Bootstack
- B35 StockSystem
- B35 stock recovery
If you have all 3 move to them again to sdcard , if you don't have them there already.
P.S. that isn't edl, did you boot to edl using: adb reboot edl ?
DrakenFX said:
Last 2 question and I'll give you a little guide to follow.
* You still have access to bootloader/fastboot mode? If so that's all you'll need for what I'm going to reply after your answer here.
* You have my :
- B35 Bootstack
- B35 StockSystem
- B35 stock recovery
If you have all 3 move to them again to sdcard , if you don't have them there already.
P.S. that isn't edl, did you boot to edl using: adb reboot edl ?
Click to expand...
Click to collapse
I tried booting into EDL mode using the 3 button combo, but I guess it didn't work as I'm on B35. The phone isn't being recognized by the PC because of the wonky charging, and that's why I'm unable to push the command through. I tried pushing the command in terminal emulator but that didn't work either. Is there any other way to boot into EDL mode? If I can just get this thing to boot into EDL mode, I can downgrade to B19 and lock the bootloader using the toolkit, I'm assuming.
parmar.saab said:
I tried booting into EDL mode using the 3 button combo, but I guess it didn't work as I'm on B35. The phone isn't being recognized by the PC because of the wonky charging, and that's why I'm unable to push the command through. I tried pushing the command in terminal emulator but that didn't work either. Is there any other way to boot into EDL mode? If I can just get this thing to boot into EDL mode, I can downgrade to B19 and lock the bootloader using the toolkit, I'm assuming.
Click to expand...
Click to collapse
if you can't send a command through terminal emulator how do you expect to do "fastboot oem lock" let alone flash a full EDL file?
AFAIK it would be as easy as flashing B19 then doing fastboot oem lock. But yeah, no USB means no EDL
parmar.saab said:
I tried booting into EDL mode using the 3 button combo, but I guess it didn't work as I'm on B35. The phone isn't being recognized by the PC because of the wonky charging, and that's why I'm unable to push the command through. I tried pushing the command in terminal emulator but that didn't work either. Is there any other way to boot into EDL mode? If I can just get this thing to boot into EDL mode, I can downgrade to B19 and lock the bootloader using the toolkit, I'm assuming.
Click to expand...
Click to collapse
You're out of luck.
You can't do anything without a computer. You will have to fix the usb port first.
Yeah, but why can't I boot into edl using terminal emulator?
@Oki, any help? When I try the commend "reboot edl" in terminal emulator, it says permission denied.
parmar.saab said:
@Oki, any help? When I try the commend "reboot edl" in terminal emulator, it says permission denied.
Click to expand...
Click to collapse
I think you need root elevated privilege to be able to do any kind if reboot command from terminal emulator.
parmar.saab said:
@Oki, any help? When I try the commend "reboot edl" in terminal emulator, it says permission denied.
Click to expand...
Click to collapse
Again, why do you want to enter EDL if you can't have a decent USB connection to a PC? What do you want to do? Flash a ROM? That takes about 5 minutes and any interruption on the data stream will surely wreak havoc on your device. Same with anything else that you want to try
You need superuser to use the command to reboot to edl. Otherwise you can use the vol+ vol- power combination but you WILL break your device beyond recognition. Total FUBAR.
Choose an username... said:
Again, why do you want to enter EDL if you can't have a decent USB connection to a PC? What do you want to do? Flash a ROM? That takes about 5 minutes and any interruption on the data stream will surely wreak havoc on your device. Same with anything else that you want to try
You need superuser to use the command to reboot to edl. Otherwise you can use the vol+ vol- power combination but you WILL break your device beyond recognition. Total FUBAR.
Click to expand...
Click to collapse
I want to enter the edl/fast boot mode to relock the bootloader. I need to send the phone in for a warranty repair/replacement. The charging port is f in nicky but it isn't bad enough to not let me flash anything if I hold it at a certain angle. I still have twrp, but I'm guessing the faatboot command isn't working as I'm on B35. I feel like I could just brick the phone at this point and send it in to save me the headache.

Can't install TWRP on OP6T

Hi - I am trying to reinstall TWRP on my OP6T after upgrading to OOS 10.3.0.
I am running Minimal ADB and Fastboot v1.4.3 on my Win10 PC. I have connected my phone to my PC, and entered Fastboot mode. The OP6T is detected when I do a fastboot devices command.
Next, I try doing a temporary Recovery Mode boot into TWRP with a fastboot boot twrp-3.3.1-1-fajita.img command. This is where I run into a problem ... While the Minimal ADB and Fastboot window says that the TWRP image was sent to the OP6T, I am still stuck on the Fastboot screen, and the phone is locked up and doesn't reboot the image.
What is going wrong?
¿GJ?
¿GotJazz? said:
Hi - I am trying to reinstall TWRP on my OP6T after upgrading to OOS 10.3.0.
I am running Minimal ADB and Fastboot v1.4.3 on my Win10 PC. I have connected my phone to my PC, and entered Fastboot mode. The OP6T is detected when I do a fastboot devices command.
Next, I try doing a temporary Recovery Mode boot into TWRP with a fastboot boot twrp-3.3.1-1-fajita.img command. This is where I run into a problem ... While the Minimal ADB and Fastboot window says that the TWRP image was sent to the OP6T, I am still stuck on the Fastboot screen, and the phone is locked up and doesn't reboot the image.
What is going wrong?
¿GJ?
Click to expand...
Click to collapse
I'm having the same problem
¿GotJazz? said:
Hi - I am trying to reinstall TWRP on my OP6T after upgrading to OOS 10.3.0.
I am running Minimal ADB and Fastboot v1.4.3 on my Win10 PC. I have connected my phone to my PC, and entered Fastboot mode. The OP6T is detected when I do a fastboot devices command.
Next, I try doing a temporary Recovery Mode boot into TWRP with a fastboot boot twrp-3.3.1-1-fajita.img command. This is where I run into a problem ... While the Minimal ADB and Fastboot window says that the TWRP image was sent to the OP6T, I am still stuck on the Fastboot screen, and the phone is locked up and doesn't reboot the image.
What is going wrong?
¿GJ?
Click to expand...
Click to collapse
3.3.1.-1???...
cultofluna said:
3.3.1.-1???...
Click to expand...
Click to collapse
Affirmative. Fajita 3.3.1-1. See attached screenshot from TWRP.me. Should I be booting into a different version?
¿GotJazz? said:
Affirmative. Fajita 3.3.1-1. See attached screenshot from TWRP.me. Should I be booting into a different version?
Click to expand...
Click to collapse
Those "official" TWRP builds don't work properly on Android 10. Here is a link to the one you need:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
jp0469 said:
Those "official" TWRP builds don't work properly on Android 10. Here is a link to the one you need:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Click to expand...
Click to collapse
Thanks, @jp0469! This helps a lot!
Just to be clear (and to get to a successful conclusion without a bricked phone), I won't be installing a TWRP installer ZIP file after booting into this TWRP image (The old style method), but instead installing the same TWRP IMG file as a "Recovery RAM Disk", correct?
¿GJ?
¿GotJazz? said:
Thanks, @jp0469! This helps a lot!
Just to be clear (and to get to a successful conclusion without a bricked phone), I won't be installing a TWRP installer ZIP file after booting into this TWRP image (The old style method), but instead installing the same TWRP IMG file as a "Recovery RAM Disk", correct?
¿GJ?
Click to expand...
Click to collapse
Need a little more info before you proceed.
I know you said that you're currently on Android 10.3.0
Are you rooted with Magisk? If not, are you planning on rooting?
jp0469 said:
Need a little more info before you proceed.
I know you said that you're currently on Android 10.3.0
Are you rooted with Magisk? If not, are you planning on rooting?
Click to expand...
Click to collapse
I was rooted with Magisk, but that got lost when I did the 10.3.0 update. Definitely planning on TWRPing and rooting again, as long as it's safe.
¿GotJazz? said:
I was rooted with Magisk, but that got lost when I did the 10.3.0 update. Definitely planning on TWRPing and rooting again, as long as it's safe.
Click to expand...
Click to collapse
Stick to good old ones...
Once booted in twrp via fastboot flash the installer zip. It has always worked and will always. Always latest version. And flash Magisk after.
¿GotJazz? said:
I was rooted with Magisk, but that got lost when I did the 10.3.0 update. Definitely planning on TWRPing and rooting again, as long as it's safe.
Click to expand...
Click to collapse
Put the latest Magisk zip and TWRP installer (zip file) on your phone's internal memory if you don't already have them there. Now you can fastboot boot the TWRP img file (Q version). Next flash the TWRP zip to permanently install TWRP into recovery. Reboot back to recovery to make sure it worked and then flash Magisk to re-gain root.
Reboot
Thanks, guys - The only reason I asked about the alternate "RAM Disk" method was because it was listed as the installation method by the developer on the link that @jp0469 provided earlier.
I'll try the old-fashioned method, since y'all say that it works OK.
I have a brand new hp windows 10 PC and a new op6t converted to international version. Running pie latest oxygen os. I need to get minimal adb fastboot installed so I can install twrp and root. Ik it's a little different process to get twrp on 6t but I need some help. Can someone provide me with the correct fastboot to install
[email protected] said:
I have a brand new hp windows 10 PC and a new op6t converted to international version. Running pie latest oxygen os. I need to get minimal adb fastboot installed so I can install twrp and root. Ik it's a little different process to get twrp on 6t but I need some help. Can someone provide me with the correct fastboot to install
Click to expand...
Click to collapse
I always install the latest directly from Google. There is a link on this page to the latest version of Windows ADB and Fastboot. Just unzip the file you download into a directory of your choice.
Everytime I try to boot twrp It says waiting on device. What's that mean
[email protected] said:
Everytime I try to boot twrp It says waiting on device. What's that mean
Click to expand...
Click to collapse
It mean you didn't install driver on your PC.
---------- Post added at 03:38 AM ---------- Previous post was at 03:35 AM ----------
¿GotJazz? said:
Hi - I am trying to reinstall TWRP on my OP6T after upgrading to OOS 10.3.0.
I am running Minimal ADB and Fastboot v1.4.3 on my Win10 PC. I have connected my phone to my PC, and entered Fastboot mode. The OP6T is detected when I do a fastboot devices command.
Next, I try doing a temporary Recovery Mode boot into TWRP with a fastboot boot twrp-3.3.1-1-fajita.img command. This is where I run into a problem ... While the Minimal ADB and Fastboot window says that the TWRP image was sent to the OP6T, I am still stuck on the Fastboot screen, and the phone is locked up and doesn't reboot the image.
What is going wrong?
¿GJ?
Click to expand...
Click to collapse
Type Command: fastboot flash boot
And Use TWRP 3.3.1.30 .
Hi - I am trying to reinstall TWRP on my OP6T after upgrading to OOS 10.3.0.
I am running Minimal ADB and Fastboot v1.4.3 on my Win10 PC. I have connected my phone to my PC, and entered Fastboot mode. The OP6T is detected when I do a fastboot devices command.
Next, I try doing a temporary Recovery Mode boot into TWRP with a fastboot boot twrp-3.3.1-1-fajita.img command. This is where I run into a problem ... While the Minimal ADB and Fastboot window says that the TWRP image was sent to the OP6T, I am still stuck on the Fastboot screen, and the phone is locked up and doesn't reboot the image.
What is going wrong?
Click to expand...
Click to collapse
same thing happened to me, but my screen went black and i cant seem to turn it back on again. what a day. fml
i really need help, i only have that one phone for daily usage. arghhhh
uncleheng said:
same thing happened to me, but my screen went black and i cant seem to turn it back on again. what a day. fml
i really need help, i only have that one phone for daily usage. arghhhh
Click to expand...
Click to collapse
press volume down,up and power button same time for 10sec your phone will boot to bootloader mode.
After doing the fastboot boot twrp-3.3.1-30-fajita-Q-mauronofrio.img in Fastboot Mode, I installed twrp-3.3.1-30-fajita-installer-mauronofrio.zip in the booted TWRP Recovery Mode, and everything is working fine again.
Thanks, guys!
Hey I am running Android 10.3.7 and am having the same problem, I tried unofficial twrp linked abouve and still stuck on fastboot screen, I think I'm using abd 1.43, if twrp doesn't work is there an alternative? I'm newish to rooting I've rooted other phones but that was back in the good old days where it wasn't complicated. I am running a T-Mobile phone converted to international with bootloader unlocked

Google Pixel 3a (sargo) brick - error boot prepare

Hi,
Today I wanted change my recovery. I had the Lineage OS recovery, but i was trying to install the twrp recovery.
So, the guide of twrp says that you should boot the twrp via fastboot boot twrp.img and install via the booted twrp. But I mistaken the command and I wrote fastboot flash boot twrp.img, I tried to reboot and the device booted himself in fastboot with the enter reason "error boot prepare" and I can't boot into the system or recovery.
I tried to flash the official image downloaded from the Google Developers website, but when i run ./flash-all.sh, console get stuck. I waited for about 15 minutes but nothing. I tried even the official Android Flash Tool but after 10 seconds it says "Your device stopped responding. You may have to select restart in the bootloader menu in order for it to be recognised again."
Does anyone know how to help me? Thanks in advance.
GioPan_ said:
Hi,
Today I wanted change my recovery. I had the Lineage OS recovery, but i was trying to install the twrp recovery.
So, the guide of twrp says that you should boot the twrp via fastboot boot twrp.img and install via the booted twrp. But I mistaken the command and I wrote fastboot flash boot twrp.img, I tried to reboot and the device booted himself in fastboot with the enter reason "error boot prepare" and I can't boot into the system or recovery.
I tried to flash the official image downloaded from the Google Developers website, but when i run ./flash-all.sh, console get stuck. I waited for about 15 minutes but nothing. I tried even the official Android Flash Tool but after 10 seconds it says "Your device stopped responding. You may have to select restart in the bootloader menu in order for it to be recognised again."
Does anyone know how to help me? Thanks in advance.
Click to expand...
Click to collapse
Do you have tryied to run the official google tool in Windows to try to rescue it?
Estebiu said:
Do you have tryied to run the official google tool in Windows to try to rescue it?
Click to expand...
Click to collapse
Yes, I wrote in the post, I tried both the command line tool and the chrome version. Btw i'm on linux
Okay so, I fixed.
For anyone who will have this problem you just need to flash official Android 9 and next Android 10. Only with Android 10 you can use fastboot flash boot recovery.img (you can't use twrp in android 10 with the Pixel 3a)
GioPan_ said:
Okay so, I fixed.
For anyone who will have this problem you just need to flash official Android 9 and next Android 10. Only with Android 10 you can use fastboot flash boot recovery.img (you can't use twrp in android 10 with the Pixel 3a)
Click to expand...
Click to collapse
I'll try this...
GioPan_ said:
Okay so, I fixed.
For anyone who will have this problem you just need to flash official Android 9 and next Android 10. Only with Android 10 you can use fastboot flash boot recovery.img (you can't use twrp in android 10 with the Pixel 3a)
Click to expand...
Click to collapse
Does this work if adb not working? I only have fastboot.
WriteLovey said:
Does this work if adb not working? I only have fastboot.
Click to expand...
Click to collapse
It depends if your pc were authorized, if it was, you can use fastboot to flash the stock version of Android 9, just running the flash-all(.bat) script.
GioPan_ said:
It depends if your pc were authorized, if it was, you can use fastboot to flash the stock version of Android 9, just running the flash-all(.bat) script.
Click to expand...
Click to collapse
I'm not certain I understand what you mean by PC authorized? I'm using a Windows 10 tablet. When the phone is attached to the computer it sees it as a device that can be disconnected through USB.
WriteLovey said:
I'm not certain I understand what you mean by PC authorized? I'm using a Windows 10 tablet. When the phone is attached to the computer it sees it as a device that can be disconnected through USB.
Click to expand...
Click to collapse
All is well. I'm back on my Pixel, yeah!
GioPan_ said:
It depends if your pc were authorized, if it was, you can use fastboot to flash the stock version of Android 9, just running the flash-all(.bat) script.
Click to expand...
Click to collapse
I just had an encounter with this. I was rooting my device (Pixel 3A) and messed up my partitions through accidentally attempting a downgrade which broke all my ****. I was unable to easily reset this device to factory, so it took me several days to figure out and root. I'm getting better though as a hacker, because a year ago this would have taken me a month.
I was able to enter recovery mode (lying down Android, NO COMMAND). From this recovery mode, adb devices -l recognized my device, although I was unable to get a shell.
At first, ADB was telling me the device was authorized, but I messed with a bunch of other stuff (tried to flash a bunch of different partitions and monkey around in general trying to install Magisk) and then ADB started telling me it wasn't authorized when I used devices -l.
Once it said unauthorized, I was unable to issue the device any commands with ADB, so I just used hardware keys to get into recovery mode. From there, I selected OTA update, and it got into sideload mode. At that point, I used adb sideload with the OTA package that I downloaded here https://developers.google.com/android/ota
^^^ That operation did successfully restore my device to factory
This following guide here describes the details of how to use hard keys to enter recovery on this phone (don't download anything from there tho, and make sure your adblock is on)
How to Hard Reset your new Google Pixel 3a [Tutorial]
In this article, you will learn how to start your Google Pixel 3a up into the Recovery Mode and perform the Hard Reset to make it work perfectly again.
thedroidguy.com
I just wanted to say, I've been wrestling this hardbrick for a couple of days with my Pixel 3a.
I've finally overcome it by sideloading the most recent OTA update after using a hard key combo to get into recovery mode. The hard key combo is hold Power Button, tap Volume Up, then release both. Then, all you need is to use the command:
adb sideload <OTA.zip>
^^^OTA wasn't the actual filename though, you can download OTA packages for Pixel 3A here: https://developers.google.com/android/ota
the OTA binaries are NOT the same as the factory images, which is here
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Sideloading the OTA package brought my phone back from only having fastboot and recovery mode, even when flash-all.sh from the official downloaded firmware failed. Now I know how to undo damage that I cause by rooting this thing. Since I sideloaded newest firmware, it was also like applying an update. I easily got root after that, and I've logged the process. I'll make it into a guide soon
I'll just note that if you accidentally flashed the TWRP boot image instead of simply booting into it, I believe all you have to do is flash the stock boot.img to fix the problem. Obviously you can sideload the entire rom image, but that shouldn't be necessary.
Using the Windows computer (or whatever computer you are sending ADB commands from), download the full stock image directly from Google. Unzip it and then upzip the folder inside. You should find the boot.img file inside that folder. Take that file and then flash it to the phone using the normal ADB command: fastboot flash boot boot.img
While I haven't tried this myself recently, it should work in theory. The command "fastboot flash boot twrp.img" flashes the boot partition with a non-working twrp image, so replacing the faulty image with the stock boot.img should fix the problem.
If I did the same I would first attempt to manually put device in bootloader/aka fastboot mode then fastboot flash the stock boot.img , sudo fastboot flash boot boot.img --slot all
I only read the op (first post here);but I betcha that would have worked. Then sudo ./flash-all.sh and let it do it's thing.

Categories

Resources