Related
Hello all,
This is just another post I am making to hopefully help newbies who may want to mod their gTab but are not sure where to start. xda has an overwhelming amount of information on it and it can be difficult to sort through it all. I hope that someone who just got a gTab or just decided to mod it will be helped by this little compilation.
Now, the first thing we should discuss is what "rooting" an Android device actually means. When you root a device you gain superuser (root) privileges on the ROM you are running. This is only useful if you do not plan to flash a custom ROM, or, in other words, you want to use the stock Tap'n'Tap (TnT) software, but be able to use superuser apps like TitaniumBackup or RootExplorer. Most custom ROMs come rooted.
Now that we've cleared that up, lets talk about what you are actually going to be doing and the stages of the g tablet boot that you will be modding. The gtab boots in 3 stages, it will first load the viewsonic birds screen, here it decides whether to boot the recovery image, the APX bootloader (for nvflash), or the main ROM you have loaded. To change what it does you wither hold the power button (main ROM), Power&Vol+ (recovery kernel), or Power&Vol- (APX bootloader. To flash a custom ROM you install a custom recovery known as ClockWork Mod.
LOADING A CUSTOM RECOVERY WILL VOID YOUR WARRANTY!
So if you don't want to do that, stop right here! I didn't care, but you might so be aware. Now there is a third thing to consider gTabs ship with two different bootloaders. Information on this topic can be found HERE. It is very important that you know what bootloader version you have before continuing, I soft-bricked (see Troubleshooting) my tablet the first time and had to recover it because I didn't check my bootloader version before trying to flash ClockWork Mod. This guide is meant for those who are on the 1.1-3588 bootloader, if you have the 1.2 bootloader you can either find a guide for that bootloader or downgrade your bootloader (this is what I did) with instructions you can find here.
Once you have CONFIRMED that you are on the 1.1-3588 bootloader, continue.
Instructions for installing ClockworkMod can be found here!
After installing ClockworkMod Successfully, you are well on your way to enjoying your tablet's fullest potential. Now you can flash a custom ROM.
Instructions for installing a custom ROM can be found here!
Some ROM's I highly recommend and their features:
VEGAn-Tab 5.1.1 - Best 2.2 ROM I used.
Dev Thread
VEGAn-TAB GingerEdition - Awesome 2.3.3 ROM! One of the best and most useful ROMs I have used. It is able to make your tablet ready to use immediately.
Dev Thread
TnT-Lite - I have never used this ROM but I have heard good things about it. Worth a look.
Dev Thread
Cyanogen Mod 7.0.3-STABLE - This is my current favorite ROM, but is not as out-of-the-box useful as VEGAn-TAB, VEGAn is an extension of Cyanogenmod, but it is based off of Cyanogenmod 7.0.0, which doesn't support even partial hardware video acceleration or Netflix streaming, therefore I use CYMod 7.0.3. With Cyanogenmod you have to download an update zip file to get google apps because of copyright issues. You can find instructions in the Cyanogenmod Wiki.
Dev Site (not hosted on xda)
Troubleshooting!
OMFGXOXROZWTFYOURUINEDMYTABLETOMG!1!!11! - No, I didn't. Please explain your problems well if you need help! I am not responsible for anything that happens to your tablet, ever
My tablet won't boot up!!! - If you can't boot your tablet this is a soft-brick, but fear not! It can be recovered (usually) Follow instructions here!
How come google apps are missing? - Look up a few lines!
I want to be able to do x!!! - Talk to the developer of the ROM you chose, not me!
Final Note: This is a compendium of useful info for newbies, putting a custom ROM on your tablet does void the warranty and can be tedious, and none of that is my problem! Hopefully anyone who was confused about the process they are considering taking on is now more in the know about what they are going to attempt. Personally I think the gTab is useless without a custom ROM, and that this is essential to making your tablet useeful, I now carry my tablet with me everywhere and would not go back on this purchase in a millon years!
Enjoy and happy modding,
Insignia96
I feel monumentally stupid asking this question, but I've run out of options. I have tried searching first, but I'm having trouble figuring out how to phrase the search and most of the search results are for non-Atrix 2 phones, so I don't know how reliable the information is.
My previous phone was an HTC Evo which was fully rootable and unlockable etc., and an HTC Evo 3d which was fully rootable and unlockable at the time I managed to do it (apparently the 3d goes through phases where it is, then phases where it isn't, depending on its updates). My basic and non-technical understanding of the Atrix 2 environment is that becauase the bootloader is currently locked, the backup/restore/flashing solutions have to perform a few tricks to work.
So from what I can tell in the dev forum, there are currently two ways to backup and flash roms. There is safestrap, which apparently isn't quite working yet, which partitions your microSD card and runs everything from there -- essentially when you boot your phone it tells the OS to boot from the microSD card which effectively lets you treat your Atrix 2 as a fully unlocked and rooted device with a remarkably large and well-configured recovery partition. Unfortunately, according to the title of the safestrap thread, it's not quite working yet, and a few of the roms posted in the development forum specifically say not to use it.
OK, so bootstrap. It was updated as of Jan 1. If you have already rooted your Atrix 2 (I have) then it throws up a menu that lets you boot into recovery, and it will install (I think this is my understanding) a custom version of ClockwordMod Recovery? But you can't get there from boot, you have to boot into Android and then reboot back into the recovery environment.
Is that correct?
If that is correct, then my next question is what happens in the hypothetical scenario where you install a rom, something goes wrong, and you want to restore a previous backup but you can't boot into Android?
There's something I'm missing about how all this is supposed to work and it looks like it's something so obvious that nobody actually talks about it in the threads -- or when they're talking about it, I don't actually realize that's what they're talking about so it doesn't register.
Anyway. Thanks for your time.
There's a script in the thread that gives you cwm on boot. The catch is it goes to recovery first EVERYTIME you boot.
ubersoft said:
I feel monumentally stupid asking this question, but I've run out of options. I have tried searching first, but I'm having trouble figuring out how to phrase the search and most of the search results are for non-Atrix 2 phones, so I don't know how reliable the information is.
My previous phone was an HTC Evo which was fully rootable and unlockable etc., and an HTC Evo 3d which was fully rootable and unlockable at the time I managed to do it (apparently the 3d goes through phases where it is, then phases where it isn't, depending on its updates). My basic and non-technical understanding of the Atrix 2 environment is that becauase the bootloader is currently locked, the backup/restore/flashing solutions have to perform a few tricks to work.
So from what I can tell in the dev forum, there are currently two ways to backup and flash roms. There is safestrap, which apparently isn't quite working yet, which partitions your microSD card and runs everything from there -- essentially when you boot your phone it tells the OS to boot from the microSD card which effectively lets you treat your Atrix 2 as a fully unlocked and rooted device with a remarkably large and well-configured recovery partition. Unfortunately, according to the title of the safestrap thread, it's not quite working yet, and a few of the roms posted in the development forum specifically say not to use it.
OK, so bootstrap. It was updated as of Jan 1. If you have already rooted your Atrix 2 (I have) then it throws up a menu that lets you boot into recovery, and it will install (I think this is my understanding) a custom version of ClockwordMod Recovery? But you can't get there from boot, you have to boot into Android and then reboot back into the recovery environment.
Is that correct?
If that is correct, then my next question is what happens in the hypothetical scenario where you install a rom, something goes wrong, and you want to restore a previous backup but you can't boot into Android?
There's something I'm missing about how all this is supposed to work and it looks like it's something so obvious that nobody actually talks about it in the threads -- or when they're talking about it, I don't actually realize that's what they're talking about so it doesn't register.
Anyway. Thanks for your time.
Click to expand...
Click to collapse
In the situation that you describe, even the CWM on boot that mtnlion mentioned, still may not get you into CWM. In that case your ONLY option is to flash the fxz file with rsd lite, that will restore you to a full stock out of the box atrix 2, which you then have to re-root, then re-install bootstrap, then restore your backup.
Sorry there is not an easier way right now, but until the bootloader is unlocked we can't flash CWM, so that we can get to it, as you would the default android recovery, because that does require the default recovery to be replaced, and an unlocked bootloader is required for that to work.
Safestrap is really a tool that is only useful to those actually developing, or people that we have asked to test something out, and since lfaber06 and I don't have a version to release to the public that we are happy with yet, that is not an option.
Oh!
So you install bootstrap, then you install the script, and when you do that it basically acts like a grub menu? That makes sense.
ubersoft said:
Oh!
So you install bootstrap, then you install the script, and when you do that it basically acts like a grub menu? That makes sense.
Click to expand...
Click to collapse
No, if you get a bad flash you still may not be able to get into CWM, since it requires files that are actually in the Android ROM, to fully work. Read my post above ^^^
Heh. Apparently I started posting at about the same time you posted your detailed explanation...
Thanks for the additional information. Based on that, it looks like I need to wait a bit longer before mucking about with my Atrix 2. Thanks for the update!
ubersoft said:
Heh. Apparently I started posting at about the same time you posted your detailed explanation...
Thanks for the additional information. Based on that, it looks like I need to wait a bit longer before mucking about with my Atrix 2. Thanks for the update!
Click to expand...
Click to collapse
No, it is perfectly safe, but the restore is just a little more complex than you had to deal with, with other phones. I have done exactly what I mentioned above SEVERAL times, with out issue, since I am doing a ton of dev work on this phone.
The ROMs that are out there are great right now, and lfaber06s ROM is really good, and I will be releasing a version of CM7 very soon. If you wait for a bootloader unlock, it may never come, or at least it may not be very soon.
The worst thing that happens is that you have to flash the fxz, which it is documented how to do that with RSD lite very well in the noob thread here. then you can restore your backup with out issue, it is just a few extra steps.
Bootstrap is really safe as is all of lfaber06 Roms right now. I have no problem recommending either of his roms to anyone. They are both very good. As Jim has stated the only problems we have is if something wrong happens on boot, but with the fastboot files, RSD lite, and the one click root method you have everything available to get you right back to where you were before you flashed.
I can promise you everything works very good as I have soft bricked my phone so many rimes in the last 2 weeks that I have become very efficient at getting back to stock, rooting and then flashing a backup with bootstrap and can be back in business n around 20 mins. Just always be near a computer when you start flashing things. One thing that will help out is to keep a backup of the bootstrap on tour SD card so if you have something go wrong you don't have to redownload it again.
We have a very good group of people here and if anyone has any problems we can get you through them and back running
Well there we are then!
So after getting a clearer picture of the situation (thanks for the explanation) I blocked off most of the night, installed bootstrap, then installed lfaber06's Supercharged v4. It took forever, but it worked flawlessly.
Thanks everyone for your patience and encouragement.
Hey fellas, I got my Verizon GS3 last Thursday knowing that it had a locked bootloader but was hoping someone would figure out how to get root. Now I see that it has been rooted but is it "completely" rooted? What I mean is, can I overclock it, flash kernals, custom roms, wifi tether? Does it have the same capabilities of all three of the other US carriers' GS3s? Is Cyanogenmod developing CM9 for it yet? I was reading somewhere that you can root it just like any other version but it's just a bigger pain in the ass. I just want to make sure that my Verizon GS3 can be completely rooted so I can do everything I did with my old Droid. Should I just take it back and go with the Sprint version of the GS3? Im sorry if some of these are "noob" questions but I just want to figure out what I should do. Any help would be much appreciated!
Rooting and the other things you spoke of are not the same thing.
Rooting = The ability to write to the system partition, while booted into android. This allows you to delete system files (such as bloatware).
Locked Boot Loader = You will not be able to flash custom files (unsigned) to the phone from Odin. This means no clockwork recovery, roms, kernels ect....
There are ways around some of the locked boot loader stuff on some phones (ex. droid 2 got a special recovery through months of dev work. This did not cicrumvent the locked boot loader, but allowed away around it). This type of recovery (2nd init) is not avalible for Samsung phones.
If you want roms and all access, I would go with the dev unit samsung is selling for verizon. However, there still may not be much for the VZW gs3 because they wont sell tons of the dev units at $600 a pop.
The Verizon S3 already has root, roms and kernels up and working and some really good devs trying to crack it. I have a VG3 and it was rooted in less than a day and I'm having no issues. It's a great phone but the locked bootloader may cause issue in the future.
If I knew that samsung was going to release a dev version I may not have pre-ordered my S3 but I"m still happy with my purchase so far. What I find amusing is the price stated on the dev phone right now is cheaper than buying the phone outright from big V right now. We will see what the price really is when the phone is made available.
Farabomb said:
The Verizon S3 already has root, roms and kernels up and working and some really good devs trying to crack it. I have a VG3 and it was rooted in less than a day and I'm having no issues. It's a great phone but the locked bootloader may cause issue in the future.
If I knew that samsung was going to release a dev version I may not have pre-ordered my S3 but I"m still happy with my purchase so far. What I find amusing is the price stated on the dev phone right now is cheaper than buying the phone outright from big V right now. We will see what the price really is when the phone is made available.
Click to expand...
Click to collapse
I second this post!
locked bootloader means no custom roms or kernels.
chakra said:
locked bootloader means no custom roms or kernels.
Click to expand...
Click to collapse
Not true.
Touchwiz based custom roms are entirely possible and it has already been shown custom kernels work using kexec. Yeah it's not as good as an unlocked bootloader but we have our work arounds until these crazy smart devs figure out how to bypass the locked bootloader.
Sent from my SGS3
tanman21 said:
Rooting and the other things you spoke of are not the same thing.
Rooting = The ability to write to the system partition, while booted into android. This allows you to delete system files (such as bloatware).
Locked Boot Loader = You will not be able to flash custom files (unsigned) to the phone from Odin. This means no clockwork recovery, roms, kernels ect....
There are ways around some of the locked boot loader stuff on some phones (ex. droid 2 got a special recovery through months of dev work. This did not cicrumvent the locked boot loader, but allowed away around it). This type of recovery (2nd init) is not avalible for Samsung phones.
If you want roms and all access, I would go with the dev unit samsung is selling for verizon. However, there still may not be much for the VZW gs3 because they wont sell tons of the dev units at $600 a pop.
Click to expand...
Click to collapse
Thanks for the reply man! The dev phone just may be an option but I really don't feel like forking over $600 when I can go to Sprint on a cheaper plan and have an unlocked bootloader....either way, I have 10 more days to return my phone and cancel my contract if I need to. And btw, I sent a long email to Verizon asking them if they will ever unlock the bootloader ( I read an article saying they may, then today read a article saying they wont. We'll see.) I also said that I may just cancel my contract and go to Sprint and ask them how they can "help" relieve this situation that alot of people are facing. I'll report back and let everyone know what their response is.
Topdroid01 said:
Hey fellas, I got my Verizon GS3 last Thursday knowing that it had a locked bootloader but was hoping someone would figure out how to get root. Now I see that it has been rooted but is it "completely" rooted? What I mean is, can I overclock it, flash kernals, custom roms, wifi tether? Does it have the same capabilities of all three of the other US carriers' GS3s? Is Cyanogenmod developing CM9 for it yet? I was reading somewhere that you can root it just like any other version but it's just a bigger pain in the ass. I just want to make sure that my Verizon GS3 can be completely rooted so I can do everything I did with my old Droid. Should I just take it back and go with the Sprint version of the GS3? Im sorry if some of these are "noob" questions but I just want to figure out what I should do. Any help would be much appreciated!
Click to expand...
Click to collapse
There's some erroneous replies so far, hopefully this will clear it up for you. Root or superuser, is a linux term, which basically provides you with admin rights. With root alone you can run WiFi tether, rename system apps, etc. Root is easily attainable on the Verizon S3, see the dev section for guides.
The S3 recovery partition is NOT signed. This allows us to install custom recoveries (i.e. ClockworkMod, TWRP, etc.) This is very different from say, a Moto phone that had to use bootstrap methods. The S3 can have a fully functioning recovery that will allow you to do backups, flash ROMs and Kernels, etc. Again, very easy to do, see dev section for guides (it's grouped with root).
What's currently being worked on is the "locked" bootloader. Basically we can write whatever we want to the various partitions, however, there is a security check being done that prevents altering various areas, like the boot.img. Right now there is a workaround where custom Kernels are flashed via the recovery partition (see recovery/kexec threads for more info).
There is no official CM9 or CM10 builds yet, but they are being worked on and there are bootable versions of both. Right now the RIL is the bigger issue as it's preventing data but that has nothing to do with the bootloader. The RIL is being worked on, no ETA.
tl;dr - The bootloader is still "locked" but there are already various workaround methods in place to allow for the flashing of custom recoveries, ROMs, Kernels, etc. Reading the guides in the dev section would be a great place to start understanding what's going on better.
s197 said:
There's some erroneous replies so far, hopefully this will clear it up for you. Root or superuser, is a linux term, which basically provides you with admin rights. With root alone you can run WiFi tether, rename system apps, etc. Root is easily attainable on the Verizon S3, see the dev section for guides.
The S3 recovery partition is NOT signed. This allows us to install custom recoveries (i.e. ClockworkMod, TWRP, etc.) This is very different from say, a Moto phone that had to use bootstrap methods. The S3 can have a fully functioning recovery that will allow you to do backups, flash ROMs and Kernels, etc. Again, very easy to do, see dev section for guides (it's grouped with root).
What's currently being worked on is the "locked" bootloader. Basically we can write whatever we want to the various partitions, however, there is a security check being done that prevents altering various areas, like the boot.img. Right now there is a workaround where custom Kernels are flashed via the recovery partition (see recovery/kexec threads for more info).
There is no official CM9 or CM10 builds yet, but they are being worked on and there are bootable versions of both. Right now the RIL is the bigger issue as it's preventing data but that has nothing to do with the bootloader. The RIL is being worked on, no ETA.
tl;dr - The bootloader is still "locked" but there are already various workaround methods in place to allow for the flashing of custom recoveries, ROMs, Kernels, etc. Reading the guides in the dev section would be a great place to start understanding what's going on better.
Click to expand...
Click to collapse
This explains things alot better for me Thank you!!!. Im coming from a OG Droid that I rooted as soon as I got it so its been a while since I've been on the scene. I've kept up with the OG Droid Development for quite some time (which is basically nonexistent) so Im somewhat familiar with rooting and such just not familiar with this lock bootloader and such on my S3. Anyways, I still may just go to Sprint but havent made my mind up yet. And THANKS again for the very knowledgeable answer!
I have a decent amount of experience flashing a couple of HP Touchpads, our Nexus S 4G CDMA phones and our HTC One V CDMA phones. I have learned alot along the way but for the last 2 days I have finally decided to unlock, root and flash our Xooms. The Xooms have already been updated to Android 4.1 with OTA updates and it has not been nearly as straightforward as my previous experiences. My motivation was Motorola ceasing to support them and a desire to get the Team EOS Xoom Jellybean MR1 4.2 Windray nightlies installed!
I started by going to the Motorola page with the official unlock my device instructions. Nothing I did could get those instructions to work. Finally I returned to XDA...my go to place in the past. It seems that I have finally accomplished my goal, but I could not find any instructions that could have easily helped me to avoid several pitfalls.
The very first thing I wish any instructions would have told me is that the latest CWM Recovery OR TWRP can not read the external SD card on Xooms. I do not know exactly why this is, but it seems it is either because I already had OTA updates prior OR for some reason I can't figure out.
So, in posting here I am wondering if anyone can point me to a comprenhinsive set of instructions for doing what I had so much difficulty doing so that I can save it for future reference. I assure you that I searched not only these forums, but the internet exhaustively, and although I was able to find answers to the many challenges that came up, the tutorials on this forum were so old that it surprised me. Does anyone know of a tutorial for unlocking, rooting and flashing the latest Android to a Xoom that helps to avoid the pitfalls?
Thanks!
donrull said:
I have a decent amount of experience flashing a couple of HP Touchpads, our Nexus S 4G CDMA phones and our HTC One V CDMA phones. I have learned alot along the way but for the last 2 days I have finally decided to unlock, root and flash our Xooms. The Xooms have already been updated to Android 4.1 with OTA updates and it has not been nearly as straightforward as my previous experiences. My motivation was Motorola ceasing to support them and a desire to get the Team EOS Xoom Jellybean MR1 4.2 Windray nightlies installed!
I started by going to the Motorola page with the official unlock my device instructions. Nothing I did could get those instructions to work. Finally I returned to XDA...my go to place in the past. It seems that I have finally accomplished my goal, but I could not find any instructions that could have easily helped me to avoid several pitfalls.
The very first thing I wish any instructions would have told me is that the latest CWM Recovery OR TWRP can not read the external SD card on Xooms. I do not know exactly why this is, but it seems it is either because I already had OTA updates prior OR for some reason I can't figure out.
So, in posting here I am wondering if anyone can point me to a comprenhinsive set of instructions for doing what I had so much difficulty doing so that I can save it for future reference. I assure you that I searched not only these forums, but the internet exhaustively, and although I was able to find answers to the many challenges that came up, the tutorials on this forum were so old that it surprised me. Does anyone know of a tutorial for unlocking, rooting and flashing the latest Android to a Xoom that helps to avoid the pitfalls?
Thanks!
Click to expand...
Click to collapse
Try this one. I had seen it on another post. I am not responsible for any problems. Use at on risk
http://www.addictivetips.com/mobile/how-to-restore-and-relock-a-motorola-xoom-tablet/
bigmeltx said:
Try this one. I had seen it on another post. I am not responsible for any problems. Use at on risk
Thanks, but I'm not trying to restore and relock...
Click to expand...
Click to collapse
To unlock bootloader and root try LordAIOTool (or popularly LAIOT), it will do this work for you... Then after I think you already know how to flash if you said you have experience (reboot into recovery blah blah blah)
Sent from my Xoom using Tapatalk HD
Looked through google, looked through threads, can find nothing whatsoever to help.
Have Verizon Samsung Galaxy S III Unlocked running Straight Talk VIA sim card. Everything works.. as a regular old phone with root. (rooted with Kingoroot - basically I googled "root galaxy s3" and followed those steps.. that much works fine, though it is not to be confused with the chinese king root. I tried the trick of swapping out king root for SU and, well.. yeah didnt work.)
Problem is I'm running 4.4.2 (the dreaded locked bootloader) and everything I try when it comes to installing custom recovery either doesn't work, bootloops the phone, or hard bricks it. v_v
so as someone who backs up their backups, (thank you OCD fairy), running around with a phone I can't backup puts me on edge, to say the least.
tried safestrap (says not secured. still says not secured after install. does nothing.)
tried various CWM and TWRP via apk installs (whatever that app is you install then tell it to install cwm) ..wouldn't install
Odin, depending on which version I install (e\ not which version of odin, which version of custom recovery), either gives me errors or hardbricks my device.
SO.. I'm looking for someone who has a Verizon Galaxy S III and who has a custom recovery on it to tell me how the devil they managed that one.
Cheers all!!
Drach0n said:
Looked through google, looked through threads, can find nothing whatsoever to help.
Have Verizon Samsung Galaxy S III Unlocked running Straight Talk VIA sim card. Everything works.. as a regular old phone with root. (rooted with Kingoroot - basically I googled "root galaxy s3" and followed those steps.. that much works fine, though it is not to be confused with the chinese king root. I tried the trick of swapping out king root for SU and, well.. yeah didnt work.)
Problem is I'm running 4.4.2 (the dreaded locked bootloader) and everything I try when it comes to installing custom recovery either doesn't work, bootloops the phone, or hard bricks it. v_v
so as someone who backs up their backups, (thank you OCD fairy), running around with a phone I can't backup puts me on edge, to say the least.
tried safestrap (says not secured. still says not secured after install. does nothing.)
tried various CWM and TWRP via apk installs (whatever that app is you install then tell it to install cwm) ..wouldn't install
Odin, depending on which version I install (e\ not which version of odin, which version of custom recovery), either gives me errors or hardbricks my device.
SO.. I'm looking for someone who has a Verizon Galaxy S III and who has a custom recovery on it to tell me how the devil they managed that one.
Cheers all!!
Click to expand...
Click to collapse
A custom recovery can only be flashed on an unlocked bootloader. Trying to flash a custom recovery on a locked bootloader will result in a brick. The only available recovery on it is safestrap
Sent from my Nexus 5
ShapesBlue said:
A custom recovery can only be flashed on an unlocked bootloader. Trying to flash a custom recovery on a locked bootloader will result in a brick. The only available recovery on it is safestrap
Sent from my Nexus 5
Click to expand...
Click to collapse
..I gathered that. I was basing my attempts off the threads I found where the OP "forgot" to mention which android OS he was using on his (or her) galaxy s3 and then omigawd installed custom recovery on it. Where nobody has yet been able to unlock the 4.3 and 4.4.2 bootloader for the galaxy s3 as yet (to my knowledge; if I'm wrong please correct me) this leaves me with safestrap, the custom recovery that doesn't touch the bootloader during install. I know this as well. Perhaps I should have clarified this, but I thought it was obvious to the folks at xda. *shrugs*
And the part where I said safestrap isn't working for one reason or another is where I was hoping to attract someone who knew how to help instead of someone who only knows how to make generic statements (+1) [e\ ftr, attempting to flash non-safestrap recoveries resulted in an error 4 times out of 5, not a brick.]
that said, I will ask again, if someone has 4.4.2 on their s3 as well as custom recovery, please come post here.
sadly, inb4 more +1ers
When you ask a question that's been asked and answered dozens of times before, you're going to get the same "generic statement" in response, because it's the right answer to your question. Your bootloader can't be unlocked, and therefore you can't install a custom recovery on your phone.
Jacquestrapp said:
When you ask a question that's been asked and answered dozens of times before, you're going to get the same "generic statement" in response, because it's the right answer to your question. Your bootloader can't be unlocked, and therefore you can't install a custom recovery on your phone.
Click to expand...
Click to collapse
*sigh* another illiterate. Try reading before posting yeah? I *know* my bootloader cant be unlocked, and I know that a custom recovery /can/ be installed, or are you saying safestrap doesn't exist? look I'm asking for help here not drivel.
..rerolling..
Q: What did you have for breakfast today?
A1: last week, I had breakfast in Deleware!
A2: Last night's dinner was good!
...
xda: the community where post count means more than relevant answers.
*sigh*
looks like I'm going to have to figure out safestrap on my own. whether there is another method for installation besides via apk, why it failed to install, whether safestrap is the only custom recovery that works by not touching the bootloader, why it hardbricked my phone.. etc
guess I'll post the answers somewhere intelligent like Android Authority.
have fun with your +1s
now go die in a fire. cheers
Drach0n said:
Q: What did you have for breakfast today?
A1: last week, I had breakfast in Deleware!
A2: Last night's dinner was good!
...
xda: the community where post count means more than relevant answers.
*sigh*
looks like I'm going to have to figure out safestrap on my own. whether there is another method for installation besides via apk, why it failed to install, whether safestrap is the only custom recovery that works by not touching the bootloader, why it hardbricked my phone.. etc
guess I'll post the answers somewhere intelligent like Android Authority.
have fun with your +1s
now go die in a fire. cheers
Click to expand...
Click to collapse
Honestly I answered your question. It's hard to talk about safestrap other than what I've learned about it. The other member was right, it gets tiring answering the same questions all the time and once in awhile people don't appreciate the answers they are given.
There are threads for safestrap as well as most of the options here on xda. And feel free to go to another forum, your posting questions in a dying forum for the VZW S3. There's not many people who are really that interested in the locked down version anymore. It's very sporadic as far as people and questions go. But to be rude about it just isn't needed.
It's not about post count at xda it's about helping the community. I've been around here long enough to know this. And if you feel someone isn't helpful there's something called a PM instead of calling them out here on the forums. I grow tired of people not being appreciative of anything when someone takes the time to do there best to explain something to someone else
Sent from my Nexus 5
running 4.4.2
PM sent. I might be able to help with that.