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

back to stock sense

i am tired to flash this rom
still show me error
i have s-off and unlocked bootloader
any help ?
{
"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"
}

nassimxmax said:
i am tired to flash this rom
still show me error
i have s-off and unlocked bootloader
any help ?
Click to expand...
Click to collapse
umm that doesnt really help, whats your fastboot getvar all, whats rom did you try to flash, your flash commands are all wrong but require the other info in order to see what your doing.

i am running GPe and want to back to stock
i trying to flash this rom https://www.androidfilehost.com/?fid=95916177934518148
but he give me error
i have s-off and unlocked bootloader

nassimxmax said:
i am running GPe and want to back to stock
i trying to flash this rom https://www.androidfilehost.com/?fid=95916177934518148
but he give me error
i have s-off and unlocked bootloader
Click to expand...
Click to collapse
ok when you have downloaded the file, put it in the same folder as ADB and fastboot files and rename it to RUU for ease
you will need to use the HTC_fastboot.exe to flash it, normal fastboot wont flash Lollipop RUU's, get the htc one from here and put in the same folder as your RUU.zip and other adb and fastboot files: https://www.androidfilehost.com/?fid=95916177934550031
then do htese commands:
fastboot oem rebootRUU (phone screen should go black with sliver HTC logo)
htc_fastboot flash zip RUU.zip (YOU MUST USE THE HTC_FASTBOOT to flash the zip, the normal fastboot wont work, now leave it alone to do its thing, takes about 10 mins, no need to issue this command twice as its automatic with the htc_fastboot)
now make sure when its finished and you have a command prompt and that it says successful at the end and OKAY
if so then type fastboot reboot-bootloader
now fastboot reboot

Seanie280672 said:
ok when you have downloaded the file, put it in the same folder as ADB and fastboot files and rename it to RUU for ease
you will need to use the HTC_fastboot.exe to flash it, normal fastboot wont flash Lollipop RUU's, get the htc one from here and put in the same folder as your RUU.zip and other adb and fastboot files: https://www.androidfilehost.com/?fid=95916177934550031
then do htese commands:
fastboot oem rebootRUU (phone screen should go black with sliver HTC logo)
htc_fastboot flash zip RUU.zip (YOU MUST USE THE HTC_FASTBOOT to flash the zip, the normal fastboot wont work, now leave it alone to do its thing, takes about 10 mins, no need to issue this command twice as its automatic with the htc_fastboot)
now make sure when its finished and you have a command prompt and that it says successful at the end and OKAY
if so then type fastboot reboot-bootloader
now fastboot reboot
Click to expand...
Click to collapse
thank you so much i trying to find that htc fastboot but i didin't find it
i understand now i will try

now it work fine
just waiting ^^

[Guide] Persist error fix in YUREKA / PLUS [21-Apr-2016]

