Related
Hello,
I have prepared a few update.zip's with kernels to boot linux:
There are two different zips.
One to boot linux from a USB Flashdrive and the other from a SD card.
Installation Instructions:
ALWAYS HAVE CHARGER CONNECTED WHEN UPDATING A FIRMWARE.
1. Please follow the instructions here to prepare your SD / USB Drive - start at "== Create a rootfs SD card ==". http://ac100.gudinna.com/README/
2. Extract contents to a folder and follow instructions below.
copy the update.zip to a sdcard, and insert sdcard into folio.
Enter "Recovery menu" when folio is just turned on and press (POWER) once and (VOL up) next.
press (VOL up) Factory reset or system update.
press(VOL down) to continue to system update.
press (VOL up) to confirm system update.
during installation progress bar will show har far it is.
folio will reboot after installation.
insert the usb or flashdrive with the prepared filesystem into the folio and the tablet will boot automaticly from it
This sounds very interesting, might give it a try when im done playing with my new folio, ubuntu on it would be awesome
Does it boot to a full Ubuntu desktop or a bash prompt?
key combination to boot ubuntu
DerArtem said:
Hello,
I have prepared a few update.zip's with kernels to boot linux:
Please follow the instructions here to prepare your SD / USB Drive - start at "== Create a rootfs SD card ==".
Unzip the zip and then use the zip inside to update your kernel.
There are two different zips.
One to boot linux from a USB Flashdrive and the other from a SD card.
Click to expand...
Click to collapse
Hi DerArtem,
once the media (SD) is setup, you need special key combo in order to let folio boot from the SD? thanks in advance.
zoken4 said:
Does it boot to a full Ubuntu desktop or a bash prompt?
Click to expand...
Click to collapse
It depends on what you have put on your sd / usb flash.
Ivalex said:
Hi DerArtem,
once the media (SD) is setup, you need special key combo in order to let folio boot from the SD? thanks in advance.
Click to expand...
Click to collapse
I have updated the 1st post.
DerArtem said:
It depends on what you have put on your sd / usb flash.
I have updated the 1st post.
Click to expand...
Click to collapse
gorgeous!
got it, the first step, is exactly the same as uploading a mod. then the SD modified as per gudinna instr. will bring you to linux.
thanks again.
how fast/responsive is this? Can you benchmark it against the AC100 netbook running the same image - that had a noticeable lag at least on SD card access.
How prepare the SD?
Thank you for your work!!!
I did all the process but I can't start linux.
The kernel boots but stop without start the desktop.
You can see when stops in this image:
ifisc.uib-csic.es/~edu/fotos_folio100/1.jpg
(Put the http:..., I can't put links because the system)
I prepared the filesystem in a SD card only decompressing the tar.gz, ¿Is necessary recompile the kernel or something like configure it?
Shark.
Shark17 said:
Thank you for your work!!!
I did all the process but I can't start linux.
The kernel boots but stop without start the desktop.
You can see when stops in this image:
ifisc.uib-csic.es/~edu/fotos_folio100/1.jpg
(Put the http:..., I can't put links because the system)
I prepared the filesystem in a SD card only decompressing the tar.gz, ¿Is necessary recompile the kernel or something like configure it?
Shark.
Click to expand...
Click to collapse
I have not tested it using a SD-Card. I will try it out when I have some time...
I met the same problem : stuck at the "no console found" point, and this either with an sd-card or a usb key. I also tried wolfx's method (boot via fastboot), and had the same problem.
To me, it seems that this must come from the system we put on the sdcard/usb key.
DerArtem : could you tell us what distro you put on your usb-key ? (and maybe even with links for download ?)
Regards,
eRaph
USB tried
I tried with the USB and had the same problem.
To me, it seems that this must come from the system we put on the sdcard/usb key.
Click to expand...
Click to collapse
I'm agree with your opinion.
I confirm that the method is not agressive for the tablet, restore android works for me.
Actually, I just found what the problem was : on the image I uncompressed on the usb key (tegra-rootfs.tgz), the /dev directory was empty, and lacked a console and a null entry (see h**p://ubuntuforums.org/showthread.php?t=28550)
The folowing command solved the problem (to do on your sdcard/usbkey) :
cd dev
mknod -m 660 console c 5 1
mknod -m 660 null c 1 3
Hi,
eraph2 said:
I met the same problem : stuck at the "no console found" point, and this either with an sd-card or a usb key. I also tried wolfx's method (boot via fastboot), and had the same problem.
To me, it seems that this must come from the system we put on the sdcard/usb key.
DerArtem : could you tell us what distro you put on your usb-key ? (and maybe even with links for download ?)
Regards,
eRaph
Click to expand...
Click to collapse
I have used gentoo linux on a usb flash:
http://dev.gentoo.org/~armin76/arm/tegra2/install.xml
http://www.gentoo.org/doc/en/handbook/handbook-arm.xml
eraph2 said:
Actually, I just found what the problem was : on the image I uncompressed on the usb key (tegra-rootfs.tgz), the /dev directory was empty, and lacked a console and a null entry (see h**p://ubuntuforums.org/showthread.php?t=28550)
The folowing command solved the problem (to do on your sdcard/usbkey) :
cd dev
mknod -m 660 console c 5 1
mknod -m 660 null c 1 3
Click to expand...
Click to collapse
Yes, this files exists in the gentoo in the .tgz ....
I think that ubuntu might require a initrd...
And ubuntu works?
Can you start ubuntu fixing this?
Console
Creating the console in the dev..., ¿are you started ubuntu?
I successfully managed to boot the ac100 ubuntu image (tegra-rootfs.tgz) copied on my sdcard. X started well, and hooking a keyboard, I managed to create a user, edit his password, ...
Nevertheless, I did not manage yet to make both a keyboard and a mouse work at the same time (the usb hub does not seem to work), and unpluggin/replugging the keyboard did not work either.
So, the ac100 ubuntu image works somewhat (in text mode via ALT-F1, i managed to get root access), but seems to lack some hardware support (which is quite normal).
The first problem is probably that the boot.img I used was the one DerArtem provided with his modified sdmmc-update.zip archive, which contains a 2.6.32 kernel, whereas the ubuntu image uses a 2.6.29-ac100 kernel, hence no modules get loaded. I should find how to rebuild a boot.img with the good kernel (or better : add the good modules to the ubuntu image).
DerArtem : may I ask you how you did rebuild the boot.img in your various packages ?
Regards,
eRaph
eraph2 said:
I successfully managed to boot the ac100 ubuntu image (tegra-rootfs.tgz) copied on my sdcard. X started well, and hooking a keyboard, I managed to create a user, edit his password, ...
Nevertheless, I did not manage yet to make both a keyboard and a mouse work at the same time (the usb hub does not seem to work), and unpluggin/replugging the keyboard did not work either.
So, the ac100 ubuntu image works somewhat (in text mode via ALT-F1, i managed to get root access), but seems to lack some hardware support (which is quite normal).
The first problem is probably that the boot.img I used was the one DerArtem provided with his modified sdmmc-update.zip archive, which contains a 2.6.32 kernel, whereas the ubuntu image uses a 2.6.29-ac100 kernel, hence no modules get loaded. I should find how to rebuild a boot.img with the good kernel (or better : add the good modules to the ubuntu image).
DerArtem : may I ask you how you did rebuild the boot.img in your various packages ?
Regards,
eRaph
Click to expand...
Click to collapse
Hi,
please search on the web how to rebuild the boot.img. This is not a problem. My zip also contains the config to rebuild the kernel. The sources of the kernel are also documented in the readme inside the zip. The initrd is just empty.
But running ubunu on the folio might be a bad idea. Ubuntu is compiled for NEON instruction set, but the Tegra 2 CPU does not support this, so a lot of applications can crash when they will try to execute more advanced code....
Debian (optimized for ARMv6 without NEON) or Gentoo are better for the Folio.
Then, if I want to install gentoo instead ubuntu, do I have to follow the same steps but changing the distro linux for the gentoo? Or is it necessary to do anything else?
Thanks
I tried to install gentoo in a USB, but it's a long process and it's not usual for me.
I'm very lost!
halu:
If you obtain a opetative distro image, can you upload in any place?
I'm thinking in write a howto with the results.
Bests
(Saludos desde Mallorca!! )
Hi
I've done a bit of searching but can't find anything too specific to what I'm trying to do. Basically we have 10 Android tablets, and I want to make them all standardised e.g. have the same Apps on, configured in the same way (e.g. enterprise wireless network added).
Now the thing is if anyone messes around with them I want a really easy way to restore them to the original config which I've done.
One way I thought was to configure one fully, install Titanium Backup on it, do a full backup of apps/system data etc, and put the backup onto an SD card. Then I already have the base ROM on an SD card so if theres any problems, I can just flash the ROM over it again, install TB, and restore all the data. Would this be suitable to do to duplicate the data onto 10 tablets, and also restore the data if required?
The other thing I looked into was customising a ROM myself, don't want to do anything too tricky it'll just be a case of removing all the preinstalled crap I don't want, preloading the Apps we do want, and if possible preloading the wireless key and getting rid of the first boot initial set up wizard.
PS I've looked at installing CWM and doing whole image backups, but supposedly the tablet isnt supported (its an Ainol Novo 7 Elf 2)
Any advice would be great, hopefully theres some fairly straight forward way of managing this
Thanks
One of the reasons I integrated a full blown GNU/Linux on my devices, was the need to run full and automated backups. If you are looking into the possibility making a custom ROM, this might be a solution for you as well. I'm using BackuPC to run backups nightly, backing them up as any other GNU/Linux machine (using tar over ssh).
See the link in my signature for more information about this.
kuisma said:
One of the reasons I integrated a full blown GNU/Linux on my devices, was the need to run full and automated backups. If you are looking into the possibility making a custom ROM, this might be a solution for you as well. I'm using BackuPC to run backups nightly, backing them up as any other GNU/Linux machine (using tar over ssh).
See the link in my signature for more information about this.
Click to expand...
Click to collapse
Hi
Thanks for the reply, not too sure this would be the right option for us. I don't really need to take nightly backups, I just need to make a backup of a preconfigured image, and then put that image onto 10 other devices. Then I want to keep the original backup and have an easy way to restore it onto any devices which have been messed up. Sort of like image cloning for PCs, I want to prepare a base image, and then flash it over all the devices.
fro5tie said:
Hi
Thanks for the reply, not too sure this would be the right option for us. I don't really need to take nightly backups, I just need to make a backup of a preconfigured image, and then put that image onto 10 other devices. Then I want to keep the original backup and have an easy way to restore it onto any devices which have been messed up. Sort of like image cloning for PCs, I want to prepare a base image, and then flash it over all the devices.
Click to expand...
Click to collapse
Ok, I see. Compile the image to you likings (boot image and system partition), and then flash it using fastboot onto you devices.
Hi
Does anyone have any more thoughts on this?
I have experimented with Titanium Backup and this seems to work quite well. I have installed a ROM, and customised it e.g. installed the apps I need and configured the apps, wireless settings and home screens etc. Then I do a full apps + system backup in TB to my SD card.
Then the plan is, I can reflash the ROM onto the other device, install TB and then restore this backup. This saves my user state and wireless settings etc.
Only problems is when I flash the ROM, I have to go through all the initial set up again and also remove some preinstalled apps which I dont want. Any ways around this?
There must be something I'm missing. Why don't you install the device, walk through the setup, remove the bloatware you don't want and then dumps the disk partitions into images you flash the other devices with using fastboot? This way you'll get'em cloned, isn't it this you want..?
Of course there's still some tinkering needed once restored/cloned, such as giving them individual Google accounts etc, but you can easily fix this without re-running the setup wizard.
kuisma said:
There must be something I'm missing. Why don't you install the device, walk through the setup, remove the bloatware you don't want and then dumps the disk partitions into images you flash the other devices with using fastboot? This way you'll get'em cloned, isn't it this you want..?
Of course there's still some tinkering needed once restored/cloned, such as giving them individual Google accounts etc, but you can easily fix this without re-running the setup wizard.
Click to expand...
Click to collapse
Hi
Yes that's what I want to do! How would I go about dumping the disk into an image and then flashing?
fro5tie said:
Hi
Yes that's what I want to do! How would I go about dumping the disk into an image and then flashing?
Click to expand...
Click to collapse
There are several methods. Some boot loaders (such as nvflash for tegra based devices) can actually read back the disk partitions to a computer via the USB port. You can also on the tablet read the raw mtd device with busybox/dd. I assume you've unlocked the bootloader and gain root access to the device, since this is a requirement for flashing them as well. A third alternative is using busybox/tar, and then recreate the filesystem image using mkyaffs (or if ext3/ext4 even easier, just loopback mount an image on you linux maching to unpack the tar archive to). Once you got the images (system and userdata partitions), you flash the devices with "fastboot flash system system.img" and "fastboot flash userdata data.img". I don't believe you'll need to tamper with the other partitions.
kuisma said:
There are several methods. Some boot loaders (such as nvflash for tegra based devices) can actually read back the disk partitions to a computer via the USB port. You can also on the tablet read the raw mtd device with busybox/dd. I assume you've unlocked the bootloader and gain root access to the device, since this is a requirement for flashing them as well. A third alternative is using busybox/tar, and then recreate the filesystem image using mkyaffs (or if ext3/ext4 even easier, just loopback mount an image on you linux maching to unpack the tar archive to). Once you got the images (system and userdata partitions), you flash the devices with "fastboot flash system system.img" and "fastboot flash userdata data.img". I don't believe you'll need to tamper with the other partitions.
Click to expand...
Click to collapse
Hi
Thanks for the quick reply, much appreciated.
Unfortunately you've lost me a bit here!
Yes the device is rooted, I dont have a linux machine though.
Any chance you'd be able to provide some more specific instructions? The device is a chinese tablet from manufacturer Ainol, the model is a Novo 7 Elf 2. Unfortunately there isn't much discussion on these online so specific help is hard to find!
fro5tie said:
Any chance you'd be able to provide some more specific instructions? The device is a chinese tablet from manufacturer Ainol, the model is a Novo 7 Elf 2. Unfortunately there isn't much discussion on these online so specific help is hard to find!
Click to expand...
Click to collapse
I can provide you specific answers to specific questions, but I have no experience of the tablet in question, so you'll have to do some digging yourself first. Make sure it supports fastboot, investigate what the proprietary bootloader is capable of, see how/if you can obtain an original image etc.
One maybe easier solution, especially if you plan to restore the tablets on a regular basis, is to only make a new boot image to reflash the devices with. The only modification done is that you change the /init.rc script to mount /data and /system from the SDcard instead of from the internal nand disk device.
Once this is done, you'll power up and run the installation wizard and everything on your master tablet. Then power it down, and clone the SDcard. This SDcard now contains everything, so you'll simply restore a device by replacing its SDcard with a copy of this master card. I guess it's easier to clone a SDcard than reflashing several internal partitions. Easier to make the master as well - you don't need to dd or tar them, they are already in "image" format. If you can get hold of the original firmware, this should be quite easy without the need to preserving data from the device itself.
fro5tie said:
Any chance you'd be able to provide some more specific instructions?
Click to expand...
Click to collapse
Issue the commands "cat /proc/mtd" and "mount" on your device at command prompt (e.g. via "adb shell" or the "ConnectBot" terminal app). This shows you if the device allows you to copy the boot image from it. Paste in the output into this thread. If you believe the "clone the tablet via the SDcard" is a good solution for you, the process is in short terms something as below;
Copy the boot image to the sdcard:
# dd if=/dev/mtd/mtd2ro of=/mnt/sdcard/boot.img bs=2048 (device dependent of contents of /proc/mtd)
Remove the sdcard, insert into a computer, split the boot image info kernel + initramfs. Read http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images for instructions about how to work with the boot.img file. I really recommend a GNU/Linux environment for this.
Then edit /init.rc replacing the "mount yaffs2 [email protected] /system" with "mount ext3 /dev/block/mmcblk0p2 /system" for system and data (use p3 for data partition, the device name may be different on your tablet, see mount output).
Create an SDcard with three partitions: #1 vfat (standard), #2 and #3 ext3. Insert into you device and boot it up again.
# mount -t ext3 /dev/block/mmcblk0p2 /root
# cd /system
# tar cf - . | (cd /root ; tar xf - )
# umount /root
# mount -t ext3 /dev/block/mmcblk0p3 /root
# cd /data
# tar cf - . | (cd /root ; tar xf - )
# umount /root
This copies your partitions to the SDcard. Shutdown the tablet again.
Make a new boot.img using the instructions in the link above, using the edited init.rc script.
Now you can non-destrutive give this a try.
Place you tablet in fastboot mode (often vol-up (or vol-down) during power on).
$ fastboot devices
This vill verify the tablet is in fastboot mode. It should be listed. Then:
$ fastboot boot boot.img
Note here, only BOOT the tablet, do NOT use the "flash" keyword. This in case of the image isn't working, you'll just have to restart you tablet, and no harm's done.
Look around. Do a "mount" command. Everything works? Mount shows /data and /system from sdcard? Perfect. Now you can reflash it. Shutdown and flash:
$ fastboot flash boot boot.img
Now the device will use /data and /system from the SDcard every time. Customize your device, and then clone your SDcard and try it in tablet #2 you'll booting with your new boot.img and the cloned SDcard. Verify that #tablet #2 is a perfect clone of tablet #1. It is? Now you can flash the boot,img into all your tablets.
--------------------
But don't forget, there may be other solutions as well, maybe more suitable. This you'll have to investigate yourself.
And the usual disclaimer - you can probably not follow above by the letter. There sure is some obstacle you'll have to overcome, something non-standard, etc.
Also keep the original boot.img file for safekeeping in the case you want to restore the device's boot image some day.
Wow! Thanks for the info! This is really helpful, I need to set aside a bit of time to work through this and have a look. Thanks again its really appreciated, I'll be back with info once I've had chance to give it a go!
I certainly can't offer more detailed info than the fellow from Sweden who seems to really know his stuff...but what about making a nandroid backup of your fully configured reference tablet (I'm assuming all tablets are rooted). Ensure all your tabs have CWM recovery and copy your nandroid file to each one.
If any of your fleet get 'corrupted' you can simply restore the original, fully configured ROM.
In fact that sounds too obvious..likely I missed something about your scenario which precludes this option from consideration!
Good luck mate.
tweeny80 said:
I certainly can't offer more detailed info than the fellow from Sweden who seems to really know his stuff...but what about making a nandroid backup of your fully configured reference tablet (I'm assuming all tablets are rooted). Ensure all your tabs have CWM recovery and copy your nandroid file to each one.
If any of your fleet get 'corrupted' you can simply restore the original, fully configured ROM.
In fact that sounds too obvious..likely I missed something about your scenario which precludes this option from consideration!
Good luck mate.
Click to expand...
Click to collapse
Hi
Yes that was my first thought as well, tablets are rooted yes but there is no CWM for the tablet. Its an obscure Chinese branded tablet.
Unless there is another way to do nandroid backups?
hmm tricky situation. Catch 22 ! From what I know, your best bet is to backup all possible things through Titanium Backup given that you don't have the use of Nandroid backups. You can include wifi settings, messages etc but it's modular & not systemic.
I did a quick google search with no luck - time to upgrade your fleet dude :-0
Best of luck.
Hi,
I'm new to Archos Hardware and their SDE, but I'm a long time Android user
and Custom ROM installer .
I have a hard time understanding how the SDE and multi boot works on the
Archos devices. I think only one kernel is used and the second filesystem
(2nd ROM) is mounted as a loop device.
Recently I tried to install DropBear SSH server II from the Play Store, but
the actual install failed throwing an error message about /system
being R(ead)O(nly).
As far as I know /system is not mounted in the custom ROM (freezenook). It seems to
be a regular folder in the loop file system. That's why I don't get the message
about it being read-only.
Furthermore I have a hard time executing ARM binaries on the Archos. I
copied over some binaries to tinker with DVB-T hardware, but I always
get 'permission denied' messages when I try to run them as root in the shell.
I tried to chmod +x them and to put them in places that were not mounted with
the noexec flag. But I didn't succeed.
To cut a long story short:
1. How do I make certain areas of the file system read/write-able in order to
install things such as DropBear SSH server?
2. Do I need to do something special to execute cross compiled binaries?
(I have a gut feeling that it's also connected to the loop file system and mount
set up for the SDE.)
Many thanks in advance,
Kleo2
Not sure my question in subject is clear, so here's the thing...
I have dual-boot tablet with Android 5.0.1 and Windows 10 installed, and the model is Onda V80 Plus (32GB), if that matters at all.
I'm really having hard time rooting this device using standard methods (even with much of background knowledge and experience), so I was about to take a different route.
I installed Paragon ExtFS windows app which gives me read/write access to /system and /data android partitions (which have ext4 filesystem).
I was wondering if anyone knows if it's possible to gain root access in Android just by copying some files and changing some permissions or whatever from within Windows OS?
Basically, for those not familiar with ExtFS app, I can assign a drive letter to /system and /data partitions, and do whatever I want with them just like with any other drive or volume.
I'm aware that modifying ext4 partitions can render my Android OS unbootable, but I have a backup and would like to try it anyway as this is my last option.
When I look into SuperSU.zip file (which I always flashed through CWM/TWRP recovery to gain root access), I see many files which some lengthy script is copying all around, so I stopped after analyzing about hundred lines of code lol.
I really didn't find any method like this on the internet, so I wonder if that's even possible, and if it is, how would I go about it?
Thanks everyone.
Burs said:
Not sure my question in subject is clear, so here's the thing...
I have dual-boot tablet with Android 5.0.1 and Windows 10 installed, and the model is Onda V80 Plus (32GB), if that matters at all.
I'm really having hard time rooting this device using standard methods (even with much of background knowledge and experience), so I was about to take a different route.
I installed Paragon ExtFS windows app which gives me read/write access to /system and /data android partitions (which have ext4 filesystem).
I was wondering if anyone knows if it's possible to gain root access in Android just by copying some files and changing some permissions or whatever from within Windows OS?
Basically, for those not familiar with ExtFS app, I can assign a drive letter to /system and /data partitions, and do whatever I want with them just like with any other drive or volume.
I'm aware that modifying ext4 partitions can render my Android OS unbootable, but I have a backup and would like to try it anyway as this is my last option.
When I look into SuperSU.zip file (which I always flashed through CWM/TWRP recovery to gain root access), I see many files which some lengthy script is copying all around, so I stopped after analyzing about hundred lines of code lol.
I really didn't find any method like this on the internet, so I wonder if that's even possible, and if it is, how would I go about it?
Thanks everyone.
Click to expand...
Click to collapse
Root needs a custom kernel. Not something you are gonna do with a Windows setup the way you have it. Also you will most likely not find anything as that is most likely not an official version of Android as Google doesn't allow dual booting.
Thanks for a reply. But I don't see what does custom kernel have to do with what I try to achieve? If I could, in my Windows environment, replicate the modifications that script inside SuperSU zip does to /system partition, I should gain root access, right? In theory that is, since I'm aware lots of things can go wrong. I was hoping someone could explain a bit what SuperSU script is doing when run inside custom recovery, so I try to do the same thing. Again, if it's possible, and if it's worth the time spent. But I have time, and I'm always willing to learn something new.
Burs said:
Thanks for a reply. But I don't see what does custom kernel have to do with what I try to achieve? If I could, in my Windows environment, replicate the modifications that script inside SuperSU zip does to /system partition, I should gain root access, right? In theory that is, since I'm aware lots of things can go wrong. I was hoping someone could explain a bit what SuperSU script is doing when run inside custom recovery, so I try to do the same thing. Again, if it's possible, and if it's worth the time spent. But I have time, and I'm always willing to learn something new.
Click to expand...
Click to collapse
what su is doing is pulls the kernel and patches it. root access is defined in the kernel. what itnis doing in system is flashimg just the apk
Ok, I see. So if I ask someone who rooted the same model successfully to send me patched kernel, I could easily flash it in fastboot mode (my bootloader is unlocked). So only thing left to do would be to copy apk inside /system/app, and cross my fingers? I'll post my findings if I manage to do something worth writing about. Thanks.
I have same problem with you. I can't root my Onda V80 plus. I unlock bootloader, flash recovery for my device. Then, i put it into recovery mode and install supersu.zip over recovery. When i reboot this onda, it has stopped in onda logo.
bahuy2003 said:
I have same problem with you. I can't root my Onda V80 plus. I unlock bootloader, flash recovery for my device. Then, i put it into recovery mode and install supersu.zip over recovery. When i reboot this onda, it has stopped in onda logo.
Click to expand...
Click to collapse
I managed to root my Onda few days after my last post, but forgot to post my findings, sorry. I didn't used any of my hacker's skills lol, but I researched a bit more and found out what I was missing. The same issue is with you, so you have to disable verity before flashing recovery by typing in these commands:
Code:
adb root
adb remount
adb disable-verity
adb reboot
After rebooting install supersu.zip, and the next boot won't hang on Onda logo anymore. Hope this helps you.
btw, note that not just any adb version has verity command line switch. You have to download newer adb version!
Thank you! I trie a lots times, but i can't make successfully!
Basic root procedure would be: unlock BL -> disable verity -> flash (temp) recovery -> install SuperSU
Here are the links containing all the files neccessary for rooting Onda V80 Plus: Mega | MediaFire
Note the ReadMe.txt inside archive. It contains list of adb/fastboot commands needed to be executed in order to successfully root the device.
Thank you very much! I download your file and root successfully my Onda V80 plus! It works well for me.
Hello,
I recently got a hand on Yuntab K107, ARM MT8752, Android 5.12 Bootloader unlocked. Everything worked fine until factory reset, after that Google play store and other gapps stopped working (play store checking info, then goes black and freezes for a while).
Tablet is rooted from factory by kingroot, I tried finding TWRP/CWM for this tablet to reflash gapps but I failed. I also tried Magic TWRP installer and MTK droid tools. Magic TWRP installer acts like it's working but no results. MTK droid tools refuses to find my device even if i tried every driver possible and cleared wrong drivers with USBDeview.
I also tried flashing gapps manually thru root explorer by unpacking gapps files and matching system file structure also no luck.
Then I backed up the stock recovery and tried flashing few custom TWRP's that some post suggested may work (you guessed it - it didn't work) It just hangs on the first booting screen then it surrenders after a while and reboots back into android.
Do you know about any TWRP/CWM that might work on this tablet or any other way to repair gapps if recovery is not necessary?
Thanks
I also rooted it with kingroot but havnt any custom recovery but i doing some experiment. Let se what it will result
I should be able to compile TWRP for you
I have one of these K107 tablets but it is running Android 7 and so far I have been unable to root it. Because you guys have root you should be able to download adbd Insecure by chainfire and follow this guide to Fetch the boot.img file by Extracting the boot.img directly from the device:
you will first have to determine the (sadly device-specific) path to the storage device where boot.img's content can be retrieved. I know two methods for this:
ls /dev/block/platform/*/by-name/ (where * covers yet another device-specific folder name, chances are it is the only directory below platform/), the exact name to search is also platform dependent but makes usual sense (some examples: boot, LNX (acronym for "Linux")). The files in this directory are actually symbolic links and some people bother to manually go to the target, but I recommend sticking with the higher level name based path which, while longer, remains less error prone. So you will end-up with a path like /dev/block/platform/sdhci-tegra.3/by-name/LNX.
On some (older?) devices, the right device could be found by investigating the output of cat /proc/mtd. If you see the device mtd2 associated to the "boot" label, then you will use the path /dev/mtd2.
Now:
From the phone's developer menu:
Enable debugging on your phone,
Allow root access to ADB (this step applies to phones running CynogenMod, other devices may require some potentially more complex procedure),
Connect it to your computer (and from there to the VM guest if you are running Android tools from within a virtual machine).
If this is not already done, I recommend to manually start the ADB server on the computer's side, this will allow you to directly validate the RSA key on device's side without affecting the behavior of the following ADB commands:
adb start-server
Then switch ADB in root mode:
adb root
Finally, you should be able to directly extract the boot.img file from the device using such command (the source and destination path and names are given as examples, adapt them to your needs and preferences):
adb pull /dev/block/platform/sdhci-tegra.3/by-name/LNX ./boot.img
The command will copy the whole partition, both used and free space, so don't be surprised that the resulting boot.img file will be larger than the original boot.img file coming with the stock ROM .zip file, the content itself remains similar.
Once the transfer is finished, disconnect the phone and don't forget to disable both debugging and root access from the developer menu.
Then upload the boot.img and I will build TWRP and test it on my tablet for you