Database Info

[Q] recovery.img and recovery-from-boot.p

Hi all,
I am trying to make sense of how the android system is made up w.r.t to boot/kernel.
I have been looking at the .img files in the build (I built for the "passion" device), and have been googling around to find some more information about the various .img files.
I ran into a nice HOWTO in android-dls.com 's WIKI, titled HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images (I'm sorry, I'm a new user so XDA won't allow me to post links. I will try to modify my post a soon as I'm granted permission for that)
but I am afraid it is a little outdated:
I have several questions, but I will try to be brief, so I'll focus on
one of them, and if that works I'll proceed to the next questions, all related to "Android bringup for dummy embedded linux kernel experts".
I am fairly aware of differences between different linux
configurations, and I am very familiar with linux bringup concepts, so I will just use common examples from the linux world as my terminology. Hope it will be clear enough.
I understood that boot.img a combination of a kernel (e.g. bzImage in linux) and an initial ramdisk (e.g. initrd.gz), wrapped by some header, as in common linux kernel loading practice (piggy.o etc.).
Now, the aforementioned HOWTO says that the "recovery" image is built on
the same way, and that it is stored on the target's /system/
recovery.img .
I would assume that this would be compound of the ramdisk-
recovery.img, and some other kernel.
Now, the problem is that:
1. This /system/recovery.img does not exist from what I saw (on my
Motorola XOOM tablet)
2. What does exist is /system/boot-from-recovery.p , which is
created during the boot process in obj/PACKAGING/
recovery_patch_intermediates/recovery_from_boot.p .
I saw tons of posts referring to the files, all said that "in order to
replace the rescue disk image, this file needs to be renamed" - but I
am looking for a way to figure out what it is, and how to extract its
contents.
I assume /system/recovery.img is deprecated, is that correct?
3. I did not see any flash devices in /proc/mtd (which is strange).
I searched for hours before sending this post, so I would appreciate
your help. I also posted a similar message at the google android-building group, but it has not been answered yet, and I got the impression that these forums are more active and can help me get where I need.
If it is not the right place to ask the question please let me know -
I just assume this is a general android concept and not device
specific.
Thanks,
Ron

I meant of course /system/recovery-from-boot.p , and not recovery-from.boot.p
-R

Hi,
I don't know if you managed to find out what "recovery-from-boot.p" is, since this is quite an old post, but I think I'll try to help anyway.
recovery.img is not deprecated at all. From my own experience, it looks like "recovery-from-boot.p" is a protection measure introduced in Gingerbread, but not the recovery itself. What it does is replacing any recovery currently installed on the phone with the default one on every boot.
I discovered it after flashing a custom recovery on my Android 2.3.4 phone. It worked, but just during the first boot. The next time I rebooted the phone, the default recovery image was there again. After browsing several sites, I found that "recovery-from-boot.p" is responsible for that.
So, if you flash a custom recovery image on a Gingerbread phone and want to keep it forever, you must delete this "recovery-from-boot.p" from /system, or at least rename it. That way, your new custom recovery will never get overwritten buy the default one, unless you do it yourself.
I hope this helps you and clarifies this question.

Well, it helped me. I'm new to rooting and just came across mention of this file. I am trying to learn 'why' as well as 'how'', so your post was informative.

Was going to ask a dumb question but I figured it out

i need to delet those files
bigrammy said:
Was going to ask a dumb question but I figured it out
Click to expand...
Click to collapse
Hello
can't delete those files >> i am rooted but every time i delete or rename it take permission then nothing happen >> how i can delete them plsssssssssssssssssssssssssssssssssssssss

recovery from boot p
ahmed morsy said:
Hello
can't delete those files >> i am rooted but every time i delete or rename it take permission then nothing happen >> how i can delete them plsssssssssssssssssssssssssssssssssssssss
Click to expand...
Click to collapse
Hey good day. Did you get your problem fixed...? I have an xt912 it has the same file. For days I've been trying to wipe the phone. Tryed rooting it. I tryed reprogramming it. And I got through with all of that. But everytime the phone boots up it goes back to the same state. Then I used a root browser and while exploring I saw this recovery from boot file. I need help. And I don't think I can downgrade the Motorola phones. Thanks in advance.

