Related
Just wanted to take the time to thank everyone here for all the useful information they provided. I spent a lot of time modifying the GT540, and had a lot of fun with it.
But it's time for an upgrade. I just ordered the Huawei U8800. From what I have read, it's basically a HTC Desire with the next generation processor and a TFT screen. It is also very reasonably priced. The Huawei U8800 recently got it's own section here at XDA, so I'm hoping for lots of development over there.
Also, lots of people in China know about XDA. I've meet a few people at my college in Xi'an, China who use XDA. So if the Chinese modders and developers get to work on the Huawei U8800, I can expect a lot of improvements for the phone.
Thanks everyone for your help.
How much did you buy it for? Does anyone you know have ideos x3? Can you rip the flash player from x3 and share it with us? (Not your model, the lesser x3)
Sent from my GT540 using XDA App
I bought it for 1550 RMB ($240 USD). You can buy them used 1250-1450 RMB ($190-$225 USD). I bought them in China off of TaoBao. I don't know what they cost elsewhere.
I originally wanted an HTC Desire (1900 RMB) or HTC Desire HD(2500 RMB), but they are a bit more expensive here. The U8800 basically gave me the Desire with the Desire HD's processor and GPU, which can be overclock up to 1.8 GHz.
I'll ask around if someone has an X3 (U8510, right?). I'll also ask around at some Chinese Android forums, after I find some. To rip the flash player it I would just copy the apk with root explorer or a back-up program, right? Is there something great about this flash player I should know about?
typci said:
I bought it for 1550 RMB ($240 USD). You can buy them used 1250-1450 RMB ($190-$225 USD). I bought them in China off of TaoBao. I don't know what they cost elsewhere.
I originally wanted an HTC Desire (1900 RMB) or HTC Desire HD(2500 RMB), but they are a bit more expensive here. The U8800 basically gave me the Desire with the Desire HD's processor and GPU, which can be overclock up to 1.8 GHz.
I'll ask around if someone has an X3 (U8510, right?). I'll also ask around at some Chinese Android forums, after I find some. To rip the flash player it I would just copy the apk with root explorer or a back-up program, right? Is there something great about this flash player I should know about?
Click to expand...
Click to collapse
Well, that's cool. Congrats with your new phone and do have fun hacking. xD
Ideos X3(U8510) supposedly has a Qualcomm MSM 7227 processor but it also boasts Adobe Flash 10.1. I do not know how this worked out. Qualcomm MSM 7227 is the same processor as in LG GT540. It's ARMv6. Am curious as to how X3 is running Flash 10.1 on ARMv6.
I don't have exact specs from an official source but if what I've heard is true, Flash 10.1 on X3 would work on other ARMv6 devices as well.
(Flash Lite is another alternative but Flash Lite depends on Sense architecture of HTC and would require a lot of tinkering to the ROM. Even after all the hacking, it'd still be Flash Lite and not Flash 10.1.)
I did some quick research on the Huawei U8510. It is quite strange.
Qualcomm MSM7227 600 MHz
256 MB RAM
Android 2.3 Gingerbread
Flash 10.1
How can the X3 it have Android 2.3 when the X5 only has Android 2.2? and with such little ram?
Anyway, leave it to the Chinese to do crazy things like that. You wouldn't believe some of the stuff they put on Chinese phones, and MP5 players (known to the rest of the world as MP4 players).
Knowing the Chinese, they probably put flash on there because they could, not because the phone will run it. You can see that the X3 has the same specifications as the GT540, minus the Android 2.3, so there is no telling if flash is running well.
Here is a link I found through Google for flash 10.1. It says it requires Android 2.2 or above, which the X3 has.
http://www.droid-life.com/2010/08/23/download-official-flash-10-1-v10-1-92-8-for-froyo-now/
I'll still ask some of my Chinese friends if any of them have the X3. I'll also go to the local computer mall and have a look at the X3. However, I wouldn't count on it being any different than the above download. Huawei is supposed to use "vanilla" or almost stock android, with little to no overlay or bloatware. I'd also like to see about porting the Android 2.3 to my X5.
typci said:
I did some quick research on the Huawei U8510. It is quite strange.
Qualcomm MSM7227 600 MHz
256 MB RAM
Android 2.3 Gingerbread
Flash 10.1
How can the X3 it have Android 2.3 when the X5 only has Android 2.2? and with such little ram?
Anyway, leave it to the Chinese to do crazy things like that. You wouldn't believe some of the stuff they put on Chinese phones, and MP5 players (known to the rest of the world as MP4 players).
Knowing the Chinese, they probably put flash on there because they could, not because the phone will run it. You can see that the X3 has the same specifications as the GT540, minus the Android 2.3, so there is no telling if flash is running well.
Here is a link I found through Google for flash 10.1. It says it requires Android 2.2 or above, which the X3 has.
http://www.droid-life.com/2010/08/23/download-official-flash-10-1-v10-1-92-8-for-froyo-now/
I'll still ask some of my Chinese friends if any of them have the X3. I'll also go to the local computer mall and have a look at the X3. However, I wouldn't count on it being any different than the above download. Huawei is supposed to use "vanilla" or almost stock android, with little to no overlay or bloatware. I'd also like to see about porting the Android 2.3 to my X5.
Click to expand...
Click to collapse
X3 was launched later than X5. That's why it has 2.3. Even G1 runs 2.3 and 3.0. Android has no hard set system requirements. Theoretically, any version of Android can be ported to any device.
The 2.3 doesn't have a lot of advantages over 2.2. The speed gain is very small.
I don't know how they put the Flash 10.1.
Flash 10.1 needs both 2.2/2.3(would work on 2.1 with some tinkering) and a ARMv7(or newer) CPU. The libflashplayer.so is compiled for ARMv7. However, someone who is good in programming could either wrap the libflashplayer.so in an emulation layer or could reverse engineer and recompile it so that it will work on ARMv6. It's not impossible but rather, it's really really hard. No one has done it so far.
Huawei is not exactly a sub-standard Chinese brand. It's a recognized brand. So, I wouldn't expect them to put a Flash Player that wouldn't work. Either the information we have about the CPU is wrong or the phone doesn't have Flash.
Since X5 is vanilla, am also expecting X3 to be vanilla which means, if it does have a working Flash 10.1 and it does run on MSM7227, the Flash 10.1 it has should run on GT540 and many other ARMv6 devices.
From pure curiosity last week I extracted flash 10.2's apk and found that it has a .lib file that could supposively be put in /system/lib with root explorer (permissions rw-r--r--) and install the apk with either push or install. That may work, it did with x-plane flight sim, which crashed before the lib push but after opened but was killed by android for it not having enough memory to run it. I will try it now and report my findings.
I will also post an extracted apk in 3 ways, 7zip, which just opens it, APKTOOL, which decodes the xmls, and dex2jar which takes the classes.dex and puts it into a jar file that can then be decoded by Java decopmiler
Quinny899 said:
From pure curiosity last week I extracted flash 10.2's apk and found that it has a .lib file that could supposively be put in /system/lib with root explorer (permissions rw-r--r--) and install the apk with either push or install. That may work, it did with x-plane flight sim, which crashed before the lib push but after opened but was killed by android for it not having enough memory to run it. I will try it now and report my findings.
I will also post an extracted apk in 3 ways, 7zip, which just opens it, APKTOOL, which decodes the xmls, and dex2jar which takes the classes.dex and puts it into a jar file that can then be decoded by Java decopmiler
Click to expand...
Click to collapse
The problem is not with the apks. The problem is with the lib file or more specifically libflashplayer.so. This file depends on ARMv7 architecture. So, if you want Flash 10.1/10.2 on ARMv6, you should be able to decompile the lib(.so) files and edit them to convert ARMv7 dependent code to ARMv6 compatible code and recompile it for ARMv6. Editing the apk is very easy but porting the .so(lib) file is very very hard.
nibras_reeza said:
The problem is not with the apks. The problem is with the lib file or more specifically libflashplayer.so. This file depends on ARMv7 architecture. So, if you want Flash 10.1/10.2 on ARMv6, you should be able to decompile the lib(.so) files and edit them to convert ARMv7 dependent code to ARMv6 compatible code and recompile it for ARMv6. Editing the apk is very easy but porting the .so(lib) file is very very hard.
Click to expand...
Click to collapse
There's more than just libflashplayer.so, there's also libstagefright_froyo.so, libstagefright_honeycomb.so and libysshared.so
Sent from my GT540 using XDA App
Quinny899 said:
There's more than just libflashplayer.so, there's also libstagefright_froyo.so, libstagefright_honeycomb.so and libysshared.so
Sent from my GT540 using XDA App
Click to expand...
Click to collapse
I'm not sure about other lib files but libflashplayer.so is the most important. If we can port it, at least Flash 10.1 would work.
I looked into finding a X3, it's most likely going to be pretty difficult. I couldn't find them at China Unicom, which is the store that sells the X5. Also, I couldn't find it online, except for 6 sellers which had it on Taobao. Normally, for any given phone model, there are at least 50-100 different sellers. Also, some of the sellers didn't have the specifications listed for the phone correctly.
Is the X3 officially released? If so, what cellphone provider has it?
typci said:
I looked into finding a X3, it's most likely going to be pretty difficult. I couldn't find them at China Unicom, which is the store that sells the X5. Also, I couldn't find it online, except for 6 sellers which had it on Taobao. Normally, for any given phone model, there are at least 50-100 different sellers. Also, some of the sellers didn't have the specifications listed for the phone correctly.
Is the X3 officially released? If so, what cellphone provider has it?
Click to expand...
Click to collapse
It's not released in US or Europe. I'm not sure about its official release in China. It was supposed to be released in Japan by SOFTBANK Mobile during the first week of May. I checked the Huawei site as well as SOFTBANK site but I couldn't find any references to X3.
I don't speak Japanese or Chinese without Google Translate. So, if I there is someone who is fluent in Japanese or Chinese, they could do two things,
1) You can contact the seller asking for the official driver/software download link or you can ask them to send you a copy via email. Most of the time, the software has an option to completely re-install the firmware(Recovery Phone in LG Mobile Phone Tools). If we could get hold of the firmware, most likely we would be able to extract the files we need from it.
2) Some of these online shops have a list of other people who bought the device. You could try messaging them for help. You could ask them to make a complete backup of the system.img with YaffsExpert or you could ask them to rip the apks with Root Explorer.
I checked the Engadget Hand-on review and the reviewer say that the device is MSM7227 and does play Flash. However, she also mentioned that the launcher was themed which means it might not be vanilla. Nonetheless, it is Adobe Flash 10.1. If this reaches the devs, they will be more interested in porting it.
I speak and read (for the most part) Chinese, however Google translate does alot to help. Ｉ also live in China.
The seller's on Taobao won't be able to provide software and firmware. They are lucky if they can get the specifications right. Also, I only saw one completed transaction for the X3 on taobao, but my Chinese is nowhere good enough to ask them for a back-up, or explain how to do it.
Huawei's website doesn't have the X3 listed as a model. All I could find about the X3 was the user manual, and an EU Declaration of Conformity.
If I can find the phone in a store, I can bring my laptop and say I want to test out the phone. They'll let me do just about anything, so long as I don't take the phone out of the store, if they think they may make a sale. And since my computer is in English, they won't know what I'm doing.
Right now, I don't think the X3 is released fully. The few sellers that have it on Taobao are most likely insiders. Someone send me a message when the X3 is released in China, and I'll see what I can do.
typci said:
I speak and read (for the most part) Chinese, however Google translate does alot to help. Ｉ also live in China.
The seller's on Taobao won't be able to provide software and firmware. They are lucky if they can get the specifications right. Also, I only saw one completed transaction for the X3 on taobao, but my Chinese is nowhere good enough to ask them for a back-up, or explain how to do it.
Huawei's website doesn't have the X3 listed as a model. All I could find about the X3 was the user manual, and an EU Declaration of Conformity.
If I can find the phone in a store, I can bring my laptop and say I want to test out the phone. They'll let me do just about anything, so long as I don't take the phone out of the store, if they think they may make a sale. And since my computer is in English, they won't know what I'm doing.
Right now, I don't think the X3 is released fully. The few sellers that have it on Taobao are most likely insiders. Someone send me a message when the X3 is released in China, and I'll see what I can do.
Click to expand...
Click to collapse
If you are lucky, the buyer might know English. xD
Please give me the link to the user guide. It might give us some insight about the specs.
I also learned from a Frash forum that the Adobe Flash 10 beta 1 which was released in a closed beta was ARMv6 compatible. I couldn't find the beta 1 apk anywhere though.
Adobe did work on ARMv6 and armeabi to begin with. They first demoed Flash on G1 but they never released the ARMv6 version. They dropped ARMv6 support because they couldn't improve performance well.
Huawei could be using the older beta or they might have developed their own port.
It seems that I have found an apk which when extracted in 7zip you look in its lib folder and it has only an armeabi folder, whereas the newer ones have a folder called armeabiv7 (arm v7). Perhaps this is what you are looking for?
We still need to do something to it, as it doesn't load flash.
To test whether we have flash go to http://www.codegeek.net/flash-version.php to check whether flash is installed & javascript enabled
The apk is attached
Source
Here you go:
Huawei U8510 X3 user manual
http://www.megaupload.com/?d=RTBQ9UFD
And the declaration of conformity is attached.
Quinny899 said:
It seems that I have found an apk which when extracted in 7zip you look in its lib folder and it has only an armeabi folder, whereas the newer ones have a folder called armeabiv7 (arm v7). Perhaps this is what you are looking for?
We still need to do something to it, as it doesn't load flash.
To test whether we have flash go to http://www.codegeek.net/flash-version.php to check whether flash is installed & javascript enabled
The apk is attached
Source
Click to expand...
Click to collapse
I'll check it soon in a while and post back. I extracted and did see armeabi folder but the version in the manifest doesn't seem to be a beta version.
armeabi can be v6 or v7 or generic. But, if it's not mentioned v7 and only armeabi, it most likely means that it could be generic but we do need to check. I'll check it in my phone.
I looked on the Huawei website for the firmware for the X3, and it's not out yet. When it does come out, we should be able to download it and extract out the flash player. It will most likely be the easiest way, since getting an actual X3 phone will be very difficult.
nibras_reeza said:
I'll check it soon in a while and post back. I extracted and did see armeabi folder but the version in the manifest doesn't seem to be a beta version.
armeabi can be v6 or v7 or generic. But, if it's not mentioned v7 and only armeabi, it most likely means that it could be generic but we do need to check. I'll check it in my phone.
Click to expand...
Click to collapse
Negative. It's not working.
typci said:
I looked on the Huawei website for the firmware for the X3, and it's not out yet. When it does come out, we should be able to download it and extract out the flash player. It will most likely be the easiest way, since getting an actual X3 phone will be very difficult.
Click to expand...
Click to collapse
That's true but you know "we are impatient" lol
Huawei might not release the firmware right after the phone is launched. The other thing is, they might not include the Flash Player in the public download link since although Android is Apache Lincensed, Flash Player is a closed and privately owned software by Adobe.
Hello Guys, i am here to share FF OS 1.4 build for ZTE Open
Much more stable than previous build.
Code:
[b]fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot flash cache ramdisk.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img[/b]
Link(updated)(22-09-14)
Thank you, I build fos myself and use your boot.img to flash my phone and now it boots well.
Could you explain which changes you have made to boot.img (and from which version)?
sekun said:
Thank you, I build fos myself and use your boot.img to flash my phone and now it boots well.
Could you explain which changes you have made to boot.img (and from which version)?
Click to expand...
Click to collapse
Which version you have compiled?
I didn't modified any boot.img
It was modified by someone else.
One More Question:
Did you ZTE Open hangs most of the times?
LinuxHolic said:
Which version you have compiled?
I didn't modified any boot.img
It was modified by someone else.
One More Question:
Did you ZTE Open hangs most of the times?
Click to expand...
Click to collapse
First I built from 1.1B02 to 1.3 and modified boot image according to this method [1] and made these modifications [2].
Next, built from 1.3 to 1.4 and used your boot img.
I've just tested 1.4 a little for now, and my zte open never hangs on 1.3.
[1] pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/#comment-1749
[2] bugzilla.mozilla.org/show_bug.cgi?id=965180#c9
sekun said:
First I built from 1.1B02 to 1.3 and modified boot image according to this method [1] and made these modifications [2].
Next, built from 1.3 to 1.4 and used your boot img.
I've just tested 1.4 a little for now, and my zte open never hangs on 1.3.
[1] pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/#comment-1749
[2] bugzilla.mozilla.org/show_bug.cgi?id=965180#c9
Click to expand...
Click to collapse
How did you installed 1.3 on you phone?
An .img files?
I wasn't able to install it on my phone. Tried with 3 different boot.img files
Thanks
LinuxHolic said:
How did you installed 1.3 on you phone?
An .img files?
I wasn't able to install it on my phone. Tried with 3 different boot.img files
Thanks
Click to expand...
Click to collapse
I've followed this tutorial [1] (built from 1.1 to 1.3, set BRANCH=v1.3 instead of v1.2 in the script) and have modified boot.img according to the 2 links [2] and [3] mentioned before.
[1] rowehl.com/blog/2013/10/24/firefoxos-1-dot-2-on-zte-open
[2] pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/#comment-1749
[3] bugzilla.mozilla.org/show_bug.cgi?id=965180#c9
sekun said:
I've followed this tutorial [1] (built from 1.1 to 1.3, set BRANCH=v1.3 instead of v1.2 in the script) and have modified boot.img according to the 2 links [2] and [3] mentioned before.
[1] rowehl.com/blog/2013/10/24/firefoxos-1-dot-2-on-zte-open
[2] pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/#comment-1749
[3] bugzilla.mozilla.org/show_bug.cgi?id=965180#c9
Click to expand...
Click to collapse
Can you give me the boot.img that you modified?
Thanks
LinuxHolic said:
Can you give me the boot.img that you modified?
Thanks
Click to expand...
Click to collapse
filebin.net/hfalt65z3o/boot-1.3.0.img
Works great!!!
LinuxHolic said:
Hello Guys, i am here to share FF OS 1.4 build for ZTE Open
This will work for all those who are having Bootloop issues while flashing Custom firmware
This build is compiled by someone so i take no credit for that. I'm just here to share that
Code:
[b]fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot flash cache ramdisk.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img[/b]
Click to expand...
Click to collapse
This image works great. At least as far as I have tested. Much snappier than 1.1, 1.2.
Could I ask (beg) you to compile a japanese version?
I'm giving a talk in Japan on JavaScript in about a month and I was hoping to show off this device.
I'd really appreciate it if you could do this for me.
I believe the information contained here may be helpful: ... 8 / I cannot post links as a newbie...
The comments at this bugzilla page explain how to add japanese text @ bugzilla mozilla org show_bug.cgi ? id=933252#c16
thank you so much!
asdf2a3 said:
This image works great. At least as far as I have tested. Much snappier than 1.1, 1.2.
Could I ask (beg) you to compile a japanese version?
I'm giving a talk in Japan on JavaScript in about a month and I was hoping to show off this device.
I'd really appreciate it if you could do this for me.
I believe the information contained here may be helpful: ... 8 / I cannot post links as a newbie...
The comments at this bugzilla page explain how to add japanese text @ bugzilla mozilla org show_bug.cgi ? id=933252#c16
thank you so much!
Click to expand...
Click to collapse
As i've already mentioned earlier that this build has been compiled by someone(not me)
Whoops
LinuxHolic said:
As i've already mentioned earlier that this build has been compiled by someone(not me)
Click to expand...
Click to collapse
:crying: My bad. I didn't read before I installed..
Could you point me in the right direction?
My own builds of b2g have been less than successful. The closest I've gotten was to get a unstable versions installed.
you may want to have a look at neuralassembly . blogspot . com (can't post links....) its in japanese and he explains how to build a japanese enabled version for Samsung Galaxy S3, you'll have to adapt that but i guess at least you will be able to read it without google translate
hope this is helpful to you.
linr76 said:
you may want to have a look at neuralassembly . blogspot . com (can't post links....) its in japanese and he explains how to build a japanese enabled version for Samsung Galaxy S3, you'll have to adapt that but i guess at least you will be able to read it without google translate
hope this is helpful to you.
Click to expand...
Click to collapse
Thanks, I can and have compiled for this device. The tricky parts are finding a version that is stable enough to use. And getting all of the right proprietary drivers. And there may be some other unknown(s) that I'm messing up. The version you've posted tells me the git version so that's 1 of the 2 major foreseeable obstacles.
Call me a conspiracy nut, but what's the big deal with closed source drivers on cell phones? So what if the public finds out how to write to a screen or send communication over the radio. Technically we can already write to small lcd screens with adrino parts and communicate over the air with shortwave. And yet every single phone out there is closed, even the Maemo was partially closed. I don't see any legitimate reason for this other than some giant conspiracy by large corporations. Either the ma bells don't want us using the air-waves for free or the governments of the world don't want us not being tracked. And I suppose it's a lot of both.
well, it was just an example on how to get japanese working on the device, not really a cookbook.
for the building i guess you should follow the instructions on Mozilla developer network.
they have a page dedicated to the ZTE Open.
mine will arrive maybe next week, so i cant really build yet, since the phone has to be connected for the build to proceed.
and i am fine with it being in english, even though my native language is german, but i always change the language to english (must be an IT thing with me)
linr76 said:
well, it was just an example on how to get japanese working on the device, not really a cookbook.
for the building i guess you should follow the instructions on Mozilla developer network.
they have a page dedicated to the ZTE Open.
mine will arrive maybe next week, so i cant really build yet, since the phone has to be connected for the build to proceed.
and i am fine with it being in english, even though my native language is german, but i always change the language to english (must be an IT thing with me)
Click to expand...
Click to collapse
There are some official ZTE versions out there with fastboot disabled. B06 is safe. But be careful to read about other user experiences before you upgrade.
asdf2a3 said:
There are some official ZTE versions out there with fastboot disabled. B06 is safe. But be careful to read about other user experiences before you upgrade.
Click to expand...
Click to collapse
As far as I am aware when ZTE first released the 1.1 Firefox OS update through their website it was released without fastboot enabled. This however was a mistake, so they took those files down and re-uploaded newly compiled versions of the same Firefox OS 1.1 but with fastboot enabled. :good:
thanks for the warnings, i have read about that and i think it is even stated on the MDN.
i think because of this there is also a lot of misunderstandings, as i do not think you need a hacked boot.img if your phone has fastboot enabled already.
well i guess i will find out when it arrives, as i want to upgrade at least to 1.3
this wont be my daily use device, i just want to see where FXOS stands and is developing to.
if i like it i guess i would go for a more mid-level device (like a Alcatel Fire E/S or the new not yet announced higher spec ZTE)
my only gripe here is that sony doesnt seem to move on and release their FXOS phone, and the support with Alcatel was a bit patchy so far from what you read.
it would be nice if all of the FXOS phones had the possibility to be used as Dev-devices.
Deleted
Hi,
Thanks for this release. Is all the device working ? I mean GPS, WiFi etc...
I'm new to Firefox OS, and I would like to install the latest fully functional release
Anyway thanks for your great work !
Nitroman70 said:
Hi,
Thanks for this release. Is all the device working ? I mean GPS, WiFi etc...
I'm new to Firefox OS, and I would like to install the latest fully functional release
Anyway thanks for your great work !
Click to expand...
Click to collapse
I am not the creator/uploader of this post but I have installed it multiple times and know a little bit about this kind of thing It is a pre-release version so it is far from being complete or "stable"... I would not suggest using this build for daily use as there is no guarentee everything will work correctly even if it does for someone else, but for testing and/or restoring a bricked (broken phone) it is perfect.
Asus zenfone selfie is a fairly brilliant device for its price point. has amazing camera, decent budget specs and also a whooping 13mp selfie camera with dual-tone flash!
but what bothers me the most is that my Asus Zenfone Selfie 32gb with 3gb ram is filled with bloatware around 1GB and even after uninstalling some of the thrid party apps, zenfone still has too many worthless apps. If only this has a vanilla stock android experience, this phone can easily give a decent competition to the One Plus 2.
I know it is too soon to ask for a ROM but is there anyway that we can get a root for this device.
I also have a zenfone selfie 32GB 3GB RAM
I tried to root With zenfone root kit, it worked on my Zenfone 5 and zenfone 2.
But on zenfone selfie, it didn't work. It says something about locked device..
I'm guessing because the bootloader is locked, and if there is a way to unlock bootloader I can root with zenfone root kit
Hope there is a way to root my Asus Zenfone Selfie soon.
And for Asus zenfone 2 laser ZE500KL???
kaushik.sripada said:
Asus zenfone selfie is a fairly brilliant device for its price point. has amazing camera, decent budget specs and also a whooping 13mp selfie camera with dual-tone flash!
but what bothers me the most is that my Asus Zenfone Selfie 32gb with 3gb ram is filled with bloatware around 1GB and even after uninstalling some of the thrid party apps, zenfone still has too many worthless apps. If only this has a vanilla stock android experience, this phone can easily give a decent competition to the One Plus 2.
I know it is too soon to ask for a ROM but is there anyway that we can get a root for this device.
Click to expand...
Click to collapse
Request ASUS ZENFONE SELFIE ROOT
I also have the Zenfone Selfie
I really need root access on this system
is there any development going on on this device or do we just have to get rid of it and take something else?
kaushik.sripada said:
is there any development going on on this device or do we just have to get rid of it and take something else?
Click to expand...
Click to collapse
so far as I know not ..
dave il barbaro said:
And for Asus zenfone 2 laser ZE500KL???
Click to expand...
Click to collapse
+1
I'm also waiting for a root method it.
I'm trying various methods to open the bootloader , but it still fails but found that there is a possibility adding those 4 lines to bulid.prop
ro.frp.pst=true
ro.secure=0
ro.debuggable=1
persist.service.adb.enable=1
ro.frp.pst=true / adds oem unlock the options developers
My suggestion would be an experienced programmer , change the ROM available on the website of the manufacturer and insert the build.prop commands , then we make the flash or sideload via fastboot
zezinhocrack said:
I'm trying various methods to open the bootloader , but it still fails but found that there is a possibility adding those 4 lines to bulid.prop
ro.frp.pst=true
ro.secure=0
ro.debuggable=1
persist.service.adb.enable=1
ro.frp.pst=true / adds oem unlock the options developers
My suggestion would be an experienced programmer , change the ROM available on the website of the manufacturer and insert the build.prop commands , then we make the flash or sideload via fastboot
Click to expand...
Click to collapse
So programmers XDA Forum ..
Can anyone give us a hand ..
Mandrakerj said:
So programmers XDA Forum ..
Can anyone give us a hand ..
Click to expand...
Click to collapse
Can I use my device as a test platform !!
zezinhocrack said:
Can I use my device as a test platform !!
Click to expand...
Click to collapse
Mine too .. Can I use my device as Test Platform XDA
dave il barbaro said:
And for Asus zenfone 2 laser ZE500KL???
Click to expand...
Click to collapse
+1 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
This device was my take as it was cheaper and almost had mixed specs from the oneplus one and two (3gb ram, 1080p display, good battery, great cameras). if only we can get a root and recovery for this, we can do wonders. if someone would please help us @xda -developers this device would rock!
and also did anyone check out if there was any development on the asus forums?
I continue to study a way to root the device , now I turned my eyes to how the LG G3 is done , we know the security restrictions Lollipop and I have a real sense of how to root the ZD551KL .
The method used by the D855 , is to copy the file to a folder supersu tmp along with the modified boot.img , so it is possible to make the img flash with supersu scripts.
So we can use the same technique to the ZD551KL , but I need the help of an expert to move on.
I know that you must enter in init.rc the code snippet that will initializing rooting and that's the problem .
How and how this should be done ???
Varies for each device?
zezinhocrack said:
I continue to study a way to root the device , now I turned my eyes to how the LG G3 is done , we know the security restrictions Lollipop and I have a real sense of how to root the ZD551KL .
The method used by the D855 , is to copy the file to a folder supersu tmp along with the modified boot.img , so it is possible to make the img flash with supersu scripts.
So we can use the same technique to the ZD551KL , but I need the help of an expert to move on.
I know that you must enter in init.rc the code snippet that will initializing rooting and that's the problem .
How and how this should be done ???
Varies for each device?
Click to expand...
Click to collapse
I find amazing is that none of the Technical Forum XDA helps us respond or gives us attention.
You are striving very, sorry I do not have this expertise so I can help.
More'll cheer to appear an enlightened soul who can help us.
Who knows everything here is possible
We will not lose hope never ever .
Mandrakerj said:
I find amazing is that none of the Technical Forum XDA helps us respond or gives us attention.
You are striving very, sorry I do not have this expertise so I can help.
More'll cheer to appear an enlightened soul who can help us.
Who knows everything here is possible
We will not lose hope never ever .
Click to expand...
Click to collapse
I contacted chainfire , please ask if you can help in this endeavor , I am waiting for a response .
I did some more analysis is possible to have a positive result if you add the parameters I sent in the previous post , entering the default.prop , but when you repack the boot.img file loses 2K in size and this causes the device startup problems , I would be happy if some soul help us !!
zezinhocrack said:
I contacted chainfire , please ask if you can help in this endeavor , I am waiting for a response .
I did some more analysis is possible to have a positive result if you add the parameters I sent in the previous post , entering the default.prop , but when you repack the boot.img file loses 2K in size and this causes the device startup problems , I would be happy if some soul help us !!
Click to expand...
Click to collapse
I sent a message to the Shakalaka many days ago.
Plus it today did not answer.
Let's see if Chainfire will help us
I'll be cheering apar figure out a way to Root in Zenfone Selfie.
I am preparing my laptop with ubuntu 14 , I will continue persisting .....
zezinhocrack said:
I am preparing my laptop with ubuntu 14 , I will continue persisting .....
Click to expand...
Click to collapse
God enlighten you so that we can find a way to root for Zenfone Selfie.
Because no one has presented ROOT solution for
Zenfone Selfie, Zenfone Laser, both with Snapdragon
Today I wanted to talk about porting current versions of TouchWiz from one device to another. This will be focused primarily on the Sprint network capability since that is my current carrier. But these same basic steps will apply for all porting of TouchWiz.
I know several people have ported roms but I first want to point out one important fact. There is ABSOLUTELY no "guide" that can help you port TouchWiz roms successfully. Period. Any "guide" thread that you may find is completely useless and is isn't even close to touching on the key components of today's porting methods. So don't waste your time reading guides because they are very outdated and irrelevant today.
First things first... When deciding to port a Samsung Rom you need to understand that there are going to be different chipsets for the different device models used in other parts of the world. With this in mind you need to choose software that was originally designed for the same similar cpu whether it be Exynos or Qualcomm. This makes a huge difference when it comes to cpu configs that will best support your device's cpu. If you try to port an Exynos rom to work on a Qualcomm device then expect to have to do a lot more work in framework, etc.
GSM vs CDMA is another very important part of the porting process. When possible, ALWAYS choose software that supports your specific carrier and service type/technology!!! If you are on a GSM network then choose a GSM rom and same for CDMA. However CDMA technology here in the US is a bit different from other countries in regards to how it is setup in the software. Each CDMA carrier will have it's own unique code inside system files. Simply replacing csc and other files will do NOTHING to fix this, leaving you with either no data services or improper generic data services. The only way to do this right is to either start with software for your specific carrier or manually modify these values in multiple files throughout framework and system using the correct values from software specific for your carrier. No exceptions.
The other thing. You ideally want to port the same Android version that is currently available for your specific device because the original kernel and libraries, etc need to support the version of Android in which you want to port. When porting you will be using most of your original software's bin files, kernel, etc... so these files need to be compatible with the version of Android you want to port. Very important!
I will not go into great details with smali modifications, etc because that is a whole different animal. This thread is a general breakdown of what is involved in the whole process. Porting a ROM such as the Note 7 software is no simple task, especially with so many unknown obstacles that must be discovered then remedied. You will need the right tools for the job before you even take on such a task. I'm talking about ApkTool, smali/baksmali, mad genius mentality, etc. Without the proper tools forget about it.
The main things that must be done for the rom to even boot, reside internally inside a few framework jar files. There will also be incompatible system files which must be removed and/or replaced with compatible versions that support your specific device/model. You also may need to make the rom support 32bit such is the case with the Note 4, since it is only 32 bit compatible. There can be no traces of 64bit libraries either inside the system apps or the library folder or else you will have issues. 32 bit devices cannot process 64 bit libraries, whether external or imbedded inside system apps. The one exception to this rule is when an app is multi-arch compatible which means the app can be installed on either 32 or 64 bit devices. In this case the 64 bit libs can remain although they will not be used since the 32 bit libs will be detected by the os. Thankfully 64 bit TouchWiz contains 99.9% of the necessary 32 bit libraries! So use them instead if your device is only compatible with 32 bit architecture.
There are several key Android/Samsung services that are not going to be compatible with other Samsung devices therefore one must identify these incompatible services and other methods in smali and either remove them or recode them in order for the rom to function in a way that is compatible with the device for which you will be running the software on. Sometimes you can simply replace services from your original device's software as long as it is compatible and from the same Android version, but not always.
There is NEVER going to be a set of instructions that will apply to all ROMS. Period. This stuff is always ever-changing with each update that Samsung releases. This is why there can be no accurate "guide" to porting TouchWiz. Whoever says otherwise is not knowledgeable on this stuff at all.
Once the framework files are prepared and rebuilt properly then you will need to have knowledge of the stock system apps and what role they play in the software. Most system apps are cross compatible but some are device and/or carrier specific and must either be removed or replaced in order for the rom to boot and run without a complete meltdown with continuous FC's. Then you have CSC (customer service codes). This plays a major role in how the software will be setup on initial rom setup. Each specific device model will have it's own unique CSC, however most of Samsung's current CSC is identical between the current available top tier devices such as the N4, N5, S7 and N7. BUT each device will have it's own unique "values" within multiple files in CSC. Some Samsung devices are compatible with features that other Samsung devices do not support. Therefore you must have knowledge of this and make the necessary edits in order for the software features to be setup correctly without major malfunctions. One wrong value can actually cause the rom to not boot. You will need experience with this as well.
Next you may need to slightly modify the kernel's ramdisk to support a couple of additional framework files which is the case with the N7 software and probably the N5 as well. It's just a matter of adding a few file names to a text file, save, then recompile the zimage and place the modified kernel inside your rom zip. These types of things must be discovered by trial & error by people who are knowledgeable and have experience porting roms. But it goes to show that these little things can determine a successful or failed port. You never know what can cause the rom to not boot. There's so many pieces to the puzzle when porting.
Moving on to the build.prop and updater-script. There MUST be a lot of edits done to the build.prop and the same principal applies here. You MUST edit the build.prop in order for it to support the software AND your specific device model, cpu, security features, etc, etc. This is an art folks. Again... there is no "guide" for doing this properly. You must possess the mental aptitude to tackle this stuff. It's not for normal people The updater-script is a VERY VERY important part of the rom porting process because it contains the permissions and symbolic links for all of the critical system files and folders. You must manually edit the updater-script so that it sets the proper permissions and symbolic links for the files that are used in the current software you are going to run. You cannot simply use a stock device updater-script straight out of the kitchen for your specific device. It will not work due to other versions of TouchWiz will likely have additional or different files and folders in the rom. This will take a LOT of time to go over everything and make sure you covered everything and properly setup the updater-script.
Next there is the process of replacing critical and device specific libraries and bin files as well as kernel modules. Generally for Samsung devices, system/bin folder must contain all of the original files from the original stock software for your specific device. You might need to add additional files from the software you are porting. The same applies to the system/lib/modules. These modules MUST come from your device's original software. The libraries are very tricky because not all libraries can be from either your original stock software nor from the software you are porting. Simply put, this is going to be the single most time consuming process with a ton of trial and error. You must figure out which lib files must be used from your original software and which libs must come from the new ported software. Good luck figuring this out! :laugh:
This pretty much covers the initial areas of the system software that must be manually modified in order for the rom to actually boot.
As you can see, there's a lot of trial and error with porting roms. Believe me. Other people who ported the early N7 and S7 port ROMs have done a LOT of work and surely they have a lot of trial and error. These early port dev's deserve a lot of credit for these early discoveries without a doubt. Without their original trials and errors & hard work, there would be no other port roms. They shared their knowledge and it was a group effort in the beginning. You guys know who you are! :highfive: Much Thanks to all of you who figured out framework issues etc in the early stages of current TouchWiz. I learned a lot in this process in which I have never shared with the public simply because there's no point in giving information that others can't use due to lack of experience. Hopefully some people will read this and better understand what goes into porting these ROMs. At a later dat, I may write up a more detailed "guide" on current TouchWiz IF I feel there is a need and there is enough people willing to step up and help out the community in the future. This is the way XDA works. You have to pass the torch to win the race. No one person can conquer the world. Teamwork is the key to success in everything you do. Remember this. Thanks for reading.
Wow, very nice write up. Thanks!
I would be interested in a more detailed guide if and when you get to it. I'm always looking to expand my know - how.
Many thanks! :highfive:
Thanks for the post....
but you did not go in to ROM porting much at all... I'd love to read a in depth view of the " copy and paste " dev .
tx_dbs_tx said:
This will be focused primarily on the Sprint network capability since that is my current carrier. But these same basic steps will apply for all porting of TouchWiz.
GSM vs CDMA is another very important part of the porting process. When possible, ALWAYS choose software that supports your specific carrier and service type/technology!!! If you are on a GSM network then choose a GSM rom and same for CDMA. However CDMA technology here in the US is a bit different from other countries in regards to how it is setup in the software. Each CDMA carrier will have it's own unique code inside system files. Simply replacing csc and other files will do NOTHING to fix this, leaving you with either no data services or improper generic data services. The only way to do this right is to either start with software for your specific carrier or manually modify these values in multiple files throughout framework and system using the correct values from software specific for your carrier. No exceptions.
The other thing. You ideally want to port the same Android version that is currently available for your specific device because the original kernel and libraries, etc need to support the version of Android in which you want to port. When porting you will be using most of your original software's bin files, kernel, etc... so these files need to be compatible with the version of Android you want to port. Very important!
Click to expand...
Click to collapse
This was great. It was exactly what I was looking for. Ive being working on porting a gsm rom to my device N900P. But the only thing Ive found is copy and paste. Trying to find something on cdma is even harder. Ive just download your Ultimate Hybrid N7 to see if can get a clue on where to start. Deodexing telephony-common should be enough? Where else should start looking? If you could point me a direction would be great. Thanks
triskaw said:
This was great. It was exactly what I was looking for. Ive being working on porting a gsm rom to my device N900P. But the only thing Ive found is copy and paste. Trying to find something on cdma is even harder. Ive just download your Ultimate Hybrid N7 to see if can get a clue on where to start. Deodexing telephony-common should be enough? Where else should start looking? If you could point me a direction would be great. Thanks
Click to expand...
Click to collapse
Sorry for the late reply. To be honest, porting a gsm rom to work on a U.S. cdma carrier is going to require massive work. Forget about it. Start your rom project with cdma compatible software and save yourself the trouble. You'll win the lottery before you get a gsm rom ported over to cdma. Copy and paste isn't going to scratch the surface. Why not port a factory Sprint ROM for your Sprint note 3? Such as the Sprint N7, N5, S7 edge? It is already setup to work on the sprint network. It would save you a lot of time and effort.
In this Article by Mishaal Rahman , we can understand why OnePlus and Nokia doesn't have treble support to their devices.
I open this thread to discuss about your opinions about how danger can be to create vendor partition outside system partition.
Tell us your opinion and how we can do it safely!
/vendor
FSadino said:
In this Article by Mishaal Rahman , we can understand why OnePlus and Nokia doesn't have treble support to their devices.
I open this thread to discuss about your opinions about how danger can be to create vendor partition outside system partition.
Tell us your opinion and how we can do it safely!
Click to expand...
Click to collapse
That partition is not accessible by the user or anyone else unless the phone is rooted, and it's no more dangerous than having the drivers and libraries in the system partition, OnePlus, as nothing more than a rebranded oppo, as well as Nokia, just don't want to put in the effort, Google has made it perfectly clear that treble is not optional, it is mandatory for devices shipping with Oreo and later, Nokia and OnePlus can do what they want with existing phones, but even they have no real choice that to support treble, unless of course that want to be stuck on phones shipping with nougat and maybe upgrading to Oreo, both of them will see the Android world passing them by and their implementations of Android will become more and more fragmented. Each to their own I suppose
Repartitioning a phone carries a certain risk, especially if it is done via OTA Update, but there are ways to do it and make it relatively safe...if you are willing to put in the work. I think that's the main point.
To me, it's much more interesting to see right now, how OEMs actually use Treble. They no longer have the excuses they used to, so someone like Sony should now be able to provide the Update to Android 8.1 within Days instead of Months...but will they actually do it?
The reasoning behind OnePlus deliberately not using Oreo on the 5T and not preplanning the extra partition...well, that tells it's own story. Not really that unexpected. Nokia though...I would have expected more from them, since they started with big promises about Stock Android and fast Updates, but so far very little has materialised...
I really think people are blowing this up far more then it needs to be. In the Google article it stated that even after the treble code is sent, the oems will still have to make their changes. So as far as I can see this will only matter to oems.
I expect to see many devices with day one 8.0 updates for a while.
Well, like I said, this will be the benchmark for Updates in the future. Since a new OS version can now boot on a phone without any big changes to the UI, Drivers or Apps, it SHOULD be far quicker. How much quicker will be interesting to see. Custom ROMs already show how fast the process can be...so... interesting times!
CommanderROR said:
Well, like I said, this will be the benchmark for Updates in the future. Since a new OS version can now boot on a phone without any big changes to the UI, Drivers or Apps, it SHOULD be far quicker. How much quicker will be interesting to see. Custom ROMs already show how fast the process can be...so... interesting times!
Click to expand...
Click to collapse
Yeah if you don't want any of the main features from the oem. Like Samsung cameras on aosp. Things like that.
As for faster updates. I doubt it. As now the oems will, have to do twice the work. Instead of adding their code to the stock frameworks. Now they will have to make completely new framework files to over write the default. Downloads will be a lot bigger now as well.
Hmm... that's not the way I understand Treble!
From what I've read, the OEM can basically exchange the OS Version without really touching much of their OEM UI...
The fact that Custom Roms are limited is mostly due to the fact, that devs don't have access to the OEM Sources, so they can only compile AOSP versions of Android...
CommanderROR said:
Hmm... that's not the way I understand Treble!
From what I've read, the OEM can basically exchange the OS Version without really touching much of their OEM UI...
The fact that Custom Roms are limited is mostly due to the fact, that devs don't have access to the OEM Sources, so they can only compile AOSP versions of Android...
Click to expand...
Click to collapse
And see that is why XDA articles are crap. The way OEMS roms have worked for years is that they replace and/or recode all of googles files. Now they will have to make even more. To over write them.
That is what you will get. Either AOSP or OEM. The aosp will not have access to the OEM code. Nor will OEM push their code to aosp for google to make things work right. This comes from the fact that OEMS dont write the drivers and code for alot of the hardware. They get that from others.
Just checked, my us997 LG G6 has a symlink for 'vendor', it points to 'system/vendor'... so no separate partition on the G6 either... I was hoping! alas.
Not unexpected...the G6 launched way before Treble was announced and hasn't been Updated to Oreo yet...
They should build a tool and require a wired connection to a pc to repartition and fallback just in case.
FWIW, I made patches to AOSP to be able to have a vendor partition WITHOUT needing to repartition, here:
https://github.com/phhusson/treble_experimentations/tree/master/no-vendor
The way it works, is it tells the kernel to look at the "system" partition, as if it was an hard-drive, to look for partition table, and then use partitions inside this fake hard-drive
Clever. Sell that idea to Oneplus and Nokia please...?
CommanderROR said:
Clever. Sell that idea to Oneplus and Nokia please...
Click to expand...
Click to collapse
I might be a good coder, but definitely not a good seller
phhusson said:
FWIW, I made patches to AOSP to be able to have a vendor partition WITHOUT needing to repartition, here:
https://github.com/phhusson/treble_experimentations/tree/master/no-vendor
The way it works, is it tells the kernel to look at the "system" partition, as if it was an hard-drive, to look for partition table, and then use partitions inside this fake hard-drive
Click to expand...
Click to collapse
Did you already tried this? I mean, I'm not developer and I can't understand the pros/cons about your patch but is extremely interesting!
@franciscofranco @eng.stk @Sultanxda @flar2 can you guys share your opinion about this? Thanks in advance
FSadino said:
Did you already tried this? I mean, I'm not developer and I can't understand the pros/cons about your patch but is extremely interesting!
Click to expand...
Click to collapse
Yup, actually my main testing device for my Treble ROM is a device using this.
Pros:
- doesn't need to repartition
- Easy to integrate
Cons are only for community rom devs:
- /system and /vendor are in read-only, even if dm-verity is disabled, the only way
- some TWRP change is required
- fastboot flashing will require to launch a s cript to merge system.img and vendor.img and flash both at the same time
Frankly, I'd guess OEMs had better to repartition. If you don't move partitions, only split system into system/vendor, and write the script with error-checking in mind, I really can't see how you would brick your device.
But this patch makes it possible to answer to OEMs saying they can't because of missing vendor partition
It will be interesting to see what happens, if a Device with strong XDA Community support like the OnePlus lineup can be "Trebleized" by the community and then supported more easily without help from the OEM that made it.
Following up here, very curious about where this is going.
Not a developer, but willing to test, my device is OP3T.
In light of a dev getting Treble support on the Redmi Note 4X, is it possible to get it on our devices too? I'm willing to test.
phhusson said:
FWIW, I made patches to AOSP to be able to have a vendor partition WITHOUT needing to repartition, here:
https://github.com/phhusson/treble_experimentations/tree/master/no-vendor
The way it works, is it tells the kernel to look at the "system" partition, as if it was an hard-drive, to look for partition table, and then use partitions inside this fake hard-drive
Click to expand...
Click to collapse
Does the Zenfone 4 use your patch actually? (didn't checked if sources are available yet)
I read a while back that first devices (or just one device?) is now project treble ready without vendor partition, not knowing you might have anything to do with it...
For reference:
https://www.androidpolice.com/2017/11/26/phones-updated-support-project-treble-continuously-updated/
Sent from my OnePlus 3T using XDA Labs