Related
And what I mean, no android kitchen and those kind of tools. Simple from the start where you are forced to do all the work yourself.
(I have to much free time)
E-13 said:
And what I mean, no android kitchen and those kind of tools. Simple from the start where you are forced to do all the work yourself.
(I have to much free time)
Click to expand...
Click to collapse
Cyanogenmod is a great place to start since its stock, http://wiki.cyanogenmod.org/w/Development
Trozzul said:
Cyanogenmod is a great place to start since its stock,
Click to expand...
Click to collapse
Ah, thank you. I will look into that.
Small problem I (probarly) have. I also have a mediatek phone (main phone) and I heard there are a few problems when you want to make roms for those. It was due to lack of released source or something?
E-13 said:
Ah, thank you. I will look into that.
Small problem I (probarly) have. I also have a mediatek phone (main phone) and I heard there are a few problems when you want to make roms for those. It was due to lack of released source or something?
Click to expand...
Click to collapse
that is true, the kernel of mediatek has problems with Cyanogenmod so its a little hard. mediatek kinda sucks to develop for.
Trozzul said:
that is true, the kernel of mediatek has problems with Cyanogenmod so its a little hard. mediatek kinda sucks to develop for.
Click to expand...
Click to collapse
Wouldn'tv it be easier to start with vanille android then or modify the stock ROM bit by bit?
E-13 said:
Wouldn'tv it be easier to start with vanille android then or modify the stock ROM bit by bit?
Click to expand...
Click to collapse
always start with modifying the stock rom, every few changes you make you should check out if they work and repeat that process.
Trozzul said:
always start with modifying the stock rom, every few changes you make you should check out if they work and repeat that process.
Click to expand...
Click to collapse
Is there a way I can make my current ROM into a flash able zip?
E-13 said:
Is there a way I can make my current ROM into a flash able zip?
Click to expand...
Click to collapse
that i wouldnt know where to get information on, im sure there are tools for this, make a backup and unzip it and see what you can do from there, of course you can flash a backup but its a start.
Trozzul said:
that i wouldnt know where to get information on, im sure there are tools for this, make a backup and unzip it and see what you can do from there, of course you can flash a backup but its a start.
Click to expand...
Click to collapse
I was able to extract the boot.img,recovery.img and the META-INF map. If I am right, I didnt miss anything else thats important. Right?
E-13 said:
I was able to extract the boot.img,recovery.img and the META-INF map. If I am right, I didnt miss anything else thats important. Right?
Click to expand...
Click to collapse
Hmm I'm pretty sure there should be a few more things, go to CyanogenMod and download a random file for whatever phone and check out those files. Make sure its a stable and not nightlie
Trozzul said:
Hmm I'm pretty sure there should be a few more things, go to CyanogenMod and download a random file for whatever phone and check out those files. Make sure its a stable and not nightlie
Click to expand...
Click to collapse
I got one from the.. eh.. HTC one.
The main files (and I looked around already) are:
META-INF
system
boot.img
Thats it. And inside system there are the "standard" folders and build.prop.
I got this already tough.
-Now a small thing, this is a mediatek device, And from what I see/understood a pain in the everything to make roms for this.
I did find this about: http://sourceforge.net/projects/alcatel/files/
A huge file ;p. It seemed to be files about the kernel. The files:
boinic
external
kernel
mediatek
system
With a line I found in a readme in mediatek/kernel:
The "mediatek/kernel/" directory is intended for Mediatek solution kernel specific non-customization codes.
Anyway, back to the point. I got system, boot.img and Meta-inf
I think I got everything ready
E-13 said:
I got one from the.. eh.. HTC one.
The main files (and I looked around already) are:
META-INF
system
boot.img
Thats it. And inside system there are the "standard" folders and build.prop.
I got this already tough.
-Now a small thing, this is a mediatek device, And from what I see/understood a pain in the everything to make roms for this.
I did find this about: http://sourceforge.net/projects/alcatel/files/
A huge file ;p. It seemed to be files about the kernel. The files:
boinic
external
kernel
mediatek
system
With a line I found in a readme in mediatek/kernel:
The "mediatek/kernel/" directory is intended for Mediatek solution kernel specific non-customization codes.
Anyway, back to the point. I got system, boot.img and Meta-inf
I think I got everything ready
Click to expand...
Click to collapse
Looks like you do, I must have been thinking about something inside meta inf that let's you change all the icons
Trozzul said:
Looks like you do, I must have been thinking about something inside meta inf that let's you change all the icons
Click to expand...
Click to collapse
*cheers* But I dont really get this part. (probarly for advanced peeps) Why is it so hard to make roms for mediatek. I get they dont release the source code/code you guys need for that. But where is the code for you so badly need for that.
E-13 said:
*cheers* But I dont really get this part. (probarly for advanced peeps) Why is it so hard to make roms for mediatek. I get they dont release the source code/code you guys need for that. But where is the code for you so badly need for that.
Click to expand...
Click to collapse
I don't know whoever owns mediatek has the codes obviously. Mediatek CPUs are terrible anyway so I'm sure nobody will leak the codes
Well, not that terrible to be honest. Mine works pretty good. (am just kinda fed up with alcatel ;p) And alot of people have devices running on mediatek cpu's. Just someone needs to put real good effort into it. (and hope he doesnt get into problems for it xD)
E-13 said:
Well, not that terrible to be honest. Mine works pretty good. (am just kinda fed up with alcatel ;p) And alot of people have devices running on mediatek cpu's. Just someone needs to put real good effort into it. (and hope he doesnt get into problems for it xD)
Click to expand...
Click to collapse
Well i wish you good luck, and if you get to somehow release a rom please be sure to hit me up on it what Alcatel device do you have by the way? if you do get a new device in the future that has Cyanogenmod support what i recommend you should do is download the latest stable and just theme that all you want (im sure you know how to move apks to make them SYSTEM apps), and when you think your ready from building it from source jump right in.
Trozzul said:
Well i wish you good luck, and if you get to somehow release a rom please be sure to hit me up on it what Alcatel device do you have by the way? if you do get a new device in the future that has Cyanogenmod support what i recommend you should do is download the latest stable and just theme that all you want (im sure you know how to move apks to make them SYSTEM apps), and when you think your ready from building it from source jump right in.
Click to expand...
Click to collapse
Haha. Thank you I have a Alcatel One Touch Scribe HD. (8008D) Supported by nothing! (expect framaroot )
Now time to abuse my phone and hopefully not turn it into a paperweight.
Well, The rom is done. Added a few Apk's. Now need to look over it and get the guts to flash it
Welcome
I have started this thread for the THEORETICAL development of the mt6732/mt6752 from source if such a thing happened to exist which of course it does not.
While compiling from source is pretty well documented :good: compiling MTK is not so well documented especially the mt6732/6752.
I have tried to keep this thread as ambiguous as possible and hopefully we will be left in peace to iron out any difficulties.
DO's:
I am a Total Noob myself to compiling from source but experienced enough to use the xda search box, Google and Youtube first before asking any questions. If your still confused after using the above then by all means ask here.
DON'T s:
If your a noob who should happen upon this thread then by all means read and learn but please respect the dev's by not asking random question without searching first :fingers-crossed:
SHARING:
Please only share things of a sensitive nature with recognised members who you know and via the PM. :good:
Lets just see how far we can push this Kernel
Recommended Reading:
[GUIDE]Building a Kernel from source{Mediatek}
Build Kernel MT6577 - Can't boot after build
How To Port CyanogenMod Android To Your Own Device
XDA:DevDB Information
k01q_e k01q_h, Kernel for all devices (see above for details)
Contributors
bigrammy
Kernel Special Features: Remains to be seen
Version Information
Status: Testing
Created 2015-02-25
Last Updated 2015-02-25
I am here, reporting for duty. If anyone wants an extra "potato" because he has too much "ketchup" for use feel free to ask me
Just to be clear
I am new to compiling from source in any shape or form
I believe the kernel to be not a problem and I know dev's are working on getting our phone on cm and maybe others :fingers-crossed:
But me being me I am very curious and would like to understand how we would go about doing what @varun.chitre15 managed to do for the mt6582 Here
I have the PC all setup for building now thanks to @carliv great guide Here and the cm and android tut's I also found this useful guide on youtube by Dave Bennet Here
Our device is not on the cm or google repo so how do we add it locally.
Do we need any special commands for mediatek
Could we use the mt6582 repo and substitute or mod the files
As you can see I have more questions than answers as normal :laugh:
I dont want to tread on any toes here or take over current developing but just want to learn as said in the OP there is a lack of mtk guides regarding this.
If I missed a clear mtk guide then please post the link to it. :good:
In short your looking at manifests. http://wiki.cyanogenmod.org/w/Doc:_Using_manifests
carliv (I think) posted the device config on github - link in your SPFlash thread somewhere.
Found it: https://github.com/carliv/device_elephone_p6000?files=1
Vendor files
I have compiled and flashed a kernel, I've been running it for 24+ hours with no obvious issues. It's honestly very easy to just get it to build if you don't try to make major changes.
I have (very lazily) tried to change a couple of things in the config to fix the known issues (OTG, compass): unfortunately I have no way to test the OTG function right now, while the compass did not magically start working. On the other hand, the notification light issue which is introduced by V8.4 is not strictly or exclusively kernel-dependent, since I am running V8.3 with my own kernel and the notification function is intact. That's all I can share at the moment.
xenonism said:
I have compiled and flashed a kernel, I've been running it for 24+ hours with no obvious issues. It's honestly very easy to just get it to build if you don't try to make major changes.
I have (very lazily) tried to change a couple of things in the config to fix the known issues (OTG, compass): unfortunately I have no way to test the OTG function right now, while the compass did not magically start working. On the other hand, the notification light issue which is introduced by V8.4 is not strictly or exclusively kernel-dependent, since I am running V8.3 with my own kernel and the notification function is intact. That's all I can share at the moment.
Click to expand...
Click to collapse
Can you switch on and post the /proc/config ?
Regarding the notification lights, I think v8.4 introduced the custom partition (might be wrong on that). Running grep -r "ro.notification.breath" /system/ the only result I got was services.odex (might have been settings.odex). I've bak(smali)ed it but couldn't see the difference between the two that would explain the change.
HypoTurtle said:
Can you switch on and post the /proc/config ?
Regarding the notification lights, I think v8.4 introduced the custom partition (might be wrong on that). Running grep -r "ro.notification.breath" /system/ the only result I got was services.odex (might have been settings.odex). I've bak(smali)ed it but couldn't see the difference between the two that would explain the change.
Click to expand...
Click to collapse
The config file is attached to the post, it's too big to paste it.
I have tried the new ROM which came out today, then flashed my kernel. I can't use either SIM card anymore. Flashed the boot.img that comes with the ROM - same. I guess I gotta go back to V8.3 for now.
The new ROM doesn't seem to be the same as the OTA: it reports as: Elephone_P6000_02_V8.0_20150206.
About the notification issues (which bothers me the most), I haven't had much time do to more experiments, but I was thinking this (which probably also led to my confusion*): there's a chance the functionality is not removed or shut down, at least in the intentions of the maker. After all, in V8.4 (and in the new ROM), when the phone is connected the light stays on, while notifications make it breath. While not a desirable behaviour (at least IMO), I wouldn't call it... a non-behaviour, so to say. So perhaps the functionality itself is intact but something is altering the way it works, for whatever reason. I also did some unpacking and grepping a few days ago, but I couldn't find anything useful.
* At some point I thought the issue was fixed because the light was breathing while connected to my PC, but it was probably because I had a notification to read.
xenonism said:
The config file is attached to the post, it's to big to paste it.
I have tried the new ROM which came out today, then flashed my kernel. I can't use either SIM card anymore. Flashed the boot.img that comes with the ROM - same. I guess I gotta go back to V8.3 for now.
The new ROM doesn't seem to be the same as the OTA: it reports as: Elephone_P6000_02_V8.0_20150206.
Click to expand...
Click to collapse
Lets not speculate too much - but perhaps there was a minor board change between the first and second preorders, notification could be a problem with granting notification access (in settings) - could this be a selinux issue? It would explain why things like Light manager work - as you grant them notification access.
For lost Imei - can you compare the custom partition to the one in the ota?
If anyone needs an easier way to grab the 'ketchup', my GitHub has it. Click on my blog link in my signature.
BachMinuetInG said:
If anyone needs an easier way to grab the 'ketchup', my GitHub has it. Click on my blog link in my signature.
Click to expand...
Click to collapse
Thanks bro,
Nice log
I was going to try use the sprout config as this is nice and clean Here when I have worked out how to do things that is.
My eyeballs are bleeding now with all this reading but from what I can see most of files are the same names so maybe we could just replace them with ours probably 98% ish
I did see one ROM some place for the mt6732/52 that had mt6582 references I just wish I could remember where I had seen it
Like I say I am a noob to this compiling and linux stuff so I maybe talking out of my ass :laugh:
bigrammy said:
Thanks bro,
Nice log
I was going to try use the sprout config as this is nice and clean Here when I have worked out how to do things that is.
My eyeballs are bleeding now with all this reading but from what I can see most of files are the same names so maybe we could just replace them with ours probably 98% ish
I did see one ROM some place for the mt6732/52 that had mt6582 references I just wish I could remember where I had seen it
Like I say I am a noob to this compiling and linux stuff so I maybe talking out of my ass :laugh:
Click to expand...
Click to collapse
I'm actually a noob too, and honestly I've only ever successfully built a fakeflash (temporary recovery) that didn't even work.
bigrammy said:
Thanks bro,
Nice log
I was going to try use the sprout config as this is nice and clean Here when I have worked out how to do things that is.
My eyeballs are bleeding now with all this reading but from what I can see most of files are the same names so maybe we could just replace them with ours probably 98% ish
I did see one ROM some place for the mt6732/52 that had mt6582 references I just wish I could remember where I had seen it
Like I say I am a noob to this compiling and linux stuff so I maybe talking out of my ass :laugh:
Click to expand...
Click to collapse
Can anyone actually make a guide noob friendly to build kernel from source? I got kernel with me locally zip file I want to build it please any help?
Tech N You said:
Can anyone actually make a guide noob friendly to build kernel from source? I got kernel with me locally zip file I want to build it please any help?
Click to expand...
Click to collapse
I think you can use the scripts in the root of the source code to build the kernel? make<something>.sh.
Make sure you're on Linux (Ubuntu preferred) and that you have all dependencies installed correctly. To execute the script, simply go to the Terminal, cd to the location, then type . make<something>.sh
Tech N You said:
Can anyone actually make a guide noob friendly to build kernel from source? I got kernel with me locally zip file I want to build it please any help?
Click to expand...
Click to collapse
Have a look at the README.
Does make menuconfig work here?
These few simple instructions from the readme file enable you to build a working kernel (at least in a Linux environment):
Code:
How to Build
kernel
======
1. Get the prebuilt cross compiler from AOSP website:
$ git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6
2. Add required cross compiler to PATH:
$ export PATH=/YOUR_TOOLCHAIN_PATH/arm-eabi-4.6/bin:$PATH
$ export CROSS_COMPILE=arm-eabi-
3. Then use the following commands to build the kernel:
$ ./makeMtk k01q_e new k
make menuconfig can be made to work, but you need to set some parameters and I can't look into it right now.
You previously asked something about the custom partition, I need some guidance there as I am not familiar with the IMEI issue.
xenonism said:
These few simple instructions from the readme file enable you to build a working kernel (at least in a Linux environment):
Code:
How to Build
kernel
======
1. Get the prebuilt cross compiler from AOSP website:
$ git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6
2. Add required cross compiler to PATH:
$ export PATH=/YOUR_TOOLCHAIN_PATH/arm-eabi-4.6/bin:$PATH
$ export CROSS_COMPILE=arm-eabi-
3. Then use the following commands to build the kernel:
$ ./makeMtk k01q_e new k
make menuconfig can be made to work, but you need to set some parameters and I can't look into it right now.
You previously asked something about the custom partition, I need some guidance there as I am not familiar with the IMEI issue.
Click to expand...
Click to collapse
Yea wasn't sure about menuconfig as mtk uses projectconfig rather than def_configs.
In the custom partition there are files like /custom/etc/firmware/modem.img etc. When messing with a Flyme port it was these files (and possible conflicts in /system) that caused an IMEI:nul.
FYI I opened the custom partitions on windows using an ext viewer after running the imgs through sgs2toext4.
Kernel building Mediatek
Tech N You said:
Can anyone actually make a guide noob friendly to build kernel from source? I got kernel with me locally zip file I want to build it please any help?
Click to expand...
Click to collapse
Not sure if you guys have seen or read this but it's a pretty comprehensive guide to building the mediatek kernel by @MasterAwesome and should really be compulsary for all kernel related things thread here http://forum.xda-developers.com/showthread.php?t=2754513
@HypoTurtle
Regarding the custom partition this is or could be a problem for us now and in the future and may require further investigation. The cm sprout branch has the modem.img in the (normal place /system/etc/firmware) but as you say ours is in the custom partition which is probably to protect it from bad /system flashes
Thing is I see no normal type link to it in the /system/etc/firmware so it must be linked some other way which may explain why all my port attempts failed as none of them used a custom partition (Asus_X002)
Maybe we will have to repartition the emmc to a standard config and alter the kernel (if the links are set via the kernel that is) for cm and other ports to work smoothly as I am unsure just how everything is linked up.
I have not had much experience with custom partitions so someone one know's of a good info source please link it. :good:
Hopefully Master @Santhosh M can figure out what's going on with the custom partition :fingers-crossed:
bigrammy said:
@HypoTurtle
Regarding the custom partition this is or could be a problem for us now and in the future and may require further investigation. The cm sprout branch has the modem.img in the (normal place /system/etc/firmware) but as you say ours is in the custom partition which is probably to protect it from bad /system flashes
Thing is I see no normal type link to it in the /system/etc/firmware so it must be linked some other way which may explain why all my port attempts failed as none of them used a custom partition (Asus_X002)
Click to expand...
Click to collapse
The partition is symlinked from .../by-name/custom (which is symlinked by the kernel from dev/block/mmcblk0p12) to /dev/customimg which is mouned after an e2fsck to /custom. /custom isn't linked to /system, it's just added to the global environment (init.environ.rc), will need to check on the environ, I'm on flyme and it has /custom/lib added to the library path (which doesn't exist).
HypoTurtle said:
The partition is symlinked from .../by-name/custom (which is symlinked by the kernel from dev/block/mmcblk0p12) to /dev/customimg which is mouned after an e2fsck to /custom. /custom isn't linked to /system, it's just added to the global environment (init.environ.rc), will need to check on the environ, I'm on flyme and it has /custom/lib added to the library path (which doesn't exist).
Click to expand...
Click to collapse
Haha thanks that explains a lot of weird things perfectly. :good:
What's the problem or what is the issue here.
Mediatek compiling guide ( by masterawesome ) that you have linked to is not actually practically this mtk kernel is done and is just way too complicatedly explained.
There is no defconfig stuff or pulling config.gz from phone in mtk. In this new source its just simple. Set up your toolchain path. Execute the makeMtk followed by the project no u want. Get zImage and patch it for mtk header and merge it with stock ramdisk. For this newer mtk chipsets repack has an extra stuff where u have to be careful of kernel command line parameters.
That's it the kernel stuff in mtk
I will take NO RESPONSABILITY for any damage on any device, so be really cautious about what you do with the recovery.
Here we are again!
In my last post i explained how to get in Fastboot mode, now here we are again to take advantage of that situation, and open the device to further development.
First of all, on my github ( https://github.com/Algesat/BladeApex2 ), you can download the sources, the build files and the compiled files, so not only developers with a certain level of knowledge can "play" with this files (remember to do a make distclean before recompiling it if you dont use the correct toolchain ( https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7 ), or you modify something on the sources.
In other hand, ill bring you a full version of the TWRP Recovery, (made by Dees_Troy and me).
https://dl.twrp.me/P892E10/
In Dees_Troy's github you can download the sources if you wanna compile it yourself:
https://github.com/Dees-Troy/android_device_zte_P892E10
Yours.
Algesat.
P.S: Thanks to Dees_Troy for his great help
Good job bro, finally someone works on it
I think its time to ask for a forum for this device, i suppose now the development on this device will be boosted and roms will appear.
Thanks.
Algesat
Algesat said:
I think its time to ask for a forum for this device, i suppose now the development on this device will be boosted and roms will appear.
Thanks.
Algesat
Click to expand...
Click to collapse
Yep, you right! :fingers-crossed:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Features::
Build based on latest CM13.0 and TWRP source.
Workaround on touchscreen. Touch screen fully works! No matter what your device's version is.
All function in a normal TWRP
Changelog:
15/7/11
First release
15/10/24
Sync latest TWRP source
Update prebuilt kernel from beta357
Fix a typo: nz510j, now it can be used to flash an official release
15/11/21
Sync latest TWRP source
Build kernel from new source
Add support for F2FS
16/03/12
Sync latest TWRP source (TWRP 3.0)
Use new kernel align with CM13
16/08/05
Sync latest TWRP source
Use new kernel align with CM13
Restructure device tree
Download link::
https://s.basketbuild.com/filedl/devs?dev=dianlujitao&dl=dianlujitao/nx510j/twrp_nx510j_v5_f2fs_dianlujitao.img
Install guide::
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Run "fastboot -i 0x19d2 flash recovery twrp_nx510j_v5_f2fs_dianlujitao.img"
4. Reboot
Source code::
https://github.com/MoKee/android_bootable_recovery-twrp/tree/mkm
https://github.com/dianlujitao/android_device_zte_nx510j/tree/twrp
XDA:DevDB Information
TWRP, Tool/Utility for all devices (see above for details)
Contributors
dianlujitao
Version Information
Status: Stable
Current Stable Version: 5
Stable Release Date: 2016-08-05
Created 2015-07-11
Last Updated 2016-08-04
how to install this .img?
Hi. Can you make a build for nx511j (z9 mini)?
djbosanac said:
how to install this .img?
Click to expand...
Click to collapse
I've added a simple install guide
How do we boot into recovery? I flashed the recovery but when I try to boot into recovery from fastboot it always boots to the main OS
Can't boot in this recovery after installing it.
Sent from my NX510J using XDA Free mobile app
Hi, it will works with newest ZTE firmware 3.06 ? or maybe someone has a newest version ? THX
Can not install official updates/ROMs. There is a misspelling in default.prop:
ro.product.name=nz510j
Must be:
ro.product.name=nx510j
5[Strogino] said:
Can not install official updates/ROMs. There is a misspelling in default.prop:
ro.product.name=nz510j
Must be:
ro.product.name=nx510j
Click to expand...
Click to collapse
Will be fixed as long as I have time, now I'm too busy
How long will this command take? All I get is < waiting for device >
Had to do this first:
- Connect phone while normally booted
- Run the installer that is automatically mounted on windows
- click 7 times the buildnumber in "about phone" to enable developer options
- enable usb debugging in developer options
Edit:
Installed your cyanogenmod build, but still have a problem. Cant reboot to recovery. What I have to do is get into fastboot, flash TWRP, reboot to recovery.
Edit2:
I can boot to recovery, only if usb is connected.
5[Strogino] said:
Can not install official updates/ROMs. There is a misspelling in default.prop:
ro.product.name=nz510j
Must be:
ro.product.name=nx510j
Click to expand...
Click to collapse
EDIT: The following isnt needed anymore as of the latest update!
To bypass this problem I use another TWRP now from here: http://www.androidiani.com/forum/mo...3-z9-max-lollipop-5-0-2-cuoco92-firmware.html
Download: https://mega.nz/#!OgYljCAa!eH54Uc7Tdld1N3Oz3L4TIr1uiBx6EZSILf67MFgpgJk"
Translated:
- Install the drivers ( http://pdanet.co/a/ )
- Unzip the ZIP
- Start the file "Install_TOOL.exe"
- Coose 2: "Install TWRP 2.8.6.0"
- Wait for restart to the new TWRP (in nubia style!)
Click to expand...
Click to collapse
jogai said:
To bypass this problem I use another TWRP now from here: http://www.androidiani.com/forum/mo...3-z9-max-lollipop-5-0-2-cuoco92-firmware.html
Download: https://mega.nz/#!OgYljCAa!eH54Uc7Tdld1N3Oz3L4TIr1uiBx6EZSILf67MFgpgJk"
Translated:
Click to expand...
Click to collapse
A friend of mine received this smartphone this week and he's unable to get twrp installed, tried many different methods, but apparently the touchscreen doesn't work when he needs to press an option. He did it through Win XP, maybe that's the reason why... I'm nervous as well as I ordered the phone as well through the same seller...
I really don't know why it's not working...
jogai said:
To bypass this problem I use another TWRP now from here: http://www.androidiani.com/forum/mo...3-z9-max-lollipop-5-0-2-cuoco92-firmware.html
Download: https://mega.nz/#!OgYljCAa!eH54Uc7Tdld1N3Oz3L4TIr1uiBx6EZSILf67MFgpgJk"
Translated:
Click to expand...
Click to collapse
already fixed
K3nshiro said:
A friend of mine received this smartphone this week and he's unable to get twrp installed, tried many different methods, but apparently the touchscreen doesn't work when he needs to press an option. He did it through Win XP, maybe that's the reason why... I'm nervous as well as I ordered the phone as well through the same seller...
I really don't know why it's not working...
Click to expand...
Click to collapse
Try my latest release,
and plz tell me which of the following path exists on your friend's phone:
/sys/bus/i2c/devices/2-004a
/sys/bus/i2c/devices/2-005d
/sys/bus/i2c/devices/2-0024
dianlujitao said:
Try my latest release,
and plz tell me which of the following path exists on your friend's phone:
/sys/bus/i2c/devices/2-004a
/sys/bus/i2c/devices/2-005d
/sys/bus/i2c/devices/2-0024
Click to expand...
Click to collapse
Thank you dianlujitao,
I hadn't seen that you had already fixed the typo, sorry for that.
I've told my friend about the new TWRP and asked him about the path - if he asks me where to find this on the phone, where should he look for, or can this be found through Windows as well ?
I'll keep you informed about my findings.
Thanks again,
Ken
K3nshiro said:
Thank you dianlujitao,
I hadn't seen that you had already fixed the typo, sorry for that.
I've told my friend about the new TWRP and asked him about the path - if he asks me where to find this on the phone, where should he look for, or can this be found through Windows as well ?
I'll keep you informed about my findings.
Thanks again,
Ken
Click to expand...
Click to collapse
Can be found even through CM file manager.
Run adb shell on computer, then use ls to find it
Hey!
I got it working on my Z9 max
Didn't work though through root path on internal storage, had to run it through another path on my pc.
Fiddling around a bit these days before I try out your Cyanogen Rom.
Btw, do you have a proper link (nubia official) for the download of the new Nubia UI?
I tried to locate it on nubia.cn, but I'm unable to find it...
I'd really appreciate if you could reveal the link
Cheers
Sent from my NX510J using Tapatalk
K3nshiro said:
Hey!
I got it working on my Z9 max
Didn't work though through root path on internal storage, had to run it through another path on my pc.
Fiddling around a bit these days before I try out your Cyanogen Rom.
Btw, do you have a proper link (nubia official) for the download of the new Nubia UI?
I tried to locate it on nubia.cn, but I'm unable to find it...
I'd really appreciate if you could reveal the link
Cheers
Sent from my NX510J using Tapatalk
Click to expand...
Click to collapse
http://bbs.nubia.cn/thread-554721-1-1.html
Latest nubia ui v3.62
dianlujitao said:
http://bbs.nubia.cn/thread-554721-1-1.html
Latest nubia ui v3.62
Click to expand...
Click to collapse
Thanks a ton dianlujitao,
Sorry for late reply, I'm currently on vacation, I'll do it when I return.
I got a couple of questions regarding this. If you can and if you want, I'd appreciate if you could give them a look, no hurry. I'm very well aware that this is your time, and I have no right to request anything.
I just don't want to brick the phone
1. Can I use your Twrp to make a Nandroid backup?
2. Can I use your Twrp to flash it (The Brush file) or should I do it with default recovery?
3. As per instructions, it says that I should unroot it and reset to factory values.... Is this necessary?
4. Where does your Twrp save the backup, to internal memory or SD card?
Last but not least, I have to say that so far the phone has impressed me, specially the camera, awesome pics.
I let the device store them on the SD card, and sometimes I have seen (4 times to be precise) that the pic is corrupt. Would you know if this is fault of the phone or of the SD card?
Cheers,
Ken
P. D. Do you have a PayPal account for donations setup for instance?
Sent from my NX510J using Tapatalk
K3nshiro said:
Thanks a ton dianlujitao,
Sorry for late reply, I'm currently on vacation, I'll do it when I return.
I got a couple of questions regarding this. If you can and if you want, I'd appreciate if you could give them a look, no hurry. I'm very well aware that this is your time, and I have no right to request anything.
I just don't want to brick the phone
1. Can I use your Twrp to make a Nandroid backup?
2. Can I use your Twrp to flash it (The Brush file) or should I do it with default recovery?
3. As per instructions, it says that I should unroot it and reset to factory values.... Is this necessary?
4. Where does your Twrp save the backup, to internal memory or SD card?
Last but not least, I have to say that so far the phone has impressed me, specially the camera, awesome pics.
I let the device store them on the SD card, and sometimes I have seen (4 times to be precise) that the pic is corrupt. Would you know if this is fault of the phone or of the SD card?
Cheers,
Ken
P. D. Do you have a PayPal account for donations setup for instance?
Sent from my NX510J using Tapatalk
Click to expand...
Click to collapse
1. yes, but system,boot and data is enough
2. yes
3. no
4. it's up to u
5. no idea
6. I forgot my paypal passward and passward reset answer, so...
i need help my tablet is so slow with the default software , i deleted as much bloatware as i could but nothing much , soo i want to find a custom recovery to install custom ROM , my tablets model number is Beauty HD Quad Core , on the aida 64 it says:
Manufacturer: eSTAR
model: Beauty HD Quad Core
brand: eSTAR
Device: MID7188 (behind the tablet it says Model eSTAR BEAUTY HD QUAD CORE [MID 7188R]
i think thats enough info for it , what can i do? please help
Don't think you'll find a Custom Recovery that is at 100% suitable to this tablet.
jwoegerbauer said:
Don't think you'll find a Custom Recovery that is at 100% suitable to this tablet.
Click to expand...
Click to collapse
i just want it to work
andreas_xs said:
i just want it to work
Click to expand...
Click to collapse
You may compile TWRP at your own.
Look inside here:
[GUIDE][NOOB FRIENDLY]How to compile TWRP from source step by step
Hi guys, Today because of the continuous requests of help to compile the TWRP on the developers' dedicated thread, I decided to write a guide for those who know very little about Linux and Android development but want to LEARN Initial...
forum.xda-developers.com
jwoegerbauer said:
You may compile TWRP at your own.
Look inside here:
[GUIDE][NOOB FRIENDLY]How to compile TWRP from source step by step
Hi guys, Today because of the continuous requests of help to compile the TWRP on the developers' dedicated thread, I decided to write a guide for those who know very little about Linux and Android development but want to LEARN Initial...
forum.xda-developers.com
Click to expand...
Click to collapse
ok ill try that thanks
andreas_xs said:
ok ill try that thanks
Click to expand...
Click to collapse
umm is there a video i could watch ?
jwoegerbauer said:
You may compile TWRP at your own.
Look inside here:
[GUIDE][NOOB FRIENDLY]How to compile TWRP from source step by step
Hi guys, Today because of the continuous requests of help to compile the TWRP on the developers' dedicated thread, I decided to write a guide for those who know very little about Linux and Android development but want to LEARN Initial...
forum.xda-developers.com
Click to expand...
Click to collapse
why isn't it as easy as on the pc ? on pc you just download the OS you want , you make it bootable with a program like rufus (in a usb drive) you plug the usb on the pc/laptop, you follow the instractions and done. on smartphones/ tablets its too complicated you have to download a custom recovery , and why every rom is not compatible with every smartphone/ tablet?
andreas_xs said:
why isn't it as easy as on the pc ? on pc you just download the OS you want , you make it bootable with a program like rufus (in a usb drive) you plug the usb on the pc/laptop, you follow the instractions and done. on smartphones/ tablets its too complicated you have to download a custom recovery , and why every rom is not compatible with every smartphone/ tablet?
Click to expand...
Click to collapse
As with the Android ROM it consists not only of the operating system software ( bootloader, Linux kernel & Android Framework ) but also of a wealth of drivers & APIs, what are tailored to Android device's hardware and its interfaces. Hence it should be clear that not every available Android ROM will flawlessly run on every Android device: thousands of different brands and models of Android devices are on the market, all have different features.
Installing an incompatible ROM, in the best case, makes components of your Android device unavailable ( they are simply not working ), in the worst case, you might "softbrick" the Android device ( it won't even start up ).
jwoegerbauer said:
As with the Android ROM it consists not only of the operating system software ( bootloader, Linux kernel & Android Framework ) but also of a wealth of drivers & APIs, what are tailored to Android device's hardware and its interfaces. Hence it should be clear that not every available Android ROM will flawlessly run on every Android device: thousands of different brands and models of Android devices are on the market, all have different features.
Installing an incompatible ROM, in the best case, makes components of your Android device unavailable ( they are simply not working ), in the worst case, you might "softbrick" the Android device ( it won't even start up , thanks
Click to expand...
Click to collapse
jwoegerbauer said:
As with the Android ROM it consists not only of the operating system software ( bootloader, Linux kernel & Android Framework ) but also of a wealth of drivers & APIs, what are tailored to Android device's hardware and its interfaces. Hence it should be clear that not every available Android ROM will flawlessly run on every Android device: thousands of different brands and models of Android devices are on the market, all have different features.
Installing an incompatible ROM, in the best case, makes components of your Android device unavailable ( they are simply not working ), in the worst case, you might "softbrick" the Android device ( it won't even start up ).
Click to expand...
Click to collapse
Οk, thank you , that's informative actually