Related
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!
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
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 Team Win Recovery recovery.img
Turn device off
Move ringer to UP position
Hold down Power and Volume Down
Flash the recovery with "fastboot flash recovery <path to recovery.img>"
Click to expand...
Click to collapse
What works:
Nandroid
Factory resetting
Clearing caches
USB mounting
Untested:
Update zip flashing
Click to expand...
Click to collapse
Changelog:
Sep 08 2012: Updated to 2.2.2.1
Aug 07 2012: Updated to 2.2.1.4
Jul 21 2012: Initial release
Click to expand...
Click to collapse
2char
more info about this recovery?
I only used it long enough to verify that:
It boots
Nandroids work
Fac resets work
USB mounting works
All recs do the same thing, this one just lets you use the touchscreen instead of the buttons
Installing it is the same process, I wont provide info on what's different from CWM, that part you can google
Update.zip also working...tried with multiple zip files also...all working good
Sent from my Dell Venue using xda app-developers app
Updated to 2.2.1.4, no V specific changes
Updated to 2.2.2.1
Does the recovery work for the Venue 8 3830???
ElmoRapz said:
Does the recovery work for the Venue 8 3830???
Click to expand...
Click to collapse
No, they are completly different devices
TheManii said:
No, they are completly different devices
Click to expand...
Click to collapse
I don't get it. Then which devices is this recovery compatible with? Will it work for Dell Venue 7370?
This is for the venue phone, if it was for a different device, it would be listed.
TheManii said:
Re: OP
Click to expand...
Click to collapse
1) As I could not see the compatible devices in OP, want to know will it work on 3840?
2) Can it take backup of boot.img? If no, then is there any other way to backup existing boot.img in tablet? I am told that recovery.img and boot.img are hidden in dell venue
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?
Team Win Recovery Project or TWRP for short. Its a fully touch driven user interface, completely theme-able & you can change just about every aspect of the look and feel.
Now ported to the Galaxy Tab A7 Lite.
Download - You'll always find the latest release in here: https://github.com/DevZillion/android_device_samsung_gta7litewifixx/releasesKnown Issues / Report Issues - https://github.com/DevZillion/android_kernel_samsung_gta7litewifixx/issuesTelegram support group - https://t.me/gta7litegroup
How to install
[Boot Into Download mode by inserting an usb cable while holding both volume buttons]
Flash the latest .tar release from releases.
Hold the recovery combination (Volume Up + Power) while the .tar is flashing via the odin tool.
When booted up into TWRP go Flash and flash this zip, then go to Wipe > Format Data, all your data will be lost.
You can now boot into your system and do whatever you want.
Click to expand...
Click to collapse
Flashing Disabled vbmeta (To boot a modified system)
Spoiler: View
Extract the vbmeta.img.lz4 from the AP slot in your firmware.
Remove it's lz4 compression [for Windows use lz4]:
Code:
sudo apt-get install lz4 -y
lz4 vbmeta.img.lz4
Click to expand...
Click to collapse
Reboot into fastboot from TWRP flash vbmeta using this command line:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Sources
TWRP Source - https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp/tree/twrp-11
Device Tree - https://github.com/DevZillion/android_device_samsung_gta7litewifixx/
Kernel Source - https://github.com/DevZillion/android_kernel_samsung_gta7litewifixx
Click to expand...
Click to collapse
Special thanks to:
TeamWin for the Recovery Project.
Zillion for doing the device tree & kernel.
Click to expand...
Click to collapse
Actual TWRP status: Bugfixing; Try at your own risk and only if you know what you're doing.
Genial!!
Zillion said:
Team Win Recovery Project or TWRP for short. Its a fully touch driven user interface, completely theme-able & you can change just about every aspect of the look and feel.
Now ported to the Galaxy Tab A7 Lite WiFi.
Download - You'll always find the latest release in here: https://github.com/DevZillion/android_device_samsung_gta7litewifixx/releasesKnown Issues / Report Issues - https://github.com/DevZillion/android_kernel_samsung_gta7litewifixx/issuesTelegram support group - https://t.me/gta7litegroup
How to install
Flashing Disabled vbmeta (To boot a modified system)
Sources
Special thanks to:
Actual TWRP status: Bugfixing; Try at your own risk and only if you know what you're doing.
Click to expand...
Click to collapse
it boots, touch does not work but its usable with a mouse and gives an error "unable to mount /data"
dda7lite said:
it boots, touch does not work but its usable with a mouse and gives an error "unable to mount /data"
Click to expand...
Click to collapse
Please, read the How To Install section.
Zillion said:
Please, read the How To Install section.
Click to expand...
Click to collapse
I did but the file that needs to be flashed is unavailable in that link
dda7lite said:
I did but the file that needs to be flashed is unavailable in that link
Click to expand...
Click to collapse
Thanks for reporting the issue, link fixed.
Zillion said:
Thanks for reporting the issue, link fixed.
Click to expand...
Click to collapse
i have other problem error "E:unable to open block device /dev/block/sda: No medium found"
What is vbmeta?
I want to install Elixir Project. Is it necessary to do something from the vbmeta? Or just flashing the rom is enough?
chocovo said:
What is vbmeta?
I want to install Elixir Project. Is it necessary to do something from the vbmeta? Or just flashing the rom is enough?
Click to expand...
Click to collapse
Flash vbmeta is necessary to boot a new system but it's easy to flash too.
dda7lite said:
Flash vbmeta is necessary to boot a new system but it's easy to flash too.
Click to expand...
Click to collapse
I understand that the vbmeta is pulled from original samsung firmware, lz4 format stripped and flashed by AP. Then we implement the command by TWRP and the desired rom is installed.
Is that so?
Does the vbmeta step have to be done every time I put a new rom or only once?
Sorry for my english
chocovo said:
I understand that the vbmeta is pulled from original samsung firmware, lz4 format stripped and flashed by AP. Then we implement the command by TWRP and the desired rom is installed.
Is that so?
Does the vbmeta step have to be done every time I put a new rom or only once?
Sorry for my english
Click to expand...
Click to collapse
I only did once and I didn't use the stock vbmeta I just searched "vbmeta disabled Samsung" it should show up with vbmeta disabled android 11 but works the same on 13 and I didn't use TWRP only fastboot so i don't know how to flash it there.
Btw your English is good don't worry.
After installing TWRP I can't install the fbe. TWRP doesn't recognize my device's internal memory either.
chocovo said:
After installing TWRP I can't install the fbe. TWRP doesn't recognize my device's internal memory either.
Click to expand...
Click to collapse
Yeah
chocovo said:
After installing TWRP I can't install the fbe. TWRP doesn't recognize my device's internal memory either.
Click to expand...
Click to collapse
Because you need to flash the fbe_disabler using some usb otg, external sd card or by pushin the zip to /tmp, flash it and then format /data.
Zillion said:
Because you need to flash the fbe_disabler using some usb otg, external sd card or by pushin the zip to /tmp, flash it and then format /data.
Click to expand...
Click to collapse
Bootloop after
Zillion said:
Because you need to flash the fbe_disabler using some usb otg, external sd card or by pushin the zip to /tmp, flash it and then format /data.
Click to expand...
Click to collapse
My device is a T220.
The touch does not work in TWRP and I use a mouse. I use Micro SD to install the FBE. But when trying to install it gives me an error in the data folder. Although apparently it seems to be installed.
I format data as you indicate and restart in fastboot in TWRP to put the vbmeta by ADB and install a GSI. But it generates bootloop.
I don't know if I'm missing some step.
chocovo said:
My device is a T220.
The touch does not work in TWRP and I use a mouse. I use Micro SD to install the FBE. But when trying to install it gives me an error in the data folder. Although apparently it seems to be installed.
I format data as you indicate and restart in fastboot in TWRP to put the vbmeta by ADB and install a GSI. But it generates bootloop.
I don't know if I'm missing some step.
Click to expand...
Click to collapse
If you really want to flash a gsi and can't get it to work use a fastboot enabled recovery that's what I did
dda7lite said:
Bootloop after
Click to expand...
Click to collapse
Disable vbmeta, it's the only thing I can see you missed.
um i flashed the recovery to my sm-t220 but i do not have a usb otg i am buying it today in the meanwhile i tried to boot back to one ui 5.1 the one i have but it only shows twrpto reboot i used power + volume down but it shows twrp and power + volume up dosnt do anything
Gian-D said:
um i flashed the recovery to my sm-t220 but i do not have a usb otg i am buying it today in the meanwhile i tried to boot back to one ui 5.1 the one i have but it only shows twrpto reboot i used power + volume down but it shows twrp and power + volume up dosnt do anything
Click to expand...
Click to collapse
Force restart and keep the usb cable connected to the PC and tablet then as soon as screen blinks hold volume +and-