Develop Bugs

[Q] I think I now own a galaxy nexus paper weight lol

I was on the latest codename and everything was working fine, but wanted to see how 4.0.4 was running as is. I downloaded the stock AOSP build that was flashable by nikademus, downloaded gapps/root files as well. Followed instructions so far so good. Booted up and noticed that the ICS animation was gone and was replaced by just the "android" with the lighting going through it animation. Didn't really care about that so i let the phone do its thing, once it was done and i completed the account setup i rebooted like i normally do when flashing roms. when the phone came back I went into the settings to verify i was on the current version. I noticed that it said 4.0.4 0 4.0.4, thought that was odd and then something else that was odd was that my market was completely blacked out and the only way to see anything was the select something and then it would become visable. By then I knew something was wrong so i tried to boot into recovery via rom manager but it would not do anything. I tried to flash a custom recovery image again and it didnt let me because of su commands ? or something like that. At this point im freaking out because I have no SU permissions apparently, no CWM recovery, and the rom that im using is clearly messed up(not saying its the rom, it was probably something i did wrong) so i tried to use the galaxy nexus root toolkit program by WugFresh. I was going to try to go back to stock+unroot and then root after. I downloaded 4.0.2 and followed the command prompts and everything seemed to be working fine but when the phone was supposedly booting up it just got stuck on the Google screen with the unlocked padlock for a long time. I didnt see no boot animation or anything for about 10 min.
So I have no clue how to recover from this =(
Is my phone a paper weight now ? or can it be fixed ?
someone help me please lol

Flash the stock images from Google with fastboot.
http://forum.xda-developers.com/showthread.php?t=1366806

Enhanced said:
Flash the stock images from Google with fastboot.
http://forum.xda-developers.com/showthread.php?t=1366806
Click to expand...
Click to collapse
but i cant even get adb to see my device?
in order for me to use fastboot dont i need adb setup ?
I had adb setup but after this issue i cant go no further then the google screen

Enhanced said:
Flash the stock images from Google with fastboot.
http://forum.xda-developers.com/showthread.php?t=1366806
Click to expand...
Click to collapse
^^^ what he said.
I have yet to see a bricked Galaxy Nexus.
Sent from the future.

okay so I was able to flash the google images using fastboot (thank god) =)
but by me doing this did i loose root permissions ?

AnthonyAldrete said:
okay so I was able to flash the google images using fastboot (thank god) =)
but by me doing this did i loose root permissions ?
Click to expand...
Click to collapse
Yes you're completely stock.

No more wugs for you sir.
You need to learn how to do this manually.
Check my sig.

All you need to do is unroot the nexus back to stock, gnex toolbox. Then reroot
Sent from my Galaxy Nexus using XDA

halifaxjesse said:
All you need to do is unroot the nexus back to stock, gnex toolbox. Then reroot
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
10 chars.

[Tutorial] Rooting the Sprint GalaxyS3 the Easy Way

Mods, please lock this thread.

Thanks skunk ape!
Sent from my SPH-L710 using xda premium

Thread stuck!

The zip would not flash in recovery, phone is running the official jellybean.
Any ideas?
Sent from my SAMSUNG-SGH-I747 using xda premium

los0325 said:
The zip would not flash in recovery, phone is running the official jellybean.
Any ideas?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Which zip would not flash in recovery?
The only zip you will flash in recovery is team epic root from recovery. And it must be flashed in the recovery that was installed with Odin.
If you let the phone restart after flashing recovery in Odin the custom recovery will be replaced by the stock recovery.

Skunk Ape1 said:
Which zip would not flash in recovery?
The only zip you will flash in recovery is team epic root from recovery. And it must be flashed in the recovery that was installed with Odin.
If you let the phone restart after flashing recovery in Odin the custom recovery will be replaced by the stock recovery.
Click to expand...
Click to collapse
Omg bro I'm so sorry, I feel like a noob
Sent from my SAMSUNG-SGH-I747 using xda premium

los0325 said:
Omg bro I'm so sorry, I feel like a noob
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
So you figure it out?

