Database Info

[RESOLVED] I Need Help To Repair My Build.Prop (While BOOT Freeze)

Hey i was messing around with the build.prop and i changed my pixle density to 150 and the icons were small but i liked it and then i thought hmmm.. i wonder what 100 would look like then. but thenn..... BOOT Freezes now just before the UI loads so the last second of the boot animation. my phone vibrates as it freezes i have a build.prop file on my pc and was wondering if i could modify the script my mkpark for fast boot.
here is what i have got.
Code:
fastboot flash x-loader ../files/x-loader.bin
fastboot flash u-boot ../files/u-boot.bin
fastboot flash boot ../files/boot.img
fastboot flash recovery ../files/cwm.img
i wanted to know if it is possible to make a line like this...
Code:
fastboot flash [COLOR="Red"]system[/COLOR] ../files/build.prop
as i dont know if system is a real term in this software. thanks or if it is could someone make a system.img for me with the build.prop from the ICS Port? thanks

Forget that.
Just boot into recovery and copy paste the correct build.prop

Cav3 said:
Hey i was messing around with the build.prop and i changed my pixle density to 150 and the icons were small but i liked it and then i thought hmmm.. i wonder what 100 would look like then. but thenn..... BOOT Freezes now just before the UI loads so the last second of the boot animation. my phone vibrates as it freezes i have a build.prop file on my pc and was wondering if i could modify the script my mkpark for fast boot.
here is what i have got.
Code:
fastboot flash x-loader ../files/x-loader.bin
fastboot flash u-boot ../files/u-boot.bin
fastboot flash boot ../files/boot.img
fastboot flash recovery ../files/cwm.img
i wanted to know if it is possible to make a line like this...
Code:
fastboot flash [COLOR="Red"]system[/COLOR] ../files/build.prop
as i dont know if system is a real term in this software. thanks or if it is could someone make a system.img for me with the build.prop from the ICS Port? thanks
Click to expand...
Click to collapse
Guessing you used root explorer Boot in TWRP Recovery delete or rename build.prop look for build.prop.bak remove the .bak extension or Just USE twrp to copy build.prop to SD Mount USB edit copy it back or use vi Editor in terminal.

xbsall said:
Forget that.
Just boot into recovery and copy paste the correct build.prop
Click to expand...
Click to collapse
defcomg said:
Guessing you used root explorer Boot in TWRP Recovery delete or rename build.prop look for build.prop.bak remove the .bak extension or Just USE twrp to copy build.prop to SD Mount USB edit copy it back or use vi Editor in terminal.
Click to expand...
Click to collapse
Thanks i am new to this stuff didnt know about TWRP being able to do that stuff thanks so much.

xbsall said:
Forget that.
Just boot into recovery and copy paste the correct build.prop
Click to expand...
Click to collapse
I rooted my Galaxy Pocket lately and installed LCD modder just to try changing the dpi settings. i changed the stock 120 dpi to 160 and clicked save. the phone froze and i had to pull of the battery. after i restart all i get is a boot loop. i get 3 things (1) s5300 logo (2) animated samsung logo (3) flashing samsung logo which appears just before the lock screen appears ( 1 and 2 vibrations during this) and then it loops all over again. as i understand the change i dpi is not supported for my device and it is not loading into the home screen. the solution seems to be editing the build.prop file to reassign the stock dpi value. but to access the file i have to get into adb mode and have the device available in the list. but since debugging mode was not selected before i essentially soft bricked my phone i am not able to access my device in adb mode. i am able to get into recovery mode tho.any way to edit the build.prop file from this debugging off situation?? I am aware that i can flash it, but i havent backed up data yet and dont wana loose it.....help is much appreciated..........thanks a ton..

Download omap4boot.
Go into fastboot mode.
Open omap4boot
Type;
adb pull /system/build.prop
Find it , edit it then type ;
adb push /location of the edited build.prop/build.prop /sdcard
The edited build.prop is in your sdcard now.
Boot into recovery and put it in your system and you're all systems go.

HELP!!!!
PLEASE HELP ME!!!
i installed LCD Resolution modder and now my device goes into the kiwi++kernel is booting CyanogenMod and after that NOTHING!!!
PLEASE HELP ME
i have Acer Iconia Tab A210 with cyanogenmod 10.2 (Android 4.3) and kiwi++kernel by U.K.F
i'm having difficulties installing the USB Drivers as well when i go into recovery mode and connect my acer into the pc a message pops up with picasso_e2 and when i tick the option so it will search online it finds nothing .
i can't install the Acer A500 drivers since my pc dosent have .NET firmware installed and i can't install it , the setup crashed .
if someone will be able to post the A500 drivers in a zip file and tell me how and where to install them ill be GREAT FULL!
i don't what to do i'm lost please help me

