Hi everyone,
Thanks for all your hard work attempting to root and install custom ROMs on the Galaxy S4 4.3.
I have a Galaxy S4 i545 with stock OTA 4.3 rooted with VRoot.
I was wondering if there is a similar method to install CWM/TWRP to the method linked to below. If not, perhaps this method could be ported to the Galaxy S4?
nokiafirmware24.blogspot.com/2013/12/root-and-remove-knox-for-samsung-galaxy. html
SoCaliSk8r said:
Hi everyone,
Thanks for all your hard work attempting to root and install custom ROMs on the Galaxy S4 4.3.
I have a Galaxy S4 i545 with stock OTA 4.3 rooted with VRoot.
I was wondering if there is a similar method to install CWM/TWRP to the method linked to below. If not, perhaps this method could be ported to the Galaxy S4?
nokiafirmware24.blogspot.com/2013/12/root-and-remove-knox-for-samsung-galaxy. html
Click to expand...
Click to collapse
No, you can't install CWM/TWRP. You can't install a custom recovery on MJ7 on an I545.
The link you pointed to is for the Galaxy Note 2. Not, in case you hadn't noticed, for the I545. Samsung has a lot of devices, each of which are differently locked down. Just because it says "Samsung" or "Galaxy" in the name of the device doesn't mean anything in terms of how it applies to other Samsung models. (For example, my Galaxy Tab 2 is completely unlocked, easily rooted. That means nothing in terms of the rest of the Samsung product line.)
k1mu said:
No, you can't install CWM/TWRP. You can't install a custom recovery on MJ7 on an I545.
The link you pointed to is for the Galaxy Note 2. Not, in case you hadn't noticed, for the I545. Samsung has a lot of devices, each of which are differently locked down. Just because it says "Samsung" or "Galaxy" in the name of the device doesn't mean anything in terms of how it applies to other Samsung models. (For example, my Galaxy Tab 2 is completely unlocked, easily rooted. That means nothing in terms of the rest of the Samsung product line.)
Click to expand...
Click to collapse
Read my post again. Think carefully before responding.
SoCaliSk8r said:
Read my post again. Think carefully before responding.
Click to expand...
Click to collapse
Looks to me like your question was answered very clearly.
Sent from my NCC 1701 using Tapatalk 4
SoCaliSk8r said:
Read my post again. Think carefully before responding.
Click to expand...
Click to collapse
Please try and be kind. He tried to help and provided (what riker147 and I both thought was a valid & relevant) answer. Maybe he didn't answer exactly what you wanted to know, but he tried. Instead of "think carefully before responding" which comes across very negatively, how about "Thanks for taking the time to try and answer my question. Unfortunately, what you wrote didn't really answer what I was looking to find out, so let me rephrase it so you may be able to help me out further."
Just my thought. You can interact with whomever as you see fit - I just wouldn't expect people to react positively to "think carefully before responding" -- if you wrote that to one of my attempts to help you, I certainly wouldn't reply and try to help you anymore.
I think some people just get sick of seeing the same questions over and over.
OP, the people that discovered the hack you linked to are the same people that are involved with trying to exploit the S4 bootloader after MDK. I'm sure they have tried their old methods.
SoCaliSk8r said:
Read my post again. Think carefully before responding.
Click to expand...
Click to collapse
I did read your post. I did think carefully. You apparently didn't read mine.
Since you apparently didn't understand, this is a forum for the Verizon SCH-I545. The Verizon Galaxy S4.
Verizon has forced Samsung to lock down the I545 boot chain, which makes it very difficult to customize. Galaxy S4 variants on other carriers (like, for example, Sprint) aren't as locked down. So, you need to be quite careful what you do to make sure it's compatible with the specific model of device you're using.
So, you post a message about a completely different device which has only one thing in common with the Verizon Samsung Galaxy S4: it has the word "Samsung" in the device name. I pointed out that what was in that thread DID NOT APPLY to the I545. I did waste some time reading it hoping it applied, but unfortunately not.
What I said is absolutely correct at the moment: you have a MJ7 phone. You can't install custom recovery. You may not like that, but tough cookies - that's the way it is.
Related
Hey guys,what's up?Hope y'all enjoying the phone(You sure are )!
I have some questions though as all my smartphones until now have been HTC and,wanting to buy a Samsung,I have noticed some differences regarding development/modding,for which questions aren't clearly answered.
First and foremost is,why with Sammy's phones we have to use Odin?ClockworkMod on HTC devices is excellent and very easy to use.What's the reason to use Odin?Samsung packaging their roms differently or something or a security thing?
Second is,why do I keep seeing many bricked Samsung phones?I have read about many people who,as they say themselves,were foolish enough to brick it.Is it that easy?With HTC's phones it's only possible when messing with bootloader if something goes horribly wrong,or when someone is foolish enough to pull the battery when updating baseband(or radio,call it whatever you want).
If someone can answer or point me to somewhere where I can find satisfactory answers I would appreciate it!Thanks!
Regards,
Apostolis
PS:Sorry for my English.Not that there's anything wrong with it in general,but I tend to speak in a very weird and complicated way when I am tired.And now,I am really tired!
NO CLOCKWORK for SGS 2 yet .
Donate SGS2 to developer .
jje
Where did you read sgs2 were getting bricked? The term was used to loosely with the orginal galaxy s phones. The original sgs was 99.9% unbrickable and I wouldnt doubt the sgs2 is the same.
Clockwork will come with time. Odin is just samsung way of upgrading there handsets. Once real custom roms come youll probably see clockwork.
Most of the so called bricks were pure user error.
intruda119 said:
Where did you read sgs2 were getting bricked? The term was used to loosely with the orginal galaxy s phones. The original sgs was 99.9% unbrickable and I wouldnt doubt the sgs2 is the same.
Clockwork will come with time. Odin is just samsung way of upgrading there handsets. Once real custom roms come youll probably see clockwork.
Most of the so called bricks were pure user error.
Click to expand...
Click to collapse
Well,I'd say all bricks are pure user error!
I can't give you exact time and post,but there were some reports.Not that the amount of people reporting this was anything shocking,but anyway.One particular guy wanted to unbrick his Vibrant with JTAG.Maybe Galaxy S variants are more "vulnerable"?
Also,about CWM I didn't know.I thought that Odin was still being used on the original Galaxy S.I only followed the GS forums at the beggining.
Odin is just a great tool to update firmware or get you out of bad situations. Theres mixed reviews about odin but its something you need to get familiar with if your hacking with any galaxy s line. Most bricks that wasnt recoverable needed jtag but that was when someone flashed something they shouldnt have. If you want to start with stock firmware you want to use odin. Alot of people like clearing out the ghost files left with custom roms. So they start fresh with odin original firmware before flashing new roms. You dont have to but you can usually avoid some bugs with a fresh firmware. Im not an expert at this but hopefully helps out some.
tolis626 said:
Well,I'd say all bricks are pure user error!
I can't give you exact time and post,but there were some reports.Not that the amount of people reporting this was anything shocking,but anyway.One particular guy wanted to unbrick his Vibrant with JTAG.Maybe Galaxy S variants are more "vulnerable"?
Also,about CWM I didn't know.I thought that Odin was still being used on the original Galaxy S.I only followed the GS forums at the beggining.
Click to expand...
Click to collapse
intruda119 said:
Odin is just a great tool to update firmware or get you out of bad situations. Theres mixed reviews about odin but its something you need to get familiar with if your hacking with any galaxy s line. Most bricks that wasnt recoverable needed jtag but that was when someone flashed something they shouldnt have. If you want to start with stock firmware you want to use odin. Alot of people like clearing out the ghost files left with custom roms. So they start fresh with odin original firmware before flashing new roms. You dont have to but you can usually avoid some bugs with a fresh firmware. Im not an expert at this but hopefully helps out some.
Click to expand...
Click to collapse
Ahaa...So it's not THAT different to modding HTC devices,is it?
tolis626 said:
Ahaa...So it's not THAT different to modding HTC devices,is it?
Click to expand...
Click to collapse
If there's a CWM-featured Kernel, then yes!
OK, so I have the Galaxy Tab 2 7.0 (I couldn't find a 7.0 section here, so I picked the next closest) it's not through any phone company. I tried to root, but it failed, so I did a restore bluh bluh bluh. Once I restored I went to update to the latest for my device. It said my system has been modified so there is no update (something along those lines). What do I do to fix this? This is my first android device and I am trying to learn the ropes. I hope I didn't mess this up too badly. Thanks for the help.
wwe9112 said:
OK, so I have the Galaxy Tab 2 7.0 (I couldn't find a 7.0 section here, so I picked the next closest) it's not through any phone company. I tried to root, but it failed, so I did a restore bluh bluh bluh. Once I restored I went to update to the latest for my device. It said my system has been modified so there is no update (something along those lines). What do I do to fix this? This is my first android device and I am trying to learn the ropes. I hope I didn't mess this up too badly. Thanks for the help.
Click to expand...
Click to collapse
Since you have a Galaxy Tab 2, then you need to ask your questions in the Galaxy Tab 2 section of the forums. Anything you install from this section of the forum isn't likely to work on your device.
Short answer to your question - you need to use Triangle Away to fix this.
k1mu said:
Since you have a Galaxy Tab 2, then you need to ask your questions in the Galaxy Tab 2 section of the forums. Anything you install from this section of the forum isn't likely to work on your device.
Short answer to your question - you need to use Triangle Away to fix this.
Click to expand...
Click to collapse
Sorry, I didn't see the tab 2 forum. My apologies. But thank you. I will ask over there to get a more detailed set of instruction set. Thanks again!
Well... with the risk of getting flamed... I really would like to get some advice Before I get started.
My Galaxy S3 is network locked to Three 3 Sweden. My first question... is this something I have to consider when rooting? I´m not concerned about warrantys and so on... my soul purpose is to get rid of some bloatware, ads and perhaps modifying a little. Not really flashing ROM´s as of yet, but who knows...
I would really like it if someone could point me in the right direction when it comes to files and so on, that I need.
My phone:
Android Version 4.1.2
Baseband I9300NELK2
Version 3.0.31-742798
Compilationnumber JZ054K.I9300XXELLA
Some hints and tips would be nice.
First time on a S3 but far from first phone to root.
=> General Section, stickies, how to root etc. all included in there
chrismast said:
=> General Section, stickies, how to root etc. all included in there
Click to expand...
Click to collapse
Yes I know... but my head question was legit:
My Galaxy S3 is network locked to Three 3 Sweden. My first question... is this something I have to consider when rooting?
Click to expand...
Click to collapse
That has nothing to do with network. Rooting and sim unlock are two different things.
US Cellular LTE SG3 - SCHR530, Was build ALK5 on 4.1.1 and was rooted (using free version mskip's Toolkit) and all was fully functional. When the 4.1.2 android update became available for my phone, I performed manual 4.1.2 download/installation, which completed successfully. Build AMD4.
Donated/upgraded to mskip's pro version Toolkit. Began the re-root - exact build wasn't listed, picked closest, completed process, phone was rooted BUT lost all access to camera and any apps that use camera failed due to camera fail. Unable to find a cure for this particular issue, I used the toolkit to unroot my phone. I RE-applied Samsung android update 4.1.2 and have remained UNrooted until last night.
Ran the Toolkit, toolkit auto-updated to the latest version released (says 4.1.2 build AMD4 is supported) , prepared to root phoneagain I find this exact build (AMD4) is not listed, so picked closest one, completed process, phone is rooted..... BUT AGAIN I have no use of camera!
How can I fix this and stay rooted? Or do I resign myself to not having a rooted phone in order to keep functionality of my camera?
Thanks for any helpful insights to this issue.
SAME issue
firstbrick said:
US Cellular LTE SG3 - SCHR530, Was build ALK5 on 4.1.1 and was rooted (using free version mskip's Toolkit) and all was fully functional. When the 4.1.2 android update became available for my phone, I performed manual 4.1.2 download/installation, which completed successfully. Build AMD4.
Donated/upgraded to mskip's pro version Toolkit. Began the re-root - exact build wasn't listed, picked closest, completed process, phone was rooted BUT lost all access to camera and any apps that use camera failed due to camera fail. Unable to find a cure for this particular issue, I used the toolkit to unroot my phone. I RE-applied Samsung android update 4.1.2 and have remained UNrooted until last night.
Ran the Toolkit, toolkit auto-updated to the latest version released (says 4.1.2 build AMD4 is supported) , prepared to root phoneagain I find this exact build (AMD4) is not listed, so picked closest one, completed process, phone is rooted..... BUT AGAIN I have no use of camera!
How can I fix this and stay rooted? Or do I resign myself to not having a rooted phone in order to keep functionality of my camera?
Thanks for any helpful insights to this issue.
Click to expand...
Click to collapse
I am having the exact same issue, I need my camera and my root, might have to go back to 4.1.1 to get it though.
I'm also on a donated toolkit, please post if you find a solution.
This is the i9300 forum, you are in the wrong place. Also have you tried contacting mskip to raise a query?
Re: Camera Failure following mskip Toolkit use to root
slaphead20 said:
This is the i9300 forum, you are in the wrong place. Also have you tried contacting mskip to raise a query?
Click to expand...
Click to collapse
Thank you for your acknowledgement, I truly appreciate it.
I did know this is the i9300 forum, and I have tried to contact mskip a number of times, including directly in the thread that the most recent toolkit was announced. Apparently I cannot post in there (?) due to not having enough posts and not being a developer; at least that's what the "error message" is when I tried. And then the advisement that I must post questions in a Q & A. I guess I'm lost!
In any case, I did several searches for the camera issue combined with rooting and I ended up in this forum. I would greatly appreciate it if you could steer me towards the proper place to post - I haven't seen a specific forum for the US Cellular model SG3, and I'll admit - I'm greatly out of practice these days in my forum using skills.
Follow up - help for root w/toolkit camera lost issue
firstbrick said:
Thank you for your acknowledgement, I truly appreciate it.
I did know this is the i9300 forum, and I have tried to contact mskip a number of times, including directly in the thread that the most recent toolkit was announced. Apparently I cannot post in there (?) due to not having enough posts and not being a developer; at least that's what the "error message" is when I tried. And then the advisement that I must post questions in a Q & A. I guess I'm lost!
In any case, I did several searches for the camera issue combined with rooting and I ended up in this forum. I would greatly appreciate it if you could steer me towards the proper place to post - I haven't seen a specific forum for the US Cellular model SG3, and I'll admit - I'm greatly out of practice these days in my forum using skills.
Click to expand...
Click to collapse
Still no love for my issue, and almost a month later, still the choice of root & no cameras or cameras & no root :crying:
Toolkit support says US CELLULAR MODEL LTE[SCH-R530] support should use AT&T, Rogers, Bell, Telus Samsung Galaxy S III forum, can anyone verify for me if that is the correct place to try to post about my problem? Thank you very much!
firstbrick said:
Still no love for my issue, and almost a month later, still the choice of root & no cameras or cameras & no root :crying:
Toolkit support says US CELLULAR MODEL LTE[SCH-R530] support should use AT&T, Rogers, Bell, Telus Samsung Galaxy S III forum, can anyone verify for me if that is the correct place to try to post about my problem? Thank you very much!
Click to expand...
Click to collapse
See sticky top of the page if its not in there try Google your model xda.
Apparently I cannot post in there (?) due to not having enough posts
you should have now
Try one of the other methods of root and recovery like TWRP .
Google finds
http://forum.xda-developers.com/wik.../SCH-R530#XDA-Developers_Forums_for_the_Phone
JJEgan said:
See sticky top of the page if its not in there try Google your model xda.
Apparently I cannot post in there (?) due to not having enough posts
you should have now
Try one of the other methods of root and recovery like TWRP .
Google finds
http://forum.xda-developers.com/wik.../SCH-R530#XDA-Developers_Forums_for_the_Phone
Click to expand...
Click to collapse
It does seem that most of that info is out of date and there is no real home for the US Cellular LTE Samsung Galaxy S3, and as far as the other methods, I am just not that savvy - the automated toolkit is slick, but I appreciate your suggestions. Thank you.
Hello, this is my first time posting on here.
I have an old Galaxy S3, USA version, T-mobile, SGH-T999. I was wondering how to update it to make it usable? From what I've read online the best way is to root and put in a custom ROM. The problem I'm having is finding the latest ROMs. Is there any way to find the latest official ROMs for the phone? And if I download an unofficial one, how can I know which will run well on my phone? Do I just simply get the latest unofficial ROM?
Lastly, if any one has any step by step guide or video on how to root and install ROMs it would be much appreciated as I've never done something like this before. Sorry if this has been posted before, I'm new to this site and have been having trouble navigating and searching old posts.
Thank you.
Samsung Galaxy TAB S3
hasnain hasnain hasnain said:
Hello, this is my first time posting on here.
I have an old Galaxy S3, USA version, T-mobile, SGH-T999. I was wondering how to update it to make it usable? From what I've read online the best way is to root and put in a custom ROM. The problem I'm having is finding the latest ROMs. Is there any way to find the latest official ROMs for the phone? And if I download an unofficial one, how can I know which will run well on my phone? Do I just simply get the latest unofficial ROM?
Lastly, if any one has any step by step guide or video on how to root and install ROMs it would be much appreciated as I've never done something like this before. Sorry if this has been posted before, I'm new to this site and have been having trouble navigating and searching old posts.
Thank you.
Click to expand...
Click to collapse
I suspect the reason that you haven't gotten any responses in the last day or so is that you are on the wrong part of the Forum! This is the area for the Samsung Galaxy Tab S3 9.7" Tablet, not the Galaxy S3 Smartphone.
You might want to take a look over here for the T-Mobile S3.
Hope that helps clear things up
DuncDog said:
I suspect the reason that you haven't gotten any responses in the last day or so is that you are on the wrong part of the Forum! This is the area for the Samsung Galaxy Tab S3 9.7" Tablet, not the Galaxy S3 Smartphone.
You might want to take a look over here for the T-Mobile S3.
Hope that helps clear things up
Click to expand...
Click to collapse
Oh wow my bad lol, thank you for letting me know!