I have a Galaxy S 4G Rooted and Unlocked. I tried to install a special lock screen tweak, and all of the sudden upon booting, the Android System imemdiately force closes. The screen stays totally black after the T-Mobile splash screen and Galaxy S logo come up.
I've erased all my data, but what i really need to do is flash the phone (i think...)
What should i do?
Thanks.
danstheman7 said:
I have a Galaxy S 4G Rooted and Unlocked. I tried to install a special lock screen tweak, and all of the sudden upon booting, the Android System imemdiately force closes. The screen stays totally black after the T-Mobile splash screen and Galaxy S logo come up.
I've erased all my data, but what i really need to do is flash the phone (i think...)
What should i do?
Thanks.
Click to expand...
Click to collapse
If your phone appears to be bricked what you may have to do is flash your phone with one of the three or four Stock Roms that can be found on the DEV site. Check here to see how to use ODEN. For flashing Roms ODEN is the process that is being used on the SGS4G until CWM is working. There may be another way to fix your issue, but if you can get into download mode ODEN should work to get you back to working order. Just make sure you don’t check Partition when using ODEN.
danstheman7 said:
What should i do?
Thanks.
Click to expand...
Click to collapse
You are in luck!!! Check Here http://forum.xda-developers.com/showthread.php?t=1061093
Samsung just released an update using Kies Mini. It's just bug fixes, but it addresses your blank screen. Kies Mini Updates your system Over The Air (OTA). read up on it before you do it. It can be done with the data connection from your phone, but you may want to have a WiFi backup to download the ROM. You don't want it to get interupted during the download process.
nwpro3 said:
You are in luck!!! Check Here http://forum.xda-developers.com/showthread.php?t=1061093
Samsung just released an update using Kies Mini. It's just bug fixes, but it addresses your blank screen. Kies Mini Updates your system Over The Air (OTA). read up on it before you do it. It can be done with the data connection from your phone, but you may want to have a WiFi backup to download the ROM. You don't want it to get interupted during the download process.
Click to expand...
Click to collapse
I ended up using ODEN like you said, and installed 2.2.1 FROYO KC1.
Phone works fine now, thank you
Oh, and I tried clicking "Software Update" and it says "No Firmware"....
Maybe because i'm unlocked on AT&T?
danstheman7 said:
I ended up using ODEN like you said, and installed 2.2.1 FROYO KC1.
Phone works fine now, thank you
Oh, and I tried clicking "Software Update" and it says "No Firmware"....
Maybe because i'm unlocked on AT&T?
Click to expand...
Click to collapse
I don't think Kies recognizes the KC1 firmware since it was never an official release. Hopefully someone will get a firmware dump so that Whitehawk can give us a Deodexed version soon.
danstheman7 said:
I ended up using ODEN like you said, and installed 2.2.1 FROYO KC1.
Phone works fine now, thank you
Oh, and I tried clicking "Software Update" and it says "No Firmware"....
Maybe because i'm unlocked on AT&T?
Click to expand...
Click to collapse
Good to hear you got your phone back up and working. Whether you use KC1 or the new KD1 that was just released won’t make all that much difference. When you clicked on Update Software it is looking for the Over The Air Update firmware. That update is selectively distributed to phones from TMO as the bandwidth allows. Your phone hasn’t received the OTA update yet. That is why you got the No Firmware message. The other way you can download the KD1 firmware is by using Keis Mini software from Samsung. I did that update last night and now have the KD1 Firmware. If you are on AT&T you would have to get the OTA update from them if you are on that network. That is if they decide to send it out.
Ah, great.
Well either way I removed the bloatware apps on my phone with TitaniumBackup, so no OTA for me anyway, correct?
danstheman7 said:
Ah, great.
Well either way I removed the bloatware apps on my phone with TitaniumBackup, so no OTA for me anyway, correct?
Click to expand...
Click to collapse
Tmo is in the process of scheduling OTA updates. If you are on ATT, the update will have to come from them if they are sending them out. You can also use the Kies Mini application to get the KD1 update from Samsung Here Check the OP. There is also a Deodexed version On the Dev page. http://forum.xda-developers.com/showthread.php?t=1063696. Note: The Deodexed version needs to be flashed using ODEN or Heimdall.
Yeah just follow the steps in this guide http://forum.xda-developers.com/showthread.php?t=1001759
to flash the deodexed rom in the post above me.
I've noticed there was an update on kies this week (P3113UEBLH1), I'm not sure what it was thought.
I've tried upgrading in kies, it was stuck at 0% downloading then connection timed out.
The OTA update didn't find any updates available.
Then next morning, kies said no update available too.
So, Anyone got the update to work, and if so what changes did you notice?
The update is available for flashing with odin on samsung-updates.com , this is the 2nd 4.0.4 update. (I'm still running the old 4.0.4 (P3113UEBLG5))
I don't have it, but I can look into it...
Bibicp said:
I've noticed there was an update on kies this week (P3113UEBLH1), I'm not sure what it was thought.
I've tried upgrading in kies, it was stuck at 0% downloading then connection timed out.
The OTA update didn't find any updates available.
Then next morning, kies said no update available too.
So, Anyone got the update to work, and if so what changes did you notice?
The update is available for flashing with odin on samsung-updates.com , this is the 2nd 4.0.4 update. (I'm still running the old 4.0.4 (P3113UEBLG5))
Click to expand...
Click to collapse
My device is rooted, and the only backup I made with CWM was after I rooted, if I go to update (if my device can find it) will I:
1) Brick out and be screwed?
2) Have to flash my backup (which is rooted, so would that mean I can't update again?)
3) Be ok and keep my rooting?
4) Be ok, and lose my rooting, and have to re-root?
I realize I am kind of answering your question with a question, but I would be happy to see if I can track it down and see what changes there are, if it's safe to install.
FlynnErik said:
My device is rooted, and the only backup I made with CWM was after I rooted, if I go to update (if my device can find it) will I:
1) Brick out and be screwed?
2) Have to flash my backup (which is rooted, so would that mean I can't update again?)
3) Be ok and keep my rooting?
4) Be ok, and lose my rooting, and have to re-root?
I realize I am kind of answering your question with a question, but I would be happy to see if I can track it down and see what changes there are, if it's safe to install.
Click to expand...
Click to collapse
Try backing up your system using clockworkmod recovery first, then go to download mode, flash your firmware version (download from samfirmware or samsung-updates) and flash it with odin.
This way you're unrooted, running stock rom and stock recovery and then you can install the update.
I didn't try to install an update while rooted, but it's not recommended so don't try.
I did a back up after I rooted with CWM
Bibicp said:
Try backing up your system using clockworkmod recovery first, then go to download mode, flash your firmware version (download from samfirmware or samsung-updates) and flash it with odin.
This way you're unrooted, running stock rom and stock recovery and then you can install the update.
I didn't try to install an update while rooted, but it's not recommended so don't try.
Click to expand...
Click to collapse
So is my backup going to be rooted? Or will it be the stock? I am currently rooted stock 4.0.4.
Btw, I have found no information about the update anywhere on the net. Maybe they accidently did a push to us, and pulled it back?
Should I wipe cache, dalvik and FDR before I flash the firmware from those sites or use the backup I made already? (which I am unsure if I should even use since idk if it will be rooted or not lol)
I wasn't going to update till it was time to get JB, but this update that vanished is intriguing enough I might lol
As i know yes when you restore backup with cwm the result will be rooted also as the cwm takes image of the system when doing backup and as you when doing backup was rooted so when restore this backup you will be still rooted if you flash via odin no need to wipe cash and dalvik cash i never read anyone doing this
Even if you do this wipe no harm at all
Sent from my GT-I9100 using xda app-developers app
As mohamed selim said, but wipe your data and do a factory reset in clockworkmod (after backup)
and why will samsung pull back the update?
There's several reasons why this may happen
Bibicp said:
As mohamed selim said, but wipe your data and do a factory reset in clockworkmod (after backup)
and why will samsung pull back the update?
Click to expand...
Click to collapse
They pushed it out to the wrong devices
They pushed it out to early
They found a last minute bug and had to pull back
They are testing it, and not everyone should have gotten the option to get it.
Ok so to get things straight. If/when we go to JB I will need to download a firmware stock from one of the sites listed above, download it.
Do a backup (just to be safe of what I have now)
FDR/Wipe everything
Install the firmware using Odin
If everything looks good, re-flash CWM
Do another backup so I have a clean stock to revert back to down the road if needed.
That sum it up correctly? This way I can bookmark this thread so I don't forget lol.
**EDIT** When I use Odin to restore stock will I lose CWM? If so, what happens if something goes wrong in the Odin restore and I have a boot loop, or etc, what would be my next move since I won't have CWM to restore previous, would I be able to install it like I would if things were going ok?
Sorry for sounding like a n00b, I am still learning all about this, but I think I am getting closer to learning enough to not be a n00b lol. I only have 10 tabs open with this forum instead of 20!
FlynnErik said:
They pushed it out to the wrong devices
They pushed it out to early
They found a last minute bug and had to pull back
They are testing it, and not everyone should have gotten the option to get it.
Ok so to get things straight. If/when we go to JB I will need to download a firmware stock from one of the sites listed above, download it.
Do a backup (just to be safe of what I have now)
FDR/Wipe everything
Install the firmware using Odin
If everything looks good, re-flash CWM
Do another backup so I have a clean stock to revert back to down the road if needed.
That sum it up correctly? This way I can bookmark this thread so I don't forget lol.
**EDIT** When I use Odin to restore stock will I lose CWM? If so, what happens if something goes wrong in the Odin restore and I have a boot loop, or etc, what would be my next move since I won't have CWM to restore previous, would I be able to install it like I would if things were going ok?
Sorry for sounding like a n00b, I am still learning all about this, but I think I am getting closer to learning enough to not be a n00b lol. I only have 10 tabs open with this forum instead of 20!
Click to expand...
Click to collapse
It's not for the wrong device since it's saying P3113, and it's not jelly bean. as I've seen on samsung firmware.com it's 4.0.4.
Well, on my homescreen I put a shortcut for the software update, it still has a circle saying 'N" on it (which probably stands for new), but going in kies I don't find it, It only says it downloaded it but the firmware is up to date.
So probably either they really pulled it back, or it's a bug and they're fixing it. (I really can't wait for jelly bean)
Second, yes it will erase the CWM recovery and go back to stock recovery.
The common mistake people make to get a bootlop is not wiping data/doing a factory reset before flashing a new ROM, so you should go to recovery and do a factory reset, then go to download mode and flash the firmware with odin. If you ever get stuck in a bootloop, try pressing volume down + power key to get to download mode and re flash the ROM. if it's still stuck, try re-downloading the ROM files you downloaded, it could be corrupted.
Awesome!
Bibicp said:
It's not for the wrong device since it's saying P3113, and it's not jelly bean. as I've seen on samsung firmware.com it's 4.0.4.
Well, on my homescreen I put a shortcut for the software update, it still has a circle saying 'N" on it (which probably stands for new), but going in kies I don't find it, It only says it downloaded it but the firmware is up to date.
So probably either they really pulled it back, or it's a bug and they're fixing it. (I really can't wait for jelly bean)
Second, yes it will erase the CWM recovery and go back to stock recovery.
The common mistake people make to get a bootlop is not wiping data/doing a factory reset before flashing a new ROM, so you should go to recovery and do a factory reset, then go to download mode and flash the firmware with odin. If you ever get stuck in a bootloop, try pressing volume down + power key to get to download mode and re flash the ROM. if it's still stuck, try re-downloading the ROM files you downloaded, it could be corrupted.
Click to expand...
Click to collapse
So the one on the site even though its XAR is us? Can I ask why we have that tag? Not something like US or etc? I mean I don't care, just kinda curious since that would make it more simple to know which region gets what, at least for me it would lol.
Thank you so much for the help and the knowledge, I figured I would end up with stock recovery, which is why I wanted to make sure about what if something goes wrong.
As a side thought, where does the backup that CWM makes located? Can I copy and paste that on to my PC so I always have a back up handy? (I would sync it into the cloud). Can I flash that with odin down the road? Or is that only a CWM usable file?
Any more info on the firmware release?....Trying to download it now!
Firmware Version: P3113UEBLH1
OS: Ice Cream Sandwich
OS Version: v4.0.4
Release Date: 08-10-2012
Build Date: 08-10-2012
Changelist: 999349
Gizmo said:
Any more info on the firmware release?....Trying to download it now!
Firmware Version: P3113UEBLH1
OS: Ice Cream Sandwich
OS Version: v4.0.4
Release Date: 08-10-2012
Build Date: 08-10-2012
Changelist: 999349
Click to expand...
Click to collapse
That's all I know about it, where are you downloading it? samsung updates.com? or kies/OTA update?
Bibicp said:
That's all I know about it, where are you downloading it? samsung updates.com? or kies/OTA update?
Click to expand...
Click to collapse
I found it on some foreign site....samsung-updates.com won't let you download the P3113UEBLH1 firmware, Just the Kernel, I don't use Kies! Uploading it right now!
Gizmo said:
I found it on some foreign site....samsung-updates.com won't let you download the P3113UEBLH1 firmware, Just the Kernel, I don't use Kies! Uploading it right now!
Click to expand...
Click to collapse
Alright, tell me if you notice anything different.
Nice
good!
Im downloading it now. Ill post it when its rooted and deodexed
Bibicp said:
I've noticed there was an update on kies this week (P3113UEBLH1), I'm not sure what it was thought.
I've tried upgrading in kies, it was stuck at 0% downloading then connection timed out.
The OTA update didn't find any updates available.
Then next morning, kies said no update available too.
So, Anyone got the update to work, and if so what changes did you notice?
The update is available for flashing with odin on samsung-updates.com , this is the 2nd 4.0.4 update. (I'm still running the old 4.0.4 (P3113UEBLG5))
Click to expand...
Click to collapse
I tried updating it once with KIES and it got to a point and froze on the screen. I had to force the tablet to shut down and rebooted and the tablet was OK. Being a glutton for punishment I tried again with KIES and the LH1 update successfully updated my GT2 7 and the About screen confirms it. Directly after installing and rebooting I started getting error messages about Chrome crashing. I uninstalled Chrome browser and reinstalled it and all is well. No other problems. Do NOT really notice ANY difference at all.
The only problem I have is that NOW I have decided that I would like to root my GT2 7 and I am NOT sure the methods I see out there will work with the P3113UEBLH1 update.
Does anyone know if my GT2 7 - P3113UEBLH1 can be rooted safely??
grobin
I dont think IT is better than CM9
RomsWell said:
Im downloading it now. Ill post it when its rooted and deodexed
Click to expand...
Click to collapse
Can you please tell me what's different than the older UEBLG5 version? and btw can you upload the stock rom itself without root so I can test it? because I couldn't download :s
EDIT: I downloaded it via samsung-updates.com and flashed it with odin.
It's pretty much the same as UEBLG5 I didn't notice anything different, but I downgraded to UEBLG5 as samsung appears to have pushed back this update (UEBLH1), because when I connect the device to kies, it doesn't recognize it.
Bibicp said:
Can you please tell me what's different than the older UEBLG5 version? and btw can you upload the stock rom itself without root so I can test it? because I couldn't download :s
EDIT: I downloaded it via samsung-updates.com and flashed it with odin.
It's pretty much the same as UEBLG5 I didn't notice anything different, but I downgraded to UEBLG5 as samsung appears to have pushed back this update (UEBLH1), because when I connect the device to kies, it doesn't recognize it.
Click to expand...
Click to collapse
I think it broke wifi. Not sure what the change log says about it. If the Cam is fixed i think im just going to add it to the G5 update. And not bother posting this untill its confrimed OTA
RomsWell said:
I think it broke wifi. Not sure what the change log says about it. If the Cam is fixed i think im just going to add it to the G5 update. And not bother posting this untill its confrimed OTA
Click to expand...
Click to collapse
Sorry for the question, but what do you mean comfirmed OTA? Once kies told me about the UEBLG5 update, I couldn't install it with kies as it was lagging.
Next day I found it on the OTA update.
This one showed on kies for a day, then next day neither kies or the OTA udpates showed there was an update so it probably got pulled back?
Rooted stock p3113: JB update downloads over the air, starts to update and fails. Tried Kies but it just keeps connecting )Uninsatlled and downlaoded Kies 3 times). Short of using ODIN, anyway to update to JB?
Bill2 said:
Rooted stock p3113: JB update downloads over the air, starts to update and fails. Tried Kies but it just keeps connecting )Uninsatlled and downlaoded Kies 3 times). Short of using ODIN, anyway to update to JB?
Click to expand...
Click to collapse
Might be possible , depending what you have installed or removed, but the easiest way will be to use ODIN .
Yeah I'm in the same boat. Can't update my stock p3113. It reminds me that I have a software update but every time I try to update I get a "Processing Failed" error. I Googled it and tried all of the fixes by logging in and out of Samsung Account, erasing details & signing up for a new account. Still no luck. I've factory reset about 5 times, I've installed and uninstalled Kies about 3 or 4 times on 2 different Win 7 x64 rigs and that still won't connect. I'm at my wit's end. Never had a device this hard to update.
Bill2 said:
Rooted stock p3113: JB update downloads over the air, starts to update and fails. Tried Kies but it just keeps connecting )Uninsatlled and downlaoded Kies 3 times). Short of using ODIN, anyway to update to JB?
Click to expand...
Click to collapse
I wrote a tutorial in the dev section on how to do this using mobile Odin light.
It is most likely failing because you're rooted...
http://forum.xda-developers.com/showthread.php?t=2098085
LeftyGR said:
I wrote a tutorial in the dev section on how to do this using mobile Odin light.
It is most likely failing because you're rooted...
http://forum.xda-developers.com/showthread.php?t=2098085
Click to expand...
Click to collapse
Well I'm not rooted but I looked over at your post and I'm in the process of trying it but I'm confused about which firmware to download and use. I see 2 JB firmwares with the same date but with different regions. Not sure which region to use with my stock US P3113. XAR or XAC?
I own a Galaxy Note 10.1 WiFi N8010, was bought in Germany quite some time ago (so CSC is German),
It came with 4.0.3, which was later updated to 4.0.4 and then to 4.1.1. Currently it is running Jellybean 4.1.1.
I had found the Exynos exploit and used it to root my device. The 4.1.2 update came out so I unrooted my device.
The "Device Status" shows "OFFICIAL".
The device received an OTA package, started installing it, started the count to 100%, and at 28-29 percent, the update stopped, the device rebooted, reported a failure and sent me to KIES.
I have some problems with KIES so I am looking for other solutions.
I thought maybe I'd use Mobile Odin to flash the stock firmware but I found it needed a flashkernel which I do not know how nor want to install right now. I was thinking about using ODIN to flash the firmware, but the size of the firmware scared me. I am used to flash 300MB SBF files on my Motorola Defy but this 1GB firmware is insane! I am afraid my computer will suddenly shut down and I will get a hard brick. Anyway, assuming I got over this fear, I have a couple of questions:
1. Does flashing with ODIN delete the user data?
2. Assuming I want to delete my data (like factory reset) - what options should I choose in ODIN when I flash?
3. Are there any options not including ODIN, KIES or the computer in general?
I was able to install the first of the two updates earlier for the 5.1.1 update on my Verizon Galaxy Note Pro 12.2. The second downloads, prompts for install, reboots and begins installing but errors out and reboots back into the OS home screen. The Verizon software update manager shows Failed software update error code 402. I have factory reset my tablet a couple of times and still same issue. I do not have my tablet rooted and no apps disabled.
I downloaded the latest available Samsung firmware md5 file, version VZW-P905VVRUANK1-20141205133604 and tried flashing using Odin 3.07 while in download mode. It starts and after a few seconds, Odin fails and on the tablet screen, I get the error, SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1. I have re-downloaded the firmware along with older versions and still same issue.
I was reading somewhere that my tablet could be "soft bricked" and that is why it will not install the second part of the OTA. As for the Odin/download mode error, I had read that the firmware version I am trying to flash in Odin has an older version of bootloader than my current and Samsung does not let you downgrade the bootloader. I may be wrong on both accounts, which is why I am seeing if anyone else has had this same issue or have any advice on what I can try.
Thanks in advance!
Same here. I unforze all the apps unintstalled SU and factory reset still no dice. VZW repair assistant wont work or smart switch. RA says device firmware not supported and smart switch says im up to date. The first part of the update installed no problem.
dansto82 said:
Same here. I unforze all the apps unintstalled SU and factory reset still no dice. VZW repair assistant wont work or smart switch. RA says device firmware not supported and smart switch says im up to date. The first part of the update installed no problem.
Click to expand...
Click to collapse
I had the exact same issues. Here's what I did with my 4.4.2 Rooted NP. I wiped it completely from within the device, then connected it and to the VZW software and let it do a "Repair". After that, my tablet also said that it was up to date, still on 4.4.2. I let it sit overnight and tried downloading the software update the next morning from the tablet, and it took both of them. My NP is rocking 5.1.1. now, much faster. No root but that's alright for now. By running the repair assistant from VZW, it also got rid of the Unlocked Symbol, which may have prevented the upgrade in the first place.
tdetroit said:
I had the exact same issues. Here's what I did with my 4.4.2 Rooted NP. I wiped it completely from within the device, then connected it and to the VZW software and let it do a "Repair". After that, my tablet also said that it was up to date, still on 4.4.2. I let it sit overnight and tried downloading the software update the next morning from the tablet, and it took both of them. My NP is rocking 5.1.1. now, much faster. No root but that's alright for now. By running the repair assistant from VZW, it also got rid of the Unlocked Symbol, which may have prevented the upgrade in the first place.
Click to expand...
Click to collapse
I was able to get mine to update using ODIN and the firmware file from sammoble. Factory reset on the tablet, factory reset in recovery and finally ODIN worked.
I was having the same problems as the OP listed. Once I decided to live without root and I would be okay with wiping the tablet, I performed exactly what dansto82 said he did and I'm now on 5.1.1.
Now hoping someone comes up with a way to root.
Hey, I have the p905v and it is running 4.4.4, I rooted it with towelroot and it was completely fine. I then tried putting twrp recovery on it the wrong way through flashify and now I don't have a recovery mode and can't update it to 5.1.1. Other than that the tablet runs perfectly fine. Is there a way I can fix it?
Sent from my SM-P905V using XDA Free mobile app