soft brick help, adb help - Xiaomi Redmi Note 7 Questions & Answers

was running the xiaomi.eu rom beta then flashed to stable and now soft brick
adb devices shows "recovery" instead of "device"
adb reboot fastboot and the phone goes into an encrypted twrp 3.3.0.0
I have miflashtool

Aaagogo said:
was running the xiaomi.eu rom beta then flashed to stable and now soft brick
adb devices shows "recovery" instead of "device"
adb reboot fastboot and the phone goes into an encrypted twrp 3.3.0.0
I have miflashtool
Click to expand...
Click to collapse
Hey there!
I kinda new here so forgive me if I gave you a wrong guide, but from what i read across forums, if you're phone get soft bricked, you just need to flash the stock firmware. try to find latest xiaomi stock firmware.
Adb devices shows "recovery" means your device was in recovery mode. Try "adb reboot recovery" and you'll end up in your custom recovery (I assume you installed one). If your recovery was encrypted try to install push "disable dm variety" command on adb and when your custom recovery asks for password, just press cancel or enter and you'll enter recovery mode.
From your recovery mode, you can enter sideload and install everything from there using adb from your computer.
Hopefully your phone will get better soon! lol
P.S.: sorry for my bad English, I'm not a native speaker.

rchmdnglng said:
Hey there!
I kinda new here so forgive me if I gave you a wrong guide, but from what i read across forums, if you're phone get soft bricked, you just need to flash the stock firmware. try to find latest xiaomi stock firmware.
Adb devices shows "recovery" means your device was in recovery mode. Try "adb reboot recovery" and you'll end up in your custom recovery (I assume you installed one). If your recovery was encrypted try to install push "disable dm variety" command on adb and when your custom recovery asks for password, just press cancel or enter and you'll enter recovery mode.
From your recovery mode, you can enter sideload and install everything from there using adb from your computer.
Hopefully your phone will get better soon! lol
P.S.: sorry for my bad English, I'm not a native speaker.
Click to expand...
Click to collapse
going to retry twrp from 10.3.6.0 PFGMIXM

TWRP is encrypted,
i miflashtoll back to 10.3.6.0 PFGMIXM, unlocked bootloader
flash twrp 3.3.0.0 and still the same result, encrypted TWRP.
no twrp means no root, need assistance.

Aaagogo said:
was running the xiaomi.eu rom beta then flashed to stable and now soft brick
adb devices shows "recovery" instead of "device"
adb reboot fastboot and the phone goes into an encrypted twrp 3.3.0.0
I have miflashtool
Click to expand...
Click to collapse
Hello,
And if instead of executing "adb fastboot reboot", you try to access fastboot mode with Vol- and Power?
What happen?

hugomoya said:
Hello,
And if instead of executing "adb fastboot reboot", you try to access fastboot mode with Vol- and Power?
What happen?
Click to expand...
Click to collapse
i can access fastboot with no problems, it's booting into recovery that doesn't work
i am using twrp from the official thread;
https://forum.xda-developers.com/redmi-note-7/how-to/one-redmi-note-7-unlock-bootloader-t3890751
same thing happen on all 3 methods of rebooting after flashing, all boots into encrypted twrp.
i hope there is a solution, i can't try anything now, there is a 24hour waiting period to unlock more than 1 bootloader a day

IceMan on xiaomi.eu has a working twrp;
TWRP 3.3.2-2 RN7 by IceMan

Aaagogo said:
i can access fastboot with no problems, it's booting into recovery that doesn't work
i am using twrp from the official thread;
https://forum.xda-developers.com/redmi-note-7/how-to/one-redmi-note-7-unlock-bootloader-t3890751
same thing happen on all 3 methods of rebooting after flashing, all boots into encrypted twrp.
i hope there is a solution, i can't try anything now, there is a 24hour waiting period to unlock more than 1 bootloader a day
Click to expand...
Click to collapse
Which is the principal problem?
Does the smartphone not start? I mean, the operating system.
Because if that's the problem, and you can start in "fastboot" mode, you can install your official ROM with MiFlash.
And reinstall TWRP, Orange Fox for example.
Regards!

hugomoya said:
Which is the principal problem?
Does the smartphone not start? I mean, the operating system.
Because if that's the problem, and you can start in "fastboot" mode, you can install your official ROM with MiFlash.
And reinstall TWRP, Orange Fox for example.
Regards!
Click to expand...
Click to collapse
every method of twrp with the "unofficial" twrp from the link to boot into encrypted twrp, can't install magisk for twrp to take
https://forum.xda-developers.com/redmi-note-7/how-to/one-redmi-note-7-unlock-bootloader-t3890751
twrp from link above
normal reboot goes into encrypted android
fastboot no prob

