[Q] Touch not working after upgrade to 4.4.2 - Samsung Galaxy Mega

I had installed 4.2.2 (after replacing the phone displays).
After the OTA update to to 4.4.2 does not work touch and context (bottom) button.
Is it possible to downgrade back to 4.2.2. or not - KNOX bootloader?

If your softkeys are not working properly go to your phone dialer and use this code *#0*# to run some test (touch,TSP hovering,sub keys) after this your softkeys should work but you will have to run these test every time you turn on your phone or after a reboot.

I got the same probleme.Any fix....
Please we need help

You can only control your phone through OTG mouse. ONLY the power, volume and home buttons working.
I tried to reflash and ten, the result is still the same.
In my opinion, is a bug in the ROM.
Temporarily I uploaded a CWM + this ROM - Dirty Unicorns - v7.8 : 20140702.
With this all works as it should, but I do not see this as a final solution.

ExEricss said:
You can only control your phone through OTG mouse. ONLY the power, volume and home buttons working.
I tried to reflash and ten, the result is still the same.
In my opinion, is a bug in the ROM.
Temporarily I uploaded a CWM + this ROM - Dirty Unicorns - v7.8 : 20140702.
ith this all works as it should, but I do not see this as a final solution.
Click to expand...
Click to collapse
Tanks i will try it

I've same problem guys,
I decide to downgrade to 4.2.2 or 4.2.1
hope to work. but if u find any solution please share...

I have learned that with the att mega if you have had a replacement screen 4.4.2 will not boot properly. If you replace the lcd with the oem at&t brand digitizer specific lyrics for the i527. It will work but it must be i527 lcd digitizer. I read this in a repair forum. If I can find it again I will post the link. As of right now I am currently booting up with original att lcd and swapping the lcd cable after the boot. Its the only way i can get the phone to not bootloop, and get touch on 4.4.2. It was running 4.2.2 fine. As soon as i did the update. It started. I sure hope someone knows of a way to get the replacement digitizers to work on the i527. Hope this info helps.
Sent from my SCH-R950 using XDA Free mobile app

Mine boots but the touch doesnt work after the kk update and cant go back to jb hopefully soon

