I'm using the awesome ROM and received the update....what do I do?
Sent from my Galaxy Nexus using xda app-developers app
...nm. -delete-
If I go back to stock ice cream its 4.0.2 and yakjuwx with I9250XXKK6
Sent from my Galaxy Nexus using xda app-developers app
tgunz said:
I'm using the awesome ROM and received the update....what do I do?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Don't accept it. You can't take an OTA when you're on a custom ROM.
You need to flash yakju or takju 4.0.4 (with the corresponding boot, radio and recovery images), then you can accept and install the update.
RoadHazard said:
You need to flash yakju or takju 4.0.4 (with the corresponding boot, radio and recovery images), then you can accept and install the update.
Click to expand...
Click to collapse
Well flashing back to stock yakju or takju will completely wipe the device and he'll have to wait to be notified again.
I'm back on stock... but I'm rooted...do I have to be completely stock without being rooted? I have the white international one with yakjuwx
Sent from my Galaxy Nexus using XDA
tgunz said:
I'm back on stock... but I'm rooted...do I have to be completely stock without being rooted? I have the white international one with yakjuwx
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Rooted doesn't matter. Custom recovery, system file changes (fonts, mods, etc.), and radio changes do matter and all stop you from being able to accept and auto-install an OTA.
If you're on yakjuwx though, you won't be notified for a 4.1 update. There's no 4.1 OTA rolling out for yakjuwx yet. If for some reason it has the 4.1 OTA from before saved in /cache and it tries to notify you, it won't work, because that OTA is meant for yakju 4.0.4 devices.
If you want to be on stock 4.1.1, you need to flash your phone to yakju/takju 4.0.4 and wait for the OTA or flash the OTA package yourself.
martonikaj said:
Rooted doesn't matter. Custom recovery, system file changes (fonts, mods, etc.), and radio changes do matter and all stop you from being able to accept and auto-install an OTA.
If you're on yakjuwx though, you won't be notified for a 4.1 update. There's no 4.1 OTA rolling out for yakjuwx yet. If for some reason it has the 4.1 OTA from before saved in /cache and it tries to notify you, it won't work, because that OTA is meant for yakju 4.0.4 devices.
If you want to be on stock 4.1.1, you need to flash your phone to yakju/takju 4.0.4 and wait for the OTA or flash the OTA package yourself.
Click to expand...
Click to collapse
i know theres is a way to convert over to yakju 4.0.4. how do i do that? the forums i have read led me to be all confused. much help if possible? i dont really want to brick my phone as much i really love the Gnexus
tgunz said:
i know theres is a way to convert over to yakju 4.0.4. how do i do that? the forums i have read led me to be all confused. much help if possible? i dont really want to brick my phone as much i really love the Gnexus
Click to expand...
Click to collapse
The Nexus is just about impossible to brick. Just make sure you follow the steps properly and you'll be fine.
To convert to yakju (or takju if you want Google Wallet preinstalled), follow this guide: [HOW-TO] [GSM & CDMA] Convert to latest yakju/takju/mysid (incl JB) / Return to stock
DO NOT USE A TOOLKIT. For God's sake please just read and learn how to do it. Then the next time you need to mess with your phone you'll actually have some knowledge of how it works. If you have a specific question, I'd be extremely surprised if it hasn't been asked before. You should search first, then post in that thread or post a new one with your specific issue.
martonikaj said:
The Nexus is just about impossible to brick. Just make sure you follow the steps properly and you'll be fine.
To convert to yakju (or takju if you want Google Wallet preinstalled), follow this guide: [HOW-TO] [GSM & CDMA] Convert to latest yakju/takju/mysid (incl JB) / Return to stock
DO NOT USE A TOOLKIT. For God's sake please just read and learn how to do it. Then the next time you need to mess with your phone you'll actually have some knowledge of how it works. If you have a specific question, I'd be extremely surprised if it hasn't been asked before. You should search first, then post in that thread or post a new one with your specific issue.
Click to expand...
Click to collapse
thanks a bunch...i will get back with you if im clueless...i have rooted before but reverting is pretty insane!
tgunz said:
thanks a bunch...i will get back with you if im clueless...i have rooted before but reverting is pretty insane!
Click to expand...
Click to collapse
ahhhh i followed all the steps and when i get to the cmd prompt....error!!! no luck
tgunz said:
ahhhh i followed all the steps and when i get to the cmd prompt....error!!! no luck
Click to expand...
Click to collapse
Almost definitely a driver issue. Follow the guide and you should be fine.
If you still need help, then post the specific error you get.
martonikaj said:
Almost definitely a driver issue. Follow the guide and you should be fine.
If you still need help, then post the specific error you get.
Click to expand...
Click to collapse
thanks for the help...i got it to yakju 4.0.4 and waited for the update and i got the error when it tried to update....my radio stayed the same as I9250XXKK6
thanks everyone...finally convert to yakju 4.0.4 with update radio and bootloader!
tgunz said:
thanks everyone...finally convert to yakju 4.0.4 with update radio and bootloader!
Click to expand...
Click to collapse
Good job. Should have noted in that guide that you need to do those "optional" steps that flash the radio and bootloader.
Glad you figured it out.
martonikaj said:
Good job. Should have noted in that guide that you need to do those "optional" steps that flash the radio and bootloader.
Glad you figured it out.
Click to expand...
Click to collapse
thanks! hey i got the update but failed before i installed the radio and bootloader...now i cant seem to get the notification back?...do i have to erase soomething?
tgunz said:
thanks! hey i got the update but failed before i installed the radio and bootloader...now i cant seem to get the notification back?...do i have to erase soomething?
Click to expand...
Click to collapse
It should notify you again. Or you could try to clear Google Framework and force it. Depends how anxious you are to get it.
martonikaj said:
It should notify you again. Or you could try to clear Google Framework and force it. Depends how anxious you are to get it.
Click to expand...
Click to collapse
man you are a GENIUS!!
tgunz said:
man you are a GENIUS!!
Click to expand...
Click to collapse
Don't know about that. Glad everything worked for you.
Related
My new GNex is stock,rooted, w/CWM Touch 5.8.0.2 . If I flash back to stock unrooted, will I be able to receive OTA update to IMM30B?
diver47591 said:
My new GNex is stock,rooted, w/CWM Touch 5.8.0.2 . If I flash back to stock unrooted, will I be able to receive OTA update to IMM30B?
Click to expand...
Click to collapse
y
tenchars
Thanks for that.
diver47591 said:
My new GNex is stock,rooted, w/CWM Touch 5.8.0.2 . If I flash back to stock unrooted, will I be able to receive OTA update to IMM30B?
Click to expand...
Click to collapse
No need to unroot. The update will still work even with root. However, you need to flash back the stock recovery, or the update won't install automatically.
If you get OTA root keeper https://market.android.com/details?id=org.projectvoodoo.otarootkeeper by supercurio you won't even loose root after the update, well thats the idea. Our phone is supported and I'm waiting to try it out.
Sent from my Galaxy Nexus using Tapatalk
Flashed back to stock recovery,installed OTA Rootkeeper, selected "temporary unroot",checked for systems update, says"your system is up to date",still on 4.0.2 ICL53F. Any suggrstions?
diver47591 said:
Flashed back to stock recovery,installed OTA Rootkeeper, selected "temporary unroot",checked for systems update, says"your system is up to date",still on 4.0.2 ICL53F. Any suggrstions?
Click to expand...
Click to collapse
Do you have the GSM version or the CDMA version?
ICL53F is the latest update for the GSM version. If you have the CDMA version, just update it manually. Look here.
Is there such a big advantage to be just rooted ?
--GNex-- said:
Is there such a big advantage to be just rooted ?
Click to expand...
Click to collapse
You can run apps that require root...
Some examples: Root Explorer, Light Flow, AdFree, Market Enabler, Quick Boot, Titanium Backup
--GNex-- said:
Is there such a big advantage to be just rooted ?
Click to expand...
Click to collapse
You can run root apps, but don't have a custom ROM. If you don't need root apps, then don't root
Could be wrong but last I checked 4.0.2 was the last official OTA for the CDMA nexus as well. Only two or so people received 4.0.4 and that was a fluke. But like I said, I could be wrong.
Sent from my GT-N7000 using xda premium
joshnichols189 said:
Could be wrong but last I checked 4.0.2 was the last official OTA for the CDMA nexus as well. Only two or so people received 4.0.4 and that was a fluke. But like I said, I could be wrong.
Click to expand...
Click to collapse
This is true. 4.0.2 is the latest official OTA for GSM and CDMA. Until 4.0.4 is rolling out to everyone, I don't call it "official".
joshnichols189 said:
Could be wrong but last I checked 4.0.2 was the last official OTA for the CDMA nexus as well. Only two or so people received 4.0.4 and that was a fluke. But like I said, I could be wrong.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
It may not be widespread yet, but if there is an official download link available (i.e., like this http://android.clients.google.com/p....signed-mysid-IMM30B-from-ICL53F.659e0a8f.zip), in my opinion it's pretty official.
efrant said:
It may not be widespread yet, but if there is an official download link available (i.e., like this http://android.clients.google.com/p....signed-mysid-IMM30B-from-ICL53F.659e0a8f.zip), in my opinion it's pretty official.
Click to expand...
Click to collapse
Thanks, wasn't aware of that. I haven't had a nexus since right around the first two people got that update so I thought it was a fluke
Sent from my GT-N7000 using xda premium
Can someone link to a guide dealing with restoring a Nexus? It's stuck at the Google logo. I can get into bootloader mode with power+volume down, but it's not reacting when trying to navigate with the volume buttons after that.
I got a little bit tired of waiting for official firmware on my Galaxy S2 (even if CM was fun) so I got a Nexus yesterday - great price these days. It was the 4.0.1 yakju version as I'm in Western Europe.Unlocked and rooted with Root Toolkit v1.4 after which I wanted to install 4.0.4 using this guide. Got as far as flashing system.img and then the above happened.
All I want is to get back to working stock so that I can flash 4.1. Have no data on the device so a factory reset is no problem.
Much appreciated.
Nitsson said:
Can someone link to a guide dealing with restoring a Nexus? It's stuck at the Google logo. I can get into bootloader mode with power+volume down, but it's not reacting when trying to navigate with the volume buttons after that.
I got a little bit tired of waiting for official firmware on my Galaxy S2 (even if CM was fun) so I got a Nexus yesterday - great price these days. It was the 4.0.1 yakju version as I'm in Western Europe.Unlocked and rooted with Root Toolkit v1.4 after which I wanted to install 4.0.4 using this guide. Got as far as flashing system.img and then the above happened.
All I want is to get back to working stock so that I can flash 4.1. Have no data on the device so a factory reset is no problem.
Much appreciated.
Click to expand...
Click to collapse
Just fastboot flash Nexus Factory Images if you have no problem with wiping your data. That's odd that your bootloader won't respond to volume buttons... I might say try reflashing the bootloader and recovery, but since your bootloader is acting up right now, I'd go to flashing the factory images first, and if that doesn't work, try reflashing just bootloader and a custom recovery.
Nitsson said:
Can someone link to a guide dealing with restoring a Nexus? It's stuck at the Google logo. I can get into bootloader mode with power+volume down, but it's not reacting when trying to navigate with the volume buttons after that.
I got a little bit tired of waiting for official firmware on my Galaxy S2 (even if CM was fun) so I got a Nexus yesterday - great price these days. It was the 4.0.1 yakju version as I'm in Western Europe.Unlocked and rooted with Root Toolkit v1.4 after which I wanted to install 4.0.4 using this guide. Got as far as flashing system.img and then the above happened.
All I want is to get back to working stock so that I can flash 4.1. Have no data on the device so a factory reset is no problem.
Much appreciated.
Click to expand...
Click to collapse
Have a look at posts 1 and 2 in the "flash" link in my sig.
BTW, volume down and power is not the bootloader. You need to press volume up and volume down and power.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Have a look at posts 1 and 2 in the "flash" link in my sig.
BTW, volume down and power is not the bootloader. You need to press volume up and volume down and power.
Click to expand...
Click to collapse
Perfect, that guide worked. Installed 4.0.4 and then 4.1. The root guide does not work on 4.1 however, but I'll find another one. Many thanks.
Do you know if the current 4.1 image is gold by the way?
Nitsson said:
The root guide does not work on 4.1 however, but I'll find another one. Many thanks.
Click to expand...
Click to collapse
The file in post #2 of that thread should work for 4.1
Nitsson said:
Do you know if the current 4.1 image is gold by the way?
Click to expand...
Click to collapse
Should be. If not, it should get an OTA update as well.
efrant said:
The file in post #2 of that thread should work for 4.1
Click to expand...
Click to collapse
Nope, I follow it to the letter; CWM installs fine, as does Superuser, but I don't have root access after reboot. Any ideas are appreciated.
efrant said:
Should be. If not, it should get an OTA update as well.
Click to expand...
Click to collapse
Perfect. Assuming the next Nexus is a nice step forward I hope to stay on this platform for a while.
Nitsson said:
Nope, I follow it to the letter; CWM installs fine, as does Superuser, but I don't have root access after reboot. Any ideas are appreciated.
Perfect. Assuming the next Nexus is a nice step forward I hope to stay on this platform for a while.
Click to expand...
Click to collapse
just flash any custom rom via your recovery. youll boot up with root access.
simms22 said:
just flash any custom rom via your recovery. youll boot up with root access.
Click to expand...
Click to collapse
Thanks, but the whole reason I got the Nexus was to get the pure Google experience, the latest updates, and to stop playing around with custom ROMs
Nitsson said:
Thanks, but the whole reason I got the Nexus was to get the pure Google experience, the latest updates, and to stop playing around with custom ROMs
Click to expand...
Click to collapse
stock, rooted, jellybean should be good for you then. bigxies jellybean rom in the development section should work out good for you. or you can try this flasable updated su https://www.box.com/shared/acb928d8edd41b91a6c9
Nitsson said:
Nope, I follow it to the letter; CWM installs fine, as does Superuser, but I don't have root access after reboot. Any ideas are appreciated.
Click to expand...
Click to collapse
That is because you didn't read what I posted above. You need to flash the file in post #2, not the one linked in post #1.
Sent from my Galaxy Nexus using Tapatalk 2
simms22 said:
stock, rooted, jellybean should be good for you then. bigxies jellybean rom in the development section should work out good for you. or you can try this flasable updated su https://www.box.com/shared/acb928d8edd41b91a6c9
Click to expand...
Click to collapse
But bigxie's ROM is NOT stock...
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
But bigxie's ROM is NOT stock...
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
ok, technically it not, since JB isnt out yet. im using his original version 1, so its close to where stock would/should be. but, that is just a guess on my part since, again, there is no official stock jellybean. theres only the google i/o preview version
simms22 said:
ok, technically it not, since JB isnt out yet. im using his original version 1, so its close to where stock would/should be. but, that is just a guess on my part since, again, there is no official stock jellybean. theres only the google i/o preview version
Click to expand...
Click to collapse
That's not really what I was trying to say: it is stock, but it's deodexed, which makes it not stock, and it won't be able to apply any future OTA updates.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
That's not really what I was trying to say: it is stock, but it's deodexed, which makes it not stock, and it won't be able to apply any future OTA updates.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
truth
efrant said:
That is because you didn't read what I posted above. You need to flash the file in post #2, not the one linked in post #1.
Click to expand...
Click to collapse
Flashed with CWM-SuperSU-v0.92-mod which worked like a charm. I now have both Superuser and SuperSU installed, with the latter taking precedence, but I guess that doesn't matter.
Nitsson said:
Flashed with CWM-SuperSU-v0.92-mod which worked like a charm. I now have both Superuser and SuperSU installed, with the latter taking precedence, but I guess that doesn't matter.
Click to expand...
Click to collapse
sweet, i thought it would. use root explorer to go to /system/app/ and delete the superuser app
simms22 said:
sweet, i thought it would. use root explorer to go to /system/app/ and delete the superuser app
Click to expand...
Click to collapse
Funny, but the superuser app is nowhere to be found in the list at /system/app/.
Hi!
I have the Samsung Galaxy Nexus, with CWM installed and unlocked bootloader. The phone was originally yakjuxw but I've converted it into yakju. Well now to the problem, my phone found the Jelly Bean update but when I tried to install, it didn't work. Is it because I have flashed my phone to yakju or could it be something else? What should I do? How to install it?
Without root if possible.
Also, I have tried to install it through flashing but of course that didn't work either.
Thanks in advance.
You should be 'Fully' stock before you update!
phone with CWM installed will not able to update OTA successfully.:crying:
Thank you for your response!
However , I'm not so good at these things so what is "fully stocked"?
Thank you
You are probably missing the yakju radio. It must be xxla2. If its not flash that.
Sent from my Galaxy Nexus using xda premium
Would it work to uninstall CWM somehow then, if that's possible?
Thank you for response
El Daddy said:
You are probably missing the yakju radio. It must be xxla2. If its not flash that.
How do I know if I have it?
And where can I find it?
Thank you for response
Click to expand...
Click to collapse
Sime3134 said:
You are probably missing the yakju radio. It must be xxla2. If its not flash that.
How do I know if I have it?
And where can I find it?
Thank you for response
Click to expand...
Click to collapse
I have attached both the recovery and radio for the stock IMM76I version of yakju. You will need to flash them using fastboot.
Unlawful said:
Sime3134 said:
I have attached both the recovery and radio for the stock IMM76I version of yakju. You will need to flash them using fastboot.
Click to expand...
Click to collapse
Thank you!
So it doesn't work with CWM?
And do you know if it's correct that phones with CWM installed can't install Android 4.1?
Click to expand...
Click to collapse
No to the first question.
You need to be on stock recovery to install any OTA.
You were provided a link to download.
Sent from my Galaxy Nexus using Tapatalk 2
rjcapp said:
No to the first question.
You need to be on stock recovery to install any OTA.
You were provided a link to download.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Now I see, my wrong. Thank you very much, I will test this
The update is halfway through now, hope it works now! Thank you all very much for the help!
It worked, thank you!
Hello everyone.
I've been having this problem for quite some time now, actually since i first rooted my phone back in summer 2011. Since then, whenever a new update was released I was unable to install it. I keep recieving an error i've not yet been able to find answers to. So now I'am kindly asking if any of you can help me get rid of it. I wont do a clean install "again"...
Here's the related screenshots: (same album)
imgurDOTcom/a/keZcZ#DH3LOOP
imgurDOTcom/a/keZcZ#u1Y1gMB
Thanks in advance.
Drixi said:
Hello everyone.
I've been having this problem for quite some time now, actually since i first rooted my phone back in summer 2011. Since then, whenever a new update was released I was unable to install it. I keep recieving an error i've not yet been able to find answers to. So now I'am kindly asking if any of you can help me get rid of it. I wont do a clean install "again"...
Here's the related screenshots: (same album)
imgurDOTcom/a/keZcZ#DH3LOOP
imgurDOTcom/a/keZcZ#u1Y1gMB
Thanks in advance.
Click to expand...
Click to collapse
You have modified a system file. This causes an OTA update to fail. Get the original applicationsprovider.apk for you current stock image and try again.
Drixi said:
Hello everyone.
I've been having this problem for quite some time now, actually since i first rooted my phone back in summer 2011. Since then, whenever a new update was released I was unable to install it. I keep recieving an error i've not yet been able to find answers to. So now I'am kindly asking if any of you can help me get rid of it. I wont do a clean install "again"...
Here's the related screenshots: (same album)
imgurDOTcom/a/keZcZ#DH3LOOP
imgurDOTcom/a/keZcZ#u1Y1gMB
Thanks in advance.
Click to expand...
Click to collapse
You are either not running a stock ROM, or you are trying to flash a takju update on a yakju ROM. Have a look at the OTA update thread in the General section. There are instructions on how to replace the system files. (Easiest would be to flash the system.img file from the factory image of the version you are currently running, and then the update will install.)
By the way, the GNex was not even out in summer 2011...
Petrovski80 said:
You have modified a system file. This causes an OTA update to fail. Get the original applicationsprovider.apk for you current stock image and try again.
Click to expand...
Click to collapse
efrant said:
You are either not running a stock ROM, or you are trying to flash a takju update on a yakju ROM. Have a look at the OTA update thread in the General section. There are instructions on how to replace the system files. (Easiest would be to flash the system.img file from the factory image of the version you are currently running, and then the update will install.)
By the way, the GNex was not even out in summer 2011...
Click to expand...
Click to collapse
2012* Typo ftw But thanks.
I'am using a stock ROM, unless the website was trolling and changed the filename on a non-stock ROM And I'am pretty sure that I did not mix up takju/yakju. I went trough everything a couple of times back then because I didnt want to mess up my phone - Look how that went -.-'
Anyway. A modified system file seem possible. How this happened, I'am unsure off, but I wont disagree that I didnt do something that might have caused this. I'll try the related solution tomorrow and post results.. Thanks guys - Amazingly fast answers
Drixi said:
2012* Typo ftw But thanks.
I'am using a stock ROM, unless the website was trolling and changed the filename on a non-stock ROM And I'am pretty sure that I did not mix up takju/yakju. I went trough everything a couple of times back then because I didnt want to mess up my phone - Look how that went -.-'
Anyway. A modified system file seem possible. How this happened, I'am unsure off, but I wont disagree that I didnt do something that might have caused this. I'll try the related solution tomorrow and post results.. Thanks guys - Amazingly fast answers
Click to expand...
Click to collapse
Note that a deodexed ROM is not stock, regardless of whether someone calls it stock or not.
efrant said:
Note that a deodexed ROM is not stock, regardless of whether someone calls it stock or not.
Click to expand...
Click to collapse
Could this can happen on source built, deodexed ROMs when build.prop is edited (product name, model, build) to match stock aka factory images?
Edit: the OTA update I mean
Sent from my Nexus
bk201doesntexist said:
Could this can happen on source built, deodexed ROMs when build.prop is edited (product name, model, build) to match stock aka factory images?
Edit: the OTA update I mean
Sent from my Nexus
Click to expand...
Click to collapse
Since stock ROMs are Odexed I don't see it making a difference.
063_XOBX said:
Since stock ROMs are Odexed I don't see it making a difference.
Click to expand...
Click to collapse
it wouldnt make a difference. the rom does not match what the OTA is expecting.
during the apply_patch process, a check is run to make sure everything matches what it should.
063_XOBX said:
Since stock ROMs are Odexed I don't see it making a difference.
Click to expand...
Click to collapse
Yes, but it would receive the notification, right? Hmm, I need to remove update system.
Sent from my Nexus
bk201doesntexist said:
Yes, but it would receive the notification, right? Hmm, I need to remove update system.
Sent from my Nexus
Click to expand...
Click to collapse
yes it would receive the update notification.
Do u have cwm installed? If so that would also caused your ota to fail.
Sent from my Galaxy Nexus using xda premium
Esteway.619 said:
Do u have cwm installed? If so that would also caused your ota to fail.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
no it doesnt.
Please somebody update the OTA (NO factory images) for the TAKJU Galaxy Nexus, Yakju has received recently! Thanks in advance!
Questions goes in the Q&A, read the rules sticky.
Beamed from my Maguro.
That's technically not a question...
Sent from my Galaxy Nexus using xda premium
markitosd said:
Please somebody update the OTA (NO factory images) for the TAKJU Galaxy Nexus, Yakju has received recently! Thanks in advance!
Click to expand...
Click to collapse
if you have an unlocked bootloader you can flash the stock images via fastboot. don't flash all together. Flash the bootloader then radio finally the image(make sure you remove the userdata.img from the image.zip). this is exactly what I did and I now have 4.3 and didn't lose a single bit of my app data.
mij1525 said:
That's technically not a question...
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
There is a [Q] tag, so it goes there.
And regarding OTAs, just wait for it, nothing major..
Beamed from my Maguro.
You're seriously asking this? I didn't know we had google employees in xda. Why not just download the flash able image from the Google developers website and save time from making a post that's useless. Also someone can't make an OTA. Only google can.
Sent from my Nexus 4 using Tapatalk 4 Beta
navodwickra said:
if you have an unlocked bootloader you can flash the stock images via fastboot. don't flash all together. Flash the bootloader then radio finally the image(make sure you remove the userdata.img from the image.zip). this is exactly what I did and I now have 4.3 and didn't lose a single bit of my app data.
Click to expand...
Click to collapse
Can I do this from the phone only? I have no access to a usb cable or a computer, and I need to update completely from the phone.
Is that possible?
/Söder
soder said:
Can I do this from the phone only? I have no access to a usb cable or a computer, and I need to update completely from the phone.
Is that possible?
/Söder
Click to expand...
Click to collapse
Then wait for the OTA..
Beamed from my Grouper
Mach3.2 said:
Then wait for the OTA..
Beamed from my Grouper
Click to expand...
Click to collapse
Yeah, I wait and I wait and I wait. =) That's why I asked about this method.
But also with the OTA, there is a chance that is will not work to flash since there might be some stuff I have done to the /system.
That was the case the for me with the 4.2.2 update, and I needed to use the Google Factory Image, and reset my internal memory and all that (I didn'n know about methods to NOT reset the internal memory then).
Strange there are no flashable .zip's that are complete stock with only some kind of root added. Just stock, that should work to update to next version, like 5.0, with OTA then. Or is there?
EDIT: I found this. http://forum.xda-developers.com/showthread.php?t=2016452
Can someone please tell me if there was some new bootloader or radio or something like that, that I need to update more then using pure stock - odexed - UNTOUCHED?
/Söder