Database Develop

VZW OTA 4.4.4 problem

hello. I just received the 4.4.4 OTA update, but I have a problem,
I clicked on "update now" and then the phone just shut off. and after it boot, it stuck on this screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
it's says, "partition (recovery) security version downgraded. fastboot reason boot failure"
so now, every time that I try to boot the phone, it's shut down and go to recovery.
recovery don't work either.
I don't understand why this is happening. the 4.4.2 OTA I received without any problems!
What should I do now? the phone is currently useless.
this is xt1060 model locked bootloader.
Thank you for your help!

ghgh1 said:
hello. I just received the 4.4.4 OTA update, but I have a problem,
I clicked on "update now" and then the phone just shut off. and after it boot, it stuck on this screen:
it's says, "partition (recovery) security version downgraded. fastboot reason boot failure"
so now, every time that I try to boot the phone, it's shut down and go to recovery.
recovery don't work either.
I don't understand why this is happening. the 4.4.2 OTA I received without any problems!
What should I do now? the phone is currently useless.
this is xt1060 model locked bootloader.
Thank you for your help!
Click to expand...
Click to collapse
This is what it appears to me: At SOME point, you flashed a newer firmware than 4.4.2
I believe this because it is the ONLY thing I have EVER seen cause this error. Did you ever flash the 4.4.3 T-Mobile Rom?
It could certainly be something else...never know.
Anyways, find the thread for the 4.4.4 VZW FXZ (in General sub-forum), and simply flash the entire FXZ per the instructions in that thread, OR the Return to 100% Stock thread (also in General sub-forum). The FXZ is a keep-data FXZ, so you won't lose your data. In fact, there is absolutely NO benefit to taking the OTA, over flashing the FXZ. In fact, one could argue (I would...) that the FXZ is superiour in that it can actually FIX a corrupted filesystem (it re-writes all partitions, except /data), while an OTA cannot.
Good Luck, keep us updated.

omanyo4 was
thank you for your reply!
now, after few reboots, the phone showed me a message that the update was unsuccessful and it's stopped to shut off, so I backed up all the stuff that I need.
I'm not sure about the FXZ(what is it mean? is that different than the regular OTA?). is the FXZ erase data?
because if it is, I just can do factory reset and take the OTA in a normal way(I guess)...
edit: I don't care so much about the data. I care about the root - so this is why I'm asking
thanks again

ghgh1 said:
thank you for your reply!
now, after few reboots, the phone showed me a message that the update was unsuccessful and it's stopped to shut off, so I backed up all the stuff that I need.
I'm not sure about the FXZ(what is it mean? is that different than the regular OTA?). is the FXZ erase data?
because if it is, I just can do factory reset and take the OTA in a normal way(I guess)...
edit: I don't care so much about the data. I care about the root - so this is why I'm asking
thanks again
Click to expand...
Click to collapse
Unless your bootloader is unlocked, you will permanently lose root once on 4.4.4 -- you should have known this before you attempted to take the OTA.
FXZ is an acronym for Full XML Zip file and is the format for most dual core Motorola firmware files.
They are an archive of all of the stock partition images for a given device to be flashed in fastboot with either RSD lite or using adb and the fastboot binary.
In contrast to an OTA will only flash successfully if the manifest verifies several files and their checksums, an FXZ can actually REPAIR a corrupted filesystem, and restore all partitions to stock.
This particular FXZ (the 4.4.4 one I suggested that you use) is a "keep data" fxz -- it won't erase your data.
Now tell me how you are / were rooted? Again you should have already known before trying to take the OTA, that 4.4.4 patches all known root-exploits -- if you didn't, then you failed to do your research....
IF (and only if) your bootloader is unlocked, you can re-root EASILY afterwards, by simply flashing TWRP via fastboot, and it will root for you.
Clarify all the questions I've asked you and I might be able to help you proceed....

I did the FXZ method and now the phone on 4.4.4
I lose my root, but I feel that the touch is softer now.
I hope that will be root to the locked bootloader devices.
the good thing is that I didn't lose my data!
Thank you very much, samwathegreat!

moto x 2013
Guys i have the same message i really don't know how to proceed, what to do, what to download... Is there any guide? If yes i'll really appreciate if you can link me something. Thanks
!

Ridiculously easy upgrade to 5.1 and keep root/TWRP/no-wipe

