Related
Tried to flash OB3 and SuperSu on my encrypted OP5 with TWRP. Was stuck at OP logo.
Tried to go back to stable Oreo build for OP5. Again, was stuck at OP logo.
Now the screen is unresponsive in TWRP (can't even swipe to allow modifications on the first screen!).
If I install stock recovery, I can navigate recovery with buttons. I tried installing OOS 5 with stock recovery from internal storage. It doesn't work. I tried to adb sideload. The computer throws a bad_alloc error.
Anyone in the same boat, or good enough to advice?
pentruexperiment said:
Tried to flash OB3 and SuperSu on my encrypted OP5 with TWRP. Was stuck at OP logo.
Tried to go back to stable Oreo build for OP5. Again, was stuck at OP logo.
Now the screen is unresponsive in TWRP (can't even swipe to allow modifications on the first screen!).
If I install stock recovery, I can navigate recovery with buttons. I tried installing OOS 5 with stock recovery from internal storage. It doesn't work. I tried to adb sideload. The computer throws a bad_alloc error.
Anyone in the same boat, or good enough to advice?
Click to expand...
Click to collapse
but u'll lost your data
i had this too, you need to flash stock recovery from cmd in yor pc by:
"fastboot flash recovery recovery_name.img"
then wipe everything,
reboot again into recovery
click on adb
and then download the stable firmware oreo 5
in adb mode with stock recovery put firmware in the same folder
and input - adb sideload name_of_firmware.zip
That fixed my phone, i'll hope and yours will be fixed
sk.c0de said:
but u'll lost your data
i had this too, you need to flash stock recovery from cmd in yor pc by:
"fastboot flash recovery recovery_name.img"
then wipe everything,
reboot again into recovery
click on adb
and then download the stable firmware oreo 5
in adb mode with stock recovery put firmware in the same folder
and input - adb sideload name_of_firmware.zip
That fixed my phone, i'll hope and yours will be fixed
Click to expand...
Click to collapse
Thanks,
The device is recognized well by the computer (when I write 'adb devices'). But when I try to sideload ('adb sideload OOS5.zip'), it gives me an error with bad_alloc. any ideas?
pentruexperiment said:
Thanks,
The device is recognized well by the computer (when I write 'adb devices'). But when I try to sideload ('adb sideload OOS5.zip'), it gives me an error with bad_alloc. any ideas?
Click to expand...
Click to collapse
Try unbrick method I think it's the quickest way to get back your device.
This procedure is intended for oreo users only !
WARNING : This is a Beta Build and is not completely stable. ANY data loss or bricked phones is not my or any of the Telegram members' responsibility. You and only YOU are responsible for the consequences.
The TWRP provided is a Beta Build by Telegram Group member Maanush. All credits go to him and the all other members of Telegram Group.
TWRP(Beta) : http://www.mediafire.com/file/7p7ida6ems0ta9l/TWRP_BETA_BUILD.img
Tutorial :
1. adb reboot bootloader
2. fastboot oem unlock
3. fastboot flash recovery twrp.img
4. fastboot oem reboot-recovery
After flashing TWRP:
1. Flash Force Encrypt Disabler.zip
2. Flash Magisk.zip
3. Wipe Dalvik/Cache
4. Format Data
6. Reboot
Not working
Sir, there is an error with magisk merge.img mount falied. Please help...
Akash.sep28 said:
Sir, there is an error with magisk merge.img mount falied. Please help...
Click to expand...
Click to collapse
If you're facing issues while flashing magisk modules then you might have done something wrong. Remember that you have to flash force encrypt disabler and format data after that
Sir
After flashing twrp my device restore stock recovery.
Sir I want only twrp recovery install on it.
So I can make backup
Help
CodeNameMadmax said:
Sir
After flashing twrp my device restore stock recovery.
Sir I want only twrp recovery install on it.
So I can make backup
Help
Click to expand...
Click to collapse
After successfully flashing image, write 'fastboot oem reboot-recovery'. Your device will boot into a black screen, now double press the power button, swipe to unlock. You will have to flash magisk zip(use adb sideload or flash from sd card) to prevent system from replacing TWRP.
Remember that you'll have to format your device once to be able to access internal storage so that you can restore backups
My phone not entering into the recovery mode
does the twrp3.1.1.0 work for 5 nov security update?
guys will the the old twrp3.1.1.0 for oreo works on latest 5 nov security patch
prashanth_a_r said:
guys will the the old twrp3.1.1.0 for oreo works on latest 5 nov security patch
Click to expand...
Click to collapse
Yes
sarathkrish02 said:
My phone not entering into the recovery mode
Click to expand...
Click to collapse
How are you trying to enter recovery mode?
Anas Rahman said:
How are you trying to enter recovery mode?
Click to expand...
Click to collapse
Now I can enter into twrp but tell me how to fix 0mb internal storage
sarathkrish02 said:
Now I can enter into twrp but tell me how to fix 0mb internal storage
Click to expand...
Click to collapse
Follow the steps that say "After flashing TWRP"
sarathkrish02 said:
Now I can enter into twrp but tell me how to fix 0mb internal storage
Click to expand...
Click to collapse
Or Google the same thing U will get the perfect answer even I had the same issue
About installation on twrp recovery
iam using lenovo k8 note. i have tried to install twrp recovery but i cant able to install it. i hve tried all the ways like using cmd all the cammands. after i complete flashing twrp and booting again it displays like "orange state " ,"device has been unlckd and cant b trusted" ,"your device will boot in 5 sec" after that my phone restarts and nothing happens . i have tried all possible ways . pls hlp me to install twrp .
salam... i m not entering into twrp recovery mode by this command "fastboot oem reboot-recovery" also tried to switch off cel phone with vol up+vol down+pwr btn and then vol+up and pwr btn but not entered... also tried with vol+down and pwr btn and select recovery mode but fail....
Finally i got my cell rooted successfully here is right twrp for lenovo k8 plus. All credit goes to @anasrehman @kqixs
https://androidfilehost.com/?fid=1322778262903998122
Hi, I have the same issue and I tried all the possible ways but nothing. Can anyone tell if got the same issue but got resolved
no usb debugging
currently my phone is switched off. I am able to go into normal recovery mode. I think the USB Debugging mode is off. How can i revive it again. I was thinking of applying from SD Card a custom ROM flashing. But how to unroot it first
Twrp Oreo Manning
I am just facing one major problem, every time I reboot my device It seems to be my recovery keeps installing again and again which means it's always so my internal storage - 0, after the formatting it reads it but after a new reboot, it doesn't.
Is this working now?
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
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
Hello,
I recently tried to degoogle my phone with Lineage and twrp. It's been a bit of a brick wall. Long story short i'm stuck in twrp. It boots into recovery fine from that. Everything else is DOA. When I plug it in the pc recognizes it and I can see my storage. I run adb devices and it comes up. When I reboot to bootloader I see download as I should on the phone screen and I hear it connect to the pc. Then that's it, it doesn't show up as storage or when I run adb of fastboot commands. I fairly certain TWRP F'd this all up. I have the recovery image for lineage but like I said nothing gets done.
So the question is, is it totally bricked or is there a soulotion I haven't found yet?
Thanks for the listen.
Some LineageOS build working with own recovery so you can try to flash with LineageOS recovery via sideload option...
gouthamram said:
Some LineageOS build working with own recovery so you can try to flash with LineageOS recovery via sideload option...
Click to expand...
Click to collapse
That's the whole problem. I can't even do that.
mech1164 said:
That's the whole problem. I can't even do that.
Click to expand...
Click to collapse
First of all flash LineageOS recovery on fastboot mode then restart to LineageOS recovery & flash LineageOS rom via adb sideload...
Everything you will do even working fastboot mode...
A/B partition system is caused whole problem so this is only the method to flash custom rom...
As I said this has been the whole problem. I boot back to bootloader where It says Download Mode. When I try to flash the recovery image this is what I get.
C:\Users\rpwor\NexusTools>fastboot flash recovery lineage-18.1-20210831-recovery-PL2.img
< waiting for any device >
And there it sits never to move again. Now do you understand what i'm dealing with?
The problem might be the recovery image you want to flash as it's for a Nokia 6.1 (PL2) not Nokia 6.1 Plus (DRG).
If your device is actually a Nokia 6.1, then you could try the `Install Recovery Ramdisk` option in TWRP, under `Advanced`.
mech1164 said:
As I said this has been the whole problem. I boot back to bootloader where It says Download Mode. When I try to flash the recovery image this is what I get.
C:\Users\rpwor\NexusTools>fastboot flash recovery lineage-18.1-20210831-recovery-PL2.img
< waiting for any device >
And there it sits never to move again. Now do you understand what i'm dealing with?
Click to expand...
Click to collapse
How is your brick? Did you find a way to revive it?