yashsingh1/xdaforums huggingface dataset:
[Firefox OS General] hevangel:
Hi,

I am new to Firefox OS, just got my ZTE Open last week. (used $10 from eBay)

I followed the instruction on the internet and XDA developers, compiled and flashed Firefox OS 2.1 into the ZTE Open.

Here is a link to the *.img files, feel free to play around with it.

https://drive.google.com/file/d/0B7HdrUmGwI8GRGlSZDdjMTBLMkk/edit?usp=sharing

2.1 seems running fine (so far so good), haven't seen it crashes since I flashed it this morning.

I can make phone call, surf the web, install new apps from the market, play mp3 and video files and the GPS is working.

It still has the same problems as the 1.3 build, the FM radio only works with speaker, the keyboard always display capital, recording video crashed the camera app after 2 seconds.

Here are the steps.

1. Update to official 1.1 release B06

2. Flash the 1.3 *.img built by linr76. (BTW, mine is a US version, but linr76's build is UK version, but it seems OK)

3. Flash my 2.1 *.img files. (pull the files from git on June 19, backup the system files from my phone on the 1.3 build)

BTW, I actually want to build 1.3 running BRANCH=1.3 VARIANT=user ./build.sh, but somehow the build script compiled 2.1 for me.
[Firefox OS General] Saijin_Naib:
Thanks for the v2.1 compile! I flashed it to my Open today as well.

I noticed the same issues as you, as well as some new ones:

"Home" orb light doesn't work

Screen timeout doesn't work properly (10 seconds no matter what you set it to)

However, it is really awesome of you to get this compile out there for people to test and use :)

I'm trying (unsuccessfully) to get my 1.4 user to compile.
[Firefox OS General] lissyx:
BRANCH=v1.3 instead. And use VARIANT=userdebug would be better since it gets you more or less the same as eng build but not enabled by default (root acces, etc.).

Regarding the bugs you are mentionning, I have no issue on other devices with FM Radio app. Keyboard displaying capital is not a bug, it's a change from UX. Video recording crashing is a legit bug however.
[Firefox OS General] Saijin_Naib:
That does not seem, to me, to be a change made for the better. The iOS keyboard has this same behavior, and it feels broken there as well.

What is the reasoning behind making the soft-keyboard case insensitive/static?

Hevangel, I issued my build with BRANCH=v1.4 VARIANT=userdebug ./build.sh and it build v2.1 for me as well.
[Firefox OS General] Saijin_Naib:
Hevangel,

I was informed by gerard-majax on the #b2g IRC channel that the reason you and I got the v2.1 build was because we issued the commands wrong. You need to set the BRANCH and VARIANT during the ./config.sh stage, not at the ./build.sh stage like you and I did.

I have successfully compiled the BRANCH=v1.4 VARIANT=userdebug 2014-06-19(svn) FirefoxOS and flashed it to my Open.

I ran ./flash.sh gaia && ./flash.sh gecko over my v1.2(zte) install and then rebooted and cleared the cache partition. This gives me a working, but highly unstable Inari.

Working:

Prox/light sensor

Light orb on Home button

Everything else except known limitations (FM only over speaker)

Not Working:

All apps are unstable

b2g will crash randomly

Link to compiled images:

http://1drv.ms/Vp6rz4
[Firefox OS General] LinuxHolic:
Why it still says 13./1.4 Prerelease?
[Firefox OS General] Saijin_Naib:
What do you mean?

If you want to change branches to build v2.1, you'll need to do this.

$home\username\B2G

git pull

BRANCH=master VARIANT=userdebug ./config.sh inari

./repo sync
[Firefox OS General] LinuxHolic:
No i mean if i install 1.3 or 1.2 on my phone than why it still says 1.2/1.3 Prerelease in the Device Information?
[Firefox OS General] Saijin_Naib:
OH! Any image compiled by a non-official source/partner will always be tagged Pre-Release. Quality control thing, I think? Not sure.
[Firefox OS General] LinuxHolic:
I can't download your v2.0 and 2.1 builds from One Drive :(
[Firefox OS General] elav:
Here you can find updated for 1.3 and 2.1 for ZTE Open images.

