yashsingh1/xdaforums huggingface dataset:
[Windows Phone 7 General] jassasman:
error 80180048

Help please, I'm having the same problem after forcing the NODO update

Error 80180048

:confused:

HD7
[Windows Phone 7 General] amtrakcn:
Sry didn't Walsh it...
[Windows Phone 7 General] JamesAllen:
Did you use Chevron Updater previously?

Fine, but did you use Chevron Updater to get NoDo?
[Windows Phone 7 General] RoboDad:
That's awesome, but this thread is for discussion of issues with phones that used the Chevon Updater (not the Chevron unlock process) to get to NoDo. There is another thread for more general 7392 update results.

[Edit]

D'oh! James beat me to it. :)
[Windows Phone 7 General] amtrakcn:
Ah I'm sorry... I used the VPN method not the Chevron method. Didn't read the op.
[Windows Phone 7 General] ameel:
so you DID flash your phone with a different rom (than stock) before. That seems to be the common factor for error 80180048
[Windows Phone 7 General] ycode90:
successfully updated 7392 "Walshed" Att surround still unlocked. Yay.
[Windows Phone 7 General] fizlan75:
My HTC HD 7 successfully got it during Match between Man U vs Schelke 04
[Windows Phone 7 General] itsraining2008:
hTC Mozart bought from Starhub without contract. Try registry hack for operator and use VPN method to update NoDo. Currently updated to 7392 and still unlocked :)

May be Walshed method only cause that error?

Other VPN method ppl don't afraid to update 7392. mine still unlocked and side-loaded app still working. may be this info useful for error. Cheerrrrrrr............ :)
[Windows Phone 7 General] homer.web:
I had same problem and I just installed the latest image and it works fine and after that it has had updated to 7392 without any problem.
[Windows Phone 7 General] ahodes:
I did some digging and figured out what's gone wrong. Some phones have more than one language installed, but the Chevron updater only installs the language update for the language you choose. When Zune goes to update your phone, it tries to install updates for the rest of the languages to, but fails since the versions on the phone are incorrect. All that needs to be done is install the missing language updates. I have a Samsung Focus that was updated with the US English update. Looking at the log files for the update, it also needed:

German

Italian

Spanish

French

Using the Chevron updater as a base, I reworked it to install the missing languages. If you're using a Samsung Focus, you can get the exe I wrote to update my phone from h ttps://rapidshare.com/files/461012568/FixFocus.zip. I can't promise that nothing horrible will happen, but my phone did update properly to 7392 via Zune after running it.

If you have some other phone that uses a different combination of languages, it's just a matter of applying a different set of updates. I'm guessing the phones that work fine only had one language installed to begin with. Definitely no need to reflash the phone!
[Windows Phone 7 General] walshieau:
So this "may" give you 7392. But this can also cause other issues if you install language packs that aren't supposed to be on your device. So I'd hold off on using this :)
[Windows Phone 7 General] WithinRafael:
STOPPPPPPPPPPPPPPPPPPPPPPPPPPPP. We're actually going back and forth with Microsoft on this to prevent a Super Walshed phone (one that cannot be fixed without flash). Please wait :(
[Windows Phone 7 General] homer.web:
You have a very easy solution for that, at least if you are a HTC HD7 owner.

I recieved this error when I tried to install security update 7392. So I downloaded the latest official image for my phone from this site and flashed it to my O2 DE HD7. After that there was no 80180048 error during the update process and phone has now 7392 build.

You can find at leas 16 branded ROMs for HD7 right here: http://xdaforums.com/forumdisplay.php?f=783
[Windows Phone 7 General] homer.web:
I recieved this error when I tried to install security update 7392. So I downloaded the latest official image for my phone from this site and flashed it to my O2 DE HD7. After that there was no 80180048 error during the update process and phone has now 7392 build.

I have used this latest ROM with NoDo: http://xdaforums.com/showthread.php?t=1037967
[Windows Phone 7 General] gentry33:
Until I can afford the time to keep flashing (which doesn't seem to work for everyone) I'll wait for Chris Walshe's fix so I can keep going forward without having to back.

Here's hoping that Microsoft learned something about expediting from all this.
[Windows Phone 7 General] homer.web:
If you flash it with stock ROM, then you are in the state where you were before Chewron update, so you do not have to flash it again after new updates will be arriving. Flash with stock ROM very likely works for everyone and its much quicker than regular update using Zune proces. :) If you are not sidedownloading applications or did not unbrand your phone, its best solution of the problem.
[Desire Q&A, Help & Troubleshooting] yeahman45:
have read a lot of threads about this issue

