Develop Bugs

[Q] (Help) Accidently flashed cwm.img to boot

Hello,
I have got a bit tired of waiting for the OTA volume fix and decided to tr and apply it manually.
I made a mistake and used the following command fastboot flash boot cwm.img.
now my nexus just boots into cwm is there any way I can fix this?
Now when I try to use fastboot it just keep saying (waiting for device), and the phone sits in CWM
any help would be appreciated.
Thanks
Cthuluh

You can try these. Factory images. Someone posted about them and I bookmarket them, and downloaded a copy just incase.
http://code.google.com/android/nexus/images.html

Hi,
Awesome I just finished getting them and and all is well
Phew!!!
thanks

Luxferro said:
You can try these. Factory images. Someone posted about them and I bookmarket them, and downloaded a copy just incase.
http://code.google.com/android/nexus/images.html
Click to expand...
Click to collapse
Excellent we have someone to test the script
You could just try flash the boot.img to the boot partition
Code:
fastboot boot boot.img
And if that works
Code:
fastboot flash boot.img

Hi,
I took the battery out for a few minutes and when I put it back in I booted it into fastboot, which it wouldnt do earlier (kept booting cwm).
I then used the instructions supplied in the google factory image download mentioned above.
fastboot flash bootloader bootloader-maguro-primekj10.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxkk1.img
fastboot reboot-bootloader
fastboot -w update image-yakju-itl41d.zip
And all is now well.
lesson learned dont flash while drinking red wine.
Thanks again
Cthuluh

[Q] Is my phone brick? stuck on google boot image

I am not a noob when it comes to android dev, but this has stomped me and I am asking for expert's help. I have a GSM version SGN that I flashed the official yakju ICL53F on it via fastboot. It has been working great for a month now. Suddenly today I felt it was vibrating in my pocket, took it out and discover it was stuck in boot loop--the google sign with the unlocked icon. I waited til I get home to put clockworkmod on it, but when I try to nandroid it first it gave me an error. Then I figure I would just fastboot the stock rom on it again, using fastboot mode like I did before. I even flashed the bootloader, radio, and system image. Still stuck on google icon with screen went blank, vibrate and repeat. Is there anything else I should try? odin mode is also available, but I am not seeing any instructions on it at the developer section so I am reluctuant to try it. I can still adb and fastboot to access my phone...help please?

well I am no noob but I am no expert either. Apparently you cannot
fastboot flash system XXXXstock_image.img, you have to use
fastboot update -w XXXstock_image.img instead.
still I am baffled by why this happened in the first place. I was ready to lock the bootloader back up and send it in for warranty...glad I didn't have to resort to that.

lettcco said:
well I am no noob but I am no expert either. Apparently you cannot
fastboot flash system XXXXstock_image.img, you have to use
fastboot update -w XXXstock_image.img instead.
still I am baffled by why this happened in the first place. I was ready to lock the bootloader back up and send it in for warranty...glad I didn't have to resort to that.
Click to expand...
Click to collapse
I think you are mixing some things up.
The "update" parameter of fastboot is used to flash a group of images inside a zip file to you device.
The "flash" parameter is used to flash a single image to your device.
The following two groups of commands do the same thing:
fastboot update -w image-yakju-icl513f.zip
or
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot erase cache

Help, possibly bricked phone

Hello, I am currently rooted and on stock on pixel xl. I am trying to flash the pure nexus rom. I downloaded through the link in the op, factory reset and flashed through twrp (3.0.2rc1). When I went to reboot, it said OS not installed. Can anyone offer any assistance with this? Needless to say, I didn't reboot with that. I did however do a backup (of stock) prior to this. I decided to restore my backup but when it rebooted it said something about the vender image is not right with this system and to flash the correct image. This is exactly what its saying : Your vendor image does not match the system. Please flash the NOF27C vendor image for your device. I have managed to move the correct image file to the internal storage but from what i read, can only install through twrp.
And when it finished rebooting, now 90% of my apps are crashing, no fingerprint hardware, developer options are not available and I had to reboot back into recovery but its like twrp is gone, it looks like the stock recovery. Somehow it appears there are parts of my stock rom and pure nexus rom combined which is understandbly causing my issues. Right now I am trying to get back to having twrp but am stuck.
I have since tried to reinstall twrp but when I plug my xl into my pc, the pc recognizes it but no storage. I cant move a file from pc to xl because its saying disconnected or not responding. Tried to get a command prompt and when I shift/right click, there is no option. I don't know what else to do.
If anyone has any suggestions, please help. I am freaking over this. Can't use my phone in the state its in.

