Hey guys, I just bought a used galaxy nexus locally and need help.
The previous owner had it rooted but he asked me if I wanted it to stock before selling it to me. I agreed and he gave it to me with the locked bootloader and on stock ICS.
I'm having a small issue though, whenever I go to settings, I'm getting a ton of crashes.
is there any way that I can re-flash stock without rooting the phone again? I just want to wait for stock JB and root in the near future.
Thanks a ton
EDIT: Its a sprint Gnex
Man a odin flashable file?
Enviado desde mi Galaxy Nexus usando Tapatalk 2
coldrazor said:
Man a odin flashable file?
Enviado desde mi Galaxy Nexus usando Tapatalk 2
Click to expand...
Click to collapse
Huh?
gab2012 said:
Huh?
Click to expand...
Click to collapse
Search ODIN flash
Sent from my Galaxy Nexus using XDA Premium HD app
I have a sprint nexus. If you would like I could remotely Odin your phone back to stock. Otherwise I can get you a video tutorial you can follow.
http://forum.xda-developers.com/showthread.php?t=1614922
Look for the link How to Unroot. Yes I know its not rooted but this does the same thing.
Sent From My Toro+ via SkyBlue Tapatalk
ÜBER™ said:
I have a sprint nexus. If you would like I could remotely Odin your phone back to stock. Otherwise I can get you a video tutorial you can follow.
http://forum.xda-developers.com/showthread.php?t=1614922
Look for the link How to Unroot. Yes I know its not rooted but this does the same thing.
Sent From My Toro+ via SkyBlue Tapatalk
Click to expand...
Click to collapse
Thanks for the tips I'll try my best and post up my results in a while
Did the whole process twice successfully and still get FC on settings What else can I try? I have insurance and might take it to sprint to have it checked out.
I just rooted the phone for the heck of it and flashed ACS Ru jellying rom and the problem is still there! settings keep FCing
I think I'm going to have to end up going to sprint and getting a refurb (not a problem but a big waste of time since the reps here don't know anything and keep you at the store for 2 hours while they try to reset it)
Anyone?
gab2012 said:
I just rooted the phone for the heck of it and flashed ACS Ru jellying rom and the problem is still there! settings keep FCing
I think I'm going to have to end up going to sprint and getting a refurb (not a problem but a big waste of time since the reps here don't know anything and keep you at the store for 2 hours while they try to reset it)
Click to expand...
Click to collapse
Something to try that's super helpful is the Galaxy Nexus Toolkit from the GNex dev pages, it can do literally anything:
http://forum.xda-developers.com/showthread.php?t=1392310
When you flashed the new ROM did you format /system in clockworkmod? When you have weird persistent problems what you probably need to do is boot into clockwork, do a factory reset, then go into 'mounts and storage' and format /system. To be extra thorough from the main menu go to advanced->format dalvik cache, then flash your new ROM (and flash gapps if the ROM needs it). What probably happened is that the previous guy neglected to format everything correctly and now your system apps are borked.
Also if you were waiting for JellyBean stock, you can get a stock JB ROM out of the GNex dev threads. I've been running a JB ROM for about a week and there's no reason to wait anymore.
Taboobat said:
Something to try that's super helpful is the Galaxy Nexus Toolkit from the GNex dev pages, it can do literally anything:
http://forum.xda-developers.com/showthread.php?t=1392310
When you flashed the new ROM did you format /system in clockworkmod? When you have weird persistent problems what you probably need to do is boot into clockwork, do a factory reset, then go into 'mounts and storage' and format /system. To be extra thorough from the main menu go to advanced->format dalvik cache, then flash your new ROM (and flash gapps if the ROM needs it). What probably happened is that the previous guy neglected to format everything correctly and now your system apps are borked.
Also if you were waiting for JellyBean stock, you can get a stock JB ROM out of the GNex dev threads. I've been running a JB ROM for about a week and there's no reason to wait anymore.
Click to expand...
Click to collapse
Thanks for the help!
I will format/erase and reflash and come back with the results!
I added my google credentials and everything seems to be working now. I'll keep using the phone for today and keep you guys posted.
Any nice battery saving tips? going on a trip to Miami tomorrow, planing on loading the phone with my albums today so I'm ready for tomorrow
Ok it happened again today while I was at the airport waiting for my flight. The settings froze when I pressed more in order to get to airplane mode.
I got frustrated and wiped the whole phone several times and re-flashed ru jellyin rom + gapps.
(went into twrp and wiped everything 3 times before flashing the rom + gapps)
Everything seems to be fine again. Can i take my phone in for service if its rooted? if not ill wait until i get home to unroot it (left my laptop) and take it in.
I think the thing that caused this for me was google wallet since I had it installed yesterday and installed it again this morning at the airport before the problems began.
Sent from my Galaxy Nexus using xda premium
Related
To start I am a newb
I Have a galaxy nexus with the 4.1 Jelly Beans ( not stock, installed via ROM from here xda). That's fine. This week a new "system" update was available for my phone. So I downloaded it and the phone reboot, when the phone starts it goes to the cwm recovery screen saying the update failed. I would like to have some HELP, I found other threads, but I really don't want to do anything worng.
My questions:
How can i get the updates to work again?
DO i need to get ICS back to update the phone?
How should i do it?
Can I do that without losing my data ( would be great, but i am ok if there is no way)
I am just afraid if i go back to ICS, and the update don't show up.
Jpcsilva said:
To start I am a newb
I Have a galaxy nexus with the 4.1 Jelly Beans ( not stock, installed via ROM from here xda). That's fine. This week a new "system" update was available for my phone. So I downloaded it and the phone reboot, when the phone starts it goes to the cwm recovery screen saying the update failed. I would like to have some HELP, I found other threads, but I really don't want to do anything worng.
My questions:
How can i get the updates to work again?
DO i need to get ICS back to update the phone?
How should i do it?
Can I do that without losing my data ( would be great, but i am ok if there is no way)
I am just afraid if i go back to ICS, and the update don't show up.
Click to expand...
Click to collapse
Flash your phone back to stock... then do the ota update... profit...
Sent from my Galaxy Nexus using xda app-developers app
Everything must must be bone stock to install an ota.
Jellin' like a felon
The issue at hand here is that you have a custom recovery. I can't say that if you remove CWM that you'll be able to OTA update, but that's at least what was the problem there. Now, if you want to keep all your apps and update to the OTA jelly bean instead of the Google I/O preview build, you can flash this here: http://forum.xda-developers.com/showthread.php?t=1737849
Follow the instructions on that post to update. This is what I did and it worked perfectly.
Camera not working after JB update!
Hi! I recently installed JB on my Dad's Galaxy Nexus, whilst everything seems to work fine, I've noticed that the camera has stopped working. The screen goes blank if i access the camera. I've tried installing 3rd party applications for camera, but none of them work! Please help me! Is it a hardware or a software fault?
nishantbhatia84 said:
Hi! I recently installed JB on my Dad's Galaxy Nexus, whilst everything seems to work fine, I've noticed that the camera has stopped working. The screen goes blank if i access the camera. I've tried installing 3rd party applications for camera, but none of them work! Please help me! Is it a hardware or a software fault?
Click to expand...
Click to collapse
What Rom? Custom or stock
What kernel? Custom or stock
Sent from my Galaxy Nexus using Tapatalk 2
And how do i do that? I really dont know how to flash it
Sent from my Galaxy Nexus using xda app-developers app
Stock JB Rom & stock kernel!
I'm gonna go back to ICS and check if that resolves the issue! What say?
Sent from my Galaxy Nexus using xda premium
nishantbhatia84 said:
Stock JB Rom & stock kernel!
I'm gonna go back to ICS and check if that resolves the issue! What say?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
first try factory reset, otherwise yes go back to stock ics and check.
Jp182
atifsh said:
first try factory reset, otherwise yes go back to stock ics and check.
Click to expand...
Click to collapse
But going to factory reset will not remove the cwm recovery... right? If i go to factory data reset on my phone ( remember i am using a 4.1 rom) will it go back to ics and delete all roms / root? Cause this sounds like the best way to do it, but you were the first one that said that. Bought my phone from Amazon unlocked ( do you guys think it is gonna update?)
I did that, no help! I think it's a hardware fault. Thanks anyway!
Sent from my Galaxy Nexus using xda premium
I don't get it. What did you do? Factory reset? Installed the stock?
Sent from my Galaxy Nexus using xda app-developers app
HELPPPPPP
nishantbhatia84 said:
I did that, no help! I think it's a hardware fault. Thanks anyway!
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
PLZ, tell me!! If I do the factory reset is it gonna remove CWM, and all stuff i have installed?
You said you downloaded your ROM from here, but you didn't say which one. There was at least one (Koush's) that was an image of the stock ROM, taken from the OTA update that went out to the phones given out at Google I/O. If you have that ROM (and the corresponding radio), you can just use CWM to install the OTA update. I know this works because I did it myself.
If you really have one of the custom ROMs, your only choice is to return to stock if you want the official OTA. And yes, this will remove CWM and wipe your entire phone (including anything in /sdcard)... so backup anything you want to keep before you try this. See efrant's excellent guide here: http://forum.xda-developers.com/showthread.php?t=1626895
ok
phazerorg said:
You said you downloaded your ROM from here, but you didn't say which one. There was at least one (Koush's) that was an image of the stock ROM, taken from the OTA update that went out to the phones given out at Google I/O. If you have that ROM (and the corresponding radio), you can just use CWM to install the OTA update. I know this works because I did it myself.
If you really have one of the custom ROMs, your only choice is to return to stock if you want the official OTA. And yes, this will remove CWM and wipe your entire phone (including anything in /sdcard)... so backup anything you want to keep before you try this. See efrant's excellent guide here: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Sorry man, I know i am not giving a lot of information, but that's cause i really don't know. I did a random "how to update your galaxy nexus to 4.1" tutorial, and i don't even remember where...... I just know the links i download were from here.
So what i am going to do:
1: Factory data reset
2: I think it's going back to ICS
3: Just do the normal system update that should just pop up.
My only fear is if the phone does not ask for update.
If you restore to stock using efrant's guide, it will be ICS since Google has not yet posted Jelly Bean firmware images. If you don't get the OTA notification or don't want to wait for it, you can just download and apply it manually (see here: http://forum.xda-developers.com/showthread.php?t=1419170)
Factory reset factory reset
phazerorg said:
If you restore to stock using efrant's guide, it will be ICS since Google has not yet posted Jelly Bean firmware images. If you don't get the OTA notification or don't want to wait for it, you can just download and apply it manually (see here: http://forum.xda-developers.com/showthread.php?t=1419170)
Click to expand...
Click to collapse
I want to restore it VIA FACTORY RESET. Cant i?
Jpcsilva said:
I want to restore it VIA FACTORY RESET. Cant i?
Click to expand...
Click to collapse
No, that will just wipe data. You'll have a clean phone, but with the same ROM you currently have. The phone doesn't keep a copy of the stock firmware hidden away or anything like that. Efrant's guide is the proper way to restore everything back to stock.
Im just running stock rooted tw. I just got the ics update pushed to my phone and I want to update. I know it won't fly because of cwm recovery. What's the best way to upgrade to ics from here?
I one of these days when ive got time I will be loading a custom rom. I dabbled with cm9 a bit, but what I need is a stable rom that has a good strong radio and GPS. So that's why I'm hanging with stock for now.
Sent from my SPH-D710 using Tapatalk 2
In a little but there will be an Odin tar out use that
But be warned it'll wipe your data
Sent from my SPH-L710 using xda premium
BiffTirkle said:
Im just running stock rooted tw. I just got the ics update pushed to my phone and I want to update. I know it won't fly because of cwm recovery. What's the best way to upgrade to ics from here?
I one of these days when ive got time I will be loading a custom rom. I dabbled with cm9 a bit, but what I need is a stable rom that has a good strong radio and GPS. So that's why I'm hanging with stock for now.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Why not just use SFHubs FF18 One Click, no data then run this to disable the OTA msg if you continue to get that?
To get your CWM Recovery back, just use the Autoroot to install CWM for FF18..
gtuansdiamm said:
In a little but there will be an Odin tar out use that
But be warned it'll wipe your data
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
There is already a OC out..
OP, you have the same phone as me and when I asked this I was told I was in the wrong section...
All I have is root for EL29 on my phone. Do you think it's safe to accept the OTA?
Sent from my Samsung Galaxy S II Epic 4G Touch, Heaux!
Charlottte said:
OP, you have the same phone as me and when I asked this I was told I was in the wrong section...
All I have is root for EL29 on my phone. Do you think it's safe to accept the OTA?
Sent from my Samsung Galaxy S II Epic 4G Touch, Heaux!
Click to expand...
Click to collapse
Why would you be in the wrong section?
And according to sfhub, and others, having root alone should not prevent the update. Though some have said it's failed.
The latest OTA is said to fix swype, and that's it.. But that's just a matter of clearing swype cache.
Why not try the update? Everyone is having their own experiences, bad / good battery life, phantom reboots, lockups, great reception.. etc..
Why not try it out? You can always change it..
MoHoGalore said:
Why would you be in the wrong section?
And according to sfhub, and others, having root alone should not prevent the update. Though some have said it's failed.
The latest OTA is said to fix swype, and that's it.. But that's just a matter of clearing swype cache.
Why not try the update? Everyone is having their own experiences, bad / good battery life, phantom reboots, lockups, great reception.. etc..
Why not try it out? You can always change it..
Click to expand...
Click to collapse
I ultimately tried it, but I'm screwed. I edited my Droidsansfallback.ttf to get soft emojis for my phone. During the update it stopped and said something about the file. I think it meant it was unverified. It also had a string of letters and numbers after it (DroidSansFallback.ttf, be7fksdsk1333, 340dj3045, etc). I'm re-downloading the stock rom in hopes that it will fix everything, but I chose no data wipe so I don't know.
Charlottte said:
I ultimately tried it, but I'm screwed. I edited my Droidsansfallback.ttf to get soft emojis for my phone. During the update it stopped and said something about the file. I think it meant it was unverified. It also had a string of letters and numbers after it (DroidSansFallback.ttf, be7fksdsk1333, 340dj3045, etc). I'm re-downloading the stock rom in hopes that it will fix everything, but I chose no data wipe so I don't know.
Click to expand...
Click to collapse
Give an update after if you don't mind.
Are you going back stock el29 for the OTA or just using the ff18?
Did you make a backup of droidsansfallback prior to editing?
:edit: I'm wondering if you had the update still in cache and went with a stock ttf and tried replying the update. I don't know if a fail clears it out of cache though..
MoHoGalore said:
Give an update after if you don't mind.
Are you going back stock el29 for the OTA or just using the ff18?
Did you make a backup of droidsansfallback prior to editing?
:edit: I'm wondering if you had the update still in cache and went with a stock ttf and tried replying the update. I don't know if a fail clears it out of cache though..
Click to expand...
Click to collapse
It's going to take an extremely long time [or a place with better reception] to download this. If someone could just send me the ttf it would be awesome.
I'm going back to stock rooted EL29. If I get another issue, I'll enable temp root. I did not make a backup of DSFB, unfortunately.
Charlottte said:
It's going to take an extremely long time [or a place with better reception] to download this. If someone could just send me the ttf it would be awesome.
I'm going back to stock rooted EL29. If I get another issue, I'll enable temp root. I did not make a backup of DSFB, unfortunately.
Click to expand...
Click to collapse
If you don't mind waiting for a bit, I'm currently trying something. But I'll go back stock rooted (el29 right??) and pull it.
Here ya go.. Don't know if it'll help but if that's where you failed, this is stock..
MoHoGalore said:
If you don't mind waiting for a bit, I'm currently trying something. But I'll go back stock rooted (el29 right??) and pull it.
Here ya go.. Don't know if it'll help but if that's where you failed, this is stock..
Click to expand...
Click to collapse
Ugh! Thank you so much for the file! BUT, I don't have the update anymore! When I go to update Android, I see "system is up to date." Should I just use ODIN and get fully rooted FF18?
Charlottte said:
Ugh! Thank you so much for the file! BUT, I don't have the update anymore! When I go to update Android, I see "system is up to date." Should I just use ODIN and get fully rooted FF18?
Click to expand...
Click to collapse
Personally? I would root and use a custom recovery to flash a nicely built rom. But that's what I would do.
I can either get you the update zip, and some links are still active to the latest OTA, or you can go custom.
Your call..
MoHoGalore said:
Personally? I would root and use a custom recovery to flash a nicely built rom. But that's what I would do.
I can either get you the update zip, and some links are still active to the latest OTA, or you can go custom.
Your call..
Click to expand...
Click to collapse
Well, I wanted to play around with ICS before I got a custom ROM, specially since I don't know which one I like yet (for EL29/2.3.6).
If it isn't too much trouble, if you could send me the update zip that would be awesome. If not, I'll stock with an ICS ROM
Sent from my Samsung Galaxy S II Epic 4G Touch, Heaux!
Charlottte said:
Well, I wanted to play around with ICS before I got a custom ROM, specially since I don't know which one I like yet (for EL29/2.3.6).
If it isn't too much trouble, if you could send me the update zip that would be awesome. If not, I'll stock with an ICS ROM
Sent from my Samsung Galaxy S II Epic 4G Touch, Heaux!
Click to expand...
Click to collapse
There are plenty of custom ics roms in the Dev section. And el29 is 2.3.6 btw depends on what you want, aosp(cm9, aokp) or tw(blu kuban, goodness, venum ice, etc) lots of choices, I personally only use aosp roms and exclusively aokp out of the choices. I'm not a fan of tw the UI looks like something my 5yo made with his crayons
We are legion, for we are many.
Sent from the DarkSide of the GalaXy with a MEK device
Charlottte said:
Well, I wanted to play around with ICS before I got a custom ROM, specially since I don't know which one I like yet (for EL29/2.3.6).
If it isn't too much trouble, if you could send me the update zip that would be awesome. If not, I'll stock with an ICS ROM
Sent from my Samsung Galaxy S II Epic 4G Touch, Heaux!
Click to expand...
Click to collapse
Crawrj still has his link active. Very recent update and you can use the stock recovery to use as the update. Just say the word of you don't know how to boot into recovery and apply. No need to rename but you can of you like, just name it update.zip and place into your sdcard.
http://d-h.st/aIc
Sent from my SPH-D710 using xda app-developers app
Okay soo, sorry for not posting! I got the OTA AGAIN, and I attempted to do it again. I didn't get an error about my font. It just said "Manual Error" "E:/ File Reporteded." and update failed somewhere so. I'm downloading the update zip still; almost done...do you think it's worth trying? Also, is it full wipe?
Sent from my Samsung Galaxy S II Epic 4G Touch, Heaux!
Charlottte said:
Okay soo, sorry for not posting! I got the OTA AGAIN, and I attempted to do it again. I didn't get an error about my font. It just said "Manual Error" "E:/ File Reporteded." and update failed somewhere so. I'm downloading the update zip still; almost done...do you think it's worth trying? Also, is it full wipe?
Sent from my Samsung Galaxy S II Epic 4G Touch, Heaux!
Click to expand...
Click to collapse
If you're using the link from the post above you, no, its not a full wipe. That is the ota file.
You'll need to boot your phone into recovery and apply the update.zip option.
Personally, no, i wouldn't run the ota.
Sent from my SPH-D710 using xda app-developers app
I finally got ICS! I used ODIN to flash the FF18 update instead of recovery and it worked. Wifi isn't as strong, the font is a smidge awkward, I still don't know how to take screenshots, but other than that ICS is awesome!
Sent from my Samsung Galaxy S II Epic 4G Touch, Heaux!
Charlottte said:
I finally got ICS! I used ODIN to flash the FF18 update instead of recovery and it worked. Wifi isn't as strong, the font is a smidge awkward, I still don't know how to take screenshots, but other than that ICS is awesome!
Sent from my Samsung Galaxy S II Epic 4G Touch, Heaux!
Click to expand...
Click to collapse
Long press power/vol down or power/home. Hold for about 3 seconds.
Sent from my SPH-D710 using Tapatalk 2
I have been on ICS since the update and although i like the interface i have been having nothing but problems. i ended up backing up with titanium and doing a reset of the phone, still having issues although not as much with the wifi.
phone freezes at time, wifi needs to be refreshed at times, phone runs slow and somewhat choppy (removed live wallpaper to help relieve.), when i click on apps there is like a fading delay transition into the app. Oh and battery will not last more thank 5 and a half hours... and that is with light to no use.
I am no thinking of going with a custom rom ( i am rooted with oden). what rom should i go with that will give a similair look to ics but without all the problems.
thanks
ALpHaMoNk said:
I have been on ICS since the update and although i like the interface i have been having nothing but problems. i ended up backing up with titanium and doing a reset of the phone, still having issues although not as much with the wifi.
phone freezes at time, wifi needs to be refreshed at times, phone runs slow and somewhat choppy (removed live wallpaper to help relieve.), when i click on apps there is like a fading delay transition into the app. Oh and battery will not last more thank 5 and a half hours... and that is with light to no use.
I am no thinking of going with a custom rom ( i am rooted with oden). what rom should i go with that will give a similair look to ics but without all the problems.
thanks
Click to expand...
Click to collapse
Is that 5 1/2 hours on screen time or total battery life?
And there are several Stock "look and feels" in the Dev section. As with any Rom, YMMV. It's just a matter of taste and all anyone can really suggest is reading through the threads and seeing what appeals to you. Read through in it's entirety to get known issues, compliments, fixes, adjustments, etc..
PLEASE TAKE THE TIME TO READ, THANK YOU.
Hello,
I am a Galaxy Nexus user, non rooted, running Android version 4.3. Yesterday I was running 4.2.2 and everything was fine and running as normal. Keep in mind I never rooted my phone, although I have to others in the past. My Nexus was running pure official 4.2.2. I had been waiting for the 4.3 update and was extremely excited when I was the notification that it was ready for my phone. I quickly downloaded it and then it rebooted the phone, as any update should. That's where everything went downhill. The phone started to lag immediately when I turned it on. It was sputtering and jerking but I just thought it was getting used to the update. Then the phone would loose its onscreen buttons and turn the page that I was looking at full screen (meaning I couldn't press home or back, because they simply just weren't there). Then the phone froze all together and after waiting 20 minutes I finally took the battery out and tried again. The EXACT same thing has been happening ever since yesterday and it has made the phone unusable because it will freeze 5 minutes into turning it on. And we then screen times out, the screen will not turn back on, as if the phone was off, when it is not. I'm very frustrated because the phone was working flawlessly before the update and now I have to use my retired G1 because the phone is that unresponsive. I was just hoping someone could please help me, or has a similar story and could make this known to Google. Thank you for reading, please if you can, help me.
Justin
Wipe cache and dalvik cacheand flash stock factory images through fastboot
Then flash the latest root files superSU 1.45 and then everything will be okay again.
Carlos_Manuel said:
Wipe cache and dalvik cacheand flash stock factory images through fastboot
Then flash the latest root files superSU 1.45 and then everything will be okay again.
Click to expand...
Click to collapse
Did you even read the post? He's never rooted and 100% stock.
Sdobron said:
Did you even read the post? He's never rooted and 100% stock.
Click to expand...
Click to collapse
Whoops. Sorry I read that quickly... Anyway flashing JB 4.3 factory images should fix that...
His systemui .apk is force closing.. Reflash if ur gonna root .. Or wie data... Best method root and flash.. Seems to be a very simple fix..
ferozfero said:
His systemui .apk is force closing.. Reflash if ur gonna root .. Or wie data... Best method root and flash.. Seems to be a very simple fix..
Click to expand...
Click to collapse
Since he didn't root his Galaxy Nexus, this method should make him lose all apps data or even internal storage since he has to unlock his bootloader for root.
But it seems to be the only method.
It's time for a full wipe.
Sent from my Nexus 4 using Tapatalk 4 Beta
I had exactly the same problem so I did factory reset from phone settings 2 days ago and now is just like a new phone working great.
There are just too many changes google did in ~6 months so full wipe is necessary.
Sent from my Galaxy Nexus using xda app-developers app
Here is my advice: use Nexus toolkit from the development section. Perform the unlock and then flash the factory image. Download it before to start. I always do that way with the new updates. Wipe ewerything. It's worth it.
Sent from my Galaxy Nexus using xda premium
teddy_irish said:
Here is my advice: use Nexus toolkit from the development section. Perform the unlock and then flash the factory image. Download it before to start. I always do that way with the new updates. Wipe ewerything. It's worth it.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Please don't use a toolkit.
Just use fastboot commands.
Beauenheim said:
Please don't use a toolkit.
Just use fastboot commands.
Click to expand...
Click to collapse
Right, and it's safe.
Please backup all your data before you do it.
I have lots of experience flashing android roms and this may be a first for me.
Flashed latest MMuzzyrom 4.3 vanilla. Originally had latest stock rooted.
Everything worked flashed full gapps for 4.3 right after it and booted right into android. Everything was previously wiped clean. rebooted soon after and it stick on "google" with "unlock"
screen for half an hour before giving up.
Tried second time and booted right into the new rom. I forgot about the previous reboot issue. spent all day getting most of my apps installed and everything setup. Went to reboot and same crap . Tried clearing cache and dalvik no help.
Wish I would have not wasted my time. I only wish their is a way to salvage this before flashing another rom or a stock image.
wseyller said:
I have lots of experience flashing android roms and this may be a first for me.
Flashed latest MMuzzyrom 4.3 vanilla. Originally had latest stock rooted.
Everything worked flashed full gapps for 4.3 right after it and booted right into android. Everything was previously wiped clean. rebooted soon after and it stick on "google" with "unlock"
screen for half an hour before giving up.
Tried second time and booted right into the new rom. I forgot about the previous reboot issue. spent all day getting most of my apps installed and everything setup. Went to reboot and same crap . Tried clearing cache and dalvik no help.
Wish I would have not wasted my time. I only wish their is a way to salvage this before flashing another rom or a stock image.
Click to expand...
Click to collapse
I have lots of experience as well and this is the first time I've run into this issue. The same **** has been happening to me on all 4.3 ROMs. I had to wipe everything, including internal storage, and reflash a 4.2.2 ROM to solve it. Wish I knew the issue here.
I decided to try flashing a different 4.3 ROM and it hung up for some reason during booting. I then decided to flash the factory image. Then tried the different ROM I downloaded. Seems to be good now. I still don't know what caused it but life is good now.
Sent from my Galaxy Nexus using Tapatalk 2
Can I ask where you found the factory image? I just picked up a Gnex so I'm still figuring everything out
playpolo4life said:
Can I ask where you found the factory image? I just picked up a Gnex so I'm still figuring everything out
Click to expand...
Click to collapse
Sorry not sure. Had it saved on my hard drive for a while. Try to download galaxy root toolkit I think it has the ability to download it for you if I remember right.
Sent from my Galaxy Nexus using Tapatalk 2
playpolo4life said:
Can I ask where you found the factory image? I just picked up a Gnex so I'm still figuring everything out
Click to expand...
Click to collapse
wseyller said:
Sorry not sure. Had it saved on my hard drive for a while. Try to download galaxy root toolkit I think it has the ability to download it for you if I remember right.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Wow.
GOOGLE!
Literally Google hosts the damn images for you.
Search for galaxy nexus factory images.
Did everyone forget who gives us this OS? A search company.
Sent from my Galaxy Nexus
What I can't understand is that I have no issues on stock. Zero. Is my device the best device in the world?
Why are you people flashing 4.3 "vanilla ROMs" through a custom recovery when we've got FACTORY IMAGES.
Is it really that hard to root a stock rom? Just follow the whole situation going on with su and you'll know!
Oh and drop the damn toolkit.
Pirateghost said:
Wow.
GOOGLE!
Literally Google hosts the damn images for you.
Search for galaxy nexus factory images.
Did everyone forget who gives us this OS? A search company.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
beekay201 said:
What I can't understand is that I have no issues on stock. Zero. Is my device the best device in the world?
Why are you people flashing 4.3 "vanilla ROMs" through a custom recovery when we've got FACTORY IMAGES.
Is it really that hard to root a stock rom? Just follow the whole situation going on with su and you'll know!
Oh and drop the damn toolkit.
Click to expand...
Click to collapse
You guys need to chill out, that's for damn sure.
Hi all,
My phone's USB port does not work at all. I need to get the stock software back on to take it back to Sprint, but cannot use Odin to do so (because of the bad USB port).
I tried flashing the FL24 tar file (from Rwilco12's repository) using Mobile Odin (I checked wipe cache & dalvik, and selected the file in the "System" button), but I must've done something wrong because it wouldn't boot, and CWM recovery was still there. So I restored my last backup.
Any input on why the flash didn't take? Did I use the wrong tar file? Am I doing something wrong in Mobile Odin?
Any help or suggestions would be greatly appreciated! =)
pillzbury said:
Hi all,
My phone's USB port does not work at all. I need to get the stock software back on to take it back to Sprint, but cannot use Odin to do so (because of the bad USB port).
I tried flashing the FL24 tar file (from Rwilco12's repository) using Mobile Odin (I checked wipe cache & dalvik, and selected the file in the "System" button), but I must've done something wrong because it wouldn't boot, and CWM recovery was still there. So I restored my last backup.
Any input on why the flash didn't take? Did I use the wrong tar file? Am I doing something wrong in Mobile Odin?
Any help or suggestions would be greatly appreciated! =)
Click to expand...
Click to collapse
I have not had to do this, but I'm thinking that if you flash an ICS or GB rom in recovery, you might be able to upgrade to the latest stock OTA available in settings>updates
I think you need Mobile Odin Pro to flash that. Mobile Odin free will only flash kernals, at least mine will only flash kernals.
Do you need stock or stock w/ root? What ROM and version are you on now?
Sent from my SPH-D710 using XDA Premium 4 mobile app
drunk0Nwater said:
Do you need stock or stock w/ root? What ROM and version are you on now?
Sent from my SPH-D710 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I need just stock, unrooted. I am on CM 10.1 right now, nightly build from 9/23.
pillzbury said:
I need just stock, unrooted. I am on CM 10.1 right now, nightly build from 9/23.
Click to expand...
Click to collapse
What's your goal? Upgrade or replacement? That drives much of the answer, as expediency is the driver here. Your phone having a busted USB port limits your options at the store. If it's upgrade, just wipe the dang thing from CWM, remove your SD card and call it a day. You've got a real shot at getting a nominal amount of credit for a busted phone towards a new one. If it's replacement, your options are entirely different.
Sent from my SPH-D710 using inverted blue xda premium
I decided I'm just going to take micmars's suggestion and wipe the thing in recovery. Initially, I was trying to get the phone replaced because I wanted to delay my upgrade for a few months until the new s5 or maybe the Nexus 5 came out, but I decided just to upgrade tomorrow when I'm eligible and get the Note 2 (can't justify Sprint's ridiculous $350 on-contract price tag for the Note 3).
Again, thanks for everyone's help and input!
pillzbury said:
I decided I'm just going to take micmars's suggestion and wipe the thing in recovery. Initially, I was trying to get the phone replaced because I wanted to delay my upgrade for a few months until the new s5 or maybe the Nexus 5 came out, but I decided just to upgrade tomorrow when I'm eligible and get the Note 2 (can't justify Sprint's ridiculous $350 on-contract price tag for the Note 3).
Again, thanks for everyone's help and input!
Click to expand...
Click to collapse
Just seen this... man that micmars always has the right answer...
Pillzbury if you're like me and hate when something doesn't work and want to know how and why...
You could have put the fl24 stock rom on the sdcard..
Then used mobile Odin and el29 direct boot kernel...once in el 29 recovery flash stock rom... should be good to go...
Glad you got it figured out anyway... like I said..micmars the man..
Sorry you won't be around in this forum... Good Luck...
Gil81 said:
Just seen this... man that micmars always has the right answer...
Pillzbury if you're like me and hate when something doesn't work and want to know how and why...
You could have put the fl24 stock rom on the sdcard..
Then used mobile Odin and el29 direct boot kernel...once in el 29 recovery flash stock rom... should be good to go...
Glad you got it figured out anyway... like I said..micmars the man..
Sorry you won't be around in this forum... Good Luck...
Click to expand...
Click to collapse
Ah, it DOES bother me when something doesn't work and I don't know why! Thanks for your answer.
The E4GT was a solid phone, but I will not miss having to flash back to a safe kernel when going between ROMs.
pillzbury said:
Ah, it DOES bother me when something doesn't work and I don't know why! Thanks for your answer.
The E4GT was a solid phone, but I will not miss having to flash back to a safe kernel when going between ROMs.
Click to expand...
Click to collapse
Yep... I have a 10.1 gtab and the recovery/kernel are seperate on it... it is kinda nice..
Good luck..