Develop Bugs

[Q] bootloader help

im in bootloader menu on my htc. i lost superuser access, and all root apps wont work either. im tryin to update superuser but cant get anything to work. please help

It sounds like perhaps you took an OTA and it replaced a lot of things, including removing root access and possibly placing you back on Stock Recovery instead of TWRP or CWM
If you're actually at the bootloader menu, does it say "UNLOCKED" at the top? I assume you've also done Rumrunner's S-OFF at some point, right?
For you to ever have had root access at some point, it means that you flashed in a custom recovery and flashed in a Superuser package ZIP file.
Being at the bootloader menu gives you the option to go to fastboot, or to go to recovery. What happens when you go to Recovery?
If you have a custom recovery (TWRP or CWM) then you'll have the option to ADB Sideload a ZIP file for installation to your phone.
Koush keeps his Superuser.zip in the description of his app on the Play Store: https://play.google.com/store/apps/d...uperuser&hl=en
ChainFire keeps his SuperSU.zip here: http://download.chainfire.eu/supersu
Don't forget to get more info about SuperSU from his official thread at http://forum.xda-developers.com/show....php?t=1538053

projektorboy said:
It sounds like perhaps you took an OTA and it replaced a lot of things, including removing root access and possibly placing you back on Stock Recovery instead of TWRP or CWM
If you're actually at the bootloader menu, does it say "UNLOCKED" at the top? I assume you've also done Rumrunner's S-OFF at some point, right?
For you to ever have had root access at some point, it means that you flashed in a custom recovery and flashed in a Superuser package ZIP file.
Being at the bootloader menu gives you the option to go to fastboot, or to go to recovery. What happens when you go to Recovery?
If you have a custom recovery (TWRP or CWM) then you'll have the option to ADB Sideload a ZIP file for installation to your phone.
Koush keeps his Superuser.zip in the description of his app on the Play Store: https://play.google.com/store/apps/d...uperuser&hl=en
ChainFire keeps his SuperSU.zip here: http://download.chainfire.eu/supersu
Don't forget to get more info about SuperSU from his official thread at http://forum.xda-developers.com/show....php?t=1538053
Click to expand...
Click to collapse
i ran rummer a month or so ago. i had s-off and on bootloader menu it says unlocked. when i click on recovery it just reboots. when i first did this i never flashed twrp. i did a root check when i did rumrunner it said root access granted. now when i check it it says no root access, and my superuser is gone. i tried dl all sdk again, but i cant get comp to find phone in cmp. i also tried to launch rumrunner again ,, it rebooted phone few times then ended with stupid problems with phone press enter to exit. im about to throw in towel after hours of trying different things..

projektorboy said:
It sounds like perhaps you took an OTA and it replaced a lot of things, including removing root access and possibly placing you back on Stock Recovery instead of TWRP or CWM
If you're actually at the bootloader menu, does it say "UNLOCKED" at the top? I assume you've also done Rumrunner's S-OFF at some point, right?
For you to ever have had root access at some point, it means that you flashed in a custom recovery and flashed in a Superuser package ZIP file.
Being at the bootloader menu gives you the option to go to fastboot, or to go to recovery. What happens when you go to Recovery?
If you have a custom recovery (TWRP or CWM) then you'll have the option to ADB Sideload a ZIP file for installation to your phone.
Koush keeps his Superuser.zip in the description of his app on the Play Store: https://play.google.com/store/apps/d...uperuser&hl=en
ChainFire keeps his SuperSU.zip here: http://download.chainfire.eu/supersu
Don't forget to get more info about SuperSU from his official thread at http://forum.xda-developers.com/show....php?t=1538053
Click to expand...
Click to collapse
this also all started after verizon came out with update and phone automatically updated but unsuccusfully

