so i had jwr66v rooted with superSU twrp cmw 6.035 or whast ever.
now i have updated to ******y and i tried to flash a ROM in in CWM but it did nothing. at all. i rebooted into recovery only to get a droid on his back with a red ! coming out his belly. um problem here. i opened super Su and it said i need to reroot because i have installed 4.3
how can i reroot if i can't access recovery.
tried using toolkit to reroot (un root to stock first) but it froze now having this problem: post #455
http://forum.xda-developers.com/showthread.php?p=45162727&posted=1#post45162727
anyone?
Just flash recovery from cmd/terminal using fastboot.
Sent from my Nexus 7 using xda app-developers app
never used it. details would be nice.
Want details? There are stickies and tutorials for a reason. Lemme guess, you used a toolkit to root it the first time?
Sent from my Galaxy Nexus
sure I'll follow one of your tutorials. most of the time written as if we know every detail about android development jargon. oh and most tuts have missing details that usually means moderate technical knowledge people have to make assumptions when following those instructions. another issue I'm funding with following "stickies" is because there are so many different ways to update and so many different versions of root tools made by many different clever developers. sometimes they don't all work together. most of the time i will follow some developers half thrown together set of instructions only to have to redo the instructions 3 of 4 times because of the reasons all mentioned above.
short response to your reply. i followed a simple tutorial put up by a developer and most likely used a tool kit. now i have issues. rather then spend countless hours hunting for else who has had the same problem and actually posted it, i decided to ask the question so someone like yourself that enjoys spending hours each night balls deep in code can give me a simple link or basic set of instructions so i can have some relief.
Adb and fastboot. Those are the only tools you need to use.
If I had been in your shoes, I would have done a bit of googling on the term 'fastboot recovery'
I don't know why some people make this so hard. This is a developer site, if you don't want to learn, you shouldn't be here. Considering all this **** is literally spelled out for you with step by step documentation, it doesn't make any sense to click that 'new thread' button when this issue is so common.
Sent from my Galaxy Nexus
yeah googling more is what got me following half arse instructions and wading hours of my day. so which part of your detailed instructions would have led you ( if in my shoes) to Google fast boot recovery?
well I have now downloaded the latest tool kit so i can un root. then I'm going to hunt through countless posts and try find which is the best way to root and install cm10.x hopefully next time their is an update i won't have to reroot just to get all my little root access apps back.
ps this is the trouble shoot q&a section not the developers only section. hence why i posted here.
Welcome to xda-DEVELOPERS.com.
Maybe you missed that part. The domain name isn't xda-hold-lazy-asses-hand-and-make-their-device-cool.com
You are expected to read, comprehend, and take initiative to learn. Asking for a hand holding session is not the way.
If you would bother reading the stickies, you would see how easy it is to flash recovery. There is a tutorial in the damn stickies that literally walks you through the process.
Hint: every goddamn nexus gets rooted and recovery flash the same way regardless of what version of android you are on
I don't know how much more plain and simple we could be here.
Fastboot flash recovery name of recovery.IMG
I mean wtf how could you NOT find that?
Sent from my Galaxy Nexus
since you are being so lazy, and i have obviously had enough to drink tonight:
http://forum.xda-developers.com/showthread.php?t=1907796
http://forum.xda-developers.com/showthread.php?t=2150661
http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro
http://forum.xda-developers.com/showthread.php?t=2072732
http://forum.xda-developers.com/showthread.php?t=2175086
READ!
heres another hint. you need a recovery made SPECIFICALLY for your device 'tilapia'
so..... thanks for the pointless rant, after re read many guides and how tos, also wasting a saturday. still cant get the bootloader to update from version 4.13 (read post 1 again) not even using fastboot. Also read post #455 http://forum.xda-developers.com/showthread.php?p=45162727&posted=1#post45162727
aza510 said:
so..... thanks for the pointless rant, after re read many guides and how tos, also wasting a saturday. still cant get the bootloader to update from version 4.13 (read post 1 again) not even using fastboot. Also read post #455 http://forum.xda-developers.com/showthread.php?p=45162727&posted=1#post45162727
Click to expand...
Click to collapse
Use stock images for Android 4.2 and not 4.3 to avoid that error.
But i'm not sure why you want to flash anything else than recovery? Do you want to get it back to pure stock?
Related
I want to root it and deodex it.
What is the easiest way to go about it.
I read his thread but it says you have to be rooted for it to work.
But i dunno what my OTA or what ever is im just being apprehensive cause i don't wanna go in gung ho and **** it all up!
Thanks guys
First start with the thread Root, Recovery, and Update. Follow the first section called "Note 1" to root and flash clockwork recovery. Then you can follow the steps to flash the Deodexed system. Make sure you make a backup of your system before you try to load the deodex just in case.
Yeah... definitely do your reading before you start cluttering the forums with these silly posts. If you read the Sticky Thread at the top you would not be having these questions. Call me an ass, call me whatever... but if people would just read everything would be so much better.
I did read that thread. it hasnt been updated in like 3 weeks so i didnt want to do something out dated, As i said i didnt know what OTA that would be great if there was a sticky for lingo too. But Im sorry im cluttering your precious little forums bro. Hope you can sleep at night knowing that will be not packed with posts about people looking for advice without people being condescending assholes.
The thread hasn't been updated because Theirs no updates simply everything in the root thread is confirmed and working just follow instructions very carefully and you shouldn't run into problems. But as you know it if "You" screw up then you might can get bricked.
I just followed the One click root method like 5 mins very easy then Clockwork recovery was easy trust me not hard.
Seriously.
I feel that if the first five posts on the forum were just stickied copies of the LOOK HERE FIRST thread, people would still be making these waste-of-space posts.
Human nature, I guess.
I'm happy you got your phone and I share your excitement over it, but I don't really care that you have it, and I don't need to know that, either.
After you're all Deodex'ed, Rooted, and Backed-up, just wait around and lurk like the rest of us until somebody makes something for us.
and btw i learned all of the lingo by typing things i didn't understand into google.
Very well put... lmfao at people getting all butt hurt. Come on mods, delete the thread.
When i run the root with the 1 click method after it says exploiting my phone its going to force the files on it says error: phone not phone. it retries about 5 more times and then it just ends.
Any help?
When you ran the Odin did you click Phone or PDA your suppose to click pda and select the files.. you shouldnt mess up anything if you just read carefully so simple.
I havent got to odin yet. After It restarts my phone and tells me to unlock it it says it should take 3 minutes to finish. It says it error: cannot find phone. this happens when it is trying to put thr.files on the phone.
^^ The same thing happened to me until I downloaded different drivers than what was posted in the one click thread. Google "Samsung Fascinate drivers" and click on the link through Verizon.
I couldn't tell you why the ones in the thread didn't work, but I guess sometimes that's the way it is... Also, the less you have running on your PC the better. I made a different login just for hacking/cell phone stuff that doesn't have much of anything running on startup.
I been at it all day guess I should just wait till something comes out for 4.2.2?
Sent from my Nexus 7 using xda app-developers app
If you don't know how to search on forums, there is something called "Google".
You ask, Google gives the answer. Easy stuff
I am backing up my n7 and setting to factory everything, including locked bootloader just to prove its possible
Code:
C:\temp\nex7>fastboot flash recovery openrecovery-twrp-2.4.1.0-grouper.img
sending 'recovery' (7182 KB)...
OKAY [ 0.951s]
writing 'recovery'...
OKAY [ 1.760s]
finished. total time: 2.718s
flashing recovery works fine
Code:
C:\temp\nex7>adb shell
[email protected]:/ $ su
su
[email protected]:/ #
yep. rooting works just like every other nexus device on any version.
Rooting via Nexus Root Toolkit v1.6.2 for 4.2.2
Hey all,
It seems like the OP may not have too much experience like me based on his post count. The responders on the other hand seem like guru's.
Well I did some troubleshooting after 4.2.2 to try to get the rooting to work (yes, i used google search). Just for the record I'm new to all this, but I've been doing a lot of goog'ling and figured the time I spent troubleshooting may be of help to other novices.
Apparently the rooting issue is well known if you're using the Nexus Root Toolkit v1.6.2 to try and do your rooting. There's a fix available which is described on the main webpage (between the red lines)
google wugfresh for homepage (I can't post links yet)
Just download the zip file and unzip in the folder described, overwriting what's already there there. Make sure your drivers are working . They were acting really finicky for me when using the toolkit but I finally troubleshooted it. If you're having issues you may want to try the newest PdaNet driver, although I didn't have to. Once your drivers are fine, select the Android "any" option and hit root with Custom Recovery checked. I dunno about everyone else but my Custom Recovery was gone/messed-up after upgrading to 4.2.2
If you don't use Nexus Root Toolkit, I recommend it for the less computer savvy ppl out there, like me. Hopefully they'll come out with an update.
Hope this helps.
One newB question I have is can I install my 4.2.1 custom ROMs after upgrading to 4.2.2? I'm not sure if there's some kind of firmware component of 4.2.2 that'll render my Nexus 7 incompatible with the 4.2.1 custom ROMs out there. If it's not okay is it possible to downgrade back down to 4.2.1 from a factory image and then install these custom ROM's?
Thanks ahead of time.
Here's a tip, it seems like your a noob with the nexus 7. In order to mod this thing you should familiarize yourself with command prompt.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jesus people hate noobs here, why doesnt some just show them how to get adb and fastboot going, instruct on how to properly instal the adt and jdk bundles inc path etc. there are no easy tutorials for noobs, if people are expect to learn then teach them, dont forget we were all noobs once.
Sent from my Nexus 7 using XDA Premium HD app
This might help. Go to this link and download the 4.1.2 (JZO54K) image for nexus7 wifi only if that's the one you got and downgrade everything to that and then root and download and install Chainfires SuperSU and SuperSU-Pro from the market and after you install that open SuperSU and check mark Survival Mode and then do the OTA update and you will still have root. Yes you can downgrade. I had to downgrade back to 4.2.1 and do what i said above. You have to have SuperSU Pro installed to use survival mode. its worth the price it cost.
https://developers.google.com/android/nexus/images#nakasi
After downloading the correct images from the link above
Follow these instructions
Nexus 7 Back to Stock
Step 1. fastboot erase boot
Step 2. fastboot format cache
Step 3. fastboot erase recovery
Step 4. fastboot format system
Step 5. fastboot format userdata
Step 6. fastboot flash bootloader bootloader-grouper-x.xx.img
Step 7. fastboot reboot-bootloader
Step 8. fastboot -w update image-nameofzip.zip
Step 9. fastboot reboot-bootloader
After you downgrade your device doing all the steps above then go and root the nexus 7 and install SuperSU and SuperSU-Pro check mark survival mode in superSU and Install busybox also from the google playstore and then do the ota update.
Unlock Boot Loader
fastboot oem unlock
fastboot reboot-bootloader
Lock Boot Loader
fastboot oem lock
fastboot reboot-bootloader
I was 4.2.1 would this still work?
Sent from my Nexus 7 using xda app-developers app
gastonwalpole said:
jesus people hate noobs here, why doesnt some just show them how to get adb and fastboot going, instruct on how to properly instal the adt and jdk bundles inc path etc. there are no easy tutorials for noobs, if people are expect to learn then teach them, dont forget we were all noobs once.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
We don't like noobs because we don't like seeing the same posts over and over and over. I remember when I was a noob, I had no help. I wasn't a member of xda so I learned everything on my own, lots of soft bricks, lots of Googling, and lots of sleepless nights. That's how everyone should learn. You learn more by figuring it out yourself, not being told how. This guy has been told how to root in about every thread he's posted but wont listen. Look at the 5 other posts he's posted, you'll understand why we're annoyed.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
lol
fastboot oem unlock it
fastboot flash a custom recovery
then in that recovery flash the supersu zip from chainfire's thread. I just did this from fully stock and now its rooted
Class_of_punk26 said:
I been at it all day guess I should just wait till something comes out for 4.2.2?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I dunno whats all this fuss about, root 4.2.2 via Nexus 7 toolkit.
I checked today, installed stock 4.2.1, and ota to 4.2.2 than rooted via Nexus 7 toolkit. Select 2nd option, and 2nd option again "install root and busy box". :good:
markj338 said:
lol
fastboot oem unlock it
fastboot flash a custom recovery
then in that recovery flash the supersu zip from chainfire's thread. I just did this from fully stock and now its rooted
Click to expand...
Click to collapse
Sorry i was just trying to help.
AndroidSmitty said:
Sorry i was just trying to help.
Click to expand...
Click to collapse
Hey I wasn't hating on you
I was just saying that if the OP already has 4.2.2 its easy to do it by flashing the supersu zip.
spitfire2425 said:
We don't like noobs because we don't like seeing the same posts over and over and over. I remember when I was a noob, I had no help. I wasn't a member of xda so I learned everything on my own, lots of soft bricks, lots of Googling, and lots of sleepless nights. That's how everyone should learn. You learn more by figuring it out yourself, not being told how. This guy has been told how to root in about every thread he's posted but wont listen. Look at the 5 other posts he's posted, you'll understand why we're annoyed.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Spitfire, it may have occurred to you that not everybody wants to go through that process, reinventing the wheel. Granted, the best way to learn something is doing it and making mistakes, but not always so for someone who just wants to get the job done rather than understand. This is why people here create guides.
If noobs annoy you so much, just let it go and do something else. Leave those with a better temperament to help them.
What's really annoying about this cat is that he has a minimum of 5 threads that he opened for the same issue.
you think thats acceptable behavior?
gastonwalpole said:
jesus people hate noobs here, why doesnt some just show them how to get adb and fastboot going, instruct on how to properly instal the adt and jdk bundles inc path etc. there are no easy tutorials for noobs, if people are expect to learn then teach them, dont forget we were all noobs once.
Click to expand...
Click to collapse
You've probably noticed by now that ROM devs and kernel devs rarely step in over here. There's a reason for that - what they do takes serious amounts of time (usually apart from their day jobs or studies) - and for every one of them there are literally hundreds of less skilled folks asking questions. If they tried to help, they simply wouldn't accomplish their positive contributions.
The other difficulties are:
(1) Forums organize info into a horrible format for learning
(2) The pace of technological change tends to invalidate even valuable posts rather quickly.
That first assertion (1) is made even worse by a flood of posts that scroll valuable (non-stickied) threads off to infinity.
Paradoxically, newbs that insist on creating their own threads for issues that closely resemble the issues covered in other threads are actually, yes, making the site worse for others - especially other newbs that seem to avoid using search.
In the case of this particular OP, he had threads closed and was issued a warning by a mod for exactly the behavior being repeated again here.
Well, if YOU want to create a tutorial, I would encourage you to do so ... & also try to get a mod to sticky the thing.
But don't come in here and say "somebody besides me should do this for the newbs". That's just lame.
The easiest way for beginners is to use Wug's toolkit. All you have to do it update the adb files in the install directory and it will all work. http://forum.xda-developers.com/showpost.php?p=37989110&postcount=1650 <-- Look there
im not an expert yet mate, just started using xda, what i know ive researched, its hard for noobs to find the info required, i dont understand why it has to be so hard for people, if info already exist here why doesnt anyone point them in the right direction, i just dont want others to go through what i went through, people dont talk to each other with respect here, id like to see if they are that up front face to face. once im more confident i will help others dont worry about that, i am trying to already.
cheers
Sent from my Nexus 7 using XDA Premium HD app
Hello
My phone tells me that it is ready to update to Kit Kat.
Before I install Kit Kat I would like to learn how to go back to Jelly Bean if things go t1ts-up.
So, I would like to learn how to root my phone?
I would also like to learn how to backup everything including the Jelly Bean operating system, and I would like to know how to revert my phone back to Jelly Bean?
Please forgive my ignorance, but this whole process genuinely scares me. I have only ever rooted my Samsung Ace phone once and the experience left a bitter taste in my mouth.
I did manage to root my phone. I also thought that I had created a backup but when I tested the backup I discovered that my phone got wiped and I ended up with a brick. I eventually found an official Samsung ROM but it wasn't the one I wanted and it caused a few problems, especially with the Bluetooth feature.
I hope you can understand or appreciate my apprehension with even contemplating such a task on my expensive Nexus 4.
Cheers muchly
the lemming said:
Hello
My phone tells me that it is ready to update to Kit Kat.
Before I install Kit Kat I would like to learn how to go back to Jelly Bean if things go t1ts-up.
So, I would like to learn how to root my phone?
I would also like to learn how to backup everything including the Jelly Bean operating system, and I would like to know how to revert my phone back to Jelly Bean?
Please forgive my ignorance, but this whole process genuinely scares me. I have only ever rooted my Samsung Ace phone once and the experience left a bitter taste in my mouth.
I did manage to root my phone. I also thought that I had created a backup but when I tested the backup I discovered that my phone got wiped and I ended up with a brick. I eventually found an official Samsung ROM but it wasn't the one I wanted and it caused a few problems, especially with the Bluetooth feature.
I hope you can understand or appreciate my apprehension with even contemplating such a task on my expensive Nexus 4.
Cheers muchly
Click to expand...
Click to collapse
You might want to check out the Wugfresh's toolkit if you are not incline with technical stuff. The toolkit is in the Development section.
Hello
I have no idea what Wugfresh's tool-kit is.
Sorry
the lemming said:
Hello
I have no idea what Wugfresh's tool-kit is.
Sorry
Click to expand...
Click to collapse
I would suggest that you study up and follow this guide here. http://forum.xda-developers.com/showthread.php?t=2010312
I was like you when I first got the nexus. Didn't know what to do and the steps seems to be so complicated. Hell..I even took couple of days to finally succeed in installing the drivers. And for me I think it is better to learn the basics of using adb before trying out the toolkits. If you start with toolkits and you will later on rely entirely on the toolkits. This is not good as some problems, the toolkits might not be able to solve it for you.
Btw, look into original android development for wug's toolkits. It is pinned there. Should be easy to find.
Sent from my Nexus 4 using xda premium
You seem to be taking interest in Rooting and stuffs. I would suggest you to get handy with a few ADB and FASTBOOT commands and you won't need any toolkit ever in Life !!!
Its very very very easy in Nexus Devices.
Here is my attempt to make you learn :-
1. Say Bye Bye to your phone OS version.
2. Open Command Prompt or Terminal.(Assuming, you have SDK & Drivers installed)
Code:
adb devices
It shall return you the device id.
3. Reboot to BootLoader
Code:
adb reboot-bootloader
4. Check for your device's recognition in FastBoot Mode.
Code:
fastboot devices
5. I assume you have all the files(Factory Image tar.gz extracted to a folder)
just type :-
Code:
flash-all.bat
BOOM...
You are now on stock KitKat !
Now, To get a Custom Recovery (IMHO go with TWRP),
1. Download latest recovery from the official website.
2. Type when in FastBoot Mode.
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.4-mako.img
(Or whatever the name is)
3. Reboot your device.
Now, to get the ROOT ACCESS, after booting up the device,
1. Download the latest UPDATE-SuperSU zip from here.
2. Keep it somewhere in DEVICE STORAGE.
3. open TWRP RECOVERY
4. FLASH that ZIP
5. HIT THANKS !
Have Fun ...
Welcome to the Flashing Fraternity !!! LOL
miku3191 said:
You seem to be taking interest in Rooting and stuffs. I would suggest you to get handy with a few ADB and FASTBOOT commands and you won't need any toolkit ever in Life !!!
BOOM...
You are now on stock KitKat !
Click to expand...
Click to collapse
Hello
Thank you for replying but I fear that I will not be following your advice at the moment.
I initially asked how to ROOT my phone so that I can learn how to do backups and recoveries. My phone is ready for the Over The Air official upgrade.
I want to take things one step at a time rather than causing problems by blindly following code.
Sorry
the lemming said:
Hello
Thank you for replying but I fear that I will not be following your advice at the moment.
I initially asked how to ROOT my phone so that I can learn how to do backups and recoveries. My phone is ready for the Over The Air official upgrade.
I want to take things one step at a time rather than causing problems by blindly following code.
Sorry
Click to expand...
Click to collapse
If you want official OTA update of KitKat you should update it, and after that unlock bootloader and root phone. That way nothing will go wrong.
If you unlock bootloader and root your phone OTA update will cause problems like stuck in bootloop(your phone will be stuck on nexus logo and it will never boot into android)
If you want to learn about rooting I suggest you this http://forum.xda-developers.com/showthread.php?t=2367406
this is excelent tutorial how to root your nexus 4 http://forum.xda-developers.com/showthread.php?t=2018179
and if you are more comfortable to hear and see somebody do it you can check out this page it have video of full process and pictures for every step http://nexus4root.com/nexus-4-root/how-to-root-nexus-4-windowsmac-osxlinuxubuntu/
Good luck!:cyclops:
miku3191 said:
You seem to be taking interest in Rooting and stuffs. I would suggest you to get handy with a few ADB and FASTBOOT commands and you won't need any toolkit ever in Life !!!
Its very very very easy in Nexus Devices.
Good luck!:cyclops:
Click to expand...
Click to collapse
This process is an absolute nightmare.
All I want to do is back-up my Jelly Bean phone operating system and have it safe in case the OTA Kit Kat goes wrong. I thought that this was sensible and safe practice before doing any updates, especially something as serious as a system update?
I have now tried several Tutorials on how to root my phone and all I have succeeded in doing is wiping my phone clean and returning it to Factory Settings. The latest Tutorial was here
http://forum.xda-developers.com/showthread.php?t=2010312
I followed the following advice to this point
1) All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory;
2) Download the attachment from the end of this post and extract the contents to the directory created in step 1. (Latest version for Windows is here). Note: if all you want to do is unlock your bootloader, skip to step 7 in this section (C).
7) Reboot your device into bootloader mode (by turning it off, hold volume down, and press and hold power) and plug it into your computer;
8) Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt.
I then get to the bit about rooting
E. Optional -- Root
If you want to get root access follow the steps below. (And no, this will not flash a custom recovery, and not, it will not make you "not stock".) Unlocked bootloader required. See steps above.
1) Download (to your computer) the latest version of CWM (from here) or TWRP (from here) for your device;
http://www.clockworkmod.com/rommanager/
http://www.clockworkmod.com/rommanager/developers/mako?name=Google Nexus 4
And when I click the link I am blinded by options. This is a nightmare.
Could somebody please cut through all this hyperbole and just explain how I get ROOT?
I have been at this for 24 hours solid.
the lemming said:
This process is an absolute nightmare.
All I want to do is back-up my Jelly Bean phone operating system and have it safe in case the OTA Kit Kat goes wrong. I thought that this was sensible and safe practice before doing any updates, especially something as serious as a system update?
I have now tried several Tutorials on how to root my phone and all I have succeeded in doing is wiping my phone clean and returning it to Factory Settings. The latest Tutorial was here
http://forum.xda-developers.com/showthread.php?t=2010312
I followed the following advice to this point
1) All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory;
2) Download the attachment from the end of this post and extract the contents to the directory created in step 1. (Latest version for Windows is here). Note: if all you want to do is unlock your bootloader, skip to step 7 in this section (C).
7) Reboot your device into bootloader mode (by turning it off, hold volume down, and press and hold power) and plug it into your computer;
8) Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt.
I then get to the bit about rooting
E. Optional -- Root
If you want to get root access follow the steps below. (And no, this will not flash a custom recovery, and not, it will not make you "not stock".) Unlocked bootloader required. See steps above.
1) Download (to your computer) the latest version of CWM (from here) or TWRP (from here) for your device;
http://www.clockworkmod.com/rommanager/
http://www.clockworkmod.com/rommanager/developers/mako?name=Google Nexus 4
And when I click the link I am blinded by options. This is a nightmare.
Could somebody please cut through all this hyperbole and just explain how I get ROOT?
I have been at this for 24 hours solid.
Click to expand...
Click to collapse
The point you are missing is that your fear is clouding your ability to simply read and comprehend the proper steps to take. My friend rooting your phone with a toolkit is a simple task but you ask what is Wugs toolkit instead of taking the time to search for it an read up. YOu do not want to root your phone but to have someone do it for you. I used to do this for people back in the days where I would log into their pc and root their phones from my home.
My friend its simple your bootloader is unlocked and now all you need to do is push a recovery over to your phone. Now go to the TWRP thread and download the image file and follow the instructions given to you to flash the recovery. I fear if following these simple directions are too much for you maybe you should simply leave your phone alone before the next step is you calling Google with an issue or having to buy another phone...
Sorry but thats my honest opinion....
Edit: Boot into bootloader and check to see if its says unlocked. If so then all thats left is flashing a recovery
the lemming said:
This process is an absolute nightmare.
And when I click the link I am blinded by options. This is a nightmare.
Could somebody please cut through all this hyperbole and just explain how I get ROOT?
I have been at this for 24 hours solid.
Click to expand...
Click to collapse
Reading your posts, I understand your frustration. Here are my suggestions, 1) step away from your PC for a few minutes or an hour or get a cup of water, 2) put the phone aside, 3) read and re-read the information in Google Nexus 4 threads just to get the knowledge first and then start working on your phone. You will be doing fine. BTW, you should have a back up phone that you can use while working on your Nexus 4.
playya said:
Edit: Boot into bootloader and check to see if its says unlocked. If so then all thats left is flashing a recovery
Click to expand...
Click to collapse
Thank you for this useful bit of information.
the lemming said:
Thank you for this useful bit of information.
Click to expand...
Click to collapse
You got it man I know but sometimes the truth hurts... You have been given all the information laid out for you in the posts above. If this is still too difficult for you your only other task is to actually have somebody do it for you this is nothing more than simply reading and taking your time. I tell you this with all sincerity I would rather see you stop now than later see another thread created by you saying possibly bricked
Sent from my Nexus 4 using Tapatalk
---------- Post added at 02:51 PM ---------- Previous post was at 02:51 PM ----------
playya said:
You got it man I know but sometimes the truth hurts... You have been given all the information laid out for you in the posts above. If this is still too difficult for you your only other task is to actually have somebody do it for you this is nothing more than simply reading and taking your time. I tell you this with all sincerity I would rather see you stop now than later see another thread created by you saying possibly bricked
Take care
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Sent from my Nexus 4 using Tapatalk
the lemming said:
And when I click the link I am blinded by options. This is a nightmare.
Could somebody please cut through all this hyperbole and just explain how I get ROOT?
I have been at this for 24 hours solid.
Click to expand...
Click to collapse
I trust that you have read the entire guide from that link you post. To get you see this clearly. Rooting is very easy. You just have to:
1. Install driver, download platform-tools (if you don't wanna download the entire android sdk) and SuperSU I trust that all the links are given in that guide.
2. Make sure you device is detected in adb. Copy SuperSU.zip into your device.
3. Unlock your device.
4. Push recovery. fastboot flash recovery recovery name.img
5. Reboot into recovery and flash SuperSu.zip
6. Reboot. Done.
Really..this is all it takes to perform a simple rooting. But if you're not the one who likes to read..and try to understand the steps. I suggest you not to mess with your device. You are more likely to brick it than make it better. The truth hurts but it is for your own good. Unless you prove me wrong. Then you are awesome instead
Sent from my Nexus 4 using xda premium
I have this shinny new powerful phone and I have no idea what to do with it. I've never got too deep into cell phones. But I want to get the most out of this phone. I pay a lot to be able to use it and I want to get the most enjoyment out of it. I've had it a while now and I haven't really done much to it.
I want to get rid of programs that is just taking up space. I want to get the best apps, learn about the phone. Customize it in cool ways.
Should I root it? Am I too much of a noob and or have too good of a phone to even need to worry about it?
Will you guys hold my hand and walk me through this phone or link me to some "lg g2 starter guide" threads to really have fun with this phone?
Thanks
Aye! First of all, welcome to the G2 community!
It's 4 in the morning for me right now, can we 'go for a walk' after I get my sleep?
Just wanted to reply so you won't feel lost and lonely, been there, done that.
In the meantime, enjoy your G2 first for what it is right now.
Sent from my LG-D802 using xda app-developers app
I feel the exact same way! Except I've had the phone for one month now.
Sent from my LG-D802 using XDA Premium 4 mobile app
Thanks. I bought my phone about two weeks ago. Switched from sprint to verizon after 7 years with sprint
honestly the phone is fast enough by itself with amazing battery, but if you like to get into flashing things first off
http://forum.xda-developers.com/showthread.php?t=2449670 this will teach you how to install TWRP. after that just download a rom of your choosing, more than likely the developer already root the rom for you so you dont need to do it. enjoy from there. make sure you know how to enter TWRP the hard button way... for tmobile is hold down and power button, once LG logo flash quickly let go and press the two button again. thats tmobile though.
I'm a bit of noob to the whole custom ROMS thing as well. I was just wondering what is a good program to make a back up before rooting and installing new ROMS?
TWRP (Team Win Recovery Project) and CWM (Clockwork Mod) both have backup utilities baked in. The stock full system backup will be quite large. Aside from being a best practice, it's too large to archive on the device, in my opinion. I would recommend offloading it to your PC and learn how to put it back using ADB (Android Debug Bridge) and the TWRP sideload feature in the event of a soft brick condition. Recommend you also backup and save your EFS/IMEI.
http://forum.xda-developers.com/showthread.php?t=2451390
First step, ioroot.
Read and re-read on how to root and flash if you've never rooted or flash ROMS before to reduce to risk of bricking.
Sent from my JEE TWO
G1_enthusiast said:
http://forum.xda-developers.com/showthread.php?t=2449670 this will teach you how to install TWRP. after that just download a rom of your choosing.
Click to expand...
Click to collapse
Hi. As someone who has very little understanding about this stuff, I'm struggling to get any use out of that guide. Is anyone else finding this?
For example:
"Ok, so if you look in the download page for your device and you are getting a zip file, this is a flashable zip, but it cannot be treated the same as an IMG file in this guide. You need to flash an older one that is a .img file, and then use that to flash the newer zip."
I have no idea how to do what it says in that last sentence, or what it even means.
Then where it starts describing option one, I don't understand what it's telling me to do. What does it mean to "push" the loki patch and the img? Where am I supposed to type that stuff in the code box?
I figured I'd just get my g2 rooted and back it up, then start reading about the stuff I didn't understand. But just getting started seems really complicated, and I'm struggling find the info I need to understand that guide. Is there a more detailed, baby step guide for idiots out there? Or can someone just quickly explain the things I mentioned about that guide?
Thanks for replies.
http://forum.xda-developers.com/showthread.php?p=45692679. If you need root, try this guide.
Sent from my LG-D800 using Tapatalk
Received device 2 hrs ago. Now stuck with "Error 7" trying to flash CM13 via TWRP
Received device 2 hrs ago. Now stuck with "Error 7" trying to flash CM13 via TWRP
Yeah well, the topic says all. Took the latest image from CM13 but it just won´t flash. Any ideas? So keen on starting with my new device...
688attacksub said:
Received device 2 hrs ago. Now stuck with "Error 7" trying to flash CM13 via TWRP
Yeah well, the topic says all. Took the latest image from CM13 but it just won´t flash. Any ideas? So keen on starting with my new device...
Click to expand...
Click to collapse
Flash the latest bootloader, radio, and vendor. And then go on flashing the ROM.
Any chance to get a quick hint HOW?! I´m rather unexperienced, sorry.
We can see that. lol
688attacksub said:
Any chance to get a quick hint HOW?! I´m rather unexperienced, sorry.
Click to expand...
Click to collapse
http://bfy.tw/4vLn
Just unrooted and unlocked it using the tool kit. Maybe I´ll have another try some other time. For time being I had enough thrill. Thx and n8 boys.
No offense to you but you should have done some reading on how to modify your phone instead of jumping to a toolkit to do all the work for you. Check out Heisenberg's guide in the general section.
688attacksub said:
Received device 2 hrs ago. Now stuck with "Error 7" trying to flash CM13 via TWRP
Yeah well, the topic says all. Took the latest image from CM13 but it just won´t flash. Any ideas? So keen on starting with my new device...
Click to expand...
Click to collapse
Read my guide. Read it again. Then read it again. Then read it some more. Ditch the toolkit. You'll be much better off knowing how to do things for yourself. You really shouldn't be modifying your phone if you don't know what you're doing, you're gonna end up bricking it.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
Read my guide. Read it again. Then read it again. Then read it some more. Ditch the toolkit. You'll be much better off knowing how to do things for yourself. You really shouldn't be modifying your phone if you don't know what you're doing, you're gonna end up bricking it.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
I do like the post you put together. But to say ditch the toolkit means some developer that put together the toolkit isn't getting support. I would agree that you should know what you're doing and how to recover a phone before using a toolkit, and probably should try to do the entire process without the toolkit, but once you got it down, no reason not to use the toolkit.
dbroer91884 said:
I do like the post you put together. But to say ditch the toolkit means some developer that put together the toolkit isn't getting support. I would agree that you should know what you're doing and how to recover a phone before using a toolkit, and probably should try to do the entire process without the toolkit, but once you got it down, no reason not to use the toolkit.
Click to expand...
Click to collapse
I can think of one reason not to use a toolkit: they're known to cause problems. There are threads in virtually every Q&A section that can attest to this.
Heisenberg said:
I can think of one reason not to use a toolkit: they're known to cause problems. There are threads in virtually every Q&A section that can attest to this.
Click to expand...
Click to collapse
I took time to learn how to to everything manually but I still have loads of experiences with tool kits nexus 5 and 7 even previous 6ps that are faulty and have never had a problem with them they simply provide more convenience
Sent from my Nexus 6P using Tapatalk
mystertom101 said:
I took time to learn how to to everything manually but I still have loads of experiences with tool kits nexus 5 and 7 even previous 6ps that are faulty and have never had a problem with them they simply provide more convenience
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I didn't say they cause problems for everyone, if they did they wouldn't be on the site. Anyway, the entire point I was making here, which seemed to be completely lost on some people, is that a beginner shouldn't be using a toolkit, they should be gaining the knowledge that's required (by reading and doing things manually) when you're modifying your phone.
Heisenberg said:
I didn't say they cause problems for everyone, if they did they wouldn't be on the site. Anyway, the entire point I was making here, which seemed to be completely lost on some people, is that a beginner shouldn't be using a toolkit, they should be gaining the knowledge that's required (by reading and doing things manually) when you're modifying your phone.
Click to expand...
Click to collapse
This. Heisenberg is not saying toolkits are useless. The main theme he's trying to employ here is that new users should not be relying on toolkits instead of taking the time to learn the basics of Fastboot before diving into the world of root and mods. When the toolkit fails, Fastboot will rescue you. If you don't know how to use Fastboot, avoidable threads such as this are constantly generated.