yashsingh1/xdaforums huggingface dataset:
[Desire HD Android Development] horsetastic:
Haha no worries I was only messing....

If it is true then we're laughing once more on DHD.....Can't wait for CM9 more then anything lol
[Desire HD Android Development] LuHe:
I just managed to build CM10 :-)

I still can't get to the UI but I think I know what the error is.

Can't work on it the next few hours (going to a birthday party), but I hope I can release a Alpha tomorrow.
[Desire HD Android Development] master reiki:
Can't wait! Best of luck! and have a nice time! peace.
[Desire HD Android Development] horsetastic:
CM10? CM9 has only just been released though?? :confused:
[Desire HD Android Development] trh1341:
when you post that it would be nice to know what the error is...
[Desire HD Android Development] MadMax:
CM10 is being working on right now, they are working on source so, they just have not released it for any phone yet
[Desire HD Android Development] DubelBoom:
"The new display drivers for Qualcomm devices on JB don't require any framework changes at all, they just work"

good news?
[Desire HD Android Development] Rabim:
Update for you guys

Jelly bean can not be compiled from source for us right now we have to many difficulties with the ace device tree we will see after HTC release the right tree for the inspire with the ics kernel.

I swear guys I had the help of lord and I tryed like 6 times and it takes like 3 hours for each new source to compile
[Desire HD Android Development] HTC_Phone:
No need to apologize man. Compiling JB was an immense task, and wasn't anywhere guaranteed to work

Sent from my Desire HD
[Desire HD Android Development] overjoy71:
No apologies needed, Rabim. Mate, We are just appreciative what you and the other developers have given, so not need to stress out.

Take your time, we need that when it is finish, you will release it. :o
[Desire HD Android Development] MadMax:
It might be hard, but if we all work together, we can make this a Jelly Bean Community rom where we all work together to get this working. I do know someone that might know why we can not get into the UI, but right now, he can not help because of personal reasons. I am going to try and chat with him tomorrow and see what we can do. It was hard to get ICS, it is going to be even harder because there is no leak yet, but i think we will be able to get something out of this
[Desire HD Android Development] Rabim:
Well I won't stop trying, just a measure of time
[Desire HD Android Development] c5satellite2:
ICS kernel in 4 days. Telus confirmed the 17th.
[Desire HD Android Development] LorD ClockaN:
3h?? What pc you have 486??

Don't do make clean after every build, only if you change build flags. Also install ccache app and look at my build script in vendor_lord how you can call to use ccache

I build ics without make clean in 15 mins..

With make clean 20-25 mins

The time rises if you change something drastically, like toolchain or webkit repo.. But the next build without make clean finishes again in 15mins..just enable ccache. It drastically improves build speed...

And I think that is buildable, but it won't work or boot...

Sent from One X supercharged with IceColdAOKP
[Desire HD Android Development] SupremeBeaver:
If true then huge news. Hopefully we get an early leak :P
[Desire HD Android Development] trh1341:
I hope you realize it means nothing aosp until they release the source I believe
[Desire HD Android Development] Rabim:
What the duck is going wrong with my pc
[Desire HD Android Development] MaR-V-iN:
You used -j X when compiling? what is you cpu usage while compiling?
[Desire HD Android Development] SupremeBeaver:
I could live with a sense ics Rom until source is released. But I'm sure some things could get hacked into aosp from the kernel.
[Desire HD Android Development] LorD ClockaN:
Well from ics htc kernel I would use gpu, audio and ts driver.. Or maybe whole base if it would work on AOSP.. BUT BUT BUT... Lately htc releases broken kernels with faulty code.. Se if not whole, we'll use part of it..

Sent from One X supercharged with IceColdAOKP
[Desire HD Android Development] DubelBoom:
and why not using also the camera drivers? :confused:

anyway, i still didn't get why its not possible to boot JB for now.

everything is possible :laugh:
[Desire HD Android Development] MusikMonk:
Edit:

This post wasn't supposed to be in this thread, and has started derailing the thread off topic.

Please ignore it and go here for discussions about the availability and release time of the ICS upgrade.

My sincere apologies to the OP.
[Desire HD Android Development] LorD ClockaN:
Because we need camera HAL lib also that is closely connected with frameworks_base and we know htc won't be releasing that code...

