Develop Bugs

[Q] Bricked my nexus - Fastboot still almost working

I Think my device is lost. It´s locked in boot of my Gummynex rom.
I´m not allowed to flash anything else, it´s like my filesystem is broken.
I have attached som screenshots of the error´s i get in galaxy nexus toolkit 5.6
{
"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 Have also tryed with Odin, but i cant seem to get odin to connect with the phone in fastboot.
If i try to go into recoverymode i get the android man lying on his back with and Red triangle inside.
Hope someone have any idea of what i should try next.

on the phone itself, can you get to bootloader?

Tomcat27 said:
I Think my device is lost. It´s locked in boot of my Gummynex rom.
I´m not allowed to flash anything else, it´s like my filesystem is broken.
I have attached som screenshots of the error´s i get in galaxy nexus toolkit 5.6
I Have also tryed with Odin, but i cant seem to get odin to connect with the phone in fastboot.
If i try to go into recoverymode i get the android man lying on his back with and Red triangle inside.
Hope someone have any idea of what i should try next.
Click to expand...
Click to collapse
Try using fastboot commands to flash the stock img files instead of the toolkit.

jhernand1102 said:
Try using fastboot commands to flash the stock img files instead of the toolkit.
Click to expand...
Click to collapse
But when i download the files from Google´s homepage there is only 1 file.
Shouldn´t it be enough ?
It´s the yakju-imm76d-factory-c6e807a1.tar file for my phone.

Tomcat27 said:
But when i download the files from Google´s homepage there is only 1 file.
Shouldn´t it be enough ?
It´s the yakju-imm76d-factory-c6e807a1.tar file for my phone.
Click to expand...
Click to collapse
extract the files.

But when i extract the files with winrar, i still only get 1 file ?

Tomcat27 said:
But when i extract the files with winrar, i still only get 1 file ?
Click to expand...
Click to collapse
Extract it again.
Sent from my Galaxy Nexus using xda premium

I´ve extracted the files again. now i have 6 img files.
boot
bootloader
radio
recovery
system
userdata
Flashed all the files to the phone, each time i get an error like before, but i can see in the fast boot screen that baseband versions ect. changes.
But unfortunatly the phone still won´t boot.
I have locked it again, and will take it to the store for repair if someone don´t have some good ideas
Thank you in advance

unlock the bootloader ( fastboot oem unlock )
5) Open up Command Prompt or Terminal, navigate to the folder you've extracted it all too and enter the following commands waiting for each to finish
Windows
fastboot-windows flash bootloader bootloader-maguro-primekk15.img
fastboot-windows reboot-bootloader
fastboot-windows flash radio radio-maguro-i9250xxkk6.img
fastboot-windows reboot-bootloader
fastboot-windows -w update image-yakju-icl53f.zip
Linux
./fastboot-linux flash bootloader bootloader-maguro-primekk15.img
./fastboot-linux reboot-bootloader
./fastboot-linux flash radio radio-maguro-i9250xxkk6.img
./fastboot-linux reboot-bootloader
./fastboot-linux -w update image-yakju-icl53f.zip
OSX
./fastboot-mac flash bootloader bootloader-maguro-primekk15.img
./fastboot-mac reboot-bootloader
./fastboot-mac flash radio radio-maguro-i9250xxkk6.img
./fastboot-mac reboot-bootloader
./fastboot-mac -w update image-yakju-icl53f.zip
6) The last step is to lock the bootloader. Restart the phone into the bootloader
7) Open CMD in the location of Superboot and type:
fastboot-windows oem lock

Help Needed
Guys,
I need any help possible although I fear I may be beyond recovery. Basically my Galaxy Nexus is bricked, I had been running 4.0.4 (IMM76D) on it. The phone is rooted and unlocked.
When switching the phone on, all I get is Google and the unlocked keypad. Will not progress further. I can boot into fastboot mode, and sometimes into recovery however although I have files showing on the SD, when I choose them I get a message declaring the path empty.
My main issue is that the handset is not recognised by my computer (running windows 7 and also since yesterday a dual boot of Ubuntu). This results in my Nexus toolkit and the AdamOutler tool being of no use as they do not recognize the device.
Any help/advice will be greatly appreciated as I'm at my wits end

