Develop Bugs

[Q] N7 LTE Dead. No Write on NAND. Permanent Brick?

Hey guys, I'd love anyone's opinion on this as this is the first time something like this has happened to be.
Was using the tablet and noticed that the WiFi wouldn't turn back on. Decided to restart. No more start up and stuck on Google logo indefinitely.
Can get into Bootloader
Computer recognizes the Nexus 7 but thats about it
Cannot get into recovery, frozen screen
Fastboot is unrecognizable
Cannot ADB anything
Tried to use Toolkit to flash OTA Google update to no avail
Code:
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
OKAY [ 0.140s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.652s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
sending 'radio' (76038 KB)...
OKAY [ 2.465s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 92.586s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
Creating filesystem with parameters:
Size: 28521246720
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6963195
Block groups: 213
Reserved block group size: 1024
Created filesystem with 11/1741488 inodes and 153337/6963195 blocks
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
--------------------------------------------
Bootloader Version...: FLO-03.14
Baseband Version.....: DEB-Z00_2.42.0_1204
Serial Number........: 07927f06
--------------------------------------------
checking product...
OKAY [ -0.000s]
checking version-bootloader...
FAILED
Device version-bootloader is 'FLO-03.14'.
Update requires 'FLO-04.02'.
finished. total time: 0.078s
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
Press any key to exit...
Is there anything that can be done or am I SOL?
The tablet is still under warranty but it was running custom ROM with an unlocked bootloader, so I'm totally screwed?

Hi mate. exactly the same happened to me few days ago, in fact I came here to open the same topic.
I tried flashing stock image using Nexus toolkit, see the progress but wouldn't load further the google logo. Tried loading the custom recovery, but when I do so from the tool fastboot on my Nexus freezes.
Tried flashing clockwork recovery and TWRP manually but it stays on stock bootloader screen and if I reboot it goes back to the stock bootloader screen (the one with laying android)
I was rooted with stock 4.4.3

@tecz0r, based on the screenshot and the log you posted, have you tried relocking and unlocking the bootloader? See if it helps.

Maverick-DBZ- said:
@tecz0r, based on the screenshot and the log you posted, have you tried relocking and unlocking the bootloader? See if it helps.
Click to expand...
Click to collapse
Just tried that, was able to lock back. Then tried selecting the recovery mode but that just restarted and then jut stayed with the google logo. Was then able to unlock again with a prompt on the device whether or not I would like to unlock but that did not help.
---------- Post added at 03:04 PM ---------- Previous post was at 02:09 PM ----------
Ok, so I was able to boot with TWPR but for some reason touch screen wouldn't work. When trying to boot with Philz or Clockwork bootloader just freezes

When you use the below command
Code:
fastboot devices
Does your device serial number show up? I'm pretty sure it does, since you're able to re-lock and unlock bootloader. I'm guessing you're using wugfresh toolkit on 64 bit windows.
Try to downgrade to JB 4.3, if this works, you can update to 4.4.3 via OTA.
https://developers.google.com/android/nexus/images#razorg
Download the JB 4.3 image above and extract all files to
C:\Program Files (x86)\WugFresh Development\data
Run the below commends manually in a dos prompt.
Code:
cd C:\Program Files (x86)\WugFresh Development\data
fastboot flash bootloader bootloader-deb-flo-03.14.img
fastboot reboot-bootloader
fastboot flash radio radio-deb-deb-g00_1.23.0_0720.img
fastboot reboot-bootloader
fastboot update image-razorg-JLS36C.zip
Then boot to recovery and factory reset.
Reboot tablet and hope for the best.

Maverick-DBZ- said:
When you use the below command
Code:
fastboot devices
Does your device serial number show up? I'm pretty sure it does, since you're able to re-lock and unlock bootloader. I'm guessing you're using wugfresh toolkit on 64 bit windows.
Try to downgrade to JB 4.3, if this works, you can update to 4.4.3 via OTA.
https://developers.google.com/android/nexus/images#razorg
Download the JB 4.3 image above and extract all files to
C:\Program Files (x86)\WugFresh Development\data
Run the below commends manually in a dos prompt.
Code:
cd C:\Program Files (x86)\WugFresh Development\data
fastboot flash bootloader bootloader-deb-flo-03.14.img
fastboot reboot-bootloader
fastboot flash radio radio-deb-deb-g00_1.23.0_0720.img
fastboot reboot-bootloader
fastboot update image-razorg-JLS36C.zip
Then boot to recovery and factory reset.
Reboot tablet and hope for the best.
Click to expand...
Click to collapse
Thanks for the tip. Happy to say that I was able to RELOCK the bootloader so atleast I have a better chance at Asus honoring the warranty.
Weird thing: couldn't get the bootloader UNLOCKED. It just hangs for about 15 minutes and then says FAILED.
At this point, I simply cannot get the bootloader to write anything or replace current bootloader. Never heard of this issue. No idea how it can be resolved without RMA.

Yeah, looks like it's gone. Good luck with the RMA.

Hey gang!
So I got it to work! yay. tried everything mentioned here, but no luck. Last thing I've tried was manually flashing 4.3. Nothing
Today a guy from the office took it apart and disconnected the battery. Connected it back and booya it's loading.
Surprisingly it loaded 4.3 so flashing was successful but something was preventing it from loading.
Nice to be back, I was kind of getting tired of using my phone for browsing internets from my couch

Interesting, reminds me of a similar problem with the nexus 4 called the red light of death.
Glad it's working fine again.

Really Bricked m9... Please Pro help required.

My M9 suddenly hang und went off... so ok i rebooted. but after boot animation off again.
i can boot into recovery and bootloader and download, but nothing else. ruu fails on pc and on sd. twrp shows system partition as 0Mb. i think something fckd up partition tables or so. i think i need a real pro to get this baby running again or at least to make it look like stock for return. if i try to flash stock recovery in download mode it says finished but still twrp on it. please please help me.
I was running Leedroid rom plus kernel.
device ist supercid and soff

nobody?? :'(

Sashtheflash said:
My M9 suddenly hang und went off... so ok i rebooted. but after boot animation off again.
i can boot into recovery and bootloader and download, but nothing else. ruu fails on pc and on sd. twrp shows system partition as 0Mb. i think something fckd up partition tables or so. i think i need a real pro to get this baby running again or at least to make it look like stock for return. if i try to flash stock recovery in download mode it says finished but still twrp on it. please please help me.
I was running Leedroid rom plus kernel.
device ist supercid and soff
Click to expand...
Click to collapse
Weird. Since you have TWRP, flashing a new ROM sounds like the best option. Maybe a full wipe beforehand? As long as you use a ROM that matches your firmware, it should work.... in theory, at least.

computerslayer said:
Weird. Since you have TWRP, flashing a new ROM sounds like the best option. Maybe a full wipe beforehand? As long as you use a ROM that matches your firmware, it should work.... in theory, at least.
Click to expand...
Click to collapse
since my phone cant find an internal memory i cant flash anything... i think partition tables are ****ed up or so. fastboot flash recovery ends in old state locking bootloader via fastboot results in bootloader still open.
Never had a problem like that and im here since the g1

Yikes. I'm afraid I don't have any further advice. Are there any threads around the M9 forums that talk about corrupted partitions?

Hello, please see my answer on pm regarding help.
Until then, please boot into TWRP and connect to adb and run cat /proc/emmc to get a listing of partitions and their sizes.
Then head over to my firmware thread, find the link to my partition table document and compare with yours. Output should be 100% identical, if not, you're right about your suspicion.
I rather assume you've got a permission / security issue which renders some partitions inaccessible. I doubt they're actually broken.
Please also make sure you always leave precise and concise info on what steps you tried and what the outcome was. This will help keep this short and helpful for others too.

Sneakyghost said:
Hello, please see my answer on pm regarding help.
Until then, please boot into TWRP and connect to adb and run cat /proc/emmc to get a listing of partitions and their sizes.
Then head over to my firmware thread, find the link to my partition table document and compare with yours. Output should be 100% identical, if not, you're right about your suspicion.
I rather assume you've got a permission / security issue which renders some partitions inaccessible. I doubt they're actually broken.
Please also make sure you always leave precise and concise info on what steps you tried and what the outcome was. This will help keep this short and helpful for others too.
Click to expand...
Click to collapse
unfortunately my device wont let me boot in recovery again... now it states: Failed to boot to recovery mode Press Volume up to back to menu.
seems my tries to flash single parts of firmware messed this up

Ok please keep it safe now. Don't do anything else to it for the time being. I can try to connect to it via team viewer tomorrow if you allow me into your machine.
What is your time zone? Will you be having time tomorrow afternoon/evening my time? I'm located in GMT +1 (Germany).

Sneakyghost said:
Ok please keep it safe now. Don't do anything else to it for the time being. I can try to connect to it via team viewer tomorrow if you allow me into your machine.
What is your time zone? Will you be having time tomorrow afternoon/evening my time? I'm located in GMT +1 (Germany).
Click to expand...
Click to collapse
Im from Germany, too ( Heilbronn) Ok i leave my fingers from it until tomorrow. Thank you a lot for trying !!!

im have also m9 dead after flash now my phone read on pc qload any one have idea to rework my phone again ?

logy122 said:
im have also m9 dead after flash now my phone read on pc qload any one have idea to rework my phone again ?
Click to expand...
Click to collapse
Yeah yours is a real brick while the OP's phone is more likely damaged NAND. Two very different things.
QHUSB on your PC when you connect it means you've managed to actually brick it.
For this, you'll need to open the phone and connect it to some special tool like the riff jtag box and rewrite the corrupted bootloader.
@Tecardo can do this for you in Germany. I'm not sure where you are but Tec has all the equipment and skills needed to fix that.

Sneakyghost said:
Yeah yours is a real brick while the OP's phone is more likely damaged NAND. Two very different things.
QHUSB on your PC when you connect it means you've managed to actually brick it.
For this, you'll need to open the phone and connect it to some special tool like the riff jtag box and rewrite the corrupted bootloader.
@Tecardo can do this for you in Germany. I'm not sure where you are but Tec has all the equipment and skills needed to fix that.
Click to expand...
Click to collapse
im also can open phone and replace emmc |> im only need boot file to write to phone and back to work

Yes you need to rewrite aboot. That's only possible with a jtag box and maybe, maybe, under Linux because the qhusb connection has no stable functioning driver on Windows. It's almost impossible to flash anything via qhusb on Windows. It could work in Linux though. I remember having had a half-stable connection to my HTC One S this way, back in 2012. I managed to rewrite the hboot back then. But afaik that never worked on the M7,8,9...
Gesendet von meinem HTC 10 mit Tapatalk

I don't want to start a new thread. I have a similar problem. I have an HTC one M9 S-OFF Unlocked. I returned my phone to stock after doing a nandrod backup. I realised I had a sms backup in the nandroid that I need so I thought I would install twrp and do a restore the nandroid. I installed twrp and afterward it bootlooped when I went to recovery mode. It goes from white HTC screen to black screen an back. I tried to go to download mode to do a fresh install but it bootloops there as well. It also bootloops if I try to turn it off with it connected to power. I have tried installing different version of twrp but I get the same problem. If I install a stock recovery it says failed to boot to recovery mode and stays on the white HTC screen. Does anyone know of a solution

Best way is to flash a RUU.
after, for your nandroid backup, flash twrp (same version you have made the backup) and don't accept supersu at the end if proposed...

bzhmobile said:
Best way is to flash a RUU.
after, for your nandroid backup, flash twrp (same version you have made the backup) and don't accept supersu at the end if proposed...
Click to expand...
Click to collapse
I get the following when I fastboot flash rom "fastboot flash rom /Users/.../Android/OPJAIMG.zip
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1013258477 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 474585325 is not a multiple of the block size 4096
sending sparse 'rom' (521267 KB)...
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
OKAY [ 15.122s]
writing 'rom'...
FAILED (remote: partition table doesn't exist)
finished. total time: 15.140s"

Sneakyghost said:
Yes you need to rewrite aboot. That's only possible with a jtag box and maybe, maybe, under Linux because the qhusb connection has no stable functioning driver on Windows. It's almost impossible to flash anything via qhusb on Windows. It could work in Linux though. I remember having had a half-stable connection to my HTC One S this way, back in 2012. I managed to rewrite the hboot back then. But afaik that never worked on the M7,8,9...
Click to expand...
Click to collapse
It was also possible w/Linux on the One XL. I too have never heard of it working on the M7 and later phones, though I've seen the odd post here claiming it is possible. No examples of anyone having done it, however.

copy the OPJAIMG.zip on the root of your Sdcard and reboot in the booloader and follow the instructions (vol +)...
or
with htc_fastboot
download Htc_fastboot.exe et copy it in your fastboot folder with the OPJAIMG.zip
fastboot oem lock , not needed if you're S-OFF
fastboot oem rebootRUU , to reboot
htc_fastboot flash zip OPJAIMG.zip
fastboot reboot
don't forget to unlock again youre device
djkfree said:
I get the following when I fastboot flash rom "fastboot flash rom /Users/.../Android/OPJAIMG.zip
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1013258477 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 474585325 is not a multiple of the block size 4096
sending sparse 'rom' (521267 KB)...
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
OKAY [ 15.122s]
writing 'rom'...
FAILED (remote: partition table doesn't exist)
finished. total time: 15.140s"
Click to expand...
Click to collapse

bzhmobile said:
copy the OPJAIMG.zip on the root of your Sdcard and reboot in the booloader and follow the instructions (vol +)...
or
with htc_fastboot
download Htc_fastboot.exe et copy it in your fastboot folder with the OPJAIMG.zip
fastboot oem lock , not needed if you're S-OFF
fastboot oem rebootRUU , to reboot
htc_fastboot flash zip OPJAIMG.zip
fastboot reboot
don't forget to unlock again youre device
Click to expand...
Click to collapse
I get bootloop when I fastboot oem rebootRUU

So,
go to download mod (option in the bootloader ) and apply the fastboot command
htc_fastboot flash zip OPJAIMG.zip

Is this fixable? Did I brick this thing?!

Here's my problem...
My Kindle Fire HD (Jem) is stuck on the Kindle Fire boot screen (orange logo, no animation). I haven't been able to get it to mount to any of my computers running various operating systems. More details below.
Here are the steps that made my device like this...
Got root using the latest eploit for 8.5.1 successfully. I confirmed that I did have root level access.
Side loaded FireFlash11
Used FireFlash11 to try installing 2nd-bootloader, TWRP and CM. I got the files from here: http://forum.xda-developers.com/showthread.php?t=2128175
Booted into recovery mode and immediately performed a backup.
When I soft rebooted after the backup I only ever saw the Kindle Fire boot screen (orange logo, no animation).
Some other notes...
In Ubuntu when I hard shut down the device and then start it up I get the message Unable to mount JEM-etc. etc.
In Windows if I when I hard shut down the device and then start it up I see something about JEM-etc etc in device manager for a quick second and then it dissapears.
I tried SoupKit on Ubuntu with no luck. I've tried just about every option but no luck. The device never mounts.
I've never had root on this device before. I just got this device a couple of days ago.
Please help! Thanks in advance for your time and effort!

sotrite5 said:
Here's my problem...
My Kindle Fire HD (Jem) is stuck on the Kindle Fire boot screen (orange logo, no animation). I haven't been able to get it to mount to any of my computers running various operating systems. More details below.
Here are the steps that made my device like this...
Got root using the latest eploit for 8.5.1 successfully. I confirmed that I did have root level access.
Side loaded FireFlash11
Used FireFlash11 to try installing 2nd-bootloader, TWRP and CM. I got the files from here: http://forum.xda-developers.com/showthread.php?t=2128175
Booted into recovery mode and immediately performed a backup.
When I soft rebooted after the backup I only ever saw the Kindle Fire boot screen (orange logo, no animation).
Some other notes...
In Ubuntu when I hard shut down the device and then start it up I get the message Unable to mount JEM-etc. etc.
In Windows if I when I hard shut down the device and then start it up I see something about JEM-etc etc in device manager for a quick second and then it dissapears.
I tried SoupKit on Ubuntu with no luck. I've tried just about every option but no luck. The device never mounts.
I've never had root on this device before. I just got this device a couple of days ago.
Please help! Thanks in advance for your time and effort!
Click to expand...
Click to collapse
Completely power off the Kindle (hold power button for 10 seconds), and then type fastboot -i 0x1949 getvar product into the terminal. Plug in the Kindle as soon as you get the <waiting for device> message. after a few seconds, you should get a string beginning with "Jem-PVT". If you do, download the 2nd bootloader, etc. from Hashcode's thread and flash them as directed in step 5. After that, follow the directions to reboot into TWRP, and your recovery process should be complete.
Sent from my Amazon Jem using XDA Labs

monster1612 said:
Completely power off the Kindle (hold power button for 10 seconds), and then type fastboot -i 0x1949 getvar product into the terminal. Plug in the Kindle as soon as you get the <waiting for device> message. after a few seconds, you should get a string beginning with "Jem-PVT". If you do, download the 2nd bootloader, etc. from Hashcode's thread and flash them as directed in step 5. After that, follow the directions to reboot into TWRP, and your recovery process should be complete.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Thanks for taking the time to post, monster. Unfortunately this doesn't work for me. In fact, before I ever changed a thing on my device fastboot wasn't working for me (just ADB), in spite of everything being properly installed on my computer. Could this be an issue with 8.5.1? Any other thoughts?

sotrite5 said:
Thanks for taking the time to post, monster. Unfortunately this doesn't work for me. In fact, before I ever changed a thing on my device fastboot wasn't working for me (just ADB), in spite of everything being properly installed on my computer. Could this be an issue with 8.5.1? Any other thoughts?
Click to expand...
Click to collapse
If you've got ADB enabled on your Kindle (settings -> security if I remember correctly?), you should be able to type adb reboot bootloader and have it boot into fastboot without a hitch.
Sent from my Amazon Jem using XDA Labs

monster1612 said:
If you've got ADB enabled on your Kindle (settings -> security if I remember correctly?), you should be able to type adb reboot fastboot and have it boot into fastboot without a hitch.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Although I did have ADB enabled on my Kindle, I am no longer able to communicate with it via ADB since using FireFlash11 to install the 2nd-bootloader, TWRP and CM. The Kindle now does not appear when I type adb devices (although it always had before using FireFlash).

Alright, I think I'm just going to return this one. I have lost all hope. Were the steps that I took above flawed? I'd consider purchasing this same device, but I need to know the mistake that I made. Can anyone tell me?

sotrite5 said:
Alright, I think I'm just going to return this one. I have lost all hope. Were the steps that I took above flawed? I'd consider purchasing this same device, but I need to know the mistake that I made. Can anyone tell me?
Click to expand...
Click to collapse
I wouldn't give up just yet. Try repeating the same directions I gave you, expect from Linux (Ubuntu) this time as opposed to Windows.
Sent from my Amazon Jem using XDA Labs

*EDIT #2 - WE DID IT, BOYS! I just want to say god bless the following:
monster
hashcode
goldenbullet
cyanogenmod
my mother
america
Monster, thanks for all of your help. I will name my first born male child after you. You earned it.
*EDIT I MADE IT INTO RECOVERY by using "fastboot -i 0x1949 oem recovery" once in fastboot mode. I'll continue with your instructions now.!
Well, fastboot worked and so I got excited for a second there but unfortunately I'm stuck again. I successfully followed all of the instructions in step 5, but unfortunately I am still stuck on the orange kindle fire boot-screen. The logo never becomes blue....
I am not able to get into recovery by holding the up and/or down volume buttons
I am not able to get into recovery via terminal yet. I can still see "fastboot mode" with the blue arrow when I issue the "fastboot -i 0x1949 getvar product" command, but it does not respond when I issue commands like "fastboot boot kfhd8-twrp-2.8.7.0-recovery.img" or fastboot flash recovery kfhd8-twrp-2.8.7.0-recovery.img" -- always just "waiting for device".
The device appears in Ubuntu's launcher as Jem PVT 04 (ONLY when in fastboot mode), but when I try to access it I get an error message about it being inaccessible.
The device still does not respond to ADB
Any other ideas?
Code:
[email protected]:~/Downloads$ fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
< waiting for device >
target reported max download size of 1006632960 bytes
sending 'bootloader' (243 KB)...
OKAY [ 0.022s]
writing 'bootloader'...
OKAY [ 0.042s]
finished. total time: 0.063s
[email protected]:~/Downloads$ fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
target reported max download size of 1006632960 bytes
sending 'boot' (8173 KB)...
OKAY [ 0.546s]
writing 'boot'...
OKAY [ 0.572s]
finished. total time: 1.118s
[email protected]:~/Downloads$ fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8173 KB)...
OKAY [ 0.531s]
writing 'recovery'...
OKAY [ 0.566s]
finished. total time: 1.097s
[email protected]:~/Downloads$ fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.050s

sotrite5 said:
*EDIT #2 - WE DID IT, BOYS! I just want to say god bless the following:
monster
hashcode
goldenbullet
cyanogenmod
my mother
america
Monster, thanks for all of your help. I will name my first born male child after you. You earned it.
*EDIT I MADE IT INTO RECOVERY by using "fastboot -i 0x1949 oem recovery" once in fastboot mode. I'll continue with your instructions now.!
Well, fastboot worked and so I got excited for a second there but unfortunately I'm stuck again. I successfully followed all of the instructions in step 5, but unfortunately I am still stuck on the orange kindle fire boot-screen. The logo never becomes blue....
I am not able to get into recovery by holding the up and/or down volume buttons
I am not able to get into recovery via terminal yet. I can still see "fastboot mode" with the blue arrow when I issue the "fastboot -i 0x1949 getvar product" command, but it does not respond when I issue commands like "fastboot boot kfhd8-twrp-2.8.7.0-recovery.img" or fastboot flash recovery kfhd8-twrp-2.8.7.0-recovery.img" -- always just "waiting for device".
The device appears in Ubuntu's launcher as Jem PVT 04 (ONLY when in fastboot mode), but when I try to access it I get an error message about it being inaccessible.
The device still does not respond to ADB
Any other ideas?
Code:
[email protected]:~/Downloads$ fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
< waiting for device >
target reported max download size of 1006632960 bytes
sending 'bootloader' (243 KB)...
OKAY [ 0.022s]
writing 'bootloader'...
OKAY [ 0.042s]
finished. total time: 0.063s
[email protected]:~/Downloads$ fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
target reported max download size of 1006632960 bytes
sending 'boot' (8173 KB)...
OKAY [ 0.546s]
writing 'boot'...
OKAY [ 0.572s]
finished. total time: 1.118s
[email protected]:~/Downloads$ fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8173 KB)...
OKAY [ 0.531s]
writing 'recovery'...
OKAY [ 0.566s]
finished. total time: 1.097s
[email protected]:~/Downloads$ fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.050s
Click to expand...
Click to collapse

Many years later and I find this post still helpful and it saved my KFHD8.9. I had this same issue with a KFHD 8.9 that I had repurposed to a photo frame. I flashed a new ROM to it, thinking it my photo frame app might run better on a different ROM. Only I hadn't flashed a ROM for a few years and got sloppy with the flashing sequence and wound up stuck at the Kindle Fire orange logo. I spent hours reading XDA posts and trying things to get fastboot and adb to get into the device during the roughly 2 or 3 second bootup window before it gets stuck. The problem is that the way windows 10 and windows 7 handle the USB drivers makes it almost impossible. I made an Ubuntu USB stick to boot from and loaded up fastboot, adb and the android usb drivers and was able to get my KFHD into fastboot mode instantly. Once there, it was simply a matter of running the fastboot commands above and I then I was in recovery and able to restore from a backup.
Many thanks!!!

---Delete----

Stuck in bootloader

Hi, hoping to get some help here. I did some quick google searching and didn't see anything specific to the pixel.
I used Skipsoft android toolkit to unlock and root my pixel xl. Shortly after I started to have some issues and was forced to do a factory reset which I believe removed root (and I'm not sure if it screwed something up with the bootloader or not) but I've never been able to get to stock recovery. For other reasons I was shipped a replacement pixel and now I need to ship this one back. I needed to revert it back to stock before I send it back. Since it didn't have root, i used Skipsoft toolkit to relock the bootloader. I was presented with a screen on the pixel asking if I wanted to relock the bootload (i had to use vol. buttons to move between yes and no and use power to select).. I selected Yes and hit the volume button. Now my phone won't boot any longer. I can get to the bootloader.. or if I try starting the phone I get a message saying my device is corrupt. It can't be trusted and may not work properly. (if its plugged into my computer or whatever I see a battery charging icon for about 10 seconds then the screen goes blank) if the phone isn't plugged into anything after the corruption notice it just goes to a blank screen.
I'm not a complete noob as I've been around rooting my devices for years but at the same time, I am no expert. Does anyone know or can anyone offer any suggestions how I can get the device back up and running stock?
Thanks in advance for any suggestions or tips!

Will it not boot into recovery from the bootloader menu?
Edit: just realised you said you've relocked the bootloader! Might have been a big nail in the coffin.
Sent from my Pixel XL using Tapatalk

Popped, hopefully Google charges you for your fraudulent warranty claim

ko0ky said:
Hi, hoping to get some help here. I did some quick google searching and didn't see anything specific to the pixel.
I used Skipsoft android toolkit to unlock and root my pixel xl. Shortly after I started to have some issues and was forced to do a factory reset which I believe removed root (and I'm not sure if it screwed something up with the bootloader or not) but I've never been able to get to stock recovery. For other reasons I was shipped a replacement pixel and now I need to ship this one back. I needed to revert it back to stock before I send it back. Since it didn't have root, i used Skipsoft toolkit to relock the bootloader. I was presented with a screen on the pixel asking if I wanted to relock the bootload (i had to use vol. buttons to move between yes and no and use power to select).. I selected Yes and hit the volume button. Now my phone won't boot any longer. I can get to the bootloader.. or if I try starting the phone I get a message saying my device is corrupt. It can't be trusted and may not work properly. (if its plugged into my computer or whatever I see a battery charging icon for about 10 seconds then the screen goes blank) if the phone isn't plugged into anything after the corruption notice it just goes to a blank screen.
I'm not a complete noob as I've been around rooting my devices for years but at the same time, I am no expert. Does anyone know or can anyone offer any suggestions how I can get the device back up and running stock?
Thanks in advance for any suggestions or tips!
Click to expand...
Click to collapse
trying to use the toolkit to download and install google factory stock image and I'm getting the following errors..
Flashing update image..
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1608281716
Baseband Version.....: 8996-012511-1609150631
Serial Number........: H*
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.050s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boota' (26481 KB)...
OKAY [ 0.842s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist)
finished. total time: 1.296s
An error occured when flashing the image

DaveHTC200 said:
Will it not boot into recovery from the bootloader menu?
Edit: just realised you said you've relocked the bootloader! Might have been a big nail in the coffin.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
i've managed to use the toolkit to unlock the bootloader again. I can get the phone to boot again to android. But I'd like to revert it back to stock. I cannot get it to boot to recovery though.

cwalker0906 said:
Popped, hopefully Google charges you for your fraudulent warranty claim
Click to expand...
Click to collapse
WTF are you talking about? I'm not the guy who was doing warranty claims. Nice try. RMA isn't WARRANTY mister clueless.

You can try "fastboot set_active _a" prior to running the script again and see if it'll actually write to slot A
Sent from my Pixel XL using Tapatalk

ko0ky said:
WTF are you talking about? I'm not the guy who was doing warranty claims. Nice try. RMA isn't WARRANTY mister clueless.
Click to expand...
Click to collapse
Sure, either way since I'm so clueless...if you read the toolkit thread you would have seen it doesn't work flashing factory images. Multiple people including myself have had this issue, so read and you will find your answers, also if RMA isn't warrant then what is it, you are exchanging a defective device for a new one... warranty lol have a good day buddy

ko0ky said:
Hi, hoping to get some help here. I did some quick google searching and didn't see anything specific to the pixel.
I used Skipsoft android toolkit to unlock and root my pixel xl. Shortly after I started to have some issues and was forced to do a factory reset which I believe removed root (and I'm not sure if it screwed something up with the bootloader or not) but I've never been able to get to stock recovery. For other reasons I was shipped a replacement pixel and now I need to ship this one back. I needed to revert it back to stock before I send it back. Since it didn't have root, i used Skipsoft toolkit to relock the bootloader. I was presented with a screen on the pixel asking if I wanted to relock the bootload (i had to use vol. buttons to move between yes and no and use power to select).. I selected Yes and hit the volume button. Now my phone won't boot any longer. I can get to the bootloader.. or if I try starting the phone I get a message saying my device is corrupt. It can't be trusted and may not work properly. (if its plugged into my computer or whatever I see a battery charging icon for about 10 seconds then the screen goes blank) if the phone isn't plugged into anything after the corruption notice it just goes to a blank screen.
I'm not a complete noob as I've been around rooting my devices for years but at the same time, I am no expert. Does anyone know or can anyone offer any suggestions how I can get the device back up and running stock?
Thanks in advance for any suggestions or tips!
Click to expand...
Click to collapse
Anyone else having this issue I was able to flash my device using directions from this page. (directly from google). https://developers.google.com/android/images You might have to accept their terms before everything gets displayed. I downloaded the image and ran flashall.bat on my windows box - rebooted the device, then got back to bootloader and ran the cmd to lock the bootloader. Everything is STOCK and good to be returned.

cwalker0906 said:
Sure, either way since I'm so clueless...if you read the toolkit thread you would have seen it doesn't work flashing factory images. Multiple people including myself have had this issue, so read and you will find your answers, also if RMA isn't warrant then what is it, you are exchanging a defective device for a new one... warranty lol have a good day buddy
Click to expand...
Click to collapse
He very clearly said that it was being returned for "other" reasons. Not the flashing fiasco.

wtherrell said:
He very clearly said that it was being returned for "other" reasons. Not the flashing fiasco.
Click to expand...
Click to collapse
You are right, I jumped the gun ,all apologies

wtherrell said:
He very clearly said that it was being returned for "other" reasons. Not the flashing fiasco.
Click to expand...
Click to collapse
thanks for being courtesy and helpful! much appreciated!

ko0ky said:
trying to use the toolkit to download and install google factory stock image and I'm getting the following errors..
Flashing update image..
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1608281716
Baseband Version.....: 8996-012511-1609150631
Serial Number........: H*
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.050s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boota' (26481 KB)...
OKAY [ 0.842s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist)
finished. total time: 1.296s
An error occured when flashing the image
Click to expand...
Click to collapse
Did you solve this problem, I'm getting the same thing. Stuck in bootloop, but somehow managed to get it started, now stuck in "checking for updates"

dabadoo said:
Did you solve this problem, I'm getting the same thing. Stuck in bootloop, but somehow managed to get it started, now stuck in "checking for updates"
Click to expand...
Click to collapse
To flash use the instructions from the Google page :
https://developers.google.com/android/images
Paolo

The other thing is make sure you're using the latest Fastboot. Old fastboots do not have support for the slot system.

Let this be a huge lesson not to go running to tool kits, the one you used is nice for installing the drivers but ultimately simply using the flash-all.bat is infinitely easier to do at this point if adb/fastboot is configured.
Also don't lock the bootloader if you have modified the system at all =/
Edit: You should probably add your solution to the OP to help anyone else that maybe have done something similar.

I am having a similar issue. All I have done is u lock the bootloader through fastboot. No toolkits involved or anything. Simply plugged in, booted bootloader mode then fastboot OEM unlock and rebooted. I am unlocked but noticed I cannot boot stock recovery. It goes to the dead Android icon and simply says no command below it. No amount of pressing the volume keys or anything changes it. Holding power eventually reboots back to Android. Anyone else experiencing this or have a fix , or better yet a reason for this occurring?

powdered_donuts said:
I am having a similar issue. All I have done is u lock the bootloader through fastboot. No toolkits involved or anything. Simply plugged in, booted bootloader mode then fastboot OEM unlock and rebooted. I am unlocked but noticed I cannot boot stock recovery. It goes to the dead Android icon and simply says no command below it. No amount of pressing the volume keys or anything changes it. Holding power eventually reboots back to Android. Anyone else experiencing this or have a fix , or better yet a reason for this occurring?
Click to expand...
Click to collapse
When on the no command screen, have you pressed and held the power button, then the volume up button?
Never fails for me! Trying to press them together I didn't have any luck.
Sent from my Pixel XL using Tapatalk

DaveHTC200 said:
When on the no command screen, have you pressed and held the power button, then the volume up button?
Never fails for me! Trying to press them together I didn't have any luck.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Maybe I didn't do it in the correct manner, I'll give it a go and report back
Update: successful! Power first then volume then release.
Thanks!!

ko0ky said:
i've managed to use the toolkit to unlock the bootloader again. I can get the phone to boot again to android. But I'd like to revert it back to stock. I cannot get it to boot to recovery though.
Click to expand...
Click to collapse
How did you manage to unlock bootloader and reboot phone trough toolkit, im in the same situation here . the phone is locked on verizon. Thankyou

Return LG Nexus 5X to original Google ROM

Hello,
I have an LG Nexus 5X (Bullhead?) running PA 7.3.1-RELEASE (Android 7.1.2). It had PA installed on it when I purchased it from ebay some six months ago.
I really would like to go back to the original Google ROM but am struggling to do this.
I've downloaded SuperSU but when I run it I get "SuperSU SU Binary is occupied" and a "HOW TO SOLVE" button.
Clicking "HOW TO SOLVE" takes me to www supersu dot com faq subinaryoccupied which reassures me that: "Only needs a coffee's time to make it happen" and a Community link and Message Us link. Community Link returns a 502 Bad Gateway response (not very reassuring!), the Message Us link goes to a facebook group (SuperSUofficial). Is this route even worth entertaining? I feel I'm only at the tip of the iceberg in getting my phone returned to factory/OEM status.
Any advise would be most appreciated. (Sorry ,not allowed to post links as I'm under the 10 posts requirement)
Thanks, BloodBaz

Follow #10 in this guide, or #11 if you want to retain the contents of the phone's internal storage. You don't need SuperSU for anything.

Jacquestrapp said:
Follow #10 in this guide, or #11 if you want to retain the contents of the phone's internal storage. You don't need SuperSU for anything.
Click to expand...
Click to collapse
Thanks Jacquestrapp, that looks like exactly what I need. I'll give this a go this week and let you know how I get on. Thank you.

Jacquestrapp said:
Follow #10 in this guide, or #11 if you want to retain the contents of the phone's internal storage. You don't need SuperSU for anything.
Click to expand...
Click to collapse
Thanks Jacquestrapp. I'm struggling at the very first step.
Here's where I'm at:
Step 10 (How To Flash The Factory Images (And Return To Stock)) has the prerequsite that I have to unlock bootloader (section 1).
Gone to section 1
Enabled Developer mode (was already enabled)
Enabled OEM unlocking
Enabled USB debugging
Powered off phone
Booted into Bootloader (Power+Volume Down)
Connected phone to PC via USB cable
Opened command prompt, gone to platform tools but as you can see, I'm not connecting here:
Code:
C:\android\platform-tools>fastboot devices
C:\android\platform-tools>fastboot devices
C:\android\platform-tools>adb devices
List of devices attached
00cad250a0599972 device
C:\android\platform-tools>fastboot reboot
< waiting for any device >
My PC is the latest Windows 10 Pro (64-bit).
I have an LG Nexus 5X (Model LGH791).
And I'm guessing I've not got the right drivers installed but I'm struggling to find where to get them (I'm in the UK)
Here's where I've tried:
Attempt 1:
Followed the same guide to "Google USB Driver Install": https://developer.android.com/studio/run/win-usb.html
which takes me to: "Click here to download the Google USB Driver ZIP file (ZIP)" (latest_usb_driver_winodws.zip 8.3MB).
Downloaded, unzipped.
Gone to Device Manager but my phone doesn't appear under "Portable Devices" or anywhere else in device manager.
Attempt 2:
Gone to LG's website, entered model which lead to this page:
https://www.lg.com/uk/support/softw...00008356&subCateId=CT00008358&modelNum=LGH791
(but alas, no software!)
Can anyone advise on how to get the phone and PC to communicate?
Thanks
Chris

You mentioned that your phone has a custom ROM on it (Paranoid Android), which means it almost certainly has an unlocked bootloader. If you reboot the phone, the first thing you see when it reboots should be a message to this effect, advising you to lock the bootloader.

Jacquestrapp said:
You mentioned that your phone has a custom ROM on it (Paranoid Android), which means it almost certainly has an unlocked bootloader. If you reboot the phone, the first thing you see when it reboots should be a message to this effect, advising you to lock the bootloader.
Click to expand...
Click to collapse
Thanks, yes it does! Sorry, I not good at this. So the pre-req for section 10 is already done.
(I'm assuming I will still need to get adb / fastboot working at some point though).
I'll start looking into section 10 now. Thanks.

Are you connecting the phone to the PC through a USB hub? If so, try connecting directly to one of the PC's built-in USB ports. It's been a while since I first set up my PC for adb/fastboot so I'm not sure what to do about the fact that fastboot doesn't show the phone. I think I used the Android SDK manager, and not the ZIP file, to install the USB drivers.

Jacquestrapp said:
Are you connecting the phone to the PC through a USB hub? If so, try connecting directly to one of the PC's built-in USB ports. It's been a while since I first set up my PC for adb/fastboot so I'm not sure what to do about the fact that fastboot doesn't show the phone. I think I used the Android SDK manager, and not the ZIP file, to install the USB drivers.
Click to expand...
Click to collapse
No, directly onto USB port on top of PC. Tried both ports on top and a USB 3 port in the back. Still no sign of the phone in Device Manager.
I've got a laptop - I will try that next.
After that I will install the Android SDK manager (although I was hoping to avoid this for a one off job).
Thanks.

Okay, so I *think* my laptop is recognising the phone, however I still don't see the phone under Device Manager > Portable Devices or Device Manager > Other Devices (in fact, neither folder exists on my Laptop in Device Manager). However I have got "Nexus 5X" listed under Device Manager > USB Devices.
I'm now following instructions in section 10 of the guide you have given me:
"Download the latest build via the appropriate factory images for your model (Nexus 5X/Bullhead) here (https://developers.google.com/android/nexus/images?hl=en)".
For me this is 8.1.0 (OPM7.181005.003, Oct 2018) under "bullhead" (https://dl.google.com/dl/android/aosp/bullhead-opm7.181005.003-factory-e23fac1c.zip)
I've done the appropriate unzips and copies and I have the following folder set up:
Code:
Volume in drive C has no label.
Volume Serial Number is 1202-7717
Directory of C:\android\images
19/10/2018 22:55 <DIR> .
19/10/2018 22:55 <DIR> ..
01/01/2009 00:00 101 android-info.txt
01/01/2009 00:00 12,068,070 boot.img
21/09/2018 12:04 4,731,396 bootloader-bullhead-bhz31b.img
21/09/2018 12:04 57,989,632 radio-bullhead-m8994f-2.6.41.5.01.img
01/01/2009 00:00 17,847,530 recovery.img
01/01/2009 00:00 2,002,471,632 system.img
01/01/2009 00:00 194,892,768 vendor.img
7 File(s) 2,290,001,129 bytes
2 Dir(s) 136,452,927,488 bytes free
C:\android\images>
The next instruction is to "Boot into the bootloader and connect your phone to your PC via usb cable."
So I shut down my phone then booted it back up again using POWER +VOLUME DOWN buttons to get the screen with the big fat green START option and FASTBOOT mode showing
Connect USB cable to laptop and phone
BUT... now the device isn't showing anymore in Device Manager and running adb devices -l just says "List of devices attached" and nothing underneath!! Grrrrr!
Q1) Should the laptop still be able to communicate with the phone when the phone is booted into the bootloader?
Q2) Could there be something fundamentally wrong with the phone that is causing it not to be recognised?
Booting up the phone and disconnecting and connecting the phone a couple of times re-established the device. This time I was able to run adb reboot bootloader but as soon as the phone starts to shut down for the reboot, the connection to the laptop is lost and the laptop shows an error popup (temporarily) (wish I knew how to keep the popup visible but it was something about an error with the USB device).
Q3) Should I select RECOVERY MODE before I can expect the USB connection to reconnect? Documentation just says to go into bootloader (with the menu)
Any more advice is appreciated. Thanks, Chris

BloodBaz said:
The next instruction is to "Boot into the bootloader and connect your phone to your PC via usb cable."
So I shut down my phone then booted it back up again using POWER +VOLUME DOWN buttons to get the screen with the big fat green START option and FASTBOOT mode showing
Connect USB cable to laptop and phone
BUT... now the device isn't showing anymore in Device Manager and running adb devices -l just says "List of devices attached" and nothing underneath!! Grrrrr!
Click to expand...
Click to collapse
That last command should be fastboot devices, not adb devices.
BloodBaz said:
Q1) Should the laptop still be able to communicate with the phone when the phone is booted into the bootloader?
Click to expand...
Click to collapse
Yes, but using fastboot commands, not adb commands. With the phone in bootloader mode (the green screen with the big Start sign), you should see it listed after the fastboot devices command. Here's what I see:
Code:
C:\adb>fastboot devices
00bc94d02c6ab546 fastboot
BloodBaz said:
Q2) Could there be something fundamentally wrong with the phone that is causing it not to be recognised?
Click to expand...
Click to collapse
The phone's type-C port can collect lint, and plugging the connector into the phone compacts the lint. Over time, the lint layer can build up to the point where the connector no longer makes full contact with the port. I don't think that's your problem though.

@Jacquestrapp, thank you for your replies. You've been a life line.
After a couple of hours I think I've now managed to do it. I've tried two laptops, multiple USB ports and two USB cables. Whatever is happening, the PC/Phone connection seems very tempremental and I have to unplug and replug in the USB cable after each reboot. However, as you say, the fastboot commands did work after I figured this out, and from the fastboot screen. Also, whenever the phone rebooted or I disconnected the USB cable, the error message was as per attached screenshot.
So, I ran the following commands:
Code:
C:\android\platform-tools>adb devices -l
List of devices attached
00cad250a0599972 recovery product:omni_bullhead model:Nexus_5X device:bullhead transport_id:5
C:\android\platform-tools>fastboot flash bootloader C:\android\images\bootloader-bullhead-bhz31b.img
< waiting for any device >
Sending 'bootloader' (4620 KB) OKAY [ 0.212s]
Writing 'bootloader' OKAY [ 0.238s]
Finished. Total time: 0.493s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader OKAY [ 0.009s]
Finished. Total time: 0.011s
C:\android\platform-tools>fastboot flash radio C:\android\images\radio-bullhead-m8994f-2.6.41.5.01.img
< waiting for any device >
Sending 'radio' (56630 KB) OKAY [ 1.633s]
Writing 'radio' OKAY [ 0.543s]
Finished. Total time: 2.300s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader OKAY [ 0.013s]
Finished. Total time: 0.014s
C:\android\platform-tools>fastboot flash boot C:\android\images\boot.img
< waiting for any device >
Sending 'boot' (11785 KB) OKAY [ 0.538s]
Writing 'boot' OKAY [ 0.133s]
Finished. Total time: 0.786s
C:\android\platform-tools>
C:\android\platform-tools>fastboot flash recovery C:\android\images\recovery.img
Sending 'recovery' (17429 KB) OKAY [ 0.545s]
Writing 'recovery' OKAY [ 0.309s]
Finished. Total time: 0.900s
C:\android\platform-tools>fastboot flash system C:\android\images\system.img
Sending sparse 'system' 1/4 (508768 KB) OKAY [ 13.739s]
Writing sparse 'system' 1/4 OKAY [ 9.283s]
Sending sparse 'system' 2/4 (524230 KB) OKAY [ 14.787s]
Writing sparse 'system' 2/4 OKAY [ 8.650s]
Sending sparse 'system' 3/4 (501070 KB) OKAY [ 14.592s]
Writing sparse 'system' 3/4 OKAY [ 12.445s]
Sending sparse 'system' 4/4 (421469 KB) OKAY [ 11.842s]
Writing sparse 'system' 4/4 OKAY [ 16.174s]
Finished. Total time: 112.698s
C:\android\platform-tools>fastboot flash vendor C:\android\images\vendor.img
Sending 'vendor' (190324 KB) OKAY [ 5.424s]
Writing 'vendor' OKAY [ 5.682s]
Finished. Total time: 11.145s
C:\android\platform-tools>fastboot reboot
Rebooting
Finished. Total time: 0.012s
The pre-google animation too ages and eventually talked about corruption on the filesystem. This is presumably because it had Paranoid Android installed on it previously. So I took the option to wipe everything (I don't have anything precious on the phone that isn't already backed up) and I've got myself back to stock Google and I'm very happy!
Thanks again for your support @Jacquestrapp.
The only thing I haven't done yet is relock the bootloader.
The guide states this warning:
"Important: do not relock your bootloader unless your phone is fully stock. You must flash the factory images first in order to remove root and custom recovery (if you have them), if this precaution isn't taken you may end up with a brick. Please see section 10 of this guide for full instructions on how to return to stock"
Now that I am booting up fine in standard Google Android 8.1, is it okay for me to issue the fastboot oem lock command? I'm not going to kill my phone am I? If it's a "yes", then I'll probably leave it a few days before I actually do it.
Thanks

BloodBaz said:
[MENTION=301158]
The only thing I haven't done yet is relock the bootloader.
The guide states this warning:
"Important: do not relock your bootloader unless your phone is fully stock. You must flash the factory images first in order to remove root and custom recovery (if you have them), if this precaution isn't taken you may end up with a brick. Please see section 10 of this guide for full instructions on how to return to stock"
Now that I am booting up fine in standard Google Android 8.1, is it okay for me to issue the fastboot oem lock command? I'm not going to kill my phone am I? If it's a "yes", then I'll probably leave it a few days before I actually do it.
Thanks
Click to expand...
Click to collapse
You're welcome. I *think* you are OK to re-lock the bootloader, but I've never done it, so I can't say with 100% certainty. Both of the 5Xs in my house have been running custom ROMs since I bought them. Also, if the USB connection is as temperamental as you say, take a toothpick (or something else thin and non-conductive) and poke around gently in the USB port to see if lint is the problem. It probably isn't, but it's easy enough to fix if it is: just dig all the lint out.