Team Win Recovery Project 2.6, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
This recovery is WIP and intended for a preview only. Touch is a total mess and devs are working on it. The boot image will boot to system as usual, only touch is buggy. While recovery image will only boot to recovery.
Download:
The complete boot image, thanx @Abhinav2: http://d-h.st/Jvs
How to (for boot image):
1. fastboot flash the boot image
2. Press Volume down repeatedly to enter TWRP
Only Recovery Image by me: Recovery.img
How to (for recovery image):
1. Download recovery image
2. Make NANDROID backup of current Rom, also have its boot.img ready
3. Enter fastboot mode and " fastboot flash boot recovery.img"
4. Start the phone, it will go directly into recovery
5. When finished, press Power + Volume up untill 3 vibrations
6. Enter fastboot mode and "fastboot flash boot boot.img"
7. Restart
CREDITS:
- munjeni
- Abhinav2
- wan5xp
it won't boot CM or stock ya? so we just test the recovery right?
itachilinux said:
it won't boot CM or stock ya? so we just test the recovery right?
Click to expand...
Click to collapse
there is no boot.img complete boot image is also WIP
Sent from my Nexus 7
XperiaMT27 said:
there is no boot.img complete boot image is also WIP
Sent from my Nexus 7
Click to expand...
Click to collapse
will test it tonight, also changing my rom from carbon to your AOKP
will report bugs also.
Here- http://d-h.st/eE0 This is my version. It SHOULD boot into twrp by pressing power button when phone vibrates. I've turned on LED. This SHOULD also boot normally into system. @XperiaMT27 I'll explain you how to do this later. If you want you can go through its ramdisk to see how it works. Basically a init script which separately controls ramdisk and recovery. Recovery related stuff is removed from main ramdisk as it is triggered separately. A bootrec-device defines all the partitions and FOTA partition is used with elf_extract method. Will let you know more later. BTW touch won't work and don't bother I'll work on it. I have enough logs now and can work. If any of you is willing to help, they are more than welcome. Help of any kind, big or small, is appreciated.
This version is untested but it should work as it works for Xperia P and Xperia U but flash at your own risk. If you don't know how to repair your device, I won't recommend you to flash.
Cheers,
AJ
Abhinav2 said:
Here- http://d-h.st/eE0 This is my version. It SHOULD boot into twrp by pressing power button when phone vibrates. I've turned on LED. This SHOULD also boot normally into system. @XperiaMT27 I'll explain you how to do this later. If you want you can go through its ramdisk to see how it works. Basically a init script which separately controls ramdisk and recovery. Recovery related stuff is removed from main ramdisk as it is triggered separately. A bootrec-device defines all the partitions and FOTA partition is used with elf_extract method. Will let you know more later. BTW touch won't work and don't bother I'll work on it. I have enough logs now and can work. If any of you is willing to help, they are more than welcome. Help of any kind, big or small, is appreciated.
This version is untested but it should work as it works for Xperia P and Xperia U but flash at your own risk. If you don't know how to repair your device, I won't recommend you to flash.
Cheers,
AJ
Click to expand...
Click to collapse
this does not stop at recovery, same thing happened to me before.
XperiaMT27 said:
this does not stop at recovery, same thing happened to me before.
Click to expand...
Click to collapse
You tried this one? And you mean it doesn't vibrates for recovery? Cause that's basically impossible as I've added the line for vibration in init.sh but I guess there must be something different with sola. I'll work on it
Cheers,
AJ
Abhinav2 said:
You tried this one? And you mean it doesn't vibrates for recovery? Cause that's basically impossible as I've added the line for vibration in init.sh but I guess there must be something different with sola. I'll work on it
Cheers,
AJ
Click to expand...
Click to collapse
vibration and led is there but i think there is ramdisk corruption.. see PM
XperiaMT27 said:
vibration and led is there but i think there is ramdisk corruption.. see PM
Click to expand...
Click to collapse
Nope. Ramdisk is alright. The problem is sola uses event1 while event2 is defined in bootrec. Connect your device to PC(usb debugging on). Open terminal and type the following exactly-
Code:
adb shell
su
cd /dev/input
ls -al event1
Let me know the output.
Cheers,
AJ
Abhinav2 said:
Nope. Ramdisk is alright. The problem is sola uses event1 while event2 is defined in bootrec. Connect your device to PC(usb debugging on). Open terminal and type the following exactly-
Code:
adb shell
su
cd /dev/input
ls -al event1
Let me know the output.
Cheers,
AJ
Click to expand...
Click to collapse
yes ramdisk is fine, was my fault.
here is the output
Code:
[email protected]:/dev/input # ls -al event1
crw-rw---- 1 root input 13, 65 Feb 26 14:49 event1
actually 10 events from 0 to 9 are defined
XperiaMT27 said:
yes ramdisk is fine, was my fault.
here is the output
Code:
[email protected]:/dev/input # ls -al event1
crw-rw---- 1 root input 13, 65 Feb 26 14:49 event1
actually 10 events from 0 to 9 are defined
Click to expand...
Click to collapse
No. I'm talking about bootrec-device, that's different.
-----
Anyways, test this guys- http://d-h.st/Jvs It should work
Cheers,
AJ
Abhinav2 said:
No. I'm talking about bootrec-device, that's different.
-----
Anyways, test this guys- http://d-h.st/Jvs It should work
Cheers,
AJ
Click to expand...
Click to collapse
not power button but good old Volume Down button
OP updated with Abhinav2's kernel.
how to adb-ing when i'm in recovery?
Sent from my Xperia Sola using XDA Premium 4 mobile app
itachilinux said:
how to adb-ing when i'm in recovery?
Sent from my Xperia Sola using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I think it should work the usual way. Just try and report
Sent from my Xperia Sola
Abhinav2 said:
No. I'm talking about bootrec-device, that's different.
-----
Anyways, test this guys- http://d-h.st/Jvs It should work
Cheers,
AJ
Click to expand...
Click to collapse
Thanks a lot @XperiaMT27 and @Abhinav2 for your hard work!
Just want to ask whether in this version is the touch fixed?
Or just the boot.img is added now?
I think I read it in OP, but sorry to bother you again.
Sent from my Xperia Sola using XDA Premium 4 mobile app
XperiaMT27 said:
This recovery is WIP and intended for a preview only. Touch is a total mess and devs are working on it. The boot image will boot to system as usual, only touch is buggy. While recovery image will only boot to recovery.
Download:
The complete boot image, thanx @Abhinav2: http://d-h.st/Jvs
How to (for boot image):
1. fastboot flash the boot image
2. Press Volume down repeatedly to enter TWRP
Only Recovery Image by me: Recovery.img
How to (for recovery image):
1. Download recovery image
2. Make NANDROID backup of current Rom, also have its boot.img ready
3. Enter fastboot mode and " fastboot flash boot recovery.img"
4. Start the phone, it will go directly into recovery
5. When finished, press Power + Volume up untill 3 vibrations
6. Enter fastboot mode and "fastboot flash boot boot.img"
7. Restart
Click to expand...
Click to collapse
I can install without problems (i'm on cm11)? Does it work the touch? which of the two linked is better to install?
Sorry for my bad english and my STUPID QUESTIONS
Petru97 said:
I can install without problems (i'm on cm11)? Does it work the touch? which of the two linked is better to install?
Sorry for my bad english and my STUPID QUESTIONS
Click to expand...
Click to collapse
no, it doesn't even work well. touch screen is messy.
Related
Thanks to all the guys posting in this forum.
I finally managed to:
- unlock bootloader with the hardware trick (without loosing DRM?)
- upgrade from stock FW 335 to 368
- unroot device
so far i can help anyone having troubles with it
now i need to:
- install CM7.1 using rom manager, but the question is:
which is the Clockworkmod Recovery for the SK17? (it's not listed in the RM options).
Thanks for answering
giank30 said:
Thanks to all the guys posting in this forum.
I finally managed to:
- unlock bootloader with the hardware trick (without loosing DRM?)
- upgrade from stock FW 335 to 368
- unroot device
so far i can help anyone having troubles with it
now i need to:
- install CM7.1 using rom manager, but the question is:
which is the Clockworkmod Recovery for the SK17? (it's not listed in the RM options).
Thanks for answering
Click to expand...
Click to collapse
the boot image is there in the download of the rom on freexperia thread , same process flashboot replace boot img , and then flash the cynogenmod via recovery simple.
berz said:
the boot image is there in the download of the rom on freexperia thread , same process flashboot replace boot img , and then flash the cynogenmod via recovery simple.
Click to expand...
Click to collapse
I wanted to see what recovery mode looks like, but i cant enter it. Do i have to replace boot.img first to even enter it?
I'm new. =)
edit: im rooted on latest stock
berz said:
the boot image is there in the download of the rom on freexperia thread , same process flashboot replace boot img , and then flash the cynogenmod via recovery simple.
Click to expand...
Click to collapse
ok for reflashing boot.img w/ flash boot, but what is "recovery simple", can you try to explain how to do that? (sorry for the stupid question)
giank30 said:
ok for reflashing boot.img w/ flash boot, but what is "recovery simple", can you try to explain how to do that? (sorry for the stupid question)
Click to expand...
Click to collapse
he meant recovery mode. you can enter it by pressing volume down key during first 5 seconds of boot. you should wipe data and apply cm7 zip file there.
but i cant enter it. im wondering if i have to replace boot.img first :S
yes thats right , u need to replace boot image first.
berz said:
yes thats right , u need to replace boot image first.
Click to expand...
Click to collapse
ok thanks.
people are reporting that menu LEDs are very bright. do you know if theres a way to reduce brightness or disable the light completely?
for what i know this the vol down at boot should trigger the Clockworkmod Recovery, but as I cannot install it it's obvious that we cannot see it...
inside update-cm-7.1.0-XperiaMiniPro-SK17i-signed.zip there is a boot.img but don't know how to handle it... :-/
is it that the file that should be flashed using fastboot?
giank30 said:
for what i know this the vol down at boot should trigger the Clockworkmod Recovery, but as I cannot install it it's obvious that we cannot see it...
inside update-cm-7.1.0-XperiaMiniPro-SK17i-signed.zip there is a boot.img but don't know how to handle it... :-/
is it that the file that should be flashed using fastboot?
Click to expand...
Click to collapse
yes, boot.img via fastboot.
the instructions are on the official CM thread. here's the post for Mini Pro. http://forum.xda-developers.com/showpost.php?p=16822404&postcount=4
so i must:
1: estract boot.img from update-cm-7.1.0-XperiaMiniPro-SK17i-signed.zip
2: flash via fastboot
3: put update-cm-7.1.0-XperiaMiniPro-SK17i-signed.zip on the sd card
4: trigger the recovery mode via vol down on boot
5: flash CM7.1?
right?
giank30 said:
so i must:
1: estract boot.img from update-cm-7.1.0-XperiaMiniPro-SK17i-signed.zip
2: flash via fastboot
3: put update-cm-7.1.0-XperiaMiniPro-SK17i-signed.zip on the sd card
4: trigger the recovery mode via vol down on boot
5: flash CM7.1?
right?
Click to expand...
Click to collapse
i believe so.
there are some issues. LEDs under menu keys are super bright, and some people are reporting vibration and keyboard layout issues. keyboard layout can be solved (theres a thread for it) and vibration could be due to not wiping data before applying CM. keyboard layout could be due it as well.
so basically, LEDs is the only known issue right now.
sulkie said:
i believe so.
Click to expand...
Click to collapse
update-cm-7.1.0-XperiaMiniPro-SK17i-signed.zip is 91Mb, is that correct? should I flash it over 4.0.A.2.368?
giank30 said:
update-cm-7.1.0-XperiaMiniPro-SK17i-signed.zip is 91Mb, is that correct? should I flash it over 4.0.A.2.368?
Click to expand...
Click to collapse
yes, except my file is 89mb. is it 91 on sdcard or on your local harddrive?
edit: its 89.2 on my sdcard as well.
91.384 Kb.. so 89 Mb...
boot.img (inside the zip file) is 4,27 MB (4.481.024 byte) dated 29.2.2008, right?
giank30 said:
91.384 Kb.. so 89 Mb...
boot.img (inside the zip file) is 4,27 MB (4.481.024 byte) dated 29.2.2008, right?
Click to expand...
Click to collapse
indeed.
i got my file from CM's site. theres also a 110mb file on the official xda thread hosted on hotfile. im downloading it now to see if theres any difference
I can't find the link, can you share it?
btw, i got the Freexperia logo on boot but then it stucked...
how do I trigger recovery mode?
tnx
giank30 said:
I can't find the link, can you share it?
btw, i got the Freexperia logo on boot but then it stucked...
how do I trigger recovery mode?
tnx
Click to expand...
Click to collapse
link is here : http://forum.xda-developers.com/showpost.php?p=16822404&postcount=4
did you wipe data in recovery before applying zip file?
cant you enter recovery mode again with volume down key?
edit: files are the same, hotfile one just has extra apps. google apps and some SE ones.
i didnt installed the zip yet.
and i didnt enter in recovery mode too...
shall i push voldown + on button at the same time to enter recovery?
giank30 said:
i didnt installed the zip yet.
and i didnt enter in recovery mode too...
shall i push voldown + on button at the same time to enter recovery?
Click to expand...
Click to collapse
yes. i linked you the instructions on the official thread several posts ago
Got iT! thank you... +1 for you
Here is a CWM-Based Recovery built from source for use with either Honeycomb or Gingerbread hboot.
Thanks to Team Revolutionary for their CWM4 Recovery and DooMLoRD for his Custom CWM-Based Touch Recovery 5.0.2.7 which I used to set up the board config and makefiles.
To install place the recovery.img in your fastboot directory and type the following commands into a terminal;
Code:
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot
Flyer CWM-Based Recovery 6.0.1.1 GB.zip - 4.92 MB
MD5: 5f8bc34e44eaeccaf320f89cecca5e52 (for .img not .zip)
Flyer CWM-Based Recovery 6.0.1.1 HC.zip - 5.02 MB
MD5: 30b5bf5952ceba8fbab02f54b39da4df (for .img not .zip)
Click to expand...
Click to collapse
Koushik Dutta said:
New ClockworkMod Backup Format
TL;DR:
ClockworkMod Recovery now deduplicates files between builds. This results in way smaller backups.
Don't delete /sdcard/clockworkmod/blobs
Overview
I've gotten a few questions about how this works, so I figured I'd make a post on it.
Basically, here's what happens:
The files being backed up are hashed (sha256, not that it matters). Then it checks for a file with the name of the hash in
/sdcard/clockworkmod/blobs
So, if the hash of the file was c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed, it looks for /sdcard/clockworkmod/blobs/c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed
If the hash file is found, it continues on to the next file. Otherwise, it copies the file to the blobs directory with the file name being the hash.
ROMs and user data, for the most part, do not change too much between builds and backups. So, your APKs, system files, etc, are generally only stored once. This saves a ton of space. Especially between incremental backups.
Some of you may be thinking "well, how do I delete a backup?".
First, never delete the blobs directory. This would actually delete all your backups by rendering them unusable.
Simply delete the usual backup directory, and the next time you run a backup, all the unused hash files will be automatically delete (a process known as garbage collection). The recovery will show "Freeing space..." while this is happening.
Click to expand...
Click to collapse
Thanks, I couldn't get if that is touch enabled or not.
teorouge said:
Thanks, I couldn't get if that is touch enabled or not.
Click to expand...
Click to collapse
I dont have access to the touch based repos as they're closed at the moment so I'm afraid for now this recovery is old school. The "change log" Koushik posted on his Google+ was enticing enough to try it out though!
Koushik Dutta said:
Backups are much faster. 4-5x faster. (Bug fix due to excessive status updates of the UI and new backup technique)
Incremental backups are smaller. Way way smaller. Only 15-20MB each for each additional backup of a ROM. This is done using a new tool I wrote to dedupe the files between incremental backups to eliminate duplicates.
Click to expand...
Click to collapse
a quick note for those who wonder.
Aroma installer does not work with touch, without the touch enabled and ntrigd running in recovery. but thats just so you know.
so thats key controlled too.
Can someone make a flashable zip?
Dexter_nlb said:
a quick note for those who wonder.
Aroma installer does not work with touch, without the touch enabled and ntrigd running in recovery. but thats just so you know.
so thats key controlled too.
Click to expand...
Click to collapse
Just to clarify, Aroma will still work manually with the volume keys and power button I assume? Thanks for the heads up.
lekhwani said:
Can someone make a flashable zip?
Click to expand...
Click to collapse
I'll check that out now.
What do i gain with flashing this ower ver. 5.?
Thx!
jprednik said:
What do i gain with flashing this ower ver. 5.?
Thx!
Click to expand...
Click to collapse
5.0.2.8 is the most up to date recovery version on the gingerbread branch at the moment. These 6.0.0.x versions are from the ics and jellybean branches. To my knowledge I don't think Koushik posts "changelogs" on the various recovery updates but he's made a few posts talking about version 6 of ClockworkMod Recovery here and here.
I have Gingerbread.
So Work well with GB ? --- >HTC Flyer - CWM-Based Recovery 6.0.0.7 - GB.zip - 4.92 MB
What are the improvements.
Thanks
No offense but what is the point of this ?!.
lekhwani said:
Can someone make a flashable zip?
Click to expand...
Click to collapse
There is no touch support when flashed and Power button actually switched the screen OFF, so it is pretty useless. The DormLord touch -based CWN is just perfect as it is. There is no serious ICS ROM to flash anyway, so I do not understand why cripple this CWN when there is no real value here.
Max128 said:
I have Gingerbread.
So Work well with GB ? --- >HTC Flyer - CWM-Based Recovery 6.0.0.7 - GB.zip - 4.92 MB
What are the improvements.
Thanks
Click to expand...
Click to collapse
The GB version will work with the Gingerbread hboot. Check out the previous posts to read up on the changes.
fteo_viking said:
There is no touch support when flashed and Power button actually switched the screen OFF, so it is pretty useless. The DormLord touch -based CWN is just perfect as it is. There is no serious ICS ROM to flash anyway, so I do not understand why cripple this CWN when there is no real value here.
Click to expand...
Click to collapse
Flash the recovery.img manually through fastboot if you're having problems. If you look at the ClockworkMod site a lot of devices don't have ClockworkMod Recovery 6 or a Touch supported version at all. The Flyer has never had an officially supported ClockworkMod Recovery anyway. I wanted to check out version 6 myself and put these up in case anyone else wanted to as well. It's not for everyone as there won't be a ClockworkMod Touch Recovery without an ICS kernel or until DooMLoRD and Team UtterChaos port their Touch UI to the ics branch. If you don't want to use it don't.
I have a WiFi + 3g Flyer and with recovery 6.0.1.0 the power button doesn't work, so I'm not able to use it...
nikoan89 said:
I have a WiFi + 3g Flyer and with recovery 6.0.1.0 the power button doesn't work, so I'm not able to use it...
Click to expand...
Click to collapse
If the text options disappear when you press the power button press it again so they return then press volume-up and volume-down at the same time to toggle between "Back menu button disabled." and "Back menu button enabled."
revert back to 4.0.1.4
I tried this and had problems with selecting an option with the powere button so I want to revert to 4.0.1.4. I flash 4.0.1.4 to recovery via fastboot but then it hangs on the HCT logo when I try to get to Recovery.
Any ideas?
UPDATE: I ended up changing to Doomlords 5.0.2.7 and it works great.
nikoan89 said:
I don't have this kind of issue, mine is that power button in recovery mode simply doesn't work, all the text options still on screen, I'm only able to navigate with the volume buttons but I'm not able to select them.
EDIT: I've fix it holding the power button and pressing repeatedly the vol down button, now it seems to work
Click to expand...
Click to collapse
Work for me with this method. Thinks.
mkintop said:
I tried this and had problems with selecting an option with the powere button so I want to revert to 4.0.1.4. I flash 4.0.1.4 to recovery via fastboot but then it hangs on the HCT logo when I try to get to Recovery.
Any ideas?
UPDATE: I ended up changing to Doomlords 5.0.2.7 and it works great.
Click to expand...
Click to collapse
I had the same problem, took me several hours to figure out how to re-flash to 5.8.3.1.
This one is not good.
nikoan89 said:
I don't have this kind of issue, mine is that power button in recovery mode simply doesn't work, all the text options still on screen, I'm only able to navigate with the volume buttons but I'm not able to select them.
Click to expand...
Click to collapse
mkintop said:
I tried this and had problems with selecting an option with the powere button so I want to revert to 4.0.1.4. I flash 4.0.1.4 to recovery via fastboot but then it hangs on the HCT logo when I try to get to Recovery. Any ideas?
Click to expand...
Click to collapse
oushouseki said:
I had the same problem, took me several hours to figure out how to re-flash to 5.8.3.1.
This one is not good.
Click to expand...
Click to collapse
I enabled the "BOARD_HAS_NO_SELECT_BUTTON" flag in BoardConfig.mk and now the power button works as soon as recovery boots. No need to toggle between "Back menu button disabled" and "Back menu button enabled" anymore.
If the recovery doesn't boot properly and hangs at the splash screen use "fastboot erase cache". Similarly, if you want to flash any other recovery use the commands in the OP.
Code:
adb reboot bootloader
fastboot flash recovery nameofrecovery.img
fastboot erase cache
fastboot reboot
Can someone make a flashable zip?
THX
I would like that too...
i am a hardcore noob so bear with me.
What is a terminal and how and where to i type that?
can somebody please explain!
I have seen that since the update notification for Jelly Bean has arrived, Many people (Including me) have been asking for a Tutorial to root the Jelly Bean updated HTC Desire X (HTC DX for short). In this tutorial I would like to mention the steps to root Android Jelly Bean (JB) on HTC DX.
UPDATE: Tutorial with Screenshots here : HTC Desire X Root
This was what had worked for me when I recently rooted by HTC Desire X with Jelly Bean Update, So I hope it works for you too. I am assuming you have just installed the OTA Update and are now sitting with a Stock Jelly Bean on your device.
Summary:
1. Unlock Bootloader (if not already unlocked).
2. Install Jelly Bean compatible Custom Recovery.
3. Flash Super User and Install Busy Box.
4. Enjoy.
Steps.
1. Unlocking Bootloader.
There is a fully explained thread on unlocking bootloader and rooting android ICS put up by user nlooooo, Follow that thread and unlock your bootloader.
http://forum.xda-developers.com/showthread.php?t=2076675
2. Install Jelly Bean compatible Custom Recovery.
Once you update via OTA for the JB Update, Your HBoot becomes JB Hboot instead of the old ICS Hboot so you need a JB Hboot compatible Custom Recovery to flash the Super User and Root.
Our fellow user atis112 fixed the recovery by neXus PRIME to make it work with JB. So you need to download the JB Custom Recovery from the attachment and put it in your C Drive, So the file location would be C:\recovery.img
2.1] Download JB Recovery.img from here : http://forum.xda-developers.com/showpost.php?p=39662992&postcount=66 OR You can use the TWRP Recovery Image made by Yasir. Download from here : http://d-h.st/tSc
2.2] Once you put it in C Drive you need to connect your HTC Mobile to PC and Install HTC JB Drivers, You can install the drivers from here : http://forum.xda-developers.com/showthread.php?t=2222501. Make sure you have installed the Drivers correctly.
2.3] Open your Android SDK (Download it from here if not already) and Go to the \sdk\platform-tools folder. If on Windows 7, Keep the Shift Key pressed + Right click on an empty place in the platform-tools folder > Open Command Window here.
2.4] Type in the following command and see if your device is detected.
adb devices
Click to expand...
Click to collapse
After it is detected, Type the following command.
adb reboot bootloader
Click to expand...
Click to collapse
Once you are in the bootloader, Type the following command.
fastboot flash recovery c:\recovery.img
Click to expand...
Click to collapse
followed by
fastboot reboot-bootloader
Click to expand...
Click to collapse
and
fastboot erase cache
Click to expand...
Click to collapse
2.5] Now you have installed your custom recovery. Now Reboot your Phone.
3. Install SuperUser and Busybox.
3.1] Once again connect your HTC to PC, Download the attached SuperUser.zip and copy it to your SD Card.
3.2] Open the command prompt again as said earlier by going to platform-tools folder and using the adb devices command to check if the phone is detected.
3.3] Once it is connected, Type the following command.
adb reboot recovery
Click to expand...
Click to collapse
3.4] Now you are in the recovery, Use the Volume Up and Down keys to navigate it (Use the power button to select an option).
Navigate to Install Flashable Zip. (This should be the first option and already selected.)
Press Power Button once.
Select "Choose Zip from internal SD-Card" or "external SD-Card" accordingly as to where you put the Superuser.zip.
Press Power Button once.
Scroll and select the Superuser.zip using the Volume Keys.
Press Power Button once.
Then you have flashed your Zip successfully and you are rooted.
Go back to the Main screen using the "Go back" option. Select the "Reboot System Now".
Once you are in the HTC Main screen > Go to App Drawer > Google Play Store > Search for Busy Box and Install it.
That is it, You are now on Jelly Bean and Successfully Rooted.
To Check If You Are Rooted.
1. Open Playstore and search for an app named "Terminal Emulator".
2. Install it.
3. Open it and type in su and execute it.
4. You will get a prompt from Superuser to allow or deny > Allow it.
If you get that prompt, You are successfully rooted.
I hope I have provided credits to all the users whose threads I have mentioned. If not please let me know.
Thanks for reading this.
Or you can refer to my TWRP for JB. Its much better than the fixed neXusRecovery.
Hey, I didn't check that.. Can you give a link to the recovery?
Droid.Anoop said:
Hey, I didn't check that.. Can you give a link to the recovery?
Click to expand...
Click to collapse
Here: http://d-h.st/tSc
xpirt
xpirt said:
Here: http://d-h.st/tSc
xpirt
Click to expand...
Click to collapse
Done. Added it to the post. Thanks Yasir and Xpirt
Droid.Anoop said:
Done. Added it to the post. Thanks Yasir and Xpirt
Click to expand...
Click to collapse
1 more little thing.
I think the instructions in recovery are using vol up down and power buttons. But if im not mistaken,, both my recoveries you mentioned are Touch enabled. So actually no need to bash the crappy volume buttons (i really hate these volume buttons due to bad tactile feedback)
neXus PRIME said:
1 more little thing.
I think the instructions in recovery are using vol up down and power buttons. But if im not mistaken,, both my recoveries you mentioned are Touch enabled. So actually no need to bash the crappy volume buttons (i really hate these volume buttons due to bad tactile feedback)
Click to expand...
Click to collapse
Actually I used the CWM Modded Recovery using Vol rockers only assuming it wasn't touch enabled due to its User Interface. The TWRP one is touch enabled. Are you sure the fixed recovery is touch enabled? As I don't want to flash the old recovery once again to test it.
Droid.Anoop said:
Actually I used the CWM Modded Recovery using Vol rockers only assuming it wasn't touch enabled due to its User Interface. The TWRP one is touch enabled. Are you sure the fixed recovery is touch enabled? As I don't want to flash the old recovery once again to test it.
Click to expand...
Click to collapse
Both my recoveries are touch enabled.
1. TWRP (JB)
2. neXusRecovery. (discontinued for updates)
I'm not really a fan of buttons.
Droid.Anoop said:
Actually I used the CWM Modded Recovery using Vol rockers only assuming it wasn't touch enabled due to its User Interface. The TWRP one is touch enabled. Are you sure the fixed recovery is touch enabled? As I don't want to flash the old recovery once again to test it.
Click to expand...
Click to collapse
Yes, also fixed recovery is touch enabled: you mean the nexus Recovery, right?
xpirt
xpirt said:
Yes, also fixed recovery is touch enabled: you mean the nexus Recovery, right?
xpirt
Click to expand...
Click to collapse
Yes, Thanks for letting me know. Also is there any method to unlock the write protection in JB? I think the JB Sources are not released yet but any workaround?
Droid.Anoop said:
Yes, Thanks for letting me know. Also is there any method to unlock the write protection in JB? I think the JB Sources are not released yet but any workaround?
Click to expand...
Click to collapse
I think ckpv5 found a way. Just think.
xpirt
xpirt said:
I think ckpv5 found a way. Just think.
xpirt
Click to expand...
Click to collapse
Wow that is cool! Wonder if he will share it soon. Or has he already shared it somewhere?
Droid.Anoop said:
Wow that is cool! Wonder if he will share it soon. Or has he already shared it somewhere?
Click to expand...
Click to collapse
Look at his ROMs: deodexed one and myOneDx+ have both hTC write permissions defeated.
xpirt
xpirt said:
Look at his ROMs: deodexed one and myOneDx+ have both hTC write permissions defeated.
xpirt
Click to expand...
Click to collapse
There is a wp_mod which has a Module file "wp_mod2.ko" and an init.d script, (credits to flar2) using which ckpv5 has made his roms.
neXus PRIME said:
There is a wp_mod which has a Module file "wp_mod2.ko" and an init.d script, (credits to flar2) using which ckpv5 has made his roms.
Click to expand...
Click to collapse
Can you explain how to implement it in stock ROM? Then we can integrate it in the tutorial with proper credits.
Droid.Anoop said:
Can you explain how to implement it in stock ROM? Then we can integrate it in the tutorial with proper credits.
Click to expand...
Click to collapse
Look at flar2's thread but use the files from ckpv5's ROM, but first ask him for permission.
xpirt
root JB without flashing custom recovery?
Hi!
I haven't flashed TWRP v2.5.0.0 but only boot the phone into this custom recovery, which is working perfectly. (I want to keep the stock recovery.)
I can install and use the Aroma File Manager (TWRP with Aroma File Manager did not work.)
I can mount the system partition and change / delete files.
However, with a reboot, all my changes will be undone.
Before installing Aroma File Manager for the first time, I installed SuperSu1.34.zip. No error. I installed Aroma File Manager right after it, and I think it said "rooted".
Using TWRP's SuperSu does not work (no error message, but system reboots, and it says it's not rooted.)
My question: can I root my phone while only booting into a non-stock recovery or do I have to flash TWRP and then root the phone?
Would I see the system apps e.g., after mounting /system, even if the phone was not rooted?
I am new to JB, I had 2.3.7 before, which I could root without flashing a custom recovery.
I am not sure if I have to flash the custom recovery because of the s-off problem with HTC devices?
If I flash a custom recovery and root the device, can I flash the stock recovery afterwards without loosing root again?
Would you recommend using SuperSu or Superuser? Which version?
I don't think I need busybox.
I only want to delete bloatware and change the battery symbol.
Thanks for your help!
I didn't try rooting using the stock recovery, but I think it won't be possible as it won't let us change system partition due to S-On. But after you rooted using a custom recovery you can flash the stock recovery again without loosing root. But keep in mind that you won't be able to change system partition. Also, you can't flash zips which aren't signed by HTC.
Sent from my HTC Desire X using xda premium
dansou901 said:
I didn't try rooting using the stock recovery, but I think it won't be possible as it won't let us change system partition due to S-On.
Click to expand...
Click to collapse
The question is if there is a difference if I just boot into the custom recovery vs. if it is flashed and I boot into it. Does ist need to be properly flashed to allow writing in /system?
mary-lou said:
The question is if there is a difference if I just boot into the custom recovery vs. if it is flashed and I boot into it. Does ist need to be properly flashed to allow writing in /system?
Click to expand...
Click to collapse
How do you boot into a custom recovery without flashing it first? It has to be on recovery partition to work correctly.
Simply put, this is (as of now) the latest TWRP (with F2FS, without multirom - sorry).
https://www.mediafire.com/?mj5885q1x5lamzv
Either install it normally or by using fastboot:
Code:
fastboot flash recovery fota.img
If you head over to AndroPlus' thread and download his latest kernel (as of writing, that is Z3_AndroPlusKernel_F2FS_v26a.zip) you could format /system and /cache as F2FS and it will boot and run fine, /data will however, sadly, not format or work as F2FS. But so far, /system and /cache does.
* Goal: get /data to work with F2FS as well
Thanks for contributing ! Will Multirom ever get integrated by any chance ?
Sent from my Xperia Z3 using XDA Free mobile app
I didn't think anybody was interested.
But sure, I'll see what I can do!
You do need to wait a few days though.
Sure I think there would be a good amount of interest considering it would mean that no matter what happened to the Kernel/recovery we would still be able to fall back on Fota for Multirom.
Sure take your time, would be great if possible.
Sent from my Xperia Z3 using XDA Free mobile app
I don't suppose we are any closer to having MultiRom integrated into this ?
Thanks bud
Sent from my Xperia Z3 using XDA Free mobile app
Sorry if i should know this, but do we need a supported kernel or something to boot into FOTA recoveries?
kjames2001 said:
Sorry if i should know this, but do we need a supported kernel or something to boot into FOTA recoveries?
Click to expand...
Click to collapse
No, Fota Recovery is independent from the Kernel
Sent from my Xperia Z3 using XDA Free mobile app
panzerscope said:
No, Fota Recovery is independent from the Kernel
Sent from my Xperia Z3 using XDA Free mobile app
Click to expand...
Click to collapse
so you mean i can just flash this into fota and boot into it? Thanks.
kjames2001 said:
so you mean i can just flash this into fota and boot into it? Thanks.
Click to expand...
Click to collapse
Correct !
Sent from my Xperia Z3 using XDA Free mobile app
panzerscope said:
Correct !
Sent from my Xperia Z3 using XDA Free mobile app
Click to expand...
Click to collapse
I flashed it via fastboot, but i couldnt enter any recovery. no led indication or vibration. pressed vol up and down and not working. runing lollipop tho, maybe that's the problem?
kjames2001 said:
I flashed it via fastboot, but i couldnt enter any recovery. no led indication or vibration. pressed vol up and down and not working. runing lollipop tho, maybe that's the problem?
Click to expand...
Click to collapse
Lol, just Remembered, you need Cm to use it.
来自我的 D6603 上的 Tapatalk
kjames2001 said:
Sorry if i should know this, but do we need a supported kernel or something to boot into FOTA recoveries?
Click to expand...
Click to collapse
You need something that, in the init, at boot, waits to check and see if you hit a set key.
"If set key is pushed - load "kernel" (or really ramdisk) from FOTA-partition"
Or more correctly, as @AndroPlus has coded it:
Code:
if [ -n "$POWRKEYCHECK" ]
then
#load FOTA ramdisk
busybox mknod -m 600 ${BOOTREC_FOTA_NODE}
busybox mount -o remount,rw /
busybox ln -sf /sbin/busybox /sbin/sh
extract_elf_ramdisk -i ${BOOTREC_FOTA} -o /sbin/ramdisk-recovery-fota.cpio -t / -c
busybox rm /sbin/sh
load_image=/sbin/ramdisk-recovery-fota.cpio
busybox echo 'Selected FOTA recovery' >>boot.txt
fi
If you want to do that yourself I can attach the original Sony LP kernel, dt.img and ramdisk for you.
Stock ROM
Hi. Just flashed your TWRP on my Z3, but I can't boot into it. What could be a problem? I am using latest CM12. Everytime I press vol + button during boot and lila light I get into CM recovery.
da900 said:
Hi. Just flashed your TWRP on my Z3, but I can't boot into it. What could be a problem? I am using latest CM12. Everytime I press vol + button during boot and lila light I get into CM recovery.
Click to expand...
Click to collapse
Well, to put it easy:
On boot the phone has a script that tells it to look for certain keys to be pushed.
1. If volume up is pushed then go to CM Recovery
2. If volume down is pushed then go to TWRP Recovery
3. If camera button is pushed then go to...
And so on. If there is no script telling the phone to do so (original Sony kernel/ramdisk) then the phone will just simply boot in to android. Nothing tells it to do otherwise.
If there is a script that only tells the phone to boot in to CM recovery or what ever, then that's the only options the phone has.
The kernel (or rather, the ramdisk with the kernel) you use has to have support for booting from the FOTAKernel-partition. If there is no support for it in the kernel then the installed FOTAKernel will just exist there. Not hurting anything, but not doing any good either.
TL;DR - ask the creator/developer of your kernel to add booting from the FOTAKernel as a feature.
Is there any automated or hassle-free way of replacing the nightly CM12 installer script with the script required for this recovery? Or do I have to download the zip manually, unzip, replace the sript manually, rezip, transfer the zip to my Z3, and then flash - every day?
panzerscope said:
No, Fota Recovery is independent from the Kernel
Sent from my Xperia Z3 using XDA Free mobile app
Click to expand...
Click to collapse
Wrong. On Sony devices, once the bootloader is locked, the device will NOT boot the contents of the FOTAKernel partition.
This is similar to older Samsung devices.
The problem with this, of course, is that you normally can't change recovery without changing the kernel.
The workaround developed (IIRC by Dees_Troy of TWRP) was to have the boot kernel extract its recovery ramdisk from the FOTAKernel partition if present, allowing a person to switch recoveries without switching kernels - but they still need a kernel that will read the ramdisk. Also, the recovery ramdisk present needs to "play nice" with the kernel itself, which can lead to problems when Qualcomm or Sony do things that break display compatibility. For example, I'm fairly certain most current Z3 FOTAKernel builds use RGBX_8888, which Qualcomm dropped support for in vanilla framebuffers (like what recovery uses) in newer kernels. So any FOTAKernel ramdisk that tries to use RGBX_8888 will fail, for example, with Sony AOSP (due to it using a newer 3.10 kernel)
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP, for Mi 11 lite 5G
bugs:
backup/restore is unreliable
adb sideload and fastbootd
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
4. select the new image
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
Send me a beer: Crypto (Preferred) | PayPal
Contributors:
@VladV1V , @TheMalachite
Tree:
GitHub - TeamWin/android_device_xiaomi_renoir
Contribute to TeamWin/android_device_xiaomi_renoir development by creating an account on GitHub.
github.com
Kernel:
https://github.com/VladV1V/kernel_xiaomi_renoir
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/xiaomi/xiaomimi11lite5g.html
Sorry, but the installation did not work for me... :-( What i have done:
- i renamend the downloaded file to "twrp.img"
- i copied this file to the internal storage
- i startet the phone in fastboot mode
- then i startet adb
- i used the command "fastboot boot twrp.img"
Then i saw the following:
downloading 'boot.img'...
OKAY [ 2.826s]
booting...
OKAY [ 0.201s]
finished. total time: 3.027s
But the phone only switched off and nothing happend. What's wrong?
EDIT: i solved the problem! I forgot to put the file "twrp.img" into the adb folder. After doing this, the installation worked! Now i tried to make a backup, but it was not possible to select the external sd-card. How can i solve this problem?
Hi, thank's for your work for our device...
I read somewhere, that if we have TWRP installed, that we cannot flash update with fastboot...I want to know if it's true and if yes, how can we flash update..we have to find recovery update, or we can extract from fastboot archive and flash it??
thanks for your answer
Rainman67 said:
Now i tried to make a backup, but it was not possible to select the external sd-card. How can i solve this problem?
Click to expand...
Click to collapse
certainly not available yet...you have to backup in internal storage and then copy to SD...
Another question: how to go back to stock recovery?
Rainman67 said:
Another question: how to go back to stock recovery?
Click to expand...
Click to collapse
I'm on Xiaomi EU ROM. After last update via fastboot Miui Recovery 5.0 comes back.
Great hopefully this leads to development of some easy to flash roms, cant wait to get rid of this buggy MIUI trash.
I tried last version (16th July). Sadly no touchscreen.
Anyway many thanks!
same with #8 boot into twrp and no touchscreen
Peterpaulmarie said:
I tried last version (16th July). Sadly no touchscreen.
Anyway many thanks!
Click to expand...
Click to collapse
FuLuLu said:
same with #8 boot into twrp and no touchscreen
Click to expand...
Click to collapse
Boot TWRP from fastboot and touch will work.
Peterpaulmarie said:
I tried last version (16th July). Sadly no touchscreen.
Anyway many thanks!
Click to expand...
Click to collapse
FuLuLu said:
same with #8 boot into twrp and no touchscreen
Click to expand...
Click to collapse
How did you flash it?
Nebrassy said:
How did you flash it?
Click to expand...
Click to collapse
Fastboot boot twrp.img
Advanced - > flash current recovery
As well tried
Fastboot flash recovery twrp.img
Failed
Also
Advanced - > install recovery ramdisk
But magisk said ramdisk Yes
Peterpaulmarie said:
Fastboot boot twrp.img
Advanced - > flash current recovery
As well tried
Fastboot flash recovery twrp.img
Failed
Also
Advanced - > install recovery ramdisk
But magisk said ramdisk Yes
Click to expand...
Click to collapse
pm me on telegram if you can get logs and have adb access
dannejanne said:
Boot TWRP from fastboot and touch will work.
Click to expand...
Click to collapse
Nebrassy said:
How did you flash it?
Click to expand...
Click to collapse
i just boot to try if it can boot in twrp lol, no need to flash it so far,if needed it i will use the method u guys said(real flash in)
Well then both of you make sure you're actually using the build from afh and only use it for fastboot boot, when you want to flash use flash current twrp don't flash it with fastboot
Touch works when using fastboot boot and when flashed, it Was already tested on multiple devices
@Nebrassy Thanks for your contribution. Looking forward to the stable version with the known bugs fixed and touch works normally, without fastboot.
Thanks again.
doclucas said:
@Nebrassy Thanks for your contribution. Looking forward to the stable version with the known bugs fixed and touch works normally, without fastboot.
Thanks again.
Click to expand...
Click to collapse
Touch already works normally without fastboot
Nebrassy said:
Touch already works normally without fastboot
Click to expand...
Click to collapse
Nebrassy said:
Touch already works normally without fastboot
Click to expand...
Click to collapse
Yes, I can confirm. After start recovery wait 10-15sec touchscreen will work
With the test builds from telegram twrp was not able to recognize my SD card. Is this now fixed?
Is it possible to flash Xiaomi.eu weekly rom only by starting twrp from fastboot without installing it?