Database Info

[Q] How to restore CWM recovery from TWRP terminal?

[SOLVED]
So after having my Transformer for some time now (unlocked, rooted, and running CROMI) it began to get sluggish. I wanted to upgrade to something else, and decided to try PA HALO http://forum.xda-developers.com/showthread.php?t=2376927
I missed something somewhere, prob the fact that I installed TWRP over my CWM that I had from long ago, instead of upgrading to the new CWM, or the fact that I'm still on the 10.4.4.25 bootloader. I rebooted into recovery, flashed the PA zip, rebooted into recovery, flashed the new GAPPS, and wiped the cache and Delvik. When I went to boot it up the "ParanoidAndroid3+" text and neon jellybean/fish thing show up, then nothing.
I (stupidly) did not make a new backup before doing this change (though there is one from my CWM, but TWRP doesn't seem to recognize it).
ADB does not seem to be working. When I select the USB icon, while using the power+volDown, I get the message "starting fastboot usb download protocol" and ADB does not see the device. If I let the device try and boot (when it gets stuck at the neon jb/fish) ADB sees the device, but gives the error <waiting for device> when I try and flash the new CWM. I seem to be able to access the terminal from TWRP, so I know there is a way to load the old CWM restore files, I just don't know how.
Help is needed.

found a way to do it, but I guess it took away my root when I flashed the new rom. Now I get "su is not recognized" from the terminal..... I'm downloading http://forum.xda-developers.com/showthread.php?t=2107271 and will try to get the os to boot. I can always re root the device, but I kinda need the device to boot into something first.

You missed quite a lot to get yourself into that pickle.
The second line of the PA thread reads:
GET THE LATEST BOOTLOADER AND RECOVERY
The link leads you to the CM 11 thread where it says in no uncertain terms that you need to be on the 10.6.1.14.4 or later bootloader. You think a 10.4.4.25 bootloader will run a JB 4.3 rom?
I hope you get it working.... Good luck

berndblb said:
You missed quite a lot to get yourself into that pickle.
The second line of the PA thread reads:
GET THE LATEST BOOTLOADER AND RECOVERY
The link leads you to the CM 11 thread where it says in no uncertain terms that you need to be on the 10.6.1.14.4 or later bootloader. You think a 10.4.4.25 bootloader will run a JB 4.3 rom?
I hope you get it working.... Good luck
Click to expand...
Click to collapse
Thanks for the kind kick to the nuts guy. I flashed the new bootloader (10.6.1.14.4) http://forum.xda-developers.com/showthread.php?t=2223918 that was already on the root of my tablet, downloaded GAPPS (4.2.2-4.3) http://forum.xda-developers.com/showthread.php?t=2405292 and placed it on MicroSD card, and already had the PA rom http://forum.xda-developers.com/showthread.php?t=2039557
Did some searching and came across a thread (can't find it now) that said to wipe before and after installing GAPPS.
It works now. The process went as follows:
1. Flash bootloader and reboot into recovery
2. Wipe cache/Delvik, flash GAPPS, wipe again
3. Flash rom
4. Reboot and wait for the rom to settle
Something is still wrong, or I'm not understanding the layout of PA, because I'm missing some options and buttons for some apps I've downloaded. I've made a back up with TWRP (for just in case), and am going to try getting CM 10.2 on there.

datboyc said:
Thanks for the kind kick to the nuts guy. I flashed the new bootloader (10.6.1.14.4) http://forum.xda-developers.com/showthread.php?t=2223918 that was already on the root of my tablet, downloaded GAPPS (4.2.2-4.3) http://forum.xda-developers.com/showthread.php?t=2405292 and placed it on MicroSD card, and already had the PA rom http://forum.xda-developers.com/showthread.php?t=2039557
Did some searching and came across a thread (can't find it now) that said to wipe before and after installing GAPPS.
It works now. The process went as follows:
1. Flash bootloader and reboot into recovery
2. Wipe cache/Delvik, flash GAPPS, wipe again
3. Flash rom
4. Reboot and wait for the rom to settle
Something is still wrong, or I'm not understanding the layout of PA, because I'm missing some options and buttons for some apps I've downloaded. I've made a back up with TWRP (for just in case), and am going to try getting CM 10.2 on there.
Click to expand...
Click to collapse
The "kick" was really meant as a friendly slap upside your head which was probably unnecessary since I hope you did that yourself already extensively - so I apologize
Glad you got it working :thumbup:

[Q] Can't flash TF101 (Rooted, TWRP2.7.0.1)

I have a rooted (Superuser 3.1.3) TF101 with TWRP 2.7.0.1. I HAD Katkiss 4.3 installed. One day the tablet locked up and then starting bootlooping. I went into recovery, wiped everything, did factory reset, format /system.
Then I tried to reflash Katkiss 4.3_020, it failed with "set_perm: some changes failed". I then tried katkiss 4.4.2_023c - it failed with a similar error message. Tried flashing stock (US_epad-user-9.2.1.27) - same thing. The first part of the error message for all three ROMs is the same set_perm failure. The next couple of lines gives different error messages depending on the ROM. Generally something like: "E: error executing updater binary in zip".
Now I have a tablet with no ROM on it (when I tried to boot it hangs at the ASUS screen). I can get into the TWRP recovery menu just fine - I can flash other things like superuser or gapps without error. But any ROM I try to flash gives the set_perm error.
Any thoughts?
Chris

Try using Easyflasher to flash a different version of TWRP in case recovery is the problem, TWRP builds newer than 2.3.2.3 are not official builds, they have been continued by another member here once the project was abandoned by the original team
http://forum.xda-developers.com/showthread.php?t=1688012
Use Easyflasher to flash TWRP again - then try flashing KatKiss #23

Thanks but...
Easyflasher doesn't seem to work for me anymore (odd because it is what I first used to root/update my TF101). It runs and declares success - but nothing gets pushed to my device. Tried both SBK1 and SBK2. Using universal naked 0.72 and 0.73 on win7 64 bit.
I tried to find an older version of TWRP like you suggested - but I couldn't. Seems they want you to use "goo manager" from the play store... which doesn't work for me since I can't boot... And the goo website doesn't list an older TWRP for my device.
In any case, the latest TWRP seems to work in every other respect. I read somewhere that superuser can set an "immutable" bit that can survive a wipe? If true - could that be my permissions problem?
Chris

stuck on load screen
*Detection* said:
Try using Easyflasher to flash a different version of TWRP in case recovery is the problem, TWRP builds newer than 2.3.2.3 are not official builds, they have been continued by another member here once the project was abandoned by the original team
http://forum.xda-developers.com/showthread.php?t=1688012
Use Easyflasher to flash TWRP again - then try flashing KatKiss #23
Click to expand...
Click to collapse
I'm new as one can get at this and likely deserve any hammering I may get....TF1010 B70, CWM 5.8.3.4, I know I missed a step somewhere. I can't recover to 4.3 as the back up was bad, not recognized by any computer, loops to recovery and holding power and vol dn the booting to the linuz get me a long (14 hrs) flashing KatKiss boot screen.
I've tried Easyflasher aswell with no results, Please, any hope for this thing, Thanks in advance!

Sounds like your problem is a bit different - can you get into your bootloader? After voldown+power you should see some small text in the upper left of the screen then immediately hit vol up.... From there you should be able to reflash any ROM...
ldwhyte said:
I'm new as one can get at this and likely deserve any hammering I may get....TF1010 B70, CWM 5.8.3.4, I know I missed a step somewhere. I can't recover to 4.3 as the back up was bad, not recognized by any computer, loops to recovery and holding power and vol dn the booting to the linuz get me a long (14 hrs) flashing KatKiss boot screen.
I've tried Easyflasher aswell with no results, Please, any hope for this thing, Thanks in advance!
Click to expand...
Click to collapse

ChrisG12 said:
Sounds like your problem is a bit different - can you get into your bootloader? After voldown+power you should see some small text in the upper left of the screen then immediately hit vol up.... From there you should be able to reflash any ROM...
Click to expand...
Click to collapse
Thanks for your reply, when I do use that button combo, it goes into the ClockworkMod Recovery v5.8.3.4, the native one seems to be gone.

Is that a bad thing? Once in ClockworkMod - you can install a new ROM (such as KatKiss or even go back to stock). Just find the right zip file on the web, copy to your sdcard and then in clockwork select that zip file to install.... Or am I missing something?
ldwhyte said:
Thanks for your reply, when I do use that button combo, it goes into the ClockworkMod Recovery v5.8.3.4, the native one seems to be gone.
Click to expand...
Click to collapse

Ok - back to my problem - I installed a new recovery and get the same error. The two recoveries I have tried are TWRP (2.3 and 2.7.0.1) and cwm-6.0.2.1-notouch-hybrid. Both seem to work fine (and I had no trouble previously with my device running TWRP and Katkiss 4.3).
After a crash I needed to reinstall a ROM. I've copied four ROMs to my sdcard (Katkiss 4.3, Katkiss 4.4.2, Omni 4.4.2, and stock asus). I've tried all 4 ROMs with both recoveries. I get the same error when I try to install the zips. Usually it is "set_perm: some changes failed". Though stock asus zip fails with a different message "Assert failed: package_extract_file(“blob”, “/tmp/blob”)".
Any ideas on what is keeping a recovery from installing the zip? Note they can install other zips fine (i.e. other recoveries, superuser, gapps, etc.). But not the ROM.

ChrisG12 said:
Is that a bad thing? Once in ClockworkMod - you can install a new ROM (such as KatKiss or even go back to stock). Just find the right zip file on the web, copy to your sdcard and then in clockwork select that zip file to install.... Or am I missing something?
Click to expand...
Click to collapse
No it's not, but I can't get anything onto the SD card, only the ext card and I CWM will not mount it to flash from. if I'm missing something and I sure I am, Im greatful for any help, and thanks again..

[Q] Can't install TWRP recovery

Can anyone tell me how I flash a recovery to the device from a zip file? Going into CWM and flashing the TWRP recovery initially seems to work, but if I then interrupt the reboot and go straight into recovery, I still see CWM, not TWRP. I'm stuck on the CWM recovery and need TWRP to try to install the Kitkat upgrade.
Should I unzip the components first and then flash the image using fastboot, or is there another way? I'm wary of fastboot as I've already (temporarily) "bricked" the Xoom by flashing a zip instead of an image that way. None of the instructions I've read has much advice on getting round installation problems.
I'm guessing the persistent CWM was caused by my selecting (at an earlier stage) the CWM option to fix the problem of the stock recovery being reinstated at each reboot. Can this be undone? Although I've installed Xoom-Universal-Root, apps that require root access - including GooManager - also fail with an access error. It's hard to tell whether the device is now rooted or not, so if there's any method of getting further without root access, that would be great.
====================
Edit: it looks as if the instructions I saw online, which mentioned two separate TWRP recoveries, were incorrect. To get Android Kitkat 4.4 onto my Xoom I didn't need the initial TWRP recovery, only the BigPart version. Once I skipped to the BigPart recovery, the problem described above did not recur.

[Q] Messed up trying to install lollipop for blue htc one s

hi everyone, good to finally sign up after being a long time reader here, unfortunately I have a problem.
My htc one s is rooted and I am running twrp and wanted to install the latest cm nightly so I downloaded it, googled instructions and used these instructions from a website.
Steps to Install Android 5.0.2 Lollipop on HTC One S via Official CyanogenMod 12 Nightly ROM
Boot into Recovery mode via adb or hardware buttons or use the QuickBoot app if your device is rooted.
In recovery mode, back up data on your current ROM. If using TWRP, select Backup and perform a Swipe to Back Up from the bottom of the screen.
Then select Wipe and do a Swipe to Factory Reset from the bottom of the screen.
Return to the main menu of TWRP recovery and select Install (if using CWM then choose Install Zip from SDcard.
Browse to the file where you saved the CM12 ROM zip file, select it and Swipe to Confirm Flash on the bottom of the screen. Now, wait until the flashing process completes.
After the ROM is flashed, repeat step 8 to flash the Gapps package as well.
Once both the files are flashed, return to recovery's Main menu and select Reboot > System.
I did all that and it installed fine, however, when I restarted the phone, it showed the htc logo then it just went black so I had to go back into twrp.
Instead I changed my mind and tried to install 4.1.1. jelly bean (since I needed to update anyways and couldn't because I'm running twrp and in that whole process I ended up deleting the version of jellybean and basically my phone has no jellybean or lollipop installed at all so my only option is going back into twrp.
After that, I read that my phone has to be S-off so I looked up instructions on how to install it (I'm on a mac) and apparently I'm supposed to flash the boot.img (kernel) via fast boot but in order to do that you need to have jellybean or some kind of rom running to have debugging mode on and I don't so basically this is where I'm stuck.
My apologies for the lengthy explanation but if anyone knows what to do from here that would be amazing thanks.

[TWRP] [Port] L.R.-Team recovery OMFG-Mod-From Cactus -to -Umidigi-F1

First version shared was twrp 3.2
New version is 3.3.0
***ORIGINAL TWRP is not my work. Only the porting of it to this device. I take no credit for the source.
*** DISSCLAIMER ALLERT***
I started having issues with encryption coming back to enforcing when using the Ported Team LR TWRP 3.3
Did not have trouble yet with OMFG-Mod version.
Also @ghost45 has made a build of twrp 3.3.1 for F1. It works good as well
https://forum.xda-developers.com/showpost.php?p=79651368&postcount=49
--- all versions give trouble of loosing IMEI when using the remove force encryption patch I suggest below. Left logs with @Zackptg5 .
**May need more testing**
-decryption is broken
-MTP is working
-ADB is working
****--Advanced menu items are not correctly on 3.2 version.
-- Some of the advanced menu was fixed in 3.3.(install root is working)
- Advanced menu has extra features.(all from source twrp)
-- install magisk (currently has V17 on OMFG V19 on LR TEAM)
-- patch dm-verity and force encrypt remove.zip. ( personally I prefer the universal dm-removal patch from xda)
-- Remove system password, (from original dev, I have not tested)
--
--Install (basic directions only)--details may be added later if needed
Open zip and fastboot flash the recovery image if bootloader is unlocked.
or
Open zip , then open scatterfile (scatter file in test 1 has issue, updating it in next test )with sp-flashtool , select download
--First boot into TWRP will give errors for unable to mount /data. This is from the force-encryption.
- When boot into TWRP, select wipe -> format type 'yes' to format data
- When format is done, return to TWRP home page, select reboot -. recovery
--Now Patch device so no longer forces encryption
-- Use built in feature from 'Advanced Menu' or use the following directions--Fails to unpack boot. (current zip used is not compatible with system-as-root boot.img)
-To remove this I use 'Disable_Dm-Verity_ForceEncrypt' from
-- https://github.com/Zackptg5/Disable_Dm-Verity_ForceEncrypt -- currently based on magisk V19.2
-Download from the "Clone or Download" button on the above linked Github Page.
-Unzip the downloaded file. You will have a folder with same name as the zip package. Browse inside this folder, select all files and zip them.
-Put this new zip file onto your phone. ( Hay notice the MTP function on this TWRP works)
- in stall the zip like any normal twrp package.
--Next Install Magisk
--Use Built in Root Option from 'Advanced Menu' to use Magisk V19 or the following direction
- Goto the releases page of magisk github page. ==>LINK
- Download latest Magisk zip , Put file to phone, Install.
-- Download Folder For TWRP Ported from OMFG-Mod
https://www.androidfilehost.com/?w=files&flid=294886
-Screenshots.
- Ported OMFG-MOD gold Button TWRP V3.2
- Ported Team LR TWRP 3.3 standard Button
Attached Below
--Thanks --Mentions
recovery source from [LR TEAM] MIUI
http: //www.miui.com/forum.php?mod=viewthread&tid=19006123&page=1&mobile=2#pid257831639
link is newer version from ported recovery. They updated recently. Next port may use newer base as well.

hello @ColtonDRG. Long time.
I see you posted in umidigi forum that bootloader is not checking signature. So you CAN flash images with flashtool without unlocking. Is that correct.?
I have based the above install guide on that fact that you CAN.
But the first twrp posted by "ghost45" says no it must be unlocked.
edit:
I should be able to verify later today or this weekend, when my order arrives.
OK, verified, when i used flash tool and put twrp on phone before unlocking bootloader, on reboot I was stuck in "RED" status for boot loader. So must unlock

Flash this zip to remove the AdupsFota app
this is the update app. You will not be able to install OTA when rooted and twrp anyway, And if an OTA comes you will get stuck in recovery bootloop. So this flash file will rename the 2 apk related to OTA download and Force reboot that supposed to install that update.

Reserved
Will keep this post for working on issues .
Right now , I discovered after playing with the built in dm verity patch and root install lead imei's getting erased.
Restored the full rom with flash tool fixed, will update process as necessary
Restarted from the top again.
--1 Full stock rom flashed with sp flash tool.
--2 Twrp flashed in flash tool
--3 format /data, reboot recovery
--4 use mtp to copy Disable_Dm-Verity_Forceencrypt to phone
--5 flash the decrypt zip. And at the end of flash the output log showed 'failed to mount /nvdata file not exist'
*** Waiting for input from the Patch dev. Others on his xda thread with MTK have had similar trouble***
--6 use mtp , put stock recovery file on phone. Image flash stock recovery, reboot recovery, do factory reset in stock recovery. This fixed the /nvdata error.
--7 sp flash twrp again, use built in 'install root' option from advanced menu.
Bam all done

New Umidigi f1 recovery 3.3.1 test2 is pubblished.
Test this one if all is corrected...
http://www.mediafire.com/file/1emy4tk1gvnkj96/recovery-twrp-3.3.1_Umidigi_F1_test_2.rar/file

ghost45 said:
New Umidigi f1 recovery 3.3.1 test2 is pubblished.
Test this one if all is corrected...
http://www.mediafire.com/file/1emy4tk1gvnkj96/recovery-twrp-3.3.1_Umidigi_F1_test_2.rar/file
Click to expand...
Click to collapse
Thank you, this one has no displayed errors.
I have question though.
Do you know how to make system be mounted as /system instead of /system/system ?

Hey, buddy. Good to see you on the forums again. When I picked up this device I wondered if anyone from the R1 HD days would also be on it. I seem to have misplaced mine but I'll find it eventually, send me a DM if you wanna talk about it. I'm not 100% sure about this, but the bootloader verifying signatures might have been patched in because I don't remember mine doing that when they first came out. Of course even if it does, SPFT is still useful for unbricking and downgrading, but I really doubt UMIDIGI will patch out the unlock option like BLU did.

Hello again, all. I've been working on my UMIDIGI F1 again and after flashing the most recent firmware update using SPFT and trying to flash TWRP again I realized that something that changed in the latest firmware update has broken all of the existing TWRP images. Now the bootloader screen hangs for a while, sometimes a green bar appears at the top of the screen briefly, and then the phone reboots into Android. It is perhaps worth noting that when I tried to flash the upgrade in download only mode it just complained about the partition layout or something like that and then bailed, telling me to use the Format and Download option instead. I didn't do that because UMIDIGI told me not too and instead opted to try the Firmware Update option, which did work. I'm going to try to downgrade (hopefully I don't get bricked from downgrading preloader, efuses, etc) but I am a bit concerned about what has changed. Stock recovery still boots OK so it would seem to me that the bootloader isn't just completely borked, but either way it's a bit alarming that an OTA caused the custom recoveries we have to go kerplooie.

ColtonDRG said:
Hello again, all. I've been working on my UMIDIGI F1 again and after flashing the most recent firmware update using SPFT and trying to flash TWRP again I realized that something that changed in the latest firmware update has broken all of the existing TWRP images. Now the bootloader screen hangs for a while, sometimes a green bar appears at the top of the screen briefly, and then the phone reboots into Android. It is perhaps worth noting that when I tried to flash the upgrade in download only mode it just complained about the partition layout or something like that and then bailed, telling me to use the Format and Download option instead. I didn't do that because UMIDIGI told me not too and instead opted to try the Firmware Update option, which did work. I'm going to try to downgrade (hopefully I don't get bricked from downgrading preloader, efuses, etc) but I am a bit concerned about what has changed. Stock recovery still boots OK so it would seem to me that the bootloader isn't just completely borked, but either way it's a bit alarming that an OTA caused the custom recoveries we have to go kerplooie.
Click to expand...
Click to collapse
There is a newer twrp that has been released on 4pda.net that supposed to work on newest firmware release.
And downgrading with flashtool should work. Again need to use firmware upgrade option.

mrmazak said:
There is a newer twrp that has been released on 4pda.net that supposed to work on newest firmware release.
And downgrading with flashtool should work. Again need to use firmware upgrade option.
Click to expand...
Click to collapse
Downgrading worked. I couldn't find the newer TWRP version you were referring to and the website you mentioned redirects to a bunch of scammy crap.

ColtonDRG said:
Downgrading worked. I couldn't find the newer TWRP version you were referring to and the website you mentioned redirects to a bunch of scammy crap.
Click to expand...
Click to collapse
We have the twrp file copied to telegram group also. I'm stuck on mobile, or I would just copy the twrp here.
UMIDIGI
UMIDIGI unofficial TG group
https://t.me/UMIDIGI

Disable_Dm-Verity_ForceEncrypt failed
Hello, I'm trying to patch my F1 using the Disable_Dm-Verity_ForceEncrypt, but am stuck with an error "Dumping/splitting image failed. Aborting..." This occurs when I try using the Install from twrp. Has anyone encountered this issue before? I have done a wipe, and also tried installing Magisk (which installs fine).