Develop Bugs

[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] Will a new rom fix this Desire Z?

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

Which of these two possibilities is better for installing updates on a rooted phone?

Hello. I'm coming from a old windows mobile phone and just got my first Android device "Samsung Galaxy S4 mini GT-i9195" and obviously i'm loving it.
Still being a newbie to Android i already did a bit of advanced stuff (at least for a novice android user) like installing CWM Recovery and rooting the phone in order to be able to install apps on and external SD card.
But a new question arose: What about new Android updates, can i still install them without loosing root or even worse, damaging the phone?
After searching a bit on google i came up with two possible and contraditory possibilities which are:
-Yes, and afterwards i would only need to restart the phone in CWM mode and reapply the zip root file i used previously;
-No, it will likely mess the phone and i should wait 1 or 2 weeks for a updated rooted rom and "install" that instead.
So, i'm a bit confused here, what would be more advisable?

I suggest to make a nandroid backup, then try a custom rom from the dev forum.
There are 4.4.4 kikat roms for our beloved S4 mini, and i dont think samsung will go further.
Envoyé de mon GT-I9190

rick6 said:
-Yes, and afterwards i would only need to restart the phone in CWM mode and reapply the zip root file i used previously;
Click to expand...
Click to collapse
...... if, as has been said, you ever get an update. An update certainly will not damage the phone.
You certainly won't have to wait for anything. I agree with zlaz, flash a new ROM such as Carbon - you get regular updates and great support here on XDA (whichever ROM you try).

Custom ROMs like CarbonRom (see the development section) is the way to go for this phone I would say. But if you wanna stay on stock and if we would get an update, Samsung probably wont let you install it via the usual OTA or Kies method, because your device is flagged as "Modified" after flashing a custom recovery (you can see this in the about this device section in the settings). You would still be able to flash the update manually with Odin, but you will then probably have to reroot it.

LanderN said:
Custom ROMs like CarbonRom (see the development section) is the way to go for this phone I would say. But if you wanna stay on stock and if we would get an update, Samsung probably wont let you install it via the usual OTA or Kies method, because your device is flagged as "Modified" after flashing a custom recovery (you can see this in the about this device section in the settings). You would still be able to flash the update manually with Odin, but you will then probably have to reroot it.
Click to expand...
Click to collapse
That's 100% true, I don't remember now exactly when your phone say, that it is modified and you can't update - moment you search for update in it or moment you try to download update that it has find.
Samsung oryginal software is not that greate anyways

Thank you all for the replies.
I think i got what i wanted with your awnsers, i just need to dig a bit more about the avaiable roms what what i can get from them. At the moment i'll keep my s4 mini as it is for a while longer i guess.
As for warranty i get something while booting up saying "Set warranty Bit: Kernel", but that seems to be what you normaly get when root a stock rom.

Samsung Galaxy S4 (T-Mobile) - Android 4.4.4 Bootloader Restriction?

Hey,
If I understand correctly, if the Samsung Galaxy S4 (SGH-M919) is updated to either: Android 4.3.X or Android 4.4.X; then a restriction is added to the bootloader - preventing the flashing of older stock roms such as Android 4.2.2 (M919UVUAMDL). Is that correct?
In addition, what would I need to do in order to remove this bootloader restriction, so that my SGH-M919 (on 4.4.4 - M919UVUFNK2) would then allow a successful flash to an older stock rom such as Android 4.2.2 (M919UVUAMDL)?
For reference, I have listed the details of my phone below:
Brand/Series/Make: Samsung Galaxy S4
Model Number: SGH-M919
Carrier (Country): T-Mobile (USA)
Android Version: Android 4.4.4
Baseband Version (Firmware/ROM): M919UVUFNK2
Phone Rooted Before?: No
Also for reference, I've listed all the various SGH-M919 stock firmwares/roms:
4.4.4 (2014 December) - M919UVUFNK2
4.4.4 (2014 September) - M919UVUFNH7
4.4.2 (2014 March) - M919UVUFNB4
4.3.0 (2013 November) - M919UVUEMK2
4.2.2 (2013 April) - M919UVUAMDL
-XDAUserII

What your looking for doesn't exist, mainly because developers and tech geeks are always developing for the future or what's ahead.
So do the apps and programs, they make changes for what's ahead, not for what passed.
For that reason no one has taken the time to find this "way back machine".
It's like buying a new led tv and trying to convert it to crt tube.
Like removing the electronic ignition on your new car and installing points and condenser.
Like ripping the guts out of your side by side fridge and putting blocks of ice in it.
Do you know what I mean.
Pp.

