Hello guys.
I just bought a used Galaxy Nexus running the latest 4.3 android.
Unfortunately, i'm seeing quite heavy battery drain and the device is really slow compared to a friend's 4.1.2 or even 4.2.2 firmware.
The phone is not rooted, it is completely stock.
I looked around the forums and even downloaded the galaxy nexus toolkit, but i coult not determine how to safely downgrade to 4.1.2 android.
Can you please point me in the right direction or advise how i can safely downgrade without bricking my phone or messing anything up?
Well, all you have to do is download the factory image for 4.1/4.2 and flash it via fastboot, Google is your friend, but its not that hard
Sent from my Gnex VZW [[email protected] GHz] on [crDroid AOSP]
IRX120 said:
Well, all you have to do is download the factory image for 4.1/4.2 and flash it via fastboot, Google is your friend, but its not that hard
Sent from my Gnex VZW [[email protected] GHz] on [crDroid AOSP]
Click to expand...
Click to collapse
thank you.
I will try to use the nexus toolkit, to download and flash 4.1.2
bogdan89 said:
thank you.
I will try to use the nexus toolkit, to download and flash 4.1.2
Click to expand...
Click to collapse
Please don't use a toolkit.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
Please don't use a toolkit.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
he and anyone else can use a toolkit if they so desire. what you should have said is if you use a toolkit, don't post about any problems loading the factory image should they arise. yes, the right way to do it is fastboot, but telling someone what they can and can't use isn't the right way to go about helping them. to the OP, consider that a warning. if you use the toolkit and have problems, take it to the toolkit thread, not here and don't start another thread. or use the fastboot method and if you have a problem, then we may be able to help you. using fastboot helps us narrow down where something went wrong. in a toolkit, since it's all automated, you can't really figure out what happened if it borks something.
---------- Post added at 03:24 PM ---------- Previous post was at 03:23 PM ----------
also, if you want, read over this thread carefully if you want to use fastboot.
http://forum.xda-developers.com/showthread.php?t=1626895
t1.8matt said:
he and anyone else can use a toolkit if they so desire. what you should have said is if you use a toolkit, don't post about any problems loading the factory image should they arise. yes, the right way to do it is fastboot, but telling someone what they can and can't use isn't the right way to go about helping them. to the OP, consider that a warning. if you use the toolkit and have problems, take it to the toolkit thread, not here and don't start another thread. or use the fastboot method and if you have a problem, then we may be able to help you. using fastboot helps us narrow down where something went wrong. in a toolkit, since it's all automated, you can't really figure out what happened if it borks something.
---------- Post added at 03:24 PM ---------- Previous post was at 03:23 PM ----------
also, if you want, read over this thread carefully if you want to use fastboot.
http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Of course. And it also is amazing that people created the toolkits! They're easy to use. I wasn't telling the OP he may not use a toolkit but he should not use a toolkit. Fastboot works some better.
Sent from my Nexus 10 using XDA Premium HD app
true, it does work better than a toolkit. you have absolute control over what is happening on your phone. but some people are intimidated by fastboot, i was at first, but i learned. that's why i gave him the option, not just don't use a toolkit. either way is gonna get him where he needs to go, but sometimes you need to go the toolkit route before you learn the other way and its up to him to decide.
Related
yup, i'm that noob you guys complain about... totally open to all general flaming attacks....
decided it was time to unlock and root....
being a total dumbass, i first did this: http://forum.xda-developers.com/showthread.php?t=1362957
phone stuck in reboot cycle. this was for gsm and i have lte, yup major oops.
tried gn toolkit 2.2 and now constantly get a write error on anything i try for all options.
didd i brick my phone? anything i can do to just get back to factory? thought i knew what i was doing after my droid and droid x. apparently i should stick with stock. so sorry guys. any help appreciated.
Can you boot into fastboot or recovery? If you can get into either you'll be fine.
i can get into fastboot just fine. just don't know what to do from there. i get write errors from toolkit 2.2
I have no idea about the toolkit, you can just use fastboot to flash clockwork recovery or boot a boot.img or system.img
As long as you can get into bootloader mode ... you can still follow the manual steps in the same post (post # 3) if automated Toolkit doesn't work. give that a shot.
Edit: lol, ikon8 beat me to it ...
enaybee said:
As long as you can get into bootloader mode ... you can still follow the manual steps in the same post (post # 3) if automated Toolkit doesn't work. give that a shot.
Edit: lol, ikon8 beat me to it ...
Click to expand...
Click to collapse
Yea, just follow the directions in post #3 of that thread. Forget that toolkit mess and just do it all manually.
everything either says cannot write too many.... or it says failed to write or failed to load...
Have you already unlocked the bootloader? fastbook oem unlock
---------- Post added at 10:01 PM ---------- Previous post was at 09:47 PM ----------
Try Paul's Superboot, it contains all the binaries you'll need to get it rooted. Make sure to unlock bootloader first then just follow his instructions.
No flame here brotha we all know what it feels like. From reading the posts above you can get into boot loader so you'll be ok. Just read thoroughly, maybe drink some coffee, read again and you should be good to go.
Sent from my Google phone
may be simpler than i thought... problem is my pc is not unzipping the google .tar file. winzip free can't figure it out. good way to go about unzipping this without paying?
wadec22 said:
may be simpler than i thought... problem is my pc is not unzipping the google .tar file. winzip free can't figure it out. good way to go about unzipping this without paying?
Click to expand...
Click to collapse
I don't know anything about windows but I think 7zip will work, it's free and open source.
ikon8 said:
I don't know anything about windows but I think 7zip will work, it's free and open source.
Click to expand...
Click to collapse
7-zip will, in fact work. It's my go-to compression/decompression tool.
1.21Gigawatts said:
7-zip will, in fact work. It's my go-to compression/decompression tool.
Click to expand...
Click to collapse
why did you necro a thread from 8 months ago?
Zepius said:
why did you necro a thread from 8 months ago?
Click to expand...
Click to collapse
Not just this thread.
Sent from my Galaxy Nexus using xda premium
He's going for 10 posts and pulling up old threds cause he has no idea how to contribute ;/
Sent from my Galaxy Nexus using xda premium
Has anyone seen this? I can't flash anything at all via the toolkit or ADB or fastboot.
On my nexus's screen it keeps saying this at the bottom in blue:
Fastboot Status - FAILWrite Fail
Here's the background. My bootloader is unlocked. I have root or had (when i "upgraded" to 4.0.2 superuser is there but I can't seem to give anything root access anymore).
I decided to start fresh and just wipe the phone and use the factory images to install 4.0.4 onto the phone. But it seems no matter which drives I try, ADB just won't recognize my phone in bootloader mode.
You're doing it wrong.
iphone. helping computer illiteracy become popular since 2007.
@rbiter said:
You're doing it wrong.
iphone. helping computer illiteracy become popular since 2007.
Click to expand...
Click to collapse
Thank you for the extremely helpful response.
Does anyone else have any ideas?
ksc6000 said:
Thank you for the extremely helpful response.
Does anyone else have any ideas?
Click to expand...
Click to collapse
uhhhh did you even unlock your bootloader?
Sent from my Galaxy Nexus using xda premium
Diger36 said:
uhhhh did you even unlock your bootloader?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yes, it's unlocked.
Make sure you have the galaxy nexus files? I was a moron and had same issue when I accidentally downloaded nexus s
Sent from my Galaxy Nexus using xda premium
ksc6000 said:
Yes, it's unlocked.
Click to expand...
Click to collapse
Sorry, didn't read your OP right... My mistake.
Do you have a proper backup? If so: Maybe a lock and unlock bootloader might work. It's just a long shot but the message triggers me in that direction. Off course you will loose all your data, inclusing on /sdcard.
Diger36 said:
Sorry, didn't read your OP right... My mistake.
Do you have a proper backup? If so: Maybe a lock and unlock bootloader might work. It's just a long shot but the message triggers me in that direction. Off course you will loose all your data, inclusing on /sdcard.
Click to expand...
Click to collapse
Worth a try. I don't mind losing everything as I made a backup of the SD card on my computer before attempting.
EDIT: Nope, was able to re-lock and unlock the bootloader but still when trying to flash anything it says: FAILED <remote: Write Fail>
aimetti said:
Make sure you have the galaxy nexus files? I was a moron and had same issue when I accidentally downloaded nexus s
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
That is exactly what I did. SMH @ myself
adb wont recognize your phone in bootloader? Because ADB is when android is running. You need fastboot when you're in bootloader.
try another usb cable. and yes, either that or you're holding it wrong.
use fastboot: http://andwise.net/?attachment_id=270
and make sure you have the drivers for fastboot
do exactly as it says here http://andwise.net/?p=268
i got the same thing .. i flashed a kernel on my stock rom and then i was trying to flash the factory image and i had write fail thing
Ok. So we have a couple of symptoms, here.
1: You try to flash via fastboot, phone says: "Nuhu! Not with me, bro!"
2: The ADB/fastboot won't recognize the phone.
3: Some guys answering this thread, are just idiots...
Solutions:
1: Try erasing, before flashing. It helps
2: Reinstall the ADB/fastboot drivers (Check my signature, and do that (It works with every distribution of Windows form Vista+) This will reinstall the drivers, and the ADB/fastboot command/deamon will be able to communicate, with the deamon on the phone...
3: Ask a moderator, if he can delete some of those nasty n00b answers...
LG familyguy59
---------- Post added at 02:14 PM ---------- Previous post was at 02:10 PM ----------
M7amad90 said:
i got the same thing .. i flashed a kernel on my stock rom and then i was trying to flash the factory image and i had write fail thing
Click to expand...
Click to collapse
Again, read my sig.
TO ALL: Before creating a new thread, save memory (on the servers) and search function!!
Beatsleigher said:
Ok. So we have a couple of symptoms, here.
1: You try to flash via fastboot, phone says: "Nuhu! Not with me, bro!"
2: The ADB/fastboot won't recognize the phone.
3: Some guys answering this thread, are just idiots...
Solutions:
1: Try erasing, before flashing. It helps
2: Reinstall the ADB/fastboot drivers (Check my signature, and do that (It works with every distribution of Windows form Vista+) This will reinstall the drivers, and the ADB/fastboot command/deamon will be able to communicate, with the deamon on the phone...
3: Ask a moderator, if he can delete some of those nasty n00b answers...
LG familyguy59
---------- Post added at 02:14 PM ---------- Previous post was at 02:10 PM ----------
Again, read my sig.
TO ALL: Before creating a new thread, save memory (on the servers) and search function!!
Click to expand...
Click to collapse
I had the same problem, erasing userdata before flashing bootloader helps in solving,
actually i flashed the fact image via nexus toolkit and it asked to erase teh userdata first.
Hello everyone, I just got my hands on my new nexus and I LOVE IT!!. I'm on verizon.
I just have a few questions. I got it yesterday but I see there are new radios/bootloader?
I'm still on stock 4.04 ICS
I want to root/unlock and load up MIUI/AKOP
Can someone give me a small tutorial on how to do this? I see there's a toolkit but i'm confused on what to do because of JB dropping.
As always i'm late to the party
http://forum.xda-developers.com/showthread.php?t=1529058
David522d said:
Hello everyone, I just got my hands on my new nexus and I LOVE IT!!. I'm on verizon.
I just have a few questions. I got it yesterday but I see there are new radios/bootloader?
I'm still on stock 4.04 ICS
I want to root/unlock and load up MIUI/AKOP
Can someone give me a small tutorial on how to do this? I see there's a toolkit but i'm confused on what to do because of JB dropping.
As always i'm late to the party
Click to expand...
Click to collapse
efrant has all the info you need:
http://forum.xda-developers.com/showthread.php?t=1814266
Can I just use the root toolkit? (Does it work well?)
David522d said:
Can I just use the root toolkit? (Does it work well?)
Click to expand...
Click to collapse
it works... but when it fails, it fails hard. and then you dont know where it failed or what it even did.
i personally will not help if you use the toolkit and things go wrong... others will still help.
It's actually very easy on this device. Since you know you are wanting to install a new ROM you don't even need to root. The hardest part is installing the ADB usb drivers and making sure they work correctly. There are basically 3 things you need to do.
1.) Install ADB and the ADB usb drivers
2.) Unlock the bootloader and install a custom recovery (ClockworkMod is the most popular)
3.) Flash a new ROM
You can do steps 1-2 by following this guide up to the recovery install step. Then for step 3 download the ROM of your choice into the internal sd and boot into CWM recovery and flash.
Stupid question, can i do all of this if the phone isnt activated? My sim card should be here in the mail tomorrow
David522d said:
Stupid question, can i do all of this if the phone isnt activated? My sim card should be here in the mail tomorrow
Click to expand...
Click to collapse
yes you can.
Zepius said:
it works... but when it fails, it fails hard. and then you dont know where it failed or what it even did.
i personally will not help if you use the toolkit and things go wrong... others will still help.
Click to expand...
Click to collapse
jeez you had no faith in tookit guy
very easy to do.
now my question to you again
im unlocked rooted and have clockwork touch
should i flash these new radios/bootloader and flash them thru clockwork?
thanks
David522d said:
jeez you had no faith in tookit guy
very easy to do.
now my question to you again
im unlocked rooted and have clockwork touch
should i flash these new radios/bootloader and flash them thru clockwork?
thanks
Click to expand...
Click to collapse
considering i read these forums and see the posts that get created, yeah i dont trust the toolkit. there are so many threads created with the title of "HELP I BRICKED MY PHONE" followed by "i used such and such toolkit"
as far as your other question, you can flash the radios and bootloaders via CWM.
David522d said:
Stupid question, can i do all of this if the phone isnt activated? My sim card should be here in the mail tomorrow
Click to expand...
Click to collapse
Since when did Verizon start using sim cards
Sent from my Galaxy Nexus using xda premium
Zepius said:
considering i read these forums and see the posts that get created, yeah i dont trust the toolkit. there are so many threads created with the title of "HELP I BRICKED MY PHONE" followed by "i used such and such toolkit"
as far as your other question, you can flash the radios and bootloaders via CWM.
Click to expand...
Click to collapse
haha yah no I do believe you.. and thanks!
last question
Until I flash a new rom over stock, will i have to re flash clockwork every time if i want to use recovery
dschreiber69 said:
Since when did Verizon start using sim cards
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Since they got lte
Sent from my Galaxy Nexus using Tapatalk 2
---------- Post added at 08:55 PM ---------- Previous post was at 08:54 PM ----------
David522d said:
haha yah no I do believe you.. and thanks!
last question
Until I flash a new rom over stock, will i have to re flash clockwork every time if i want to use recovery
Click to expand...
Click to collapse
Delete recovery-from-boot.p from /system
Sent from my Galaxy Nexus using Tapatalk 2
Zepius said:
Since they got lte
Sent from my Galaxy Nexus using Tapatalk 2
---------- Post added at 08:55 PM ---------- Previous post was at 08:54 PM ----------
Delete recovery-from-boot.p from /system
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
What i did was install jellybean and now everytime it boots into recovery when i want it to =)
Was android restoring the default recovery because i was on stock ROM?
wtf is wrong with this site no helps me ****
First why don't you tell us about your problem and calm down
Sent from my GT-I9100G using xda premium
josephnero said:
First why don't you tell us about your problem and calm down
Sent from my GT-I9100G using xda premium
Click to expand...
Click to collapse
i am trying to root my phone i am using this guide http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ everytime i run terminal (i am on a mac ) it never finds my phone
iam unfamilliar with nexus s.let me search a bit and i ll get back
---------- Post added at 12:45 AM ---------- Previous post was at 12:41 AM ----------
so are you on ICS or JB?
---------- Post added at 12:55 AM ---------- Previous post was at 12:45 AM ----------
tried any of these?
http://forums.acsyndicate.net/showthread.php?2024-ACS-Nexus-S-One-Click-Root-V4-0
also have you installed your phones drivers?
NemoHoees said:
i am trying to root my phone i am using this guide http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ everytime i run terminal (i am on a mac ) it never finds my phone
Click to expand...
Click to collapse
Here is what I found in Nexus S forum (Q&A section):
Q: How do I root/unroot the Nexus S?
Check the development section links below for more detail, but you gain root on the Nexus S by booting the phone into fastboot mode and typing "fastboot oem unlock." This will wipe your phone and it's SD card partition. To unroot it, again boot into fastboot mode and type "fastboot oem lock."
Follow the root guide stickied at the top of this forum: http://forum.xda-developers.com/showthread.php?t=895545
In the event you want to return to stock, simply flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 . This will restore everything, including the stock recovery image. Then as mentioned above go into the bootloader/fastboot mode and enter "fastboot oem lock" in ADB.
(All credit goes to the original author(s) of the linked thread!)
Click to expand...
Click to collapse
And here in general section:
[GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9023 and i9020A)
[GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9020T only)
[GUIDE] MAC Rooting Nexus S
Click to expand...
Click to collapse
Good luck !
What is wrong is that you think this is a support site. Let me let you in on something. Its not! This is a developers site.
Oh and if your set up is not seeing your device then guess what your problem is? If you can't answer that then you need to so more research.
Thread closed
Sent from my SGH-I777 using Tapatalk 2
hello guys,
i flashed unroot file using odin for galaxy nexus gsm. its unrooted but the boot.img isnt changed. there is a unlock icon under the google logo.
then i change boot img file in odin pda tar file from a nexus factory image.
my problem is :
now i flashing changed tar file using odin but it paused in boot.img level.(around 12%)
can you help?
thx.
yashade2001 said:
hello guys,
i flashed unroot file using odin for galaxy nexus gsm. its unrooted but the boot.img isnt changed. there is a unlock icon under the google logo.
then i change boot img file in odin pda tar file from a nexus factory image.
my problem is :
now i flashing changed tar file using odin but it paused in boot.img level.(around 12%)
can you help?
thx.
Click to expand...
Click to collapse
why would you use odin? thats an awful hacker tool, leaked, no documentation, press one wrong button and your nexus is dead. google has made fastboot, use that to flash images. you find a tutorial in the galaxy nexus toolkit thread, you might aswell use that, though, it relies on fastboot and adb.
For people that came from samsung devices Odin is a very useful and the most comfortable tool. Fastboot is safer indeed but....sometimes u just don't want to write plenty commands in terminal when in Odin is just a one click.
gnextoolkit is one click aswell, its safe as milk, its clean, well documented and theres not much you can do wrong. dont harass poor nexus with odin. for all we know the guy could have just killed his phone, stuck at 12% doent sound so nice, hope it still came trhough.
Ok guys i repaired. From so diffcult way
Sent from my Galaxy Nexus using xda app-developers app
Yeah sure, if Odin fails then it's the time to use different means. I only use Odin when I want to perform a clean flash with full wipe. Otherwise (most of the time) I use fastboot. Toolkit goes very seldom.
EDIT: Great!!! How did you fix it?
molesarecoming said:
gnextoolkit is one click aswell, its safe as milk, its clean, well documented and theres not much you can do wrong. dont harass poor nexus with odin. for all we know the guy could have just killed his phone, stuck at 12% doent sound so nice, hope it still came trhough.
Click to expand...
Click to collapse
Well, problems with toolkits is they run commands in sequence. Not to mention the user knows nothing and almost always ends up in the Q&A section asking for help because they get bootloops trying to flash a ROM/mod downloaded from what they think is a make my nexus kewl forum.
This will put him into the right path:
http://forum.xda-developers.com/showthread.php?t=1529058
---------- Post added at 06:41 PM ---------- Previous post was at 06:40 PM ----------
yashade2001 said:
hello guys,
i flashed unroot file using odin for galaxy nexus gsm. its unrooted but the boot.img isnt changed. there is a unlock icon under the google logo.
then i change boot img file in odin pda tar file from a nexus factory image.
my problem is :
now i flashing changed tar file using odin but it paused in boot.img level.(around 12%)
can you help?
thx.
Click to expand...
Click to collapse
Boot.img have nothing to do with the padlock icon..
Padlock icon means unlocked bootloader.
fastboot oem lock to get rid of it.
Mach3.2 said:
Well, problems with toolkits is they run commands in sequence. Not to mention the user knows nothing and almost always ends up in the Q&A section asking for help because they get bootloops trying to flash a ROM/mod downloaded from what they think is a make my nexus kewl forum.
This will put him into the right path:
http://forum.xda-developers.com/showthread.php?t=1529058
---------- Post added at 06:41 PM ---------- Previous post was at 06:40 PM ----------
Boot.img have nothing to do with the padlock icon..
Padlock icon means unlocked bootloader.
fastboot oem lock to get rid of it.
Click to expand...
Click to collapse
Thx very much.
Sent from my Galaxy Nexus using xda app-developers app
m.kochan10 said:
Yeah sure, if Odin fails then it's the time to use different means. I only use Odin when I want to perform a clean flash with full wipe. Otherwise (most of the time) I use fastboot. Toolkit goes very seldom.
EDIT: Great!!! How did you fix it?
Click to expand...
Click to collapse
Long story...
Sent from my Galaxy Nexus using xda app-developers app
yashade2001 said:
Long story...
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
This information can be useful for other users. U sure you don't wanna share it?
m.kochan10 said:
This information can be useful for other users. U sure you don't wanna share it?
Click to expand...
Click to collapse
Ok. İf you wanna know,
İ unpugged my phone. Then its bricked of course. And i unbricked this using linux. İ installed ubuntu to my computer. İ used terminal. But it isnt finished . İ have to use mac os x. For a program. İts command line osx. Then its unbricked and i flashed original rom with odin.
Sent from my Galaxy Nexus using xda app-developers app
Mach3.2 said:
Well, problems with toolkits is they run commands in sequence. Not to mention the user knows nothing and almost always ends up in the Q&A section asking for help because they get bootloops trying to flash a ROM/mod downloaded from what they think is a make my nexus kewl forum..
Click to expand...
Click to collapse
i have rather an established toolkit running official google components in sequence than a hacked/leaked samsung app that is neither documented nor known as to what it does and how it does it (and it will run stuff in sequence though). i own the s2 and know their forums, it is overfull of odin broke this odin broke that, pressed a wrong button phone dead, try jig here send it in for repair there. gnextoolkit is a great tool and the guy has put so much effort in it to keep it up to date and documented. every single thing he does there is laid out in the tutorial, fastboot commands aswell. i would recommend that tool to new users in a heartbeat.
I wouldn't exaggerate though. I owned Galaxy R, then S2 for more than year totally. I've never had one single issue with Odin (and I am a flashoholic ). Yes there were some instances when people messed around using it in a mindless way (or simply had bad luck...or Kies turned out to be a villain...) but the majority used it regularly without bigger problems. I'm not trying to say that Odin is perfectly safe...no no but if you follow the guide, have all required drivers installed (and Kies turned off) I don't see the reason why I should discourage users from running it.
odin
molesarecoming said:
i have rather an established toolkit running official google components in sequence than a hacked/leaked samsung app that is neither documented nor known as to what it does and how it does it (and it will run stuff in sequence though). i own the s2 and know their forums, it is overfull of odin broke this odin broke that, pressed a wrong button phone dead, try jig here send it in for repair there. gnextoolkit is a great tool and the guy has put so much effort in it to keep it up to date and documented. every single thing he does there is laid out in the tutorial, fastboot commands aswell. i would recommend that tool to new users in a heartbeat.
Click to expand...
Click to collapse
yeah, i perefer fastboot and gnex toolkit too but this time i hav to use odin.
use always odin and don't post if you will have problems.as molesarecoming sad you,fadtboot it's the way to go.odin works too,but fastboot is better,and don't say "fastboot has command to write,it's more difficult bla bla bla" all ****,there are not more than 5 commands to know for the major parts of operations.tools works withouyt commans,but i prefer manually because i know what i'm doing and i know if seomething goes wrong,at which type of command the phone was when occured the problem.