Database Develop

[Q] So I wiped System in TWRP...

Like an idiot I wiped my System inside TWRP. Using TWRP 2.6.0.2
Earlier tonight my phone starting rebooting. I was inside GooManager and tapped reboot to recovery. When I did that, for some reason my phone lost root. Meaning when I went to reboot inside TWRP it stated that it looks as if my phone is not rooted. I rebooted anyway without installing SuperSU through TWRP. I was already rooted. Afterwards, it would boot up fine but kept constantly rebooting only after a minute or two.
I went back into TWRP and clicked through dalvik wipe and cache wipe. Still got reboots. I was planning on flashing CyanogenMod anyways so I thought I'd go on and wipe everything. I went in to advance wipe and check everything. As I swiped the slider to wipe I realized I checked System too, but it was too late.
Now my phone won't boot past the HTC logo with the red text underneath. I can boot into TWRP however so I hope all is not lost. I am currently at work so I have no way to try anything on the phone at the moment but was hoping for some advice on what to try later when I get home.
I'm thinking maybe I'll be able to use the "Mount" tab in TWRP to load a ROM on and flash and everything will be well again. Would I mistaken to think that? If not, I'll purchase an USB OTG cable and use a USB stick but I really need this up an running as quickly as possible.
Also, does anyone think it would be best just to go back to stock at this point (if I can) and start from scratch?
Much thanks for your help and advice,
dgb1891

So, oddly enough I did the same thing, How I managed to recover it so you can adb sideload a rom from TWRP and have access to a "working" phone again was to find your stock recovery.img, then flash it via fastboot, and then from the hboot menu, choose factory reset and let the stock recovery do it's thing, then reflash TWRP (I honestly like CWM doe) and adb sideload a rom (presumably what you were using before). It SHOULD fix your problem and you'll be able to mount files again.

hayame said:
So, oddly enough I did the same thing, How I managed to recover it so you can adb sideload a rom from TWRP and have access to a "working" phone again was to find your stock recovery.img, then flash it via fastboot, and then from the hboot menu, choose factory reset and let the stock recovery do it's thing, then reflash TWRP (I honestly like CWM doe) and adb sideload a rom (presumably what you were using before). It SHOULD fix your problem and you'll be able to mount files again.
Click to expand...
Click to collapse
By stock recovery.img you mean a stock HTC image? - or do you mean a recovery like TWRP or CWM?

dgb1891 said:
By stock recovery.img you mean a stock HTC image? - or do you mean a recovery like TWRP or CWM?
Click to expand...
Click to collapse
Literally stock recovery.img, not TWRP or CWM.

hayame said:
Literally stock recovery.img, not TWRP or CWM.
Click to expand...
Click to collapse
K. Thanks. I have a feeling this is going to be a bit more complicated than I first thought...

I followed what you suggested and got the phone back up and working. Thanks again.

[Q] [RESOLVED] Lollipop OTA update aborted

Hi all.
This is a moment that I'm disconnected hacks because I am in stock (6.0.401.11) and satisfied. I had OTA updates without problems until this kitkat version but today after receiving and downloading 2 times the OTA lollipop I can not install it because installation starts well and some moments later, the screen is stuck on the phone with red triangle and I have this in the recovery:
Verifying current system ...
"/ System / bin / reboot" has unexpected content
Installation aborted
Even when I do it manually, it's the same. Yet I have just manually switch successfully 6.0.401.12 that I missed somehow.
What's the trouble?

kamso said:
Hi all.
This is a moment that I'm disconnected hacks because I am in stock (6.0.401.11) and satisfied. I had OTA updates without problems until this kitkat version but today after receiving and downloading 2 times the OTA lollipop I can not install it because installation starts well and some moments later, the screen is stuck on the phone with red triangle and I have this in the recovery:
Verifying current system ...
"/ System / bin / reboot" has unexpected content
Installation aborted
Even when I do it manually, it's the same. Yet I have just manually switch successfully 6.0.401.12 that I missed somehow.
What's the trouble?
Click to expand...
Click to collapse
this says to me, in system/bin you have modified files, you must be 100% stock so flash TWRP recovery then use this: https://www.androidfilehost.com/?fid=95864024717072880 to retore full stock rom.
DO NOT try and root or anything, 100% pure stock required.
Full Reboot into android
boot back to recovery and flash this pre-load data here: https://www.androidfilehost.com/?fid=95864024717072879
Full reboot into android
You will need TWRP recovery for both of the above files, but you will also need to flash stock recovery afterwards to update which is here: https://www.androidfilehost.com/?fid=95864024717072472
fastboot flash recovery
fastboot erase cache
fastboot reboot-bootloader
full reboot into android, then update.
DO NOT try and root or anything, 100% pure stock required.

