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.
Related
Folks,
My phone is rooted, h-boot. I can't load any custom roms, so I decided to just stick with the stock rom. I received the OTA ICS updated today in the US (t-mobile) and tried to update. It errors out giving me the exclamation sign and green android logo. I've done research and tried to flash the RUU, I've tried several RUU that I thought fits my phone description. Apparently not the case though. Any thoughts and help would be appreciated.
Here is my specs:
phone: HTC Sensation Z710e European non-branded T-mobile
on 2.3.4
Software: 1.50.401.1
baseband: 10.56.9035.OOU_10.14.9035.01_M
The OTA ICS update I received this morning is the following name:
OTA_PYRAMID_ICS_HTC_Europe_3.32.401.5_R-1.50.401.1_release_252072fll6erq
It was told at least a million times, that never install official OTAs on a rooted phone. Search the sticky/guide threads for solution.
And when flashing the correct RUU flash it from fastboot and make sure you have HTC drivers (come with HTC Sync) installed.
What's worse case scenario installing official OTA update on rooted phone? I don't care if i lose root or not. I just want ICS.
Problems without root
Hi,
I'm getting the same problem on an un-rooted phone.
The phone died half-way during the update download due to power outage/low battery.
So I deleted the old update file, which was half-downloaded and ran "Check for updates" again. This time it downloaded the complete file, but when it begins installation it's stuck for hours at the Android logo. The update doesn't seem to be installing. Had to re-boot the phone to get the old ROM back without ICS.
Any ideas how to fix this?
Some phones don't like the update mine didn't if you want to try
http://forum.xda-developers.com/showthread.php?t=1542555
[Fix] 3.32 firmware and bootloops fix
That's how I did mine
Sent from my HTC Sensation 4G using xda premium
I did a search and couldnt find the answer to this.
I have a TMOUS Sensation 4G, i went ahead and did s-off, rooted, and installed an ics rom. I loved the rom, but decided to go back to stock due to radio issues i just couldn't get figured out with multiple attempts. So, i'm back to current stock firmware and am un-rooted. The only thing i haven't done is gone back to s-on. Does anyone no if that will effect me getting the OTA to ICS when released?
Thanks for the help!
No being S-off will not keep you from getting the OTA update when it gets pushed. You just have to be running the 1.50 software and have the stock recovery.
Check out this thread and follow the instructions in order to install the ICS OTA.
Hey,
I have a telus HTC One S and they just released the Android v 4.1.1 (my current is 4.0.3)
I've rooted my phone and installed CWM. But i would like to undo this to install the new ota update to this version. I assume this means i will have to :
remove super User
lock my boot loader using fast boot
Then using the RUU_Ville_U_TELUS_WWE_1.70.661.1_Radio_0.16.31501S.02_10.18.31501S.08L_release_254554_signed.exe
file install the stock recovery and rom?
Is this correct or am i missing something.
hbforce
Thehurst said:
Hey,
I have a telus HTC One S and they just released the Android v 4.1.1 (my current is 4.0.3)
I've rooted my phone and installed CWM. But i would like to undo this to install the new ota update to this version. I assume this means i will have to :
remove super User
lock my boot loader using fast boot
Then using the RUU_Ville_U_TELUS_WWE_1.70.661.1_Radio_0.16.31501S.02_10.18.31501S.08L_release_254554_signed.exe
file install the stock recovery and rom?
Is this correct or am i missing something.
Click to expand...
Click to collapse
Right, go for it.
"IF I HELPED YOU HIT THANKS BUTTON"
.
You don't need to re-lock bootloader. Just remove superuser and restore stock recovery, then you are ready for OTA update.
So It worked but I encountered another issue, after the update was done my phone was unable to stay connected to the telus network.
it will connect to 4g with almost full bars for about 2 mins of which i can use data then it will disconnect me entirely, I can't search for the network or automatically configure it.
I took it to telus the sales guy played around with it reset the setting, nothing, then he Gave me a new sim (said it fixed his htc one which he did the same update last week) but it didn't work for me.
Does anyone know why this is happening or how i might fix it. They want me to sent my phone into for repairs but I don't want a loner phone for the 3 weeks it takes them to fix it.
I'm tempted to run the RUU again and sent my phone back to the stock 4.0.3 from 4.1.1 to see if it works and then try upgrading again.
Any advice?
maybe clear cache and possibly check the apn setting.
I tried that, and even factory recoveries with no luck so i returned it to Telus and hopefully it'll be repaired, It says re-locked and the tampered was removed so hopefully i don't get my warranty void'd if it is i'm sure i can down grade to the original os then load a custom rom and it should work
Just got my phone back from HTC
Despite having previously rooted my phone, they repaired it with no questions, and for free. Turns out my phone had a defective mainboard so once i updated the defect affected the phones ability to connect to the wireless network or something. But with the replaced board and with the new software update its working perfectly again.
I have ATT i727 Skyrocket that was at 4.1.x and working fine for months.
I rooted the phone about 6 months ago. All OK.
Yesterday phone locked up. I pulled battery to reboot. Phone stopped at Samsung word boot screen.
I got TWRP re-installed, then gingerbread tar 2.3.5 installed. phone now works.
Will not OTA to ICS. Will download, reboot and get to 25% and fail.
ODIN says YES 2 and Custom for ROM.
I can't find a tar image of ICS and would like to reset counter to zero, maybe unroot, go back to orig. firmware and then ICS.
Please, any suggestions? Thank you.
Alan - [email protected]
Go to sammobile.com for the stock firmware
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
alanmcbride said:
I have ATT i727 Skyrocket that was at 4.1.x and working fine for months.
I rooted the phone about 6 months ago. All OK.
Yesterday phone locked up. I pulled battery to reboot. Phone stopped at Samsung word boot screen.
I got TWRP re-installed, then gingerbread tar 2.3.5 installed. phone now works.
Will not OTA to ICS. Will download, reboot and get to 25% and fail.
ODIN says YES 2 and Custom for ROM.
I can't find a tar image of ICS and would like to reset counter to zero, maybe unroot, go back to orig. firmware and then ICS.
Please, any suggestions? Thank you.
Alan - [email protected]
Click to expand...
Click to collapse
Here are som ICS TARs:
Rogers Canada (imo less bloatware than AT&T):
http://hotfile.com/dl/163303882/02796f1/
AT&T USA:
http://hotfile.com/dl/162903193/644c77d/
Telcel Mexico (someone said it has a sim lock, read here):
http://hotfile.com/dl/182237393/93f6637/
everything u need is in the sticky NEWB GUIDES To: | RESTORE TO STOCK
how did u increase your counter, its been ages since there was a tar file that did that
Hello I rooted my i997r infuse rogers but the com# in oden was in the wrong box and it saied succesful /failed one but I didn't think much of it I was so exited that it worked I upgraded from 2.3.3 to 2.3.6 AT&T firmware thinking i have to in order to install ics I then installed cms 10 J.B 4.3 my phones runs great better than ever before execpt for the fact that my screen takes about one minute to turn on with lines I think its called rainbowing im not sure I think it has something to do with my original root that messed up my screen so I want to downgrade to stock using odin and reinstall and hopefully my screen won't be messed up so I used http://forum.xda-developers.com/showthread.php?t=1193927 it was successful I used the Odin_UXKG3_rooted_no_bootloaders_v2.zip then Odin_Stock_Rogers_UXKG3_Kernel.zip and my screen now has a shade of gray with this shade of blue this blue shade that covers the screen right when I turn it on it keeps getting worse it goes away after a couple minutes in recovery mode but now I just don't know what to do I can't even use my phone now help me please! How do I fix my video driver I guess this is whats going on help I can't seem to find a working link for CWM-UXKG3-rooted-de-odexed-update-v2.zip maybe if I install the cwm the light neon blue screen will go away?
crayzze said:
Hello I rooted my i997r infuse rogers but the com# in oden was in the wrong box and it saied succesful /failed one but I didn't think much of it I was so exited that it worked I upgraded from 2.3.3 to 2.3.6 AT&T firmware thinking i have to in order to install ics I then installed cms 10 J.B 4.3 my phones runs great better than ever before execpt for the fact that my screen takes about one minute to turn on with lines I think its called rainbowing im not sure I think it has something to do with my original root that messed up my screen so I want to downgrade to stock using odin and reinstall and hopefully my screen won't be messed up so I used http://forum.xda-developers.com/showthread.php?t=1193927 it was successful I used the Odin_UXKG3_rooted_no_bootloaders_v2.zip then Odin_Stock_Rogers_UXKG3_Kernel.zip and my screen now has a shade of gray with this shade of blue this blue shade that covers the screen right when I turn it on it keeps getting worse it goes away after a couple minutes in recovery mode but now I just don't know what to do I can't even use my phone now help me please! How do I fix my video driver I guess this is whats going on help
Click to expand...
Click to collapse
Read this:
http://forum.xda-developers.com/showthread.php?t=1613523
Thanks I read the part about the bootloaders I flashed to gb 2.3.6 and then flashed the bootloaders hoping it would fix the blue screen i always get and have to wait 5 minutes to go away every time turn m screen on it just isin't when I power my phone on its whenever I turn my screen on I can't see anything when someone calls me I have to wait, im on a rogers infuse and I hope this isn't a permanent bug. I went back to 2.3.3 gb stock I don't have a rogers boot logo anymore but it runs fine execpt for this light neon blue that covers the screen does anyone else ever have this problem please help.
crayzze said:
Thanks I read the part about the bootloaders I flashed to gb 2.3.6 and then flashed the bootloaders hoping it would fix the blue screen i always get and have to wait 5 minutes to go away every time turn m screen on it just isin't when I power my phone on its whenever I turn my screen on I can't see anything when someone calls me I have to wait, im on a rogers infuse and I hope this isn't a permanent bug. I went back to 2.3.3 gb stock I don't have a rogers boot logo anymore but it runs fine execpt for this light neon blue that covers the screen does anyone else ever have this problem please help.
Click to expand...
Click to collapse
rainbow screen on recovery = no gb bootloaders
blue screen on phone ...maybe bad cable connection or corrosion at contact
you might have to open it and check the connections
Working and tested CWM 1.2 ghz
Phase 1:
---------
To obtain CWM head over too Jscotts odin url.
1. download the file which includes root access.
"Stock UCLB3 with root
UCLB3_Unbrick_root_1.1.zip"
2. you will also need Samsung Kies, which will install the usb driver for your Samsung galaxy. The link is on the website.
3. Place your phone into Download mode
To do this, have your usb cable for your phone plugged into the computer but disconnected from your phone. shut off your phone. When the power is off press Volume up and Volume down simultaneously, after the buttons are pressed plug in the usb cable at the same time, which should be connected to the computer.
This will place the phone in Download mode.
4. open the included Odin.exe, when you see the yellow bar under ID:COM then everything is good.
Follow the rest of the instructions on jscotts website.
Finally when this procces is done, reboot into android.
Phase 2:
---------
1) Download SGS kernel flasher
2) Click on the link on jscotts website to download a stock kernel which contains CWM. use "2013.04.30-CWM-Synthesis-1.2Ghz.zip in the following link:
forum.xda-developers.com/showthread.php?p=25724638
You now have a working GB cwm and next is follow Enthropy's CM9 guide for your first ROM!
Fullmetal Jun said:
Phase 1:
---------
To obtain CWM head over too Jscotts odin url.
1. download the file which includes root access.
"Stock UCLB3 with root
UCLB3_Unbrick_root_1.1.zip"
2. you will also need Samsung Kies, which will install the usb driver for your Samsung galaxy. The link is on the website.
3. Place your phone into Download mode
To do this, have your usb cable for your phone plugged into the computer but disconnected from your phone. shut off your phone. When the power is off press Volume up and Volume down simultaneously, after the buttons are pressed plug in the usb cable at the same time, which should be connected to the computer.
This will place the phone in Download mode.
4. open the included Odin.exe, when you see the yellow bar under ID:COM then everything is good.
Follow the rest of the instructions on jscotts website.
Finally when this procces is done, reboot into android.
Phase 2:
---------
1) Download SGS kernel flasher
2) Click on the link on jscotts website to download a stock kernel which contains CWM. use "2013.04.30-CWM-Synthesis-1.2Ghz.zip in the following link:
forum.xda-developers.com/showthread.php?p=25724638
You now have a working GB cwm and next is follow Enthropy's CM9 guide for your first ROM!
Click to expand...
Click to collapse
Thank you but it's not bricked... are you suggesting this will take away the screen issue?... k so it's been a while since I used my infuse the screen was getting so annoying that I put it away for a month last night I turned it on and the screen seemed fine, I was very pleasantly surprised I re rooted it and put on the new cm10 jellybean and noticed the longer I kept using the screen the more the lines/screen problem came back I left it untouched overnight after modding it and this morning it's fine again until continued use of the screen... I have taken it apart and unplugged all the screen plugs reattached looked around everything seemed fine so I dunno... I have a really newbie question for the way I went about getting to jellybean from stock... first I rooted it with Odin_Infused_Gingerbread_Kernel_v1 and noticed that cwm was installed so is this all I need to proceed with installing ics? because I kept thinking I needed to install 2.3.6 and that is not firmware meant for my phone and thats what I think might be the cause of my screen issue sooo do I just need to root it first then go straight to ics or do I need to put 2.3.6 then ics?
I am on a rogers infuse.
crayzze said:
Thank you but it's not bricked... are you suggesting this will take away the screen issue?... k so it's been a while since I used my infuse the screen was getting so annoying that I put it away for a month last night I turned it on and the screen seemed fine, I was very pleasantly surprised I re rooted it and put on the new cm10 jellybean and noticed the longer I kept using the screen the more the lines/screen problem came back I left it untouched overnight after modding it and this morning it's fine again until continued use of the screen... I have taken it apart and unplugged all the screen plugs reattached looked around everything seemed fine so I dunno... I have a really newbie question for the way I went about getting to jellybean from stock... first I rooted it with Odin_Infused_Gingerbread_Kernel_v1 and noticed that cwm was installed so is this all I need to proceed with installing ics? because I kept thinking I needed to install 2.3.6 and that is not firmware meant for my phone and thats what I think might be the cause of my screen issue sooo do I just need to root it first then go straight to ics or do I need to put 2.3.6 then ics?
I am on a rogers infuse.
Click to expand...
Click to collapse
Re-reading your thread, I realized that you have a i997R - Roger's. These come stock GB 2.3.4 - unlike the i997-ATT that started with 2.2.1
The difference is that the i997R has already built in bootloaders from the start. That means that Roger's phone do not get the distorted recovery with flashing we termed as "rainbow." The rainbow is fixed with a bootloader flash. Roger's phone do not need this step.
I think the color distortion you are seeing could be due to a heating issue, the screen or the graphics chip. More likely than not, this may be hardware related.
If you have opened and cleaned out the connections and such, and have not noted any difference, then the problem may be deeper situated. Further testing may require another Infuse and swapping out parts to see where the issue lies.
gl
Help!
qkster said:
Re-reading your thread, I realized that you have a i997R - Roger's. These come stock GB 2.3.4 - unlike the i997-ATT that started with 2.2.1
The difference is that the i997R has already built in bootloaders from the start. That means that Roger's phone do not get the distorted recovery with flashing we termed as "rainbow." The rainbow is fixed with a bootloader flash. Roger's phone do not need this step.
I think the color distortion you are seeing could be due to a heating issue, the screen or the graphics chip. More likely than not, this may be hardware related.
If you have opened and cleaned out the connections and such, and have not noted any difference, then the problem may be deeper situated. Further testing may require another Infuse and swapping out parts to see where the issue lies.
gl
Click to expand...
Click to collapse
Yes I bootloader flashed it in desperation with an at&t bootloader and now lost the rogers bootloader lol... My phone came stock 2.3.3 gb and I desperatly wanted gb 2.3.6 so I rooted it and did so, then after discovering ics and then after jb... I believe that installing 2.3.6 might have damaged the hardware being that its only ment for at&t i997's or possibly a combination of 2.3.6 and then installing ics then jb or whatever the case may be my screen needs 1 to 5 minutes to fully appear... my question is if I ever happen to root another rogers i997 do I need to upgrade to 2.3.6 before installing ics or can I install right after root? Because I also might re root the phone back to stock and root it then install the newer version of ics then jb cm 10.2... I am currently running on jb cm 10.2 do you think it would make a difference if I rerooted to stock then install newer ics then jb with upgrading to 2.3.6 for at&t phones??? Thank you.
crayzze said:
Yes I bootloader flashed it in desperation with an at&t bootloader and now lost the rogers bootloader lol...
Click to expand...
Click to collapse
no big deal..same phone..same hardware..different version of firmware..it's the APN for providers that makes the difference
crayzze said:
My phone came stock 2.3.3 gb and I desperatly wanted gb 2.3.6 so I rooted it and did so, then after discovering ics and then after jb... I believe that installing 2.3.6 might have damaged the hardware being that its only ment for at&t i997's or possibly a combination of 2.3.6 and then installing ics then jb or whatever the case may be my screen needs 1 to 5 minutes to fully appear.
Click to expand...
Click to collapse
yes..you are right. Rogers came with 2.3.3 not 2.3.4 as I previously stated.
the earlier versions of gb came with Carrier IQ that track users. It was taken out later.
I doubt Installing 2.3.6 or ICS or JB will cause any prob with the phone. I suspect your phone may have some hardware issues.
After the first flash, the os (esp ICS or JB) may need time to build cache and dalvik..sometimes it may take a few minutes. Blue or distorted screen, however, is not typical from my experience.
crayzze said:
my question is if I ever happen to root another rogers i997 do I need to upgrade to 2.3.6 before installing ics or can I install right after root? Because I also might re root the phone back to stock and root it then install the newer version of ics then jb cm 10.2... I am currently running on jb cm 10.2 do you think it would make a difference if I rerooted to stock then install newer ics then jb with upgrading to 2.3.6 for at&t phones??? Thank you.
Click to expand...
Click to collapse
IMO, it doesn't matter how you get to CM10.2. Rooting is just one method. The idea is to get insecure recovery...ie..cwm.
from stock rom, you can odin or heimdall a custom kernel without rooting. boot into recovery and flash what you want.
it doesn't matter if its rogers or att. same phone..same hardware. years ago, it only mattered when a user had to return or exchange the phone for warranty...after the warranty period ended..it's not a big deal.
flash away at any method you want. it doesn't make any difference in my mind. get some practice..the infuse has many restore methods via odin or heimdall
rooting gives one access to the root directory
insecure kernel or custom recovery allows one to flash firmware without manufacturer signature