I have a Google Fi edition X4, and I may have bricked it. What led to me trying it is that we just got a new ISP and an Eero setup, and the phone just isn't working well with the wifi. My daughter has a retail / Amazon X4, and she's had no problems. I thought flashing it to a different ROM might help. Obviously I screwed up somewhere.
I've been following the instructions at https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
The ./fastboot devices command works just fine, and it finds the device. I can run other fastboot commands such as ./fastboot getvar all.
However, when I ran the flash-all.sh script, I get a bunch of errors. I've tried again using the Google Fi ROM linked from the article. Here's a sample of the errors I see:
Setting current slot to 'a' FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:modem_a: not found
(bootloader) is-logical:fsg_a: not found
. . . lots of things not found. I also get a big block when it tries to do the system:
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
When the phone reboots, I get a setup screen, where it first asks if I have a SIM (I took it out) then it tries to setup wifi, but can't find anything.
Of course, I didn't make a backup before doing any of this. I think somewhere in my subconscious I may be looking for an excuse to get a new phone or something. Any ideas of what I should try next?
Do you have qcn or efs backup , if you have then can you provide that
Related
Hello everyone.
I am hoping someone might be able to help me out.
I had been using the sensation for a while with the s-off bootloader with no problems.
Recently I tried to update it to see how it would work on the lolipop builds that are out.
I updated the recovery to 2.8.3.0 TWRP and tried to flash the rom.
It looked like it completeled normally but when I went to restart the phone it will only boot into the fastboot of the boot loader. I can not get it to boot into the rom or recovery.
I have tried to reflash the recovery using fastboot but get the following error:
FAILED (remote: image update error)
I used the command (fastboot flash recovery recovery.img) to try and flash a previous one that worked.
I can use fastboot to boot the recovery though and then it will load.
But when the recovery is loaded or by using the adb terminal I can not access any of the partitions.
It seems like the partition table is corrupted.
I have been trying to find a hboot to reflash but I also can not seem to use the command
fastboot OEM reboot RUU
That command gives me the following error
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) erase sector 130560 ~ 131071 (512)
(bootloader) emmc_erase(1852): sd_write_sector failed!
OKAY [ 0.081s]
finished. total time: 0.082s
Currently the phone is on Firmware 3.33
s-off
hboot 1.27.110
Does anyone know where I might be able to find the firmware / hboot to reflash to see if that fixes the partitions on the phone?
Or any other way to fix this?
I am finding it hard to try and dig up files that have working links for this device anymore.
If I am not mistaken, reflashing the firmware should be able to fix it though.
I think I might need to find the RUU and just reflash back to stock and am waiting on the download for that as we speak. Just dreading going through and rerooting the phone again.
The wire part was really tricky.
Any help would be greatly appreciated.
Thank you for your time to read this.
TheArtiszan said:
Hello everyone.
I am hoping someone might be able to help me out.
I had been using the sensation for a while with the s-off bootloader with no problems.
Recently I tried to update it to see how it would work on the lolipop builds that are out.
I updated the recovery to 2.8.3.0 TWRP and tried to flash the rom.
It looked like it completeled normally but when I went to restart the phone it will only boot into the fastboot of the boot loader. I can not get it to boot into the rom or recovery.
I have tried to reflash the recovery using fastboot but get the following error:
FAILED (remote: image update error)
I used the command (fastboot flash recovery recovery.img) to try and flash a previous one that worked.
I can use fastboot to boot the recovery though and then it will load.
But when the recovery is loaded or by using the adb terminal I can not access any of the partitions.
It seems like the partition table is corrupted.
I have been trying to find a hboot to reflash but I also can not seem to use the command
fastboot OEM reboot RUU
That command gives me the following error
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) erase sector 130560 ~ 131071 (512)
(bootloader) emmc_erase(1852): sd_write_sector failed!
OKAY [ 0.081s]
finished. total time: 0.082s
Currently the phone is on Firmware 3.33
s-off
hboot 1.27.110
Does anyone know where I might be able to find the firmware / hboot to reflash to see if that fixes the partitions on the phone?
Or any other way to fix this?
I am finding it hard to try and dig up files that have working links for this device anymore.
If I am not mistaken, reflashing the firmware should be able to fix it though.
I think I might need to find the RUU and just reflash back to stock and am waiting on the download for that as we speak. Just dreading going through and rerooting the phone again.
The wire part was really tricky.
Any help would be greatly appreciated.
Thank you for your time to read this.
Click to expand...
Click to collapse
Okay so the only good news I can see is that if you can make the RUU run it will not s-on your phone so rooting will be easy but, if fastboot oem reboot RUU doesn't work then your in alot of trouble. When you download the RUU (any I'd one for the sensation of XE will do) run it and then extract the .zip (search on Google if you are unsure how to) when you have that extract everything and then move system.img data.img and anything rom related out of the folder. Your aiming to only have hboot related items and the android txt file in there. Zip it back up by highlighting all the files and make a zip file, not by zipping the folder. Rename the zip file to the device model number with img (i think its pg58img.zip) then pass it to your sdcard and then reboot to hboot.
If your hboot can "update" it will hopefully be able to restore/remake your damaged partition table but if that fails your options are really limited. A J-tag would be able to restore the devices partition tables forcefully but you would need a repair shop to do that.
Sent from my LG-D802 using Tapatalk
heavy_metal_man said:
A J-tag would be able to restore the devices partition tables forcefully but you would need a repair shop to do that.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
or if you know what to do about jtag method see here
http://forum.xda-developers.com/showthread.php?t=2775115
Yeah I think I'm toast then.
I tried grabbing the default Rom .zip and flash with boot loader and that failed.
Not sure if it needed to be on a gold card or not though.
TheArtiszan said:
Yeah I think I'm toast then.
I tried grabbing the default Rom .zip and flash with boot loader and that failed.
Not sure if it needed to be on a gold card or not though.
Click to expand...
Click to collapse
Shouldn't make a difference as you are s-off.
What happens if you issue the command. Fastboot getvar all
Does it work?
Sent from my LG-D802 using Tapatalk
I tried turning on my Shield (WiFi) tablet today and it just stays stuck on the nVidia logo. I tried booting into recovery and it also just sits, stuck on the nVidia logo. I figured it might be corrupted (bad update, possibly), so I decided to restore it to factory settings by using the latest system image files from nVidia on their Dev site. I followed the instructions, but didn't get too far when I needed to unlock my bootloader and it failed, returning:
Code:
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: (Unknown error code))
finished. total time: 14.872s
I have tried 2 computers, 2 USB cables, and still have had no luck getting it to unlock the bootloader to flash the factory image. I also did some digging and found that my bootloader is listed as UNDEF_BUILD and that some people had luck restoring it though flashing the file tegra124-tn8-p1761-1270-a04-e-battery.dtb, but it won't let me do that because it also complains my bootloader is locked.
The tablet is out of warranty, so I really don't want to have to RMA it due to cost. Any ideas or hope of bringing it back to life?
Applied for unlocking at http://en.miui.com/unlock/ and got this:
Apply for unlocking permissions
Sorry, your application has been rejected.
The more active your Mi Account is, the more likely your application will get approved.
Reapply>>
So no way to get unlock code!
Then tried: https://forum.xda-developers.com/mi-4c/general/guide-unlocking-mi4c-bl-verification-t3336779
And it seemed to work, could flash TWRP and CM 13.1
Had problems with radio, tried flashing radio, now I'm stuck in fastboot, can't boot to recovery or anything else, loops back to fastboot.
C:\adb>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.062s]
finished. total time: 0.063s
Any attempt to flash I get: "Partition flashing is not allowed"
Any ideas or should I just enter the "How far can you toss your Xiaomi MI4c contest"?
Your bootloader is re-locked. Follow the unlock procedure again, maybe you flashed the new bootloader.
BTW you don't have to flash the whole rom to change the bootloader, you can just extract it from firmware in zip and run:
fastboot flash aboot emmc_appsboot.mbn
Ydraulikos said:
Your bootloader is re-locked. Follow the unlock procedure again, maybe you flashed the new bootloader.
BTW you don't have to flash the whole rom to change the bootloader, you can just extract it from firmware in zip and run:
fastboot flash aboot emmc_appsboot.mbn
Click to expand...
Click to collapse
Thank you friend Ydraulikos, I have tried flashing boot and recovery before, but I have not tried your version.
Unfortunately this was the result:
C:\adb\images>fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'aboot' (469 KB)...
OKAY [ 0.036s]
writing 'aboot'...
FAILED (remote: Critical partition flashing is not allowed)
finished. total time: 0.083s
SOLVED!
Things looked pretty hopeless, two days without a phone, but managed to return to MIUI 7.1.6.7 and can proceed from here. I'm not saying this is the righ method, it worked for me and perhaps can help others in a similar situation. Have read a lot of posts in the last two days so please forgive me if I can not give credit to all the people whose advice helped, so thank you xda!
Installed QDLoader HS-USB Driver_64bit_Setup recommended in one of the posts and rechecked my drivers in general.
One command that seemed to be promising was "fastboot oem edl"
However, when my phone went to edl mode it was no longer accessible for fastboot <waiting for device>
On advice of another post I downloaded MiFlash2015.10.28.0 and libra_images_6.1.7_20151221.0000.11_5.1.*.tar.gz
From the command line typed "fastboot oem edl" and with MiFlash flashed MIUI 6.1.7, had to choose the "Flash all except data and storage" option as other options gave me a memory error message. Flashing went okay!
So my phone is back in business now!
Hello,
So I have been using my Shield Tablet just fine for the past few years but now its locked on the Nvidia logo when it boots up, I've tried going into recovery mode to factory reset but then it just hangs on "No Command" I noticed that the bootloader is locked so I got ABD and fastboot. Once I setup the tablet to register in fastboot devices, I then use 'fastboot oem unlock' like it says to from the Nvidia support forums, but it fails and gives this command. Can anyone help me out to figure out what is wrong?
.... > fastboot oem unlock
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: '(')
fastboot: error: Command failed
Any advice would be helpful
Malzra said:
Hello,
So I have been using my Shield Tablet just fine for the past few years but now its locked on the Nvidia logo when it boots up, I've tried going into recovery mode to factory reset but then it just hangs on "No Command" I noticed that the bootloader is locked so I got ABD and fastboot. Once I setup the tablet to register in fastboot devices, I then use 'fastboot oem unlock' like it says to from the Nvidia support forums, but it fails and gives this command. Can anyone help me out to figure out what is wrong?
.... > fastboot oem unlock
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: '(')
fastboot: error: Command failed
Any advice would be helpful
Click to expand...
Click to collapse
What happens when fastboot flashing unlock
Hi, I don't know why my old Moto G3 was in an infinit bootloop and I need it to make a baby monitor.
I've tried to flash different stock ROMs downloaded from here, but I can't get it to boot correctly.
When I try to install the ROMs I get errors like this:
Code:
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
1) I think I need to unlock de bootloader, but as I've read, I must enable developer tools from the phone settings menu, and I can't do that with this phone status. So I'm a bit confused right now, is it possible?
2) I also run this command "fastboot getvar al" to find the correct firmware I need to download to make one more try, but I can't find it anywhere! (xt1043_osprey_retla_ds_6.0.1_MPIS24.107-55-2-17_cid12):
Code:
sku: XT1543
ro.build.fingerprint[0]: motorola/osprey_retla_ds/osprey_ud
ro.build.fingerprint[1]: s:6.0.1/MPIS24.107-55-2-17/18:user
cid: 0x000C
Any help will be REALLY appreciated, as I don't know how to continue right now. Thank you