Develop Bugs

Unrooted but not stock build? [Solution Found]

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

[Q] Galaxy S3 Unknown ROM

Hi everyone, new android user here! I'll try to make this as brief as possible:
Recently purchased a used Unlocked Galaxy S3.
Currently using Bell Carrier on it and it works fine.
I noticed that even after restoring SuperSU was installed.
Checked download mode -> odin installed with custom binary
Checked to see if the phone has root access -> it does not
I wanted to try and flash it with a official ROM to completely restore factory settings but I don't know what the original carrier is so I don't know what ROM to download. I called a couple carriers but they have no record of the IMEI.
I'm fairly new to android and my past two days of google searching hasn't accomplished anything relative to my problem (although I know a lot more about the rooting community!) so I thought I'd ask here.
Is there any way to know what's going on here?
Can I restore the phone to factory firmware/ROM/etc.?
Here is some phone information:
Model: SGH-I747M
Android Version: 4.1.1
Baseband: I747MVLDLK4
Kernel: 3.0.31-538866
Build Number: JRO03L.I747MVLDLK4
Any help would be greatly appreciated!

Just go and download this program http://www.samsung.com/ca/support/usefulsoftware/KIES/JSP
Go to Tools > Firmware Install and Initialization
It will ask you for your model number and Serial number. It will use those to determine what stock ROM is correct for your phone.
It will then flash you to stock, just as Odin would, including the stock recovery.

theXact said:
Hi everyone, new android user here! I'll try to make this as brief as possible:
Recently purchased a used Unlocked Galaxy S3.
Currently using Bell Carrier on it and it works fine.
I noticed that even after restoring SuperSU was installed.
Checked download mode -> odin installed with custom binary
Checked to see if the phone has root access -> it does not
I wanted to try and flash it with a official ROM to completely restore factory settings but I don't know what the original carrier is so I don't know what ROM to download. I called a couple carriers but they have no record of the IMEI.
I'm fairly new to android and my past two days of google searching hasn't accomplished anything relative to my problem (although I know a lot more about the rooting community!) so I thought I'd ask here.
Is there any way to know what's going on here?
Can I restore the phone to factory firmware/ROM/etc.?
Here is some phone information:
Model: SGH-I747M
Android Version: 4.1.1
Baseband: I747MVLDLK4
Kernel: 3.0.31-538866
Build Number: JRO03L.I747MVLDLK4
Any help would be greatly appreciated!
Click to expand...
Click to collapse
It definitely looks like you are on the stock Jelly Bean firmware from Samsung. I747M is the Canadian model (747 is ATT). Your build number also looks to be the stock 4.1.1 based on the DLK4 build number! Just as the last guy said, grab kies or use Odin to go back to complete stock if you are not happy with what you have now. If your phone is showing custom binary flashes and you want to get rid of that, give Triangle Away a try! Good luck. :good:

Lumixz said:
Just go and download this program *link removed since I'm a newbie*
Go to Tools > Firmware Install and Initialization
It will ask you for your model number and Serial number. It will use those to determine what stock ROM is correct for your phone.
It will then flash you to stock, just as Odin would, including the stock recovery.
Click to expand...
Click to collapse
Thank you! That worked like a charm! The device is now in a "normal" state and the binaries are "official".
BAM1789 said:
]It definitely looks like you are on the stock Jelly Bean firmware from Samsung. I747M is the Canadian model (747 is ATT). Your build number also looks to be the stock 4.1.1 based on the DLK4 build number! Just as the last guy said, grab kies or use Odin to go back to complete stock if you are not happy with what you have now. If your phone is showing custom binary flashes and you want to get rid of that, give Triangle Away a try! Good luck.
Click to expand...
Click to collapse
Thanks for the advice! I'm not too concerned about the flash count, that's only really important your warranty to to be valid, right? But I'll look into it, it may be worth it anyway.
Thanks again everyone!

[Q] Please help...Unrooting problem