All I know is that the wugfresh nexus root toolkit is the way to go. I discovered that windows application early on in my Nexus 5 ownership and haven't looked back. Sure, back in the day I would SDK and ADB and root and rom when it was cool and almost mandatory to bring in the cutting edge features on my incredible and galaxy nexus but there's just no need for it anymore with Lollipop having all the must-haves. And with the toolkit all I did was fire it up and the app put my N5 to sleep, poured it some warm milk, and rubbed its belly until it purred. 5 minutes later I'm up from 5.01 to 5.1 and I still have root, TWRP, and didn't even have to lose my ex-girlfriends phone number with a wipe. It even pre-downloaded 5.1 for me and checked md5. I really can't say enough good things about how painfree it is. Essentially 1 click.
If no-wipe turns out to be crap, I'll just click the OTHER button and be good to go. Thanks WUG!! You ROCK!

So far so good on the dirty flash...

What are you looking for? Validation? An argument? Validation through argument? Help me out here.

Wakamatsu said:
What are you looking for? Validation? An argument? Validation through argument? Help me out here.
Click to expand...
Click to collapse
Hahah, you're right. I was just sharing the solution. When the last update came out everyone who had root/custom recovery was freaking out and having issues with upgrading and they had all these how-to threads, etc. Wug's application is just so easy. And I wanted to poll to see how many people are using a toolkit vs. ADB.

rabaker07 said:
Hahah, you're right. I was just sharing the solution. When the last update came out everyone who had root/custom recovery was freaking out and having issues with upgrading and they had all these how-to threads, etc. Wug's application is just so easy. And I wanted to poll to see how many people are using a toolkit vs. ADB.
Click to expand...
Click to collapse
Probably some people are like me and prefer doing it the tough way by flashing files manually, instead of using a tool kit.

Wugfreshes toolkit is the best. As you probably know most of the senior pple discuss and ridicule toolkits. I've never had trouble with his.
ADB is hassle if you are new. We all know driver issues. Thats a nightmare b4 you even start. I've since learnt ADB commands but still would only use it as a last stop. It was the toolkit that found and loaded the driver allowing ADB.
To be honest I think, subconsciously, ADB users see them selves as superior to the rest of us.
I'm happy with the years Rug fresh has been there for me. The tool updates automatically.
Sent from a Toolbox rooted and flashed phone
Sent from my Nexus 5

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But seriously:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
boot into custom recovery
flash SuperSU/other stuff if desired
isn't that hard.
Driver issues? If you had driver issues your toolkit wouldn't work either. All it does is literally the above—if that is so hard, then maybe you shouldn't modify your device.
Also, ADB ≠ fastboot, they are separate binaries and have a completely different purpose.

@Elluel
Agreed. Just to notice you - Wug's Toolkit recognize ADB or fastboot by itself.
@rabaker07
Was using Wug's Toolkit for a long time. But I don't prefere anymore that app itself take so much space and not necessary files on my PC. So this is much better solution: @rootSU http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
@zerosum0
To be honest. Yes, there are people that feel superior at XDA. But hey, they have reasons.
Problem is, that if you got a bootloop or something like that, its very hard to help people, because they actually don't know what they were doing with their phones before that happened. And if they are also yellers then we got to much threads here like "OMG, please help. :crying:"

I got the drivers on my computer with the kit,after trying everything. That did it in seconds. I do take notice and have written all the commands needed should something go wrong and no toolkit.
A lot of people just are not computer literate.
If push comes to shove I could do it that way but say I want to flash a factory image. The toolkit fetches it, after sorting out the connection between phone and computer. It then flashes it, with a step by step account. Quick and simple. I've never had trouble with it. Toolkits have come along way and I guess there are bad ones out there. Horses for courses. And if someone screws up with a toolkit OR ADB. They should eat humble pie before asking for help.
Sent from my Nexus 5

rabaker07 said:
All I know is that the wugfresh nexus root toolkit is the way to go. I discovered that windows application early on in my Nexus 5 ownership and haven't looked back. Sure, back in the day I would SDK and ADB and root and rom when it was cool and almost mandatory to bring in the cutting edge features on my incredible and galaxy nexus but there's just no need for it anymore with Lollipop having all the must-haves. And with the toolkit all I did was fire it up and the app put my N5 to sleep, poured it some warm milk, and rubbed its belly until it purred. 5 minutes later I'm up from 5.01 to 5.1 and I still have root, TWRP, and didn't even have to lose my ex-girlfriends phone number with a wipe. It even pre-downloaded 5.1 for me and checked md5. I really can't say enough good things about how painfree it is. Essentially 1 click.
If no-wipe turns out to be crap, I'll just click the OTHER button and be good to go. Thanks WUG!! You ROCK!
Click to expand...
Click to collapse
Thank you for sharing your experiences
Glad it worked for you
Thread closed

