Develop Bugs

Xperia M flashing CM12.1 is messed up and not working. Please help.

Hi,
I have followed the official wiki to install Cyanogenmod 12.1 nightly builds (December 25, 2015 nightly build) on my xperia M. It all worked well for the first time.
But suddenly after using it for some days happily, when I rebooted the device, the moment the device boots up, all the apps start crashing, causing the device unusable. I tried to reboot but it's still there. So I tried to repeat the process to get rid of this and tried to flash the December 30, 2015 build but somehow it is not working.
When I sideload the update zip file, it starts and gets stuck at 47% for quite long time and then suddenly finishes with (Total xfer: 1.00x ). The instant it goes 100%, the android icon showing "update" process disappears and screen keeps blinking and stays dark but still "adb devices" shows my device connected but the device screen just keeps blinking and nothing shows. I tried "adb reboot" but it throws this error
"error: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device."
the "kill-server" command fails as well and thus, the problem persists.
I also installed open gapps after installing CM12.1 on the very first time. But in all those re-flashes, I skipped flashing it altogether and wiping cache partition, media and data & factory reset, these apps (calendar, music and gmail etc) throw the error the devices boots up. I guess the device is not getting formatted properly and its not being flashed with just the newer image. It gets stuck at 47% for way too long (almost 20 mins or more), while if I remember correctly, it didn't do so on first flashing.
Since I can't use any app when the device is ON, I can't open settings to check anything. Please help me getting rid of this, so that I can enjoy using this awesome ROM.
Thanks in advance.

Soft Bricked - Unable to Sideload OTA

