Right, from the top, I'm a retard and shouldn't have messed with ROM's and custom recovery whilst blindly following a guide (I cant remember which guide, so mistake #1). I have a Telstra (Australian) Galaxy Nexus. I followed a guide to put CWM, Jelly Bean and root on, however I ran into a few problems and wanted to revert to my stock ROM, well I never performed a backup of my original ROM (mistake #2). I went looking and someone posted a Telstra stock ROM in CWM backup form here on xda, I successfully restored it and am *mostly* happy with the results, however no I cannot recieve OTA updates, which seems to be due to the prop file and others assert failing. Basically, I've learnt my lesson and want to be a good boy and go back to a non-root, completely out of the box state so if in the future, I need to return the phone for warranty, I can without fear of recourse for messing with the phone.
So again, I'm a tard, but can you help me?
EDIT: Mistake #3, I went back through my downloads and found the files I used from the guide I cant find to show you, but it DID involve Busybox which I have since read screws **** up.
http://forum.xda-developers.com/showthread.php?t=1626895
alll you need to know
atifsh said:
http://forum.xda-developers.com/showthread.php?t=1626895
alll you need to know
Click to expand...
Click to collapse
I've been over that thread twice now and cant find the Return to Stock instructions, am I blind? (happy to be proven wrong)
Syn3rgi3 said:
Right, from the top, I'm a retard and shouldn't have messed with ROM's and custom recovery whilst blindly following a guide (I cant remember which guide, so mistake #1). I have a Telstra (Australian) Galaxy Nexus. I followed a guide to put CWM, Jelly Bean and root on, however I ran into a few problems and wanted to revert to my stock ROM, well I never performed a backup of my original ROM (mistake #2). I went looking and someone posted a Telstra stock ROM in CWM backup form here on xda, I successfully restored it and am *mostly* happy with the results, however no I cannot recieve OTA updates, which seems to be due to the prop file and others assert failing. Basically, I've learnt my lesson and want to be a good boy and go back to a non-root, completely out of the box state so if in the future, I need to return the phone for warranty, I can without fear of recourse for messing with the phone.
So again, I'm a tard, but can you help me?
EDIT: Mistake #3, I went back through my downloads and found the files I used from the guide I cant find to show you, but it DID involve Busybox which I have since read screws **** up.
Click to expand...
Click to collapse
As I understand it, you should just be able to re-apply a stock GSM ROM to your Galaxy Nexus to get back to the original state of things. That's the whole point of a Nexus - it's stock with no customisations etc. It sounds like you'll have start from the very beginning and reinstall apps etc. but I guess you've already bitten that bullet, and presumably you're happy with your current ROM configuration?
It's not clear what recovery you have installed at the moment. You've made mention of CWM ... Clockwork Mod recovery possibly installed in that case? Again, as I understand it, Clockwork Mod recovery means you can't <s>receive</s> apply OTA updates. If you're on a stock ROM you should still receive notification about them though? If you are truly on stock, but have the Clockwork Mod recovery installed you can reinstall the stock boot recovery image. You should be able to find the stock images via a google search easily enough.
Once you've determined which recovery you currently have installed you'll have a better idea of how to get back to stock everything.
Above all, don't panic
PS I could add that busybox doesn't screw stuff up ... it just allows you to screw things up
Hi there,
the most simple way to go back to stock is using the GNex-Toolkit (to be found here http://forum.xda-developers.com/showthread.php?t=1392310) downloading the stock image here https://developers.google.com/android/nexus/images. Almost no chance to mess up your phone with this tool.
real_becksaufex said:
Hi there,
the most simple way to go back to stock is using the GNex-Toolkit (to be found here http://forum.xda-developers.com/showthread.php?t=1392310) downloading the stock image here https://developers.google.com/android/nexus/images. Almost no chance to mess up your phone with this tool.
Click to expand...
Click to collapse
Given a bit more research, I want to be able to get rid of Clockworkmod so I can receive OTA updates again.
Syn3rgi3 said:
Given a bit more research, I want to be able to get rid of Clockworkmod so I can receive OTA updates again.
Click to expand...
Click to collapse
yeah and if tried the tool, you would have seen, that there is an option to flash stock recovery to your phone. you can also disable the bootloader again.
choose your model/build perform action 7 --> option 3 and your back on stock recovery
real_becksaufex said:
yeah and if tried the tool, you would have seen, that there is an option to flash stock recovery to your phone. you can also disable the bootloader again.
choose your model/build perform action 7 --> option 3 and your back on stock recovery
Click to expand...
Click to collapse
I executed that successfully however CWM still exists =/
Syn3rgi3 said:
I've been over that thread twice now and cant find the Return to Stock instructions, am I blind? (happy to be proven wrong)
Click to expand...
Click to collapse
Seriously? The instructions in the first post...
Sent from my Galaxy Nexus using Tapatalk 2
real_becksaufex said:
yeah and if tried the tool, you would have seen, that there is an option to flash stock recovery to your phone. you can also disable the bootloader again.
choose your model/build perform action 7 --> option 3 and your back on stock recovery
Click to expand...
Click to collapse
Disable bootloader?
Pressed from my Maguro
efrant said:
Seriously? The instructions in the first post...
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
This still doesn't solve the problem I have in regard to not having the original Telstra (yakjudv) ROM.
Syn3rgi3 said:
This still doesn't solve the problem I have in regard to not having the original Telstra (yakjudv) ROM.
Click to expand...
Click to collapse
I few things:
1) If you can find a backup of a yakjudv ROM from some Australian user, I'd be happy to help you restore it; but
2) You do realize that yakjudv is still on 4.0.4 (ICS) and not Jelly Bean, right? And you do realize that it only recently (past few weeks) got updated to 4.0.4 while yakju has been on 4.0.4 since March?
3) You do realize that yakju is stock, and the factory images provided by Google are the "stock" ones that get updated first. yakjudv is a Samsung build, not a stock Google build.
LOL, Telstra
Syn3rgi3 said:
Right, from the top, I'm a retard and shouldn't have messed with ROM's and custom recovery whilst blindly following a guide (I cant remember which guide, so mistake #1). I have a Telstra (Australian) Galaxy Nexus. I followed a guide to put CWM, Jelly Bean and root on, however I ran into a few problems and wanted to revert to my stock ROM, well I never performed a backup of my original ROM (mistake #2). I went looking and someone posted a Telstra stock ROM in CWM backup form here on xda, I successfully restored it and am *mostly* happy with the results, however no I cannot recieve OTA updates, which seems to be due to the prop file and others assert failing. Basically, I've learnt my lesson and want to be a good boy and go back to a non-root, completely out of the box state so if in the future, I need to return the phone for warranty, I can without fear of recourse for messing with the phone.
So again, I'm a tard, but can you help me?
EDIT: Mistake #3, I went back through my downloads and found the files I used from the guide I cant find to show you, but it DID involve Busybox which I have since read screws **** up.
Click to expand...
Click to collapse
DO NOT GET YAKJUDV!!! Try and just get Yakju, Then you will get your updates from Google NOT Telstra. You don't need the Telstra stock rom, you can use Google's Yakju. I have a Telstra one and I get updates from google because I put Yakju. You will need to flash the ROM though your pc. I have been through what you have with the exact phone (Telstra one), If you need any help you can PM me
I agree with the post from Atifsh.
The guide offered by Efrant gives you, step by step, everything you need to reach your goal.
Contrary to your case I did not need to change the factory ROM but I applied the rest of the guide (for instance post 855 in Efrant thread shows what I did).
Since I want to learn I refuse, so far, to rely on a toolkit.
I deeply share Efrant philosophy of learning. And I agree on the purpose of the XDA forum. It is not a walking clinic, it is a hospital implementing new medecines:laugh:.
Finally, taking into account my age I am closer to the hospital than to the clinic.
Thanks to Efrant and few others I am doing "stuff" I did not know I could do.
And, yes I am over the time I used to want and get everything at once.
efrant said:
I few things:
1) If you can find a backup of a yakjudv ROM from some Australian user, I'd be happy to help you restore it; but
2) You do realize that yakjudv is still on 4.0.4 (ICS) and not Jelly Bean, right? And you do realize that it only recently (past few weeks) got updated to 4.0.4 while yakju has been on 4.0.4 since March?
3) You do realize that yakju is stock, and the factory images provided by Google are the "stock" ones that get updated first. yakjudv is a Samsung build, not a stock Google build.
Click to expand...
Click to collapse
I understand all the benefits of yakju, however I want to revert to yakjudv if for any reason in the future I require warranty (the phone is under contract).
I do in fact have a 4.0.1 Nandroid backup from another user on Telstra, I went ahead and restored it through CWM and everything was fine, except I still cannot receive OTA updates, doing some reading finds I need to get rid of CWM and revert to stock recovery, so how do I do this?
Syn3rgi3 said:
I understand all the benefits of yakju, however I want to revert to yakjudv if for any reason in the future I require warranty (the phone is under contract).
I do in fact have a 4.0.1 Nandroid backup from another user on Telstra, I went ahead and restored it through CWM and everything was fine, except I still cannot receive OTA updates, doing some reading finds I need to get rid of CWM and revert to stock recovery, so how do I do this?
Click to expand...
Click to collapse
As you say, the problem is you need the stock recovery for the build that you are on. What build is the backup you restored? If it is ITL41F, then you are in luck. Go to this thread and download any one of the two yakjudv updates to /sdcard. Use CWM to flash it, and you will be all set -- it will wipe CWM and replace it with the correct stock recovery for that build.
---------- Post added at 08:49 PM ---------- Previous post was at 08:48 PM ----------
And please change the title of this thread to "Return to stock yakjudv" as it is very confusing. Most people refer to stock as yakju or takju for GSM devices.
Syn3rgi3 said:
I understand all the benefits of yakju, however I want to revert to yakjudv if for any reason in the future I require warranty (the phone is under contract).
I do in fact have a 4.0.1 Nandroid backup from another user on Telstra, I went ahead and restored it through CWM and everything was fine, except I still cannot receive OTA updates, doing some reading finds I need to get rid of CWM and revert to stock recovery, so how do I do this?
Click to expand...
Click to collapse
Can you please post the back up on here please via drop box or something, I need the same thing so I can return for a warranty issue however everywhere I look I just find silly people trying to inform me that I should use Google builds and no Samsung/Telstra build. I know all this however my phone is now on life support and everything seems to be going wrong so I just want to return to out of the box and return it.
---------- Post added at 07:36 PM ---------- Previous post was at 07:31 PM ----------
I love it when people ignore the question in the OP and just decide to tell others to flash different firmware. This isnt helpful in any way when trying to return your device to Telstra in Australia as that's not what come with it so they will just give you your faulty POS back and laugh in your face because you are no longer covered by the warranty.
picton said:
Can you please post the back up on here please via drop box or something, I need the same thing so I can return for a warranty issue however everywhere I look I just find silly people trying to inform me that I should use Google builds and no Samsung/Telstra build. I know all this however my phone is now on life support and everything seems to be going wrong so I just want to return to out of the box and return it.
I love it when people ignore the question in the OP and just decide to tell others to flash different firmware. This isnt helpful in any way when trying to return your device to Telstra in Australia as that's not what come with it so they will just give you your faulty POS back and laugh in your face because you are no longer covered by the warranty.
Click to expand...
Click to collapse
Have you tried returning a device with yakju and have Telstra give you back your "faulty POS" back? Have you heard of others who have experienced that? On the contrary, I have heard of many people returning their non-yakju-bought device with yakju, and have had full warranty.
And if you would have searched before lipping off, you would have found this: http://forum.xda-developers.com/showpost.php?p=29898676&postcount=175
efrant said:
Have you tried returning a device with yakju and have Telstra give you back your "faulty POS" back? Have you heard of others who have experienced that? On the contrary, I have heard of many people returning their non-yakju-bought device with yakju, and have had full warranty.
And if you would have searched before lipping off, you would have found this: http://forum.xda-developers.com/showpost.php?p=29898676&postcount=175
Click to expand...
Click to collapse
I have tried that link bro and it wont flash in CWM. I just get a red triangle with a robot on it. A mate of mine tried to take his back due to a similar problem im having and he was told he had played with the device and wouldn't fix it under warranty and wanted to charge him something stupid to fix it. I'm not giving ya lip but I have been looking for the last 6 hours and in every thread about this subject everyone is saying the same thing.
picton said:
I have tried that link bro and it wont flash in CWM. I just get a red triangle with a robot on it. A mate of mine tried to take his back due to a similar problem im having and he was told he had played with the device and wouldn't fix it under warranty and wanted to charge him something stupid to fix it. I'm not giving ya lip but I have been looking for the last 6 hours and in every thread about this subject everyone is saying the same thing.
Click to expand...
Click to collapse
Ok, are you flashing it in CWM? The "red triangle with a robot" IS the stock recovery, it is not an error. What is the exact procedure you are using to flash it?
Related
So if I reset the phone with CM7 and didn't run a recovery to backup the stock ROM and bloatware, what potential issues could I come across? I don't plan on having to send the phone back to T-mobile (it has been holding together very well so far) and I will probably upgrade in about a year or so.
My question is, does it really matter? And if I had to send the phone in is there somewhere online I could grab the stock software to reset it?
(I searched using several different wordings and found info on other phones but not the Defy)
Thee GOC said:
So if I reset the phone with CM7 and didn't run a recovery to backup the stock ROM and bloatware, what potential issues could I come across? I don't plan on having to send the phone back to T-mobile (it has been holding together very well so far) and I will probably upgrade in about a year or so.
My question is, does it really matter? And if I had to send the phone in is there somewhere online I could grab the stock software to reset it?
(I searched using several different wordings and found info on other phones but not the Defy)
Click to expand...
Click to collapse
go here
http://forum.xda-developers.com/showthread.php?t=1216982
read and follow the procedure ....good luck
jassi32 said:
go here
http://forum.xda-developers.com/showthread.php?t=1216982
read and follow the procedure ....good luck
Click to expand...
Click to collapse
I have read that post several times, but my question should have been where do I get the stock SBF if I need to revert to stock to, let's say, sell the unit or send it in?
Thee GOC said:
I have read that post several times, but my question should have been where do I get the stock SBF if I need to revert to stock to, let's say, sell the unit or send it in?
Click to expand...
Click to collapse
http://forum.xda-developers.com/wiki/Motorola_Defy
Thee GOC said:
I have read that post several times, but my question should have been where do I get the stock SBF if I need to revert to stock to, let's say, sell the unit or send it in?
Click to expand...
Click to collapse
I successfully reverted back to US Stock 2.2.1 after flashing nordic/CEE etc. and installing CM7
by first flashing 2.1 and then upgrading using motorla update.
See http://forum.xda-developers.com/showthread.php?p=18325086#post18325086
Did this because there's no 3.4.2-107_JDN-9 sbf, only an leaded 2.2.1-3.4.2-107_JDN-4.
My nexus is rooted and unlocked running stock 4.0.2, no custom ROMs. Received the 4.0.4 ota update this morning. Will it install if I let it, or do I need to follow the instructions that others used to do the early install of the update?
Sent from my Galaxy Nexus using XDA
I am just like you. I have the stock 4.0.2 that came with my phone but I've unlocked and rooted it. Received the upgrade notice this morning and said, "yes", but during reboot all I get is the android lying on its back with a red triangle and exclamation point. I have to pull the battery to reboot but then it only comes back in 4.0.2.
Ok, that's what I expected. Sounds like we need to run the manual update. I'm in the process of packing and moving this weekend so I was hoping for an easy fix. Thx for your reply.
Sent from my Galaxy Nexus using XDA
hey there guys i once had the same problem when i was on stockrom with root:
It is simple : Do not do it!
Either U will get what is described above but atleast you will loose your root rights/ unlockes status.
To upate properly use ClockworkMod (App RomManager) and download an already unlocked version of the current update.
I recommend you to switch to a non stock rom hence u will not get these OTA notifications anymore which you may accept "by accident". Good ROms are CM9, Trickster, Paranoid, just haver a look in the dev section.
cryptiq said:
My nexus is rooted and unlocked running stock 4.0.2, no custom ROMs. Received the 4.0.4 ota update this morning. Will it install if I let it, or do I need to follow the instructions that others used to do the early install of the update?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
If you did not change anything (other than root), you can install it no issue. However, if you have changed your radio, kernel, recovery, or any system file, then the update will not work.
Not however, that you need to install something like OTA Rootkeeper BEFORE you go through the update process, as you will lose root otherwise.
dogunter said:
I am just like you. I have the stock 4.0.2 that came with my phone but I've unlocked and rooted it. Received the upgrade notice this morning and said, "yes", but during reboot all I get is the android lying on its back with a red triangle and exclamation point. I have to pull the battery to reboot but then it only comes back in 4.0.2.
Click to expand...
Click to collapse
That is because you have something that is not stock 4.0.2, be it a kernel, radio, modified system file, recovery, etc.
FellX said:
hey there guys i once had the same problem when i was on stockrom with root:
It is simple : Do not do it!
Either U will get what is described above but atleast you will loose your root rights/ unlockes status.
To upate properly use ClockworkMod (App RomManager) and download an already unlocked version of the current update.
I recommend you to switch to a non stock rom hence u will not get these OTA notifications anymore which you may accept "by accident". Good ROms are CM9, Trickster, Paranoid, just haver a look in the dev section.
Click to expand...
Click to collapse
An update does not affect the "unlocked status" as you say.
See my comments above about root.
You comments about switching to a non-stock ROM don't really make sense for someone who likes stock ROMs and wants to update...
Here you go, a rooted 4.0.4...
http://www.droid-life.com/2012/05/3...6k-build-for-galaxy-nexus-flash-over-any-rom/
efrant said:
That is because you have something that is not stock 4.0.2, be it a kernel, radio, modified system file, recovery, etc.
Click to expand...
Click to collapse
He is right, once upon a time I had flashed a rom and then wanted to go back to stock. I used someones method first (I dont remember whose it was) and I thought I was on stock but I got the android guy on his back and it wasnt working properly (I think the radio was the wrong one) so I then flashed the stock image from Google to 4.0.4 and I was able to get the 4.0.4 OTA no problem and I didnt see the android guy on his back at all during the process.
So more than likely there is something that isnt stock on your phones.
WiredPirate said:
Here you go, a rooted 4.0.4...
http://www.droid-life.com/2012/05/3...6k-build-for-galaxy-nexus-flash-over-any-rom/
Click to expand...
Click to collapse
That is NOT an update. The guy wants to update his build, not flash a brand new one...
same issue
first time poster here. stumbled upon this thread earlier this morning while searching for a solution to what appears to be the same problem that "dogunter" is experiencing. i have a stock 4.0.2 verizon galaxy nexus that i purchased through eBay a few months back. it was listed as brand new but when it arrived it had already been unlocked. from what ive gathered thus far, im assuming that the seller not only unlocked it, but also modified a system file(s), as i am getting the "android on its back with a red triangle" whenever i attempt to update to 4.0.4 via OTA push.
what steps should i take in order to correctly install 4.0.4? i see that "jonnyg1097" claims he "flashed the stock image from Google to 4.0.4 and I was able to get the 4.0.4 OTA no problem and I didnt see the android guy on his back at all during the process. " how would i go about doing this, and is this the best/only method to install the update? thanks in advance!
galaxy_sexus said:
first time poster here. stumbled upon this thread earlier this morning while searching for a solution to what appears to be the same problem that "dogunter" is experiencing. i have a stock 4.0.2 verizon galaxy nexus that i purchased through eBay a few months back. it was listed as brand new but when it arrived it had already been unlocked. from what ive gathered thus far, im assuming that the seller not only unlocked it, but also modified a system file(s), as i am getting the "android on its back with a red triangle" whenever i attempt to update to 4.0.4 via OTA push.
what steps should i take in order to correctly install 4.0.4? i see that "jonnyg1097" claims he "flashed the stock image from Google to 4.0.4 and I was able to get the 4.0.4 OTA no problem and I didnt see the android guy on his back at all during the process. " how would i go about doing this, and is this the best/only method to install the update? thanks in advance!
Click to expand...
Click to collapse
I would follow the instructions here, which takes you through the whole process set-by-step (make sure you do the optional steps in part D). That way you can be certain that you are fully stock. (Leave the bootloader unlocked.) Once you do that, then you can have a look here for how to use the OTA update file to update.
hmm
thanks for that, efrant. im currently in the process of getting it back to stock so i can receive the 4.0.4 OTA update. i am, however, running into a slight issue. in step D, number 2, you say to unlock the bootloader by typing "fastboot oem unlock". upon doing that, the cmd prompt gives me "...FAILED <remote: Already Unlocked>" i suspected it would say that as my phone was already unlocked by the seller. however, im not getting the prompt on my nexus about the device being wiped...do you know why that is and what i need to to in order to continue?
...by the way, a blue line of text appeared at the bottom of the phone's screen that reads "FASTBOOT STATUS - FAILALready Unlocked".
again, thanks in advance for all of the help.
galaxy_sexus said:
thanks for that, efrant. im currently in the process of getting it back to stock so i can receive the 4.0.4 OTA update. i am, however, running into a slight issue. in step D, number 2, you say to unlock the bootloader by typing "fastboot oem unlock". upon doing that, the cmd prompt gives me "...FAILED <remote: Already Unlocked>" i suspected it would say that as my phone was already unlocked by the seller. however, im not getting the prompt on my nexus about the device being wiped...do you know why that is and what i need to to in order to continue?
...by the way, a blue line of text appeared at the bottom of the phone's screen that reads "FASTBOOT STATUS - FAILALready Unlocked".
again, thanks in advance for all of the help.
Click to expand...
Click to collapse
You are good to proceed. You won't get the wipe prompt if your bootloader is already unlocked. No worries, just keep going with the steps.
Sent from my Galaxy Nexus using Tapatalk 2
thanks
thanks for the quick responses! you are quite helpful. everything appeared to install successfully, but upon the first reboot after finishing, im unable to get any service! it reads "Searching for service...", sits there for about 2 minutes, then tells me it cannot find service and thus cant activate. i skipped instead of restarting, and checked the settings to see if anything looked suspicious. im seeing that under "Baseband version" it says "Unknown". did i screw something up?!
sorry to keep troubling you with such noobish problems, but although im an experienced PC user im fairly new to smartphones and android. please have mercy on me.
galaxy_sexus said:
thanks for the quick responses! you are quite helpful. everything appeared to install successfully, but upon the first reboot after finishing, im unable to get any service! it reads "Searching for service...", sits there for about 2 minutes, then tells me it cannot find service and thus cant activate. i skipped instead of restarting, and checked the settings to see if anything looked suspicious. im seeing that under "Baseband version" it says "Unknown". did i screw something up?!
sorry to keep troubling you with such noobish problems, but although im an experienced PC user im fairly new to smartphones and android. please have mercy on me.
Click to expand...
Click to collapse
The first thing i would do is reboot. If that doesn't work, then I would just flash the images one more time. (Just in case one of them messed up.) Make sure both radios flash successfully.
Sent from my Galaxy Nexus using Tapatalk 2
got it
figured it out! when i did the cmda radio install i accidentally typed "fastboot flash radio" instead of "fastboot flash radio-cdma". doh! worked perfectly the second time around. thanks again, man. youve been a fantastic help.
galaxy_sexus said:
figured it out! when i did the cmda radio install i accidentally typed "fastboot flash radio" instead of "fastboot flash radio-cdma". doh! worked perfectly the second time around. thanks again, man. youve been a fantastic help.
Click to expand...
Click to collapse
useful thread
Hello,
So, I will try to explain clearly my problem. I'm french, so I have an Galaxy Nexus with Android 4.0.4 (IMM76I) - Yakju.
I bought my phone at the very beginning, with the first ICS version. After that, I tried to use " Font changer ", and my phone rebooted, and loading... infinite
So, that was a big problem. To recover it, I tried so many thing, Wipe data, cache, etc... And I flashed the phone with the Factory Image. And it worked. Since this incident, I ALWAYS must flash the new factory image to use new versions of ICS. For 4.0.4 and 4.1. Because on every update, my phone reboot, it loads, and I get the Bugdroid with Warning icon :/
But I'm pissed of, and I want to do something, I'm bored to have that phone, and must do so much tricks for a simple update
So, I'm coming to you, for answers, if there are ?
Thanks !
So when you flashed the factory images, have you been flashing the corresponding radio, bootloader and recovery? And have you modified any system files since then? All of these things will prevent you from applying an OTA.
I used all factory elements from here : h**ps://developers.google.com/android/nexus/images?hl=fr
But now you ask me if I flashed bootloader, recovery, and radio, and I'm not sure :/
If I use the Gnex Toolkit, does he flash all of this himself ? Because I didn't use it before, and I don't remember me flashing the recovery.
I will wait for the 4.1 factory image to be released by Google, and do all of this
Thanks !
draentor said:
I used all factory elements from here : h**ps://developers.google.com/android/nexus/images?hl=fr
But now you ask me if I flashed bootloader, recovery, and radio, and I'm not sure :/
If I use the Gnex Toolkit, does he flash all of this himself ? Because I didn't use it before, and I don't remember me flashing the recovery.
I will wait for the 4.1 factory image to be released by Google, and do all of this
Thanks !
Click to expand...
Click to collapse
Don't use a toolkit and you will know what gets flashed. Follow steps in post #1 here.
Ok, I will follow all steps with 4.1 update.
And after that, I still can use the Toolkit right ?
draentor said:
Ok, I will follow all steps with 4.1 update.
And after that, I still can use the Toolkit right ?
Click to expand...
Click to collapse
No. Follow the steps in the link I sent you, and you will get the OTA update for 4.1.1 shortly after.
Yeah, I thinked about it, and that's the better solution.
But for root and others things, absolutely use your way ?
And what's the avantages and inconveniences of the tho methods ?
draentor said:
Yeah, I thinked about it, and that's the better solution.
But for root and others things, absolutely use your way ?
And what's the avantages and inconveniences of the tho methods ?
Click to expand...
Click to collapse
Use any way you want. Except when you are learning, you should not use any toolkits or 1-click methods <-- you don't know what they are doing, and if something messes up, it will be difficult for you to troubleshoot.
erec, icandoit
Yeah, seems logical.
I must do it the old way, before use new things
So, thanks for all your quick answers, there are much more knowledge here than the FrAndroid French forum
I bought a used nexus its in great condition everything works but the buyer didnt tell me it was rooted already. Thats fine cause i was going to but i wanted to learn the ropes myself. So is there anyone to get back to 100% stock? He flashed a CWM too. I just want to do it myself. And is there anyway to wipe format the internal memory aswell? Thanks!
you can use this guide : http://forum.xda-developers.com/showthread.php?t=1626895
even if you don't want to convert and already have yakju or takju, this is the way you can go back to pure stock
bgdxv said:
you can use this guide : http://forum.xda-developers.com/showthread.php?t=1626895
even if you don't want to convert and already have yakju or takju, this is the way you can go back to pure stock
Click to expand...
Click to collapse
Yup this guide is the way to go. Flash the "takju" images. There's full 4.1.1 images now too.
Thanks guys i have a usa gsm model and I guess i looked around and found out a way to wipe the internal data with those tools so i think im good and im kinda getting the hang of using the tool kit. But the phone has 4.1 i wanted to install rooted 4.1.1 is that possible? or how would i go about doing that? Thanks alot for your quick and helpful responses!
Nocturnal86 said:
Thanks guys i have a usa gsm model and I guess i looked around and found out a way to wipe the internal data with those tools so i think im good and im kinda getting the hang of using the tool kit. But the phone has 4.1 i wanted to install rooted 4.1.1 is that possible? or how would i go about doing that? Thanks alot for your quick and helpful responses!
Click to expand...
Click to collapse
Don't use a toolkit. Follow that guide posted. That guide will wipe the device completely and put you on 100% stock 4.1.1. If you want root, you can follow the last part of the guide, which has a step-by-step routine to root also.
martonikaj said:
Don't use a toolkit. Follow that guide posted. That guide will wipe the device completely and put you on 100% stock 4.1.1. If you want root, you can follow the last part of the guide, which has a step-by-step routine to root also.
Click to expand...
Click to collapse
Why shouldnt i use the tools? they seem pretty straight foward is there something bad about them? But Im finally going to get a chance to follow that guide hopefully and go to 4.1.1 and then root it cause i just want root right now for back up purposes. But thans for the info!
Nocturnal86 said:
Why shouldnt i use the tools? they seem pretty straight foward is there something bad about them? But Im finally going to get a chance to follow that guide hopefully and go to 4.1.1 and then root it cause i just want root right now for back up purposes. But thans for the info!
Click to expand...
Click to collapse
The tools aren't inherently bad, but they're kind of a "black box" to new users, where they put their phone in and it comes out rooted/flashed. The issue occurs when something goes wrong, and the user doesn't know why because they don't understand the procedure, and they can't reverse engineer what happened to fix it. So what they end up doing is coming and posting threads, etc.
If they were doing it the "real" (manual) way, via Fastboot, they'd know what was going on and have a better understanding of what they're doing to their phone. Because we have a Nexus, there's really no reason not to just use Fastboot because it's the tool that Google gives us. You own a ~$650 (much cheaper now w/ the Play Store, but still) device, why not spend 15 minutes learning how to work with it properly?
martonikaj said:
The tools aren't inherently bad, but they're kind of a "black box" to new users, where they put their phone in and it comes out rooted/flashed. The issue occurs when something goes wrong, and the user doesn't know why because they don't understand the procedure, and they can't reverse engineer what happened to fix it. So what they end up doing is coming and posting threads, etc.
If they were doing it the "real" (manual) way, via Fastboot, they'd know what was going on and have a better understanding of what they're doing to their phone. Because we have a Nexus, there's really no reason not to just use Fastboot because it's the tool that Google gives us. You own a ~$650 (much cheaper now w/ the Play Store, but still) device, why not spend 15 minutes learning how to work with it properly?
Click to expand...
Click to collapse
I can understand that and i usually do want to learn the ropes but i was kind of thrust into the middle cause i bought a used nexus and it was rooted and had CWM 6 flashed to it so I am just trying to figure things out a bit or at least go back to Full stock and no recovory flashed so i can learn the ropes myself and flash recoverys myself if needed and i want to get 4.1.1 and root it myself. If possible can i use the tools to just go to stock and then learn the manual ways from there? I got adb and the fastboot.exe finally so i never had that or new i needed it and when i first used the toolkit to wipe my sd I think it installed some drivers that the tool kit told me to which im hoping are correct. I really hate to ask questions unless its needed and i apprecieate it.
Nocturnal86 said:
I can understand that and i usually do want to learn the ropes but i was kind of thrust into the middle cause i bought a used nexus and it was rooted and had CWM 6 flashed to it so I am just trying to figure things out a bit or at least go back to Full stock and no recovory flashed so i can learn the ropes myself and flash recoverys myself if needed and i want to get 4.1.1 and root it myself. If possible can i use the tools to just go to stock and then learn the manual ways from there? I got adb and the fastboot.exe finally so i never had that or new i needed it and when i first used the toolkit to wipe my sd I think it installed some drivers that the tool kit told me to which im hoping are correct. I really hate to ask questions unless its needed and i apprecieate it.
Click to expand...
Click to collapse
The guide that was linked earlier is extremely simple to follow. It breaks everything down step by step, and you will be fully stock.
Hi, i have an unlocked Galaxy Nexus running Android 4.1.1 that has not received the android 4.2 OTA update. This is because my system is yakjuxw.
So i found a site explaining on how to switch to yakju or takju without loosing any data, apps etc:
http://andwise.net/?p=569
My questions are:
. Has anyone tried this?
. What are the cons?
. Does it void my phone's warranty?
Sorry if this has been asked or is posted somewhere else but i just cant seem to find it.
cheers!
Bruno
It's completely fine. In fact there is a thread specifically about the process that's been around for months.
Cool! Can u point me to it?
You have the same search function as I do.
Clearly you have not read my last paragraph.
But thank you for letting me there is a search feature, technology these days... Next thing u know there will be a global search engine for the whole Internet
brunobliss said:
Clearly you have not read my last paragraph.
But thank you for letting me there is a search feature, technology these days... Next thing u know there will be a global search engine for the whole Internet
Click to expand...
Click to collapse
clearly you didnt even bother to read the stickies. any of them.
AS a matter of fact i did, and found ways to flash a rom wiping all data from my phone, which is precisely what i don't want.
Now, i would thank those who actually came forward to answers to my questions instead of arguments that lead nowhere.
Thank you in advance.
The process in the first link is fine and works.
However to point out a few important things:
1) If your bootloader is locked you have to unlock it with: "fastboot unlock oem" and continuing with the instructions on the phone which will eventually delete all your data. (if you have flshed a ROM before you know that)
2) do install CWM recovery ( you can find instructions to do that everywhere and also on the same page you found for the 4.2) and do a Nandroid backup. This way you can go back to your original system anytime you want (I do this all the time)
3) keep also other backups of apps and contacts I find google cloud pretty handy for that.
4) The instructions mentioned on this site works but it might happen that some app or library or database is not happy with the update so the device will go in a boot loop. In this case delete dalvik-cache (it might help), but if it doesn't help you will need to delete the data or the part that causes the issue for this you might look into the logcat.
PS: Zepius, Pandas are not so cute actually ... so what's the best ROM / Kernel (stock it isn't
brunobliss said:
AS a matter of fact i did, and found ways to flash a rom wiping all data from my phone, which is precisely what i don't want.
Now, i would thank those who actually came forward to answers to my questions instead of arguments that lead nowhere.
Thank you in advance.
Click to expand...
Click to collapse
Thank you!
I have flashed many roms in my old phone using CMW. Surely i don't want to debrand my new phone, so unless the bootloader is unlocked, i guess i'll be looking forward for the yakjuxw updates.
Thank you once more!
brunobliss said:
Thank you!
I have flashed many roms in my old phone using CMW. Surely i don't want to debrand my new phone, so unless the bootloader is unlocked, i guess i'll be looking forward for the yakjuxw updates.
Thank you once more!
Click to expand...
Click to collapse
I used to think the same way as you and i also had the same yakjuxw but the updates come too late for those versions so i decided to go yakju and i have no problems now
My advice is that you do it, if you read carefully it becomes dead easy and its worth it
Sent from my Galaxy Nexus using Tapatalk 2
As written(linked) in the article this is just the software fingerprint I can assure you will not have issues as the main software is the same. The only thing changed is who is providing the updates. Imagine windows you get with dell and hp PC they both have their logos (yakju/xw) but the windows is the same s*itty windows
I used tohave yakjuxw, changed to yakju, takju back to xw.. not im on yakju. This is my job indeed to test apps on diff android versions and i flash time quite often every day and i can assure you all works fine
Anyway if you need a ROM that tells you it is xw let me know Ill upload one for you
brunobliss said:
Thank you!
I have flashed many roms in my old phone using CMW. Surely i don't want to debrand my new phone, so unless the bootloader is unlocked, i guess i'll be looking forward for the yakjuxw updates.
Thank you once more!
Click to expand...
Click to collapse
Just to let future googlers know that the solution to convert yakjuxw to yakju as seen on this site:
http://andwise.net/?p=569
has soft bricked my phone! I was able to flash a new ROM using Gnex toolkit but (of course) i did lose all my data!
BTW, with android 4.2.2 i'm noticing that wireless turns off after i lock the phone, is there a way round this or is it a new bug ?
4.2.1 Update
I've got a Galaxy Nexus with the yakjuxw build. Previously my phone's Android version was 4.1.1. Just this morning I got the 4.2.1 update! Fire away on the Check Now buttons guys.
brunobliss said:
Just to let future googlers know that the solution to convert yakjuxw to yakju as seen on this site:
http://andwise.net/?p=569
has soft bricked my phone! I was able to flash a new ROM using Gnex toolkit but (of course) i did lose all my data!
BTW, with android 4.2.2 i'm noticing that wireless turns off after i lock the phone, is there a way round this or is it a new bug ?
Click to expand...
Click to collapse
Look around the WiFi settings, and the answer to the question in the OP is in this section's sticky, clearly you did not look hard enough, it's also in my signature if you want to take a look.(Jubakuba's Guide)
4.2.1 Update
Hi
I am using a yakjuxw variant of Galaxy Nexus I9250. Today I got an official update and now I am running 4.2.1.
The update was about 95 MB....so now this confirms people are getting update for yakjuxw variant.
thanks
Amarr