Update Failing

I just got a regular S6 through T-Mobile and for some reason, the initial update is failing. It will download (177 mb), reboot to install, get to 25%, fail, and reboot. The phone is working perfectly other than that. Any idea what I can do to fix it? Thanks.

Since you just got it, why not do a factory reset, then see if the update takes.

roger1955 said:
Since you just got it, why not do a factory reset, then see if the update takes.
Click to expand...
Click to collapse
I just did a factory reset and it still fails repeatedly.
I get the error "dm verity verification failed".
Also keep in mind that it was doing this out of the box before I even installed any apps.

BTow1105 said:
I just did a factory reset and it still fails repeatedly.
I get the error "dm verity verification failed".
Also keep in mind that it was doing this out of the box before I even installed any apps.
Click to expand...
Click to collapse
What firmware is listed under build number in settings?
The only things off the top of my head I can think of that would be causing this out of the box are Samsung's own phone security or a buggy phone. When trying to root some people got stuck in a boot loop, not cause of a bootloader lock, but because of some part samsung's anti malware security of whatever it is that can be disabled in settings. It was apparently turned on without them knowing. Not sure if this could happen with an official OTA but it's something you can check.
Other than calling samsung or T-mobile considering this is a bug that happened without root, you could try flashing the stock firmware with odin. Although, I can't say whether you'll still have access to the OTA or not, which is why I asked what firmware version you're on.
If it's G920TUVU1AOCG then it's the same as the stock anyway and potentially that could mean it's a bug with the update that was pushed to you seen as it's new. If it's not G920TUVU1AOCG then chances are G920TUVU1AOCG is newer and you can just flash it via odin to update.
edit: you could also try booting into recovery and clearing cache then try the ota again.

When me and my girlfriend got our S6's, hers wouldn't take the update either. It said she had a custom system....The only way I got it to take it was to odin the firmware. That's probably what you'll have to do. Out of curiosity is yours white?

Alarand said:
What firmware is listed under build number in settings?
The only things off the top of my head I can think of that would be causing this out of the box are Samsung's own phone security or a buggy phone. When trying to root some people got stuck in a boot loop, not cause of a bootloader lock, but because of some part samsung's anti malware security of whatever it is that can be disabled in settings. It was apparently turned on without them knowing. Not sure if this could happen with an official OTA but it's something you can check.
Other than calling samsung or T-mobile considering this is a bug that happened without root, you could try flashing the stock firmware with odin. Although, I can't say whether you'll still have access to the OTA or not, which is why I asked what firmware version you're on.
If it's G920TUVU1AOCG then it's the same as the stock anyway and potentially that could mean it's a bug with the update that was pushed to you seen as it's new. If it's not G920TUVU1AOCG then chances are G920TUVU1AOCG is newer and you can just flash it via odin to update.
edit: you could also try booting into recovery and clearing cache then try the ota again.
Click to expand...
Click to collapse
Here is the info you're looking for. It doesn't look to be exactly the same as either version you mentioned.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mikeyinid said:
When me and my girlfriend got our S6's, hers wouldn't take the update either. It said she had a custom system....The only way I got it to take it was to odin the firmware. That's probably what you'll have to do. Out of curiosity is yours white?
Click to expand...
Click to collapse
I tried to use Odin and it seemed like the phone froze on the blue "Downloading..." screen after I tried to send it the stock firmware.
Its a white 32gb regular S6.

BTow1105 said:
Here is the info you're looking for. It doesn't look to be exactly the same as either version you mentioned.
I tried to use Odin and it seemed like the phone froze on the blue "Downloading..." screen after I tried to send it the stock firmware.
Its a white 32gb regular S6.
Click to expand...
Click to collapse
Weird. Same as hers. Do you have all the drivers installed? Is odin seeing your device?

mikeyinid said:
Weird. Same as hers. Do you have all the drivers installed? Is odin seeing your device?
Click to expand...
Click to collapse
The drivers are installed, Odin recognizes the device, but it just seemed frozen on the blue screen. Odin did a few things and said "started" or something and it said that for about 20 minutes before I decided that couldn't be right. Rebooted it and it went right back to normal.