when i receive calls, there is no country code in number and some of my contacts are stored with country code included: result : Contact is not recognised

when i receive sms, country code is include in number and some of my contacts are stored without country code and result : Contact not recognised

this is the most stupid issue in android imo and i still haven't found a proper solution for that...... i don't quite understand why there isn't any proper fix (apart saving contact with 2 numbers (one with country code and one without country code) for that till now!

the next most stupid issue in android is sms ordering issue... (i still can't believe that there aren't proper fix for these 2 issues.. i use handscent sms for ordering issue... quite stupid honestly that u need a third party app for that)
[Desire Q&A, Help & Troubleshooting] Meaple:
It's just you. Works fine for me
[Desire Q&A, Help & Troubleshooting] yeahman45:
i saw several threads with this problem : all threads are either without answer or there's a workaround (save 2 numbers per contact)... wanted to know if there was a clean way to fix this issue instead of saving 2 numbers per contact(pretty messy)
[Desire Q&A, Help & Troubleshooting] yeahman45:
look how many people has this issue

http://code.google.com/p/android/issues/detail?id=4134

no solution on google's site since ages

i am trying my luck here... maybe there's a third party app that fixes it?
[Desire Q&A, Help & Troubleshooting] yeahman45:
No one has a solution. I have installed touchpal dialer and it identify the contacts properly when I look at the call log. Is there a way to use touchpal dialer to handle incoming call screen so that it can identify my contacts properly?
[Desire Q&A, Help & Troubleshooting] yeahman45:
was trying to write an app to fix this issue but realised that on the android emulator, there is no such problem... is it because on my actual phone, i am on htc sense? can someone with htc sense confirm that this issue occurs only on htc sense?
[Desire HD Q&A, Help & Troubleshooting] laughter_22:
Hi guys,

new newb here, i just had a question, i recently purchased Desire HD (3 months ago) since then i hear alot of ginger bread and all other versions coming out...but doesnt seem HTC is bothering to provide the firmware upgrade for Desire HD ..apart from the guys giving their Mods here..

Do i understand this correctly?

Laughter.
[Desire HD Q&A, Help & Troubleshooting] Mr_JMM:
GB has started to be rolled out in Europe. As always with OTA ROM upgrades, patience is the key.

[EDIT] There's a thread dedicated to this subject on this very forum:

http://xdaforums.com/showthread.php?t=863327

(Man I'm in a nice mood. See "Andy", I can be nice *rasp*) [/EDIT]

Or you can stop waiting, have fun and check out the naughtiness on the development forum :o)
[Desire HD Q&A, Help & Troubleshooting] laughter_22:
i think i'll go the naughty way, whats the worst, a bricked phone good for hitting lizards with!
[Desire HD Q&A, Help & Troubleshooting] Mr_JMM:
That's the attitude I like to see.

BTW, I edited my original reply with link to thread on update thread.
[Desire HD Q&A, Help & Troubleshooting] jamy10:
Can u fix a bricked phone or is there difrent levels of bricked .?
[Desire HD Q&A, Help & Troubleshooting] Mr_JMM:
As a rule, bricked is bricked is bricked.

There are rumblings of fixes involving soldering resistors to a USB cable but nothing confirmed, that I know of.

For the moment, assume no fix. If bricked it will need to go back to HTC.
[Desire HD Q&A, Help & Troubleshooting] jamy10:
Sorry if that sounds nooby
[Desire HD Q&A, Help & Troubleshooting] Mr_JMM:
No worries. It's what we're here for.
[Desire HD Q&A, Help & Troubleshooting] jamy10:
Thx m8 will avoid that at all cost lol
[Desire HD Q&A, Help & Troubleshooting] Palmahnic:
You can flash a ROM with out messing around with the radio, which is what can get your device bricked. Plus there's a Gingerbread ROM of the latest build (2.36) you can flash without even having your device rooted... search for ROM 2.36 and you'll find it plus instructions on how to.

Happy flashing :)
[Desire HD Q&A, Help & Troubleshooting] MarcoHD:
Is it the same version like the leaked one?
[Desire HD Q&A, Help & Troubleshooting] killersloth:
Lol I have flashed so much ****, from so many people, to so many devices. I follow the directions and xda-devz never fail me