Sounds far from bricked.
Just entirely screwed up.
FASTboot the latest factory image and then refrain from tinkering for the weekend.
These are the steps i use.
I think a new ADB/FastBoot package was released yesterday you might want to install that.
Execute fastboot commands (assuming the bin is on your PATH)
fastboot flash bootloader c:\_PIXEL_XL_\bootloader.img
fastboot reboot-bootloader
fastboot flash radio c:\_PIXEL_XL_\radio.img
fastboot reboot-bootloader
fastboot flash boot_a c:\_PIXEL_XL_\boot.img
fastboot flash boot_b c:\_PIXEL_XL_\boot.img
fastboot flash system c:\_PIXEL_XL_\system.img
fastboot flash system_b c:\_PIXEL_XL_\system_other.img
fastboot flash vendor c:\_PIXEL_XL_\vendor.img
fastboot flash modem c:\_PIXEL_XL_\modem.img
fastboot reboot
To add TWRP and Root:
fastboot boot c:\_PIXEL_XL_\twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip

[HELP] Moto G5 (XT1672) BootLoop after install firmware

Hey guys!
I install a new firmware on Moto G5 (XT1672), using the RSDLite, and now it stuck on bootloop. This is a version installed -> Moto G5 - Nov 2017 firmware NPP25.137-93
This phone don't have a bootloader unlocked, then downgrade it's not possible.
There's something can I try?
Sorry my bad english.

In fastboot mode
Type command prompt
Code:
fastboot erase user data
Or Flash the entire firmware via fastboot
You do not need an unlocked bootloader to flash firmware via fastboot - no other software is required other than the fastboot drivers

TheFixItMan said:
In fastboot mode
Type command prompt
Code:
fastboot erase user data
Or Flash the entire firmware via fastboot
You do not need an unlocked bootloader to flash firmware via fastboot - no other software is required other than the fastboot drivers
Click to expand...
Click to collapse
Thanks bro, i have tried this, but I didn't have sucess. Via Fastboot, didn't have errors in the process, but phone stuck in bootloop. When I put phone in Fastboot Mode, the information of baseband is blank. Have you seen this? Any idea?

Try installing a custom rom and see if it also bootloops on that, maybe it's an issue with your phone's hardware?
If you're not sure how to install a rom;
1. Flash stock firmware, reboot
2. Flash twrp, boot straight into twrp when flash finishes
3. Disable dm verity via flashable zip on twrp, reboot twrp
4. Flash a stable rom and see if it bootloops again.
Another thought that came to mind is that maybe you messed around by changing the filesystems of the partitions on your device? Because doing so is bound to throw you into a bootloop, so please do not mess around with reformatting them after flashing stock firmware.

Silva Lucas said:
Thanks bro, i have tried this, but I didn't have sucess. Via Fastboot, didn't have errors in the process, but phone stuck in bootloop. When I put phone in Fastboot Mode, the information of baseband is blank. Have you seen this? Any idea?
Click to expand...
Click to collapse
Sorry userdata should have been all one word
So
Code:
fastboot erase userdata
If it doesn't work flash the entire phones firmware via fastboot

I installed linux by a mistake into my nokia 3.2 and now i am stuck in fastboot

I installed Linux by a mistake into my Nokia 3.2 which led me here, I am stuck in fast boot mode I tried multiple solutions like scratching the edl trigger, going to recovery mode, and restarting the bootloader. it only vibrates and reopens the fastboot menu, I cannot install, or perhaps I don't know how to install the default OS, IMG, or whatever you call it I am really new to this kinda stuff, sorry, and I appreciate your help.

I had the same issue after trying to install an incompatible custom ROM the way I fixed it is by:
1- downloading the stock ROM
2- extract it
3- while the phone is in fastboot flash all .img files like this:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
etc...
after flashing all .img files type
Code:
fastboot reboot
and that's it, it might tell you your phone isn't trusted this will go after a system update.

MRza3ter said:
I had the same issue after trying to install an incompatible custom ROM the way I fixed it is by:
1- downloading the stock ROM
2- extract it
3- while the phone is in fastboot flash all .img files like this:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
etc...
after flashing all .img files type
Code:
fastboot reboot
and that's it, it might tell you your phone isn't trusted this will go after a system update.
Click to expand...
Click to collapse
to download the stock ROM just search Nokia 3.2 stock rom