Have another computer to try, just to cancel out that computer being the problem?

So its fixed now. I went to Best Buy and they have a Samsung rep there. I talked to him about it and he decided to plug it into his laptop and put the stock firmware on it (which I tried to do but it also didnt work). The build number changed slightly and now it says the phone is up to date. Here is the old and new build info:

BTow1105 said:
So its fixed now. I went to Best Buy and they have a Samsung rep there. I talked to him about it and he decided to plug it into his laptop and put the stock firmware on it (which I tried to do but it also didnt work). The build number changed slightly and now it says the phone is up to date. Here is the old and new build info:
Click to expand...
Click to collapse
That was very cool of him, I'm pretty sure they're not suppose to do that. To bad he didn't flash some super secret unreleased test software on it lol.

mikeyinid said:
That was very cool of him, I'm pretty sure they're not suppose to do that. To bad he didn't flash some super secret unreleased test software on it lol.
Click to expand...
Click to collapse
5.1 the dream

mikeyinid said:
That was very cool of him, I'm pretty sure they're not suppose to do that. To bad he didn't flash some super secret unreleased test software on it lol.
Click to expand...
Click to collapse
They actually are setup to do it. The Bestbuy Samsung experience shops can install firmware on any Samsung device as long as it has not been modified. They cannot reset Knox.

altimax98 said:
They actually are setup to do it. The Bestbuy Samsung experience shops can install firmware on any Samsung device as long as it has not been modified. They cannot reset Knox.
Click to expand...
Click to collapse
Well , to be honest, they should be doing all warranty work and claims and things right there as well. They have such ****ttty customer service that I'd much rather go somewhere so that I could actually discuss things in person. Kinda like......... APPLE!! That's really the only reason I keep these Crapple devices around, because they will swap out anything 4 me on a dime and it can be done in less than an hour. No 2-3-4 weeks without a phone. It seems like being 2015, Samsung should be able to compete in that sense. Oh well, Sorry, I am just daydreaming over here. :cyclops:

Anybody have a tar file that we can flash in Odin for the 5.1.1 update? I just got my phone today and it wont take the update from T-Mobile. It downloaded all the files and started installing in recovery,then it rebooted and stated the update failed. My phone is bone stock factory and has never been modified in any way. Any help is greatly appreciated!!

PS4AndroidHacker said:
Anybody have a tar file that we can flash in Odin for the 5.1.1 update? I just got my phone today and it wont take the update from T-Mobile. It downloaded all the files and started installing in recovery,then it rebooted and stated the update failed. My phone is bone stock factory and has never been modified in any way. Any help is greatly appreciated!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=62486197

How to Root the Moto Z2 Force T-Mobile/Sprint

Hi everybody! Just here to let people know how to gain root on their shiny new Z2 force!
Straight and simple here's what your going to need:
Fastboot and adb installer
Download This for T-Mobile Rooted August Image For T-Mobile
Download this for Sprint Rooted August Image for Sprint
Installation Instructions
1. Make sure your on T-Mobiles latest update (August)
2. Unlocking your bootloader is a MUST!
3. Open the newly installed adb and fastboot you just installed. You should get a blank command screen.
4. Reboot your device to bootloader mode using the command adb reboot bootloader (make sure usb debugging is on)
5. On the bootloader screen your going to type the command Fastboot flash boot and LEAVE IT THERE DONT DO ANYTHING!
6. Next your going to go to the downloaded rooted august image and drag that to the command screen
7. Once that is done you should see something along the lines of "fastboot flash boot "C:\path\to\boot\Magisk_Moto_August.img"
8. Once you see that hit enter and once you see its done on the bootloader screen click start and it should boot up.
9. Once that is done download this Magisk Manager
10. Install it and BOOM you should have root!
Special thanks to:
@topjohnwu for the updated pixel magisk
@Chainfire for everything he has already done for the community.

Awesome! Today is going to go by so slowly waiting for the Sprint image lol

So, now we can work on ways to fix using third party messaging, notifications, etc? After I turned off the Moto Display the screen rarely lights up with notifications.

filthyfnj24 said:
Awesome! Today is going to go by so slowly waiting for the Sprint image lol
Click to expand...
Click to collapse
The T-Mobile one will work fine since it's the exact same device and once I make one tonight you can just reflash the boot img

