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!
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
BETA WARNING:
This version of CWM is now in beta testing.
I need user reports of what zips are compatable/not-compatable.
I will remove the beta tag once I have a fair idea of what update zips are/arnt compatable with CWM 6.0.
For any developers: I will be providing instructions/binaries to work with CWM 6.0 soon.
They will likely not be compatable with streakmod.
Once CWM is out of beta, I would strongly recommend everyone migrating off of streakmod.
Click to expand...
Click to collapse
How to use fastboot:
Setting up fastboot for Windows -XDA wiki
Installing a recovery - XDA wiki
Click to expand...
Click to collapse
Requirements:
Ability to enter fastboot mode
Basic understanding of the command line
Click to expand...
Click to collapse
Install instructions:
Download Clockwork mod recovery.img
streak5
streak5ex (link TBA)
streak5sd8 (link TBA)
Turn device off
Hold down Power and Camera Down
Flash the recovery with "fastboot flash recovery <path to recovery.img>"
Click to expand...
Click to collapse
What works:
Clearing caches
Factory resetting
Nandroid
Update zip flashing
USB mounting
Click to expand...
Click to collapse
Notice:
What to do if your nandroid freezes at /cache, /data, /datadata:
Flash update-CWMfixer-1.zip as an update zip and try again.
OR: Factory reset and manually restore data (Not recommended)
This is portrait only, unless someone is willing to give me code to rotate it 270 degrees it will remain as so
Removing the battery door while recovery is active will cause it to exit (this is intentional, it is also part of the stock 407 kernal)
Streakmod nandroids are not compatable with CWM. You may be able to get it to work by copying the contents of "rom_backup" to "clockworkmod", but this is not supported
If you get errors about not being able to mount your SD card, power the device off and remove the battery for a moment, then try again
Notes about sd-ext:
If you get the error message while nandroid: "sd-ext.img not found. Skipping restore of /sd-ext." This is normal, as sd-ext is an optional partition.
If you get the error message while formatting: "E: format_volume: make_ext4fs failed on /dev/block/mmcblk0p2", same as above
Click to expand...
Click to collapse
Controls:
Vol Up: Scroll up
Vol Down: Scroll down
Camera: Select item
Back: Go back
Click to expand...
Click to collapse
Changelog:
Sep 09 2012: Updated to 6.0.1.2
Aug 21 2012: Removed beta tag, added workaround for nandroid issues
Aug 07 2012: Updated to 6.0.1.1
Jul 21 2012: Updated to 6.0.1.0 - entered beta phase
Jul 20 2012: Updated to 6.0.0.9
Jul 18 2012: Initial release
Click to expand...
Click to collapse
2char
glad to hear this
i am trying
So is this the touch version?
it displays nothing when moving up (or down)
and show back when moving for the second time
not just display ，
if you want to select the 2nd (4th ，6th ... ）item
you must moving up and down till it shows "BACK menu button enabled" or "BACK menu button disabled"
and is there anying new in CWM6007?
i had posted CWM5027 chinese version
most functions are working well
what about change it back to english version?
and i had seen a special version of CWM4010
it has a new function “advanced backup”
i think it's very useful
http://bbs.anzhi.com/thread-3182311-1-1.html
the Attach File is for ZTE X876
it is NOT for streak
Crinos512 said:
So is this the touch version?
Click to expand...
Click to collapse
no
If by advanced backup you mean selective backing up of partitions.
I had considered that many months ago, but I didnt add it because it wouldnt matter. (I never had a fully working CWM previously)
CWM never liked booting on the S5 for whatever reasons.
Adding in selective backups shouldnt be terribly difficult, but I'm not really interestested in modding CWM, (excluding the S5) all my devices have working CWM 6.0.0.x and the source code is available for anyone interested.
I'm trying to modify CWM as little as possible to make it easier for future changes. CWM 6.0 was only released a couple days ago and we're already at 6.0.0.7+
The biggest change in 6.0 is "dedupe" where nandroids are base + delta so if you constantly nandroid, the deltas become very small.
Besides the screen I would assume everything works and it would be ready to replace streakmod, but the screen issue is very annoying.
Also to note: I will attempt to port TWRP later, as it DOES support RGB_565 displays still, and since we have an ICS kernel, it might just work.
somewhere from CWM 5.5 -> 6.0 RGB_565 displays took a back seat to RGBX_8888/BGRA_8888 displays and I guess wasnt really fixed.
Edit: The other major feature is that I dont have to make multiple versions of every update zip.
Currently it's S5/V and S7 and nothing for the S10.
Streakmod doesnt have much in /sbin, CWM has busybox, and a bunch of filesystem utils.
so instead of needing:
Code:
mount("MTD", "system", "/system"); (for the S5/V)
mount("ext4", "/dev/block/mmcblk3p3", "/system"); (for the S7)
mount("ext4", "/dev/block/mmcblk0p3", "/system"); (for the S10)
Or make a new one for each specific device I'm gonna support
I can do
Code:
run_program("/sbin/busybox", "mount", "/system");
and that will work with any device with any device with a recent enough recovery
Edit2:
If and when I get CWM 6.0 working on the S5, I will be making all future update zips "generic" as in they should be able to install on any device (assuming they're relevent for that device)
Examples of such are: Superuser.zip, Gapps
Edit3:
After doing a test zip, I can in fact use the same mount script on all 4 devices instead of needing 3 seperate ones.
Unfortunately like previously mentioned they simply dont work on streakmod as it doesnt have busybox.
Edit4:
I will be internally using CM6.0 now, regardless of if I can fix the framebuffer issue.
Any future S5-specific update zips will be deemed "legacy update" zips
I will be updating to CWM 6.0.0.9 as soon as it's available.
Also: I have no idea of older update zips (from whoever) will work on CWM 6.0, there's many changes to the scripting from 1.8 -> 6.0 (streakmod is based on a very old CWM) and even edify based update.zips may not work if they're using an old enough binary.
Updated to 6.0.0.9 now,
there's no changes specific to the S5 though, so everything prevous still applies
TheManii said:
Updated to 6.0.0.9 now,
there's no changes specific to the S5 though, so everything prevous still applies
Click to expand...
Click to collapse
maybe this will help people to test new recovery without PC
just flash it in recovery as ROMs
2 files?
I assume recovery6009a.zip is the CWM recovery...what is the other one?
The other one is likely streakmod from the version number
I think I got it
Edit: I am in the middle of testing it, but I think I will be able to release a full version soon
CWM 6.0.1.0 is now released an in the beta phase!
What I need tester reports of:
flashing recent roms
flashing random (things you would normally expect to flash in streakmod) zips
fac resetting
I believe nandroids are already reliable, but any reports to re-confirm/deny would be welcomed.
USB mounting works fine
I will be migrating all my utilities to be CWM compatable and marking streakmod-compatable versions as "legacy"
ALL HAIL TheManii!!!
Dude, you are god! THANK YOU!
what are the odds of a flashable Zip version? Can't wait to try this out too!
Crinos512 said:
2 files?
I assume recovery6009a.zip is the CWM recovery...what is the other one?
Click to expand...
Click to collapse
these two could be used to flash recovery to clockwork mod recovery 6.0.0.9 or to streakmod 0.3.2.8these are zip flash ,without PC
Controls:
•Vol Up: Scroll up
•Vol Down: Scroll down
•Power: Select item
•Back: Go back
Click to expand...
Click to collapse
1. the key to select item is camere ,not power
2. i think using back or home to select item will be better
then we can only use "back \ menu \home"
3. could you please add utf-8 support then i can translate it to chinese version
manics said:
1. the key to select item is camere ,not power
2. i think using back or home to select item will be better
then we can only use "back \ menu \home"
3. could you please add utf-8 support then i can translate it to chinese version
Click to expand...
Click to collapse
Is this the flashable zip via streakmod recovery?
manics said:
1. the key to select item is camere ,not power
2. i think using back or home to select item will be better
then we can only use "back \ menu \home"
3. could you please add utf-8 support then i can translate it to chinese version
Click to expand...
Click to collapse
i dont like using the touch key for CWM coz sometime it thinks u pressed it twise, like a double tap.. it gets very annoying
sinan33 said:
Is this the flashable zip via streakmod recovery?
Click to expand...
Click to collapse
yes,
not only streakmod but also clockwork mod
Key Features:
Ability to save custom recovery settings
Default partitions to back up
Default zip folder location
Default color theme (lots to choose from) (Thanks to ffolkes!)
Default Time Zone (for more accurate time stamps)
Zip Signature Verification
Zip md5 Verification (looks for file with zipname.zip.md5)
Ability to flash multiple zips in one go
Ability to select which individual partitions to backup, and restore.
Ability to choose compression or no compression backups.
Compression takes longer of course, but you save roughly half the space. EVO3D's stock system uncompressed is ~800mb, 380mb compressed. You choose.
Ability to auto restore GAPPS on zip flash (for CM based ROMS)
Ability to auto reboot after successful flashes (for the lazy)
Some devices utilize their capacitive buttons in recovery.
Home - Main Menu
Menu - Advanced Menu
Back - Up a Menu Level
Search - Select Current Selection
Battery Level and Timestamp (Better safe than sorry)
HTC Dumlock Instructions:
Install the build of TWRP using your method of choice, but you must actually flash TWRP to recovery. No fastboot booting it. We need it in recovery so that this build of TWRP will be flashed to your boot. This new build of TWRP has features in it to easily restore your original boot.
Reboot into recovery.
Make a backup of your phone.
Tap Advanced.
Tap HTC Dumlock. (If you don't see HTC Dumlock then you need to remove any custom TWRP theme that you might be using.)
Tap Install HTC Dumlock. This will install the app and binaries needed to make everything work nicely.
Reboot your device.
Find and open the HTC Dumlock app.
If/when prompted, give the app root (SuperUser) permissions.
Tap the Execute HTC Dumlock button.
Wait patiently for a couple of minutes. It takes a little while.
If your device doesn't reboot automatically, reboot it manually. Reboot it normally. DO NOT reboot it to recovery.
You should now be in your recovery, but your recovery is flashed into boot.
Tap Advanced.
Tap HTC Dumlock.
Tap Restore Original Boot.
Use your recovery like normal. Flash a new kernel. Restore a backup with a different kernel. Do whatever you please!
Consider donating!
Note, you must repeat steps 8 through 17 EVERY TIME you need to flash boot.
Installation:
Unlock bootloader at http://www.htcdev.com/bootloader/
Make sure fastboot is unchecked in power options and turn phone completely off
Boot into HBOOT then Fastboot
From fastboot. Use command "fastboot erase cache"
From fastboot. Use command "fastboot flash recovery recovery.img"
Video Tutorials:
How To Unlock The Bootloader EASIEST Method - https://www.youtube.com/watch?v=r0gzJdwCxX0
How To ROOT EASIEST METHOD - https://www.youtube.com/watch?v=S1KmsxO84UU
PC USB Mass Storage:
You can't! http://teamw.in/DataMedia
Downloads:
If rooted. You can flash using GooManager in the Play Store
http://techerrata.com/browse/twrp2/m7/
Thanks..
I have a buddy who is picking one up this week.. We all have the "one" from sprint and it works great.
Just ordered mine
Sent from my HTC One S
and you continue to pop up everywhere! lol. I can see it's the same recovery for the int'l/at&t models. I'll just mirror my toolkit here as well!
hasoon2000 said:
and you continue to pop up everywhere! lol. I can see it's the same recovery for the int'l/at&t models. I'll just mirror my toolkit here as well!
Click to expand...
Click to collapse
hahahaha I'll try to pop up on every new HTC device. :laugh:
hasoon2000 said:
and you continue to pop up everywhere! lol. I can see it's the same recovery for the int'l/at&t models. I'll just mirror my toolkit here as well!
Click to expand...
Click to collapse
Great! I used your Toolkit for my girlfriends One S! Keep up the great work. I should be going to the Tmo Store soon to decide if I want it or not.
Weird I am unable to have any zips show up here so I can flash them.. any idea why nothing shows up in TWRP?
Sent from my HTC One
I just tried using adb sideload and it transferred the rom zip, and the rom looked like it was installing, it even said it was installed. However, when I went to reboot, TWRP says 'are you sure no OS installed?' sure enough, i got stuck at the HTC One screen for a long time afterwards. The rom installed fine with adb push, then installing it. Just wondering if this is me or other people experience it.
Billyvnilly said:
I just tried using adb sideload and it transferred the rom zip, and the rom looked like it was installing, it even said it was installed. However, when I went to reboot, TWRP says 'are you sure no OS installed?' sure enough, i got stuck at the HTC One screen for a long time afterwards. The rom installed fine with adb push, then installing it. Just wondering if this is me or other people experience it.
Click to expand...
Click to collapse
Idk about this phone but did you make sure the boot.img was installed. Try flashing manually the boot.img.
Can anyone help please.I flashed twrp v 2.5.0.0 but I think I checked fast boot in power for some reason . Now twrp is giving me some problems like it doesn't recognise my internal storage and can't flash supersu or superu ,so my device is still unrooted. Could anybody tell me what should I do now? Thanks in advance and sorry guys if I'm using the wrong thread.
Sent from my HTC One using xda app-developers app
Delete.
Hello everyone... I really like the way TWRP works even though the backup files seem to be proprietary. I especially like the way the wipe area allows you to select other specific items under "advanced." One question I have though is this... is the "fix permissions" option working for everyone? Would this not work on certain ROMs? I am just curious. Thanks for your insight!
cant flash the recovery. it says out of memory :/
help pls
Could someone please link me to a flashable zip? No OS installed. outdated TWRP >_<
i want to ask that if i can flash that recovery then rooted my phone then back to stock recovery my HTC GPE works or not ??
sadeg111 said:
i want to ask that if i can flash that recovery then rooted my phone then back to stock recovery my HTC GPE works or not ??
Click to expand...
Click to collapse
It should work as long your bootloader is unlock.
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.
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?