CWM backup to .Img - Miscellaneous Android Development

Hi all,
I'm looking for tool or idea how to transfer CWM backup to image.
I formatted my unknown china tablet rk3188 and I have no access to CWM recovery.I can flash via RKAndroidTool if I have image file.
Please help.

styropian said:
Hi all,
I'm looking for tool or idea how to transfer CWM backup to image.
I formatted my unknown china tablet rk3188 and I have no access to CWM recovery.I can flash via RKAndroidTool if I have image file.
Please help.
Click to expand...
Click to collapse
UPDATE ___
RK3188 adb is running no screen__help PLEASE
After erasing IDB in my unknown china tablet and loosing my whole system I was able to load different custom firmware from Chuwi v88 + different kernel and my Tab popup in windows showing 2 extra drives F and G.I did open android studio and notice access to adb and all activity in my android.The RKandroidTool also recognizing my tab.
No reaction to power button only automatically connecting to my comp ( black screen on my tab).
I have original CWM backup of my device.
Can someone advise me how to access recovery from this point or find the way to completely start my tablet.Maybe is possible to recover CWM from adb?I will need some help to use a proper commands perhaps in adb.

Related

Cannot get to flash on Ployer Momo2

I have a Ployer Momo2 Android 2.1 and I would like to flash it to 2.3.
I managed to download the upgrade package from the oem ployer website, and got the program RKandroidtool v1.29 to execute. It only manage to detect the tablet in mass storage mode even I tried many ways to get it to boot into loader USB mode
There are only three buttons on the tablet, power, menu and esc. I'm running on Win 7 64-bit ultimate. The OS detect the device without any additional installation.
I have been googling around and this post is my only hope now. Anyone out there manage to get the tablet booting up in loader mode ?
I tried copying the file update.img to the root drive of the internal memory. After powering up, the device detect the image file but complains that it is an invalid image file and asked me to delete it.

[Q] Bassoon 7" dual sim .zip SDcard recovery rom needed or USB driver for flashtool

