Develop Bugs

I can not activate blututu

Since I had a problem yesterday when trying to backup from ROM Manager, with the ongoing recovery Amon-Ra, I was the Desi who had no access to SD.
Following the tutorial to repair the brick USB, I got to read it again and from there I wanted to connect the PC and gave me a driver error, when it was installed with no problems so far, and I have root and s- off.
The fact is that I get an error installing the blututu driver "? and finally not just install the drivers so I have no access usb from windows.
Now the problem: I can not enable blututu from the configuration of Desi, I say start, I think a few seconds and then disconnect.
I tried to flash the radio, thinking that since it is the same chip that controls the wifi, 3g, blututuh, etc ... be solved and has not worked.
I do not know if you have something to do, but I notice that in settings has lost blututu device name. Do you know how I can fix this?

Moved to Q&A
Please do not post question threads in Development.
Post What Where:
General - general technical discussion items, news, anything else that does not fit into the other fora categories.
Q&A (Questions and Answers) - all questions, irrespective of type, get posted in here whether they be theme related, accessory related, technical, etc.
Accessories - any items to do with components and/or accessories relating to your device.
Rom Development - only meant for very advanced technical discussion directly related to ROM development activity and the delivery of actual ROMs and ROM components ONLY. Nothing else goes in here.
Themes & Apps - anything to do directly with the development of themes and/or applications. Nothing else goes in here.

Z1C won't start - advice please

I've got myself into quite a muddle with my rooted Z1 Compact. I was prompted to update the firmware to 14.4.A.0.157, which I did over the air. Since the update, the device had been freezing, restarting and generally being unwell. What I didn't realise, based on a piece I read somewhere, was that this was likely or probable if the phone had been rooted. My memory is a bit sketchy on all the steps I took - but briefly - it suggested checking the status of the phone, from which I followed instructions using flashtool to flash a preceding firmware (xxxx.108), which it appeared to do successfully but now the phone does not boot at all. I'm now lost what to do next and I couldn't say if I've soft or hard bricked the phone. Another article (at android.gs / unbrick-sony-xperia-z1 ) says that if it's hard bricked then I need to flash the full firmware (not just kernel only). I've downloaded and installed Emma from Sony's site. I can get the software to recognise the phone but it says it is locked and I am in the process of downloading the Android SDK to [see if I can] continue this process.
I should have stopped and asked for advice before I did any of this. Now finally I am pausing to seek advice. Can anyone point me in the right direction?
The phone will charge when plugged in, at least it is showing a green LED to imply fully charged.

Brief update: I couldn't enable USB debugging on device, as device doesn't start up. I enter fastboot mode when connecting the device (Windows) and I run "fastboot devices" in the platform-tools folder without an error however when I enter the command with my unlock key, I just get "waiting for device" (several minutes). I am assuming that this might be because I couldn't enable USB debugging on the device? Any suggestions on where to go from here?

I might as well log the antics of my adventurous mind. Given that I hit a dead end, I continued on the original path and used FlashTool to flash 14.2.A.1.114_Customized firmware (why this - because it was the only full firmware that I found). Anyway, thankfully, I now have a working device running that firmware with Android 4.3. I'll try and proceed to get back up to date.

devo1d said:
(why this - because it was the only full firmware that I found).
Click to expand...
Click to collapse
Not sure how when this thread is stickied at the top of the General Section. Z1 Compact Resource Thread -|-Rooting-BL Unlocking-Firmware & More..

Oh my goodness......... It is pantomime season after all

Magic. I confess to being another dizzy head when things don't go right and reading from a multiple sources and getting a bit overwhelmed & lost. Anyway, found the way out and thank you for the pointer to the sticky right-in-front-of-the-eyes info. Bookmarked.

Nexus 6 with Android N stops booting after entering start pin - bricked?

