I got the update and it is downloaded b/c I see it in the recovery mode. I scroll down to install update, but it will not work.
My phone is rooted, I have CWM, and it is unlocked. How can I get my update completed? I really want to keep stock right now. I don't want to keep checking up on updated ROM's , etc...
Thanks so much. Please - if you respond, break it down easy. step by step. That is what I need. Basics. thanks.
i<3myphone said:
I got the update and it is downloaded b/c I see it in the recovery mode. I scroll down to install update, but it will not work.
My phone is rooted, I have CWM, and it is unlocked. How can I get my update completed? I really want to keep stock right now. I don't want to keep checking up on updated ROM's , etc...
Thanks so much. Please - if you respond, break it down easy. step by step. That is what I need. Basics. thanks.
Click to expand...
Click to collapse
the update will only install with the stock recovery.
i<3myphone said:
I got the update and it is downloaded b/c I see it in the recovery mode. I scroll down to install update, but it will not work.
My phone is rooted, I have CWM, and it is unlocked. How can I get my update completed? I really want to keep stock right now. I don't want to keep checking up on updated ROM's , etc...
Thanks so much. Please - if you respond, break it down easy. step by step. That is what I need. Basics. thanks.
Click to expand...
Click to collapse
As far as my knowledge goes. You wont be able to install OTA's on rooted GN.
Edit
Answer was already given
Heppieboeddah said:
As far as my knowledge goes. You wont be able to install OTA's on rooted GN.
Edit
Answer was already given
Click to expand...
Click to collapse
It's CWM recovery that messes it up not root.
jhuynh said:
It's CWM recovery that messes it up not root.
Click to expand...
Click to collapse
Assumption is the mother of all **** ups...so i assumed that if you are rooted the most common thing is that you have CWM installed...
So how do I get there from here? Do I need to uninstall something and then do the update??
Thanks for the help.
i<3myphone said:
So how do I get there from here? Do I need to uninstall something and then do the update??
Thanks for the help.
Click to expand...
Click to collapse
you could fastboot the stock recovery in...but you might as well fastboot the latest images from google if you do that
ogdobber said:
you could fastboot the stock recovery in...but you might as well fastboot the latest images from google if you do that
Click to expand...
Click to collapse
Ok, I can try that. How do I do that? I am not sure I am familiar with fastboot. I can follow step by step instructions though.
Did you try the instructions on this thread?
http://forum.xda-developers.com/showthread.php?t=1419170&highlight=ota+update
You seem to have the same set up as I do. I've just updated no problem with method 1.
The only instruction missing is that you have to re-root afterwards (you can check with Titanium).
When re-rooting, it got stuck on the Google image. I disconnected from the computer and pulled the battery out. restarted and voilá, all done
ogdobber said:
the update will only install with the stock recovery.
Click to expand...
Click to collapse
Heppieboeddah said:
As far as my knowledge goes. You wont be able to install OTA's on rooted GN.
Edit
Answer was already given
Click to expand...
Click to collapse
jhuynh said:
It's CWM recovery that messes it up not root.
Click to expand...
Click to collapse
Heppieboeddah said:
Assumption is the mother of all **** ups...so i assumed that if you are rooted the most common thing is that you have CWM installed...
Click to expand...
Click to collapse
As I'm sure you all have read the post above this one, neither CWM nor root prevent you from receiving the OTA update. CWM, however, will prevent it from automatically installing, but CWM can easily install the OTA. See link in post above.
---------- Post added at 01:28 PM ---------- Previous post was at 01:21 PM ----------
ogdobber said:
you could fastboot the stock recovery in...but you might as well fastboot the latest images from google if you do that
Click to expand...
Click to collapse
Yes, but if you flash the latest images, you will lose all your data...
I tried doing it via CWM. It was aborted. I just went ahead and uploaded a ROM. The Android Revolution HD one. I kinda gave up trying to do the OTA myself. Thanks for hte help anyway.
efrant said:
As I'm sure you all have read the post above this one, neither CWM nor root prevent you from receiving the OTA update. CWM, however, will prevent it from automatically installing, but CWM can easily install the OTA. See link in post above.
---------- Post added at 01:28 PM ---------- Previous post was at 01:21 PM ----------
Yes, but if you flash the latest images, you will lose all your data...
Click to expand...
Click to collapse
Related
This morning I excitedly got a notification to update to 4.02. Installing update failed when phone rebooted to recovery and I got a red exclamation mark over the little Android.
My phone has been rooted with CMW installed. I know I lot of you will be thinking "just flash a different ROM" but the truth is I don't like any of the Roms currently available.
Did my update fail because of CWM? Or am I making a super noob mistake? Please help
Sent from my Galaxy Nexus using XDA App
wynthewun said:
This morning I excitedly got a notification to update to 4.02. Installing update failed when phone rebooted to recovery and I got a red exclamation mark over the little Android.
My phone has been rooted with CMW installed. I know I lot of you will be thinking "just flash a different ROM" but the truth is I don't like any of the Roms currently available.
Did my update fail because of CWM? Or am I making a super noob mistake? Please help
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
yes CWM will cause update to fail the install. Flash the stock recovery img through fastboot if you want OTA's
---------- Post added at 03:13 AM ---------- Previous post was at 03:05 AM ----------
download the stock system image files from google and extact it to find the recovery.img
- copy the recovery.img file to the directory that contains your fastboot utility
- start-up a terminal/command session
- put your phone into fastboot / bootloader mode
- type the following fastboot command to flash the stock recovery:
Code:
fastboot flash recovery recovery.img
badassirocz said:
yes CWM will cause update to fail the install. Flash the stock recovery img through fastboot if you want OTA's
---------- Post added at 03:13 AM ---------- Previous post was at 03:05 AM ----------
download the stock system image files from google and extact it to find the recovery.img
- copy the recovery.img file to the directory that contains your fastboot utility
- start-up a terminal/command session
- put your phone into fastboot / bootloader mode
- type the following fastboot command to flash the stock recovery:
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Thank you very much, i had the same problem this morning, the update disappeared so will it get back when i flash the recovery?
plus my launcher is modified will it affect the update?
it should come back if you check for updates in the system menu. If not it might take a few days to show back up from what I have heard. The launcher will not effect OTA's.
Please hit the thanks button if I helped
having this issue
I am having this issue also, but I didn't flash cwm into my phone, I only fastboot it, will this also cause this problem, or because I rooted my phone and on locked it, really need help.
thanks.
formula1210204 said:
I am having this issue also, but I didn't flash cwm into my phone, I only fastboot it, will this also cause this problem, or because I rooted my phone and on locked it, really need help.
thanks.
Click to expand...
Click to collapse
It won't work because you are rooted. The install looks for the stock bootloader. You don't have the stock bootloader because you rooted.
jd1001 said:
It won't work because you are rooted. The install looks for the stock bootloader. You don't have the stock bootloader because you rooted.
Click to expand...
Click to collapse
You are WRONG. Stop telling people wrong info. CWM is what caused the failure. Root doesn't mean you changed your bootloader.
jhuynh said:
You are WRONG. Stop telling people wrong info. CWM is what caused the failure. Root doesn't mean you changed your bootloader.
Click to expand...
Click to collapse
Yeah apologies! I got my wires crossed. Thanks for clearing it up for me. I wasn't sure if it was the bootloader or the custom recovery. Thanks again and sorry for misleading anyone.
reply
thanks for reply, but as I said, I didn't flash CWM into my phone, I just boot it, in this case, it will also making this problem?
So, to clear this up for noobs (like me!)
If I root my Nexus, but keep it all stock, will I still get OTA updates?
If so, will an OTA update remove the root?
Thanks
The update won't work because you will be using a different recovery when you root. So the update does not install at all.
However the benefits of rooting will allow you to have the latest Google updates thanks to the hard work of devs here. So root and get romming!!!
formula1210204 said:
thanks for reply, but as I said, I didn't flash CWM into my phone, I just boot it, in this case, it will also making this problem?
Click to expand...
Click to collapse
brypie said:
So, to clear this up for noobs (like me!)
If I root my Nexus, but keep it all stock, will I still get OTA updates?
If so, will an OTA update remove the root?
Thanks
Click to expand...
Click to collapse
If you just root the Phone and keep it complete stock (including Stock recovery, so not CWM) then OTA should work. I'm not sure about removing root though but I guess the OTA would not remove root. And if it does: It is easy to re-root isn't it?
The OTA should work if you didn't install CWM recovery or something like flashing a different radio. It removes root but you can easily re-root. I have not received 4.0.2 yet but when I received the volume fix update OTA I did not have any issues with it even though I was rooted. I just had to re-root after the update.
I am new with rooting my phone. I have used Rooted phones before, I followed http://forum.xda-developers.com/showthread.php?t=2258633 Motochopper how to. I ran into a problem. I click the superuser app that was installed onto my phone, and it tells me that "The Superuser binary (su) must be updated. Please choose an installation method. Recovery mode installation is recommended for HTC devices." I click install and it tells me there was an error. I would like to root my phone along with potentially installing CWM so that I can easily install Cyanogenmod when they release a stable verison for the S4. Also would love to install titanium backup along with some Adfree apps.
Any help would be very much appreciated.
OK, so it looks like you already have it rooted.
When super SU asks that question, dont install via CWM, tell it to just install normally.
Once you have SuperSU working, Download Rom Manager from the play store and install CWM Recovery right from within the ROM Manager app.
It will give you the option to pick between two types of CWM(ClockWorkMod). The Touch version, like its name gives you the ability to use the touch screen and not only the volume up/down + Power button.
Telling it to install normally causes it to just tell me there was an error, it also tells me it is out of date as well. Titanium Backup tells me that it cant get root access and I was never asked about it.
OK, so your phone is not rooted then.
Your going to have to try rooting it again or flashing an already rooted rom with Odin.
I just tried it again, this time it said failure after the install of the superuser.apk. I just read that one of the later updates by samsung can make it harder to root. I just got my phone and i was fully updated. What Roms, are already rooted for the S4. I am actually enjoying some of the default apps that came with the phone.
Wicked (and most ROMs that don't include the [STOCK] tag) are pre-rooted...but you'll need to ODIN a custom recovery first then flash the ROM.
If you want to stay on rooted stock, follow the steps in the "root May 7 MDL" thread to ODIN a rooted kernel, and you'll be good to go.
(You don't need root access to get a custom recovery flashed)
Basically, any of your options are pretty straightforward, but they're going to involve Odin-ing stuff.
So there isn't really a way to just root my phone without installing a custom rom?
There was before the second update, with the second update rooting got just a little bit more steps
Sent from my SGH-M919 using xda premium
movieaddict said:
There was before the second update, with the second update rooting got just a little bit more steps
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
So is there a way to keep it stock but root it? What are the other steps I would have to take. Why does Samsung not like people rooting their phones, I thought carriers were the ones that hated people rooting their phones
Spud37 said:
So is there a way to keep it stock but root it? What are the other steps I would have to take. Why does Samsung not like people rooting their phones, I thought carriers were the ones that hated people rooting their phones
Click to expand...
Click to collapse
Are you still on the MDB firmware or have you done any over the air updates? Specifically the May 7 update which is MDL. Motochopper is specifically for then older firmware (MDB) and it won't work if you are already on the updated. MDL firmware. In which case you would have to follow these instructions to acquire root.
http://forum.xda-developers.com/showthread.php?p=41162041
I usually use a market app called root checker to quickly check if I do have root.
And yes you can be rooted on stock.
Sent from my SGH-M919
lazaro17 said:
Are you still on the MDB firmware or have you done any over the air updates? Specifically the May 7 update which is MDL. Motochopper is specifically for then older firmware (MDB) and it won't work if you are already on the updated. MDL firmware. In which case you would have to follow these instructions to acquire root.
http://forum.xda-developers.com/showthread.php?p=41162041
I usually use a market app called root checker to quickly check if I do have root.
And yes you can be rooted on stock.
Sent from my SGH-M919
Click to expand...
Click to collapse
Root checker says no root. I believe it does have that over the air update installed. T Mobile updated it when they gave me the phone, because they thought I didn't really know anything about phones. I assume this means I have to follow another method to root my phone?
If you have the MDL update you have to root using the steps listed here:
http://forum.xda-developers.com/showthread.php?t=2268880
Easily done, just a few more steps.
ronin4740 said:
If you have the MDL update you have to root using the steps listed here:
http://forum.xda-developers.com/showthread.php?t=2268880
Easily done, just a few more steps.
Click to expand...
Click to collapse
This is going to sound like a dumb question but from reading all of that I need to use ODIN to install the ROOT_M919?UVUAMDL onto the phone? that should root the phone and allow me to install ROM Manager and install CWM from there right?
Also would doing this delete everything I have on my phone right now?
Spud37 said:
This is going to sound like a dumb question but from reading all of that I need to use ODIN to install the ROOT_M919?UVUAMDL onto the phone? that should root the phone and allow me to install ROM Manager and install CWM from there right?
Also would doing this delete everything I have on my phone right now?
Click to expand...
Click to collapse
No, you use Odin to install one of the recoveries. You use the recovery to install the zip ROOT_M919?UVUAMD. Personally I didn't use that file. I installed the kernel in recovery and SuperSU in recovery. And no, it won't delete things on your phone.
Atmazzz said:
No, you use Odin to install one of the recoveries. You use the recovery to install the zip ROOT_M919?UVUAMD. Personally I didn't use that file. I installed the kernel in recovery and SuperSU in recovery. And no, it won't delete things on your phone.
Click to expand...
Click to collapse
Thank you so much, I am about to go and do this. I will use the kernel you suggested since that looks like a better option, after flashing the kernal should i reboot and just use it normally for a bit and then go to recovery and flash SuperSU?
EDIT: The steps on the thread for ODIN are for installing a rooted ROM, I am assuming its still the same steps for installing a recovery instead of a rooted ROM
Spud37 said:
after flashing the kernal should i reboot and just use it normally for a bit and then go to recovery and flash SuperSU?
Click to expand...
Click to collapse
If I remember right I just flashed them both at the same time. Just make sure you do the kernel first.
---------- Post added at 02:01 PM ---------- Previous post was at 01:59 PM ----------
Spud37 said:
EDIT: The steps on the thread for ODIN are for installing a rooted ROM, I am assuming its still the same steps for installing a recovery instead of a rooted ROM
Click to expand...
Click to collapse
The steps for Odin are for the stock rom, but yes, you use it the same way for a recovery.
Atmazzz said:
If I remember right I just flashed them both at the same time. Just make sure you do the kernel first.
---------- Post added at 02:01 PM ---------- Previous post was at 01:59 PM ----------
The steps for Odin are for the stock rom, but yes, you use it the same way for a recovery.
Click to expand...
Click to collapse
Okay I didn't get any error using ODIN, however when I try and boot into CWM using Volume Up + Power it just goes to android recovery. Which doesn't have any of the options I need. Am I just booting up the wrong way, or did I do something wrong. I tried both the touch version and the non-touch version
Spud37 said:
Okay I didn't get any error using ODIN, however when I try and boot into CWM using Volume Up + Power it just goes to android recovery. Which doesn't have any of the options I need. Am I just booting up the wrong way, or did I do something wrong. I tried both the touch version and the non-touch version
Click to expand...
Click to collapse
2 options. uncheck auto reboot in Odin. When Odin is done, unplug your phone, pull your battery, then boot into recovery. Or .. when Odin is done and it reboots your phone, keep holding volume up to get to recovery.
Atmazzz said:
2 options. uncheck auto reboot in Odin. When Odin is done, unplug your phone, pull your battery, then boot into recovery. Or .. when Odin is done and it reboots your phone, keep holding volume up to get to recovery.
Click to expand...
Click to collapse
Thank You so much. However it now seems like I have both Super User and SuperSU installed.
How did you root? Did you install the ROOT_M919?UVUAMDL zip and install SuperSU?
Sorry if i don't understand whats going on this is the first time rooting for me.
I have a SGH-I747
4.3
I am trying to root my phone to be able to run 4.4 on it and have followed the steps here http://forum.xda-developers.com/showthread.php?t=1963790 but once i get back to my home page and try to use superSU I get an error message stating "Unfortunately, SuperSU has stopped." along with "Security information" "An application attempted to access system on your device without authorization. This attempt has been blocked".
Sorry if this is an easy fix or i left out important information but i would just like some help getting off the gound
woerner said:
Sorry if i don't understand whats going on this is the first time rooting for me.
I have a SGH-I747
4.3
I am trying to root my phone to be able to run 4.4 on it and have followed the steps here http://forum.xda-developers.com/showthread.php?t=1963790 but once i get back to my home page and try to use superSU I get an error message stating "Unfortunately, SuperSU has stopped." along with "Security information" "An application attempted to access system on your device without authorization. This attempt has been blocked".
Sorry if this is an easy fix or i left out important information but i would just like some help getting off the gound
Click to expand...
Click to collapse
Rooting the SG3 running stock 4.3 is notoriously difficult. CF AutoRoot may not always work. The instructions below (thanks to XDA Developer upndwn4par), however, works pretty well. The usual disclaimers ... you are trying this at your own risk etc. apply here...
(http://forum.xda-developers.com/showthread.php?t=2538991)
Before rooting your phone, however, please check to see if rooting is really necessary. You may not need root access to install a custom or stock ROM. Custom recovery (e.g. CWM or TWRP) alone may be sufficient.
---------- Post added at 09:43 PM ---------- Previous post was at 09:27 PM ----------
Larry2999 said:
Rooting the SG3 running stock 4.3 is notoriously difficult. CF AutoRoot may not always work. The instructions below (thanks to XDA Developer upndwn4par), however, works pretty well. The usual disclaimers ... you are trying this at your own risk etc. apply here...
(http://forum.xda-developers.com/showthread.php?t=2538991)
Before rooting your phone, however, please check to see if rooting is really necessary. You may not need root access to install a custom or stock ROM. Custom recovery (e.g. CWM or TWRP) alone may be sufficient.
Click to expand...
Click to collapse
I presume also you are trying to install a 4.4 based custom ROM since KitKat is not officially available for the i747?
Larry2999 said:
Rooting the SG3 running stock 4.3 is notoriously difficult. CF AutoRoot may not always work. The instructions below (thanks to XDA Developer upndwn4par), however, works pretty well. The usual disclaimers ... you are trying this at your own risk etc. apply here...
(http://forum.xda-developers.com/showthread.php?t=2538991)
Before rooting your phone, however, please check to see if rooting is really necessary. You may not need root access to install a custom or stock ROM. Custom recovery (e.g. CWM or TWRP) alone may be sufficient.
---------- Post added at 09:43 PM ---------- Previous post was at 09:27 PM ----------
I presume also you are trying to install a 4.4 based custom ROM since KitKat is not officially available for the i747?
Click to expand...
Click to collapse
Yes right now the end result is to try and install KitKat i was looking into http://forum.xda-developers.com/showthread.php?t=2556839 but am having troubles with the rooting part let alone trying to flash a ROM for the first time
Thanks for anything!
woerner said:
Yes right now the end result is to try and install KitKat i was looking into http://forum.xda-developers.com/showthread.php?t=2556839 but am having troubles with the rooting part let alone trying to flash a ROM for the first time
Thanks for anything!
Click to expand...
Click to collapse
so i think that my phone is rooted and i am trying to flash the ROM but the Error i am getting is...
set_metadata_recusive: some changes failed
E: Error executing updater binary in zip '.extern
Error flashing zip '/external_sd/Gummy-M. 1-02-27
woerner said:
so i think that my phone is rooted and i am trying to flash the ROM but the Error i am getting is...
set_metadata_recusive: some changes failed
E: Error executing updater binary in zip '.extern
Error flashing zip '/external_sd/Gummy-M. 1-02-27
Click to expand...
Click to collapse
Well i think i "Soft Bricked" my phone. currently stuck in a reboot loop but can still boot into recovery and download but nothing seams to be able to get me out of this loop
woerner said:
Well i think i "Soft Bricked" my phone. currently stuck in a reboot loop but can still boot into recovery and download but nothing seams to be able to get me out of this loop
Click to expand...
Click to collapse
Since you can get to download mode the best thing may be to restore stock 4.3. Check out this thread
AT&T I747 UCUEMJB Stock Restore
dawgdoc said:
Since you can get to download mode the best thing may be to restore stock 4.3. Check out this thread
AT&T I747 UCUEMJB Stock Restore
Click to expand...
Click to collapse
Thanks for all this help any being patient with me ill try and restore back to stock and read up somemore
dawgdoc said:
Since you can get to download mode the best thing may be to restore stock 4.3. Check out this thread
AT&T I747 UCUEMJB Stock Restore
Click to expand...
Click to collapse
Tried to use this and when i swipe to confirm flash, it will freeze for 3 sec. and then show the blue teamwin page and then go right back to the twrp home page
will try more in after work tomorrow...
This is exactly whats happening to me! gah!
Exact same errors, my question is, i can get a custom recovery, i can root, but i cant for the life of me, flash any roms.
woerner said:
Tried to use this and when i swipe to confirm flash, it will freeze for 3 sec. and then show the blue teamwin page and then go right back to the twrp home page
will try more in after work tomorrow...
Click to expand...
Click to collapse
Jewyou said:
This is exactly whats happening to me! gah!
Exact same errors, my question is, i can get a custom recovery, i can root, but i cant for the life of me, flash any roms.
Click to expand...
Click to collapse
Have you removed Knox before attempting to flash the custom ROM?
Other than that I don't have a suggestion, mostly because I have never used TWRP.
dawgdoc said:
Have you removed Knox before attempting to flash the custom ROM?
Other than that I don't have a suggestion, mostly because I have never used TWRP.
Click to expand...
Click to collapse
I personally have tried both http://forum.xda-developers.com/showthread.php?t=1963790 And http://forum.xda-developers.com/showthread.php?t=2538991
Both have gotten me to Root, but still unavailable to install roms
yes i have removed Knox several times with still failing.
Jewyou said:
This is exactly whats happening to me! gah!
Exact same errors, my question is, i can get a custom recovery, i can root, but i cant for the life of me, flash any roms.
Click to expand...
Click to collapse
I was able to get it to work by using philztouch instead of TWRP try using that hope this helps!
Alright so here is the story.
Earlier this week, wanting lolipop since i still didnt get it and i thought i will get it with next OTA which is in august, i decide to root the phone.
All goes fine untill i get to S-Off-ing the phone which you cant do without 25$.
I decide to leave it at that till i have 25$ at hand.
Yesterday lolipop OTA pops up, so without anything flashed yet i thought it would install but it just restarted into recovery.
Then i go with unrooting it.
Followed some guide all went well but when i needed to flash superuser uninstall, it didnt uninstall(in twrp it said it was successful).
Then i flashed stock recovery and relocked bootloader with superuser still installed.
Only then i discovered that superuser is still there, and when i tried installing update it restarted into fastboot.
Today i was reading something and found out about supersu. I got it and it uninstalled superuser and root checker said phone is not rooted correctly but update still did the same thing.
What to do now? I cant even factory reset. Also tried uninstalling root from supersu settings, didnt work. Also cant acess twrp and a few times i tried unlocking bootloader but it didnt work.
Restore your stock rom. The one you made before rooting and tampering with it. Flash the stock recovery and ota up.
No need to relock the bootloader, not needed for ota !
I didnt make stock rom backup.... I do have nandroid thought(with superuser installed).
I assume there are stock roms here on xda, but if i find it how do i flash it exactly?
SynoX4 said:
I didnt make stock rom backup.... I do have nandroid thought(with superuser installed).
I assume there are stock roms here on xda, but if i find it how do i flash it exactly?
Click to expand...
Click to collapse
Do you have twrp recovery?
No,, i flashed stock recovery. Maybe its still there somewhere but when i go to hboot and go to recovery it starts that screen with htc and red letters at bottom, but just reboots into hboot/fastboot, cant remember.
I tried unlocking bootloader again so i can get twrp again but it didnt work, i tried it 2-3 times. Gonna try it again in a bit.
Bit of searching would get ya loads of info !
http://forum.xda-developers.com/showthread.php?t=2701376
Mr Hofs said:
Bit of searching would get ya loads of info !
http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
Yes i know about this,where you think i got stock recovery
obtained said:
Do you have twrp recovery?
Click to expand...
Click to collapse
I got twrp installed somehow,i need to get stock rom now,but thing is from the link above there isnt my version. My version starts with 3.33 and cid is HTC__032,but closest to it with that cid is 3.32. Should i flash that version?
Edit:
Just noticed factory reset in twrp menu. Would that allow me to update?
SynoX4 said:
Just noticed factory reset in twrp menu. Would that allow me to update?
Click to expand...
Click to collapse
Factory reset doesn't mean what you think it does, it just wipes user data. It won't magically restore your stock ROM.
---------- Post added at 02:48 PM ---------- Previous post was at 02:46 PM ----------
SynoX4 said:
Then i go with unrooting it.
Followed some guide all went well but when i needed to flash superuser uninstall, it didnt uninstall(in twrp it said it was successful).
Then i flashed stock recovery and relocked bootloader with superuser still installed.
Only then i discovered that superuser is still there, and when i tried installing update it restarted into fastboot.
Today i was reading something and found out about supersu. I got it and it uninstalled superuser and root checker said phone is not rooted correctly but update still did the same thing.
Click to expand...
Click to collapse
You do NOT need to unroot to OTA. You also did not need to relock the bootloader to OTA. Doing so is what put you in the current non-bootable position.
redpoint73 said:
Factory reset doesn't mean what you think it does, it just wipes user data. It won't magically restore your stock ROM.
---------- Post added at 02:48 PM ---------- Previous post was at 02:46 PM ----------
You do NOT need to unroot to OTA. You also did not need to relock the bootloader to OTA. Doing so is what put you in the current non-bootable position.
Click to expand...
Click to collapse
Yeah,well i solved problem,thought this thread died... Is there a way to mark thread as solved?
Also thanks,and sorry for wasting your time.
SynoX4 said:
Yeah,well i solved problem,thought this thread died... Is there a way to mark thread as solved?
Also thanks,and sorry for wasting your time.
Click to expand...
Click to collapse
You didn't waste anyone's time. I couldn't find a stock nandroid with the software number you were looking for, or I would have tried to help some more.
You can just add [SOLVED] to the thread title. But you should also add a post explaining how you fixed your issue (in case someone with the similar or similar problem is looking for the solution.
redpoint73 said:
You didn't waste anyone's time. I couldn't find a stock nandroid with the software number you were looking for, or I would have tried to help some more.
You can just add [SOLVED] to the thread title. But you should also add a post explaining how you fixed your issue (in case someone with the similar or similar problem is looking for the solution.
Click to expand...
Click to collapse
Sure,will do tomorrow,out of time for today.
So some might remember me awhile back ago... https://forum.xda-developers.com/pixel-xl/help/unlocking-verizon-bootloader-t3557290
I got tired of not having a unlocked/rooted device since I just dropped so much money on a new phone for my 27th bday sooo I took it back to verizon and swapped it for a new one. I was having the battery problems where my phone would hit 30-15% and just die on me OR the screen would die on me but the phone stayed on no problems.. I'd be in a phone call and the screen would shut off and I couldnt get it to turn back on without plugging in a charger or battery bank.
I've got my new phone now and everything is working flawlessly.. It's unlocked, has twrp installed and rooted just fine..
Now I remember seeing something about once I unlock/root the device my OTA becomes disabled so where do I get the OTA update for the device so I can go to 7.1.1 or later this month 7.1.2? I found this https://developers.google.com/android/ota and I see the 7.1.1 update but it's 800mbs which means I'm guessing if I flash that i'd be completely reinstalling a new copy of android and lose all of my data and have to go through setting up my phone again etc..
How do I just get the update itself and flash that? When I use the OTA on my Pixel XL the download is only like 200MB it doesn't install though just says it failed. Still new to all of this but I'm learning and how else am I gonna learn if I don't ask questions
a point in the right direction would be great.
https://developers.google.com/android/images
Sent from my Pixel XL using Tapatalk
---------- Post added at 07:23 PM ---------- Previous post was at 07:22 PM ----------
Point point
Sent from my Pixel XL using Tapatalk
wyrdtrtle said:
https://developers.google.com/android/images
Sent from my Pixel XL using Tapatalk
---------- Post added at 07:23 PM ---------- Previous post was at 07:22 PM ----------
Point point
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
These images are even bigger than the ones I linked.. the 7.1.1 update is 1.8GB? the file I'm downloading via my Phone is 282.1 MB?
[QUOTE=
If you go to that link in the post above you can download the newest firmware. Unzip it and open the bat file with note editor or something like that and remove the -w and it will update without losing your data.
Dimmizer said:
These images are even bigger than the ones I linked.. the 7.1.1 update is 1.8GB? the file I'm downloading via my Phone is 282.1 MB?
Click to expand...
Click to collapse
You use your original link and sideload it with TWRP.
TonikJDK said:
You use your original link and sideload it with TWRP.
Click to expand...
Click to collapse
Thanks
Upper left corner Link to OTA's smaller
Sent from my Pixel XL using Tapatalk
Now one last question...
From official TWRP webpage it says
Never try official ota updates using TWRP. Its not recommended. should I wait to update to 7.1.1 or flash? any pros/cons?
Thanks for all the help and ansrewing of questions so far
Edit: should I unroot and try to OTA again and if it works just reroot the device?
Dimmizer said:
Now one last question...
From official TWRP webpage it says
Never try official ota updates using TWRP. Its not recommended. should I wait to update to 7.1.1 or flash? any pros/cons?
Thanks for all the help and ansrewing of questions so far
Edit: should I unroot and try to OTA again and if it works just reroot the device?
Click to expand...
Click to collapse
You are unlocked, so the only danger here is that you bootloop and lose your data. Make sure your data is backed up and sideload the ota with the directions on googles ota page and re install TWRP.
That's the easiest way and pretty darn safe. I dont recall seeing anyone having trouble with that.
Looking at unrooting my device so I can do OTA updates via the phone and then I'll just reroot again but during the unroot process it says
Attempt to restore stock boot image? This is require for OTA's to succeed. If you manually decrypted your device, note that this might prevent my device from booting.
How do I know if I manually decrypted it? I used depixel8 to unlock bootloader and used SuperSU to root so am I safe to proceed or should I not attempt to restore a stock boot image?
Dimmizer said:
Looking at unrooting my device so I can do OTA updates via the phone and then I'll just reroot again but during the unroot process it says
Attempt to restore stock boot image? This is require for OTA's to succeed. If you manually decrypted your device, note that this might prevent my device from booting.
How do I know if I manually decrypted it? I used depixel8 to unlock bootloader and used SuperSU to root so am I safe to proceed or should I not attempt to restore a stock boot image?
Click to expand...
Click to collapse
You did not decrypt it. That isn't currently doable.
TonikJDK said:
You are unlocked, so the only danger here is that you bootloop and lose your data. Make sure your data is backed up and sideload the ota with the directions on googles ota page and re install TWRP.
That's the easiest way and pretty darn safe. I dont recall seeing anyone having trouble with that.
Click to expand...
Click to collapse
Doing what you said now
[
Dimmizer said:
Looking at unrooting my device so I can do OTA updates via the phone and then I'll just reroot again but during the unroot process it says
Attempt to restore stock boot image? This is require for OTA's to succeed. If you manually decrypted your device, note that this might prevent my device from booting.
How do I know if I manually decrypted it? I used depixel8 to unlock bootloader and used SuperSU to root so am I safe to proceed or should I not attempt to restore a stock boot image?
Click to expand...
Click to collapse
I wouldn't unroot with that, doesn't work all the time just flash the newest firmware and you will be unrooted. You are going to have a bad time if you do.
mk so another question..
https://twrp.me/faq/officialota.html
twrp says NOT to flash ota with twrp? so should I flash back to a stock recovery or just use twrp? if so how? lol
https://developers.google.com/android/ota
The google site explains what to do but I'm assuming it's explaining things as if I had a stock recovery and I don't..
lol... I know this isn't that hard and I'm just being paranoid cause I don't wanna brick my phone etc. but also it's like ALLLL this work just so I can flash new android update to my phone... and this whole thing seems to be taking longer than it really needs to.
Dimmizer said:
lol... I know this isn't that hard and I'm just being paranoid cause I don't wanna brick my phone etc. but also it's like ALLLL this work just so I can flash new android update to my phone... and this whole thing seems to be taking longer than it really needs to.
Click to expand...
Click to collapse
Hit the link below, it explains it well and you will see it worked for others.
https://forum.xda-developers.com/pixel-xl/help/rooted-twrp-recovery-how-update-ota-t3524279
If you ever bootloop don't freak, its an unlocked google phone. Flashing back to stock is easy.
The only thing that was in question was the bootloader unlock, once its unlocked your safe. It wont relock unless you lock it. But, if you do lock it, its locked for good. Afaika
Sent from my Pixel XL using Tapatalk
Dimmizer said:
lol... I know this isn't that hard and I'm just being paranoid cause I don't wanna brick my phone etc. but also it's like ALLLL this work just so I can flash new android update to my phone... and this whole thing seems to be taking longer than it really needs to.
Click to expand...
Click to collapse
Dimmizer said:
mk so another question..
https://twrp.me/faq/officialota.html
twrp says NOT to flash ota with twrp? so should I flash back to a stock recovery or just use twrp? if so how? lol
https://developers.google.com/android/ota
The google site explains what to do but I'm assuming it's explaining things as if I had a stock recovery and I don't..
Click to expand...
Click to collapse
I flashed OTA with twrp on my buddy's pixel for the Feb update worked just fine. Just make sure it's the OTA and not the factory image. But the best way would be using fastboot
Most anything you flash (stock updates, custom roms, will overwrite recovery. But not a problem, you just re-boot it to flash it, or just boot it and flash su and reboot device.
Sent from my Pixel XL using Tapatalk
awesome , thanks again everyone for your time and the help, very much greatly appreciated.