[Q] Flashing firmware error

A friend of mine has a CID 044 and still got ICS since his Bootloader is already unlocked and he doesn't get OTAs
So, he tried to install the Jelly bean firmware from here: http://forum.xda-developers.com/showthread.php?t=1957376
and while writing the commands he ran into a problem, thats what he said happened:
After he wrote the first command [fastboot oem rebootRUU] the phone rebooted into the HTC logo and got stuck there, so he rebooted it again and it rebooted as usual
Then he got it back to fastboot USB, wrote the second command and this is what he got:
{
"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"
}
Anyone knows whats wrong?

You can't run that command in fastboot mode. When he ran 'fastboot oem rebootRUU' the phone should have rebooted to a black screen with the HTC logo - this is normal. While on that screen run the second command to flash the zip (he'll probably have to run it twice because it usually throws an error the first time round).

hopscotchjunkie said:
You can't run that command in fastboot mode. When he ran 'fastboot oem rebootRUU' the phone should have rebooted to a black screen with the HTC logo - this is normal. While on that screen run the second command to flash the zip (he'll probably have to run it twice because it usually throws an error the first time round).
Click to expand...
Click to collapse
Hey, im his friend with the firmware problem.
I did as you said (did it more then twice) and got the next problem:
I cant post photoes here so i'll just copy it
c:\fastboot>fastboot flash zip firmware.zip
sending 'zip' <12875 KB>...
OKAY [ 1.672s]
writing 'zip'...
<bootloader> adopting the signature contained in this image...
FAILED <remote: 99 unknown fail>
finished. total time: 2.281s
Click to expand...
Click to collapse
Any chance you know whats the problem is?
Thanks alot

1. Which version of the firmware are you trying to flash?
2. Did you relock your bootloader before starting? If not, boot back into fastboot, run 'fastboot oem lock' and then try again.

hopscotchjunkie said:
1. Which version of the firmware are you trying to flash?
2. Did you relock your bootloader before starting? If not, boot back into fastboot, run 'fastboot oem lock' and then try again.
Click to expand...
Click to collapse
1. copyed from where i downloaded
x.xx.707.x - Asia WWE (World Wide English)
cidnum: HTC__044
Download:
firmware.zip with hboot 1.36
2. I didnt relock my bootloader before starting,
Now it finnaly worked, but it stuck on the black screen with the htc logo, and it added like a green loading bar that showed that it had finished loading but still stuck on this screen.
Should I wait for something to happend or reboot manually?

Reboot manually (use 'fastboot reboot-bootloader' to get back into the bootloader and unlock it again)

the system has been destroyed

Plz help me what can i do? i dont flash properly my system has been destroyed. i did evething for solved this problem . now i have no option to solve this problem . now what can i do? any one Help me?
i am attached some photos
my image file : ginkgo_in_global_images_V11.0.3.0.PCOINXM
{
"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"
}
_20200214.0000.00_9.0_in_8e42c719e

Flash vbmeta file or try to move files to root directory.

shovan.cc said:
Plz help me what can i do? i dont flash properly my system has been destroyed. i did evething for solved this problem . now i have no option to solve this problem . now what can i do? any one Help me?
i am attached some photos
my image file : ginkgo_in_global_images_V11.0.3.0.PCOINXM
_20200214.0000.00_9.0_in_8e42c719e
Click to expand...
Click to collapse
in fastboot rom there must be a file vbmeta.img....
download latest platform tools first.
extract the plaform tools zip...copy vbmeta.img in this folder,open cmd in this folder path and flash vbmeta with phone in fastboot mode by this command
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after this flash recovery.

if you solve the problem, here the vbmeta: https://mega.nz/#!bUwliDDS!PNCWo68avE9GsyK4JeJgV1zoVIiejh0-gIs1X6MCEPk