PanchoPlanet said:
What your looking for doesn't exist, mainly because developers and tech geeks are always developing for the future or what's ahead.
So do the apps and programs, they make changes for what's ahead, not for what passed.
For that reason no one has taken the time to find this "way back machine".
Click to expand...
Click to collapse
I understand the point. However, I do believe there is a way to essentially downgrade from Android 4.4.4 (SGH-M919: M919UVUFNK2) to Android 4.2.2 (SGH-M919: M919UVUAMDL); since I have seen guides on how to do it (links listed below)
http://forum.xda-developers.com/showthread.php?t=2258628
http://forum.xda-developers.com/showthread.php?t=2336392
http://www.theandroidsoul.com/downg...-sgh-m919-android-4-2-2-jelly-bean-back-stock
https://www.youtube.com/watch?v=KUebfbEn5HU [<-- 4.4.2 to 4.3.0]
although it's ambiguous if this can be done from Android 4.4.4 (M919UVUFNK2).
Perhaps there is a method of accomplishing this indirectly maybe not through removing the bootloader restriction directly, but instead getting around it on the SGH-M919? I have listed below some of the ideas I have read online, and would like some feedback to be provided on indicating which would be viable for allowing the downgrade?
Ideas:
-Flashing the bootloader itself?
-Using a custom recovery?
-Using a custom kernel?
-Disabling/Removing Samsung KNOX? (Perhaps in doing so, the bootloader restriction may also be disabled?)
-Root Android 4.4.4 (SGH-M919: M919UVUFNK2) first to gain Root access, and then use Root access to increase the permission level needed to override the bootloader restriction?
-Install a custom Android 4.4.4 rom/firmware which unlocks the bootloader as part of its' installation, and then try flashing to Android 4.2.2 (M919UVUAMDL) when on the installed custom rom?
I'm sure given how many custom roms, custom recoveries, and custom kernels, and many other modifications developed for the SGH-M919 on Android 4.4.4 that the ability to flash - either directly/indirectly - from Android 4.4.4 (SGH-M919: M919UVUFNK2) to Android 4.2.2 (SGH-M919: M919UVUAMDL) should be feasible - any ideas?
-XDAUserII

Ok.
Pp.

Once you have a Knox bootloader, you can only load a newer version. That's what Knox and Samsung did to enhance security for the BYOD corporate systems. Once you have a Knox bootloader, you'll always have a Knox bootloader.
However, if the reason you want to run a MDL bootloader is to SIM unlock, it's not the bootloader, but the kernel that will enable the service menus. Search for MDL kernel, or other threads.
BTW, the newer modems rely on the newer bootloaders.
Rob

rlichtefeld said:
Once you have a Knox bootloader, you can only load a newer version. That's what Knox and Samsung did to enhance security for the BYOD corporate systems. Once you have a Knox bootloader, you'll always have a Knox bootloader.
However, if the reason you want to run a MDL bootloader is to SIM unlock, it's not the bootloader, but the kernel that will enable the service menus. Search for MDL kernel, or other threads.
BTW, the newer modems rely on the newer bootloaders.
Rob
Click to expand...
Click to collapse
The reason I would like to downgrade from Android 4.4.4 (M919UVUFNK2) to Android 4.2.2 (M919UVUAMDL) is to be able to run apps from the Google Play Store that are only compatible with Android 4.2.2. Would changing the kernel allow me to run apps from the Google Play Store that are only compatible with Android 4.2.2? And run these Android 4.2.2 apps with full compatibility?
-XDAUserII

What apps would these be?
Pp.

XDAUserII said:
The reason I would like to downgrade from Android 4.4.4 (M919UVUFNK2) to Android 4.2.2 (M919UVUAMDL) is to be able to run apps from the Google Play Store that are only compatible with Android 4.2.2. Would changing the kernel allow me to run apps from the Google Play Store that are only compatible with Android 4.2.2? And run these Android 4.2.2 apps with full compatibility?
-XDAUserII
Click to expand...
Click to collapse
I'd be interested in knowing which apps those are. That's a pretty small market share to only allow it to run on 4.2.2
http://www.phonedog.com/2015/01/07/...january-2015-sees-kitkat-grow-all-others-fall
Rob

I just had to have my phone returned for sim card errors and the one they sent me was 4.4.4 and m919uvufnk2
So am I unable to root from where i am or even downgrade to get root?
If wrong place ill make a thread i just seen this topic and it looks like it may be the cause of the issues getting anywhere with Odin

NiMaD83 said:
I just had to have my phone returned for sim card errors and the one they sent me was 4.4.4 and m919uvufnk2
So am I unable to root from where i am or even downgrade to get root?
If wrong place ill make a thread i just seen this topic and it looks like it may be the cause of the issues getting anywhere with Odin
Click to expand...
Click to collapse
This is all you need to root your phone.
http://forum.xda-developers.com/showthread.php?p=41797176
Just follow instructions.
Pp.

wth, sersiouly man. I tried everything i came across all morning and nothing . I go to that link and say to myself "wtf ive tried to flash this in odin already and nothing but i guess ill try it again" and viola
thank you

rlichtefeld said:
However, if the reason you want to run a MDL bootloader is to SIM unlock, it's not the bootloader, but the kernel that will enable the service menus. Search for MDL kernel, or other threads.
Click to expand...
Click to collapse
I have looked for more information on this and cannot find anything. I would like to unlock my phone and am running 4.4.4, Nk2 with a kernel date of Nov 17 2014. Is there any information you could link that can help me get this done? I have a rooted phone. (Sorry if im not providing the correct information, I am new to all of this)