Seanie280672 said:
this says to me, in system/bin you have modified files, you must be 100% stock so flash TWRP recovery then use this: https://www.androidfilehost.com/?fid=95864024717072880 to retore full stock rom.
DO NOT try and root or anything, 100% pure stock required.
Full Reboot into android
boot back to recovery and flash this pre-load data here: https://www.androidfilehost.com/?fid=95864024717072879
Full reboot into android
You will need TWRP recovery for both of the above files, but you will also need to flash stock recovery afterwards to update which is here: https://www.androidfilehost.com/?fid=95864024717072472
fastboot flash recovery
fastboot erase cache
fastboot reboot-bootloader
full reboot into android, then update.
DO NOT try and root or anything, 100% pure stock required.
Click to expand...
Click to collapse
Ok, thank you. But what I don't understand is that there's a long time I'm no more root, I'm full stock (Rom, recovery...), only S-off and Unlocked. So Why for previous OTA updates I have not had this problem? Why I have to manually update successfully from 6.09.401.11 version to 6.09.401.12 one? Why it is only the upgrade to the Lollipop which has problem?
What is the preload data? I already have this: https://www.androidfilehost.com/?w=...0f40a2a319761577a4c3f1e723594b05669cb009e9d00
Can I flash it and the stock recovery only?

Your problem is the lack or corruption of the file /bin/reboot
2 solutions:
Flash a custom recovery and reflash the rom
Flash a custom recovery and replace the file

migascalp said:
Your problem is the lack or corruption of the file /bin/reboot
2 solutions:
Flash a custom recovery and reflash the rom
Flash a custom recovery and replace the file
Click to expand...
Click to collapse
Ok thanks. I'm downloading the Rom and I have to flash it through TWRP, flash stock recovery and try OTA update again.

kamso said:
Ok thanks. I'm downloading the Rom and I have to flash it through TWRP, flash stock recovery and try OTA update again.
Click to expand...
Click to collapse
preload data is HTC's little hidden way of stopping you getting OTA's if you unlock your bootloader, and yes it is required to update, without it, updates will fail.

Seanie280672 said:
preload data is HTC's little hidden way of stopping you getting OTA's if you unlock your bootloader, and yes it is required to update, without it, updates will fail.
Click to expand...
Click to collapse
Ah Ok I understand. These are applications that disappear when we unlock the bootloader. I had already installed them there's a long time. As I said my OTA updates passed without problem.

Problem flashing stock Rom in TWRP:
"- Zip signature verification failed
- Error flashing zip"
I don't understand anything, what's happen?

Problem solved and phone updated. Thank you!!!

recovery will not stick on 6.0.1

I was having issues and wanted to switch to the systemless SU so I decided to start over fresh. used toolkit to restore stock image and unrooted. tried to install newest twrp using toolkit but it kept coming up with bugdroid with red triangle and exclamation mark. Did some research and few places said you have to go back to lp. so I downloaded factory image and went back to lp unrooted and locked bootloader. unlocked, rooted and installed twrp everything was good. I extracted the newest 6.0.1 factory image and installed each component separately except for the recovery. now I am on 6.0.1 and try to go to recovery and bugdroid with red triangle and using toolkit I cannot get the newest twrp to stick. my sdk is updated.
any ideas on what to do?
thanks

jdpeck said:
I was having issues and wanted to switch to the systemless SU so I decided to start over fresh. used toolkit to restore stock image and unrooted. tried to install newest twrp using toolkit but it kept coming up with bugdroid with red triangle and exclamation mark. Did some research and few places said you have to go back to lp. so I downloaded factory image and went back to lp unrooted and locked bootloader. unlocked, rooted and installed twrp everything was good. I extracted the newest 6.0.1 factory image and installed each component separately except for the recovery. now I am on 6.0.1 and try to go to recovery and bugdroid with red triangle and using toolkit I cannot get the newest twrp to stick. my sdk is updated.
any ideas on what to do?
thanks
Click to expand...
Click to collapse
Never trust a recovery installed by a tool kit. Grab the recovery img from the site and flash it manually.