http://157.88.55.36:8080/job/master-inari/

http://157.88.55.36:8080/job/1.3-inari/

To update use these steps:

fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot flash boot ramdisk.img
fastboot flash system system.img
fastboot flash userdata userdata.img
[Firefox OS General] martin_s5670:
Please, which boot.img you used? And what partition for the ramdisk.img you has taken?
[Firefox OS General] TheEternalAbyss:
2.1 build and Keon??

Hello,

I have a ZTE Open and it's currently running Prerelease 1.3. I must say I'm quite happy with its performance and the bugs aren't crippling at all. I was thinking of upgrading to the 2.1 build from this thread. I was wondering though since I saw that there's a Geeksphone Keon 2.0 build. Since it looks exactly like a ZTE Open, the question popped into my head: "would that build work on a ZTE Open?". SO I turn that question over to the community here at XDADevelopers :)

Also, can I jump from 1.3 to 2.1? or would I have to do more of a 1.3 -> 1.4 -> 2.0 -> 2.1 sort of upgrade path?

Thanks!
[Firefox OS General] LinuxHolic:
No, Geeksphone Keon builds won't work on ZTE Open because both phones have different hardware :)

And yes you can directly jump from V1.3 to V2.1 :)

Precompiled images by Saijin_Naib of ZTE Open
[Firefox OS General] Saijin_Naib:
Please see my thread here: ZTE Open (Inari) Build Versions & Issues for an overview of the various issues & limitations I've encountered on each SVN compile version using my ZTE Open.

If you want full hardware functionality, you're stuck with the official ZTE ROMs only. If missing GPS & home orb light don't bother you, then you can pick and choose the other versions at will.
[Firefox OS General] TheEternalAbyss:
I'll definitely check them out. I don't use gps on my ZTE Open, so that is a non issue for me. In my 1.3 pre-release the home light works just fine. I don't think it would bother me much really. I'll just have to see. I may just wait for some new phones to come out before spending time on my poor broken ZTE Open lol

Thank you though for the info.
[Firefox OS General] Saijin_Naib:
No problem.

So far in my testing, v1.4 seems to be the most recent SVN that will have a working Home Orb light, but it was also far and away the most unstable version I have tested yet (surprisingly).
[Firefox OS General] mahdsip:
Flash steps

Hi!! Thank you very much for the information and the images, it really helps when you try to compile the source from a computer that is not debian 64...

I am in the way of flashing my ZTE open to 2.0 and i found in the Precompiled images by Saijin_Naib there is only a ramdisk,userdata and system images, ¿which are the correct steps to get the update? do i need any other boot.img or recovery.img that is not present in the repository?

BTW, i have tried to do just fastboot flash boot ramdisk.img as [MENTION=5564635]elav[/MENTION] said below but i get an error: FAILED (remote: image is not a boot image)

Thanks!!
[Firefox OS General] mahdsip:
Hi!! Thank you very much for the information and the images, it really helps when you try to compile the source from a computer that is not debian 64...

I am in the way of flashing my ZTE open to 2.0 and i found in the Precompiled images by Saijin_Naib there is only a ramdisk,userdata and system images, ¿which are the correct steps to get the update? do i need any other boot.img or recovery.img that is not present in the repository?

BTW, i have tried to do just fastboot flash boot ramdisk.img as [MENTION=5564635]elav[/MENTION] said below but i get an error: FAILED (remote: image is not a boot image)

Thanks!!
[Firefox OS General] LinuxHolic:
Connect your phone in USB Debugging Mode and enter the following commands:

adb reboot-bootloader

fastboot erase userdata

fastboot erase cache

fastboot flash system system.img

fastboot flash userdata userdata.img