[Q] Bassoon 7" dual sim .zip SDcard recovery rom needed or USB driver for flashtool
Ls,
I'm trying to help a friend who deleted too many files from his Bassoon 7"dual sim tablet.
Now it fails to make calls and keeps saying that: "unfortunately, the system laucher has stopped".
I have no idea what he deleted (after I adviced him to install SU so he could move apps to the SDcard, so i feel responsible)
So im trying to reinstall the entire thing.
Factory reset doesnt help.
On needrom.com I found some jxd p1000 roms that might work(apparently the bassoon 7"is a jxd p1000 clone)
I have found several roms on needrom.com that might apply.
There's only 1 .zip rom that will attempt to install from SDcard. It starts but fails after a while because its the wrong ROM prob. It has android 4.1.1 and the tablet says 4.2.2.
The other roms require the flashtool.
I tried all possible flashtool that were adviced on this, and other, forums.
The problem is that the flashtools dont seem to recognize the device, neither does adb.exe.
I can use sideload but dont have the right .zip file for it. I can also copy it to the sdcard and use; recovery boot and install from SDcard but again, i dont have the right .zip ROM for that.
WIndows recognizes and is able to acess the device as a USB or as a m72_nand_p88 device.
I have installed the MTP-65xx usb drivers. some HTC usb drivers (windows reported the device as a HTC desire at some point) and the ADB usb drivers(windows reports the device as a ADB usb device if connected in recovery mode)
Questions(calls for help );
- Is there a USB driver that I haven't found that will enable me to use the flashtools so I can try the other ROMS from needrom.com
and/or
- Is there a way to convert the .rar ROMS that use the scatterfile to a .zip that i can use in reboot recovery from SDcard or use ADB sideload
and/or
:cyclops: :silly: im going crazy here....
Recap:
- I cant connect to the device with the flashtool
- I do not have the rom in a .zip that I can use in recovery from SDcard :silly:
- I do not know how, or if its possible to, convert the scatterfile/flashtool roms to a format (.zip) that I can use with recovery from SDcard or sideload (the scatterfile .rar roms are about 170Mb the .zips are about 400+ Mb so eitehr they are pre-unpacked-installed...?)
- I seriously have no idea what to do next..
Device:
samsung p1000 look alike clone; it has dual sim, 7 inch display, says bassoon on the back.
android 4.2.2
baseband: MOLY.WR8.W1315.MD.WG.MP.V8
Kernel: 3.4.5 [email protected]#1
Build: ALPS.JB3.MP.V1.12
Custom build V023
Any and all help is much appreciated!
Highest regards,
Mac
MacShrike said:
Ls,
I'm trying to help a friend who deleted too many files from his Bassoon 7"dual sim tablet.
Now it fails to make calls and keeps saying that: "unfortunately, the system laucher has stopped".
I have no idea what he deleted (after I adviced him to install SU so he could move apps to the SDcard, so i feel responsible)
So im trying to reinstall the entire thing.
Factory reset doesnt help.
On needrom.com I found some jxd p1000 roms that might work(apparently the bassoon 7"is a jxd p1000 clone)
I have found several roms on needrom.com that might apply.
There's only 1 .zip rom that will attempt to install from SDcard. It starts but fails after a while because its the wrong ROM prob. It has android 4.1.1 and the tablet says 4.2.2.
The other roms require the flashtool.
I tried all possible flashtool that were adviced on this, and other, forums.
The problem is that the flashtools dont seem to recognize the device, neither does adb.exe.
I can use sideload but dont have the right .zip file for it. I can also copy it to the sdcard and use; recovery boot and install from SDcard but again, i dont have the right .zip ROM for that.
WIndows recognizes and is able to acess the device as a USB or as a m72_nand_p88 device.
I have installed the MTP-65xx usb drivers. some HTC usb drivers (windows reported the device as a HTC desire at some point) and the ADB usb drivers(windows reports the device as a ADB usb device if connected in recovery mode)
Questions(calls for help );
- Is there a USB driver that I haven't found that will enable me to use the flashtools so I can try the other ROMS from needrom.com
and/or
- Is there a way to convert the .rar ROMS that use the scatterfile to a .zip that i can use in reboot recovery from SDcard or use ADB sideload
and/or
:cyclops: :silly: im going crazy here....
Recap:
- I cant connect to the device with the flashtool
- I do not have the rom in a .zip that I can use in recovery from SDcard :silly:
- I do not know how, or if its possible to, convert the scatterfile/flashtool roms to a format (.zip) that I can use with recovery from SDcard or sideload (the scatterfile .rar roms are about 170Mb the .zips are about 400+ Mb so eitehr they are pre-unpacked-installed...?)
- I seriously have no idea what to do next..
Device:
samsung p1000 look alike clone; it has dual sim, 7 inch display, says bassoon on the back.
android 4.2.2
baseband: MOLY.WR8.W1315.MD.WG.MP.V8
Kernel: 3.4.5 [email protected]#1
Build: ALPS.JB3.MP.V1.12
Custom build V023
Any and all help is much appreciated!
Highest regards,
Mac
Click to expand...
Click to collapse
Greetings Mac,
I have a similar problem with same tablet but I was able to fine the direct download site for Bassoon. It's in Chinese but you can figure it out. Scroll to the model and version (version # under 2nd battery i.e. 061) as well as the , click on link and on the page there is a down arrow and horizontal bracket on button on top to download. "SP_Flash_Tool". I am currently downloading the rom for my device but will post results.
Here's the link: http://pan.baidu.com/share/home?uk=2285182452&view=share#category/type=0
Good Luck!
bassoon stock roms with flash tool
MacShrike said:
Ls,
I'm trying to help a friend who deleted too many files from his Bassoon 7"dual sim tablet.
Now it fails to make calls and keeps saying that: "unfortunately, the system laucher has stopped".
I have no idea what he deleted (after I adviced him to install SU so he could move apps to the SDcard, so i feel responsible)
So im trying to reinstall the entire thing.
Factory reset doesnt help.
On needrom.com I found some jxd p1000 roms that might work(apparently the bassoon 7"is a jxd p1000 clone)
I have found several roms on needrom.com that might apply.
There's only 1 .zip rom that will attempt to install from SDcard. It starts but fails after a while because its the wrong ROM prob. It has android 4.1.1 and the tablet says 4.2.2.
The other roms require the flashtool.
I tried all possible flashtool that were adviced on this, and other, forums.
The problem is that the flashtools dont seem to recognize the device, neither does adb.exe.
I can use sideload but dont have the right .zip file for it. I can also copy it to the sdcard and use; recovery boot and install from SDcard but again, i dont have the right .zip ROM for that.
WIndows recognizes and is able to acess the device as a USB or as a m72_nand_p88 device.
I have installed the MTP-65xx usb drivers. some HTC usb drivers (windows reported the device as a HTC desire at some point) and the ADB usb drivers(windows reports the device as a ADB usb device if connected in recovery mode)
Questions(calls for help );
- Is there a USB driver that I haven't found that will enable me to use the flashtools so I can try the other ROMS from needrom.com
and/or
- Is there a way to convert the .rar ROMS that use the scatterfile to a .zip that i can use in reboot recovery from SDcard or use ADB sideload
and/or
:cyclops: :silly: im going crazy here....
Recap:
- I cant connect to the device with the flashtool
- I do not have the rom in a .zip that I can use in recovery from SDcard :silly:
- I do not know how, or if its possible to, convert the scatterfile/flashtool roms to a format (.zip) that I can use with recovery from SDcard or sideload (the scatterfile .rar roms are about 170Mb the .zips are about 400+ Mb so eitehr they are pre-unpacked-installed...?)
- I seriously have no idea what to do next..
Device:
samsung p1000 look alike clone; it has dual sim, 7 inch display, says bassoon on the back.
android 4.2.2
baseband: MOLY.WR8.W1315.MD.WG.MP.V8
Kernel: 3.4.5 [email protected]#1
Build: ALPS.JB3.MP.V1.12
Custom build V023
Any and all help is much appreciated!
Highest regards,
Mac
Click to expand...
Click to collapse
this is the link where you can download the stock rom for basoon phablets https://androidmtk.com/download-bassoon-stock-rom-models
they have some bugs like wifi nvram warning, no working gps, gravity, and compas
and one very very annooing chinese app that constandly sends you app announcements that you can install if you delete it than youre contacts and phone functions will not work
maybe you can fix those things
greetings flappie311

[Q] Problem with META MODE and custom recovery

I have a Lenovo A536. My problem ISN'T device specific.
I installed a custom rom and after some time it started appearing this message "System UI has stopped working".
I downloaded the original rom to flash it.
I got into TWRP and first formated my internal sdcard. The problem is that I forgot to transfer the IMG to the external sdcard. Now it doesn't have anything to boot and also I can't get in TWRP again. I also can't get in fastboot. My only solution is to do it through META MODE. I have read that I need a special cable that fits in the headphone hole.
Can you tell me:
1. How is this cable called? (in order to buy it)
2. What programs do i need to use from the computer in order to execute commands in meta mode
3. What commands i need in order to transfer the official image to my phone and/or flash it.
Any answer is acceptible

Lenovo Tab3-710f custom recovery?

We are trying to get hold a custom recovery for Lenovo Tab3-710F. We are using hundreds of Lenovo tablets in our projects and have up until now used Tab2 A7-10 which has a custom recovery build for it (found here att XDA).
The reason we need the custom recovery is for cloning the unit which works good in CWM or TWRP.
The problem now is that Lenovo have stopped selling Tab2 so we are now stuck with a unit we cant clone.
Have somebody successfully created a custom recovery for the unit? If not or if you have we are offering payments/devices to get this working asap. Are you interested please PM us? When we have it we can share it to the world here no problems for us.
If you need to root the device KingoRoot latest APK works.
So hope somebody can help us.
Perhaps useful for you: I've managed to extract the stock rom of a brand new TB3-710F
http://forum.xda-developers.com/android/help/lenovo-tab-3-7-essential-tb3-710f-mt8127-t3416397
This also includes the "recovery.img" so you could try to change this image and simply flashing it. If it does not work you'll have a stock rom to restore it.
gogetrd said:
We are trying to get hold a custom recovery for Lenovo Tab3-710F. We are using hundreds of Lenovo tablets in our projects and have up until now used Tab2 A7-10 which has a custom recovery build for it (found here att XDA).
The reason we need the custom recovery is for cloning the unit which works good in CWM or TWRP.
The problem now is that Lenovo have stopped selling Tab2 so we are now stuck with a unit we cant clone.
Have somebody successfully created a custom recovery for the unit? If not or if you have we are offering payments/devices to get this working asap. Are you interested please PM us? When we have it we can share it to the world here no problems for us.
If you need to root the device KingoRoot latest APK works.
So hope somebody can help us.
Click to expand...
Click to collapse
Did u manage to get TWRP or CWM for TB3-710F ?
zwirc said:
Did u manage to get TWRP or CWM for TB3-710F ?
Click to expand...
Click to collapse
Yes, I built it for them. Download here
@Tzul @gogetrd We are trying to achieve something similar, configure about 700 tablets of this model. I have played with custom ROMs in the past, but mostly as a consumer (e.g. Cyanogen on personal devices).
It is my understanding that installation using the files provided by @Tzul would require to;
0. create a custom ROM.
Then for each device
1. root device (e.g. Developper mode, allow "Unknown source"s, adb install one rooting apk, run it, etc).
2. install custom recovery on device
3. flash custom ROM
Am I right?
If so do we agree that the time spent doing these operations might be about similar than the time spent e.g. manually installing / configuring the device? Or is there a way to automate the steps above?
You can configure 1 tablet, then extract the ROM and flash it with the "download mode". You don't even need to boot the tablet!
If you want more info let me know, back from holiday in a few days
@lacostej You can certainly automate some steps, and you do not always need root. (And the best way to root is to install the latest SuperSU via TWRP; no need for questionable apps that are doing who knows what...)
There are three ways to install another firmware:
The MediaTek SmartPhone Flash Tool (SPFT). This is a PC program (Windows and Linux) that allows reading and writing of the entire internal storage (on a partition granularity). Via USB, while the device is powered down. Only for devices based on MediaTek chips, of course (this tablet is MediaTek-based).
Fastboot. This is a little USB protocol implemented by the bootloader. A Fastboot client on PC can communicate with the bootloader via USB and execute certain commands, e.g. "fastboot flash" for flashing partitions. However, there are a few drawbacks with this:
First, you need to boot the device into fastboot mode. Some devices have a boot menu that allows you to do this, but this device doesn't. Starting the tablet via power+volumeUP takes you directly to the recovery instead of a boot menu. But in the recovery, whether stock or TWRP, there's a reboot to bootloader option. Using ADB (adb reboot bootloader) should also take you there.
Second, the "fastboot flash" command is restricted on this tablet. If you were to use "fastboot flash recovery <recoveryfilename_here>", for example, it would abort with an error message. I have patched the bootloader to allow the flash command, but you'd first need to install this patched version on your tablet(s), of course, via SPFT or other means.
Third, the "fastboot flash" command has a size limit - the bootloader needs to buffer the USB data in RAM before it can be written, and since the tablet has only 1 GB of RAM, you obviously can't flash a 1 GB system image this way. The buffer is actually a lot smaller: just 128 MiB. Meaning whatever file you send to the tablet via "fastboot flash", it cannot be larger than 128 MiB. So, how do you flash the system or userdata partition then, which are much, much larger? By splitting their image file into many smaller "sparse" image files, each of which is below the size limit. There's probably a tool for doing this, but I don't know any details.
TWRP, or another custom recovery. They allow you to create and restore backups. TWRP has some automation support via OpenRecoveryScript.
So, if you have 700 tablets to configure, you can configure just one, then save its state via SPFT or TWRP, then restore that on each other tablet.
What is its "state"? Well, the system, cache, and data partitions. The system partition is normally read-only and won't change, therefore you do not need to clone it. Unless you install root and modify stuff on the system partition, of course. The cache partition is quite irrelevant. It is the data partition that has all the app settings.
However, if you clone the data partition from one tablet to others, then you're causing each tablet to use the same Android ID (a long number identifying an Android device, usually randomly generated when Android is first booted after a factory reset), the same Bluetooth and WiFi MAC addresses, and some other IDs that should be unique on each device (the tablet's Lenovo serial number might be in some cloned files as well, e.g. the WiFi settings).
You can at least avoid cloning the MAC addresses by deleting the entire directory /data/nvram/ before you create your backup. MediaTek devices have a dedicated NVRAM partition that contains the MAC addresses and some other stuff, and this data gets unpacked to /data/nvram/ when Android boots. Unless the files there already exist. So, by deleting /data/nvram/ before you clone, you force each tablet to extract its unique MAC addresses again at the next boot...
Thanks a lot for the feedback. Really appreciated.
Tzul said:
@lacostej And the best way to root is to install the latest SuperSU via TWRP; no need for questionable apps that are doing who knows what...
Click to expand...
Click to collapse
Doesn't SuperSU already requires root? (http://forum.xda-developers.com/showthread.php?t=1538053)
How did you get root on your Lenovo device? (I assume you had one to dump the image)
However, if you clone the data partition from one tablet to others, then you're causing each tablet to use the same Android ID (a long number identifying an Android device, usually randomly generated when Android is first booted after a factory reset), the same Bluetooth and WiFi MAC addresses, and some other IDs that should be unique on each device (the tablet's Lenovo serial number might be in some cloned files as well, e.g. the WiFi settings).
.
Click to expand...
Click to collapse
That's exactly the thing I was worried about when it comes to cloning. Those problems might arise later during QA, and I probably don't have the time required to do it properly this time.
lacostej said:
Doesn't SuperSU already requires root? (http://forum.xda-developers.com/showthread.php?t=1538053)
How did you get root on your Lenovo device? (I assume you had one to dump the image)
Click to expand...
Click to collapse
SuperSU is just like any other root manager. It provides the actual "su" (superuser) binary that other programs rely on to obtain root privileges, plus an Android app for managing permissions and settings. The su binary needs to be installed on the system partition (at least traditionally), but in order to get write access there, you need root privileges. Therefore, this is a chicken and egg problem: SuperSU provides root, but it also needs root in order to be installed. Other root manager are no different - except that some try to exploit security flaws in Android in order to temporarily obtain root and install their su binary.
Anyway, the classic solution to this conundrum is the (custom) recovery: it basically has root built-in. It can write to the system partition by default, after all one of its jobs is to install firmware updates.
TWRP includes a SuperSU stub. If you leave TWRP via the Reboot menu, it checks whether or not the su binary is installed (at least in Android 4 and 5), and if it isn't, it asks if you'd like to install the SuperSU stub. Which you can then use in Android to update to the latest SuperSU via Play Store. But you can also install SuperSU's latest "update zip" in TWRP to immediately install the full version.
lacostej said:
That's exactly the thing I was worried about when it comes to cloning. Those problems might arise later during QA, and I probably don't have the time required to do it properly this time.
Click to expand...
Click to collapse
Yeah, it is annoying. MediaTek apparently wisened up a bit. Newer platforms they produce do not unpack the NVRAM partition to the data partition anymore. Instead, they use a dedicated "nvdata" partition for that purpose. That way, if you clone the data partition, you at least won't include the unpacked NVRAM data (MAC addresses and IMEI). But still, some other IDs such as the Android ID, references to the serial number, etc. will very likely be referenced by some other files on the data partition.
I created a little "update zip" that can be "installed" via TWRP, which is just a shell script that tries to delete all the files on the data partition that contain unique or sensitive info. I use it to "clean" a data partition before publishing it. But it's not perfect yet...
@Tzul Your modified rom is great. But I have one problem with it.
When you connect your turned off device to the power supply there is a clock and charging animation. The clock is several hours ahead of the system clock. System clock and clock during the charging are connected (when I change the system time the 2nd clock also changes the hour).
I was trying to use hwclock but without success.
Is there some kind of file where I can set the correct time zone for the 2nd clock?
Sorry for my English.
@Yozen I didn't modify the ROM. I extracted and packaged it.
When the tablet is turned off and then connected to a power supply, it will usually start "off-mode charging" (can be disabled, so that Android will boot up instead). This is handled by the bootloader (LK, lk.bin), which also displays the battery animation and the clock that you see. Apparently the bootloader on this device doesn't handle time zones, because the clock shown uses China Standard Time (CST, UTC+08:00). This is the first MediaTek-based device I've seen which shows a clock in the off-mode charging screen at all. I guess they normally don't because they have no simple way to figure out the user's correct time zone at that stage.
Will this method and these files work for TB3-730F?
Sir, is there a custom ROM available for Lenovo tab3-710f ?
lacostej said:
@Tzul @gogetrd We are trying to achieve something similar, configure about 700 tablets of this model. I have played with custom ROMs in the past, but mostly as a consumer (e.g. Cyanogen on personal devices).
It is my understanding that installation using the files provided by @Tzul would require to;
0. create a custom ROM.
Then for each device
1. root device (e.g. Developper mode, allow "Unknown source"s, adb install one rooting apk, run it, etc).
2. install custom recovery on device
3. flash custom ROM
Am I right?
If so do we agree that the time spent doing these operations might be about similar than the time spent e.g. manually installing / configuring the device? Or is there a way to automate the steps above?
Click to expand...
Click to collapse
How did you do it in the end? I'm trying to do something similar here and am very curious!
.acy said:
How did you do it in the end? I'm trying to do something similar here and am very curious!
Click to expand...
Click to collapse
For us it is this "simple".
1. Manually configure a single device
2. Readback the ROM (get the ROM from the device and store it on your PC) using SP Flash Tool
3. Parse the ROM from a single file to multiple files using Mtk Droid Tool
4. (clear cache partition & remove stuff like serial number)
5. Load your ROM in SP Flash Tool
6. Click start
7. DO NOT START your new tablet
8. Connect it to USB
9. Wait (assuming you already have the preloader drivers installed)
10. Done, new ROM is flashed to your tab!
edit:
Oh and with 700 tablets it might be nice to look into compressing the file as the full 8gb dump we flash (and we don't do a lot these days) will take ~30-40 minutes
mattiemvs said:
3. Parse the ROM from a single file to multiple files using Mtk Droid Tool
Click to expand...
Click to collapse
That's unnecessary, because the SP Flash Tool can already read back partitions into separate files.
Also, you don't need to clone some partitions like cache, and you really should not clone nvram and parts of data, otherwise you'll end up with tablets sharing unique IDs such as MAC addresses, which will cause problems.
Tzul, you are absolutely right! I typed the items from my mind as it has been quite some time since I've created the ROM
tb3-710f s000028
Tzul said:
Yes, I built it for them.
Click to expand...
Click to collapse
Hello tzul,
Thanks for your jobs.
I want to install Lenovo_TB3-710F_S000027_TO_S000028_Patched_Tzul.zip
But i don't know how i do this when i try with SPFT i choose teh scatter-file and i have an error :
sp flash toll error : 5417
The load scatter file is invalid !
hint :
please check the scatter file and select again
Can you help me ? please
@siegheart73 That is a patched OTA update. It needs to be installed by the recovery (stock or TWRP). If a zip file contains a "META-INF" folder, then it's most likely intended for the recovery, and not for the SPFT.
Tzul said:
@siegheart73 That is a patched OTA update. It needs to be installed by the recovery (stock or TWRP). If a zip file contains a "META-INF" folder, then it's most likely intended for the recovery, and not for the SPFT.
Click to expand...
Click to collapse
Thanks for your answer.
I go to test it.
I want to root this kernel 000028 and i have difficult to do it ?
Do you have a easy solution ?
Thanks a lot for your help.

[ROOT][TWRP][Unlock] Chuwi HI10 Pro by yener90

I tried lots of ways to root this tablet.
Finally succeed.
This package contains a modified kernel. It is required to let the tablet boot with modificated system drive.
After root, you shouldn't update your firmware. You could end in a bootloop.
Thanks @kostyamat. I used his way to root this tablet. But needed to edit most of the files, to get this done with our tablet
http://forum.xda-developers.com/android/general/root-chuwi-hibook-kostyamat-t3368642
DOWNLOAD
http://www43.zippyshare.com/v/lSaWBKVt/file.html
PREPERATION
Unzip the archive to PC, but try not to use special characters or folder names with space in the paths to files. Better way is unzip to a folder in the root of drive C: or D:
Turn on ADB-debugging: "Settings"-"About Tablet" >-> Taps under the item "build number" until the caption appears "you became a developer"-> Return one step back-> enter the item for developers "-> Enable" USB debugging ". A popup may appear on tablet. Set remember and press ok. Also enable OEM unlock.
Connect the device to the PC.
Install the Intel driver IntelAndroidDrvSetup1.10.0.exe
ROOT
1. Unlock_Bootloader.bat - Run first. It will unlock the bootloader. Carefully follow the description of the script and on the screen of the tablet. ATTENTION! All settings, programs, as well as all data on internal SDCard will be destroyed! Data on external MicroSD and Windows will not suffer. After unlocking the device will reboot in factory recovery, which does not display anything (stupidly black screen with backlight), the process may take up to 10 minutes, then the device will reboot into Android.
Tablet is now reseted, enable ADB Debugging and OEM-Unlocking again
2. Outside_boot-TWRP-recovery.bat - The device will be rebooted into the temporary session of TWRP-recovery, to Internal sdcard will be placed UPDATE-SuperSU.zip - install it using TWRP. Previously, you can make TWRP backup (recommended!)
3. Flash-TWRP-recovery.bat - (It is optional) TWRP-recovery will be permanently flashed into the Tablet. (Not recommended! Some time firmware will update, TWRP cannot install OTA-update)
4. Flash-ORIGINAL-recovery.bat - (It is optional) Flash back to the original Recovery.
ENABLE EXFAT & NTFS
SuperSU is required for this!
Download attachment, copy hi10pro-android-fs-1.0.4-install.zip to your tablet and flash it in recovery using TWRP.
WARNING!
Xposed doesn't work. Don't try it.
yener90 said:
I tried lots of ways to root this tablet.
Finally succeed.
This package contains a modified kernel. It is required to let the tablet boot with modificated system drive.
After root, you shouldn't update your firmware. You could end in a bootloop.
Thanks @kostyamat. I used his way to root this tablet. But needed to edit most of the files, to get this done with our tablet
http://forum.xda-developers.com/android/general/root-chuwi-hibook-kostyamat-t3368642
DOWNLOAD
http://www43.zippyshare.com/v/lSaWBKVt/file.html
PREPERATION
Unzip the archive to PC, but try not to use special characters or folder names with space in the paths to files. Better way is unzip to a folder in the root of drive C: or D:
Turn on ADB-debugging: "Settings"-"About Tablet" >-> Taps under the item "build number" until the caption appears "you became a developer"-> Return one step back-> enter the item for developers "-> Enable" USB debugging ". A popup may appear on tablet. Set remember and press ok. Also enable OEM unlock.
Connect the device to the PC.
Install the Intel driver IntelAndroidDrvSetup1.10.0.exe
ROOT
1. Unlock_Bootloader.bat - Run first. It will unlock the bootloader. Carefully follow the description of the script and on the screen of the tablet. ATTENTION! All settings, programs, as well as all data on internal SDCard will be destroyed! Data on external MicroSD and Windows will not suffer. After unlocking the device will reboot in factory recovery, which does not display anything (stupidly black screen with backlight), the process may take up to 10 minutes, then the device will reboot into Android.
Tablet is now reseted, enable ADB Debugging and OEM-Unlocking again
2. Outside_boot-TWRP-recovery.bat - The device will be rebooted into the temporary session of TWRP-recovery, to Internal sdcard will be placed UPDATE-SuperSU.zip - install it using TWRP. Previously, you can make TWRP backup (recommended!)
3. Flash-TWRP-recovery.bat - (It is optional) TWRP-recovery will be permanently flashed into the Tablet. (Not recommended! Some time firmware will update, TWRP cannot install OTA-update)
4. Flash-ORIGINAL-recovery.bat - (It is optional) Flash back to the original Recovery.
ENABLE EXFAT & NTFS
SuperSU is required for this!
Download attachment, copy hi10pro-android-fs-1.0.4-install.zip to your tablet and flash it in recovery using TWRP.
WARNING!
Xposed doesn't work. Don't try it.
Click to expand...
Click to collapse
Does this work for CHUWI HI10 not pro with dual os? and if it does can you make a video tutorial how to root the tablet?
hi10pro-android-fs-1.0.4-install.zip
I tried this and from now on the tablet Hibook 10 pro does NOT accept the external SD-card dany more
How to remove this "feature"?? any ideas welcome ...
WIFI, bluetooth and camera do not work
HI, Thanks for the tutorial
My problem is that, after follow your instructions, I have lost WIFI and BT connectivity. The camera icon and functionality has also dissapear.
How can I recover the initial sotware. I have downloade the image from the Chuwi Website but I do not know how to flash it.
Is there any thread for the Chuwi Hi10 Pro on XDA?
Head over here: http://www.modaco.com/forums/topic/...us-hi10-plus-hi10-pro-hibook-pro-hi12/?page=1
After I unlocked the bootloader, when reboot into android the touch does not work even if I reboot to recovery TWRP.. any ideas??
Use a PC and reflash the recovery again? It is for a Chuwi hi10 Pro right?
RichTJ99 said:
Use a PC and reflash the recovery again? It is for a Chuwi hi10 Pro right?
Click to expand...
Click to collapse
yes is a hi10 pro.. I already tried to reflash recovery and system, but the touch does not work.. it seems that the screen rotation is not right
I would ask over here:
http://www.modaco.com/forums/topic/...10-plus-hi10-plus-hi10-pro-hibook-pro/?page=3
You should be able to get a response/advice.
TWRP backup file
Hi!
Maybe someone could do on the running the tablet backup in TWRP. Android on my tablet died - would need to backup the whole android - system + bootloader.
I have a Chuwi Hi10 Model: CWI515 S / N: Q64G421161XXXXXX
Thank you very much !
przem0 said:
Hi!
Maybe someone could do on the running the tablet backup in TWRP. Android on my tablet died - would need to backup the whole android - system + bootloader.
I have a Chuwi Hi10 Model: CWI515 S / N: Q64G421161XXXXXX
Thank you very much !
Click to expand...
Click to collapse
you should find stock images at the chuwi.com website
Can't read SD card after flashing hi10pro-android-fs-1.0.4-install.zip
Hi there. Thanks for your information. I purchased a Hi10pro recently with the newer chipset. The bootloader was already UNLOCKED. I managed to load TWRP and rooted my tablet. I then flashed hi10pro-android-fs-1.0.4-install.zip and now it wont read the SD card.
If I put the card in another device I can see the data.
I ran a TWRP backup before I flashed hi10pro-android-fs-1.0.4-install.zip but it is on the SD card.
Any ideas on how to fix the problem?
Which partitions would need to be reflashed to be able to read SD card without losing my tablet data?
Looking forward to your response. Thanks
My chuwi hi10 pro doesn't get detected in adb or fastboot mode. I can't even connect it in MTP mode. Charging works fine but. Any help appreciated.
alby_92 said:
yes is a hi10 pro.. I already tried to reflash recovery and system, but the touch does not work.. it seems that the screen rotation is not right
Click to expand...
Click to collapse
Do you have mouse for PC? It works well with mouse. You don't use mouse Bluetooth because mouse bluethooth doesn't work.
https://www.youtube.com/watch?v=V33fbnoaPkE
Chuwi Hi10 PRO UNBOXING, REVIEW, BENCHMARK + GEARBEST COUPONS - YouTube
Hi there, I do not try to hijack this thread, but would someone please be so kind tohelp me find a bios dump from th PQ64 version of this tablet. My bios seemed to be fried by the previous owner. I Ihave the necessary tools to write to the chip over spi, but without the right bits/bytes the tools are useless.
Thx in advance
tron1
SAME
alby_92 said:
After I unlocked the bootloader, when reboot into android the touch does not work even if I reboot to recovery TWRP.. any ideas??
Click to expand...
Click to collapse
so i see that i wasnt the only one with this problem so only the android wont work with touch screen but its fine with a mouse, what i used to finish the set up seeing ass i couldnt touch the screen and i dont know how to fix this problem does anyone know how to fix it? if so reply
---------- Post added at 07:22 PM ---------- Previous post was at 06:56 PM ----------
THANKS SO MUCH YENER90 MY CHUWI HI10 IS ROOTED AND NOW I CANT CONNECT TO WIFI OR USE BLUETOOH NOT TO FORGET I CANT EVEN CLICK THE FREAKING SCREEN :good::good::good::silly::silly::silly::silly::silly:
---------- Post added at 07:32 PM ---------- Previous post was at 07:22 PM ----------
THANKS SO MUCH YENER90 MY CHUWI HI10 IS ROOTED AND NOW I CANT CONNECT TO WIFI OR USE BLUETOOH NOT TO FORGET I CANT EVEN CLICK THE FREAKING SCREEN :good: :good: :good: :silly: :silly: :silly: :silly: :silly:
I have a similar problem.
Horizontal and vertical appear to be reversed. Any Ideas?
I can't go back either. The problem still remains.
Hi guys, no idea?

Categories

Resources