TWRP for X8

[shindros]

I'm currently using cwm v6.044 for recovery backup on my X8, the problem is that it takes more than 45 minutes to backup my drive, and the same time to restore, Does anybody have a copy of TWRP, for the X8, as I'm using TWRP on my Iocean G7 and I can backup my drive in about 5 minutes.[/align]

[aus9]

EDIT

the problem is that it takes more than 45 minutes to backup my drive, and the same time to restore

thankyou for starting a new thread.

Has it crossed your mind that it might be that there may be nothing wrong with your CWM build?

Also it is possible you have installed a new ROM that might be the source of the problem and have nothing to do with CWM.

Or that your filesystem is full of junk
for example.....it could be that you have so many apps and files that even TWRP would struggle.

Yes I know you may have TWRP on another device and be happy it only takes about 5 minutes.

2) are you really on a CWM recovery?

can you link to it?

or is it possible you are on a CWM based recovery called CTR as per
[Only registered and activated users can see links Click here to register]

or are you using a recovery from here?
[Only registered and activated users can see links Click here to register]

3) it is possible the build of what ever your recovery is .....is faulty

I can build a proper one....try at own risk if you link me to your boot image.
I need the boot image from your working phone not some crappy file from another site pls.

good luck

[shindros]

Hi,re your comments, I am running CalivTR from needrom,... The ROM I am running is the third one, the first being JB the second being KK and this is a very recent release of KitKat, the performance was the same on all 3roms.Re my screen, The x8 runs fhd 1920 x 1080,density 3.0,density DPI 480.I do have mobile uncle but find it difficult to see what the file system is, does, selinuxfs, mean anything to you?rootfs/sys/fs/selinux selinuxfs. This is the only info I can find on mobile uncle,device info... Maybe calivTR is the fault.... Curious...I can do screenshots of Mobile Uncle device info if they are of any help...

[aus9]

you are alllowed to post needrom links at this forum
do you mean this ROM
[Only registered and activated users can see links Click here to register]

2) If so it says not rooted. Can you confirm your device is rooted pls
click on my link and just do the photo commands

Code:

su
id
mount | busybox grep /system

if you get permission denied on last command your device not rooted

if unsure post a photo of result.

3) you still have not cofirmed which CTR you have was it my link or not?

4) in relation to /system you are looking for /system not /sys which is different

selinux is a form of security Linux....don't worry about it at this stage

5) ok lets pretend you are not rooted try this in a terminal

Code:

mount > /sdcard/mount.txt

upload that text file to some file sharing site like dropbox
now link me to it

6) I will comment on filesystem after I see your mount if that works

cheers

[shindros]

Hi, a couple of things,my X8 is definately rooted and i also installed busybox,the link you gave me for CTR,is the same as i am using ,but the link for the rom isnt the one i am using.
I am using a newer one ,dated 25/09/2014.
[Only registered and activated users can see links Click here to register]
I also used your commands from your tutorial,"Testing for true root" and except for identifying my phone as "S5" it is the same.Its definately rooted..
I must get around to opening a dropbox account or similar,then i can send you "screenshots"
Im going have to go now,as "Her Indoors is calling"LOL The Real Boss...

---

Here are my dropbox links...


[Only registered and activated users can see links Click here to register]

[Only registered and activated users can see links Click here to register]

[Only registered and activated users can see links Click here to register]

[aus9]

EDIT

ADD the word gap or space to (3)

1) your first image
your device not true rooted. pls compare my image to yours....they differ.

2) because your device is not truly rooted it borks on the mount command and gives you the funny stuff left of prompt.

3) the last command should have no gap between / and the word system so it reads as /system

4) go back to true root and attempt to make system read writeable pls
I assume you will need to setup adb for a windows user
#####################

yes I wil need you to upload your working boot image after all.

I have just unpacked the ctr image I alluded to earlier and you may be shocked to hear this is a mod of a different phone.

a bad mod is what us aussies call it.

from build.prop

ro.product.brand=ZOPO

enough said?

no secondly there is no init.usb.rc file in unpack.
that means you will not IMHO be able to safely use sideload while in CTR -> install zip -> by sideload

speaking of which.....the X8 has no removeable battery
----not sure how you use flashtools by attempting to comply with the rule to remove battery.

[shindros]

Hi,
please find a new screenshot [Only registered and activated users can see links Click here to register] i did a couple of days ago..I would be interested in your comments,if you have time.I think the system is readable,
Its interesting what you say about "Zopo",as sometimes when I benchtest it with Antutu,it Identifies itself,half the time as Iocean X8,and the Other half as Zopo...but without a Model Number.
Okay ,here at the moment its Bedelum,weve just moved house a couple of weeks ago..I cant find anything lol.
I appreciate the help and time youve given me..Thanks..

EDIT

ADD the word gap or space to (3)

1) your first image
your device not true rooted. pls compare my image to yours....they differ.

2) because your device is not truly rooted it borks on the mount command and gives you the funny stuff left of prompt.

3) the last command should have no gap between / and the word system so it reads as /system

