I am looking to install TWRP on my wife's newly acquired LG G2. I have already rooted it using ioroot22.
I am looking at using adb to install TWRP. Is this recommended? I have seen some things about the newest firmware not being Loki friendly, and needing to downgrade the about or some such.
I just want to make sure I am using the best and most current method.
I have searched both here and elsewhere, but I am still confused. In a nutshell, I want to know:
What is the best method for installing TWRP?
Do I need to downgrade anything first?
What is the easiest way to do this?
I have rooted our previous phones [EVO 3D, one with a locked bootloader and one with an unlocked bootloader), my friend's Droid RAZR, my current Note 3 and my Tab 3. So I'm not entirely new at this. But I haven't used add since my 3VO (wife got the unlocked one). I'm hoping to avoid it if possible. If not, well, I haven't PERMANENTLY bricked any phones so far, so I'll go that route.
Any help or advice would be much appreciated.
Also, should I just wait for the KitKat update for the G2 to even start messing with my wife's phone?
Edit: used FreeGee app, no adb. EASY and headache free.
Mods please close thread. Sorry.
Sent from my JellyBombed Not3 using xda premium 4 mobile app
Related
is this happening to everyone? Wasn't going to install or even acknowledge that there was an update, because of the boot loader. But i plug it into a charger and 5 minutes later, it is like the phone is giving me the middle finger and accepting the update on it's own, without any question on if i want to or not.
My phone feels violated.
:thumbup:
Sent from my Transformer Prime TF201 using xda app-developers app
Same thing happened to me. O well not ready just yet to brick my s4 lol
Sent from my SAMSUNG-SGH-I337 using xda premium
tried everything i could to stop it, even removed battery as it started the update. was hoping for a brick, don't know why. lol, also not to worried about bricking mine, i am fairly confident in my ability to read, unless the thread is in some language other than english, but then again, now i got s translate!
Sent from my Transformer Prime TF201 using xda app-developers app
You would of had to freeze the ota update apps before hand not to be forced to get it
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Could you please let me know which services to freez with TB on At&t S4 as to avoid forced updates, is it At&T Software Update V 42_1_1303_5_1?
Alos please excuse my noobiness, this is my first android and coming from apple jailbreaks, I of coarse was not happy with closed phone policy so i was researching root options (which i know very little about since its my first android platform). Anyways long story short I rooted using motochopper exploit and got superuser. My questions are:
1. Is motochopper a real root or just tricks the phone into thinking its root?
2. Read about a bootloader hack soon to be released...what exactly is that and what will it give us? also what would be the difference between the motochopper "root" i have on my S4 now and the bootloader hack to be released?
3. Got Ram Manager but was unable to create backup recovery since clockwork mod is not yet released for S4, is that true or is there other ways to use Rom manager?
4. And the last but not least, what should a noob user like myself do, or how can we avoid bricking our phones now that we rooted (with motochopper) or will use the boot-loader hack?
5. is Samsung.Cloud Data Relay 2.1.4 responsible in anyways for forced updates?
Please if you can answer any or all questions I would be so grateful, as im sure many other noobs like myself would be. Please don't think I don't research the subject, its just when you are new to something, you always want to be sure. I am sure logic is to be used and common sense also as to not mess with software service or delete stuff you don't know as to avoid bricking but is there something else to watch out for?
Thnks a million guys
Stokem
unlocking the bootloader will allow us to flash an alternate recovery such as clockwork or twrp and then flash a rom. best bet to avoid a brick is to read everything you can about what you want to do. make sure you read any instructions several times before doing anything to make sure you understand.
sent from my black at&t sgs4
p1gp3n said:
unlocking the bootloader will allow us to flash an alternate recovery such as clockwork or twrp and then flash a rom. best bet to avoid a brick is to read everything you can about what you want to do. make sure you read any instructions several times before doing anything to make sure you understand.
sent from my black at&t sgs4
Click to expand...
Click to collapse
thank you, will there be some custom roms developed for S4 once the bootloader is unlocked or is there some good once already?
also, i read that since AtT can force updates it might patch the bootloader unlock in the future, which processes do we have to freeze in order to avoid it on Att S4. I couldn't find any SDM processes as explained for other S4 carriers. Is it At&T Software Update V 42_1_1303_5_1, do you know by any chance?
I would imagine that roms will be developed & released, but can not say they definitely will.
sent from my black at&t sgs4
Once the bootloader is unlocked Roms will come fast and furious.
To avoid future updates freeze in TB:
AT&T software update
FWUpgrade
LocalFOTA
thank you for your replies. much appreciated
Ok so I got my AT&T S4 successfully rooted using the guide I found on here that uses the Motochopper tool. Root Checker verified I am indeed rooted. But that's it. I'm only rooted to the stock ROM. Nothing custom. Now how to I go about getting a CWM recovery thing on my phone, while still maintaining the stock ROM?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
On the play store, download goo manager (for twrp) or rom manager (for cwm) to install a custom recovery. Don't use either app to do anything but just install the recovery. Once it's installed, boot into recovery and make a backup, even if you're planning on staying stock. Cheers
Step 1. Go to the development forum and read about how to do it.
Step 2. Know how to do it.
Step 3. Do it.
I need more basic. I mean I know CWM means ClockWorkMod, but I don't know what that means. I also know that CWM is more popular than TWRP (I don't know what TWRP stands for) because the rom manager app has tons more downloads in the play store than the goo one does. What is a recovery mode and why do you need one? I mean if I screw up I can just use Odin to flash the AT&T stock ROM back. I wish someone would post a link to a ROMS for Dummies page.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
If I were you I'd be happy that your rooted and now find out what that means to you and what you want to do with a rooted phone. You don't need a custom recovery if all you're interested in is being rooted. And if you mess up, Odin back to stock may not be an option. You may permanently hard brick your phone. So really decide what you want to do with the phone before you proceed any further.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
feetr2c said:
I need more basic. I mean I know CWM means ClockWorkMod, but I don't know what that means. I also know that CWM is more popular than TWRP (I don't know what TWRP stands for) because the rom manager app has tons more downloads in the play store than the goo one does. What is a recovery mode and why do you need one? I mean if I screw up I can just use Odin to flash the AT&T stock ROM back. I wish someone would post a link to a ROMS for Dummies page.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
you really should have read and understood this first: http://forum.xda-developers.com/showthread.php?t=2301762
These guys are correct and trying to help you avoid a brick. If you are not aware of the basics start reading. Even if you are experienced at flashing on another device.
I had extensive experience on HTC phones and feel like a noob here, but getting better. But I have read over a thousand posts, at least, and dozens of how to videos since early may. And only feel comfortable now to flash a custom rom. Not ready yet as phone stock is pretty good for me atm. And would prefer an unlocked bootloader first. I only rooted and flashed a recovery about a week ago. May be a little slower than some, but never got into a problem I couldn't get out of on my HTC phones using the same learning process.
If you come back with specific questions where they know you have researched things they will gladly help. Googling some of the terminology is a good idea too. Had to do that when I first started flashing roms. A different language for sure.
Good luck and enjoy the phone and the rooted world.
In my experience with the S4 CWM does not work as well as TWRP. I had many issues installing a few custom ROMS with CWM, but as soon as i loaded TWRP those ROMS which wouldn't install would install properly. TWRP also was able to read my ext SD when it was formatted in exFat.
Hey all,
Now that there is a monthly snapshot of CM11 out for the G2, I am looking forward to trying it out, but I am googling and confusing myself regarding what the latest and most effective way to unlock the bootloader on the VZW G2.
I am already rooted and have been for some time.
I have found some old guides from September on how to install loki and TWRP, but I am not sure if they are still current, and th ebest way to do things. These forums are great but sometimes they amount to a little information overload finding the right info.
Ideally, I'd like to go with clockworkmod rather than TWRP. If I flash loki to my phone, will I be able to install Clockworkmod using the ROM Manager app? What is the best and most current way to do this?
Thank you,
Matt
Bump?
Noone has a link or any information regarding what the latest way to bypass the bootloader and install recovery is?
You can use Freegee from play store since you are rooted. Gives you the option to install lokified Cwm or twrp with the touch of a button. I used it with no issues.
Sent from my VS980 4G using XDA Premium 4 mobile app
Hello, I've been doing a bit of research on my own, and I haven't found any straight answers. Recently, I downloaded the leaked Verizon Kitkat OS. From what I hear, this is the build I should be staying on. That's great and all, but I was wondering if there is any way for me to be able to root from 4.4.2 and be able to install some custom roms. Sorry if this is redundant in any way to what you guys normally see on here, but I am really confused on where all to start with this rooting process.
Also, I've seen people running custom roms on kitkat on the SM-900V, so I know it's possible. I just need a guide for dummies on how to do it.
Thanks again
The best way to root kitkat is installing twrp and when you boot system it asks if you want to root.
Sent from my P6-U06 using XDA Free mobile app
Philfactor said:
Hello, I've been doing a bit of research on my own, and I haven't found any straight answers. Recently, I downloaded the leaked Verizon Kitkat OS. From what I hear, this is the build I should be staying on. That's great and all, but I was wondering if there is any way for me to be able to root from 4.4.2 and be able to install some custom roms. Sorry if this is redundant in any way to what you guys normally see on here, but I am really confused on where all to start with this rooting process.
Also, I've seen people running custom roms on kitkat on the SM-900V, so I know it's possible. I just need a guide for dummies on how to do it.
Thanks again
Click to expand...
Click to collapse
Use towelroot method then install latest superuser from chainfire website and then install safestrap. After you've done this you will be able to flash some custom TW roms. You cant get AOSP roms on the vzw retail note 3 yet because the bootloader is still locked.
Sent from my SM-N900V using XDA Premium 4 mobile app
Hello there,
I've had an AT&T Galaxy S4 for about a year now and I've been on custom ROMs since January of this year. When I was last on Stock, I had Android 4.2.2 Jellybean. Recently, I've been running into a lot of problems with my ROM so I tried installing other ROMs only to find more issues that were bothering me. I decided to just go back to stock but I was curious as to whether taking an OTA update will ruin my root? I do apologize for asking this but I'm still rather new at this. I was also curious if taking the OTA will remove my custom recovery as well as re-lock my bootloader? If I'm not supplying enough information for someone to determine the answer, please let me know and I'll provide that information.
BrokeEven said:
Hello there,
I've had an AT&T Galaxy S4 for about a year now and I've been on custom ROMs since January of this year. When I was last on Stock, I had Android 4.2.2 Jellybean. Recently, I've been running into a lot of problems with my ROM so I tried installing other ROMs only to find more issues that were bothering me. I decided to just go back to stock but I was curious as to whether taking an OTA update will ruin my root? I do apologize for asking this but I'm still rather new at this. I was also curious if taking the OTA will remove my custom recovery as well as re-lock my bootloader? If I'm not supplying enough information for someone to determine the answer, please let me know and I'll provide that information.
Click to expand...
Click to collapse
One question my bro, what galaxy s4 do you have?
Sent from my SGH-I337 using XDA Free mobile app
I don't know the specific model name but I know it's the Galaxy S4 for AT&T
BrokeEven said:
I don't know the specific model name but I know it's the Galaxy S4 for AT&T
Click to expand...
Click to collapse
If you don't know what model you're on you shouldn't be rooted. The at&t version is the i337, and yes if the ota works you'll lose root.
And questions go in the q&a forum, not general
Sent from my Nexus 5 using XDA Free mobile app
you need to know your build first, so you can install right .tar
odin will replace everything. except sdcards. best to back up cards anyway and/or pull ext card.
use terminal emulator and type in
SU
getprop ro.bootloader
it will give you your build--:good:
btw your bootloader was never unlocked on an i337.
EDIT: Beat me jd
Oh really? Cuz whenever I turn my phone on it shows a pad lock unlocked. The same animation appeared on my Galaxy Nexus when I had it so I just assumed the bootloader was unlocked
No, that comes up in the rooting process. The i337 has not been unlocked. There is an exploit called loki-doki for pre MF3 builds that bypasses Sammy's security checks. It allows those of us on early build to flash custom recoveries/kernels. Otherwise you need to use SafeStrap and only TW roms. If you are not familiar with SafeStrap then you are probably on a pre MF3 build.
Some people refer to the exploit as unlocking the phone. That's incorrect though--
You should get the ota root keeper, it backs up the root, then after ota update, you can restore back.
Sent from my XT1031 using XDA Free mobile app