fastboot flash cache ramdisk.img

And you're good to go ;)
[Firefox OS General] mahdsip:
Thanks LinuxHolic!! I have followed these steps and now the system gets stuck on boot image showing firefox logo and Firefox OS text and nothing else seems to happen, what can be causing this? I have been able to bring zte open back lo 1.1 oficial image from zte.

I am triying to update from FFOS1.1 working official image to 1.3 published images by Saijin_Naib.
[Firefox OS General] YemSalat:
You'll probably need the boot.img from 1.3 as well. I don't think this version works with the one in 1.1 update.
[Firefox OS General] mahdsip:
Thanks again for your help!! I finally get a ffos 1.3 boot image but after all flashing all images (boot,userdata,system) i just get a reboot loop....I guess it is my karma who is making me to keep stuck to 1.1. :)

Any idea?
[Firefox OS General] YemSalat:
That probably wasn't me who helped you previously, but you're welcome anyway )

It's weird that you can't flash the 1.3, are you using the version which linr76 provided?

You can try flashing my 2.1 build (link), it should work for 1.1.
[Firefox OS General] linr76:
my image is not available anymore because i stopped all work for the Open....
[Firefox OS General] YemSalat:
Is there any particular reason you decided not to work on it anymore? It sucks that building inari does not create any boot image whatsoever(
[Firefox OS General] linr76:
yes, frankly said Mozilla's and ZTE's stupiditiy. throwing a half-done device on the market and then stop supporting it immediately didn't get many points with me.
[Firefox OS General] enzobelmont:
is mozilla supporting this phone?

is mozilla supporting this phone?
[Firefox OS General] YemSalat:
Somewhat, it is considered a 'Tier 1' device, refered to as 'Inari' (there are other devices that fall into this category as well)

https://developer.mozilla.org/en-US/Firefox_OS/Firefox_OS_build_prerequisites

But you won't be able to get new builds unless you jaibreak it, cause ZTE stopped supporting this device shortly after release.
[Firefox OS General] linr76:
No.

the automatic updates have been disabled from FXOS 1.3 tree onwards. not sure if it still works on 1.2.

only "supported" FXOS on ZTE Open is 1.1 which is practically obsolete.

as you can see here, there are some people who try and "fix" this issue, there is even a 2.1 build available, but the hardware layer underneath (HAL/gonk) will stay forever at 1.1 level, which WILL prove a major dealbreaker down the road.

the only (and i mean that dead serious) FXOS device worth buying is the Flame (reference phone) but with 170 USD it's just way too expensive.

almost same specs ZTE Open C retails 99 USD and below, which is ok-ish, still too expensive imo.

the best way to get anything "supported" is if you check out feherneoh's thread about porting FXOS to different devices,

Sony is well supported by the community and you can self-build updates.
[Firefox OS General] mahdsip:
Thanks YemSalat!!! I finally could install your image so i am not in 1.1 anymore :) Your build is actually very cool, thanks for your images again. My next step will be triying to build it by myself, but my first attempts was also frustrating...we will see.. :)
[Firefox OS General] hevangel:
Somehow I found my old ZTE Open (1st gen) in a lost corner, so I decided to download the latest source from B2G, compile and flash the phone.

Now I have Firefox OS 3.0 running in the ZTE Open. 3.0 seems slightly faster than 2.2, but the radio app and video camera still do not work.

Other than that, I don't see any big difference between 3.0 and 2.2

Here is the link to the ROM image Enjoy.

