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.
Related
Hey guys,
Like many T-Mobile G2x users i got seriously fed up with the poor gps K on the phone. When i first got my phone, after i rooted it I tried many of the roms here on the development forum but none of them could fix the gps locking issue. IN the past few days, the phone could not even "view" satellites at all. I was running the JUL 2011 baseband at the time. However after digging around, I went ahead and updated from the LG website with their update software. now my current baseband is M6600A-SCAUTNZ-2.0.9720T 1 [MAR 11 2012 10:00:00] MP:TRULGE_08.09.02R-MDM and gps functionality comletely came back. I have a lock under 1 min, the phone still works for calls/text, and data still works.
I ran this process on a computer with Windows 7 Ultimate 64-bit. After the LG update completes it will revert the phone to stock recovery.
Here is a step by step of what I did. Please read everything first before doing the steps.
1. Use TGA_Gunman's guide to restoring a stock Nandroid OS that is unrooted. http://forum.xda-developers.com/showthread.php?t=1048274
A Stock ROM (v21e, v10f, or possibly others) is required for the "LG MOBILE SUPPORT TOOL" to work. Either from a personal backup or downloaded. Recovery version doesn't matter, but suggested to have latest CWM to make Nandroid backups & restores easier.
2. (optional) After you boot into the system link your google accounts, just as you would when opening a phone for the first time.
3.Visit LG's Website and download the T-Mobile LG G2x software update tool.
http://www.lg.com/us/support-mobile/lg-P999 (click on the software update tab and follow the 4 steps)
4.After installing LG Update software on your computer, run it, and follow the steps it tells you exactly.
5.Have PATIENCE! This will take around 15 min. and patience is the key. Let it sit there and do it's thing. Make sure your computer doesn't turn off or go into standby during the process and don't disconnect your USB cable until the installer is at its last step and its tells you it's done with the update.
6. Enjoy your functional gps!
P.S.: Thanks to everyone for the helpful feedback and tips to making this guide better!
If you are looking to downgrade your baseband or have unknown baseband error check out xBkKx's guide http://forum.xda-developers.com/showthread.php?t=1680292
EDIT 06/2/2012:
The CM7 RC3 update has been verified that it will work with the new March 2012 baseband. If you wish to update to the rc3, apply a "dirty flash" of the 27th nightly update after it (this resolves the gps locking time back to a couple of seconds again).
CM7 RC3 Update link : http://download.cyanogenmod.com/get...t/archive/update-cm-7.2.0-RC3-p999-signed.zip
CM7 27th Nightly Build: http://download.cyanogenmod.com/get/jenkins/1991/update-cm-7-20120527-NIGHTLY-p999-signed.zip
Why wouldn't you have calling/data after updating only calling issue is people not wanting to stay stock with this baseband.
You don't have to be on that nandroid or link your Google account prior to the update.. I restored my rooted stock nandroid downloaded drivers, installed lg tool and it updated fine as I just walked away and came back to it sitting in home screen with new baseband
Sent from my LG-P999
xBkKx said:
Why wouldn't you have calling/data after updating only calling issue is people not wanting to stay stock with this baseband.
Isn't there already guides to update the phone?
You don't need to be on that nandroid or link your account.. I restored my rooted stock nandroid downloaded drivers, installed lg tool and it updated fine as I just walked away and came back to it sitting in home screen with new baseband
Sent from my LG-P999
Click to expand...
Click to collapse
When i said calling/data still works i was referring to what some other people in the forums had said that they couldn't get a signal after updating baseband. I, however, did not find anything about using LGs update tool on windows 7. All the topics that came up were about procedures on doing it with windows xp only.
If this way works with the other nandroid versions that thats great news . However, when i was on the July 2011 baseband and I loaded one of the other stock nandroid versions the earpiece and microphone were not working at all. I could place/receive calls but the other person could not hear me nor could i hear them. when I loaded the v10f stock this problem did not come up, so just to be safe I recommend using that one.
Also you said there's calling issues for people that want to use other roms with this baseband? Does that mean I can't load up one of the recent EB ICs roms, etc with this baseband version?
call audio doesnt work with newest baseband and modded roms (tother than kwes's and buru's, both of which are based on V21Y). it just clicks and pops unless you are on wifi calling. basically devs need to start basing their ENTIRE rom on this baseband if they want call audio to work.
BuddhaTeh1337 said:
call audio doesnt work with newest baseband and modded roms (tother than kwes's and buru's, both of which are based on V21Y). it just clicks and pops unless you are on wifi calling. basically devs need to start basing their ENTIRE rom on this baseband if they want call audio to work.
Click to expand...
Click to collapse
actually now the 27th CM nightly update and the CM7 rc3 update have fixed the in call audio problem. im running this update with the new baseband on my phone and everything is working fine. the only thing that doesnt work yet are the old ROMs .hopefully devs do something about that
I also updated from rooted stock (xboarders 2.3.3). I didn't go back to stock recovery. I just ran the LG updater (already had drivers installed), plugged in the phone, hit the update button, and let it do it's thing. It took about 20 minutes
I'm confused about all of the confusion.
XDA Mobile
Hi all,
I did the above procedure, and did the restore from the "LG-P999-V10f" image.
On reboot, the phone comes up and shows the stock "LG" boot up screen.
The scrolly thing goes across for a bit, and then *stops*!
At this point, it is locked up, it won't boot any further up, and when I attempt to use the LG Updater tool, it does see the phone, and says "Phone connected", but the 2nd part of it when checking the phone communication, it fails with "Problem with communication between the cell phone and PC".
So I am stuck...
(Hopefully not bricked?)
Any thoughts? Suggestions?
Thanks!
Scott
I figured it out, after some minor panic!
The problem was, my ClockWork Mod Recovery bootloader version on the phone was too old!
I used a factory ROM image that was taken from a newer version, and it included some (.tar's I think) file types that weren't supported on the old version of the Recovery.
Thus, I burned an incomplete version of the stock firmware to the phone!!!
(Which is why it was stuck at boot!)
I was able to "One Touch Recovery" with a newer version of Clockwork Mod, slap my Backup of my CM in place, and get back to where I started.
And as part of the "One Touch Recovery", it updated my boot loader to a newer version, and so now the loading of the factory ROM image worked.
I then just ran the LG Updater software after going back to the factory ROM Image, and indeed, it finally works as expected!
Scott
Glad to hear that it worked Scott! And thanks for the feedback, i have updated step 1 to say you need latest version of clockwork recovery
It looks like LG may have taken the update file down, or for whatever other reason, the software update tab is blank. Could someone put up a link to the update file?
@sigmabeta: I noticed during a particularly slow page refresh that the links for the usb driver showed up briefly as the page loaded, then disappeared. I managed to stop the page from loading completely and got the 4 steps listed (under manuals, of all places) one of the links was the update tool, here is the link:
h-t-t-p://csmg[dot]lgmobile[dot]com:9002/clientapp/B2CAppSetup.exe
I downloaded it successfully from there. Enjoy!
(sorry I'm new and it won't let me post links yet)
LG update tool won't update
I managed to download it from LGs site, but despite flashing the v10f rom onto my phone, the update tool says software version is 11f (even tho the phone info shows 10f) and that it is up to date, and won't let me perform the update. Baseband is still Jun 2011. Any ideas, or a link to the version of the setup tool you used?
aft3rgl0w said:
I managed to download it from LGs site, but despite flashing the v10f rom onto my phone, the update tool says software version is 11f (even tho the phone info shows 10f) and that it is up to date, and won't let me perform the update. Baseband is still Jun 2011. Any ideas, or a link to the version of the setup tool you used?
Click to expand...
Click to collapse
hmm. im not sure about this one. try this: reboot into clockwork recovery mod and do factory reset . after clear your cache, then clear your dalvik cache. then install the v10f from the restore menu in clockwork mod . after restart, set up your phone as you would do for first time (link google account to it) and then plug it in to your computer and run the LG update tool. thats what i did and it worked for me
also you said version v11f? you must have not flashed the restore correctly. do the above.
The first time I flashed it, I followed the instructions, which said to factory reset AFTER the flash, but I did think of what you suggested and tried it again, factory resetting, clearing cache and dalvik twice before restoring, but the tool is still saying the SW version is 11f. If I go to Customer Support -> Update history, it shows SW v21e (even after reading phone info). Phone info SW ver says LG-P999-V10f. Weird. Should I factory reset/cache/dalvik _after_ flashing the v10f rom as well? i'll re-download it again and try in the morning. what version of the LG updater tool do you have? mine is v1.5.7.0. many thanks for your help.
aft3rgl0w said:
The first time I flashed it, I followed the instructions, which said to factory reset AFTER the flash, but I did think of what you suggested and tried it again, factory resetting, clearing cache and dalvik twice before restoring, but the tool is still saying the SW version is 11f. If I go to Customer Support -> Update history, it shows SW v21e (even after reading phone info). Weird. Should I factory reset/cache/dalvik _after_ flashing the v10f rom as well? i'll redownload it again and try in the morning. what version of te LG updater tool do you have? mine is v1.5.7.0. many thanks for your help.
Click to expand...
Click to collapse
yes. you should do a complete factory reset even after installing the v10f rom. this is detailed on the original post on how to flash back to stock rom in TGA_Gunmans post.
I just noticed too that it reverted back to froyo (v2.2.2) and not GB, could this be part of the problem? should the stock be 2.3?
just to clarify your last reply re factory reset after v10f flash - should i clear dalvik as well?
yes it should revert back to froyo. and yes reset the dalvik cache too
Have you tried the V21E? I just flashed back to my Jul baseband and restored my 2.3.3/V21E nandroid and the updater found the 2.3.4 release instantly for my phone
Sent from my LG-P999
xBkKx said:
Have you tried the V21E? I just flashed back to my Jul baseband and restored my 2.3.3/V21E nandroid and the updater found the 2.3.4 release instantly for my
Sent from my LG-P999
Click to expand...
Click to collapse
yes you could try the 21e. however for me, that version always failed to download from the website gunman uses to host those files so i used the v10f inatead. much faster download.
btw how do you revert back to a previous baseband?
I just Googled how to do it using like 6 different guides :/ I edited my thread on iso help on it with what worked for me if you want to try it: http://forum.xda-developers.com/showthread.php?t=1680292
V21E/2.3.3 Mirrors, just restore it, connect phone to computer, run updater, should go smoothly :
Dropbox
MediaFire
RapidShare
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?
Hey guys, I just got a T-Mobile SGH-T869 and it came with Honeycomb on it.
I've been able to root it (which was as dumb as flashing a ZIP on the stock recovery), and I've flashed the CWM 5 I found (here). However, I'm unable to flash CM10 from that, so I'm looking to figure out what's wrong or the missing step.
Any suggestions?
Just to follow up on my own issue, I figured it'd be a good idea to update my SGH-T869 to ICS, because HoneyComb is kinda terrible.
For this device, at least for now, the "official" ICS update isn't being made available over the air, only available via the Samsung Kies program.
Its totally free and you can get it for Mac or Windows here http://www.samsung.com/us/kies/
The procedure to update was seriously as dumb as "Install Kies, then plug in your device".
Kies should auto-detect and in the case of my SGH-T869, it immediately offered to update the firmware. However, Kies requires your battery to be charged up before it'll let you proceed, so initially it didn't allow me to flash (my battery was down to around 43%).
After updating this way, everything was back to stock and I had no root anymore.
I re-obtained root by downloading the two attached files. The attached CWM is a "temporary" touch-enabled version. Flashing it from the stock recovery boots you into CWM but after you reboot, its gone. I booted to that and then flashed the attached root.zip, which re-established root on my tablet.
So, sort of progress. Next step: figure out how to get CM10 on this bad boy, since the stock ICS kinda blows
I am on stock 4.1.2, VRBMB1. I am rooted, unlocked and with TWRP recovery. I have used Titanium to freeze SDM 1.0.
I am considering going to VRBMF1. I don't know how to safely get there. I also don't know what improvements might come with the OTA to MF1. Should I just hang out with VRBMB1 until the rumored update to 4.3 arrives? I would like to be in the position to return to what I have now (just in case), or be able to move to 4.3 if, and when, it come out. How do I proceed? Thanks
I have the same question... subscribed!
Is there a rooted/unlocked update file, or do I just run the VZ update and use Voodoo rootkeeper to restore root (or Casual unlock again, if needed)? Or dirty-flash one of the rooted/unlocked stock ROMs (and then the firmwares)?
So many ways to get there, just looking for the safest... I figure the VZ update might be best.
So, I finally bit the bullet. I backed up all kinds of things before running, but it seems I didn't need to. I unfroze SDM, and then checked for updates. It downloaded and then rebooted to install. Since CWM was installed, it tried to perform the update, gave a few errors, but I let it go anyway. After the main install was done, CWM asked me if I want to let the updater install a new (stock) recovery - I said no. Then it said that I may have lost root, so do I want CWM to fix it - I said yes. Then I cleared the cache (just in case) and rebooted. The phone booted up, said it completed the upgrade, and then dropped me back into the rooted OS. Pretty cool.
SDM did complain to say that the updated "didn't happen" but the phone shows the new MF1 version, and a few new apps as well. So, obviously, the update happened... and I didn't lose root or recovery. Damn nice...
I wonder if TWRP does the same things (disable the stock recovery and restoring root)...?
EDIT: Reading the TWRP page says that they don't support nor recommend applying a stock ROM update.
Secondly, I found that while my phone was working fine, when I tried to get into recovery, it popped up the unauthorized software error. Meh. I used the Casual rooting tool to reroot, apply the insecure aboot, and then reapply CWM... and I'm back to normal now. Not a big deal, but still more steps than I thought I needed above!
First; I hate to be a double poster, but I'm on the back page of How to Upgrade to 5.0.1 and Keep Root. My apologies. I've spent several days trying to solve this and have no answers.
I did the 5.0.1 "Keep Root" when it first came out, but it acted buggy and unpredictable. I just got a Note 4, and hate that I can't root it, so I decided to try to resolve the problems with my S4. I re-did the process, as stated and it seemed to work fine. I downgraded, rooted, and upgraded to 5.0.1. Then the trouble started. I installed the "Stock" Kernel, Modem, and Recovery. When I rebooted; it gave me a nasty message like: "AT&T has discovered unauthorized software on your phone." and froze up. I booted back into download mode, re-flashed the NB1 file, and it seemed to work, except for no Wi-Fi. When I tried to re-flash the OC4 with Flashfire, it acted like it was going to do it, but only booted into the recovery screen. I've tried close to a hundred different combinations, but no joy.
It allows me to root the NB1 and install Flashfire, but cant get it above 4.3. I installed a terminal emulator APK file and checked my bootloader status and it shows OC4. If my understanding is correct; I'm screwed. Is there any way to get past this and upgrade to ANY working ROM that will allow Wi-Fi and be fairly stable?
BTW; I'm on AT&T.
Thanks in advance!
As far as I'm concerned, ODIN just puts back your phone to its original state. Have you tried following the guide on how to install a custom Lollipop ROM? You gotta flash a rootable NB1 firmware and then continue with the process explained in the thread.
Here, take a look and tell me how it goes http://forum.xda-developers.com/galaxy-s4-att/general/how-to-installed-custom-lollipop-rom-t3135396
Crash and Burn
Crash and burn. NB1 wouldn't think of loading with Odin. Fails almost immediately.
Thanks for the help, though. Any other ideas?
Here's a screenshot of my phone parameters.
http://dl-1.va.us.xda-developers.co....png?key=Hy1bNEcEPo2F55Cm_pjqYg&ts=1450058617
Guess it won't upload my photo...