daniel199751 said:
PLEASE HELP ME!!!
i installed LCD Resolution modder and now my device goes into the kiwi++kernel is booting CyanogenMod and after that NOTHING!!!
PLEASE HELP ME
i have Acer Iconia Tab A210 with cyanogenmod 10.2 (Android 4.3) and kiwi++kernel by U.K.F
i'm having difficulties installing the USB Drivers as well when i go into recovery mode and connect my acer into the pc a message pops up with picasso_e2 and when i tick the option so it will search online it finds nothing .
i can't install the Acer A500 drivers since my pc dosent have .NET firmware installed and i can't install it , the setup crashed .
if someone will be able to post the A500 drivers in a zip file and tell me how and where to install them ill be GREAT FULL!
i don't what to do i'm lost please help me
Click to expand...
Click to collapse
u don't need further driver in a zip file your previous driver is ok, all u have to do is download .NET Framework which u can either Google or u can find it from the site like 'filehippo.com'..dats it.
after installing it u will be able to install your desire driver.

[ROOT][CWM RECOVERY] Onda V971 Quad-core | V972 | Allwinner A31

Hello everybody!
Here is the ROOT and CWM Recovery for Onda v971 Allwinner A31 and Onda v972.
CAUTION : I'm not responsible for any damage to your device.Use at your own risk
Back up your data before you start doing anything
Links :
ROOT : ROOT Allwinner A31
CWM RECOVERY : CWM Recovery Onda v971 and V972
INSTRUCTIONS :
ROOT :
1.Download the root zip and put it on SD card.
2.Open Update app, select Local update option.
3.Now select "ROOT_Limpieza_Logo_V3.zip" from the file list then update.
Update app checks the zip and flashes using stock recovery. After its done, device will automatically reboots.
This ROOT zip removes all most all Chinese apps and installs NOVA Launcher. If you don't want NOVA launcher you can delete is using
ES File explorer.
This Root zip works for all Allwinner A31 tablets which has update app.
RECOVERY : (ROOT required)
1.Download the recovery zip and extract it to some folder on your computer.
2.Copy all three files , extracted from the zip, to the SD card.
3.Connect your device to the computer (enable "USB debugging" option in Developer Options), open terminal or command prompt and enter below commands.
Code:
adb shell
Code:
su
Code:
busybox sh /sdcard/install-recovery.sh
Above command installs CWM recovery.To reboot into recovery run below command
Code:
busybox sh /sdcard/reboot-recovery.sh
NOTE : Pressing power button for about 30 secs to 1 min while holding home button boots device into recovery.
For Geeks :
to flash the recovery, run from adb shell
Code:
cat '/sdcard/path to recovery img' > /dev/block/nandg
to reboot into recovery
Code:
echo -n boot-recovery | busybox dd of=/dev/block/nandf count=1 conv=sync;sync;reboot
Now your device boots into CWM recovery.
NOTE : Use home button to navigate and power button to select, as touch controls are not working.
If some thing goes wrong, you have to flash stock firmware using Phoenix suit.while upgrading you have to select "yes" to format the device to get it working again.
CREDITS :
Thanks to CyanogenMod for their great work
Thanks to Koushik dutta for his great CLOCKWORKMOD Recovery
Thanks to http://www.htcmania.com/member.php?u=463595 for root zip
Thanks to everybody who helped me to understand and write this post and to port the CWM .

thanks for your work, a user HTCMania :laugh:

Just only need a cm ROM...jaj
Enviado desde mi V972 Core4 usando Tapatalk 2

1. Do we need Busybox on our devices?
2. Do we need to type the commands into a terminal app from the play store or on cmd of windows? (maybe a dumb question, because it looks Linux/Ubuntu-Like)
Thank you, a huge step forward!
I'm on V812

Thank you so much, now with this being how, how far are we from a TWRP version?

Great work! Thx a lot!

Semms to work even on an Onda v812. :good:
I've used Script Manager to install and reboot in recovery. So It's only a few button press task.
After install, you can use the regulare button press combination to boot in CWM while booting.

natkingcole said:
1. Do we need Busybox on our devices?
2. Do we need to type the commands into a terminal app from the play store or on cmd of windows? (maybe a dumb question, because it looks Linux/Ubuntu-Like)
Thank you, a huge step forward!
I'm on V812
Click to expand...
Click to collapse
Busybox is already installed on our devices.but its old version.so you can update it with busybox from market.
if you use terminal app, you dont need to type first command.i.e "adb shell" .In command prompt in windows , you have to type adb shell to enter into android shell.

Root with SuperSu (not china ) but in us fr... (ok with V812 )
http://translate.google.com/translate?hl=fr&sl=es&tl=en&u=http%3A%2F%2Fwww.htcmania.com%2Fshowthread.php%3Ft%3D543593

That's just greaaaaaat!!
thanks a lot!!

Thanks so much for this hariprasadiit. Installed perfectly.

@Hariprasaditt,
How much dev experience do you carry under you belt? There has been a few people here working hard trying to come up with something, yourself of course, and Arctablet. I've seen some others on androidtablet already coding somethings, but its for the Novo 9. I know the drivers for the screen is going to be different. They are almost finished with it already. Do you think any of their work would assist with us here? Also, I still haven't heard anything from Cyanogenmod, on my request. Thanks to everyone that supported it by the way .

Guauuuuuuuuuuuuuu.... it works!!! thks for your work!!! You´re in fire!!! thks!!!

Dvalin21 said:
@Hariprasaditt,
How much dev experience do you carry under you belt? There has been a few people here working hard trying to come up with something, yourself of course, and Arctablet. I've seen some others on androidtablet already coding somethings, but its for the Novo 9. I know the drivers for the screen is going to be different. They are almost finished with it already. Do you think any of their work would assist with us here? Also, I still haven't heard anything from Cyanogenmod, on my request. Thanks to everyone that supported it by the way .
Click to expand...
Click to collapse
I'm working on porting CM10 now.i'll get help from them in this process. I've already tried Novo 9 and you are right, the drivers are different and also some modules.

