Related
Hello!
I need help from developers or those familiar with the file structures of the android system.
Let me explain, I have a Chinese touch pad. I tried to install several custom rom (CM9, AOKP, etc ...) as well as Roma manufacturer of tablet very similar to mine (A90 Ampe, Sanei N90, etc ...).
The flash firmware or install via Recovery is done very well. The android starts very well. However, the only problem I have is that my touchscreen is not responding.
Indeed, I have to connect a mouse to use my tablet.
So here the object of my request. I love and I think it is possible created a sort of patch to apply via the recovery or via command ADB with the "drivers" of my touchscreen from my original rom.
For info, I already decompiled the image of my ROM so I have access to the entire file structure. But I do not know enough to identify which files that match the drivers of the screen.
Ya-til someone help me on the files or the place where he could find?
Thank you for your help.
For help, please find attached a complete list of the file structure of the ROM manufacturer.
list HTML
list txt
Help please!
Hello,
I have a Prestigio MultiPad 9.7 PRO tablet that I got for free. The device itself is not bad, but it could do so much more if it had root access. The tablet is not so popular, so there aren't any tutorials on the web. That is why I'm asking for help here.
The device is getting updates via the OTA Service app. It downloads a system.img file onto the SD card, and then it asks me if I want to install it. Now, I'm asking is there some way to "inject" SU and BusyBox into the IMG file, and then install it.
Any help will be grateful.
Hi! :laugh:
I rooted this tablet with a modified rom, you can find it here
(http://dl.dropbox.com/u/17482271/PMP5097CPRO_V1.0.3_20120418.rar)
But it is "only" version 1.03 which is rooted but t works flawlessly. Decomress the .zip file and rename the file to "update.img" and put it directly on your internal sd card of the tablet and restart it. It will ask for an update. You will get a rooted rom v1.03 without loosing any data. When you update to the latest firmware you will loose root. Tried by myself. I also tried to modify v.1.06 and to implement Superuser & Co but without success. I am a totally noob in linux .
http://forum.xda-developers.com/showthread.php?t=1796067
The link to official roms from Prestigio: http://yf.value4it.com/Service_Files/TabletPC/PMP5097CPRO/
Best regards from Germany
Dummy guide
Hi all,
Yes its me the lazy one ha not really i work hard at other stuff
I need a complete dummy guide on upgrading and rooting a pretigio multipad 5097CPRO I have been asked to do this for a friend whos sole purpose of getting this done is to be able to download a 4OD app to play for his kids,
I never use these tablets however i am a linux sys admin and fairly computer literate so i can be thought
Any takers on this one
Cheers,
James
Hi all,
I am working in a school and we have ordered some tables for students to use. The problem I am faced with is that the systems needs to be very secure (the students can't change settings, install/uninstall apps) and i need to be able to apply the restrictions and software to many tablets with relative ease or to apply it to them simultaneously.
Sumvision provides software to flash an image to the tablet and will flash multiple tablets at once (8 if i remember correctly). It would be very handy if I could easily create my own image with a few apps and things configured so it can flash the tablet ready to use, however i have never created a ROM before and am inexperienced in programming.
Another option is to set up one tablet and use CWM to backup/restore to all the other devices, however I am unable to find any way of doing this, or any actual recovery.img files to download for this model. Does anyone know of any?
Any help would be appreciated, as at the moment my plan is to upgrade the tablets 8(?) at a time to 4.2.2 and use titanium backup to restore apps and settings to each tablet.
The tablets are Sumvision Cyclone Voyager 10.1" BT tablets.
Thanks in advanced,
tylergard702
CWM recovery for Sumvision Cyclone Voyager BT
tylergard702 said:
Hi all,
Another option is to set up one tablet and use CWM to backup/restore to all the other devices, however I am unable to find any way of doing this, or any actual recovery.img files to download for this model. Does anyone know of any?
tylergard702
Click to expand...
Click to collapse
Disclaimer: The following worked for me. Any one else is trying it at there own risk.
Here are roughly edited notes on how I got ClockworkMod recovery onto Sumvison Cyclone Voyager BT (Bluetooth edition)
Hope it's helpful, it comes from bits and pieces of other folks work found on the net, to all of whom I'm grateful.
After you go through this process on all tablets you could make a NAND backup, of a tablet suitably set-up for your own requirements, to micro-SD card and flash it to all remaining tablets
Getting into Recovery Mode
From a terminal program in fully booted system
#su#reboot recovery
or from Power Off
From Power OFF (NO Cables Connected)
Hold Vol+ while plugging in Power, release Vol+ when splash screen appears
How I installed CWM-based Recovery for Rockchip Sumvison Cyclone Voyager BT
Recovery image used was:
RECOVERY Image for v10_BT_recovery_fun_13-02-13.rar (Google it)
(Generic rockchip recovery image from CWM.zip did not work, but I used the flash_image utility from that archive. Again search Google for CWM recovery images for rockchip 3066)
In XP with tablet fully booted and power and USB cable plugged in (don’t know if power in required, as far as I remember adb driver is fine without power, but no harm to have it plugged in. When flashing firmware from SCV's rockchip software utilities power must be plugged in. Also if you have the choice, prefer USB2 over USB3, although unlikely to make a difference. (Note: since got adb working on Ubuntu Linux also, but that's another story )
1. Extracted flash_image from CWM.zip
2. Extracted recovery.img from v10_BT_recovery_fun_13-02-13.rar
3. Copied both files to /dev on tablet
adb push flash_image /dev/ adb push recovery.img /dev/4. Started shell
adb shell5.Set flash_image utility executable
chmod 755 /dev/flash_image6. Flashed the recovery.img
/dev/flash_image recovery /dev/recovery.img
Hope that helps
Thanks
Ah, thank you
This has quite possibly saved me hours of time reformatting the tablets. I take it that this can be installed relentless of the ROM that is on the tablet? I will try this as soon as the tablets arrive
Thanks again,
tylergard702
PS:
I don't suppose that sumvision's flash utility will flash the recovery.img to the tablet successfully? I currently don't have a linux workstation at work, and adb confuses me :S
Recovery Img?
Thankyou for all of you help John,
Ignore my previous post, i dived in with adb and got quite well acquainted with it
The only problem i have now is that the rar file for the recovery .img you told me to Google for yields no results. Is there another place i can download it? i can't find any :S.
Or if you have a copy of it would you be able to email it to me? (I can PM you my email)
Thanks in advanced,
tylergard702
Flashing recovery image with RK tools
tylergard702 said:
Ah, thank you
I don't suppose that sumvision's flash utility will flash the recovery.img to the tablet successfully? I currently don't have a linux workstation at work, and adb confuses me :S
Click to expand...
Click to collapse
Disclaimer: things can go wrong. You are responsible for whatever you do to your tablet!
I think that the rockchip tools should flash the recovery image for you, I haven't used the Sumvision utility in a while so don't know. The rockchip tools will provide you with a Windows user interface. Make sure you only flash recovery, and leave the rest unmarked. Put the recovery image in the same directory where the tool executable resides (or it may need to be in a sub-folder named ROM). I think the app will tell what path it is looking at for images.
Download from the Sumvision support page (I'm not allowed to post links yet, but find your tablet on Sumvision and go to support page)
Look for: Download Link for RKAndroid tool "cleanup tool" REQUIRED on that page.
Good luck!
---------- Post added at 11:40 AM ---------- Previous post was at 11:29 AM ----------
tylergard702 said:
Or if you have a copy of it would you be able to email it to me? (I can PM you my email)
tylergard702
Click to expand...
Click to collapse
Okay, PM your email and I'll send you a dropbox link to the recovery image previously mentioned.
(I discovered that the CWM recovery for generic rk3066 that didn't work for me, was an incomplete download and likely the reason it didn't work for me. I haven't retried it because the v10_BT_recovery_fun_13-02-13 recovery image works fine, so just left that alone).
Worked a treat
Thank you very much John,
The fun_ package worked perfectly.
The generic package lead to a broken recovery, it wasn't just your download, however the specific package soon fixed that.
Can't tell you how much easier you have made my work, i can now prepare about 4 tablets in 30 minutes for the students to use, which will come in very handy when they get their hands on them and start to find ways around our security measures.
Thanks for everything,
tylergard702
John Hoyne said:
Disclaimer: things can go wrong. You are responsible for whatever you do to your tablet!
I think that the rockchip tools should flash the recovery image for you, I haven't used the Sumvision utility in a while so don't know. The rockchip tools will provide you with a Windows user interface. Make sure you only flash recovery, and leave the rest unmarked. Put the recovery image in the same directory where the tool executable resides (or it may need to be in a sub-folder named ROM). I think the app will tell what path it is looking at for images.
Download from the Sumvision support page (I'm not allowed to post links yet, but find your tablet on Sumvision and go to support page)
Look for: Download Link for RKAndroid tool "cleanup tool" REQUIRED on that page.
Good luck!
---------- Post added at 11:40 AM ---------- Previous post was at 11:29 AM ----------
cheers.
Okay, PM your email and I'll send you a dropbox link to the recovery image previously mentioned.
(I discovered that the CWM recovery for generic rk3066 that didn't work for me, was an incomplete download and likely the reason it didn't work for me. I haven't retried it because the v10_BT_recovery_fun_13-02-13 recovery image works fine, so just left that alone).
Click to expand...
Click to collapse
Any chance i can have a copy of that file to flash recovery to my 10.1 BT?
Sumvision Cyclone Voyager 10.1 BT Recovery Image
jtheg said:
Any chance i can have a copy of that file to flash recovery to my 10.1 BT?
Click to expand...
Click to collapse
Hey jtheg,
Of course I can If you PM me your email I will send you a zip containing the flash_image file, the recovery10.img file (I renamed it for batch purpose, but it works all the same). The zip also contains adb and a batch script I wrote that should do it for you. If you don't want to use the script, you can refer to the instructions above or ask for help
Just make sure all the drivers for your tablet are installed before you start.
I used a program called "moborobo" It detects the device and installs all the drivers for you. It installs junk on your device but you can uninstall it right after
I would also like to point out that although this has worked for me with 16 of these tablets, It may not work for you due to subtle differences between the tablets or human error, and I cannot accept liability for your device. I can, however, say it has worked treat for me and wish you the best of luck experimenting with your device As soon as I get to work in about 20~30 minutes I'll check back and email you if I can
all cwm for cylone voyager can be found on the flashmyandroid forum
Q&A for Intel Android Devices Root / Temp CWM Session
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Intel Android Devices Root / Temp CWM Session. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Will this root method work with ASUS devices?
The thread title (Intel Android Devices Root / Temp CWM Session) suggests this is a generic rooting method for tablets with Intel SoCs. Is there any reason why this shouldn't work with the newer Intel Atom-based Asus tablets such as the MeMO Pad ME176CX? The current and as far as I know, only rooting method, for the ME176X uses an app called RootZenPhone.
RootZenPhone appears to use the same exploit as your script-based root method, but wraps it up in a APK with obfuscated asset names. (Note: I ran clamscan on both the APK and your files, and both tested positive for the exploit). I prefer your method because it has a cleaner, more opensource design. I can basically read what it's going to do, at least up to the point where you run the exploit.
usenametaken said:
The thread title (Intel Android Devices Root / Temp CWM Session) suggests this is a generic rooting method for tablets with Intel SoCs. Is there any reason why this shouldn't work with the newer Intel Atom-based Asus tablets such as the MeMO Pad ME176CX? The current and as far as I know, only rooting method, for the ME176X uses an app called RootZenPhone.
RootZenPhone appears to use the same exploit as your script-based root method, but wraps it up in a APK with obfuscated asset names. (Note: I ran clamscan on both the APK and your files, and both tested positive for the exploit). I prefer your method because it has a cleaner, more opensource design. I can basically read what it's going to do, at least up to the point where you run the exploit.
Click to expand...
Click to collapse
It should work I've tested it on Medfield, Clovertrail, and Baytrail devices, from the Asus fastboot.imgs I've looked at trigger 2 and 3 should work.
the apk you refer to i believe actually uses a function Asus only seems to of built into thier droidboot binary on the Asus when you start droidboot it looks at /factory for a file called .addon and then triggers it Asus uses it for automating things under droidboot I believe and several recoverys have been built to take advantage of it.
As for the exploit the exploit is the the script the binarys are nothing really special just responsible for setting up and starting the recovery session. recovery.trigger is a simple daemon to launch recovery.launcher and recovery.launcher is basically a small subset of cwm recovery its self.
Sent from my XT907 using XDA Free mobile app
Hi,
this worked on an odys intellitab 7, now i got finnaly root . BIG THX!
Btw I trird trigger 2 and 3 and both worked for me
How can i see if the bootloader is locked on my device?
Another possible device
Hello,
in Czech forum where I compiled a native-language short guide how to use your tethered CWM recovery to root Op3n Dott (I see that somebody confirmed that both T2 and T3 triggers work] one Slovak user reported that he was able to use the tool to root Prestigio MultiPad Thunder 7.0i http://www.prestigio.sk/catalogue/M...NDER_7.0i#/product-specs?article=PMT3377_WI_C. I sent him a question concerning which trigger did he use so if he replies I will send more info. Sorry for the Q&A thread, but I got kicked here because of the low post count.
Succesfully rooted Tesla L7 Tablet
Using the method described successfully rooted Tesla L7 tablet. The method used is T3 and supersu used is UPDATE-SuperSU-v2.40
Is the recovery built from source?
Hello, one more question - is the recovery built from source by you, or is it a ready-made recovery from someone else? Because if you have your own tree an are building it from scratch, it might be possible to include the call of my tool used for dumping images (dump_images from merrifield_bin of dell-venue-boot-tools for signed images and possibly a renamed one from zte_gxi_boot_tools for unsigned images) to /sbin/nandroid-md5.sh script and add the tool(s) to /sbin. I know it is not the best solution but at least it would be possible to backup the images if not restore them from CWM.
pm-cz said:
Hello, one more question - is the recovery built from source by you, or is it a ready-made recovery from someone else? Because if you have your own tree an are building it from scratch, it might be possible to include the call of my tool used for dumping images (dump_images from merrifield_bin of dell-venue-boot-tools for signed images and possibly a renamed one from zte_gxi_boot_tools for unsigned images) to /sbin/nandroid-md5.sh script and add the tool(s) to /sbin. I know it is not the best solution but at least it would be possible to backup the images if not restore them from CWM.
Click to expand...
Click to collapse
The actual recovery is built by @vampirefo but i am very interested in adding that feature in and was actually going to ask you about that.
Also have you looked at any of the older update_osip source?
Can you please tell me an easier to understand method.
Because even though i understand what you're talking about, i don't know where to put the files. I understand flashing the session and all but coukd you pleeease explain how to root. Because this the first time i'm rooting a device
Thanks
rooting without voiding warranty
Can you please tell me how to root my dwll venue 8 3830 without voiding the warranty?
Yay, i rooted my tab Dell Venue 7340!
But when i'd like to install some optimization script like: http://forum.xda-developers.com/android/software-hacking/mod-projct-mod-boost-nitro-x-edition-t2809443 recovery (cwm) said error 255... there is any chance to install this?
Getting Windows 7/8 to Recognize Dell Venue 3740
Fajfie said:
Yay, i rooted my tab Dell Venue 7340!
But when i'd like to install some optimization script like: http://forum.xda-developers.com/and...mod-projct-mod-boost-nitro-x-edition-t2809443 recovery (cwm) said error 255... there is any chance to install this?
Click to expand...
Click to collapse
Thanks to Social Design Concepts for the great work. It is appreciated!
Fajfie, thanks for posting. That's awesome. If you used Windows, how did you get Device Manager to identify the Dell Venue 3740? I've downloaded all recommended driver files in this and the previous thread and I can't get Windows to identify the device. When I run launcher.bat I get DEVICE: UNKNOWN.
Any ideas?
Another rooted
Great work, this worked to gain root on Medion (Lenovo) Lifetab S10346 tablet.
Intel Z3735F cpu
2GB ram, 32 GB storage.
I used trigger T3 and it went through smoothly, a Great bit of work.
Works perfectly on the Asus Padfone X Mini. I referenced this thread over in the device specific forum. I used the T3 command in step 3.
Thanks!!!
Worked on my ASUS Padfone X mini (TOOS) used T3 option.
Thanks!
Thanks you. The procedure works with method 3 to GoClever Insignia 700 PRO , Android 4.4.2.
I just installed IntelAndroidDrvSetup 1.5.0 with the drivers for my pc.
hi im having the same problem as GeeKerGurL
" Try to manually boot to droidboot
Anyways... everything was going ok, I selected trigger 3 to try first, reboots to droidboot (with "waiting for fastboot command") then I select recovery and get android dude laying down with a red exclamation point coming out his belly and it just said "no command" now I am soft bricked, only getting the USB symbal with the white line under it. Please help! "
i have a Acer Iconia A1830
Problems with the update surpeuser zip
I followed your guide to rooting Acer iconia tab 8 A1-840FHD with intel chip, (Wich is great by the way thanks) and evrything goes to plan until, i get to Install Zip. I get, E:Can't mount /sdcard/ Update-superSu-v2.40(1).zip Installation aborted. I've downloaded the zip from your link by desk top (windows 7) and transferred it over. Also downloaded from the tablet and just used a file manager to move it over to sd. Same msg for each. I used the T3 option. any ideas how to get the zip to install?
Zip copy to folder on your tablet (download,...) and install from recovery install. zip.
Send from my Samsung Galaxy S2 - RR Lollipop v. 5.2.7
Verified with Acer Iconia A1-830
Firstly, big thanks to the dev, social-design-concepts for making this thing work on Intel device. Thumb up~
It works wonders with my Acer Iconia A1-830 android 4.4.2.
I used option T1 and it works without any problem.
Thanks again.
P/s: Hope this will work on the latest Intel devices like Asus Zenfone 2 ;p
Hello there,
I'm wondering if there's anyone knowledgeable to point me in the right direction. Coronavirus (or I) messed up the build.prop file in a Chinese-made JTY-K107 (MT6580 architecture) tablet and now stuck in a soft-brick state. I cannot use adb push or adb sideload (doesn't detect device probably because I had attached another MT device, a Huawei on the PC before and that is the device I pulled the build.prop from to mess with the bigger tablet and now all seems jumbled driver-wise on my Win 10). In any case, I am able to copy to the SD card an update.zip but factory recovery installation is not possible ("installation aborted" - signing issue?). I tried these two zips inside which the original build.prop files are now nestled. It's maybe the commands/scripts that are at fault or it's some signing issue (that hopefully can be tackled). I don't know. I am very reluctant to think about flashing ROMs at this stage. (Porting MT-architecture ROMs are not exactly easy or risk-free, from what I have seen around other threads/forums.)
The link to the folder with the non-working update zips I pulled from other sites or threads (not knowing how I should go about building these files from scratch on my own):
https://app.box.com/s/7byabibx2j0jfo2zlgmg0oi0ca66vkyn
Thanks very much for any info (or possibly a fix of the zips to make it compatible with MT6580 to install the update).
Cheers,
Zoltán
@zanodor
IMHO a simple factory reset may solve your problems.
jwoegerbauer said:
@zanodor
IMHO a simple factory reset may solve your problems.
Click to expand...
Click to collapse
Today I was thinking, people like overcomplicating things: there must be some easy solution. I actually had done that out of frustration (knowing that I had a Titanium Backup on SD) but the boot issue persists (I tried again but all I see is the Android logo for minutes now).
I thought maybe there was a way to repackage my full Titanium Backup into a zip that could be used in Factory Recovery for a restore solution? I perused the net in vain for that too.
I really don't fancy reinstalling Win 10 to fix the driver issues or trying on one of my Linux machines (I am a noob on those too).
Thanks for the answer, anyway.
In the end I managed to restore the tablet (took me 2-3 days of looking around). I'm only writing this up so others facing adb probs can solve their issues on their MTK-built devices. (Actually probably this will work on any device that is not Samsung or whatever old famous brands.)
The first thing to do was sorting out VCOM drivers. There's a Nigerian-sounding guy whose forum Hovatek I followed for tricks on how to go about it (had to download and install Virtual Serial Port Driver to sort out connection issues in Miracle Box/Thunder). Whenever you have some problem, I suggest you include Hovatek in the search string, cause chances are he has a tool and a tut.
Using Miracle Thunder and acting on Hovatek's instructions I made a copy of my firmware. All I really needed was the sytem.img, of course. My bootloader being fine (messing up your device with build.prop only results in a soft brick), it didn't need fixing. Using Assayyed's Kitchen and Hovatek's tutorial again I unpacked the system.bin I extracted with Miracle (which must be all the time used with virus protection off) after renaming system.bin to sytem.img. I exchanged the build.prop and repacked system but didn't wait for the update.zip to be made, instead I took the img file I wanted in the Kitchen. Then tried SP Flash tool to flash system.img on the device but I had issues with the scatter file. So I downloaded a firmware from Boycracked or whoever and used that scatter (in the meantime I overwrote the system.img with mine). I flashed device, turned on the tablet and voila. I hope this helps peeps out there with similar issues.