Related
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. 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.
Phone look:
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DOWNLOAD:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Thanks very much downloading now
does USB Work ?
Let's hope it charges in recovery
Sent from my HTC One X using XDA
Tried now. Its AWESOME!!!
leventccc said:
Tried now. Its AWESOME!!!
Click to expand...
Click to collapse
yes but does it charge in recovery?
jmkhenka said:
yes but does it charge in recovery?
Click to expand...
Click to collapse
Looks like its not charging. Before flashing rom it shows %56 in recovery and now %55.
I find downloading the recovery, storage usb works? thanks
Enviado desde mi HTC One X usando Tapatalk
No charging (Recovery) for me - but, a great tool!
i`m searching for it, now its here - thx!
time to change the color *g*
This also charges while in recovery and when off..
Good job Guys!!!!
broncogr said:
This also charges while in recovery and when off..
Good job Guys!!!!
Click to expand...
Click to collapse
How do you mean? For me it doesn´t charges while in recovery.
Thanks.
Sent from my HTC One X using XDA Premium HD app
....it says u mst b s-off before installing??????
Sent from my HTC One X using xda premium
lalitsehgal21 said:
....it says u mst b s-off before installing??????
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
No. Just flash it with fastboot.
Gesendet von meinem HTC One X mit Tapatalk 2
inzaghi75 said:
No. Just flash it with fastboot.
Gesendet von meinem HTC One X mit Tapatalk 2
Click to expand...
Click to collapse
Thnx my frnd.....
Sent from my HTC One X using xda premium
Nobody has answered the question yet!! Does USB mounting work?!?!
Sent from my HTC One X using xda premium
Stuart.upton666 said:
Nobody has answered the question yet!! Does USB mounting work?!?!
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
You mean USB charging?
Gesendet von meinem HTC One X mit Tapatalk 2
inzaghi75 said:
You mean USB charging?
Gesendet von meinem HTC One X mit Tapatalk 2
Click to expand...
Click to collapse
Nope. He means usb mounting like if u can access ur sd card while in recovery.
I don't think it works yet though
Why htc unlock is so fail
Stuart.upton666 said:
Nobody has answered the question yet!! Does USB mounting work?!?!
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
no, USB mount does not work in recovery. It appears to be locked out in recovery mode. the workarounds to get it working are one of two things.
(1) fastboot boot awesomeRecovery.img (this works because fastboot then boots recovery on the boot/temporary partition. So the you're not actually in recovery mode
(2) Offmode (this works because again you're again not technically in recovery mode. It uses the recovery ramdisk, kernel, and binaries but its still not technically recovery.
On that note I've seen suggestions that it's possibly a recovery issue with cwm and twrp. Unfortunately it doesn't appear to be the case. If it were then in CWM u wouldn't have usb when u fastboot boot the recovery or in offmode (fair assumption since both these options use the same kernel, ramdisk and binaries as recovery?). Can it be fix? Not that i know of. It looks to me like a total radio or bootloader lockout from using USB in recovery. Which means on a radio or bootloader level USB is disabled in recovery mode.
edit: USB issue could be kernel related and just need for a modified kernel to be compiles for recovery. BUT we don't have kernel source because HTC isn't winnering by releasing it on time.
Code:
//TODO: ADD ABOVE KERNEL SOURCE RELEASE FAIL TO THE MOUNTING ISSUES BELOW
On that note I think we should raise the point to HTC that this locking down of the device does not suite our needs.Key points of fail would be as follows.
(1) Can NOT flash the boot partition from recovery. I've personally contacted HTC on this numerous times and they seem to just not care. Responding with "It's a security issue" and so forth. I would love to know how this is a security issue of any sort. Every other Android device has this ability except HTC devices since they started the HTC unlock ordeal. It's utter fail IMHO and HTC should listen to our needs .
(2) Can NOT flash recovery or boot partitions from system. This issue is NOT a deal breaker and isn't so bad when it comes down to the nitty gritty. But since the issue above exists, flashing with applications like htc dumlock and such were our only options. These work around apps cant be used to flash now because of the lockpout from system and it wouldn't be such an issue if HTC didnt lock us out in recovery from flashing boot.
(3) Can NOT flash P*IMG.zips in hboot/bootloader anymore. For the unlocked device running a custom firmware this is a must. Specially when radio updates and such are needed from the OEM. We seen a big use of this on the Sensation when HTC updated the device from Gingerbread to Ice Cream Sandwich. The update required new hboots, radios, and partitioning to actually use. So in that instead of having to flash a RUU Which didn't exist the only choice was to flash a custom P*IMG.zip that included all the radios and images need to run the builds. At this point we can't update those image/partitions without flashing an RUU. This makes no since and doesn't seem to do anything but make things more difficult on the unlocker to customize and modify their device.
(4) If all the conditions above HAVE to exist. Then why not give us documentation or utilities to flash fimware.zips from recovery like HTC does? When HTC was the proud Nexus device there was full support and documentation available on how to flash firmware on their devices. This made anyone choosing an HTC device blessed with knowing that their device was not only open and unlocked, but when flashing firmware that it was being flashed correctly to Google and HTC's standards. This code has now been moved out of recovery since right before the move to edify scripting and moved to vendor/htc/ (not arguing this choice as thats where it belongs from a maintaining point of view). But the problem is that vendor/htc is proprietary now. Which means Documentation and support for flashing firmware correctly is not available and left to developers of recoveries for the community to figure out. One would think if HTC was standing behind us that they would step up and give us a PROPER/OPEN/REAL unlock, or if they cant for the lame excuse of security concerns, then give us the documentation and utilities to flash the boot and firmware partitions properly. I mean really... what is there to lose there?
(5) WHAT WAS THE POINT OF HTC UNLOCK? It was to reach out and accept us as a community. It was to keep us from having to exploit their firmware and look for holes to gain control of a device we rightfully own. WHAT DID HTC UNLOCK DO? It unlocked the devices at first and with each new revision of the unlock it gets more locked down and harder for us to use it as intended. WHAT DOES THAT LEAD TO? It leads to us hoping someone will take the time out of their life and exploit HTC's firmware so we can have access and control of our devices. I mean, it's bad when u have people poking a device with a paperclip to get a device unlocked to avoid a official unlock.
Bottom line; I'm personally fed up with HTC's unlock. It's absolute crap! It does not serve the purpose it was intended and only makes things harder then they were before. As a devoted HTC customer it has me questioning if my next device will be an HTC. With all the other options that would allow me to spend less time trying to gain proper access to my device and more time actually having fun with it, why choose HTC? Everyone else is shying away for these same issues. Everyone with an HTC unlocked device waits for someone to exploit HTC's firmware and give them a proper unlock. Why not just choose a device without the locked down/unlock instead? IDK but HTC needs to step up and listen to us. Every HTC forum with an HTC Unlock is screaming for these issues to be fixed.
My call to HTC is to fix these issue and/or give us proper documentation on flashing firmware to our devices via custom recoveries. The boot flashing lockout is dumb, pointless, and in NO WAY a security threat AT ALL and is nothing more then a CRAP RESPONSE to something that they sould be working to correct, instead of ignoring. In the end its hurting HTC's relations with developers and is ultimately doing the opposite of what it's original intent.
HTC, PLEASE READ AND LISTEN!!!11ONEone
To everyone else, SPREAD THE WORD!!!ONEone
This is the future of HTC unlock and each new device it gets worse. Maybe HTC will listen and address these issues, then again maybe we will just need to find another OEM that supports us and does listen.
Damn, toast, this is where you are now?!
I'm still using my OG Evo 4g that was rooted via your root method at launch. Still eng hboot. Full openness. First android device for me and I attribute my awesome time with it in large part to you.
That said, great points. I intend to get Evo LTE. Unless it's as locked as you guys are experiencing. Have you considered starting a thread with the with the points you laid out, getting co-signers and submitting to HTC?
(Sorry for kinda off topic)
Sent from my PC36100 using xda premium
so hey guys, recently got a used nexus from a guy, and i'm running Jellybean on it and love it!
however, he changed his splashscreen using LogoMe when he was on ICS to the michigan state logo....i clearly have no desire to see that whenever i boot up the phone, so i want to just get the stock Google image back, or a Nexus image, or anything pertaining to the phone.
i bought LogoMe, but after purchasing, it said it didn't work with my version of hboot (i believe) so i assumed it won't work with JB, so i refunded it.
is there a guide out there as to how to do this manually? i wasn't keen on paying $2.50 just to change a splash image ONE time and never touch it again, so i'm glad i refunded the purchase...but i mean, there has to be a manual way to do this some how. every other phone i've owned (htc eris, inc, rezound, flyer) all have ways to do this, and i would think a phone as dev-friendly as the Nexus would as well!
thanks for any help!
Um hboot? Wtf is hboot?
LOL
Boot loader. What boot loader are you running. And it should support it. It just got an update to support the latest boot loader. And jelly bean. Should have taken a screen shot. The manual way of doing this is extremely tough. From what I've heard.
Sent from my sprint galaxy nexus
bahaha sorry, i come from HTC!
but i actually just saw he updated it for the newest bootloader, so i bought it again. everything works fine now!
jayochs said:
bahaha sorry, i come from HTC!
but i actually just saw he updated it for the newest bootloader, so i bought it again. everything works fine now!
Click to expand...
Click to collapse
Good there are options for the stock logo. But I have a thread started for custom images in Themes and apps section. I even make custom ones.
Sent from my sprint galaxy nexus
ÜBER™ said:
Good there are options for the stock logo. But I have a thread started for custom images in Themes and apps section. I even make custom ones.
Sent from my sprint galaxy nexus
Click to expand...
Click to collapse
awesome! i'm gonna go check it out now, i've been searching for some cool ones to put on!
Edit: n/m
I tried to ask in android-building about changing splash screen, wasn't even accepted nor was I told why it wasn't.
Saw a tut for it on kandroid, but idk if that works.
Sent from my i9250
jayochs said:
is there a guide out there as to how to do this manually?
Click to expand...
Click to collapse
I would like to know how to do this as well. If anyone knows, any info would be much appreciated.
Nexus 7 splash image change
I am also interested in knowing how to change splash for JellyBean on Nexus 7. Any help is appreciated.
thanks.
EDIT: Never mind, major misunderstanding.
Unlawful said:
Well, this was bumped from a while ago and also, it's kinda in the wrong forum.
Any who, generally if you want to replace a splash screen, you place the new .zip of the boot animation into /system/media or /data/local (this is for the Galaxy Nexus, should be the same for the Nexus 7). It's up to you, which one you choose. Search around for boot animations as they should be in the forum somewhere.
Click to expand...
Click to collapse
That's not what this thread is about. It is NOT about changing the boot animation. It is about changing the splash screen, i.e., the screen with "Google" in white and the unlock icon at the bottom.
efrant said:
That's not what this thread is about. It is NOT about changing the boot animation. It is about changing the splash screen, i.e., the screen with "Google" in white and the unlock icon at the bottom.
Click to expand...
Click to collapse
Ooops, major misunderstanding then. Sorry!
jayochs said:
so hey guys, recently got a used nexus from a guy, and i'm running Jellybean on it and love it!
however, he changed his splashscreen using LogoMe when he was on ICS to the michigan state logo....i clearly have no desire to see that whenever i boot up the phone, so i want to just get the stock Google image back, or a Nexus image, or anything pertaining to the phone.
i bought LogoMe, but after purchasing, it said it didn't work with my version of hboot (i believe) so i assumed it won't work with JB, so i refunded it.
is there a guide out there as to how to do this manually? i wasn't keen on paying $2.50 just to change a splash image ONE time and never touch it again, so i'm glad i refunded the purchase...but i mean, there has to be a manual way to do this some how. every other phone i've owned (htc eris, inc, rezound, flyer) all have ways to do this, and i would think a phone as dev-friendly as the Nexus would as well!
thanks for any help!
Click to expand...
Click to collapse
Logo me should be compatible with JB bootloaders. Did you try installing busybox using stericssons installer?
Sent from my Galaxy Nexus using Tapatalk 2
Petrovski80 said:
Logo me should be compatible with JB bootloaders. Did you try installing busybox using stericssons installer?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yes, I think it does. But I'm pretty sure the OP wants to figure out how to do it without LogoMe.
Hm, I just realized something. If OP just wants the original Google boot logo back and not a custom one, isn't flashing the bootloader enough to get rid of it?
Petrovski80 said:
Hm, I just realized something. If OP just wants the original Google boot logo back and not a custom one, isn't flashing the bootloader enough to get rid of it?
Click to expand...
Click to collapse
Although I haven't looked at the bootloader to see if the image is stored in there, you are probably right, it should revert to the original splash screen if you flash a stock bootloader. If not, what would work is to get a hold of someone's SBL partition and flash that using dd.
I was wondering has anyone tried decompiling our hboot and tryig to see if we can re size our portion sizes? Other phones such as the nexus one i believe has a modified hboot(blackrose) that allows resizing htc hero has a nice mod as well called firerat. Patches both recovery and boot.img to allow more size to data or system as needed(set by user). If i have the time & money to buy a test monkey i will be trying to decompile it.
Sent from my rooted GameBoy Advance! ^¬^
Decompiling is disassembly generally. Some decompilers can go back to the source code but it's not the original source and usually harder to read. Also, if you do something wrong in HBOOT you will likely brick your phone.
The correct word is partition not portion.
Maybe if you're interested you can ask the devs who did it. It sounds complicated and very risky. I think a safer option would be to create .img files on the emmc or sdcard storage and tell the ramdisk to boot from there. Boot Manager already accomplishes this and can multi boot ROMs but it hasn't been worked on since the ICS days. I think the devs of that project have said that someone could pick up on it and continue. It doesn't work on Jellybean but that's ideally the smartest concept, though the img method seems to be a bit slower.
Another option is LVM which I mentioned a while back and didn't get around to trying out.
This thread talks about it
http://forum.xda-developers.com/showthread.php?p=26164523
That above looks interesting but the users will also have to be technical enough to be able to create the LVM partitions themselves and set up their system enough to flash a ROM for it. It requires a modified boot.img and recovery.
I had an idea, but I'm not sure if it would work since I'm a beginner and don't know the inside and out of android. For the LG G4 the root method is altering the system.img to insert SuperSU and the root exploit and then flash the img via download mode. My question is:
Couldn't we analyze the bootloader part of the G4 and overwrite it in the same manner as we do with the system.img? I know it's different for every model and the bootloader may not even be located inside the system.img. It's worth a shot asking though.
The aboot partition is android bootloader...to be able to flash a bootloader it would need to be 100% facrory image or it will give a secure boot error...in order to flash a modified img we would need lgs singning code to verify it on boot...read up on bump'd signing and this is what we would need...but lg changed the way they signed their files and it no longer works unless someone figures out the new signing method
I figured as much. If only I could flash a recovery for the at&t model. It is rooted and you can use the terminal app to access recovery mode. The screen comes up with the dead Android picture with no menu however :/.
You certainly can alter/replace the bootloader the same way you do the root partition... Trouble is it's cryptographically signed, so if you change even a single bit, the previous step in the chain (the modem ROM) will reject it and you'll just have a brick.
To unlock bootloader we need to find a way to either change the secure boot flags (efuses) to tell it not to verify the signature, trick the verification process into thinking a modified bootloader is stock, or find a way to hijack the boot process at that stage.
Just ask my previous G4, I totally wiped out the boot partition (and the recovery partition, and the partition table, and everything else)... Nothing prevented me from doing it, but it wouldn't power on after that. Oops.
That sucks! Oh well, I wouldn't be much help since I don't know much about bootloaders and such so I may just sell my AT&T model and buy either the H815 or a different phone.
Hey all, so I'm finally thinking of retiring my Motorola Nexus 6. I've had this thing for so long and was such a great device. Now I'm wondering a few things before going all in.
1) I see people selling them brand new on eBay for as low as $550 to $600. They even show pictures of them in the original box with shrink wrap and all, is this too good to be true?
2) How hard is it to get used to the new A/B partitioning scheme Google is going with now? I'm so used to the traditional scheme Android has always used.
3) How's the dev scene looking for this device? At a glance, there seems to be a decent amount of good roms and great devs, but do these Pixel devices see the same support or near it as the Nexus devices always have?
4) Do roms flash to both system A and B and boot A and B partitions?
5) Does flashing a boot.img file also wipe the recovery entirely since there's no recovery partition on these devices? Is it a danger if you forget to reflash twrp zip?
Thanks guys! Really putting thought into getting this phone.
1) Those are almost certainly Verizon phones. They have locked bootloaders. Many will say "unlocked", they mean SIM unlocked. The only way to be sure it is unlockable is to get a Google version straight from the Google store. You can check IMEI's if the seller will give it to you.
2) Pretend the A B system does not exist. When you flash it flashes current slot, that is all you need to know really. It only switches slots when it does an OTA.
3) Not as much as the Nexus devices but it is decent. I suspect the phones cost keeps some devs away.
4) See 2 above.
5) Yes flashing boot wipes TWRP, as does side loading OTA's and so on. If you forget to put TWRP back it is no problem. I have never installed TWRP on either my 2 or my OG XLs. I do it all from my computer. Certainly I boot to TWRP to install zips. There is a bootable TWRP img file for that.
TonikJDK said:
1) Those are almost certainly Verizon phones. They have locked bootloaders. Many will say "unlocked", they mean SIM unlocked. The only way to be sure it is unlockable is to get a Google version straight from the Google store. You can check IMEI's if the seller will give it to you.
2) Pretend the A B system does not exist. When you flash it flashes current slot, that is all you need to know really. It only switches slots when it does an OTA.
3) Not as much as the Nexus devices but it is decent. I suspect the phones cost keeps some devs away.
4) See 2 above.
5) Yes flashing boot wipes TWRP, as does side loading OTA's and so on. If you forget to put TWRP back it is no problem. I have never installed TWRP on either my 2 or my OG XLs. I do it all from my computer. Certainly I boot to TWRP to install zips. There is a bootable TWRP img file for that.
Click to expand...
Click to collapse
Question about 5 right there, with the old partition scheme Android used, all roms had a boot.img inside the zip that could be flashed with TWRP directly. Do Pixel roms have this boot.img file as well? Not at my PC at the moment so I can't download one and see. I always used to reflash the boot.img file from my roms before updating to a different kernel on my Nexus 6. Thanks! Appreciate the reply!
Also, the A/B partitions only change with an OTA and not a rom flash from TWRP correct?
H4X0R46 said:
Also, the A/B partitions only change with an OTA and not a rom flash from TWRP correct?
Click to expand...
Click to collapse
It depends on the ROM. Some flash both partitions, some only one. You can always change slots with TWRP, so this is no issue at all.
But for me, the Pixel 2XL is the first phone where I don't see a reason to flash a custom ROM, the stock ROM is fantastic :good:
Your mileage may vary, of course.