Mi Flash should be able to restore your phone to 100% stock, including boot and vbmeta - it could be that the directory is too long. Try placing the fastboot file in your root folder (C:/) and direct Mi Flash Tool towards that.
System has been destroyed should only really show up when you try flashing a ROM without a dummy vbmeta.img

Thx.
CommieColin said:
Mi Flash should be able to restore your phone to 100% stock, including boot and vbmeta - it could be that the directory is too long. Try placing the fastboot file in your root folder (C:/) and direct Mi Flash Tool towards that.
System has been destroyed should only really show up when you try flashing a ROM without a dummy vbmeta.img
Click to expand...
Click to collapse
Thanks For Your Suggestion.. & i Am done This flash Properly.

thank you
the_weird_aquarian said:
in fastboot rom there must be a file vbmeta.img....
download latest platform tools first.
extract the plaform tools zip...copy vbmeta.img in this folder,open cmd in this folder path and flash vbmeta with phone in fastboot mode by this command
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after this flash recovery.
Click to expand...
Click to collapse
thank you you saved me

the_weird_aquarian said:
in fastboot rom there must be a file vbmeta.img....
download latest platform tools first.
extract the plaform tools zip...copy vbmeta.img in this folder,open cmd in this folder path and flash vbmeta with phone in fastboot mode by this command
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after this flash recovery.
Click to expand...
Click to collapse
I am trying my best to perform this action and i cant

Janelas said:
I am trying my best to perform this action and i cant
Click to expand...
Click to collapse
All commands worked but stil stuck on fastboot

Janelas said:
All commands worked but stil stuck on fastboot
Click to expand...
Click to collapse
sorry for the late reply...after vbmeta is successful, did you flash recovery.img?? if after flashing recovery it doesn't enter recovery mode, press vol up + power button then check.

Plz help - trying to flash Stock image from Google