Sent from One X supercharged with IceColdAOKP
[Desire HD Android Development] choghok:
Desire HD has similar ian in some ways better hardware than incredible s, if that device inow has ICS then it is very strange to say oor erformance by DHD is the reason. I am also wondering why you do not use Incredible S ICS ROM for your work
[Desire HD Android Development] MadMax:
I do not believe this, other phones with same specs are getting ics, so I think it is something with telus.
[Desire HD Android Development] :
if this is true, DesireHD will be my last HTC.

Im really dissapointed, it cant be true.

I also had Sense 4.0 and it ran lagfree.
[Desire HD Android Development] ashu_crazyboy1994:
Let's not make this thread a flame war against htc

Sent from my Desire HD
[Desire HD Android Development] LorD ClockaN:
why would you hate HTC.. HTC Desire HD is more than 2 years old phone... why would they want to update an old phone and because of that it will lower sales of new phones
[Desire HD Android Development] DubelBoom:
"I/ServiceManager( 1215): service 'media.audio_flinger' died

I/ServiceManager( 1215): service 'media.player' died

I/ServiceManager( 1215): service 'media.camera' died

I/ServiceManager( 1215): service 'media.audio_policy' died"

i get these errors on any rom i try to port!!!

LC, you know how to fix it right? please help us..
[Desire HD Android Development] MaR-V-iN:
This is not the problem.

This occurs if zygote dies because of an error.
[Desire HD Android Development] :
LorD ClockaN

Its not even 2 years old.

it came out october 2010.

Update android 4.0 came out oct 2011.

every manufacturer, which are using android on their mobile phone, must update their phones 18 months long.

its in the agreements.

but htc didnt do it.

-> and on the new phones they go iphone way, with no more exchangable batterys and sd card interfaces

but i trusted HTC with updates, now they also failed at this point,

for me HTC is dead.
[Desire HD Android Development] johrie:
HTC has not failed at updating the Desire HD. Telus has. Everybody should stop ranting at HTC and try to help for once......
[Desire HD Android Development] perern:
The update agreement came after the Desire HD was released. Only phones released after this is going to be supported for 18 months
[Desire HD Android Development] Madaz2:
so its 3 months away from being 2 years old friken get a grip man let me call the wahmbulance for you

and i think you getting manufacturing agreements and service providers mixed up

sometimes i think we would be better off without users like you in the community, all the best when you get an iPhail
[Desire HD Android Development] paulb_nl:
Can you post the link of your build?

You should probably create your own thread so there won't be any clutter.
[Desire HD Android Development] Madaz2:
^^ keep all the constructive building in one place i say
[HTC One X] cropcircle:
I think the camera on the HOX is quite prone to scratches due to the way it protrudes from the phone's back.

I don't really like screen protectors but I got one with the Nillkin cover.

I decided to make a camera protector.

I cut a circle from the screen protector. I started with a circle larger than the camera lens and then started trimming it, a little bit every time. Each trim I measured it against the camera until it fitted.

All this time I kept the film on both sides of the screen protector, and always remember which side is 1 and which is 2.

After I finished trimming, I took film No. 1 off, put the circle im place and removed film No. 2.

Now I have a protecting cover to the camera lens. :D
[HTC One X] naveen94:
Does it mess up the pictures in any way? Do you have before and after pictures by any chance?
[HTC One X] cropcircle:
The protector is very clear. I don't see any difference in the pictures. I don't have any before and after.
[HTC One X] jacobgong:
Screen protectors are not desinged with optical performance in mind because they are really close to the screen and distortions will be minimal. But I don't think putting one on your lens is such a good idea, you might not notice anything because the HOX isn't a DSLR, but still, what's the point if you're using an image quality reducing device to protect it from potential image quality reducing damages?
[HTC One X] Crabitpig:
risky