[email protected] said:
I have learned that with the att mega if you have had a replacement screen 4.4.2 will not boot properly. If you replace the lcd with the oem at&t brand digitizer specific lyrics for the i527. It will work but it must be i527 lcd digitizer. I read this in a repair forum. If I can find it again I will post the link. As of right now I am currently booting up with original att lcd and swapping the lcd cable after the boot. Its the only way i can get the phone to not bootloop, and get touch on 4.4.2. It was running 4.2.2 fine. As soon as i did the update. It started. I sure hope someone knows of a way to get the replacement digitizers to work on the i527. Hope this info helps.
Sent from my SCH-R950 using XDA Free mobile app
Click to expand...
Click to collapse
This also apply to the r960 mega. Bought lcd digitizer specifically for it and works fine with 4.4.2
sent from my M E G A . . . >((((((●)(●)

drendoral said:
i've same problem guys,
i decide to downgrade to 4.2.2 or 4.2.1
hope to work. But if u find any solution please share...
Click to expand...
Click to collapse
how did you downgrade

vazersecurity said:
how did you downgrade
Click to expand...
Click to collapse
Go to live.samsung-updates.com/index.php?device=GT-N5100 to download the version u want, then flash ur tab with Odin

Will try this

vazersecurity said:
Will try this
Click to expand...
Click to collapse
It says GT-N5100 on the link which is Galaxy Note 8.0. May not be for our Mega. Proceed with caution.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]

Yeah. I noticed. I didn't even try. I couldn't find anything.

I loaded CWM and installed the zip from the sd card. They say you cant go back. But I did. But mine was rooted before. Dont if that makes the difference or not. I hadn't tryed the dirty unicorn mod yet buti will wheni get time.
Sent from my SPH-L600 using XDA Free mobile app

drendoral said:
Go to live.samsung-updates.com/index.php?device=GT-N5100 to download the version u want, then flash ur tab with Odin
Click to expand...
Click to collapse
You loaded a galaxy note 8.0 firmware on the galaxy mega?
Sent from my SM-N900V using XDA Free mobile app

http://forum.xda-developers.com/galaxy-mega/help/galaxy-mega-screen-stopped-upgrade-to-t2863891 <-- Try this

Replaced touch screen does not work in 4.4.2
ericss said:
I had installed 4.2.2 (after replacing the phone displays).
After the OTA update to to 4.4.2 does not work touch and context (bottom) button.
Is it possible to downgrade back to 4.2.2. or not - KNOX bootloader?
Click to expand...
Click to collapse
I have same problem too....
Downgrade is horrible! but it can by box... after downgrade to 4.2.2 my baseband had gone left and several days tried to restore my IMEI and WIFI... and later install a new unofficial ROM, like slimkat and cyanogenmod. and I don't know how to downgrade to 4.2.2 by WIFI Fixed or my touch screen work correctly in 4.4.2 kitkat...

Related

[Q] [SOLVED] Touch screen not working for stock 1.4.2 report image?

Not sure if anyone else has this problem, but when I restored my nook to stock using the 1.4.2 report image the touch screen didn't work. Does anyone else have this problem and know how to fix it?
Sent from Nook Tablet 8GB with CM10.1 iamafanof's build
Re: [Q] Touch screen not working for stock 1.4.2 report image?
You had 10 touch firmware installed on cm10? You should revert to 2 touch before returning to stock.
Sent from my ST27i
And the solution is to go back to CM10 and reflash original touch firmware, and then go back to stock.
satan89 said:
You had 10 touch firmware installed on cm10? You should revert to 2 touch before returning to stock.
Sent from my ST27i
Click to expand...
Click to collapse
What's the best way to do this without being able to touch the screen?
Do any of the Nook kernels support USB to OTG? If so I can try a USB mouse to manipulate the screen
Re: [Q] Touch screen not working for stock 1.4.2 report image?
No need for touch when using CWM. Install CM10 from CWM and you're back in business.
Sent from my GT-P7300 using Tapatalk 2
asawi said:
No need for touch when using CWM. Install CM10 from CWM and you're back in business.
Sent from my GT-P7300 using Tapatalk 2
Click to expand...
Click to collapse
Did that, touch screen stil doesn't work. Im pretty sure it's bad hardware. I have another thread open with the details of what i've tried. Feel free to take a peek.
Re: [Q] Touch screen not working for stock 1.4.2 report image?
Okay thank you the stock works now.
Sent from Nook Tablet 8GB with CM10.1 iamafanof's build.
asawi said:
And the solution is to go back to CM10 and reflash original touch firmware, and then go back to stock.
Click to expand...
Click to collapse
After weeks of fiddling ( I have no clue How I got here!) I think I got CM10 installed now How and where might I find the original Touch firmware to get my Stock touch to work?I have been working on this for almost 6 months! I know I should be on the short Yellow bus But SO help would be greatly appreciated. Thanks... OH I forgot to say please!
Re: [Q] Touch screen not working for stock 1.4.2 report image?
Most Cm10 builds come with the app installed.
Look. For app 'touchscreen firmware flasher '
Sent from my ST27i
satan89 said:
Most Cm10 builds come with the app installed.
Look. For app 'touchscreen firmware flasher '
Sent from my ST27i
Click to expand...
Click to collapse
I hate to sound slow but I guess I cant help it... So I tap that touch app and initiate it, is there anything that I need to know about how the touch firmware flasher works? IS it a toggle? Are there check boxes I have to tick? Sorry, But I kind of want to know what to expect... I have been going crazy to get to this point! Thanks again!
There are boxes to click to start the process. So it's not started automatically when you click the app, if that's what you're worried about.
asawi said:
There are boxes to click to start the process. So it's not started automatically when you click the app, if that's what you're worried about.
Click to expand...
Click to collapse
Well I am worried about clicking the wrong boxes and such... Is it self explanatory, is it intuitive? I lost the touch capability on the stock Nook and have been trying to get it back for about 6 months, forgive me if I am a little "gun shy". I just want to get it right and be done with it! Thanks!
:fingers-crossed:
Re: [Q] [Solved] Touch screen not working for stock 1.4.2 report image?
Depending on what build you have the firmware flasher might look a little different. All in all they all do the same. On the build I have there is only one button to push which will either flash stock (2 touch) or 10 touch.
For the touch screen to work on a stock Barns and Noble Tablet you need to flash it to stock (2 touch). If you already wiped to factory reset you'll have to re install CM 10. Then use the firmware flasher to return to stock. (There may be a simpler way but that is what came to my mind first.)
If you have any further problems send me a message or email me at [email protected]
Sent from Nook Tablet 8GB with CM10.1 iamafanof's build.

touchscreen not working after update?

Ok bought a telus mega SGH-I527M with a broken screen,bought a screen on ebay (seller swears it is origional)but I think he is lieing as it has a black back to it instead of my beige origional screen and doesnt even have the numbers sticker on it,but anyhow worked great for an evening and I unlocked useing a code for rogers,it downloaded an update on its own and asked me if I wanted to install,so I did the update and when it rebooted the screen wouldnt unlock with a swipe any more so I factory restored it now can not press next at the start,can I go back to old firmware?stock rom for rogers instead of telus?and how?or any other ideas?thanks.
[email protected] said:
Ok bought a telus mega SGH-I527M with a broken screen,bought a screen on ebay (seller swears it is origional)but I think he is lieing as it has a black back to it instead of my beige origional screen and doesnt even have the numbers sticker on it,but anyhow worked great for an evening and I unlocked useing a code for rogers,it downloaded an update on its own and asked me if I wanted to install,so I did the update and when it rebooted the screen wouldnt unlock with a swipe any more so I factory restored it now can not press next at the start,can I go back to old firmware?stock rom for rogers instead of telus?and how?or any other ideas?thanks.
Click to expand...
Click to collapse
Why buy a **** touchscreen ? -.-
??Thank Me Up If I Helped You ??
also dont know if the previous owner had rooted,he said it was only 3mnths old
If you updated to the official kk which would be NE5 and this would be the most likely cause of the touchscreen not responding as phones with still the original screens has not responded after the NE5 update on other i527m mega..so your screen is not at fault.
Samsung should have tested the new kk update better before releasing the update.
Sent from my SGH-I527M using XDA Free mobile app
[email protected] said:
Ok bought a telus mega SGH-I527M with a broken screen,bought a screen on ebay (seller swears it is origional)but I think he is lieing as it has a black back to it instead of my beige origional screen and doesnt even have the numbers sticker on it,but anyhow worked great for an evening and I unlocked useing a code for rogers,it downloaded an update on its own and asked me if I wanted to install,so I did the update and when it rebooted the screen wouldnt unlock with a swipe any more so I factory restored it now can not press next at the start,can I go back to old firmware?stock rom for rogers instead of telus?and how?or any other ideas?thanks.
Click to expand...
Click to collapse
Try flashing this rom from my post here and see if it will help you out and you must unpack it first and then flash with odin..and i believe this rom was made with the rogers rom, but if you did receive the new KK NE5 update then this will not likely work, but it will not harm the phone..worth a try as i use this rom in certain situations also to get back and it works great.
starmaster10 said:
Try flashing this rom from my post here and see if it will help you out and you must unpack it first and then flash with odin..and i believe this rom was made with the rogers rom, but if you did receive the new KK NE5 update then this will not likely work, but it will not harm the phone..worth a try as i use this rom in certain situations also to get back and it works great.
Click to expand...
Click to collapse
couldnt go to your link,browser said forbidden?
can I root this?or custom rom?any way to be useable again?thanks(also I am new to all of this so a guide would be good)
found this?
If the downgrade was from the leaked 4.4.2,then this is probably because this repackaged and leaked firmware did not have a locked bootloader.
The officially released India 4.4.2 may cause more problems with downgrading - but we will have to wait and see if it contains a locked bootloader.
I didn't downgrade from leaked 4.4.2... My downgrade from official 4.4.2 DBT was also successfully in spite of new BL. I mean, didn't change BL with downgrade, just the firmware via Odin. And luckily the new BL from 4.4.2 works fine with firmware 4.1.2... that's what I wanted to inform about, because many think that it will not work, but it does! (At least in 3 oder 4 cases with german firmware.)
There is always a risk, yes, but maybe, somebody doesn't like 4.4.2 just as me and needs an idea to go back without root, so that's the answer I want to give.
[email protected] said:
couldnt go to your link,browser said forbidden?
can I root this?or custom rom?any way to be useable again?thanks(also I am new to all of this so a guide would be good)
Click to expand...
Click to collapse
Ooops..sorry about the link as somehow it was set to private, i have now corrected it and will put link here also
ROOT_JDQ39.I527MVLUBNA3.tar
And check my post here as it will help you in the flashing using odin and all .tar files are flashed this way, the only difference when flashing a recovery is you uncheck the reboot box and with other .tar files for roms etc. you check that reboot box, but everytime odin is restarted the reboot box will be checked already..let me know how this all goes with that rom above that i put a link to and the other stuff as all the custom roms in this mega section by @Silesh.Nair can be flashed and these are all the custom roms i tested so far that work on the i527m mega, but they all work even the newer ones and the custom roms i tried can be seen in this thread
starmaster10 said:
Ooops..sorry about the link as somehow it was set to private, i have now corrected it and will put link here also
ROOT_JDQ39.I527MVLUBNA3.tar
And check my post here as it will help you in the flashing using odin and all .tar files are flashed this way, the only difference when flashing a recovery is you uncheck the reboot box and with other .tar files for roms etc. you check that reboot box, but everytime odin is restarted the reboot box will be checked already..let me know how this all goes with that rom above that i put a link to and the other stuff as all the custom roms in this mega section by @Silesh.Nair can be flashed and these are all the custom roms i tested so far that work on the i527m mega, but they all work even the newer ones and the custom roms i tried can be seen in this thread
Click to expand...
Click to collapse
thank you verry much for the help,will try that and the link is good!!!!!
now seem to be stuck at the samsung flashing screen with no start?
[email protected] said:
now seem to be stuck at the samsung flashing screen with no start?
Click to expand...
Click to collapse
ok did a restore and on 2.2 now,thw screen is working again but have no sound no wi-fi and no rogers network?
?
[email protected] said:
ok did a restore and on 2.2 now,thw screen is working again but have no sound no wi-fi and no rogers network?
?
Click to expand...
Click to collapse
also no bluetooth,ran the supersu on phone and it said that it disabled knox?so rooted I think,wouldnt mind a custom rom that is stable but with all the crap samsung puts in removed,also it was koodo and still has koodo apps would like a rogers 16gb version and thanks for your help earlier.
i have this same problem with my i9200 idk what to do
[email protected] said:
also no bluetooth,ran the supersu on phone and it said that it disabled knox?so rooted I think,wouldnt mind a custom rom that is stable but with all the crap samsung puts in removed,also it was koodo and still has koodo apps would like a rogers 16gb version and thanks for your help earlier.
Click to expand...
Click to collapse
I cant get into the mode where I can use the sdcard anymore,says could not do normal boot?still works with odin but dont know what to try next?thanks.
ok,can boot from sd now useing phils recovery and flashed CM11 but still have no wi-fi or sound or bluetooth?Knox?

Ive been asking for help for about 4 days now, please someone help

Hello xda people,
i have the galaxy mega gt-i9200 with 4.2.2 software (no knox included)
ive tried every 4.4.2 kitkat update firmware from sammobile and everytime i end up with the same result.
Problem is when i flash the firmware , it boots up and my touchscreen and softkeys are disbaled/dont work.
i have no clue what the problem is, custom roms seem to work, and 4.2.2 official stock works.
can someone help me out? please.
Ntech02 said:
Hello xda people,
i have the galaxy mega gt-i9200 with 4.2.2 software (no knox included)
ive tried every 4.4.2 kitkat update firmware from sammobile and everytime i end up with the same result.
Problem is when i flash the firmware , it boots up and my touchscreen and softkeys are disbaled/dont work.
i have no clue what the problem is, custom roms seem to work, and 4.2.2 official stock works.
can someone help me out? please.
Click to expand...
Click to collapse
Maybe nobody has had this same issue. JIMMBOB offered a suggestion in one of your other threads.
You have 3 different threads.....are they 3 different problems. I only ask cause they are worded differently.
When you flash, are you flashing clean?
I am trying to offer some assistance. It sounds as if your having same problem across the board. Just have to start with basic responses so dont get upset. Try to walk through your process of flashing. Maybe you missed something. We all can.
Folks are reading, again maybe others just havent come across this issue.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Ntech02 said:
Hello xda people,
i have the galaxy mega gt-i9200 with 4.2.2 software (no knox included)
ive tried every 4.4.2 kitkat update firmware from sammobile and everytime i end up with the same result.
Problem is when i flash the firmware , it boots up and my touchscreen and softkeys are disbaled/dont work.
i have no clue what the problem is, custom roms seem to work, and 4.2.2 official stock works.
can someone help me out? please.
Click to expand...
Click to collapse
Ntech02 said:
I flashed this stock rom here http://forum.xda-developers.com/showthread.php?p=53767196 for my GT-i9200 Mega
coming from silentnight's flashable stock rom & another time from C-ROM 4.4.3,
each time i flash the stock rom (http://forum.xda-developers.com/showthread.php?p=53767196) it completes, reboots just fine, and when it starts up my screen doesnt respond anymore ive tried factory resets and full wipes & reflashed multiple times, idk what to do to make it work.
i can still go back to custom roms and my screen works fine on those. ive even tried going to 4.2.2 official stock but that doesnt work either.
someone please help =(
Click to expand...
Click to collapse
Ntech02 said:
Hello xda,
ive been having an issue for sometime but idk what it is,
when i boot my phone i cant see the logo that says "GALAXY MEGA i9200" it just stays black until the samsung boot animation appears.
in addition i cant see the DOWNLOAD mode screen either, although i can still enter download mode by using the button combination or just hitting reboot to DOWNLOAD mode.
does anybody know how to fix this?
Click to expand...
Click to collapse
Ntech02 said:
i have asked multiple times and im getting no response which is why i took my question here. if u werent gonna help me figure out something u didnt have to reply. and i can say its a stock rom because thats what it is. Stock Russian 4.4.2 kitkat Update for the GT-I9200. the only thing is this developer removed knox & the recovery. ive tried both versions of the rom and ended in the same result.
Click to expand...
Click to collapse
@Ntech02
Are you sure you are flashing the correct Official Firmware? I show many but you stated Russian above so I show two for your phone on KitKat. Also, if you were not made aware or didn't read up on the forums, once you upgrade to the "NE4 Bootloader" (Or KITKAT) and above you can not revert back to the previous ( JellyBean ) "Bootloaders". If you manage to flash back to them you will more than likely brick your phone.
Flashing a Custom Rom via Custom Recovery being from NF2, NE4, NA2, and MJ2 Roms for your Mega is still okay. Just remember not to Flash/Odin the Official Firmware from prior NE4 as the Firmwares include the Bootloader in them that one can not downgrade to.
All except for one of these Official Firmware is Flashable via Kies as well:
GT-I9200 Ukraine (Kyivstar)......2014 June ........4.4.2 ........I9200XXUDNF1 ........I9200OXEDNF1
GT-I9200 Kazakhstan...............2014 June ........4.4.2 ........I9200XXUDNF1 ........I9200OXEDNF1
GT-I9200 Uzbekistan ...............2014 June ........4.4.2 ........I9200XXUDNF1 ........I9200OXEDNF1
GT-I9200 Russia .....................2014 June ........4.4.2 ........I9200XXUDNF1 ........I9200SERDNF2
GT-I9200 Brazil .......................2014 June ........4.4.2 ........I9200UBUDNE2 ........I9200ZTODNE2
GT-I9200 Russia .....................2014 May .........4.4.2 ........I9200XXUDNE4 ........I9200SERDNE4
I know it has been mentioned / suggested before in other sections of the forum but updating your profile to reflect at least the Country and a Carrier for your phone would be helpful to provide some assistance.
captemo said:
Maybe nobody has had this same issue. JIMMBOB offered a suggestion in one of your other threads.
You have 3 different threads.....are they 3 different problems. I only ask cause they are worded differently.
When you flash, are you flashing clean?
I am trying to offer some assistance. It sounds as if your having same problem across the board. Just have to start with basic responses so dont get upset. Try to walk through your process of flashing. Maybe you missed something. We all can.
Folks are reading, again maybe others just havent come across this issue.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
Yes i understand i have 3 threads but someone could've at least attempted to help me out like you & dark angle is doing now, so i thank you guys for taking the time to reply.
its the same issue regarding the screen, im not gonna get upset with u lol
but ive followed all the instructions correctly, and yes ive flashed clean.
im on philz cwm recovery as it is.
i would erase my data b4 installing the kitkat stock update.
used odin3 3.09 & 3.04
the firmware flashes fine.
it boots up like its supposed to, but the screen is just unresponsive .
ive done factory resets from stock recovery
ive even left it on over night to see if maybe something didnt load. but nothing works maybe its a driver issue?
DarkAngel said:
@Ntech02
Are you sure you are flashing the correct Official Firmware? I show many but you stated Russian above so I show two for your phone on KitKat. Also, if you were not made aware or didn't read up on the forums, once you upgrade to the "NE4 Bootloader" (Or KITKAT) and above you can not revert back to the previous ( JellyBean ) "Bootloaders". If you manage to flash back to them you will more than likely brick your phone.
Flashing a Custom Rom via Custom Recovery being from NF2, NE4, NA2, and MJ2 Roms for your Mega is still okay. Just remember not to Flash/Odin the Official Firmware from prior NE4 as the Firmwares include the Bootloader in them that one can not downgrade to.
All except for one of these Official Firmware is Flashable via Kies as well:
GT-I9200 Ukraine (Kyivstar)......2014 June ........4.4.2 ........I9200XXUDNF1 ........I9200OXEDNF1
GT-I9200 Kazakhstan...............2014 June ........4.4.2 ........I9200XXUDNF1 ........I9200OXEDNF1
GT-I9200 Uzbekistan ...............2014 June ........4.4.2 ........I9200XXUDNF1 ........I9200OXEDNF1
GT-I9200 Russia .....................2014 June ........4.4.2 ........I9200XXUDNF1 ........I9200SERDNF2
GT-I9200 Brazil .......................2014 June ........4.4.2 ........I9200UBUDNE2 ........I9200ZTODNE2
GT-I9200 Russia .....................2014 May .........4.4.2 ........I9200XXUDNE4 ........I9200SERDNE4
I know it has been mentioned / suggested before in other sections of the forum but updating your profile to reflect at least the Country and a Carrier for your phone would be helpful to provide some assistance.
Click to expand...
Click to collapse
hey darkangel thank you both for trying to help me out,
my i9200 is unlocked and on tmobile, i am in the USA but my firmware is the Russian 4.2.2
i actually am on the NE4 (kitkat) bootloader but im still running Russian 4.2.2 jellybean,
i did a nandroid backup from Philz CWM recovery b4 i flashed the Russian official kitkat update
as stated above anything i tried just didnt work. the screen is unresponsive and so are the softkeys
so i just flashed philz recovery again and restored my jellybean stock which is how im still running on JB.
ive had no issues as far as bricking my phone im pretty savy when it comes to android i think im having a bad day lol
Ntech02 said:
hey darkangel thank you both for trying to help me out,
my i9200 is unlocked and on tmobile, i am in the USA but my firmware is the Russian 4.2.2
i actually am on the NE4 (kitkat) bootloader but im still running Russian 4.2.2 jellybean,
i did a nandroid backup from Philz CWM recovery b4 i flashed the Russian official kitkat update
as stated above anything i tried just didnt work. the screen is unresponsive and so are the softkeys
so i just flashed philz recovery again and restored my jellybean stock which is how im still running on JB.
ive had no issues as far as bricking my phone im pretty savy when it comes to android i think im having a bad day lol
Click to expand...
Click to collapse
This is more than likely going to sound like a stupid noob answer.
Did you buy your phone new or used?
I noticed when I was looking at buying a Mega with a broken screen, if you use a cheap replacement screen, you need to plug in the factory screen and boot and then plug in the aftermarket screen. I wonder if maybe you got it used and it was repaired and the stock OS is seeing as not being an OEM screen? Maybe Custom ROMs don't check these things?
@Ntech02 try flashing this rom via recovery http://forum.xda-developers.com/showthread.php?t=2608110
Sent from my GT-I9200 using XDA Premium 4 mobile app
nitromuscle said:
This is more than likely going to sound like a stupid noob answer.
Did you buy your phone new or used?
I noticed when I was looking at buying a Mega with a broken screen, if you use a cheap replacement screen, you need to plug in the factory screen and boot and then plug in the aftermarket screen. I wonder if maybe you got it used and it was repaired and the stock OS is seeing as not being an OEM screen? Maybe Custom ROMs don't check these things?
Click to expand...
Click to collapse
I Bought it New from NewEgg.com but the screen did break b4, and i bought a replacement 70$ screen and fixed it myself, idk if thats cheap but thats how much they typically cost on amazon.com . all custom roms work, and the 4.2.2 jelly bean official software works fine.
you maybe right about the OEM screen
alexischino said:
@Ntech02 try flashing this rom via recovery http://forum.xda-developers.com/showthread.php?t=2608110
Sent from my GT-I9200 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
is this kitkat?
@Ntech02 No is jellybean 4.2.2 but if you are on kitkat you can flash this rom via recovery i'm using the russia 4.4.2 kk and i have flash the v10 and the v11 you can use them to go back to jellybean.
Sent from my GT-I9200 using XDA Premium 4 mobile app
alexischino said:
@Ntech02 No is jellybean 4.2.2 but if you are on kitkat you can flash this rom via recovery i'm using the russia 4.4.2 kk and i have flash the v10 and the v11 you can use them to go back to jellybean.
Sent from my GT-I9200 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ohhh no no no lol ive been saying all along that im already on JB 4.2.2 official stock.
im still on the kitkat boot loader though.
You should be fine running JB on kitkat bootloader as long as you do not try and Odin a firmware with the JB bootloader and try to go back to the 4.2.2 bootloader. It will not let you go back to it. Flashing ROM's for your phone is all good as long as you do not touch the bootloader.
But if you really want to have KitKat then you need to try and reflash one of the KitKat official Firmwares I had mentioned above for your phone. You can only flash Firmwares via Odin from KitKat and above now because of the KitKat Bootloader.

Need i527m testers for 4.4.2 TW ROM base

Hey guys so basically the thread title says it all. I need a few testers who have the Canadian variant sgh-i527m who can test a rom base for me. What I need is confirmation that everything works on the base ie Bluetooth, data, WiFi, NFC,etc. Once deemed a stable base I can work on making the magic happen of adding cool features.
Of course the standard risks apply: you are responsible for anything you flash or that happens as a result. As always please make a nandroid backup before flashing and ensure you are using the latest, stable recovery
At this point the ROM is rooted, deodexed, zipaligned all apks and Knox free
Here is the link
https://mega.co.nz/#!KRRQXKBb!183bVTwJsmg_Wd-VfjHO-YYhKa4tlea7R4Cf6R3sN7g
Please share your results
Thanks
Sent from my GT-I9205 using Tapatalk
markbencze said:
Hey guys so basically the thread title says it all. I need a few testers who have the Canadian variant sgh-i527m who can test a rom base for me. What I need is confirmation that everything works on the base ie Bluetooth, data, WiFi, NFC,etc. Once deemed a stable base I can work on making the magic happen of adding cool features.
Of course the standard risks apply: you are responsible for anything you flash or that happens as a result. As always please make a nandroid backup before flashing and ensure you are using the latest, stable recovery
At this point the ROM is rooted, deodexed, zipaligned all apks and Knox free
Here is the link
https://mega.co.nz/#!KRRQXKBb!183bVTwJsmg_Wd-VfjHO-YYhKa4tlea7R4Cf6R3sN7g
Please share your results
Thanks
Sent from my GT-I9205 using Tapatalk
Click to expand...
Click to collapse
Hello,
I'm testing it on a i9205....
I installed it over a 4.2.2 bootloader as I never installed KK. So it looks like KK is installing over 4.2.2 Mega fire bootloader
.
I'm finishing up to setup all my account and let you know. So far its working well, the first run Wizard even detect my country "France", it did not before in 4.2.
I ll keep you posted but so far looking good.
Thanks
see screenshot attached
Just a small adjustement, on the i9205 the wifi is not turning on... I dont know why, a driver issue maybe. I will try replace wifi firmware and modules if I can.
Also when I go to ->Setting->security it says setting has stopped. then the phone is rebooting
pierrottls31 said:
Just a small adjustement, on the i9205 the wifi is not turning on... I dont know why, a driver issue maybe. I will try replace wifi firmware and modules if I can.
Also when I go to ->Setting->security it says setting has stopped. then the phone is rebooting
Click to expand...
Click to collapse
OK thanks for the feedback. If you're still on the ROM can you run a lotcat and try wifi and also go back to settings security. And then send me the logcat. If you send me it with those issues recreated I should be able to see what the problem is
Sent from my Nexus 5 using Tapatalk
markbencze said:
OK thanks for the feedback. If you're still on the ROM can you run a lotcat and try wifi and also go back to settings security. And then send me the logcat. If you send me it with those issues recreated I should be able to see what the problem is
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Sorry I cant, I had to go back to Mega Fire rom as I had no Wifi and cannot install Titanium to restore everything (As I cannot access security options) I had to revert to 4.2.2.
I also tried to modified your zip with a i9205 boot.img and all the System files into your zip from another 4.4.2 i9205, and I had the same issue. I'm starting to wonder if I dont have a radio issue compatibilty or my bootloader 4.2 is messing with some feature (like android finding knox is not on the bootloader). If you have any idea, I dont mind trying again but so far I would like to preserve my bootloader as my phone still under warranty.
pierrottls31 said:
Sorry I cant, I had to go back to Mega Fire rom as I had no Wifi and cannot install Titanium to restore everything (As I cannot access security options) I had to revert to 4.2.2.
I also tried to modified your zip with a i9205 boot.img and all the System files into your zip from another 4.4.2 i9205, and I had the same issue. I'm starting to wonder if I dont have a radio issue compatibilty or my bootloader 4.2 is messing with some feature (like android finding knox is not on the bootloader). If you have any idea, I dont mind trying again but so far I would like to preserve my bootloader as my phone still under warranty.
Click to expand...
Click to collapse
At this point my best guess is boot loader but who knows. Hopefully I can get more user feedback and i257m feedback most importantly. Thanks for your time
Sent from my Nexus 5 using Tapatalk
FYI, someone else tried it :
Originally Posted by pierrottls31 View Post
Hi, when you did test the rom from your link did you had same issues as I did? Wifi did not turn on, and when you go to Parameters-> Security i got a message saying security had to close. 5 secondes later the phone is rebooting.
I ve tried another rom 4.4.2 as a zip file and same issues. I revert it back to MF V11X and it works as normal.
I'm wondering if those issues are related to the bootloader (like for Param-Security) phone is looking for knox info and cannot find them.
reply:
Anyway for now my bootloader still in 4.2
I never checked wifi (I barely use wifi as is) System settings kept force closing on me and the ROM overall was a bit laggy (compared to MegaFire - probably not a fair comparison though - lol). My phone did keep rebooting every time I went into certain system settings to make changes (I don't remember which ones at this point). To be honest, I was just trying to see if I could flash it onto my phone. I had no intent to fully test the ROM for stability. Mega's ROMs are rock steady stable so I was just trying that 4.4.2 ROM while waiting for Mega to finish and post MegaKat.
see post from here:
http://forum.xda-developers.com/showthread.php?p=54072684 post #1994
Hi,
I just test the megakat rom from megafire, with the newbootloader and its all working. I can confirm wifi and setting issue were due to the bootloader
You should take a look at megakat op and rom, u will work with a almost bug free rom
Sent from my GT-I9205 using XDA Free mobile app
pierrottls31 said:
Hi,
I just test the megakat rom from megafire, with the newbootloader and its all working. I can confirm wifi and setting issue were due to the bootloader
You should take a look at megakat op and rom, u will work with a almost bug free rom
Sent from my GT-I9205 using XDA Free mobile app
Click to expand...
Click to collapse
you're missing the point of this thread! I'm not interested in another rom!!! I'm looking for sgh-i527m testers!!! i appreciate your efforts though
Okay i will give it whirl and see how the rom runs as i have the i527m mega (Canadian version).
Mega i527 bootloader is locked...no custom roms can go on it
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
scoobthegambler said:
Mega i527 bootloader is locked...no custom roms can go on it
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
Read the op andthread title. I'm not looking for i527 testers:banghead::banghead::banghead:
Sent from my Nexus 5 using XDA Free mobile app
markbencze said:
Read the op andthread title. I'm not looking for i527 testers:banghead::banghead::banghead:
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
i527 boot loader is locked. Just because you put an M at the end doesn't automatically make it unlocked....pssh noobs. ?
edit>>> @scoobthegambler, you are right, I made a mistake, my apologies
@pierrottls31 it's very poor etiquette to post another devs rom in someone else's rom thread. Please help to keep development threads eleventh to the threads they pertain to
Thanks in advance
@GT247 I never posted or mention another developer's rom I merely stated that the i527 had a locked bootloader and the op restated that he was talking about i527m
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
just tried the rom, works fine except i got no wifi, my baseband is still NA3. Any way to get it updated to NE4 or NE5 ?
apen83 said:
i527 boot loader is locked. Just because you put an M at the end doesn't automatically make it unlocked....pssh noobs. ?
Click to expand...
Click to collapse
No it doesnt, but the M does have a recovery and is able to flash any of Sileshnair's roms.
It is not an ATT device.
GT......what are you doing here?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
captemo said:
No it doesnt, but the M does have a recovery and is able to flash any of Sileshnair's roms.
It is not an ATT device.
GT......what are you doing here?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
So if I put an M at the end of my Nexus5 can I flash Sileshnairs Roms?
@captemo, I'm watching my friend at work building roms, and hopefully keeping you out of trouble. Don't mess with Apen..lol
btw, I'm sure Mark Bencze will really appreciate if you'd stick around while he works this out.
---------- Post added at 10:53 PM ---------- Previous post was at 10:23 PM ----------
apen83 said:
So if I put an M at the end of my Nexus5 can I flash Sileshnairs Roms?
Click to expand...
Click to collapse
as the user you get to choose if adding that m does that
GT247 said:
edit>>> @scoobthegambler, you are right, I made a mistake, my apologies
@pierrottls31 it's very poor etiquette to post another devs rom in someone else's rom thread. Please help to keep development threads eleventh to the threads they pertain to
Thanks in advance
Click to expand...
Click to collapse
I did not mean too, I just wanted him to know you can go from more clean room to start than stock... Stock rom is buggy and all... I took the rom from megafire and tweak it my way, this way I dont have to re-correct all the bug.... but sorry if it was mis-understood... I did mention it for reference only.... cheers

factory rom problems

I truly hope someone here can help me. I am trying to fix my wife's tablet. Its a cheaper tablet (a craig cmp756), 70 dollars, but to me 70 isn't cheap. It was acting up, freezing, glitching and locking up. I got on the factory site, and found 2 firmware update packages for it. One was android 4.2 which it had in it, and the other was android 4.4. I tried to upgrade the firmware last night to 4.4. There is a bug in the update software. The screen dpi is NOT correct in the new firmware package. I say it is not correct because the screen will not rotate, and when you touch an icon to open it up, you have to touch about a half inch below it to activate it. So, I know there is a problem with the firmware. I downloaded the 4.2 and tried to revert, but it will not. I cannot even get into the settings far enough to activate developer options and activate usb debugging, so I cannot get a pc to link up to it. It has never been able to link up to a pc though for some reason. I really need to speak to someone who knows how to modify roms or firmware updates. I know that somewhere in the fw update packages is a file dealing with the screen dpi or resolution settings. I really need to swap in the 4.2 settings file into the 4.4 fw package. Can someone please help me?
tattmann said:
I truly hope someone here can help me. I am trying to fix my wife's tablet. Its a cheaper tablet (a craig cmp756), 70 dollars, but to me 70 isn't cheap. It was acting up, freezing, glitching and locking up. I got on the factory site, and found 2 firmware update packages for it. One was android 4.2 which it had in it, and the other was android 4.4. I tried to upgrade the firmware last night to 4.4. There is a bug in the update software. The screen dpi is NOT correct in the new firmware package. I say it is not correct because the screen will not rotate, and when you touch an icon to open it up, you have to touch about a half inch below it to activate it. So, I know there is a problem with the firmware. I downloaded the 4.2 and tried to revert, but it will not. I cannot even get into the settings far enough to activate developer options and activate usb debugging, so I cannot get a pc to link up to it. It has never been able to link up to a pc though for some reason. I really need to speak to someone who knows how to modify roms or firmware updates. I know that somewhere in the fw update packages is a file dealing with the screen dpi or resolution settings. I really need to swap in the 4.2 settings file into the 4.4 fw package. Can someone please help me?
Click to expand...
Click to collapse
incompatble firmware buddy
Sent from my GT-N7105 using Tapatalk
tornado92 said:
incompatble firmware buddy
Sent from my GT-N7105 using Tapatalk
Click to expand...
Click to collapse
so youre saying its not a simple swap of a dpi screen res file from old fw to new?
tattmann said:
so youre saying its not a simple swap of a dpi screen res file from old fw to new?
Click to expand...
Click to collapse
You flashed via livesuit??
Sent from my GT-N7105 using Tapatalk
tornado92 said:
You flashed via livesuit??
Sent from my GT-N7105 using Tapatalk
Click to expand...
Click to collapse
I flashed by placing the files on the external and booting. It auto flashed. I cannot get it to revert back, and cant get the new fw to work the screen properly
Is it a all winner tablet?? Can u unscrew and check procesor?? Is it wriiten a13 or a10?
Sent from my GT-N7105 using Tapatalk
---------- Post added at 06:33 PM ---------- Previous post was at 06:23 PM ----------
tattmann said:
I flashed by placing the files on the external and booting. It auto flashed. I cannot get it to revert back, and cant get the new fw to work the screen properly
Click to expand...
Click to collapse
http://www.craigelectronics.com/firmware_update/android4.4/cmp756hd_firmware4.4.rar
Sent from my GT-N7105 using Tapatalk
Okay, thats the high def version. Mine is the lower res version. Will that make a difference?
I cant post a link to the one I downloaded as I havent reached 10 posts yet however the last of the url is pdetails.php?id=580
I opened it. allwinner? no. chip says amlogic aml8726-mxs a-ppg176.00 dmwsno57
just to let you know, I was able to install the fw you posted the link to. its a lot worse now lol. The screen is only showing me about 2/3 of whats supposed to be there. So that was definitely the wrong fw. I am about to give up and throw this thing in the trash and get a different brand. If I could find a program to autoload and root from the external sd card, then I may be able to downgrade the fw back to 4.2. until then I guess I am out of luck.

Categories

Resources