Need someone to verify this for me. It says here that you can use a program called "EZ Unlock" to unlock the bootloader on the Galaxy S 3.
Can someone verify if this app would unlock my GS3 bootloader? I'm on 4.3 so mine is updated unfortunately. I would just get the bootloader unlock code from Samsung but I don't have an international model, that's the only one they would give you the BL code for.
EXTRA CREDIT I heard rumor of something called a "golden backup" supposedly a backup that exist on the phone of the older version you upgraded from, anyone?
drago10029 said:
Need someone to verify this for me. It says here that you can use a program called "EZ Unlock" to unlock the bootloader on the Galaxy S 3.
Can someone verify if this app would unlock my GS3 bootloader? I'm on 4.3 so mine is updated unfortunately. I would just get the bootloader unlock code from Samsung but I don't have an international model, that's the only one they would give you the BL code for.
EXTRA CREDIT I heard rumor of something called a "golden backup" supposedly a backup that exist on the phone of the older version you upgraded from, anyone?
Click to expand...
Click to collapse
No joy there, I'm afraid. Ol' Sam knew what he was doing with the 4.3 bootloader thing and a BL with EZ Unlock is a No-No. I just tried it now and whilst the whole process went well enough, the outcome was a hard brick. It, therefore, doesn't seem possible to 'unlock' your bootloader, at least, not for now.
The 'golden backup' is an option you see in the service menu. Not sure what it does though.
Larry2999 said:
No joy there, I'm afraid. Ol' Sam knew what he was doing with the 4.3 bootloader thing and a BL with EZ Unlock is a No-No. I just tried it now and whilst the whole process went well enough, the outcome was a hard brick. It, therefore, doesn't seem possible to 'unlock' your bootloader, at least, not for now.
The 'golden backup' is an option you see in the service menu. Not sure what it does though.
Click to expand...
Click to collapse
Really you tried it out? why?!?! also any information on the golden backup? how about accessing the service menu on android 4.3?
drago10029 said:
Really you tried it out? why?!?! also any information on the golden backup? how about accessing the service menu on android 4.3?
Click to expand...
Click to collapse
Yeah. Just to see if there was any way I could add to the body of knowledge... I'm aware EZ Unlock works with older firmware versions of the VZW model. The instructions on the site, however, suggested it works with the i747 as well. Apparently, this must be with older firmware versions as well and not the 4.3. After powering off the phone following the process, the phone just wouldn't power back on again. At least, not until, I'd inserted my debrick card and done a firmware restore.
I know I've seen the golden back function when accessing the service menu via *#197328640#. Never had to use it though so I wouldn't know if it does back up from older firmware.
Larry2999 said:
Yeah. Just to see if there was any way I could add to the body of knowledge... I'm aware EZ Unlock works with older firmware versions of the VZW model. The instructions on the site, however, suggested it works with the i747 as well. Apparently, this must be with older firmware versions as well and not the 4.3. After powering off the phone following the process, the phone just wouldn't power back on again. At least, not until, I'd inserted my debrick card and done a firmware restore.
I know I've seen the golden back function when accessing the service menu via *#197328640#. Never had to use it though so I wouldn't know if it does back up from older firmware.
Click to expand...
Click to collapse
Well, your failure has become my knowledge lol. I'm still really interested in the learning about the "golden backup" though. I wonder if the Galaxy S4 unlock procedure would work for us? I may play around with it.
and glad you knew about the SD De-brick. I thought you just haphazardly tried used EZ unlock :silly: so the SD-Debrick works on 4.3?
Honestly, I've read a lot of stickies but most of the OP's don't mention things supporting 4.3 or not, so it makes trying things out a little tougher. Is there a "back to stock" 4.3 guide? I assumed that's what you did when you bricked. Every 4.3 forum/guide I find is all like (4.3 beware this and beware that!) lol
Back to stock
drago10029 said:
Well, your failure has become my knowledge lol. I'm still really interested in the learning about the "golden backup" though. I wonder if the Galaxy S4 unlock procedure would work for us? I may play around with it.
and glad you knew about the SD De-brick. I thought you just haphazardly tried used EZ unlock :silly: so the SD-Debrick works on 4.3?
Honestly, I've read a lot of stickies but most of the OP's don't mention things supporting 4.3 or not, so it makes trying things out a little tougher. Is there a "back to stock" 4.3 guide? I assumed that's what you did when you bricked. Every 4.3 forum/guide I find is all like (4.3 beware this and beware that!) lol
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2658486 As close as it gets for now...at&t
drago10029 said:
Well, your failure has become my knowledge lol. I'm still really interested in the learning about the "golden backup" though. I wonder if the Galaxy S4 unlock procedure would work for us? I may play around with it.
and glad you knew about the SD De-brick. I thought you just haphazardly tried used EZ unlock :silly: so the SD-Debrick works on 4.3?
Honestly, I've read a lot of stickies but most of the OP's don't mention things supporting 4.3 or not, so it makes trying things out a little tougher. Is there a "back to stock" 4.3 guide? I assumed that's what you did when you bricked. Every 4.3 forum/guide I find is all like (4.3 beware this and beware that!) lol
Click to expand...
Click to collapse
Oh! I wouldn't risk "bricking" my phone if I wasn't reasonably sure I could recover. In fact, I've "intentionally" bricked this particular device in every way you can imagine just for learning purposes. I really think an unlock exploit is possible and we may be closer to one now than we know. Indeed I feel Touchwiz 4.3 has been unduly vilified because of the secure bootloader and other than the absence of a free unlock option, it's a major improvement on previous versions. I haven't seen the S4 unlock procedure. Can you send me a link to any thread on this?
There are a couple of threads dealing with recovery and return to stock for the 4.3. The first is a guide on how to recover from a hard brick caused by flashing the wrong bootloader. That was where I got my debrick file from ...
http://forum.xda-developers.com/showthread.php?t=2549068
Whilst the second is a guide on returning to factory stock (4.3) firmware via custom recovery ...
http://forum.xda-developers.com/showthread.php?t=2658486
pckarma112 said:
http://forum.xda-developers.com/showthread.php?t=2658486 As close as it gets for now...at&t
Click to expand...
Click to collapse
Larry2999 said:
Oh! I wouldn't risk "bricking" my phone......
Click to expand...
Click to collapse
"I REPLIED TO THIS AT WORK FRIDAY, WONDER WHAT HAPPENED"
Thanks both you guys, I'm actually not concerned with warranty though. I'm ultra careful so I've never used once so far for something I broke on a phone lol.
And thanks for the stock guide pckarma, probably wouldn't of found that on my own. also would you 2 know if flashing any i747 rom with cmw/twrp would work on my phone with updated bootloader? (being that I don't flash a different bootloader of course lol)
drago10029 said:
"I REPLIED TO THIS AT WORK FRIDAY, WONDER WHAT HAPPENED"
Thanks both you guys, I'm actually not concerned with warranty though. I'm ultra careful so I've never used once so far for something I broke on a phone lol.
And thanks for the stock guide pckarma, probably wouldn't of found that on my own. also would you 2 know if flashing any i747 rom with cmw/twrp would work on my phone with updated bootloader? (being that I don't flash a different bootloader of course lol)
Click to expand...
Click to collapse
Yes, it should work - as long as you are not flashing a non-compatible bootloader. I noticed also from the development threads that someone has now put together an Odin flash-able image for 4.3
Larry2999 said:
Yes, it should work - as long as you are not flashing a non-compatible bootloader. I noticed also from the development threads that someone has now put together an Odin flash-able image for 4.3
Click to expand...
Click to collapse
The only compatibility problem I had was with the old TWRP version which I knew doesn't work with KK ROMs, just updated to the new TWRP and Kit Kat flashed fine. And "development thread"? You mean one of the stickies their?
drago10029 said:
The only compatibility problem I had was with the old TWRP version which I knew doesn't work with KK ROMs, just updated to the new TWRP and Kit Kat flashed fine. And "development thread"? You mean one of the stickies their?
Click to expand...
Click to collapse
I was referring to the one posted in this thread by enewman...
http://forum.xda-developers.com/showthread.php?t=2722660
Larry2999 said:
I was referring to the one posted in this thread by enewman...
http://forum.xda-developers.com/showthread.php?t=2722660
Click to expand...
Click to collapse
When the time comes hopefully it works.
Related
Is any method of root or custom ROM compatible with our T Mobile Samsung Note tablet? Coming from a HTC one m7 where all rom were compatible other then CDMA/ GSM
I've used the towelroot but really looking to install aosp on this thing already
Sent from my One using XDA Free mobile app
law16 said:
Is any method of root or custom ROM compatible with our T Mobile Samsung Note tablet? Coming from a HTC one m7 where all rom were compatible other then CDMA/ GSM
I've used the towelroot but really looking to install aosp on this thing already
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
Your best bet is to ask in the rom thread. I have yet to flash anything on my P607T other then rooting. It looks like Dev work is very slow for this tablet. So you may not get a 100% working AOSP rom any time soon. Stock rom is really fast and sable once you root and deboat it. That is what I am sticking with for awhile.
Prod1702 said:
Your best bet is to ask in the rom thread. I have yet to flash anything on my P607T other then rooting. It looks like Dev work is very slow for this tablet. So you may not get a 100% working AOSP rom any time soon. Stock rom is really fast and sable once you root and deboat it. That is what I am sticking with for awhile.
Click to expand...
Click to collapse
I'm looking for ROMs too. But I think I'll stay with stock for now. Any recommendations on what apps to debloat?
dmunjal said:
I'm looking for ROMs too. But I think I'll stay with stock for now. Any recommendations on what apps to debloat?
Click to expand...
Click to collapse
Your best way is to just use TB and froze whatever you do not want. If you run into problems just unfroze it. If you uninstall and you run into a bootloop you will need to have the stock Odin firmware ready. here is a link to get the stock odin file.
http://www.sammobile.com/firmwares/3/?download=29807
I just uninstalled whatever I did not want. If you google What apps are safe to remove on a Note 3 to debloat, it will pretty much be the same as the 10.1. Both the note 3 and the 10.1 are pretty much the same other then screen.
Edit: I got this list from here
https://docs.google.com/spreadsheet...ZzBfWlR4MC03aDMyZ1BDUFNqU0E&usp=sharing#gid=0
Here is a a list for the GS4 which as a lot of the apps we have as well
http://forum.xda-developers.com/showthread.php?t=2317714
unlocking bootloader
I think we need to get the bootloader unlocked to get development on this thing rollin'
I'm willing to lend my device to a well-reputed senior-member/developer and pay shipping both ways if they think they can work some magic for the SM-P607T
Should I make a new post with regards to this?
Was able to root using this method no Knox either
http://forum.xda-developers.com/showthread.php?t=2785804
Sent from my SM-P607T using XDA Free mobile app
TG2008 said:
I think we need to get the bootloader unlocked to get development on this thing rollin'
I'm willing to lend my device to a well-reputed senior-member/developer and pay shipping both ways if they think they can work some magic for the SM-P607T
Should I make a new post with regards to this?
Click to expand...
Click to collapse
bootloader is unlocked and there is no problems getting root and current Twrp can be installed which says the bootloader is unlock. if the bootloader was locked you wouldn't be able to flash Twrp. from the looks of it no one has a p607. it is all 605 or the wifi only one p600 and 601. stock rom with root and debloated works great. try a 605 rom. hopefully CM starts to pick up more then we are set.
Sent from my HTC One_M8 using Tapatalk
Do P605 ROMs even work on a P607T? I've been wondering that myself. I have a 607T and although I am very impressed with the stock ROM it just is never going to measure up to CM for me.
I've been thinking about giving the P605 CM 11 port a try in a few weeks when it's just a bit more stable, but I have no idea how similar they are or if my device would even boot after flashing it!
amirite said:
Do P605 ROMs even work on a P607T?
Click to expand...
Click to collapse
Yes.
kcrudup said:
Yes.
Click to expand...
Click to collapse
Anyway to flash the "modem.bin" and "NON-HLOS.bin" flash partitions yet?
kcrudup said:
Yes.
Click to expand...
Click to collapse
And how do i install a dialer app to make voice call with my haedset on my note 10.1 2014 edition (T-Mobile) p607t..is it possible at all??
TG2008 said:
Anyway to flash the "modem.bin" and "NON-HLOS.bin" flash partitions yet?
Click to expand...
Click to collapse
Guys... Did you even read that thread in the link?
You should be asking these questions there... That whole thread is dedicated to making calls on the P607T.... And if you read the thread you'll know the author hit a brick wall and a boot loader hack is needed to flash the proper modem files for phone calls.
amirite said:
Guys... Did you even read that thread in the link?
Click to expand...
Click to collapse
Reading is Fundamental, amirite? (... sorry, couldn't resist )
But yeah, go there for any updates.
kcrudup said:
Reading is Fundamental, amirite? (... sorry, couldn't resist )
But yeah, go there for any updates.
Click to expand...
Click to collapse
Haha. Thank you kcrudup for pointing to that thread, gave me some useful info on using P605 Roms on a P607T.
Any idea about what sort of problems may pop up from doing this? I got a reply in the CM thread that their P605 version of CM should work fine on my P607 but... Surely it can't be that simple? Any idea what differences there are between thecode of the two tablets or is it really that similar?
amirite said:
I got a reply in the CM thread that their P605 version of CM should work fine on my P607- but surely it can't be that simple?
Click to expand...
Click to collapse
I'm 95% sure the only difference physically is the radio "front end" hardware is tuned for the T-Mo LTE frequencies so the modem baseband SW reflects that, and software-wise all that's new is a few pre-installed apps like the "My T-Mobile" app and that (loud-and-annoying-as-hell-and-quickly-removed) T-Mobile "jingle" on startup; I've put several P605 ROMs on my 607T and everything's worked OK ('cause the bootloader won't let me overwrite the radios and potentially-dangerous bootloader files anyway).
kcrudup said:
I'm 95% sure the only difference physically is the radio "front end" hardware is tuned for the T-Mo LTE frequencies so the modem baseband SW reflects that, and software-wise all that's new is a few pre-installed apps like the "My T-Mobile" app and that (loud-and-annoying-as-hell-and-quickly-removed) T-Mobile "jingle" on startup; I've put several P605 ROMs on my 607T and everything's worked OK ('cause the bootloader won't let me overwrite the radios and potentially-dangerous bootloader files anyway).
Click to expand...
Click to collapse
Awesome info thanks so much!! So if I understand correctly, any differnces that would render my tablet completely inoperable are already protected from flashing? So I don't need to meet with the TARs for the Roms to remove the modem files or anything?
I mean, I don't mind if my radio breaks or something, I can handle flashing back to stock I am just never sure when I start flashing a new Android device what risks there are of bricking it completely (which, with Knox in the picture, could totally screw me).
So with that I will probably be going flash crazy tonight and tomorrow to test our some different 605 Roms starting with Cyanogen. I'll try to post any findings or quarks here or in those threads!
amirite said:
So I don't need to [mess?] with the TARs for the Roms to remove the modem files or anything?
Click to expand...
Click to collapse
You will have to remove all the "*.mbn" and "*.bin" files from (Samsung-supplied) non-P607T ROMs, though- Odin will abort the flash if it receives a bad status from the bootloader when the bootloader rejects the flash operation. But it should be a straightforward unzip/rm/zip operation to repack, and I'm sure the CM flashes are just "boot" and "system" (and possibly "recovery") partitions anyway.
kcrudup said:
You will have to remove all the "*.mbn" and "*.bin" files from (Samsung-supplied) non-P607T ROMs, though- Odin will abort the flash if it receives a bad status from the bootloader when the bootloader rejects the flash operation. But it should be a straightforward unzip/rm/zip operation to repack, and I'm sure the CM flashes are just "boot" and "system" (and possibly "recovery") partitions anyway.
Click to expand...
Click to collapse
so is it necessary to remove the above mentioned files. I can't just flash a p605 rom with twrp?
stoehner said:
so is it necessary to remove the above mentioned files. I can't just flash a p605 rom with twrp?
Click to expand...
Click to collapse
Yes it is necessary, the .mbn files relate to the bootloader and the .bin files is the modem and NON_HLOS, being that they are for a different ROM it could cause major problems and maybe even bricking. @kcrudup even mentioned the bootloader conflicting with Odin if the device models don't match, so it seems you won't get the 605's installed without removing said files.
Prod1702 said:
Your best bet is to ask in the rom thread. I have yet to flash anything on my P607T other then rooting. It looks like Dev work is very slow for this tablet. So you may not get a 100% working AOSP rom any time soon. Stock rom is really fast and sable once you root and deboat it. That is what I am sticking with for awhile.
Click to expand...
Click to collapse
I have been looking for a guide for flashing twrp onto my sm-p607t but i cant find one. I mainly need the correct twrp img.tar file for odin. I found this one ( openrecovery-twrp-2.6.3.3-lt03wifiue.img ) but I don't know if it is the right one. I used towelroot to root it and i used the proper supersu to disable knox so i just need the custom recovery now.
I haven't found any information for my specific model for some reason.
What I want to do is install stock Android 5 (by stock, I mean what comes on the Google Nexus) on my Verizon Samsung s4 mini (SCH-I435).
To my knowledge, this would involve:
Rooting the phone
Finding a compatible ROM
Flashing the ROM
I just can't find any guides or ROMs for my specific model. Can anyone here help?
I have the exact same model of the s4-mini as you do, and I've looked around just about everywhere. It seems that the bootloader has never been unlocked for this variant of the S4-mini. Verizon also just released a new firmware update that patches the kernel, preventing the use of previous root methods, and it may be some time till someone finds a way around it. If you find anything, please tell me, as I can't stand this bloatware crap on my phone.
How do you usually unlock the bootloader?
19lmyers said:
How do you usually unlock the bootloader?
Click to expand...
Click to collapse
Usually people create software, such as Cyanogenmod, that exploit vulnerabilities in the software on the phone, giving them access to the bootloader. One of the many issues with this variant is that it is distributed by Verizon, and Verizon is very vigilant about patching vulnerabilities.
EDIT: After a little more digging, I found that the bootloader is completely locked and there is a 99.9999999% chance that it will never be unlocked, typical Verizon for you.
Stuckurface said:
Usually people create software, such as Cyanogenmod, that exploit vulnerabilities in the software on the phone, giving them access to the bootloader. One of the many issues with this variant is that it is distributed by Verizon, and Verizon is very vigilant about patching vulnerabilities.
EDIT: After a little more digging, I found that the bootloader is completely locked and there is a 99.9999999% chance that it will ever be unlocked, typical Verizon for you.
Click to expand...
Click to collapse
Don't you mean never?
19lmyers said:
Don't you mean never?
Click to expand...
Click to collapse
Pretty much.
Correction
You can root the SCH-I435 with towel root, install SuperSU and Busy Box from Play store. Then flash phils touch recovery and then flash a rom from SD card in recovery. Beware, if you are on Bluegrass cellular. Any rom must be for CDMA phone for the SCH-I435.
Where would I find a compatible ROM?
looking for too!
I have been looking too. Tried a couple, but lose phone service. Everything else works.
I discovered this. Is it legitimate?
phoneupdateblog.blogspot.com/2015/04/working-tutorial-how-to-updateupgrade_70.html
19lmyers said:
I discovered this. Is it legitimate?
phoneupdateblog.blogspot.com/2015/04/working-tutorial-how-to-updateupgrade_70.html
Click to expand...
Click to collapse
Definitely not legit. They simply have tons of links on their site to upgrading every single phone to lollipop. Inside of each page is exactly the same link to the same "ROM" for every phone, and the comments at the bottom of the page aren't actually real, they are just a picture. Try changing the number at the end of the link "...updateupgrade_70.html" and you will see what I mean.
I was able to successfully root my phone by flashing 4.4.2 NE1 (opposed to the latest version) via Odin and using Towelroot.
Has there been any progress on the addition of a custom recovery?
19lmyers said:
I was able to successfully root my phone by flashing 4.4.2 NE1 (opposed to the latest version) via Odin and using Towelroot.
Has there been any progress on the addition of a custom recovery?
Click to expand...
Click to collapse
I found something interesting that might be worth looking into. This guy (http://forums.androidcentral.com/samsung-galaxy-s4-mini/527518-serious-question-needing-advice.html) claims to have installed a custom rom that was designed for the GT-I9195 on his SCH- i435. I have actually run into him before on other on some other threads and he seems to be legit. But the problem still remains that when he installed the rom his sound and mic didn't work. Still worth looking into though.
The thread I ran into TheGhost1951: http://forum.xda-developers.com/showthread.php?t=2575913
His profile on xda: http://forum.xda-developers.com/member.php?u=1561233
Stuckurface said:
I found something interesting that might be worth looking into. This guy (http://forums.androidcentral.com/samsung-galaxy-s4-mini/527518-serious-question-needing-advice.html) claims to have installed a custom rom that was designed for the GT-I9195 on his SCH- i435. I have actually run into him before on other on some other threads and he seems to be legit. But the problem still remains that when he installed the rom his sound and mic didn't work. Still worth looking into though.
The thread I ran into TheGhost1951: http://forum.xda-developers.com/showthread.php?t=2575913
His profile on xda: http://forum.xda-developers.com/member.php?u=1561233
Click to expand...
Click to collapse
I sent him a PM. Maybe he can shed some light on this
Just curious, would over of the international variant ROMs work if we managed to unlock the bootloader or would the SCH-I435 require its own specific one?
I found an app called Flashify that claims to be able to flash a boot loader or recovery to your device from your device.
Do you think flashing CWM or TWRP would work this way?
19lmyers said:
I found an app called Flashify that claims to be able to flash a boot loader or recovery to your device from your device.
Do you think flashing CWM or TWRP would work this way?
Click to expand...
Click to collapse
It seems that the only thing that this has to offer for us is a way to flash your phone without using a computer, and to back up your phone (I haven't actually tried restoring from a backup). But we still need a version of CWM or TWRP that is made for the sch-i435.
Stuckurface said:
It seems that the only thing that this has to offer for us is a way to flash your phone without using a computer, and to back up your phone (I haven't actually tried restoring from a backup). But we still need a version of CWM or TWRP that is made for the sch-i435.
Click to expand...
Click to collapse
But we'd still need to unlock the boy loader...
SCH-I435
Anyone got success for installing custom recovery and custom ROM on SCH-I435 Verizon? Please help if anyone have done that all.
kjaved8 said:
Anyone got success for installing custom recovery and custom ROM on SCH-I435 Verizon? Please help if anyone have done that all.
Click to expand...
Click to collapse
So two years later - has this ever been done?
I need to put android 5.0 on my S4 Mini so I can use the Square app to accept credit card payments for my business. Their app will not work on anything earlier than 5.0. Otherwise I will have to buy a new phone!:crying:
So, I recently bought a galaxy s4 from ebay, and it seems to work on the network, so I don't think the IMEI is blacklisted. However, when I tried the steps here http://forum.xda-developers.com/showthread.php?t=2282683 and here http://forum.xda-developers.com/showthread.php?t=2283068, I am unable to complete the process. When I do the latter, which seems more like what I did with my S3, I get the same message "unable to process request". I remember I was getting this message on my S3 when I had the SlimKat ROM on it. But when I look at my S4, it looks like it has the OEM ROM on it, so I am not sure what is happening. I looked at my boot loader/baseband, and this is what I have: m919uvufnh7. I know that with my S3 I had to make sure I used the correct ROM to flash my phone, so I could get it unlocked the free method. So, does anyone know what bootloader and ROM could help me accomplish these steps in the second thread?
I am thinking I should flash a different ROM on my phone.
mji2015 said:
So, I recently bought a galaxy s4 from ebay, and it seems to work on the network, so I don't think the IMEI is blacklisted. However, when I tried the steps here http://forum.xda-developers.com/showthread.php?t=2282683 and here http://forum.xda-developers.com/showthread.php?t=2283068, I am unable to complete the process. When I do the latter, which seems more like what I did with my S3, I get the same message "unable to process request". I remember I was getting this message on my S3 when I had the SlimKat ROM on it. But when I look at my S4, it looks like it has the OEM ROM on it, so I am not sure what is happening. I looked at my boot loader/baseband, and this is what I have: m919uvufnh7. I know that with my S3 I had to make sure I used the correct ROM to flash my phone, so I could get it unlocked the free method. So, does anyone know what bootloader and ROM could help me accomplish these steps in the second thread?
I am thinking I should flash a different ROM on my phone.
Click to expand...
Click to collapse
Have you tried contacting T-Mobile? If the phone is paid for in full, they are supposed to unlock it for free.
This worked for me:
http://forum.xda-developers.com/showthread.php?p=58645651
Sent from my SGH-M919 using XDA Free mobile app
rlichtefeld said:
Have you tried contacting T-Mobile? If the phone is paid for in full, they are supposed to unlock it for free.
Click to expand...
Click to collapse
Thanks for the response, but I have not tried it, because I don't think it is that easy. I also purchased AT&T tablets and tried unlocking them, but AT&T said they were 'active' under someone else. They were not not showing as stolen, but active. I am not sure what that entails, but I am guessing I have to register it under my account first, before I can request to unlock it. So before I try going through the long process of figuring out how T-Mobile can unlock my device, I thought I would give this a try. It seems simpler and since I plan on modding my phone after I unlock it, I see it as just part of the process. (At least I hope so.)
radoo7701 said:
This worked for me:
http://forum.xda-developers.com/showthread.php?p=58645651
Sent from my SGH-M919 using XDA Free mobile app
Click to expand...
Click to collapse
I will try this. But I was trying to make sure that there was no problem with downgrading, as I am currently on 4.4.4. And I know that on my S3 there was a big warning about downgrading from 4.3 to 4.1. To avoid bricking my phone, I thought I would ask and make sure.
So thanks again to both of you for the responses!
I will try this. But I was trying to make sure that there was no problem with downgrading, as I am currently on 4.4.4. And I know that on my S3 there was a big warning about downgrading from 4.3 to 4.1. To avoid bricking my phone, I thought I would ask and make sure.
So thanks again to both of you for the responses![/QUOTE]
You only have to downgrade the modem. This should not brick your phone.
Sent from my SGH-M919 using XDA Free mobile app
Would you please posts step by step on what you did to successfully unlock 4.4.4 T-Mobile which I assume is version M919UVUFNK2.
How to Unlock Samsung Galaxy S4 M919 4.4.4
c627627 said:
Would you please posts step by step on what you did to successfully unlock 4.4.4 T-Mobile which I assume is version M919UVUFNK2.
Click to expand...
Click to collapse
Alright, I was able to get mine to work, so maybe I will list my steps. However, I must say that I had some failed attempts (in part due to not understanding the post referred to by radoo7701) and some issues with my phone. But those steps wont be included. Also, my version was m919uvufnh7, not NK2. I would think it does not make a difference, as long as you reflash back to NK2 at the end.
1. I locaed the modem for M919UVUAMDL and m919uvufnh7 modem (as I did not make a backup of mine before starting)
2. I used Odin 3.07 to flash the AMDL modem
3. I tried the steps here http://forum.xda-developers.com/showthread.php?t=2283068, but this would not work, I could not even get the menu to pull up, as it would say request unable to complete. So I tried this http://forum.xda-developers.com/showthread.php?t=2282683 and that actually worked, so I went through these steps successfully.
4. Use cf-auto-root to root your phone
5. Download regionlockaway and transfer it to phone, then install it on phone and run it.
6. flash m919uvufnh7 modem and booted up with my AT&T sim, and it did not ask for unlock code. It just worked!
NOTE: I did have to use a T-Mobile sim card to do the menu process, but radoo claims that he did not do the menu portion. I had already done the menu portion when I finally got to reading his comment. So I can't say that it will work or not. Either way, his suggestion worked for me and I am content with the result!
Thanks radoo7701!
Please post link to files in step 1 you specifically used. And also links for step 5 you used.
Just saw it on the verizon note 4 forum. How come no one is posting about i? Can it be used on N910A variant?
Well.. they have been talking about it.. for over 2 weeks actually.
And no, as of right now it cannot be used for att
Sent from my SAMSUNG-SM-N910A using XDA-Developers mobile app
atx84 said:
Well.. they have been talking about it.. for over 2 weeks actually.
And no, as of right now it cannot be used for att
Sent from my SAMSUNG-SM-N910A using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes i have converted to Developer mode, unlocked rooted retail verizon note4 as of now only works for that phone. I also have a retail verizon edge and there is no unlock yet for that....
bigbooker455 said:
Yes i have converted to Developer mode, unlocked rooted retail verizon note4 as of now only works for that phone. I also have a retail verizon edge and there is no unlock yet for that....
Click to expand...
Click to collapse
So the N910A still is no go. What a bummer!
Is that because at&t left out the developer mode?
I hate at&t so much never in the history of stupidity has anyone screwed up a perfectly well manufactured item as they do.
Remember when they were the only company to add the PMA standard of wireless charging on the lumia 1520?
Man I hope someone fired that idiot. LOL
cxyjordan said:
So the N910A still is no go. What a bummer!
Click to expand...
Click to collapse
YUP!
adambomb_13 said:
Is that because at&t left out the developer mode?
I hate at&t so much never in the history of stupidity has anyone screwed up a perfectly well manufactured item as they do.
Remember when they were the only company to add the PMA standard of wireless charging on the lumia 1520?
Man I hope someone fired that idiot. LOL
Click to expand...
Click to collapse
I was reading note4 AT&T thread and found this, like i said do not take any updates!
AT&T released an update with security enhancements yesterday, any word about this and how this affects us?
I am not sure. I know that I have my OTA blocked; however, I too find it interesting that a sudden security update is released now about two weeks after the Verizon hack is discovered and rolled out. It is stuff like this that tells me that their devs know something that we have yet to discover.
This may work for you AT&T guys.......
Plus, the tools to finish this are already public.
You compile SamsungCID (in a KitKat tree), and use it to change the CID using temp root, then you can flash the corresponding developer edition aboot via ODIN. The reason I haven't release it is that there is an easier method.
Ryan has a slightly better method, he extracts the CID blob from the developer edition aboot, and places it into the current aboot partition, then changes the CID to match the blob. This allows us to convert without needing to be on the developer edition aboot's increment version to unlock.
I have opted to not release the former method, as it could result in people who don't read thoroughly enough bricking due to flashing the old aboot on a newer increment.
bigbooker455 said:
This may work for you AT&T guys.......
Plus, the tools to finish this are already public.
You compile SamsungCID (in a KitKat tree), and use it to change the CID using temp root, then you can flash the corresponding developer edition aboot via ODIN. The reason I haven't release it is that there is an easier method.
Ryan has a slightly better method, he extracts the CID blob from the developer edition aboot, and places it into the current aboot partition, then changes the CID to match the blob. This allows us to convert without needing to be on the developer edition aboot's increment version to unlock.
I have opted to not release the former method, as it could result in people who don't read thoroughly enough bricking due to flashing the old aboot on a newer increment.
Click to expand...
Click to collapse
Now that sounds feasible..... if i had all the tools and a full set of instructions i would love to give it a try in a heart beat.......
giga8547 said:
Now that sounds feasible..... if i had all the tools and a full set of instructions i would love to give it a try in a heart beat.......
Click to expand...
Click to collapse
Make that two of us, I am typically very thorough when I read instructions and have a way of thinking outside the box when looking at issues. Not to mention, if we can unlock the darn bootloader on these things, many of us could do a MM OS update from a more unbloated and pure form.
bigbooker455 said:
This may work for you AT&T guys.......
Plus, the tools to finish this are already public.
You compile SamsungCID (in a KitKat tree), and use it to change the CID using temp root, then you can flash the corresponding developer edition aboot via ODIN. The reason I haven't release it is that there is an easier method.
Ryan has a slightly better method, he extracts the CID blob from the developer edition aboot, and places it into the current aboot partition, then changes the CID to match the blob. This allows us to convert without needing to be on the developer edition aboot's increment version to unlock.
I have opted to not release the former method, as it could result in people who don't read thoroughly enough bricking due to flashing the old aboot on a newer increment.
Click to expand...
Click to collapse
We should be able to change the CID on any Note 4 so I don't see why this wouldn't work. Don't we need root to copy the aboot? My understanding was that the kingroot method doesn't work anymore after an AT&T update. It is now soft bricking phones. I am wondering if the security update could be removed by flashing the original 5.1.1 or maybe even 5.0.1.
dkmac said:
Make that two of us, I am typically very thorough when I read instructions and have a way of thinking outside the box when looking at issues. Not to mention, if we can unlock the darn bootloader on these things, many of us could do a MM OS update from a more unbloated and pure form.
Click to expand...
Click to collapse
I don't own a AT&T version of the Note4, can you roll back?
bigbooker455 said:
I don't own a AT&T version of the Note4, can you roll back?
Click to expand...
Click to collapse
Unfortunatly, once you are on 5.1.1 you are stuck there. I believe that all attempts to roll back to 4.4.4 ended either in failure or a bricked device. To complicate matters more, after king root released I believe version 4.2 it became successful and unstable. Once the phone reboots automatically or manually, you cannot make it past the boot screen. You get a display that tells you to return to an att store. If you root now, you have to reboot via Odin to get the phone up and going again. With all that said, king root is stable to use, but only for a few minutes before unstability and then ultimately reboot. I always have faith in the possible and know that there is and will be a way around all this mess for a permanent unlock bootloader and root.
dkmac said:
Unfortunatly, once you are on 5.1.1 you are stuck there. I believe that all attempts to roll back to 4.4.4 ended either in failure or a bricked device. To complicate matters more, after king root released I believe version 4.2 it became successful and unstable. Once the phone reboots automatically or manually, you cannot make it past the boot screen. You get a display that tells you to return to an att store. If you root now, you have to reboot via Odin to get the phone up and going again. With all that said, king root is stable to use, but only for a few minutes before unstability and then ultimately reboot. I always have faith in the possible and know that there is and will be a way around all this mess for a permanent unlock bootloader and root.
Click to expand...
Click to collapse
I feel you!
bigbooker455 said:
I feel you!
Click to expand...
Click to collapse
Yea, that's why I have been looking for the info that you were talking about. I want to see what I could do to help breath new life back into our phones.
Hello Folks!
As soon as I got the tablet I spent a good few hours looking around for the combo firmware to start looking for exploits so figured I would provide you guys with a link to the firmware for free
It was quite funny actually, after I soft bricked and got stuck in a boot loop I realized I couldn't find any stock firmware anywhere either haha, so I spent a few hours looking for that as well.
I have the Verizon variant, I am not sure if it will work on other USA variants or not as I have no way of trying. With that being said, below will be the links. I will provide a rev1 combination firmware and a rev1 stock firmware as well as a link to a modified ODIN for easy flashing!
And with all that being said, the combo firm is good to bypass FRP. You can enable the oem unlock switch but other than removing FRP it is useless as of right now. You can however, mix and match the firmware unlike my S9+. I am currently on stock firmware with a permissive boot.img for example.
If you got questions or need help, well, you probably shouldn't be downloading anything or flashing haha. But I will try to help when I have time. I do not have any current plans to keep this thread going with updated filese as I had to pay for these. If I can find em free moving forward I will re-upload if I can but I typically stay on the lowest rev/firmware I can until I find a root method
T837VVRU1ARG4 COMBINATION FIRMWARE/FACTORY BINARY
T837VVRU1ARGG STOCK FIRMWARE
MODDED ODIN v3.13.1
If you feel like buying me a beer...
What is the main benefit of this?
In the q&a section someone wrote it is readily rootable with Magisk. Is that not the case?
@elliwigy
Is there any firmware for the unlocked LTE snapdragon. I got the Verizon version but it's not playing nice with AT&T. Any ideas? Maybe flashing the unlocked firmware would help.
apascual89 said:
@elliwigy
Is there any firmware for the unlocked LTE snapdragon. I got the Verizon version but it's not playing nice with AT&T. Any ideas? Maybe flashing the unlocked firmware would help.
Click to expand...
Click to collapse
to my knowledge no.. different models.. not sure if there is a U version or if the sammy one is lte capable
apascual89 said:
@elliwigy
Is there any firmware for the unlocked LTE snapdragon. I got the Verizon version but it's not playing nice with AT&T. Any ideas? Maybe flashing the unlocked firmware would help.
Click to expand...
Click to collapse
I think it's just the tablet, my Verizon one isn't playing nice with my Verizon service. Constantly not switch towers and losing service when full service is available. Or it's a tower problem but my note8 doesn't do it when my tablet does
Thanks for this, have been looking for a couple days for the build.prop file.
If you get permissive boot, try adb verity disable and mod through push pull adb style like we did on Att note 5
Will this work on sm-t817v?
pujuois said:
Will this work on sm-t817v?
Click to expand...
Click to collapse
lol no.. its for t837v.. the 817 is a completely different tablet.. i dont even think there is an 817v.. u sure its not a 818v?
either way, search the internet and you will b rewarded i am sure
TechNyne66 said:
If you get permissive boot, try adb verity disable and mod through push pull adb style like we did on Att note 5
Click to expand...
Click to collapse
its adb disable-verity but no, doesnt work as its not userdebug..
combo firmware are always permissive boots..
i am going to mess with it some more tonight
elliwigy said:
lol no.. its for t837v.. the 817 is a completely different tablet.. i dont even think there is an 817v.. u sure its not a 818v?
either way, search the internet and you will b rewarded i am sure
Click to expand...
Click to collapse
I actually had a 817v. They called it the pro version. It was just an updated version at the time.
OEM Unlock
I have the T837V and would like to ODIN flash your files, but as you know there is no OEM unlock in the Developer Options on this tablet. Are you saying that you can flash these files without enabling the OEM unlocking?
I would like to install TWRP, but I believe this is not possible without enabling the OEM unlock. Do you know if this is true?
Thanks
gene5522 said:
I have the T837V and would like to ODIN flash your files, but as you know there is no OEM unlock in the Developer Options on this tablet. Are you saying that you can flash these files without enabling the OEM unlocking?
I would like to install TWRP, but I believe this is not possible without enabling the OEM unlock. Do you know if this is true?
Thanks
Click to expand...
Click to collapse
there is no unlocking the bl so no twrp is possible..
you can however flash T837V/A/P/T/T1/R4/R7/W firmwares using modified odin
elliwigy said:
there is no unlocking the bl so no twrp is possible..
you can however flash T837V/A/P/T/T1/R4/R7/W firmwares using modified odin
Click to expand...
Click to collapse
@elliwigy any idea what I could flash on a T835C without breaking Knox? Do you think I could flash a T835N or T835 no suffix ROM with modified Odin?
philow said:
@elliwigy any idea what I could flash on a T835C without breaking Knox? Do you think I could flash a T835N or T835 no suffix ROM with modified Odin?
Click to expand...
Click to collapse
not sure.. i dont really look at other region devices
Sent from my SM-N960U using Tapatalk
elliwigy said:
there is no unlocking the bl so no twrp is possible..
you can however flash T837V/A/P/T/T1/R4/R7/W firmwares using modified odin
Click to expand...
Click to collapse
Forgive my apparent noobishness but what exactly will that do? Looking for a way to root and wanna know if u have found something I haven't.
Flash firm then what? Does it make OEM show or what? I just happen ta have the most difficult version of the tab S4 which is SM-T837V
Tybirdy9 said:
Forgive my apparent noobishness but what exactly will that do? Looking for a way to root and wanna know if u have found something I haven't.
Flash firm then what? Does it make OEM show or what? I just happen ta have the most difficult version of the tab S4 which is SM-T837V
Click to expand...
Click to collapse
I am currently working on a root method with the N9 but it should also work on Tab S4 once all is said and done. I actually found the exploit I use on the Tab S4 originally before I started workin the N9. Nothing is released yet as so far have only gained root on S9 Exynos and I am currently super bricked and waiting for a device replacement lol
Flashing other carrier firmware won't help you unlock any bootloaders or anything nor will it necessarily help you root. Only benefit I can see really in flashing other carrier firmware is say if you have an sim unlocked tablet (we'll say it's a Verizon tablet) and you want to use it on say Sprint. You can flash the Sprint software in ODIN and everything should work. It would be like you purchased the tablet from Sprint essentially.
elliwigy said:
I am currently working on a root method with the N9 but it should also work on Tab S4 once all is said and done. I actually found the exploit I use on the Tab S4 originally before I started workin the N9. Nothing is released yet as so far have only gained root on S9 Exynos and I am currently super bricked and waiting for a device replacement lol
Flashing other carrier firmware won't help you unlock any bootloaders or anything nor will it necessarily help you root. Only benefit I can see really in flashing other carrier firmware is say if you have an sim unlocked tablet (we'll say it's a Verizon tablet) and you want to use it on say Sprint. You can flash the Sprint software in ODIN and everything should work. It would be like you purchased the tablet from Sprint essentially.
Click to expand...
Click to collapse
Thanks for the quick reply. I really wanna rid myself of bloatware and unwanted ram usage. I mean really 4gigs for a so called productivity device. I'm sure u understand
Welp here's to a hopeful outcome
837T firmware
elliwigy said:
Hello Folks!
As soon as I got the tablet I spent a good few hours looking around for the combo firmware to start looking for exploits so figured I would provide you guys with a link to the firmware for free
It was quite funny actually, after I soft bricked and got stuck in a boot loop I realized I couldn't find any stock firmware anywhere either haha, so I spent a few hours looking for that as well.
I have the Verizon variant, I am not sure if it will work on other USA variants or not as I have no way of trying. With that being said, below will be the links. I will provide a rev1 combination firmware and a rev1 stock firmware as well as a link to a modified ODIN for easy flashing!
And with all that being said, the combo firm is good to bypass FRP. You can enable the oem unlock switch but other than removing FRP it is useless as of right now. You can however, mix and match the firmware unlike my S9+. I am currently on stock firmware with a permissive boot.img for example.
If you got questions or need help, well, you probably shouldn't be downloading anything or flashing haha. But I will try to help when I have time. I do not have any current plans to keep this thread going with updated filese as I had to pay for these. If I can find em free moving forward I will re-upload if I can but I typically stay on the lowest rev/firmware I can until I find a root method
I was wondering if i could flash firmware for my 837T for tobile to work on AT&T? I understand how to work odin etc, i just was not clear on the software variants and their capabilities.......
thanks
chris
Click to expand...
Click to collapse