Aaagogo said:
every method of twrp with the "unofficial" twrp from the link to boot into encrypted twrp, can't install magisk for twrp to take
https://forum.xda-developers.com/redmi-note-7/how-to/one-redmi-note-7-unlock-bootloader-t3890751
twrp from link above
normal reboot goes into encrypted android
fastboot no prob
Click to expand...
Click to collapse
Try with Orange Fox R10.0 Stable (Based in TWRP 3.3.1)
https://sourceforge.net/projects/orangefox/files/lavender/
Regards!

hugomoya said:
Try with Orange Fox R10.0 Stable (Based in TWRP 3.3.1)
https://sourceforge.net/projects/orangefox/files/lavender/
Regards!
Click to expand...
Click to collapse
cheers for that, i'm using twrp 3.2.3-2 RN7 by IceMan over at xiaomi.eu

Related

Need help, bricked my 3s

Was supposed to flash CM13 Rom. I did a full wipe including system via TWRP.
Before flashing I decided to reboot into recovery, but it didn't. Only gets stuck in the MI logo now. Can't boot into recovery anymore.
I can go into Fastboot mode. Tried flashing twrp via ADB but whenever i type 'adb devices' in command prompt it says device is offline.
Tried to enter EDL via ADB in fastboot mode, it gets stuck at 'waiting for device'.
When plugged in PC, it gets detected as USB ADB interface
Bootloader was unlocked prior, was on xioami.eu ROM before this. I have TWRP system backup of last ROM installed.
Hoping someone can point me in the right direction on what to do next. Very much appreciated, thank you.
Hi Supdow,
I was facing with the same issue and I also thought I bricked my phone... No worries. To solve it is very easy, just unlock your bootloader again with Mi UnlockTool. Than you have access to your recovery again.
Good luck!
Boesila said:
Hi Supdow,
I was facing with the same issue and I also thought I bricked my phone... No worries. To solve it is very easy, just unlock your bootloader again with Mi UnlockTool. Than you have access to your recovery again.
Good luck!
Click to expand...
Click to collapse
Do I have to apply to unlock the bootloader again like the first time?
Boesila said:
Hi Supdow,
I was facing with the same issue and I also thought I bricked my phone... No worries. To solve it is very easy, just unlock your bootloader again with Mi UnlockTool. Than you have access to your recovery again.
Good luck!
Click to expand...
Click to collapse
Was able to unlock bootloader again, but I still can't access recovery. I may have forgotten how to exactly do this since the last time I did it. What do i have to do after unlocking bootloader? I tried flashing TWRP via fastboot but it only gives me an error.
So you have a few options
1. Hold volume+ & - and power (if you have twrp)
2. Take fedosis twrp 3.1 and installer, put twrp 3.1 into extracted installer folder, then shift+right click on installer folder, open cmd, then type
fastboot flash recovery twrp_name.img
fastboot boot twrp_name.img (or do step 1)
3. Just flash dev/stable with miflash (recommendation: go into fastboot, then like step 2 go into cmd and type fastboot oem edl then flash mi rom)
Hope this helps
bekcicandrej said:
So you have a few options
1. Hold volume+ & - and power (if you have twrp)
2. Take fedosis twrp 3.1 and installer, put twrp 3.1 into extracted installer folder, then shift+right click on installer folder, open cmd, then type
fastboot flash recovery twrp_name.img
fastboot boot twrp_name.img (or do step 1)
3. Just flash dev/stable with miflash (recommendation: go into fastboot, then like step 2 go into cmd and type fastboot oem edl then flash mi rom)
Hope this helps
Click to expand...
Click to collapse
Thank you, finally on CM13 fedosis!

[Help][A2017G] SoftBrick only bootloader and stock recovery