Skunk Ape1 said:
So you figure it out?
Click to expand...
Click to collapse
Yes sir I did thanks
Sent from my SAMSUNG-SGH-I747 using xda premium

Will this work with the latest update and does it wipe data?

jstn76rs said:
Will this work with the latest update and does it wipe data?
Click to expand...
Click to collapse
It will not wipe any data and can be used to root any version android on the Sprint gs3.

Skunk Ape1 said:
It will not wipe any data and can be used to root any version android on the Sprint gs3.
Click to expand...
Click to collapse
Thanks for the quick reply. Will give this a go as soon as my wife gives me the ok.

jstn76rs said:
Thanks for the quick reply. Will give this a go as soon as my wife gives me the ok.
Click to expand...
Click to collapse
Really?
If you need anything, I monitor this thread and will provide support if needed.

Thanks!
As a TOTAL noob: appreciate the easy explanation! Waiting to do this myself, but have a few quick questions first. I've done a lot of reading up on rooting but I'm still not entirely clear on a few things so I'm hoping someone can explain it to me like I'm five:
1. Can I accept over-the-air updates from Sprint on a rooted phone? i.e. when they push Android 4.2. If not, do I unroot and reroot to update? Do I have to uninstall everything?
2. Is there something I need to install after doing this? I previously rooted an HTC EVO and remember having to install Superuser immediately after. Anything similar here? Looking to ultimately run wifi tether so any advice toward that end would be greatly appreciated.
3. I'm a little confused about rooting/flashing and some basic definitions. Are they the same thing? I hear a lot about CyanogenMod - what is it and is it coming into play here?
Thanks so much!!

As a TOTAL noob: appreciate the easy explanation! Waiting to do this myself, but have a few quick questions first. I've done a lot of reading up on rooting but I'm still not entirely clear on a few things so I'm hoping someone can explain it to me like I'm five:
1. Can I accept over-the-air updates from Sprint on a rooted phone? i.e. when they push Android 4.2. If not, do I unroot and reroot to update? Do I have to uninstall everything?
This is not going to be a straight up yes or no answer. If an update comes ota to your phone, you will be able to receive it providing you:
1. reflash stock recovery before accepting it.
2. haven't flashed a custom rom
3. haven't removed any required software. The ota will look for certain software and files. if the required software and files aren't present the ota will fail
None of this should concern you though. There are ALWAYS ways to get the updates while being rooted
2. Is there something I need to install after doing this? I previously rooted an HTC EVO and remember having to install Superuser immediately after. Anything similar here? Looking to ultimately run wifi tether so any advice toward that end would be greatly appreciated.
These instructions seem like you are doing many things. You aren't. There are really only 5 steps. I just broke all the steps down in detail. Really all this is:
1. Downloading all the files to your computer
2. Installing your Samsung Drivers to your computer
3. Copying one file to your phones sd or external sd card. (Team_Epic Root_From Recovery)
4. Flashing CWM Recovery to your phone with Odin.
5. Flashing TeamEpic-Root-from-Recovery-v5.zip with CWM Recovery
The Team Epic File that you are flashing in recovery installs superuser, busy box, and in addition removes two files needed to make recovery stick.
3. I'm a little confused about rooting/flashing and some basic definitions. Are they the same thing? I hear a lot about CyanogenMod - what is it and is it coming into play here?
Rooting is really nothing more than giving you the user, the right to access root or system files. It has very little to do with flashing as you can flash updates with stock recovery.
Flashing is simply installing something in a tar, img, or zip format. tar files are flashed with Odin, zips are flashed from recovery and img files are flashed or pushed with adb (Android Debug Bridge)or fastboot.
Cyanogen is a rom. roms are very simply the phones operating system and user interface. They're called roms because their files are kept on read only memory. There are many roms out there for our phone.

Awesome, appreciate the prompt response - thanks so much!!

Thanks!
Thanks for putting this together. My new gs3 arrives tomorrow and I have already prepped my computer with your files in anticipation.
I'll report back how it works out.
Thanks again!