all i have now is stock recovery. whats the best way to manually install twrp

go into fastboot and flash it. you have to be in your bootloader to flash via fastboot. you put the file in the same window as your fastboot program, then type.. fastboot flash recovery recoveryname.img, and that will flash twrp. if you type fastboot boot recovery recoveryname.img then itll only boot into recovery one time, thats what your toolkit did.

Wugfresh Toolkit works great for me and I used it for 6.0.1
Make sure you flash permrecovery file provided by the toolkit, it prompts this during the steps.
If the copies of factory img or recovery provided by the toolkit are not working one easy way is download your own, the toolkit allows you to use your own files and not the one it obtains.
jdpeck said:
I was having issues and wanted to switch to the systemless SU so I decided to start over fresh. used toolkit to restore stock image and unrooted. tried to install newest twrp using toolkit but it kept coming up with bugdroid with red triangle and exclamation mark. Did some research and few places said you have to go back to lp. so I downloaded factory image and went back to lp unrooted and locked bootloader. unlocked, rooted and installed twrp everything was good. I extracted the newest 6.0.1 factory image and installed each component separately except for the recovery. now I am on 6.0.1 and try to go to recovery and bugdroid with red triangle and using toolkit I cannot get the newest twrp to stick. my sdk is updated.
any ideas on what to do?
thanks
Click to expand...
Click to collapse

Don't use toolkits. I recommend yoiu follow @simms22's solution.
Sent from my Nexus 6 running cyosp using Tapatalk

when you have root, you can always use an app, like flashify, to flash twrp recovery. but you need to have root first.

arcane spade said:
Wugfresh Toolkit works great for me and I used it for 6.0.1
Make sure you flash permrecovery file provided by the toolkit, it prompts this during the steps.
If the copies of factory img or recovery provided by the toolkit are not working one easy way is download your own, the toolkit allows you to use your own files and not the one it obtains.
Click to expand...
Click to collapse
I have tried with and without perm recovery checked, I had the newest twrp img file so I choose other and selected it, I even used the option for one time recovery boot with twrp and then flashed twrp within it like I was updating twrp and still nothing. I am going to try fast boot itself without the tool kit.
Is there any other part of the stock factory image that would update the recovery? I didn't install it coming from lp but it still went back to stock instead of staying on twrp

jdpeck said:
I have tried with and without perm recovery checked, I had the newest twrp img file so I choose other and selected it, I even used the option for one time recovery boot with twrp and then flashed twrp within it like I was updating twrp and still nothing. I am going to try fast boot itself without the tool kit.
Is there any other part of the stock factory image that would update the recovery? I didn't install it coming from lp but it still went back to stock instead of staying on twrp
Click to expand...
Click to collapse
no. but when you flash the full factory image, stock recovery will replace twrp. if you just want to update, flashing the system.umg and boot.img will work, and youll keep twrp.

This is why we don't use toolkits.
Boot to bootloader mode
Code:
fastboot flash recovery <recovery filename>
Where <recovery filename> is the path and filename of the twrp image you downloaded
After flashing use the arrow keys to boot into your newly installed recovery
Take a backup of your phone
Use recovery to boot android
Reboot to recovery with custom power menu options, or by opening a console on your phone and typing in reboot recovery
Post here to tell me that I am right, and thank me.
If you don't reboot to recovery from the bootloader, it will likely be restored back to the OEM recovery.

scryan said:
This is why we don't use toolkits.
Boot to bootloader mode
Code:
fastboot flash recovery <recovery filename>
Where <recovery filename> is the path and filename of the twrp image you downloaded
After flashing use the arrow keys to boot into your newly installed recovery
Take a backup of your phone
Use recovery to boot android
Reboot to recovery with custom power menu options, or by opening a console on your phone and typing in reboot recovery
Post here to tell me that I am right, and thank me.
If you don't reboot to recovery from the bootloader, it will likely be restored back to the OEM recovery.
Click to expand...
Click to collapse
well, thats how you should flash recovery. but its not the reason that we dont use toolkits. we dont use toolkits for several reasons.. 1. they mess up 2. doing it properly is just as fast if not faster 3. newbs think that toolkits are made for them to use. well, they are wrong. toolkits teach you absolutely nothing, which is the worst for beginners.