https://drive.google.com/file/d/0B7HdrUmGwI8GRzR0Y25DZmlkZm8
[Firefox OS General] Saijin_Naib:
Are GPS and the Home button light still broken?
[Firefox OS General] hevangel:
Yeap. They are still broken.
[Firefox OS General] Ver Greeneyes:
How did you compile B2G 2.2 for inari at all? Every time I've tried I've run into bug 1121600 (can't link it because I'm a newbie here). The last time I tried to compile 3.0 it failed to flash the phone, so I figured that was the end of the line, but maybe that's been fixed. I wish they would branch to B2G 3.1 or something though, I don't want to use a pre-alpha on my phone (from what I've heard, they decided to only branch once a year because vendors complained about the frequency of updates).

Edit: I still get the same error trying to flash my phone with a local build of 3.0: "too many links". I need to try your build, but I have no idea why there would be a difference (and it's 2 months out of date at this point).

Edit2: I can flash the system.img you provided onto it without any problems! What the heck? I wonder if mine is too big: I noticed my system.img is 169.13MiB whereas yours is only 128.64MiB. The commandline I used was simply the following:

BRANCH=master VARIANT=user ./config.sh inari
BRANCH=master VARIANT=user ./build.sh

I think you omitted the 'VARIANT=user' part since the mochitest stuff is installed. I'll try omitting it too.

Edit3: Huh, so a 'VARIANT=eng' build using B2G tip and GCC 4.8 gives a system.img of 138.91MiB and a 'VARIANT=userdebug' build gives a system.img of 171.04MiB. I can flash the 'eng' variant onto my phone just fine! So that's that mystery at least partially solved - I wonder why it's bigger with the 'user' variants though.

Edit4: Except it doesn't detect my SIM card. Welp, back to the latest 2.1s it is.
[Firefox OS General] measle:
Downloaded TomTom app and after toggling location in settings a few times, GPS seems to be working!
[Firefox OS General] martin_s5670:
at <hevangel>

Somehow I found my old ZTE Open ...

I have flashed your system.img and userdata.img to get ffos 3.0, and it works well and indeed a good thing faster and smoother than 2.1.

During flashing "fastboot flash boot ramdisk.img" I got an error (no such partition). How can I flash your ramdisk, have I to repack the boot.img?

Thanks for compiling ffos 3.0., is there a way for you to integrate german language (new compiling?)?
[Firefox OS General] mahdsip:
Building FFOS code

Thanks a lot for posting Hevangel, currently using your build ;) i have been trying to compile source code for 3.0 with no success, i always get an error message

Blob setup script has changed, re-running

Backing up system partition to backup-inari

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

Pulling files from ../../../backup-inari

Pulling "libOmxAacDec.so"

Failed to pull libOmxAacDec.so. Giving up.

I am strictely following the steps from the mozilla devs website, but i am not able to move forward on this. My environment is Ubuntu 12.04 (as they recommend in the website), 40 free GB, java oracle 6, g++ and gcc 4.8.1 and android rules file working.

Any help?? Wich environment are you using??

Thanks!!
[Firefox OS General] autra:
The problem seems to be in whatever rom you have currently on your device, not in your environment. It tries to pull some blob from the device and fails to get what it expected to... That's all I can say with that.
[LG Optimus G (International)] optimus e977:
galera sou klinsmann tenho o lg optimus g...o problema e q eu briquei ele dai fui reinstala o software nele e dai o aparelho funcina bem so q a tela dele aparece tudo maus os led de brilho e de iluminação não acendem e vc só consegue ver contra a luz do sol..minha duvida e se isso e bug ou defeito no aparelho??? alguem pode mim ajudar?
[AT&T HTC One (M8)] robjbw:
I currently have my AT&T HTC One m8 bootloader unlocked and s-off. If I run the new full Ruu that was released, will it restore my device to stock? Will it relock my bootloader and turn s-on??? Or will it brick my One? I like to restore to stock so I can receive updates and I'm okay leaving the bootloader unlocked and keeping s-off. Thanks.
[AT&T HTC One (M8)] Android The Greek:
All it will do is write the stock Rom, firmware and recovery. You will still be locked/unlocked and soff
[AT&T HTC One (M8)] redpoint73:
Its safe to do. But IMO OTA updates don't belong on modded phones. You have the ability to install the same or better since you are BL unlocked and S-off. Going back to stock recovery and ROM is a step backwards.

This is my 4th HTC Android device, and the number of times I've installed an OTA update is ZERO.
[AT&T HTC One (M8)] Android The Greek:
Just out of curiosity what Rom do you run redpoint?
[AT&T HTC One (M8)] redpoint73:
I'm not a fan of the questions "what is your favorite ROM", "best ROM" etc. Its a highly personal choice, and what works for me, may not be the "best" others.

But I am currently on InsertCoin. IMO, almost anything is preferable to stock. InsertCoin happens to have the features I want, and not too much that I don't. I'm personally drawn to Sense-based ROMs, with stock look (but cleaned up and optimized). And I prefer international base to AT&T base.
[AT&T HTC One (M8)] Android The Greek:
No disrespect and I understand your response. Was just curious what you personally were running at the moment. I agree with your response on international base. Wish there was an ruu. Since my m7 I got spoiled flashing ruu.zips instead of roms.
[One (M7) Q&A, Help & Troubleshooting] alxr31:
I have been having camera issues with my phone and need to send it back to service centre in Cyprus.

This phone was Rooted, with S-Off and Unlocked in the Bootloader, I started researching today how to put it back to stock and in the process I have probably soft bricked my phone and have tried and exhausted everything to reverse the problem.

When I reboot into RUU and try to flash the RUU Zip M7_UL_JB_50_HTC_Europe_1.29.401.16_R_Radio_4A.14.3250.13_10.33.1150.01_release_318486_signed_2_4_decrypted.zip it fails:

C:\fastboot>fastboot flash zip M7RUU.zip

sending 'zip' (xxxx KB)...

OKAY [ xxx s]

writing 'zip'...

(bootloader) signature checking...

FAILED (remote: 12 signature verify fail)

finished. total time: xxxx s

I am not able to go into or load any recovery files either, I am only able to do fastboot commands and no adb commands.

I really have searched all over xda forums and have not found the answer.

My HTC currently will not boot and is able to fastboot only.

It is Displaying:

TAMPERED

RELOCKED

Security Warning

M7_UL PVT SHIP S-ON RH

HBOOT-1.44.0000

RADIO-1A.21.3263.04

OpenDSP-v32.120.274.0909

eMMC-boot

aPRIL 12 2013, 12:10:45:-1

FASTBOOT USB

ETC..

Here are the notes from fastboot get var

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.44.0000

(bootloader) version-baseband: 4A.21.3263.04

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 1.29.401.12

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno: FA34DW904422

(bootloader) imei: 354436050872454

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0710000

(bootloader) cidnum: HTC__001

(bootloader) battery-status: good

(bootloader) battery-voltage: 4191mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

getvar:all FAILED (status read failed (Too many links))

finished. total time: 0.044s

Please if you have any advice or assistance, I would love to hear it.

Thank you
[One (M7) Q&A, Help & Troubleshooting] clsA:
was your hboot always 1.44?

did you relock the bootloader to flash the RUU

and you can't use a decrypted RUU your not s-off .. find the RUU.exe for your phone
[One (M7) Q&A, Help & Troubleshooting] alxr31:
Hi,

And sorry for the truble!!

I was trying to use an RUU.exe to go back to stock for the repair sentre and someone sugested to flash 1.44 for it to work.

Also I was told to lock the bootloader and go back to S-onn. So I did and tried to use the exe and now Im stack..!
[One (M7) Q&A, Help & Troubleshooting] alxr31:
How can I find the correct RUU.exe for me with encryption? Any suggestions?
[One (M7) Q&A, Help & Troubleshooting] clsA:
What RUU.exe did you try ? any ruu above 1.29.401.12 should work

your on the correct hboot and relocked. Try http://www.androidruu.com/getdownlo...50.13_10.33.1150.01_release_316789_signed.zip

MD5: 533347483ae3040f85b8470112d7a7fb (Be sure and check it)
[One (M7) Q&A, Help & Troubleshooting] alxr31:
I couldnt find the correct one for sure!

I tried this with no luck. RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe

Downloading your suggestion, thanks alot.

Should I just connect my phone which is alreasdy in bootloader and run the exe from windows right? No cmd correct?

EDIT: I see its a zip so I will fastboot it from cmd.
[One (M7) Q&A, Help & Troubleshooting] clsA:
no it looks like the file i linked is the extracted rom.zip from a RUU

flash it with

fastboot oem rebootRUU

fastboot flash zip rom.zip

fastboot flash zip rom.zip <yes 2 times>

fastboot reboot
[One (M7) Q&A, Help & Troubleshooting] alxr31:
:::SOLVED:::

Please accept my best wishes for your help. My phone is alive again thanks to you.

All the best.
[One (M7) Q&A, Help & Troubleshooting] clsA:
Very Good ... if you have time could you edit your first post (advanced edit and add Solved to the title).
[iPAQ rw6828, XDA Atom General] JamesManios:
I've had the XDA2, XDA2s, XDA mini, and now, (cause my mini LCD is having a problem) I'm thinking of getting the Atom Exec, but after reading this forum, I'm a little worried.

The number 1 complaint is the humming, and the 2 complaint is bad sound phone quality.

I THINK I can live with 1 and 2 because my old Audiovox Thera made a humming and I could live with it, and I don’t use the phone that often but was wondering….

1} Does the humming go away if the screen is powered off? If you are on a phone call and are running an app like PhoneAlarm and it powers off the screen, do you STILL hear a humming?