I recommend leedroid or rc's if you like sense or cm7 for overall pwnage.
[Desire HD Q&A, Help & Troubleshooting] naimmkassim:
Is there any forum which inform which radio to be use with which rom, as to avoid any bricked from happen? Or something which we must not do as can cause bricked etc?
[Desire HD Q&A, Help & Troubleshooting] jkoljo:
Mate, you cannot brick it unless you do something stupid in command line. Really any wrong flash combination is recoverable.
[Desire HD Q&A, Help & Troubleshooting] sanjayng:
For Lee's rom, he usually specifies what radio will be better suited and a link to radio as well in the first post.
[General Accessories] PCTechNerd:
I used to own the original version of the Liveview, but due to the watch holder snap on case design flaw it flew off while playing PS Move and broke (this was one of the two main issues with it). That happened around 3 months ago, and try as I might, I couldn't find a watch that could hold a candle to the functionality and awesomeness that was the Liveview.

Flash forward to yesterday. I saw that Amazon.com was selling the Liveview Directly now (as opposed to a 3rd party vendor using Amazon's storefront). I went ahead and ordered one with the impression that it was the same version, and I had planned to use the velcro idea to keep the liveview attached.

Well today I received the liveview (Amazon Prime FTW), and lo and behold, it's the newer version (the one talked about with the US release). Right now it's doing it's first initial charge, so i haven't updated the FW or anything yet so I will update this thread later with more info, but there are some major differences already that make me happy! The first and most important is the clip-on watch holder. It has been redesigned to stop from popping off, and to work with ANY watch band (that fits the 20mm size coupler of course). The backing is completely filled in.

Once it's fully charged and I update the FW, I will run some other tests. If you have any questions, or there's something you want me to try, post here and I will get back to you. Also, if you want to order the US release version of the Liveview you can do so by Clicking Here.

Update:

So it's fully charged, and I put it in the updated watch holder, and it snapped in with a nice snug fit. It feels like it's in there really good, and there is no chance it would fall out like before. It's hard to explain, but hot damn it feels like the way it should have in the first place.

before turning it on, I went ahead and downloaded SEUS and updated the firmware for it. I've had it connected to my phone for over 2.5 hours, and have not had a single disconnect (my phone is a Thunderbolt). Now I know a good factor of the disconnects is caused by low memory on the phone, and chances are that isn't applicable with my phone, but there are also disconnects caused by things other than the phone memory. Needless to say, the whole liveview experience has improved drastically, and i'm very pleased none the less.
[General Accessories] dazultra2000:
Hmm. Doesn't really look that different to me. All I can really see that is different is that they've filled the back of the mounting clip in. Which to be honest would probably annoy me more than anything as I used to jam my thumb through that hole to pop the liveview out of it's mounting clip.

I guess you still can't charge it whilst in the mount?

Any other hardware changes?

I can't see any difference to the way the strap is attached. I threw the included strap away as soon as I opened the box to mine and replaced it with a silicone strap with a deployment clasp. So much easier.

What's the model number? Is it still an MN800?

I'm not quite as excited as you are about this, but I'm glad you are! :)
[General Accessories] thekenderman:
I just got my liveview yesterday, and it is indeed a drastic change to the watch strap cilp...

The golden quesiton though is how the hell am I supposed to charge it with a watch strap on?!?!

The new 'holster' for the liveview to be used as a watch (not the cloths clip) is so tight that it is VERY difficult to remove from it's mount to charge, so it is still pretty useless that way...and I won't want to weaken the plastic or break anything.

With the silocone strap, does it allow for charging without having to unmount? I am dying to find a good solution for 'on the watch' charging!!
[General Accessories] dazultra2000:
No :/

Because the watch strap pin is effectively directly in front of the MicroUSB plug, there's not a chance that you could charge whilst still in the strap.

The only way to do it is to modify the "belt clip" attachment and somehow attach a strap to that instead.

Pretty piss-poor design flaw to be honest.
[General Accessories] thekenderman:
What a terrible design. Ugh. Battery life on my livebirw has been piss poor too.
[General Accessories] Midi_Amp:
I bought this one when it was "unofficially" launched in my country 2 days ago. Twitted about what the hey people are fussing about the clip because it's clipped on very tight... Well... Too tight even. Now I have difficulty taking it off.

Any pointers about taking the LiveView from the clip? I got mine clipped on by the shop keeper for added assurance about loose clip, but now I can't seem to be able to release it from the clip.

The clip has two small tabs and one long tab, I wonder which direction I should push before lifting the LiveView from the clip, towards the small tabs or the long tab? Tried pushing and lifting towards the small tabs, but lost my nerve somewhere in the gutter.

