Hello Everyone. I need some help with restoring my shield because I seem to have soft-bricked it. Last week I rooted and installed a custom recovery file and all was well but this past weekend I was messing around with it trying to install the custom rom for full android and I think I accidentally deleted the boot file and the recovery file because all I get is the android on his back with the red triangle. Also, when I try to connect to the unit using fastboot nothing is found but I DO get a hit if I put the unit in stock recovery, it gives me the option to click apply update from adb.
From what I have been reading it sounds like I should be able to sideload the recovery and/or the stock firmware. Can anyone confirm or provide me with instructions on how to get this unit back up and running.
Any help is greatly appreciated
Wow I expected people to jump on this one. I guess I'll just keep messing around with it
Hy, here is the firmware and the instructions:
FW:
https://developer.nvidia.com/gameworksdownload (here you will have to scroll down to your console version PRO/non-PRO
Instructions:
http://developer.download.nvidia.co...TV/Upgrade-2.1/HowTo-Flash-Recovery-Image.txt
Thanks but I already looked at those and it only provides details for using fastboot which I am unable to use.. device will only show up when I use the regular recovery method and the only option is apply update from adb.
So, if you perform a adb reboot bootloader command from adb it doesn't reboot into the bootloader?
hpric said:
Thanks but I already looked at those and it only provides details for using fastboot which I am unable to use.. device will only show up when I use the regular recovery method and the only option is apply update from adb.
Click to expand...
Click to collapse
And you have tried restoring boot from stock recovery download ? with 'fastboot flash boot boot.img' ?
gffmac said:
And you have tried restoring boot from stock recovery download ? with 'fastboot flash boot boot.img' ?
Click to expand...
Click to collapse
He can only do this if he can adb into the bootloader, hence my question. The implication appears to be that he can't if I'm reading his comments correctly.
Beefheart said:
So, if you perform a adb reboot bootloader command from adb it doesn't reboot into the bootloader?
Click to expand...
Click to collapse
Correct. I can only use sideload at this time. Yesterday I was messing around with it a little more trying to sideload the recovery but I kept getting a message saying "The footer was incorrect" and it would cancel the install. I tried different files to make sure I wasn't dealing with a corrupted zip file but they all gave the same message.
I'm trying to figure out how to sideload the recovery
Beefheart said:
He can only do this if he can adb into the bootloader, hence my question. The implication appears to be that he can't if I'm reading his comments correctly.
Click to expand...
Click to collapse
Correct
Hello, I am facing the exact issue. Please let me know if you figured a way to debrick?
All I can do is ADB sideload and E:footer error keeps coming up.
Help is appricated,
Thanks
Related
My Nexus 7 (2012-wifi) was running 4.4 rooted with CWM. I flashed the 4.4 update zip from recovery which failed late in the flash.
Did it fail because I forgot to unroot before I flashed the update?
At any rate even though the flash failed I also flashed SuperSu in case the update was good enough.
It wasn't, when I boot I get rotating/expanding/contracting colored balls forever.
Is there some way for me to recover from this without wiping the device? I was over confident and didn't do an external backup.
I don't know how to help you fix the problemm but it definitely didn't fail because you were rooted. I was rooted too and all it did was that I lost root (had to root again)
You can try wiping dalvik cache from recovery?
I got into the exact same problem as you.
I fixed it by following the steps here:
http://forum.xda-developers.com/showthread.php?t=2376978
It basically flashes back your 4.3 firmware. Just one thing to note though, DO NOT flash the userdata, YOU MUST SKIP THIS STEP unless you want to lose your files.
Tehloy said:
I got into the exact same problem as you.
I fixed it by following the steps here:
http://forum.xda-developers.com/showthread.php?t=2376978
It basically flashes back your 4.3 firmware. Just one thing to note though, DO NOT flash the userdata, YOU MUST SKIP THIS STEP unless you want to lose your files.
Click to expand...
Click to collapse
I had a look at this. One thing I'm wondering is, doI really need to update the boot loader as in the instructions, or can I go directly to the fastboot flash of the system and boot img?
kmandel said:
I had a look at this. One thing I'm wondering is, doI really need to update the boot loader as in the instructions, or can I go directly to the fastboot flash of the system and boot img?
Click to expand...
Click to collapse
I think you can skip flashing the bootloader. Just jump straight in to flashing the rest.
I got ready to try fastboot flash of the system img. I booted into bootloader mode and adb doesn't see the device. I then went into CWM and it does see the device from there. "adb devices" and "adb shell" work from recovery. However, "fastboot flash" just waits forever for device.
Suggestions?
kmandel said:
I got ready to try fastboot flash of the system img. I booted into bootloader mode and adb doesn't see the device. I then went into CWM and it does see the device from there. "adb devices" and "adb shell" work from recovery. However, "fastboot flash" just waits forever for device.
Suggestions?
Click to expand...
Click to collapse
Never mind, fastboot did work from the bootloader, I was just surprised that adb devices didn't see it. All is good, I'm back on 4.3 with my files intact. I'll try the 4.4 update again tonight.
Well,
basically subject says all.
I tried to install zulu99 Full android rom 2.1.
basically 'fastboot flash system system.img worked' but 'fastboot -w' failed ('no space left' error).
So I rebooted hoping to reflash a nandroid backup but now the box keeps on rebooting into twrp trying to wipe cache and data but failing. after a while it stops and black screen appears.
I attach the screen it presents when reboots.
Please tell me I didn't trash 220 euros.
Thanks.
puppinoo said:
Well,
basically subject says all.
I tried to install zulu99 Full android rom 2.1.
basically 'fastboot flash system system.img worked' but 'fastboot -w' failed ('no space left' error).
So I rebooted hoping to reflash a nandroid backup but now the box keeps on rebooting into twrp trying to wipe cache and data but failing. after a while it stops and black screen appears.
I attach the screen it presents when reboots.
Please tell me I didn't trash 220 euros.
Thanks.
Click to expand...
Click to collapse
Theres a hardware method to boot into the bootloader, this i think you can test, just to see if you can at least get into bootloader.....nothing more
Details in the official nvidia link
http://nv-tegra.nvidia.com/gitweb/?...ob_plain;f=README_SHIELD;hb=rel-22r18-partner
There's a thread here on the "questions" thread with users reporting that the timing of the hardware method can be a pain in the you know where.............might be worth looking into that thread for their experiences in booting the bootloader using the hardware method
Disclaimer:If your brave enough to risk a brick, read on
I suspect this might be the 2.1 stock/twrp issue........current twrp, or current stock dont play nice
Its a good sign that SOMETHINGS loading, rather then NOTHING booting, but dont know if theirs a solution
My analysis of the situation, of what little i know, the -w (wipe) command was expecting a stock recovery but instead got twrp, which is why your in this situation.........maybe, i stress maybe, if you could reflash stock again, you might be able to boot into android stock again and try full android again, leaving out twrp, until a twrp fix is found
Edit
Saying that, if the bootloader is, as i suspect, now using twrp to flash things, then you might be boned....... im no expert on bootloaders, stock "recoveries" and how they work, so i might be wrong on that
Reports around here say that 1.3 stock firmware is the recommended back to stock firmware, apparently, flashing any other firmware versions, bring their own issues.............
From 1.3 stock, use nvidias official OTA to upgrade from 1.3 stock, to 2.1 stock, then try 2.1 full android again...........note, i dont think you can skip firmwares i.e. you have to upgrade to 1.4, then to 2.0, then to 2.1, alot of downloading.......the OTA does'nt give you any other choice
Before doing anything that ive suggested, wait till someone with more experience to come along........i dont want to be responsible for you fully bricking your shield..........just wanna give you an idea of what i think has happened
If worse comes to worse, if you have warrenty, get a replacement
Gd luck........remember, this is an analysis of your predicament of what i THINK might of happened, and what steps, i likely might of entertained.......after looking into it more thouroughly, knowing that i could get a replacement if it went downhill.........so your mileage might vary
Edits
Crappy grammer, further musings, clarifications
Thanks.[/QUOTE]
puppinoo said:
Well,
basically subject says all.
I tried to install zulu99 Full android rom 2.1.
basically 'fastboot flash system system.img worked' but 'fastboot -w' failed ('no space left' error).
So I rebooted hoping to reflash a nandroid backup but now the box keeps on rebooting into twrp trying to wipe cache and data but failing. after a while it stops and black screen appears.
I attach the screen it presents when reboots.
Please tell me I didn't trash 220 euros.
Thanks.
Click to expand...
Click to collapse
I had something similar about... shield goes booting in recovery and trying delete some cache and keeps repeat and repeat
Hardware boot in fastboot / bootloader mode
Accessing Bootloader via Hardware
Unplug power from the Shield Android TV. *
Wait a few seconds.
Hold down the power button.
Plug in power
Count to three
Release the power button
You should see the bootloader screen.
If you hold it down too long or not long enough, it simply doesn’t work.
Restore Shield Android TV to Stock
P.s. Personally me I followed this instructions and kind of magically got it in bootloader mode. First done by instruction and then just gave up and pressed randomly and fastboot screen appear. Thanks God I had to done only once, if I would do again I wouldn't had patients
Good luck with this, hope you will get sorted
Here will be link about where I got instructions about hardware boot
http://nvidiashieldzone.com/index.php/shield-android-tv/root-shield-android-tv/
Sent from my Nokia 3310 using free xda app
Thanks a lot fro your help.
I was able to put the box in fastboot mode.
Since I'm not that expert can you tell me where and which rom I have to download (I have a french 16gb version of the box).
Then I'd need to know exactly what commands to performs (even a link to a tutorial is fine).
I really appreciate your help. It seems I can (hopefully) save the box.
EDIT: The fastboot command gave me a (not enough space) when I bricked the box. Is there a risk it could happen again while flashing stock? No idea how much space I have left on the box really.
EDIT2: I found this page: https://developer.nvidia.com/shield-open-source
and I'm downloading this rom called nv-recovery-image-shield-atv-upgrade2_1.zip
and Intend to follow these instructions: http://developer.download.nvidia.co...TV/Upgrade-2.1/HowTo-Flash-Recovery-Image.txt
Can anyone please confirm I'm doing right?
EDIT with joy : I followed all the steps using that rom and it seems everything worked. I reconfiguring the box now. Thanks for help.
basically the procedure I intend to follow is this part (please confirm it's ok):
To flash this recovery image to your SHIELD, run the following commands from
the directory where you extracted the recovery image package. If this is the
first time you have done this procedure, you must unlock the bootloader. Get
DTB file name to use for flashing for your product(see below):
P.s. maybe Since past fastboot commands failed and I only flashed system from zulu99 I could skip the 'fastboot flash boot boot.img' command so if it fails again I still can attempt the fastboot process again?
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb <DTB file name>
puppinoo said:
Thanks a lot fro your help.
I was able to put the box in fastboot mode.
Since I'm not that expert can you tell me where and which rom I have to download (I have a french 16gb version of the box).
Then I'd need to know exactly what commands to performs (even a link to a tutorial is fine).
I really appreciate your help. It seems I can (hopefully) save the box.
EDIT: The fastboot command gave me a (not enough space) when I bricked the box. Is there a risk it could happen again while flashing stock? No idea how much space I have left on the box really.
EDIT2: I found this page: https://developer.nvidia.com/shield-open-source
and I'm downloading this rom called nv-recovery-image-shield-atv-upgrade2_1.zip
and Intend to follow these instructions: http://developer.download.nvidia.co...TV/Upgrade-2.1/HowTo-Flash-Recovery-Image.txt
Can anyone please confirm I'm doing right?
Click to expand...
Click to collapse
You are on the right way with those links
P.s. You can do manual one by one entering or paste and copy those commands or (I'm doing) drag and drop file "flash-all.bat" on cmd previous opened there where you have abd/fastboot etc files and extracted RIGHT FIRMWARE (like shift and right click mouse "open command prompt here"
And after this all sit down and relax
Anyway you are on the right way.
P.s. Hope you download adb fastboot drivers somewhere from Internet !?!
Sent from my Nokia 3310 using free xda app
I have the Chinese version of axon 7 and under development options I can click on OEM unlock then it asks for a pin number. How do I get that pin number?
Have you contacted zte customer service?
Please let me know how this turns out
I've been around these forums multiple times now and the ways that should work don't seem to work for me :/ Can't find a confirmed unlock of the Chinese version and am stuck on B13 while I wany Cyanogen.
If you go and sign up for ztes website and then go to the developers lounge there is a lot of talk about bootloader unlock. The way I read it you could have signed up to receive a pin number to unlock bootloader but zte has put that on hold? But are suppose to start it back up?
you can flash unlock bootloader in port 9008, I unlocked successfully by this way
@jiabing520a could you explain how?
after booting into recovery my device isnt visible in the device list from adb.
enkrs said:
@jiabing520a could you explain how?
after booting into recovery my device isnt visible in the device list from adb.
Click to expand...
Click to collapse
Did you flash twrp ? Official recovery does not support adb.
If you have already flashed twrp, then open computer manager- device manager, you will see your phone doesn‘t work correctly (triangle) , right click on the triangle, and click update driver, then computer will fix this proble automatically.
Can not even get to flashing the TWRP, so stock recovery.
I want to backup the recovery.img in case i brick the device after doing
adb reboot recovery the device cant be found any more in the adb device list so nothing from that.
I tried to sideload it using the adb sideload but the same
it`s saying waiting for device and stays there even when i`m trying to send a file to the device.
Ok little update.
tried to downgrade but getting the error footer not correct and unable to verify.
Normaly saying you can disable this using the TWRP system as i cannot even get the bootloader to unlock.
So i cant get TWRP installed on the device.
If anyone knows how to downgrade the b13 to the b10 so we can use the tools provided in other posts
Please help how further .
enkrs said:
Can not even get to flashing the TWRP, so stock recovery.
I want to backup the recovery.img in case i brick the device after doing
adb reboot recovery the device cant be found any more in the adb device list so nothing from that.
I tried to sideload it using the adb sideload but the same
it`s saying waiting for device and stays there even when i`m trying to send a file to the device.
Click to expand...
Click to collapse
waiting for device...you should kill adb process first, and then reconnect your pc
---------- Post added at 11:33 ---------- Previous post was at 11:32 ----------
enkrs said:
Ok little update.
tried to downgrade but getting the error footer not correct and unable to verify.
Normaly saying you can disable this using the TWRP system as i cannot even get the bootloader to unlock.
So i cant get TWRP installed on the device.
If anyone knows how to downgrade the b13 to the b10 so we can use the tools provided in other posts
Please help how further .
Click to expand...
Click to collapse
if you want to downgrade the b13 to the b10，maybe you should use official recovery
If you can explain how to downgrade using the original recovery please i have tried sideloading
and placing the rom file in the location reserved for update etc.
enkrs said:
If you can explain how to downgrade using the original recovery please i have tried sideloading
and placing the rom file in the location reserved for update etc.
Click to expand...
Click to collapse
Hello Mate,
I am in the same situation as you. I have been looking all over the internet and came across a Chinese forum. Apparently, it is possible to unlock and root B13. However, I have used Google translater to translate the page. It's hard to understand the steps. I have not tested it. But maybe someone out there will have a better understanding and could give it a go. Here is the link
http://www.myzte.cn/forum.php?mod=viewthread&tid=320458&mobile=2
Hope that helps
Hi,
I have TWRP but I want to use the default bootloader. Is there a way to restore it back to stock without losing my apps and settings?
I downloaded (A2017UV1.1.B35 (Nougat) (Post # 2 or Click Here)) from here:
https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
https://androidfilehost.com/?w=file...c9cf15e47b9a9c4af6f1239b585792c06c0520ebc3480
I extracted the recovery.img
then I followed this:
https://www.theandroidsoul.com/how-to-install-twrp-recovery-via-fastboot/
But after I type this:
adb reboot bootloader
I am in the booting black screen for 5 seconds, as the loading screen tells me, before it reboots. Either way when I call this command right after:
fastboot flash recovery recovery.img
I am getting "waiting for device" print and it never finishes. Before that ADB sees my device. What do I need to do so I can fix this?
Thanks in advance.
lachdanan said:
Hi,
I have TWRP but I want to use the default bootloader. Is there a way to restore it back to stock without losing my apps and settings?
I downloaded (A2017UV1.1.B35 (Nougat) (Post # 2 or Click Here)) from here:
https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
https://androidfilehost.com/?w=file...c9cf15e47b9a9c4af6f1239b585792c06c0520ebc3480
I extracted the recovery.img
then I followed this:
https://www.theandroidsoul.com/how-to-install-twrp-recovery-via-fastboot/
But after I type this:
adb reboot bootloader
I am in the booting black screen for 5 seconds, as the loading screen tells me, before it reboots. Either way when I call this command right after:
fastboot flash recovery recovery.img
I am getting "waiting for device" print and it never finishes. Before that ADB sees my device. What do I need to do so I can fix this?
Thanks in advance.
Click to expand...
Click to collapse
First of all it would be a good start to actually get fastboot mode :laugh: You should actually follow a guide instead of trying to do this by your own. Find a guide for the U (assuming that you have an U). You'll have to install fastboot via miflash or whatever
Thanks the guides I found online all advise to use that fastboot command. That's why I couldn't figure it out. I have A2017U yes. Do you know any guide for this?
I will google more using your miflash keyword. Thanks again
The toolkit can do this for you. Make sure you are 100% stock bootstack, recovery, and system, with everything working, before you attempt to lock your bootloader. Lots of people ignore that warning and brick their phones. I'm not sure if your apps and data survive a lock.
I tried to lock mine via adb and bricked it. Luckily, the RMA people believed me that it was a failed software update and fixed it for me. I wouldn't try to do that again ^^
lachdanan said:
Thanks the guides I found online all advise to use that fastboot command. That's why I couldn't figure it out. I have A2017U yes. Do you know any guide for this?
I will google more using your miflash keyword. Thanks again
Click to expand...
Click to collapse
Were the guides that you found online for the Axon 7? Because I meant HERE AT XDA...
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.