Well i had to re flash my froyo today cuz of some issues i was having with my wifi. (but i think it was cuz i was messing around with lag fix..) so yes..what i did was to flash to JM6 (because even after restoring from factory on froyo I still kept getting wifi issues saying..attempting to connect to wifi obtaining IP address..) but it never got the ip address.
So then i went to apply the reg mod
as per http://forum.xda-developers.com/showthread.php?t=769400
well when i did that...i didnt get JPC but JM1 :-o
so...yes it looks like we made too much of a noise that Samsung has pull the plug .
so am thinking to flash to JM7 and just wait ...only 28 days left!..
I just installed JF3, will try updating via KIES and see what wil happen
nandihno said:
so...yes it looks like we made too much of a noise that Samsung has pull the plug .
so am thinking to flash to JM7 and just wait ...only 28 days left!..
Click to expand...
Click to collapse
Hope indeed Samsung read this so they put up the gear, so they can release the REAL official Froyo very soon
No official update for JF3
Related
Ok, PC is fine, close any running programs. Hermes has stock WM5 with some programs added. Only reg tweaks are PTT and removed 3G animation at start.
Device syncs normally every day and both Work and Home.
When I follow all the directions, run the Updater - The PPC gets the Color Bars as the Updater is trying to read it....then AS (V4.5) disconnects and closes. (gone from taskbar) I can soft reset the device, reopen AS, they sync just fine. At this point I have the updater do the next, it pulls up the Current ROM info and says it will upgrade to the new one. I select next, and it starts.....and AS closes again. After a minute the upgrade app says it lost connection. (duh!)
Any ideas why?
I'm not a stranger to upgrading roms on PPC's, have several that have both been updated a number of times. No issues, though that several AS versions earlier.
I've given thought to Hard Reseting the device, but I'm wondering if its more AS's fault.
Any and all input much appreciated!
Thank You!
JETninja said:
Ok, PC is fine, close any running programs. Hermes has stock WM5 with some programs added. Only reg tweaks are PTT and removed 3G animation at start.
Device syncs normally every day and both Work and Home.
When I follow all the directions, run the Updater - The PPC gets the Color Bars as the Updater is trying to read it....then AS (V4.5) disconnects and closes. (gone from taskbar) I can soft reset the device, reopen AS, they sync just fine. At this point I have the updater do the next, it pulls up the Current ROM info and says it will upgrade to the new one. I select next, and it starts.....and AS closes again. After a minute the upgrade app says it lost connection. (duh!)
Any ideas why?
I'm not a stranger to upgrading roms on PPC's, have several that have both been updated a number of times. No issues, though that several AS versions earlier.
I've given thought to Hard Reseting the device, but I'm wondering if its more AS's fault.
Any and all input much appreciated!
Thank You!
Click to expand...
Click to collapse
Are you following the directions at THIS GUIDE . What ROM are you trying to put on there? Did you CID unlock the device? Are you running Vista? Do you have .NET 2.0 or 3.0 version?
That should be enough questions to get us started.
Did you read my title? This is the stock ATT WM6 that came out yesterday. No need to unlock the phone, it is a 1 week old ATT 8525 with the stock ATT WM5 Rom on it.....
Windows XP SP2+ PC.
If it's the rom RUU_Hermes_CINGULAR_WWE_3.62.502.3_6275_1.54.07.00_108_UOOS_SVN05_Ship maybe it had some problems because if you go to the official release site http://www.htcamerica.net/support/8525/software-downloads.html they are still showing the WM5 rom for download.
There may have been a problem with the release and they pulled it back for some reason. Just a thought and not much help I'm afraid.
Yes thats it. When it ID's my current Rom and what it will upgrade to, it is correct. (it shows it's 3.62 vs my current 2.xx) Many peeps have had no problem upgrading to it. (most find it a very good Rom from the varios sites I read)
And this page at HTC still has it up:
http://www.america.htc.com/support/8525/software-downloads.html
JETninja said:
Ok, PC is fine, close any running programs. Hermes has stock WM5 with some programs added. Only reg tweaks are PTT and removed 3G animation at start.
Device syncs normally every day and both Work and Home.
When I follow all the directions, run the Updater - The PPC gets the Color Bars as the Updater is trying to read it....then AS (V4.5) disconnects and closes. (gone from taskbar) I can soft reset the device, reopen AS, they sync just fine. At this point I have the updater do the next, it pulls up the Current ROM info and says it will upgrade to the new one. I select next, and it starts.....and AS closes again. After a minute the upgrade app says it lost connection. (duh!)
Any ideas why?
I'm not a stranger to upgrading roms on PPC's, have several that have both been updated a number of times. No issues, though that several AS versions earlier.
I've given thought to Hard Reseting the device, but I'm wondering if its more AS's fault.
Any and all input much appreciated!
Thank You!
Click to expand...
Click to collapse
You just need to wait for a while AS shuts down that is normal be patient and it will start updating you will see a progress bar will take approx 10 min after that
@brorex he can wait till christmas next year, if the updater cant communicate with the device , because it has closed AS then it will never update.
@JETninja
try doing what i said to this guy here,
http://forum.xda-developers.com/showthread.php?t=341282
yesterday he upgraded with the same rom and device and it worked
brorex said:
You just need to wait for a while AS shuts down that is normal be patient and it will start updating you will see a progress bar will take approx 10 min after that
Click to expand...
Click to collapse
I thought that too, but after the color bar test when it want to set you up to actually install the ROM, the Upgrader whats you to make sure there is an active connection with AS. Well, there isn't. It shut down and the PPC is still showing the color bars. I can reset it, then re-sync to AS. (after having to re-launch AS from the Program Files - it no longer resides in the Tray when it shuts down during the process) I then get it going again, it attempts to start the ROM upgrade, AS quits again.....about a min later I get the Communication Error message....
I'm downloading a 2nd copy right now, will try it as soon as it completes...
*Edit...think I have an idea what I'm doing wrong, I have it connected and synced too early, the first part of the ROM updater is just a PC test, I'm thinking the PPC should not have been connected at that time. Re-trying it now.....
Try putting it in boot loader and upload...thats what i did when i updated my 8525...Very much like the new ROM...
Going to give it a shot here at work on this PC. If no go still, will try the above mentioned methods. PC at home kept getting communication errors...
i had the same problem
make the connection at AS then start the update process.... the 8525 will go into 3 bar mode and when the update gets to the upgrading rom screen... the installed rom wont show up.... hit upgrade... and then continue and it will work.... i was stuck there for a while too because if i waited for the istallation to load then made the as connection the right image would show up in the installer but then it would stop working after that.....
I just put this rom on my 8525 and it worked well for me. My 8525 is unlocked with supercid so I had to extract the OS and update using the methods described for working with SPL-140 Olipro with IPL-1.01 or the "How not to Brick thread".
That won't help you much as you don't want to do that mod to your New 8525 and void the warranty, but thought you might like to know the stock OS seems pretty stable at this point and I have had no problems yet.
Thanks everyone! It finally worked here on my Work PC. At home I could get to the Bootloader, but it would lose connection for some reason. Here I lost it the first time, but tried it again and it managed to stay connected and apply the update. Got it up and running, applied owner info, just now re-doing the AS relationship. (a good 500+ contacts! LOL! It'll take a little while as usual!)
Then it's back to all the tweaks I like so far...and some new ones I've held up on since I've been waiting for WM6.
Out of my 3 PDA's (2 ipaqs and this puppy) this one has certainly been the trickiest ROM update, but it seems to be more my device since most don't have this much trouble.
Thanks again!
So far- So good, but just one problem- BATTERY!!!
After I installed upgrade, my battery drains in few hours... I reset phone, I reloded upgrade- nothing helps! Warranty still in affect, but phone worked well and I'm positive- hardware is OK. What else can i do to fix this problem?
I have the same problem
ai6908 said:
Try putting it in boot loader and upload...thats what i did when i updated my 8525...Very much like the new ROM...
Click to expand...
Click to collapse
I have the same problem exactly. As soon as I start the upgrade the device immediately sleeps and the connection is lost. 1 minute later I get a Connection error message.
I am new to all this. How do i put the machine in 'boot loader' mode?
Thanks
Just did this rom update again on a 8525 the installation went extracting files active sync shut down wait a few minutes nothing happens the the upgrade screen no ACTIVESYNC connection while update is happening as soon as device is in bootloader mode activesync closes out
I just swapped my phone out and received a new phones. now with the old phone which was the one i originally purchased, I could send a 4-6mb song via bluetooth in about a minute and a few seconds on Stock Verizon Rom, and on my rom im using at the moment The latest Mighty Rom Sense 2.1
Now on my replacement device ive tried on stock rom and The latest mighty rom it sends the files almost 10x slower if they go threw at all. Alot of times it goes at like dial up like pace when trying to send files over bluetooth...even small cab files that used to send on my old phone in under 20 seconds takes forever to send if they go through at all
when the files fail to go through it says Connection failed or lost
is it something wrong with my replacement device's bluetooth or is there something i can do to fix this issue? im thinkin about calling this in for another replacement
Do a hard reset and try again and/or go back to stock verizon 6.5 rom and try on it. If the stock rom is slow then the phone has issues.
Before going all the way back to a stock ROM, you might want to check and see if the ROM you're using has a different radio version than the stock one, that could be the source of degraded BT performance. Try whatever one came with the stock ROM, and see if it clears up the issue...if it does, then you should be able to keep the ROM you like, and just use the stock radio.
well im on my second replacement now i went all the way back to stock verizon 6.1 rom because i was having the same issues with the second replacement they sent me....slow bluetooth file transfer
im on stock verizon 6.1 now and im trying to pick up a samsung omnnia 2 but i cant pick it up at all and when the omnia 2 tries to pick me up it can find me but the pairing doesnt go through
the rom version is 1..18.605.6
the radio version is 1.87.00wv
is it a faulty device? is there anything i can do with the bluetooth to fix it?
EDIT:
ok im assuming it was a issue with the radio that comes with verizon's 6.5. Now when i went to 6.1 and then back to my custom rom it worked fine just like before. But for some reason i could not find the omnia2 ill have to test that with a different device and see if it works with my earpiece and other phones but so far so good hope that helps if anyone else is having these problems
As the title says, should i stay with my 2.1 (i did clock workmod and using Mobile AP to pair it to my Samsung Galaxy Tab) or should i go and update to 2.2(EB13)
the question is cuz i have heard a lot of bad thing about the update (2.2), that it doesnt work properly, problems with data connectivity, problems with the sd card and that even Samsung pulled out the update from their web page cuz of the complaints etc etc etc...
dont know what to do
guy's what do you recommend
i just what to keep using my Mobile AP
The stock Eb-13 is horrid, it does have problems, but if you flash a good stable rom, you'll be able to use Wireless Tether from marketplace and have the same setup. Froyo enables so many more features than Eclair so I would update.
Syndicate ROM will be a perfect ROM to run once he updates his ROM (mostly tomorrow) to v1.0.1.
I would honestly upfmgrade to eb13. Yeah it has some problems but most of the problems have been patched. You could stay on stick rom and flash a.custom kernel that has the patches into it or flash a custom rom that will have the kernel built into it. As far as best ron's its up to but I like bonsai rom. Version 3.0.1 is getting ready to be released as I am a beta tester and it's very fast and stable and has all the carrier IQ removed. Good luck with your decusionr
Sent From My Evo Killer!
But if i get EB13 , would i b able to get Mobile AP, i like it cuz it pairs easy with my Samsung Galaxy tab and with tether my tablet never find my Epic 4g (wifi)
were can i download that custom EB13 ??? whats its name??? Syndicate rom it is??
I'm having the same issue. I'm wondering if I should even update to EB13, I just received a replacement Epic through Sprint and I don't want to run the chance of ruining my new phone with EB13. Especially with the data connectivity bugs, sd card, profile and prl not updating etc... (which I don't believe I had any of these issues, but not sure I want to take the chance). Is it OK to update, really?
dcraig723 said:
I'm having the same issue. I'm wondering if I should even update to EB13, I just received a replacement Epic through Sprint and I don't want to run the chance of ruining my new phone with EB13. Especially with the data connectivity bugs, sd card, profile and prl not updating etc... (which I don't believe I had any of these issues, but not sure I want to take the chance). Is it OK to update, really?
Click to expand...
Click to collapse
EB13 was working fine for me, noticeably faster! Although perhaps not so good a battery life... but I just made the jump to Syndicate. Couple issues, but they're being worked through and it is fantastically efficient as is. But if you update either way, do a fresh install. Avoid most of the issues you've read about by doing a clean install.
In my opinion I would upgrade, You cant make judgement on a few people mishaps. If anything you can just root & rom, after you upgrade.
Hello all,
I just received my shiny new HOX yesterday and it was working very well at first, however last night I updated it to the latest firmware (with Sense 4.1) and now it will not connect to the mobile network at all (no bars, won't find any networks when I manually search). I have noticed that it seems to be stuck in airplane mode.
Under airplane mode in the settings page it says "off", then a few seconds later it will say "turning off...", then it will go back to saying "off" and then back to "turning off.." and so on. I think it must be a bug in the firmware because I have tested the sim card in another phone (worked fine), and it was working fine before the update.
The only way to see if it is a bug in the firmware (as far as I am aware) would be to install a different ROM. However, I cannot find any way to install a new ROM (custom or stock) without unlocking the bootloader and therefore voiding the warranty (which I don't want to do in case it turns out to be a hardware issue).
I should also add that I could return the phone, but I would like to leave that as a last resort because I live in the middle of nowhere and trying to post stuff if a pain in the ass (and expensive).
I have also tried both a hard and soft reset, with no luck.
This is my first HTC device so I don't really know what I'm doing (although I have plenty of experience rooting and flashing my S2)
Any suggestions would be greatly appreciated
same prob
i've the same problem since the last update. hope it will fixed soon.
ms141289 said:
i've the same problem since the last update. hope it will fixed soon.
Click to expand...
Click to collapse
I'm glad I'm not the person having this problem . Does anyone know if it is definitely a firmware issue? (I might feel more confident about flashing a custom ROM if that's definitely the problem)
Anybody?
Maybe something went wrong with the OTA flash?
First thing HTC will do is flash the RUU to ensure it's back to stock. It will delete all your data, but it's worth a go.
You can use adb backup.
I updated to Android 4.2.2 some days ago, I tested somethings on it before realising the Wi-Fi didn't work. I didn't do much about it there and then, since I had to get up early the day after and it was getting late.
So I went to school and checked if the Wi-Fi worked there, it did.
I already tried a hard reset, and it looks like the phone finds the Wi-Fi in the setup phase, but then it goes back to "Not in range".
I didn't find anyone with a similar problem so I just thought I'd post it here.
Thanks in advance to anyone answering!
Norberedv1 said:
I updated to Android 4.2.2 some days ago, I tested somethings on it before realising the Wi-Fi didn't work. I didn't do much about it there and then, since I had to get up early the day after and it was getting late.
So I went to school and checked if the Wi-Fi worked there, it did.
I already tried a hard reset, and it looks like the phone finds the Wi-Fi in the setup phase, but then it goes back to "Not in range".
I didn't find anyone with a similar problem so I just thought I'd post it here.
Thanks in advance to anyone answering!
Click to expand...
Click to collapse
Is this update official or did you flash some custom ROM? If it's official, you should try some RUU to go back before the update and maybe update again, see if the issue persists. It it's custom, you should try re-flashing and if that doesn't help, try another ROM or maybe official.
Since you experienced this problem after updating, it's most likely software related.
unikulkiss said:
Is this update official or did you flash some custom ROM? If it's official, you should try some RUU to go back before the update and maybe update again, see if the issue persists. It it's custom, you should try re-flashing and if that doesn't help, try another ROM or maybe official.
Since you experienced this problem after updating, it's most likely software related.
Click to expand...
Click to collapse
It's the official update.
I'm not extremely good with these things.. So how would I use an RUU to revert to an old version?
Norberedv1 said:
It's the official update.
I'm not extremely good with these things.. So how would I use an RUU to revert to an old version?
Click to expand...
Click to collapse
You can learn HERE how to use RUU and how to find what version is right for your phone.