Hi All, Here is the first build of TWRP I did. This is a port and not developed from source. But that shouldn't matter as of now. Will also try to build it from source and see if it can go into official twrp. No guarantee on making it official. I don't want to be stuck on making twrp official as it doesn't yield us much benefit. I will try to put my effort on building lineageos.
That being said here is whats working and not
Working:
Touch(should wait for 10 seconds after twrp screen appears)
adb
Mounting partitions
Vibration - no one cares for this anyway
Need testing:
External sdcard
Flashing zips
Not working:
Mounting /data which is our internal sdcard
Instructions:
Reboot to bootloader -> Press and hold volume down and power
Code:
fastboot boot twrp_capri.img
Warning: Don't flash this image to your boot partition. It will only boot recovery
FAQ:
1. Shouldn't I flash it so that I can boot to recovery without help of computer?
Answer: We do not have a separate recovery partition for our phone. So if we flash it, then it should serve to boot android as well as recovery. Which is very much possible but it will then be locked to a specific version of phone's software. It wont let us update our phone even the security updates. If we somehow update it then `touch` and other things would be broken if we use this twrp recovery to boot. Also I have made changes to lower security to have adb always working etc. So use this only as a flashable image through bootloader. Or you can flash this through magisk from android if you want to boot into recovery when required and flash stock boot when we want to boot android.
Does not work at all on g10
@PHYSC-1 this is for g10 power. In this same forum, you should find a TWRP for g10. Please try that.
Related
I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE. DO IT AT YOUR OWN RISK.EVERYTHING WRITTEN IN THIS DOCUMENT WAS TESTED ON MY PHONE.
- Development finished.
After successfully unlocked the bootloader of my mate , started to compile TWRP for our device.Thanks to Teamwin for this great touch recovery.
This version is a permanent recovery , it replaces the stock recovery (3e) . You have to restore the stock recovery if you want to install update.app format stock rom .
You do not need root to install , but unlocked bootloader is a must. You can read how to unlock your Mate's bootloader here:Bootloader Unlock.
There is two way to install permanent TWRP.
1. From existing permanent twrp recovery , if you selected this method of unlocking the bootloader.
Download the zip file and copy it to the sdcard. Restart the phone in recovery mode. (power + volume up). TWRP comes up. Select install and choose the storage where you copied the zip file. Select the file and swipe to install.
TWRP 2.7.0.1 twrp flashable version
2. From bootloader mode using fastboot flash recovery twrp2_7_0_1.img command.
TWRP 2.7.0.1 fastboot flashable package
TWRP 2.7.0.1 fastboot flashable package mirror
It will not backup/restore the contents of internal sd . Formatting data will delete the contents of internal_sd. Wiping data will not delete the contents of internal_sd.
Changelog :
- 2.6.3.0
Initial release
- 2.6.3.2
Fixed adb connection now it runs fine and runs in root mode.
Fixed internal SD handling , now it is correctly /data/share not data/media .
Creating backup of Data does not back up internal sd , so you can backup userdata to internal sd for example.
Fixed wipe of Data . Now it does not removes the content of internal SD.
Backup possibility of internal sd is added.
Internal storage is renamed to Internal SD.
External storage is renamed to External (Micro) SD Card.
Reduced font size
- 2.6.3.3
Fixed recreation of /data/media when data is wiped.
- 2.7.0.0
Changed to Omnirom twrp repo.
Fixed charging in recovery, battery percentage is shown , turned off device chargeable. (Thanks to Surdu_Petru)
Fixed recreation of /data/media folder after format of data partition.
Revert Backup possibility of internal sd is added.
Revert Internal storage is renamed to Internal SD.
- 2.7.0.1
Fixed charging LED in recovery. (Thanks to Surdu_Petru)
Custom kernel :
I compiled a kernel for B221 rom .Nothing really serious , just some config changes and added sio , sioplus , zen I/O scheduler from surdu_petru's P6 kernel source.
Download the zip , copy it your sdcard and install it from Twrp recovery.
Download B221 custom kernel
This is a great achievement
Congratulations
This recovery could be compatible to test HAM 4.4 ROM?
I guess not?
Because it is a permanent twrp recovery , you can try any recovery flashable rom on your device. If it does not boot , the recovery still available.
The only problem can be if the installer zip contains in its updater-script an assert command to check the device type.
e.g.:
assert(getprop("ro.product.device") == "hwp6_u06" || getprop("ro.build.product") == "hwp6_u06");
simply remove that line from updater script.
You can ask the developer of the rom to put the following line to boardconfig.mk if it is compatible with both device (P6 , MT1)
TARGET_OTA_ASSERT_DEVICE := hwmt1-u06 hwp6-u06
TWRP updated , see first post.
joe.stone said:
TWRP updated , see first post.
Click to expand...
Click to collapse
how do you reboot into this recovery and how do you reboot into fastboot mode please urgent help needed
Kannibalism said:
how do you reboot into this recovery and how do you reboot into fastboot mode please urgent help needed
Click to expand...
Click to collapse
adb reboot recovery or power + volume up
adb reboot bootloader or power + volume down
joe.stone said:
adb reboot recovery or power + volume up
adb reboot bootloader or power + volume down
Click to expand...
Click to collapse
thank you sir you are a legend i had flashed this recovery with locked bootloader and trouble started i am now reverting back to stock to fix up the problem
Hello joe.stone
I already fixed battery charger on TWRP for P6 !
Maybe you have time to take a look into my github , to fix this issue for HAM !
Also we already passed to TWRP 2.7.0.0.
Good luck !
TWRP updated.
Hi @joe.stone
In the Advanced Wipe...
I can Format all?
'system'
'cahe'
'data'
'internal storage'
...and everything else.
Thanks.
Work but not smooth I think twrp 2.6.3 better
Could someone tell me why at my mate i must use VolUP + VolDown do get the Recovery Menu (TWRP) ?
Mine too
Sent from my Huawei Ascend Mate
farewell
New version uploaded. Fixed charge LED in recovery (Thanks to Surdu_Petru).
I have changed my Mate to a LG G-Flex , so I have finished development on Mate. All my sources will be left on github if anyone wants to develop.
Thank you guys all the support and I wish the best .
That's sad but it's comprehensible. Good luck and thanks for everything!!!!
Sent from my MT1-U06 using XDA Premium 4 mobile app
Help?
Anyway to get an Ascend Mate MT1-U06 Back to original Stock ROM? I bought 15 of them and only 1 is having issues right out of the box. This phone looks as though it has been flashed with something other than Huawei Original Firmware. When starting the phone, the Huawei logo comes up, but then after, opposed to going to a Huawei Splash screen with the jingle, it goes to the pulsing all lower case colored "android" splash/boot image. The wallpaper looks like something from a custom CM ROM, and none of the themes can change it. The app icons wont move either, if I try to move one I get "Unfortunately, Huawei home has stopped". We can not take screen shots as the phone will not allow it, I will have to take pics with another device.... I tried to flash Original Huawei 4.1.1 ROM as well as the official 4.2.2 ROM. I have Wiped the Phone with TWRP (System, Date, Cache, EVERYTHING), then flashed the stock recovery back and flashed Huawei Original firmware again (several Times), but whatever is on this phone hanging on like an old girlfriend. Any help?
@joe.stone, is your device configuration folder that you used to build TWRP posted on github by any chance? Would like to review it. I have made one up for the HAM2 and built TWRP for testing. Currently undergoing an issue with the bootloader though. Using fastboot or key combination won't access the recovery if it is custom, but with stock it works. I figure one of two things with this problem: either the bootloader does a security check on the recovery and aborts if it isn't stock or the build just simply doesn't boot. So, to ease things up a bit on narrowing down this problem I am hoping to take a look at your source if it's available.
Modding.MyMind said:
@joe.stone, is your device configuration folder that you used to build TWRP posted on github by any chance? Would like to review it. I have made one up for the HAM2 and built TWRP for testing. Currently undergoing an issue with the bootloader though. Using fastboot or key combination won't access the recovery if it is custom, but with stock it works. I figure one of two things with this problem: either the bootloader does a security check on the recovery and aborts if it isn't stock or the build just simply doesn't boot. So, to ease things up a bit on narrowing down this problem I am hoping to take a look at your source if it's available.
Click to expand...
Click to collapse
My modified twrp(needed because /data/share is the internal sd) and its config is included in my cm10.1 repo. (bootable/recovery) and my boardconfig contains the settings needed for twrp. About your issue :
You need to unlock your bootloader. The mate also has the security check enabled , but with unlocked bootloader it does nothing. You need to figure out how to open your bootloader.
joe.stone said:
My modified twrp(needed because /data/share is the internal sd) and its config is included in my cm10.1 repo. (bootable/recovery) and my boardconfig contains the settings needed for twrp. About your issue :
You need to unlock your bootloader. The mate also has the security check enabled , but with unlocked bootloader it does nothing. You need to figure out how to open your bootloader.
Click to expand...
Click to collapse
Thanks, and yea, the bootloader was recently able to be unlocked. So, I must say its safe to assume the TWRP build failed. I'm doing it blind since I don't own the device. However, one of the guys was kind enough to send me a used one so when I get it I will be able to resolve the problem rather quickly. Thanks.
Hi folks,
today is a good day for all you guys who own a Huawei Honor 3C 4G (H30-L02). I was able to compile the source code of TWRP for our phone. So we finally have a working custom recovery. That means no more scratching one's head whether the next full update from Huawei is still rootable or not. You flash SuperSU via TWRP and that's it.
This new TWRP recovery was compiled against the build H30-L02V100R001CHNC17B130. I hope it also works with higher builds up to B138 (the latest).
But before you start to freak out, be sure to read the following:
Disclaimer
Flashing a custom recovery is considered HIGH RISK if you do not know what you are doing. You can easily brick your phone if you flash to the wrong partition, for example.
Furthermore, neither me nor XDA assume any responsibility or liability for failing flashes or bricked devices. If you decide to give this new recovery a shot, you are in charge and control of your phone. If it fails to start after that, tough luck. So think twice if you really want to try something that risky.
Installation
Your phone is connected to your PC with either Linux or Windows and all necessary drivers are installed and working correctly.
You need an unlocked bootloader. Please follow the procedure outlined HERE.
You also have to have root access. To become root you need an app called SuperSU, for instance. I used RootGenius which will also install SuperSU. Only for Windows!
Install apps "busybox" and a terminal emulator. Do not forget to open busybox and install in-app!
Android 4.2+ uses SELinux as base operating system, which means certains files (determined by the phone manufacturer) are secured against manipulation - even if you are root! You need to switch off this protection and remove the file "/system/set_immutable.list". See here how it is done:
Open your terminal emulator and type
Code:
su
mount -o rw,remount /system
chattr -R -i /system
Rename the file "/system/set_immutable.list" as you wish.
This step is necessary for TWRP to restore files on the system partition. If you fail to accomplish this step, you won't be able to restore a system image! TWRP will report an error and will leave your phone in a potentially non-bootable state!
Now you need to boot the bootloader of your phone. Connect your phone to your PC, open a shell or command line and type:
Code:
adb reboot bootloader
Then you flash the TWRP recovery:
Code:
fastboot flash recovery twrp_recovery_h30l02_with_kernel_CHNC17B130.img
You may need the "sudo" command on your Ubuntu Linux distribution prefixed to each adb or fastboot command.
Finally you need to boot to recovery.
IMPORTANT: Press Vol. up on your phone and don't let go until you see the screen with the boot logo! Failing to do this means your phone will start normal operation and not recovery! While pressing enter this:
Code:
fastboot reboot
If everything goes fine, you will see the TWRP curtain and after that the buttons of the TWRP gui.
Source Code
TeamWin Recovery sources on GitHub
TWRP Huawei 3C 4G sources on (later ... maybe on GitHub, I don't know yet.)
Back to Original Recovery
In case something goes wrong, be sure to have the original recovery at hand.
The original recovery is also necessary if you plan to flash regular full updates from Huawei.
Proceed analogously like what was written before.
Switch your phone off. Hold power button until it becomes quiet and dark.
Connect the USB cable to your phone, but don't plug it into your PC yet!!
Press Vol. down and don't let go until you see your phone's boot logo.
Now while pressing Vol. down connect the USB cable to your PC.
The fastboot screen should appear with the green Android.
Type
Code:
fastboot flash recovery orig_recovery_h30l02_CHNC17B130.img
This installs the old recovery. Finally, you will issue a "fastboot reboot" and operation is back to normal.
Credits
The developer of TWRP Dees_Troy.
The guy who ported TWRP to the Ascend P7 Surdu_Petru.
This thread for the Galaxy Tab S and the original thread started by Dees_Troy.
Miscellaneous
You have read thus far. That's good because that shows me you are eager to do what is necessary to follow through all of the steps. Please notice the following:
I did not test TWRP recovery for H30-L02 extensively! Backup and Restore should work, but I can't warrant for that!
This port of TWRP is a bit different from the normal TWRP. The latter has iconified buttons at the bottom of the screen. I removed these icons and switched their particular functions to the soft buttons of the phone. So when you touch the back button you will navigate a screen back. You touch the home button and you get to the home screen. You touch the button with the three lines and you will see a console window that is rendered as overlay. Touch the button again and it will disappear.
You might run into bugs. What does that mean? It may mean that you wreck the contents of one or more of your phone partitions which will result in a phone that does not boot any longer. You have been warned. So be sure you have a backup of all your valuable user data somewhere and a full original UPDATE.APP that's valid and applicable for your H30-L02.
Issues
none to report yet.
Downloads
The new TWRP recovery.
The old recovery by Huawei.
Happy backup-ing and restoring!
Please report back any errors in this thread. Thanks!
DFahren
If you found a bug or have problems, please add the "last_log" file to your report.
From the shell or command window you type
Code:
adb pull /cache/recovery/last_log
So I can better see what might have gone wrong.
For all those who updated to b151, they have to downgrade to b130 flashing vía fastboot an extracted rom from update.app, and after that root, and everything according to this post.
You can install custom ROM when you've TWRP installed
Hello,
I am having a problem where my phone is only, as far as I can tell, willing to boot into recovery. From the system, doing a normal reboot ends up in recovery, from powered off it goes into recovery, rebooting from recovery to system ends up back in the recovery, and the fastboot menu's "Continue" option goes reboots to recovery. The only way I can get into the system is to boot via fastboot -- i.e.,
Code:
fastboot boot boot.img
Where boot.img is the one packaged with the rom I am currently running.
This is not convenient because I need to connect it to a computer!
Is there some way to tell the bootloader to not boot recovery by default?
I have tried simply flashing the boot.img from above with:
Code:
fastboot flash boot boot.img
Which doesn't have any noticeable effect.
I suspect I broke something last night kicking around. I flashed the Open Beta 10 Modem & Firmware, then flashed the Open Beta 10 recovery, before changing my mind and installing TWRP 3-28 and Resurrection Remix v5.8. Somewhere in there, fastboot -w got run, but I don't think I did anything else potentially destructive.
Thanks for reading!
Hmm... Try install boot into recovery partition and recovery into boot? I know it's sound like a joke, but it will probably help you while u wait for a beter solution or just solution to repair that problem.
Anyway - maybe try flash old MM firmware?
A solution for me...
For anyone who rolls along and sees this in the future, my fix was:
0. Take a backup of sdcard AND data -- Step 2 will wipe data and sdcard without asking
1. Download the official recovery for the OnePlus 3
2. Use fastboot to boot (I didn't even have to flash) the official OnePlus 3 recovery AGAIN: WARNING: This step wipes all data without asking for confirmation!!!
I have now installed TWRP-3.0.4.0 and Resurrection Remix v5.8.1-20170202 and everything seems to be working just fine.
Thanks to @sylviohneto for finding this fix here: https://forum.xda-developers.com/oneplus-3/help/critical-bootloader-boot-recovery-fresh-t3530283
I had same problem so for that just take nandroid backup of data and while in turn copy it to pc and any other backup of data you need then format all the partions and reinstall rom and restore data... And if your lock screen have security then check Google you will have to delete a file called locscreen.db from file manager in twrp to access your phone
Hi everyone,
I tried to update my rooted Pixel C with Android 8 and TWRP 3.1.0.0 from August build to September build with FlashFire.
All of the following have I done on my Nexus 5x as well and it worked as a charm there.
Therefore i dl'd the corresponding zip-file from google dev page and started the update with FF. It said to me it can update the boot, system, recovery and vendor partition so I unchecked the recovery partition only to keep TWRP. I also told FF it should include SuperSU again to root the new Android.
After the update the device was unrooted, so i tried to start into recovery to install superSU manually. But TWRP was gone and i get everytime the android on the back with the text "no command".
Therefore I tried to flash TWRP with NRT again. But after the flash the device always starts into TWRP and Android isn't starting anymore.
I can use NRT again to flash Android without loosing my data but than TWRP is gone again.
So either the device always starts into TWRP or I have no recovery installed.
Anyone an idea what i can do to flash TWRP again and to fix the boot order or whats broken than?
Regards,
flattervieh
I don't have the C but here's what I would try. First, have your device booting normally with the stock recovery. Then use fastboot to boot into TWRP, not flash it. When it boots into TWRP then flash supersu. From TWRP then boot back into the bootloader and then flash TWRP with fastboot.
Flash the latest (beta?) TWRP. It allows reading the encrypted data folder.
Short notice, i'm still struggling with the problem.
In the meantime I tried the following:
1. I temporarely booted TWRP 3.1.0.0, with this version I was not able to encrypt the data partion (always invalid key) but I was able to see the system partition and I installed SuperSU. After that i restarted into the bootloader and flashed TWRP 3.1.0.0.
This led to the same phenomenon, that my pixel always boots into TWRP and not into Android itself.
2. Same thing as before but with TWRP 3.1.1.1.
With this version I was able to see the size of the data partition, but I was also not able to read or write onto it. (Again invalid code) I installed SuperSU and made a device restart without flashing TWRP 3.1.1.1.
This led to a totally softbricked device with a boot into "no command" screen.
After flashing Android again via fastboot Android starts correctly and I can use the device but root is still not working.
Regards
I'm not sure why twrp isn't sticking. But the android on its back with "no command"is the stock recovery. To get into it simultaneously press and release the power and vol up keys. You might have to try it a few times as the timing can be very finicky. From there you can boot into the system, you don't need to flash the factory image and start all over.
So, wanted to use my old pixel 2 xl but USB only works for charging. PC won't detect it, used dozens of cables and different computers.
I have latest carbon image and root. Wanted to boot twrp.img and then flash the twrp.zip since it used to be that way.
Any hints on this please? Because using apps says partion doesn't exist. I recall it used to be the "issue". That's why we had to boot twrp first and then flash it.
Maybe there is a different solution now.
Any help would be much appreciated.
This is not possible without USB. When the device reboots, RAM is cleared and nothing is "held" in NVRAM for the boot process. The device will either boot the image currently in the boot partition, or if commanded, will live boot the image you specify.
It -is- possible to write images to /boot using root, but keep in mind that since Magisk does not support the compression used for the stock recovery kernel, flashing TWRP to /boot will result in a device that can only boot TWRP.
i see, ok, so, sorry the stupid question in advance.
What if i write twrp .img to boot, then it always boots from twrp, but since i have twrp.zip and a rom.zip in media i can flash .zip to recovery partition and then reboot to recovery and flash rom.zip?
Or is this just to dumb to even ask.
hfmls said:
i see, ok, so, sorry the stupid question in advance.
What if i write twrp .img to boot, then it always boots from twrp, but since i have twrp.zip and a rom.zip in media i can flash .zip to recovery partition and then reboot to recovery and flash rom.zip?
Or is this just to dumb to even ask.
Click to expand...
Click to collapse
Not a dumb question. However, flashing TWRP will result in a device that can only boot TWRP. This applies even if you flash a ROM to a slot.
The best alternative I've found is to run LineageOS. This is because that ROM includes its own recovery that can flash non-Google zips. Further, its updater not only doesn't require a usb cable it also gracefully handles Magisk.
Unfortunately, LineageOS isn't Carbon, and Carbon doesn't include a built-in updater. In your case, you may have no choice but to use a USB cable.