jman0 said:
Hi,
I don't know if you managed to find out what "recovery-from-boot.p" is, since this is quite an old post, but I think I'll try to help anyway.
recovery.img is not deprecated at all. From my own experience, it looks like "recovery-from-boot.p" is a protection measure introduced in Gingerbread, but not the recovery itself. What it does is replacing any recovery currently installed on the phone with the default one on every boot.
I discovered it after flashing a custom recovery on my Android 2.3.4 phone. It worked, but just during the first boot. The next time I rebooted the phone, the default recovery image was there again. After browsing several sites, I found that "recovery-from-boot.p" is responsible for that.
So, if you flash a custom recovery image on a Gingerbread phone and want to keep it forever, you must delete this "recovery-from-boot.p" from /system, or at least rename it. That way, your new custom recovery will never get overwritten buy the default one, unless you do it yourself.
I hope this helps you and clarifies this question.
Click to expand...
Click to collapse
i have deleted it . then flash recovery ,, but it failed .. it wont even now go to stock recovery itself.. any help..

Does recovery from boot has to do anything with ota update applying ? or it will cause issues in system update ?

I have recovery-from-boot.p in my system and i cant root my phone i cant change the recovery img ... Help?

I hadn't had to deal with this for some time, perhaps because I've updated my devices (Nexus 4, Nexus 5, Nexus 7 '13) with the factory images, with "-w" removed from flash-all, then flashing CWM's recovery, ensure SuperSU was installed, then continuing. Today, I used the new OTA image on my Hammerhead/N5, and recovery-from-boot.p seems to be up to its old tricks again.
Solution is simple.
Flash your alternate Recovery in fastboot, fastboot flash recovery [recovery image file] . Boot into Recovery. Apply/install root app (typically via sideload). Mount /system. adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.bak. Reboot. Done. (If you're unfamiliar with fastboot, adb, and flashing new recovery partitions, you have some reading to do. Commence RTFM.)
I also used to have to move /system/etc/install-recovery.sh but that seems to be gone in Marshmallow. :} Or moved...?

well, after following a guide I have extracted the system.img from a pure-nexus ROM(The ROM I'm currently using), now I can see that "recovery-from-boot.p" file is responsible for recovery lock in my phone. I'll keep it short and straight to the question
"Can I remove this file and rebuild the .dat file and flash it?, so that I won't have any other problems at all"
I want to know if recovery-from-boot.p file is linked to anything other than just locking the recovery or re-flashing it innumerable times.

[Q] Deployment of image to multiple devices

Hi gurus! I have done some searching based on this, but I seem to come across many different answers based on devices, ROMs etc. So I thought I would just ask. Apologies if there is an easy guide I have missed!
I need to configure a number of Android sticks with customized settings and software then deploy them in kiosk environments. Rather than configure each one separately, I'm hoping to be able to deploy an image nice and quickly to them.
The sticks are RK30 based. The webpage is here: http://multitouch.com/istick-a200-fastest-mini-computer.html and the specs are here: http://multitouch.com/download/datasheet/istick-a200-datasheet.pdf.
They are pre-rooted and you can download a "Factory Restore Pack" which includes the ADB driver, RKBatch Tool and a single factory image. It seems pretty easy to use the tool to push the image to the device and reset it.
I'm hoping to be able to configure a single device and then backup or export the image to an img file (like the factory default one) then just push this to the other devices using the same method. Is this possible and if so, how would I create the img file?
I've read and tried to understand about img files, but it seems there are boot.img files, system.img files and a whole bunch of others. I'm guessing this is a system.img file, but if I stuff around with no direction, I'll probably just brick a bunch of devices.
I also guess I could install clockwork mod and then backup to an SD, then install cm on each new device and restore the backup, but I'm hoping to do this without even needing cm by just using the RKBatch tool.
I really appreciate any help anyone can provide. Thanks in advance!

OK - update (maybe)
Can I use this tool: http://vondroid.com/threads/updated-27-08-2012-how-to-dump-current-rom.322/? I'm guessing that the file I then want to get is the system partition? Is this the one that RKBatchTool will push back to the device?
Soooo many ways to brick!!!

[SOLVED] Wiko Rainbow Jam seems hard to root: I'm looking for help

Hi all,
I have a Wiko Rainbow Jam (which is provided with the stock rom "Wiko Rainbow Jam version 8", Android Lollipop 5.1 and the latest updates from Wiko), is about a week that I attempt to root my phone, but I am unable to do this operation, since I am totally unable to mount the /system as RW, and furthermore the bootloader is locked.
Firstly I found this method which consist to write/flash the TWRP custom recovery in place of the original one:
Root method 1
(sorry for the Google Translate link, but I cannot find the same how-to in English)
Which seems similar to this how-to
http://forum.xda-developers.com/showpost.php?p=63803008&postcount=5
But seems that these two methods will wipe/erase everything on my phone, and I would avoid this risk.
I also read that by flashing another custom recovery I will be unable to install updates from Wiko.
Then I tried this method using adb which is more simple:
https://f-droid.org/forums/topic/tutorial-how-to-root-an-android-device/
But when I launch the "adb root" command, all that I get is "adbd cannot run as root in production builds"; so I attempted various workarounds to "fix" adb, but all unsuccesfully.
I have to mention the fact that I have some skills in using Linux and the shell commands: maybe there would be a way to place the "su" binary on my Phone using Linux on my computer, by logging on the phone as root user, by acquiring the needed privileges?
Any help/suggestion/hints would be very appreciate! :good:
Kind regards.

I have a mtk6580 phone and also had the root issues, for a while I used kingroot, which rooted fine but I didnt trust it. Then I used supersume to get rid of kingroot which seemed to work but again, wasnt 100% it was all gone. Followed a similar guide to your first link which wasnt working. What worked for me was:
Download the twrp recovery .img file
rename it to recovery.img
open SPflash tools
add your own scatter file from your stock rom
deselect all the boxes except recovery
double click the recovery address box and find the renamed recovery.img
click download
plug your turned off phone in,
let it flash.
reboot into recovery
select reboot system
TWRP will tell you its not rooted and ask to install superSU
swipe for yes
reboot and you are rooted.
NO DATA LOSS

Thank you for this detailed how-to! However, for me, nor kingroot, kingoroot, framaroot and no other apk worked on my phone, so I will attempt to try your method, but first I have some questions:
1): On my phone, under SETTINGS > DEVELOPER OPTIONS, I can see the option “OEM unlocking”: I have to enable this option to permit the flashing of the TWRP img?
2): Is ok to download TWRP from here? dl.twrp.me/i9300/twrp-2.8.6.1-i9300.tar.html
3): "add your own scatter file from your stock rom":
where I can get/grab such file?
4): "TWRP will tell you its not rooted and ask to install superSU":
so TWRP is already provided with the SuperSU utility?
5): To be sure to avoid any risk, here I have a backup of my phone, which was done using "adb backup -apk -shared -all"; in case of emergency I will be able to restore my phone using this backup?
Many thanks for your attention! :good:

