Related
Team Win Recovery Project 2.2, 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.2.0):
- On-screen keyboard in recovery! -- supports long press, backspace repeat, and swipe left deletes everything left of the cursor
- Name new backups and rename existing backups
- Rename files and folders in the file manager
- Pseudo-terminal emulator
- Support decrypting an encrypted data partition on Galaxy Nexus (enter password using keyboard)
- Backup archive splitting -- allows backup and restore of data partitions larger than 2GB
- Simplified XML layout support between resolutions
- Added dual storage selection radio buttons to zip install, backup, and restore pages
- Improved zip install compatibility
- Updated update-binary source code
- Numerous small bug fixes and improvements
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct 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 30 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.
ORIGINAL POST (from May):
This is a work in progress.
TWRP (Team Win Recovery Project) 2.1 by TeamWin is an alternative recovery (instead of ClockworkMod) that is a good companion for Goo Manager. See this video for more info.
This is an experimental, mostly untested build of TWRP2 for entertainment purposes only. USE OR ATTEMPT TO USE ENTIRELY AT YOUR OWN RISK. It is intended for those who are willing to risk any and all damage, loss, and STD infection to their hardware, data, person, and associates resulting from this software. Do not attempt to use unless you understand and accept these risks.
Please note this is using the still-being-developed 3.x kernel.
I am including the raw .imgs which can be fastbooted or used on an SD (rename recovery.img.sdcard to recovery.img and put on SD in place of the existing version). Which I don't recommend doing of course, given the disclaimer above. Remember I don't have an NT so I haven't run this... ever.
Finally, this has not at all been put through any kind of paces. That's for you, assuming all the risks, to do. And report it back here for everyone's benefit.
Thanks to dees_troy, eyeballer and demetris_I & frustro for testing this. I'm busy the next few days, so I'm volunteering demetris_I, who has it running, to answer anyone's questions per his availability
twrp-2.1-nt-2012-05-17E-fullofbugs.tar.gz
History
6/12/12 - updated first post.. No binaries yet.. Can someone make one?
5/17 -
Updated 3.0 kernel to support new 512GB NTs (untested)
Updated twrp codebase to latest
Newer cm9 stuff as well
5/17B&C
Use cmdline from u-boot.bin to determine max ram size.
fix device showing up as "B" to "NookTablet"
5/17D&E
I can't remember. But it's betterer.
Has anyone successfully flashed this yet? And can anyone offer up the steps in a more-in-depth way?
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Well... there's always update.zip
I haven't tried it, but I'm guessing if you've installed fastboot to your computer, this should work:
1. boot into cyanoboot and choose Fastboot from the menu.
2. On your computer, navigate to where recovery.img is and enter into the terminal
fastboot flash recovery recovery.img
Or... maybe someone could whip up a quick update-twrp2-nt-2012-5-14.zip maybe?
I guess that someone might as well be me. This is intended for use with an existing cwm recovery. This will flash to emmc...maybe.
update-twrp-2.1-nt-2012-05-14-fullofbugs-emmc.zip
MD5: 337269fa77017150325d398216a6dd3c
Thoroughly and completely untested. I really don't know if it will even install, and if it does, if it will work. See all disclaimers above, plus make up some additional ones yourself.
Edit: See below about a possible issue with possible difficulties accessing the external SD card. Internal /emmc seems to work consistently. Looking into it, but if you want to help debug this, that would be much appreciated. Just knowing what works or doesn't work and log samples (dmesg via adb) would be great.
Will this completely replace CWM as the recovery? Or will it run alongside. Anything else I should be aware if before I try to flash (do it on a fresh rom install, will I be able to restore from a backup if something goes wrong etc etc...)
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
It will replace cwm.
Rom doesnt matter , they reside in different partitions.
Cyanoboot is all you want if anything goes wrong or/and CWM/TWRP from sd card so you can dd the recovery.
SilentStormer said:
Will this completely replace CWM as the recovery? Or will it run alongside. Anything else I should be aware if before I try to flash (do it on a fresh rom install, will I be able to restore from a backup if something goes wrong etc etc...)
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Click to expand...
Click to collapse
Should replace it completely. I say should because if you do this with the update.zip, you will be the first one to try it.
Oh, Mister_Argent is trying it on IRC...
The Zip seems to work! Android boots fine, and it's entirely possible to get into TWRP via Cyanoboot. This might just be me, but the terminal seems to lock up...
Oh hey argent, so the zip works? And is it worth my time to change from CWM to TWRP?
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
SilentStormer said:
Oh hey argent, so the zip works? And is it worth my time to change from CWM to TWRP?
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Click to expand...
Click to collapse
There may be issues with selecting the external SD card... not sure what the deal is. I believe demetris_I checked this out previously, but you can use the internal (/emmc) one though until this is worked out/confirmed one way or the other.
Note: if anyone is good at verifying/debugging, post any relavent dmesg stuff + what your theory is on the issue
So we can still flash stuff through emmc?
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Indirect gave me this command to flash recovery via terminal emulator and it worked out nicely
dd if=/recovery.img of=/dev/block/mmcblk0p3
Click to expand...
Click to collapse
where "/recovery.img" is the file path/file name of the recovery image
Recovery looks nice. I'll do some more playing with it later when I have time.
fattire said:
There may be issues with selecting the external SD card... not sure what the deal is. I believe demetris_I checked this out previously, but you can use the internal (/emmc) one though until this is worked out/confirmed one way or the other.
Note: if anyone is good at verifying/debugging, post any relavent dmesg stuff + what your theory is on the issue
Click to expand...
Click to collapse
No issues with external sd it just take some seconds to mount, is not instant but it will mount.
8gb NT. Successfully flashed internally; will test, log and provide feedback on any issues.
The zip file name is overly long and CWM doesn't like it. Renaming to something shorter solves the issue.
In my experience with other android devices, it is normally recommended you wipe 'dalvik cache' whenever changing / updating kernel. Perhaps this step will avoid some issues for people.
Edit: Flashing gapps update via Goo Manager results in failure of rom to load after Cyanoboot screen. I did not choose to wipe dalvik / cache in Goo Manager. Also unable to access Cyanoboot via N. Screen appears but does not seem to respond and automatically boots emmc (blank screen).
Re-download Gapps and press the buttons combo to access twrp/cwm and reflash (power+N)
What rom and what gapps you are using?
Make sure they are downloaded ok before flashing.
demetris_I said:
Re-download Gapps and press the buttons combo to access twrp/cwm and reflash (power+N)
What rom and what gapps you are using?
Make sure they are downloaded ok before flashing.
Click to expand...
Click to collapse
I could not access twrp as already stated, because Cyanoboot did not respond to button press. I've managed to get access to CWM via sdcard and reflashed another gapps. CM9 still will not load.
Next, I plan to wipe everything and flash CM9 anew.
Edit: Still won't boot. Looks like I have a brick to fix.
Edit2: Flashing CWM internally got everything working again. Cyanoboot would previously go automatically to loading from emmc; there was no delay / opportunity to press N to access the menu. Now the delay occurs and I have access. CM9 also loads.
Edit3: Reflashed TWRP internally again. It's not working on 8gb NT. It doesn't break Cyanoboot or prevent CM9 from loading, but any attempt to load TWRP results in a black screen.
How do you flash twrp?
If you flash the zip can you please try the fastboot way?
fastboot flash recovery twrp.img, thanks
demetris_I said:
How do you flash twrp?
If you flash the zip can you please try the fastboot way?
fastboot flash recovery twrp.img, thanks
Click to expand...
Click to collapse
I flashed the above emmc zip via cwm internal
I have adb working, however fastboot seems to require a separate driver to work in windows. I've searched the forum and have not found a clear answer.
I'm guessing the 3.0 kernel doesn't have support added for the 8gb nts yet. I guess maybe I could look into that...
Sent from my HTC Vision using XDA
So to run this I have to be running the new 3.x kernel? Or can I just flash the zip if I'm on the 2.x Cm9
(16gb Tablet)
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
SilentStormer said:
So to run this I have to be running the new 3.x kernel? Or can I just flash the zip if I'm on the 2.x Cm9
(16gb Tablet)
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Click to expand...
Click to collapse
Recovery is separate from the rom. You'll be fine. I have it running on my 16GB.
Hi all
I am opening up this Q&A thread as extension to my ROM threads, for the simple reason that ever since there is a limitation preventing new users from posting in development threads, I get flooded with PM's. So I intent to move any Q&A, help requests, as well as free and open discussions between users here.
Since the A750 and A789 are so similar, and I put the same stuff in them, I extent both into this one Q&A thread, and in fact, much of it knowledge applies to other Lenovo's like the P700, P700i, S880, A660 which are again very similar and I even use them as basis of my ROM.
Also, I am not intending to be topic police. Like in my other threads, I do not mind if you guys share knowledge about APKHOT or Smileyvvv or Etotalk ROM. As long as it is helpful. Also, I may not always reply myself, so feel free to help each other.
Link to the original threads:
[ROM][2012.xx.xx] Lenovo A750 custom ROM (GB&ICS). <last page>
[ROM][2012.xx.xx] Lenovo A789,P700i,A660 factory&custom ROM (ICS). <last page>
Other related threads (not all mine):
CWM flashing tutorial (update using recovery)
MT6575 flashing tutorial (update using flash utility
Lenovo Original recovery tutorial
[SCRIPTS] Unpack / repack MT65xx boot.img, recovery.img or logo.bin
[REF] Unpacking and repacking stock rom .img files
[UTIL][APP]Lenovo Security / LeSec app (anti-virus/spam/theft/firewall)
[TOOL][TUT]Backup and Restore Mediatek based phone's IMEI
How to DIY : Self root/gapps/playstore/locationfix/clean my ROM
This is a guide on how to root & cleanup your China ROM yourself. It will probably work on all ICS China phones. But it requires & starts with the availability of a recovery image for your phone
There are in fact a few steps:
- Get a proper recovery image for your phone.
- Root it by installing Chainfire's root package
- Install Google GMS ('GAPPS') to get Play Store and Localisation to work
And optionally
- Install Mobile UncleToolset
- Install an extra small fix with location services
- Install an extra small fix with latest APN list
- Install an extra fix to remove well known Chinese system apps
Recovery image
The Recovery Image allows you to boot into an alternative small Linux that you can then use to update the main Android. Updates usually come in "update.zip" scripted files. And the recovery has some other utilities like backup or wipe the entire phone. Getting a working recovery for your phone is step number one, because if you have a recovery, you can do everything else.
To check if you already have a recovery: Well, try to boot into it. The boot sequence may vary with the phone, but on MediaTek phones it is usually to replace the battery and then press&hold both volume buttons while powering up. I have seen it where you need to actually press the power button a split second before pressing both volume buttons. Try a few times, replacing the battery each time.
If you get to a screen that reads CWMR or CWMR Touch (short for ClockWorkModRecovery), you are all set and can continue with rooting. CWMR it is the most common open recovery image. If your recovery is closed, then you need to search the web for a working recovery for your specific model. Each brand and model needs its own recovery, because screen drivers, buttons and partition tables may differ.
Search the web is the best advise. Search wide and search deep. If you cannot find any recovery, then see if you can find a full ROM for your phone. If you have a working ROM image, then there are people on XDA that can make a recovery for you, but typically you need to show/prove that you have really tried to find one yourself.
Flashing a recovery
If you do find a recovery, that you suspect is the correct one for your ROM, then comes the scary part: Flashing the recovery to the phone.
This paragraph is specific to Mediatek based phones. On different hardware you also need a recovery, and once you have a recovery, you can use the other parts of this post, but how to flash other hardware, I do not know, sorry
Flashing using the flash tool is scary to new users. Because new users suspect that if they mess it up, the phone dies. And this is correct! But if you only flash the recovery.img part, you should be fairly safe. Read this manual on flashing. Getting the USB driver installed is sometimes a bit tricky, you may also want to read post #21 and post #25 for help.
I have seen several people asking 'where to find the scatter file'. Well, it comes with the ROM you want to flash. If your ROM file does not come with a scatter file, then is not a ROM file that can be flashed with the flash utility, but with an open recovery.
Rooting
Once you have a working recovery, the rest is simple. For rooting, simply install (from inside the recovery) chainfire's "CMW installable ZIP"
Link to his post: (ignore his big red 'requires root' warning). The file you need is labeled "CWM installable ZIP" at the bottom. Direct link to the file you need to install via recovery update.zip
This usually works by putting the zip file on the SD card (its name can be anything, though for some limited recoveries it sometimes must be named 'update.zip'), booting into recovery, and selecting the zip file to update.
Google GMS (Market/Play Store, Location, etc)
Simply install the latest Google Mobile Services (better known as GAPPS) from CyanogenMod V9. This is their explaining wiki from CyanogenMod
The file you need is called gapps-ics-20120429-signed.zip for ICS and gapps-jb-20121212-signed.zip for JB and can be found here. You probably also want to wipe your cache partition after doing this.
Mobile Uncle toolset
Just install this program apk (so not through the recovery, just install it normally). Or search the web for the latest one.
Fix location services
If location services does not work, do apply Google GMS (GAPPS) above. If it still does not work, it may be because the phone is programmed to use Chinese location services. This patch will tell it to use GMS. The patch will apply, and probably even work, on all ICS phones. But was originally made&tested on a Lenovo A750 ICS. Its called V1.3 because many people have downloaded the A750 v1.3 patch and used it on many MT6575 phones. It is still the same patch, except the update.zip is tweaked to work on any ICS phone, not only MT6575 ones.
Sometimes you also need to go into MobileUncle tool, the MTK Engineer mode, and in location settings. Depending on your exact model, somewhere in there is a NetLoc or NetLocation and a GeoCoding setting, with options of MEDIATEK and GOOGLE. Ensure they are set to GOOGLE.
After messing with location settings, it is best to also wipe cache.
Fix APN list (or My 3G does not connect!)
You can always add your own APN (Access Point Names) from the settings menu. Just add your own, and select that over the pre-build one. But this package will update with the latest list as maintained by CyanogenMod 9. The update.zip was made in such a way it should work on all ICS phones, Mediatek or other.
Clean well known Chinese system apps
<patch still coming>
==========================================
List of known recovery images for Mediatek Flash tool:
Lenovo A750 : 592zn : See also this post #607, nandroid backup does not work.
Lenovo A789 : 592zn or APKHOT
Lenovo P700i : My own, based on APKHOT with CWM.
Lenovo P700 : My own, based on CWMT / 592zn. nandroid backup will not work.
Lenovo A660 : My own, based on APKHOT with CWM
Lenovo S560 : My own, based on APKHOT with CWM (as yet untested)
Additional Recovery Images in this post.
If you feel you searched all over the web, and could not find a recovery for your model, and you next feel you should ask me or one of the other people on XDA to make you one (which I am not encouraging), than please be aware we need at least a 'standard ROM' for your phone to start from. Without it, I can do nothing. So go back out there, and find a standard ROM, does not matter what language, as long as it is for your specific phone model and known to work.
Also, as an extra warning : If you are flashing, and you experiment with 'suspicious' ROM sources, *never ever* flash the preloader, mbr, ebr uboot. Only flash those from a trusted source and if they belong to your exact brand and model phone.
One more reserved
lolo250612 said:
Hello from France,
Just a little message to thank you very much for your very useful "Lenovo A789 factory&custom ROM (ICS)" thread. I have just bought a A789 from etotalk, and your posts really help to master the beast.
I can't participate to the thread because I am a new member and consequently can't post message to this development thread. And this very sad, because I have discovered a shortcoming of this phone. Apparently, the ICS entire phone encryption does not work and, according to some information I have gathered around the web, it may be due to the fact that the internal sd partition is not ext4 which seems to be required.
It may be due to the fact that the kernel does not support ext4. If this was the case, I would be very pleased to activate the option, recompile it and share the result with other people at xda. I have done it for two types of Samsung Galaxy phones.
In this case, the two problems I would be faced with are:
1) Getting the kernel sources. For Samsung it is quite easy. For Lenovo, I am not able to find them (I can't read Chinese).
2) The process to package the new compiled kernel to a zip, compatible with cwm.
Anyway, thanks for your help and to share your knowledge.
Sheers,
Laurent
Click to expand...
Click to collapse
cybermaus said:
well, not sure about encryption, but I can *assure* you that the phone supports ext4, because in fact the root; system; cache; secro and data partitions are all in ext4 . I know that quite certain, because to unpack/repack, I need to recreate an ext4 loop device.
Internal SD is indeed FAT partition. But it is normal for SD to be FAT
Click to expand...
Click to collapse
It is possible the encryption fails on the FAT of the SD card. It is an internal device, if that encryption utility tries to parse all the internal partitions, it may fail on FAT, but I am guessing here. However, then it would fail on pretty much all recent china phones, they all seem to have this internal SD card. You could try to simply format the internal SD as ext4.
I do not think it would fail on the recovery or boot sections. Those are all nicely wrapped up in the first partition of the emmc chip (emmc0p0 or something) in a proprietary filesystem, as I suspect true for all Androids. So your tool would know to exclude that the first one. However, if you want, you can get the original recovery you asked about from the original A789 ROM in my Dev-Host.
Edit: Encryption issue solved, see post#9 below
I already managed to build a multilang framework-res.apk for the A789 ROM. But now there are all those apps that need to be made multilang also - settings.apk and more... a lot of work.
Is it possible to take a P700 ROM with A750 kernel and flash it to the A750? Or a P700i ROM and A789 kernel for the A789? They seem to be almost identical.
Any plans to integrate the long press home button function in A750_ROW_S114_cybermaus_ICS_V3.1? Would like to test this rom but this missing feature is essentail for me...and onother question: V3.1 is also for A789, right? Same problem with long press home feature?
@oz42
Well, I am a little disappointed about that question. Putting the P700_ROW on the A750 is *exactly* what my V3 series is. Works wonderful. It's the reason I have been updating this thread for the last two weeks. Problem is that the only extra language is Vietnamese. You may want to re-read posts #2 and #585 in the A750 thread.
I suspect the same is true for P700i and A789, but I did not find a P700i_ROW rom yet. I did find a S880_ROW, and when I have time (later this weekend) I will check if that has proper multilanguage (edit: No. It adds ru, vi, id to en and zh. Not quite what I had hoped for)
@metzner
Yes. When I know how. But I do not have a clue at this moment. I am very pleased about the V3.1, but the missing long press is annoying me at times.
No, V3.1 is not for A789 (yet). They have different partitions, different schreen driver. YOU CANNOT flash a A750 on A789 (or any MT6575 on MT7577) without 'porting' the ROM. I do have a Frankenstein ROM, using p700_ROW with kernel/partition/modules/baseband from A789. But it was not tried out yet.
A789: Encryption problem
I have installed aLogcat to determine what could block the encryption service on the different ROMS I have tested on my A789. The interesting part revealed to be:
E/Cryptfs ( 87): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
Googling for this problem, it appears that there is a strong probability that the culprit is CWMR that I have installed almost right after getting my phone. See: http://forum.xda-developers.com/showthread.php?t=1792101 or http://rootzwiki.com/topic/25652-fixing-galaxy-tab-2-encryption/.
So if somebody has a package that can be safely used with mt6575-flashing tools, to recover the stock recovery or, much better, to install a "clean" version of CWMR, I would be glad to test it and see if it is actually the origin of the encryption problem.
Edit:
@Cybermaus: I have just noticed that you have already addressed part of this message. I have already tried to format the internal sd as ext4 with Minitool partition Wizard on Windows. This fails also. Moreover, the system reports a failure on this partition and ask to reformat it as vfat. I will try by putting back the original recovery from your 4shared. Thanks a lot.
@lolo250612
If I read that post you found, the problem is not so much CWMR or CWMRT itself, but the fact it wipes and formats /data completely, without leaving 16KB of unused space at the end of the partition.
That means replacing it with factory recovery will not help, unless if you then also wipe using that factory recovery, and that factory recovery does leave 16KB. You could also try wiping it from the settings menu.
After you have tried the factory , let me know. I think I can make an empty /data for you that is 16KB shorter than the partition, but you would have to apply it using the flash-utility method.
Edit: checking, I found that the userdata.img that is inside the original S228 factory flash ROM is already 1024K short of 768M. So 767M. No need to build one with only 16K short, just use the one you already have.
Hi cybermaus
Thanks for your contribution. Please help me if you've free time.
Does this custom ROM support traditional Chinese character?? I'm sure Chinese support would include simplified Chinese.....
@loimlo
The A750 V1 and A789 V2has two forms of Chinese, which I cannot read, but I suspect are traditional and simplified. The A750 V3 has one form of Chinese, which I still cannot read, so I am not sure which of the two, but here is a screenshot of it, let me know which it is.
Amadis223 said:
Hi, I wrote with yuweng on this subject. And it is very strange. He says, that mt6575 has only ext4 filesystem, but I,am sure,that I have mt6575 and yaffs filesystem. What do you think ?
Click to expand...
Click to collapse
Well, all the MT6575 and MT6577 based ROM's that I have dissected have ext4. This is probably because mediatek provides ext4 in their development kit. So yeah, I think all mt6575 are on ext4, and not yaffs. I think maybe the mt6573 has yaffs.
cybermaus said:
@lolo250612
If I read that post you found, the problem is not so much CWMR or CWMRT itself, but the fact it wipes and formats /data completely, without leaving 16KB of unused space at the end of the partition.
Click to expand...
Click to collapse
I agree with you.
Edit: checking, I found that the userdata.img that is inside the original S228 factory flash ROM is already 1024K short of 768M. So 767M. No need to build one with only 16K short, just use the one you already have.
Click to expand...
Click to collapse
I have flashed userdata.img. That WORKS :victory:. The phone reboots and then encryption starts. Done in less than 5 minutes. Great. Now, just have to tried one of the utility around that allows to have an encryption password different from the lock one. Many thanks for your help :good:.
hi there,
I just got a Lenovo A789 and i just installed A789_S228_cybermaus_V2.1 and it works perfecly...
i'm new to android and i can't get cellular data to work ( i have reason to believe that it worked in original ETOTALK rom, but im not sure ).
1) i do have a data plan
2) cellular data / mobile data is turned on
3) 3G card with cellular data plan is in slot 1
wrong basebands or apn settings (Portugal, Vodafone) ? ( i can see them in mobileuncletools but i cant change them )
help?
note: i cant follow most of android tips that i googled because some of the menus to edit APN settings do not exist on this rom :\
@spinal2k
Well, the simply solution would be to try and apply the A750 V1.4 as listed in post#2. It only applies location fix and new APN list, so its safe on the A789, even if it was originally for A750.
Second option would be to Google for the keyword APN together with your provider and country names.
Last option is to tell us the mcc/mnc that mobile uncle found, as well as your current APN settings, and maybe we can figure it out.
Edit: you can change APN in Settings->Wireless->More->MobileNetworks->AccessPointNames
cybermaus said:
Last option is to tell us the mcc/mnc that mobile uncle found, as well as your current APN settings, and maybe we can figure it out.
Edit: you can change APN in Settings->Wireless->More->MobileNetworks->AccessPointNames
Click to expand...
Click to collapse
ok, thanks for the tip... how can i see mmc/mnc on mobileuncle tools?
According to that wikipedia page, my MMC/MNC is 268/01 and that it uses GSM 900 / GSM 1800 / UMTS 2100.... On mobile uncle engineer mode i can see that on the 1st sim card UMTS 2100 doesn't exist ( only UMTS 2000 )... :\
acoording to the "you can change APN in..." i can't changed them, just see them... they look fine to me, they're not wrong...
:\
@spinal2k
Don't tell me the ones from that Wiki page, but the ones you find in the APN settings. And then also the "market name" of the service you have. You cannot change, but you can add a new APN, and then select that to use.
But simply applying the V1.3 may be easier, it has the APN list maintained by Cyanogenmod, and will probably solve it anyway.
cybermaus said:
@spinal2k
Don't tell me the ones from that Wiki page, but the ones you find in the APN settings. And then also the "market name" of the service you have. You cannot change, but you can add a new APN, and then select that to use.
But simply applying the V1.3 may be easier, it has the APN list maintained by Cyanogenmod, and will probably solve it anyway.
Click to expand...
Click to collapse
oh, i couldn't see that i could add new.... Now i added an optional apn ( even though the one listed was on official carriers page ) ... now its working...
Thank you for the tips... keep them updates coming
note: i did update with A750 v1.3 and i saw no changed in apn list...
A750 V3.1 battery life
I have been using the cybermaus V1.3 ICS for ages, and it works really well. Recently tried the V3.1 ICS.
Also seems to work really well as well, and a definite plus is the 3G signal strength - I see a definite improvement.
There is a dealbreaker problem for me, though - the battery life is noticeably worse than the excellent life on the V1.3 rom. I'm a noob - tried clearing user cache/dalvik, but not reset (I want to keep my apps/data).
Any suggestions before I go back to V1.3 - thanks.
zapzog said:
Any suggestions before I go back to V1.3 - thanks.
Click to expand...
Click to collapse
Well, a request more than a suggestion: your battery is now a few months old, so slightly less good then when new, but you got used to it. But now, due to the flashing of a new ROM, you are playing on it more, and it is in your attention very much.
I cannot properly test myself, I have to tether it daily for data access. So please try to get a proper test of it:
Stay with V3.1 a few bit longer, at least 2 battery cycles extra. (you can barely have had one) so you get a better baseline. Charge the same method as before (I find that charger works better than PC-USB) After two more cycles, when you have a proper idea on the life, go back, and get a renewed baseline on V1.3 also. And then report your results
M8s+ Amlogic S812 Devices
---------------------------------------------------------------------------------------------------------------------------------------------------------
M8s+ With s812 amlogic with the XT-S812-V10 Board / Samsung chipset.
ABOUT DEVICE:
Brand: WIIKEE
CPU:Amlogic S812 Quad Core up to 2.0GHz(Cortex-A9)
GPU: Octa Core ARM Mali-450 GPU up to 600MHz
Operation System: Andriod kitkat 4.4 Upgrade to 5.1
RAM: DDR3 2GB
EMMC: 16GB
Shell Material: Plastic
Card Extended: Support SD/TF card up to 32GB
Antenna: Built-in antenna for dual WIFI
Ethernet: 1000M LAN
WIFI:Support Dual wifi 2.4G/5G, IEEE 802.11a/b/g/n
Bluetooth:Bluetooth 4.0
Graphics Type: Integrated Graphics Mali400, Supports 1080P video (1920*1080)
Flash Player:Support Adobe Flash 1.1
Gaming: Built-in 3D Accelerator. Support 3D gaming
Video Decoding: Mpeg1/2/4.H.264,VC-1,Divx,Xvid,RM8/9/10,VP6
Power management: Adapter 5V 2A
And like no other development section. Please make backups before taking this journey with me and im not liable for your messed up bricked device's so CONTINUE AT YOUR OWN RISK!!!
A ton of this info is coming from freaktab.com and some other russian/german sites that ive found. Including the chinagadgets.com updates page for the m8 boxes.
---------------------------------------------------------------------------------------------------------------------------------------------------------
:::::::::::The links::::::::::::
Root:
Rooting these boxes seems to be incredibly simple. They are either prerooted or can be done easily.
Kingoroot app , and kingo superuser app got me enough access to Install img twrp via Rashr app all avalible via the playstore. As well as you can use the updater app to install roms in zip format using the stock recovery without twrp but backups are important! Theres a few recoveries out there for our boxes. Some work for the clones, some dont.
You need to verify if you have the s812 chipset or not.
**************************************************************************************************************************************************
:HOW TO ENTER RECOVERY MODE:
To enter the recovery stock or not, there are multiple methods.
Using a toothpick and pushing the reset button inside the AV port ( Harder/nonrooted )
1.) At the bottom of the AV jack hole is the reset button.
Using a tooth pick hold this button in. You know you have pressed it if you feel the click.
2.) Now plug in the power cord.
3.) While holding the reset button down, wait until you see the logo and you can then release the reset button.
done: The recovery menu should now be shown and the device should update.
ALT For rooted devices:
1.) Install romtoolbox lite and Give romtoolbox superuser permissions
2.) Use the rebooter function inside the app to enter recovery mode. (easier)
To install the custom recovery I used [Root] Rashr - Flashingtool app to install the custom TWRP recovery, this also can be used to install the image files. The images are only the recovery, or boot images for the device. Im assuming here that these images should match the firmware version you are on. IE: 4.4 needs the 4.4 boot/recovery not the 5.1 . The Zips contain the correct boot images for the roms and will flash everything in one shot. The images are a seperate source for modding as well as using the usb flash tool or the apps i suggested. The files came prezipped together to be used with the pre installed updater program on most boxes, Its alot lighter to only update what you need.
---------------------------------------------------------------------------------------------------------------------------------------------------------
Recovery:
Twrp:
Source:
http://freaktab.com/forum/tv-player...-unofficial-twrp-3-0-2-videostrong-acemax-kii
DirectDL:
https://www.androidfilehost.com/?fid=24588212152304611
---------------------------------------------------------------------------------------------------------------------------------------------------------
*****Stock Based Roms***
Roms Zips:
4.0 Roms:
Coming soon.
5.0 Roms:
1.) https://www.androidfilehost.com/?fid=24588212152304603
2.) https://www.androidfilehost.com/?fid=24588212152304604
Tested :
*Wifi
*Playstore
*Root - SU/SuperUser/KingoRoot/KingoSuperUser
*TWRP By Abdul
*Kodi
*Showbox
*BusyBox
Broken Items on 5.1:
* Ethernet Wont connect without manual entry of Ip
* Remote needs re-installed via remote.zip matching remote you have
* Front LED lights get reversed / red is on / blue is off (wont wake up from standby needs unplugged)
----------------------------------------------Custom Roms By Team DevDigitel Universal!!!------------------------------------------------------------------
No Boot.image included, must be on 5.1.1 for this to work, if no boot, restore boot.img only from twrp backup.
Rom:
TeamDevDigitel 5.1.1 -
1.) https://www.androidfilehost.com/?fid=24588212152304711
*StatusBar Fixed must be turned on under display. Resolution may also need adjusted.
*Speed Increases to wifi
*May need your own Build.prop to function perfectly, backup using zipme and flash after flashing this.
*Boot.img not included. Will use your boot.img, bust be on 5.1.1 for this to work!!
Tested :
*Wifi
*Playstore
*Root - SU/SuperUser/KingoRoot/KingoSuperUser
*TWRP By Abdul
*Kodi
*Showbox
*BusyBox
Broken Items on :
* Ethernet Wont connect without manual entry of Ip
* Remote needs re-installed via remote.zip matching remote you have
* Front LED lights get reversed / red is on / blue is off (wont wake up from standby needs unplugged)
----------------------------------------------------------------------------------------------------------------------------------------------------------
Custom Boot.img :
Flash Via Twrp:
For s812 (tested on board xt-s812-v10)
https://www.androidfilehost.com/?fid=24588212152304713
----------------------------------------------------------------------------------------------------------------------------------------------------------
Custom Build Props:
Team DevDigitel Custom Build.prop
Flash Via Twrp:
https://www.androidfilehost.com/?fid=24588212152304712
Others:
http://freaktab.com/forum/development-area/build-prop-tweaking
------------------------------------------------------------------Custom Roms From Others------------------------------------------------------------------
VS/Acemx KII : http://freaktab.com/forum/tv-player...tools-al/571716-rom-vs-acemax-kii-xsatius-rom (based on 4.4)
KII Valkostur : http://freaktab.com/forum/tv-player...rmware-roms-tools-al/553983-rom-kii-valkostur (based on 4.4)
-----------------------------------------------------------OPEN ELEC PROJECT--------------------------------------------------------------
Links:
HOW TO INSTALL VIDEO: https://www.youtube.com/watch?v=QEuBQEGTpP4 (justmeroms)
OpenELEC 6.0 ROMS Below:
OpenELEC-Amlogic-MXiiiG - http://*******/12297117/mxiiig-update
OpenELEC-Amlogic Minix x8HP6.0 - http://*******/1Vfxnq
OpenELEC-Amlogic-M8-6.0 - http://*******/1VLUcI
OpenELEC-Amlogic-M8S-6.0 - http://*******/1VLV3J
OpenELEC-Amlogic-M8S+-6.0 - http://*******/1VLUvn
OpenELEC-Amlogic-S82-6.0 - http://*******/1VLV89
OpenELEC-Amlogic-MXQ -6.0 - http://*******/1VLqJz
Updated files for some that may get black blank screen posted below.
Another Solution for people that get a blank black screen is to use these files and extract all 3 files onto the root directory
of the SD Card.
You sould see ( factory_update_param.aml, recovery.img and OpenELEC.zip) files then do the toothpick method by pressing the micro switch inside and releasing after 5 seconds.
OpenELEC-Amlogic-MXiiiG - http://*******/12297117/mxiiig
OpenELEC-AMlogic Minix x8HP6.0 - http://*******/1VfxUv
OpenELEC_6.m M8/M8N - http://*******/1VdS7g
OpenELEC_6.0 M8s - http://*******/1VdSXO
OpenELEC_6.0 M8s+ - http://*******/1VdSfS
OpenELEC_6.0 s82 - http://*******/1VdSmi
OpenELEC_6.0 MXQ - http://*******/1VdSuR
Added 27.03.2016
OpenELEC 6.0.1 MX2 - http://*******/12297117/openelec601-mx...
-----------------------------------------------------------------EtertainmentBox-----------------------------------------------------------------
Etertainment Box Brand M8s Stock Dl - https://www.entertainmentbox.com/latest-m8s-firmware-download/
DL Mirorr: N/A
-------------------------------------------------------------------------------------------------------------------------------------------------------
Apps:
KingoRoot : https://root-apk.kingoapp.com/kingoroot-download.htm
KingoSuperuser : https://superuser.kingoapp.com/
{Root} Rashr - Flashtool :http://forum.xda-developers.com/showthread.php?t=2334554
Romtoolbox: https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox&hl=en
Busybox: https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer&hl=en
SuperSu: https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
Kodi: https://play.google.com/store/apps/details?id=org.xbmc.kodi
Zipme: https://play.google.com/store/apps/details?id=zip.me&hl=en
Tons of others : https://www.entertainmentbox.com/official-android-tv-box-apps/
---------------------------------------------------------------------------------------------------------------------------------------------------------
Utilities:
Usb img burning tool: https://mega.nz/#!cJ1RnI4T!S2dq8VnObB4TLSHjCvJBx7zD5A__LPrLKvm999qsxwY
How To Usb Burn tool:
[Video]
http://chinagadgetsreviews.blogspot.ro/2014/08/how-to-easily-flash-firmware-on-probox2.html
Unbrick M series boxes:
[Video] https://youtu.be/1o7KQaLAEeU
Identify your box:
http://freaktab.com/forum/tv-player...ilogic-device-is-bricked-read-this-post-first
----------------------------------------------------------------------------------------------------------------------------------------------------
Remote Configure zips:
These are flashed to get the stock remotes found for these boxes working aftee changing roms.
The remote config files are located at
/System/ETC/remote.conf
These will determine what keys on the remotes do.
Link to Download Zips:
http://freaktab.com/forum/tv-player...tools-af/18312-s802-multi-remote-patcher-zips
---------------------------------------------------------------------------------------------------------------------------------------------------------
*
*
*
*::::::::::::::::::::Resources::::::::::::::::::::
Freaktab Amlogic Based Devices. S8xx Series
http://freaktab.com/forum/tv-player-support/amlogic-based-tv-players
JustmeRoms
https://justmeroms.com/
Chinagadgets.com Firmwares Page
http://chinagadgetsreviews.com/firmwares
S8xx Chipse Devices UNIVERSAL ROM:
Roms Zip:
4.0:
Coming Soon
----------------------------------------------Custom Roms By Team DevDigitel Universal!!!------------------------------------------------------------------
No Boot.image included, must be on 5.1.1 for this to work, if no boot, restore boot.img only from twrp backup.
Rom:
TeamDevDigitel 5.1.1 -
1.) https://www.androidfilehost.com/?fid=24588212152304711
*StatusBar Fixed must be turned on under display. Resolution may also need adjusted.
*Speed Increases to wifi
*May need your own Build.prop to function perfectly, backup using zipme and flash after flashing this.
*Boot.img not included. Will use your boot.img, bust be on 5.1.1 for this to work!!
Tested :
*Wifi
*Playstore
*Root - SU/SuperUser/KingoRoot/KingoSuperUser
*TWRP By Abdul
*Kodi
*Showbox
*BusyBox
Broken Items on :
* Ethernet Wont connect without manual entry of Ip
* Remote needs re-installed via remote.zip matching remote you have
* Front LED lights get reversed / red is on / blue is off (wont wake up from standby needs unplugged)
** If playstore wont Login through app. Go to settings/more settings/accounts and sign in through there.
If playstore wont download apps or fully load up like its not getting network. Go to settings/more settings/Apps/ and force.stop.playstore and clear its data.
Enjoy
----------------------------------------------------------------------------------------------------------------------------------------------------------
Custom Boot.img :
Flash Via Twrp:
For s812 (tested on board xt-s812-v10)
https://www.androidfilehost.com/?fid=24588212152304713
----------------------------------------------------------------------------------------------------------------------------------------------------------
Custom Build Props:
Team DevDigitel Custom Build.prop
Flash Via Twrp:
https://www.androidfilehost.com/?fid=24588212152304712
Reaerved 2
Reserved 3
Reserved 4
Reserved 5
Bare with me
Please hit Thanks Button On Main Op;
This helps me know if this is helping people and being used!
also, this work is free of charge and its motivational!
Now that the base info is up. Is anyone on this side of xda interested in getting xdas android tv boxes more orginized and displayed? If not ill just limit my work to what i developed for and move on..
Using brackets on your posts helps users navigate the forum so much easier.
[Wip] work in progress
[Rom] Flashable rom
[Q&A) questions section to keep forums clean
[Dev] developers needed / open project
[Guide] walk throughs
Identifying the model is good, but identification of your chipset is the important part. These boxes are heavily clones and sold as whatever the distributor said it was. And a lot of times it wasnt what you thought it was.
Rkxxxxx S8xxxxx Txxxxxx Etc is how you will be locating the correct firmwares for your devices. Im hoping that in the future we can go cross platform/chipset by including the correct boot.img and xml/build.prop files for the right chips and the software will be universal (ish)
See post #2 for Universal rom Flash.
Highly suggest only using TWRP and backing up to your external SD.
the build.prop and the boot.img are both twrp flashable files.
these also can be used to put your stock boot.img or build.prop after flashing a universal softwear rom to gain all
your device specifics back. the custom one is based on m8s/+ models and was off a 16gb device so both 8/16 can flash.
you can alos use the app zipme to make your own flashable zips. great for backing up certain files.
remote.config is another one thats important to backup from your original build the device shipped with!
how to adjust twrp screeen size
screen size is to big on my tv i cant navigate some keys on my usb keyboard,, imean i cant navigate twrp properly using my navigation keys on my wireless key board...pls help thanks
Hey man first of all big thanks for the THREAD, is very hard to find some information about all of this you have no idea how this thread can help us with these android TV devices (F**** smart TV's)
So i have a S82 Plus, with the android 5.1.1, kernel 3.10.33, fimrware 101L1 and running silk and smooth the only problem for me is the remote controler that i bought... doesn't work well some keys and functions just dont work!! and i don't know why..
And i was thinking maybe i just the ROM because if i put to work with my computer works fine, if i put it with my S4 works well too...
So i was thinking is there any 6.0 rom for this device?? Would you recommend another one to try??
My Remote is the measy rc12-b5
Big thanks again for the help!!
nice i finally found this thread all i really want is to make it like a basic tablet with out the crap. Where can i learn how to dump a new box and change it to work like a tablet. btw the game myvegas doesnt work
Hi Team DevDigitel thanks for your work
I think this will be a great place for M8s owners .
My Box is a M8S now running this 5.1 rom (M8S(n200c)_to_M8S+ 5.1 20151022-aml_upgrade_package) it works fine only no WIFI and no remote seams that only 2 of the 4 cpu cores are working non rooted
download (M8S(n200c)_to_M8S+ 5.1 20151022-aml_upgrade_package) here https://mega.nz/#!ZUxQSJQK!nt8g1nGV6jdTe3mZFa3_aXPY4UcXTaLQuUIGK-c-jbg
Threre is also a android 4.4 rom what is working okay pre rooted (M8S_aml_upgrade_package_16.0_20160229)
download https://drive.google.com/file/d/0B4NYLg8trzWdYl82UlpteHppOU0/view
I cant get my box into recovery whit the sd card toothpick method
I only can flash img whit usb burningtool
Goal to get a fully working 5.1 rom whit working wifi and remote in img because my M8S cant get into recovery whit SD card toothpick method
it also be nice to have root so i can boot in recovery
I hope that this becomes a place to collect and develop M8, M8S M8S+ roms
I recently bought m8s+ and wondering if we can get latest 6.0 firmware on this tv box btw it came with 5.1 Lollipop.
I second that also make sure the MyVegas app works from google play. It didnt with the last firmware
Hi i want know how i can unpack and repack stock rom? I want change the stock apk with other ones! Otherwise there is another method?
All the tools create an incompatible system.transfer.list (not for android lollipop 5.1.1!) because the version that will be created is 1 but the original version of 5.1.1 is 2!
And so when i flash a new rom i get this error: unexpected transfer list version [1 ]
I tried to change version with notepad++ and the error no longer appears but the firmware cannot be flashed because the installation starts but doesn't complete!
Please help me
Stock system.transfer.list:
Code:
2
146445
0
0
erase 2,0,262144
new 32,0,32767,32768,32770,32833,32835,33347,65535,65536,65538,98304,98306,98369,98371,98883,131071,131072,131074,163840,163842,163905,163907,164419,196607,196608,196610,229376,229378,229441,229443,229955,247047
Repack system.transfer.list
Code:
1
150644
erase 2,0,262144
new 84,0,64,65,179,579,580,4675,20050,20053,22476,22479,22487,22490,22491,22500,22506,22517,22671,22672,23814,23826,24082,24094,25259,25260,32767,32768,32770,32833,32834,33347,41193,41196,45537,45538,49457,49464,49622,49623,54103,54105,54112,54118,54139,54140,54141,54160,55263,55264,65535,65536,65537,98304,98306,98369,98370,98883,122919,122920,123534,123539,131071,131072,131073,163840,163842,163905,163906,164419,166592,166593,196607,196608,196609,229376,229378,229441,229442,229955,254995,254996,255021,255074,255906
Big thanks for the ROMS!
I just want to say thank you for your big effort on making these ROMS! :good:
Like my username indicates, I finally got my troublesome M8S box working flawlessly with Android Lollipop, in which your Universal ROM was the key. I documented my steps in another related thread.
m8s+ firmware IMG format for USB method
Hi,
Where I download rom (android 5.1.1 lollipop on 2016.1219) for IMG format for USB upgrade method?
I have problem at upgrade SD card method.
gorus1 said:
Hi,
Where I download rom (android 5.1.1 lollipop on 2016.1219) for IMG format for USB upgrade method?
I have problem at upgrade SD card method.
Click to expand...
Click to collapse
Here you are https://androidtvbox.eu/new-firmware-m8s-tv-box-amlogic-s812-20161219-release/
Thanks for link, but I need have ROM in IMG format becose i have problem with SD card port.
I downloaded ROM from link and unzipped this, but there is no IMG format.
Sorry, maybe something I do not know, but I need have IMG compilation.
Please for help!
Hello,
I've purchased this one: http://www.dx.com/p/x96-tv-box-andr...-2gb-ram-16gb-rom-us-plug-449347#.WPuxONryuUk
Just wondering what ROMs and recoveries work. I've searched a bunch and found some dead links and conflicting information so I'm hesitant to flash it especially where I do not have a stock image to go back to if it renders it bricked.
If anyone can help out, it would be much appreciated.
Thank you,
Scott
Note: Keeping a repository here as I find more information about this box: https://drive.google.com/open?id=0Bzj6JjnAJZjjczVIbFlHS3VUWlU
Working on it
Custom TWRP and stripped down/modded firmware is on the way.
I hope we can get a pure Android Rom working on it
Again: Working on it
Fully unbranded and hopefully with unlocked custom bootanimation (Original Google would be my prefered option over Mbox).
Give me a bit of time and you will find flashable ZIP soon
All done
Another question about the box: is-it possible to have Android TV instead of a modded android marshmallow? Because the interface would be a lot easier to use.
Android TV is a complete different story and you can't really compare the two like this.
Android TV uses the Leanback launcher if I am not mistaken.
Already tried to include it into a testrom but so far no real luck as it uses a lot more binaries that are not included in the standard system.
Will have to create some symlinks, add binaries and do a lot of testing - not to mention finding all the included apps for android TV and figuring out how to make them work.
If the interface is your only trouble check some nice launchers first, like Apex for example.
Once I have something cooked up that actually works as expected you will find it in this section somewhere
Also interesting to test that , as mine is not even root ^^
Rom
Any news about the firmware for this device?
Nope, still no updates coming from the chinamen, seems they already abandoned firmware updates and moved on to different devices.
See this thread (beta 6 I used for.mine)
https://forum.xda-developers.com/an...gic/rom-x96-2-16gb-root-supersu-twrp-t3596525
I join the thread because because of a storm my X96 looks brick. I've been looking everywhere but I do not find the guide for unbrick. I wanted to save it not to throw it but I do not know where to download the firmware how to do unbrick. I know I'm in the wrong thread but I did not want to open it a lot like this and make it confusing. Thank you all
As long as you get into the TWRP recovery on the SD card all should be fine - assuming the box is a X96.
If that fails only the burn tool or burn card maker can help with a genuine firmware to get going again.
Hi guys sorry to bump an old thread. I'm still trying to find the TWRP zip for these so I can do a complete back up and then paste on other boxes.
Have an X96 Amlogic S905X Quad Core 2G/16G Android 6.0 Wifi HD 4K TV Box.
I flashed the FULLY UNBRANDED Kodi 17, everything looked fine but the box's red light just stays on after the reboot.
Does not go into TWRP at all or nothing on screen.
It now a paperweight?
Downloaded the Stock firmware (Android 6.0.1 X96 Amlogic S905x 20161122) and am trying to start box with a bootable SD-card.
BurnCardMaker asks for an IMG file with all the relevant (aml_autoscript, factory_update_param.aml, firmware.zip, recovery.img, u-boot.bin, etc) files in but i cannot find this IMG file.
Without these BurnCardMaker does not work at all or nothing happens on TV box at least.
Must also say, i use a 64gig SD card but it worked for the initial flash.
Am i wasting my time with this box now?
Thanks for help.
Hi,
I've been trying to find a custom recovery for the new Asus Tinkerboard, which is based on a RK3288 chipset, running Android 6.0.1, so I can install zip files from sdcard etc.
The generic CWM 6.0.5.1 by @Oma7144 *almost* works, but it usually hangs after saying can't open /dev/block/...../misc (no such file or directory).
The one time it got past this it gave me the menu option for reboot/install zip etc, but I couldn't move up and down the menu with my USB-attached keyboard.
Does anyone know if there's a later build, or a tinkerboard-specific one anywhere?
Thanks,
Iain
iainfm said:
Hi,
I've been trying to find a custom recovery for the new Asus Tinkerboard, which is based on a RK3288 chipset, running Android 6.0.1, so I can install zip files from sdcard etc.
The generic CWM 6.0.5.1 by @Oma7144 *almost* works, but it usually hangs after saying can't open /dev/block/...../misc (no such file or directory).
The one time it got past this it gave me the menu option for reboot/install zip etc, but I couldn't move up and down the menu with my USB-attached keyboard.
Does anyone know if there's a later build, or a tinkerboard-specific one anywhere?
Thanks,
Iain
Click to expand...
Click to collapse
Hey lain,
Did you solved your problem till now?
i think the big problem is that the Tinker board is not so popolar at the moment and you see this specialy on xda that there are not much to find about it.
I have the TB too and i am actually very active at the Tinker board community Forum but also there are not much solutions for some things i need or want for example bluetooth functions to use it as a headset.
But try your luck there and ask your question.
Greets
Check out TWRP Builder
iainfm said:
Hi,
I've been trying to find a custom recovery for the new Asus Tinkerboard, which is based on a RK3288 chipset, running Android 6.0.1, so I can install zip files from sdcard etc.
The generic CWM 6.0.5.1 by @Oma7144 *almost* works, but it usually hangs after saying can't open /dev/block/...../misc (no such file or directory).
The one time it got past this it gave me the menu option for reboot/install zip etc, but I couldn't move up and down the menu with my USB-attached keyboard.
Does anyone know if there's a later build, or a tinkerboard-specific one anywhere?
Thanks,
Iain
Click to expand...
Click to collapse
They already compiled a working I'm going of TWRP and it can be downloaded thru the site or app. Heads up thou, I have a TB S with 7.1.2 and it would not work, just bootlooped or wouldn't return to recovery at all. Let me know if that works for you, the img number is 630 I believe, just follow the instructions, I already rooted and installed play on mine before doing this
supasleeze said:
They already compiled a working I'm going of TWRP and it can be downloaded thru the site or app. Heads up thou, I have a TB S with 7.1.2 and it would not work, just bootlooped or wouldn't return to recovery at all. Let me know if that works for you, the img number is 630 I believe, just follow the instructions, I already rooted and installed play on mine before doing this
Click to expand...
Click to collapse
had same issue, not sure if mine is s or not, i think it's just the regular TB.
the port poorly ported or it's just intentional anti-leech. if you look in the fstab files, you'll see it...
honestly, the best way would be to port it by yourself. i'm gonna try doing that sometime this month, no guarantees though