LaszerBranes said:
I have looked for more information on this and cannot find anything. I would like to unlock my phone and am running 4.4.4, Nk2 with a kernel date of Nov 17 2014. Is there any information you could link that can help me get this done? I have a rooted phone. (Sorry if im not providing the correct information, I am new to all of this)
Click to expand...
Click to collapse
Not sure how hard you looked, since there is a whole thread:
http://forum.xda-developers.com/showthread.php?t=2780006
Start reading at the top, I think you'll find very interesting info about post #13.
Or, if the phone is paid for, T-Mobile is now required by law (as of Feb 11)to give you the unlock codes. Just call 611 on your phone and talk to a rep.
Rob

rlichtefeld said:
Once you have a Knox bootloader, you can only load a newer version. That's what Knox and Samsung did to enhance security for the BYOD corporate systems. Once you have a Knox bootloader, you'll always have a Knox bootloader.
However, if the reason you want to run a MDL bootloader is to SIM unlock, it's not the bootloader, but the kernel that will enable the service menus. Search for MDL kernel, or other threads.
BTW, the newer modems rely on the newer bootloaders.
Rob
Click to expand...
Click to collapse
i'm trying to unlock my s4 can you tell me what i need to do to do this please?
do i need to downgrade to MDL?

rlichtefeld said:
Once you have a Knox bootloader, you can only load a newer version. That's what Knox and Samsung did to enhance security for the BYOD corporate systems. Once you have a Knox bootloader, you'll always have a Knox bootloader.
However, if the reason you want to run a MDL bootloader is to SIM unlock, it's not the bootloader, but the kernel that will enable the service menus. Search for MDL kernel, or other threads.
BTW, the newer modems rely on the newer bootloaders.
Rob
Click to expand...
Click to collapse
In my experience, I can go back and forward between knox bootloaders on my M919, at the expense of flash counts, but never tried returning to a pre-knox bootloader.

Tried to root.. nothing worked but now having issues.

I was trying to root my device through Odin.. i found a couple different things though this forum to flash through TWRP but none worked, it seems I have the wrong device and noone has made one compatible with it. Anyway, my system status is changed from Original to Custom and my build number has changed. I am trying to change it back to the stock recovery... and back to normal. I cant find any downloads for this. Could someone please direct me. My normal build number, version, and other info that I need a stock for:
Build number: kot49h.t310ueucnk1
Version: 4.4.2
SM-T310
Samsung Galaxy Tab 3 8.0
I'd really appreciate it if someone did this for me, because multiple apps seem to not work...

Doom1337 said:
I was trying to root my device through Odin.. i found a couple different things though this forum to flash through TWRP but none worked, it seems I have the wrong device and noone has made one compatible with it. Anyway, my system status is changed from Original to Custom and my build number has changed. I am trying to change it back to the stock recovery... and back to normal. I cant find any downloads for this. Could someone please direct me. My normal build number, version, and other info that I need a stock for:
Build number: kot49h.t310ueucnk1
Version: 4.4.2
SM-T310
Samsung Galaxy Tab 3 8.0
I'd really appreciate it if someone did this for me, because multiple apps seem to not work...
Click to expand...
Click to collapse
I dont think changing of build numbers actually related to your apps. Try this link: http://www.sammobile.com/firmwares/download/38524/T310UEUCNK1_T310XARCNK1_XAR

Doom1337 said:
I was trying to root my device through Odin.. i found a couple different things though this forum to flash through TWRP but none worked, it seems I have the wrong device and noone has made one compatible with it. Anyway, my system status is changed from Original to Custom and my build number has changed. I am trying to change it back to the stock recovery... and back to normal. I cant find any downloads for this. Could someone please direct me. My normal build number, version, and other info that I need a stock for:
Build number: kot49h.t310ueucnk1
Version: 4.4.2
SM-T310
Samsung Galaxy Tab 3 8.0
I'd really appreciate it if someone did this for me, because multiple apps seem to not work...
Click to expand...
Click to collapse
Nothing will happen if you change the build number, but if you still want to change it search for your device and look for its build number
example": Samsung galaxy tab 3 sm-t310 build number.

Doom1337 said:
I was trying to root my device through Odin.. i found a couple different things though this forum to flash through TWRP but none worked, it seems I have the wrong device and noone has made one compatible with it. Anyway, my system status is changed from Original to Custom and my build number has changed. I am trying to change it back to the stock recovery... and back to normal. I cant find any downloads for this. Could someone please direct me. My normal build number, version, and other info that I need a stock for:
Build number: kot49h.t310ueucnk1
Version: 4.4.2
SM-T310
Samsung Galaxy Tab 3 8.0
I'd really appreciate it if someone did this for me, because multiple apps seem to not work...
Click to expand...
Click to collapse
Hm... Strange. Have you tried doing a factory data reset? that may help since there was stuff put into your system... at least I think. Or you could look for a stock firmware and flash it via odin. Also, since you do have a custom recovery you can flash root via the custom recovery and then you'll gain root then you can unroot to fix the problems. I never really had this problem but you can try those steps and maybe it will work. Can you tell me if you tried any of these steps and if it work?