Need to second charge the device, and although releasing the pin and strap behind the micro USB helps, I can't rely on this method since I'm planning to buy a real watch strap for it, or got stuck with the velcro strap (ick).
[General Accessories] thekenderman:
Ya I got mine unofficially released aswell. What a tight ass clip.
[General Accessories] machmandp:
This looks much better

now all i have to do is to try and get one

Sony spares have no idea that it's available, it should be free to everyone with a Liveview TBH
[General Accessories] ysk168:
A better choice of wrist band for Liveview.:)

See this :

talk.sonyericsson.com/message/77377#77377
[General Accessories] thekenderman:
I just got a leather strap by Timex that has "ez pin". It allows you to remove the strap to charge and easily put it back on....14.99 Walmart in Canada....genuine leather and looks good too....Better than that ass liking Velcro...it now looks decent!
[General Accessories] el_venga:
Im going to do that to mine. Get rid of velcro. Thanks for bumping the topic @user above me.
[General Accessories] thekenderman:
So, here is my strap...as you can see, pull the pin which is spring loaded and voila....charging port is accessible and it's not a pain to charge!
[General Accessories] TracerBullitt:
So, how's it been working for you so far? Thinking about putting it on my Christmas list... :P
[Nexus S Android Development] trismegistos:
This ROM aims to be really fast and stable, that is the reason it is mostly plain AOSP and not going to be the ROM with the largest Feature List ;).

There are some additional Features (see below) and several performance and battery life tweaks implemented in the ROM.

Rom Info

- compiled from latest AOSP 2.3.4 Source (http://source.android.com/)

- complete optimized system for best performance and battery life

- SuperUser and busybox (rooted)

- incl. APPS: Titanium Backup, RomManager, Voodoo control, UD Launcher

- Netarchy CFS 1.3.5 Kernel w/BLN,ext4 & full voodoo Kernel

- complete Themed Userinterface (ZuluZulu Theme)

Features

- Large list of preset APN

- /etc/hosts file for AD block

- reboot, bootloader, recovery from power-off menu

- Enable SIP over 3G

- Facebooksync -> Contacts working

- Replaced Stock Launcher with UD Launcher

- enhanced MMS Settings in MMS app

- swipe left/right Notification in Status Bar

- configurable PowerWidget in Statusbar

- Themed: Transparent Status Bar

- Themed: Percentage of battery

- Themed: HSDPA icon

- Themed: Transparent Contacts & Dialer

- Themed: sms/mms advanced settings for black Background, gestures etc..

ROM download

ZuluZulu 1.3.1

Latest Zulu-Trinity-TUV11 Kernel (thx Morfic)

TUV11-zulu-NS+4G-12082011.zip

additional Battery Mod (see last Screenshot)

zulu-1.3.1-theme.zip

Installation

Flashing the ROM is on your own risk. Do nandroid backup before installing.

- Download the ROM Zipfile to your SDCard

- Boot into Recovery

- Flash ROM

- Reboot

Screenshots

additional Battery Mod

Special Thanks

CM Team

Morfic for Zulu Kernel

Netarchy & ogdobber for cool Kernels

and everyone who helped me and i did not listed... :)
[Nexus S Android Development] trismegistos:
Changelog

Version 1.3.1

- Fixed SpareParts fc on Battery History

- Fixed no Dictionary available in LatinIME

- added Netarchy Kernel 1.3.5

- added new additional Battery Icon (see Screenshot in the 1st Post)

Version 1.3.0

- compiled from latest Source, a lot of official AOSP updates and fixes are included

- renamed Extra Settings to Power Widget in Settings menu

- finalized blue theme in several minor bugs

- added spanish language

Version 1.2.9 [15/6/11]

- Themed PowerWidget icons in statusbar

- replaced Stock Launcher with UD Launcher

Version 1.2.3 [10/6/11]

For Version 1.2.3 Wipe/Factory Reset is REQUIRED for all users!

- implemented a lot of tweaks to optimize the system performance and the battery life

(you will not recognize it in quadrant because quadrant only shows hardware related speed, but you will definitely recognize it in you phone behavior)

- better implementation of swiping left/right of notifications in the statusbar

- ui design tweaked

- reverted back to netarchys cfs kernel (the usb mount problems are fixed and now you can decide your own if you want to do some UV with the protonvoltage app on the market or overclock. The bootanimation and the long boot time of trinity are sucking a bit)

- updated all new app versions

