Unrooted and downgraded to RC7 yesterday.
Followed this one
http://forum.xda-developers.com/showthread.php?t=491350
Its been 24 hours. I still havent got the RC9 or even RC8 upgrade!
Tried Anycut - Device Info - Check for upgrade
How long Im supposed to wait?
Related
Hi!
I have JF 1.42 RC 33 with root enabled on my G1 from polish network Era.
Then I've decided to switch to JF 1.5 ADP, so first I've installed radio update from htc web page and after this i 've installed 1.5. After succesfull instalation my phone restarts after few minutes and loops on android logo. It is immposible to switch it off. I can only take off battery. Only way to use it once again is to go to recovery mode, then wipe it, and install JF 1.5 one more time. But after this my phone once again is working till first reboot. I've tryied JF 1.5, the Dudes and Hayakuro updatesl but it is same situation. Reboot and loop on android logo.
Now I have JF 1.43 RC9 and new radio 2.22. I've also tryied to install one more time radio update and JF 1.5 update, but it doesn't help. What elsa I can do?
Also I have newest version on Hard SPL. But I did't changed it since I've rooted phone.
szymarek said:
Hi!
I have JF 1.42 RC 33 with root enabled on my G1 from polish network Era.
Then I've decided to switch to JF 1.5 ADP, so first I've installed radio update from htc web page and after this i 've installed 1.5. After succesfull instalation my phone restarts after few minutes and loops on android logo. It is immposible to switch it off. I can only take off battery. Only way to use it once again is to go to recovery mode, then wipe it, and install JF 1.5 one more time. But after this my phone once again is working till first reboot. I've tryied JF 1.5, the Dudes and Hayakuro updatesl but it is same situation. Reboot and loop on android logo.
Now I have JF 1.43 RC9 and new radio 2.22. I've also tryied to install one more time radio update and JF 1.5 update, but it doesn't help. What elsa I can do?
Also I have newest version on Hard SPL. But I did't changed it since I've rooted phone.
Click to expand...
Click to collapse
There are actually a few threads for people running into issues including myself. Mine turned out to be an issue form apps2sd that I have in my thread
http://forum.xda-developers.com/showthread.php?t=511709
There is also http://forum.xda-developers.com/showthread.php?p=3731933
and http://forum.xda-developers.com/showthread.php?t=511955
i bricked one HTC Dream (G1) Black PVT 35 with new radio but **** it, i went and bought another g1 and was bold enough to try again and it worked, so that was cool, installed the newest haykuro update and learned i didnt like it as much as i liked jf 1.5, so i downloaded the newest jf 1.5 build and flashed my phone to it and it sits on the g1 screen, so i was like omg, thinking i bricked my new g1, but i didnt i was able to get back in the bootloader, so i whiped again and tried my famous jf 1.5 and it sat on the g1 screen again, so i said wtf, so i went back to the haykuro build, i decided to choice the g build since its the one i like, and it worked fine and went passed the g1 screen, so with the new sql, im i only limited to HTC Magic builds ??
1st G1 really bricked? maybe you can access adb even if you're in G1 screen?
Cant explain why, but i've personally run HK 6.0 (current) and dudecake 1.1 (plan on returning for 1.2 release) and roomate is on JF 1.5, all with new SPL
ESKIMOn00b said:
Cant explain why, but i've personally run HK 6.0 (current) and dudecake 1.1 (plan on returning for 1.2 release) and roomate is on JF 1.5, all with new SPL
Click to expand...
Click to collapse
umm interesting, yea i gave up on the first g1, its dead lol theres not going to be a fix to that, the computer doesnt even reconize it when its sitting on the g1 screen, imma add insurance, wait a month and send the bricked one in as it malfunctioned and just resell the one they send me to cover my lost.
but anyways i guess i will try the jf 1.5 again, maybe if i redownload it , i might get lucky
ESKIMOn00b said:
Cant explain why, but i've personally run HK 6.0 (current) and dudecake 1.1 (plan on returning for 1.2 release) and roomate is on JF 1.5, all with new SPL
Click to expand...
Click to collapse
after 2 hours i figured it out, since i had a new g1 i had a new sdcard, it was not Partitioned, i did the FAT32 / EXT2 Partitions on the MicroSD and tried my famous jf 1.5 and it worked fine
yea wait for a month and wait for the mass cupcake update and tell them that you're phone died while updating the cupcake lolz
jrherras said:
yea wait for a month and wait for the mass cupcake update and tell them that you're phone died while updating the cupcake lolz
Click to expand...
Click to collapse
lol even better idea, i sure in the hell will do that
OR tell them you thought your G1 froze while updating then you took the battery out
sorry for making yet another "i need help thread" but i need some help.
i had a D2G on the latest OTA GB, SBF'd back to Froyo (blur version 2.4.330) to get on CM7 (now i decided i just want stock). and since the phone is no longer activated, i cannot use System Update (it is greyed out). How can i update to the latest GB? just SBF to the latest? i just dont wanna mess up the phone any more than i already have. any help is really appreciated!
Flashing the SBF for 4.5.608 would be the best solution.
I'm also not quite sure why System Update is not available for you; it doesn't depend on activation at all. I've never had my phone activated on VZW and yet system update worked perfectly.
ok i will do that now, thank you for the help, it is much appreciated!
I have been reading around for a day or so now and am a bit stuck
Here is the problem
I had to send my phone back for repair as it had stopped charging (BTW I did not return it to stock or unroot etc. Sent as was running elegancia rom, rooted s=off and supercid11111111)
They just replaced the Mobo and sent it back (4 day turn around)
It came back with GB 2.3.4.
I applied s=off from rev no problems then could not get it to boot as I also updated the firmware to 3.32 as I wanted to go back to elengancia.
Got round that by downgrading the firmware to 3.12 and was just about to apply latest firmware 1 step at a time when I was offered a OTA update to android 4.03. nice (I thought) that will sort all the firmware out for me.
Now I can not s= off as rev says there is no phone attached (adb fastboot says there is)
I cannot root either and cannot install a custom recovery???
any help please.
Hello all,
Long time reader, just started posted recently. I bought my HTC One S when it first came out, and immediately rooted it and installed the ViperOneS Rom on it. I never got the chance to recieve the OTA updates for JellyBean or any of the other firmware updates. Now, as I was reading the CM10.1 thread, it said that certain firmware updates were required to install the new nightlies. I figured it was time to RUU my phone to stock with the newest firmware, and then re-root it so that I can take advantage of the 3.4.x kernel in the new CM 10.1 releases. Anyway, I went to www.shipped-roms.com and went to ville, and saw that the newest release appeared to be the :
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
....However, on my HTC One S news app, I looked back about two months, and it showed that Tmobile released a new RUU/OTA on June 24th, 2013. That build was labeled
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.17_Radio_1.13.50.05.31_10.30.50.08L_release_320836_ICS_2_JB.exe
Now, the one on Shipped-Roms has the 3.16.x build as opposed to the Tmobile's 3.14.x. But the Tmobile has a higher number after the "release" at the end of the exe, being 320836 as opposed to 301814 on the Shipped-Roms RUU.
So does anyone know which one is truly the most recent firmware for the HTC One S. I went and installed the Tmobile One, im going to play around with it for a day or two before I root it again. It was said one of the reasons TMobile released this was to address battery drain issues for jellybean users.
The entire article is available here : https://support.htc.com/en-us/080-H...HTC_One_S™_for_T-MOBILE_ROM_Update_|6.24.2013
I ran the RUU with no problems and am now running stock, until I decide to root again. I basically posted this to make people aware that their might be a newer firmware available than the one they are using, and it isn't on any of the RUU list such as Shipped-Roms. Anyway, if I experience any problems with it, I will post. Take care - dRedmentia
dredmentia said:
Hello all,
Long time reader, just started posted recently. I bought my HTC One S when it first came out, and immediately rooted it and installed the ViperOneS Rom on it. I never got the chance to recieve the OTA updates for JellyBean or any of the other firmware updates. Now, as I was reading the CM10.1 thread, it said that certain firmware updates were required to install the new nightlies. I figured it was time to RUU my phone to stock with the newest firmware, and then re-root it so that I can take advantage of the 3.4.x kernel in the new CM 10.1 releases. Anyway, I went to www.shipped-roms.com and went to ville, and saw that the newest release appeared to be the :
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
....However, on my HTC One S news app, I looked back about two months, and it showed that Tmobile released a new RUU/OTA on June 24th, 2013. That build was labeled
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.17_Radio_1.13.50.05.31_10.30.50.08L_release_320836_ICS_2_JB.exe
Now, the one on Shipped-Roms has the 3.16.x build as opposed to the Tmobile's 3.14.x. But the Tmobile has a higher number after the "release" at the end of the exe, being 320836 as opposed to 301814 on the Shipped-Roms RUU.
So does anyone know which one is truly the most recent firmware for the HTC One S. I went and installed the Tmobile One, im going to play around with it for a day or two before I root it again. It was said one of the reasons TMobile released this was to address battery drain issues for jellybean users.
The entire article is available here : https://support.htc.com/en-us/080-H...HTC_One_S™_for_T-MOBILE_ROM_Update_|6.24.2013
I ran the RUU with no problems and am now running stock, until I decide to root again. I basically posted this to make people aware that their might be a newer firmware available than the one they are using, and it isn't on any of the RUU list such as Shipped-Roms. Anyway, if I experience any problems with it, I will post. Take care - dRedmentia
Click to expand...
Click to collapse
higher numbers not always newer builded software, since jb for the unbranded was released several months sooner than the tmobile one the higer number is logical. However there has been a ota for the unbranded going to 3.16.401.9
watch out, many people got bricked wanting to update there already updated firmware to the newest.
if its already on jb firmware and works flawlessy leave it as is, or take the risk.
real187 said:
higher numbers not always newer builded software, since jb for the unbranded was released several months sooner than the tmobile one the higer number is logical. However there has been a ota for the unbranded going to 3.16.401.9
watch out, many people got bricked wanting to update there already updated firmware to the newest.
if its already on jb firmware and works flawlessy leave it as is, or take the risk.
Click to expand...
Click to collapse
I installed the Tmobile Jan 24th RUU no problem. As I said, I rooted my phone right when I got home from the Tmobile store, so it was still running the original firmware it came with. Now Its up to date, running CM 10.1 flawlessly with the 3.4 kernel, and overall seems quicker and more responsive. Now hopefully the battery life issue gets resolved, that was the only problem I was having before. Thank you though, from what I understand this will be the last firmware update from Tmobile, so I will never have to go through that process again. The HTC One S still holds its own as a great phone, I don't see any need to upgrade anytime soon.
are you dunning CM10.1 nightlies? is it stable? Any issues with camera/ bluetooth/ 4g?
Do we need s-off for that?
myechophone said:
are you dunning CM10.1 nightlies? is it stable? Any issues with camera/ bluetooth/ 4g?
Do we need s-off for that?
Click to expand...
Click to collapse
Actually I am running the August 13th CM10.1 Nightlie, and the camera works, bluetooth works, but my damn 4g is not connecting. All my mobile data settings keep getting stuck on Edge network or worse. It said it would have taken 10 hours to download a 150 mb file....I didn't notice until I left my house earlier today because it was my day off so I didn't use my phone for work. It was working flawlessly on wifi, thought everything was going good, and once I started driving around the service would go in and out, and never made it to 4g once, I think in one or two spots it hit 3g, but most of the time it was stuck on EDGE:2 in the Phone Settings. If I can't get this issue fixed I will go back to the stable CM10, which sucks because that doesn't use the new 3.4 kernel, or use a different ROM based on that kernel.