Mister_Dave said:
3): "add your own scatter file from your stock rom":
where I can get/grab such file?
Click to expand...
Click to collapse
Ok, seems that such file was available in the first link:
s000.tinyupload.com/download.php?file_id=53888272183191245346&t=5388827218319124534686744
is called MT6580_Android_scatter.txt , can you take a look and tell me if is ok?
Many thanks!

1) cant hurt to turn it on, however the phone will be flashed whilst turned off so dont know if its needed, but Im sure I wouldve enabled it.
2) and 3) I dont know what your exact model number etc.. is for your phone, so the twrp you would have to find and check yourself, go here: http://www.needrom.com/category/others/u-v-w-x-y-z/brands-w/wiko/ and you can try to get a twrp from there, and definetely get a stock rom. Use the scatterfile from an 'SP TOOLS FLASHABLE STOCK/UPDATE ROM'
4) yes
5) I dont know, I dont use adb and wouldnt like to say its OK. You can use this: https://play.google.com/store/apps/details?id=com.h3r3t1c.onnandbup&hl=en which will make a TWRP or CWM backup of your entire phone which you can then flash in TWRP or CWM once they are flashed, or get all the data from the backup. I would advise to find this out before trying though, just in case. I personally didnt lose any data, flashed twrp in SPtools, took 5 seconds, rebooted, added SU, rebooted, took 2 minutes and everything was still there.
---------- Post added at 04:43 PM ---------- Previous post was at 04:41 PM ----------
it has to be a scatter file from your exact model of phone, as everything has to match, partitions, nvram...etc... loads of things that can go wrong if the scatter is wrong