joemossjr Great job! You give me hope! :good: :highfive:

Woo-Hoo! Glad to see this has finally happened!

Works! I love you person!

joemossjr said:
The T-Mobile one will work fine since it's the exact same device and once I make one tonight you can just reflash the boot img
Click to expand...
Click to collapse
Awesome. Does this wipe data?
Edit: answered my own question. I took the plunge and it does not wipe. I've never used magisk before. Install via the recommended direct install? Sorry for all the questions, this is a little different than rooting my last three Xperias and I don't really want to become the first guy to brick his z2 on xda lol.

Nope

Once you flash this you should just need the manager and it should be rooted. If it's telling you to install then something went wrong

filthyfnj24 said:
Awesome. Does this wipe data?
Edit: answered my own question. I took the plunge and it does not wipe. I've never used magisk before. Install via the recommended direct install? Sorry for all the questions, this is a little different than rooting my last three Xperias and I don't really want to become the first guy to brick his z2 on xda lol.
Click to expand...
Click to collapse
Put a screen shot of your manager here

joemossjr said:
Put a screen shot of your manager here
Click to expand...
Click to collapse
I'm guessing it's installed. I am able to backup with titanium but unable to delete bloatware (tested on Amazon app and received this error message) I'm guessing it has something to do with the r/w permissions but I'm not sure how to change them on this phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I was able to delete some apps try es file explorer and go to the root section and mount system re and / rw if that doesnt work use this app it worked for me

joemossjr said:
I was able to delete some apps try es file explorer and go to the root section and mount system re and / rw if that doesnt work use this app it worked for me
Click to expand...
Click to collapse
Hmmm. I tried both methods and both said I have been granted rewrite permissions but I still get the same error message from tibu. It's not a big deal, just strange. Adaway installed and is working fine. Those are the only two root apps I've tested.

Can you uninstall any other apps?

This is great thank you
Sent from my SM-N930F using XDA-Developers Legacy app

joemossjr said:
Can you uninstall any other apps?
Click to expand...
Click to collapse
I just downloaded an app from the play store and deleted it with tibu with no problem.

A lot of T-Mobile and Sprint talk, no love for Verizon?? lol
Seriously though if you need any testing done I'm here to help out!

filthyfnj24 said:
I just downloaded an app from the play store and deleted it with tibu with no problem.
Click to expand...
Click to collapse
Odd

chetqwerty said:
A lot of T-Mobile and Sprint talk, no love for Verizon?? lol
Seriously though if you need any testing done I'm here to help out!
Click to expand...
Click to collapse
Sadly Verizon doesn't have an unlocked bootloader and that way past my profession lol

Need to recover data - phone stuck in booting screen

For some reason my Pixel 4XL got stuck on the "G" screen. I realize this means I'm probably going to have to reset my phone, but I really need to recover the photos and videos that are on it. I know, I know, I need to back-up regularly. But I didn't, and now my kid has no digital memories of his pet that died last weekend. I followed some instructions posted by "Techno Bill" a few years ago to sideload an OTA image onto the phone, and everything went very smoothly, but when I re-booted the phone, it is still stuck on the G screen. The first time I got a "No error" error (...?),so I checked for a more recent version of the image and found one. Tried that one twice, seemed like it worked both times, but both times I was still stuck on the G screen. I'm wondering if its because I already had *210305.006* on my phone, which is the one I'm trying to sideload. Any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ChrisH78 said:
For some reason my Pixel 4XL got stuck on the "G" screen. I realize this means I'm probably going to have to reset my phone, but I really need to recover the photos and videos that are on it. I know, I know, I need to back-up regularly. But I didn't, and now my kid has no digital memories of his pet that died last weekend. I followed some instructions posted by "Techno Bill" a few years ago to sideload an OTA image onto the phone, and everything went very smoothly, but when I re-booted the phone, it is still stuck on the G screen. The first time I got a "No error" error (...?),so I checked for a more recent version of the image and found one. Tried that one twice, seemed like it worked both times, but both times I was still stuck on the G screen. I'm wondering if its because I already had *210305.006* on my phone, which is the one I'm trying to sideload. Any ideas?
View attachment 5253543
View attachment 5253545
Click to expand...
Click to collapse
Are you rooted? Did you ever enable usb debugging in developer settings?

