Database Users

EA28 OTA

I just activated my girlfriend's phone and immediately it prompted for update, so I did. To my surprise it was not DL09, but instead EA28. So after some google searches I found this:
http://phandroid.com/2011/02/03/samsung-fascinates-ea28-update-coming-to-fix-emergency-calling-bug/

The site is basically right, they repackaged dl09 with the emergency calling bugfix and pushed it out with a new build number.

just got mine... I'm gonna have a seizure in a public place to test it out.

Does any one know if one click root will work with this update
Sent from my SCH-I500 using XDA App

Deathbeaver said:
Does any one know if one click root will work with this update
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
It worked for me on DL09 and this isn't that much different so I'd say yes.

Skrazz said:
just got mine... I'm gonna have a seizure in a public place to test it out.
Click to expand...
Click to collapse
Youtube...

The only other thing that worries me is odin I have no idea what version to get our how to use it....thanks an advance from noob
Sent from my SCH-I500 using XDA App

Deathbeaver said:
The only other thing that worries me is odin I have no idea what version to get our how to use it....thanks an advance from noob
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
There is a thread on ODIN. Simple directions, I thought.
Sent from my SCH-I500 using XDA App

So how does one "Make instantaneous emergency calls from a locked device in a time of need"?

Deathbeaver said:
The only other thing that worries me is odin I have no idea what version to get our how to use it....thanks an advance from noob
Just as a side note if your having to redo the phone from scratch make sure to put the pit file in the pit on odin otherwise the phone will not activate!
Click to expand...
Click to collapse

One Click root works just fine! Just completed root!

I believe I was able to root successfully but when I try to flash ClockwordMod, it doesn't seem to be working. ROM manager says its flashed and has the latest version, but when I boot into recovery it is definitely not ClockwordMod. I cannot do backups or choose a file from SD to install.

PantsOnFire said:
I believe I was able to root successfully but when I try to flash ClockwordMod, it doesn't seem to be working. ROM manager says its flashed and has the latest version, but when I boot into recovery it is definitely not ClockwordMod. I cannot do backups or choose a file from SD to install.
Click to expand...
Click to collapse
When you flash a new ROM it overwrites CWM, so you'll have to re-install it with Odin.

What is pit in general and why it is needed?

CNemo7539 said:
What is pit in general and why it is needed?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=771426
may answer some questions
http://forum.xda-developers.com/showthread.php?t=723596
may answer others
the search tool is great. google works too.

Update broke my phone!
I just saw a screen forcing the update upon my phone. I clicked "OK" but when the EA28 update installed itself on my phone, it locked my phone into a cycle of trying to install it again and again. The baseband version shows S:i500.04 V.EA28, the Build number shows SCH-I500.EA28, but the update keeps trying to install the update. It gives a Prompt to Install-Reboots Phone-Prompt to Install-Reboot Phone... I managed to get it to stop for a little while by scheduling a deferral of the update until tomorrow. Does anyone know how I can keep the update from trying to install?

Yeah I just went to ask if there is an update and it said yes. Afraid to update because who knows if it'll break root....
Sent from my SCH-I500 using XDA App

Why suggest people to mess with pit in odin? You do NOT need to do this. Geez, people make this mistake enough on their own. Pda, choose file, press start... thats it.
Sent from my stock 2.1 unrooted, fully bloated Fascinate