Hi all,
My Nexus 5x (16gb - all stock.) went and soft bricked today. Not sure why - just seemed to start wanting to constantly restart - never making it past the white google text part of the boot process. Not sure if it's an update or hardware. No trauma or dropping of the phone - which makes me think s/w rather than h/w.
I have attempted to install a rescue OTA update (instructions I followed are from technobill - don't have enough posts to add a link). However, when running "adb sideload <file>" I get a "failed to read command" error. Have tired multiple cables/ports however to no avail.
(Recovery screen shows the following build details: 7.0/NBD90W/3239497)
Any ideas?
Thanks.
Somewhat Irked

SomewhatIrked said:
Hi all,
My Nexus 5x (16gb - all stock.) went and soft bricked today. Not sure why - just seemed to start wanting to constantly restart - never making it past the white google text part of the boot process. Not sure if it's an update or hardware. No trauma or dropping of the phone - which makes me think s/w rather than h/w.
I have attempted to install a rescue OTA update (instructions I followed are from technobill - don't have enough posts to add a link). However, when running "adb sideload <file>" I get a "failed to read command" error. Have tired multiple cables/ports however to no avail.
(Recovery screen shows the following build details: 7.0/NBD90W/3239497)
Any ideas?
Thanks.
Somewhat Irked
Click to expand...
Click to collapse
Did your phone just reboot in the middle of doing something innocuous then start bootlooping? Were/Are you on total stock with bootloader locked? If both yes, it is probably hardware issue you are encountering.
Regarding sideloading, did you place your Android recovery in sideload mode?
Did you verify adb can "see" your device using "adb devices"?

SomewhatIrked said:
Hi all,
My Nexus 5x (16gb - all stock.) went and soft bricked today. Not sure why - just seemed to start wanting to constantly restart - never making it past the white google text part of the boot process. Not sure if it's an update or hardware. No trauma or dropping of the phone - which makes me think s/w rather than h/w.
I have attempted to install a rescue OTA update (instructions I followed are from technobill - don't have enough posts to add a link). However, when running "adb sideload <file>" I get a "failed to read command" error. Have tired multiple cables/ports however to no avail.
(Recovery screen shows the following build details: 7.0/NBD90W/3239497)
Any ideas?
Thanks.
Somewhat Irked
Click to expand...
Click to collapse
Well luckily I made this post today.

The more this goes on, the more I believe it to be hardware ...
@sfhub - reasonably innocuous. Had just opened one or 2 apps that morning. Not sure what had updated overnight app/os wise. Not anything interesting as far as I can tell. Once I managed to get it into recovery "adb devices" was returning the phone.
@bardhi92 - I saw that once I got in. However, I couldn't get it to see my phone.
Updated things I have tried and why I've all but thrown in the towel:
After the OTA rescue sideload failed I started trying a few different things. It stopped taking me into recovery mode more frequently, at least it seemed that way - it would just keep bootlooping. My main issue is that I has a locked bootloader, which stopped me whacking TWRP on and loading on a custom rom - just to see if that worked.
I thought it might let me sideload on a factory default img file. Turns out nope.
However I used NRT to "Flash Stock + Unroot" (with "Soft Brick/Bootloop" checked) which for some reason, then allowed me to get back into recovery mode. I had also removed the sim card/tray at this point. May have been either or neither of those that allowed me to get into recovery mode. Can't say for certain.
I cleared /cache and /data and then attempted the OTA rescue update again. This time it failed at 45% (according to my cmd prmpt) with the error: "* failed to read command: No error". I'm not sure text was on the phone at the time. But it did manage to boot into Android. I quickly stepped through the various intro steps (putting in the sim, adding my mail google account details).
I went to get a beer. Only to find it boot looping again.
Not to be deterred, I vowed to try again. Same steps as before (remove sim, nrt voodoo). This time however the OTA rescue worked and fully completed. I went through the intro steps again. This time I quickly turned on dev options, enabled usb debugging and sorted out the OEM bootloader. I thought this would be smart, just in case it hapened again. Once I chose to unlock ("fastboot reboot", selected yes), it decided to start boot looping again.
The main annoyance is: I don't think I have any proof of purchase, even though it's in warranty. That, and I now live in Dubai - so shipping back to the UK where I brought it is going to be killer. But I think it's the path of least resistance at the moment.

SomewhatIrked said:
The more this goes on, the more I believe it to be hardware ...
@sfhub - reasonably innocuous. Had just opened one or 2 apps that morning. Not sure what had updated overnight app/os wise. Not anything interesting as far as I can tell. Once I managed to get it into recovery "adb devices" was returning the phone.
@bardhi92 - I saw that once I got in. However, I couldn't get it to see my phone.
Updated things I have tried and why I've all but thrown in the towel:
After the OTA rescue sideload failed I started trying a few different things. It stopped taking me into recovery mode more frequently, at least it seemed that way - it would just keep bootlooping. My main issue is that I has a locked bootloader, which stopped me whacking TWRP on and loading on a custom rom - just to see if that worked.
I thought it might let me sideload on a factory default img file. Turns out nope.
However I used NRT to "Flash Stock + Unroot" (with "Soft Brick/Bootloop" checked) which for some reason, then allowed me to get back into recovery mode. I had also removed the sim card/tray at this point. May have been either or neither of those that allowed me to get into recovery mode. Can't say for certain.
I cleared /cache and /data and then attempted the OTA rescue update again. This time it failed at 45% (according to my cmd prmpt) with the error: "* failed to read command: No error". I'm not sure text was on the phone at the time. But it did manage to boot into Android. I quickly stepped through the various intro steps (putting in the sim, adding my mail google account details).
I went to get a beer. Only to find it boot looping again.
Not to be deterred, I vowed to try again. Same steps as before (remove sim, nrt voodoo). This time however the OTA rescue worked and fully completed. I went through the intro steps again. This time I quickly turned on dev options, enabled usb debugging and sorted out the OEM bootloader. I thought this would be smart, just in case it hapened again. Once I chose to unlock ("fastboot reboot", selected yes), it decided to start boot looping again.
The main annoyance is: I don't think I have any proof of purchase, even though it's in warranty. That, and I now live in Dubai - so shipping back to the UK where I brought it is going to be killer. But I think it's the path of least resistance at the moment.
Click to expand...
Click to collapse
So, you flashed the .TOT file, sideloaded the given OTA within the stock recovery bootloader that comes with the .TOT file, and cleared cache/factory reset?
Please condense it. If you managed to start up the phone, that's a huge success for people who have not been able to yet.

bardhi92 said:
So, you flashed the .TOT file, sideloaded the given OTA within the stock recovery bootloader that comes with the .TOT file, and cleared cache/factory reset?
Please condense it. If you managed to start up the phone, that's a huge success for people who have not been able to yet.
Click to expand...
Click to collapse
In short:
OTA rescue failed during adb sideload,
Tried bullhead-nbd90w-factory-d2f11c5f.zip & removed sim tray - seemed to allow access to recovery mode,
OTA rescue claims to have failed at 47% during adb sideload- still booted into android. However briefly. Went back to bootloop,
Tried bullhead-nbd90w-factory-d2f11c5f.zip & removed sim tray - seemed to allow access to recovery mode,
OTA rescue completed via adb sideload,
Turned on dev options (usb debug, oem unlock),
Booted to fastboot - unlocked bootloader. Now back to bootlooping
@bardhi92 - I could not get the LG utility to detect my phone. Will attempt again tomorrow.

SomewhatIrked said:
@bardhi92 - I could not get the LG utility to detect my phone. Will attempt again tomorrow.
Click to expand...
Click to collapse
IMO you shouldn't flash the TOT file. If you end up bootlooping again, your phone will be stuck in bootloader locked mode with no ability to unlock it.
If you were able to get your phone to boot into android once, there is really nothing the TOT file will do for you that you can't do from TWRP or bootloader, whereas once it locks your bootloader, there are problems you can no longer fix like EFS corruption (which likely isn't your problem).
In the end, you probably do have eMMC that is slowly starting to fail. There is usually error correction on the eMMC that can lock out bad blocks but if it gets to serious, it'll fail. This is why reflashing stuff over and over sometimes works.

Stuck in setup wizard after factory reset

Alright, hello everyone,
I'm having a pretty weird issue here. I've flashed my DUK-L09 and the C432B183 EU Firmware, everything was running fine.
I couldn't make a backup of the /data/ partition though, someone told me to wipe the data to decrypt it, but nothing came good after this.
So I tried to flash back the old recovery image by extracting it, flashing it via fastboot, as I would normally do; enter the factory reset, run it.
Everything is good, it goes up to 100% pretty fast, less than 2 minutes. I then enter the setup wizard the NFC is acting weird. It keeps activating
and deactivating illogically. So, ignoring this issue, I kept up configuring the phone then once I'm logged in Google and sync'd, pops a Huawei ID
logging page really really fast then goes back to the EMUI menu at the beginning of the Setup, in an infinite loop.
Useful information to let you help me better:
- Many firmwares. Currently trying to flash back to B120a and NoCheck from OldDroid and Morph. (Edit: Didn't work)
- Phone unlocked, TWRP accessible.
- Getting a weird "Error 9" when trying to run Update.zip from TWRP.
- Sideload working, but not transferring anything.
- Cannot find any B182 or B130 stock firmware. Everything seems to be gone from Huawei's servers.
- The loading logo isn't Honor anymore but Android, for a reason I can't yet understand.
- Restoring a clean backup (without /data/, since I couldn't back it up) did not fix the problem.
- Trying to update with the 3 buttons do not work, even with the right firmware (C432B183) (Software install failed)
- Factory reset works with the right ROM, but gets me to the setup loop issue.
- The loop occurs when I am supposed to see the Huawei ID setup page. If I do not put any SIM card, or WiFi
I am prompted to choose which way to restore data; if I skip this step, it blinks and doesn't do anything.
- I tried to restore via WiFi (Google's cloud stored data from my account), but it does the same thing as mentioned
earlier. It blinks multiple times rapidly the "Huawei ID" setup page then goes back to the first Setup screen w/o
me being able to do anything about that.
I'll be glad if you knew the answer to this, because I'm all lost right now.
Greetings, Kameyuu.

UP !
After many tries and a LOT of hard work, and spent an entire night (was about to spend the second night on this), I found the culprit and now I know what the issue is, it sounds completely legitimate.
So here are the reason and the solution to this issue:
Actually, my CUST was somehow broken. I never flashed it back because no one told me to flash the CUST.img back. They told me to flash BOOT, SYSTEM, and RECOVERY only.
So, after I downloaded a software called HUAWEI Multi-Tool (From hwmt.ru) I noticed they were also asking for the CUST.img and USERDATA.img (<- this one was apparently optional)
So, trying my luck I flashed it. Did a factory reset, and all, it acted weird and failed, then I tried again and it succeeded. So, with all my hope I booted the phone to the system, started configuring... And it worked !
I was able to set up the phone. For a -yet- unknown reason, some apps look missing and the NFC is still blinking on and off repeatedly and randomly, but I'm investigating that.
If you have any question on the precise steps feel free to send me a PM or ask in the thread directly I'll be glad to sort your issue out.

[EDIT]
Sorry, double post I don't know why my message was posted twice. Feel free to delete this message @moderators

Help -- phone won't boot and I need to get photos off

My daughter has been using this phone, but never backed her photos up. Now it won't boot and she is worried they are lost forever. I've been trying to help, but only seem to make things worse.
1. She never enabled USB debugging, or rooted it
2. She could not tell me whether she had allowed the OTA upgrades.
3. It got into a reboot loop a few days ago. It would start to boot, then say it was optimising a random number of apps (anything between 90 and 158) and then start over. Wileyfox tech support told me that this was due to an incompatibility between Cyanogen and the latest Facebook Update.
4. They sent me a link to the FOTA files with instructions how to progressively upgrade to Android 7 (TOS111B)
5. They couldn't tell me how to determine whether it was running CM12 or CM13 (I now realise that I could have looked at the log files in the recovery partition)
6. I therefore assumed that it was running CM12. I used their instructions to go into recovery and manually update from SD card to ZNH0EAS2NH from there to ZNH2KAS7EB and then to TOS111B
7. Fatally I did not reboot between updates. At the end I had the Wileyfox splash screen black on white, and then got an animation with it red on white. It then got stuck.
8. I then tried using fastboot to go back to the original version of the OS so I could start over. I found the fastboot image and I flashed the boot and system partitions.
9. Now on boot it either gets stuck on the black on white boot screen, or it displays it for a second and then turns off.
Can anyone help me? - I think my daughter will have a nervous breakdown if I don't find a way of recovering her photos. Recovering the photos is more important than unbricking the phone.

jerrytaff said:
My daughter has been using this phone, but never backed her photos up. Now it won't boot and she is worried they are lost forever. I've been trying to help, but only seem to make things worse.
1. She never enabled USB debugging, or rooted it
2. She could not tell me whether she had allowed the OTA upgrades.
3. It got into a reboot loop a few days ago. It would start to boot, then say it was optimising a random number of apps (anything between 90 and 158) and then start over. Wileyfox tech support told me that this was due to an incompatibility between Cyanogen and the latest Facebook Update.
4. They sent me a link to the FOTA files with instructions how to progressively upgrade to Android 7 (TOS111B)
5. They couldn't tell me how to determine whether it was running CM12 or CM13 (I now realise that I could have looked at the log files in the recovery partition)
6. I therefore assumed that it was running CM12. I used their instructions to go into recovery and manually update from SD card to ZNH0EAS2NH from there to ZNH2KAS7EB and then to TOS111B
7. Fatally I did not reboot between updates. At the end I had the Wileyfox splash screen black on white, and then got an animation with it red on white. It then got stuck.
8. I then tried using fastboot to go back to the original version of the OS so I could start over. I found the fastboot image and I flashed the boot and system partitions.
9. Now on boot it either gets stuck on the black on white boot screen, or it displays it for a second and then turns off.
Can anyone help me? - I think my daughter will have a nervous breakdown if I don't find a way of recovering her photos. Recovering the photos is more important than unbricking the phone.
Click to expand...
Click to collapse
Since posting this I have had a partial success. A more complete set of fastboot flashing using the TOS111B fastboot images has got me to a phone that boots. Many of the apps work. However...
a) I get an "unfortunately the process com.android.phone has stopped" appearing almost as fast as I can close the app making it very difficult to get anything off the phone. However, I did manage to set up a google sync to upload the photos.
b) my daughter now tells me that her SMS's are vital.... and the messaging app says " getting message" then closes down
c) I cannot enable developer setting to enable usb debug mode. I can get into the phone status page under settings. Repeated tapping on the android version brings up the nougat splash screen, but the 7 taps (or 700 for that matter) on build number does nothing whatsoever.
Does anyone have any ideas how to recover to a fully working system without doing a factory reset?
I suspect that the sms database would have gone when the cache was cleared. Can anyone confirm that to be the case before I spend any more time trying to recover them?

Hi Jerry ,
Exactly the same problem here. Could you tell me where you've found the TOS111B fastboot images?
Thx!

Have you tried booting into safe mode?
I think you do that by pressing and holding the volume down down button during reboot.
If you can manage that you may be able to dissable the apps that are causing the crash.

[SOLVED] Soft brick (?) on Z1C-based ZPG handheld

SOLVED: I figured out the issue. As mentioned in this thread, downgrading to an older version of flashtool successfully got me past the bundle mismatch error, allowing me to flash stock US firmware onto the device. Still not exactly sure why that's the case, but it worked for me.
Hey folks,
Hope you're all doing well! I have a bit of an odd situation. I recently picked up a Z-Pocket Game, a handheld built using the internals from a torn down Z1 Compact.
A few days ago, I decided to see if I could poke around and install a custom ROM onto the device, given how many are available for the source hardware (Z1C). The device already came pre-installed with XZDualRecovery and was running a custom ROM in Chinese built off Lollipop.
I'm a novice when it comes to flashing and custom ROMs, so I tried to learn more about the process before getting started. Evidently, however, I'm in over my head - fully my responsibility, of course, but over my head nonetheless.
Long story short, I tried to install Lineage OS 17.1 onto the device via the version of TWRP already installed on the device. As per the installation instructions detailed here, I did an advanced wipe before attempting the install, selecting "Dalvik," "System," "Cache," and "Data." When I actually attempted the process, however, it errored out almost immediately, leaving me with a wiped system and no ROM (TWRP warned me about this prior to rebooting).
When I now power on the device, it's stuck on the "Sony - XPERIA" screen, and the LEDs don't light up at all. I can't seem to access TWRP or Philz on the device with the normal key presses. I can force the device off by holding Power and Volume Up, and it also seems able to enter fastboot mode (with a solid blue LED) and flash mode (the LED flashes green, then turns off). I've tried a number of different things to try and fix it, but all of them haven't worked in one way or another. Providing a brief overview to the best of my recollection here, but happy to try again and give more detail if needed:
Using fastboot via the command line to flash a new recovery onto the device gives me an error indicating I can't write the file to the device, and things just end there.
Trying to flash a stock US ROM to the device via flashtool gives me an error indicating the device does not match the bundle, and things just end there.
Trying to restore the device using Xperia Companion first gives an error requesting permission to access the device, then when I select "My Device Cannot Be Detected or Started" and follow the instructions, it tells me that "an error occurred while repairing this device," and provides this small blurb of device info:
UEGetPhoneInfoMissingInfo
Z-POCKET GAME 3579 1279-6978 R2D 14.6.A.1.236
2.11.6.0 / Windows 10 64 bit / Win32 / US / /
So I'm a bit stumped. It seems as though enough of the device is working to get everything back into a workable state, but I'm not sure of how to go about that. Any thoughts or leads would be greatly appreciated!

edit_duplicate said:
SOLVED: I figured out the issue. As mentioned in this thread, downgrading to an older version of flashtool successfully got me past the bundle mismatch error, allowing me to flash stock US firmware onto the device. Still not exactly sure why that's the case, but it worked for me.
Hey folks,
Hope you're all doing well! I have a bit of an odd situation. I recently picked up a Z-Pocket Game, a handheld built using the internals from a torn down Z1 Compact.
A few days ago, I decided to see if I could poke around and install a custom ROM onto the device, given how many are available for the source hardware (Z1C). The device already came pre-installed with XZDualRecovery and was running a custom ROM in Chinese built off Lollipop.
I'm a novice when it comes to flashing and custom ROMs, so I tried to learn more about the process before getting started. Evidently, however, I'm in over my head - fully my responsibility, of course, but over my head nonetheless.
Long story short, I tried to install Lineage OS 17.1 onto the device via the version of TWRP already installed on the device. As per the installation instructions detailed here, I did an advanced wipe before attempting the install, selecting "Dalvik," "System," "Cache," and "Data." When I actually attempted the process, however, it errored out almost immediately, leaving me with a wiped system and no ROM (TWRP warned me about this prior to rebooting).
When I now power on the device, it's stuck on the "Sony - XPERIA" screen, and the LEDs don't light up at all. I can't seem to access TWRP or Philz on the device with the normal key presses. I can force the device off by holding Power and Volume Up, and it also seems able to enter fastboot mode (with a solid blue LED) and flash mode (the LED flashes green, then turns off). I've tried a number of different things to try and fix it, but all of them haven't worked in one way or another. Providing a brief overview to the best of my recollection here, but happy to try again and give more detail if needed:
Using fastboot via the command line to flash a new recovery onto the device gives me an error indicating I can't write the file to the device, and things just end there.
Trying to flash a stock US ROM to the device via flashtool gives me an error indicating the device does not match the bundle, and things just end there.
Trying to restore the device using Xperia Companion first gives an error requesting permission to access the device, then when I select "My Device Cannot Be Detected or Started" and follow the instructions, it tells me that "an error occurred while repairing this device," and provides this small blurb of device info:
UEGetPhoneInfoMissingInfo
Z-POCKET GAME 3579 1279-6978 R2D 14.6.A.1.236
2.11.6.0 / Windows 10 64 bit / Win32 / US / /
So I'm a bit stumped. It seems as though enough of the device is working to get everything back into a workable state, but I'm not sure of how to go about that. Any thoughts or leads would be greatly appreciated!
Click to expand...
Click to collapse
Glad that you find out yourself.
And thanks for sharing!