Related
Hello,
I am pondering the possibility to buy the Samsung Galaxy S II and have heard quite a few rumors that this phone will have a locked and encrypted boot loader making it impossible to use alternative ROMs.
I am sure hackers will take very little time in fixing this but am still wondering. Has anyone seen tangible claims of encrypted/lock boot compared to the I9000 (which I own atm).
Thanks!
Expansys has a 32 gb model listed as coming april 11th but pricing is not yet announced
galaxinho said:
Expansys has a 32 gb model listed as coming april 11th but pricing is not yet announced
Click to expand...
Click to collapse
Yes, no definite date. Doesn't answer my question though
FRLinux said:
Yes, no definite date. Doesn't answer my question though
Click to expand...
Click to collapse
Samsung's own website mentions encryption, but doesn't give enough detail for us to know if it'll be custom ROM friendly yet. I'm sure it'll take very little time once the phone is released to let you know, just hold tight until then!
Ayrlupine said:
Samsung's own website mentions encryption, but doesn't give enough detail for us to know if it'll be custom ROM friendly yet. I'm sure it'll take very little time once the phone is released to let you know, just hold tight until then!
Click to expand...
Click to collapse
Link please?
I suppose you are referring to the data encryption that Samsung mentioned in its splash page? I really doubt they would post information about a Locked Bootloader on their website as it really wouldn't do them any good publicity wise.
sarsh11 said:
Link please?
I suppose you are referring to the data encryption that Samsung mentioned in its splash page? I really doubt they would post information about a Locked Bootloader on their website as it really wouldn't do them any good publicity wise.
Click to expand...
Click to collapse
Yeah, I said encryption. Of course we have no idea about the bootloader until it's released or someone techy gets their hands on one! That's why I said we have to wait. Sorry if my post was ambiguous.
SamFirmware just tweeted, Samsung are using same ODIN for Galaxy S II, just with new .PIT file. So it will be flashable.
Broomfundel said:
SamFirmware just tweeted, Samsung are using same ODIN for Galaxy S II, just with new .PIT file. So it will be flashable.
Click to expand...
Click to collapse
Yes saw that but it doesn't mean it is flashable just like that until you see it working. Good start anyway.
FRLinux said:
Hello,
I am pondering the possibility to buy the Samsung Galaxy S II and have heard quite a few rumors that this phone will have a locked and encrypted boot loader making it impossible to use alternative ROMs.
I am sure hackers will take very little time in fixing this but am still wondering. Has anyone seen tangible claims of encrypted/lock boot compared to the I9000 (which I own atm).
Thanks!
Click to expand...
Click to collapse
There's already a running topic on this question found here.
Beards said:
There's already a running topic on this question found here.
Click to expand...
Click to collapse
Thanks spotted it afterwards.
FRLinux said:
Thanks spotted it afterwards.
Click to expand...
Click to collapse
No problem... Your not the only one who has started a topic and found later it's already running.
That link I passed you is actually a second topic on another which was started a day earlier here.
That means we now have three topics covering the same (although each will fragment as further posts are made).
Everyone has their needs/requirements for a phone but for me-personally to fulfill my individual desires and needs it would need to be unlocked 100%. Otherwise I will jsut have to keep my captivate
As I do not approve of manufacturers locking hardware that I paid for with my hard earned money and now own.
HappyBallz said:
Everyone has their needs/requirements for a phone but for me-personally to fulfill my individual desires and needs it would need to be unlocked 100%. Otherwise I will jsut have to keep my captivate
As I do not approve of manufacturers locking hardware that I paid for with my hard earned money and now own.
Click to expand...
Click to collapse
Seem the norm these days on android handsets but keep in mind that the mobile market has always liked a locked an tight device.
Sent from my GT-I9000 using Tapatalk
SE was from the very few to lock the bootloader with X10 and now they decided to unlock the simfree Arc, HTC locked their Incredible S in another hand
I don't think sammy will lock the bootloader,just a little security for the formalities that can be easily decoded by happy devs
vegetaleb said:
SE was from the very few to lock the bootloader with X10 and now they decided to unlock the simfree Arc, HTC locked their Incredible S in another hand
I don't think sammy will lock the bootloader,just a little security for the formalities that can be easily decoded by happy devs
Click to expand...
Click to collapse
Yes over time there is always a way. But that said, new devices tend to have better boot loader locking.
Has there been any update on whether the S2 have a locked bootloader?
monkley said:
Has there been any update on whether the S2 have a locked bootloader?
Click to expand...
Click to collapse
Search this very forum. Several threads opened about this but only speculations until someone has one and messes with it.
Locked bootloader...
So I see the chat regarding the locked bootloader on the sg2...I also see people on the forum actually have the device...could they some how check and see if it is locked?
I have been going round in circles looking for a new phone...finally decided on the sam sg2 to find out they are going down the same route as moto!
So, to all the happy owners of a shiney new sg2...whats the dealo!?!?!?
owners of the sgs2 in this forum? you must be mistaken lol...
sam locking the bootloader? who told you that nonsense?
they wouldnt dare to lock the bootloader. its 1 of many reason why sgs 1 succeeded as it did.
if they want sgs2 to be a successful device as well they wont lock the bootloader. it makes sense that the bootloader will be UNlocked.. but then again you can never tell... we might be like if we will find out its locked. followed by and then after we will unlock it. leading to
First and foremost, Thank you to all of the devs that put in their time and efforts. Secondly, I have a very good friend that works at a verizon store. I would like to know if there is any information that he can provide me(within reason) that would assist with the Verizon Galaxy Note3 bootloader unlock. Please shoot any questions my way and I will forward them to him immediately. Again this is ONLY for the Verizon Galaxy Note 3 bootloader specific questions.[/FONT]
siggmund said:
First and foremost, Thank you to all of the devs that put in their time and efforts. Secondly, I have a very good friend that works at a verizon store. I would like to know if there is any information that he can provide me(within reason) that would assist with the Verizon Galaxy Note3 bootloader unlock. Please shoot any questions my way and I will forward them to him immediately. Again this is ONLY for the Verizon Galaxy Note 3 bootloader specific questions.[/FONT]
Click to expand...
Click to collapse
There's a bounty thread opp open where toy might find someone that could use your help. Look in the general section.
no real knowledge
toddnbrown said:
There's a bounty thread opp open where toy might find someone that could use your help. Look in the general section.
Click to expand...
Click to collapse
I wanted to go back to stock with my note 3 after root and safestrap. OTA would not work even flashing back to stock through Odin left behind custom symbol at the Samsung screen but updating through Verizon worked with no issues no faild updates. while doing this I noticed a series of numbers and letters going on during the Verizon update process. with no real knowledge of how anything works admittedly I feel like the correspondence during Verizon update via computer may help someone who knows what to do with the information
novice22 said:
I wanted to go back to stock with my note 3 after root and safestrap. OTA would not work even flashing back to stock through Odin left behind custom symbol at the Samsung screen but updating through Verizon worked with no issues no faild updates. while doing this I noticed a series of numbers and letters going on during the Verizon update process. with no real knowledge of how anything works admittedly I feel like the correspondence during Verizon update via computer may help someone who knows what to do with the information
Click to expand...
Click to collapse
I think we should all write and ask us to help http://forum.xda-developers.com/member.php?u=3682533
he helped owners note 2
http://forum.xda-developers.com/showthread.php?t=2045563
But the note 2 had a exynos processor...thus is a qualicom processor with supposed e fuse and knox...He is a mad genius though....but I would say safe strap is the best unless someone leaks a engineering bootloader like they did for the Verizon s3 with snapdragon/qualicom
Sent from my VZW Note3..ha..ha..
Janker5050 said:
But the note 2 had a exynos processor...thus is a qualicom processor with supposed e fuse and knox...He is a mad genius though....but I would say safe strap is the best unless someone leaks a engineering bootloader like they did for the Verizon s3 with snapdragon/qualicom
Sent from my VZW Note3..ha..ha..
Click to expand...
Click to collapse
I am holding out hope for the sock monkey again.
Sent from my SCH-I535 using Tapatalk
Lol...I would have @$%+_% that sock monkey
Ok, so I have an idea to like downgrade from mk2 or mf3... I am a noob to i337, so please explain to me WHY I can't do this before flaming :C
So we obv can't flash because of Samsung's locked bootloader and knox and stuff, but what if we were to completely wipe our phone. Not like a regular "I'ma factory reset my brick yo!" No no no, I mean completely getting rid of EVERYTHING. Modem, kernel, everything to make it as if you haven't gotten a single flash of ANYTHING on your phone, as if your phone is just getting it's software installed. THEN, we flash a MDL and everything for 4.1.2, or practically whatever came before mf3 (since my phone was shipped with that, I never really took the time to research what came before so I'm not sure what version is before). So, I'm thinking maybe someone has actually tried this, and thinking someone has not... Just want to find out if you can, and if you can't, why not.
Thanks
P.S: Wasn't sure whether to post in General or Q&A, so I posted it here
Because when your phone updated to mf3 or later it blows a q fuse that makes it impossible. It's beyond software. It's a hardware issue
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Ends said:
Because when your phone updated to mf3 or later it blows a q fuse that makes it impossible. It's beyond software. It's a hardware issue
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Oh ok, well in that case (sorry I'm a noob) whats a qfuse? I've searched it up and haven't really gotten anywhere with it
SkyAttacksX said:
Oh ok, well in that case (sorry I'm a noob) whats a qfuse? I've searched it up and haven't really gotten anywhere with it
Click to expand...
Click to collapse
From what I've read, it's a piece of hardware that only counts up. It is checked when attempting to flash old bootloaders.
DeadlySin9 said:
From what I've read, it's a piece of hardware that only counts up. It is checked when attempting to flash old bootloaders.
Click to expand...
Click to collapse
This seems like a good place to ask this question: does flashing 4.3 MK2 blow another qfuse? And if we're already on MF3, would you recommend waiting to update and not blowing that qfuse in case that might be the key to regaining access to custom recovery? Or are we doomed forever already and I should just go ahead and take the update?
karate104 said:
This seems like a good place to ask this question: does flashing 4.3 MK2 blow another qfuse? And if we're already on MF3, would you recommend waiting to update and not blowing that qfuse in case that might be the key to regaining access to custom recovery? Or are we doomed forever already and I should just go ahead and take the update?
Click to expand...
Click to collapse
MK2 does trip it, so no MF3 downgrade. Whether or not you upgrade is really up to you: progress is not coming too quickly and unless Samsung patched a security hole we haven't even found yet in the boot loader there's a chance any MF3 exploit may carry over. I would recommend MF3 personally since you can still use Safestrap for some freedom and it'll be less difficult since they won't have Knox to work around.
Hmmm... so it's a piece of hardware huh... would it be possible to remove this hardware? I took apart my S3 when the screen broke to see what was going on internally so if I'm correct, you can take apart the S4, right?
EDIT : Then again, that hardware could be pretty itty bitty...
SkyAttacksX said:
Hmmm... so it's a piece of hardware huh... would it be possible to remove this hardware? I took apart my S3 when the screen broke to see what was going on internally so if I'm correct, you can take apart the S4, right?
EDIT : Then again, that hardware could be pretty itty bitty...
Click to expand...
Click to collapse
I think it would be better for someone to hack the firmware and alter it to make it "think" it has checked this piece of hardware and return a favorable response.
However, i am no developer...
joeybear23 said:
I think it would be better for someone to hack the firmware and alter it to make it "think" it has checked this piece of hardware and return a favorable response.
However, i am no developer...
Click to expand...
Click to collapse
Hmmmm I've wanted to be a dev for quite some time and I am only 14... However I did do a little noob java scripting for irc chats back when I was like 10, so if you know anyone willing to teach me the basics and give me the structure to adb and coding for android and all that, that'd be great
SkyAttacksX said:
Hmmmm I've wanted to be a dev for quite some time and I am only 14... However I did do a little noob java scripting for irc chats back when I was like 10, so if you know anyone willing to teach me the basics and give me the structure to adb and coding for android and all that, that'd be great
Click to expand...
Click to collapse
This is a great community. PM some of the developers and they can probably point you in the right direction to get started.
LOL.. If it were that easy, it would have already been done.
joeybear23 said:
This is a great community. PM some of the developers and they can probably point you in the right direction to get started.
Click to expand...
Click to collapse
Alright, thanks a ton! +1
custommx3 said:
LOL.. If it were that easy, it would have already been done.
Click to expand...
Click to collapse
That doesn't help
I still have a S4, and I never did the update, so I can flash roms, but do as I am fixing to do, I am fixing to sell the wifes S4 MF3, you can still get $500-$600 and get a T-Mobile Note 3.....there are people who know nothing of flashing roms that will pay that price....quit wasting time looking for a solution as the devs that were working on it moved on to different devices....you can bet that there will be no fix for this in the near future.....keep in mind that this is NO software problem.
.
TheAxman said:
I still have a S4, and I never did the update, so I can flash roms, but do as I am fixing to do, I am fixing to sell the wifes S4 MF3, you can still get $500-$600 and get a T-Mobile Note 3.....there are people who know nothing of flashing roms that will pay that price....quit wasting time looking for a solution as the devs that were working on it moved on to different devices....you can bet that there will be no fix for this in the near future.....keep in mind that this is NO software problem.
.
Click to expand...
Click to collapse
CURRENTLY CHATTING WITH SAMSUNG (SORRY FOR CAPS JUST SO EXCITED ) This is what they said just now after I asked about an eFuse/qFuse. Tell me if this is invalid!!!
******: As of now, I would like to inform you that, eFuse is not available in S4 mobile.
This is what the rep has said so far for the i337, will be updating further soon
UPDATE BEFORE POST : I had to ask them this, as I am a newbie and I didn't want to put the burden on you guys.
Visitor: Thank you very much. If you don't mind, is there a difference between qFuse and eFuse?
******: You are welcome. I wish I could have helped you in this regard. However we in live chat have information regarding the US model devices trouble shooting only.
So I guess this could mean they aren't completely suited for these types of Q&A's? Either way, rumors did spread about eFuse stuff being involved but I was just told officially that this was incorrect. Please tell me if I am wrong? Or I might have to start a new thread on this, rather.
SkyAttacksX said:
CURRENTLY CHATTING WITH SAMSUNG (SORRY FOR CAPS JUST SO EXCITED ) This is what they said just now after I asked about an eFuse/qFuse. Tell me if this is invalid!!!
******: As of now, I would like to inform you that, eFuse is not available in S4 mobile.
This is what the rep has said so far for the i337, will be updating further soon
UPDATE BEFORE POST : I had to ask them this, as I am a newbie and I didn't want to put the burden on you guys.
Visitor: Thank you very much. If you don't mind, is there a difference between qFuse and eFuse?
******: You are welcome. I wish I could have helped you in this regard. However we in live chat have information regarding the US model devices trouble shooting only.
So I guess this could mean they aren't completely suited for these types of Q&A's? Either way, rumors did spread about eFuse stuff being involved but I was just told officially that this was incorrect. Please tell me if I am wrong? Or I might have to start a new thread on this, rather.
Click to expand...
Click to collapse
Samsung customer service reps have no clue about the device other than what's on their scripts. A noob on xda has 100 times the knowledge they do
jd1639 said:
Samsung customer service reps have no clue about the device other than what's on their scripts. A noob on xda has 100 times the knowledge they do
Click to expand...
Click to collapse
My hopes
TheAxman said:
I still have a S4, and I never did the update, so I can flash roms, but do as I am fixing to do, I am fixing to sell the wifes S4 MF3, you can still get $500-$600 and get a T-Mobile Note 3.....there are people who know nothing of flashing roms that will pay that price....quit wasting time looking for a solution as the devs that were working on it moved on to different devices....you can bet that there will be no fix for this in the near future.....keep in mind that this is NO software problem.
.
Click to expand...
Click to collapse
Keep in mind the T-Mobile Note 3, N900T gets really bad LTE reception when using an AT&T sim. In places that had a -90dbm LTE signal on the S4 wouldn't even connect to LTE on the N900T for me. The device also got really warm when it was connected to LTE. I don't know if that's because the N900T isn't optimized for band 17, or just a way for them to discourage people from using AT&T.
Developers for the S4 have not called it quits. They are currently working on bringing safestrap to the latest MK2 update.
I'm really just wasting my time here because actually "searching" for any of the stuff in this thread would have provided answers, but I guess posting the information 1001 times is no different than the 1000 times it's already been posted.
A q-fuse involves hardware on some level, an e-fuse is software related. The AT&T S4 used q-fuses to increment firmware boot-loaders. It was incremented between MDL and MF3. It was incremented again between MF3 and MJ6. And it was increased again between MJ6 and MK2. When it is incremented, YOU CAN NOT GO BACK TO A PREVIOUS FIRMWARE...PERIOD! You can not simply change the information in aboot. Any changes invalidate Samsung's signature and without their encrypted key, a file CAN NOT be resigned.
scott14719 said:
I'm really just wasting my time here because actually "searching" for any of the stuff in this thread would have provided answers, but I guess posting the information 1001 times is no different than the 1000 times it's already been posted.
A q-fuse involves hardware on some level, an e-fuse is software related. The AT&T S4 used q-fuses to increment firmware boot-loaders. It was incremented between MDL and MF3. It was incremented again between MF3 and MJ6. And it was increased again between MJ6 and MK2. When it is incremented, YOU CAN NOT GO BACK TO A PREVIOUS FIRMWARE...PERIOD! You can not simply change the information in aboot. Any changes invalidate Samsung's signature and without their encrypted key, a file CAN NOT be resigned.
Click to expand...
Click to collapse
I'm very much sorry for that. However, do not misinterpret me when I say this but, your post was unnecessary as someone already said qFuse was on a hardware level. I dedicated a bunch of today to S4 and the I337 model specifically. Tomorrow or Wednesday is when I'll be sending some PMs to Devs
Basically, thread is over with. Thanks everyone
As the title says might switch to verizon when the s6 releases. Coming from and at&t s5 with bootloader being locked and updates slow. I wanted your guy input.
How long was it for you guys to achieve root? Unlocked Bootloader?
And of course hows development going? Is it still Alive ?
Thanks guys for your input.
David111jr said:
As the title says might switch to verizon when the s6 releases. Coming from and at&t s5 with bootloader being locked and updates slow. I wanted your guy input.
How long was it for you guys to achieve root? Unlocked Bootloader?
And of course hows development going? Is it still Alive ?
Thanks guys for your input.
Click to expand...
Click to collapse
We achieved root on June 15, 2014. I'm pretty sure that was the same time as the AT&T version.
We have not unlocked the bootloader.
Check out the Development subforum and you'll see we only have a small handful of developers going. They are wonderfully talented/dedicated, but a small group.
But keep in mind - this is the S5. The S6 could be totally different, with either TONS of development or none at all. Or it could be very similar. Each phone is different and it's just a matter of what catches on. You won't know until after it's out.
btonetbone said:
We achieved root on June 15, 2014. I'm pretty sure that was the same time as the AT&T version.
We have not unlocked the bootloader.
Check out the Development subforum and you'll see we only have a small handful of developers going. They are wonderfully talented/dedicated, but a small group.
But keep in mind - this is the S5. The S6 could be totally different, with either TONS of development or none at all. Or it could be very similar. Each phone is different and it's just a matter of what catches on. You won't know until after it's out.
Click to expand...
Click to collapse
I hear ya, that's why I wanna see what htc brings to the table I'm hoping they can "wow" me with there new m9. And there development is always good as long as htcdev allows anybody to unlock the bootloader.
I guess I will know soon enough ?
David111jr said:
I hear ya, that's why I wanna see what htc brings to the table I'm hoping they can "wow" me with there new m9. And there development is always good as long as htcdev allows anybody to unlock the bootloader.
I guess I will know soon enough ?
Click to expand...
Click to collapse
The chances for root for the VZ S5 were slim anyway and it took Geohot to break it. Forget about bootloader, it will most likely never happen. Same thing with root of the S6
ldeveraux said:
The chances for root for the VZ S5 were slim anyway and it took Geohot to break it. Forget about bootloader, it will most likely never happen. Same thing with root of the S6
Click to expand...
Click to collapse
Agreed. They probably won't provide an unlocked bootloader.
bpham said:
Agreed. They probably won't provide an unlocked bootloader.
Click to expand...
Click to collapse
No, Samsung definitely will not unlock their bootloader for non-dev handset (if they even still make the dev version). My point is I doubt anyone will be able to unlock it...
I'm hoping for Dev. Ed. S6, like the S4 and S5 before it.
timeToy said:
I'm hoping for Dev. Ed. S6, like the S4 and S5 before it.
Click to expand...
Click to collapse
i hear you guys and even if the s6 would never get root i think i can live with that as long as there would be reasonable timed updates. the main reason for me to root would be to flash a rom that has a new update that a stock ota would take months behind.
i think sunday i will get my answer when we will see the specs on both m9 and s6 and would just have to make up my mind.
So I've searched around XDA, Reddit and the rest of the net trying to find any root method for this tablet. I just got this tablet for free as a deal with T-Mobile.
I see a lot of guides on XDA for older Tab A's, and also for what appears to be the WiFi variant of mine (a lot of 380 and 385), but nothing for T387. I've blindly rooted stuff and made mistakes in the past ambitiously trying to find root on older devices and have ended up in soft bricks and (even a hard brick on LG devices) in the past, and I'm not looking to make that mistake again. I do know that Samsung's variants have kind of homogenized a bit more the past few years also.
Will these root/TWRP guides for the 380/385 also work for my 4G variant of this tablet, or am I going to have to hope and wait someone makes something a bit more specific?
Just wanted to inquire.
Hey, I'm actually looking for the same info! Subscribed and am hoping to hear back.
News
Have you found anything?
Nope. I haven't. I opened a thread on reddit as well. I actually used the title of this post since it was perfectly worded and anyone searching the web will find both in the results. I hope speedanderson doesn't mind
Of course not!
Sorry, I forgot about this post and checking back I'm glad to see I'm not the only one who wants an answer to this.
I'm going to see if I can find your Reddit thread also just to keep tabs.
Edit: found it immediately. Sad to see nobody answered there I did give it silver in hopes it might make someone notice it
did you unlock the oem?
I am still unable to unlock it!
combination
flashed combination
oem unlock
trying to flash magisk
anyone tried twrp?
Thanks man. I responded there but I think this is the same issue I have e with my 950u and snapdragon processor. Outta luck for the time being!
speedanderson said:
Of course not!
Sorry, I forgot about this post and checking back I'm glad to see I'm not the only one who wants an answer to this.
I'm going to see if I can find your Reddit thread also just to keep tabs.
Edit: found it immediately. Sad to see nobody answered there I did give it silver in hopes it might make someone notice it
Click to expand...
Click to collapse
gdillard1002 said:
flashed combination
oem unlock
trying to flash magisk
anyone tried twrp?
Click to expand...
Click to collapse
Can you tell me from where you got the combination file for this.
My problem now is that qualcomm secureboot is enabled and cant flash twrp.
Anyone can give a hint on bypassing the secure boot?
any luck?
Has there been any luck in rooting the SM-T387T?
Well, if this thread ever produces success be sure and let me know. I have the same combination files y'all have I'm sure.
Bump... surely someone has been able to root these devices by now.
Sent from my SM-T385 using Tapatalk
I'm going to assume adb would be our friend here.
To elaborate, connect to adb with the tablet on and pull the kernel to Downloads. Use magisk to patch that Img and then try to push it back.
I'm joining you guys
In for +1 as well...
I have a Verizon T-387 would love to get Lineage or stock android on there.
Maybe we need to start a donation ring to attract developers.
Or feed this thread to show how amazing people we are
Btw I'm quite impressed by the tab A 2018 (our version), my nexus 7 died 2 month ago and I got the galaxy for "free"with a data plan. I chose it instead of a Huawei Mediapad T5 thinking that they would be equally slow with their 2 Gb of ram... But the Tab A is very fast and handle everything I throw to it very well and timely imho (YouTube, browsing, very light multitasking).
I don't know how the T5 would have behave but I'm glad that I chose the smaller 8' tab vs the 10" T5.
Nice thread
Hi all I'm looking for a root for this new galaxy t387t tablet. But I haven't seen anything yet except for this thread. Has anyone made any progress and rooted this device yet? Thanks in advance for any replies.
Stumbled across this thread. I've bought one on OfferUp that is google locked. Are the steps to bypass the same as for the T387 the same as for the t580 or t380?