EA28 broke my phone
knmb323 said:
I just saw a screen forcing the update upon my phone. I clicked "OK" but when the EA28 update installed itself on my phone, it locked my phone into a cycle of trying to install it again and again. The baseband version shows S:i500.04 V.EA28, the Build number shows SCH-I500.EA28, but the update keeps trying to install the update. It gives a Prompt to Install-Reboots Phone-Prompt to Install-Reboot Phone... I managed to get it to stop for a little while by scheduling a deferral of the update until tomorrow. Does anyone know how I can keep the update from trying to install?
Click to expand...
Click to collapse
I managed to get my phone to stop rebooting every 3 minutes by ending the InnoPath Active Care process and clearing the cache. But when I woke up this morning, the phone was at the emergency recovery screen. It went into a cycle of rebooting that made it as far as media scanner. I got it to stop rebooting by turning ON wifi (I suppose that's because Active Care needs WiFi off to do an OTA). Does anyone have any suggestions on how to stop this "Feature" that is rebooting my phone?

You tried pulling the battery (soft reset) i presume? After that theres factory rest, then odin back to stock
Sent from my stock 2.1 unrooted, fully bloated Fascinate

Updated OTA - Now my tab seems broken

Hey everyone. My 8013 has been rooted and running like a champ. Today I ran the OTA update via Kies and it said it successfully installed. I show that Im on build UEALH2.
I was having issues where it looked like the OTA didnt install all the way because I was getting notifications again that it was available. I rebooted into CWM and cleared the cache and dalvik, rerooted and booted into the device again. It went through the OTA installer again. This time when it was done, I checked and no software updates available. Sweet.
But now Im having issues with my screen not responding to touch inputs. The screen is still working, because I can remove the pen and the side bar loads, plus widgets are still updating... but it wont accept any inputs from my fingers or the pen? I did a factory reset to see if that would fix it, but what happens is when it starts up I have control of the touch screen. If I lock the device and then try to unlock it, the screen is immediately unresponsive to touch input. I was going to flash using Odin and the latest stock rom but the only post I saw where the latest rom was posted at shows the file is down: http://forum.xda-developers.com/showthread.php?t=1847706
Any ideas on what could be wrong or where I should go from here? Ive never ran into any issues like this with past devices.

GaresTaylan said:
Hey everyone. My 8013 has been rooted and running like a champ. Today I ran the OTA update via Kies and it said it successfully installed. I show that Im on build UEALH2.
I was having issues where it looked like the OTA didnt install all the way because I was getting notifications again that it was available. I rebooted into CWM and cleared the cache and dalvik, rerooted and booted into the device again. It went through the OTA installer again. This time when it was done, I checked and no software updates available. Sweet.
But now Im having issues with my screen not responding to touch inputs. The screen is still working, because I can remove the pen and the side bar loads, plus widgets are still updating... but it wont accept any inputs from my fingers or the pen? I did a factory reset to see if that would fix it, but what happens is when it starts up I have control of the touch screen. If I lock the device and then try to unlock it, the screen is immediately unresponsive to touch input. I was going to flash using Odin and the latest stock rom but the only post I saw where the latest rom was posted at shows the file is down: http://forum.xda-developers.com/showthread.php?t=1847706
Any ideas on what could be wrong or where I should go from here? Ive never ran into any issues like this with past devices.
Click to expand...
Click to collapse
Same issues here. Have been speaking with entropy and another member to try to fix this. I am at a loss as well.
Things I have tried:
*MD5 Post-update*
*Wipe Data/Cache via stock recovery*
*Re-flash MD5*
I am now in the process of locating a UEALGB recovery/kernel. If any member has a link to it or can help its certainly appreciated.

vanillanesquik said:
Same issues here. Have been speaking with entropy and another member to try to fix this. I am at a loss as well.
Click to expand...
Click to collapse
Are you just having OTA update issues or is your screen not responding properly to touch as well?

GaresTaylan said:
Are you just having OTA update issues or is your screen not responding properly to touch as well?
Click to expand...
Click to collapse
No touch, no pen input. Its worst-case.

vanillanesquik said:
No touch, no pen input. Its worst-case.
Click to expand...
Click to collapse
If you find the UEALGB recovery/kernel please let me know and provide the steps you used to fix the issue.
Guess thats what I get for jumping the gun on the update.

GaresTaylan said:
If you find the UEALGB recovery/kernel please let me know and provide the steps you used to fix the issue.
Guess thats what I get for jumping the gun on the update.
Click to expand...
Click to collapse
The update restored touch function but the pen functions are completely derped.
A pre-rooted full package is being uploaded by entropy in the next 2 hours so I am crossing my fingers that this will fix it.

I have the same issues I\m trying all things to get it to work just like you are to no avail, Samsung update now things are all screwed up

Alright (For N8013) who have lost pen/touch:
1. Wipe data/cache via stock recovery/kernel flashed in ODIN: http://forum.xda-developers.com/show...9&postcount=45
2. Flash root injected system via ODIN: http://stockroms.net/file/GalaxyNote...ctedSystem.zip
3. Re-kies to new firmware via WINDOWS

vanillanesquik said:
Alright (For N8013) who have lost pen/touch:
1. Wipe data/cache via stock recovery/kernel flashed in ODIN: http://forum.xda-developers.com/show...9&postcount=45
2. Flash root injected system via ODIN: http://stockroms.net/file/GalaxyNote...ctedSystem.zip
3. Re-kies to new firmware via WINDOWS
Click to expand...
Click to collapse
top link is dead, btw i lost touch functions LOL
anyway i will fix it

I'm not sure why any rooted user would take an OTA?
Sent from my EVO using Tapatalk 2

I had the same issue and flashed this via Odin: http://forum.xda-developers.com/showthread.php?t=1847706
Fixed it and now i'm running the latest update.

I lost touch and pen and now i have them back. Heres how:
1. IM AWESOME!
2. Rebooted my computer.
3. Wiped everything.
4. ODIN root injected original firmware.
5. Kies update.
6. ODIN Clockwork Recovery
7. Flash Superuser.
Boom, everything works.
** DISCLAIMER - There is a strong possibility this worked only due to #1. YMMV.
Sent from my GT-N8013 using Tapatalk 2

-viperboy- said:
I'm not sure why any rooted user would take an OTA?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Thank you!!! I have been saying this in other threads. Why would you use anything from Samsung knowing you have modified files to have root. :banghead:
Sent from my Galaxy Note 10.1 using Tapatalk

BigAtrain said:
Thank you!!! I have been saying this in other threads. Why would you use anything from Samsung knowing you have modified files to have root. :banghead:
Sent from my Galaxy Note 10.1 using Tapatalk
Click to expand...
Click to collapse
I took the OTA via Kies because it was listed in the OTA update thread that it was ok to do so? And that root was working fine afterward?

BigAtrain said:
Thank you!!! I have been saying this in other threads. Why would you use anything from Samsung knowing you have modified files to have root. :banghead:
Sent from my Galaxy Note 10.1 using Tapatalk
Click to expand...
Click to collapse
Because we are dangerous, exciting and chicks dig us.
Sent from my GT-N8013 using Tapatalk 2

-viperboy- said:
I'm not sure why any rooted user would take an OTA?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
The root method 2 specified that OTA was viable with stock recovery. I flashed stock recovery and the OTA failed. We were then forced to update via KIES and touch/pen functions were then bugged. The best way is my method above.

vanillanesquik said:
Alright (For N8013) who have lost pen/touch:
1. Wipe data/cache via stock recovery/kernel flashed in ODIN: http://forum.xda-developers.com/show...9&postcount=45
2. Flash root injected system via ODIN: http://stockroms.net/file/GalaxyNote...ctedSystem.zip
3. Re-kies to new firmware via WINDOWS
Click to expand...
Click to collapse
I tried this method and when my note boots up s note keeps crashing every 15 seconds or so without my even opening it.

BigAtrain said:
Thank you!!! I have been saying this in other threads. Why would you use anything from Samsung knowing you have modified files to have root. :banghead:
Sent from my Galaxy Note 10.1 using Tapatalk
Click to expand...
Click to collapse
In many cases, if you ONLY have added su and Superuser.apk - you can safely apply an OTA. However if you've touched anything else in /system - boom

Standard practice is to reimage back to stock then apply OTA but the full image wasn't available via Kies until this update came out. This will be less of issue going forward as there's a full image now.

mi7chy said:
Standard practice is to reimage back to stock then apply OTA but the full image wasn't available via Kies until this update came out. This will be less of issue going forward as there's a full image now.
Click to expand...
Click to collapse
OK so o tried vanillas order and kies froze or disconnect me or something so I odined the md5 tar of the new update and back to no touch screen but like 5 mins so I shut it off and resume later.
What is the best thing to do to get all fixed up?
Sent from a Baked Black Jelly Belly

Rogers 4.4.2 updated!

Woot. Finally!
Sent from my XT1058 using xda app-developers app

varcos said:
Woot. Finally!
Click to expand...
Click to collapse
My fiancee's Fido's Moto X just got the OTA notification. I told her to wait until it's rooted.

Just now.
Sent from my XT1058 using xda app-developers app

thor124 said:
My fiancee's Fido's Moto X just got the OTA notification. I told her to wait until it's rooted.
Click to expand...
Click to collapse
Flash before you root otherwise it will result in bootloops, twrp should and will work without issues as its still kitkat
Sent on my Lenoto X

got the update.. while installing my phone shuts off? now it won't turn on or even get into bootloader?? my battery was at 80%? wth am i hard bricked?? i was on stock 4.2.2 unlocked bootloader and non rooted.

Yup got the update an hour ago, but I'm bummed that I lost my big font settings (was previously rooted), now I gotta wait til 4.4 gets a root, even with "large" font settings in both display and accessability, it's too small.

Just got the update as well, disappointed with the camera still.

crookx said:
got the update.. while installing my phone shuts off? now it won't turn on or even get into bootloader?? my battery was at 80%? wth am i hard bricked?? i was on stock 4.2.2 unlocked bootloader and non rooted.
Click to expand...
Click to collapse
Ouch, had you done any upgrading or downgrading or flashing in the past? Do you get anything when you plug it into a PC, if you do it can likely be restored.

Mine updated. Happy to finally get the smart dialer - something HTC has had since Froyo. Not a great fan of the all white notification icons, but I'll get used to it.

Steve-x said:
Ouch, had you done any upgrading or downgrading or flashing in the past? Do you get anything when you plug it into a PC, if you do it can likely be restored.
Click to expand...
Click to collapse
well i flashed one of the 4.4.2 firmwares from the uk had that running great. but i flashed back to stock rogers 4.2.2 since i knew we will be having a update soon. did i mess something up?? shoot me

crookx said:
well i flashed one of the 4.4.2 firmwares from the uk had that running great. but i flashed back to stock rogers 4.2.2 since i knew we will be having a update soon. did i mess something up?? shoot me
Click to expand...
Click to collapse
What did you do to flash back to 4.2.2? That raises a red flag for me as the upgrade to 4.4.2 would have incremented the bootloader version and from what I can determine you can only safely downgrade to 4.4 (Yes I know there is no 4.4 for Rogers)
I would say it is a brick for certain at the moment, but there is a chance you can recover it, check this thread - http://forum.xda-developers.com/showthread.php?t=2629057

I also got the update! I'm on Rogers. When I tried applying it, the phone went into an endless loop of booting up into the OS, and then "Powering off." I fixed this by restoring to android 4.2.2 through RSDLite, but I'm wondering if anyone can help me out here. I don't know what is going on...

50CalPotato said:
I also got the update! I'm on Rogers. When I tried applying it, the phone went into an endless loop of booting up into the OS, and then "Powering off." I fixed this by restoring to android 4.2.2 through RSDLite, but I'm wondering if anyone can help me out here. I don't know what is going on...
Click to expand...
Click to collapse
u can stop the loop by clearing ur cache in recovery.
now.... who can tell me how to unroot so i can install the damn thing? do i need to remove TWRP too? if yes, how?

I still didnt get it
Sent from my XT1058 using Tapatalk

Steve-x said:
What did you do to flash back to 4.2.2? That raises a red flag for me as the upgrade to 4.4.2 would have incremented the bootloader version and from what I can determine you can only safely downgrade to 4.4 (Yes I know there is no 4.4 for Rogers)
I would say it is a brick for certain at the moment, but there is a chance you can recover it, check this thread - http://forum.xda-developers.com/showthread.php?t=2629057
Click to expand...
Click to collapse
problem is when i plug in my device to the pc nothing shows up? not even that QHSUSB_DLOAD that tut is mentioning?

crookx said:
problem is when i plug in my device to the pc nothing shows up? not even that QHSUSB_DLOAD that tut is mentioning?
Click to expand...
Click to collapse
Try holding the power button down for up to 1 minute. A few times if needed, while connected to the computer via USB.

R3dbeaver said:
u can stop the loop by clearing ur cache in recovery.
now.... who can tell me how to unroot so i can install the damn thing? do i need to remove TWRP too? if yes, how?
Click to expand...
Click to collapse
First I would uninstall xposed or anything like that. Then, I'm assuming you have an unlocked bootloader, so you would need to flash the the 4.2.2 (I assume that is what you are on?) recovery. I'm not sure if having root will do anything. If so, then you need to reflash the stock kernel and then clear the cache and you should be back to stock. Alternatively I think you can also use a tool kit.

Jayrod1980 said:
First I would uninstall xposed or anything like that. Then, I'm assuming you have an unlocked bootloader, so you would need to flash the the 4.2.2 (I assume that is what you are on?) recovery. I'm not sure if having root will do anything. If so, then you need to reflash the stock kernel and then clear the cache and you should be back to stock. Alternatively I think you can also use a tool kit.
Click to expand...
Click to collapse
1. where can i find the stock 4.2.2 recovery?
2. which tool kit will work with Canadian Rogers?

50CalPotato said:
I also got the update! I'm on Rogers. When I tried applying it, the phone went into an endless loop of booting up into the OS, and then "Powering off." I fixed this by restoring to android 4.2.2 through RSDLite, but I'm wondering if anyone can help me out here. I don't know what is going on...
Click to expand...
Click to collapse
Are you rooted? Try fastboot erase cache hopefully that works, otherwise its fastboot erase userdata and bam factory reset list everything. Its bootlooping due to root or a bad system file
Sent on my Lenoto X

I'm not rooted I just received my update notification and it's downloading 4.4.2 as we speak.
I'm on Rogers
Sent from my XT1058 using xda app-developers app

Knox after restore

I restored my galaxy back to stock with Odin and now I'm getting constant Knox pop ups. Anyone know the fix to make this go away so I can give the phone to my wife to use unrooted?
Thanks in advance for your help
Sent from my iPhone using Tapatalk

Also, if I try and install the Knox app, it says it can't be installed because I previously installed a custom os
Sent from my iPhone using Tapatalk

Last thing, it's showing custom rom in the download screen. It's not showing Knox 0x1. So Knox wasn't tripped.
Sent from my iPhone using Tapatalk

didureboot said:
I restored my galaxy back to stock with Odin and now I'm getting constant Knox pop ups. Anyone know the fix to make this go away so I can give the phone to my wife to use unrooted?
Thanks in advance for your help
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
There's a real easy fix if you're rooted...
What does the pop-up even say, you never explained

I think I solved the problem. I changed the file system to art and then back to dalvik. The lock and custom are gone on boot up now. Now I just gotta figure out why when trying to update, it says that the update service is temporarily unavailable.

Does your baseband and build number match? What did you flash?

I was rooted on NI2. Restored to stock NI2. Had the custom message with the padlock icon on startup. Finally changing to art and back to dalvik made the padlock go away.

T
didureboot said:
I think I solved the problem. I changed the file system to art and then back to dalvik. The lock and custom are gone on boot up now. Now I just gotta figure out why when trying to update, it says that the update service is temporarily unavailable.
Click to expand...
Click to collapse
You could Odin the build you wanted to update to. Did you connect with kies?

I didn't connect with kies. I used standard Samsung drivers and Odin.

didureboot said:
I didn't connect with kies. I used standard Samsung drivers and Odin.
Click to expand...
Click to collapse
Some people connect to kies to get their updates. Just thought that might be worth trying.

Hadn't thought about that. Will remote into my home computer and get that installed so I can try that this evening. Thanks for the idea.

didureboot said:
Hadn't thought about that. Will remote into my home computer and get that installed so I can try that this evening. Thanks for the idea.
Click to expand...
Click to collapse
Here is someone with the same problem. Seems like their answer was to flash the stock firmware.
http://forums.androidcentral.com/sa...ollipop-not-working-out-help.html#post4223525

Downgrade from Nougat causes loss of vibrator

Hi,
I had a rooted phone and TWRP and was using the latest Nougat release. However i decided to return to stock so using Kies i did a full factory reset.
It's working - however i've lost the vibrator functionality. I can hear a faint beep whenever the phone should vibrate. The only solution i can find here on xda seems to be downgrading the bootloader, so i'ved tried flashing everything through Odin with same results.
When I try to open the bootloader (volume up, power and home button) it shows the Android updating screen (installing system update) which after a while fails (exclamation mark) - and shows the Samsung bootloader where i can reset phone, clear cache etc.
Any ideas on how to fix the vibrator?

sessingø said:
Hi,
I had a rooted phone and TWRP and was using the latest Nougat release. However i decided to return to stock so using Kies i did a full factory reset.
It's working - however i've lost the vibrator functionality. I can hear a faint beep whenever the phone should vibrate. The only solution i can find here on xda seems to be downgrading the bootloader, so i'ved tried flashing everything through Odin with same results.
When I try to open the bootloader (volume up, power and home button) it shows the Android updating screen (installing system update) which after a while fails (exclamation mark) - and shows the Samsung bootloader where i can reset phone, clear cache etc.
Any ideas on how to fix the vibrator?
Click to expand...
Click to collapse
Buy a new vibrator and enjoy :laugh:

Flash last bootlader and radio.

Leejay1953 said:
Buy a new vibrator and enjoy :laugh:
Click to expand...
Click to collapse
are you kidding me, this same problem happened to me, what is the solution

Leejay1953 said:
Buy a new vibrator and enjoy [emoji23]
Click to expand...
Click to collapse
Lol. I think some didn't understand this.

Eye eye saucy! Lol
Sent from my SM-G935F using XDA-Developers mobile app

Leejay1953 said:
Buy a new vibrator and enjoy :laugh:
Click to expand...
Click to collapse
hahaha! this is a nice one! :laugh::good:

Waaat. I have the same issue. But I like it lol. It sounds nice. So I just kept it. And it randomly happens. Depends on what rom I use.

Must be upsetting having a broken vibrator

Ask your girlfriend where it is.
Gesendet von meinem SM-G935F mit Tapatalk

Rofl, bad boys !

....

Here's the solution!
sessingø said:
Hi,
I had a rooted phone and TWRP and was using the latest Nougat release. However i decided to return to stock so using Kies i did a full factory reset.
It's working - however i've lost the vibrator functionality. I can hear a faint beep whenever the phone should vibrate. The only solution i can find here on xda seems to be downgrading the bootloader, so i'ved tried flashing everything through Odin with same results.
When I try to open the bootloader (volume up, power and home button) it shows the Android updating screen (installing system update) which after a while fails (exclamation mark) - and shows the Samsung bootloader where i can reset phone, clear cache etc.
Any ideas on how to fix the vibrator?
Click to expand...
Click to collapse
Temporarily upgrade to Android 7 to fix the vibration issue then use odin to flash final version of android 6.0.1. You must flash all 4 files contained in the extracted (unzipped) firmware package but ignore the home_CSC file. IMPORTANT...tick the option in odin "phone bootloader update". This process will wipe all data on the phone full but will give you a fully functioning galaxy s7 with Android 6.0.1 marshmallow!

Leejay1953 said:
Buy a new vibrator and enjoy :laugh:
Click to expand...
Click to collapse
Hi,
I'm interested to learn how you downgraded your boot-loader from DRAG update? Can you please explain?
Thank you.
M T Coulibaly