simms22 said:
no. but when you flash the full factory image, stock recovery will replace twrp. if you just want to update, flashing the system.umg and boot.img will work, and youll keep twrp.
Click to expand...
Click to collapse
thats why after going to lp and getting twrp working I flashed system, boot, and newest radio independently and skipped over recovery but for some reason it reverted back.
just using fastboot by itself worked great thanks for the help

jdpeck said:
thats why after going to lp and getting twrp working I flashed system, boot, and newest radio independently and skipped over recovery but for some reason it reverted back.
just using fastboot by itself worked great thanks for the help
Click to expand...
Click to collapse
if you skipped the recovery.img, your recovery should have stayed.. oh, never mind, i just remembered a file that you need to remove after the first boot, or itll install the stock recovery after the first reboot. its called recovery-from-boot.bak. if you remove that on first boot, youll be fine

TWRP not flashing

I have been having an issue flashing TWRP. I have previously had TWRP on my Nexus 6, but I recently flashed the latest security update, and now for the life of me, I cannot get TWRP to flash.
I run fastboot flash recovery twrp-3.0.2-0-shamu.img, it says it ran OKAY, I reboot the phone, then use ADB reboot recovery but it always comes back to the stock recovery. I have done this a hundred times, and never had an issue. Anyone else seen this?

lenard_hester said:
I have been having an issue flashing TWRP. I have previously had TWRP on my Nexus 6, but I recently flashed the latest security update, and now for the life of me, I cannot get TWRP to flash.
I run fastboot flash recovery twrp-3.0.2-0-shamu.img, it says it ran OKAY, I reboot the phone, then use ADB reboot recovery but it always comes back to the stock recovery. I have done this a hundred times, and never had an issue. Anyone else seen this?
Click to expand...
Click to collapse
boot up first, remove some system apps to clear up some space, then flash again with fastboot.

simms22 said:
boot up first, remove some system apps to clear up some space, then flash again with fastboot.
Click to expand...
Click to collapse
I can't remove any system apps. I need to have root first, and I need TWRP to install root. Besides, TWRP goes on the recovery partition not the system partition.

lenard_hester said:
I can't remove any system apps. I need to have root first, and I need TWRP to install root. Besides, TWRP goes on the recovery partition not the system partition.
Click to expand...
Click to collapse
true. you are using fastboot while you are in the bootloader?

simms22 said:
true. you are using fastboot while you are in the bootloader?
Click to expand...
Click to collapse
yes. I think I figured out a way around it. my mistake was rebooting. Instead of rebooting from the bootloader, I just went to recovery mode directly from there and TWRP booted right up.

lenard_hester said:
yes. I think I figured out a way around it. my mistake was rebooting. Instead of rebooting from the bootloader, I just went to recovery mode directly from there and TWRP booted right up.
Click to expand...
Click to collapse
I think you have to rename stock recovery files or when you reboot it will reinstall stock recovery.

cajun9924 said:
I think you have to rename stock recovery files or when you reboot it will reinstall stock recovery.
Click to expand...
Click to collapse
that is true, if the op is running stock android. or you can just delete that one file in /system/.

I don't want the OTA, I just want to boot my phone

I accidentally downloaded the OTA. Now it boots into TWRP (3.02) and stops. I can flash a ROM and I can restore a backup but it still boots to TWRP.
Any way to load some system without having to flash stock?

Yeah you can download the stock image, extract it, and "fastboot flash system system.img"

fakecharles said:
I accidentally downloaded the OTA. Now it boots into TWRP (3.02) and stops. I can flash a ROM and I can restore a backup but it still boots to TWRP.
Any way to load some system without having to flash stock?
Click to expand...
Click to collapse
It would be good to know if your problem is resolved - it would save me the effort of typing this, for a start.
The simplest way is to download the OTA to your PC and sideload it. If you're already in TWRP there is a button which allows you to sideload via ADB.
Edit: Sorry, I see you say "not stock". Downloading the OTA doesn't do anything - I guess that you tried to install it? Which ROM were you on before you did this? And you know that there's a newer TWRP - 3.1?

I did resolve it. I found some instruction I could tie in the terminal. Sorry, I don't have a link.