4) go back to true root and attempt to make system read writeable pls
I assume you will need to setup adb for a windows user
#####################

yes I wil need you to upload your working boot image after all.

I have just unpacked the ctr image I alluded to earlier and you may be shocked to hear this is a mod of a different phone.

a bad mod is what us aussies call it.

from build.prop

ro.product.brand=ZOPO

enough said?

no secondly there is no init.usb.rc file in unpack.
that means you will not IMHO be able to safely use sideload while in CTR -> install zip -> by sideload

speaking of which.....the X8 has no removeable battery
----not sure how you use flashtools by attempting to comply with the rule to remove battery.

[aus9]

your link contains an error but is viewable here
[Only registered and activated users can see links Click here to register]

yes you are read writeable.

we can progress.
#######################

Would you consider full edit of your first post and change TWRP to CTR?
#################

your boot image contains build.prop and antutu is likely to read that and find your rom is a mod of zoppo ....that is....your CTR is faulty and your normal boot is faulty.

relooking at your rom
[Only registered and activated users can see links Click here to register]

I can now see how windows users use flashtool with a non-removable battery.

if you trust me, we are going to mod using root powers that we know exists on your phone.....various files

these are text files......and will tell antutu you have iocean x8
but also will have other consequences when using or trying to use adb.

#########################

but we need to be smart and you have some times issues as well.

so I suggest you hang five....I will download your rom and rebuild CTR

CTR is independent of normal boot stuff.....so antutu won't know anything about it.

################

1) What buttons you push to get from off state to recovery mode?

is it power button plus vol up?

2) while in recovery mode....do nothing there please just this test.

LONG PRESS the power button.......confirm it turns off or reboots phone into normal mode

3) later on.....I need you to look at this thread and adb minimal download

[Only registered and activated users can see links Click here to register]

4) when you have time.....no rush I then need you to go into recovery mode and do nothing in there.
instead....using windows and adb .....setup as from link
confirm you see adb devices

b) then in android ....recovery choose install zip
from sideload
and because of bad build you are going to get an error or not.

I will discuss this later......what I am trying to do is to prepare you for changes and for trouble shooting do ......one change at a time
because once we change your normal boot.....you will need to know what to do if you plan on using that rom builder for updates

[shindros]

Yeh, to go into recovery mode from off,it is exactly as you say,its Power Button plus volume up,providing the phone has the power lead connected and is charging (this is the norm for these chinese phones)Ive read this many times and is applicable to The X8.With no power lead conected,it just boots up as normal ,NOT into Recovery Mode.or if my X8 is already on,I use a small app called "Quick Boot".With this i can power off,Reboot,Reboot into recovery or reboot into the bootloader.Can also use Mobileuncle.
I dont have ADB for Windows,so I will have to download it...Is there a shortened version for windows? as if i remember rightly its about 500 Mb in size, when I downloaded this before.. Ive just booted my phone into recovery mode and then squeezed the power button,and it has rebooted,normally.
I Dont have any problem changing the name of this Post from TWRP to CTR...Im on my laptop now as its a little easier to communicate with you and this forum,than previously,when i was using my phone. I will try to change the name of this thread to CTR,however ,im very new to this so may need your help or advise...we will see ..ok im going as its past lunch time and im hungry..talk to you later

[aus9]

try and break up what you write with breaks....you are hard to read otherwise.
Pls don't quote all my post if it has no relevance instead use a quote box like this

Code:

[quote]blah blah
snip
blah blah[/quote]

as I said before adb will be a minimal download....no rush to try it

your X8 is same as my X7 for buttons to recovery mode and I too use quickboot.

now before you get too excited I need to explain why you should not be on your current rom

1) rom builder has not understood how to quality check it
proof is on unpack of both the stock recovery image and stock boot image
----check his init.rc

in particular--stock recovery init.rc

import /init.recovery.${ro.hardware}.rc

does not have any.....laughs out loud

insmod /sec.ko

this is a command to insert a kernel module called sec(urity)
---standard command but ...not included in image

I won't bore you with more than 2 examples.....but your original post was complaining about time to image your files.

I suspect a part of answer is
a) the number of files you have
b) delays caused by bad and missing system files

#######################

what we do know is that your boot image boots and it was exactly the same as the stock recovery kernel......no surprises there at least.

################

TRY AT OWN RISK

download new CTR
[Only registered and activated users can see links Click here to register]

place at root of sdcard as per tutorial
[Only registered and activated users can see links Click here to register]

but do not change file name downloaded

flash it using mobileuncle and reboot into it via mobileuncle

##########

test how long backup images take......with caution that I think you are on bad "normal" boot images.

good luck

############
what can go wrong?

size is within limits see your scater file for recovery is
partition_index: SYS10
partition_name: RECOVERY
partition_size: 0xa00000

====10 megs in real terms mine is less than 7 megs

error 2 bad kernel module
I have injected a kernel module....but it may bork as its not from your kernel.
I wanted to use your "official" kernel and so if it borks I have 2 options

option 1....rebuild with no init.rc line to insert kernel module
option 2...rebuild with kernel that has a matching kernel module
------only you can tell.