I've spent an hour searching for something to explain what bootchains are. I want to understand how they allow the S3 to be rooted and why you need to put them back when you're done. But I'd settle just for a simple what are they.
TommyTFC said:
I've spent an hour searching for something to explain what bootchains are. I want to understand how they allow the S3 to be rooted and why you need to put them back when you're done. But I'd settle just for a simple what are they.
Click to expand...
Click to collapse
A bootchain is the process your phone takes in order to boot. Flashing a specific bootchain is the bootchain available at the time when it was released.
It specifically tells the phone to boot through a series of steps in order to make sure the phone is running correct files. If any part of the chain is broken, the phone won't be able to boot up.
An example which we bypass on our specific phone is the aboot step in the bootchain. To unlock the phone, we simply flash a modified aboot file that makes the phone think it's running the correct rom and kernel. Aboot is only one part of the bootchain.
Hope that makes sense.
Sent from my SCH-I535 using Tapatalk 2
So the files in the tar are programs and they each execute in turn?
The rooting instructions say it doesn't matter if you put the original back. Know why?
Sent from my SCH-I535 using xda app-developers app
TommyTFC said:
So the files in the tar are programs and they each execute in turn?
The rooting instructions say it doesn't matter if you put the original back. Know why?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Basically you got it. That's exactly what's in the tar file.
I'm not really sure how exactly the new rooting process works the way it does, but I know it has something to do with breaking the chain and allowing it to inject a superuser app and recovery. The original bootchain blocks this process and doesn't allow superuser permission. ICS allowed this, which is why it was easier to root it. JB blocks this method, which is why a modified bootchain is needed.
I'm only assuming, but restoring to the original bootchain is simply recommended because it's what should be on the phone. If there's something wrong with the modified bootchain then it may break your booting checkpoints. You're probably safe not restoring it, but you can be sure you're safe if you do restore it.
Sent from my SCH-I535 using Tapatalk 2
Yea you should restore the original bootchains. You want to be original.
Did a search, and this was the best thread I could find.
I'm looking to root, and know that I need to download the correct bootchain.
Question: How do I determine which one that is?
I'm running the (new, awful) version of 4.1.2 that just updated my Verizon Galaxy S3. Currently, I'm stock... but not for long.
Thanks for the assistance.
ccstra54 said:
Did a search, and this was the best thread I could find.
I'm looking to root, and know that I need to download the correct bootchain.
Question: How do I determine which one that is?
I'm running the (new, awful) version of 4.1.2 that just updated my Verizon Galaxy S3. Currently, I'm stock... but not for long.
Thanks for the assistance.
Click to expand...
Click to collapse
You can get everything you need from the S3 link in my signature. Instructions are there also.
If anyone is more curious about this, you should google "2nd-init" or "milestone bootchain" theres a couple good blogs/posts discussing how they got past the locked boot loader on the Motorola Droid/ milestone.
Related
EDIT: Thanks guys, I no longer have this need. Thank you
Folks,
I'm trying to generate a root method that doesn't trip the flash counter in the download mode. If you boot in the download mode, there's a counter for how many non-stock flashes you've done. Anyone here who has rooted has likely tripped this counter and is at least at "1" if not more.
One of the devs helping me with my work has requested a partition from a non-tripped phone, but that of course would require having root. So I've created a flashable stock samsung rom with root injected. But I need help testing it.
The counter is one of those things that could get your support request denied if you ever have to take your phone in for repair.
Mind you... if the test doesn't work, the phone will have it's counter tripped... and that's all on you. I can't be held responsible. I mean, I suppose you could hate me, but it's your own fault for helping
Any takers?
Any phone can meet this requirement by flashing the reset counter package that used to be on here... I think someone linked the package and it's in the themes area. Then the flash counter will now say 'no' but it will still say custom binary. To remove this flash back to stock and update to ics via kies. Then the flash counter will say no and binary will say Samsung official. Hope that will help.
Edit: if the reset counter is no longer there I believe it's the same as the sgs2 (I think that's where the OP pulled it from when they posted it in the themes area). Or if you want I could put the copy I have on dropbox and link it here.
Sent from my SGH-T769 using xda app-developers app
We reposted it since the douche op went crazy.
I'm about to roor my roommatesblaze. Never been rooted.what do I need to do
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
chjema said:
We reposted it since the douche op went crazy.
I'm about to roor my roommatesblaze. Never been rooted.what do I need to do
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
ahhh, ok, lemme find a place to upload my modded root injected tarball.
Mostly, I want to make sure that, if you go into download mode, it says that the counter is at 0. If it's not at 0, then this is pointless
The idea is to upgrade to the latest version through kies. Either that or do a data reset/wipe and then stop the phone from booting when it goes to reboot.
Then, boot into download mode and flash my root injected tar through odin. Once that's done, when you reboot, it should be rooted. If you then go into download mode again, the counter should still be at 0.
If this is the case, then I'll ask you to get me the contents of a partition on your phone.
For now, lemme find a place to upload my tar to. It's huge.
EDIT: Wait... just saw the other stuff... lemme try doing that. If it doesn't work for me, we'll proceed
Still need help? She really wants to root her phone.
chjema said:
Still need help? She really wants to root her phone.
Click to expand...
Click to collapse
The method for resetting in the themes & apps section works fine. Use that
dr4stic said:
The method for resetting in the themes & apps section works fine. Use that
Click to expand...
Click to collapse
No I meant you wanted some testing help with something, I dont care about resetting flash numbers just thought you said you need a virgin un rooted phone. If not Ill flash Tweaked on it. Just making sure because you said you wanted a untouched partition.
chjema said:
No I meant you wanted some testing help with something, I dont care about resetting flash numbers just thought you said you need a virgin un rooted phone. If not Ill flash Tweaked on it. Just making sure because you said you wanted a untouched partition.
Click to expand...
Click to collapse
Oh, thanks, Yeah. Was just trying to generate that partition.
I have a 600M tar file you could flash with odin and wouldn't trip the counter, but it'd take 2 hours to upload, and I'd need somewhere to upload, which is near impossible at that size.
The partition flash that's in themes & apps is for the T989, so maybe there's some bad identifying information there, who knows. While it'd be nice to have an exact version for our phone, that method is good enough for me and for the dude asking me for it
Thanks though!
You could try adrive.com it allows 2gb per file, though I'm not sure on the speed side of things. Seems they have an Android app too.
Lol no worries. I've sent back three phones so far with that other flash. Worked just fine
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
see then, no worries... now can we let this thread die?
I've searched (perhaps incorrectly) for more info on the bootchain for the S3, but haven't been able to find the answer to my question.
On the VZW SGS3, is there a way to determine which bootchain I'm currently using? I had the triangle issue a while back and had to use odin to replace the bootchain, but recently read that we should always use the latest bootchain. So, how do I determine if I'm using the latest bootchain?
Thanks
Bootchain can be as old or new as you want so long as aboot is VRALE6
Whoever told you to use the newest bootchain in its entirety has no idea what they were talking about
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
LLStarks said:
Bootchain can be as old or new as you want so long as aboot is VRALE6
Whoever told you to use the newest bootchain in its entirety has no idea what they were talking about
Click to expand...
Click to collapse
That's great, but how does one determine the version currently in use? How does one determine the version of aboot?
ddog511 said:
That's great, but how does one determine the version currently in use? How does one determine the version of aboot?
Click to expand...
Click to collapse
dead silence...I would also like to know the answer to the question. Anyone?
dweezle said:
dead silence...I would also like to know the answer to the question. Anyone?
Click to expand...
Click to collapse
There isn't much information on finding your bootchain partitions to be blunt. Can't say I'm surprised either because there's not much reason, as a general rom user, to care about your bootchain once you've successfully done the root/unlock process.
Now if you want to know the aboot (slightly different, this is the bootloader) then if you're rooted and unlocked you are using the VRALE6 bootloader. We all are in order to flash roms and kernels. If you're just rooted AND NOT unlocked then doing this is probably a good start. This table also tells you where the bootloader is btw.
SlimSnoopOS said:
There isn't much information on finding your bootchain partitions to be blunt. Can't say I'm surprised either because there's not much reason, as a general rom user, to care about your bootchain once you've successfully done the root/unlock process.
Now if you want to know the aboot (slightly different, this is the bootloader) then if you're rooted and unlocked you are using the VRALE6 bootloader. We all are in order to flash roms and kernels. If you're just rooted AND NOT unlocked then doing this is probably a good start. This table also tells you where the bootloader is btw.
Click to expand...
Click to collapse
Why I was interested was because I flashed VRALEC using Odin 3.07 and installed TWRP. I rooted and unlocked the phone using TWRP. Then I wanted to return to the original 4.1.2 bootchain (VRBMB1). I flashed it using Odin (at least I thought I did). Later I was using an app called Network Signal Info which showed my bootloader as i535VRALEC. That's why I wanted some way of knowing whether my bootchain was still VRALEC or if I had successfully flashed to VRBMB1.
I hope I've explained this clearly. I feel like I am reading a foreign language from a phrase book. I might be pronouncing the words correctly but I am still don't exactly know what I might be saying. I love this stuff.
dweezle said:
Why I was interested was because I flashed VRALEC using Odin 3.07 and installed TWRP. I rooted and unlocked the phone using TWRP. Then I wanted to return to the original 4.1.2 bootchain (VRBMB1). I flashed it using Odin (at least I thought I did). Later I was using an app called Network Signal Info which showed my bootloader as i535VRALEC. That's why I wanted some way of knowing whether my bootchain was still VRALEC or if I had successfully flashed to VRBMB1.
I hope I've explained this clearly. I feel like I am reading a foreign language from a phrase book. I might be pronouncing the words correctly but I am still don't exactly know what I might be saying. I love this stuff.
Click to expand...
Click to collapse
Ahh, I replied to you in Open's thread as well. Don't worry, I wasn't helpful there lol BUT Open has actually explained this better than I could have as another user noticed same as well. Read his reply (post #569). Also, could you remove the pic with your IMEI or at least blur out the IMEI? That's actually sensitive stuff for you and someone could actually do bad things with your IMEI. Try not to post your IMEI in the future unless it's significantly changed.
Hi, all. I rooted my continuum a couple of years ago via Odin, so I've done it once and I'm not afraid of it. But now I have a GS3 with the new MF1 update. I want to root so I can get rid of the VZW junk and find the best tethering option. I paid $400 for my phone instead of upgrading with Verizon so I can keep my unlimited data, so I'm not about to wantonly brick it, which is why I'm asking dumb questions!
1) Can I root without unlocking the bootloader? The reason why I'm asking is that I don't want to flash any custom roms at this time, just clean out the bloatware and have SU. Or am I mistaken...I thought the only reason to unlock it was to install a custom recovery, but that the recovery is only needed to flash a custom rom, not to root it.
1a) If I can root without unlocking the bootloader, which is the best way?
I went through [GUIDE] Root for Jelly Bean 4.1.1 or 4.1.2 OTA ***UPDATED 5/29*** here --> http://forum.xda-developers.com/showthread.php?t=2046439
But it seems that the VRBMF1 bootchain is not available yet. Someone mentioned flashing mb1 with Odin, and then using the mb1 bootchain to root, but that seems counterintuitive if I don't plan on then flashing a custom rom.
1b) What would happen if I flashed a different bootchain than the version I currently have and tried rooting?
2) If my phone is soft-bricked, as has happened to a couple of people using the Casual method, is it possible/hard to unbrick it?
3) I have baseband VRBMF1, but I noticed that with the Casual method, whoever did it in the video had VRBMA2. Now, I understand that the baseband version is independent of the firmware, but can the baseband version interfere with the rooting process, for instance using the Casual method?
Also, the main reason why I haven't done Casual is that it bricked a few phones. I'm not opposed to having a custom recovery, as would be installed with Casual, but given the few failures, I'm not eager to try it.
4) I've been using PDANet+ to tether, but I'm not convinced that using PDANet with wifi is good, as it seems to use the phone's hotspot (unlike using the USB function in the app). What is the best way to hide tethering from Verizon? And are there better options available to root users?
Thanks for any advice!
You have the guide you need. Just follow the directions. You can root without unlocking boot loader. If you unlock the boot loader then you can flash a custom Rom that has built in tether feature if you don't want to use pda. I would just bite the bullet and do casual. It really is fool proof.
Sent from my SCH-I535 using Tapatalk 2
bbqsfire said:
You have the guide you need. Just follow the directions. You can root without unlocking boot loader. If you unlock the boot loader then you can flash a custom Rom that has built in tether feature if you don't want to use pda. I would just bite the bullet and do casual. It really is fool proof.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the reply. I agree with you about having the guide I need for the Odin method, but I still don't have the correct bootchain. Will another work? And the casual root does seem foolproof, except for the few bricks. No one has identified what caused those, whether some java issue, or something else.
So if I used the Odin method, does it matter which bootchain for 4.1.2 I use, either MB1 or MD3, considering i'm on MF1?
hturbulence said:
Thanks for the reply. I agree with you about having the guide I need for the Odin method, but I still don't have the correct bootchain. Will another work? And the casual root does seem foolproof, except for the few bricks. No one has identified what caused those, whether some java issue, or something else.
So if I used the Odin method, does it matter which bootchain for 4.1.2 I use, either MB1 or MD3, considering i'm on MF1?
Click to expand...
Click to collapse
It will not matter because you can flash the radio later. You will be flashing an older bootchAin but once you flash a Rom and the radio you are fine.
Sent from my GT-P5113 using xda premium
If the bootchain doesn't matter, why are there different versions? I'm not so concerned about the radio because that doesn't change with rooting, does it? I guess my question would be, if I'm on the VRBMF1 build, and say I used the VRBMD3 bootchain, would everything go as planned? I mean, doesn't the bootchain just tell the phone in which order to use files for boot?
I really appreciate your help!:good:
I came from the continuum too, have to say I miss the ticker, but not the lack of RAM!
I used this method to root my S3:
http://forum.xda-developers.com/showthread.php?t=1984436
Used the first link (mb1 no wipe). It is Stock, locked bootloader, stock recovery, rooted. Then I used OTA Rootkeeper (from play store) to back up root. Then I took the OTA to MF1. This will get you to the latest stock firmware with root. You can unlock the bootloader and install a custom recovery later if you want, which is what I did. . No issues for me so far.
Sent from my SCH-I535 using xda app-developers app
Thanks for the info. I actually rooted with casual about an hour ago. I was nervous about the casual method because of the few bricks with MF1, but I gave it a shot, and it worked.
Now, just have to figure out best way to tether without VZW knowing!
Sent from my SCH-I535 using xda app-developers app
So I've been using an HTC MyTouch 4G for the past few years and had the rooting/flashing process down with that phone, but I recently switched to the Verizon variant of the Samasung Galasy S III and have run into an issue trying to root and flash an aftermarket rom to this device.
As per the CM Wiki for my device, I need to install and use Heimdall to downgrade the bootloader. I'm not new to using the terminal, so I figured this wouldn't be a difficult step, however I can't get Heimdall to work even after many attempts to download just the binary from the CM wiki, download the entire package including the frontend directly from the website Heimdall is hosted on, and even after compiling directly from source.
After trying to install it many different times/ways, I'm running into the same error every single time. After opening the terminal and trying to execute any command pertaining to Heimdall (Heimdall help, Heimdall detect, etc.) I get a response of "Illegal Instruction." I cannot get it to do ANYTHING other than to respond with "Illegal Instruction."
It's driving me mad because all I need Heimdall for at this point is to downgrade the bootloader.
I know I must be making some very minute error, but I can't figure it out.
Just a bit more information: I'm running OSX 10.6 so the current Heimdall Frontend is not compatable, so I have to use the Terminal (which I'd rather do anyways because I have more control that way.)
Any help or isight would be appreciated.
Thanks!
Just use the casual script instead of trying to downgrade
Sent from my SCH-I535 using Tapatalk 4 Beta
If I've helped, please hit the thanks button
tylerlawhon said:
Just use the casual script instead of trying to downgrade
Sent from my SCH-I535 using Tapatalk 4 Beta
If I've helped, please hit the thanks button
Click to expand...
Click to collapse
Casual script? Mind elaborating or guiding me in the right direction?
checkthisSH said:
Casual script? Mind elaborating or guiding me in the right direction?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2332825
You shouldn't need to do anything with the bootloader, use this to load a custom recovery, then flash the cm10 image for the Verizon sgs3.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
http://forum.xda-developers.com/showthread.php?t=2332825
You shouldn't need to do anything with the bootloader, use this to load a custom recovery, then flash the cm10 image for the Verizon sgs3.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for getting back to me so quickly.
According to the CM Wiki and a couple of other sources I can't think of at the moment, if I'm coming from stock/no root, I would need to load an older bootloader before flashing recovery and ultimately flashing CM10.
The Samsung root process is a bit different from some of the other phones I have worked with. Would you mind explaining to me why I wouldn't need to load an older bootloader?
Edit: After taking a look into the thread you provided for me I may have answered my own question. Loading the older bootloader is probably essential to getting the exploit to work with Heimdall, right? But not with the Casual exploit?
checkthisSH said:
Thanks for getting back to me so quickly.
According to the CM Wiki and a couple of other sources I can't think of at the moment, if I'm coming from stock/no root, I would need to load an older bootloader before flashing recovery and ultimately flashing CM10.
This process is a bit different from some of the other phones I have worked with. Would you mind explaining to me why I wouldn't need to load an older bootloader?
Click to expand...
Click to collapse
I've never seen those instructions before, but i would try posting this In the cm10 question and answer thread.
That could also be old instructions, find the cm10 development thread and see what the latest instructions are for installation.
I've never used heimdall and couldn't give you instructions how to use it, using odin to flash those would be significantly easier if you can get access to a window computer.
Either way, that process won't achieve root anyway. You're better off running casual first to get a custom recovery and root access, then run that process later if needed.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
I've never seen those instructions before, but i would try posting this In the cm10 question and answer thread.
That could also be old instructions, find the cm10 development thread and see what the latest instructions are for installation.
I've never used heimdall and couldn't give you instructions how to use it, using odin to flash those would be significantly easier if you can get access to a window computer.
Either way, that process won't achieve root anyway. You're better off running casual first to get a custom recovery and root access, then run that process later if needed.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
In theory, and please correct me if I'm wrong, but it looks like I should be able to use Casual up until I need to flash CM10. Which is as simple as throwing the .zip file onto my SD card and installing from recovery. That way I probably won't even have to touch Heimdall.
The only thing that concerns me is that following the CM wiki instructions has you flash an older kernel as well. Again, this appears to me like it could only be required to load the customer recovery using Heimdall, but I'm not entirely sure.
I'll have to look around for the CM10 dev thread around here because the one on the CM forum is a ghost town.
Thanks again for all of your help!
checkthisSH said:
In theory, and please correct me if I'm wrong, but it looks like I should be able to use Casual up until I need to flash CM10. Which is as simple as throwing the .zip file onto my SD card and installing from recovery. That way I probably won't even have to touch Heimdall.
The only thing that concerns me is that following the CM wiki instructions has you flash an older kernel as well. Again, this appears to me like it could only be required to load the customer recovery using Heimdall, but I'm not entirely sure.
I'll have to look around for the CM10 dev thread around here because the one on the CM forum is a ghost town.
Thanks again for all of your help!
Click to expand...
Click to collapse
That's exactly what I'm saying. However, the whole thing is confusing to me also. It seems weird that you'd need an older bootloader in order to run the rom.
Just make a backup before you flash in recovery, then if it won't run at least you have a way to get a working phone.
The kernel should have nothing to do with anything, as soon as you flash cm10 it'll get overwritten with the cm10 stock kernel.
Also make sure that the bootloader is unlocked before you flash, or you'd have to odin back to stock.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
That's exactly what I'm saying. However, the whole thing is confusing to me also. It seems weird that you'd need an older bootloader in order to run the rom.
Just make a backup before you flash in recovery, then if it won't run at least you have a way to get a working phone.
The kernel should have nothing to do with anything, as soon as you flash cm10 it'll get overwritten with the cm10 stock kernel.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I'm assuming it has something to do with using Heimdall, and if that's the case, I don't know why anyone would ever want to use that method when it is clearly more difficult. Maybe someone else can weigh in on the topic.
Thanks again for the solid advice. I'll take the Casual route and see where it takes me.
BadUsername said:
That's exactly what I'm saying. However, the whole thing is confusing to me also. It seems weird that you'd need an older bootloader in order to run the rom.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
FYI, every rooted and unlocked Verizon GSIII is using a pre-release unlocked bootloader so you're using an older bootloader already.
Sent from my SCH-I535 using Tapatalk 4 Beta
SlimSnoopOS said:
FYI, every rooted and unlocked Verizon GSIII is using a pre-release unlocked bootloader so you're using an older bootloader already.
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
You mean once you unlock the phone with an old aboot file right? The newer phones would have a newer bootloader until you change it.
The instructions are really confusing because they're instructing to downgrade the bootloader to inject an aboot file and custom recovery. I still think that entire step is unnecessary.
Sent from my SCH-I535 using Tapatalk 2
Hello everyone, so I have a couple questions for you guys in regards to rooting my S3. Back in November when I got the phone, I had rooted it and unlocked it using Odin and the EZ-Unlock app off of the play store. Not long after that, i returned back to stock, and here we are 6/7 months later and I am wanting to re-root, but I have discovered that the way to go about this has since changed.
I have looked at this guide http://forum.xda-developers.com/showthread.php?t=2046439 and looked at these videos http://forum.xda-developers.com/showthread.php?t=2295146 but am still a little iffy about jumping right into this since the methods involved are different than the last time I did it. One thing I noticed on the guide that I linked is that they do not have the bootchain for the version on my phone (VRBMF1).
Basically so this thread does not turn into a short story, I am just going to ask if the steps I lay out is the correct way to go about this. I am strictly wanting to root and unlock so that I can flash to a custom ROM, mainly CM10.
1. install samsung drivers
2. download Odin
3. download the "both root and unlocked bootloader"
4. download VRALEC bootchain
5. download either CWM or TWRP
6. and for this step, should I just flash to either VRBMB1 or VRBMD3, or should I just skip this step since it is optional and go straight to flashing a custom ROM?
In addition to this, I have heard things mentioned about backing up the IMEI, and I see them saying you can do it in a Terminal Emulator (the su and reboot nvbackup commands) . Is this something that has to be done after root and unlock?
I would love to get back to rooted and running custom ROMS again, so any help you can provide would be greatly appreciated.
Bump.
Flash the VRBMD3 bootchain and backup your IMEI after rooting and unlocking the bootloader but before flashing a custom ROM.
Thanks for your reply. Is there any benefit to flashing the md3 bootchain if I am just going to be flashing to a custom ROM?
Sent from my SCH-I535 using Tapatalk 2
The boot chain makes a great stable platform before you go off on a custom. That way you can boot and make sure the root has taken
Sent from my SCH-I535
Lord_Tardis said:
The boot chain makes a great stable platform before you go off on a custom. That way you can boot and make sure the root has taken
Sent from my SCH-I535
Click to expand...
Click to collapse
Thanks for your reply. I am happy to report that I listened and flashed the VRBMD3 bootchain and am successfully unlocked and rooted and am running a custom ROM. I did not know that the bootchain would have an effect after I had flashed a custom ROM, so I am glad that I did that. Thanks for your replies everyone. One question though. Since my baseband version is VRBMF1, is there any downside to flashing the VRBMD3 bootchain or does it really matter?
Atwooooood said:
Thanks for your reply. I am happy to report that I listened and flashed the VRBMD3 bootchain and am successfully unlocked and rooted and am running a custom ROM. I did not know that the bootchain would have an effect after I had flashed a custom ROM, so I am glad that I did that. Thanks for your replies everyone. One question though. Since my baseband version is VRBMF1, is there any downside to flashing the VRBMD3 bootchain or does it really matter?
Click to expand...
Click to collapse
The mf1 is the most current radio data. I do not believe there is harm in flashing to an older one. The best bet is to find the one that gives you the best signal strength.
Sent from my SCH-I535
If I wanted to test a couple bootchains as far as signal strength goes , am I able to flash to a different one after I've already flashed a custom ROM or are there more steps involved?
Sent from my SCH-I535 using Tapatalk 2
Correct me if I'm wrong. But bootchains do not affect signal. Only modems/basebands. You can go download any which one as long as kids meant for your model/carrier.
Sent from my SCH-I535 using Tapatalk 4
Sandman-007 said:
Correct me if I'm wrong. But bootchains do not affect signal. Only modems/basebands. You can go download any which one as long as kids meant for your model/carrier.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
You, sir, are correct.
Sent from my SCH-I535 using xda app-developers app
Thanks for clarifying guys. Appreciate your alls help.
Sent from my SCH-I535 using Tapatalk 2