Hi,
I have an A2017G which after trying linageos had the stock rom from here https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484 TWRP and an unlocked bootloader. That worked ok, and I wanted to upgrade to the stock ROM 7.1. I installed this using TWRP https://forum.xda-developers.com/showpost.php?p=71664539&postcount=29. But now when it boot's after the bootloader it's stuck showing a linux logo, and it won't boot Android.
In the bootloader (http://i.imgur.com/Os4vkwT.jpg) I can try to go to fastboot, but selecting that only reboots the phone. I can however select recovery and go to the stock recovery (http://i.imgur.com/PBj6y6X.jpg). From there I have tried to sideload (selecting Apply update from ADB and adb sideload rom.zip) the stock rom (http://www.ztedevice.com/support/detail?id=1170789A90BA42E18B3364B80C7F5A26), the previous rom I tried to install (https://forum.xda-developers.com/showpost.php?p=71664539&postcount=29) and another TWRP stock rom (https://forum.xda-developers.com/axon-7/development/rom-kernel-stock-7-1-1-b02-based-a2017g-t3592470) but all fail at the very beginning saying "(adbd status 1) Installation aborted" (http://i.imgur.com/RzNSBtu.jpg).
I also tried to install linageos back using sideload but it fails ("failed to verify whole-file signature"). I believe that is because it's not the official rom and the stock recovery only accepts that.
ADB only works in sideload mode and fastboot doesn't (it loads the bootloader again).
Do you know how I should proceed? How could I install the stock rom, or TWRP again?
Thanks in advance.
Try it with this guide:
https://forum.xda-developers.com/axon-7/how-to/guide-reinstall-twrp-root-update-to-t3578552
If you can't flash recovery with axon7toolkit try it with the last step "Get Fastboot" first. ZTE removed the fastboot mode in Nougat, so you have to flash another fastboot image.
If you can boot into fastboot again you can flash TWRP and from TWRP a rom.
Good luck!
Hi Darkem,
Thanks a lot, that actually worked. I was under the impression I wouldn't be able to install TWRP because I was only able to use the command "adb sideload update.zip" but other commands like "adb reboot edl" didn't work. But as it's said in the other post, pushing the three buttons of the phone set the phone into EDL mode. From there I was able to install TWRP.
Thanks a lot again
(A2017G) Hello. I no longer have access to fastboot because I flash a stock rom (Nougat) with the recovery stock and it has removed my modified bootloader, I managed to install twrp in edl mode but I still have no access to bootloader. What should I do please? Flash a stock rom (Marshmallow) here (https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547) to gain access to fastboot again (bootloader )? Thank you. Sorry translation from French to English with Google Translate
GAO161 said:
Hello. I no longer have access to fastboot because I flash a stock rom (Nougat) with the recovery stock and it has removed my modified bootloader, I managed to install twrp in edl mode but I still have no access to bootloader. What should I do please? Flash a stock rom (Marshmallow) here (https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547) to gain access to fastboot again (bootloader )? Thank you. Sorry translation from French to English with Google Translate
Click to expand...
Click to collapse
Granted I have the A2017U, but in stock recovery I can still access the phone memory with my pc. Why not download the stock rom from ZTE, put it on the phone memory, and flash it in the stock recovery?
tabletalker7 said:
Granted I have the A2017U, but in stock recovery I can still access the phone memory with my pc. Why not download the stock rom from ZTE, put it on the phone memory, and flash it in the stock recovery?
Click to expand...
Click to collapse
So I flash a recovery stock with twrp and then I update to an official version Marshmallow with the recovery stock? I will recover my bootloader? Thank you
GAO161 said:
So I flash a recovery stock with twrp and then I update to an official version Marshmallow with the recovery stock? I will recover my bootloader? Thank you
Click to expand...
Click to collapse
Sorry, why do you want fastboot? If you're planning to relock the bootloader you'll need to be fully stock, which wouldn't be the case if you just installed a fastboot zip. Relocking the bootloader is probably the only thing that fastboot is mandatory for
Choose an username... said:
Sorry, why do you want fastboot? If you're planning to relock the bootloader you'll need to be fully stock, which wouldn't be the case if you just installed a fastboot zip. Relocking the bootloader is probably the only thing that fastboot is mandatory for
Click to expand...
Click to collapse
I want fastboot to be able to order with adb. Before I had it and when I flash a rom stock nougat it has deleted me
GAO161 said:
I want fastboot to be able to order with adb. Before I had it and when I flash a rom stock nougat it has deleted me
Click to expand...
Click to collapse
on fastboot mode you have fastboot lol
you have adb on FTM mode (vol down + power) or recovery
Choose an username... said:
on fastboot mode you have fastboot lol
you have adb on FTM mode (vol down + power) or recovery
Click to expand...
Click to collapse
I want to go back to ROM stock and bootloader locked but when I do not have access to the bootloader anymore I can not do the command "adb lock oem"

Without commands

Hello, I have an issue with TWRP.
When I reboot to system the next time that I want to enter recovery the phone doesn't enter to recovery, but after flashing it, it does. It says "Without Commands" instead of enter to TWRP. I tried to enter in it on fastboot mode. I installed TWRP 3.2.1 with 3.0.1 Vache.
And yes I already have unlocked the bootloader, I'm on November 1st security patch without root.
What can I do?
Regards to everyone :laugh:
Are you sure that the command you used was fastboot flash recovery twrpxxx.img? Also kingroot pc sometimes tries to install a custom recovery, it got rid of my stock recovery like that.
thedr34m13 said:
Are you sure that the command you used was fastboot flash recovery twrpxxx.img? Also kingroot pc sometimes tries to install a custom recovery, it got rid of my stock recovery like that.
Click to expand...
Click to collapse
Yes, a few moments ago I flashed it once more sucessfully, and the problem persists.
I'm sure
thedr34m13 said:
Are you sure that the command you used was fastboot flash recovery twrpxxx.img? Also kingroot pc sometimes tries to install a custom recovery, it got rid of my stock recovery like that.
Click to expand...
Click to collapse
Yes I'm sure, I flashed it once more and the problem persists.
doctroll971 said:
Hello, I have an issue with TWRP.
When I reboot to system the next time that I want to enter recovery the phone doesn't enter to recovery, but after flashing it, it does. It says "Without Commands" instead of enter to TWRP. I tried to enter in it on fastboot mode. I installed TWRP 3.2.1 with 3.0.1 Vache.
And yes I already have unlocked the bootloader, I'm on November 1st security patch without root.
What can I do?
Regards to everyone :laugh:
Click to expand...
Click to collapse
I saw a new detail, the recovery says "Unable to mount storage"

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

flashing oneplus one

howto flash the one without working volume controls??
is this possible?
Yes, it is possible. LineageOS has an option to boot to recovery or fastboot via the standard reboot dialogue.
You can also use adb commands "adb reboot recovery" or "adb reboot fastboot".
kekerosberg said:
Yes, it is possible. LineageOS has an option to boot to recovery or fastboot via the standard reboot dialogue.
You can also use adb commands "adb reboot recovery" or "adb reboot fastboot".
Click to expand...
Click to collapse
thanks for the reply. is there any manual to do so?
for im´m an absolute newbie on this. adb and faastboot are installed on my ubuntu machine.
Depends on what you are trying to accomplish.
Flash TWRP recovery? You may also use LineageOS recovery instead of TWRP if you want. Follow their instructions https://twrp.me/oneplus/oneplusone.html
Flash LineageOS? Follow the wiki instructions https://wiki.lineageos.org/devices/bacon/install
Beware that unlocking the bootloader will erase all data on the phone.
kekerosberg said:
Yes, it is possible. LineageOS has an option to boot to recovery or fastboot via the standard reboot dialogue.
You can also use adb commands "adb reboot recovery" or "adb reboot fastboot".
Click to expand...
Click to collapse
yes i tried but failed because in the last step i had to reboot in recovery with the volume control and start button, because at that point iḿ in fastboot mode and adb reboot recovery won work?!
yes i tried but i failed because in the last step i had to reboot in recovery with the volume control and start button, because at that point i'm in fastboot mode and adb reboot recovery won't work?!
While in fastboot mode, you may boot into recovery using "fastboot reboot recovery". Almost there, good luck!
kekerosberg said:
While in fastboot mode, you may boot into recovery using "fastboot reboot recovery". Almost there, good luck!
Click to expand...
Click to collapse
doesn't work on my ubuntu machine. "unkown rebbot target recvery..
i tried .guess i check it on my win machine.
You can also reboot to recovery from within the OS by using "adb reboot recovery". It should work if you were able to reboot to fastboot using this method.
unfortunately it does not work while being in fastboot mode.
adb says device 'null'not found..
Yes, you are supposed to use adb from whatever OS you have installed, CM, CyanogenOS, LOS, ...
but?
is flashing possible without being in fastboot mode? just using adb?
I understood that you had already flashed the recovery. Now you need to boot into the recovery to flash an OS.
Fastboot is used to flash the recovery.
Recovery is used to flash the OS.
yes i think that's it and therefore i had to reboot to recovery without working controls..
koeskemc said:
yes i think that's it and therefore i had to reboot to recovery without working controls..
Click to expand...
Click to collapse
any idea?
kekerosberg said:
I understood that you had already flashed the recovery. Now you need to boot into the recovery to flash an OS.
Fastboot is used to flash the recovery.
Recovery is used to flash the OS.
Click to expand...
Click to collapse
yes, and that's my prob how to boot into recovery without using any controls?
or is there another way?e.g adb sideload??
You have a working operating system installed? Cyanogenmod, LineageOS or something similar?
Use the power button to boot into the operating system. Then connect the phone to your PC and "adb reboot recovery".
hello again.
i got a new prob. i've istalled twrp(don know how!)
with terp i imstalled lineage 18.1...zip.
but after booting i alwasy get twrp and not the os.
whats my fault
or do ihavr to istall the .img file??instead of.zip?
hello again,
everything's fine so far. i got lineage os on boot up! but how to get back to twrp again to install gapps??

Categories

Resources