Hi everyone,
My phone was running perfectly, and nothing was wrong with it.
Yesterday, I tried to reboot it to "Reconvery" mode. But I noticed that the phone was rebooted to "Fastboot" mode.
I thought I might have pressed on "Bootloader" in the reboot menu, so I didn't care about it.
I turned it off, then turned it on again. It booted into "Fastboot" mode immediately.
I tried that multiple time, but it won't boot normally.
I gave up, turned it off and went home to see what might be wrong.
I plugged it into the wall to charge it, and I noticed instead of the charging battery icon, the phone has booted to "Fastboot" mode immediately.
I tried updating the whole system with the original zip file that contains everything.
"cm-11.0-XNPH44S-bacon-signed-fastboot.zip" -This is the file's name.
I rebooted it, hoping it would work. But unfortunately it booted to "Fastboot" mode.
I searched, and didn't find any results that could help me with this problem.
Is there anyway to fix it ? I tried everything and nothing seems to be working.
What was the phone on before it got stuck ? CM12? CM11s? 44 ? 05 ?What modifications had you made ?
yaminoteio said:
Hi everyone,
My phone was running perfectly, and nothing was wrong with it.
Yesterday, I tried to reboot it to "Reconvery" mode. But I noticed that the phone was rebooted to "Fastboot" mode.
I thought I might have pressed on "Bootloader" in the reboot menu, so I didn't care about it.
I turned it off, then turned it on again. It booted into "Fastboot" mode immediately.
I tried that multiple time, but it won't boot normally.
I gave up, turned it off and went home to see what might be wrong.
I plugged it into the wall to charge it, and I noticed instead of the charging battery icon, the phone has booted to "Fastboot" mode immediately.
I tried updating the whole system with the original zip file that contains everything.
"cm-11.0-XNPH44S-bacon-signed-fastboot.zip" -This is the file's name.
I rebooted it, hoping it would work. But unfortunately it booted to "Fastboot" mode.
I searched, and didn't find any results that could help me with this problem.
Is there anyway to fix it ? I tried everything and nothing seems to be working.
Click to expand...
Click to collapse
Did your phone vibrate twice when it booted into fastboot mode? Did you have any errors when you flashed all staffs through fastboot mode especially flashed the static_nvbk.bin ?
If yes, it smelled like you have locked your bootloader by accident.
I have encountered almost the same question the day before. More info in here and there.
I hope it will work.
Cholerabob said:
What was the phone on before it got stuck ? CM12? CM11s? 44 ? 05 ?What modifications had you made ?
Click to expand...
Click to collapse
CYANOGEN 11S, rooted, TWRP recovery
alpha.shining said:
Did your phone vibrate twice when it booted into fastboot mode? Did you have any errors when you flashed all staffs through fastboot mode especially flashed the static_nvbk.bin ?
If yes, it smelled like you have locked your bootloader by accident.
I have encountered almost the same question the day before. More info in here and there.
I hope it will work.
Click to expand...
Click to collapse
The device vibrates twice when I boot it, it boots to fastboot always.
If I plugged it to pc or wall, it boots to fastboot
If I booted to recovery, it boots to fastboot
If I used fastboot reboot command to reboot it, it reboots to fastboot again.
I've just erased "system - cache - boot - recovery" partitions, and installed the whole zip file.
Still, nothing has happened.
Also, this is a link to the zip I've updated the device with:
http://builds.cyngn.com/factory/bacon/cm-11.0-XNPH44S-bacon-signed-fastboot.zip
***EDIT:
My brother did his magic, and downloaded the one of the old version, and flashed everything
http://mirror.lucky.li/android/oneplus/one/firmware/cm-11.0-XNPH25R-bacon-signed-fastboot.zip
This is the one he downloaded. Also, he flashed everything inside the zip with the following:
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata_64g.img
fastboot reboot
And now, it'working like a new one.
But, that idiot unlocked my phone, and I lost everything because of him.
Well, I guess I learned my lesson today.
Related
Tried to return my wif xoom to stock with the official images and ran into a problem. Followed the steps :
adb reboot bootloader
fastboot flash boot boot.img < this flashed Ok
fastboot flash system system.img < adb stuck waiting for xoom .. had to manual reboot the xoom.
Never got to the remaing steps.
Tried several times with the same result, almost. One time after manual reboot
came up with "RSD mode support 3". Had to do a hard reset to recover.
I ended up flashing Tiamet v1.4.0 again.
Maybe I'm doing something wrong here.
RSjagman said:
Tried to return my wif xoom to stock with the official images and ran into a problem. Followed the steps :
adb reboot bootloader
fastboot flash boot boot.img < this flashed Ok
fastboot flash system system.img < adb stuck waiting for xoom .. had to manual reboot the xoom.
Never got to the remaing steps.
Tried several times with the same result, almost. One time after manual reboot
came up with "RSD mode support 3". Had to do a hard reset to recover.
I ended up flashing Tiamet v1.4.0 again.
Maybe I'm doing something wrong here.
Click to expand...
Click to collapse
Are you sure it froze up I mean the system.img does take longer to do than the boot.img.
Have tried RSDLite 5.0? You might want to look into it.
I waited about 10 minutes before the manual reboot. Is 'adb' required before the flash command? The 1st step took about 14sec and based on the size of the files, the system image should flash in less than a minute.
I'll research RSDLite 5.0. Thanks.
UPdate: Today I tried it again and was successful, Xoom now stock and locked.
For info:
boot.img took 15sec to flash
system.img 17 minutes
Recovery.img 20sec
Userdata.img 4 min
erase cache 1.5s
Hope this helps someone.
Long story short I bricked my phone when trying to flash recovery using toolkit. Now my phone won't turn on and recovery is gone as well. Somehow my PC can recognize the phone in fastboot mode although there's nothing showing on the screen.
So I tried the method in this thread:
http://forum.xda-developers.com/oneplus-one/help/wrong-kernel-black-screen-fastboot-adb-t2835696
It shows I flashed everything and it shows green color in the tool but when I checked the partitions, boot.img, recovery.img, userdata.img, system.img, etc are still broken. At that time the bootloader was still unlocked.
Since my computer can still see the phone in fastboot so I tried to flash the original image in fastboot. Again everything went through with no error but the phone still wouldn't turn on and the partitions are still same broken/corrupted. However the bootloader became locked after this. So now I end up with no more solutions. Since bootloader says locked(although boot.img is actually corrupted) I can't flash or do anything in fastboot command.
So I guess I'm really SOL right now... My only hope right now is maybe there will be USB JTAG or Nand flasher but I don't know if anyone can repair that right now.
Any suggestions?
fastboot oem unlock
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot erase recovery
Now use twrp or cwm or whatever
fastboot boot recovery nameofrecovery.img
If your phone boots to recovery you may consider running e2fsck against data and cache partitions through adb shell
Best of luck
Hi
I have Nexus 5 (Hammerhead) 16GB. After Marshmallow latest update my phone begun to restart randomly, So I tried to do factory reset. When I entered recovery mode It did not show android lying on its back with label "No command" , instead It showed standing android with some rotating cube (or gear) on its tummy. I tried to flash factory image in several ways, using nexus root toolkit and fastboot. I even tried different versions of android to flash but no result. My phone still shows Android with rotating gear on its tummy. Today I found this Thread and did everything that was told but no luck. :crying: If anyone could help I would be very grateful. Sorry for my bad English.
What is "everything that was told"? Did you erase everything then flash everything new? How long are you letting it sit with the rotating cube/gear thing?
exninja said:
What is "everything that was told"? Did you erase everything then flash everything new? How long are you letting it sit with the rotating cube/gear thing?
Click to expand...
Click to collapse
thank you for your reply.
I used this commands as it was described
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
fastboot flash radio "name of radio"
fastboot reboot-bootloader
astboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
every operation was successful.
I waited for this rotating gear more than 10 hours, nothing changed Still shows same
When I click power button + up volume key It says "Formatting /data"
Did you erase and reflash userdata img file?
audit13 said:
Did you erase and reflash userdata img file?
Click to expand...
Click to collapse
yes I did that, but still shows Android with rotating gears.
It does not matter whether I start my phone normally or boot a recovery mode It still shows this Android animation.
Does the phone's bootloader remain unlocked after rebooting?
Hey guys, I have a 64gb OnePlus One and it's seems to be stuck on an infinite bootloop(soft-brick). I am able to access both fastboot mode and recovery. My phone's bootloader is unlocked and I have the stock cyanogen recovery presently.
I had run into this issue several times earlier, and was quickly able to resolve it... Either by flashing a different custom rom or factory resetting the phone using TWRP recovery and it all worked out, but this time, nothing seems to work. After reading several guides and watching many videos, I frequently came across that flashing the stock(cm12.1 factory image) would fix the bootlooping issue once and for all, and it turns out and it did work, but only momentarily and it was quite weird infact... After the fastboot flashing process was done, the phone started bootlooping once again and I let it happen for 5-10 mins, after which I gave up and turned it off. But after leaving it off for sometime and then turning it on later, it did boot up once for sometime to the initial boot setup screen, only to start rebooting again.
I gave it some more time to be turned off and the next time I turned it on, it booted normally and everything seemed to be working fine... I installed whatever apps I needed, downloaded music and everything looked great, but then it started crashing into random reboots once again, at random instances, but using the temporary power off technique I talked about earlier, I made it work somehow, until even that stopped working.
I've tried literally every method, even locking and unlocking the bootloader and then flashing stock again... Also... using the single command method mentioned which fixed persist partitions on that phone, and even that was in vain.
Infact, now my phone is in an even worse condition, it won't even make it past the 1+ logo, just keeps on rebooting there. Any help with this issue would be greatly appreciated... Thank you.
Sounds like the exact final stage issue that my friend was having. Finally his phone even bootlooped in fastboot when he was on holiday.
I had the phone with me for a couple of hours when he returned and nothing worked. I couldn't even connect to the pc in the end. I personally think his memory had an issue.
Seems like you tried all you could. Does it stay on in fastboot?
In the end I had my friend rma his phone and Oneplus said the warranty was void because one sticker was slightly red .... complete bull story since the phone was never ever in contact with water or other liquid stuff and they would not answer a single question in regards to that. So my advice if someone else doesn't have a hocus pocus solution is to check if you have warranty and see if you can't see these moisture indicator through the headphone jack and try to go for warranty repair.
Download the latest fastboot signed ROM from here: https://forums.oneplus.net/threads/mirrors-for-official-cyanogen-roms-ota-updates.141825/
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash recovery recovery.img
fastboot flash userdata userdata_64G.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
Hello everyone,
this is about the Nexus 5 16gb.
It has been completely erased and no backup has been done by the previous owner :silly: and he asked for help. I am a complete noob myself and could only do the below listed things thanks to this forum.
It was completely empty when I received it (as far as I can tell), but I can access the bootloader. I put a costum recovery on it with the help of this forum. When in costum recovery mode my computer identifies it as the Nexus 5 with the help of the Google Drivers and the SDK-Android (I presume) I installed previously.
I went to Google and was able to put a factory image on it from their collection of "hammerhead" for Nexus 5 (GSM/LTE).
I tried the 6.0.1 (MOB31E) and installed it via the flash-all.bat via CMD since this version was, according to the owner, installed before. It worked, as far as I could tell - data got copied on the phone.
When I restart the phone, the Google Logo with an opened lock blinks very slowly. The swirly loading screen I have seen on some Youtube videos for this model's OS does not appear. I presume that the phone does not recognize the flashed factory image?
My question is:
Do I need to try all of the factory images from Google until one works? Or is something so fundamentally lost (maybe somewhere in the booting process), that the phone cannot be repaired since the swirly loading screen does not appear?
Do I need to copy something else on the phone besides the factory image for it to start the booting process for the OS that I have installed via the flash-all.bat?
I am very lost - if someone could point me toward the right direction or even just toward the right kind of tutorial, I'd be very grateful.
You can flash the factory image using the following fastboot commands (subtitute file names to match the file names from the unzipped factory image):
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cache cache.img