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
Related
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?
Hi
My phone is rooted and I have the OTA update of JB 4.1 installed . Today i got an System Update from Google and when i clicked restart and install , my phone rebooted in recovery mode of ClockworkMod, then i saw that the update has failed .
I restarted my phone and when i saw that version it is 4.1 and when i selected check for update is says my phone is up to date ?
Please let me know how can i get the update from google now ?
Thanks
??
Manually flash the OTA in the release section. You have to be on stock everything (with the exception of root and an unlocked bootloader) for the OTA to succeed i.e. you will need to have a stock recovery which by seeing that you booted into CWR, you don't have. You can simply boot into CWR rather than flash it e.g. fastboot boot NAME_OF_RECOVERY.img
Unlawful said:
Manually flash the OTA in the release section. You have to be on stock everything (with the exception of root and an unlocked bootloader) for the OTA to succeed i.e. you will need to have a stock recovery which by seeing that you booted into CWR, you don't have. You can simply boot into CWR rather than flash it e.g. fastboot boot NAME_OF_RECOVERY.img
Click to expand...
Click to collapse
Thanks for your reply , can you please tell me how can i get the Stock Recovery ?
http://forum.xda-developers.com/showthread.php?t=1392310
Tapatalk 2 powered by Jelly Bean Nexus
innovat0r said:
Thanks for your reply , can you please tell me how can i get the Stock Recovery ?
Click to expand...
Click to collapse
thanks , now i am on JB 4.1.1
ohh crap
I have the same problem. I relly don't wanna lose all my data. Isn't there an easier way to do it?
Answer me plz: If i get the stock recovery am i going back to ICS?
Jpcsilva said:
I have the same problem. I relly don't wanna lose all my data. Isn't there an easier way to do it?
Answer me plz: If i get the stock recovery am i going back to ICS?
Click to expand...
Click to collapse
ive answered your problem here
http://forum.xda-developers.com/showthread.php?p=28871195#post28871195
Ok Im gonna try but just want some information: is my galaxy nexus going back to ICS? And am i gonna lose all my data?
Sent from my Galaxy Nexus using xda app-developers app
Jpcsilva said:
Ok Im gonna try but just want some information: is my galaxy nexus going back to ICS? And am i gonna lose all my data?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Relating to flashing the stock recovery? Well you have to be on ICS to update to JB...and assuming your bootloader is already unlocked, you shouldn't lose any data when flashing the stock recovery, radio or bootloader.
I am already on JB. I got via rom from here (xda). So i will need to go back to ics. Is that it?
Sent from my Galaxy Nexus using xda app-developers app
Can some one upload their recovery-from-boot.p file from galaxy nexus 4.1.1 stock
And before people start posting about using custom recovery bla bla bla I need it for future ota updates
Sent from my Galaxy Nexus using xda premium
Here's mine https://www.box.com/shared/gq7dpbilfufdejijb8oe
Sent from my Galaxy Nexus using Tapatalk 2
Be sure you don't edit your built.prop, or won't receive the ota too.
Beamed from my Grouper.
Thanks
Sent from my Galaxy Nexus using xda premium
My replacement phone didn't have the file. I thought that was strange when I rooted it.
Perhaps the manner of root you used had a script which deletes the file to have permanent custom recovery which is why it's not there.
Sent from my Galaxy Nexus using Tapatalk 2
blackt5 said:
My replacement phone didn't have the file. I thought that was strange when I rooted it.
Click to expand...
Click to collapse
I believe that file only appears if you've accepted an OTA. If the replacement was flashed to the latest image it wouldn't be there.
What if the Recovery-from-boot.p was there for a reason? Like to keep the phone stable. I always keep the stock recovery and boot the custom. Why would you need it all the time anyway??
patalo said:
What if the Recovery-from-boot.p was there for a reason? Like to keep the phone stable. I always keep the stock recovery and boot the custom. Why would you need it all the time anyway??
Click to expand...
Click to collapse
If i happen to mess with my phone on the go, i will have the means to unf*ck my phone if the unfortunate happens.
3rdstring said:
I believe that file only appears if you've accepted an OTA. If the replacement was flashed to the latest image it wouldn't be there.
Click to expand...
Click to collapse
Never thought of that. Thanks
Mach3.2 said:
If i happen to mess with my phone on the go, i will have the means to unf*ck my phone if the unfortunate happens.
Click to expand...
Click to collapse
HAHAHA Touche
Just for some clarification:
There are two files placed on your device when you upgrade via an OTA update. They are:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
These files are NOT part of the stock ROM.
The sole purpose of these files is to re-flash the stock recovery on every boot. So, every time you boot your device, those files flash the stock recovery. They do nothing else. The first file mentioned above is the script that flashes the second file, which is the stock recovery.
These files are not necessary for OTA updates to install on your device, as they are not part of the stock ROM.
So I was trying to flash a rom today and ended up soft bricking because the file was bad. Didn't get the chance to flash the new rom and already wiped data. The backup I did was also not working and I didn't have another rom to flash.
Now I am stuck on Samsung boot logo but I could still access download mode and CWM.
What should I do to fix this? Should I just flash to stock firmware and that would fix the issue? Or is there an easier way?
Basically I just need to push the new downloaded rom into sdcard but how do I do that when my phone wont even boot?
gahlaygai said:
So I was trying to flash a rom today and ended up soft bricking because the file was bad. Didn't get the chance to flash the new rom and already wiped data. The backup I did was also not working and I didn't have another rom to flash.
Now I am stuck on Samsung boot logo but I could still access download mode and CWM.
What should I do to fix this? Should I just flash to stock firmware and that would fix the issue? Or is there an easier way?
Basically I just need to push the new downloaded rom into sdcard but how do I do that when my phone wont even boot?
Click to expand...
Click to collapse
Odin back to stock or use an external SD card with the new ROM files.
Sent from my SGH-I747 using xda app-developers app
geoldr said:
Odin back to stock or use an external SD card with the new ROM files.
Click to expand...
Click to collapse
If you're reasonably competent with adb, you could also boot into recovery and upload a different ROM file to your phone with it.
smelenchuk said:
If you're reasonably competent with adb, you could also boot into recovery and upload a different ROM file to your phone with it.
Click to expand...
Click to collapse
Right, that's what I forgot to add.
geoldr said:
Odin back to stock or use an external SD card with the new ROM files.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks, that fixed the problem!
New question, sorry for being such a noob. I tried rooting using GS3 Snapdragon Toolkit to root but the problem now is that when after it reboots, the screen is black and there is only flashing blue LED. What am I doing wrong?
gahlaygai said:
Thanks, that fixed the problem!
New question, sorry for being such a noob. I tried rooting using GS3 Snapdragon Toolkit to root but the problem now is that when after it reboots, the screen is black and there is only flashing blue LED. What am I doing wrong?
Click to expand...
Click to collapse
Did you try to use the toolkit with a Jelly Bean stock? It explicitly can't do that.
Since you're using Odin anyway, you might try one of the pre-rooted stock images from this thread.
smelenchuk said:
Did you try to use the toolkit with a Jelly Bean stock? It explicitly can't do that.
Since you're using Odin anyway, you might try one of the pre-rooted stock images from this thread.
Click to expand...
Click to collapse
Yeah, that's exactly what happened. Will read entire instructions next time. Thanks for you help!
In an attempt to unroot and return to stock for 4.4 OTA I flashed stock firmware and unrooted my device in the process, so far so good.
I reboot my phone after to initiate the OTA but of course I can't download the OTA because my device status is still custom and without root I can't triangle away or do anything.
I'm still trying to figure out how to get root back onto my phone from my phone since I don't have access to a computer where I'm at. I'm basically just screwed and also stuck on MDL baseband with a MK2 build running 4.3 stock so I'm getting no downloads at all. XDA the app itself too 10min to download
Any insight would be greatly appreciated...I knew I should have just waited until I I had access to a pc but I jumped the gun of course. I've been looking around a lot and the only methods of rooting I've found require or use a pc.
Sent from my SGH-M919 using xda app-developers app
JORDVN said:
In an attempt to unroot and return to stock for 4.4 OTA I flashed stock firmware and unrooted my device in the process, so far so good.
I reboot my phone after to initiate the OTA but of course I can't download the OTA because my device status is still custom and without root I can't triangle away or do anything.
I'm still trying to figure out how to get root back onto my phone from my phone since I don't have access to a computer where I'm at. I'm basically just screwed and also stuck on MDL baseband with a MK2 build running 4.3 stock so I'm getting no downloads at all. XDA the app itself too 10min to download
Any insight would be greatly appreciated...I knew I should have just waited until I I had access to a pc but I jumped the gun of course. I've been looking around a lot and the only methods of rooting I've found require or use a pc.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
A stock firmware package makes the phone all stock. MDL baseband on an MK2 build means you didn't flash a stock firmware. Which 'stock' firmware did you flash?
As to root, did this 'stock' firmware also flash recovery? if it didn't you can download the recovery flashable supersu zip from chainfire's website into the phone and do it that way. Otherwise, I don't think there is a way to get root access from the OS itself, unless you find an exploit that grants su access so you can make system writable and push supersu.
qxps said:
A stock firmware package makes the phone all stock. MDL baseband on an MK2 build means you didn't flash a stock firmware. Which 'stock' firmware did you flash?
As to root, did this 'stock' firmware also flash recovery? if it didn't you can download the recovery flashable supersu zip from chainfire's website into the phone and do it that way. Otherwise, I don't think there is a way to get root access from the OS itself, unless you find an exploit that grants su access so you can make system writable and push supersu.
Click to expand...
Click to collapse
I'm can't remember where I got this firmware from but, it was from a thread within the general section which stated it was stock so I'm just unsure on that part. I will try to root using your information given. This did return to stock recovery as well but when I try to flash anything through it I get a signature verification failure. I've never had this happen where baseband and build didn't match after returning to a stock firmware. My guess is that I just used something I shouldn't have. Thanks for the help.
Sent from my SGH-M919 using xda app-developers app
After downloading the supersu and attempting to flash it through stock recovery, I'm still getting signature verification failure then the device reboots.
Sent from my SGH-M919 using xda app-developers app
JORDVN said:
After downloading the supersu and attempting to flash it through stock recovery, I'm still getting signature verification failure then the device reboots.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Unfortunately, rooting or installing custom recovery needs to be done through a computer. As of this moment, there are no root exploits that can be done via the phone itself. I'm sorry.
JORDVN said:
After downloading the supersu and attempting to flash it through stock recovery, I'm still getting signature verification failure then the device reboots.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
That's because you need a custom recovery, it's why I asked whether the firmware you flashed replaced recovery or not.
As vigz said, you need a computer to at least flash cf root with odin.
qxps said:
That's because you need a custom recovery, it's why I asked whether the firmware you flashed replaced recovery or not.
As vigz said, you need a computer to at least flash cf root with odin.
Click to expand...
Click to collapse
Okay I've pretty much come to that conclusion after continuously searching with no solid method. I'll just have to deal with the baseband problem for now until I get back home. Wifi toggle doesn't work at all either. Is that a baseband problem, correct?
Sent from my SGH-M919 using xda app-developers app
Vigz said:
Unfortunately, rooting or installing custom recovery needs to be done through a computer. As of this moment, there are no root exploits that can be done via the phone itself. I'm sorry.
Click to expand...
Click to collapse
Thanks for the insight, I'll have to make due with what I have for now
Sent from my SGH-M919 using xda app-developers app