Because I had to open my phone to fix my WiFi antenna I removed the lens and lay a circle of unsoldered solder in the lens housing then put the lens on top of it so now it sits about 3-4mm inset inside rather than being flush.I wouldn't recommend you go around opening your phones unless you know what your doing tho because I wish I hadn't as I damaged my volume up ribbon
[Galaxy S III Q&A, (US Carriers)] jamcar:
when i make a flashable .zip are the update binaries different? what about the partitions are they different?
[Droid Pro General] BlackFire27:
Move my post if you feel the need. I hate picking forums. Anyways. I have a XPRT from boost mobile running android 2.3.5 and I have been working for a few days to no avail in any vulnerabilities to rooting. Searching for users with same model and objective?
[Droid Pro General] BlackFire27:
Anyone with the same phone please post or PM me.
[Droid Pro General] BlackFire27:
Anybody? Seriously?
[Droid Pro General] BlackFire27:
Almost 300 views and no responses? Anyone have the same model and want to collaborate?
[Droid Pro General] nyxclusive1:
I would really like to see some type of update this is crazy that no one has done anything with this system yet. :(
[Droid Pro General] BlackFire27:
You have the the same model and carrier right? :D
[Droid Pro General] jklung84:
There is currently no way to root the Boost Mobile version of the XPRT at the moment. I looked around and tried the .zip file from sd and it bricked. I have talked to numerous people who tried the Sprint .SBF which bricked the system to. Right now you will just have to sit back and wait and see if someone comes up with something. Sorry for the bad news. :(
[Droid Pro General] BlackFire27:
Well that sucks ._. I do believe that a heavy amount of editing was done to the software and firmware by Boost. But this isn't bad news. Its actually a huge relief that finally I've gotten some feedback. We need a small community of people wishing to root this phone. Developer or not.
[Droid Pro General] jklung84:
Well I would love to just get a stock sbf so I can get mine working again lol.

Yes, rooting the boost version would be great, they just have so many restrictions on the phone. No hotspot, tethering is very limited, Hoping someone will find something soon.
[Droid Pro General] BlackFire27:
This is actually my first Motorola phone. Lol. I normally used HTCs beforehand. Would you be so kind as to explain what an SBF is and where they come from?
[Droid Pro General] jklung84:
An SBF ( SYSTEM BOOT FILE) file from what I gather is the original Image of the Phone. It's kind of like if you are running a windows computer you need a Windows image to run the operating system. The same is true for a cell phone. The only place to get them is have them leaked from Motorola Techs. Each tech has different level access to be able to work on your phone.

A normal tech has Level 1 and Level 2 access which can look at your phone and figure out what is wrong. The "head Motorola Techs" have Level 3 and Level 4 access and they are the ones who actually can pull the files ( SBF ) and do the reflashing and other needed services.

This may not be totally accurate but it is what I have put together from the massive amount of research and reading I have done on these phones. If anyone has anything to add or correct please do because I don't want to give bad information. =/

I have currently been browsing around a lot, and trying to figure out this development thing. I am also reading currently on how the "rooting" process is achieved on phones. I have a moderate amount experience on linux machines so the reading is going fairly easy. Hopefully we can get some real DEVS in here to help us out.
[Droid Pro General] BlackFire27:
That's a nice amount of research. I appreciate that. And android is linux. So you may find some nice similarities. I personally am much more experienced on the hardware side of the computer world ._. I need to brush up on my coding...and from what I assume. Root is achieved by exploiting the kernel in order to pretty much shove Busybox into the root filesystem. The Su binary. And the Superuser app.
[Droid Pro General] jklung84:
From what I understand YES, that is exactly how it is done.
[Droid Pro General] BlackFire27:
But getting permission is the challenge.
[Droid Pro General] jklung84:
Anyone know of a way to get the drivers and stuff to work on a linux machine? I just can't seem to find anything.

What I don't understand is the sbf file is like a backup of everything on the phone, if they can put it there, there has to be some way of pulling it off. I would like to know and understand why we can't pull the .sbf file off of the phone it's self? Any developers out there give me a shout and fill me in?
[Droid Pro General] BlackFire27:
Well what an sbf seems to be basically a zip encoded specially for Motorola devices. I don't think its really possible to get it off without a factory reset and a custom recovery or bootloader.
[Droid Pro General] jklung84:
That is what I was wondering about. Thanks.
[Droid Pro General] Taichi Yukihyou:
I find it odd how carriers feel they need to go so far to prevent rooting, I find it wrong.

This is atleast my perspective. I go out to buy lets say a computer from best buy. I have the right to change anything on the computer, hardware and software.

Even mircosoft lets you modify (they just don't want you stealing it)

Their os and have built in applications to do so.

So why when I buy a phone and I can't do it. All of it is my property, Hard/software. If I brick it it'll bee my fault. Meaning I'll have to buy another one.
[Droid Pro General] samgr:
bingo here is the sbf http://xdaforums.com/showthread.php?p=30831590#post30831590
[Droid Pro General] kapilthio:
You cant root the Sprint Gingerbread (Leaked version) and the Boost as well. I tried lots of tools, but nothing.
[Droid Pro General] samgr:
root

we will if I find the right exploit
[Droid Pro General] BlackFire27:
Well now that we have the SBF. A more brute force type of approach on a new exploit is possible.
[Droid Pro General] nanlinsen:
now it is already able to root xprt (mb612)2.35 :)
[Droid Pro General] zhongwu:
Dear friend,I have a problem when I use my XPRT.It has got the ROOT sucessfully,but I can't add or delete files in System/lib or System/fonts.I do urge to get the permission.Could you help me ?By the way，I flashed the Sprint ROM 2.3.5.
[Droid Pro General] BlackFire27:
Are you using adb or a file manager? And do you have superuser installed?
[Droid Pro General] zhongwu:
I used xprt_root_windows.zip may my XPRT get ROOT.I have installed superuser.Also the RE files manager got the permission.:crying:
[Droid Pro General] DorkyDev:
Because you're buying into a company and possible contract with that company, basically and they don't want ya to be able to get apps for free and/or upgrade your rom. They want ya to be tied up and handcuffed to them and them only. Quite literally...

Just like I'm 100% Certain that Bill Gates and Steve Jobs don't want you running OSx86/Hackintosh on a Windows PC, cause then you're taking money away from them with the freedom of what you're able to do!

_

Anyways, any news on being able to root this or not? LoL
[Droid Pro General] tzuba12:
Root can be found in the motorola xprt general thread. We don't only have root, we also have cm7 now (thanks to Rongsang) and will soon be getting CM9 (also thanks to Rongsang)
[Droid Pro General] DorkyDev:
Cool, should make my gf happy. First android for her... Although I'll have to try and keep my hands off her toy unless she says otherwise. haha!

Never knew xda finally made a xprt forum.
[Verizon Samsung Galaxy S III] cell128:
I'm not sure if this might help with the boot loader issue but I hope its a good thing

http://m.androidcentral.com/samsung-releases-source-code-galaxy-s-iii-verizon
[AT&T, Rogers HTC One X, Telstra One XL] jojojohnson7410:
Hey,

Starting this thread up as a place to figure out the "Preparing Sim Card" problem.

Essentially, if you flash CleanROM 4.1 with CWM, you'll probably get this error. There were plethora of fixes out there, such as:

1. Clearing all cache (fastboot/recovery)

2. Clearing all data/force stopping problem apps (people/dialer/messaging)

3. RUUing back to stock

4. Flashing a new radio

5. Removing/Changing SIM cards

6. Trying dialer trick:

.....a. Go to Dialer (if you can't access it, clear the data in it first)

.....b. dial *#*#4636#*#*

.....c. Turn off the radio

.....d. Turn on the radio, and right as the toast appears, choose something from the drop down menu.

.....e. Run a ping test to make sure everything's alright.

7. Used TWRP to clear system/flash new ROM

8. Tried another ROM with GSM Patch

CURRENT STATUS: WORKING!!!! =D

The answer to all your problems issss........

Well, it's multi-step :P

1. Make sure to flash back via RUU (preferably 1.82 since 1.85 was a b**** for me to re-root T_T)

2. Make sure to unlock your bootloader again

3. Install back CWM (I know...wtf?!) <<THIS STEP IS IMPORTANT (believe it or not)

4. Go back and flash CleanMOD 3.1 or something (just anything below 4.1 should do the trick) [if just installing CleanMOD doesn't work, install the GSM Patch too!]

5. NOW install TWRP

6. Install CleanMOD 4.1

7. SUCCESS!!!

Also, thanks to tehdef, who also tried this method:

Here is what I did to break my phone.

I had the following MODS.

-AOKP 6.1

-CWM

Decided I wanted to test something on CleanROM 4.1

- Flashed CR4.1 in CWM

Got stuck in Boot Cycle and CWM would not load

1. Locked Bootloader

2. Installed 1.85 Evita RUU

3. Unlocked Bootloader

4. Installed TWRP

5. Flashed AOKP 6.1

At this point, I still had an issue. Instead of receiving the "Preparing SIM" Message, I had absolutely zero signal, and I could not "SAVE" an APN.

6. Rebooted to Bootloader

7. Reset to Factory while in AOKP

8. TWRP Loads

9. Reboot to System

My phone now has signal and full contacts and I can make calls and send Texts and MMS with no additional modifications. Please note that with AOKP Superuser comes installed and works just fine, so for whatever reason I did not have to root my device.

NOTE:

YOU DO NOT NEED TO USE CLEANROM 3.1 IN ORDER TO GET BACK TO A WORKING STATE!!! Just any rom supporting the unofficial CWM should do. =] (at least I think so, but I'll confirm when someone get's back to me =D)

Thanks goes out to...

Scott for his awesome ROMs and his life lessons :P

kleeman7 for toughing it out and helping me through the entire thing

tehdef for helping me test out several of my theories

shackman716 for suggesting the idea that worked (it was so crazy it actually worked! XD)

and thanks goes out to anyone I forgot to mention. XD

Now, back to more ROM flashing :D
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
scrosler specifically states not to use CWM to flash his ROM. Have you tried TWRP?
[AT&T, Rogers HTC One X, Telstra One XL] tehdef:
We are well past that point, redpoint. We've already flashed, and now things aren't working correctly.

In my specific case, XDA Mobile didn't Bold/Red the text to use TWRP instead of CWM, so when I flashed and attempted to boot, I got stuck in a boot cycle. I went back to try to get into recovery, and it wouldn't even go there. So I re-locked, and flashed the 1.85 RUU.

Now I'm getting the same 'Preparing' issue only when I attempt to open up Phone, Contacts, Messaging, all on the stock RUU while being Locked.

I can't even attempt to re-flash the Stock RUU because I'm getting Error 170 on the RUU installer.

This majorly sucks.
[AT&T, Rogers HTC One X, Telstra One XL] gunnyman:
Error 170 is a usb communication error and is fixable. Turn off HTC sync. Check for it in running processes. If you still get the error reboot to the bootloader make sure the phone says fastboot usb in red then start the ruu.
[AT&T, Rogers HTC One X, Telstra One XL] daddioj:
thats a driver error do u have htc drivers installed? good usb cable? tried a diff slot?

if not install htc sync let the first portion install. when it comes time for htc sync inself to install cancel. and just the drivers will be installed
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
The OP never stated any of that, and it doesn't seem that he is stuck in the same way you are. So I was asking if he tried to flash TWRP, and then reflash the ROM. Which is not listed as one of his "possible fixes".
[AT&T, Rogers HTC One X, Telstra One XL] elsupermang:
I had the same error. I believe I was able to reproduce it by adding my Google Play Account then adding my gmail account (with the same email address) using Activesync. Right after adding my gmail account I would get an application crash (cant recall which one) the phone would reboot and go into a reboot cycle when "Preparing Sim Card". To avoid the issue I did the following:

1. Wipe System, Wipe Data

2. Flash CleanROM 4.1 DE

3. Wipe Cache

4. Install Mods

5. Boot up, add Google Account from the setup wizard

6. Turn on Auto-Sync from Wizard

7. Go into Settings > Accounts > Uncheck sync Email,Contacts, Calendar

8. Clear Data for Email, Contacts, Calendar apps.

9. Add gmail via Activesync w/ Email/Contact/Calendar sync
[AT&T, Rogers HTC One X, Telstra One XL] jojojohnson7410:
Well, I tried emailing and stuff, and it seems anything regarding data seems to be alright. It just seems to be the issue with phone/sms data now. I believe it's something software related as it still reads my sim just fine, and it recognizes when it gets a call. Just when I get a call, it repeatedly FCs. I might give it a try though, so thanks!

Sorry, I had to go out for lunch, so I didn't really go into much detail. I have tried using TWRP and is still using that atm, and also tried flashing a rom with GSM Patch, which I'll edit the OP to match. Both of these did not work and I'm going to try and pull a logcat or something. Will update when I get it
[AT&T, Rogers HTC One X, Telstra One XL] tehdef:
Just got mine to flash. I noticed though that for whatever reason my current 1.85 had an _r2 at the end, and the one I'm flashing does not. Curious if ATT network is rejecting due to the RUU version.

Guess we will find out when it's done.

Edit: Nope, nada... Same issue.

Curious though why none of my contacts sync. seems like this is a contacts issue for me.
[AT&T, Rogers HTC One X, Telstra One XL] jojojohnson7410:
i feel like the dialer and the contacts are linked together. if we can solve one, we can probably solve both. I looked in my catlog and they stated that they couldnt find a particular file/db in the /data/data folder. ill look into this and see what happens
[AT&T, Rogers HTC One X, Telstra One XL] kleeman7:
Did either of you try flashing a different rom like xi40, or sick sense, and do a system, cache, dalvik, factory reset, wipe from twrp before you flash a rom, and see how that goes

Sent from my HTC One X
[AT&T, Rogers HTC One X, Telstra One XL] tehdef:
Well, hopefully that's it.

---------- Post added at 01:12 PM ---------- Previous post was at 01:06 PM ----------

I haven't unlocked my BL again because I'm at home, and frankly, I'm not sure how the process is changed once I already ahve the Auth Key, and if I can do it quickly here from work.