So I was tring to go back to stock completely, after I locked my bootloader and installed stock recovery, I proceed to sideload oss, like I've done before I put the phone in sideload mode, the device is recognized by adb although I got a cannot read file error, I downloaded the stock rom again (even though the zips were not corrupted as I could browse them easily) and the same thing happend.
Now I'm at a loss as what to do as it has stock recovery and no os installed, I can get into the bootloader and the stock recovery but I've never had this happen and I can't find anything that will help.
I tried with cmd prompt and adb in administration mode no change, I also made sure the file was in the adb folder.
I'm not sure of what else to say except to ask for help, I'm way bummed out, I've gone back to stock on this device before the only difference was I was running marshmallow other than that idk any other changes since the last time.
I would be very grateful for any help at all. Right now I just need a working phone,
Thank you for reading my post and thank you in advance for possible help with my issue.
Simple reboot of PC should do the trick, at least that did it for me
Didn't work for me, after the first fail I went to a l coffee shop and downloaded the rom again after shutting the pc off in the mean time.
It had no problem flashing the stock recovery it was only after I locked the bootloader and then tried to flash the stock rom
Check the specification of pc should be 4GB ram, drivers, and disable anti virus.
lebeatnik said:
Didn't work for me, after the first fail I went to a l coffee shop and downloaded the rom again after shutting the pc off in the mean time.
It had no problem flashing the stock recovery it was only after I locked the bootloader and then tried to flash the stock rom
Click to expand...
Click to collapse
Keep your bootloader unlocked, I assume you try to ADB sideload? Try adb push file /sdcard/ then manually flash it through TWRP
madsponge26 said:
Check the specification of pc should be 4GB ram, drivers, and disable anti virus.
Click to expand...
Click to collapse
This doesn't make sense... Even a 1GB RAM laptop can do this.
The specs. Of the pc is not the issue
So your advice would be to unlock the bootloader and use twrp?
Currently as I s
lebeatnik said:
The specs. Of the pc is not the issue
So your advice would be to unlock the bootloader and use twrp?
Currently as I s
Click to expand...
Click to collapse
No the specs are not an issue lol.. Basically it cannot read the file you are trying to sideload, this is because of either wrong adb drivers, or wrong Fastboot drivers... A easy work around is to manually push the file with "adb push filename directory" then you manually flash it but since stock recovery can't do this it won't work.
So what steps do I need to do to fix this,
Do I first lock the bootloader, then flash twrp? Also to push the file with adb what mode should I put the phone in?
Sorry For these terrible replies, I'm on a very old backup device.
It's odd to me as adb detects the device just fine, I was even able to flash the stock recovery, as I was trying to go back to complete stock.
In all I need to get the device work again.
I have the latest stock rom and twrp, I just don't want to make it totally bricked as right now I can at least get the phone into the bootloader and in side load mode (although it doesn't work)
So basically I'm asking how in what order should i go about, locking the bootloader, flashing twrp, and push the rom, I've never done this before.
I can't thank you enough for trying to help me out.
I'm thinking I would unlock the bootloader then flash twrp recovery, then idk what mode I should be in to try and push the rom via adb (I've never done this) as once I get twrp on the device and have the rom on the device I hope to have no problem flashing the rom through twrp.
Thank you for replying I hope to resolve this ASAP.
Sorry for not editing my previous post im struggling with the device I'm currently using, I don't understand why my drivers or adb version isn't working as i had no problems locking the bootloader and flashing stock recovery, the only problem I ran into was the last step, flashing the rom.
So yeah I don't know but after I locked the bootloader.... problems
lebeatnik said:
Sorry for not editing my previous post im struggling with the device I'm currently using, I don't understand why my drivers or adb version isn't working as i had no problems locking the bootloader and flashing stock recovery, the only problem I ran into was the last step, flashing the rom.
So yeah I don't know but after I locked the bootloader.... problems
Click to expand...
Click to collapse
Unlock your bootloader, install twrp. Then wipe all partitions. Adb push your rom to a directory you can remember I usually do /sdcard/ (just stay in twrp.) then you click on install and your rom should be there.
Keep the bootloader unlocked... Just in case, no need to relock it again since you will lose data if you run into an issue.
THANK YOU! All I did was unlock the bootloader and the phone started up I am assuming it did not wipe the system partition and it ended up restarting as if I did a factory reset
Related
So earlier today I had my Verizon HTC One running smoothly; 4.3, 2.10.605.10, all that jazz. Then firewater came out, so I did S-Off. I then installed Clockworkmod, because TWRP wouldn't (turns out I installed the m7 variant instead of the m7vzw one). I also had the wrong version of clockworkmod, so it wouldn't factory reset or clear cache. I decided I would try to install Cyanogenmod anyway, and right after I started the install I found the correct version of TWRP so I hard reset out of the install with the Power and Volume Down buttons.
Now I am stuck in bootloader, and there is not much I can do. I can't install the RUU that i have because I cant "fastboot oem lock" and I also can't flash or boot directly to the TWRP or Clockworkmod .img files. Any ideas on how to fix it?
tl;dr I stopped a .zip install and now I am stuck in bootloader HELP PLEASE
Billcheese5 said:
So earlier today I had my Verizon HTC One running smoothly; 4.3, 2.10.605.10, all that jazz. Then firewater came out, so I did S-Off. I then installed Clockworkmod, because TWRP wouldn't (turns out I installed the m7 variant instead of the m7vzw one). I also had the wrong version of clockworkmod, so it wouldn't factory reset or clear cache. I decided I would try to install Cyanogenmod anyway, and right after I started the install I found the correct version of TWRP so I hard reset out of the install with the Power and Volume Down buttons.
Now I am stuck in bootloader, and there is not much I can do. I can't install the RUU that i have because I cant "fastboot oem lock" and I also can't flash or boot directly to the TWRP or Clockworkmod .img files. Any ideas on how to fix it?
tl;dr I stopped a .zip install and now I am stuck in bootloader HELP PLEASE
Click to expand...
Click to collapse
Are you able to access fastboot from the boot loader?
If so do
Fastboot reboot recovery
Since you have TWRP installed already? If you can get adb sideload to work you can flash a new ROM of your choice after you clear the dalvik cache and such. If adb won't work for you you may have to order an otg cable to get that ROM to your phone. If you can't access fastboot and/or get into recovery.... RIP M7Vzw
eXperianceHD said:
Are you able to access fastboot from the boot loader?
If so do
Fastboot reboot recovery
Since you have TWRP installed already? If you can get adb sideload to work you can flash a new ROM of your choice after you clear the dalvik cache and such. If adb won't work for you you may have to order an otg cable to get that ROM to your phone. If you can't access fastboot and/or get into recovery.... RIP M7Vzw
Click to expand...
Click to collapse
So I tried the fastboot rebbot recovery and I don't think that is a correct command, because when I do it a list of all the fastboot commands comes back and my phone doesn't do anything. Also it was working before but now my device isn't visible under adb devices, so I don't think sideloading a different rom will work. Plus I can't get to the recovery, or even the stock factory reset or anything. They all just bounce me back to the bootloader menu.
Do you think it would be worth it to order and wait for an otg cable or just order a new phone? I'm not due for an upgrade and I don't think I'm willing to shell out $500 for a new One, or even $400 for a new Moto X, so I think I'll be getting the Moto G (I'm on a student budget here).
Are you running your commands fro the platform tools folder?
Oh well
Thanks for the help guys, I wasn't able to run any adb commands like I could before, so I guess that's that. Again, I am at college, and my parents happened to be visiting so I gave it to them. I have accident insurance on my phone, so they are going to send it back and have the replacement sent to me... so I can try again, hopefully more successfully the second time :laugh:
Hello.
So I tried to install Lollipop on my Nexus 7 2013 WiFi. I used their official instructions developers.google.com/android/nexus/images . Before that I made a backup in recovery (if something went wrong) and wiped data. So I did all that and tried to install Lollipop using their instructions, but now after turning the device on I see Google logo and that's all. Also recovery doesn't work. It just shows dead android. Fastboot works, but adb doesn't see my device now.
Before this I had Clean Rom installed.
EDIT: I can see it using fastboot, but it f'd recovery.
EDIT2: I used flash-all second time and now it works, God, for a moment I thought I lost my baby.
Just restart device to bootloader, unpack official Lollipop image and run flash-all.bat within directory with fastboot.
It's very difficult to hard brick..
kuba9519 said:
Fastboot works, but adb doesn't see my device now.
Click to expand...
Click to collapse
FWIW adb only works when booted into Android. Fastboot only works in the bootloader.
kuba9519 said:
Hello.
So I tried to install Lollipop on my Nexus 7 2013 WiFi. I used their official instructions developers.google.com/android/nexus/images . Before that I made a backup in recovery (if something went wrong) and wiped data. So I did all that and tried to install Lollipop using their instructions, but now after turning the device on I see Google logo and that's all. Also recovery doesn't work. It just shows dead android. Fastboot works, but adb doesn't see my device now.
Before this I had Clean Rom installed.
EDIT: I can see it using fastboot, but it f'd recovery.
EDIT2: I used flash-all second time and now it works, God, for a moment I thought I lost my baby.
Click to expand...
Click to collapse
Just download wuzwigs Rom toolkit and revert back to kitkat and start over. Ive had moments where i could barely get fastboot to work because my freaking power went. Just run through that and follow the appropriate steps and try again... Or just wait for the official update next time. It cant be more than a few days away now
Nexus still in mortal peril
GalaxySN00B:0 said:
Just download wuzwigs Rom toolkit and revert back to kitkat and start over. Ive had moments where i could barely get fastboot to work because my freaking power went. Just run through that and follow the appropriate steps and try again... Or just wait for the official update next time. It cant be more than a few days away now
Click to expand...
Click to collapse
My problem is I tried to unroot in order to flash the update to lollipop and now unfortunately I seem to have actually hard bricked the device. I can boot into the bootloader. My device is still ulocked. However when I try to access recovery I get the dead android icon. I tried reinstalling adb. It didn't take. I can't get device to show up in the command line. I tried reinstalling drivers and that's where I'm stuck. I can't seem to make this work. Even if I can just go back to 4.4.4 I'll be happy. What are my other options that don't involve sending it in for repair?
This shows how to get to recovery mode from the dead Android screen http://www.robschmuecker.com/how-to-boot-into-recovery-mode-nexus-7/
Sent from my XT1080 using XDA Free mobile app
atrielienz said:
My problem is I tried to unroot in order to flash the update to lollipop and now unfortunately I seem to have actually hard bricked the device. I can boot into the bootloader. My device is still ulocked. However when I try to access recovery I get the dead android icon. I tried reinstalling adb. It didn't take. I can't get device to show up in the command line. I tried reinstalling drivers and that's where I'm stuck. I can't seem to make this work. Even if I can just go back to 4.4.4 I'll be happy. What are my other options that don't involve sending it in for repair?
Click to expand...
Click to collapse
I accidentally wiped my internal storage and my operating system this weekend! Mskips toolkit is the only one i could find that would install the drivers properly and then flash a factory 5.0.1 image... Everything works great now!!
DMF1977 said:
I accidentally wiped my internal storage and my operating system this weekend! Mskips toolkit is the only one i could find that would install the drivers properly and then flash a factory 5.0.1 image... Everything works great now!!
Click to expand...
Click to collapse
The problem is that I can't boot up. Which means I can't put the device in ADB mode. Which means I can't use the skipsoft tool kit.
Use wugs but make sure you tick tablet is in bootloop, worked for me.
atrielienz said:
The problem is that I can't boot up. Which means I can't put the device in ADB mode. Which means I can't use the skipsoft tool kit.
Click to expand...
Click to collapse
U can't boot in to android, but u did state earlier that u can boot to the bootloader, and that it was unlocked, so its definitely not hard bricked!
I have a soft-bricked HTC One M8, It happened when I was attempting to return the phone to stock android with stock kernel and stock recovery while relocking the bootloader, none of that is really important though what happened is I had a bad flash and the phone got put into a bootloader loop with no OS. It still had an Unlocked bootloader with S-Off. Once it was in a bootloader loop I was able to download a custom recovery via fastboot commands, the phone can now go into TWRP but it will only boot version 2.7.0.0 - earlier versions don't boot at all and newer versions will boot but are non-responsive/have no display.
Once in TWRP 2.7.0.0 I use push command from adb to load a stock android RUU zip into my MicroSD, I attempt to flash it via TWRP 2.7.0.0 but get a failed response. I have cleared everything and TWRP 2.7.0.0 is having trouble mounting /data/. I tried using using push command through adb to put a newer version of TWRP on my MicroSD so that TWRP could flash it but TWRP was unable to do so. Any version of Clockwork Mod has been unsuccessful to boot.
Essentially TWRP 2.7.0.0 can't flash anything or mount anything for me, I believe I need either a newer version or a different recovery, but no other recovery or twrp version seems to be able to boot correctly.
Any tips, advice, or general help would be extremely appreciated. I try to help myself before asking others and I don't know what else I can do, I have searched the forums for every relevant thread possible and tried many many things to get this to work with no success. Thank you for reading.
Gitnerd said:
I have a soft-bricked HTC One M8, It happened when I was attempting to return the phone to stock android with stock kernel and stock recovery while relocking the bootloader, none of that is really important though what happened is I had a bad flash and the phone got put into a bootloader loop with no OS. It still had an Unlocked bootloader with S-Off. Once it was in a bootloader loop I was able to download a custom recovery via fastboot commands, the phone can now go into TWRP but it will only boot version 2.7.0.0 - earlier versions don't boot at all and newer versions will boot but are non-responsive/have no display.
Once in TWRP 2.7.0.0 I use push command from adb to load a stock android RUU zip into my MicroSD, I attempt to flash it via TWRP 2.7.0.0 but get a failed response. I have cleared everything and TWRP 2.7.0.0 is having trouble mounting /data/. I tried using using push command through adb to put a newer version of TWRP on my MicroSD so that TWRP could flash it but TWRP was unable to do so. Any version of Clockwork Mod has been unsuccessful to boot.
Essentially TWRP 2.7.0.0 can't flash anything or mount anything for me, I believe I need either a newer version or a different recovery, but no other recovery or twrp version seems to be able to boot correctly.
Any tips, advice, or general help would be extremely appreciated. I try to help myself before asking others and I don't know what else I can do, I have searched the forums for every relevant thread possible and tried many many things to get this to work with no success. Thank you for reading.
Click to expand...
Click to collapse
If you ask me
since i have s-off I would just change my mid and cid to dev edition then flash dev end ruu.
Gitnerd said:
I have a soft-bricked HTC One M8, It happened when I was attempting to return the phone to stock android with stock kernel and stock recovery while relocking the bootloader, none of that is really important though what happened is I had a bad flash and the phone got put into a bootloader loop with no OS. It still had an Unlocked bootloader with S-Off. Once it was in a bootloader loop I was able to download a custom recovery via fastboot commands, the phone can now go into TWRP but it will only boot version 2.7.0.0 - earlier versions don't boot at all and newer versions will boot but are non-responsive/have no display.
Once in TWRP 2.7.0.0 I use push command from adb to load a stock android RUU zip into my MicroSD, I attempt to flash it via TWRP 2.7.0.0 but get a failed response. I have cleared everything and TWRP 2.7.0.0 is having trouble mounting /data/. I tried using using push command through adb to put a newer version of TWRP on my MicroSD so that TWRP could flash it but TWRP was unable to do so. Any version of Clockwork Mod has been unsuccessful to boot.
Essentially TWRP 2.7.0.0 can't flash anything or mount anything for me, I believe I need either a newer version or a different recovery, but no other recovery or twrp version seems to be able to boot correctly.
Any tips, advice, or general help would be extremely appreciated. I try to help myself before asking others and I don't know what else I can do, I have searched the forums for every relevant thread possible and tried many many things to get this to work with no success. Thank you for reading.
Click to expand...
Click to collapse
That's not how to flash an RUU.zip
This is how it is done.
Make sure that your extSD is formatted to FAT32 first. It won't work otherwise.
After the format, rename the zip to 0P6BIMG.zip (that's a zero, not the letter) and place it onto the root of your card.
Boot into bootloader (Turn off you phone, then boot it up while holding power + vol down) and select hboot if it doesn't do that automatically.
Follow the prompts (vol up to flash ~ power to reboot)
That's it. Super easy.
Make sure to delete the renamed file from your extSD, otherwise every time you boot to hboot, it'll try to update again.
xunholyx said:
That's not how to flash an RUU.zip
This is how it is done.
Make sure that your extSD is formatted to FAT32 first. It won't work otherwise.
After the format, rename the zip to 0P6BIMG.zip (that's a zero, not the letter) and place it onto the root of your card.
Boot into bootloader (Turn off you phone, then boot it up while holding power + vol down) and select hboot if it doesn't do that automatically.
Follow the prompts (vol up to flash ~ power to reboot)
That's it. Super easy.
Make sure to delete the renamed file from your extSD, otherwise every time you boot to hboot, it'll try to update again.
Click to expand...
Click to collapse
Hello, thank you for your reply, I was traveling for holidays and have been working on the phone for the past couple of days and have run into alot of trouble doing what you say here, any help would be greatly appreciated I'm at the end of my rope with this phone. I got the 0P6BIMG.zip RUU and loaded it onto my Fat.32 formatted SD Card , I loaded the card into the phone and followed the fastboot options to flash, it recognized the RUU and attempted to flash it but said the model ID was incorrect. I opened up the zip and sure enough the android-info.txt file in the RUU does not list my model number and I cannot put my model number into it because it is an htc encrypted zip that will not let me change the file properties of the archive. I thought about trying to put the HTC into developer kernel so that my model ID would line up with that of the RUU info file but I did something (don't know what I did) and now fastboot won't even recognize the device (fastboot devices command shows nothing when phone is in fastboot USB mode).
My mid is 0P6B20000
My cid is VZW_001
Gitnerd said:
Hello, thank you for your reply, I was traveling for holidays and have been working on the phone for the past couple of days and have run into alot of trouble doing what you say here, any help would be greatly appreciated I'm at the end of my rope with this phone. I got the 0P6BIMG.zip RUU and loaded it onto my Fat.32 formatted SD Card , I loaded the card into the phone and followed the fastboot options to flash, it recognized the RUU and attempted to flash it but said the model ID was incorrect. I opened up the zip and sure enough the android-info.txt file in the RUU does not list my model number and I cannot put my model number into it because it is an htc encrypted zip that will not let me change the file properties of the archive. I thought about trying to put the HTC into developer kernel so that my model ID would line up with that of the RUU info file but I did something (don't know what I did) and now fastboot won't even recognize the device (fastboot devices command shows nothing when phone is in fastboot USB mode).
My mid is 0P6B20000
My cid is VZW_001
Click to expand...
Click to collapse
You need to use this RUU.zip
It is for the Verizon model
xunholyx said:
You need to use this RUU.zip
It is for the Verizon model
Click to expand...
Click to collapse
My goodness, I looked for this RUU everywhere, I would type in my mid and cid into google, I checked the One m8 archive of RUU's in that XDA thread, I couldn't find it. I don't know how you did, but you just saved my phone! Im booted into Android 4.4.2, receiving texts and everything. I'll figure out if I'm safe to update android later, I'm just so happy to have a working phone again. I gave you a thanks but do you have a contribution link or anything I could give to? You have helped me out tremendously.
Gitnerd said:
My goodness, I looked for this RUU everywhere, I would type in my mid and cid into google, I checked the One m8 archive of RUU's in that XDA thread, I couldn't find it. I don't know how you did, but you just saved my phone! Im booted into Android 4.4.2, receiving texts and everything. I'll figure out if I'm safe to update android later, I'm just so happy to have a working phone again. I gave you a thanks but do you have a contribution link or anything I could give to? You have helped me out tremendously.
Click to expand...
Click to collapse
I gave you an old RUU link. Sorry.
You can get the 5.0.1 RUU.zip from here if you want to update. It would be good to do it now, since running the RUU wipes your device, and yours is already wiped.
I've sent a PM with a donation link.
Thank you!
Long story short, I made my phone bricked with a small mistake:
I had Freedom OS (latest build) and then tried to flash Miui rom. To do so, I needed to flash back to official Hygrogen/Oxygen OS (MM). The mistake I made was to lock bootloader first. Then, phone got into bootloop....I searched and found Qualcomm software can revive any Qualcomm phone. I downloaded Qualcomm app and driver for Oneplus 3 and tried reviving my phone....What happened finally was that the phone was restarted and a screen showing Cache failed, System failed, userdata failed appeared. I tried to find Cache, system img ...of OOS 4.02 to flash separately....while I couldn't find them anywhere...I just tried fastboot flashing a recovery (both official and TWRP) but got error that partition doesn't allow writing (I guess because phone is locked now)....anyway, phone can boot only in fastboot and I wonder what else I can do....
Any help is very much appreciated!
alireza.nasibi said:
Long story short, I made my phone bricked with a small mistake:
I had Freedom OS (latest build) and then tried to flash Miui rom. To do so, I needed to flash back to official Hygrogen/Oxygen OS (MM). The mistake I made was to lock bootloader first. Then, phone got into bootloop....I searched and found Qualcomm software can revive any Qualcomm phone. I downloaded Qualcomm app and driver for Oneplus 3 and tried reviving my phone....What happened finally was that the phone was restarted and a screen showing Cache failed, System failed, userdata failed appeared. I tried to find Cache, system img ...of OOS 4.02 to flash separately....while I couldn't find them anywhere...I just tried fastboot flashing a recovery (both official and TWRP) but got error that partition doesn't allow writing (I guess because phone is locked now)....anyway, phone can boot only in fastboot and I wonder what else I can do....
Any help is very much appreciated!
Click to expand...
Click to collapse
Try this method now it will work
https://forum.xda-developers.com/showpost.php?p=68245482&postcount=111
The point is I can't flash anything on any partition as phone is locked and can't be unlocked!
alireza.nasibi said:
The point is I can't flash anything on any partition as phone is locked and can't be unlocked!
Click to expand...
Click to collapse
If you can access fastboot mode then you can definitely flash by other method
abhi0502 said:
If you can access fastboot mode then you can definitely flash by other method
Click to expand...
Click to collapse
you mean the 2nd method?
You said you lock the bootloader in 5th line, in order to flash any recovery you need to unlock bootloader again.
I also tried to lock bootloader last week and then my op3 got bricked with bootloop.
-First get into fastboot and unlock bootloader this will wipe your all data including you saved ROM files.
- after this flash TWRP or OnePlus recovery and sideload OOS ROM. Or transfer the ROM file using mtp in TWRP recovery.
- then you can easily do anything you want. Don't relock bootloader.
Those red things on your screen basically means your phone misses partitions, without these partitions it doesn't boot duhh.
If method 2 of the unbrick tool doesn't work, you can manually flash those files in Fastboot, the program has a folder that has all partitions like, cache.img, boot.img etc. I've been here as well nothing to worry about just keep us updated so we can help you
There's no mention in your post on which unbrick method you used. Was it first or second? By the looks of the end result, it was the first.
Just follow the same steps, but use method 2, that should leave you with a phone like out of the factory. Afterwards, you can simply set it up and let it update through OTA if you want to remain stock, or simply unlock bootloader, flash TWRP and flash whatever you want.
use the second method. the file you have to download contains all the raw room and when you follow the process, it would work. happened to me two times and i used this method
Just simply use fastboot oem unlock in fastboot mode then flash a recovery via fastboot flash recovery then go to recovery and once wipe all the partions and install a rom and then tried booting
Thank you all for your time and support. Method 2 saved my phone!
Ok, first off, I have everything I needed installed, I have a Verizon model, its unlocked, rooted, etc... did all that good stuff and was running great.
Problem I'm having now is, well that last thing I done was installed 7.1.2 which was a week or so ago. I'm still running stock but now I noticed I try and go to recovery and I get a No Command, so I figured TWRP for some reason didn't get installed again.
Its crazy and confusing how twrp installs but erases supersu, then supersu installs but erases twrp or whatever, I don't understand that at all. so I'm figuring that's what happened and twrp is not installed considering I'm getting the "No Command" when I try to enter recovery, correct??
Next, I got my phone connected to computer through usb and ADB see its fine as long as the phone is ON, when I reboot to bootloader, ADB doesn't see that phone any more.
What I was planning on doing was reinstalling twrp so I have a recovery, but I cant do that if ADB isn't seeing my phone. So I'm kind of stuck at the moment, I tried updating drivers, blah bla
and don't know what else to try so I figured Id post here again.
If twrp is installed and the no command is something else please help me through to get it back to where I need it to be, I appreciate it.
Thanks!
I think when you're in bootloader you have to use fastboot instead of adb. Try "fastboot devices" and see if it lists anything. You may also need to unplug/replug the USB cable after the phone reboots.
Sent from my Pixel XL using Tapatalk
disco1224 said:
Ok, first off, I have everything I needed installed, I have a Verizon model, its unlocked, rooted, etc... did all that good stuff and was running great.
Problem I'm having now is, well that last thing I done was installed 7.1.2 which was a week or so ago. I'm still running stock but now I noticed I try and go to recovery and I get a No Command, so I figured TWRP for some reason didn't get installed again.
Its crazy and confusing how twrp installs but erases supersu, then supersu installs but erases twrp or whatever, I don't understand that at all. so I'm figuring that's what happened and twrp is not installed considering I'm getting the "No Command" when I try to enter recovery, correct??
Next, I got my phone connected to computer through usb and ADB see its fine as long as the phone is ON, when I reboot to bootloader, ADB doesn't see that phone any more.
What I was planning on doing was reinstalling twrp so I have a recovery, but I cant do that if ADB isn't seeing my phone. So I'm kind of stuck at the moment, I tried updating drivers, blah bla
and don't know what else to try so I figured Id post here again.
If twrp is installed and the no command is something else please help me through to get it back to where I need it to be, I appreciate it.
Thanks!
Click to expand...
Click to collapse
Hello,
@stevexyz0 statement is correct, you have to use fastboot commands in bootloader...
You said you installed 7.1.2
How did you proceed? OTA, flash-all method? TWRP likely got overwritten by stock 7.1.2 boot.img since recovery is now part of the boot.img...
If you want to reinstall TWRP and root, proceed this way:
Download SuperSU and place it in the root of internal storage
https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
Download TWRP IMG and ZIP RC1:
https://dl.twrp.me/marlin/twrp-3.0.2-0-RC1-fastboot-marlin.img
https://dl.twrp.me/marlin/twrp-pixel-installer-marlin-3.0.2-0-RC1.zip
Place the zip in the root of internal storage
Reboot to bootloader,
Open a command prompt and Boot TWRP RC1 IMG:
fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img
Once your phone is in TWRP, choose install and install twrp-pixel-installer-marlin-3.0.2-0-RC1.zip
After that, install SuperSU zip.
Reboot, done.
Cheers...