Related
I'm sure that a lot of people already know about the -=V6 SuperCharger=- by zeppelinrox.
If you are not familiar with his great work please follow the link above and read more about it on his thread.
Those of you who have already tried it on their HTC One S (stock) will probably know that there is a whole different level of complexity when it comes to installing it on an ICS ROM. First of all, on any ICS ROM you have to patch the framework library services.jar to get the full functionalaty of the V6 SuperCharger. To make matters worse the HTC Sense is an odexed ROM meaning that you have to do all the patching manually, which is by no means a trivial exercise. Of course you may decide that you don't want to go patching any files and you may be happy with the limited functionality that you get from the V6 SuperCharger as it is. If that's the case you probably won't find this thread very useful...
However, if you're one of those who will not settle for anything less than the full functionality, you need not worry anymore!
Over the last few days I've done all the hard work of decompiling and manually patching the stock services.odex library so people don't have to do it themselves anymore. Not only that, but I've prepared separate versions of the services.odex for each of the three launcher SuperCharge options available:
1. Hard-to-Kill (downloads 1 & 5)
2. Die-Hard (downloads 2 & 6)
3. Bullet-Proof (downloads 3 & 7)
In addition, I'm also including the stock services.odex file so you can restore it back to your system in case you have any problems with the patched files.
4. Stock services.odex (download 4)
Installation procedure:
DISCLAIMER: I take no responsibility whatsoever for anything that might go wrong with your phone, for any and all data loss, for bricking your phone, etc. You do this at your own risk and it is 100% your responsibility.
WARNING! The files provided are specifically for, and have only been tested on, HTC One S with Stock Sense ROM v1.53.401.2 (Europe). These files may also work fine on different versions of the Stock Sense ROM but I haven't tested that. However, if you use them on any other (custom) ROM they are most likely to get your phone either stuck at boot or into a boot loop!
REQUIREMENTS:
a. First and foremost your phone needs to be rooted and have BusyBox v1.16.2 or higher installed. This is a requirement for the V6 SuperCharger script to run so there's no way to get around it.
b. To install the patched services.odex file you ideally need to have a custom recovery installed, such as ClockworkMod. This way you can just flash the patched services.odex from the recovery and if anything goes wrong, simply flashing the stock services.odex over should get you out of trouble (stock file also provided as a recovery update). While it is not absolutely necessary to save a recovery image of your ROM, I would strongly advise you to do so as it's always a good idea to have a recent recovery image to hand just in case (e.g. there is a chance that the stock services.odex included in here may not work if you have a region/operator specific Sense ROM on your HTC One S). Please keep in mind that the stock services.odex included in here comes from Stock Sense ROM v1.53.401.2 (Europe) so it may not work on other versions of Sense ROM!
c. If you don't want to use the recovery update file, you can also download just the services.odex and install it manually. However, if you choose to do this then you're on your own as I don't have enough time to write a tutorial on how to install it manually.
Step 1. If you haven't already done it, go to the -=V6 SuperCharger=- thread by zeppelinrox and read up on the script and what it does.
Step 2. Follow the instructions on the thread (see Step 1) on how to install the -=V6 SuperCharger=- on a typical non-ICS system.
You can get the latest version of the script from this post: http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021
Step 3. Forget about manually patching the services.jar or the services.odex file! Just download the version you need from the bottom of this post AS WELL AS THE STOCK VERSION! You will need the stock if your phone gets stuck on boot. For the installation, see the two options below. Before you do anything however, I strongly advise you to save a system recovery image just in case.
a.The first 4 attached files, named update-services.odex-[something].zip, are recovery update files meant to be flashed via a custom recovery such as ClockworkMod. After flashing the recovery update, also wipe cache and dalvik cache and then reboot.
b. The last 3 attached files are just archives of the patched service.odex files. If you want to go this route you can find some guidance on the -=V6 SuperCharger=- thread in terms of where it needs to be installed and what permissions it should have. Also, if you're using this method don't forget to do a SuperClean & Reboot using the option in the V6 SuperCharger script.
Step 4. It is normal for the first boot after installation to take longer than usual. If your phone has gone past the boot animation and is displaying a windows saying something like 'upgrading applications...' then it's all gone fine so just wait for it to finish. If your phone hangs on the boot animation longer than usual it means that it's probably stuck there and the patched services.odex file is not compatible with your ROM. DO NOT PANIC! Simply go to the recovery instructions further on.
Recovery.
a. If you phone is stuck on the boot screen, hold the power button pressed for about 10 seconds so that the phone goes into hard power off (the touch keys below the screen will start blinking after a few seconds, that's normal).
b. After that just boot into recovery as you nomally do (while holding the volume down pressed, also press the power button briefly and the phone should start into the boot menu; in there, scroll using the volume up / down keys and select the RECOVERY option by pressing the power key).
c. In the recovery simply flash the stock services.odex update file, wipe cache and dalvik cache and reboot. Now the phone should start up fine but your services.odex will not be patched.
d. If your phone is again stuck on the boot screen, you'll have to do a full restore of your ROM from the image that I have strongly advised you to save earlier.
Good luck and I hope you find this useful!
Oh, and pleeease use the Thanks button!
thanx, just installed busybox then flashed "Hard to kill" thru recovery, booted right up on Noble 4.0
Bxrxyxaxn said:
thanx, just installed busybox then flashed "Hard to kill" thru recovery, booted right up on Noble 4.0
Click to expand...
Click to collapse
Thanks, but if you're using this patch on Noble 4.0 it will have absolutely no effect.
That's because Noble 4.0 is a deodexed ROM which means that the services.odex file you've just installed is simply ignored by the system.
Instead you should patch the services.jar file using the online patching tool for deodexed ROMs provided on the V6 SuperCharger thread.
will try on stock T-MobileUS nand later...but thanx for the heads up, will do, edit: Noble already has it
Flashed bullet-proof on stock TMOUS rooted ROM. Caused boot loop. No surprise, it's a different ROM but thought I would give it a go anyways.
Thanks for the post, will definitely use if I go with an EU ROM.
tmobile us
Will this work on the tmobile us one s? Update: noticed the post above stating it doesnt work for T-Mobile us.
Dear Android Hackers!
Please consider helping if you have some spare time and good will.
The device is Samsung Galaxy Player 4.2 (mine is North America version from the US)
Product code: YP-GI1
Android: Gingerbread 2.3.6
Kernel: 2.6.35.7
There is no special section in XDA for this device, so we (the owners of such devices and others who are trying to help) were discussing the matters of rooting here: http://forum.xda-developers.com/showthread.php?t=1715461&page=999
We have tried all the publicly available exploit-based rooting methods, none works, the device release date is April 2012, and there is no Android Gingerbread Local Privilege Escalation exploit released after that date if I am not wrong, and all the old ones are patched as it comes out...
Disclaimer: I'm not a developer, and everything I know I've learned in the last month, so please not laugh if I'm telling something stupid
So, as I understand the options are:
1.
Solution: Find a new exploit, get root, install SuperSU, profit
Problem: There is no publicly available exploit that I'm aware of
2.
Solution: Create an update.zip package with SuperSU and BusyBox, install it in the Recovery Mode
Problem: We need a genuine Samsung signing key to bypass the signature checking
3.
Solution: Get the stock rom, inject SuperSU and BusyBox, flash using Heimdall or Odin
Problem: There is no stock rom available, where do you people get them ha?
4.
Solution: Port CWM to our device, install it, then install and update.zip with SuperSU and BusyBox
Problem: I don't know how to create a CWM rom for my device
So, can anybody help with anything please? THANK YOU!
Up.. Anybody?
There hasn't been a leak of the firmware?
If there's no exploit for you to use, it's going to be hard.
And there probably aren't many people working on GB root exploits.
If you can get the kernel or system partition firmware file it would be easy to do.
Wish I had more help for you.
Did it ship with this version, or did it take an update?
If it took an update you might have hope. PM me if it did, I prolly won't see this thread again.
D
.
dsb9938 said:
There hasn't been a leak of the firmware?
If there's no exploit for you to use, it's going to be hard.
And there probably aren't many people working on GB root exploits.
If you can get the kernel or system partition firmware file it would be easy to do.
Wish I had more help for you.
Did it ship with this version, or did it take an update?
If it took an update you might have hope. PM me if it did, I prolly won't see this thread again.
D
.
Click to expand...
Click to collapse
Thanks for your interest.
No, there were no updates, it is the stock firmware.
The source code of the kernel is available at Samsung's site. And I have dumped the contents of the /system partition (except for several config files, see below):
Code:
$ /data/local/tar -czf /sdcard/external_sd/system.tar.gz /system
tar: removing leading '/' from member names
tar: can't open '/system/etc/bluetooth/audio.conf': Permission denied
tar: can't open '/system/etc/bluetooth/auto_pairing.conf': Permission denied
tar: can't open '/system/etc/bluetooth/input.conf': Permission denied
tar: can't open '/system/etc/bluetooth/main.conf': Permission denied
tar: can't open '/system/etc/dbus.conf': Permission denied
tar: error exit delayed from previous errors
So here is the /system:
http://depositfiles.com/files/e0odb9gvt
password: XDA-DEV
P.S.
Also PM'ed you this post
dsb9938 said:
There hasn't been a leak of the firmware?
If there's no exploit for you to use, it's going to be hard.
And there probably aren't many people working on GB root exploits.
If you can get the kernel or system partition firmware file it would be easy to do.
Wish I had more help for you.
Did it ship with this version, or did it take an update?
If it took an update you might have hope. PM me if it did, I prolly won't see this thread again.
D
.
Click to expand...
Click to collapse
any way you could help?
You will need two devices. There are a few different approaches, but all will require two devices to get everything.
First option:
Dump all /system partition contents. This can be tough without busybox, and without root it will likely be incomplete. (Edit: Looks like you have this.)
Assuming the 4.2 uses ext4 - use http://forum.xda-developers.com/showthread.php?t=1081239 to rebuild an Odin-flashable image from the dump. Without root access, the dump will likely be incomplete but at least hopefully bootable. (Based on the posts above, my guess is that Bluetooth will be busted.)
Once booted, use dd to dump the stock kernel image
Use initramfs repacking tools (these vary by device...) to change default.prop of the stock kernel so that it is debuggable and insecure (ADB sessions have root)
Flash this image into another device to get a full and complete /system dump (including the ones you couldn't dump above).
Second option:
Copy individual files from the initramfs of a running system including scripts
Get kernel source
Build a kernel using the manually dumped initramfs (basically, everything in / that isn't a mount point)
Flash this kernel to get a clean /system dump
Root-inject the /system dump (see above) and flash that on another device to get the stock kernel
It sucks that US devices never seem to have stock firmware images available on release like international devices do.
I can't help you beyond this, everything else is device-specific.
I'm not too experienced with this, but if you you can compile the system.img you might be able to root it. Pm me if you need more specifics, I remember a friend doing this with his motorola charm.
Edit: Heres a nand upload, you should be able to get it from here. Just extract it with yaffs2
http://forum.xda-developers.com/showthread.php?p=30320175&postcount=53
flapflip22 said:
I'm not too experienced with this, but if you you can compile the system.img you might be able to root it. Pm me if you need more specifics, I remember a friend doing this with his motorola charm.
Edit: Heres a nand upload, you should be able to get it from here. Just extract it with yaffs2
http://forum.xda-developers.com/showthread.php?p=30320175&postcount=53
Click to expand...
Click to collapse
No recent device uses raw NAND, and thus yaffs2 doesn't apply.
The problem is getting clean kernel and system dumps without root access - the best you'll do usually is a partial system dump that is hopefully bootable, can be root-injected, and then flashed to a device to get clean kernel dumps. With the kernel dump, you can build an insecure kernel, flash it to a second device, and get the factory image.
In the case of Player 4.2 - there is a POSSIBILITY an insecure international device kernel will boot well enough to get a clean system dump. I know Player 5.0 initramfs was identical, and the only difference between international and USA kernels was the touchkey map. So an international kernel would boot on USA devices but would have broken touchkeys.
Have you checked for rom on sammobile.com. If anyone can provide original firmware are those guys. You can also request it on their forum.
Sent from my HTC One S using xda app-developers app
Entropy512 said:
No recent device uses raw NAND, and thus yaffs2 doesn't apply.
The problem is getting clean kernel and system dumps without root access - the best you'll do usually is a partial system dump that is hopefully bootable, can be root-injected, and then flashed to a device to get clean kernel dumps. With the kernel dump, you can build an insecure kernel, flash it to a second device, and get the factory image.
In the case of Player 4.2 - there is a POSSIBILITY an insecure international device kernel will boot well enough to get a clean system dump. I know Player 5.0 initramfs was identical, and the only difference between international and USA kernels was the touchkey map. So an international kernel would boot on USA devices but would have broken touchkeys.
Click to expand...
Click to collapse
can u explain this a bit more? what are touch keys exactly? sorry ima noob but we are still cant find anything. if you could post your ideas on the thread http://forum.xda-developers.com/showthread.php?t=1715461 that would be helpful thanks!
Entropy512 said:
You will need two devices. There are a few different approaches, but all will require two devices to get everything.
First option:
Dump all /system partition contents. This can be tough without busybox, and without root it will likely be incomplete. (Edit: Looks like you have this.)
Assuming the 4.2 uses ext4 - use http://forum.xda-developers.com/showthread.php?t=1081239 to rebuild an Odin-flashable image from the dump. Without root access, the dump will likely be incomplete but at least hopefully bootable. (Based on the posts above, my guess is that Bluetooth will be busted.)
Once booted, use dd to dump the stock kernel image
Use initramfs repacking tools (these vary by device...) to change default.prop of the stock kernel so that it is debuggable and insecure (ADB sessions have root)
Flash this image into another device to get a full and complete /system dump (including the ones you couldn't dump above).
Second option:
Copy individual files from the initramfs of a running system including scripts
Get kernel source
Build a kernel using the manually dumped initramfs (basically, everything in / that isn't a mount point)
Flash this kernel to get a clean /system dump
Root-inject the /system dump (see above) and flash that on another device to get the stock kernel
It sucks that US devices never seem to have stock firmware images available on release like international devices do.
I can't help you beyond this, everything else is device-specific.
Click to expand...
Click to collapse
I tought of the 2nd option but I miss actually the init.rc, init.hugo.rc and init and recovery files. Someone that tried to help me said that he can't do it. Maybe alice you can make a dump of this for me so I can build an insecure kernel. (hopefully)
good nice.....
Sorry, I was offline the last 3 days.
Entropy512, thank you very much for detailed description of the available options.
Assuming the 4.2 uses ext4 - use http://forum.xda-developers.com/show....php?t=1081239 to rebuild an Odin-flashable image from the dump. Without root access, the dump will likely be incomplete but at least hopefully bootable. (Based on the posts above, my guess is that Bluetooth will be busted.)
Once booted, use dd to dump the stock kernel image
Click to expand...
Click to collapse
I don't understand this part. Wouldn't I just rewrite the stock image when flashing the dumped one? And what is the point of flashing the dumped image without modifications? (or you just didn't write about the needed modifications, e.g. injecting the su binary there?). And should I deodex the /system/app/ and /system/framework directories before creating the new image or no modifications are needed? And if it's preferable to deodex, how do I do that in Linux? Thank you!!
Added:
Meanwhile, I've created a system.img with injected su and superuser.apk, not deodexed, here - http://forum.xda-developers.com/showpost.php?p=31345895&postcount=418
1. Search google and xda...
2. Sign zip with signapk or some other signing tool...
3. Try sams firmware or extract your rom... search for how to in guide in my signature(create custom rom)
4. Search if someone have already ported it on your device or use build.clockworkmod.com
Sent from my GT-S7500 using xda premium
Hey everyone, I'd just like to throw this in here as It's currently only in the general G3 threat with no other D850 verification's.
I have successfully rooted, and installed TWRP on my G3 while running Lollipop. It was not previously rooted nor was there any modification done before upgrading to Lollipop.
It takes a bit of searching for files, but once it's together it works likes a breeze!
http://forum.xda-developers.com/lg-...e-to-lollipop-root-bumpd-twrp-t3048845/page16
Post # 153
eldragon0 said:
Hey everyone, I'd just like to throw this in here as It's currently only in the general G3 threat with no other D850 verification's.
I have successfully rooted, and installed TWRP on my G3 while running Lollipop. It was not previously rooted nor was there any modification done before upgrading to Lollipop.
It takes a bit of searching for files, but once it's together it works likes a breeze!
http://forum.xda-developers.com/lg-...e-to-lollipop-root-bumpd-twrp-t3048845/page16
Post # 153
Click to expand...
Click to collapse
Excellent. Thanks. Nice to see this posted here as well. I wonder if all the many files could be put into a 'master' zip for ease of downloading and installing, and the script be modified to unzip the master and then get going?
Know where i can get the lollipop firmware? Do I use the lollipop or kitkat firmware? Where can I get all the files? I have the root done, the extractor and the twrp.
Thanks for bringing this to our attention. What, if any, is the advantage of this over autoprime's method? Sort my you get to downgrade on less image to KK at the expense of collecting a lot more files and doing a lot more reading of instructions. Or am I missing something?
I don't really know the difference as this is the first one I've seen that allows you to bump stock lollipop (Fresh out of the box)
As for the files, you can find them by googling "Stock D850 Kitkat firmware" >>>>KITKAT<<<< not lollipop firmware. You do not need the lollipop firmware for this method AT ALL. The video in the link I posted is an extremely good walk-through.
Disclaimer : Please note that neither,I nore topet2k12001 are responsible for any bricked phones, or devices that blow up or malfunction. Please thoroughly read this file before using anything inside
Requirements (Follow 100%)
https://mega.co.nz/#!RUxQ3CJC!w0F1xGTcYkIvGvGpdHKIWQ7x_xvyADzedScTqd76e9M <<< Imageprep
Place the imageprep folder in the root of your interal SD card then follow the installation instructions below.
What are the requirements?
>>>>> LG G3 850 Running STOCK 5.0.1 Lollipop. <<<<<<
A "freshly-flashed" Stock Android Lollipop (either by fully flashing a KDZ or TOT, or by OTA update) - strongly recommended, to ensure that there is no "mix" of Kitkat and Lollipop files
Root - please follow the rooting guides from the other threads like this one
Extracted Kitkat Boot Stack (aboot.img, dbi.img, rpm.img, persist.img, sbl1.img, laf.img, tz.img)>>>> INCLUDED IN THIS FILE <<<
"Bump'd" TWRP Custom Recovery >>>INCLUDED IN THIS FILE <<<
Android Terminal Emulator
Busybox - make sure to open the app and you will see a loading progress indicator at the top portion. Once it completes, please click on "Install" at the bottom portion.
Root Checker - to make sure that you have Root and Busybox properly installed
For installation instructions please visit :http://forum.xda-developers.com/showpost.php?p=59447661&postcount=153 and follow the video
CREDIT Goes 100% to topet2k120001 for making all this possible, I'm just repackaging.
does this work on mac?
no
will this lollipop bump work on other LG lollipop phones?
These are stock-based recovery flashable ROMs I've cooked up for the Cube iWork 10 Flagship (aka iWork 10 Ultimate), device i15-T(D).
They are all based on the stock build i15-T_V1.0_20160302, kernel version 3.14.37-x86_64-L1-R429 Wed Mar 2 18:22:46 CST 2016
I have tested these on my stock i15TD purchased directly from cube-tablet.com
If you are stock, unrooted with stock recovery you will need to go here first before you can use these.
WARNING: Flash at your own risk!!!
Make a full backup before flashing!
I would recommend wiping dalvik, cache, data & system before flashing.
For the Odexed versions a factory reset (dalvik, cache & data) will probably work. You might even be able to get away with a dirty flash if you're coming from the same stock build & kernel version, let me know
OTA: Will probably not work with the Stock Odexed version (I wouldn't try it anyhow) and definitely not work with any of the others as I've removed all the OTA stuff in them.
Descriptions
Stock Odexed NoRoot 552.4 MB
-Nothing has been touched here except for changing default location/language, so it boots up in English
Stock Odexed Debloated NoRoot 484.7 MB
-Same as above except debloated
Stock Odexed Debloated Root 489.0 MB
-Same as above and rooted
Stock Deodexed Debloated Root 417.03 MB
-Fully deodexed, debloated and rooted
Stock Deodexed Debloated Root NoGoogle 368.06 MB
-All the stock google stuff has been removed so you can flash a real gapps of your choice. (I have tested opengapps pico and recommend)
Instructions (remember, make a full backup first!)
Boot into TWRP, wipe dalvik, cache, data & system
Flash ROM
If you didn't wipe system in step 1 then go back to main screen, "Mount", select "system"
(if you're flashing the NoGoogle version, then flash gapps now)
Reboot
Enjoy
Thanks
@SuperR. -for the great kitchen
@vampirefo -for TWRP
Downloads
Stock Odexed NoRoot: Android FileHost or BasketBuild
Stock Odexed Debloated NoRoot: Android FileHost or BasketBuild
Stock Odexed Debloated Root: Android FileHost or BasketBuild
Stock Deodexed Debloated Root: Android FileHost or BasketBuild
Stock Deodexed Debloated Root NoGoogle: Android FileHost or BasketBuild
Gapps: Open GApps (select Platform x86, Android 5.1 & the variant of your choice. Note: x86_64 platfom gapps will NOT work.)
If this thread was helpful for you then please hit the "Thanks!" button!
reserved for additional resources
new fw version
chinagadgetsreviews.com/download-latest-android-lollipop-5-1-1-stock-firmware-cube-iwork-10-flagship-tablet.html
stefan_danut said:
chinagadgetsreviews.com/download-latest-android-lollipop-5-1-1-stock-firmware-cube-iwork-10-flagship-tablet.html
Click to expand...
Click to collapse
Thanks for the heads-up man -going to get started tomorrow on cooking up some ROMs for this version...
Sent from my OnePlus2 using XDA Labs
Turns out that build (20160412) is NOT lollipop 5.1.1, still 5.1. No big differences I can tell so far except for lack of play store/services and a bit less bloat. The boot animation is different (not Chinese cube one but text "TOPWING" ???). The device ID is also different.
I think I'll be holding off on making additional zips for this until there's a more serious and official update...
Sent from my OnePlus2 using XDA Labs
Hi jet, thanks for the tutorials!
I tried to install gapps but I get the error that there's insufficient storage available in system.
Did you get the same error? I'd like to use the stock installer.
According to the logs I have NO free system space.
Edit: I fixed it, might want to mention that you shouldn't forget to mount system!
UsernameNotRecognized said:
Hi jet, thanks for the tutorials!
I tried to install gapps but I get the error that there's insufficient storage available in system.
Did you get the same error? I'd like to use the stock installer.
According to the logs I have NO free system space.
Edit: I fixed it, might want to mention that you shouldn't forget to mount system!
Click to expand...
Click to collapse
Yeah, I didn't add it initially because if one wipes system before flashing then it's already mounted. It's the weird location of system partition on this tablet, opengapps (and supersu) install scripts can't mount it.
But, yeah it should be there as you pointed out, so I added it.
Thanks, and enjoy!
jetfin said:
Yeah, I didn't add it initially because if one wipes system before flashing then it's already mounted. It's the weird location of system partition on this tablet, opengapps (and supersu) install scripts can't mount it.
But, yeah it should be there as you pointed out, so I added it.
Thanks, and enjoy!
Click to expand...
Click to collapse
Ow, yeah, I had to because TWRP has issues remounting an otg mounted storage device, that might explain why it failed for me.
I just tried installing xposed and it got stuck in a bootloop, not a big issue as I've backed it up and haven't done much so far, but do you know if it's possible to install it?
And, heck, because I'm asking anyway, have you tried reinstalling windows? I'd like to install windows 10 enterprise on this tablet. Might save me the trouble from going to techtablets.
UsernameNotRecognized said:
I just tried installing xposed and it got stuck in a bootloop, not a big issue as I've backed it up and haven't done much so far, but do you know if it's possible to install it?
And, heck, because I'm asking anyway, have you tried reinstalling windows? I'd like to install windows 10 enterprise on this tablet. Might save me the trouble from going to techtablets.
Click to expand...
Click to collapse
I haven't tried xposed yet myself on this tab, but one guy over on my howto thread mentioned he tried and also ended up in a bootloop. Too much other stuff going on now but when I get around to xposed, if i get it working, I'll post here.
Sorry, can't help you on the windows side at all, in fact this iWork 10 is the first windows machine I've had in years, just android & ubuntu for me these days...
The people at techtablets are more keyed into the windows side of this tab, especially Laura. I'd recommend asking there.
It's the same tablet this and mine that have a Dual Boot (Windows 10 + Android 5.1.1).
And guys, any web page to follow curiosity of this tablet? mods, ROMS, etc...
What I *really* dislike about this tablet:
NO XPOSED... always destroys the bootup of android...
sdk22 x86 is the correct version, but not supported by this tablet... meh
jetfin said:
These are stock-based recovery flashable ROMs I've cooked up for the Cube iWork 10 Flagship (aka iWork 10 Ultimate), device i15-T(D).
They are all based on the stock build i15-T_V1.0_20160302, kernel version 3.14.37-x86_64-L1-R429 Wed Mar 2 18:22:46 CST 2016
Click to expand...
Click to collapse
Are these images for "Cube iWork 10 Flagship (i15-TC)" ?
Guys i need someone to tell me the network adapter name, because i installed new windows 10 and now i cannot find the network adapter driver.
Pls help, how to root td version? Need video tutorial
Hello everyone.
What is the available space of Android and Windows partition at the beginning?
No-one can answer this simply question??
Sent from my m1 note using Tapatalk
Help pls
Hi jet,
I flashed i15-T_Stock_Deodexed_Debloated_Root_NoGoogle.zip and open_gapps-x86-5.1-pico-20160917.zip,everything went okay except when I try to download apps from play store it shows downloading then it says can't download,what can be the reason for that? Or what can I do ?
demanik said:
Are these images for "Cube iWork 10 Flagship (i15-TC)" ?
Click to expand...
Click to collapse
No
Sent from my ONE A2003 using XDA Labs
abu laving said:
Hi jet,
I flashed i15-T_Stock_Deodexed_Debloated_Root_NoGoogle.zip and open_gapps-x86-5.1-pico-20160917.zip,everything went okay except when I try to download apps from play store it shows downloading then it says can't download,what can be the reason for that? Or what can I do ?
Click to expand...
Click to collapse
I've had similar before on other devices, flashing a different opengapps (like nano instead of Pico) or older opengapps or even other gapps package has usually worked... Note that you would want to reflash the rom and immediately following flash the gapps
Sent from my ONE A2003 using XDA Labs
In order to keep this thread clean, please use this one to discuss about Development, Support or Software Updates.
ROMs:
To avoid any possible issue, do not forget to backup your NVRAM so that you won't risk to lose your IMEI. How-to: http://www.anythingultimate.in/2015/11/how-to-backup-your-nvram-partition.html
Stock (Android 6.0)
- 20161025: https://cloud.mail.ru/public/A5Hu/qfeC79DqB or http://www.doogee.cc/bbs/viewtopic.php?f=10&t=38
DO NOT USE THE "Format All & Download" OPTION IF YOU CARE ABOUT YOUR IMEI! Choose "Download Only" instead.
Previous Releases:
- 20160818: https://drive.google.com/file/d/0BzpZ7jq52i28YXZmaUl1eWZhS00
Flash Tool
- SP Flash Tool v5.1628 for Windows & Linux: https://mega.nz/#F!dYUm0TbB!SWeMLb5Wu1NbRzTPQ8-s_A
Recovery:
- TWRP 3.0.2-0: https://mega.nz/#F!0clg0YSB!jWuLefEhJOATBlxbmWfuxw
Root:
Rooting Methods (if you are on Stock ROM)
- SuperSU (flashable using TWRP): http://forum.xda-developers.com/apps/supersu
Extras (Root-Only):
Customization
- Xposed Framework: http://forum.xda-developers.com/showthread.php?t=3034811
Useful Third-Party Apps:
Battery Life
- Amplify: https://play.google.com/store/apps/details?id=com.ryansteckler.nlpunbounce&hl=en
- Greenify: https://play.google.com/store/apps/details?id=com.oasisfeng.greenify&hl=en
20160818 Stock ROM added to first post.
CyanogenMod
Please help to install CyanogenMod
xposed install
Please help,
Error during install Xposed Framework : No space left on device.
bahrom312 said:
Please help to install CyanogenMod
Click to expand...
Click to collapse
How should someone help you if there is no CM available?
bahrom312 said:
Please help,
Error during install Xposed Framework : No space left on device.
Click to expand...
Click to collapse
Well...that's the reason.
Remove some system apps and retry. I recommend you to delete /system/app/Email | /system/app/Exchange2
Hello
I have problem with my T5 lite, after 20 days of use my rear camera is dead!
I have now only front camera.
i don't know is it hardware of software problem i tray factory reset and is the same.
if someone has this problem?
Is it difficult to change the camera?
Increase space for apps
Alberto96 said:
How should someone help you if there is no CM available?
Well...that's the reason.
Remove some system apps and retry. I recommend you to delete /system/app/Email | /system/app/Exchange2
Click to expand...
Click to collapse
Hi Alberto,
On Android 4.4.2 (Star i6 and Star P7 with MTK6582), I was able to change the mount point of the internal flash with the external one so that, even though my phone had only 4GB of "ROM" (of which about 1.3GB usable) I actually was able to use a 32GB external flash as usable space for all my apps.
First, I am not familiar with Android 6.0. Second I am not familiar with this specific stock ROM.
My questions are:
Is it possible to do a similar thing on this phone with Android 6.0 so that the total available space to install new apps is overall increased?
Is it possible to re-partition the memory (a-la 4.4.2) so that the partition used for Apps is increased and the partition used for data is decreased?
Thank you very much for your kind reply.
Best regards
Rosario
I have Problems with the official Stock ROM, com.android.snap shows ads and popups and the system crashes very often Is there a clean ROM?
benxy said:
Hello
I have problem with my T5 lite, after 20 days of use my rear camera is dead!
I have now only front camera.
i don't know is it hardware of software problem i tray factory reset and is the same.
if someone has this problem?
Is it difficult to change the camera?
Click to expand...
Click to collapse
Well you will lose the IP67 capability, but it shouldn't be difficult. Try to reflash the OS first. (Link in Doogee's website)
rdarioc said:
Hi Alberto,
On Android 4.4.2 (Star i6 and Star P7 with MTK6582), I was able to change the mount point of the internal flash with the external one so that, even though my phone had only 4GB of "ROM" (of which about 1.3GB usable) I actually was able to use a 32GB external flash as usable space for all my apps.
First, I am not familiar with Android 6.0. Second I am not familiar with this specific stock ROM.
My questions are:
Is it possible to do a similar thing on this phone with Android 6.0 so that the total available space to install new apps is overall increased?
Is it possible to re-partition the memory (a-la 4.4.2) so that the partition used for Apps is increased and the partition used for data is decreased?
Thank you very much for your kind reply.
Best regards
Rosario
Click to expand...
Click to collapse
Not possible because it is already partitioned properly.
seokai said:
I have Problems with the official Stock ROM, com.android.snap shows ads and popups and the system crashes very often Is there a clean ROM?
Click to expand...
Click to collapse
Yes, first post.
Alberto96 said:
Well you will lose the IP67 capability, but it shouldn't be difficult. Try to reflash the OS first. (Link in Doogee's website)
.
Click to expand...
Click to collapse
Thanks for answer,but i tray reflashing OS,notting hapend.
Need to find where to buy new camera
Root support for init.d
Hi Alberto,
I understand you rooted the Doogee T5.
May I ask you if the rooted ROM has support for the init.d directory (and, of course, the start up of scripts at boot time, with specific mention for the IPtables configuration) ?
Furthermore, I understand the T5 differs from the T5 S for the lower resolution camera and the smaller RAM. Do you know if the procedure to root the T5S is the same used to root the T5, with the same ROM ?
Thank you in advance
Rosario
rdarioc said:
Hi Alberto,
I understand you rooted the Doogee T5.
May I ask you if the rooted ROM has support for the init.d directory (and, of course, the start up of scripts at boot time, with specific mention for the IPtables configuration) ?
Furthermore, I understand the T5 differs from the T5 S for the lower resolution camera and the smaller RAM. Do you know if the procedure to root the T5S is the same used to root the T5, with the same ROM ?
Thank you in advance
Rosario
Click to expand...
Click to collapse
Procedure is the same. Recovery was done special for T5S, but it is suitable for T5 as well.
---------- Post added at 06:01 PM ---------- Previous post was at 06:00 PM ----------
SloN said:
Procedure is the same. Recovery was done special for T5S, but it is suitable for T5 as well.
Click to expand...
Click to collapse
Good. Do you know if it has support for init.d scripting as well?
It is linux, of course yes. May be you must install busybox on rooted device.
SloN said:
It is linux, of course yes. May be you must install busybox on rooted device.
Click to expand...
Click to collapse
I'm sorry to disappoint you, but many Android ROM do not have init.d support, so, unless you have verified yourself, I would still keep it with a question mark. So, do you have the rooted ROM of the T5? Does it have init.d support?
As for the busibox tools, forgive me, but that has nothing to do with the init.d support.
I'm not sure that rom for T5 and for T5S are the same. These devices have different CPU, RAM and ROM. But procedure for TWRP and root are the same. For placing your own scripts in init.d you must install busybox and rootexplorer on rooted device. Than you can put what you want in init.d
SloN said:
I'm not sure that rom for T5 and for T5S are the same. These devices have different CPU, RAM and ROM. But procedure for TWRP and root are the same. For placing your own scripts in init.d you must install busybox and rootexplorer on rooted device. Than you can put what you want in init.d
Click to expand...
Click to collapse
Didn't you just say that the ROM for T5s was also suitable for the T5?
I wrote that the hardware is different ...
And, by the way, again, look init.d and busibox are two completely different things.
1. I said about TWRP recovery, not ROM.
2. To place your working script in to init.d you must have executable commands. Busybox is not only one solution for it, but it is simple.
SloN said:
1. I said about TWRP recovery, not ROM.
2. To place your working script in to init.d you must have executable commands. Busybox is not only one solution for it, but it is simple.
Click to expand...
Click to collapse
You keep answering to questions that I have never given.
1. I did not ask if TWRP was OK, I asked if the ROM was the same.
2. I did not ask how to put scripts into init.d directory, I asked if init.d was supported by this ROM.
But thank you anyway for the conversation. I understand you don't have a rooted T5, that is totally ok. Just I need to know something else. Thank you again.
How to root Doogee T5
1. you need following software:
a) SP Flash Tool: -https://forum.xda-developers.com/showthread.php?t=1982587 (also you can download from site http://spflashtools.com/)
b) Doogee TWRP recovery: http://www.needrom.com/wp-content/uploads/2016/10/TWRP_Doogee_T5.rar
c) SuperSu: http://forum.xda-developers.com/apps/supersu - you must save this zip into phone storage or sd card
2. Install SP Flash Tool, then flash Doogee TWRP recovery (see pic.)
1) choose scatter file from extracted TWRP_Doogee_T5 folder (recovery will be marked automaticaly)
2) push Download button
3) connect your phone. Phone must be power off.
4) after TWRP flashing will be done, disconnect your phone.
5) press volume up + power - you will enter into TWRP
6) choose install, and select your SuperSu zip
7) reboot your phone
3. Enjoy rooted Doogee T5
After installing TWRP and SuperSu - forget about OTA updates. After that you can install updates through TWRP or SP Flash Tool only.