[Q] Can't flash any CWM through TWRP - TouchPad Q&A, Help & Troubleshooting

I don't remember if I deleted it or what but I only have TWRP 2.6.1 on my device as a recovery and I would like to reinstall CWM on my device. However, every "flashable" CWM zip I have tried through TWRP has failed and I'm not sure why. Don't nwant to brick my device and don't necessarily want to WebOS doctor it if I can avoid it, as my device has run fairly well (I am on 4.2.2). Any/all help is appreciated. Thanks!

I'm guessing that TWRP doesn't support flashing another recovery from it. Have you tried flashing recovery image from fastboot?

bananagranola said:
I'm guessing that TWRP doesn't support flashing another recovery from it. Have you tried flashing recovery image from fastboot?
Click to expand...
Click to collapse
Not yet, although I managed to get a workable CWM running by moving an image to the boot folder and then updating to the latest working version (couldn't get the "touch" version to work via touch, however).
However, I may try flashing via fastboot if something unexpected happens. Thanks for the help

Related

[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.

T stuck in recovery mode,ROM not installing,5% battery.

So I decided to install cyanogenmod WhiteNeo ROM on my xperia T
did the entire process alright.
for recovery, CWM din't work so downloaded app from playsore and got TWRP from there.
the followed the steps from here to reach till step 8 from wiki.cyanogen guide.
stuck at step 8. DOn't get how to perform it because it is confusing.
altenrately sentthe zip package to sd card and tried there but says Error executing updater binary in zip.
I am stuck.
5%battery left.
and I dont know what to do.
can't even get out of Recovery mode.
device is unresponsive when connected to USB and is powered off.
can anyone please sort this out and explain in simple words how to get out of this mess?
p.s: if battery expires,then what happens?
tried installing stock firmware using flashtool
but
07/014/2015 19:14:54 - ERROR - Error in processHeader
all the time
googled all the solutions
none works
help please?
You should be able to flash official CM12 and proceed from there.
First, revert to stock FOTAKernel, then flash my ROM's boot.img via Fastboot mode in Flashtool. Then reboot to TWRP and check versions. Should be 2.8.7.0.
Then flash the ROM zip, gapps and supersu. Done.
WhiteNeo said:
You should be able to flash official CM12 and proceed from there.
First, revert to stock FOTAKernel, then flash my ROM's boot.img via Fastboot mode in Flashtool. Then reboot to TWRP and check versions. Should be 2.8.7.0.
Then flash the ROM zip, gapps and supersu. Done.
Click to expand...
Click to collapse
Thankyou soo much!
could you just elaborate a bit on how to revert to stock FOTA kernel and check TWRP version. confused about that.
btw... how do I use CM recovery instead of TWRP?
also if you have time.
another issue
before you posted this, I already flashed CM12 official, it works fine. But I am having an issue flashing gapps.
have tried
gapps-L-4-21-15.zip
pa_gapps-stock-5.0.1-20150215-signed (1).zip
gapps-lp-20141212-signed (1).zip
For installing
proceeded to install through sdcard and in recovery mode.
installs fine.
as soon as phone starts, google errors(stopped working) start spamming the screen and pressing ok just causes more to come.
reset all to factory version, reinstalled cyanogenmod with gapps, still no good.
can you point out the correct process for it or where am I going wrong.
aber96crombie said:
Thankyou soo much!
could you just elaborate a bit on how to revert to stock FOTA kernel and check TWRP version. confused about that.
btw... how do I use CM recovery instead of TWRP?
also if you have time.
another issue
before you posted this, I already flashed CM12 official, it works fine. But I am having an issue flashing gapps.
have tried
gapps-L-4-21-15.zip
pa_gapps-stock-5.0.1-20150215-signed (1).zip
gapps-lp-20141212-signed (1).zip
For installing
proceeded to install through sdcard and in recovery mode.
installs fine.
as soon as phone starts, google errors(stopped working) start spamming the screen and pressing ok just causes more to come.
reset all to factory version, reinstalled cyanogenmod with gapps, still no good.
can you point out the correct process for it or where am I going wrong.
Click to expand...
Click to collapse
Reverting to stock FOTA and getting official CM recovery (which won't flash anything but official CM builds and gapps) can be done with flashtool and a suitable ftf or using a Terminal command that you will find on the last pages of my CM12.1 thread for Xperia T.
TWRP version should be visible in settings or what one would call a "status bar".
And the force-closing gapps are just the result of a broken or outdated recovery. I've already been reported the same issue after creating a FOTAKernel TWRP for a friend.
You should be able to flash official CM12 gapps from Cyanogen Recovery.. Just google those.

guys i flashed cm-13.0-20160528-NIGHTLY-huashan now error coming while installing app

teamwin recovery coming but its getting hang i tried the touch & switch not working.
im unable go back to my stock either to install gapps what should do
please help .........
device xepria sp
CJCHERO said:
teamwin recovery coming but its getting hang i tried the touch & switch not working.
im unable go back to my stock either to install gapps what should do
please help .........
device xepria sp
Click to expand...
Click to collapse
You get an error when installing app from playstore?
And about recovery,
Get "twrp-3.0.2-rXX-fota-huashan.zip" from here.
Extract it,
Flash the .img via fastboot mode,
Reboot your device, it'll boot directly into TWRP.
Flash the "twrp-3.0.2-rXX-fota-huashan.zip" again from there, this will install TWRP in the FOTA partition.
Then flash another ROM/ Restore any backup.
Zenith said:
You get an error when installing app from playstore?
And about recovery,
Get "twrp-3.0.2-rXX-fota-huashan.zip" from here.
Extract it,
Flash the .img via fastboot mode,
Reboot your device, it'll boot directly into TWRP.
Flash the "twrp-3.0.2-rXX-fota-huashan.zip" again from there, this will install TWRP in the FOTA partition.
Then flash another ROM/ Restore any backup.
Click to expand...
Click to collapse
Bro
I flashed cm 13 but when boots into recovery Twrp comes It gets stuck no touch n switch working.
Is a problem with cm 13 nighty .
I would really appreciate a very detailed story. Even if it is a tiny part of it which people often omit..
A detailed story may actually help others to analyse your current situation better Myself included

Requesting Oneplus 3t stock recovery

Does anyone have the default OP3t recovery.img?
The device cannot boot into any recovery versions I have installed (TWRP or the stock recovery). The only way to access TWRP is from ADB on my computer by typing "fastboot boot [twrp.img]".
Ive tried installing TWRP through ADB to see if flashing it again will mount it properly, but nothing has worked. I can boot into the OS still, but the only way to access recovery is (as i said) through ADB.
Anyone know how to fix this? I was thinking that reflashing the default recovery.img would fix this problem, but not overly sure about even that.
I tried to install the latest OTA patch from TWRP that people have been saying fixes the bootloader issues, but that left with "updater error 7".
nicnaknic said:
Does anyone have the default OP3t recovery.img?
The device cannot boot into any recovery versions I have installed (TWRP or the stock recovery). The only way to access TWRP is from ADB on my computer by typing "fastboot boot [twrp.img]".
Ive tried installing TWRP through ADB to see if flashing it again will mount it properly, but nothing has worked. I can boot into the OS still, but the only way to access recovery is (as i said) through ADB.
Anyone know how to fix this? I was thinking that reflashing the default recovery.img would fix this problem, but not overly sure about even that.
I tried to install the latest OTA patch from TWRP that people have been saying fixes the bootloader issues, but that left with "updater error 7".
Click to expand...
Click to collapse
I have it here: https://drive.google.com/drive/folders/0B4tnYt16-NAUQm02dHhDaWlyQUE
nicnaknic said:
Does anyone have the default OP3t recovery.img?
The device cannot boot into any recovery versions I have installed (TWRP or the stock recovery). The only way to access TWRP is from ADB on my computer by typing "fastboot boot [twrp.img]".
Ive tried installing TWRP through ADB to see if flashing it again will mount it properly, but nothing has worked. I can boot into the OS still, but the only way to access recovery is (as i said) through ADB.
Anyone know how to fix this? I was thinking that reflashing the default recovery.img would fix this problem, but not overly sure about even that.
I tried to install the latest OTA patch from TWRP that people have been saying fixes the bootloader issues, but that left with "updater error 7".
Click to expand...
Click to collapse
I believe if you re-lock your phone, the phone can factory reset and get re-flash stock recovery itself. btw,have you check the OTA zip file and make sure it was not damage when you downloaded it.
can you help me man i need that file but seems to be that link in not correct, can you give me the correct link pls i am stuck
Can't you just download the stock firmware and flash through ODIN? Then you will have stock recovery and everything.
EDIT:
Cancel my suggestion. ODIN is only for Samsung phones. My bad!
nicnaknic said:
Does anyone have the default OP3t recovery.img?
The device cannot boot into any recovery versions I have installed (TWRP or the stock recovery). The only way to access TWRP is from ADB on my computer by typing "fastboot boot [twrp.img]".
Ive tried installing TWRP through ADB to see if flashing it again will mount it properly, but nothing has worked. I can boot into the OS still, but the only way to access recovery is (as i said) through ADB.
Anyone know how to fix this? I was thinking that reflashing the default recovery.img would fix this problem, but not overly sure about even that.
I tried to install the latest OTA patch from TWRP that people have been saying fixes the bootloader issues, but that left with "updater error 7".
Click to expand...
Click to collapse
http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_3.5.4/
Scroll right to the bottom and look for oxygen recovery.
manor7777 said:
http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_3.5.4/
Scroll right to the bottom and look for oxygen recovery.
Click to expand...
Click to collapse
that link doesnt work, when i try to download it states no file attatched

Stuck in recovery after 4.0.1 OTA

Hi,
I was running Oxygen 4.0.0 and a beta build of TWRP 3.0.3 which works with new encryption. I used the android update mechanics to get the 4.0.1 OTA. System rebooted to recovery, recovery threw an error (zip file corrputed) and since then I am not able to boot the system. Whatever I do I land in TWRP recovery.
Things I did so far:
- Tried installing the full 4.0.1 zip. Install worked without errors, device still boots to recovery.
- Tried to get stock recovery, since another post (https://forum.xda-developers.com/oneplus-3t/help/stuck-recovery-mode-t3532524) indicates stock recovery might fix the problem
--> stock recovery is not obtainable anymore. Seems deleted from all the download links I could find. Example is here: https://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015
- Wipe cache and dalvik cache in the hopes, the instruction to boot to recovery is there somewhere.
I did not do the unbrick tool, since I run linux and didnt want to fiddle with windows yet.
I did make a nandroid backup, so once my system boots again I should be fine.
Any Idea where to either get a mirror of stock recovery or how to fix this problem otherwise?
I had this same problem, and I solved downloading the unbrick tool and extracting the recovery from there. Here is the file
https://drive.google.com/file/d/0BwaafKaXbak3d1RFblFOWVd5eGs/view?usp=sharing
Also locking the bootloader worked for me. Booted into system then unlocked again.
Thanks a lot for the stock recovery. That worked!
Once it booted, installing TWRP and SuperSU again.
mad-murdock said:
Thanks a lot for the stock recovery. That worked!
Once it booted, installing TWRP and SuperSU again.
Click to expand...
Click to collapse
Does your TWRP boot correctly? I flashed it and when I restarted I still had the stock recovery, so I used fastboot boot and it booted, but it is stuck in the loading screen.
Edit: After rebooting and reflashing totally random, it worked.
mariospizza said:
Does your TWRP boot correctly? I flashed it and when I restarted I still had the stock recovery, so I used fastboot boot and it booted, but it is stuck in the loading screen.
Edit: After rebooting and reflashing totally random, it worked.
Click to expand...
Click to collapse
Yeah, worked totally normal as it should.
My educated guess about this whole dilemma is, the system sets a flag to boot to recovery which TWRP doesn't clear and only stock recovery clears. Usually those flags should be in cache partition, but in this case isn't.
Tldr: don't use build in update mechanisms if you modified Rom and recovery.

Categories

Resources