hariprasadiit said:
I'm working on porting CM10 now.i'll get help from them in this process. I've already tried Novo 9 and you are right, the drivers are different and also some modules.
Click to expand...
Click to collapse
If I can make a suggestion, Christian Troy here at XDA has some experience with some of the Allwinner CPUs. He ported CM over to multiple chinese branded tablet. Maybe he can added to the knowledge base.
http://forum.xda-developers.com/showthread.php?t=1821398&highlight=onda
---------- Post added at 12:47 AM ---------- Previous post was at 12:29 AM ----------
Has everyone seen this link? First for me, feel a little late on info
http://www.allwinnertech.com/en/product/A31.html

Does anyone tried to use on v812 also? really thanks.

kcthomlau said:
Does anyone tried to use on v812 also? really thanks.
Click to expand...
Click to collapse
As I posted before, yes it works in v812.
I've done a backup and restore without problems. So the other options should work too.
Now we need only custom ROM to flash.
Gamepad support and external bt would be fine.

@hariprasadiit
Do you think you will be able to reenable the full 1080 HD Recording for the back camera?
Also, has anyone seen any improvement to mic quality or may figured out a quick fix to increase mic quality?
@msav,
You opened your tab before correct? If so I was wondering if you would do it gain, I need to get some good detailed pics of the battery connector. I want to take the specs to a custom battery maker near my house and see how much it would cost to create a 10k mAh battery for the tablet.

hariprasadiit said:
I'm working on porting CM10 now.i'll get help from them in this process. I've already tried Novo 9 and you are right, the drivers are different and also some modules.
Click to expand...
Click to collapse
Thanks for your hard work!
Not to be rude, why only cm10, wouldn't it be better to go straight to cm10.1 rather than having to update again in future?

hello i have unpack the cwm for onda v972 to get keys change cuz my tablet NEXTWAY F9X does not have Volume keys just an ESC and power button
i have use keytest.apk
Keycode:4
KeyEvent:KeyEvent{action=ACTION_DOWN,
KeyCode=KEYCODE_BACK,scanCode=158,
metaState=0,flags=0x8,repeatCount=0,
eventTime=17948240,downTime=17948240,deviceId=0,
source=0x101}

[Q] ROM for iJoy Andromeda Tablet (Pipo DS970) RK2918

Hello,
I got an iJoy Andromeda Tablet with Androids ICS 4.03. The fact is that I have quite a lot of problems with it and I would like to try a new ROM.
These are the specs of my tablet
Tablet PC (Mobile Internet Device)
● Display: 9.7" digital TFT, resolution 1024*768(4:3),IPS technology with wide
viewing angle and low power consumption , capacitive touch screen( 10- touch)
● CPU: Rockchip 2918,1GHz,ARM Cortex A8
● SDRAM: 1GB DDR3
● Internal storage: 8GB/16GB/32GB (optional)
● External storage: with Micro SD slot to support external memory up to 32GB
● OS: Android 4.0
● Built-in 2M pixel front Camera & 2M pixel back camera
● With WiFi 802.11b/g/n
● With voice recording, speaker, G-sensor
● With USB host, supports USB device directly, such as keyboard/mouse/USB drive/Lan...
● Supports external USB 3G dangle
● Battery: 4000mAh by 7.4V
● With HDMI output
http://www.pipo.com/product.php?id=74
Could someone recommend me a ROM? I'm familiar rooting, installing recovery etc.. but not for these chipset.
I saw this ROM but I'm not sure if it's good for my tablet.
http://forum.xda-developers.com/showthread.php?t=1987393
Thanks!

You could always give it a try, remember to make a backup

Daniel120201 said:
You could always give it a try, remember to make a backup
Click to expand...
Click to collapse
Thanks just tried but I'm unable to install CWM recovery. The tablet won't boot at all. Any guide around there? I tried to find on the forum but I couldn't find any clear information...

Can your tablet boot into fastboot mode or something?