PERISIST ERROR IN TWRP WHILE FLASHING ANY ZIP.....? THEN HERE IS THE GUIDE
{
"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 am not responsible for anything that may happen to your phone as a result of installing custom roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.
What is the persist partition?
Persist is partition mounted at /persist. It has ext4 file system. DRM releated files, sensor reg file (sns.reg), wifi and bluetooth mac addresses are stored there.
If you experience the following issues:
1. You get "e: cannot mount /persist" in recovery
2. Can't access to internal storage.
3. Boot loop on Lollipop 5.0 and above
4. IMEI number is lost even after formating cache and fastboot flash cache.img
5. No signal even after formating cache and fastboot flash cache.img
Then your persist partition have to be fixed​
Follow instructions carefully to solve this issue
NOTE : UNLOCK your device bootloader first before doing this
1. Download this " persist file & ADB+&+Fastboot of yureka " provided by @Annabathina
2. extract them in PC
3. open ADB+&+Fastboot of yureka
4. place presist.img file which you have extracted in ADB+&+Fastboot folder
5. Hold shift key and right click on mouse and select Open command window here
6. Connect your device to pc..... and make sure that drivers are installed properly..... ( VERY VERY IMPORTANT )
a. Type : adb devices
If your device is connected you will get it in connected devices list
b. Type : adb reboot-bootloader
Your phone will restart into bootloader.
c. Type : fastboot -i 0x1ebf flash persist persist.img
7. Disconnect your device from PC and REBOOT​
ADB+&+Fastboot : link
persist : link
Useful links
ADB for pc : link
YU usb drivers : link
PdaNet drivers : link
@Annabathina............................for Guide
Ricks ............... for Presist file
YU YUREKA
YU YUREKA PLUS​
XDA:DevDB Information
[Guide] Persist error fix in YUREKA / PLUS [21-Apr-2016], Tool/Utility for the YU Yureka
Contributors
Annabathina
Version Information
Status: Stable
Stable Release Date: 2016-04-21
Created 2016-04-21
Last Updated 2016-04-23

Reserved

Reserved

I dont get a multirom function in the advanced settings menu. Is it because im using twrp 3.0.... Or is it bcoz of persist partition ?
Sent from my AO5510 using XDA-Developers mobile app

After booting into fastboot mode .. i put the commands and then it just says "waiting for device"..

Bazilbycom said:
After booting into fastboot mode .. i put the commands and then it just says "waiting for device"..
Click to expand...
Click to collapse
Have you solved it?

saurav007 said:
Have you solved it?
Click to expand...
Click to collapse
Yes! .. All you have to do is install proper drivers for your device .
Use PDAnet and Google Usb Drivers

Hi,
For me the message is : is not possible to erase this partition
Thanks a lot for your help

still same error.....what to do now..??

Bazilbycom said:
Yes! .. All you have to do is install proper drivers for your device .
Use PDAnet and Google Usb Drivers
Click to expand...
Click to collapse
Earlier i was getting error even after installing all the drivers, all i needed was to update PDAnet on phone as well & it does everything.
Thank you it worked well!

still stucking
i was suffering of problem error persist but using this method it solved the error is gone but not still my device stuck on boot i tried many custom roms stock rom formats and all but still it stuck after 2 of android logo. in twrp recovery in mount option the system, persist, firmware are uncheck .i think it means they are not mount right??? i click many time to check and reboot but still logo stuck problem please give me solution!!!!!!!
Thank You

Can I flash this zip by twrp
Sent from my YU5510 using Tapatalk

vijaysingh1996 said:
Can I flash this zip by twrp
Sent from my YU5510 using Tapatalk
Click to expand...
Click to collapse
This isn't TWRP flashable zip. You have to flash via fastboot (see OP) after extracting the img from downloaded zip file.

Failing on my Pantech Sky Vega Iron 2 IM-A910S (codename: ef63) and bootloader unlocked.
In Fedora Linux the command continues to display "waiting for device" message even though the device is detected by "fastboot devices" command, although its serial number is not displayed and ???????? is display in that place.
While in Windows 7 (64-bit), the following error message is displayed after execution of the command "fastboot -i 0x1ebf flash persist persist.img":
target reported max download size of 1610612736 bytes
sending 'persist' (4324 KB)...
OKAY [ 0.165s]
writing 'persist'...
FAILED (remote: It is not surpport in user build.)
finished. total time: 0.186s
Any one please help...

In my device it showing can't load persist
After typing last line

shekarsahani said:
In my device it showing can't load persist
After typing last line
Click to expand...
Click to collapse
Can you post CMD screenshot?
Make sure the file name is same as in CMD.

Unfortunately I can't is send cmd screenshot it is not uploading..
When I type fastboot -i 0x1ebf flash persist persist.img then it shows error cannot load 'persist.img'

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!

How To Guide [ALL RMX] How to soft unbrick stock ROM with OTA update file (unlocked bootloader needed)

DO IT AT YOUR OWN RISK, I'M NOT RESPONSIBLE
I've just unbricked an RMX3474 (Realme 9 5G with unlocked bootloader) using this method. It was bricked (bootloader boot loop) following a bad downgrade by mistake from RUI4 to RUI3 (there's actually no RUI4 ROM available in .ofp format for the RMX3474GDPR).
QPST/QFIL is a powerful (and therefore dangerous) tool, which is why in my opinion it should be reserved for hard unbrick, i.e. for smartphones that only have access to EDL (Emergency DownLoad) mode. I think its current democratisation is not a good thing. This remains my humble opinion, of course. For a soft bricked smartphone, I'm still looking for a "fastboot" solution. LOL, that's just common sense
So (I call back : unlocked bootloader needed).
1. Download the lastest android-tools : here
2. Download the OTA update for the last stock ROM installed on the smartphone :
2a. realme-ota
2b. Type the command :
Code:
realme-ota -v4 -i IMEI1 IMEI2 --old-method RMX3363 RMX3363_11.firmware.XX_0000_000000000000 RUI_version region
2c. Where : - -i IMEI1 IMEI2 = for your smartphone (optional), firmware = letter of firmware, XX = number of firmware, RUI_version = 2, 3 or 4 and region = your smartphone region
2d. For example, for my smartphone, the last "F" firmware, RUI4 and EUEX region :
Code:
realme-ota -v4 -i IMEI1 IMEI2 --old-method RMX3363 RMX3363_11.F.00_0000_000000000000 4 01000100
2e. Result of the command is : "foreign_my_manifest_RMX3363_11.F.07_3070_202305171723.44.71d53b2c_1_cf16f9cb6b61168cd0959cff607e3b32"
2f. You'll find the download link for the OTA update in the result, just below this line
3. Extract .img files from payload.bin :
3a. payload-dumper-go
3b. Type the command :
Code:
payload-dumper-go /path/to/payload.bin
4. Put all files in the same directory (android-tools & extracted payload .img files)
4a. Example for RMX3363GDPR-F07 :
{
"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"
}
5. Boot your smartphone into bootloader and connect it to the PC USB port
6. You need to enter fastbootd mode (to be authorised to flash critical partitions), so open a terminal and type the following command :
Code:
fastboot reboot fastboot
7. Begin with slot a :
Code:
fastboot --set-active=a
8. Start the flash of the .img files (the number of .img files may vary depending on the smartphone model and the version of OTA update) :
Code:
fastboot flash file1 file1.img
fastboot flash file2 file2.img
fastboot flash file3 file3.img
(... etc)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img
9. Switch to slot b :
Code:
fastboot --set-active=b
10. Relaunch the flash of the .img files
11. Switch slot a back to active :
Code:
fastboot --set-active=a
12. Reboot the smartphone :
Code:
fastboot reboot
Note : I had 2 errors during the flashes (1 on slot a, 1 on slot b, not the same). On slot a, "Writing 'modem_a' FAILED (remote: 'Operation not permitted')". On slot b, I can't remember (a problem of insufficient space for a file). I tried several things but couldn't get round these errors. Nevertheless, the smartphone rebooted correctly with RUI4
After that, you can easily patch boot.img and vendor_boot.img (optional) files with Magisk, flash them again via fastboot and obtain root mode.
Have a nice day !