Database Develop

[Q] Verizon Moto X won't boot, but will boot into boot loader mode...

then when I get it into fastboot mode (it says "AP Fastboot Flash Mode (S)" and try to do a factory reset using the volume up button it will boot back into the startup screen (Moto "M") and not go past that or if I try to use the method outlined on Motorola's support site (use the vol down key to navigate then "tap" the power button to select) it goes black and does nothing.
This phone hasn't been updated to 4.4. I'm pretty sure it has the factory 4.2 on it still.
It also says the "Device is LOCKED Status Code: 0" If this is a clue to anyone who could lead me to the right direction of how to get this device back up and running, I'd be very grateful.

smacsteve said:
then when I get it into fastboot mode (it says "AP Fastboot Flash Mode (S)" and try to do a factory reset using the volume up button it will boot back into the startup screen (Moto "M") and not go past that or if I try to use the method outlined on Motorola's support site (use the vol down key to navigate then "tap" the power button to select) it goes black and does nothing.
This phone hasn't been updated to 4.4. I'm pretty sure it has the factory 4.2 on it still.
It also says the "Device is LOCKED Status Code: 0" If this is a clue to anyone who could lead me to the right direction of how to get this device back up and running, I'd be very grateful.
Click to expand...
Click to collapse
What was the last thing you did before this happened?

smacsteve said:
then when I get it into fastboot mode (it says "AP Fastboot Flash Mode (S)" and try to do a factory reset using the volume up button it will boot back into the startup screen (Moto "M") and not go past that or if I try to use the method outlined on Motorola's support site (use the vol down key to navigate then "tap" the power button to select) it goes black and does nothing.
This phone hasn't been updated to 4.4. I'm pretty sure it has the factory 4.2 on it still.
It also says the "Device is LOCKED Status Code: 0" If this is a clue to anyone who could lead me to the right direction of how to get this device back up and running, I'd be very grateful.
Click to expand...
Click to collapse
Have tried to fxz yet. It usually will fix a software issue.

Use RSDLite to flash the 4.2.2 or 4.4 firmware/sbf which can be found at http://sbf.droid-developers.org. You need to be sure that you're not on 4.4.2 before doing so. If your phone has already been updated to 4.4.2, flash only the 4.4.2 firmware/sbf.

Which one?
{
"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 found two versions for 4.2.2 How do I know which one is correct?

smacsteve said:
I found two versions for 4.2.2 How do I know which one is correct?
Click to expand...
Click to collapse
If you are SURE you device had 4.2.2, then use 139.15.1 for verizon.
There are really 4 roms for Verizon...
Initial shipping 4.2.2 = 139.10.53
First OTA - 4.2.2 w/camera fix = 139.15.1
Second OTA - 4.4 = 140.45.5
Third OTA - 4.4.2 = 164.55.2
Reason nhizzat says be sure you're not on 4.4.2 is due to changes in 4.4.2 (bootloader, gpt.bin, and a few other parts). once you have 4.4.2, there are issues that will arise if you try flashing anything older. Some of those issues include bricking the phone!!
So the safest suggestion is if you have 4.4.2, do not flash anything but 4.4.2.
And you never answered what was the last thing you did that got you in this state.

KidJoe said:
If you are SURE you device had 4.2.2, then use 139.15.1 for verizon.
There are really 4 roms for Verizon...
Initial shipping 4.2.2 = 139.10.53
First OTA - 4.2.2 w/camera fix = 139.15.1
Second OTA - 4.4 = 140.45.5
Third OTA - 4.4.2 = 164.55.2
Reason nhizzat says be sure you're not on 4.4.2 is due to changes in 4.4.2 (bootloader, gpt.bin, and a few other parts). once you have 4.4.2, there are issues that will arise if you try flashing anything older. Some of those issues include bricking the phone!!
So the safest suggestion is if you have 4.4.2, do not flash anything but 4.4.2.
And you never answered what was the last thing you did that got you in this state.
Click to expand...
Click to collapse
Okay, it's kind of hard to say what the last thing was as this is a demo device that was on the sales floor at my retail establishment. So it's fair to say that it's unknown. It's been un-used for nearly since after the first of the year. It may have been going through a firmware update and ran out of power. I'm not 100% certain it didn't get to 4.4.2 What was the date of release of Kitkat for the VZN Moto X? That would be helpful to know, then I would be a bit more certain of which it is. Does this help?

smacsteve said:
Okay, it's kind of hard to say what the last thing was as this is a demo device that was on the sales floor at my retail establishment. So it's fair to say that it's unknown. It's been un-used for nearly since after the first of the year. It may have been going through a firmware update and ran out of power. I'm not 100% certain it didn't get to 4.4.2 What was the date of release of Kitkat for the VZN Moto X? That would be helpful to know, then I would be a bit more certain of which it is. Does this help?
Click to expand...
Click to collapse
Based on this thread -> http://forum.xda-developers.com/moto-x/general/4-4-2-vzw-t2656843 4.4.2 came out Feb 21.
I'd have to look to find the 4.4 thread.
If you don't need root (or if you have the Dev Edition for Verizon), then you might as well play it safe and just flash the 4.4.2 SBF and be done with it.

KidJoe said:
Based on this thread -> http://forum.xda-developers.com/moto-x/general/4-4-2-vzw-t2656843 4.4.2 came out Feb 21.
I'd have to look to find the 4.4 thread.
If you don't need root (or if you have the Dev Edition for Verizon), then you might as well play it safe and just flash the 4.4.2 SBF and be done with it.
Click to expand...
Click to collapse
Thanks for your help... I know it's not a VZN Dev Ed. I'm inclined to think it may have been updated to 4.4.2 or at least 4.4. I'll go with your suggestion and try to flash with the 4.4.2 SBF and as you said... "be done with it" I'm not going to have time to get to it for a few days, but I'll report back my success or dare I say it... failure? Hope not. I've got nothing to lose with this unit anyways. Just trying to get a dead demo back up and running.

Force closes after 5.1 update

I just received the 5.1 update today. I'm on sprint, if that matters. Immediately after the update, I'm getting bombarded with these force closes, immediately returning after hitting either "ok" or "report". It will continue for 3 or 4 minutes, then clear up for a few minutes, then returning when I open an app.
I'm stock, not rooted. Since I'm not rooted, I'm not sure what I can do other than reboot or factory reset? This is the first phone I haven't rooted since I got into android. I'm feeling like I should just root /wipe/flash, but before I do, any other suggestions to quickly clear up the force closes? Thanks!
{
"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 had the same message after updating to 5.1 from 5.0 when trying to use my camera app.
I had rebooted the phone, and the problem went away.

3f62011 said:
I had the same message after updating to 5.1 from 5.0 when trying to use my camera app.
I had rebooted the phone, and the problem went away.
Click to expand...
Click to collapse
Thanks! Unfortunately that hasn't solved it. I booted into the stock recovery and wiped cache. Still no dice. I'll factory reset next I guess!

I guess if you don't want to root I would get some cache cleaning apps
Sent from my Google N6 on VZ

Well I unlocked the bootloader and flashed the most updated stock image using fastboot, manually. All is well now. It took longer to get my computer and drivers working than actually fixing the phone. Now that my bootloader is unlocked, I guess it's time to root. Thanks for the advice.

Do yourself a favor and get the Nexus toolkit you can run commands by hand or let the tool do it for you.
http://www.wugfresh.com/nrt/
WugFresh trolls this forum pretty often too
Sent from my Google N6 on VZ

You don't need root or any special "app" to see what is going on.
You need a LOGCAT.
And to post it here so that somebody who understands it can interpret it.

doitright said:
You don't need root or any special "app" to see what is going on.
You need a LOGCAT.
And to post it here so that somebody who understands it can interpret it.
Click to expand...
Click to collapse
I 100% percent agree with you but the reality is you could reload the phone and reset everything before you get a definitive answer.
Sent from my Google N6 on VZ

DebianDog said:
I 100% percent agree with you but the reality is you could reload the phone and reset everything before you get a definitive answer.
Click to expand...
Click to collapse
I don't agree. At least not entirely. There are enough people here to interpret a logcat, it could be done in seconds.
But it does come down to how significant of a setup you're dealing with, and how well equipped you are to understand and manage a problem.
My wife's hammerhead did something weird not long ago, google applications continuous force close. A quick examination of the logcat yielded a "can not downgrade database from version 3 to 2" problem on the gms package. Kind of weird, since it just happened out of the blue, she's running factory + root on the thing. So I wiped the database, rebooted, and its back to normal. Took 2 minutes. A wipe and reload and reconfigure would have taken hours.
For my own devices, last time I did a "wipe" was in... 2012. I did a full backup and restore from my last phone to my N6, wiped/adjusted/reset whatever databases and configurations didn't match between the Samsung Relay custom 5.0 build (I did userdata "upgrade" the whole way up from 4.0 on that device, without wiping even ONCE) and the N6. Saved tons of time.

In the time it took you to respond to this message I could have backed up my whole phone on titanium backup. Wiped it. flashed it. Reroot it and restored all my settings and applications. That's my point.
Sent from my Google N6 on VZ

DebianDog said:
In the time it took you to respond to this message I could have backed up my whole phone on titanium backup. Wiped it. flashed it. Reroot it and restored all my settings and applications. That's my point.
Click to expand...
Click to collapse
Except that in restoring your backup, you have also restored whatever the problem was, and are now back to square one.

doitright said:
Except that in restoring your backup, you have also restored whatever the problem was, and are now back to square one.
Click to expand...
Click to collapse
Maybe or maybe not you mean. Caches inconsistent with the current version how Android are usually the cause of this or caches that got corrupted in some manner . And as you know you never restore caches.
My 5 years experience with Android dictates that these problems are usually EASILY resolved with a wipe of the cache/phone. perhaps your personal evidence is different.
Yes I personally would fire up system info and look at the logs before I wiped my caches and if that didn't work I would wipe the phone.
Sent from my Google N6 on VZ

[Q] Trouble installing OTA update.

I'm brand new to rooting, but I've had an android phone for years. I finally managed to install towelroot to my i537. I had to flash to NE3 install towelroot and run it, and then flash back to NH3 (these may be wrong I did it a while back.) so now I'm on NH3, and I uninstalled supersu and did a factory reset, hoping that I could install the OTA update with my root removed and a factory reset. This didn't work, I didn't have a custom rom installed, and all I had was supersu so i could uninstall bloatware and use some root dependent apps. When I attempt to install the ota update it says update failed at about 25%. My baseband version is i537ucucnh3, im not sure if this is needed but my kernel version is 3.4.0-2638177 [email protected] #1, and my build number is kot49h.i537ucucnh3. Any help is great, but If you can be very clear because I have almost no clue what im doing. I had to have a buddy of mine help with installing the root in the first place, and he isn't around to help.

notmechjeb said:
I'm brand new to rooting, but I've had an android phone for years. I finally managed to install towelroot to my i537. I had to flash to NE3 install towelroot and run it, and then flash back to NH3 (these may be wrong I did it a while back.) so now I'm on NH3, and I uninstalled supersu and did a factory reset, hoping that I could install the OTA update with my root removed and a factory reset. This didn't work, I didn't have a custom rom installed, and all I had was supersu so i could uninstall bloatware and use some root dependent apps. When I attempt to install the ota update it says update failed at about 25%. My baseband version is i537ucucnh3, im not sure if this is needed but my kernel version is 3.4.0-2638177 [email protected] #1, and my build number is kot49h.i537ucucnh3. Any help is great, but If you can be very clear because I have almost no clue what im doing. I had to have a buddy of mine help with installing the root in the first place, and he isn't around to help.
Click to expand...
Click to collapse
You can't do the ota like normal, and uninstalling superSU isn't the same as unrooting. Honestly if you want to update to lollipop manually, I would recommend Odin flashing back to NE3, rooting, then going straight to OC6 (lollipop) and following these instructions to update while keeping root. No matter what you do, you have a bit of work cut out for you, may as well do the method that lets you be rooted on lollipop, plus it's not too difficult if you follow instructions carefully and is confirmed working by numerous users

thisisapoorusernamechoice said:
You can't do the ota like normal, and uninstalling superSU isn't the same as unrooting. Honestly if you want to update to lollipop manually, I would recommend Odin flashing back to NE3, rooting, then going straight to OC6 (lollipop) and following these instructions to update while keeping root. No matter what you do, you have a bit of work cut out for you, may as well do the method that lets you be rooted on lollipop, plus it's not too difficult if you follow instructions carefully and is confirmed working by numerous users
Click to expand...
Click to collapse
Alright, that shouldnt be too hard, so I just flash back to NE3 and root with towelroot, and then flash back to oc6, skipping nh3 right? The file in the thread you posted is nh3tolollipop, does that matter? or with it work with ne3 to lollipop too?

notmechjeb said:
Alright, that shouldnt be too hard, so I just flash back to NE3 and root with towelroot, and then flash back to oc6, skipping nh3 right? The file in the thread you posted is nh3tolollipop, does that matter? or with it work with ne3 to lollipop too?
Click to expand...
Click to collapse
NE3 to lollipop works just fine, I've done it like a dozen times now lol. Skipping NH3 is easier and quicker for a bunch of reasons

hey! I got it! thanks for the help

notmechjeb said:
hey! I got it! thanks for the help
Click to expand...
Click to collapse
Hey I am having the same problem. I am wondering which file you are using from here http://forum.xda-developers.com/showthread.php?t=2629093 to flash back to ne3. I was just going to use this page for instructions on Odin http://www.w0lfdroid.com/2014/09/To...4-S5-and-Note3-Android-4.4.2-NF-or-Later.html

BeastyBananaCo said:
Hey I am having the same problem. I am wondering which file you are using from here http://forum.xda-developers.com/showthread.php?t=2629093 to flash back to ne3. I was just going to use this page for instructions on Odin http://www.w0lfdroid.com/2014/09/To...4-S5-and-Note3-Android-4.4.2-NF-or-Later.html
Click to expand...
Click to collapse
That w0lfdroid site is how to root NH3, you don't need that to root NE3, you can just do normal towelroot. NE3 Odin files are here you have to extract that zip and flash all four files simultaneously in Odin. It'll look like this:
{
"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"
}

BeastyBananaCo said:
Hey I am having the same problem. I am wondering which file you are using from here http://forum.xda-developers.com/showthread.php?t=2629093 to flash back to ne3. I was just going to use this page for instructions on Odin http://www.w0lfdroid.com/2014/09/To...4-S5-and-Note3-Android-4.4.2-NF-or-Later.html
Click to expand...
Click to collapse
There's an entire guide on how to flash any firmware.
http://forum.xda-developers.com/showthread.php?t=2835481

Wow so I messed up. While I was flashing NE3 on my phone and the cable came loose and my phone disconnected. It of course caused the flash to fail. I restarted the flash because it explicitly says not to restart your device. It was nearly complete and I got an error on my phone saying something along the lines of " The percentage bar is filled but the process isn't done" I now can't finish the flash. What should I do? Am I just royally screwed?
Good news! I fixed it! If anyone else has their install fail basically I just relaunched it in download mode and then I just retried the install.

How to Downgrade to Root-able Version

Ok so I accidentally upgraded my phone to g925vvru2aof1 verison, and when I researched to see if I could root I found it wasn't supported. My question is, can I downgrade this version to a version that you can root? Or am I stuck on this update? Thanks in advance for your help!

collinfc said:
Ok so I accidentally upgraded my phone to g925vvru2aof1 verison, and when I researched to see if I could root I found it wasn't supported. My question is, can I downgrade this version to a version that you can root? Or am I stuck on this update? Thanks in advance for your help!
Click to expand...
Click to collapse
You're stuck unfortunately.

collinfc said:
Ok so I accidentally upgraded my phone to g925vvru2aof1 verison, and when I researched to see if I could root I found it wasn't supported. My question is, can I downgrade this version to a version that you can root? Or am I stuck on this update? Thanks in advance for your help!
Click to expand...
Click to collapse
The OE2 build you can downgrade.
The OF1 build you cannot.
Very sad. Very disheartening.

Have you tried this?
http://forum.xda-developers.com/verizon-galaxy-s6-edge/development/trailblazer101-lightlycleaned-rooted-rom-t3157394
I was already rooted and couldn't take OF1 update, so I don't know if this would work for you.
Basically, odin back to OC3 or OE2 and also odin the firmware package called "Flash Me Package" by Trailblazer before rebooting the system.
This might enable you ping-pong root the OC3. but you would still be on OF1 radio.

mngdew said:
Have you tried this?
http://forum.xda-developers.com/ver...lblazer101-lightlycleaned-rooted-rom-t3157394
I was already rooted and couldn't take OF1 update, so I don't know if this would work for you.
Basically, odin back to OC3 or OE2 and also odin the firmware package called "Flash Me Package" by Trailblazer before rebooting the system.
This might enable you ping-pong root the OC3. but you would still be on OF1 radio.
Click to expand...
Click to collapse
It has already been said on many threads that it is impossible to downgrade. There is no way around it.

Snowby123 said:
It has already been said on many threads that it is impossible to downgrade. There is no way around it.
Click to expand...
Click to collapse
Are you sure? Sounds like people are saying it's possible in that thread.

latetext said:
Are you sure? Sounds like people are saying it's possible in that thread.
Click to expand...
Click to collapse
How the flash me package works is it installs the OF1 radios onto the rom while maintaining the OE2 bootloader, kernel, etc.

You can not downgrade, that rom is a hybrid which lets you but the full of1 cant

can i downgrade from G925VVRU4BOK7 to any rootable version.
im pretty sure i cannot.
thanks anyway.

vedgya said:
can i downgrade from G925VVRU4BOK7 to any rootable version.
im pretty sure i cannot.
thanks anyway.
Click to expand...
Click to collapse
No way.

G920vvru4 is it possible to downgrade ?

Hi everyone, I just wanted to tell everyone that I've discovered that root on G925V 5.1.1 (G925VVRU4BOG7) is now a reality. Some guys at easy-firmware made it possible. I have not tested it yet:
forums.easy-firmware.com/showthread.php?59402-ROOT-Sm-g925v-5-1-1-og7-eng-root-free-for-all

SuperSZ said:
Hi everyone, I just wanted to tell everyone that I've discovered that root on G925V 5.1.1 (G925VVRU4BOG7) is now a reality. Some guys at easy-firmware made it possible. I have not tested it yet:
forums.easy-firmware.com/showthread.php?59402-ROOT-Sm-g925v-5-1-1-og7-eng-root-free-for-all
Click to expand...
Click to collapse
Did anyone tried this, or at least, get the password?
I can try it if somebody send me the password.

dami391 said:
Did anyone tried this, or at least, get the password?
I can try it if somebody send me the password.
Click to expand...
Click to collapse
The password is fghdbnfgdfgb19545525 (really, just copy paste it). I tried it. It works. Here are the steps:
1) Put the phone in download mode (With the phone turned off press down+home+power at the same) and flash the file through Odin (using the second file, the one it says AP or PDA (depending of your version)). It takes a couple seconds. After that the phone will boot normaly. Then, if you reboot the phone, the next time you turn on the phone, you'll see a big icon of a locker but unlocked and just below it will say 'custom', just like this:
{
"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"
}
(If it didn't work (you keep getting the normal boot screen), then try to flash it again until you succeed. It may take some tries.)
2) Up to that point the phone will be technically rooted, but you can't do 'root stuff' yet. So what do you do? You download the Kingroot apk (from the official site) and install it. Now you'll be able to fully use the root. The only downside; its a temporary root (every time you reboot the device you'll have to install root again from the Kingroot app)

is g925vvrs4cqa3 rootable or can i downgrade to one that is? not one post about this baseband cut ones that i made...

I downloaded the file but only have 1 file. a boot.img file Do i flash that in AP or in the BL spot in ODIN?

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?