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).
Hi all.
If you are here, then you have likely experienced issues with custom ROMs not detecting SIM, or you are still experiencing this issue.
I have a XT1562 UK Single-SIM model and have had this problem with EVERY ROM I have tried and it was getting so frustrating.
Over the last few weeks, I have flashed custom ROMs based on CM13 and all have presented the SIM not detected issue. A simple fix was to pop-out the SIM module and reinsert - more often than never, the SIM was detected. Then I would restart (as is often the case with a custom setup) and alas, the SIM was not detectable.
After trying various suggestions from developers, nothing was working until I happened to flash a dualSIM firmware and I haven't looked back. I can now flash EVERY CM13-based ROM with successful SIM detection BUT it takes a few extra steps to get to that stage.
Here are the things you need:
This firmware
This fix
A custom ROM of your choice (Highly recommend crDroid or Temasek)
GAPPS of your choice - I would recommend this
TWRP
Okay - the solution (confirmed working and reliable):
1. Unpack the Firmware into it's own folder
2. Copy across the files to Fastboot folder
3. Restart phone into bootloader (power off first then hold power and volume down)
4. In the Fastboot folder hold shift and right click.
5. Select "open command window here"
6. Connect phone via USB to computer and in command window enter the following commands 1 by 1 making sure "[okay]" is displayed each time:
if nothing happens on screen, then simply use your volume keys on the phone to restart the bootloader
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot​
7. Once completed restart phone and setup as normal.
8. When setup is complete, restart phone into bootloader.
9. Flash TWRP
10. Restart phone into recovery
11. in TWRP, factory reset then flash ROM and GAPPS and DualSIMFix
12. Restart phone and setup. If SIM shows not detected, press "skip" and it should detect after WiFi setup.
Voila! You can now confidently flash ANY CM13-based custom ROM with the added assurance of SIM detection. IF, however, you flash a ROM and SIM is NOT detected, then simply reflash the DualSIMFix.
If this solution works for you, please give credit where it's due - thank me using the thumbs-up icon below AND vote in the poll at the head of this thread
So, you want to say, that i need to flash stock DS ROM
and after that i'll can flash any custom CM13 based ROM and SIM will be detected?
perfectsense72 said:
So, you want to say, that i need to flash stock DS ROM
and after that i'll can flash any custom CM13 based ROM and SIM will be detected?
Click to expand...
Click to collapse
It has worked for me and I have tried everything that has been recommended. Just by determined trial-and-error I have found my solution.
Just to reiterate
and my intention is to generate enough interest to further assist developers of the CM13 custom ROMs.
Click to expand...
Click to collapse
Can you write a sequence of actions? What nuances?
perfectsense72 said:
Can you write a sequence of actions? What nuances?
Click to expand...
Click to collapse
I fastboot flashed XT1562_LUX_RETASIA_DS_6.0_MPD24.65-18.1 (here ); flashed ROM; flashed GAPPS and then flashed DualSIMFix (from here)
I've tested reboots and SIM is detected each time.
I am assuming you know how to flash a stock image - if not let me know.
I am assuming you know how to flash a stock image - if not let me know
Click to expand...
Click to collapse
From PC by fastboot in stock recovery mode, right?
Did you perform any wipe between flashing stocj ROM and flashing CM13 based ROM?
perfectsense72 said:
From PC by fastboot in stock recovery mode, right?
Did you perform any wipe between flashing stocj ROM and flashing CM13 based ROM?
Click to expand...
Click to collapse
Follow this:
1. Unpack the Firmware into it's own folder
2. Copy across the files to Fastboot folder
3. Restart phone into bootloader (power off first then hold power and volume down)
4. In the Fastboot folder hold shift and right click.
5. Select "open command window here"
6. Connect phone via USB to computer and in command window enter the following commands 1 by 1 making sure "[okay]" is displayed each time:
if nothing happens on screen, then simply use your volume keys on the phone to restart the bootloader
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
7. Once completed restart phone and setup as normal.
8. When setup is complete, restart phone into bootloader.
9. Flash TWRP
10. Restart phone into recovery
11. in TWRP, factory reset then flash ROM and GAPPS and DualSIMFix
12. Restart phone and setup. If SIM shows not detected, press "skip" and it should detect after WiFi setup.
13. Enjoy - but please let me know if not quite right.
@perfectsense72 - once you are able to confirm fully working, then I'll amend the OP to reflect necessary details for successful detection, etc. Thanks for trying this.
Thank you, i'll try tomorrow.
I can't confirm your problems with single sim modem.
I have german single sim and had problems after flashing french dual sim stock image and then flash cm13 roms.
Sometimes the boot was fine with detected sim and sometimes without detected sim and with random reboots of the device.
After flashing back a single sim stock and completly boot the stock then flash again crdroid no problems appeared again. All fine with detected sim on every boot.
For now I'm using Pac-ROM (LP) and have no problem, I'll try CrDroid soon and I'll let you know.
Jeso said:
Sometimes the boot was fine with detected sim and sometimes without detected sim and with random reboots of the device.
Click to expand...
Click to collapse
This is what I'm aiming to avoid for those with issues such as this. Every firmware flash produced an error on flashing bootloader. The only one to not present me with the error is the 18.1 DS retasia.
This has, I believe, been the key to my issues as well as other users. I can flash any official firmware and use it perfectly well, it's just the custom MM ROMs that are problematic.
moozer said:
fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
Does it lock the bootloader?
(Sorry for noob question)
axxx007xxxz said:
Does it lock the bootloader?
(Sorry for noob question)
Click to expand...
Click to collapse
No - this just re-introduces the stock bootloader for the firmware
So, it's working. Flash Unoficial CM13 after stock DS asian and no problem, both simcards a detected.
Thanks, moozer.
perfectsense72 said:
So, it's working. Flash Unoficial CM13 after stock DS asian and no problem, both simcards a detected.
Thanks, moozer.
Click to expand...
Click to collapse
You're welcome. Checked rebooting the phone? SIM remains?
You can now flash custom ROMs to your heart's content. No need to fart around with firmware flashes. All that you need to check is SIM detection on setup and if necessary flash the SIMfix.
^^
Yes, SIM remains after reboot, everything is OK
Thanks a lot! Worked perfectly for me aswell. Currently running ResurrectionRemix and I've had no problems with the sim card since.
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?