robneymcplum said:
2) and 3) I dont know what your exact model number etc.. is for your phone, so the twrp you would have to find and check yourself, go here: http://www.needrom.com/category/others/u-v-w-x-y-z/brands-w/wiko/ and you can try to get a twrp from there, and definetely get a stock rom. Use the scatterfile from an 'SP TOOLS FLASHABLE STOCK/UPDATE ROM'
Click to expand...
Click to collapse
I went there, but my model is not listed.. As I stated in the subject is a Wiko Rainbow Jam: if i search for Rainbow Jam is such link, no model is displayed..
it has to be a scatter file from your exact model of phone, as everything has to match, partitions, nvram...etc... loads of things that can go wrong if the scatter is wrong
Click to expand...
Click to collapse
I got the scatter file in the first link "Root method 1", where there is the how-to for my exact model.

ah right, in that case, its OK

robneymcplum said:
ah right, in that case, its OK
Click to expand...
Click to collapse
Ok: it was painless differently from what I thought: now, following your advice (I used the TWRP and the scatter file from the first link) my phone is nicely provided with the root access
EDIT: was necessary to activate the “OEM unlocking” option under SETTINGS > DEVELOPER OPTION, without this option activated, I was unable to flash the TWRP recovery img.
Many thanks!
p.s: If a moderator see this post, feel free to add [RESOLVED] to the title of this thread, since I cannot edit the title.

Glad it worked lots of guides I saw also made it excessively complicated, this way took you what? 2 minutes? And am guessing all your data is safe and untouched.