Version 1.2.2 [6/6/11]

- added Norway language

- added things to blue theme

- added gtalk over 3g fix (hopefully)

Version 1.2.1 [4/6/11]

- fixed chinese language

Version 1.2.1 [2/6/11]

- added gestures and date/time settings and more features to mms/sms application

- added lock/unlock ogg files

- changed size (smaller) and color of power widget icons in status bar (hope you all like it)

- changed color of animations in the ui from orange to blue

- saved 2 mb more in memory ;)
[Nexus S Android Development] deeren:
Great to see new chefs here! thanks . will give it a try
[Nexus S Android Development] Jibreil:
And the ROM hits just keep on coming :-)
[Nexus S Android Development] Borky_16:
deoxed?

zipaligned?

:)
[Nexus S Android Development] trismegistos:
Yes
[Nexus S Android Development] Borky_16:
Nice, looking forward to a new Star in the NS Dev section ;)
[Nexus S Android Development] trismegistos:
;) will see
[Nexus S Android Development] Borky_16:
One quick Bug before I'm going to sleep (Europe time)

You should change the Build Prop the Android Version is still Blandroid 2.3.4p0 :)

But as an quick response to upcoming users, I think here was made a clean Job :) so happy flashing :D
[Nexus S Android Development] stevm:
First welcome and thank you for sharing the rom

Installed few hours ago ,and everything went perfect.Still no issues,reflashed it with netarchy's kernel and I'm so satisfied with this one. Thanks again
[Nexus S Android Development] trismegistos:
Yep, comes tomorrow, thx
[Nexus S Android Development] trismegistos:
I am happy when you are ;)
[Nexus S Android Development] FaithCry:
nice build, but the Gtalk video still doesn't work :( i was on blandroid before this and had the same problem.
[Nexus S Android Development] BraydenJames:
So is this confirmed with this ROM? I'm having current issues with CM7 so contemplating flashing back to stock-ish ROM. This one looks pretty promising as it'd be nice to have 2.3.4 but still have some extras :). But does the video chat not work on here even with updated gapps? What if you start the call in silent? Thanks! Glad to see yet another developer here!
[Nexus S Android Development] trismegistos:
I will have a look on the gtalk video today. I don't use it so I haven't testet it.
[Nexus S Android Development] trismegistos:
so the workaround to start the call with silent seems to work. looking forward for a complet fix for the issue..
[Nexus S Android Development] kevin_ngckk:
Thanks for your rom :D i will flash it when the gtalk had been fixed. And how abOut the battery life of this rom??
[Nexus S Android Development] trismegistos:
under 1% per hour with facebook, twitter and 2 emailaccounts every hour syncing.
[Nexus S Android Development] kevin_ngckk:
LoL thanks for reply my fool question. Im waiting the next build of your great rom :D

Edit: i want to ask something about launcher pro... is there any freeze issue in this rom?? Because launcher pro seems like not totally suport nexus s :(
[Nexus S Android Development] trismegistos:
definitly not. i am using launcher pro since i have the nexus s and had never any FC's or frezzes.
[Nexus S Android Development] Paleryder:
That would be great
[Nexus S Android Development] liorry:
Great ROM... thanks
[Nexus S Android Development] mephissto:
Thanks for the beautiful ROM

I really like the UI
[Nexus S Android Development] bakron1:
I really like this ROM, I would like to ask if someone could build the "blacklist" feature into a ROM like CM. I know everyone wants they're ROM to be unique, but I love this feature when it comes to telemarketers and calls I do not want to be bothered with.

I know there are apps out there that do this but it is nice to have it built in. I would donate a little extra if someone could do this please.
[Nexus S Android Development] jesrazo:
Beautiful, fast, and very stable. The only thing that bothers me is when you scroll all the way up or down I get the blueish glow, I wish it where orange. Also your bad ass battery percentage indicator, wish it where orange also. Other than that, this has made this phone exactly what it should be. Its making my choice of leaving to the G2X really hard. But at least I can try it and just return knowing your Rom made this device way better for me. Lol, sorry for thinking there was some weirdness going on with that Oriental app. Don't speak the language, didn't know what it was.
[Nexus S Android Development] Magguz:
lol... i hope everything which is now orange is blue :D
[Nexus S Android Development] trismegistos:
thanks for your response. it is a hard choice for me what color i should choose for glow effects and battery. i know, that my choice is not always the choice of other users, but hey, that is life :). i am thinking since the weekend for a design/color which fits the most needs of all, haven't find an answer till yet.