Scenario:
- I have a Nexus 6 (shamu) with Android preview: the version of the OTA is NPD90G. (Android beta)
- Yesterday it crashed right after it lost radio signal (this used to be a common problem for me but when it crashed it came back again fine for me)
- Now when it boots it asked for my personal pin, then the animation makes its first round and at the end of the second round it stops and it reboots.
-- This is what it looks like for a moment: www andreaundstefanhoehn de / nexusboothang.jpg (cannot post urls at the moment)
-- Removing the simcard has no effect
-- I wiped the cache partion
- Of course I do not have a backup of my data
- Of course the device is locked
- The last message in the log_kmsg is "SELinux: initialized...
What I did:
- I tried the famous "Fix Dead Android in Recovery Mode" but it doesn't help
- After many tries I understood I can update my device with "adb sideload"
-- after searching around a lot I even found the firmware NPD90G and I was successfully to reinstall the firmware.
-- For those who are desperately looking for that version as it seems not to be listed anywhere, here is the still working link: storage.googleapis.com /androiddevelopers/shareables/preview/ota/ shamu-ota-npd90g-06f5d23d.zip (cannot post urls at the moment)
-- Unfortunately even after reinstalling the firmware, it still stops at the same point
-- I tried to unlock the device with "fastboot oem unlock" but it tells me to check "allow oem unlock" in Dev Options which 100% likelyhood is not checked
- Run graphics test results quickly "error", then in a dead android image, then saying "erasing" and then saying "installing system update" but it doesn't fix the problem
Questions
- Does anyone know what the actual issue is that the device stops?
- Is there any newer OTA for shamu I could use? Is there maybe a final Android N for shamu somewhere available?
- Given the above situation, is there any chance I can access files on my device?
- Any other option I have, except factory reset (and wiping my data)?
I really put a lot of effort in it (and learned a lot) but I only got that far. I wished there are other options?
Thanks in advance for helping,
Stefan

I "reposted" the question to the forum here. Not sure how to move delete it in the the other forum. Sorry.

Mod Edit
Duplicate post
Thread Closed.
jackeagle
Forum Moderator

Mi Note 2 stuck on "Checking for updates" screen after a simple factory reset. Brick?

Mi Note 2 stuck on "Checking for updates" screen after a simple factory reset. Brick?
Hi all,
I have Mi Note 2 phone. It's never been unlocked or ROMed before (although it has been reflashed successfully via Xiaomi's own pushed updates). It is running MIUI 10.0.something (cannot access menus to verify exact).
Following a standard factory reset, I go through the normal setup screens such as 'language', 'region', 'wifi network' after which I am given the option to select "copy your data from an old phone" or "set up as new", no matter which I select, my phone goes to the next screen which shows "Checking for updates". Here it stays - endlessly...
I have tried a different wifi network but it does the same.
I have also tried selecting "copy your data" instead of "set up as new" but it does the same.
I thought I would try to install a new stock rom to see if that would fix the issue. However, in order to unlock with the Mi bootloader unlock tool (and then use their flashing tool), apparently I need to enable something under developer options - clearly impossible when I cannot get to any menus
The phone can be re-started into the fastboot screen but does this help me at all?
On the MIUI website I noticed the following in the tips and tutorials forum: How to install a MIUI update without unlocking the bootloader: https://en.miui.com/thread-3852597-1-1.html
The above got me slightly excited before I realised that I have no way to place a ROM into the ‘downloaded_rom’ folder in the internal storage of my device (as the article instructs). Note that the reason for this is that although a Windows explorer window does open when I connect the phone to my laptop, it is empty (i.e. you cannot see any files/folders in it). BTW - I know what causes that specific issue as that bug was present in the device ages ago - basically, the phone seems to default to be in USB charge mode and in order to see the folders in Windows Explorer, you have to go into developer options and manually change the USB mode and then change it back to MTP mode. Once that is done, you can see the files/folder structures. However, I cannot get to any developer options as I cannot get to Settings at all.
So my burning question is this: How can I re-rom this theoretically 'working' device, given the above constraints? Is there any way to do anything while the phone is in the fastboot mode perhaps?
Thank you for any help offered!
Cheers!

avmad said:
Hi all, I have Mi Note 2 phone...........
Click to expand...
Click to collapse
I don't have this device but, you should be able to obtain some member guidance within the following thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3839540
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Commodore 64.

Ibuprophen said:
I don't have this device but, you should be able to obtain some member guidance within the following thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3839540
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Commodore 64.
Click to expand...
Click to collapse
Thanks Ibuprophen - I'll give that a shot!

[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!