Related
I understand that this may have been asked, and I've been looking at similar threads, but I'm having a hard time finding a direct answer, so I apologize.
I have some experience rooting with an Atrix, but I just got this phone two days ago, this morning I used the 1-click method from rootwhiz to install the ICS leak. No problems having it run at all. I need to know, directly, did this install change my bootloader and change the binary count? I can't remember if I saw anytime of yellow triangle as people talk about. If it changed the bootloader what is there a safe method to return to the older bootloaders, and or do I even need to do so to root and install other roms?
I know that the Atrix had some problems in terms of returning to prior versions of things, and in my research I haven't found a direct answer to this question too.
Basically, did my bootloader change? Can I root using the heimdall method I keep seeing about safely? What would be the best way to root and install custom roms, neglecting the binary counter if I can get a jig or something?
Forgive me again for asking, I just need to have better answers before I try anything.
Are you asking for info for your Atrix or SGS2 device?
Sorry, I am asking about the SGS2.
ds1904.ds said:
I understand that this may have been asked, and I've been looking at similar threads, but I'm having a hard time finding a direct answer, so I apologize.
I have some experience rooting with an Atrix, but I just got this phone two days ago, this morning I used the 1-click method from rootwhiz to install the ICS leak. No problems having it run at all. I need to know, directly, did this install change my bootloader and change the binary count? I can't remember if I saw anytime of yellow triangle as people talk about. If it changed the bootloader what is there a safe method to return to the older bootloaders, and or do I even need to do so to root and install other roms?
I know that the Atrix had some problems in terms of returning to prior versions of things, and in my research I haven't found a direct answer to this question too.
Basically, did my bootloader change? Can I root using the heimdall method I keep seeing about safely? What would be the best way to root and install custom roms, neglecting the binary counter if I can get a jig or something?
Forgive me again for asking, I just need to have better answers before I try anything.
Click to expand...
Click to collapse
If you used the 1-Click method, yes. Your bootloaders are changed. Wouldve been much better to use the Heimdall method or just root your phone then flash the Leak ROM that task650 and Fenny made. As far as reverting bootloaders to stock, thats out of my range of knowledge. Im sure there is a way to do it though.
EDIT: For rooting, best way is to be on stock 2.3.4 and use the Zergrush exploit.
I've seen you're using the past tense a lot, I thought you already DID.
Anyway, for rooting and installing custom ROM, follow this thread:
http://forum.xda-developers.com/showthread.php?t=1311081
I can't pinpoint exactly what to do since having no info.
Thanks for the answers so far, now that I know my bootloaders have been changed I need to figure out how to either change back / and how to safely root. I may just have to wait it out I think though, no problem with that really, working just fine now. And never use the alarm
For clarification, my rooting experience is limited to the Atrix, the SGS2 is new as of Monday, and I am having trouble sifting through information. What I've learned so far is that maybe it was a little hasty to install the ICS leak the way I did. Prior to the ICS leak there was nothing changed on the phone.
You're going to have to get some experience with ODIN. Here is the bootloader you'll want to flash back to, however, then you'll probably need to flash a kernel with CWM (clock work mod) and then boot into cwm to flash a rom such as Tasks stock ICS leak. http://forum.xda-developers.com/showthread.php?t=1316726
So if I follow correctly the ICS leak I installed added newer bootloaders that prevent jigging in the future if it was needed. My two options are apparently to use the method that bypasses the counter, which was posted, or to use ODIN and flash the older bootloader, but this can be dangerous if done incorrectly.
The danger of bricking scares me a little, but I successfully used RSD Lite to unlock the bootloader on my Atrix, don't know if it's similar. Perhaps I should take the Atrix and attempt to install an older bootloader on it to get a feel for things? I figure that it wouldn't make much of a difference however...
I figured out that even though I have a newer bootloader now I still have a 0 for the binary counter, as the leak is considered a samsung official release, of course I don't know how that would effect any given warranty.
So, I still feel that these following questions are unanswered, I apologize if I am not understanding correctly:
1. Is it safe for me to root with the heimdall method even with the newer bootloaders
2. Is it safe for me to install custom roms without reverting the bootloader, as long as I am using the bypass method to prevent my counter from changing?
3. What is the exact risk to flashing the older bootloader, and what precautions should I take before doing so? If I flash the older bootloader without reverting to stock firmware will that cause a brick? Or is the risk just associated with fudging up the process of the flash itself, and hoping that the connection doesn't get cut (on that note, the phone, usb cord, and computer I'm using are all less than 4 months old, so that risk doesn't concern me a whole lote).
Sorry if these are stupid questions, I hope I am asking good enough questions to help others out in the future
After some more reading, here's another question as well:
Does the SGS2 technically have an unlocked bootloader already? It just counts how many times you install non samsung firmware?
Also just so I know that I'm not wrong, are Kernal, Firmware, and "Roms" all the same thing? How can you tell if a "package" or "rom" comes with bootloaders, as this is something I apparently am supposed to avoid.
ds1904.ds said:
1. Is it safe for me to root with the heimdall method even with the newer bootloaders
Click to expand...
Click to collapse
Dont believe you can root since you already flashed it with ODIN 1-Click
ds1904.ds said:
2. Is it safe for me to install custom roms without reverting the bootloader, as long as I am using the bypass method to prevent my counter from changing?
Click to expand...
Click to collapse
You cannot install custom ROM's because you dont have CWM.
ds1904.ds said:
3. What is the exact risk to flashing the older bootloader, and what precautions should I take before doing so? If I flash the older bootloader without reverting to stock firmware will that cause a brick? Or is the risk just associated with fudging up the process of the flash itself, and hoping that the connection doesn't get cut (on that note, the phone, usb cord, and computer I'm using are all less than 4 months old, so that risk doesn't concern me a whole lot).
Click to expand...
Click to collapse
Really not sure on these questions. Any takers?
ds1904.ds said:
After some more reading, here's another question as well:
Does the SGS2 technically have an unlocked bootloader already? It just counts how many times you install non samsung firmware?
Click to expand...
Click to collapse
No; Only download mode (Odin/Heimdall) flashes trigger changes to the warning screen.
ds1904.ds said:
Also just so I know that I'm not wrong, are Kernal, Firmware, and "Roms" all the same thing? How can you tell if a "package" or "rom" comes with bootloaders, as this is something I apparently am supposed to avoid.
Click to expand...
Click to collapse
Kernel is a set of drivers that tells the hardware what to do. Firmware is like a new base. (XXLPQ, DXLP7 etc.) A ROM is the whole package.
Please if I missed anything or am incorrect about some/all of this, somebody correct me.
Okay I think I'm starting to figure this out. I downgraded to 2.3.4 using an unroot/stock method I found, using odin and it worked. It would not accept the OTA update however, but I believe this is due to the ULCL2 baseband? Someone correct me if I am wrong.
Now I am going to use method 2c found here:
http://forum.xda-developers.com/showthread.php?t=1311081
to root and restore to the other baseband, which also happens to be the one that's best for my area I believe. From there, I can install CWM using one of the 31-c methods, and use CWM to install custom roms as long as they don't have bootloaders, correct? Or does it not matter if the packages have bootloaders.
Someone correct me if I am wrong, I don't want to ruin anything here. I think it's safe to install the files that come from the 2c method but wont be doing anything else until I know it's safe.
ds1904.ds said:
Okay I think I'm starting to figure this out. I downgraded to 2.3.4 using an unroot/stock method I found, using odin and it worked. It would not accept the OTA update however, but I believe this is due to the ULCL2 baseband? Someone correct me if I am wrong.
Now I am going to use method 2c found here:
http://forum.xda-developers.com/showthread.php?t=1311081
to root and restore to the other baseband, which also happens to be the one that's best for my area I believe. From there, I can install CWM using one of the 31-c methods, and use CWM to install custom roms as long as they don't have bootloaders, correct? Or does it not matter if the packages have bootloaders.
Someone correct me if I am wrong, I don't want to ruin anything here. I think it's safe to install the files that come from the 2c method but wont be doing anything else until I know it's safe.
Click to expand...
Click to collapse
Should be fine. NONE of the ROMs you find on the I777 boards in Ported or Original will have bootloaders so no worries. And yes after root use Mobile ODIN to install a zImage which will give you CWM. Highly recommend Siyah 2.6.14. Please stick to just trying some GB ROM's and get the hang of making nandroids etc before moving on the ICS ROM's.
D3M3NT3D_L0RD said:
Should be fine. NONE of the ROMs you find on the I777 boards in Ported or Original will have bootloaders so no worries. And yes after root use Mobile ODIN to install a zImage which will give you CWM. Highly recommend Siyah 2.6.14. Please stick to just trying some GB ROM's and get the hang of making nandroids etc before moving on the ICS ROM's.
Click to expand...
Click to collapse
All I get is an apk file, I've been searching all night for a zimage... The file says i777 flashkernal, and it's just an .apk. Mobile Odin can't see it unless I name it zimage with no file extension. I tried that and it seemed like it was soft-bricked so I used odin on the PC to reflash the stock root think mentioned in the thread.
I was thinking of CM7 if it will work flashing as a zip from CWM, if I can get CWM on there that is.
ds1904.ds said:
All I get is an apk file, I've been searching all night for a zimage... The file says i777 flashkernal, and it's just an .apk. Mobile Odin can't see it unless I name it zimage with no file extension. I tried that and it seemed like it was soft-bricked so I used odin on the PC to reflash the stock root think mentioned in the thread.
I was thinking of CM7 if it will work flashing as a zip from CWM, if I can get CWM on there that is.
Click to expand...
Click to collapse
Where in the hell are you getting an apk from? If you dl Siyah or Entropy kernel, the zImage is in the zip. Pull that and put it on your SD card
I am interested because I was in your position. Did the ICS leak 1 day too early and lost root. So what method did you use to go back to GB? Did you have to flash a new bootloader or was that all done in one package? Was it Entropy's "return" method?
I was seeing if I can keep the ICS leak and root. A dev here advised that all I need to do is re-flash the zip filed ICS leak. However since I have no root, I can't CWM recovery...I don't know another method to flash the rooted ICS leak.
So I'm thinking I have to wait for an exploit, or flash back to an old GB, root, ensure I have CWM, nandroid (I nandroided my rooted GB before upgrading to ICS leak), then flash the zip ICS leak.
Does anyone else have alternatives?
ds1904.ds said:
Okay I think I'm starting to figure this out. I downgraded to 2.3.4 using an unroot/stock method I found, using odin and it worked. It would not accept the OTA update however, but I believe this is due to the ULCL2 baseband? Someone correct me if I am wrong.
Now I am going to use method 2c found here:
http://forum.xda-developers.com/showthread.php?t=1311081
to root and restore to the other baseband, which also happens to be the one that's best for my area I believe. From there, I can install CWM using one of the 31-c methods, and use CWM to install custom roms as long as they don't have bootloaders, correct? Or does it not matter if the packages have bootloaders.
Someone correct me if I am wrong, I don't want to ruin anything here. I think it's safe to install the files that come from the 2c method but wont be doing anything else until I know it's safe.
Click to expand...
Click to collapse
SMH...root is not needed for CWM... a custom kernel is
Pirateghost said:
SMH...root is not needed for CWM... a custom kernel is
Click to expand...
Click to collapse
True but to do it with Mobile ODIN you need root
ds1904.ds said:
After some more reading, here's another question as well:
Does the SGS2 technically have an unlocked bootloader already? It just counts how many times you install non samsung firmware?
Also just so I know that I'm not wrong, are Kernal, Firmware, and "Roms" all the same thing? How can you tell if a "package" or "rom" comes with bootloaders, as this is something I apparently am supposed to avoid.
Click to expand...
Click to collapse
"ROM" is an improper name for the firmware flashed to a phone. (the memory in question isn't read-only by any means. In Windows Mobile devices, you had to flash the firmware image all in one go - but on Android, /system contents can be modified on the fly as they're a normal file system.) garyd9 started a little crusade against the term ROM and I try to continue it (but I slip up sometimes).
Kernel contains the most basic low-level hardware drivers for a device. It's a small portion of the firmware for a phone. The remaining portion is the system partition - /system - kernel and /system together make a complete firmware package.
And you are correct - our bootloaders are fundamentally unlocked, the only code signing enforcement is the custom binary counter. It can be reset either with the jig or with TriangleAway (TriangleAway requires ICS)
Entropy512 said:
"ROM" is an improper name for the firmware flashed to a phone. (the memory in question isn't read-only by any means. In Windows Mobile devices, you had to flash the firmware image all in one go - but on Android, /system contents can be modified on the fly as they're a normal file system.) garyd9 started a little crusade against the term ROM and I try to continue it (but I slip up sometimes).
Kernel contains the most basic low-level hardware drivers for a device. It's a small portion of the firmware for a phone. The remaining portion is the system partition - /system - kernel and /system together make a complete firmware package.
And you are correct - our bootloaders are fundamentally unlocked, the only code signing enforcement is the custom binary counter. It can be reset either with the jig or with TriangleAway (TriangleAway requires ICS)
Click to expand...
Click to collapse
Glad you chimed in. I now feel stupid at my lack of knowledge
I almost think that the issue is that your "unzipping" the zip image files that you are downloading.
Why is it so important that you keep the phone in a reversable mode? Are you planning on returning it or perhaps selling it and do not want it to be known that you have flashed it?
Personally I am not knowledgeable enough to offer much advice, I just read the forums as most and try to put together the peices of information that fit my situation.
The Dev forum is by far the best place to look and get your questions answered and there are a bunch of guides on step by step processes. The only real advice I can give you is to google each term and understand what it is you need and then post your question.
Ok I recently got a tf201. I have finally decided 2 go for it and trying 2 get a custom rom.
Untill now (using a SGS) I needed 2 root the phone then get a custom kernel then apply the rom.
How is the procedure for a prime? I tried 2 root but shortly found out that i had the .21 update, Im guesing I can downgrade not sure.
does "unlock" = root?
can some1 clarify the process tree to get to a new rom?
http://transformerprimeroot.com/tra...ow-to-unlock-bootloader-on-transformer-prime/ <--- how hard is it 2 succeed this without bricking it?
b3ava said:
Ok I recently got a tf201. I have finally decided 2 go for it and trying 2 get a custom rom.
Untill now (using a SGS) I needed 2 root the phone then get a custom kernel then apply the rom.
How is the procedure for a prime? I tried 2 root but shortly found out that i had the .21 update, Im guesing I can downgrade not sure.
does "unlock" = root?
If any1 can redirect me 2 the appropriate topics I can never spot out what I want :/ and can some1 clarify the process tree to get to a new rom?
Click to expand...
Click to collapse
You will have to unlock via the asus unlock tool (you can just google that and get it directly off of the Asus website). Then you will have to use Fastboot to flash CWM onto your device. From there the usual, back up the stock rom, and install any custom rom of your liking.
omac_ranger said:
You will have to unlock via the asus unlock tool (you can just google that and get it directly off of the Asus website). Then you will have to use Fastboot to flash CWM onto your device. From there the usual, back up the stock rom, and install any custom rom of your liking.
Click to expand...
Click to collapse
unlock tool from asus website. ok but can u explain 1 thing 2 me? if its on asus website why does it void your warranty? and root and unlock are different?
If you are planning to flash a custom rom, check out androwookie v1.2 its good.
Unlock gives you the ability to install a custom recovery e.g. cwm, you then use this to flash a pre-rooted rom. Root just means having access to the root directory. It enables access to features and functions that are normally made inaccessible.
Using the fastboot method is pretty simple and guides can be found easily. I just did it yesterday after having previously only rooted and installed cm 7+9 on my sgs2.
Thats my understanding anyway
b3ava said:
unlock tool from asus website. ok but can u explain 1 thing 2 me? if its on asus website why does it void your warranty? and root and unlock are different?
Click to expand...
Click to collapse
It's just one of their stipulations. Most manufacturers are like that in regards to using their unlock tools.
Root = enhanced permissions to run apps like Titanium Backup, Root Explorer (if you're modifying anything in the/System directory), stuff like that.
Unlock = your bootloader is "unlocked," you can now put ClockworkMod recovery on your device, flash ROMs and kernels. These things can't be done while only being rooted.
I hope I cleared it up for you a bit
Sent from my ADR6425LVW using XDA Premium.
SteveG12543 said:
It's just one of their stipulations. Most
Root = enhanced permissions to run apps like Titanium Backup, Root Explorer (if you're modifying anything in the/System directory), stuff like that.
Unlock = your bootloader is "unlocked," you can now put ClockworkMod recovery on your device, flash ROMs and kernels. These things can't be done while only being rooted.
Sent from my ADR6425LVW using XDA Premium.
Click to expand...
Click to collapse
so with unlocking the device I wont have root privs? so things like you said titanium backup wont work?
1 more thing. is unlocking considered harder? and does any1 have a video of unlocking so that I know what I can expect b4 freaking out?
b3ava said:
so with unlocking the device I wont have root privs? so things like you said titanium backup wont work?
1 more thing. is unlocking considered harder? and does any1 have a video of unlocking so that I know what I can expect b4 freaking out?
Click to expand...
Click to collapse
Unlocking doesn't instantly get you root, it just makes rooting a lot easier to do. Like they said, unlock, put CWM on it, flash a rooted ROM and bam, rooted. But correct, apps like Titanium won't work if you're only unlocked, you would need root.
As far as I know, unlocking just requires downloading the .apk from Asus' site, installing it and going through the prompts. It doesn't sound hard at all. I personally don't know the ins and outs of it, as I never unlocked my Prime, but that's all it really sounded like. Sounds pretty simple. I believe there's some videos on it on YouTube though.
Sent from my ADR6425LVW using XDA Premium.
SteveG12543 said:
Unlocking doesn't instantly get you root, it just makes rooting a lot easier to do. Like they said, unlock, put CWM on it, flash a rooted ROM and bam, rooted. But correct, apps like Titanium won't work if you're only unlocked, you would need root.
As far as I know, unlocking just requires downloading the .apk from Asus' site, installing it and going through the prompts. It doesn't sound hard at all. I personally don't know the ins and outs of it, as I never unlocked my Prime, but that's all it really sounded like. Sounds pretty simple. I believe there's some videos on it on YouTube though.
Sent from my ADR6425LVW using XDA Premium.
Click to expand...
Click to collapse
buddy thanx for all of this info was just wondering if the link i posted is the process for this unlocking? as every1 is describing? and where do i get that CWM?
b3ava said:
buddy thanx for all of this info was just wondering if the link i posted is the process for this unlocking? as every1 is describing? and where do i get that CWM?
Click to expand...
Click to collapse
No problem! And yep, the link in the first post is a great looking guide for unlocking. Nice and easy, step by step. And after you have unlocked, just download ROM Manager from the market and you can flash CWM through the app itself. From my understanding that's the easiest way to do it, at least. Sorry it's been a few days since I responded, I haven't really been checking out the Q&A section lately
Sent from my Transformer Prime TF201 using XDA Premium HD app.
Bootloader unlock:
Custom Kernel possible
Official updates impossible
Waranty impacted
CWM backups possible
Need to use community ROMs in future
improved but not great chance of recovering from bad ROM flash (really needs NVFLASH)
Rooted:
Now possible with firmwares up to .28
Permits write access to /system partition
Makes it easier to brick and block OTA updates
Should be reversable
Allows most tweaks to be applied except for replacing kernel (which is a prerequisite for some kernels)
Going to make this a FAQ I think...
Hi, i'm on 4.1.2 and rooted using link2sd and foldermount so I can store apps on the external sd card. If I upgrade to 4.2.2 do I need to unroot first and then root again after flashing the new firmware?
Also i'm assuming i'm going to lose all my game saves etc as I will lose my link2sd and foldermount setups?
My phone is unlocked from the 3 network but still has the 3 network logo on boot up and so I thought if i'm going to have to start afresh I might as well get the stock unbranded S3 rom and get rid of the 3 network branding. I used Galaxsim unlock to unlock the network so i'm assuming I won't lose my network unlock by doing any of the above?
Thanks in advance for any help given.
Sp0oner said:
Hi, i'm on 4.1.2 and rooted using link2sd and foldermount so I can store apps on the external sd card. If I upgrade to 4.2.2 do I need to unroot first and then root again after flashing the new firmware?
Also i'm assuming i'm going to lose all my game saves etc as I will lose my link2sd and foldermount setups?
My phone is unlocked from the 3 network but still has the 3 network logo on boot up and so I thought if i'm going to have to start afresh I might as well get the stock unbranded S3 rom and get rid of the 3 network branding. I used Galaxsim unlock to unlock the network so i'm assuming I won't lose my network unlock by doing any of the above?
Thanks in advance for any help given.
Click to expand...
Click to collapse
Just flash any rooted 4.2.2 ROM via custom recovery. You should take a titanium backup and a nandroid backup first. If it flashes without a wipe, you've lost nothing. If you do have to wipe, you can restore using Titanium. The Nandroid is a full system restore incase nothing works.
rootSU said:
Just flash any rooted 4.2.2 ROM via custom recovery. You should take a titanium backup and a nandroid backup first. If it flashes without a wipe, you've lost nothing. If you do have to wipe, you can restore using Titanium. The Nandroid is a full system restore incase nothing works.
Click to expand...
Click to collapse
Thanks. As you can tell i'm not up to speed on android rooting as i'm an ex iphone devotee that was good with jailbreaking but i'm new to android rooting really.
If I take an already rooted rom that surely still overwrites my current data as a rom replaces what is already there doesn't it? Can titanium and nandroid backup to pc via usb cable as my 32gb sd card won't have enough room to backup onto as it's heavily used for foldermount and link2sd.
If I wanted a pre rooted 4.2.2 stock rom for the I9300 is that something I can find on this forum to safely download and try? And if for any reasom i'm not happy with it the nandroid backup will restore the phone back to my original rom and setup as if I hadn't changed roms?
Rom and data are different. Please read the link in my signature "read before reading". It should contain everything you need to know (i'm not just saying this because I wrote it, but its really essential).
Sent from my GT-I9300 using Tapatalk 4 Beta
rootSU said:
Rom and data are different. Please read the link in my signature "read before reading". It should contain everything you need to know (i'm not just saying this because I wrote it, but its really essential).
Sent from my GT-I9300 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thank you, again. I have read all that this morning and I am in no rush to change anything as one thing i've learnt from jailbreaking when I first got into it was rushing = ending up in a big mess and panicking you've bricked your device.
I rooted my S3 earlier this year and so I expect I still have all the files and the url of the guide I followed so I can check exactly what it was I did. My flash counter won't reset to zero which really bugged me and again another lesson learnt from doing something without fully checking the consequences.
I'm an IT engineer but all windows based so when it comes to android/linux what I think would be logical pretty much seems to go out the window!
Its always good to hold off and understand before moving forward. Read the thread through a few times.
I'm also a wintel IT engineer but I wanted to get into android development so I've been using Linux at home as my daily driver for 2 years.
If there's ever anything in that thread you want me to put into windows analogies or similes,,just ask in that thread. It will help me expand the thread also
Sent from my GT-I9300 using Tapatalk 4 Beta
rootSU said:
Its always good to hold off and understand before moving forward. Read the thread through a few times.
I'm also a wintel IT engineer but I wanted to get into android development so I've been using Linux at home as my daily driver for 2 years.
If there's ever anything in that thread you want me to put into windows analogies or similes,,just ask in that thread. It will help me expand the thread also
Sent from my GT-I9300 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks again. I've been having a play about today and firstly got a titanium backup done for everything and then copied to my laptop. Then got the online version of nandroid backup so no reboot required to take the backup and did a full one of those and copied to my laptop too.
I've checked what root process I followed and it was one posted on the s3 forums using GalaxyS3root which uses a file via odin called CF-Root-SGS3-v6.1.tar. I won't post the link in case it breaks any rules etc. After reading your other post as advised I get the impression i'm not going to be able to reset my flash counter to zero. I have tried triangle away but it doesn't succeed.
As Android 4.3 is out/due out i'm now thinking pointless moving to 4.2.2 and I should wait and got straight to 4.3. Now what I wanted to ask was the following...
If I took titanium backup and then undid all my link2sd and foldermount links and then unrooted would I be able to flash the stock 4.3 rom when available, root it then reset up link2sd and foldermount and restore the titanium backup and have all my apps back to how they were?
I want to get an unmodified samsung rom that is unbranded so I can get rid of my 3 network branding I currently have on boot up. I also want to know if it is possible in anyway to reset the flash counter so I could in theory if unrooted get ota updates.
First question...
If you wipe and manually set up link2sd - when you then restore via titanium everything should be as it was.
You can reset the counter before unrooting. Theres a return-to-stock guide stuck in the "sticky roll-up thread" that covers it. The counter goes up to 1 on boot so the trick is to prevent the boot...
Sent from my GT-I9300 using Tapatalk 4 Beta
rootSU said:
First question...
If you wipe and manually set up link2sd - when you then restore via titanium everything should be as it was.
You can reset the counter before unrooting. Theres a return-to-stock guide stuck in the "sticky roll-up thread" that covers it. The counter goes up to 1 on boot so the trick is to prevent the boot...
Sent from my GT-I9300 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks, so the counter can't be cleared permanently for warranty purposes as a reboot will just put it back to 1. So as I have a custom recovery on the phone that went on with the root will that cause issues if I tried to update via official updates?
It can be prevented with an ics bootloader.
Imho its best to stay away from official updates when rooted
Sent from my GT-I9300 using Tapatalk 4 Beta
rootSU said:
It can be prevented with an ics bootloader.
Imho its best to stay away from official updates when rooted
Sent from my GT-I9300 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks. An ics bootloader however will just further invalidate the warranty and also prevent stock updates? What I had been getting at with wanting to do stock updates was to unroot first. However now i've got the custom recovery there that in itself makes stock updates an unwise move even with rooting removed?
So with my current setup what is the best method to go to 4.2.2 without using a custom rom?
They check warranty by looking at the information provided in the bootloader. Your warranty is either void or not void. There is no such thing as further invalidation. Its 0 or 1. There is no 2.
There is no "best way" without using a "custom rom". If you want to flash a stock rom, do it. Theres only one way.
By the way, 4.2.2 hasn't been officially released, so you wont be getting stock updates. You'll have to manually keep flashing release via odin until you get one that is official. Then if your csc is wrong, you have to change it (which requires factory reset) and then you will still only get updates over USB if you're rooted.
Don't get me wrong, but that sounds ridiculous to me. I just don't understand any rooted user wanting to do that
Sent from my GT-I9300 using Tapatalk 4 Beta
rootSU said:
They check warranty by looking at the information provided in the bootloader. Your warranty is either void or not void. There is no such thing as further invalidation. Its 0 or 1. There is no 2.
There is no "best way" without using a "custom rom". If you want to flash a stock rom, do it. Theres only one way.
Sent from my GT-I9300 using Tapatalk 4 Beta
---------- Post added at 10:52 PM ---------- Previous post was at 10:51 PM ----------
By the way, 4.2.2 hasn't been officially released
Sent from my GT-I9300 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks for the quick reply. I've just read through the link on your thread for returning to stock and unless i've misread it you can actually return to stock even if you have installed a custom recovery/used the auto cf root method of rooting? That's step 16?
Sorry on the invalidating warranty thing, what I meant was that if you use the ics bootloader you fix the triangleaway issue but you are then left with the ics bootloader so your warranty is still invalid.
My mistake on 4.2.2, what's the latest official version as if I plug into kies it tells me there is an update available which i'd wrongly assumed was 4.2.2?
4.1.2 is the latest.
They don't check bootloader version for warranty. They only check download mode.
You can return to stock so long as phone fully boots and usb works. If phone only partially boots, you can't return to stock or reset counter. This is why IMHO its better to have an ics bootloader where counter is always in the reset state
Sent from my GT-I9300 using Tapatalk 4 Beta
rootSU said:
You can return to stock so long as phone fully boots and usb works. If phone only partially boots, you can't return to stock or reset counter. This is why IMHO its better to have an ics bootloader where counter is always in the reset state
Sent from my GT-I9300 using Tapatalk 4 Beta
Click to expand...
Click to collapse
OK this has totally lost me now, I need to do some more reading! Also i'm on 4.1.2 yet if I plug into Kies ittells me there is an update available.
Sp0oner said:
OK this has totally lost me now, I need to do some more reading! Also i'm on 4.1.2 yet if I plug into Kies ittells me there is an update available.
Click to expand...
Click to collapse
An update won't necessarily update the android version. It will update the Samsung build version. Samsung have probably close to 100 updates on 4.1.2 (globally).
Android is just the base OS. It has Samsung GUI on top of that (and frameworks to support Samsung proprietary features). So Samsung take the android code for 4.1.2 and add all their stuff to it. But they will improve on that over a number of builds. Fixing bugs, addressing performance issues etc.
However, Samsung tend to release new features in line with android base updates too. so if Samsung are working on 4.1.2 and decide, "hey this feature would be cool", they would usually wait for the next android version to release it.
Hope that makes sense
Did that address your confusion?
Or is your confusion about returning to stock?
You return to stock by flashing a full ROM (which includes a bootloader, Android ROM, Recovery, baseband etc) over USB connection to a computer. The phone is put into download mode and flashed. if your USB is faulty, this wont work (obviously).
Before returning to stock, you need to ensure your download mode doesnt show how many times you flashed custom things. You can reset it then flash stock and warranty is fine. However, to reset it, android needs to boot, so if android doesnt boot and counter says more than "0", you've lost warranty, With ICS bootloader, you reset it once and it always says "0", so you are protected if phone doesnt boot.
rootSU said:
An update won't necessarily update the android version. It will update the Samsung build version. Samsung have probably close to 100 updates on 4.1.2 (globally).
Android is just the base OS. It has Samsung GUI on top of that (and frameworks to support Samsung proprietary features). So Samsung take the android code for 4.1.2 and add all their stuff to it. But they will improve on that over a number of builds. Fixing bugs, addressing performance issues etc.
However, Samsung tend to release new features in line with android base updates too. so if Samsung are working on 4.1.2 and decide, "hey this feature would be cool", they would usually wait for the next android version to release it.
Hope that makes sense
Did that address your confusion?
Or is your confusion about returning to stock?
You return to stock by flashing a full ROM (which includes a bootloader, Android ROM, Recovery, baseband etc) over USB connection to a computer. The phone is put into download mode and flashed. if your USB is faulty, this wont work (obviously).
Before returning to stock, you need to ensure your download mode doesnt show how many times you flashed custom things. You can reset it then flash stock and warranty is fine. However, to reset it, android needs to boot, so if android doesnt boot and counter says more than "0", you've lost warranty, With ICS bootloader, you reset it once and it always says "0", so you are protected if phone doesnt boot.
Click to expand...
Click to collapse
Thanks for both explanations :good: It was the ics bootloader I was really confused about. I'm in two minds as to change anything, the techy part of me says play with it and learn and understand more about what you've explained but the other side says i've got everything setup perfectly at the moment now I have link2sd and foldermount working and not to risk ruining that setup. I think the only thing i'd notice from 4.2.2 is the access camera from the lock screen feature.
Sp0oner said:
Thanks for both explanations :good: It was the ics bootloader I was really confused about. I'm in two minds as to change anything, the techy part of me says play with it and learn and understand more about what you've explained but the other side says i've got everything setup perfectly at the moment now I have link2sd and foldermount working and not to risk ruining that setup. I think the only thing i'd notice from 4.2.2 is the access camera from the lock screen feature.
Click to expand...
Click to collapse
If you want to continue to use stock.....
1) Backup all your app data with titanium backup (as a precaution)
2) Copy all internal /sdcard data to PC
3) Flash whatever "official" ROM you want via Odin
4) If it doesn't boot, perform factory reset#
5) re root using either cf auto root or framaroot (both do not give custom recovery)
6) Install Titanium backup and restore data.
Its worth noting a factory reset from custom recovery only wipes data and settings. A reset from stock recovery wipes internal /sdcard storage too.
rootSU said:
If you want to continue to use stock.....
1) Backup all your app data with titanium backup (as a precaution)
2) Copy all internal /sdcard data to PC
3) Flash whatever "official" ROM you want via Odin
4) If it doesn't boot, perform factory reset#
5) re root using either cf auto root or framaroot (both do not give custom recovery)
6) Install Titanium backup and restore data.
Its worth noting a factory reset from custom recovery only wipes data and settings. A reset from stock recovery wipes internal /sdcard storage too.
Click to expand...
Click to collapse
Thanks again :good: I have CWM installed and when I open CWM Manager I get a message "this version of CWM Manager should be used with CF-CWM v1.1 or newer. It appears you are running a different recovery. Various features have been disabled."
If I boot into recovery at the top it says "CWM-based recovery v5.5.04 :: CF-v1.3"
What effect does any of that have on the above steps?
Sp0oner said:
Thanks again :good: I have CWM installed and when I open CWM Manager I get a message "this version of CWM Manager should be used with CF-CWM v1.1 or newer. It appears you are running a different recovery. Various features have been disabled."
If I boot into recovery at the top it says "CWM-based recovery v5.5.04 :: CF-v1.3"
What effect does any of that have on the above steps?
Click to expand...
Click to collapse
CWM manager is an app to manage CWM. Its pretty pointless. I dont think it works on JB ROMs though.
CWM 5 is old and should be replaced by users who want to continue using a custom recovery.
The flashing stock from Odin process will overwrite any bootloader, recovery, ROM and Baseband. Nothing you have can prevent that.
So I have my stock S4 on MJ7 rooted already, now I want to flash custom recovery or boot strap recovery, but when I run the safestrap .apk on my phone it just makes Titanium Backup and KNOX both crash, and then I try booting into recovery but my phone just boots like normal, with no recovery option. How can I get this custom recovery on my MJ7 phone so I can start flashing custom ROMs? I absolutely can not stand this stock touchwiz crap. Sorry if this has been explained before, but the verizon section is so full of threads its impossible to find anything.
All we have is root on 4.3 right now. No Safestrap or Loki, so no custom recovery. Sorry.
We should presumably be able to get Safestrap soon since hashcode has it working on the Note 3 with 4.3 but at this point yes there is currently nothing other than a root. A totally unlocked bootloader isn't anywhere in sight either.
thcaddict said:
So I have my stock S4 on MJ7 rooted already, now I want to flash custom recovery or boot strap recovery, but when I run the safestrap .apk on my phone it just makes Titanium Backup and KNOX both crash, and then I try booting into recovery but my phone just boots like normal, with no recovery option. How can I get this custom recovery on my MJ7 phone so I can start flashing custom ROMs? I absolutely can not stand this stock touchwiz crap. Sorry if this has been explained before, but the verizon section is so full of threads its impossible to find anything.
Click to expand...
Click to collapse
That's sort of an understatement. You could have used search and found your answer in about 5 seconds.
LemonSlice said:
We should presumably be able to get Safestrap soon since hashcode has it working on the Note 3 with 4.3 but at this point yes there is currently nothing other than a root. A totally unlocked bootloader isn't anywhere in sight either.
Click to expand...
Click to collapse
thanks for the reply. I was unaware there is no custom recovery, or anything else besides root. I can't wait until I can put a new ROM on this phone. I really wish I would not have ran the update as soon as I bought it. Coming from an s3 with custom roms for the last year its a real bummer having to run TouchWiz.
may I ask what is loki? I just moved to Verizon from another carrier... didn't have to put up with locked bootloaders or anything ridiculous like that with my old carrier
Loki is an exploitation method to bypass bootloader checks, which allows you to run full custom recoveries, kernels, etc.
Unfortunately, only the first firmware that this phone came out with, MDK, can use Loki.
I was in your situation, if you want to run AOSP on a VZW S4, buy an MDK version on Swappa, that's what I did.
Sent from the 215
Crawshayi said:
That's sort of an understatement. You could have used search and found your answer in about 5 seconds.
Click to expand...
Click to collapse
So true, someone needs to make a sticky so we don't get 5+ new threads a week with the same question.
Sent from my SCH-I545 using xda app-developers app
richii0207 said:
So true, someone needs to make a sticky so we don't get 5+ new threads a week with the same question
Click to expand...
Click to collapse
That won't help. Sadly, most people won't read the sticky threads.
mateopase said:
All we have is root on 4.3 right now. No Safestrap or Loki, so no custom recovery. Sorry.
Click to expand...
Click to collapse
Where is the directions for root on MJ7
Crawshayi said:
That's sort of an understatement. You could have used search and found your answer in about 5 seconds.
Click to expand...
Click to collapse
Not sure if the OP tried to use the search - but I've tried to use it several times over the past week and have gotten error messages from the site each & every time.
As a matter of fact - prior to submitting this reply - I received two different error messages when trying to search the word "root" in the "Search This Forum" box - just to test it out before I reply.
The "usual" error I get is: Search is temporarily unavailable. We apologize for the inconvenience.
The other one lists actual trouble codes & has a link to notify an admin.
Believe me - I'm all for searching out info on forums - but when there are 7 sub-forums for the Verizon Galaxy S4 - and the search function isn't working - it's pretty easy to not find the info you're looking for.
Also - to the person asking about root on MJ7 - see the Verizon Samsung Galaxy S 4 General forum - and find the post titled "How to Root Build MJ7 and get SuperSU installed"
skny said:
Not sure if the OP tried to use the search - but I've tried to use it several times over the past week and have gotten error messages from the site each & every time.
As a matter of fact - prior to submitting this reply - I received two different error messages when trying to search the word "root" in the "Search This Forum" box - just to test it out before I reply.
The "usual" error I get is: Search is temporarily unavailable. We apologize for the inconvenience.
The other one lists actual trouble codes & has a link to notify an admin.
Believe me - I'm all for searching out info on forums - but when there are 7 sub-forums for the Verizon Galaxy S4 - and the search function isn't working - it's pretty easy to not find the info you're looking for.
Also - to the person asking about root on MJ7 - see the Verizon Samsung Galaxy S 4 General forum - and find the post titled "How to Root Build MJ7 and get SuperSU installed"
Click to expand...
Click to collapse
There is no working safestrap version or custom recovery for MJ7. Custom recovery can only be installed on MDK. Safestrap works on ME7 and MI1, but flaky on MI1 from what I have read. You are SOL.
dincodee said:
Where is the directions for root on MJ7
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2511815&page=1
If we are all SOL for now, do we know if anyone is working on this? I would love to flash a custom ROM and rid myself of this garbage....
MJ7 Root
dincodee said:
Where is the directions for root on MJ7
Click to expand...
Click to collapse
There is also this video by Tomsgt123 which lays it out nicely and tells you how to delete the chinese superuser app (if you are worried about that). I have not tried this method myself, just found the video while searching.
https://www.youtube.com/watch?v=K5mCsDyW-TI&feature=youtu.be
Good luck.
CoMtnMan said:
There is also this video by Tomsgt123 which lays it out nicely and tells you how to delete the chinese superuser app (if you are worried about that). I have not tried this method myself, just found the video while searching.
https://www.youtube.com/watch?v=K5mCsDyW-TI&feature=youtu.be
Good luck.
Click to expand...
Click to collapse
This works well, rooted my dad's S4 this way and it put the american/english supersu app in there in place of the chinese one at the end
No unlocked boot loader/custom recovery yet but I check back every week
Can you achieve more on loki than safestrap?
Specifically, can you flash custom kernels?
If so I may jump ship for the g2 since it has loki support
I thought they had the same limitations.
crazysoccerman said:
Can you achieve more on loki than safestrap?
Specifically, can you flash custom kernels?
If so I may jump ship for the g2 since it has loki support
I thought they had the same limitations.
Click to expand...
Click to collapse
Not speaking about the G2, but loki allows you to bypass the locked bootloader, which then permits you to flash whatever recovery, kernels, and ROMs that you want. On the I545, once you're past MDK, Loki won't work.
k1mu said:
Not speaking about the G2, but loki allows you to bypass the locked bootloader, which then permits you to flash whatever recovery, kernels, and ROMs that you want. On the I545, once you're past MDK, Loki won't work.
Click to expand...
Click to collapse
I thought safestrap did the same thing?
You can't flash kernels on safestrap, right?
crazysoccerman said:
I thought safestrap did the same thing?
You can't flash kernels on safestrap, right?
Click to expand...
Click to collapse
Correct, which is why it's not the same thing as Loki'd MDK. On anything later than MDK, you can't replace the stock recovery (but can boot into a Safestrap recovery), can't flash custom kernels, etc. On MDK, you can flash any ROM that's compatible with the phone's hardware. Using Safestrap, you can only use ROMs that are compatible with the stock kernel.
Safestrap gets you most of what you get from an unlocked bootloader, just not everything.
Thanks for your help. I made sure to hit the thanks button.
I'm going to return my s4 for a g2.
I don't think samsung and verizon considered the cost of returned phones because of lack of mod ability. Hopefully users on verizon and at&t aren't witnessing the end of a modding era.
It's sad to see what two years since I purchased my gnex has brought to the modding community. Rather than making awesome new features, developers are fighting for the ability to mod at all.
I also find it hypocritical that newer versions of android and proprietary interfaces have copied features that were originally on custom mods.
A while back when I first got my Verizon Note 2, I used Adam Outler's Casual method to root my phone to Stock. I don't mind stock and root mostly for the Tethering.
About a week back the OTA notice hit my phone. I have declined the notice/update twice giving myself time to look for the root update. I found this thread by Beans: http://forum.xda-developers.com/showthread.php?t=2518704 ........ It seems right but this thread by AdamOutler says not to use ODIN: http://forum.xda-developers.com/showthread.php?t=2045563
So I am a little confused. I just want the update but don't want to mess up and not have my tethering ever again.... or brick the phone.
As a newbie, it's a scary task. Someone please help point me in the right direction. I just want the 4.3 Stock. If there is a thread for my situation I couldn't find it. I search "casual TWRP 4.3 OTA" and other similar variations.
I can still get to the TWRP 2.5.0.0. I have also downloaded the ODIN and started it... looks simple, but there are no instructions.
Someone please help me...
Thanks
MrNewbie said:
A while back when I first got my Verizon Note 2, I used Adam Outler's Casual method to root my phone to Stock. I don't mind stock and root mostly for the Tethering.
About a week back the OTA notice hit my phone. I have declined the notice/update twice giving myself time to look for the root update. I found this thread by Beans: http://forum.xda-developers.com/showthread.php?t=2518704 ........ It seems right but this thread by AdamOutler says not to use ODIN: http://forum.xda-developers.com/showthread.php?t=2045563
So I am a little confused. I just want the update but don't want to mess up and not have my tethering ever again.... or brick the phone.
As a newbie, it's a scary task. Someone please help point me in the right direction. I just want the 4.3 Stock. If there is a thread for my situation I couldn't find it. I search "casual TWRP 4.3 OTA" and other similar variations.
I can still get to the TWRP 2.5.0.0. I have also downloaded the ODIN and started it... looks simple, but there are no instructions.
Someone please help me...
Thanks
Click to expand...
Click to collapse
Welp, couple things...
#1 - The link you posted above is the from the Note 3. You want this one http://forum.xda-developers.com/showthread.php?t=2578458
#2, The ROM gets flashed via CWM or TRWP like normal, it's only the radio update that gets flashed via ODIN. That shouldn't affect your current unlock/root status.
#3 - If it is only ROOT you are after, the 4.3 OTA is Rootable, just not unlockable. So if by chance you accidentally take the OTA you should still be able to ROOT and install your Tethering app. You just won't be able to unlock the bootloader and install a custom recovery/rom.
Jiggabitties said:
Welp, couple things...
#3 - If it is only ROOT you are after, the 4.3 OTA is Rootable, just not unlockable. So if by chance you accidentally take the OTA you should still be able to ROOT and install your Tethering app. You just won't be able to unlock the bootloader and install a custom recovery/rom.
Click to expand...
Click to collapse
So if you are OTA'd to MJ9, how do you unlock?
SteveHebe said:
So if you are OTA'd to MJ9, how do you unlock?
Click to expand...
Click to collapse
You cannot. Best bet is to not take the other and unlock your bootloader. If you take it you will probably be locked for a very long time.
Sent from my SCH-I605 using Tapatalk 2
michigan66 said:
You cannot. Best bet is to not take the other and unlock your bootloader. If you take it you will probably be locked for a very long time.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
SteveHebe said:
So if you are OTA'd to MJ9, how do you unlock?
Click to expand...
Click to collapse
Correct, you cannot currently UNLOCK the OTA MJ9 boot loader. But you can ROOT. Which will allow you to tether.
Sent from my SCH-I605 using xda app-developers app
MrNewbie said:
A while back when I first got my Verizon Note 2, I used Adam Outler's Casual method to root my phone to Stock. I don't mind stock and root mostly for the Tethering.
About a week back the OTA notice hit my phone. I have declined the notice/update twice giving myself time to look for the root update. I found this thread by Beans: http://forum.xda-developers.com/showthread.php?t=2518704 ........ It seems right but this thread by AdamOutler says not to use ODIN: http://forum.xda-developers.com/showthread.php?t=2045563
So I am a little confused. I just want the update but don't want to mess up and not have my tethering ever again.... or brick the phone.
As a newbie, it's a scary task. Someone please help point me in the right direction. I just want the 4.3 Stock. If there is a thread for my situation I couldn't find it. I search "casual TWRP 4.3 OTA" and other similar variations.
I can still get to the TWRP 2.5.0.0. I have also downloaded the ODIN and started it... looks simple, but there are no instructions.
Someone please help me...
Thanks
Click to expand...
Click to collapse
I would think long and hard about taking the OTA...although root is available, you may want an unlocked bootloader at some point, and there is no guarantee that is coming to the official 4.3. My guess is that it will not simply because this phone is 18 months old and the skilled developers that put in the time to do things like unlock bootloaders move on to newer devices.
If you managed to use Casual in the past, Odin won't be a problem for you. Below are the steps:
Odin takes about 5 minutes total...its really easy.
Download Odin (it's just a simple windows program). - http://forum.xda-developers.com/atta...3&d=1304094576
Make sure you have the latest samsung drivers - http://www.mediafire.com/?hzlnda0l5t8qyes
Download and extract the firmware from the first post in this thread - http://forum.xda-developers.com/showthread.php?t=2578458
Save whatever 4.3 ROM you choose to your external SD card.
Power down the phone and boot back into download mode (volume down, power and home at the same time).
Open Odin, plug in phone...Odin should recognize the phone and you will see the com port noted in yellow.
Check the PDA box and put the firmware file (unzipped) in the PDA slot. Click start and 30 seconds later you are done. Phone will reboot into recovery at this point.
Then you can flash any of the 4.3 ROMs (including stock) in TWRP (I use 2.5.0.0 too). I have tried them all and Sophisticated 3.0 has worked the best for me...I will be trying beans 23 as soon as it is done.
tfly212 said:
I would think long and hard about taking the OTA...although root is available, you may want an unlocked bootloader at some point, and there is no guarantee that is coming to the official 4.3. My guess is that it will not simply because this phone is 18 months old and the skilled developers that put in the time to do things like unlock bootloaders move on to newer devices.
If you managed to use Casual in the past, Odin won't be a problem for you. Below are the steps:
Odin takes about 5 minutes total...its really easy.
Download Odin (it's just a simple windows program). - http://forum.xda-developers.com/atta...3&d=1304094576
Make sure you have the latest samsung drivers - http://www.mediafire.com/?hzlnda0l5t8qyes
Download and extract the firmware from the first post in this thread - http://forum.xda-developers.com/showthread.php?t=2578458
Save whatever 4.3 ROM you choose to your external SD card.
Power down the phone and boot back into download mode (volume down, power and home at the same time).
Open Odin, plug in phone...Odin should recognize the phone and you will see the com port noted in yellow.
Check the PDA box and put the firmware file (unzipped) in the PDA slot. Click start and 30 seconds later you are done. Phone will reboot into recovery at this point.
Then you can flash any of the 4.3 ROMs (including stock) in TWRP (I use 2.5.0.0 too). I have tried them all and Sophisticated 3.0 has worked the best for me...I will be trying beans 23 as soon as it is done.
Click to expand...
Click to collapse
Thank you so much. Updated and everything seem to work just fine, but after some use it started rebooting. I am going to put on Sophisticated as you suggested. Hopefully, it will be more stable then the stock ROM.
And I can't get the WIFI Tethering to work. Which Tethering app are you using? I have unlimited data... and need to make sure Verizon isn't charging me for no reason.
MrNewbie said:
Thank you so much. Updated and everything seem to work just fine, but after some use it started rebooting. I am going to put on Sophisticated as you suggested. Hopefully, it will be more stable then the stock ROM.
And I can't get the WIFI Tethering to work. Which Tethering app are you using? I have unlimited data... and need to make sure Verizon isn't charging me for no reason.
Click to expand...
Click to collapse
I had some reboots on the stock rom too...but once I went to the other roms (I tried Nephilium, Sophisticated and N3bula, but had the best results with Sophisticated) and I haven't had one reboot.
As for the wifi tethering, on stock you need to flash the file below (some of the newer roms, including Sophisticated have it baked in).
http://forum.xda-developers.com/showpost.php?p=48315091&postcount=245
IS anybody getting close to an unlock/root post VRUEMJ9 VZWi605 Note 2.
the reason I ask is I unrooted back to stock 4.1.1 and then picked up the VZW OTA 4.3 and now can't use Casual or any other method, I can root but not unlock bootloader. well anybody have any Ideas? thank you.
david515 said:
the reason I ask is I unrooted back to stock 4.1.1 and then picked up the VZW OTA 4.3 and now can't use Casual or any other method, I can root but not unlock bootloader. well anybody have any Ideas? thank you.
Click to expand...
Click to collapse
The reason you ask what? You didn't ask anything. And as it's been stated a million times, no unlock method avaliable and unlikely there will be one.
Sent from my SCH-I605 using xda app-developers app
akellar said:
The reason you ask what? You didn't ask anything. And as it's been stated a million times, no unlock method avaliable and unlikely there will be one.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Eh, he is one of those that puts the question in his title instead of the body of the reply. But as @akellar said, there is nothing available.
Thanks so much for all the help. I got everything working right based on the instructions from this thread. I initially had an issue with the "Wifi Tether" because I was using a 3rd party app. Instead the correct app is the "Mobile Hotspot" app. It might be named differently for other carriers, but for Verizon it is "Mobile Hotspot".
Again thank you for all the replies.
Thank you for Sophisticated v3.
Thank you Adam Outler for the original Casual root.
And Thank you runandhide05 for the "Mobile Hotspot" hack!
:good::fingers-crossed: LOL