Related
...I downloaded the 4.0.4 update and went to install and reboot. But the phone got stuck at the screen with the android belly up and a exclamation point. Pulled the battery and rebooted and was at 4.0.2 still. Haven't gotten another OTA notification. Do I get another OTA alert or do I have to update manually.
I have a GSM Nexus, rooted but with stock 4.0.2. And I activated OTA RootKeeper before downloading the update. Any help will be greatly accepted.
Sent from my Galaxy Nexus using Tapatalk
Besides root and maybe unlock your bootloader, did you change anything in your system (install mods, different radio etc. or rename system files)? If you are not completely stock your OTA will not work and you will have to update manually or get back to Stock first.
Sent from my Galaxy Nexus using xda premium
Nothing changed. Except for root and unlocked bootloader everything is stock.
Sent from my Galaxy Nexus using Tapatalk
Well the screen you were looking at (Android belly up) is the stock recovery. If you see that: no need to pull battery. Simply push volume up + power simultaneously and you'll get into the recovery menu. Scrolling through the options can be done with the volume buttons, select with the power button.
That said: I think no one knows for sure but I myself would not wait and update myself. There are a lot of guides here on how to do that and if you flash the stock images you will have the same as anyone who had the OTA. Make a proper backup first (you allways should)! You will lose all your data if you have to unlock your bootloader.
Sent from my Galaxy Nexus using xda premium
jrodsep said:
Nothing changed. Except for root and unlocked bootloader everything is stock.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Have you installed CWM recovery installed?
The "belly up" android is the phone trying to boot in the stock recovery to update the phone. But as you may have CWM recovery installed (which replaces the stock recovery) the phone cannot complete the update.
You will need to re-install the stock recovery. I believe you can do this with the GNex Toolkit.
Sent from my Galaxy Nexus
stuu.f said:
Have you installed CWM recovery installed?
The "belly up" android is the phone trying to boot in the stock recovery to update the phone. But as you may have CWM recovery installed (which replaces the stock recovery) the phone cannot complete the update.
You will need to re-install the stock recovery. I believe you can do this with the GNex Toolkit.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Is it possible to get the Stock Recovery Screen when you have CWM installed? Didn't think that was possible... that it would just boot into CWM recovery. That is why I didn't mention it (trying to learn here).
Same problem here. Stock 4.0.2, rooted, CWM installed.
Does this mean we will lose settings before we are able to update the device?
Lex_Michdeandroid said:
Same problem here. Stock 4.0.2, rooted, CWM installed.
Does this mean we will lose settings before we are able to update the device?
Click to expand...
Click to collapse
this mean you are not eligible for the OTA update mate, because you have a custom recovery
i suggest you to
flash the stock rom manually
flash a custom rom wih 4.04 inside
my 2 cents
Viridis Draco said:
this mean you are not eligible for the OTA update mate, because you have a custom recovery
i suggest you to
flash the stock rom manually
flash a custom rom wih 4.04 inside
my 2 cents
Click to expand...
Click to collapse
I don't even understand why I have CWM installed in the first place. I only neet root acces, all the rest can stay stock for all I care... Is there a way to avoid these problems in the future? So be able to root and OTA at the same time?
Sent from my Transformer TF101 using XDA
Lex_Michdeandroid said:
I don't even understand why I have CWM installed in the first place. I only neet root acces, all the rest can stay stock for all I care... Is there a way to avoid these problems in the future? So be able to root and OTA at the same time?
Sent from my Transformer TF101 using XDA
Click to expand...
Click to collapse
custom recovery is needed in order to install custom ROM dude, is quite simple
and yes, you can root the stock ROM without custom recovery, there are a lot of guide about that in the developer section
Viridis Draco said:
custom recovery is needed in order to install custom ROM dude, is quite simple
and yes, you can root the stock ROM without custom recovery, there are a lot of guide about that in the developer section
Click to expand...
Click to collapse
So my only option to fix this now is flash 4.0.4 manually (will I lose stuff?) and then root again and get stock recovery back? Sorry for my n00b questions, thanks for your help!
Edit: would it be easier if I just get the stock recovery back and then try to get the OTA to turn up again?
Sent from my Transformer TF101 using XDA
Lex_Michdeandroid said:
So my only option to fix this now is flash 4.0.4 manually (will I lose stuff?) and then root again and get stock recovery back? Sorry for my n00b questions, thanks for your help!
Sent from my Transformer TF101 using XDA
Click to expand...
Click to collapse
you have nothing broken mate, i can't tell you if you will lose data, it depend on your ROM, what you flash and mainly how
the Force and the Developer Section is with you, young padawan
damn, i'm playing SW:TOR too much:/
Viridis Draco said:
you have nothing broken mate, i can't tell you if you will lose data, it depend on your ROM, what you flash and mainly how
the Force and the Developer Section is with you, young padawan
damn, i'm playing SW:TOR too much:/
Click to expand...
Click to collapse
Thank you master for your soothing words. I just want my Galaxy Nexus to be like he is right out of the box, but rooted. Thats all I need from him... I am guessing my girlfriends Nexus S is going to be a pain in my assholes in a few weeks bc its still on GB and my TF101 will also go haywire because of my rooting adventures...
First this GN nuisance... Guess I am going to have to wait until tomorrow, I am flying to Dublin in about two hours and I don't think I can fix this in time...
Sent from my Transformer TF101 using XDA
Lex_Michdeandroid said:
Thank you master for your soothing words. I just want my Galaxy Nexus to be like he is right out of the box, but rooted. Thats all I need from him... I am guessing my girlfriends Nexus S is going to be a pain in my assholes in a few weeks bc its still on GB and my TF101 will also go haywire because of my rooting adventures...
First this GN nuisance... Guess I am going to have to wait until tomorrow, I am flying to Dublin in about two hours and I don't think I can fix this in time...
Sent from my Transformer TF101 using XDA
Click to expand...
Click to collapse
i agree, take your time and you wouldn't regret it
I want to manually flash 4.0.4 and stay unrooted. Should I use the GNex Toolkit to flash 4.0.4 directly or do I need to flash the same version I have on my phone?
Sent from my Galaxy Nexus using Tapatalk
I had the same issue described by the OP, the belly up android when trying to update to 4.0.4 from the OTA notification. I had previously changed to 4.0.2 yakju using efrant's instructions from the first post in this thread: http://forum.xda-developers.com/showthread.php?t=1391881
However, I had skipped the optional sections. In particular step 12 to flash the recovery partition. I went back and just executed step 12 (fastboot flash recovery recovery.img) and rebooted. Then I was able to update to 4.0.4 successfully from the OTA notification.
I'm guessing I didn't have the "stock recovery" because I previously had the default Samsung version?
Just got the update again OTA, and again the belly up droid. I'm really pissed now, bc it also reset my Go launcher... Had 7 screens w/ widgets and shortcuts...
Why did it go wrong again? I thought I put back the recovery to stock to solve the OTA problem... Should I do other things? The phone starts to really slow down and I'm ready to toss this piece of c* in the bin...
Sent from my Galaxy Nexus using XDA
Lex_Michdeandroid said:
Just got the update again OTA, and again the belly up droid. I'm really pissed now, bc it also reset my Go launcher... Had 7 screens w/ widgets and shortcuts...
Why did it go wrong again? I thought I put back the recovery to stock to solve the OTA problem... Should I do other things? The phone starts to really slow down and I'm ready to toss this piece of c* in the bin...
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I had the same issue just now with my phone (unlocked, rooted, stock revcovery), but a quick reboot allowed the update to complete and I'm now on 4.0.4. Did you check the version number again after this latest attempt?
Yes, still 4.0.2.
And of course, my phone says I'm up to date. Lovely, NAAAAAT!
Sent from my Galaxy Nexus using XDA
just want to let you know that T-Mobile firmware is ready for download
http://samsung-updates.com/device/?id=SGH-T999
Is this for odin
Sent from my SGH-T999 using Tapatalk 2
Can this be used with the t mobile variant
Sent from my SGH-T999 using Tapatalk 2
If this is for sprint, why does the title say T-Mobile..
Sent from my HTC One X using xda premium
Edit: In that case, thanks PP
Sent from my SGH-T999 using xda premium
Its for T Mobile.. if you click on the link it says its for the T999
I was wondering the same thing, but if it matters I went to the link and it says it's for T-Mobile T999UVALEM like the title
Sent from my SGH-T999 using xda app-developers app
Tweezydak1d said:
Is this for odin
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
yes it is - same firmware as you would get updting with kies
anthonykash said:
Can this be used with the t mobile variant
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
ye, it is tmobile version i am tired and made a typo - corrected thnks and gnite
my phone came with this firmware. is this just posted to revert to stock if on a custom rom or is there other significance?
Has anyone tried flashing yet?
Sent from my SGH-T999 using xda app-developers app
So this must mean we can flash fash back to stock with odin if we have problems.
yup! this is our fall back ROM. now we need a triangle away to reset the counter!
It Works
I decided to be the test monkey on this one.
I had a nandroid backup of when I screwed my system so badly it just boot looped repeatedly. Restored that with cwm, verified it was still hosed, unpacked this zip, used odin to burn the .tar.md5 to the phone as PDA, rebooted.
It does some gear chunking while booting the first time then reboots - don't panic yet! On second boot it does some more rebuilding, then 'WELCOME!'
Bonus: CWM now sees the actual external sdcard as /sdcard and can find things like roms and backups on it. Edit: This CWM finds .zips on the sdcard, but doesn't seem to know how to backup/restore.
So is this for un rooting our phones?
Sent from my SGH-T999 using xda premium
sizer99 said:
I decided to be the test monkey on this one.
I had a nandroid backup of when I screwed my system so badly it just boot looped repeatedly. Restored that with cwm, verified it was still hosed, unpacked this zip, used odin to burn the .tar.md5 to the phone as PDA, rebooted.
It does some gear chunking while booting the first time then reboots - don't panic yet! On second boot it does some more rebuilding, then 'WELCOME!'
Bonus: CWM now sees the actual external sdcard as /sdcard and can find things like roms and backups on it. Edit: This CWM finds .zips on the sdcard, but doesn't seem to know how to backup/restore.
Click to expand...
Click to collapse
What do you mean "This CWM" ? The tars we're talking about in this thread are completely stock from samsung, there is no CWM in these... please elaborate.
hiazn said:
What do you mean "This CWM" ? The tars we're talking about in this thread are completely stock from samsung, there is no CWM in these... please elaborate.
Click to expand...
Click to collapse
After burning this with Odin I ended up with a CWM that I didn't expect - and I've never seen one that actually recognized the external card. However, with all the things I've been trying it's quite possible I ended up burning a boot image I forgot about. I need to try reburning this and see if anything changes, but can't do it right now.
sizer99 said:
After burning this with Odin I ended up with a CWM that I didn't expect - and I've never seen one that actually recognized the external card. However, with all the things I've been trying it's quite possible I ended up burning a boot image I forgot about. I need to try reburning this and see if anything changes, but can't do it right now.
Click to expand...
Click to collapse
Sounds like a plan, let us know what you find.
is this actually
T999UVALEM
or
T999UVLEM
M9x3mos said:
is this actually
T999UVALEM
or
T999UVLEM
Click to expand...
Click to collapse
Mine stock is T999UVLEM, whats the difference between the two?
does this restore everything, including stock recovery, but resetting the counter?
Strange - I had kind of a weird experience with this. I flashed via Odin as usual (as I've done a 100x before) and when it rebooted, it still had remnants of the previous rom I had installed. I didn't get the "welcome" screen as if I was starting from a new factory rom. but at least it got me back to step 1 and I could flash the Lean 2.1 rom again to repair my screw ups.
Ok so I got the GSM version today, I was using this http://www.youtube.com/watch?v=oSmd9ZbUH50&feature=player_embedded to help me unlock the bootloader, flash CWM, and flash the SU files. I unlocked the bootloader without a problem, just It did not delete all my data like the video said.
Once I try flashing CWM and looks like its fine, but after reboot when trying to boot into recovery, I get the Red Triangle with exclamation mark. I have tried flashing it a couple times, it still does the same thing. Can anyone help me please?
I just got mine today also, did you rename the stock recovery image before flashing cwm? I renamed it after and had the same issue so I reflashed cwm and all is good.
Sent from my SGH-T959V using xda premium
try using this tool http://forum.xda-developers.com/showthread.php?t=1400871
1) Play Store devices do NOT wipe when unlocking the bootloader. (We are still trying to figure out why.)
2) The Android with the red "!" IS the stock recovery. There are two files in you /system that reflash the stock recovery on every boot. If you want you custom recovery to stick, you need to delete/rename one or both:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
Sent from my Galaxy Nexus using Tapatalk 2
I didn't rename anything, just exactly how the guy in youtube has it. :crying: Do you have to flash a custom recovery after every reboot? even with the toolkit after i reboot, i get the red triangle.
manuelsavino said:
I didn't rename anything, just exactly how the guy in youtube has it. :crying: Do you have to flash a custom recovery after every reboot? even with the toolkit after i reboot, i get the red triangle.
Click to expand...
Click to collapse
Did you not read what I wrote? You NEED to rename one of those files for CWM to stay installed.
Sent from my Galaxy Nexus using Tapatalk 2
So pretty much without rebooting, I flash custom recovery, root, then rename those two files. correct?
manuelsavino said:
So pretty much without rebooting, I flash custom recovery, root, then rename those two files. correct?
Click to expand...
Click to collapse
Yup. Or if you reboot before renaming the files, just reflash cwm again once you delete then. No big deal.
Sent from my Galaxy Nexus using Tapatalk 2
Ok. Thank you all! I will report back once I do it!
manuelsavino said:
Ok. Thank you all! I will report back once I do it!
Click to expand...
Click to collapse
This would have taken less than 5 minutes with the V7 Toolkit- boot loader unlock, root, rename recovery file, and install CWM/TWRP.
It is good that your trying other methods, though.
Sent from my Galaxy Nexus
bhowanidin said:
This would have taken less than 5 minutes with the V7 Toolkit
Click to expand...
Click to collapse
If he did it using a toolkit as you suggested, we would have learned nothing.
Sent from my Galaxy Nexus using Tapatalk 2
Mate I had the same problem. I got my device yesterday and unlocked my device with the tool Galaxy Nexus Root Toolkit v1.4. But it didn't allow me to root it. As I had ADB installed I tried to flash recovery trough it. But still no success. Here's how I did it.
Download Galaxy Nexus Root Toolkit v1.4. Enter the advanced settings.
Transfer su.zip to your internal memory and then "Boot into Temp CWM" trough that tool. Then you can root your device. Once it's rooted, download "ROM Manager" from the market. Accept the permissions it's asking for. And flash CWM recovery from it.
And voila. It worked for me.
Why did you use version 1.4 when you could use V7 which does all that for you in one click.
Ran into this version in a video I watched. So I just downloaded it.
Oh right you should check the development section for the newer version it is far more simple & self explanatory.
I'm done with rooting and unlocking. I did it already. Just explained how above.
No need for a tool no more.
Its useful if you want to relock your phone and go back to stock
replied..
ste1164 said:
Why did you use version 1.4 when you could use V7 which does all that for you in one click.
Click to expand...
Click to collapse
I'm guessing it just worked for him..:good:
If it anit broke why try to fix it
Ended up using the toolkit. One question, the two files that need to be renamed/deleted so it wont go back to stock recovery, on the toolkit it says rename, though once i go on root explorer to see if the two files are still there, they disappeared. So if I ever wanted to go back to stock recovery for any reason, are those two files available anywhere? Or is there a stock recovery image?
Hello everyone!
Im not sure if this post belongs in this thread, but I thought it would be best suited in the Sprint Galaxy Nexus thread.
Can someone please make a stock 4.3 rooted rom for the Sprint Galaxy Nexus? Or, if someone has already received the update, could you post a nand backup?
I want to update, but I dont want to lose root. However, If there isn't any other solution, I will definitely take the plunge
Sent from my Galaxy Nexus using Tapatalk 2
vincentallen2 said:
Hello everyone!
Im not sure if this post belongs in this thread, but I thought it would be best suited in the Sprint Galaxy Nexus thread.
Can someone please make a stock 4.3 rooted rom for the Sprint Galaxy Nexus? Or, if someone has already received the update, could you post a nand backup?
I want to update, but I dont want to lose root. However, If there isn't any other solution, I will definitely take the plunge
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
what's funny is that there is a 155mb zip out there, but no one has seen a actual update rollout even start yet like sprint said it was doing yesterday, and shockingly no one has used that 155mb zip to even do this yet, lol.
tomh1979 said:
what's funny is that there is a 155mb zip out there, but no one has seen a actual update rollout even start yet like sprint said it was doing yesterday, and shockingly no one has used that 155mb zip to even do this yet, lol.
Click to expand...
Click to collapse
Ive downloaded that yesterday, but just like QBKing said, itd probably be better to wait for a stock rooted option. I think it would be just less of a hassle than to go through all the motions of unrooting and updating.
Sent from my Galaxy Nexus using Tapatalk 2
tomh1979 said:
what's funny is that there is a 155mb zip out there, but no one has seen a actual update rollout even start yet like sprint said it was doing yesterday, and shockingly no one has used that 155mb zip to even do this yet, lol.
Click to expand...
Click to collapse
when I updated from 4.1 to 4.2.1, I had CWM, and I got the ota, with it prompting me to keep root and disable recovery flash. I actually have the zip on my phone, I'm just scared of what will happen if I try to flash it. I don't have access to a PC, so there's no way to recover if I f*ck up.
mattchew86 said:
when I updated from 4.1 to 4.2.1, I had CWM, and I got the ota, with it prompting me to keep root and disable recovery flash. I actually have the zip on my phone, I'm just scared of what will happen if I try to flash it. I don't have access to a PC, so there's no way to recover if I f*ck up.
Click to expand...
Click to collapse
Nandroid backup just in case.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
tomh1979 said:
what's funny is that there is a 155mb zip out there, but no one has seen a actual update rollout even start yet like sprint said it was doing yesterday, and shockingly no one has used that 155mb zip to even do this yet, lol.
Click to expand...
Click to collapse
If you're doubting the update don't, the OTA process involves sending the update 1 by 1 randomly so that everyone doesn't download the file at once and overload the download servers, causing bad downloads, and bricking devices and in the end you'll get unhappy customers.
Sent from my Galaxy Nexus using Tapatalk 4
Savoca said:
Nandroid backup just in case.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If he loses root or custom recovery how's he gonna restore ? I'm thinking of trying it as well . I've made a nandroid , just wondering if I'd be able to get it restored complete with root and custom recovery ? Thanks
Jimlarck said:
If you're doubting the update don't, the OTA process involves sending the update 1 by 1 randomly so that everyone doesn't download the file at once and overload the download servers, causing bad downloads, and bricking devices and in the end you'll get unhappy customers.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
I never said I was doubting, just surprised I haven't seen anyone saying they got it yet since it was supposed to start rolling out yesterday,
Sent from my Nexus 7 using Tapatalk 4
I actually flashed the 155 mb zip and rooted using nexus toolkit and all is well.
Sent from my Galaxy Nexus using xda app-developers app
Been running stock rooted all day today. I just used Odin to go back to 4.2.1 and used that zip Phandroid (I think it was them) renamed it update.zip put it in root of storage. Booted the phone and it said there was an update. Choose to reboot and it installed it. Then fastboot flashed twrp and flashed an su zip. Granted It wiped my phone but I just used helium to restore data on some of my apps and everything has been fine
Sent from my Galaxy Nexus using Tapatalk
MonstaDriva said:
If he loses root or custom recovery how's he gonna restore ? I'm thinking of trying it as well . I've made a nandroid , just wondering if I'd be able to get it restored complete with root and custom recovery ? Thanks
Click to expand...
Click to collapse
Tl;dr custom recovery stayed, root obtained by flashing supersu.
Last night I used fastboot to flash system user data radios and boot images from the 4.2.1 factory image. Flashed the 4.3 zip in twrp. Made a nandroid of stock, then flashed supersu zip. All is good
Sent from my Galaxy Nexus using Tapatalk
I tried flashing the zip in TWRP and it failed. Not sure why maybe a bad download.
Savoca said:
Nandroid backup just in case.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I went ahead and flashed it, in CWM, and everything is working great. Had to reflash Superuser, in this case, Koush's Superuser, and everything is fine.
mattchew86 said:
I went ahead and flashed it, in CWM, and everything is working great. Had to reflash Superuser, in this case, Koush's Superuser, and everything is fine.
Click to expand...
Click to collapse
I renamed the file update.zip and tried this, and no go, what am I doing wrong, could it be due to being on a 4.2.2 ROM?
Sent from my Nexus 7 using Tapatalk 4
I tried a fresh download using CWM this time and it still failed. What am I missing?
Sent from my Nexus 7 using XDA Premium 4 mobile app
tomh1979 said:
I renamed the file update.zip and tried this, and no go, what am I doing wrong, could it be due to being on a 4.2.2 ROM?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I went and restored a backup of Stock 4.2.1, and just flashed over that. No wiping or anything. Do you have a Stock backup?
mattchew86 said:
I went and restored a backup of Stock 4.2.1, and just flashed over that. No wiping or anything. Do you have a Stock backup?
Click to expand...
Click to collapse
Nope, any chance on flashing a stock rooted ROM perhaps.
Sent from my Nexus 7 using Tapatalk 4
tomh1979 said:
Nope, any chance on flashing a stock rooted ROM perhaps.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
You could try it. My Stock ROM was rooted, and I all I had to do was reflash my Superuser zip after I let it boot up once, just to make sure the update took properly.
http://forum.xda-developers.com/showthread.php?t=1419170
Download the file from the linked thread there for our device and then pick which instruction set applies to you from the second post in that thread. Since I'm leaving Sprint and giving my Gnex to my two year old, I unrooted, returned to stock, and locked the device. After following the directions for adb sideload, everything came up great.
X
Sent from my Galaxy Nexus using xda app-developers app
Well, I used a factory reset tool to reset my rom back to stock. However, when I try to do a system update, it goes all the way to the end and says Error. Note that I can get into my tablet before I launch the update, but afterwards it just boots into recovery and I have to hard reset and reset my device using the aforementioned factory reset tool. Basically all I want to know is if it has anything to do with me recovering from the tool, or are OTA's iffy? I bought the device yesterday and I love it. I rooted it, unlocked the bootloader, etc. So yes it is modified. However It is not in anyway bricked. I just want to know if it's possible to do an official OTA from System Update, or do I have to use the one provided on the Index of the Nexus 7 Flo forum? Thanks for any help. Like I said, It's not bricked, I'm not complaining. Just a few questions
SwiftLeeO said:
Well, I used a factory reset tool to reset my rom back to stock. However, when I try to do a system update, it goes all the way to the end and says Error. Note that I can get into my tablet before I launch the update, but afterwards it just boots into recovery and I have to hard reset and reset my device using the aforementioned factory reset tool. Basically all I want to know is if it has anything to do with me recovering from the tool, or are OTA's iffy? I bought the device yesterday and I love it. I rooted it, unlocked the bootloader, etc. So yes it is modified. However It is not in anyway bricked. I just want to know if it's possible to do an official OTA from System Update, or do I have to use the one provided on the Index of the Nexus 7 Flo forum? Thanks for any help. Like I said, It's not bricked, I'm not complaining. Just a few questions
Click to expand...
Click to collapse
Well, without much detail about the error, it's hard to help. Are you just stock rooted with stock recovery? If so, you should be able to take an OTA no problem, although you'd lose root. But you can always flash supersu to get it back. Did you install a custom recovery to root? Or did you use a toolkit? Lots of questions. If you have a custom recovery, you'd have to fastboot flash the stock recovery from the factory image. If you still have the stock recovery and are just stock rooted, you've probably modified the system in some way. In that case, you can just fastboot flash the stock system image.
charesa39 said:
Well, without much detail about the error, it's hard to help. Are you just stock rooted with stock recovery? If so, you should be able to take an OTA no problem, although you'd lose root. But you can always flash supersu to get it back. Did you install a custom recovery to root? Or did you use a toolkit? Lots of questions. If you have a custom recovery, you'd have to fastboot flash the stock recovery from the factory image. If you still have the stock recovery and are just stock rooted, you've probably modified the system in some way. In that case, you can just fastboot flash the stock system image.
Click to expand...
Click to collapse
Stock Rooted with Stock Recovery. It downloads the OTA no issue, but when in download mode, it gets to the very end and says Error!. I used CFAutoRoot for rooting. I used fastboot to unlock the bootloader and install custom recovery.
SwiftLeeO said:
Stock Rooted with Stock Recovery. It downloads the OTA no issue, but when in download mode, it gets to the very end and says Error!. I used CFAutoRoot for rooting. I used fastboot to unlock the bootloader and install custom recovery.
Click to expand...
Click to collapse
Wait. So do you currently have stock recovery or a custom recovery?
Sent from my Nexus 5 using xda app-developers app
charesa39 said:
Wait. So do you currently have stock recovery or a custom recovery?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Exactly what I was wondering!
charesa39 said:
Wait. So do you currently have stock recovery or a custom recovery?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Stock.
SwiftLeeO said:
Stock.
Click to expand...
Click to collapse
Since you have stock recovery, there's probably an app that modified your system that's not allowing it to install the update because it detects a change in one of your system files. Fastboot flash the system image from the stock factory image. Then, it should update.
Sent from my Nexus 7 using xda app-developers app
charesa39 said:
Since you have stock recovery, there's probably an app that modified your system that's not allowing it to install the update because it detects a change in one of your system files. Fastboot flash the system image from the stock factory image. Then, it should update.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
You wouldn't happen to have one of those lying around would you? The img file I mean.
SwiftLeeO said:
You wouldn't happen to have one of those lying around would you? The img file I mean.
Click to expand...
Click to collapse
I'm assuming you're on 4.3 since you're trying to update? Either way, you can find the factory images here: https://developers.google.com/android/nexus/images.
Just download the the one for the version you're currently running on your N7. MAKE SURE YOU DOWNLOAD THE CORRECT ONE. Then, just extract the files from the tar.gz file. There's another zip file in that tar.gz file. Extract that one, and there's a system.img file. Fastboot flash it in the bootloader.
Sent from my Nexus 7 using xda app-developers app
charesa39 said:
I'm assuming you're on 4.3 since you're trying to update? Either way, you can find the factory images here: https://developers.google.com/android/nexus/images.
Just download the the one for the version you're currently running on your N7. MAKE SURE YOU DOWNLOAD THE CORRECT ONE. Then, just extract the files from the tar.gz file. There's another zip file in that tar.gz file. Extract that one, and there's a system.img file. Fastboot flash it in the bootloader.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help
SwiftLeeO said:
Thanks for the help
Click to expand...
Click to collapse
Anytime. :thumbup:
Sent from my Nexus 7 using xda app-developers app