2} Can anyone compare the phone quality to the iMate JAM for example, (or any of the above phones is it better/worse/same) ??

3} Are the buttons locked down, or can programs like AEBPlus override them and allow you to assign whatever you want?

4} Has anyone found a case like this for the Atom

http://www.expansys.ca/product.asp?code=121959&tab=1

Should I get a Jammin instead? Please steer me in the right direction.
[iPAQ rw6828, XDA Atom General] homer285:
Bro check out the Nokia N95 you will be surprised. I returned my Atom Exec last week for refund, it had been replaced twice and still the LCD squeals like crazy
[iPAQ rw6828, XDA Atom General] kropotov:
don't bye - too expensive
[iPAQ rw6828, XDA Atom General] JamesManios:
Thanks, I ended up buying the Jammin, just hearing/reading about too many problems with the Atom, too bad though.
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] tangoboyz:
What is your favorite app for app management, battery controlled ect.. GO!!
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] elliwigy:
greenify.. ftw
[Galaxy Tab 4 Q&A, Help & Troubleshooting] gch230:
Hey all,

I've got a Galaxy Tab 4 (SM-T330NU) that I've been attempting to run a Kali distribution on using Complete Linux Installer. I've rooted the device but can't seem to get the SE for Android to change to "Permissive" mode and allow me to run the bootscript.sh without kicking back a message saying "Operation not Permitted" when creating the loop device (mknod /dev/block/loop255: Operation not Permitted). I'm running Andriod 4.4.2 with kernel version 3.4.0-1337409. Any help would be great. I've searched all over and can't find anything that gets me to any point of success with this.

Thanks

-Geoff
[Galaxy Tab 4 Q&A, Help & Troubleshooting] ShinySide:
add setenforce 0 in the init.rc in the ramdisk at the bottom of this group

on property:init.svc.bootanim=stopped
restorecon /data/media
restorecon /data/media/obb
start auditd
start freshsebool

Should set to permissive. Theres an app or 2 also. Ive never used them tho
[Galaxy Tab 4 Q&A, Help & Troubleshooting] CrackSoft:
Full tutorial

A full tuto on how to install Kali Linux Nethunter On SM-T330NU will be nice
[Moto G Q&A, Help & Troubleshooting] Clarkiieh:
Have you got a custom kernel? What's your CPU clocked at.. Cant be a hardware issue if CM works fine... If in doubt Reflash..Restore.. Renew ;)