Hi all,
I tried to unroot using odin. Everything went fine, the phone appears to be working correctly, no issues so far.
I wanted to get the phone unlocked for a trip to Euroope. Well when I called, Tmobile said they still couldn't locate the phone, and that I still have an unofficial build.
I'm on build IML74K.UVLE1.
Kernel is [email protected] #1 SMP preempt Sun May 6 15:07:07 KST 2012
baseband version is T989UVLE1
Running Android 4.0.3
On the down side, when I try to update in the systems menu, it says there is no firmware, so not sure if that has anything to do with it.
Worse comes to worst, I'll just reroot and just work over wifi over there, but I'd prefer to be able to unlock the damn thing first.
Any thoughts here?
______________
Ok, so I went back and using odin I flashed the gingerbread tar.md5 file found in KK's thread here: http://forum.xda-developers.com/showthread.php?t=1513359&highlight=reset
That worked like a charm. Although, as an aside, I found that the enter button in the gingerbreak stock recovery is actually the home button, not the lock button. That threw me for a fright for about fifteen seconds, until I figured it out.
Anyway, all is good to go now. I'm waiting on the unlock code in my email right now.
erdingerchamp66 said:
Hi all,
I tried to unroot using odin. Everything went fine, the phone appears to be working correctly, no issues so far.
I wanted to get the phone unlocked for a trip to Euroope. Well when I called, Tmobile said they still couldn't locate the phone, and that I still have an unofficial build.
I'm on build IML74K.UVLE1.
Kernel is [email protected] #1 SMP preempt Sun May 6 15:07:07 KST 2012
baseband version is T989UVLE1
Running Android 4.0.3
On the down side, when I try to update in the systems menu, it says there is no firmware, so not sure if that has anything to do with it.
Worse comes to worst, I'll just reroot and just work over wifi over there, but I'd prefer to be able to unlock the damn thing first.
Any thoughts here?
Click to expand...
Click to collapse
first of all, why are they even asking you about your firmware for an unlock code? That doesn't play a part in any way, shape or form...
second, I would redownload the tar/md5 for stock ics and try to reflash it initially, but in reality it shouldn't make a difference if you were on 1.5 or 4.1 the unlock code is based on your imei (for them). Just my thoughts though
Related
So, I purchased two identical unlocked gsm nexus phones on separate occasions. The problem is, on my first one, I have upgraded to the latest 4.04 build (IMM76L) which was like 708kb...but the second...it will not complete that update. I constantly get the little android guy on his back with the red exclamation point. It will not finish the install. The phones bootloader was unlocked because I flashed to yakju back when I got it...but again, one phone works and updated fine but the second didn't. Maybe something else was already updated or something...but here are the other pieces of relevant info:
Phone 1 which updated correctly:
Baseband: I9250XXLA2
Kernel: 3.0.8-gda6252b
Build: IMM76L
Phone 2 which DIDN'T update:
Baseband: I9250XXKK6
Kernel: 3.0.8-g034fec9
Build: IMM76D
I guess my main question is how do I get Phone 2 updated successfully...the phone keeps telling me the update is available, yet it never completes, so I am constantly getting the pop up which is really annoying.
Any help would be much appreciated.
Flash the 4.0.4 IMM76I directly.
https://developers.google.com/android/nexus/images
dbdynsty25 said:
So, I purchased two identical unlocked gsm nexus phones on separate occasions. The problem is, on my first one, I have upgraded to the latest 4.04 build (IMM76L) which was like 708kb...but the second...it will not complete that update. I constantly get the little android guy on his back with the red exclamation point. It will not finish the install. The phones bootloader was unlocked because I flashed to yakju back when I got it...but again, one phone works and updated fine but the second didn't. Maybe something else was already updated or something...but here are the other pieces of relevant info:
Phone 1 which updated correctly:
Baseband: I9250XXLA2
Kernel: 3.0.8-gda6252b
Build: IMM76L
Phone 2 which DIDN'T update:
Baseband: I9250XXKK6
Kernel: 3.0.8-g034fec9
Build: IMM76D
I guess my main question is how do I get Phone 2 updated successfully...the phone keeps telling me the update is available, yet it never completes, so I am constantly getting the pop up which is really annoying.
Any help would be much appreciated.
Click to expand...
Click to collapse
is the recovery still stock on that one or did you install a different one when you flashed it? i'm thinking this was flashed with a toolkit and some would put a different recovery so it won't update as the update looks for a complete stock image.
dbdynsty25 said:
[snip]
I guess my main question is how do I get Phone 2 updated successfully...the phone keeps telling me the update is available, yet it never completes, so I am constantly getting the pop up which is really annoying.
Any help would be much appreciated.
Click to expand...
Click to collapse
Since your device has no data to lose, just flash the full IMM76I build by following the instructions here.
Hi
My daughter has a desire z and it is playing up on her:
Randomly rebooting
Year and date of phone changes randomly
I am thinking that I could just wipe the phone and reload the stock rom on and it may fix it (maybe just my winxp memories kicking in)
Im not too sure how to go about it though.
If I am loading a stock rom on it, do I need to root it?
Whats the easiest way to wipe the phone and relaod the rom?
Also, where would I get the rom from?
The phones details ATM:
Android Version: 2.2.1
Baseband Version: 12.28h.60.140fu_26.06.02.27_M
Kernel version: 2.6.32.21-g132894e
[email protected] #1
Fri Jan 14 13:17:35 CST 2011
Build number: 1.85.861.3 CL331649 release-keys
Software number: 1.85.861.3
Hope this helps and thanks for any help I get.
Since it appears that its running stock already I think you can factory reset from bootloader. You might also be able to flash the stock image from the bootloader. Wait for more responses until you do anything
Sent from my Nexus 4 using xda app-developers app
Yes, you're on an old version.
2 options :
- rooting it and opening custom ROM choice
- updating via wifi with stock ROM (via Wifi in the system menu).
Kéno40;37693413
2 options :
- rooting it and opening custom ROM choice
- updating via wifi with stock ROM (via Wifi in the system menu).[/QUOTE said:
my daughter has actually just got herself an iphone so I am doing this phone up for my wife to use, as she has the same model but screen is cracked.
She fears change so I wanted to just put stock back on.
Is there an updated stock I can put on it?
I am not sure what is meant by "update from bootloader"?
Click to expand...
Click to collapse
You should be fine with stock, granted there are many superior custom ROMs based off stock but that's besides the point.
Simple fix is to do a factory reset in settings>privacy>factory reset, or something like that. Then being you are on froyo I would suggest doing an ota update, simple way is to go to settings>about pone>check for update.
Or from dialer type *#*#CHECKIN#*#*
Sent from my Nexus 7 using xda premium
Mungrel said:
I am not sure what is meant by "update from bootloader"?
Click to expand...
Click to collapse
We all tell the same.
1srt : erase data : From bootloader or from Menu ("reset factory " or something like that).
2nd : after booting again, update by wifi.
You must know that some data may certainly be lost (SMS, apps...)
Thanks for all your help.
I have done the factory reset and then upgraded via "check for update"
The phone is working fine and the missus is happy with it so I am not going to touch it anymore
Cheers
Had 4.1.1 rooted with CWM. Phone downloaded a 600MB update file. Got some sort of error part way through. Flashed stock recovery back. Let phone download OTA update. Stopped half way through the flash and aborted. No error, rebooted before I could see one - just said that it was interrupted or something after rebooting. Go to check for updates and it says the phone is up to date, however about shows 4.1.1! Kernel though is showing SMP Preempt Nov 20 date so that's go to be something new.
I noticed on Kies it says 4.1.1 is the latest version! I know 4.3 had a lot of bugs initially. Is AT&T still chickening out on this for now and all the msgs I see about 4.3 OTA update are before AT&T stopped it? Or somet issue with my phone.
I'm about to just do back to CWM, move to CM11 nightly and roll the dice on having to deal with bugs and other funky stuff. But then stability is my #1 priority so maybe just stay on 4.1.1. Can't be right as I thought there was a 4.1.2 even?? (I had the update app frozen via TI so I never bothered with the OTA updates.)
*** shoots straight into your head ***
Dead, yet ?
There's a flashable zip of the official 4.3 update in the development thread. I would recommend the no knox prerooted version though because the other version is apparently "unrootable" right now.
jazee said:
Had 4.1.1 rooted with CWM. Phone downloaded a 600MB update file. Got some sort of error part way through. Flashed stock recovery back. Let phone download OTA update. Stopped half way through the flash and aborted. No error, rebooted before I could see one - just said that it was interrupted or something after rebooting. Go to check for updates and it says the phone is up to date, however about shows 4.1.1! Kernel though is showing SMP Preempt Nov 20 date so that's go to be something new.
I noticed on Kies it says 4.1.1 is the latest version! I know 4.3 had a lot of bugs initially. Is AT&T still chickening out on this for now and all the msgs I see about 4.3 OTA update are before AT&T stopped it? Or somet issue with my phone.
I'm about to just do back to CWM, move to CM11 nightly and roll the dice on having to deal with bugs and other funky stuff. But then stability is my #1 priority so maybe just stay on 4.1.1. Can't be right as I thought there was a 4.1.2 even?? (I had the update app frozen via TI so I never bothered with the OTA updates.)
Click to expand...
Click to collapse
jukiewalsh said:
There's a flashable zip of the official 4.3 update in the development thread. I would recommend the no knox prerooted version though because the other version is apparently "unrootable" right now.
Click to expand...
Click to collapse
Jazee, I read your posts on why you chose to try 4.3. I did what jukiewalsh recommends & have 4.3 as a stable DD.
This only works if your bootloader remains on 4.1.2 or less!
Posted some detail in these 2 posts:
http://forum.xda-developers.com/showthread.php?p=48303313#post48303313 #264
http://forum.xda-developers.com/showthread.php?p=48550720#post48550720 #875
jukiewalsh said:
There's a flashable zip of the official 4.3 update in the development thread. I would recommend the no knox prerooted version though because the other version is apparently "unrootable" right now.
Click to expand...
Click to collapse
I took a quick look and qasn't sure what thread you are referring to?
I'm guessing this one:
http://forum.xda-developers.com/showthread.php?t=2498233
But aside from having a pre-root pre-no knox version how does this one compare to this one?
http://forum.xda-developers.com/showthread.php?t=2387423
Are both of these buggy and that's why AT&T stopped pushing out the update?
jazee said:
I took a quick look and qasn't sure what thread you are referring to?
I'm guessing this one:
http://forum.xda-developers.com/showthread.php?t=2498233
But aside from having a pre-root pre-no knox version how does this one compare to this one?
http://forum.xda-developers.com/showthread.php?t=2387423
Are both of these buggy and that's why AT&T stopped pushing out the update?
Click to expand...
Click to collapse
I'm pretty sure that is the difference, that it's pre-rooted and insecure. As the second one's title says it's a "one way road". If you have any plans on rooting or installing a custom rom in the future I wouldn't do the second one because currently I think it's hard to root. The other one is essentially like flashing a custom rom so you can still switch between other ones or flash a kernel if you ever decide to. And I haven't tried the 4.3 TW yet so I can't attest to the bugginess
So, I'm trying to install a custom recovery to flash a new ROM on this stock, UCUFNJ1 phone, but I'm concerned I might approach it wrong. Could I get a hand, 'fellas?
I inherited the phone, and have had pretty good success with the I747 in the past, installing TWRP and CM 10.2 on a few phones in the past for friends and family (I usually default to that one since, in my experience, it's been most stable). I've heard that there's a high rate of bricking when trying to install a custom recovery on AT&T i747 devices running 4.3+ bootloaders, so I'm trying to play it safe, since I've never worked with one that had anything newer than 4.2.1 installed on it.
I can't seem to find anything definitive on rooting this phone for the UCUFNJ1, but a lot of people trying to update to that bootloader from NE4. Interestingly, this device was running UCUFNE4 (I decided to check because I had a feeling the folks weren't going to heed my warning, "NOT TO TOUCH IT BEFORE YOU GIVE IT TO ME.") But when I got it back, I discovered they must have reset it and some kind of OTA was applied when they were using it.
For the record, this device is unrooted, and is running stock TW, and has no custom recovery.
I'm going to document my approach with this, as well: from what I can see, the information on rooting/unlocking this particular model is pretty scarce, and a lot of the methods are very outdated. Since this is a newer bootloader, I have a sinking feeling it's uncharted territory.
Here's what I'm dealing with now:
Android Version: 4.4.2
Baseband version: I747UCUFNJ1
Kernel Version:
¶3.4.0-1514807
¶][email protected] #1
¶Wed Oct 1 21:09:24 KST 2014
Build Number: KOT49h.i747UCUFNJ1
SE for Android Status:
¶]Enforcing
¶SEPF_SAMSUNG-SGH-I747_4.4.2_0016
¶Wed Oct 01 21:09:13 2014
This is what the phone was running before they accepted the OTA:
Android Version: 4.4.2
Baseband version: I747UCUFNE4
Kernel Version:
¶3.4.0-1514807
¶[email protected] #1
¶Mon May 19 21:00:05 KST 2014
Build Number: KOT49H.i747UCUFNE4
SE for Android Status:
¶Enforcing
¶SEPF_SAMSUNG-SGH-I747_4.4.2_0016
¶Mon May 19 20:59:50 2014
I suggest flashing Philz Touch via Odin from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Make sure you download the tar.md5 file.
Copy a custom ROM to an SD card, boot into recovery, backup your existing ROM, wipe cache, Dalvik, data, system, and flash the custom ROM.
Is there any significant difference from using Philz versus TWRP or CWM? Can anybody report success with this configuration? I wouldn't want to brick this device, since if I do, it's back to my ancient Motorola Atrix 4G and I do not want that to happen, haha.
Additionally, will I have any trouble installing ROMs of earlier Android versions? For instance, I've had a good experience with CM 10.2 on all the GS3s I've installed it on, but since I'm running the UCUFNJ1 bootloader for 4.4.x devices, would I run the risk of bricking the phone by trying to install anything other than a Kitkat ROM? (If it just fails to install, I'm no stranger to that, I'm just trying to cover my bases here.)
Thanks.
I had issues with TWRP on my s3 and Note 3 so I switched to Philz.
Philz is actually based on CWM with a touch interface.
Older ROMs should work properly on updated bootloaders and modems. Newer ROMs may not be fully functional on older bootloaders and modems.
Feel free to wait for others to chime in. I understand your hesitation. I would not want a brick on my hands either
You do not need root to install a custom recovery and flash ROMs.
ok, chymeing in then. have had just opposite experience. lol. on mj2 had no problem flashing new roms. updated bootloader/modem to NE4 (KK), and get fail error older CM builds (cm10/10.2,etc.) but was taught by docholiday that on older roms you just edit the updater script to include the new bootloader version and bam! flashes just fine.
p.s. thanks for all your good advice/help audit13, would have drown many times without.:thumbup:
"all i can really do , is stay out of my own way and let the will of heaven be done"
Alright, I'm going to give this a go on Thursday or Friday, thanks for the help--
--I'll be sure to post the procedure and results.
hey all sorry for being a pain i still have my m919 still not unlocked i have disabled knox i have rooted the device tried towelroot rooted to chainfire root for the life of me i have a stubborn samsung lol i have gone into hidden menu via dialer and im not getting the flag on/off option i have ran out of ideas it is locked to t-mobile and where im living theres hardly any coverage . ive had an idea i dont know if it can be done but is it possable to totally wipe all software/firmware from the m919 and replace it with the sgh-i9500 software/firmware? i really need help and would appreciate any ideas please you can pm me or i have left my skype in my profile
many thanks
mad
Did you get the phone from T-Mobile? What firmware are you on?
firmware
serio22 said:
Did you get the phone from T-Mobile? What firmware are you on?
Click to expand...
Click to collapse
hi bud running 4.4.4 / baseband m919uvufnh7 /kernel 3.4.0 [email protected]#1 wed aug 27 21:44:08 kst 2014 /se for android status enforcing sepf_sgh-m919_4.4.4_0024 wed aug 27 21:43:58 2014 i got the phone second hand and was using myfamilymobile i also came to no signal today its gone from bad to worse my imei has dissapeared i done a check on the t-mobils site and the imei is clean i dont know where to go from here
many thanks for getting back to me
mad
Well you can't flash any other firmware. So try flashing NH7 firmware again to see if it fixes your imei. I think you can use an app called region lock away to try to unlock NH7, but not sure