Database Info

[NEW][Huawei IDEOS U8150][RECOVERY] UltraJack-Recovery v6.2.2 (06/03/2011)

Hi guys!!
NEW UltraJack-Recovery 6.2.2!!​Codename:Cappuccino​
NO MORE BLUE SCREEN!!!!​
Changelog:
FIX: Backup/restore of /cust partition (Bug present in all releases of Ultrajack -up 5.2.2 too- and Clockworkmod too!! )
Added:
mount and umount /cust partition
WIPE /cust
Amend support to CUST partition (Edify is supporting CUST alredy)
Amend/Edify are both supported! (the oldest and newest and future roms can be flashed )
New Base (RA_Recovery 2.2.2!)
FULL EXT4 support (read-write and formatting partition!)
Backup/restore menu (and scripts) updated
Backup/restore google apps
New menù colors
ADB Updated
Kernel sources Modded and compiled to solve an issue on toggle USB function
Download it now!! (6.2.2)(IMG only)
guide and zip file with fastboot binary and scripts here:
http://forum.xda-developers.com/showpost.php?p=11771509&postcount=39
If some1 liked my work and want donate me a beer (or a new micro-SD), there is the link link, or just say tnx
Thanks to:
Me, Myself and I!
Udk ( my best compiler-friend )
Maja (beta tester, and many great ideas! )
Amon_RA(this recovery was based on him RA_Recovery 2.2.1 sources, and many thx about compiling tips!)
JackTheVendicator (without his modded tools the boot.img and recovery wouldn't be possible)

Old versions:
Hi guys there was a problem on some devices with amonra 1.6.2 for the pulse mini.
The BSOD!!!! (windows like)
But now this issue has been SOLVED!!!!
NEW VERSION!!​
NO MORE BLUE SCREEN!!!!​
Download it now!! (4.6.2)
Changelog:
Fixed SD-MassStorage function
Fixed all Wipes!
Ext2/3/4 support
if some1 liked my work and want donate me a beer (or a new micro-SD), there is the link link
Thanks to:
Me, Myself and I!
Udk ( my best compiler-friend )
Maja (beta tester, and many great ideas! )
Amon_RA(this recovery was based on Amonra pulse mini v1.6.2, and many thx about compiling tips!)
JackTheVendicator (without his modded tools the boot.img and recovery wouldn't be possible)
UltraJack-Recovery_v2.6.1

you are f***ing great!!!

Now is the time for the dedicated section

NVM fastboot install. Nice.

I hope you don't mind but I linked this to the IDEOS group over at www.simply-android.com
THANKS!

What i should do with this .img file?

This recovery won't allow you to do a boot or system wipe. just data/cache and dalvik. If you do the wipes included you can still boot the phone afterwards...that's not a full wipe.
Just FYI.

nobreak1970 said:
This recovery won't allow you to do a boot or system wipe. just data/cache and dalvik. If you do the wipes included you can still boot the phone afterwards...that's not a full wipe.
Just FYI.
Click to expand...
Click to collapse
So are you saying this is just like Googles own recovery?
It wont actually allow you to wipe the phone like AmonRA does?
Then thats useless wouldn't you agree?

@ Ultrakiller
plz plz plzzz somebody teach me how to Flash a custom recovery like the one above for my Ideos U8150-B......
I've been all around the forums and internet ....but nothings working for me ..... im using Windows7 x86 Ult Ed .....
i've even tried 1.6.2-pulsemini-amonrarecovery Instructions for windows ......but still no luck !!!
i Even tried to Flash Image through Terminal .... but for some reason it said " Flash_image not found" .....even though the filename was accurate !!! ........
Kindly Kindly Kindly guide me through the process ..... im so frustrated now .... and im dying to try new ROMS on my Ideos .....
(Also wat ROM u think is better DjDroid's or Sudomod ??????)
Plz Help ASAP !!!!

How To: Flash UltraJack Recovery to your Phone (Windows/Mac/Linux)
How To: Flash UltraJack Recovery to your Phone (Windows/Mac/Linux)
NOTE: This is a modified version of the AmonRA recovery flashing package.
The only thing I really did was modify the .sh/.bat files and include the UltraJack Recovery.​
@devilzeye793 and whoever else may be wondering: Here you go!
1. Download the attached ZIP and extract
2. Make sure you have the necessary drivers installed for bootloader mode (installing PDAnet seems to do the trick on Windows: http://forum.xda-developers.com/showthread.php?p=9861928#post9861928)
3. Boot your phone into bootloader mode (Google it, I can't list all the ways here).
4. Plug your phone into your computer and let Windows install the drivers automatically (if you're on Windows, unfortunately I'm not really sure how this happens on Mac/Linux). NOTE: On some phones (i.e. the U8150), the phone will stay on the carrier logo screen. THIS IS NORMAL!
5. Run the installer for your OS from the extracted folder (.bat file on Windows, .sh file on Mac/Linux) and let it work its magic
6. After the script has flashed the recovery image (should take ~1-5 seconds), unplug your phone and remove/re-insert the battery to get out of bootloader mode
7. Enjoy your new recovery image!
Hope this helped some people out there!

stevenmirabito said:
How To: Flash UltraJack Recovery to your Phone (Windows/Mac/Linux)
NOTE: This is a modified version of the AmonRA recovery flashing package.
The only thing I really did was modify the .sh/.bat files and include the UltraJack Recovery.​
@devilzeye793 and whoever else may be wondering: Here you go!
1. Download the attached ZIP and extract
2. Make sure you have the necessary drivers installed for bootloader mode (installing PDAnet seems to do the trick on Windows: http://forum.xda-developers.com/showthread.php?p=9861928#post9861928)
3. Boot your phone into bootloader mode (Google it, I can't list all the ways here).
4. Plug your phone into your computer and let Windows install the drivers automatically (if you're on Windows, unfortunately I'm not really sure how this happens on Mac/Linux). NOTE: On some phones (i.e. the U8150), the phone will stay on the carrier logo screen. THIS IS NORMAL!
5. Run the installer for your OS from the extracted folder (.bat file on Windows, .sh file on Mac/Linux) and let it work its magic
6. After the script has flashed the recovery image (should take ~1-5 seconds), unplug your phone and remove/re-insert the battery to get out of bootloader mode
7. Enjoy your new recovery image!
Hope this helped some people out there!
Click to expand...
Click to collapse
well awesome man ....it worked this time .....u ppl are awesome !!!
GOD BLESS !!!
btw what Ideos ROM is Best in your opinion !! ????

Great, I'm glad it worked out for you!
I am currently using the stock ROM, simply because I currently see no reason to install any of the currently available custom ROMs for the Comet. As soon as someone has created a stable port of Cyanogen however, you better believe I'm going to be one of the first people on board!
Sent from my Comet using XDA App

fvckyougooglescammer said:
So are you saying this is just like Googles own recovery?
It wont actually allow you to wipe the phone like AmonRA does?
Then thats useless wouldn't you agree?
Click to expand...
Click to collapse
It has a Wipe option but it only wipes the caches it seems and not the boot and system areas.

stevenmirabito said:
Great, I'm glad it worked out for you!
I am currently using the stock ROM, simply because I currently see no reason to install any of the currently available custom ROMs for the Comet. As soon as someone has created a stable port of Cyanogen however, you better believe I'm going to be one of the first people on board!
Sent from my Comet using XDA App
Click to expand...
Click to collapse
+1
Sent from my Comet using XDA App

Nand + Ext backup doesn't work properly, an error messages with regards to :adb something .

New version done!
First post updated.

Well done!

stevenmirabito said:
How To: Flash UltraJack Recovery to your Phone (Windows/Mac/Linux)
NOTE: This is a modified version of the AmonRA recovery flashing package.
The only thing I really did was modify the .sh/.bat files and include the UltraJack Recovery.​
@devilzeye793 and whoever else may be wondering: Here you go!
1. Download the attached ZIP and extract
2. Make sure you have the necessary drivers installed for bootloader mode (installing PDAnet seems to do the trick on Windows: http://forum.xda-developers.com/showthread.php?p=9861928#post9861928)
3. Boot your phone into bootloader mode (Google it, I can't list all the ways here).
4. Plug your phone into your computer and let Windows install the drivers automatically (if you're on Windows, unfortunately I'm not really sure how this happens on Mac/Linux). NOTE: On some phones (i.e. the U8150), the phone will stay on the carrier logo screen. THIS IS NORMAL!
5. Run the installer for your OS from the extracted folder (.bat file on Windows, .sh file on Mac/Linux) and let it work its magic
6. After the script has flashed the recovery image (should take ~1-5 seconds), unplug your phone and remove/re-insert the battery to get out of bootloader mode
7. Enjoy your new recovery image!
Hope this helped some people out there!
Click to expand...
Click to collapse
Can this be uninstalled? I need to send mine back so I need to get the phone back to it's original state...

I'm not an expert, but you probably need to find an IMG of the original recovery image and flash it to the phone.
Anyone have it?
Sent from my Comet using XDA App

[Q] Painted myself into a corner...

I made a mistake by trying to get through the rooting/rom-ing process in a hurry. The result is that i'm stuck on cm boot logo.
1. I installed cwm 5.5.0.4 custom recovery through this guide.
2. Made a nandroid and copied it to pc, sd card, external sd card.
3. Flashed cm-10.1-noname>gapps>tablet ui>wipe cache>wipe dalvik>reboot. (source, version:cm-10.1-20130827-UNOFFICIAL-tf101.zip )
4. Stuck on boot screen.
I'm guessing I should have used twrp rather than cwm.
The trouble is that cwm 5.5.0.4 seemingly doesnt have external sd card support, and having tried to flash cm, it means that the stock nandroid i made probably got moved elsewhere as no backups are found when i try to recover.
Is there a way out of this mess?

Ah, you are not totally painted into a corner. Just climb up the wall and across the ceiling!
There are 2 ways out: ADB or APX.
To use ADB, whilst booted to CWM, connect your USB cord to your computer. Update using the Naked Drivers 0.72 for the unknown device, or ADB device. It will probably show an MTP device as well, leave that alone.
Once you think you have the driver working, you will need ADB. I have a copy of the files in my dropbox so you don't need the whole android SDK.
https://dl.dropboxusercontent.com/u/34321735/adb.zip
Unzip them to the c:\adb folder.
Command prompt and run the following:
Code:
c:
cd c:\adb
adb devices
You should see a device followed by RECOVERY.
Once this is working, find the file you want to move to the tablet to flash (I would recommend TWRP 2.6.3.9 unless you plan on flashing Android Revolution HD) and move this file to c:\adb. I will call it flash.zip for the purposes of this.
Next, go back to your command prompt and type the following:
Code:
adb push flash.zip /sdcard/
Once this is completed you should see the flash.zip on the tablet in CWM so you can install it.
If you do install TWRP, be sure to do a NORMAL reboot (even if it is to a bootlooped OS) so the installation completes. Once you get to the ROM boot screen (pas the Eee Pad logo screens) you can boot back to recovery.
Method 2 - APX
I have a guide for using APX and EasyFlasher here: http://www.transformerforums.com/fo...nt/31927-frederucos-guide-root-rom-tf101.html
You can either use one of my repacked versions (linked in that thread) to install TWRP (has not been updated for the latest TWRP yet, but it is only a few versions old). If you want the latest, put it on a microSD and flash it after updating to the Easyflasher version.
Or you can download the stock ROM from the Asus Support site, place the .zip file as is in the asusupdate folder within EasyFlasher folder structure and then click the unbrick option.

Thank you Sir for the lightning quick response
Will try the apx method first and will let you know how it goes.
Just a quick question though if i may:
cwm is just a personal preference for me so is there an updated cwm easyflasher and will it do the cm 10.1 install better than 5.5.0.4?
(the last time i was adventurous with a recovery, philz raped my cat and shaved my mom. i know it was just a senseless crime! something about having to manually backup /preload/ or end up with broken nandroid)

jbonetwo said:
Thank you Sir for the lightning quick response
Will try the apx method first and will let you know how it goes.
Just a quick question though if i may:
cwm is just a personal preference for me so is there an updated cwm easyflasher and will it do the cm 10.1 install better than 5.5.0.4?
(the last time i was adventurous with a recovery, philz raped my cat and shaved my mom. i know it was just a senseless crime! something about having to manually backup /preload/ or end up with broken nandroid)
Click to expand...
Click to collapse
If you are going to venture into the JellyBean 4.2/4.3 ROMs, I would HIGHLY recommend using TWRP. It is by far superior to CWM, and no one is supporting CWM for the TF101 as far as I know. 4.2 introduced a new file structure for multi-users and updates do not flash properly if using an older recovery. You end up with your /sdcard/ folder in the /sdcard/0/ (and an additional 0 for each new ROM update flashed).
TWRP is far more intuitive IMO (all wipes are in one simple menu), and @sidneyk has added (in addition to internal and microSD support) dock USB and SD card support. TWRP has a terminal emulator and lots of other nice features over CWM.

Well thats got me puzzled.
Installed TWRP 2.6.3.0 using APX.method
Reflashed cm-10.1-20130721-UNOFFICIAL-tf101.zip >
gapps_4.2.2_CM10.1_TF101_20130324_stock_camera >
cm-10.1-20130721-UNOFFICIAL-tf101-tabletUIpatch >
wipe cache/dalvik >
reboot
And I'm still stuck on cm loading screen. Unless it takes more than 10 minutes for first boot I'm stumped...
P.S. Any way of reusing the CWM made stock nandroid with TWRP?
P.P.S. You're right TWRP is MUCH better. Gonna convert all of my devices for sure.

solved!
flashed cm then rebooted - worked!
flashed cm and gapps then rebooted - still works!
flashed cm>gapps>tablet ui - still working!
all with wiped cache/dalvik
apparently it doesnt like all of them being flashed at the same time for first installs :S

Can I flash twrp from goomanager?

I have a 8013. I need to put in a different recovery and I like twrp. has anyone flashed it from goomanager? I see that there is one on there I just dont want to mess something up.
Already rooted.
I would search for this but I cant find a search button. Really not in the app or on the website.
Sent from my GT-N8013 using xda app-developers app

Let me see...
eggwardo said:
I have a 8013. I need to put in a different recovery and I like twrp. has anyone flashed it from goomanager? I see that there is one on there I just dont want to mess something up.
Already rooted.
I would search for this but I cant find a search button. Really not in the app or on the website.
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
Hmm... When I read here: Goomanager so there is function for flash recovery. But if I don't get wrong, so this recovery files must be on www.goo.im server. Theoretically all ROMs, MODs and RECOVERY files lying on goo.im server
you can download to your device and flash it!
But for me and if I want to flash something, the best way is: Flashify
Here is it TOP 11:
1 - Flash boot and recovery .img without even needing to go to recovery.
2 - Flash zip files. Option to wipe cache, dalvik and data when using TWRP or Philz recovery.
3 - Download and flash CWM, Philz, TWRP, Gapps, Franco Kernel, Stock Nexus Kernel (premium), and Stock Nexus Recovery (premium).
4 - Automatic Loki Patch when needed.
5 - Full nandroid backups/restores when using TWRP or Philz recovery.
6 - Backup/Restore kernel and recovery using Sdcard or cloud (Dropbox, Box (premium) or Google Drive (premium)).
7 - Automatic cloud synchronisation of backups between devices and desktops.
8 - Keep track of recently flashed items.
9 - Flash multiple files and build your flash queue.
11 - Flash from anywhere! Do you want to flash from your favorite File Explorer or Email app? No biggie, that also works together with Flashify.
More at links above!
Have great Flashing :victory: Peter

I have an 8013 as well that I acquired used. it was pre-rooted, but the custom recovery on it didn't work for newer roms. I looked into installing TWRP and found that although the official TWRP instructions said you could install it from GooManager, when I tried to, it didn't find a recovery for the device.
I did successfully get TWRP installed quite easily using their alternate instructions, though. here's a quick breakdown, especially since their instructions are a bit vague.
1. download the .img file for the recovery from here: http ://teamw.in /project/ twrp2/110 (remove the spaces; I can't post outside links yet.)
2. in either terminal emultor or through adb shell, run the command shown below, replacing the bracketed sections with the path and filename of the .img file:
dd if=/<File path>/<filename>.img of=/dev/block/mmcblk0p6
For example, say you save it in your downloads folder on the internal sd card. The path is probably something along the lines of /storage/sdcard0/Download/openrecovery-twrp-2.7.0.0-gt-n8013.img
If you get the path or filename wrong when you runthis command, it will just tell you that it could not find the file you told it to write. if you get the second part wrong, however, you could brick your device, so make sure you double and triple check that part.
Another good check to do before running the command is to ensure that your download is not corrupt by checking the md5 checksum. To do this, make sure you copy that when you download the file and then check using a file browser that supports it. I use Explorer (by Speed Software) to check the md5. To see it, long press the file and click properties. If the one given when you downloaded it and and the one you get from the file do not match, your download likely got corrupted and you should try again until they do match. It's rare, but you don't want to flash a corrupted recovery, so do check it.
The command itself can either be run from an app like terminal emulator or over adb (android debug bridge) from your computer using the command:
adb shell <command>
I followed this basic procedure and now have a fully functioning TWRP recovery on my 8013. Best of luck to you in getting yours working. :good:

[p500][CWM Advanced Edition] PhilZ Touch

Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
To take a screen shot, just long press outside a menu (2 sec and slightly change pressure after the delay)
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
LG Optimus One P500 (p500)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/p500
Click to expand...
Click to collapse
XDA:DevDB Information
[p500][CWM Advanced Edition] PhilZ Touch, a Tool/Utility for the LG Optimus One P500
Contributors
Phil3759
Version Information
Status: Testing
Created 2014-04-21
Last Updated 2014-04-21

Cool.
Upon which CWM version is this based? Note fundamental differences between newer 6.0.* after June 16 -- can flash new Kitkat ROMs and older 5.* which flash older ROMs.
Because of space limitations -- whole business must fit < 5 meg, functionality such as partitioning SDcard was removed from the 6.0.* versions.
What do we have in this version?

Plz update the post with all the features of this recovery... How can we test, if we don't know what to expect???

ujilraj said:
Plz update the post with all the features of this recovery... How can we test, if we don't know what to expect???
Click to expand...
Click to collapse
If you can't read OP and follow links, just do not test
I am fine with this

Unable to flash!
Can't flash the image file by "CWM 6.0.4.6. 16 Jan" recovery by Mukulsoni.Status 7.Please suggest what wrong i did?
1) After d'loading the .image file, i rename it to "recovery" as it in the zipped folder of Mukulsoni recovery.
2) Then i open the zip of Mukulsoni recovery and drag Phil's image file to replace it.
3) Close the zip, put it in the sd card and flash.
4) Status 7 happened.
What should i do? Please help! :crying:

I suggest that the first link needs to highlighted... My mistake, but honestly i didn't notice a link below the title...

sumansur2008 said:
Can't flash the image file by "CWM 6.0.4.6. 16 Jan" recovery by Mukulsoni.Status 7.Please suggest what wrong i did?
1) After d'loading the .image file, i rename it to "recovery" as it in the zipped folder of Mukulsoni recovery.
2) Then i open the zip of Mukulsoni recovery and drag Phil's image file to replace it.
3) Close the zip, put it in the sd card and flash.
4) Status 7 happened.
What should i do? Please help! :crying:
Click to expand...
Click to collapse
This is NOT a flashable zip file!
1. Download, adb push a 6.0.4.6 image file to sdcard (just in case).
2. adb push the PhilZ file to sdcard.
3. In terminal emulator or adb shell (must be rooted):
4. flash_image recovery path-to-file
If it fits and all goes well, you got it.
In case of error, do same for the 6.0.4.6 image and be back in business.

Dovidhalevi said:
This is NOT a flashable zip file!
1. Download, adb push a 6.0.4.6 image file to sdcard (just in case).
2. adb push the PhilZ file to sdcard.
3. In terminal emulator or adb shell (must be rooted):
4. flash_image recovery path-to-file
If it fits and all goes well, you got it.
In case of error, do same for the 6.0.4.6 image and be back in business.
Click to expand...
Click to collapse
I wouldn't suggest anyone do that, I tried to it and almost bricked my phone (long story). I did it before you mentioned this, so it's not your fault. Apparently there isn't enough space in recovery to flash this. I think our recovery has 5mb and this recovery is almost 6mb. I may be wrong with this, but that was the error that showed up when I tried to flash it with flash_image.
It would be safer to suggest to download the recovery, rename it to recovery.img and place it on the root of another recovery zip, overwriting the old recovery, and then trying to flash it. That way, if something happens you will get an error instead of flashing it wrong. But as I said earlier, even if you try you will most likely get a Status 7 error.

indigobv said:
I wouldn't suggest anyone do that, I tried to it and almost bricked my phone (long story). I did it before you mentioned this, so it's not your fault. Apparently there isn't enough space in recovery to flash this. I think our recovery has 5mb and this recovery is almost 6mb. I may be wrong with this, but that was the error that showed up when I tried to flash it with flash_image
Click to expand...
Click to collapse
This should be the error. Then flash_image the 6.0.4.6 which fits. Do it immediately or else .... I believe I had that happen once. I posted about that 5meg limit above. Did not try this because of the limit.
It would be safer to suggest to download the recovery, rename it to recovery.img and place it on the root of another recovery zip, overwriting the old recovery, and then trying to flash it. That way, if something happens you will get an error instead of flashing it wrong. But as I said earlier, even if you try you will most likely get a Status 7 error.
Click to expand...
Click to collapse
Maybe the op should post a proper flashable zip instead. Problem is that status 7 itself might mean a brick.

Dovidhalevi said:
Problem is that status 7 itself might mean a brick.
Click to expand...
Click to collapse
Thanks for the heads up, I actually didn't try booting in recovery after the status 7 error. Now I can confirm that it tries to flash it even if it shows the error and then forces the phone to go in fastboot mode until the problem is solved.

I built using official p500 armv6 repo
They should fix the device recovery size in that case!!

Hi
Recovery Tools will work on LG p500?
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
I See LG optimus me
Because I Want To Flash The Recovery Without Taking Risk

eran32 said:
Hi
Recovery Tools will work on LG p500?
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
I See LG optimus me
Because I Want To Flash The Recovery Without Taking Risk
Click to expand...
Click to collapse
I believe this is simple a nice GUI for flash_image. Aint no such thing as no risk so beware.
The method I suggested should be safe if one flash_image's a valid recovery immediately after any error (but I make no guarantee!).
I advise against flashing this recovery version at this point because it is clearly too big for our device. We can get along just fine without a touch interface if need be. Never had one.
Changing board partition sizes is not a readily done simple matter by any means.

[RECOVERY] TWRP 2.8.7.0 for Onda v919 Air CH DualOS

Actually the first working version of custom recovery for Onda v919 Air CH DualOS -> TWRP 2.8.7.0.
This is the port TWRP for Teclast x98Pro provided by user Dani Basabe on this resource, for which many thanks to him, honor and respect.
All basic functions are working: touch, install, wipe, backup and restore, OTG-function (can make a backup on a flash drive) & etc.
Only no vibration feedback. I suppose it's not the worst thing in life...
With the appear of TWRP can install different system mods, for example, audio. After taking a backup copy of the system, of course.
I have to say: xposed on this device doesn't run! After installation bootloop.
Installation:
Place twrp.img in the root of internal /sdcard and run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/by-name/android_recovery
(I described the usual and most simple way for me. With devices through adb-interface I'm working with Total Commander with the plugin. We can try to install TWRP through fastboot commands:
adb reboot bootloader
fastboot flash recovery twrp.img)
To enter in TWRP after selecting "Android" in the main boot menu, hold down volume "-" before the advent of the service menu where the volume keys select "Recovery Mode" and press the power button.
Or you can use this method: http://forum.xda-developers.com/android/development/root-how-to-root-access-tablet-onda-t3396299
Download

Work fine!!
I just installed!
Excellent!
Thank you

ViAlexSt said:
Actually the first working version of custom recovery for Onda v919 Air CH DualOS -> TWRP 2.8.7.0.
This is the port TWRP for Teclast x98Pro provided by user Dani Basabe on this resource, for which many thanks to him, honor and respect.
All basic functions are working: touch, install, wipe, backup and restore, OTG-function (can make a backup on a flash drive) & etc.
Only no vibration feedback. I suppose it's not the worst thing in life...
With the appear of TWRP can install different system mods, for example, audio. After taking a backup copy of the system, of course.
I have to say: xposed on this device doesn't run! After installation bootloop.
Installation:
Place twrp.img in the root of internal /sdcard and run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/by-name/android_recovery
(I described the usual and most simple way for me. With devices through adb-interface I'm working with Total Commander with the plugin. We can try to install TWRP through fastboot commands:
adb reboot bootloader
fastboot flash recovery twrp.img)
To enter in TWRP after selecting "Android" in the main boot menu, hold down volume "-" before the advent of the service menu where the volume keys select "Recovery Mode" and press the power button.
Download
Click to expand...
Click to collapse
Thank you very much!
Please, try to do the mod to enable audio on latest firmware with old bios.

mismamente said:
Please, try to do the mod to enable audio on latest firmware with old bios.
Click to expand...
Click to collapse
The difficulty is that I have sound. How do I determine whether sound on other devices? I have tried to use Viper-mod, but for some reason it stubbornly refuses to install the driver. You can try different audio mods from this forum, after making the system backup. Mods based on Viper most likely will not start, therefore it's necessary to try with another engine.
I currently run an interesting RemixOS: version 2.0 starts successfully, but no wifi and sound. While thinking about it, what libraries to take from stock firmware.

mismamente said:
Thank you very much!
Please, try to do the mod to enable audio on latest firmware with old bios.
Click to expand...
Click to collapse
Try Remix OS - boot 20160429, but system audio libraries other.

ViAlexSt said:
Try Remix OS - boot 20160429, but system audio libraries other.
Click to expand...
Click to collapse
thank you, I will try.

I have a cube tablet which has the same processor (intel bay trail), how did you port the twrp? I would like to do the same from my stock recovery (if you don't mind). Thanks. All I want is advice/tips... The recovery that I've ported just reboots when entered on recovery from Droidboot.

XDA_h3n said:
I have a cube tablet which has the same processor (intel bay trail) ... The recovery that I've ported just reboots when entered on recovery from Droidboot.
Click to expand...
Click to collapse
I can't say for sure how identical processors in terms of porting TWRP (Cherry Trail <=> Bay Trail). May need more significant changes to the original TWRP. General method for porting one: from stock recovery move to port kernel and recovery.fstab. Further it's necessary to look and compare other files. Unpack/pack images possible using Carliv Image Kitchen for Android. But in your place I would have found TWRP for a more suitable tablet. What is your model? Maybe I will prompt the object of porting.

ViAlexSt said:
I can't say for sure how identical processors in terms of porting TWRP (Cherry Trail <=> Bay Trail). May need more significant changes to the original TWRP. General method for porting one: from stock recovery move to port kernel and recovery.fstab. Further it's necessary to look and compare other files. Unpack/pack images possible using Carliv Image Kitchen for Android. But in your place I would have found TWRP for a more suitable tablet. What is your model? Maybe I will prompt the object of porting.
Click to expand...
Click to collapse
Well, I've tried the method of replacing zimage and dtb images and the recovery.fstab, which was the image I created before. It just doesn't work. I would think it's something to do with an partition layout issue.
I've been using the Teclast X98 twrp, as their rom actually works on our tablet without any modifications needed other than a couple of framework changes with resolution as it causes issue with the system ui being bigger.
Anyhow, thanks for your help, I'll try to see what I can do from the tool you've provided, as I used to unpack and repack the images using another kitchen tool. It quite off-topic from this thread; thanks for you help. Here's my stock recovery if you do have free time.

XDA_h3n said:
Well, I've tried the method of replacing zimage and dtb images and the recovery.fstab, which was the image I created before. It just doesn't work. I would think it's something to do with an partition layout issue.
Click to expand...
Click to collapse
I'm pretty sure that your chances of success will increase significantly if you select TWRP for a more suitable machine. I suggest to try TWRP for Onda v820w, as most similar devices Cube iWork7: Bay Trail+Android 4.4.4 (see attachment; autor kostyamat@4pda). About dt.img: I can't tell you how to do when porting, but if you are compiling TWRP this point is taken into consideration when editing BoardConfig.mk. What concrete advice I can't give, my recovery/TWRP hasn't dt.img.
For example: I to run on Onda TWRP 3.0.2.0 for Cube iWork8 Ultimate did (unpacked Carliv Imagetool):
1. Replaced all: recovery.img-base, recovery.img-cmdline, recovery.img-kernel, recovery.img-kernel_offset, recovery.img-pagesize, recovery.img-ramdisk-compress, recovery.img-ramdisk_offset, recovery.img-tags_offset.
2. In folder 'ramdisk':
- etc/recovery.fstab -> edited blocks like me;
- replaced: file_contexts, selinux_version, service_contexts, default.prop;
- file names init.recovery.***.rc, ueventd.***.rc changed like me, contents are not changed.
It was enough for a successful launch. But there is a little roughness in it work, so don't share.
Successful porting!

ViAlexSt said:
I'm pretty sure that your chances of success will increase significantly if you select TWRP for a more suitable machine. I suggest to try TWRP for Onda v820w, as most similar devices Cube iWork7: Bay Trail+Android 4.4.4 (see attachment; autor kostyamat@4pda). About dt.img: I can't tell you how to do when porting, but if you are compiling TWRP this point is taken into consideration when editing BoardConfig.mk. What concrete advice I can't give, my recovery/TWRP hasn't dt.img.
For example: I to run on Onda TWRP 3.0.2.0 for Cube iWork8 Ultimate did (unpacked Carliv Imagetool):
1. Replaced all: recovery.img-base, recovery.img-cmdline, recovery.img-kernel, recovery.img-kernel_offset, recovery.img-pagesize, recovery.img-ramdisk-compress, recovery.img-ramdisk_offset, recovery.img-tags_offset.
2. In folder 'ramdisk':
- etc/recovery.fstab -> edited blocks like me;
- replaced: file_contexts, selinux_version, service_contexts, default.prop;
- file names init.recovery.***.rc, ueventd.***.rc changed like me, contents are not changed.
It was enough for a successful launch. But there is a little roughness in it work, so don't share.
Successful porting!
Click to expand...
Click to collapse
Thank you a lot for all of your help
I've got it working on my tablet. I am very grateful for your help.
Recovery just doesn't mount the partitions correctly, but I'll be modifying the recovery.fstab until I'll find a way. Intel does the mount points like /dev/block/platform/intel/by-label/boot on stock recovery. I'll need to find the true location of all of the partitions, but it is fixable.
Again, I am very grateful :laugh:
Lol the original recovery.fstab from the port, has the same guid name on the partition blocks. That fixed it. Everything is mounting! Thanks.
Anybody with an Linx 7 or a Cube iWork 7 I'd posted in the linx forums and there is a tool that should do everything for you soon