One more thing
When I do get my phone should I activate it first or root it first or does it matter?
I know it voids the warranty but I guess I could unroot to take it in for service if needed?
Thanks again.

brianando said:
When I do get my phone should I activate it first or root it first or does it matter?
I know it voids the warranty but I guess I could unroot to take it in for service if needed?
Thanks again.
Click to expand...
Click to collapse
I would activate it.

This works with the 4.1 update, correct?

I previously had the Galaxy S1 (Epic) and went through several custom ROMs before finally going back to a stable release with root because of dissatisfaction with the ROMs. My phone never really returned to perfect functionality after this experimentation, and always had some buggy glitches and many FC's. Now that I have a perfectly running GS3 with Android 4.1, I would love to be able to wifi tether and install apps like adblock and Titanium Backup Pro, but I am hesitant because of my past experience.
Do you think there is any reason at all that simply doing this root procedure would change the functionality of my perfectly smooth-running GS3?

Custom rom flashed. Boots 1st time not 2nd

I have lots of experience flashing android roms and this may be a first for me.
Flashed latest MMuzzyrom 4.3 vanilla. Originally had latest stock rooted.
Everything worked flashed full gapps for 4.3 right after it and booted right into android. Everything was previously wiped clean. rebooted soon after and it stick on "google" with "unlock"
screen for half an hour before giving up.
Tried second time and booted right into the new rom. I forgot about the previous reboot issue. spent all day getting most of my apps installed and everything setup. Went to reboot and same crap . Tried clearing cache and dalvik no help.
Wish I would have not wasted my time. I only wish their is a way to salvage this before flashing another rom or a stock image.

wseyller said:
I have lots of experience flashing android roms and this may be a first for me.
Flashed latest MMuzzyrom 4.3 vanilla. Originally had latest stock rooted.
Everything worked flashed full gapps for 4.3 right after it and booted right into android. Everything was previously wiped clean. rebooted soon after and it stick on "google" with "unlock"
screen for half an hour before giving up.
Tried second time and booted right into the new rom. I forgot about the previous reboot issue. spent all day getting most of my apps installed and everything setup. Went to reboot and same crap . Tried clearing cache and dalvik no help.
Wish I would have not wasted my time. I only wish their is a way to salvage this before flashing another rom or a stock image.
Click to expand...
Click to collapse
I have lots of experience as well and this is the first time I've run into this issue. The same **** has been happening to me on all 4.3 ROMs. I had to wipe everything, including internal storage, and reflash a 4.2.2 ROM to solve it. Wish I knew the issue here.

I decided to try flashing a different 4.3 ROM and it hung up for some reason during booting. I then decided to flash the factory image. Then tried the different ROM I downloaded. Seems to be good now. I still don't know what caused it but life is good now.
Sent from my Galaxy Nexus using Tapatalk 2

Can I ask where you found the factory image? I just picked up a Gnex so I'm still figuring everything out

playpolo4life said:
Can I ask where you found the factory image? I just picked up a Gnex so I'm still figuring everything out
Click to expand...
Click to collapse
Sorry not sure. Had it saved on my hard drive for a while. Try to download galaxy root toolkit I think it has the ability to download it for you if I remember right.
Sent from my Galaxy Nexus using Tapatalk 2

playpolo4life said:
Can I ask where you found the factory image? I just picked up a Gnex so I'm still figuring everything out
Click to expand...
Click to collapse
wseyller said:
Sorry not sure. Had it saved on my hard drive for a while. Try to download galaxy root toolkit I think it has the ability to download it for you if I remember right.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Wow.
GOOGLE!
Literally Google hosts the damn images for you.
Search for galaxy nexus factory images.
Did everyone forget who gives us this OS? A search company.
Sent from my Galaxy Nexus

What I can't understand is that I have no issues on stock. Zero. Is my device the best device in the world?
Why are you people flashing 4.3 "vanilla ROMs" through a custom recovery when we've got FACTORY IMAGES.
Is it really that hard to root a stock rom? Just follow the whole situation going on with su and you'll know!
Oh and drop the damn toolkit.