Thank you for re-affirming my suspicion that an OTA put you in this position.
Rumrunner wasn't ever going to help you in your situation. Rumrunner is purely for achieving S-OFF. Since you're still S-OFF, it didn't have anything to do with your phone. Your root access is gone because the OTA wiped it out. It's important to always be careful about OTA updates because OTA updates assume that you NEVER modified your phone and will write whatever they want to wherever they want.
Since you can at least get to the bootloader, your phone can be saved. You said that you tried to update your SDK so that you could have the fastboot files available. When you run the SDK updater (I assume you're on Windows) you have to right-click and run as Administrator to make it work.
The files you want for fastboot are hiding in c:\program files (x86)\Android\android-sdk\platform-tools\
Take adb.exe, fastboot.exe, adbwinapi.dll, and adbwinusbapi.dll and copy them to a separate folder. (Such as C:\adb\) Navigate to that folder and do shift+right-click in a blank area of the folder so you can run a command prompt. You will want to put a ROM and a recovery file in this same folder too. (You sound like you want the stock ROM)
Use the command 'fastboot devices' to see if the phone shows up. If the phone doesn't show up, then you need to go to the HTC Website so you can install HTC Sync, then remove Sync (while leaving the drivers behind) so that your phone has the correct drivers to make it show up in fastboot.
If 'fastboot devices' ends up revealing a device, then you can grab a custom recovery image file and do "fastboot flash recovery filename.img" to put a custom recovery in your phone. Then within the custom recovery you can do adb sideload romname.zip to install a ROM and that should put your phone back into a usable state.

projektorboy said:
Thank you for re-affirming my suspicion that an OTA put you in this position.
Rumrunner wasn't ever going to help you in your situation. Rumrunner is purely for achieving S-OFF. Since you're still S-OFF, it didn't have anything to do with your phone. Your root access is gone because the OTA wiped it out. It's important to always be careful about OTA updates because OTA updates assume that you NEVER modified your phone and will write whatever they want to wherever they want.
Since you can at least get to the bootloader, your phone can be saved. You said that you tried to update your SDK so that you could have the fastboot files available. When you run the SDK updater (I assume you're on Windows) you have to right-click and run as Administrator to make it work.
The files you want for fastboot are hiding in c:\program files (x86)\Android\android-sdk\platform-tools\
Take adb.exe, fastboot.exe, adbwinapi.dll, and adbwinusbapi.dll and copy them to a separate folder. (Such as C:\adb\) Navigate to that folder and do shift+right-click in a blank area of the folder so you can run a command prompt. You will want to put a ROM and a recovery file in this same folder too. (You sound like you want the stock ROM)
Use the command 'fastboot devices' to see if the phone shows up. If the phone doesn't show up, then you need to go to the HTC Website so you can install HTC Sync, then remove Sync (while leaving the drivers behind) so that your phone has the correct drivers to make it show up in fastboot.
If 'fastboot devices' ends up revealing a device, then you can grab a custom recovery image file and do "fastboot flash recovery filename.img" to put a custom recovery in your phone. Then within the custom recovery you can do adb sideload romname.zip to install a ROM and that should put your phone back into a usable state.
Click to expand...
Click to collapse
Ty for walk through! Will try tomorrow! I wanna get kit kat on here. I think some problems were from files on comp in wrong folders. Hope this works

[HOW-TO] Root the Shield TV

First of all, let me say this isn't my post, and I didn't develop this method. The user, "Teletype" got this all figured out and did an amazing write-up for it. I'm posting it on their behalf so it can be in this newly added forum. The link to the recovery zip is also in his original thread, which I've linked below.
Here's the link to his original thread. If you feel the urge to press "thanks", please go to his original thread and press it for him, he deserves all the credit.
teletype said:
I just managed to get TWRP running on the new Shield console, and installed SuperSU successfully. Two caveats: the display is upside down, and the USB host ports don't work. I had to plugin a mouse via an OTG cable in order to interact with it. ETA: That's only an issue when booted to TWRP. Everything's working fine in the stock ROM after rooting.
Procedure:
- enable developer tools / USB debugging
- adb push supersu.zip /sdcard
- adb reboot bootloader
- fastboot oem unlock
- fastboot boot twrp-2.8.6.0-shieldtv-unofficial.img
- unplug USB cable, connect mouse via USB, install SuperSU
TWRP boot image is attached. Off to explore...
EDIT: by request, some more detailed instructions:
On the Shield device, head to Settings -> About, and click "Build number" 7 times. This will enable Android's Developer options.
Go to Settings -> Developer options, and enable USB debugging.
Install the ADB/fastboot drivers and utilities if you don't already have them. When "adb devices" shows your Shield, you're good to go.
Download and extract recovery.zip from this thread.
Head to the SuperSU forum and download the latest version.
Open a command prompt and navigate to the directory where you downloaded everything. (Google this for your OS if you don't know how).
With the Shield still booted, run "adb push supersu.zip /sdcard" (change supersu.zip to appropriate file name). This will upload the SuperSU update zip to your device, which you'll install from TWRP.
If that worked fine, run "adb reboot bootloader". Your device should shut down, and display the Fastboot screen after a few seconds.
FOLLOW THE NEXT THREE INSTRUCTIONS AT YOUR OWN RISK. This WILL wipe all your user data, back it up with ADB first if you want to preserve it. DISCLAIMER #2: I have no idea if there are any DRM keys or anything that get wiped when this is done (this was the case on my Xperia Z3 Compact). I will say that Grid streaming still works fine after doing this.
This step will unlock your bootloader to enable booting unsigned images.
Run "fastboot devices" and make sure your Shield is visible.
Run "fastboot oem unlock" and follow the prompts on the screen. Your bootloader is now unlocked.
Now, boot the TWRP image with: "fastboot boot twrp-2.8.6.0-shieldtv-unofficial.img" - Note: I used this instead of "fastboot flash" so I could keep the stock recovery around, to grab an image of it after rooting.
You should now see a TWRP recovery menu (upside down for now).
Connect a keyboard or mouse via OTG cable, and select "Install", navigate to your SuperSU zip, select it, and follow the prompts.
Click "reboot" and you should now be rooted.
Click to expand...
Click to collapse

does this have to be done with an otg cable

You can use the supplied micro USB cable to do the adb portion. You shouldn't ever need otg with this device since it also has 2 full sized USB ports.
Sent from my nexus 9 using XDA Free mobile app

Instructions got updated
Hi,
I have updated the instructions to ones that more closely aligned with my experience of doing this. The initial instructions were good for me - but some were in slightly the wrong order or not quite clear enough to be immediately intuitive. I've tried to fix that Hope it helps.
On the Shield device, head to Settings -> About, and click "Build number" 7 times. This will enable Android's Developer options.
Exit settings, then go back in to settings -> Developer options, and enable USB debugging.
Install the ADB/fastboot drivers and utilities on to your PC if you don't already have them. When "adb devices" shows your Shield, you're good to go.
Download the latest Super user zip file from the super user thread here.
Download and extract the recovery file from here. (it needs to be a .img not a .zip)
run "adb reboot bootloader". Your device should shut down, and display the Fastboot screen after a few seconds.
FOLLOW THE NEXT THREE INSTRUCTIONS AT YOUR OWN RISK. This WILL wipe all your user data, back it up with ADB first if you want to preserve it. DISCLAIMER #2: I have no idea if there are any DRM keys or anything that get wiped when this is done.
This step will unlock your bootloader to enable booting unsigned images.
Run "fastboot devices" and make sure your Shield is listed when you do so.
Run "fastboot oem unlock" and follow the prompts on the Shield's screen. You use the power button on the shield device itself to navigate the menu, and long press to select an option. Once you have confirmed, this can take along time to unlock (hour and a half for me on the Pro version). Your bootloader is now unlocked.
"Fastboot reboot" to reboot to AndroidTV.
run "adb push supersu.zip /sdcard/" (change supersu.zip to appropriate file name that you downloaded earlier). This will upload the SuperSU update zip to your device, which you'll install from TWRP.
Now, boot the TWRP image with: "fastboot boot RECOVERYFILENAME.img" - Note: I used this instead of "fastboot flash" so I could keep the stock recovery around, to grab an image of it after rooting. (change the name of the file in the instructions to the name of your recovery file that you downloaded).
After a short while you should now see a TWRP recovery menu.
Connect a keyboard or mouse via OTG cable, and select "Install", navigate to your SuperSU zip, select it, and follow the prompts.
Click "reboot" and you should now be rooted.
Click to expand...
Click to collapse

Anyone tried kingroot?

Sean09 said:
Anyone tried kingroot?
Click to expand...
Click to collapse
We have a factory supported way to unlock and root. No real point in trying to exploit the system. If you are rooted, you should have a custom recovery anyway, which means you need to unlock the bootloader anyway in case you need to fix something.

Hey, I have rooted my shield and I didn't backup my stock recovery, anyone have a stock recovery img, I want to update to 1.4
Thanks

Gig11gs said:
Hey, I have rooted my shield and I didn't backup my stock recovery, anyone have a stock recovery img, I want to update to 1.4
Thanks
Click to expand...
Click to collapse
You can download the 1.4 firmware and flash it manually. There's a discussion on it a few pages back :good:

Will I be able to get OTA updates if I root ?

rahulkadukar said:
Will I be able to get OTA updates if I root ?
Click to expand...
Click to collapse
You'll get the OTA notification but I was not able to install the OTA. You will need to download and new firmware and flash from fastboot.

Can I still root it this way if I already updated to 1.4 as I'm still fully stock and took the OTA

Im asking the same, im on the latest as of 2015 10 19, can i root using this method ?

baileyjr said:
You'll get the OTA notification but I was not able to install the OTA. You will need to download and new firmware and flash from fastboot.
Click to expand...
Click to collapse
You're guided imagery? I read without understanding very much

Can anyone confirm this rooting method works for new firmware 2.1?

garz said:
Can anyone confirm this rooting method works for new firmware 2.1?
Click to expand...
Click to collapse
I struggled to get root with this write up, and I am not a rookie. There were a few key steps missing, for example, you actually have to flash twrp, you can't just boot from twrp as suggested, if you are on 1.4 and up. Also, you have to let the unit reboot after you do the OEM unlock before flashing twrp. I didn't and mine just froze after flashing the recovery img. I found this write up http://nvidiashieldzone.com/index.php/shield-android-tv/root-shield-android-tv/
That one in the shield zone forum was so much more complete. And yes, it worked just fine with the 2.1 update. I did it yesterday with no problems. It will wipe out your data, and it will take a long time after you do the fastboot oem unlock, especially if you have the PRO version. But root is working with no problems.

RyanInBinary said:
First of all, let me say this isn't my post, and I didn't develop this method. The user, "Teletype" got this all figured out and did an amazing write-up for it. I'm posting it on their behalf so it can be in this newly added forum. The link to the recovery zip is also in his original thread, which I've linked below.
Here's the link to his original thread. If you feel the urge to press "thanks", please go to his original thread and press it for him, he deserves all the credit.
Click to expand...
Click to collapse
Do you want to build pre-root shiled TV firmware by nvidia open source？ and have experience？

Rooting.
KingRoot dose not work on this device.

Good guide thanks.

OK i have a 16gb model on 2.1, got adb hooked up but get this when trying to push supersu.zip to sdcard0:
C:\shield>adb push supersu.zip /sdcard1
failed to copy 'supersu.zip' to '/sdcard1': Read-only file system
Any ideas?

bearkilla said:
OK i have a 16gb model on 2.1, got adb hooked up but get this when trying to push supersu.zip to sdcard0:
C:\shield>adb push supersu.zip /sdcard1
failed to copy 'supersu.zip' to '/sdcard1': Read-only file system
Any ideas?
Click to expand...
Click to collapse
Try
Adb push supersu.zip /sdcard/
Inviato dal mio SHIELD Tablet utilizzando Tapatalk

Yet another OTA softbrick thread. How screwed am I?

Hi all,
It seems I come back a n00b every few years.
I rooted my Zenfone 2 to remove some clutter and guess what I did today? I updated. Didn't know that would brick my phone but well here I am.
I followed these steps:
http://www.asus-zenfone.com/2015/06/how-to-update-ota-without-bootloop-on-rooted-zenfone2.html
Only to find that it wouldn't boot.
Went into recovery and tried to factory reset... went on for more than 15 minutes (I didn't want to stop the process....). I then had to hard reset then boot into recovery and tried to wipe cache which yielded nothing...
BTW, I think the failed wipe and reset messed up permissions as fastboot yields an error (even though the "flash recovery" bit seems to work).
I tried installing TWRP and it only boots back into fastboot. Reinstall the recovery from the link above and I can go back into recovery but can't seem to use any of the functions.
Any ideas?
p.s. I did do a few searches. Can't find anything specific about

I also tried using the adb sideload to sideload official firmware but it yields "error: device not found" and then goes back into regular recovery...

adramelch said:
I also tried using the adb sideload to sideload official firmware but it yields "error: device not found" and then goes back into regular recovery...
Click to expand...
Click to collapse
Have you installed all your drivers correctly?
In TWRP, have you gone into advanced and selected ADB Sideload? I've also had issues with sideloading, I think it's a TWRP issue though.
Here's what you can try:
Boot into TWRP and make sure the phone is detected on the PC.
open up adb
type: adb devices
hit enter
your device should be listed
type: adb push -p rom.zip /sdcard0/
-for push, it's just the command to push files to your phone. Alternatively, pull is for taking files from your phone (in the event you can't boot up and need a certain file)
-for -p, it just means show progress, so in CMD you'll see a percentage sign which is always a good thing to know
-for rom.zip you type in the location of the file
-for /sdcard0/ you can leave that, as that is the send destination and should land right in your main folder.
And once the file is transferred over, install through TWRP.
Wipe Dalvik/Cache.
Reboot system.
Profit.
If all this doesn't work, try a microsd card with the file on it.
EDIT: I just realized you meant you meant stock recovery. In that case...it should still allow you to adb sideload, but I'm not sure. As long as you can still use ADB, you can follow my instructions above.

adb push yields "error: closed"
adb sideload says it needs adb 1.0.32 to do operation...

Try using microSD, download the latest firmware on asus website, then rename the zip to MOFD_UPDATE.zip and copy it to your microSD then go to recovery mode and it'll install the update. it took sometime be patient

badaboomBURP said:
Try using microSD, download the latest firmware on asus website, then rename the zip to MOFD_UPDATE.zip and copy it to your microSD then go to recovery mode and it'll install the update. it took sometime be patient
Click to expand...
Click to collapse
Recovery doeasn't have option "Update from zip" but this time, the adb sideload command worked for some reason...

adramelch said:
Recovery doeasn't have option "Update from zip" but this time, the adb sideload command worked for some reason...
Click to expand...
Click to collapse
in my experience, it automatically install the zip if i go to recovery

Update: Sideload worked and I've been back to stock since. Didn't want to flash because I was ok with stock but didn't want the clutter. Will find another stable firmware if need be.
Thanks again for the help!

ZE500CL Can't boot TWRP/Recovery, Can't factory reset

Picked one of the 2e's up cheap. Check your Walmarts, it's on clearance for $11.
Followed the Root instructions. No problem there.
Followed the bootloader unlock instructions. It seemed to work but my splash screen didn't change.
Went to install the Russianbear Rom. That left me with a blackscreen and nothing else.
From there, I managed to get into TWRP and flash the Stock ASUS ZE500CL Rom. That went in fine and the phone is 100% functional.
But now, I can't boot into recovery or even access TWRP. If I Power+Vol +, to where it gives the option of Recovery/Reboot/Power etc, Recovery just brings me back to the same menu. I reflashed TWRP on through ADB. Still no go.
I rerooted and installed TWRP manager to attempt to reflash just brings me back to that same menu.
I wanted to reset it to stock again with the ZE500CL rom, or if possible, test a different rom for ****s and giggles. Just to see what flavors are out there.
Any input into how to get TWRP or another flasher working would be appreciated.

Fastboot flash twrp. I've had issues with twrp manager on that phone
Sent from my ASUS_Z00AD using XDA-Developers mobile app

jflow36 said:
Fastboot flash twrp. I've had issues with twrp manager on that phone
I did. Fastboot Flash Recovery Twrp.img through CMD. Still nada.
It's the first TWRP I used. and the crap thing is, I can't even revert to stock because that involves going through a recovery.
Click to expand...
Click to collapse

Try adb reboot recovery in Android. Remember to turn on USB debugging

HungNgocPhat said:
Try adb reboot recovery in Android. Remember to turn on USB debugging
Click to expand...
Click to collapse
done that too. Nada. And yup, still in Debug mode.

I take this from a Vietnamese post, you should read the post to see the screenshots: http://amtech.vn/threads/tat-tan-tat-ve-recovery-tren-zenfone-2-ze551ml-ze550ml.365204/ (these are different methods, not steps in one method)
Translated:
I. If your are unlocked and rooted, download Terminal Emulator from Play Store, copy your TWRP image to /sdcard, rename to recovery.img, then open Terminal Emulator, type
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/by-name/recovery
Remember to grant access to Terminal Emulator after typing su.
II. Download Rashr from Play Store (must be rooted and unlocked)
Copy your TWRP image to your sdcard. Open Rashr and choose Recovery from Storage then navigate to your TWRP image. Select YES at the prompt. (grant superuser if prompted)
III. Copy your TWRP image to your SDcard, then boot temporary TWRP, choose Install... then select Image... then choose the image. Select Recovery. Slide to confirm flash.

Pixel xl in twrp with no OS installed?

Hello to all. I have just unlocked bootloader, installed twrp and su. After everything booted up properly, I went to install an adblocker zip file, however once it booted into twrp it had no download folder, as well as when I went to reboot system it told me I had no os installed.. I'm a bit confused as to what to do now.. My apologies for clogging the thread if this has been answered before..
Edit: do I adb side load an image file or OS? I'm afraid of bricking this phone as I don't know how to continue from this point..

Which guide did you use to do all of this? I will help us understand where you started

Mrbobrowitz said:
Which guide did you use to do all of this? I will help us understand where you started
Click to expand...
Click to collapse
Hi thanks for the reply. This link right here:
http://www.androidsage.com/2016/11/...timate-guide-root-twrp-and-bootloader-unlock/
Steps I followed:
1 unlocked bootloader
2 Download the below files TWRP and Root files for Google Pixel & Pixel XL
Official TWRP for Pixel phones → Download |
Files: twrp-pixel-installer-sailfish-3.0.2-0-alpha1.zip 7.6M
twrp-3.0.2-0-alpha1-fastboot-sailfish.img 25M
Flash SuperSU 2.78 SRF4 → Download | File: SR4-SuperSU-v2.78-SR4-20161115184928.zip
Twrp install instructions:
Step 1: Download the TWRP recovery and latest SuperSU zip file for your Google Pixel and Pixel XL devices. There are 2 TWRP files with .zip and .img extensions. You will need both. You don’t need to extract the files, just place all the files on your PC as well as your Android phone’s internal storage where you can easily locate it.
Step 2: Make sure that you setup ADB and Fastboot on your PC and gone through all the prerequisites from above.
Step 3: Now plug in the Pixel device to the computer and open a command prompt or terminal on your PC to the window where TWRP.zip file is located. (See above to know how to open cmd)
Step 4: Boot your Android device into the bootloader or Fastboot mode. To do so, issue the following command through cmd or terminal. You can also manually boot into it using the hard key combination like Power+Volume Down while the device is turned off. Meanwhile, use code:
adb reboot-bootloader
Step 5: Now issue the following command in the command prompt to check your device connectivity
fastboot devices
Step 6: Now issue the following command to temporarily boot up the TWRP image.
fastboot boot path/to/twrp.img
Note: If you have installed our recommend quick 15 second ADB & fastboot installer, you do not need to insert the complete file path. Simply go to where the TWRP image file is and issue command “fastboot boot twrp.img” Otherwise, note that “path/to/” is the actual directory for the TWRP image file. Use fastboot boot and not fastboot flash and that the file you are booting is not the zip file.
Simply After that, TWRP will be accessible to you no matter which active partition slots are being used.
Step 7: After that fastboot command, you will be rebooted into a temporary TWRP recovery interface. To make it permanent, use the TWRP interface to navigate to and install the TWRP.zip file. This is just like using TWRP to flash custom ROMS and SuperSU.
Once the installation completes, you can now enjoy your new firmware. Alternatively, while, on Mac OS, you can issue “./fastboot boot path/to/twrp.img” command or on Linux type “sudo fastboot path/to/twrp.img” to flash the TWRP. For detailed tutorial and alternate methods to flash the TWRP recovery, click here.
Now it’s time to root your Google Pixel with latest SuperSU 2.78 SR4.
How to root :
Place the latest SuperSU 2.78 SR4 package onto your device’s internal storage or SDcard.
Boot your device into the custom TWRP recovery and tap install. For that, turn off your device completely and hold volume down and power buttons for a few seconds.
Once into TWRP tap the install button and select the SuperSU file.
Swipe the confirmation action below to start flashing.
Once done. reboot to system.
You can boot into the TWRP recovery by issuing the following command:
adb reboot recovery

There is an alpha 2 for twrp now. I would try installing this and seeing if it works. If not, you can simply flash the latest factory image and "start over". Granted you would lose any data that you might have had not backed up on your device, but youre not out of luck!

I wouldn't waste your time. Just flash the factory image and start all over. You managed to wipe the Rom off your device

Smallsmx3 said:
I wouldn't waste your time. Just flash the factory image and start all over. You managed to wipe the Rom off your device
Click to expand...
Click to collapse
Mrbobrowitz said:
There is an alpha 2 for twrp now. I would try installing this and seeing if it works. If not, you can simply flash the latest factory image and "start over". Granted you would lose any data that you might have had not backed up on your device, but youre not out of luck!
Click to expand...
Click to collapse
Thanks guys, I actually have installed the alpha 2 twrp. I guess my question is how do I proceed? I'm in twrp and my PC does not see the device when typing adb devices.. Within twrp it says no os installed... What do I do here?
So how do I "start over" or "flash factory image" from the state that I'm in?

mazubo said:
Thanks guys, I actually have installed the alpha 2 twrp. I guess my question is how do I proceed? I'm in twrp and my PC does not see the device when typing adb devices.. Within twrp it says no os installed... What do I do here?
So how do I "start over" or "flash factory image" from the state that I'm in?
Click to expand...
Click to collapse
You should be able to boot into fastboot

Smallsmx3 said:
You should be able to boot into fastboot
Click to expand...
Click to collapse
Ok, and if that works then flash 7.1.1? Then twrp alpha then root via SuperSU flash?
A side question here is how did I wipe the os/from off the phone? I'm stumped on that one..

mazubo said:
Ok, and if that works then flash 7.1.1? Then twrp alpha then root via SuperSU flash?
A side question here is how did I wipe the os/from off the phone? I'm stumped on that one..
Click to expand...
Click to collapse
I couldn't tell you! I've had it happen to me before a couple times. But yes if you can get into fastboot you should be able to fastboot flash a factory image. Then go and flash TWRP and root

Smallsmx3 said:
I couldn't tell you! I've had it happen to me before a couple times. But yes if you can get into fastboot you should be able to fastboot flash a factory image. Then go and flash TWRP and root
Click to expand...
Click to collapse
Ok thanks. I've been able to reboot to bootloader...

I've figured it out via fast boot. The phone is back in action, however not sure how it got wiped initially.. Thanks everyone!

mazubo said:
Ok, and if that works then flash 7.1.1? Then twrp alpha then root via SuperSU flash?
A side question here is how did I wipe the os/from off the phone? I'm stumped on that one..
Click to expand...
Click to collapse
mazubo said:
I've figured it out via fast boot. The phone is back in action, however not sure how it got wiped initially.. Thanks everyone!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Off the top of my head... Probably selected the wrong "slot" maybe?
Remember on this device there are two locations for the ROM. Slot A and B. If you select the wrong one it will show no OS.
As far as the download folder missing... I know its mute at this point, but that has to do with the FBE (File Based Encryption). Make sure TWRP asks you for your Pattern Password. If you do not have one I would consider setting one. That way you know for fact that the File system will get decrypted properly. Also reports say you may have to reboot TWRP twice to get it to decrypt as well.