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.
Related
Hi I've owned my one for a few months now and have flashed numerous ROMs since plus I've owned every nexus and have flashed countless roms on them. Yesterday I flashed Aicp on a clean wipe and all of a sudden my phone would get to the setup and reboot. I tried restoring 3 different nandroids and they would boot into the os but I had no access to data or WiFi and my hardware keys wouldn't work except the back key. I managed to get into settings and I'm missing my baseband. So I tried to fastboot the cm11s factory image and all I get is audiofx fc every second. I then did a bit of research and here on xda there were a few others with this issue and read that side loading the color os would bring back the files I lost. I'm now writing this from color os and I do indeed have data back but WiFi does not work and its showing my 64 GB one as a 16gb one. I'm lost what to do from here, will flashing stock cm11s work? I tried flashing liquid and same thing happened again. I'm getting extremely frustrated and do not want to send this in to oppo if I can help it. Any help would be so greatly appreciated.
Sent from my A0001 using XDA Premium HD app
1)Reboot into bootloader
2)reinstall cm11s using fastboot
http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH33R-bacon-signed-fastboot.zip
fastboot flash boot boot.img
fastboot flash userdata userdata_64g.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
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 reboot
3)flash twrp recovery using fastboot
you can download here
http://techerrata.com/file/twrp2/bacon/openrecovery-twrp-2.8.0.1-bacon.img
rename it "recovery.img"
fastboot flash recovery recovery.img
4)boot into recovery
factory reset,advanced wipe-->dalvik,cache,system,data
and flash cm11 rom zip
https://download.cyanogenmod.org/get/jenkins/84302/cm-11-20140921-NIGHTLY-bacon.zip
kenzolo said:
1)Reboot into bootloader
2)reinstall cm11s using fastboot
http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH33R-bacon-signed-fastboot.zip
fastboot flash boot boot.img
fastboot flash userdata userdata_64g.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
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 reboot
3)flash twrp recovery using fastboot
you can download here
http://techerrata.com/file/twrp2/bacon/openrecovery-twrp-2.8.0.1-bacon.img
rename it "recovery.img"
fastboot flash recovery recovery.img
4)boot into recovery
factory reset,advanced wipe-->dalvik,cache,system,data
and flash cm11 rom zip
https://download.cyanogenmod.org/get/jenkins/84302/cm-11-20140921-NIGHTLY-bacon.zip
Click to expand...
Click to collapse
I think its file system problem,because it shows 16gb instead 64gb.Pls also check your imei,probably its 0.
k3mik4l said:
Hi I've owned my one for a few months now and have flashed numerous ROMs since plus I've owned every nexus and have flashed countless roms on them. Yesterday I flashed Aicp on a clean wipe and all of a sudden my phone would get to the setup and reboot. I tried restoring 3 different nandroids and they would boot into the os but I had no access to data or WiFi and my hardware keys wouldn't work except the back key. I managed to get into settings and I'm missing my baseband. So I tried to fastboot the cm11s factory image and all I get is audiofx fc every second. I then did a bit of research and here on xda there were a few others with this issue and read that side loading the color os would bring back the files I lost. I'm now writing this from color os and I do indeed have data back but WiFi does not work and its showing my 64 GB one as a 16gb one. I'm lost what to do from here, will flashing stock cm11s work? I tried flashing liquid and same thing happened again. I'm getting extremely frustrated and do not want to send this in to oppo if I can help it. Any help would be so greatly appreciated.
Sent from my A0001 using XDA Premium HD app
Click to expand...
Click to collapse
Your issue clearly describes what's in this thread here. Have you tried it? What recovery are you using?
Hello,
I have been updating my cyanogenmod 12s using the nightlies for a while now.
While I was updating with the update on the 18th, my phone got stuck at the 'upgrading apps' step and keeps repeating the upgrade for hours.
I accidentally then wiped the phone completely in TWRP while trying to restore the phone.
I lost the backups and OS. The warning saying 'No OS installed' shows up when I try rebooting.
My PC does not show the phone when I connect it via USB. I have nothing on TWRP to install either.
Can anyone please suggest how I should proceed?
Thank you,
Abhi2488
1. If you can boot into fastboot, just download stock CM11S fastboot package (you wont have trouble find it, just search forum) and simply flash it with fastboot, one by one partition.
I will just qoute some instructions from oneplus forum:
"Once you're on ColorOS and want to go to Cyanogenmod 11S, you have a few options. The easiest way if to use a toolkit from http://forum.xda-developers.com/onep...9-gui-t2807418, or you can download an image manually from: http://forum.xda-developers.com/onep...stock-t2826541 and run the following commands in fastboot mode:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
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
Make sure you have the proper image. I accidentally installed the 16GB version on my 64GB OPO first time and obviously didn't get 64GB of space.
That's about it. I think if people are still having problems then it's likely due to drivers, or Windows 7/8 issue. If you're still getting stuck, let me know, I'll see if I can help."
2. If you allready have custom recovery installed, you can try to flash any custom rom from OTG USB disc (you need OTG cable or OTG adapter and USB fat32 formatted disc where you will copy some custom firmware).
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 everybody,
I did a mistake :crying:
On my Mi4 was installed a CyanogenMod 13 ROM. To do this, I resize the phone partitions in the past.
Now I want to update to LineageOS 14.1 but at the installation I got the error: "assert failed cancro.verify baseband mpss.di.4.0 == 1".
At the Lineage Community I found the solution, to install first a newer Stock OS and then the Lineage Rom.
But to install the Stock OS I had to resize the system partitions to the original size.
This article was helping me:
http://en.miui.com/thread-93248-1-1.html
After the successfully resizing, I wanted to flash the cancro_global_images_V8.1.6.0.MXDMIDI_20161230.0000.00_6.0_global
with the FLASHING FASTBOOT MiUI ROMS Guide from xda:
https://forum.xda-developers.com/xiaomi-mi-3/general/guide-flashing-fastboot-miui-roms-t2938279
To flash following parts was successfully:
fastboot flash tz tz.mbn
fastboot flash dbi sdi.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash rpm rpm.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot erase boot
fastboot flash misc misc.img
fastboot flash modem NON-HLOS.bin
The error was displayed by the "fastboot flash system system.img" command:
I think the resizing zip was wrong.
Now my Phone doesn't display anything. Not fastboot with power+volume down or cwm with power+volume up.
Only my PC is showing me a lot of partitions and two images folders:
Please help me!
everything ok
I found a possibility, to restore the phone
with the old MiFlash Tool. The newer one does not work.
I'm not able to post the link.
It's the link inside this thread:
https://forum.xda-developers.com/mi-4/help/hard-bricked-mi-4s-black-screen-t3512501
Almost everything possible with the tools provided at MIUI forums. Let us know if your device booted up. Good luck!
I was running LineageOS 16, the unit went into a bootloop while I was restoring the call and sms history to update it from my main phone. It is something I have been doing weekly for a year now.
I can boot into 'fastboot mode' but not 'recovery mode'.
In fastboot it is recognised by the comand
Code:
fastboot devices -l
. Typing
Code:
fastboot boot /<path_to_file>/twrp-3.3.1-0-bacon.img
puts it back into the bootloop, as does the command
Code:
fastboot reboot-bootloader
.
What can I try next to recover the unit?
Are you hesitant in flashing TWRP instead? Also, use the K-releases of TWRP (see the guide in my signature). They work better opposed to the official releases.
Wrapped with delicious Fajita [emoji896]
I was hoping to recover the unit rather than avoiding re-flashing it.
Is the operating system and all the data lost?
If that is what has happened then I will rebuild, trying the version of TWRP you suggested.
Regards.
alistairrc said:
I was hoping to recover the unit rather than avoiding re-flashing it.
Is the operating system and all the data lost?
If that is what has happened then I will rebuild, trying the version of TWRP you suggested.
Regards.
Click to expand...
Click to collapse
Perhaps the NAND memory sector was damaged, which was very important to boot. It is possible because the memory is overwritten all the time.
Read the entire story of another user who had a similar system loss problem.
The best TWTP was made by The Muppets
twrp-3.2.3-20190125-bacon.img
It is based on a toybox, and not like other TWRP in which there is a busybox. Toybox contains more repair tools and is therefore better than busybox.
have tried to recover using "cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot"
but I get an error when I try the command:
Code:
fastboot flash modem NON-HLOS.bin
error: cannot load 'NON-HLOS.bin'
I am now struggling to find any guides that can help me.
(Most of the guides I have read state "connect phone and boot into fastboot mode" but my unit will not boot to fastboot mode when it is connected.)
I have tried to restore the unit twice using
cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot.zip
First using the all in one tool on a windows 8.1 box, then using these commands on a linux box:
Code:
fastboot oem unlock
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 boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata_64G.img
The phone is still stuck either in a bootloop, or in fastboot mode.
What can I try now?