Pirateghost said:
Wow.
GOOGLE!
Literally Google hosts the damn images for you.
Search for galaxy nexus factory images.
Did everyone forget who gives us this OS? A search company.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
beekay201 said:
What I can't understand is that I have no issues on stock. Zero. Is my device the best device in the world?
Why are you people flashing 4.3 "vanilla ROMs" through a custom recovery when we've got FACTORY IMAGES.
Is it really that hard to root a stock rom? Just follow the whole situation going on with su and you'll know!
Oh and drop the damn toolkit.
Click to expand...
Click to collapse
You guys need to chill out, that's for damn sure.

Little help with the new stuff

So my n7 has been down for the past 2 months cause of poor Asus service on an RMA. Took me sending the unit in 3 times before they gave me a new device.
I feel so out of the loop and overwhelmed
Anyways, I was unlocked manually, rooted with wugs tool and twrp recovery flashed with wugs tool. Is this still all possible to do on kit Kat, the latest update?
What's the best ROM and or kernel being run out there in you guys opinions. This is the biggest thing that's overwhelming since development has taken off in the last 2 months IMO.
Thanks for any help and tips, I appreciate it guys/girls!
Sent from my Nexus 7 using Tapatalk

Yeah you can still do that..
If you unlocked manually you know how to use fastboot so just flash twrp or cwm with that. No need for a toolkit.
Rom/kernels up to you man. Depends what you want, see what they offer, there is no best. I like CM myself.

Alright thanks. Yeah, I'm familiar with fastboot. I'll just do that. How do I root though if I fastboot install twrp?
Sent from my Nexus 7 using Tapatalk

Right now I am running SinlessRom with ElementalX kernel and the ROM is liquid smooth, scored 28205 in anTuTu (overclocked). Have tried BS Harmony CM based but I just don't like the look of it and CM ROMs used to be my fav.

Where do I find the proper super su zip to root after fastboot flashing twrp?
Sent from my Nexus 7 using Tapatalk

silver04v said:
Where do I find the proper super su zip to root after fastboot flashing twrp?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Google chainfire supersu

evoer said:
Google chainfire supersu
Click to expand...
Click to collapse
I found this , do I just DL the flashable zip and flash it, then reboot and its rooted? I've never rooted this way before. Can you give me a hand?
http://forum.xda-developers.com/showthread.php?t=1538053
Sent from my Nexus 7 using Tapatalk

With all due respect, sure we could walk you through the process but really, do yourself a favor and do some reading to learn all that is required. Familiarize yourself with everything first, in the end you'll be thankful you did. After all...learning is part of the fun. Lots of folks use a toolkit like wugfresh's to unlock, root, install recoveries, etc.

Yeah, I know the steps, just not sure if I'm looking in the right spot. Guess I'll read more in that thread to find out if it's the right one......
Sent from my Nexus 7 using Tapatalk

I've done it before, it just been awhile and it wasn't on kit Kat so all my files I have now are outdated I'm sure.
Sent from my Nexus 7 using Tapatalk

Guide to Update to KitKat on a Rooted Phone

Hi All,
With all the threads about bricked phones, I wanted to take the safer route and outright ask for the best method to upgrade to KitKat on a rooted phone running 4.2.2 stock? I've already 'bricked" my phone once last year doing an OTA update, so I'm trying to avoid doing that again. I know this is a noob question, but I haven't been able to locate a sprint specific guide consolidating all of the information out there. Any help is appreciated.
Sprint LS980ZV7
4.2.2 stock on a rooted phone
twrp installed
IOroot25
Kernel: 3.4.0