Daniel120201 said:
Can your tablet boot into fastboot mode or something?
Click to expand...
Click to collapse
Many thanks Daniel,
I could restore the original ROM. I suppose this means fastboot, the tablet is not completely dead after trying to flash CWM, but it won't boot at all (screen doesn't power on). The tablet can be reflashed as it is still detected with no problems (pushing ESC key + power).
When I tried to install CWM I kept the default options: This means flashing recovery.img, parameters file and boot-recovery.img file (I can't remember exactly the name of this file).
I will try flashing only recovery.img this afternoon.
I'm using the method on the seconf post of http://forum.xda-developers.com/showthread.php?t=1987393
I read about flashing only recovery partition etc.. but I couldn't find how do I know which is the setup of my tablet.
It looks like my tablet is quite rare as I cannot find any information about it, but the hardware looks quite common.

http://androtab.info/clockworkmod/rockchip/
You could try those if it doesn't work

Daniel120201 said:
You could try those if it doesn't work
Click to expand...
Click to collapse
Yesterday I tried but I couldn't be sucessful. It looks like I need a new boot.img file and a new parameters file in order to flash my device.
I used wendal 19808-rk29xx-imagetools-v21 from slatedroid to extract the parameters from my original restore ROM
And the program told me that I need to modify boot.img with Linux (I have linux so no problem) in order to be able to install CWM on my device but I don't know exactly what I need to modify inside boot.img... Anyone knows?
I'll keep trying, but if anyone has some kind of guide it will be welcome!
Thanks

btw, boot.img is the kernel

Daniel120201 said:
btw, boot.img is the kernel
Click to expand...
Click to collapse
Finally I succeded making one more step.
After the compressing my update.img I got several files:
boot.img
misc.img
recovery.img (I suppose I have to substitute this one with the one from CWM)
system.img
package-file
parameter
RK29xxLoader(L)_V2.14.bin
recover-script
update-script
Wendal tools said I had to modify boot.img in order to be able to use CWM.
I tried with rk29kitchen tools and I could decompress boot.img with abootimg.exe.
Now I got three files from boot.img
zImage
bootimg.cfg
initrd.img
Can someone help in order to know what I need to patch?
Though I tried to find a guide or something I cannot find clear information regarding what should I do.
Thanks

qwertyu123 said:
Finally I succeded making one more step.
After the compressing my update.img I got several files:
boot.img
misc.img
recovery.img (I suppose I have to substitute this one with the one from CWM)
system.img
package-file
parameter
RK29xxLoader(L)_V2.14.bin
recover-script
update-script
Wendal tools said I had to modify boot.img in order to be able to use CWM.
I tried with rk29kitchen tools and I could decompress boot.img with abootimg.exe.
Now I got three files from boot.img
zImage
bootimg.cfg
initrd.img
Can someone help in order to know what I need to patch?
Though I tried to find a guide or something I cannot find clear information regarding what should I do.
Thanks
Click to expand...
Click to collapse
I just saw that Technaxx BigTAB is very similar to Pipo DS970 or iJoy Andromeda. The outside is the same, buttons, screen size, etc, and is also based on RK2918, just difference is BigTAB 1,2Ghz instead of 1Ghz

Anyone? or does anyone know any useful post?

[HOWTO] Cube iWork 10 Flagship Dual boot (i15-T) - unlock, TWRP, root

WARNING: Performing the actions decribed here will void your warranty and possibly brick your device. This was not written for complete noobs and assumes some prior experience. I will not be held responsible if you ruin your device.
NOTE: This was all tested on a stock iWork 10 Flagship dual boot (aka iWork 10 Ultimate) purchased from the manufacturers website. Device model is "i15 T", Device serial number starts with "i15TD": if you have another variant such as i15TL i can not vouch for any of this working the same way.is tablet
UPDATE: @popcorn2404 modified the boot.img on his USB Type-C variant if this tablet (i15-TCL), confirmed everything working well and was nice enough to provide the modified boot image. See downloads at end of post.
OTA: Most likely this will break OTA. Dont know yet... ​
Prerequisites:
PC with working ADB/Fastboot
Device properly recognized.
I'm using ubuntu 15.10 so I just added an entry to /etc/udev/rules.d/51-android.rules to get things going properly
(EDIT: Windows 64 bit usb drivers attached to post -thanks @Jade.J.Munkey)
TIP: I would highly recommend extracting your stock recovery, boot and system images for safekeeping. These can easily be flashed back in fastboot if something goes wrong. Some may say this is overkill as you will be able to backup and recover with TWRP, but one never knows...
Unlocking bootloader
WARNING: this will erase all data, settings, etc... AND system default language will be chinese when you reboot
Go to settings, about tablet and tap 5 times on the Build number to activate developer options
Go to Developer options and enable OEM unlocking & USB debugging
Plug in your device while booted into android, then open a terminal
just to make sure adb is good type
Code:
adb devices
my output looks like this
Code:
List of devices attached
0123456789ABCDEF device
reboot tablet into fastboot mode
Code:
adb reboot fastboot
The device will now reboot to the OS selection screen. Select android and then it will boot into fastboot mode
once again just to be sure all is good type
Code:
fastboot devices
once again, my output
Code:
0123456789ABCDEF fastboot
then to unlock the bootloader
Code:
fastboot oem unlock
you then should see something like:
Code:
...
(bootloader) Unlock protection is set
(bootloader) Unlocking anyway since this is not a User build
OKAY [ 15.330s]
finished. total time: 15.330s
This is what you should see now in the bootloader if all went well:
SECURE BOOT - DISABLED
LOCK STATE - unlocked
Your bootloader in now unlocked. When you reboot it will take some time for the first boot and the system language will have defaulted back to chinese. Not too difficult to sort if you're familar with Android settings. Otherwise just google "android change system language from chinese to english".
Tip: At this point you may want to already download/copy the supersu zip to internal storage of the tablet so you're all set up for flashing it later...
Modified boot.img
Because of built in security, if you make any changes to system the device will not boot, so you need a modified boot image.
If you have the exact same kernel version as I do you can download the provided modified boot image here. Otherwise you can look HERE for instructions on how to make your own modified boot image. Personally I used SuperR's Kitchen to unpack & repack the image and did the modifications manually with gedit.
Kernel version 3.14.37-x86_64-L1-R429 made on Wed Mar 2 18:22:46 CST 2016
-if you have that one you are good to go ahead and use the image provided here.
Boot device into fastboot connected to PC. From the directory where you have the modified boot image type:
Code:
fastboot flash boot i15TDboot.img
Obviously if you made your own boot image you'll need to replace "i15TDboot.img" with the name of yours...
That's it, now on to recovery and rooting...
Flashing custom TWRP (compiled by @vampirefo)
Assuming you are still connected to the device in fastboot and the custom recovery is in the same directory:
Code:
fastboot flash recovery i15t_recovery.img
Now use volume buttons to select recovery mode and tap power button.
You should now be in TWRP. First, please be smart and make a backup!
Because this device has an unusual mount point, the supersu script will fail to properly mount system (thus failing to flash) so:
From TWRP main screen select "mount" then select system, then return to main screen
Select "install" and then the supersu zip you should already have on the tablet.
Boot system. Now there is one thing left to do:
To prevent the system from overwriting TWRP with the stock recovery on the next reboot:
With a root enabled file manager mount system r/w and navigate to /system/etc
Rename install-recovery.sh to install-recovery.sh.bak
That's it. Enjoy!
If you're looking for more info on this device, check out Laura's great thread
Thanks
@vampirefo - for taking the time to compile TWRP for this device, you rule man!
Laura - for all the info she's made available for this device
@SuperR. - for his kitchen
@Chainfire
@popcorn2404​
Downloads
TWRP recovery
Modified boot image (i15-TD)
Modified boot image (i15-TCL)
SuperSU

There will be additional resources for this device here

Delete

Windows 10 64bit fastboot driver for Cube iwork10 Ultimate
When the device is at fastboot, Windows Device Manager says "Cherry Trail CR" with a yellow exlamation point. abd works fine when it is booted in to normal android. Anyone have this driver or could tell me where to aquire it ?

Cube iwork10 Ultimate Fastboot driver for Windows 10 64bit
Jade.J.Munkey said:
When the device is at fastboot, Windows Device Manager says "Cherry Trail CR" with a yellow exlamation point. abd works fine when it is booted in to normal android. Anyone have this driver or could tell me where to aquire it ?
Click to expand...
Click to collapse
Thanks very much for the good work, I am successfully rooted. The only deviation from the instructions that occurred for me was that /system/etc did not appear in the TWRP file manager, fortunately the .sh did not run upon rebooting after installing the SU zip. So I just I just renamed the .sh in NextApp File Explorer with Root Add-On installed once booted in to android; I have since tested booting in to recovery and then back to android and it is working fine.
Here is the driver I found to enable the Cube iwork10 Ultimate to be seen by Windows 10 64bit whilst in fastboot:
onedrive.live.com/redir?resid=96BA73741E4680ED!5237&authkey=!ALGigNIfrlvxfvI&ithint=file%2czip
if anyone needs it. (remove space from url before pasting in to browser)

Jade.J.Munkey said:
Thanks very much for the good work, I am successfully rooted. The only deviation from the instructions that occurred for me was that /system/etc did not appear in the TWRP file manager, fortunately the .sh did not run upon rebooting after installing the SU zip. So I just I just renamed the .sh in NextApp File Explorer with Root Add-On installed once booted in to android; I have since tested booting in to recovery and then back to android and it is working fine.
Here is the driver I found to enable the Cube iwork10 Ultimate to be seen by Windows 10 64bit whilst in fastboot:
onedrive.live.com/redir?resid=96BA73741E4680ED!5237&authkey=!ALGigNIfrlvxfvI&ithint=file%2czip
if anyone needs it. (remove space from url before pasting in to browser)
Click to expand...
Click to collapse
Glad it worked out for you. Based on your experience I changed the instructions in the OP. Actually that's the exact same I did after doing this the first time but I thought it would be easier to do before first boot in TWRP. Anyhow thanks for pointing this out.
Attached windows usb driver to OP. Thanks!

Stock based, recovery flashable ROMs now available:
http://forum.xda-developers.com/android/development/rom-stock-cube-iwork-10-flagship-i15-t-t3372281

Can someone please make like a video for this or something more lames terms (user friendly). Cause i have a cube iwork 10 Ultimate Dual Boot (i15-TL) and am having issues on Android side where i do not have an option to move apps to sd card in apps settings. Also in storage there is no tab showing all apps on sd card. Im guessing i would need to root my device right? Can someone please help me i just want to get this working properly... i would show screenshots but i don't know how to attach them.

Will the recovery work with i15-TL?
Thank you in advance

flubber1911 said:
Will the recovery work with i15-TL?
Thank you in advance
Click to expand...
Click to collapse
From what I understand from reading at http://techtablets.com/forum/forums/cube/iwork-10-ultimate/
-it *should* work as my understanding is that the TD and TL are virtually identical other than different flavors of windows installed. But I can NOT personally confirm this as I have not tested on the TL variant.
What I can say with a higher level of certainty is that the procedure for unlocking the bootloader should be exactly the same. Once the bootloader is unlocked it is easy to reflash the stock recovery via fastboot should the custom recovery not work properly. (Assuming one has previously extracted an image of the original recovery to begin with. Same for boot and system images.)
So if the custom recovery does not work, it is pretty easy to reflash the original, as well as the original boot or system images should something else get messed up.
Hope this helps. Feel free to ask anything else if anything is unclear...
Sent from my OnePlus2 using XDA Labs

Thank you for your precise answer. I already successfully rooted my Cube. I need the recovery to flash the latest xposed sdk. I' ll have a look if someone extracted the original recovery.

geryalvi said:
Can someone please make like a video for this or something more lames terms (user friendly). Cause i have a cube iwork 10 Ultimate Dual Boot (i15-TL) and am having issues on Android side where i do not have an option to move apps to sd card in apps settings. Also in storage there is no tab showing all apps on sd card. Im guessing i would need to root my device right? Can someone please help me i just want to get this working properly... i would show screenshots but i don't know how to attach them.
Click to expand...
Click to collapse
The stock android on this device does not offer the option to move apps to sdcard.
Tools such as link2sd require a rooted device.
Sent from my OnePlus2 using XDA Labs

flubber1911 said:
Thank you for your precise answer. I already successfully rooted my Cube. I need the recovery to flash the latest xposed sdk. I' ll have a look if someone extracted the original recovery.
Click to expand...
Click to collapse
Yeah, no problem man. I'm curious to see how xposed works out, I've not got around to trying to install yet. Let us know here how that goes.
A copy of the original recovery from my i15-T(D) can be downloaded here: https://www.androidfilehost.com/?fid=24499762636003042
Sent from my OnePlus2 using XDA Labs

I installed an app called Rashr - Flash Tool on my phone. It says it can backup the recovery.
So I did; lets see then if your custom recovery works out

jetfin said:
The stock android on this device does not offer the option to move apps to sdcard.
Tools such as link2sd require a rooted device.
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
Ok so i have i15-TL, with the instructions provided will i be able to root my Android? Also if i Root Android does anything happen with the Winows side? (I still would like a Dual Boot) So im looking to be able to move apps to my sd card, can someone please help me understand how to Root my device and be able to move apps to sd card? Any help would be greatly appreciated, and also thanks to Jetfin for replying my last post. Plz hlp...

geryalvi said:
Ok so i have i15-TL, with the instructions provided will i be able to root my Android?.
Click to expand...
Click to collapse
As clearly stated in the OP, I do not know for sure because I have not tried on that variant, but it *should* work. If you read a few posts back, you can see that another TL owner seems to have successfully rooted his device. Hot tip: *reading* is very important here before asking questions.
geryalvi said:
Also if i Root Android does anything happen with the Winows side? (I still would like a Dual Boot)
Click to expand...
Click to collapse
No, this will not affect the windows side of things. Dual boot is unaffected.
geryalvi said:
So im looking to be able to move apps to my sd card, can someone please help me understand how to Root my device and be able to move apps to sd card?
Click to expand...
Click to collapse
The instructions for unlocking and rooting in the OP are very simple and straightforward. If you are inexperienced in general with rooting android or with adb/fastboot, those answers can easily be found on XDA and elsewhere by searching.
As far as moving apps to SD, since nobody seems to have done it yet (or posted that they have) the only way right now would be to root your device and try out one of the specific apps for that like link2sd. I will try to check this out ASAP but can not promise how soon because I'm focusing my efforts right now on porting another ROM to this device...
Sent from my OnePlus2 using XDA Labs

I could cry right now ... At first I have to say that flashing the TWRP recovery worked flawlessly But always when I tried to flash the Xposed SDK I got an error saying: Updater process ended with error: 255 ( I have no idea how to fix that yet

flubber1911 said:
I could cry right now ... At first I have to say that flashing the TWRP recovery worked flawlessly But always when I tried to flash the Xposed SDK I got an error saying: Updater process ended with error: 255 ( I have no idea how to fix that yet
Click to expand...
Click to collapse
Did you manually Mount system in TWRP before flashing xposed?
Sent from my OnePlus2 using XDA Labs

jetfin said:
Did you manually Mount system in TWRP before flashing xposed?
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
No, do I have to do that? D
---------- Post added at 10:55 PM ---------- Previous post was at 10:51 PM ----------
Ok I manually mounted System, but it still doesn´t work ...

jetfin said:
As clearly stated in the OP, I do not know for sure because I have not tried on that variant, but it *should* work. If you read a few posts back, you can see that another TL owner seems to have successfully rooted his device. Hot tip: *reading* is very important here before asking questions.
No, this will not affect the windows side of things. Dual boot is unaffected.
The instructions for unlocking and rooting in the OP are very simple and straightforward. If you are inexperienced in general with rooting android or with adb/fastboot, those answers can easily be found on XDA and elsewhere by searching.
As far as moving apps to SD, since nobody seems to have done it yet (or posted that they have) the only way right now would be to root your device and try out one of the specific apps for that like link2sd. I will try to check this out ASAP but can not promise how soon because I'm focusing my efforts right now on porting another ROM to this device...
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
Thanks for the reply, so my question before i attempt to root my device is: if i follow the steps provided on OP will i loose any of my current information on my Android side? If so would i need to backup my android (How so). Sorry for all of hte questions but i am a noob on how to do this..
Thanks again

Huawei Mediapad t3 7

Hello folks,
Bought a Mediapad T3 7 from Walmart recently. Has anyone found root yet? I tried all of the Kingroot, etc. APK's so far. Don't waste your time. Tried them all.
If our magicians here can find root, I'd love it!
Thanks,
Rich

Got the same request. Tried KingRoot and iRoot, cause you never know
I'd imagine it's coming one day or another. Tablet isn't that old yet.

Just a matter of somebody compiling twrp for it, I'd imagine..

I would love to know if any progress has been made. I need TWRP and an AOSP ROM. I love the devices look and feel, and its bluetooth operability. but absolutely DESPISE the UI and how it operates.

+1. Decent little tab but no built-in ext4 format for external SD, hoping for root. Getting it to run on stock android would be neat, too.

I tried the online root solutions-none of them work. Just tried Kingroot today and no good.

Same here I got a new huawei t3 10" great tablet by the way but no way I can root it.. I've tried all the Internet suggested ways and nothing seem to work at all but I manage to get the Device ID typing a code in the dialer.

Mercer99 said:
Same here I got a new huawei t3 10" great tablet by the way but no way I can root it.. I've tried all the Internet suggested ways and nothing seem to work at all but I manage to get the Device ID typing a code in the dialer.
Click to expand...
Click to collapse
hi, are you able to make calls on your T3 10? If yes, can you let me know your firmware details, thanks

buddimanv said:
hi, are you able to make calls on your T3 10? If yes, can you let me know your firmware details, thanks
Click to expand...
Click to collapse
Hi there, about that yes I can make phone calls with it I bought the Model with the 4G option (there is 3 models from the same Huawei tablet one of them is WiFi only and the other two can make phone calls) also I managed to unlocked the bootloader by using the device ID I got earlier and Huawei website.
mine is AGS-L09 model

Thanks Mercer99, appreciate it (for your device security, can you remove the image as this has your IMEI)- we have the same model, but different firmware.
AGS-L09C199B002 is “Saudi Arabia Oman Kenya Cameroon Jordan Qatar Ghana Android 7.0 EMUI 5.1” region.
AGS-L09C127B031 is “Greece Hungary United Kingdom Nonspecific Android 7.0_EMUI” . The dialer/calling function is disabled on this firmware - confirmed on Vodafone and EE network.
Is there any way you can extract the OEMINFO from your device and share it with us. This should enable me to debrand the phone if I can find your firmware (downloaded EUROPEAN version with Firmware finder already – so really need an European OEMINFO).
My phone is still locked to Vodafone so I am not sure whether I can flash the firmware or even need root to flash a different OEMINFO (bootloader is unlocked already).

Sorry buddimanv I would love to help but I don't know how

OEMinfo
Last time I did was with P9 Lite - changing from EE to European firmware using a tool (I think SRK Tool or “VNS-L21/22/23/31 [EU] Toolkit [0.0.0.12] All-in-One”) but it was rooted - seems like root is needed before anything. I think the process would be to change the firmware on tablet as well.....
I was hoping as bootloader is unlocked, we can retrieve OEMINFO from fastboot or something and debrand….would be good if anyone can clarify.

Possible Root Solution
Anyone prepared to test rooting method below?
How to install Magisk with ADB
How to install Magisk with ADB
Does not require the availability of custom recovery and root-access
1. Delete all other types of root-access and restore the partition image of the boot partition
2. Download Magisk v13.6 or later and download / unzip from the firmware partition image of the boot partition
3. Unpack the Magisk archive, put the boot image of the boot partition in the same folder, and rename it to boot.img
4. Rename the folder with the name corresponding to the architecture of your device (arm, arm64, chromeos, x64, x86), in magisk_inject
5. In the terminal, change the current directory to the folder with Magisk and run the following commands one at a time:
PHP:
adb shell "rm -rf / data / local / tmp / *"
adb push META-INF / com / google / android / update-binary common magisk_inject boot.img / data / local / tmp
adb shell "cd / data / local / tmp / magisk_inject; mv ../common/*.; chmod 755 *; sh ../update-binary indep boot_patch.sh ../boot.img; mv ../bin/ busybox busybox "
adb pull /data/local/tmp/magisk_inject/new-boot.img
adb shell "cd / data / local / tmp; rm -rf * .img magisk_inject / *. img update-binary bin common"
6. To flash the resulting boot partition image with the name new-boot.img
PHP:
fastboot flash boot new-boot.img
7. Download the system and make sure that Magisk Manager is installed and that its version corresponds to the version of Magisk. If not, manually install the correct version of Magisk Manager.
Click to expand...
Click to collapse
or follow original post
Via Magisk Manager (Only support v14.0+):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/MagiskManager/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Voilà!
Check whether Magisk Manager is installed and the version matches the latest one in the OP
If for some reason Magisk Manager isn't installed/upgraded automatically, please install it manually
Click to expand...
Click to collapse
Bootloader can be unlocked easily of course (code is given immediately) - here
I am tempted but trying to control myself as I don't have a copy of my existing firmware to revert back via dload method if something goes wrong. However, AGS-L09C199B003 firmware is available, so if it fails, I believe you can always go back to stock. I have a feeling this will work.

Took a risk and its rooted now - Magisk v14.0 installed fine and seems to be working (need to test further). Also, Vodafone unlocked the device now for me
Challenge now is to debrand so as to enable functions which has been disabled by Vodafone (namely calling).
Would appreciate if anyone can help - need OEMINFO from another region so as to change the firmware, especially European one or even other UK network who does not disable calling.

Could not contain myself…. In my quest to debrand so I can have a dialer/phone calling function, downloaded a firmware (either from FF Team or on the internet), tried flashing system.img file to see if it installs the dialer as it would not install extracted ones and it did not work. So tested with the boot.img and it did work but phone kept rebooting to eRecovery.
Restoring from TWRP (incomplete/untested) backup did not work. Can’t install any other regional firmware because of OEMINFO. eRecovery can’t find any firmware. The only thing – TWRP/Stock Recovery, eRecovery or bootloader!
Chatted with Huawei support and they won’t give me a link to download the firmware – want me to send for repair, which I don’t really want to – too much hassle and they may end up blaming me anyway….lol He agreed to upload one to their website if he can find one.
I would appreciate if anyone can give me an OEMINFO or link to EUROPEAN firmware with a dialer….. I think European one is AGS-L09C127B031CUSTC127D002 – would appreciate if anyone can share the file with me.

Mercer99 said:
Hi there, about that yes I can make phone calls with it I bought the Model with the 4G option (there is 3 models from the same Huawei tablet one of them is WiFi only and the other two can make phone calls) also I managed to unlocked the bootloader by using the device ID I got earlier and Huawei website.
mine is AGS-L09 model
Click to expand...
Click to collapse
More details and links for the bootloader please, I really need a tutorial-thanks.

dorpmuller said:
More details and links for the bootloader please, I really need a tutorial-thanks.
Click to expand...
Click to collapse
What a buncha bull**** the huawei site is. I got there and when I go to type the product id# in it brings up a calculator dialog with digits I don't even have on the calc.
Done with huawei. All night effing with this is enough. Won't deal with bizarre companies. I'll stick with my samsungs.
I tried... thanks for all of your responses.
Rich

dorpmuller said:
What a buncha bull**** the huawei site is. I got there and when I go to type the product id# in it brings up a calculator dialog with digits I don't even have on the calc.
Done with huawei. All night effing with this is enough. Won't deal with bizarre companies. I'll stick with my samsungs.
I tried... thanks for all of your responses.
Rich
Click to expand...
Click to collapse
I got stuck on the calculator part too. I didn't see the parenthesis buttons. But I turn the tablet on its sit. the view turned horizontal and i was able to see more buttons available. Horrible design for the calculator app.

Hi guys, can someone finally root this Tablet? I would also like to install TWRP to install an AOSP ROM.
Thank you!

Hi.
Did anyone succeed unlock Mediapad T3 7 bootloader ?
I have model BG2-W09 wifi only (European version). I have problem get product id
which is necessary part for bootloader unlock on Huawei site. Stucked to the calculator thing,
when i'll enter ()()1357946()()= on the calculator - i will get ERROR.
Contacted with the Huawei customer service for the help and got not nice answer:
We are unable to send boot loader code via email and can only be obtained through our website.
If you would want to unlock your phone, you should meet the following conditions:
1.Please register your Huawei ID in our official website on your phone.
2.Log in and logout your Huawei ID continuously for 14 days.
3.Each Huawei ID should not apply for the unlock code more than fifth time within 6 months.
Early people informed that email support works fast, but seems now the Huawei tightened terms.
Now i can expect 2 weeks everyday login to meet the requirements.
Some comments about tablet, maybe following helps someone.
One strange thing i've noticed with the tablet, it's not so easy bring up fastboot / recovery menu.
Pressing volume down + power brings up Chinese language test menu (8 options), nowhere to go with that,
pressing volume up + power brings up dialog with 3 options, "Reboot system now" or "Wipe data / factory reset" or "Wipe cache partition". Pressing by same all 3 buttons, volume up + volume down + power brings
up message that update not succeeded, update file not found on sd card. Also if you press only volume down and connect micro usb cable, it brings you to the Chinese test menu again. Also weird why European version tablet has at all Chinese test menu ?
I have triple boot desktop computer and i've downloaded 3 latest adb and fastboot platform-tools packages, for windows (using 10), mac and linux. With windows, using cmd i can start adb session, query device,
seems like everything works, when i'll try:
"adb reboot bootloader", device just reboots back to the main. Tried the same with the Ubuntu, same thing, adb helps finds the device, but when trying: "adb reboot bootloader" device just reboots into normal, not going into fastboot/rescue mode.
The thing is different with the mac (OSX 10.12), when i'll type to the terminal:
"adb reboot bootloader" the device rebooting into the fastboot mode.... and the terminal not responding any further, example when quering: "fastboot devices",
but having already fastboot mode activated on tablet and when rebooting desktop into windows 10 or ubuntu, i'm able using fastboot, tablet responds to the: "fastboot devices" or "fastboot oem get-bootinfo", even "fastboot oem unlock" responds informing about not valid key...
So far i'm able to put tablet into fastboot mode only using mac. Hope that's useful info for someone struggling
with same problems.
Unfortunately bootloader is still locked, problem finding product id, Huawei also did not help.
Huawei product id generator did not recognise Mediapad T3 versions.
Any ideas how to find product id or maybe someone can share the unlock code ?
Thanks in advance.