Hi!
It's a demo TWRP recovery, built for this device. It just demo, and, I'm afraid, almost nothing work correctly. No touch, support, so only USB mouse can be useful for any input. But, surely, it's better than nothing
A fully working TWRP for the 701 would be a dream come true.
I have a question for the developers regarding TWRP and this device. I have heard that there is only maybe 4 megs for recovery to use in the TF701 (tegra 4 chip) and not enough for the TWRP libraries that are needed for TWRP touch. My question is this- can the libraries needed be compressed somewhere in a self exstracting file and a script be written into TWRP that would extract the libraries to the devices ram, or external sdcard and used by TWRP recovery for a touch mode?
loner. said:
I have a question for the developers regarding TWRP and this device. I have heard that there is only maybe 4 megs for recovery to use in the TF701 (tegra 4 chip) and not enough for the TWRP libraries that are needed for TWRP touch. My question is this- can the libraries needed be compressed somewhere in a self exstracting file and a script be written into TWRP that would extract the libraries to the devices ram, or external sdcard and used by TWRP recovery for a touch mode?
Click to expand...
Click to collapse
It's more complicated than that. There is actually 8MB available in the recovery partition. We have built a version of TWRP with and without touch and neither function correctly and are unuseable.
CWM recovery seems to work better with the touch drivers but was still unstable for me - regular lockups and freezes.
Trel725 said:
Hi!
It's a demo TWRP recovery, built for this device. It just demo, and, I'm afraid, almost nothing work correctly. No touch, support, so only USB mouse can be useful for any input. But, surely, it's better than nothing
Click to expand...
Click to collapse
Can I get the kernel source as per the GPL & XDA's policy ....
http://forum.xda-developers.com/showthread.php?t=2645321
Thx Josh
lj50036 said:
Can I get the kernel source as per the GPL & XDA's policy ....
http://forum.xda-developers.com/showthread.php?t=2645321
Thx Josh
Click to expand...
Click to collapse
I just used CM source http://wiki.cyanogenmod.org/w/Tf701t_Info
And TWRP source from github.
Thanks to lj50036, _that and bogdacutu + trel57 for kicking this off we now have fully working touch TWRP that is flashable and stable.
TEASER SHOTS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So... any progress on this, or a release date? Been almost a month since those teasers were posted.
---------- Post added at 08:40 AM ---------- Previous post was at 08:38 AM ----------
brianhill1980 said:
So... any progress on this, or a release date? Been almost a month since those teasers were posted.
Click to expand...
Click to collapse
My bad, didn't see the post for it in the other forum. Might be worth updating the OP to reflect this.
Related
These recoverys are based on the latest CM9 source which I modified for myself. We all know this is Koush's hard work, I am just compiling with a few changes...
-source
-touch support thanks to @gweedo767
I would take screenshots, but ddms doesn't work in recovery on the galaxy s3...
It's too bad, because these look absolutely gorgeous on the sgs3, even in recovery
Note* if rom manager doesn't recognize the recovery, flash official recovery from the rom manager app, then use odin to install the mod one in and you will be good to go
to install
1-flash tar in Odin as PDA
2-use mobile odin
(read about it here)
cool trick to get rid of extra no's
(or get the one_confirm.zip from the bottom of the page and extract it to /sdcard/clockworkmod)
Code:
adb shell
touch /sdcard/clockworkmod/.one_confirm
I9300
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i9300_og-ec_touch-halo_mc-r1.1-v5.8.4.3.tar
Click to expand...
Click to collapse
todo-
external sd support
more designs
battery level
since ddms screenshot in recovery mode for the galaxy s3 doesn't work yet, here are the actual images
master chief
Code:
#define MENU_TEXT_COLOR 177, 170, 115, 255
#define NORMAL_TEXT_COLOR 37, 112, 0, 255
menu_top + menu_sel...gr_color(247, 255, 65, 255)
one more just in case
great
Thanks. ill be flashing them now.
Sent from my GT-I9300 using xda premium
The process seems to stop half way and not move when trying to flash the recovery image in Odin.
Is it possible to flash a .ZIP from the externalSD in this Recovery? When I got it right - on the other available Touch-Recovery there's no externalSD supported.
no, it's not possible, Yet.
I've installed this recovery, no external Sd supported.
cargobr151 said:
no, it's not possible, Yet.
I've installed this recovery, no external Sd supported.
Click to expand...
Click to collapse
no, it's not possible, Yet.
ogdobber said:
no, it's not possible, Yet.
Click to expand...
Click to collapse
Sounds good I've flashed it anyways. Works like a charme! Good work!
Maybe you can increase the font-size a little in the next version like in the Recovery (for the Galaxy Nexus) of Nathan Grebowiec (https://plus.google.com/u/1/102668644728495519296/posts/A6dUdXr7y6a)?
Nice work for the touch recovery dude .
PS : Ahah masterchief, add me on XBL : zSaNgO
bumped version to 5.8.4.3
really no significant change...
extsd is still in the works:fingers-crossed:
i9300_og-ec_touch-halo_mc-r1.1-v5.8.4.3.tar uploaded.
slight color change (made a mistake was 155 should have been 115)
Friends,
Clockwork Mod Recovery 6 is out and the sources are at github to grab and as the title suggests can someone port it to our devices, Here's changelog
Now It's The Final build
Here is what Koush said on his G+ Account
New backup format that deduplicates data between backups.
Faster backups.
Fixed restores > 2GB.
Minor UI tweaks (new background, animated Android)
Click to expand...
Click to collapse
Here Koush explains how the new CWM method works that makes the backup files so small in size
New ClockworkMod Backup Format
Don't delete /sdcard/clockworkmod/blobs
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 c5273884b90d490134e7737b29a65405cea0f7bb786ca82c63 37ceb24de6f5ed, it looks for /sdcard/clockworkmod/blobs/c5273884b90d490134e7737b29a65405cea0f7bb786ca82c63 37ceb24de6f5ed
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
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The original Post on G+ : http://goo.gl/jGgl5
Post courtesy
I specially request TJ, Napster (if he reads this ), ardX, CK and Aben to look into this as they are the people those who can work on this.
Thanks for reading it.
wait a moment, still learning and testing it
*update: sorry, still have minor bugs, as I's still learning it, maybe tomorrow, as now I'm sleepy
you can test it here,but its not stable enough, so don't use it as daily
and please post bug if you can find
known bugs :
- cant mount usb
- random reboot
As I don't find any official section for the huawei u8650 can I ask if someone could port this recovery for my device here?
ardX said:
wait a moment, still learning and testing it
*update: sorry, still have minor bugs, as I's still learning it, maybe tomorrow, as now I'm sleepy
you can test it here,but its not stable enough, so don't use it as daily
and please post bug if you can find
known bugs :
- cant mount usb
- random reboot
Click to expand...
Click to collapse
Is it for .35 kernel base or .32 or will work on both
Edit: It Crashes during restore of old backups made by CWM 5.x on .35 kernel baseband
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
General Info:
More information about Firefox OS (B2G) is available here and here. So... I saw this and couldn't resist having a little sneaky play around with it. This is NOT a daily driver. This is NOT stable. It's pre-alpha. If you want something to use as a phone, this isn't it. If you just want to use your phone as a phone, you need android rom.
With that aside, and with the clear understanding that while this won't brick your phone, it's nothing to do with me if it did for some reason, or likewise if your cat (or other cute pet) suffers a painful death as a result of flashing this. At your own risk, like everything else here on XDA-Developers!
So without further ado, WTF is this? Well, it's a project from Mozilla (the lovely people behind the Firefox browser). I won't go into details, suffice to say I suggest you read a lot over at their wiki - start off at https://wiki.mozilla.org/B2G and work your way through the pages.
These builds can only be installed with CWM!!!
Instructions for installing the first time :
Wipe data/factory reset
Format system
Install data.zip
Install system.zip
Upgrade Instruction:
Format system
Install system.zip
Download:
Data
System
Code:
Build 1:
- Initial release
Follow me on G+ for more news:good:
Hi) I dont have Nexus S, so I cant test it( Please test it and send me what works)
Tell me the chances of bricking my device with this.
ej8989 said:
Tell me the chances of bricking my device with this.
Click to expand...
Click to collapse
Zero
Axel2033 said:
Zero
Click to expand...
Click to collapse
hi Axel...see you here again (Love your work on my old phone galaxy ace) Will test now and report ASAP :good:
xxxMADxxx said:
hi Axel...see you here again (Love your work on my old phone galaxy ace) Will test now and report ASAP :good:
Click to expand...
Click to collapse
Nice to hear, thank you)
Doesn't boot. Just hangs at google logo.
andrewanemic said:
Doesn't boot. Just hangs at google logo.
Click to expand...
Click to collapse
confirm
Are you going to try to make this bug less? Or as far as possible?
Sent from my Nexus S using Tapatalk 2
http://forum.xda-developers.com/showthread.php?t=1924367
for those interested.
Doesn't boot.
That was confirmed 10 days ago
any news?
Sensitivity said:
any news?
Click to expand...
Click to collapse
I flashed this fox-os and does not boot extract boot.img from zip file and flash via fastboot ... does not boot logcat return with
Code:
[email protected] >> adb logcat
- exec '/system/bin/sh' failed: No such file or directory (2) -
Is there Flash support in the browser?
For custom ROM addicts, the custom recovery is an essential tool, and lately Team Win Recovery Project (usually shortened to "TWRP") has been the most popular option as of late. Today Team Win upgraded the core recovery to version 2.7.0.0, with more new features than you can shake a stick at. The latest version is available for dozens of officially-supported devices on the Project website.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Among the more interesting additions in TWRP 2.7 are sideloading from the /tmp directory on encrypted devices, support for a mouse via a USB OTG connection (for devices with broken touchscreens), haptic feedback for buttons and finishing actions, and caps lock support for keyboards.
LINK TO THE HTC VERSION OF THE TWRP 2.7
https://mega.co.nz/#!FNIXEAoA!dSEwJoRtYHyLv30P6-xL1oUed68p_15AUZ2SWD8PmsU
Click to expand...
Click to collapse
Zeus20 said:
For custom ROM addicts, the custom recovery is an essential tool, and lately Team Win Recovery Project (usually shortened to "TWRP") has been the most popular option as of late. Today Team Win upgraded the core recovery to version 2.7.0.0, with more new features than you can shake a stick at. The latest version is available for dozens of officially-supported devices on the Project website.
Among the more interesting additions in TWRP 2.7 are sideloading from the /tmp directory on encrypted devices, support for a mouse via a USB OTG connection (for devices with broken touchscreens), haptic feedback for buttons and finishing actions, and caps lock support for keyboards.
LINK TO THE HTC VERSION OF THE TWRP 2.7
Click to expand...
Click to collapse
thanks for the info, much appreciated! :good:
Just a side note: maybe you should have posted this in the ''General'' section instead because its not related to Q&A/Troubleshooting.
But again many thanks for keeping us up to date
alray said:
thanks for the info, much appreciated! :good:
Just a side note: maybe you should have posted this in the ''General'' section instead because its not related to Q&A/Troubleshooting.
But again many thanks for keeping us up to date
Click to expand...
Click to collapse
I was debating which category to put it in. If it could get moved by a mod to general I think you may be right @alray
Sent from my HTC One using xda app-developers app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP Recovery for the Galaxy J3 2016
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
Bugs:
Nothing...
Download: TWRP-3.2.1
if anyone can tell me if it works and it's stable, i would thank it sm
does not work
tvrp bootlup not working
Max456l said:
does not work
Click to expand...
Click to collapse
ooooh holy cr- then im gonna release a fix soon I guess, but for the j1 mini prime it was so easy to port this TWRP
Try this guys, this one might work:
ok i'll check it out
Twrp does not work, crashes and instead of it, stock recovery
aleksandr mi said:
Twrp does not work, crashes and instead of it, stock recovery
Click to expand...
Click to collapse
so it boots to stock...the problem is in the twrp
when will twrp be released?
ALEKSKART said:
when will twrp be released?
Click to expand...
Click to collapse
soon. i need to figure it out why it isnt booting up.
notnoelchannel when will twrp be released
NMTdontknow said:
notnoelchannel when will twrp be released
Click to expand...
Click to collapse
First off say hello first please,
Second: I'm looking for testers
I have that device in my collection, how can I help you testing?
L3P3 said:
I have that device in my collection, how can I help you testing?
Click to expand...
Click to collapse
Sorry, I gave up on this device :/
Can you link to your GitHub repo for this so others can give it a try?
Also, please remove or hide the link from initial post and add a disclaimer that you gave up... I almost flashed that file...
L3P3 said:
Can you link to your GitHub repo for this so others can give it a try?
Click to expand...
Click to collapse
can't. device tree is unstable and the recovery isn't bootin'
notnoelchannel said:
can't. device tree is unstable and the recovery isn't bootin'
Click to expand...
Click to collapse
Could you at least tell me what you tried so someone else (or me) can continue where you left without having to figure out all self?
L3P3 said:
Could you at least tell me what you tried so someone else (or me) can continue where you left without having to figure out all self?
Click to expand...
Click to collapse
. making custom kernel didnt work
- using stock kernel didnt work
- using a custom prebuilt kernel from djemans twrp didnt work
- using a custom stock kernel didnt work
thats all i tried.the device tree is excellent