Related
A few months ago, I loaded 2.3.6 firmware on phone. It is stock gingerbread with root from oden file all_in_one_odin_ep4d. Last week I received an OTA update. The update fails to load and leaves me at the screen with the white triangle with yellow exclamation point. I pulled the battery and rebooted. Today, the update came back. Still no go. I think the update is incompatible with the software on the phone.
Can someone tell me:
1. What is in the update? Is it going to remove root and allow Verizon to see that I 3rd party tether? Are they suddenly going to slap a tether package on my bill? Is it even worth installing?
2. If it’s not worth installing, can I tell my phone that I don’t want it by making it think that the update is already installed?
3. If the update is worth installing, should I wait for an oden install that contains the update or do I do something to the phone to allow it to receive the OTA update? If I do opt for the OTA what must I do to allow it to load?
Being somewhat novice when it comes to loading software on phones, is there a good FAQ out there that lists all the different loads, with what they contain and explanations of those components. Right now, voodoo, Peanut butter and jelly… buzzwords.
beavermjr said:
A few months ago, I loaded 2.3.6 firmware on phone. It is stock gingerbread with root from oden file all_in_one_odin_ep4d. Last week I received an OTA update. The update fails to load and leaves me at the screen with the white triangle with yellow exclamation point. I pulled the battery and rebooted. Today, the update came back. Still no go. I think the update is incompatible with the software on the phone.
Can someone tell me:
1. What is in the update? Is it going to remove root and allow Verizon to see that I 3rd party tether? Are they suddenly going to slap a tether package on my bill? Is it even worth installing?
2. If it’s not worth installing, can I tell my phone that I don’t want it by making it think that the update is already installed?
3. If the update is worth installing, should I wait for an oden install that contains the update or do I do something to the phone to allow it to receive the OTA update? If I do opt for the OTA what must I do to allow it to load?
Being somewhat novice when it comes to loading software on phones, is there a good FAQ out there that lists all the different loads, with what they contain and explanations of those components. Right now, voodoo, Peanut butter and jelly… buzzwords.
Click to expand...
Click to collapse
All in one package that you installed came with custom kernel. You need to flash a FP1 debloated/bloated/rooted rom and the FP1 kernel. Since you have the custom rom+kernel you can not use OTA update. Some people (like me) prefer to do it clean by go back to stock EP4d rom, then do the full update to FP1, then flash what ever custom rom out there, like Eclipse or debloated etc...More on how to do it here:
http://forum.xda-developers.com/showthread.php?t=1560117
Sooner or later you should be on the latest version any way specially for support from XDA.
Thanks for setting me straight. Let’s see if I understand your info.
1. I have a custom ROM and need to use the stock one to be able to get the update to install.
2. Once I install the stock ROM and get the update, I could reinstall the same custom ROM I have now.
3. Returning my phone to stock will remove root access so I can get the update
How do I get back to stock everything, update the phone and then add only root access. I don’t know enough about stock ROMs to know why I’d want or need one.
beavermjr said:
Thanks for setting me straight. Let’s see if I understand your info.
1. I have a custom ROM and need to use the stock one to be able to get the update to install.
2. Once I install the stock ROM and get the update, I could reinstall the same custom ROM I have now.
3. Returning my phone to stock will remove root access so I can get the update
How do I get back to stock everything, update the phone and then add only root access. I don’t know enough about stock ROMs to know why I’d want or need one.
Click to expand...
Click to collapse
1. Yes, you need EP4D stock rom to get OTA update.
2. Yes, once you on stock FP1, you can use flash eclipse 2.0 (which build from FP1 rom). Once done you will have FP1 eclipse with FP1 stock kernel.
3. If you have pure stock EP4D and rooted, you can take the OTA, but yours is not.
You have 2 Options to upgrade:
1. Flash back to pure stock EP4D, OTA upgrade to FP1 then flash pre-rooted FP1 eclipse 2.0 rom. Then flash cwm.
2. Flash FP1 pre-rooted eclipse 2.0 rom, flash cwm, flash FP1 kernel, flash FP1 radio.
Hope this help, don't hesitate to ask if you have more questions.
Ok. That makes sense, sort of…
I’m going to give #1 a try since I found the stock EP4D load on the page you recommended. I will then be able to get the OTA update and have a stock phone with FP1.
I will then follow #5 on that page to root my pure stock FP1 and make CWM stick after reboot. Do you know if there is a free program that will let me change the file permissions of “install-recovery.sh” like root explorer?
beavermjr said:
Ok. That makes sense, sort of…
I’m going to give #1 a try since I found the stock EP4D load on the page you recommended. I will then be able to get the OTA update and have a stock phone with FP1.
I will then follow #5 on that page to root my pure stock FP1 and make CWM stick after reboot. Do you know if there is a free program that will let me change the file permissions of “install-recovery.sh” like root explorer?
Click to expand...
Click to collapse
root browser lite or ES file explorer. Both you can get from the Market (google play).
Thanks for the help. I got the phone updated successfully. I ended up having to load eclipse ROM on the phone after the OTA update as the other method with superuser update and superuser fixer failed to deliver root access.
couple of questions:
1. I can no longer set multi-screen wallpaper. How do I restore this functionality?
2. I can't answer my phone using the puzzle pieces. what am I missing?
Mike
PS thanks again for all the help. Sometimes I just need a push in the right direction.
Now that i've had a chance to play with the phone... The market keeps crashing. Anyone know what to do?
Sent from my SCH-I510 using XDA
FIX: settings/applications/market/clear data Reboot
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?
I'm using the default ROM for my One X and I'd like to update it (I haven't since I got it 6 month ago); do I need to re-lock the bootloader and unroot it before I can use the OTA update? Also it's been a while since I even fiddled with my phones software so I forgot anything else I may have done, is there a way I can check to see what else has been done and if it's safe to update it?
Currently I have:
Android Version: 4.0.3
HTC Sense Version: 4.0
Software Number: 1.73.631.1
HTC SDK API Level: 4.11
HTC Extension Version: HTCExtension_403_1_HA_4
What firmware are u on currently for starters
Sent from my HTC One XL using xda app-developers app
I added the info to the original post
bman3k said:
do I need to re-lock the bootloader and unroot it before I can use the OTA update?
Click to expand...
Click to collapse
Your phone should be factory default before performing OTA updates or results may be unexpected.
Most OTA updates are patch file based and require the files to be exactly what is expected.
There have been known issues with root being detected and the OTA failing.
Rooted phones progressing with an update but root lost after the update.
System files being modified and the OTA failing.
Recovery must be factory; not TWRP or CWM.
CID and MID must suit OTA.
The only modification I would consider safe through all OTA's so far has been SuperCID.
If you have any interest in rooting and flashing custom ROMs, I would suggest rooting and unlocking the bootloader now, while you are on 1.73, and not updating via OTA. The latest 2.20 update will also update your hboot, which plugs the holes by which kernels and radios can be flashed from recovery.
Since you're with att you can expect the jelly bean update any time from now till the end of the world which isn't fun waiting for .. I'd suggest if you were rooted download goo manager flash twrp....than flash a solid ics Rom if your prefer ice sense or you can go venture into the jb realms
omario8484 said:
Since you're with att you can expect the jelly bean update any time from now till the end of the world which isn't fun waiting for .. I'd suggest if you were rooted download goo manager flash twrp....than flash a solid ics Rom if your prefer ice sense or you can go venture into the jb realms
Click to expand...
Click to collapse
Agree. If you are already BL unlocked and rooted, why go through the hassle of relocking the BL and returning to stock, just to wait for the OTA?
Just flash a JB ROM, as there are already stock and custom JB ROMs posted in Development.
Plus, until the OTA actually hits, we don't know if it will even be rootable. They have plugged the existing root exploits with every successive AT&T OTA for this phone so far. No reason to think any different for the JB update.
Just flash a JB ROM and stay rooted.
Ya I really like viper xl v3 . Just apply fix listed on op and you should be good to go
Sent from my HTC One XL using xda premium
Stock OTA is not WORTH IT IMO, been there
Reselling the phone is probably the only reason i'd revert to stock.
Ok, so I tried to flash Android Revolution HD 18.0 instead of going back to stock. I used TWRP, but it said "unable to read zip file" and the flash failed, now my phone won't start up it just shows the HTC screen with "this build is for development purposes..." and continuously turns on and off.
bman3k said:
Ok, so I tried to flash Android Revolution HD 18.0 instead of going back to stock. I used TWRP, but it said "unable to read zip file" and the flash failed, now my phone won't start up it just shows the HTC screen with "this build is for development purposes..." and continuously turns on and off.
Click to expand...
Click to collapse
Ok you're really lucky you didn't just brick your phone.... You want to stay in the att one x forums.... Notice theres a title diff. You're lucky it didn't succesfully flash or your phone would be dead... That's an international one x rom
bman3k said:
Ok, so I tried to flash Android Revolution HD 18.0 instead of going back to stock. I used TWRP, but it said "unable to read zip file" and the flash failed, now my phone won't start up it just shows the HTC screen with "this build is for development purposes..." and continuously turns on and off.
Click to expand...
Click to collapse
Stick to the ROM's in our forum, I never heard of anything like that ROM for our phone sorry. Lucky you didn't brick it
O damn I feel very stupid now...
Can someone recommend me a JB ROM?
Also how would I even install one now? The AR HD one was the only ROM I had on my SD card
Edit: I figured out the Mount function in TWRP, so I know how to add new ROMs now
bman3k said:
O damn I feel very stupid now...
Can someone recommend me a JB ROM? Also how would I even install one now? The AR HD one was the only ROM I had on my SD card
Click to expand...
Click to collapse
Try them all, they are all good, the time it takes to ask for other peoples opinions you could have test driven them all yourself.
Are you looking for jb sense?
omario8484 said:
Are you looking for jb sense?
Click to expand...
Click to collapse
I'm just going to try a couple like wrecker suggested now that I've figured out how to flash ROM's properly
Thanks for your guys' helps
Is there a way to back up my apps/texts and stuff when flashing ROM's? I totally forgot about that and lost all of it, I didn't have anything particularly important, but it'd be a hassle to redownload everything everytime. I had Titanium Backup, but that's not a recovery for if you reflash right?
bman3k said:
I'm just going to try a couple like wrecker suggested now that I've figured out how to flash ROM's properly
Thanks for your guys' helps
Is there a way to back up my apps/texts and stuff when flashing ROM's? I totally forgot about that and lost all of it, I didn't have anything particularly important, but it'd be a hassle to redownload everything everytime. I had Titanium Backup, but that's not a recovery for if you reflash right?
Click to expand...
Click to collapse
Funny that you bring titanium up...titanium helps you back up apps it also backs up your app data...and for sms just download something from the market here's one download the app super backup and you can backup your sms
So I installed Cyanogen 10.0.0 but it didn't come with Google Play so I installed Gapps as well; now I keep getting the "Android Keyboard ASOP has stopped working" and I can't do anything. I've tried multiple versions of Gapps but they all give the error. I've also tried installing a keyboard apk on it's own but I am still unable to type anything.
Edit: Also when I downloaded Google Play as an apk separately it would crash immediately, but when I installed it from Gapps it was ok.
bman3k said:
So I installed Cyanogen 10.0.0 but it didn't come with Google Play so I installed Gapps as well; now I keep getting the "Android Keyboard ASOP has stopped working" and I can't do anything. I've tried multiple versions of Gapps but they all give the error. I've also tried installing a keyboard apk on it's own but I am still unable to type anything.
Edit: Also when I downloaded Google Play as an apk separately it would crash immediately, but when I installed it from Gapps it was ok.
Click to expand...
Click to collapse
You did a full wipe before hand right?
I did the factory, system, cache and dalvik cache wipes
Edit: I got it to work, not really sure what I did different =/
Being my first smartphone, of course I wanted to fiddle with it, so the first thing I did want upgrade to ICS (Android 4.0.4, got the link from Samsung's site). All that rooting stuff kinda made me gun-shy, at first...but, after getting up the nerve, I got Odin, the pit and tar files, and fired for effect. However...during the process, I got some sort of device driver error from my laptop ("not successfully installed" or some such, which was rectified since), and after rooting attempt, my phone wouldn't get past the welcome screen. Did the unroot (many thanks to k0nane), and was back to stock...or so I thought. Baseband still shows T769UVMB1, which I was told by T-Mobile tech support was the latest update; "About Phone" shows Android 2.3.6, Kernel v.2.6.35.11, Gingerbread UVLB7. "Software Updates" show none available. I recall the Menu being different when I had 4.0.4, though, much better than what I have now. I tried the root process again, was successful, and DLed Superuser and Titanium Backup to get rid of a lot of clutter. Phone runs like a champ, and I love it, but there's always room for improvement. Oh, and the link that *was* on Samsung's site for the upgrade is now "Page Not Found".
So...am I running the latest software/OS/updates? If not, how can I get 4.0.4 back?
ElGorditoMagnifico said:
Being my first smartphone, of course I wanted to fiddle with it, so the first thing I did want upgrade to ICS (Android 4.0.4, got the link from Samsung's site). All that rooting stuff kinda made me gun-shy, at first...but, after getting up the nerve, I got Odin, the pit and tar files, and fired for effect. However...during the process, I got some sort of device driver error from my laptop ("not successfully installed" or some such, which was rectified since), and after rooting attempt, my phone wouldn't get past the welcome screen. Did the unroot (many thanks to k0nane), and was back to stock...or so I thought. Baseband still shows T769UVMB1, which I was told by T-Mobile tech support was the latest update; "About Phone" shows Android 2.3.6, Kernel v.2.6.35.11, Gingerbread UVLB7. "Software Updates" show none available. I recall the Menu being different when I had 4.0.4, though, much better than what I have now. I tried the root process again, was successful, and DLed Superuser and Titanium Backup to get rid of a lot of clutter. Phone runs like a champ, and I love it, but there's always room for improvement. Oh, and the link that *was* on Samsung's site for the upgrade is now "Page Not Found".
So...am I running the latest software/OS/updates? If not, how can I get 4.0.4 back?
Click to expand...
Click to collapse
Baseband T769UVMB1 is a radio, not the rom. Android 2.3.6 is Gingerbread, so no, it does not look like you are on ICS. Looks like you have Root. Do you have (if not you should get) Clockword Mod Recovery - once you have a recovery, you can do a complete Nandroid backup of your currently running rom; then you are free to try any of the custom roms and if there is a problem you can flash backwards to your old rom. So get a recovery and nandroid first, then flash away!
LBN1 said:
Baseband T769UVMB1 is a radio, not the rom. Android 2.3.6 is Gingerbread, so no, it does not look like you are on ICS. Looks like you have Root. Do you have (if not you should get) Clockword Mod Recovery - once you have a recovery, you can do a complete Nandroid backup of your currently running rom; then you are free to try any of the custom roms and if there is a problem you can flash backwards to your old rom. So get a recovery and nandroid first, then flash away!
Click to expand...
Click to collapse
Thanks, I'll bone up more on this stuff & see what happens.
Update: I installed Odin 3.07 and did a flash with *SGH-T769_TMB_T769UVLH5_T769TMBLH5_Original.zip*, but it failed to root. Did a reflash, the updates, and I'm back in business again. It's late; I'm going to bed...I'll work on rooting this later...
CWM Recovery weirded out
Well, I tried the 4.0.4 root (as per Beastmode's guide)...and when I downloaded the ClockWorkMod Recovery file, it showed up in WinZip as recovery.img & tried to open in Paint Shop Pro. PSP did *not* like it, and told me so, refusing to open, 'cuz it wasn't an image file. Weird.
Hi guys, a couple of months ago I've rooted my new S2+ and after Alex posted the new 4.2.2 I've flashed my device with RDS_GT-I9105P-XEO-I9105PXXAMC2 (topic here GT-I9105/I9105P Stock Prerooted Firmware Without loss of warranty(4.2.2) http://forum.xda-developers.com/showthread.php?t=2334103).
So far it is working perfect! This week I've received a notification, that there is a new update available OTA for my device, so I've decided to download and install it. I've downloaded it, the phone restarts and starts to install the "new update", but at 25% shows an error (the Android guy wearing the red triangle etc. and reboots automatically).
After the restart the OS boots normally and is working OK as previous.
My question is: Since my phone has a prerooted stock FW (4.2.2) and is rooted at the same time running CWM, why I can't install the latest updates OTA?
If CW is causing this, why am I able to get the OTA update notification?
Thanks for the replies.
boyansky78 said:
Hi guys, a couple of months ago I've rooted my new S2+ and after Alex posted the new 4.2.2 I've flashed my device with RDS_GT-I9105P-XEO-I9105PXXAMC2 (topic here GT-I9105/I9105P Stock Prerooted Firmware Without loss of warranty(4.2.2) http://forum.xda-developers.com/showthread.php?t=2334103).
So far it is working perfect! This week I've received a notification, that there is a new update available OTA for my device, so I've decided to download and install it. I've downloaded it, the phone restarts and starts to install the "new update", but at 25% shows an error (the Android guy wearing the red triangle etc. and reboots automatically).
After the restart the OS boots normally and is working OK as previous.
My question is: Since my phone has a prerooted stock FW (4.2.2) and is rooted at the same time running CWM, why I can't install the latest updates OTA?
If CW is causing this, why am I able to get the OTA update notification?
Thanks for the replies.
Click to expand...
Click to collapse
that is because it is a modded firmware
safariking said:
that is because it is a modded firmware
Click to expand...
Click to collapse
I understand that the FW is modded, as the previous one (4.1.2), which I've downloaded from here and installed on my G2+. But with 4.1.2 at that time I wasn't able to check for any updates for my OS. Every time I've checked manually for updates, the OS gave me error message, that this is not possible. And now with 4.2.2 I am not only able to check if my FW is the latest, but also to download and install 1/4 of the updates. I am trying to find the algorithm here.
boyansky78 said:
I understand that the FW is modded, as the previous one (4.1.2), which I've downloaded from here and installed on my G2+. But with 4.1.2 at that time I wasn't able to check for any updates for my OS. Every time I've checked manually for updates, the OS gave me error message, that this is not possible. And now with 4.2.2 I am not only able to check if my FW is the latest, but also to download and install 1/4 of the updates. I am trying to find the algorithm here.
Click to expand...
Click to collapse
I will say it again
It is not possible to check for updates because the Firmware is modded and not original anymore that's why!!!
Hi "safariking",
In the current situation we have two identically modded FWs, but a different outcome.
It's very nice of you to take the time to answer my question so fully That's why I'd like to thank you for the effort. Herewith I am closing the topic.
Cheers.
No probs guy i will repeat myself 100 times no problem
Verstuurd van mijn GT-I9105P
safariking said:
No probs guy i will repeat myself 100 times no problem
Verstuurd van mijn GT-I9105P
Click to expand...
Click to collapse
chill down everyone safari bro,this guy trying to say he got updated with mod fw,just when reach certain percent,the downloaded file seems corrupted. Now i understand mod fw can't even received the ota file,but how this process is allowed, and what happened with the ota file he downloaded?
either way,it's pointless,1st the phone fail to update completely(stuck at 25%), 2nd i don't think this problem can be solved.
cheers everyone~ :highfive:
nickchk said:
chill down everyone safari bro,this guy trying to say he got updated with mod fw,just when reach certain percent,the downloaded file seems corrupted. Now i understand mod fw can't even received the ota file,but how this process is allowed, and what happened with the ota file he downloaded?
either way,it's pointless,1st the phone fail to update completely(stuck at 25%), 2nd i don't think this problem can be solved.
cheers everyone~ :highfive:
Click to expand...
Click to collapse
Hi Nick,
Thanks for your reply. You are reading my mind. The issue is really interesting & I think it is worth discussing this.
Safari is right, when he says that FW upgrade OTA for customized ROM is not possible. This is of course true and no one has ever doubted it. This is why when I had the 4.1.2 installed on my G2+ no update was even possible. Droid detects immediately, that the OS has been modified and that you are not running stock ROM.
Okay, so far so good.
Now I have pre-rooted 4.2.2 installed on my phone. When I hit the "Check for update button" it detects that my OS is genuine (although it is not), downloads the whole update package (see screenshot), restarts the phone (part of the update process) and starts installing the update. When the installation reaches 25%, an error message appears saying, that an error has occurred. The phone restarts and loads the "old" OS.
I have tested this a several times and it always hangs on 25%.
The question is NOT why I CAN'T install OTA updates on modified ROM. The question is why I CAN download and install OTA updates on modified ROM.
My suggestion is that:
ROM 1 (4.1.2) had a modified kernel. That's why the OTA updates were not possible.
ROM 2 (4.2.2) is pre-rooted. And I assume it is just stock FW (kernel not modified) with few modifications in the user permissions. This would explain the OTA update and why it reaches download mode and hangs on 25% of the installation.
I hope this brings more clarification to the situation and this would be useful to all members of the forum.
Cheers!:highfive:
I have randomly come across and read posts and topics on this in the other devices' forum.
If I remember correctly, it is the custom recovery, i.e Cwm or twrp that blocks or interrupts the OTA process. 2 reasons why: you'll lose root access if the update went through. Secondly, if a user freezes or uninstalls stock apps like S Voice, Chat On etc, there will be trouble.
There are some ways of allowing an OTA to get pass a custom recovery. I think TWRP has this feature. Again, I stand corrected here lol.
Heard of OTA Root Keeper but no idea how it works
Sent from my GT-I9105 using xda app-developers app