Hi everyone, This is my first post and my first trouble
I have samsung galaxy nexus, Its made in korea (written at its back when we remove the battery), when i got this phone it was probably rooted because it was on 4.0.2 and software update was available to 4.1.1 but when the update completed and phone restarted, it suddenly shows me a red Exclamation mark and then nothing happens and i have to pull out the battery, i thought its because my phone is rooted. So, i searched on the internet about how to bring my nexus to stock factory rom, i found this thread to be helpful http://forum.xda-developers.com/showthread.php?t=1626895 , so i followed all the steps excluding the last step saying to re-lock the bootloader... and downloaded this factory image from google Factory Images "takju" for Galaxy Nexus "maguro" (GSM/HSPA+) (with Google Wallet) - Android 4.0.4 (IMM76I), first i tried with the 4.1.2 but it says exceed buffers or something during installation, thats why i tried 4.0.4 (IMM76l) and it was installed on my nexus. It works fine, but still i can't update to a newer version of android, when i got in settings > system updates it shows me the update of around 144mb of adnroid version 4.1 but when it finished downloading, i get the same error, android with a red exclamation mark, and i have to restart...help me please i am writing here with full details about my firmware
Model Number: Galaxy Nexus
Android Version: 4.0.4
Baseband Version: SCO4DOMLA1
Kernal version: 3.0.8 - gda6252b
android - [email protected] #1
SMP PREEMPT fri Apr 13 11:35:09 PDT 2012
Build Number: IMM76l
and when i go to fastboot mode, it shows this detail:
Product name: tuna
Variant: maguro
HW version: 9
Bootloader version: PRIMEKK15
Baseband version: SC04DOMLA1
Carrier info: None
Serial number: 01498F8C0300600D
Signing: production
Lock state: Unlocked
Tell me, how to install a stock firmware which can be updated easily, tell me step by step, so that i can understand and follow it easily...

really doesnt get any easier than straight from GOOGLE
https://developers.google.com/android/nexus/images

But, i am really confused, which image to install...i have tried few and they all failed when i try the first command in fastboot mode, it gives me error like exceed buffer size, please help me to choose which is the right update for me...

I believe that the relative error in fastboot is related to the fact that it was not flashed the correct bootloader present in the stock rom downloaded from Google ... following the efrant's guide, step by step, and the order of operations, should no longer give back the error and then allow properly flash the stock rom.

rameez.ahmed said:
Baseband Version: SCO4DOMLA1
Click to expand...
Click to collapse
This is not an international gsm device, so the factory images will not work I believe, since it requires another radio, and neither will the OTA update.
Sent from my Nexus

R: [Q] Please help...Unrooting problem
bk201doesntexist said:
This is not an international gsm device, so the factory images will not work I believe, since it requires another radio, and neither will the OTA update.
Sent from my Nexus
Click to expand...
Click to collapse
yes, in fact, the baseband radio seems to be used on the nexus ntt docomo ...
From Gnex with Tapatalk 2

Maxmaximus said:
yes, in fact, the baseband radio seems to be used on the nexus ntt docomo ...
From Gnex with Tapatalk 2
Click to expand...
Click to collapse
oh no, i am afraid that i wont be able to use jelly bean...yes, ntt docomo is written on its back cover, what does that mean, i got this cellphone from a boy who told me that its a japanese phone...what should i do, i want to use jelly bean....any solutions...?

bk201doesntexist said:
This is not an international gsm device, so the factory images will not work I believe, since it requires another radio, and neither will the OTA update.
Sent from my Nexus
Click to expand...
Click to collapse
what is the solution then, should i sell it? please guide me...and there is another problem that my nexus screen is showing some icons on its background that are slightly visible when the screen is white or anything which uses white color, is it a screen issue? or software problem...?

Screen burn in. A quick search suggests that any gsm image would work on the docomo version (takju, yakju). What does the phone say as far as device if you go into Maps > settings> about? It seems he could fastboot flash everything except the radio..

