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
Related
I think I bricked my phone but im not sure if its a soft or hard brick. I got the phone and it had Droid 4.2.2 on it and then unlocked the bootloader. I then installed all of the updates to it and then rooted it with TWRP and SU. I got a stock image for my phone for 4.2.2 then I flashed the system image and all was ok when I rebooted the phone It just hung there so I then tried to go into recovery and that worked and I then tried to do a factory reset and it just got stuck in a bootloader loop it would turn on and then the bootloader warning came up and then it would be blank screen and then the bootloader warning would come up again and repeat. I am able to still go into fastboot and TWRP but I did not back up the image. Any ideas...Im a noob and I dont want a 650 dollar paperweight.
Knight71 said:
I think I bricked my phone but im not sure if its a soft or hard brick. I got the phone and it had Droid 4.2.2 on it and then unlocked the bootloader. I then installed all of the updates to it and then rooted it with TWRP and SU. I got a stock image for my phone for 4.2.2 then I flashed the system image and all was ok when I rebooted the phone It just hung there so I then tried to go into recovery and that worked and I then tried to do a factory reset and it just got stuck in a bootloader loop it would turn on and then the bootloader warning came up and then it would be blank screen and then the bootloader warning would come up again and repeat. I am able to still go into fastboot and TWRP but I did not back up the image. Any ideas...Im a noob and I dont want a 650 dollar paperweight.
Click to expand...
Click to collapse
Don't worry. There is no such thing as a soft brick. It's either bricked or its not. If a phone is bricked, it does nothing at all. In your case download the factory images to your pc again to make sure you have a clean download and fastboot flash them onto your device. I'd flash the files individually and restart the bootloader between each file. Then clear the cache and reboot.
Lokke9191 said:
Don't worry. There is no such thing as a soft brick. It's either bricked or its not. If a phone is bricked, it does nothing at all. In your case download the factory images to your pc again to make sure you have a clean download and fastboot flash them onto your device. I'd flash the files individually and restart the bootloader between each file. Then clear the cache and reboot.
Click to expand...
Click to collapse
Ok...I got my phone up and running again. If I told you what I did to get into this situation you would just laugh. So I redone everything typed out the code and 2 items failed...I dont know if this is good or bad but my phone is up and running sort of....
OK..........fastboot oem fb_mode_set
FAILED....fastboot flash partition gpt.bin
FAILED....fastboot flash motoboot motoboot.img
OK..........fastboot flash logo logo.bin
OK..........fastboot flash boot boot.img
OK..........fastboot flash recovery recovery.img
OK.......mfastboot flash system system.img
OK..........fastboot flash modem NON-HLOS.bin
OK..........fastboot erase modemst1
OK..........fastboot erase modemst2
OK..........fastboot flash fsg fsg.mbn
OK..........fastboot erase cache
OK..........fastboot erase userdata
OK..........fastboot erase customize
OK..........fastboot erase clogo
OK..........fastboot oem config carrier vzw
OK..........fastboot oem fb_mode_clear
I then rebooted the phone and went threw the whole set up new phone process. I then unlocked developer mode did the google playstore updates. Meanwhile the phone is downloading OTA update. I did not want to install that update because I am now on 4.2.2 - 12.15.15 because I want to use FoxFi to teather my phone to my laptop using Wifi and KitKat turns off Wifi. I am having some problems with that app because now I have to set a pin password to lock the phone instead of swipe. And the other problem is that when I went back in fastboot and setup TWRP in the recover partition it just keeps rebooting into that partition like a loop not the system partition like it should. So now I dont know how im going to root my phone so I can freeze my OTA update with Titanium Backup. unless there is another way of doing it to get rid of the OTA. But I still want to be rooted im just not sure how to do it now.
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 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.
Hi there, so recently I was forced to update OTA from CM11 to the latest CM13 and it has made my phone unreliable. Problems receiving calls, making calls, mobile internet, etc, etc
So I have been trying to get my phone back working again, and have been introduced to using fastboot to install different versions of CM and also tried Oxygen but none of it seems to fix it.
Not sure what else to try =( any suggestions?
I've been trying to learn from reading this forum but have been getting confused with the terms ROM and firmware. People in some threads saying to flash the ROM then update the firmware. Aren't they the same thing?
Is using the fastboot method as clean an install as you can get? I find using different recoveries confusing at this point so have just been using fastboot as it seems like the most straightforward method. Is the only time you would use TWRP is when you want to keep data?
If I am just trying to fix my phone network functionality, do I just need to flash the modem? or do I need to do ALL 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 oppostanvbk static_nvbk.bin
I read somewhere that I need to wait 5 minutes after turning on the phone following any flashing activity before I should test anything out. Is that right?
Thanks for any help. Hopefully I can get caught up on all this flashing stuff. Seems like every time I need to do some type of flashing (every few years) the whole process changes and I need to relearn the whole process again.
Is anyone experience bootloops on random occasions with android 10 ROMs?
Things work great, played with tons of stuff and when android 10 ROMs appeared I jump to them. With android 9 firmware and android 10 custom ROMs I had no issues except the HEVC issues which were common before they fix this.
So after a while Xiaomi release android 10(miui) and I've put the firmware only and clean flash custom ROMs but after a few weeks I've experience some hard reboots. Random without any reason, bam hard reboot and when it occured it was bootlooping without a stop.
So Xiaomi image(unlocked), rom load and bam again restart, sometimes it booted properly but most of the times the boot loop never stopped UNLESS I force restart faster than the rom logo and enter twrp and shut it off and leave it a few seconds then boot it up ...after that it was working fine until the next boot loop that might occur same day or a few days later
One time it bootloop I enter to twrp fast and it boot looped even in TWRP!!!
This is weird, so let's fastboot the phone and clean everything up. Using Mi flashtool I tried to flash MIUI, after 30+ minutes nothing..it was trying to flash. Oh well. I force restart and enter fastboot and tried again..it finished with error but seemed to flash MIUI properly, clean flash custom ROMs but the issue remains
Anyone have similar experience? After some search some other Xiaomi users have similar issues and use an app called "wakelock" ..I'll see how this goes
P.S. If issue remains I'll fastboot the phone manually(without the mi flashtool), that would be my last resort - Sorry for the long post
P.S.2 usually the bootloop starts when I'm stop using my phone and press the power button to turn off display, it never happened when the phone is on idle
EDIT: Wakelock didn't save anything, got bootloop once again ..tonight I'm gonna try fastboot manual ..hoping for a fix(if it still keeps messing around I'd go back to android 9 where I had no issues at all)
So Xiaomi flash tool failed me if you read my original post, didn't want to risk it again, so I backup up everything and went the old way, it seems the bootloop is fixed, my proximity issues are also fixed(proximity sensor worked on short calls but on long calls the screen remained black - cleaned it as some suggested but the issue was there, now it seems that it's also fixed!!)
So if you have weird behavior just use CMD with fastboot style and write the following(one at a time, or you can create a batch file(bat file) but I strongly recommend that you do it one after another and seek for "success" after each command):
fastboot erase boot
fastboot flash crclist crclist.txt
fastboot flash sparsecrclist sparsecrclist.txt
fastboot flash xbl_ab xbl.img
fastboot flash xbl_config_ab xbl_config.img
fastboot flash abl_ab abl.img
fastboot flash tz_ab tz.img
fastboot flash hyp_ab hyp.img
fastboot flash devcfg_ab devcfg.img
fastboot flash storsec_ab storsec.img
fastboot flash bluetooth bluetooth.img
fastboot flash cmnlib_ab cmnlib.img
fastboot flash cmnlib64_ab cmnlib64.img
fastboot flash modem modem.img
fastboot flash dsp dsp.img
fastboot flash keymaster_ab keymaster.img
fastboot flash logo logo.img
fastboot flash misc misc.img
fastboot flash aop_ab aop.img
fastboot flash qupfw_ab qupfw.img
fastboot flash ImageFv imagefv.elf
fastboot flash vendor vendor.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot erase sec
fastboot flash cust cust.img
fastboot flash boot boot.img
fastboot reboot
P.S. This WILL ERASE your internal data but won't lock bootloader, so back up your photos and files before
Requirements:
1) ADB Installer v1.4.3 (or any adb installer you prefer)
2) Fastboot MIUI rom, I've use "polaris_global_images_V11.0.4.0.QDGMIXM_20200325.0000.00_10.0_global_82f39e53fd"