I installed the OTA update on my stock AT&T HTC One M9 today to bring it up to 2.6.502.16 (Android 5.1). Afterwards, I performed a Factory Reset to start off with a clean slate. As I was setting it up, I noticed that the Motion Launch gestures were not working (I used the power on gesture all the time prior to the update). I've toggled the settings and even tested with them set to OFF/unchecked with no success. I've restarted a few times as well.
Anyone else seeing similar behavior?
I just completed the update a bit ago and am not having any issues with motion launch gestures.
fernandezhjr said:
I just completed the update a bit ago and am not having any issues with motion launch gestures.
Click to expand...
Click to collapse
Since you didn't mention it, I assume you haven't Factory Reset since?
chp said:
Since you didn't mention it, I assume you haven't Factory Reset since?
Click to expand...
Click to collapse
Correct, no factory reset.
I have the same issue after updating. I did a FDR and still can't get motion gestures to work. I calibrated the G-sensor and even downgraded the lock screen to a previous version and still no luck.
Weird. I returned to stock last night by running the 1.32 RUU, the took the OTA and MLG worked fine. Then, today, I ran the new 2.6 RUU and now MLG doesn't work.
No Issues with my update, did not reset.
I also can't get the notification menu to pull down during a phone call. This update sucks
My ota failed last night so I had to ruu to 1.32 then took the ota from their, my gestures have all worked fine, they occasionally miss and don't wake but they have never been 100% reliable anyway but work just as they did before for me.
The status bar during call issue I did notice, weird and kind of annoying has to be a bug cause it starts to pull down but then bugs out, will work fine and pull down if the call is on speaker
Sent from my HTC One M9 using Tapatalk
Did the update and then a Full Reset. Motion Gestures won't work now.
fade79 said:
Did the update and then a Full Reset. Motion Gestures won't work now.
Click to expand...
Click to collapse
And they worked prior to the full reset?
jollywhitefoot said:
And they worked prior to the full reset?
Click to expand...
Click to collapse
Yep before the update they worked fine. Strangely enough I just noticed that if I'm on the lock screen I can do the Double Tap to turn off the screen. But I can't do the same to wake it. Also can't get use the volume buttons to start the camera also. So the sensor is working. Must be some kind of software bug in the update.
fade79 said:
Yep before the update they worked fine. Strangely enough I just noticed that if I'm on the lock screen I can do the Double Tap to turn off the screen. But I can't do the same to wake it. Also can't get use the volume buttons to start the camera also. So the sensor is working. Must be some kind of software bug in the update.
Click to expand...
Click to collapse
Definitely not firmware or hardware, because I'm on a custom rom now and MLG works fine.
What I was asking, though, is after you took the OTA, but before you did the reset, did they work? Mine worked last night after I upgraded from 1.32 to 2.6 via OTA, but today I ran the 2.6 RUU and they didn't work after that. So the full reset and the RUU are probably just wiping a setting or file that breaks MLG.
jollywhitefoot said:
Definitely not firmware or hardware, because I'm on a custom rom now and MLG works fine.
What I was asking, though, is after you took the OTA, but before you did the reset, did they work? Mine worked last night after I upgraded from 1.32 to 2.6 via OTA, but today I ran the 2.6 RUU and they didn't work after that. So the full reset and the RUU are probably just wiping a setting or file that breaks MLG.
Click to expand...
Click to collapse
I can't remember if it worked after the OTA and before the reset. The first thing I noticed after the OTA was that it was lagging a little so I just did a reset right off the bat.
For me It didn't work before the reset so I reset and still no luck also WiFi is sketchy
fade79 said:
Yep before the update they worked fine. Strangely enough I just noticed that if I'm on the lock screen I can do the Double Tap to turn off the screen. But I can't do the same to wake it. Also can't get use the volume buttons to start the camera also. So the sensor is working. Must be some kind of software bug in the update.
Click to expand...
Click to collapse
Good to see I am not the only one. As you pointed out, at the lock screen, double-tap to sleep does work.
I tried to downgrade using the 1.32.502.31 RUU but could never get it to work. I'm going to try the 2.6.502.16 RUU just for giggles to see if anything changes.
My motion controls worked perfectly before installing 5.1. I was on 5.0.2 stock rooted s-on prior to installing via RUU from HTC's website. Now double tap to wake doesn't work! I can double tap the lock screen to sleep, and auto rotate works. I've factory reset to no avail . Calibrated g sensor to no avail. Now what?
I had to use a different computer, but was finally able to install the 2.6.502.16 RUU. When all was said and done, Motion Launch gestures still not working.
On the same computer, I can't seem to get the 1.32.502.31 RUU to work; it shows Updating Boot, then Updating Signature, then error 155. Does HTC prevent downgrades?
chp said:
I had to use a different computer, but was finally able to install the 2.6.502.16 RUU. When all was said and done, Motion Launch gestures still not working.
On the same computer, I can't seem to get the 1.32.502.31 RUU to work; it shows Updating Boot, then Updating Signature, then error 155. Does HTC prevent downgrades?
Click to expand...
Click to collapse
you need s-off to downgrade, If your not s-off did you relock the bootloader?
clsA said:
you need s-off to downgrade, If your not s-off did you relock the bootloader?
Click to expand...
Click to collapse
My M9 is fully stock (S-ON, Bootloader never unlocked).
Related
I just flashed [ROM] (5/25) Nils' Business ICS 4.0.3 Sense 3.6 last night for my S-OFF ReZound. Everything went beautifully and the ROM looks great. The problem I think I have is whenever an app throws up a notification my phone reboots. I first noticed it whenever I sync'd my Google account and it threw up a notification about new gmail messages. So I stopped syncing Gmail. Then it happened whenever I tried to open Twitter/Facebook or when I adjusted the ringtone volume or my alarm went off.
Does anyone have an idea why these things would cause the phone to reboot? Are there any commonalities between these functions?
Weird. Not sure about that. The only rebooting I get on the ROM is when I use my Lock Screen App instead of using the power button. From what I understand though, that is a problem with ALL the ICS versions for Rezound. I can't wait until that is fixed...I hate trying to press that little power button through the small hole in the case I use.
Did you do a full wipe and then flash? Sounds like something residual from a previous ROM. If you did wipe and flash, did you restore anything in Titanium? It clearly states in the OP for that ROM not to do that.
yea i did a full wipe and flash twice. i havent installed or used Titanium to this point.
it first started happening when i attempted to sync my google account, which was about the 3rd thing i did after installing the ROM.
Someone for mad at me for telling them search the old firmware patch
Is suggest you do the same
If you can't find your sdcard or if your phone reboots when it makes a sound.... You need to flash the old firmware patch
Sent from my ADR6425LVW using Tapatalk 2
superchilpil said:
Someone for mad at me for telling them search the old firmware patch
Is suggest you do the same
If you can't find your sdcard or if your phone reboots when it makes a sound.... You need to flash the old firmware patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
if you're referring to the GB firmware patch, then I did do that during the ROM install process per the instructions. i can try doing that again though.
You are on gingerbread firmware correct?
I have read about the patch not working the first time so that could be the issue
Sent from my ADR6425LVW using Tapatalk 2
i did come from GB firmware, but flashed the RUU 3.14.605.5 and then flashed the GB firmware patch. after doing this and booting into the RUU, i then flashed Nil's ROM.
nalees said:
i did come from GB firmware, but flashed the RUU 3.14.605.5 and then flashed the GB firmware patch. after doing this and booting into the RUU, i then flashed Nil's ROM.
Click to expand...
Click to collapse
if you flashed the 3.14RUU, you shouldn't need the GB firmware patch since you are now on ICS.
I would reinstall the ROM and skip the patch.
oh ok! i will do that now.
*update 2*
rats, 5 minutes later, as i'm refreshing my twitter app, it reboots. going to see if it continues to replicate. so far it has. uninstalling and reinstalling it. /// still rebooting when i refresh twitter. weird.
nalees said:
oh ok! i will do that now.
*update 2*
rats, 5 minutes later, as i'm refreshing my twitter app, it reboots. going to see if it continues to replicate. so far it has. uninstalling and reinstalling it. /// still rebooting when i refresh twitter. weird.
Click to expand...
Click to collapse
When you went from gb and ran the ics ruu, did you run the ruu twice.? It only updates a few things the first time through. The second time it does all items on the list.
Sent from my Rezound
oh my, just read through Nil's instructions again and you're right, it does say to run it twice...
i only did the RUU once.
ok, so from here, I need to reflash the RUU one more time? and then reload Nil's ROM?
hmm, also noticed on step #10 i need to unlock the bootloader again? is this true even if i'm s-off?
I went from completely stock to S-OFF and running Nils' latest Business Sense 2 days ago. I have not had any of the problems you mentioned.
His instructions do no say to install the RUU twice. They say that it's a 2 pass affair to install it. If you went through the whole process to install it once, you don't need to do it again.
However, I agree with an earlier post. Installing a GB firmware patch after installing an ICS RUU is probably your problem. Re-doing the whole thing from Nils' instructions for "Latest Leak and Installation Instructions", and then just installing his v4.1 ROM is probably all you need to do to get straightened out.
You absolutely need to flash the RUU twice. The 2nd time it will appear to be stuck on one of the times and flash it like 10 times but that is normal.
nalees said:
hmm, also noticed on step #11 i need to unlock the bootloader again? is this true even if i'm s-off?
Click to expand...
Click to collapse
It says that in Step #10, I believe. And yes, you have to do that in order to install (or re-install, as the case may be) AR Recovery (Step #11).
---------- Post added at 02:10 PM ---------- Previous post was at 02:03 PM ----------
con247 said:
You absolutely need to flash the RUU twice. The 2nd time it will appear to be stuck on one of the times and flash it like 10 times but that is normal.
Click to expand...
Click to collapse
I started on Monday with a bone stock Rezound. I unlocked, rooted, and did the wire trick for S-OFF.
Then I flashed the 3.14 RUU once, unlocked again, installed AR Recovery again, and then flashed Nils' v4.1 ROM (for S-OFF).
My phone seems to be working fine. Exchange mail (I don't use Gmail), contacts, calendar and tasks. Visual Voice Mail. Notifications. Text messaging. Facebook. WiFi Tether. Google Maps. Camera. Bluetooth handsfree. Everything seems to work fine. The only thing I haven't tested yet, that I mean to, is to force it to 3G only for data and test that I can talk and surf the Web at the same time.
Since I did not flash the RUU twice, what should I be looking for to not work right?
Do not HTC unlock after s-off.
Edit: saw you did.... Basically you will have unlocked or re locked. If you wanted the bootloader to appear stock you have to s-on and do the s-off process again. Then it would say locked. Not a big deal.... Unless you are paranoid and have to do a warranty swap.
Sent from my Rezound
ericsignals said:
Do not HTC unlock after s-off.
Sent from my Rezound
Click to expand...
Click to collapse
yea, i was reading this thread and that's why i thought that...
http://forum.xda-developers.com/showthread.php?t=1620211&page=6
i'll do some more reading before i proceed.
Just tested the SVDO.
Went into Phone Info and set my phone to CDMA Auto (PRL).
Turned off WiFi.
Confirmed status bar displayed 3G.
Called up my bank and let the automated menu thing talk over speakerphone.
Ran Speedtest on phone and it worked.
Went into Phone browser, did a Google search and got results.
Turned on WiFi Tether on my phone.
Connected my TouchPad (running ICS) to phone hotspot.
Ran Speedtest on TP. Got 1934kbps down and 1945kbps up.
I'd say simultaneous voice and 3G data work just fine with Nils' ROM, too...
so i redid everything tonight the proper way and its up and running perfectly! loving it
nalees said:
so i redid everything tonight the proper way and its up and running perfectly! loving it
Click to expand...
Click to collapse
And that releives me. Have fun
I purchased an AT&T SGH-i717 and was told everything worked. When I checked it out, everything seemed fine too. After using it for a couple hours I realized it just seemed to reboot at random. I rebooted into recovery and did a factory reset and wiped the cache. After rebooting it...it would get stuck at the AT&T screen. I then installed the latest stock rom 4.4.2 using Odin and it booted up fine but I got the no sim card error. I put in an AT&T sim card and rebooted but got a sim not provisioned error. I then tried a T-Mobile card and I didn't get the error and it showed signal bars but when I tried to dial it said emergency calls only. I tried a Verizon sim card just to see what kind of error I would get but it was just the same as the T-Mobile sim. I thought it might a corrupted rom so I tried installing the latest nightly CyanogenMod using CWM but got error status 7. I then tried various custom and stock roms including AOKP, BeanStalk, and several different versions of CyanogenMod but always got the same error status 7 msg. I then came across a forum posts stating that CWM no longer works for the SGH-i717. I downloaded the latest TWRP touch recovery and was able install the latest stable CyanogenMod but it would not boot past the animated CyanogenMod logo even after sitting for over an hour. At that point I gave up and decided to just go back to the stock rom. I rebooted into TWRP and the slide to unlock would not work anymore. I had to install CWM using Odin which allowed me to flash back to the stock 4.4.2 rom. After doing another factory reset and wiping the cache then rebooting...the touch screen stopped working. I then flashed it back to the stock 4.0.4 rom but the touch screen still does not work. While trying to figure out what happened I realized the pen still works and touch screen buttons on the bottom but thats it. Also the pen only works on the screen and not on the touch screen buttons. I've been messing with this for 3 days and will probably just sell it for parts but wanted to post this problem so if anyone else had this problem they would know what I've already tried. I did also take apart the phone and clean the connections but that didn't help either.
If anyone has a suggestion for something I haven't tried...please let me know. My last attempt will be install the Padawan JB rom from this post:
http://forum.xda-developers.com/showthread.php?t=1907203
Thanks
Right out of tge gate, there is no stock 4.4.2 for this device. Not official anyway. 4.1.2 is official OS.
Status 7 means your recovery needs updating.
CWM does work and the newest CWM touch is just dandy.
I would try going all the way back. You need to be totally clean.
Factory
Cache
Davlik
Format
Go to Kies and go with emergency firmware recovery.
Get back to stock and see what is working.
Clean clean clean, the best way for anyone to help you. You would be at the best starting point.
Maybe do a little reading as many of your issues have been documented and solved. None of them are major.
Start from scratch and folks can get you running again.
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
captemo said:
Right out of tge gate, there is no stock 4.4.2 for this device. Not official anyway. 4.1.2 is official OS.
Status 7 means your recovery needs updating.
CWM does work and the newest CWM touch is just dandy.
I would try going all the way back. You need to be totally clean.
Factory
Cache
Davlik
Format
Go to Kies and go with emergency firmware recovery.
Get back to stock and see what is working.
Clean clean clean, the best way for anyone to help you. You would be at the best starting point.
Maybe do a little reading as many of your issues have been documented and solved. None of them are major.
Start from scratch and folks can get you running again.
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
Click to expand...
Click to collapse
Thanks for replying...I hadn't used Kies in awhile becuase it never seemed to work right. I downloaded the latest version and it looks like they made a lot of improvements. I did the factory restore and wiped the cache then installed the latest firmware thru Kies. Everything seemed to work fine but after rebooting the touch screen doesn't work at all, not even with the pen. The touch screen buttons seem to still work but its stuck at the AT&T Ready2go screen because I can't hit cancel or get started buttons.
Thanks
cycloneus said:
Thanks for replying...I hadn't used Kies in awhile becuase it never seemed to work right. I downloaded the latest version and it looks like they made a lot of improvements. I did the factory restore and wiped the cache then installed the latest firmware thru Kies. Everything seemed to work fine but after rebooting the touch screen doesn't work at all, not even with the pen. The touch screen buttons seem to still work but its stuck at the AT&T Ready2go screen because I can't hit cancel or get started buttons.
Thanks
Click to expand...
Click to collapse
well my friend, you had the phone apart once already, I am no expert, but my guess is this is no software issue. maybe some connections came loose. in my time here, I have not come across this issue. I do not have the brain pan nor the courage to take my phone apart.
good luck to you.
maybe someone else will mosey on by.
cycloneus said:
Thanks for replying...I hadn't used Kies in awhile becuase it never seemed to work right. I downloaded the latest version and it looks like they made a lot of improvements. I did the factory restore and wiped the cache then installed the latest firmware thru Kies. Everything seemed to work fine but after rebooting the touch screen doesn't work at all, not even with the pen. The touch screen buttons seem to still work but its stuck at the AT&T Ready2go screen because I can't hit cancel or get started buttons.
Thanks
Click to expand...
Click to collapse
My guess is the digitizer has gone bad if odin &/or kies can't fix the issue at hand.
Just got s-off on my DNA but installing a custom Rom makes the phone randomly freeze and reboot. Tried CM11, carbon, and a few others. The time before restarting varies wildly from 10 seconds after boot to 20-30 minutes. It seems more frequent when the screen is on or when plugged into my PC but I could just be imagining things or could be coincidence.
I have flashed and rommed many phones over the years and this one really has me stumped.
I cleared the cache and dalvik and formatted the system partition before installing the Rom and gapps. I have tried multiple roms and multiple versions of gapps as well with no luck. I have superCID of 11111111 from the original unlock process if that makes any difference. I have currently RUUd back to 3.06 for now and it seems perfectly stable on the stock Rom. Any help would be appreciated!
renegadeone8 said:
Just got s-off on my DNA but installing a custom Rom makes the phone randomly freeze and reboot. Tried CM11, carbon, and a few others. The time before restarting varies wildly from 10 seconds after boot to 20-30 minutes. It seems more frequent when the screen is on or when plugged into my PC but I could just be imagining things or could be coincidence.
I have flashed and rommed many phones over the years and this one really has me stumped.
I cleared the cache and dalvik and formatted the system partition before installing the Rom and gapps. I have tried multiple roms and multiple versions of gapps as well with no luck. I have superCID of 11111111 from the original unlock process if that makes any difference. I have currently RUUd back to 3.06 for now and it seems perfectly stable on the stock Rom. Any help would be appreciated!
Click to expand...
Click to collapse
check my thread in the same section, mine started doing this two nights ago. I don't know why it started, my phone was fine prior to this. I did nothing to it, had been running Venom for a while, and two nights ago it started rebooting randomly and wildly. I have switched ROMs twice since then and it has not stopped. Like you said, it tends to be when the screen is on or gets plugged up. But unfortunately mine is doing it a lot on answering phone calls. I don't know if we are having same issure or what.
Possibly
lemonoid said:
check my thread in the same section, mine started doing this two nights ago. I don't know why it started, my phone was fine prior to this. I did nothing to it, had been running Venom for a while, and two nights ago it started rebooting randomly and wildly. I have switched ROMs twice since then and it has not stopped. Like you said, it tends to be when the screen is on or gets plugged up. But unfortunately mine is doing it a lot on answering phone calls. I don't know if we are having same issure or what.
Click to expand...
Click to collapse
I don't know if we are having the same issue it may be that we are though. I am on stock 3.06 not one reboot since I went to work this morning. Get home, install the newest twrp (it is removed in the RUU process), install cm11 snapshot m5, and the appropriate gapps. I got through setup to the point of adding my gmail and it froze and rebooted. I tried cwm recovery too but it made zero difference
TBH my screen is shattered really bad and I was going to replace it but I don't want to if I have to run stock roms forever. I was running one of the original Venom roms before s-off was possible, but then I broke the screen and switched back to my droid bionic but now I can afford the new LCD so I want to get this one running
renegadeone8 said:
I don't know if we are having the same issue it may be that we are though. I am on stock 3.06 not one reboot since I went to work this morning. Get home, install the newest twrp (it is removed in the RUU process), install cm11 snapshot m5, and the appropriate gapps. I got through setup to the point of adding my gmail and it froze and rebooted. I tried cwm recovery too but it made zero difference
TBH my screen is shattered really bad and I was going to replace it but I don't want to if I have to run stock roms forever. I was running one of the original Venom roms before s-off was possible, but then I broke the screen and switched back to my droid bionic but now I can afford the new LCD so I want to get this one running
Click to expand...
Click to collapse
Did you use the proper recovery stated in the thread to flash the rom, have you installed any new apps recently? Does it happen when you run the phone in safemode? Have you tried Performing an RUU and the unlocking and installing a custom rom again?
Did all that
Jaggar345 said:
Did you use the proper recovery stated in the thread to flash the rom, have you installed any new apps recently? Does it happen when you run the phone in safemode? Have you tried Performing an RUU and the unlocking and installing a custom rom again?
Click to expand...
Click to collapse
I have done all of that stuff multiple times
I haven't installed any apps at all on it. This phone is basically brand new, I got it right when they launched. I shattered the screen like 3 days after I got it, and tucked it in a drawer. It has been sitting there ever since.
I have another piece to add to the puzzle. While it has the stock ROM installed it seems to get service and work just fine, but when I install the custom ROMS it has absolutely zero cell connectivity (though WiFi works fine.)
Going into the settings reveals that on the custom roms it shows the IMEI and MEID as Unknown, and the ICCID is listed as Unknown as well. If I try to change the network mode (to LTE/CDMA or any one of the many available options) it says com.phone has crashed.
After the RUU process I have my proper MEID and ICCID showing in the settings panel, and service returns.
Can't flash radio?
After discovering the issues with the service while on custom ROMS I wondered if the radio had something wrong with it.
I tried to manually reflash the radio via fastboot (fastboot flash radio radio.img).
I tried this both in standard fastboot as well as in the rebootRUU mode, but both times I get an error that says remote not allowed. Could my bootloader somehow still be locked? The flag in bootloader mode says "Unlocked" but I unlocked manually after obtaining s-off rather than doing it officially via HTCdev. just trying to explore all options
My phone did that at one point. I had to re-lock and RUU back to 100% stock. I then unlocked my phone with Rumrunner S-Off tool. Flashed a Sense 6 ROM and has been working fine since.
Fixed!
So this problem is fixed!! I am not 100% sure what did the trick, so I will post my solution here in case anybody else experiences a similar issue. I won't go into too much detail with these instructions as all the tools are here: http://forum.xda-developers.com/showthread.php?t=2612740
I first downgraded to the 1.15 hboot and radio. I had to rebootRUU and flash them there as it can't be done directly in fastboot as far as I know.
Do them one at a time (flash the hboot, then reboot-bootloader, then rebootRUU then flash the radio, then reboot bootloader again.)
After doing this I tried to run the RUU exe but it came up with an error that it could not update my phone, so I did the manual Alt 3.06 RUU.
This seemed to work great, restarted the phone and saw the stock rom. I then changed from superCID 11111111 back to the stock CID, relocked my bootloader went back to s-on status. At this point I ran the RUU.exe again just to make sure everything was as stock as could be.
Got that all finished, ran RumRunner again, installed CM11 and no reboot for nearly 24 hours. Pretty sure all is well!
renegadeone8 said:
I don't know if we are having the same issue it may be that we are though. I am on stock 3.06 not one reboot since I went to work this morning. Get home, install the newest twrp (it is removed in the RUU process), install cm11 snapshot m5, and the appropriate gapps. I got through setup to the point of adding my gmail and it froze and rebooted. I tried cwm recovery too but it made zero difference
TBH my screen is shattered really bad and I was going to replace it but I don't want to if I have to run stock roms forever. I was running one of the original Venom roms before s-off was possible, but then I broke the screen and switched back to my droid bionic but now I can afford the new LCD so I want to get this one running
Click to expand...
Click to collapse
thats kinda crazy... i was on bionic before my dna. my screen on DNA is shattered like crazy. thought about going back to bionic temporarily, instead i'm gonna replace my screen and RUU and see if it fixes my problem
lemonoid said:
thats kinda crazy... i was on bionic before my dna. my screen on DNA is shattered like crazy. thought about going back to bionic temporarily, instead i'm gonna replace my screen and RUU and see if it fixes my problem
Click to expand...
Click to collapse
Good news and bad news. The good news is for you!!! I think I figured out what the problem was. It seems to be an issue either with using an older radio, or an older hboot on a newer ROM. I don't know why exactly, but the RUU process was not properly updating my radios. This may be because I ran an RUU while unlocked at one point (every guide I see is very adamant about relocking before the RUU process.)
The bad news is that I ordered a new LCD for my DNA, and I ruined my phone trying to do the repairs. It is by FAR the worst phone I have ever had to work on. I have replaced LCD's in Galaxy devices, Iphones/ipod touches, laptops, TV's, and one in a smartwatch and have never hurt a thing. Got my DNA back together and it flat out wont turn on I don't know what the problem is, but something is fried. Hope you have better luck than me!
Hi,
I flashed kitkat 4.4.2 stock firmware today using Odin, After the mobile booted successfully the touch screen stopped working completely, also the option and back button stopped also, I tried reflashing multiple times the same thing.
I have replaced this screen and the digitizer 10 days ago after it crashed, it was working normally before upgrade.
What could be the problem.
Regards
Are you sure your using the right odin model?
Run in administration mode, and disable all virus pc programs.
Also, after flash reboot into stock recovery and data reset/ Wipe.
If that doesn't work the most likely you have a bad piece of hardware or something is unperfectivley seated. Try reconnecting the ribbon cables.
Reflash
Yes4g4me said:
Are you sure your using the right odin model?
Run in administration mode, and disable all virus pc programs.
Also, after flash reboot into stock recovery and data reset/ Wipe.
If that doesn't work the most likely you have a bad piece of hardware or something is unperfectivley seated. Try reconnecting the ribbon cables.
Click to expand...
Click to collapse
I did what you said, I tried reflashing with another jellybeans stock version but the same results, I took it to the mobile center where I changed the screen and he told me he can revert it to jellybeans.
I will tell you what he did when he finish.
samirkal said:
I did what you said, I tried reflashing with another jellybeans stock version but the same results, I took it to the mobile center where I changed the screen and he told me he can revert it to jellybeans.
I will tell you what he did when he finish.
Click to expand...
Click to collapse
It will be interesting to see how they could revert firmware from KK to JB... IMO this is impossible because of new bootloader in KK. Anyway let they make phone usable on ANY firmware.
Probably jigg it right?
Yes4g4me said:
Probably jigg it right?
Click to expand...
Click to collapse
It is unclear for now but there may be involved e-fuses technology - that means physically burning connections inside chip during firmware upgrade, so in that case it impossible to bring back previous state.
The main problem is why replaced screen doesn't work after flashing KK. I do not know what version of Mega do you have, but i red on this forum so some versions required exclusively Samsung original parts. People who changed screens by themself obtained i.e. from ebay had problems after upgrading to KK. Lets prove the source of parts in service where was replaced your screen.
EDIT// You can read about it here
http://forum.xda-developers.com/showthread.php?p=55189673
successfully downgraded
Successfully downgraded to jellybeans but didn't tell me how. He performed rooting and flashing which led to baseband loss, but then he returned the baseband, great.
Congratulations. Can you post sreenshot of the Informations about unit?
samirkal said:
Successfully downgraded to jellybeans but didn't tell me how. He performed rooting and flashing which led to baseband loss, but then he returned the baseband, great.
Click to expand...
Click to collapse
Which version do you own? i527?
Would love to know howbyou downgraded back to jb
Sent from my LG-LS980 using XDA Free mobile app
argggg
samirkal said:
Successfully downgraded to jellybeans but didn't tell me how. He performed rooting and flashing which led to baseband loss, but then he returned the baseband, great.
Click to expand...
Click to collapse
hi
my touch after ota does not vvork....
hovv you repair your baseband?
my basebandd is novv unknovvn !!
i9200
samirkal said:
Hi,
I flashed kitkat 4.4.2 stock firmware today using Odin, After the mobile booted successfully the touch screen stopped working completely, also the option and back button stopped also, I tried reflashing multiple times the same thing.
I have replaced this screen and the digitizer 10 days ago after it crashed, it was working normally before upgrade.
What could be the problem.
Regards
Click to expand...
Click to collapse
I have a samsung mobile, Galaxy Mega 6.3 (GT-I9200).
I updated my 4.2.2 android to 4.4.2 by OTA, last month in my Settings and About menu and Check for Update...
This update completed successfully, but after update my touch screen does not work at all, and I don't know what shall I do right now... my phone is completly unusable...
Solved.. Use this
http://forum.xda-developers.com/showthread.php?t=2922542
Useful information
Good deal glad you got your phone working again
The gestures randomly stop working after the marshmallow update. So, I clean flashed 3.1.3 with stock recovery after deleting cache and data. Gestures randomly stop after sometime but works again if you reboot. Any way out?
Now, I am rooted with twrp recovery.
No such issues here. I'm no expert but I had issues with notification. So I wiped everything including internet with twrp. Be warned wiping internal is never suggested. But I had a lot of junk left over from ROMs and such. Then I flashed 2.2.2, 2.2.3 and last 3.1.3 finally reboot. Everything is working 100℅ now feels like brand new phone. Again I'm no expert and always back up your important files on your computer and or thumb drive before attempting because you will loose everything.
I think that explains it.
Exodusche said:
No such issues here. I'm no expert but I had issues with notification. So I wiped everything including internet with twrp. Be warned wiping internal is never suggested. But I had a lot of junk left over from ROMs and such. Then I flashed 2.2.2, 2.2.3 and last 3.1.3 finally reboot. Everything is working 100℅ now feels like brand new phone. Again I'm no expert and always back up your important files on your computer and or thumb drive before attempting because you will loose everything.
Click to expand...
Click to collapse
Thanks I will do my research!
pavikum said:
Thanks I will do my research!
Click to expand...
Click to collapse
No problem also meant to say gestures never worked better. . Almost to good every time I clean my screen flashlight or music starts playing lol.
I also have random gestures not working on my fresh installed OOS 3.1.3.
It never occurred before under 2.1.3 – 2.2.0 – 2.2.1 and 2.2.2, always rooted.
To prevent from rebooting the phone, enabling the proximity wake up (in parameters, display) does the trick.
Once I activate the proximity wake up, the gestures work again.
After that, you can disable the proximity wake up, the gestures keep working. Until it fails again.
I don’t know why this occurs, but at least, it’s an easy work around.
vinz_uk80 said:
I also have random gestures not working on my fresh installed OOS 3.1.3.
It never occurred before under 2.1.3 – 2.2.0 – 2.2.1 and 2.2.2, always rooted.
To prevent from rebooting the phone, enabling the proximity wake up (in parameters, display) does the trick.
Once I activate the proximity wake up, the gestures work again.
After that, you can disable the proximity wake up, the gestures keep working. Until it fails again.
I don’t know why this occurs, but at least, it’s an easy work around.
Click to expand...
Click to collapse
Haha, at least I have some company now!. Thanks, that trick works!
maybe we followed the similar steps to arrive at this issue.
I was on Sultan CM rom 13 , when the 3.1.1 update arrived, I unrooted my phone locked the OEM and clean installed 3.1.1 through stock rcovery after clearing data and cache. My phone gesture problem started from here, I updated to 3.1.2 through OTA and that did not solve it, so I clean installed 3.1.2 and later 3.1.3. Rooted it with modified superSU and blu spark twrp recovery. Did you follow the same steps.
I am not wiping the internal storage yet, as suggested by 'Exodusche', as I am doing my research to understand the potential risks. But, I did not really find any helpful article till now.