thadeus_d3 said:
Hi All,
With all the threads about bricked phones, I wanted to take the safer route and outright ask for the best method to upgrade to KitKat on a rooted phone running 4.2.2 stock? I've already 'bricked" my phone once last year doing an OTA update, so I'm trying to avoid doing that again. I know this is a noob question, but I haven't been able to locate a sprint specific guide consolidating all of the information out there. Any help is appreciated.
Sprint LS980ZV7
4.2.2 stock on a rooted phone
twrp installed
IOroot25
Kernel: 3.4.0
Click to expand...
Click to collapse
Use this thread for the files
http://forum.xda-developers.com/showthread.php?p=51557219
Or you can use this one to flash zvc tot file straight to phone.
http://forum.xda-developers.com/showthread.php?p=45293512
The second post as you read will give information I thought a bit more clear on Sprint.
@#***This will wipe your phone as in complete. Nothing will be left of yours. So copy anything off internal [email protected]#***
Follow the directions, use ioroot25. Root.
If you want custom recovery.
http://forum.xda-developers.com/showthread.php?p=51857807
Use auto-rec from above thread. Thank cloudyfa for putting that together.
If you reboot after and screen shuts off and you get white lines.
You might a well tot back to zvc and just root. @Cloudyfa on that same thread is working out the details to fix.
Sent from my Nexus 7 using Tapatalk

secret.animal said:
Use this thread for the files
http://forum.xda-developers.com/showthread.php?p=51557219
Or you can use this one to flash zvc tot file straight to phone.
http://forum.xda-developers.com/showthread.php?p=45293512
The second post as you read will give information I thought a bit more clear on Sprint.
@#***This will wipe your phone as in complete. Nothing will be left of yours. So copy anything off internal [email protected]#***
Follow the directions, use ioroot25. Root.
If you want custom recovery.
http://forum.xda-developers.com/showthread.php?p=51857807
Use auto-rec from above thread. Thank cloudyfa for putting that together.
If you reboot after and screen shuts off and you get white lines.
You might a well tot back to zvc and just root. @Cloudyfa on that same thread is working out the details to fix.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thank you for the reply. I'll give this a shot tonight!

I have a question: I already screwed up and applied the KitKat update to my rooted G2 without thinking. It's now stuck booting to TWRP, where I was a moron and of course didn't create a backup at any point. Is there a way for me to sideload the ROM onto my phone at this point?
Any ideas?

Coop1979 said:
I have a question: I already screwed up and applied the KitKat update to my rooted G2 without thinking. It's now stuck booting to TWRP, where I was a moron and of course didn't create a backup at any point. Is there a way for me to sideload the ROM onto my phone at this point?
Any ideas?
Click to expand...
Click to collapse
Even sideload may not help you, if you can access down load mode. You might get to use tot, back to stock.
But there is no stock zvc yet for ls980.
Sent from my Nexus 7 using Tapatalk

secret.animal said:
Even sideload may not help you, if you can access down load mode. You might get to use tot, back to stock.
But there is no stock zvc yet for ls980.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thank you for that suggestion. I was able to use Download Mode to fix my G2 and then OTA the KitKat update. Your post saved my phone.
Sent from my Nexus 7 using Tapatalk

I must have gotten lucky...wasn't thinking and took the OTA a while ago. Lost root but phone is fine.
Now...I'm off to find it again so I can get tether working

thadeus_d3 said:
Thank you for the reply. I'll give this a shot tonight!
Click to expand...
Click to collapse
To the OP, can I ask which method you chose and how it went? I need to do this as well and I'm in the same boat as you (rooted ZVA with custom recovery).
Thanks.
Ed

esoh said:
To the OP, can I ask which method you chose and how it went? I need to do this as well and I'm in the same boat as you (rooted ZVA with custom recovery).
Thanks.
Ed
Click to expand...
Click to collapse
I actually read a bit more and decided to hold off on the update. I'm happy with my phone's performance, so I really don't have the time to troubleshoot should the update go awry.

thadeus_d3 said:
I actually read a bit more and decided to hold off on the update. I'm happy with my phone's performance, so I really don't have the time to troubleshoot should the update go awry.
Click to expand...
Click to collapse
I'm the same way, but I figured that I should just go ahead.
So I'll throw that out, anyone pick one of these methods have a preference? I'm on TWRP, rooted, stock ZVA. Some mods including tether and camera. Thanks.