robneymcplum said:
Glad it worked lots of guides I saw also made it excessively complicated, this way took you what? 2 minutes? And am guessing all your data is safe and untouched.
Click to expand...
Click to collapse
Yeah, it took about 2 minutes, just the time to figure out that I needed the USB OTG cable with an usb mouse and to browse to the UPDATE-SuperSU-v2.76.zip file (as I said I used the TWRP posted in the first link, which doesn't work with the touch screen).
I want to say thank you again for your friendly assistance!
EDIT: Yes: all my data is safe and untouched!

Like:good:

Kiwami Samurai FTU152D stock Lollipop 5.1, Root and Xposed, Help and Tips

This post is to help users who have accidentally or on purpose tried to upgrade to Android 6.0 on their Kiwami Samurai FTU152D using software for FTJ152D (Japanese version of phone), and to help with root and installing Xposed on your phone. There is a risk of getting the phone stuck on boot screen if a user uses certain versions of SuperSU. If you searched the net and found this thread, and are still on Stock Rom for your FTU152D, Do not Upgrade until you have read this thread. Upgrading by flashing a rom using SP Flash Tool you risk losing your IMEI information in the phone forever. I am going to write this thread with an assumption that reader has upgraded the software in their phone using the Japanese Firmware. You can read through and use this thread based on your situation and if confused, better to ask questions on the thread than trying something on your own. I do not take any responsibility if you brick or hard brick your phone, so please be careful and do not just randomly flash things without full understanding, confused? ask questions.
Note #1: First and Foremost, Be careful to not flash a preloader.bin file in your phone from other phone models. You run the risk of permanently bricking your phone. Use the correct preloader made for your phone.
Note#2: Make at least a 5 GB backup dump of your phone using SP Flash Tool 'Read Back' tab before you attempt root or other customizations on your phone. This can be done using the scatter file from stock rom of FTJ152D Android 6.0 available at needrom website at:
https://www.needrom.com/download/freetel-samurai-kiwami-ftj152d/
You will need to input scatter file in the download tab before SP Flash tool will allow you to do a 'Read Back' dump of your phone. Be very careful when attempting this and do not accidently download (the whole reason of this thread and my troubles is because I did exactly that). In 'Read Back' tab, you can click on 'Add', name the raw dump, and add the starting address (that will be 0 of course) and make the length equivalent of at least 5 gigabytes, make sure that you have selected the 'EMCC_USER' as your region. Use 'Add' to add another 'Read Back', this time for preloader (in boot_1 region). You can open the scatter.txt file from the rom you downloaded earlier to see how long this 'Read Back' needs to be. Next, click on 'Read Back' to start the backup dump, power off and connect your phone via usb to the computer. (You may need the VCOM drivers, if the phone is not detected by SP Flash Tool or you keep getting errors, search for the driver online or download it from the needrom website, same page where the rom is (link above). Keep these two dump files safe as these are effectively your backup in case you mess up your phone.
ROOT and Xposed:
If on lollipop there are at least couple of options to root using kingroot (personally dislike) and others. If on Marshmallow, you can use my posts in this thread to root using Magisk:
https://forum.xda-developers.com/general/help/how-to-root-freetel-kiwami-samurai-t3610015
Recover from Japanese firmware and/or Going back to Lollipop:
In case you have flashed the Japanese firmware and now have problems using the phone and want to go back to FTU152D stock rom (Android 5.1) with correct baseband, use the attached file (mega link below) with SP Flash Tool. First, find an nvram.bin file online compatible for mtk6795 chipset or look at this page as you can download a nvram.bin from there:
https://afterroot.wordpress.com/2015/07/22/mtk-restore-nvram-bin/
***Very Important Note*** Nvram.bin file as the one on the above website will fix your phone, especially the baseband (all the better if you made a backup using the method mentioned in Note#2 above, you can use the scatter file and hex editor (such as HxN from download.cnet.com) to cut out the nvram.bin and secro.img (need both to restore imei and baseband) partition file from the raw dump) but the IMEI numbers will be specific to the nvram.bin file you use (and this is why i didn't provide my backup nvram file, but i did provide secro.img as it contains baseband info), and using wrong imei number with your phone may not be legal. If you use the file from the above website, your IMEI numbers will be specific to that file and you MUST change your IMEI numbers to your original numbers using a number of apps or other methods available online, just search the web.
You should unzip the rom zip from this link:
https://mega.nz/#!1v4GUaBC!Wj4JW6fZkxNB-ZISrdPmBcR_hu_XSu9NoCrnOKYMdYo
that I put together by dicing raw dump of my phone using SP Flash Tool and putting together some of the files from the MM folder. Some of these files may not be needed for a successful installation but i just wanted to be sure because I had issue with some folders not being visible in the phone's internal memory. Make sure you insert an nvram.bin file in the rom folder before proceeding otherwise your phone sims will be greyed out, choose the scatter file in the folder with SP Flash Tool download tab, and use 'format all + download' option in download tab, click on 'Download', power off the phone and attach to PC via USB cable. Once download is done, power up your phone and you are done. Now you can root and install xposed, and fix your IMEI numbers if they are wrong using the tips and link provided above if like.
I am trying to get a custom recovery to work with this phone but so far because there is no touch in recovery mode, TWRP doesn't work. If anyone have been able to install or use custom recovery, please share your experience and help out others. Thanks.

If anyone have internal phone storage not showing DCIM, Alarm, Ringtones, and other folders, make sure you don't have an SD card in the phone, do full factory reset after flashing, go to storage settings and make sure the internal phone storage is selected for write to memory, then insert SD card in the phone. That fixed this issue for me. It is just how this phone is setup that you have to select internal phone storage or external sd card for where the stuff gets stored.
Another fix that worked for me was to remove SD card from phone, format whole flash except bootloader in format tab first, flash all files except userdata.img and cache.img in download mode, and then make sure you go directly to stock recovery at first power on (hold volume up while powering up the phone), wipe cache and wipe data/factory reset, and then allowing the phone to boot up the first time.

Another tip for other Kiwami Samurai users i wanted to share is that both Freetel roms (5.1 & 6.0) come pre-installed on either variant of phone with 3 potential malware or PUPs that i just detected using Malwarebytes (see screenshot). I wouldn't have expected this from a Japanese smartphone manufacturer. These are installed as system apps and require root and an app like Titanium Backup to freeze and/or remove these. 'Debloater' app by Gatesjunior on xda forums can also remove these.

Thank you for the thread.
I have this phone, the US version FTU152D.
From what I can find on XDA and other places. there is no update to Marshmellow available for the US version. Can you confirm?
I see your methods above. I am thinking of flashing stock ROM to the phone to clean up some issues. Think of it as a clean install.
Thank you,

Onda v820w ch v3, dual boot, win 10 64 bit home + android 5.1 (files, instructions)

Hi guys,
I bought this tablet at the end of 2016. I played a lot with it, about 2 years. I sold it at the end of 2018.
These days i try to make some space in my hard drive, so i delete some files.
I have downloaded on 2016 many things about this tablet. Even now, Onda's official site is in Chinese and i saw that Onda Forum is down.
So i decided to upload here my experience, some instructions and service files about this tablet.
I will upload the files i have not at once, so before asking questions wait a little.
Enjoy
P.S : Sorry, now i saw that there is a limit on the size of files that a member can upload !! I wanted to upload the Original ROMS of this tablet (they are some GBs !!).

Please put the instructions
Hello,
I appreciate your good will gesture. I am interested in reinstalling the os on such a tablet ( I think mine is v5) and I can't find instructions and files for windows only the V820W_DUALOS_V5_32_1605279_20160602.zip(after windwos 10 reset I can't boot windows ,works only on Android). Hope you will continue, thanks.

Found solution to recover Windows 10 on tablet but lost Android
Hello , after some more search I found an interesting russian forum with many download links for this tablet. Here is a download link that contains many of the necessary files for Onda v820w from there:
........
For my case (tablet was reseted from windows options I presume, and was not able to boot anymore just some automatic repair started but did not work) , making a NTFS bootable disk with rufus and copied all the windows files from 10_V3.rar found in the download link provided and choosing ->"System image recovery"->then something about boot from EFI usb drive I remember. And it worked, it managed to reinstall windows and make it boot again by itself.
After succeeding this I became more confident and tried to update the Android form this tablet from 4.4 to 5 as I saw it has everything we need in the above link. After trying different versions of Manufacturing flash tool and Intel drivers for this tablet I managed to connect to it and make it take the provided image with Android 5 from fastboot menu when connected to laptop with the flash tool.
The only problem is it said it does not have enough space to flash system.img at around 84% on the Manufacturing flash tool loading bar. (strange as the tablet is empty,nothing on it, just default software).
Now Android does not boot anymore (haha, fixed something destroyed something).
The questions are:
-Can and how to use the other Android 5 images I found on the russian forum ? They are different type of backup files (with system.ext4.win type of files not .img files that the manufacturing flash tool expects).
From what I've read they are TWRP generated backups but my tablet has the default recovery.
-Can I convert the TWRP files to .img ?
-I found an TWRP recovery for this tablet (I hope) but I am not sure that if I flash the TWRP recovery it will not mess with the windows partitions already working on this tablet...
Here are the files I found and some english step by step tutorial for flashing the Android and a spanish tutorial for the Windows part of this tablet, on my google drive:
......
Edit: "To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!"
So I cannot post yet the links to images and the files but if somebody is interested I will sent in private massage. (If I will remember about this post in a few months , pretty lame the anti-spam rule...) Now I understand why who initiated this thread abandoned it...

RE: Links to Onda v820w windows files
Hi Olaruci,
I seem to have a similar problem to the one you and POWERSER have had. Please can you assist with the download links for this tablet. I can't boot the tablet into Android or Windows, only the system recovery option is available to me and it doesn't work.
Thanks :good:
Olaruci said:
Hello , after some more search I found an interesting russian forum with many download links for this tablet. Here is a download link that contains many of the necessary files for Onda v820w from there:
........
For my case (tablet was reseted from windows options I presume, and was not able to boot anymore just some automatic repair started but did not work) , making a NTFS bootable disk with rufus and copied all the windows files from 10_V3.rar found in the download link provided and choosing ->"System image recovery"->then something about boot from EFI usb drive I remember. And it worked, it managed to reinstall windows and make it boot again by itself.
After succeeding this I became more confident and tried to update the Android form this tablet from 4.4 to 5 as I saw it has everything we need in the above link. After trying different versions of Manufacturing flash tool and Intel drivers for this tablet I managed to connect to it and make it take the provided image with Android 5 from fastboot menu when connected to laptop with the flash tool.
The only problem is it said it does not have enough space to flash system.img at around 84% on the Manufacturing flash tool loading bar. (strange as the tablet is empty,nothing on it, just default software).
Now Android does not boot anymore (haha, fixed something destroyed something).
The questions are:
-Can and how to use the other Android 5 images I found on the russian forum ? They are different type of backup files (with system.ext4.win type of files not .img files that the manufacturing flash tool expects).
From what I've read they are TWRP generated backups but my tablet has the default recovery.
-Can I convert the TWRP files to .img ?
-I found an TWRP recovery for this tablet (I hope) but I am not sure that if I flash the TWRP recovery it will not mess with the windows partitions already working on this tablet...
Here are the files I found and some english step by step tutorial for flashing the Android and a spanish tutorial for the Windows part of this tablet, on my google drive:
......
Edit: "To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!"
So I cannot post yet the links to images and the files but if somebody is interested I will sent in private massage. (If I will remember about this post in a few months , pretty lame the anti-spam rule...) Now I understand why who initiated this thread abandoned it...
Click to expand...
Click to collapse

Download links Onda v820w
Hello Grimm1,
I've sent the download links in private message.
I still did not manage to flash any of the system.img files ( I tried to unzip system.ext4.win images and change extension to .img but it's not working, not valid).
So I've changed the original recovery.img with the TWRP recovery found in the download link, and it works.
Now I have TWRP but with a small problem, it's in russian... now I try to find a way to change language (it's the materialized theme of TWRP 2.8 , and it seems it does't have a change language option)
Also windows 10 on PC needs latest versions of:
- Manufacturing flash tool (6.051)
- IntelAndroidDrvSetup1.10.0
- iSocUSB-Driver-Setup-1.0.4 or 1.0.5 (I THINK THIS IS THE MOST IMPORTANT to have latest version FOR THE MANUFACTURING FLASH TOOL TO SEE THE TABLET)
Also only connect tablet to laptop usb(in fastboot mode) AFTER opening manufacturing flash tool and AFTER selecting xml file and message "ready to flash" appears.

Hi,
I'm using an Onda v820w dual OS. I like this tablet and its dual OS capability.
I'm trying for days to find a way to change a few things but ondaforum is down so it's not easy now.
Once I succede I will give links and steps.
A first link where there is a lot to download : http://chinagadgetsreviews.blogspot.com/search?q=v820w&x=0&y=0
/!\ WARNING /!\ I did not test any of the software found on the link above so don't blame me if it screw your devices.
The first step was to install TWRP to be able to flash Android 5 instead of 4.4. The one I use is in russian for the moment so I use Google translate...
Anyway I just flashed Android 5.1 found on a russian forum a few minutes ago. For the moment the tablet is on the boot anim for at least 20mn...
I will tell you.

Need links
Hey @Olaruci can you please send me files as well?
Having the same issue after recovery

headshotp said:
Hey @Olaruci can you please send me files as well?
Having the same issue after recovery
Click to expand...
Click to collapse
You've got message
And now I can post links apparently :
https://drive.google.com/open?id=1lhb29j5tnwyvyZS5KUzEuxNVYBKxaBoa

Hi
Is there anyone who succeeded with Remix OS on this tablet?

v1 bios
I need onda v820w v1 bios flash please. My camera dont work anymore after wrong bios updating. please help me...
---------- Post added at 03:15 PM ---------- Previous post was at 03:13 PM ----------
Olaruci said:
You've got message
And now I can post links apparently :
https://drive.google.com/open?id=1lhb29j5tnwyvyZS5KUzEuxNVYBKxaBoa
Click to expand...
Click to collapse
hi you have for v1 bios ? please help me.

Olaruci said:
You've got message
And now I can post links apparently :
https://drive.google.com/open?id=1lhb29j5tnwyvyZS5KUzEuxNVYBKxaBoa
Click to expand...
Click to collapse
Hi Olaruci, thanks for the link it was a lifesaver for me
I only stumbled to one problem - for some reason I can not calibrate my Touchscreen. It works, but nither the Touch PG or MS Calibration software helped me...the calibration is just off (few cm gap). Did anyone had this kind of problem and what do you think I could do to solve this problem?
Kind regards to everyone who contributed this feed....it helped a lot.