After updating to the OTA 4.3 my S3 now has a glitch causing the screen to occasionally black out, mostly during phone calls but also after screen timeouts when i hit the power button to turn the screen back on it'll stay black for awhile, the menu and back buttons light up and the touch sensor still works even when black. it work flawlessly before the update. I tried to root and was successful at it using the saferoot method but because of the know being lock I can not install a custom rom or recovery and the problem was still there because I was still using the 4.3 rom. So I used odin3 vs3.07 and put the stock rom back on and unrooted and the problem is still there. does anyone know how to fix this glitch or does anyone know how i can go back to the 4.2.1 rom or install the 4.4.2 rom because 4.3 has been nothing but a headache for me.
johnwilliams-84 said:
After updating to the OTA 4.3 my S3 now has a glitch causing the screen to occasionally black out, mostly during phone calls but also after screen timeouts when i hit the power button to turn the screen back on it'll stay black for awhile, the menu and back buttons light up and the touch sensor still works even when black. it work flawlessly before the update. I tried to root and was successful at it using the saferoot method but because of the know being lock I can not install a custom rom or recovery and the problem was still there because I was still using the 4.3 rom. So I used odin3 vs3.07 and put the stock rom back on and unrooted and the problem is still there. does anyone know how to fix this glitch or does anyone know how i can go back to the 4.2.1 rom or install the 4.4.2 rom because 4.3 has been nothing but a headache for me.
Click to expand...
Click to collapse
It is currently impossible to downgrade the firmware. If you took the 4.3 OTA, you're stuck with it. As far as bugs, they are being addressed by Verizon and a patch should come soon. Meanwhile, you can try reflashing the 4.3 firmware with Odin to see if that clears up any issues.
Sorry you're having trouble, buddy.
Sent from my SCH-I535 using Tapatalk
Related
Ok, Here goes. FIrst off I would like to say I am on a 32GB Note 10.1 N8013 which has been rooted with the CWM method and I am also past my return and exchange window at Best Buy.
A few days ago my S-pen suddenly stopped working suddenly. Every time I removed it from the tablet touch would stop working completely and i would have to reboot the tablet. (the popup menu would still disappear when i put the pen back in the slot). I looked in the forums and saw that some people had similar issues, such as Mitchellvii here: http://forum.xda-developers.com/showthread.php?t=1848838&highlight=not+working
I tried everything in that thread from flashing stock kernel, recovery and UEALH2 firmware (both pre-rooted by Entropy and bone stock from Jaaka), but nothing works. Now every time the tablet goes to sleep the touch is unresponsive and I have to reboot. The S-pen still does not work and I have no idea what to try next.
Any ideas would be greatly appreciated.
-jjflemin
Mods can delete this. Everything works again after flashing stock UEALH2 from Jaaka, flashing Entropy's Triangle Kernel and rooting with CWM method. Kind of strange that the pen didn't work until it was rooted again.
wait, so are you saying that you managed to get the S pen working again after flashing stock UEALH2 and Entropy's kernel, but after you rooted the note it stopped working again?
Where is this triangle kernel you're speaking of? None of entropy's posts mention triangle kernel, I only see stock, rooted stock and CM posts.
Sent from my LG-P920 using xda app-developers app
EDIT:
I got it to work:
1. Flash this:
http://forum.xda-developers.com/showthread.php?t=1849994
2. Flash the UEALH2 from here:
http://forum.xda-developers.com/showthread.php?t=1853209
that should do the trick. Installing CWM and SuperSU did not fix the problem for me. Flashing rooted stock and kernel did.
http://forum.xda-developers.com/showthread.php?t=1849015
That is Entropy's kernel with triangle away support.
What I meant was that it didn't work right away once I flashed UEALH2 and stock kernel, but started working again when I rooted it with the CWM method. Really not sure why that would be.
Will I need to flash the stock kernel back on my phone to take the OTA or will it work with Imo's kernel? I tried to reflash the boot.img from my nandroid and wifi was not working, so I reflashed Imo's kernel and wifi works again and I am sitting in a holding pattern. I'd rather not have to ODIN back to full stock because I only have access to PC's at work and don't really have time in the day at work to be doing stuff like that while there.
Also can I just download EZ Recovery and flash the stock recovery?
Phone is rooted, unlocked, CWM with Casual and Imo's Lean Touchwiz kernel. TIA
What exactly makes you want the update? If it's the radio (which imo is the only reason to consider the OTA) then just get the radio and flash it in CWM.
i already have the radios flashed but I've had this weird issue that seems to only happen after flashing the kernel but has only happened on a few occasions mainly on the weekends at my daughter's 2 soccer games to be exact. Camera and video have acted weird, first was video controls were upside down, had to reboot a few times for it to fix and just yesterday everything I shot shows fine in gallery but when I go to import into Instagram the pics are all rotated 90 degrees.
I can't afford to have data issues which is the reason I haven't installed a custom ROM since I use my phone for work quite a bit. Figured go back to stock kernel, take OTA to clean out any weird issues that would linger and wait for either official JB or for ROMs to get solid on data issues.
mav3rick478 said:
Also can I just download EZ Recovery and flash the stock recovery?
Phone is rooted, unlocked, CWM with Casual and Imo's Lean Touchwiz kernel. TIA
Click to expand...
Click to collapse
Yes, but remember if you don't already have the OTA notification nothing with come just because you removed the custom recovery. If you've already received that notification then disregard this post.
Sent from my SCH-I535 using xda app-developers app
Thanks Snoop, been getting the OTA notification for 2 weeks now. I thought originally after it failed because of CWM it disappeared but woke up a few mornings to my phone being in CWM asking if i wanted to install the OTA and thinking to myself, "good god how long has my screen been on?!"
mav3rick478 said:
Thanks Snoop, been getting the OTA notification for 2 weeks now. I thought originally after it failed because of CWM it disappeared but woke up a few mornings to my phone being in CWM asking if i wanted to install the OTA and thinking to myself, "good god how long has my screen been on?!"
Click to expand...
Click to collapse
No problem. If you still notice weird issues then Odin to an older firmware and accept the OTA from there.
Sent from my SCH-I535 using xda app-developers app
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
I have searched high and low for help getting Kitkat to work on my phone. Here is the background to my problem:
I rooted my Bell Note 3 (Canadian) phone running JB. After doing so I then put a CWM recovery and then flashed with a custom JB rom. Everything works great and yes I do know that I have tripped the KNOX counter. So when the new Kitkat was released I wanted to upgrade to it. I downloaded the original Bell stock JB rom and the stock KK rom. I also downloaded Odin. I tried to flash back to the stock JB rom like I should before updating to Kitkat and while doing so and with Odin I keep getting errors not allowing me to revert back to stock. I know when I boot up I get a notification in the top left corner saying on two separate line exactly like you see it below.
KERNEL IS NOT SEADROID ENFORCING
Set Warranty Bit : kernel
My question is to whoever knows the solution to how to return back to stock JB and then flash KK rom. I have a feeling it has something to do with what is in the left corner when I boot like you see above. If there is a fix please let me know and if I am totally wrong and the problem and fix is something else please feel free to help me. I have been flashing custom roms since Android has been around. This problem has me baffled and don't know what to do from here to get me back to JB then to KK.
I updated to the new firmware (4.4.4) this weekend. Everything is working great, except the g-sensor seems to be a bit wonky... Often, the screen does not auto-rotate. Also, I use Screeble Pro app to keep the screen on when not laying flat and it consistently thinks the phone is laying flat when it is not (did that make sense?). I've tried the basic calibrate function in the settings, but that did not help. Also, flashed the new firmware with both the RUU. and SD card methods... Even went back to 4.4.3 firmware with no change... Anyone else having this issue? Any ideas? Thanks for the help.
Sent from my HTC6525LVW using Tapatalk
OK, update... The sensor info to Screebl seems to be working, but the auto rotate (can't even force it to landscape) stopped working at all.
Sent from my HTC6525LVW using Tapatalk
Did you flash the firmware via ADB? Did you flash it 2x??
I had an issue with my IR blaster after I updated to 4.4.4. Could have been caused by my not flashing the firmware twice, or because of non-matching firmware/rom.
Freedom First said:
Did you flash the firmware via ADB? Did you flash it 2x??
I had an issue with my IR blaster after I updated to 4.4.4. Could have been caused by my not flashing the firmware twice, or because of non-matching firmware/rom.
Click to expand...
Click to collapse
Flashed it twice... via fastboot RUU method (as well as with the SD card method) I am currently running a 4.4.3 based ROM (ViperOne 2.5). Am hoping that when that ROM gets updated to the 4.4.4 version and I do a clean install maybe the problem will go away...