Tulsadiver said:
Are you rooted? Did you ever enable usb debugging in developer settings?
Click to expand...
Click to collapse
I'm not, I haven't rooted a phone since my first gen Galaxy, haha. The only things I've done so far are in this instruction (https://drive.google.com/file/d/0Bz6x7k-VkpUJMlZ1aEliVnhMOHM/view). Installed ADB, Fastboot, and necessary drivers. Downloaded an OTA file from developers.google.com, and installed it using the "Apply Update from ADB" option in the recovery menu. My biggest concern is the data. If I can get those photos and videos off I'm perfectly happy nuking the install afterwards and going back to stock. Would rooting it wipe the data?

ChrisH78 said:
I'm not, I haven't rooted a phone since my first gen Galaxy, haha. The only things I've done so far are in this instruction (https://drive.google.com/file/d/0Bz6x7k-VkpUJMlZ1aEliVnhMOHM/view). Installed ADB, Fastboot, and necessary drivers. Downloaded an OTA file from developers.google.com, and installed it using the "Apply Update from ADB" option in the recovery menu. My biggest concern is the data. If I can get those photos and videos off I'm perfectly happy nuking the install afterwards and going back to stock. Would rooting it wipe the data?
Click to expand...
Click to collapse
Yes, you have to unlock the bootloader and that wipes the data. Your phone would have to be able to boot up for that to happen. Just wondering if you flashed something that didn't agree with your phone. Without usb debugging enabled, I don't know a way to pull anything off.

ChrisH78 said:
For some reason my Pixel 4XL got stuck on the "G" screen. I realize this means I'm probably going to have to reset my phone, but I really need to recover the photos and videos that are on it. I know, I know, I need to back-up regularly. But I didn't, and now my kid has no digital memories of his pet that died last weekend. I followed some instructions posted by "Techno Bill" a few years ago to sideload an OTA image onto the phone, and everything went very smoothly, but when I re-booted the phone, it is still stuck on the G screen. The first time I got a "No error" error (...?),so I checked for a more recent version of the image and found one. Tried that one twice, seemed like it worked both times, but both times I was still stuck on the G screen. I'm wondering if its because I already had *210305.006* on my phone, which is the one I'm trying to sideload. Any ideas?
Click to expand...
Click to collapse
At this point you may be lucky to recover your phone at all. It would be helpful to know how you got to this point. You started with the "rescue ota" method which is the last ditch effort for most to reflash a phone with a locked bootloader. Knowing what happened beforehand would be useful information. Since you have flashed the full OTA numerous times via ADB, the only thing left is a factory data reset. At some point you will have to abandon the data and move to the next step in recovering your phone. Even if you never intend to root your phone, you should ALWAYS unlock the bootloader so when the **** hits the fan you have more options to save your data. Wishing you a successful recovery.

v12xke said:
At this point you may be lucky to recover your phone at all. It would be helpful to know how you got to this point. You started with the "rescue ota" method which is the last ditch effort for most to reflash a phone with a locked bootloader. Knowing what happened beforehand would be useful information. Since you have flashed the full OTA numerous times via ADB, the only thing left is a factory data reset. At some point you will have to abandon the data and move to the next step in recovering your phone. Even if you never intend to root your phone, you should ALWAYS unlock the bootloader so when the **** hits the fan you have more options to save your data. Wishing you a successful recovery.
Click to expand...
Click to collapse
Thanks for the reply. I basically got here because every Google post I saw said that I was screwed and would be lucky to save my phone, forget about the data. Except for one, and that one told me to go this route. In the future I'll absolutely unlock my bootloader, but just for my own edification, where would have been a good first place to start with a locked bootloader?

v12xke said:
Wishing you a successful recovery.
Click to expand...
Click to collapse
Would the mount /system option be of any use to me?

ChrisH78 said:
Thanks for the reply. I basically got here because every Google post I saw said that I was screwed and would be lucky to save my phone, forget about the data. Except for one, and that one told me to go this route. In the future I'll absolutely unlock my bootloader, but just for my own edification, where would have been a good first place to start with a locked bootloader?
Click to expand...
Click to collapse
You would use fastboot to dirty flash a full image, removing the wipe flag (-w) from the flash-all script beforehand. This wipes and replaces the boot partition but leaves your data intact.

ChrisH78 said:
Would the mount /system option be of any use to me?
Click to expand...
Click to collapse
No. Even unlocked and rooted we cannot write to the system partition anymore. Any luck on getting your phone working again?