bodh said:
Screen burn in. A quick search suggests that any gsm image would work on the docomo version (takju, yakju). What does the phone say as far as device if you go into Maps > settings> about? It seems he could fastboot flash everything except the radio..
Click to expand...
Click to collapse
my platform in maps is: samsung maguro- galaxy nexus
and version: 6.4.0 (#6040015)
gmm-android-google
what about my screen problem. why there are slight icons whcih are noticeable when the screen is white and it shows that there are icons on the background.

Immediately below your platform, it should say what firmware your device is running (yakju, yakjux, yakjuxx, etc.). Im just wondering because i know all yakjus are convertible. But i guess just knowing its a maguro is detail enough. As far as screen burn in, turn down your brightness. I never run mine above say 40%.

bodh said:
Immediately below your platform, it should say what firmware your device is running (yakju, yakjux, yakjuxx, etc.). Im just wondering because i know all yakjus are convertible. But i guess just knowing its a maguro is detail enough. As far as screen burn in, turn down your brightness. I never run mine above say 40%.
Click to expand...
Click to collapse
Well, when i got this phone, it was like this, i did not noticed screen burns when i was buying it, can i do something to fix those screen burns myself, i dont want to spend money to replace the led screen?
Secondly, help me i dont understand much what is radio or baseband or whatever, i just want to use jelly bean...tell me how to update it, please

Again, turn down your brightness. And you already mentioned the only thread you should need: efrant's return to stock thread. If you don't understand something, keep trying to learn before you mess with your phone.

[Q] How do I keep root access when flashing latest CyanogenMod?

the question is short, sweet, and to the point. How do I get (or keep intact) root access on the newest version of CyanogenMod?
ANNOYING- (I lose root access every time I install CyanogenMod, and I have to boot into CMW and restore back to stock ROM every time to get root back)
I did some research on this issue, and most sources say "CyanogenMod has officially decided not to include root rights in their newer ROMs".
EEEK! :/ HALP PL0X!!1!111!!!!

Root access is turn off by default but you can still turn it on.
Look in Developer Options menu.

In developer options, enable Root for ADB & Apps.

deleted
I replied to this post....But I wanted to reply to another post,actually....sorry, I opened too many browser tabs....and caused this mistake

Restore Root status to Captivate phone w/CyanogenMod 11 M12
Moderators, If this is not the right place to post, kindly move to proper location.
I have a AT&T Captivate phone (SGH-I897 Samsung) that I rooted and changed to a Cyanogenmod 11 M12.
Before changing to KitKat
Code:
Capivate
Model: Samsung SGH-I897
Firmware: 2.3.5
Baseband: I897UCKK4
Kernel: 2.6.35.7-I897UCKK4-CL614489
Build#: GINGERBREAD.UCKK4
I changed the OS from GingerBread to KitKat with Odin3 V1.85 and this thread
http://forum.xda-developers.com/showthread.php?t=1350266
Instead of (speedmod kernel) I used Corn kernal 7.0A Odin flashable version .
My phone now reads:
Code:
Capivate
Model: Samsung SGH-I897
Firmware: 4.4.4
Baseband: I9000UGK3
Kernel: 3.0.101-gd54123e [email protected] #1 Tue Nov 11 21:49:07 PST 2014
Build#: cm_captivatemtd-userdebug 4.4.4 KTU84Q a842ce8199 test-keys
Most of the apps need to be reinstalled (not an issue). I will need to restore phone contacts, txt msging logs. (If I can not, it will just be inconvenient. (I did {I think correctly} a backup of the data. Will see if info can be restored.)
My main question: My phone is no longer Rooted. Is there a procedure to restore the Rooted state? How can this be accomplished? (Detailed directions preferred if available.)
Thank you in advance for your assistance.
EDIT -- Problem solved regarding ROOT Access
Congrats! Android 4.4.2 KitKat firmware based custom ROM CM11 M4 is now installed and running on your AT&T Galaxy Captivate SGH-I897. [Note: Root may turned off by default in CM ROM, To enable it, enable developer settings first (tap the build number 8 times under about device), then enable root under Developer Settings]
Click to expand...
Click to collapse
androidiphonehacker said:
the question is short, sweet, and to the point. How do I get (or keep intact) root access on the newest version of CyanogenMod?
ANNOYING- (I lose root access every time I install CyanogenMod, and I have to boot into CMW and restore back to stock ROM every time to get root back)
I did some research on this issue, and most sources say "CyanogenMod has officially decided not to include root rights in their newer ROMs".
EEEK! :/ HALP PL0X!!1!111!!!!
Click to expand...
Click to collapse

MITHRAND1R said:
Thank you in advance for your assistance.
Click to expand...
Click to collapse
You are, in fact, in the wrong forum.... this is for the S4, not the Captivate. Any way, check either security settings or developer options for an entry called root access. It should be something to do with that.

lordcheeto03 said:
You are, in fact, in the wrong forum.... this is for the S4, not the Captivate. Any way, check either security settings or developer options for an entry called root access. It should be something to do with that.
Click to expand...
Click to collapse
Thanks. I'll look for the Captivate forum and post my question there.

You may have to update superusr.

OTA Update Today for AT&T Note 2

Check for OTA Update in your settings.

Is it Lollipop?

I don't think so. I think it is a security update.
I'm rooted on stock rom so i just froze it using Titanium backup. Heard people installed the update and it froze there rooted phone.

Update the Software for the Samsung Galaxy Note II (i317)
Update summary
AT&T released a new software update for the Samsung Galaxy Note 2 (SGH-i317) via Firmware Over the Air (FOTA) over Wi-Fi on November 11, 2014.
Software Update Includes
Android OS Enhancements
User-Initiated Software Update
From the Home screen, press the Menu key.
Tap Settings.
Tap the More tab.
Tap About Device.
Tap Software update.
Tap Check for updates, and then follow the subsequent prompts.
Verifying the Update
From the Home screen, press the Menu key.
Tap Settings.
Tap the More tab.
Tap About Device.
The following information displays:
Android version: 4.4.2
Baseband version: I317UCUCNJ1
Kernel version: 3.0.31-1728680 [email protected] #1 Wed Oct 1 22:38:36 KST 2014
Build number: KOT49H.I317UCUCNJ1
File size: 93.2MB

I already have TWRP installed (stock rooted - last build) and I'm just wondering if it is worth it go back to stock recovery and update - then reinstall TWRP all over again.
What do you think guys?

keplenk said:
I already have TWRP installed (stock rooted - last build) and I'm just wondering if it is worth it go back to stock recovery and update - then reinstall TWRP all over again.
What do you think guys?
Click to expand...
Click to collapse
I wouldn't. I just posted this in the other thread about the OTA:
a042349 said:
Same thing happened to me. Rooted but otherwise stock GN2. Got the update, rebooted and it got stuck at the boot logo. I tried everything. Flashed CWM, then tried a couple different ROM's. Then went to TWRP recovery, and tried the Team Elektron ROM, that got a little farther, boot logo with sound, but it still hung. Tried a modem update, and even the bootloader - nothing worked.
Luckily I had just bought mine ($300 on Amazon right now) so I just sent it back as defective and ordered a new one. Gonna be real careful of the ATT update and maybe even skip it and go right to a custom ROM.
Click to expand...
Click to collapse

same thing just happened to me. Got stuck on the "Launching Apps" screen. tried everything to recover. still have black tie protection on my phone from BB and decided to have them swap it under my plan.
New phone, up to date on 4.4.2 NJ1 but i would like to root now. Anyone successful yet?

kabinoff said:
same thing just happened to me. Got stuck on the "Launching Apps" screen. tried everything to recover. still have black tie protection on my phone from BB and decided to have them swap it under my plan.
New phone, up to date on 4.4.2 NJ1 but i would like to root now. Anyone successful yet?
Click to expand...
Click to collapse
Best way is to download a custom recovery and flash it in Odin. Then when boot hold on the home and up key to enter recovery. If the phone boot complete withou enter recovery, the recovery would be replaced with the factory recovery. When in recovery flash supersu zip and restart. The recovery will be replaced with the factory recovery, but you had root installed, enter supersu and reboot.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

melvinaury said:
Best way is to download a custom recovery and flash it in Odin. Then when boot hold on the home and up key to enter recovery. If the phone boot complete withou enter recovery, the recovery would be replaced with the factory recovery. When in recovery flash supersu zip and restart. The recovery will be replaced with the factory recovery, but you had root installed, enter supersu and reboot.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
actually flashed CF with Odin and it worked.

kabinoff said:
actually flashed CF with Odin and it worked.
Click to expand...
Click to collapse
Did it really work?

I don't understand one thing - official 4.4.2 OTA was released over a month ago, correct?
I have two Note 2 SGH-I317s AT&T branded with OEM 4.3 (no rooting or other non-OEM additions).
If I stick working AT&T SIM card and check for updates it says the device is up to date.
Moreover if I'd connect it to Kies it would also say that firmware is up to date!
Same thing on both phones - what am I missing?
I purchased them used - maybe the previous owners rooted them and this prevents them from updating?
One had a Knox at "1" since I for some stupid reason downgraded it to 4.1 via Odin (and then took it to AT&T service center where they flashed 4.3 back), another one has Knox at "0"...

toshik1 said:
I don't understand one thing - official 4.4.2 OTA was released over a month ago, correct?
I have two Note 2 SGH-I317s AT&T branded with OEM 4.3 (no rooting or other non-OEM additions).
If I stick working AT&T SIM card and check for updates it says the device is up to date.
Moreover if I'd connect it to Kies it would also say that firmware is up to date!
Same thing on both phones - what am I missing?
I purchased them used - maybe the previous owners rooted them and this prevents them from updating?
One had a Knox at "1" since I for some stupid reason downgraded it to 4.1 via Odin (and then took it to AT&T service center where they flashed 4.3 back), another one has Knox at "0"...
Click to expand...
Click to collapse
Is service activated on the AT&T SIM? That might be a factor.
Regardless, there are two 4.4.2 official releases for the I317 - NE5 and NJ1. If OTA won't work for you, check my sig for links to packages that provide another way to get the complete stock firmare on your phone - rooted or unrooted.

Zen Arcade said:
Is service activated on the AT&T SIM? That might be a factor.
Regardless, there are two 4.4.2 official releases for the I317 - NE5 and NJ1. If OTA won't work for you, check my sig for links to packages that provide another way to get the complete stock firmare on your phone - rooted or unrooted.
Click to expand...
Click to collapse
Yes the SIM card has normal active service on it.

Other reasons OTA won't work:
1 - Location (if you are not in an area where OTA updates are provided, then...
)
2 - AT&T Update apk disabled on phones (seems unlikely that this would be the case on two phones but a factory reset might clear this as it is set on the data side)
3 - Identity issues (could be any number of things related to IMEI, efs partition scrambling, etc - just spitballing)
As far as suggestions go, I'd say try a factory reset and clear cache from recovery. If that doesn't work, maybe go back to AT&T and see if they can figure it out - the phones are stock and it's their OTA process. If that doesn't work, you can pursue the path I suggested previously - same firmware update, minus the script that pushes stock recovery every time you boot. You will trip the knox flag though...only an issue for warranty repair really. Others here have intentially or unitentionally received the NJ1 OTA with the knox flag tripped on their phones.

DroidTuner said:
I don't think so. I think it is a security update.
I'm rooted on stock rom so i just froze it using Titanium backup. Heard people installed the update and it froze there rooted phone.
Click to expand...
Click to collapse
Which process did you freeze?

I did a hard reset and finally took 423.13(!!!) Mb upgrade! Be careful what you wish for
Got 4.4.2 I317UCUCNE5

toshik1 said:
I did a hard reset and finally took 423.13(!!!) Mb upgrade! Be careful what you wish for
Got 4.4.2 I317UCUCNE5
Click to expand...
Click to collapse
Glad to hear it. Wait a day (or disable network time and the set the time on the phone forward at least a day) and try again - you should get NJ1. (If that's what you want). Approx. 93MB security and minor enhancement update.

Just to follow-up - it took the second update with T-Mobile SIM card even without waiting for 24 hours.
I guess in order to take the updates the phone's IMEI MUST re-register on AT&T network with the valid AT&T SIM card first.
It's now I317UCUCNJ1