Hi all,
Just wondering if anyone might be able to lend a hand... Im trying to flash back my Pixel C back to stock (currently running TWRP and build from [ROM][UNOFFICIAL][LineageOS]18.
For some reason, when running the flash-all script or manually flashing the Booloader img, it comes back with "writing 'bootloader' failed (remote 'unsupported command')".
The tablet still boots into the Lineage OS (at least its not a brick... yet..) but really like to try and get it back to stock if I can..

if it helps..
{
"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"
}

When running the flash-all bat file:

If you have no working recovery there is no way to fix this problem (at the moment).
Instead, if you have a working recovery, you could use the following fix from adb shell:
fwtool vbnv write dev_boot_fastboot_full_cap 1
See also:
Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command"
Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command" Fixed flashing error "remote: unsupported command" when flashing a Pixel C back to stock I used TWRP and SuperSU to root and modify the buildprops to enable and get...
forum.xda-developers.com

bernardomarx said:
If you have no working recovery there is no way to fix this problem (at the moment).
Instead, if you have a working recovery, you could use the following fix from adb shell:
fwtool vbnv write dev_boot_fastboot_full_cap 1
Click to expand...
Click to collapse
Thanks bernardomarx! That seemed to have done the trick!!
Yeah - Luckily TWRP recovery was still accessable, typed in the command within TWRP Terminal. And followed the post you linked to
Essentially after doing the fwtool command in a cmd window:
>fastboot erase userdata
>fastboot erase boot
>fastboot erase cache
>fastboot erase recovery
>fastboot erase system
Flashed the bootloader:
fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
I then had to extract the img zip file and manually flash each img file:
>fastboot flash system system.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
>fastboot flash cache cache.img
>fastboot flash vendor vendor.img

Many thanks for entering the details of how you recovered your Pixel C. I had the same problem when un-installing TWRP. I did performed the same steps as you, and the tablet is back up and running!
Many thanks for documenting it here!

no recovery mode!!!!!!

my phone only restarting with message ΄΄this phone is unlocked will continue to boot in 5 seconds''''...But i type fast the command (fastboot reboot bootloader) so i get into download mode...now i am trying to flash twrp but nothing happening....i use cmd from this folder...the phone is stucked..cant start..i dont know what happened...i just tryed to put new twrp because i want install new rom....thanks all guys.....
{
"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"
}

'No such partition' means there exist no such partition 'recovery'!!!!!!
don't use exclamation marks!!!!!!
RTFM!!!!!!

what i must do bro

I recommend to read the instructions.
first, set your windows explorer view so you can see file name suffix. unbelievable you didn't do this yet. you can't even differ .img from .zip
this is just common instructions for devices with recovery ramdisk in boot partition. (no guarantee it is suitable for your device)
Code:
fastboot boot twrp.img
adb push twrp-installer.zip /tmp
adb shell twrp install /tmp/twrp-installer.zip

i need to join in powershell for the adb commands ?

cmd.exe is prefered.

what i do wrong...can we just make a reset the phone and start from the begine?
https://github.com/TeamWin/android_device_razer_cheryl about this ? can we make something ?

you are typing invalid commands without any sense.
the first command flashed twrp into boot partition (boot_b) successfully.
now set slot B active slot and reboot. this will bring you in TWRP recovery.
Code:
fastboot --set-active=b
fastboot reboot
once you are in TWRP restore the boot partition from adb shell. do not type commands you don't fully understand!
Code:
adb devices
adb shell
# dd if=/dev/block/bootdevice/by-name/boot_a of=/dev/block/bootdevice/by-name/boot_b
# exit
you have now repaired your boot partition.
now in TWRP proceed with installing TWRP. this will install TWRP into both slots.
Code:
adb push twrp-installer-3.6.0_9-0-cheryl.zip /tmp
adb shell twrp install /tmp/twrp-installer-3.6.0_9-0-cheryl.zip

Τhe device still does not enter into twrp and restarting all the time.this is the all problem,i cant untarstand why the factory twrp disappeared

you probably did not check current slot beforehand, maybe flashed TWRP into wrong slot.
get stock boot.img according to the current ROM and flash into both slots. if phone is working, start from scratch.

what must type to check if this happened ? btw thanks so much for your help.

according to instructions one must boot up android and from adb shell getprop ro.boot.slot_suffix - but it's too late now. you can try these commands from fastboot
Code:
fastboot getvar current-slot
fastboot getvar slot-bootable
fastboot getvar slot-successful
do you have boot.img?

C:\Users\Main User\Desktop\mobrom\platform-tools>adb shell getprop ro.boot.slot_suffix
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb.exe: no devices/emulators found
i dont have boot.img

as stated adb works only in fully booted android (with usb-debugging enabled) or in TWRP recovery.
if you don't have any boot.img congratulations to your first brick.
search in the thread if someone has shared.
TWRP for Razer Phone
https://dl.twrp.me/cheryl Razer Phone Install Instructions Read these instructions and follow them carefully. Failure to do so may result in not being able to update the device in the future and there are no factory images available. The Razer...
forum.xda-developers.com

the phone is unlocked,usb debugging enabled and cant join in TWRP mode or start normally.i can join only into fastboot mode by comand fastboot reboot-bootloader

yes, I know. that's why I said you need to unbrick first. find the proper stock boot.img

(deleted)

i need download the stock boot.img from internet or set with command ?

you need matching boot.img according to the current ROM. you can check ROM buildno from fastboot.
Code:
fastboot getvar ro.build.fingerprint
you can search for ROM on mirrors.lolinet.com and extract zip file.
edit: no Motorola device sorry
Razer Phone Factory Images - Razer Developer Portal
This page contains instructions that allow you to restore your Razer Phone's original factory firmware.
developer.razer.com
found some threads offering boot.img but links are dead
https://forum.xda-developers.com/t/guide-system-restore-using-twrp.3727777
https://forum.xda-developers.com/t/razer-phone-android-9-0-pie-cheryl-p-magisk-twrp-boot.3974325

working link for Oreo
https://forum.xda-developers.com/t/...ll-9-0-gsi-on-razer-phone-on-both-a-b.3883586
there is also LineageOS available
https://forum.xda-developers.com/t/official-lineageos-19-1-for-the-razer-phone.4436937