Related
I want to install cwm recovery in my canvas a1 for backup my current rom android 4.4.4.
I m going to install lollipop 5.1 I heard about some bug in lollipop so for my safety i want a backup.
I used minimal adb and fastboot for installing cwm.
But when i type the command "fastboot flash recovery recovery.img"
End hit enter
Then it show a error.
"Failed (remote download for partition 'recovery' is not allowed'
What should i do now?
http://forum.xda-developers.com/cro...oolbox-android-one-toolkit-one-click-t3030165
Go to this thread and follow the simple instructions...dnt go through such command prompts..when an easy way is available hit thanks if i helped
MaxySpark said:
I want to install cwm recovery in my canvas a1 for backup my current rom android 4.4.4.
I m going to install lollipop 5.1 I heard about some bug in lollipop so for my safety i want a backup.
I used minimal adb and fastboot for installing cwm.
But when i type the command "fastboot flash recovery recovery.img"
End hit enter
Then it show a error.
"Failed (remote download for partition 'recovery' is not allowed'
What should i do now?
Click to expand...
Click to collapse
Before flashing CWM recovery, you have to unlock the boot loader, using the command:
Code:
fastboot oem unlock
Then press Volume Up in phone to confirm.
Now you can flash.
Note: Unlocking bootloader formats the User data (/data partition), such as apps and other settings. Take a backup using Titanium Backup Tools, then proceed
Your recovery partition is locked.
1. Make yourself a developer (go to Settings -> About Phone -> Tap on Build until developer
2. In Developer options turn on Enable OEM unlock
3. Flash the new recovery, don forget to "fastboot oem unlock"
4. Important: don't allow phone to complete a normal reboot after flash. When rebooting, press Vol Up + Vol Down + Power to enter CWM recovery directly. Otherwise the stock recovery will replace CWM again.
When I type the command "fastboot oem unlock" and press enter, my phone displays a long-ish disclaimer text about the dangers of unlocking the bootloader, ending with the instruction to use Volume Up key to confirm ("YES, unlock...") or the Volume Down key to cancel ("NO, don't unlock..."). Pressing Volume Down works as expected: the line "returning to fastboot in 3secs" is displayed, followed by a return to fastboot. But pressing Volume UP seems to have NO EFFECT at all!! NOthing highlighted, no change in the screen, pressing power afterward does nothing. It is not a hardware problem of the Volume Up button either -- Volume Up/Down keys work in normal apps and in recovery mode just fine.
I was hoping that perhaps it just silently succeeded, but when i next try to flash the CWM recovery img, I still get 'sending recovery' OKAY but 'writing recovery' FAILED??
what do I do to get the volume UP to work while the phone in this mode??
BTW the phone is a Rook 4G phone from EE here in the UK. This is apparently the same as a ZTE Blade 3 A410 phone with carrier branding.
THANKS in advance for any help!
sbpetrack said:
When I type the command "fastboot oem unlock" and press enter, my phone displays a long-ish disclaimer text about the dangers of unlocking the bootloader, ending with the instruction to use Volume Up key to confirm ("YES, unlock...") or the Volume Down key to cancel ("NO, don't unlock..."). Pressing Volume Down works as expected: the line "returning to fastboot in 3secs" is displayed, followed by a return to fastboot. But pressing Volume UP seems to have NO EFFECT at all!! NOthing highlighted, no change in the screen, pressing power afterward does nothing. It is not a hardware problem of the Volume Up button either -- Volume Up/Down keys work in normal apps and in recovery mode just fine.
I was hoping that perhaps it just silently succeeded, but when i next try to flash the CWM recovery img, I still get 'sending recovery' OKAY but 'writing recovery' FAILED??
what do I do to get the volume UP to work while the phone in this mode??
BTW the phone is a Rook 4G phone from EE here in the UK. This is apparently the same as a ZTE Blade 3 A410 phone with carrier branding.
THANKS in advance for any help!
Click to expand...
Click to collapse
Hi, I have exactly the same situation!
No effect on Volume UP. I can't understand...
marc2800 said:
Hi, I have exactly the same situation!
No effect on Volume UP. I can't understand...
Click to expand...
Click to collapse
Absolutely identical experience here with the Alcatel One Touch Pop 3 - 5015x. I was following this tutorial http://forum.xda-developers.com/and...lcatel-one-touch-pop-s3-t3060092/post65430049, had a problem with the OEM, solved it by finding the top post on THIS thread and now I have the exact same issue as you two gentlemen. Any help would be appreciated, cus the phone seems bricked as it is. It's stuck in boot loop and receiving no input.
Thi is NOT the exact same issue as we have: you are stuck in a boot-loop; we have a version of fastboot which seems to have disabled the volumeUp button, thereby making it impossible to confirm our request to unlock the bootloader. e can only press VolumeDown (which cancels our request to unlock the bootloader).
i posted at http://forum.xda-developers.com/showpost.php?p=65462453&postcount=48 a suggestion for how to proceed in your case: just use SP Flash tools to reinstall a stock recovery image, and then use that recovery to install a complete stock ROM.
,BTW, Sir, when you say:
> ...with the Alcatel One Touch Pop 3 - 5015x. I ... had a problem with the OEM, solved it by finding the top post on THIS thread
note that the solution given in the top post of this thread is designed for Android One devices, and your Alcatel One Touch does NOT appear in the list of supported devices for that "fix." can't say it's entirely surprising that you would get into a bootloader problem if you apply top your phone a bootloader unlock solution for some random other platform!! LUck would not likely be with you when doing that.
zeta274 said:
Absolutely identical experience here with the Alcatel One Touch Pop 3 - 5015x. I was following this tutorial http://forum.xda-developers.com/and...lcatel-one-touch-pop-s3-t3060092/post65430049, had a problem with the OEM, solved it by finding the top post on THIS thread and now I have the exact same issue as you two gentlemen. Any help would be appreciated, cus the phone seems bricked as it is. It's stuck in boot loop and receiving no input.
Click to expand...
Click to collapse
I can't understand why volume down is working fine and not volume UP...
zeta274 said:
Absolutely identical experience here with the Alcatel One Touch Pop 3 - 5015x. I was following this tutorial http://forum.xda-developers.com/and...lcatel-one-touch-pop-s3-t3060092/post65430049, had a problem with the OEM, solved it by finding the top post on THIS thread and now I have the exact same issue as you two gentlemen. Any help would be appreciated, cus the phone seems bricked as it is. It's stuck in boot loop and receiving no input.
Click to expand...
Click to collapse
Go in bootloader mode, connect your phone to your computer and tell me what do you get if you tape in your console "fastboot devices"
I want to know the number before fastboot.. mine is strange and maybe not the original
MaxySpark said:
I want to install cwm recovery in my canvas a1 for backup my current rom android 4.4.4.
I m going to install lollipop 5.1 I heard about some bug in lollipop so for my safety i want a backup.
I used minimal adb and fastboot for installing cwm.
But when i type the command "fastboot flash recovery recovery.img"
End hit enter
Then it show a error.
"Failed (remote download for partition 'recovery' is not allowed'
What should i do now?
Click to expand...
Click to collapse
That is also my problem with my phone!
---------- Post added at 05:56 AM ---------- Previous post was at 05:54 AM ----------
GokulNC said:
Before flashing CWM recovery, you have to unlock the boot loader, using the command:
Code:
fastboot oem unlock
Then press Volume Up in phone to confirm.
Now you can flash.
Note: Unlocking bootloader formats the User data (/data partition), such as apps and other settings. Take a backup using Titanium Backup Tools, then proceed
Click to expand...
Click to collapse
Hi, I had done that fastboot oem unlock command and pressed Volume Up but nothing happened and my bootloader still locked could you help? Thanks, my phone is Starmobile UP HD MTK6582 :laugh:
GokulNC said:
Before flashing CWM recovery, you have to unlock the boot loader, using the command:
Code:
fastboot oem unlock
Then press Volume Up in phone to confirm.
Now you can flash.
Note: Unlocking bootloader formats the User data (/data partition), such as apps and other settings. Take a backup using Titanium Backup Tools, then proceed
Click to expand...
Click to collapse
really thanks:angel:
I can't
I have an error installing a ROM, partition x not allowed.
I can't go in recovery mode + I can't open my phone to enable usb debugging.
I don't have root & and I don't have my OEM unlocked.
How can I install my ROM for Asus Zenfone GO ZC500TG? :'( :'(
Anyone, please?!!
ADB devices allowed?
I have the same problem, but i just resolve it now. First, i've connected my phone in normal mode, then i opened cmd and wrote: adb devices, and a popup displayed in my phone to allow adb debug. I allowed and reboot to bootloader and follow all steps to unlock bootloader.
I also have problems, my phone is a polaroid turbo c4 plus and i cand get through the setup, so i can't install cwm and i am searching for methods to recover it, it's pretty hard since theres nothing online about it
Hello there,
we have here a Swift that is stuck on a starting screen since an attempt to downgrade from Cyanogenos 13.1 to Cyanogenmod 12.1. Bootloader ist unlocked and to my knowledge only the recovery was flashed via fastboot.
As soon as the USB cable is connected, the screen goes on with "Wileyfox(with logo) powered by android" and remains there.
Luckily fastboot works, but I can't get into recovery. Neither by selecting "reboot into recovery" from fastboot nor by "Vol-" + "Power".
I tried to reflash Cyanogenos 13 via fastboot as it was suggested in several threads (i.e. unzip and flash the different files step by step). Fastboot always stated success, but no luck... Still the same starting screen.
I even tried flashing TWRP recovery, no change either.
Is there something else I can try?
Thank you all
SOLVED: I was persistent: one other threads regarding a lenovo phone suggested to hold down Power and VolDn continuously for several minutes. After about a minute or so and multiple (min. 15x) power off/ons to the "powered by android" screen, I finally got into TWRP! After a format /data I was able to flash the desired CM.
I hope this helps others with similar problems
Erdbeerfrosch said:
Hello there,
we have here a Swift that is stuck on a starting screen since an attempt to downgrade from Cyanogenos 13.1 to Cyanogenmod 12.1. Bootloader ist unlocked and to my knowledge only the recovery was flashed via fastboot.
As soon as the USB cable is connected, the screen goes on with "Wileyfox(with logo) powered by android" and remains there.
Luckily fastboot works, but I can't get into recovery. Neither by selecting "reboot into recovery" from fastboot nor by "Vol-" + "Power".
I tried to reflash Cyanogenos 13 via fastboot as it was suggested in several threads (i.e. unzip and flash the different files step by step). Fastboot always stated success, but no luck... Still the same starting screen.
I even tried flashing TWRP recovery, no change either.
Is there something else I can try?
Thank you all
SOLVED: I was persistent: one other threads regarding a lenovo phone suggested to hold down Power and VolDn continuously for several minutes. After about a minute or so and multiple (min. 15x) power off/ons to the "powered by android" screen, I finally got into TWRP! After a format /data I was able to flash the desired CM.
I hope this helps others with similar problems
Click to expand...
Click to collapse
I've got the same problem. How id you solve yours?
I did hold the VolumeDown+Power buttons for 5 minutes and I did not get into recovery at all (this was with latest TWRP version 3.1.1-0)
Then I thought it could be the TWRP version, and I tried 3.0.3-0 and finally 3.0.0-0.
After flashing 3.0.0-0 I typed "fastboot reboot" and immediately after pressed VolumeDown+Power on the phone and ... finally was in recovery mode, where I could install microG's lineageos version.
cweiske said:
I did hold the VolumeDown+Power buttons for 5 minutes and I did not get into recovery at all (this was with latest TWRP version 3.1.1-0)
Then I thought it could be the TWRP version, and I tried 3.0.3-0 and finally 3.0.0-0.
After flashing 3.0.0-0 I typed "fastboot reboot" and immediately after pressed VolumeDown+Power on the phone and ... finally was in recovery mode, where I could install microG's lineageos version.
Click to expand...
Click to collapse
hi could you post exactly what you did line by line inc code plz i have twrp 3 img just need to get it over i must be typing something wrong.
thanks
im having a problem, my phone wont go out of fast boot mode, tried everything
Any suggestions??
Here is the correct fix, at least it worked for me,
https://forum.xda-developers.com/showpost.php?p=66158015
Unlock bootloader
Download and unzip this archive or this archive (if you model is BTV-W09)
In command prompt:
Code:
adb reboot-bootloader
fastboot flash recovery twrp.img
fastboot reboot
Update 21/12 fot US version change twrp.img
This twrp works correctly
Rename it's to twrp.img and replace in unzipped folder
Or use this code
Code:
adb reboot-bootloader
fastboot flash recovery twrp-m3-us-greatslon.img
fastboot reboot
All new version (And for EMUI5 too) this a lot of partitions for backup/restore and images can be download here
Where did you get the TWRP recovey from?
It's not on the TWRP.me website?
Flavio said:
Where did you get the TWRP recovey from?
It's not on the TWRP.me website?
Click to expand...
Click to collapse
Read subj )
It's my work.
Thx a lot.
I managed to root my M3 now.
Thanks fro your work but...
...will be the "own created" twrp-image really work on the new M3 due to that this is not official available on the twrp-homepage?!
Have I install the SuperUser-App from Chainfire too or will be this included?
Scrabbledo said:
...will be the "own created" twrp-image really work on the new M3 due to that this is not official available on the twrp-homepage?!
Have I install the SuperUser-App from Chainfire too or will be this included?
Click to expand...
Click to collapse
It is working on my M3 LTE without issues.
I tried flashing Chainfire's SuperUser with TWRP but that didn't work (bootloop).
I used the SRK Tool to get root.
remot command not allowed
Dear Greatslon!
unlocked the bootloader wir DC Unlocking client ... done.
I'm not able to write twrp to my device ..
download O.K.
remote command not allowed ...
failed
---->
DC unlocking did not realy unlock the device
done with unlock code from huawei page it work fine
---->
any idea?
kind regards in advance,
ein777er
Have you enabled USB debugging?
Flavio said:
It is working on my M3 LTE without issues.
I tried flashing Chainfire's SuperUser with TWRP but that didn't work (bootloop).
I used the SRK Tool to get root.
Click to expand...
Click to collapse
Hi @Flavio,
With the unlock-code I could unlock the bootloader.
On every start of the tablet I get now a warning that my device is untrusted, after some seconds it booted up into the normal "Desktop" view.
After I've activated again the USB-Debugging option I send it via "adb reboot bootloader" into the fastboot-mode and now the FRP-status shows "unlocked".
So, I've flashed the downloaded "twrp.img" to the recovery partition and reboot the tablet.
There is no difference to see, I get the untrust-note and then it is booting into the desktop view.
BUT how can I get into the twrp-mode? Normally when I boot up with "Volume-up"+"Power" but here it started into the Huawei EMUI Recovery console, not the TWRP surface. So I've flashed the twrp.img again but no change. And when I boot directly into the recovery "adb reboot recovery" I get the untrust-hint and the note that the system is booting now, but nothing is happen. Whit a cold-reset it shows the same screen. First when I go into the Huawei Recovery mode and press only "Reboot" it is booting up again as normal as before into the desktop mode.
My 2nd question is: you say you have used the SRK Tool to root your device. But under the link I can find a toot for the Huawei Mate 8 ? You mean I can download and use this tool for the Huawei Mediapad M3 too? ...after I could install TWRP?
Thanks for you help.
Greets,
Scrab
Flavio said:
Have you enabled USB debugging?
Click to expand...
Click to collapse
Dear Flavio!
thx.
with the unlock code from the huawei page it works fine
kind regards,
ein777er
---------- Post added at 06:49 AM ---------- Previous post was at 06:45 AM ----------
Dear scrab!
->My 2nd question is: you say you have used the SRK Tool to root your device. But under the link I can find a toot for the Huawei Mate 8 ? You mean I can download and use this tool for the Huawei Mediapad M3 too? ...after I could install TWRP?
The tool for huawei devices version 2.0 works fine (pont 4 (root), use another huawei device for routing)
kind regards,
ein777er
Thanks ein777er for this hint.
But before I can root my device I have to install TWRP. Here is currently my stop-point due to that fastboot tells that the twrp.img was installed without issues but when I boot into the recovery the tablet stops the boot on the "untrust"-screen and first when I go into the eRecovery-mode and reboot the tablet I will be back on the working surface.
For the root process the SRK tool want as well to boot into twrp first and I end up in the same stop-screen.
Maybe this is caused from the installed version of EMUI?
I made no updates/upgrades and have only unpack it from the box. So I have EMUI 4.1 as system.
Beside this is there any known fix yet to "hide" the untrust screen during the boot?
Greets,
Scrab
Dear Scrab!
>But before I can root my device I have to install TWRP. Here is currently my stop-point due to that fastboot tells that the twrp.img was installed without issues but when I boot into the recovery the tablet stops the boot on the "untrust"-screen and first when I go into the >eRecovery-mode and reboot the tablet I will be back on the working surface.
try this :
https://play.google.com/store/apps/details?id=gt.recovery.reboot
or
recoverymode : press vol+ and power
>Maybe this is caused from the installed version of EMUI?
>I made no updates/upgrades and have only unpack it from the box. So I have EMUI 4.1 as system.
i use it also out of the box
kind regards
Scrabbledo said:
Hi @Flavio,
BUT how can I get into the twrp-mode? Normally when I boot up with "Volume-up"+"Power" but here it started into the Huawei EMUI Recovery console, not the TWRP surface. So I've flashed the twrp.img again but no change. And when I boot directly into the recovery "adb reboot recovery" I get the untrust-hint and the note that the system is booting now, but nothing is happen. Whit a cold-reset it shows the same screen. First when I go into the Huawei Recovery mode and press only "Reboot" it is booting up again as normal as before into the desktop mode.
Click to expand...
Click to collapse
I need to turn off the tablet and then turn it on with Volume Up and Power on and hold it till TWRP starts.
//EDIT
OK last time I installed the Button combination changed. Try Vol+ and Vol- and Power. Had whole day headache till I recognized this
greatslon said:
Unlock bootloader
Download and unzip this archive
In command prompt:
Code:
adb reboot-bootloader
fastboot flash recovery twrp.img
fastboot reboot
Click to expand...
Click to collapse
I get an error when I try to make a backup: createTarFork() process ended with ERROR: 255.
Everything else I tested works great.
sebbo2015 said:
I get an error when I try to make a backup: createTarFork() process ended with ERROR: 255..
Click to expand...
Click to collapse
try to make backup to internal storage
---------- Post added at 03:52 PM ---------- Previous post was at 03:45 PM ----------
If your M3 USB plug (charger or computer) you can't go TWRP, only EMUI recovery.
please use Vol+ and Power when not connected USB for custom recovery
So I have my bootloader unlocked via the official huawei website method, and now I'm trying to flash twrp. I followed the instructions and attempted to flash twrp. See the attached screenshot of my command window. It seems like it finished successfully (only took 0.7 seconds) but I saw nothing happen on the tablet itself. Just the same white screen with the android logo that says FASTBOOT&RESCUE MODE. No script or anything changed. So far I've been unable to boot into TWRP.
I have tried holding down the VOL UP + POWER combination and it takes me to the black "Your device has been unlocked and can't be trusted." screen with the text "Your device is booting now..." at the bottom and the tablet will just stay frozen there. Then if I hold the power button for a few seconds it will take me to a similar black screen but with three options. If I do option (1) which is to hold the VOL UP button for 3 seconds it will take me to the EMUI recovery not TWRP.
Hopefully someone can help out here.
I'm stuck on the same step as you. Greatslons version of twrp doesn't seem to work on the US versions. Just freezes upon boot. Anyone have any idea why that would be?
Fyi, my working twrp flash to my non-US M3 was also very fast. So fast that I thought it didn't really do anything. But it worked.
Did you guys do the OEM unlock step? I wonder if there is some kind of region locking between the hardware and the bootloader.
I did the OEM unlock step. I also tried flashing it to recovery and recovery2, both of which didn't work. Sucks cause we can't root without twrp, yet we have our bootloaders unlocked.
elsamuraiguapo said:
So I have my bootloader unlocked via the official huawei website method, and now I'm trying to flash twrp. I followed the instructions and attempted to flash twrp. See the attached screenshot of my command window. It seems like it finished successfully (only took 0.7 seconds) but I saw nothing happen on the tablet itself. Just the same white screen with the android logo that says FASTBOOT&RESCUE MODE. No script or anything changed. So far I've been unable to boot into TWRP.
I have tried holding down the VOL UP + POWER combination and it takes me to the black "Your device has been unlocked and can't be trusted." screen with the text "Your device is booting now..." at the bottom and the tablet will just stay frozen there. Then if I hold the power button for a few seconds it will take me to a similar black screen but with three options. If I do option (1) which is to hold the VOL UP button for 3 seconds it will take me to the EMUI recovery not TWRP.
Hopefully someone can help out here.
Click to expand...
Click to collapse
Exact same issue here I got the unlock code and unlocked the bootloader, no issues there. Next I flashed twrp and got the exact same result as you. There doesn't seem to be any way to get in to twrp at all... I even tried "adb reboot recovery" but it just goes in to the "Your device has been unlocked.. " screen and then says "Your device is booting now...", then gets hung on that screen. How do we get past this? Thanks in advance for any help.
I bought this device thinking I could root it
I'm in the USA and I bought the device from Amazon: https://www.amazon.com/gp/product/B01LB08BH6/
For those that, like me, could not get driver recognition on the latest Win 10 x64 no matter what you tried. And ,yes, using every tutorial I could find on this and two "other Forums". Odin failed to see my device (still can't) Cydia impactor allows rebooting into fastboot and D/L but doesn't connect in either alt. mode. Yes, drivers all removed and replaced in varying states (usbdeview, etc.).
But ADB/Fastboot works!
Make sure you have your adb/fastboot drivers installed universally (Check this Fabulous Forum)
Download device-specific TWRP - I used this one for the 4gb version - https://www.dropbox.com/s/b7u3k1mgpppxlyx/recovery.img?dl=0
L.Shift-R. click in the folder you downloaded to (Open Command Window Here) - "adb devices" (to make sure device registers) then - "adb reboot bootloader" gets you into fastboot. - "fastoot boot {your-recovery-name}.img"
I got a fully functional TOUCH CAPABLE TWRP. Which I proceeded to load this - https://www.dropbox.com/s/j1owqv7mjkdpo75/UPDATE-SuperSU-v2.46.zip?dl=0 - and, VOILA! ROOT!!
I had similar issues with my laptop and drivers. Used a friend laptop in the end to "see" the phone and install twrp.
Sent from my S7 using Tapatalk
When I try to boot the recovery.img with fastboot it says that my OEM is locked. I check OEM unlock in developer options, then I do: adb reboot bootloader, then fastboot oem unlock. A warning appears saying to press VOLUME UP button to continue, voiding the warranty or VOLUME DOWN to go back. I try to press VOLUME UP and nothing happens... how did you do it?
vaskovass said:
When I try to boot the recovery.img with fastboot it says that my OEM is locked. I check OEM unlock in developer options, then I do: adb reboot bootloader, then fastboot oem unlock. A warning appears saying to press VOLUME UP button to continue, voiding the warranty or VOLUME DOWN to go back. I try to press VOLUME UP and nothing happens... how did you do it?
Click to expand...
Click to collapse
Hi there, I have the same issue. No success
I found a way, instead of volume up, use the home button this worked for me.. however after I unlocked the OEM and flashed TWRP the phone didn't want to boot anymore. It was stuck on Elephone logo with warning: "Orange State: The phone has been unlocked and can't be trusted. Your device will boot in 5s", however it didn't boot and stayed like that for almost an hour. Had to flash back the stock firmware to boot. Tried 1 more time the procedure to root but again the same. Maybe I do something wrong?
stock fw flash back
Hi, please can you help me with how you flashed back the stock firmware?
I get an error message with twrp : invalid zip file format.
Thank you in advance!
dnsgtr said:
Hi, please can you help me with how you flashed back the stock firmware?
I get an error message with twrp : invalid zip file format.
Thank you in advance!
Click to expand...
Click to collapse
I read somewhere the is a zip inside the update.zip & is that one that is flash able with twrp.
Have a look
During the main time I managed to flash the 0218 stock rom.
I still got the orange message but the phone finally boot. Then I just called the twrp recovery img via atb. I did nothing only touch the reboot in the twrp screen and since then "Orange status...." again.
May be the twrp recovery img is not the right one...
Bad command "fastoot boot {your-recovery-name}.img"
after OEM alow (informacion phone/compilacion number touch fast 9 times/access/alow oem)
fastboot oem unlock
"fastboot boot {your-recovery-name}.img" for me is fastboot boot recovery.img and all OK
bat still not working (phone not thrust unlocked bootloader cleaning data in 5..4..3..2..1.. and rebot)
I unlocked my Nexus 7, though after a TWRP install when selecting recovery mode it stays stuck on the Google logo as if there’s no TWRP; though the command prompt said install was successful.
Any help?
mendelmusic said:
I unlocked my Nexus 7, though after a TWRP install when selecting recovery mode it stays stuck on the Google logo as if there’s no TWRP; though the command prompt said install was successful. Any help?
Click to expand...
Click to collapse
It may be incorrect sequence of steps, note:
"many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
Try this:
Restock
run Android once
flash TWRP
immediately and directly boot TWRP
Will try that!