yashsingh1/xdaforums huggingface dataset:
[HTC One S] mraabs:
I have recently upgrade my hboot to hboot 2.15 and tried to flash new rom, but I'm facing a problem with wifi. I can't turn on the wifi, when I click on it just stick on "turning wifi on" and nothing happens.

I have tried these rom xenonHD,candy, LP but same issue, I have also installed a custom kernel "Mark kernel" but no luck.

while installing the rom I have followed every step required and mentioned by the developers "wipe cash, system...."

the wifi errors taken from logcat file are here:

[ 05-06 23:10:21.717 669: 1110 E/WifiHW ]
Supplicant not running, cannot connect

[ 05-06 23:10:21.818 669: 1110 E/WifiHW ]
Supplicant not running, cannot connect

[ 05-06 23:10:21.818 669: 1110 E/WifiMonitor ]
startMonitoring(wlan0) failed!

[ 05-06 23:10:21.823 669: 1110 E/WifiStateMachine ]
Failed to setup control channel, restart supplicant

[ 05-06 23:10:21.823 669: 1110 E/WifiMonitor ]
killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown

[ 05-06 23:10:31.885 185: 601 E/WifiHW ]
Failed to write wlan fw path param (No such device)

[ 05-06 23:10:31.885 185: 601 E/SoftapController ]
Softap fwReload failed

[ 05-06 23:10:31.887 669: 1110 E/NetdConnector ]
NDC Command {148 softap fwreload wlan0 STA} took too long (5056ms)

[ 05-06 23:10:31.888 669: 1110 E/WifiStateMachine ]
Failed to reload STA firmware java.lang.IllegalStateException: command '148 softap fwreload wlan0 STA' failed with '400 148 SoftAP command has failed'

[ 05-06 23:10:31.893 185: 601 W/CommandListener ]
Failed to retrieve HW addr for wlan0 (No such device)

[ 05-06 23:10:31.898 185: 601 D/CommandListener ]
Setting iface cfg

[ 05-06 23:10:31.902 669: 1110 E/WifiStateMachine ]
Unable to change interface settings: java.lang.IllegalStateException: command '150 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 150 Failed to set address (No such device)'

[ 05-06 23:10:31.902 669: 1110 E/WifiMonitor ]
killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown

[ 05-06 23:10:31.912 3822: 3822 D/BluetoothAdapter ]
760752152: getState() : mService = null. Returning STATE_OFF

[ 05-06 23:10:31.914 669: 1110 D/WifiMonitor ]
startMonitoring(wlan0) with mConnected = false

[ 05-06 23:10:31.914 669: 1110 E/WifiHW ]
Unable to open connection to supplicant on "@android:wpa_wlan0": No such file or directory

[ 05-06 23:10:31.945 6595: 6595 I/wpa_supplicant ]
Successfully initialized wpa_supplicant

[ 05-06 23:10:31.947 6595: 6595 E/wpa_supplicant ]
Could not read interface wlan0 flags: No such device

[ 05-06 23:10:31.947 6595: 6595 E/wpa_supplicant ]
wlan0: Failed to initialize driver interface

[ 05-06 23:10:32.015 669: 1110 E/WifiHW ]

Please let me know what steps I should take to fix this problem.
[HTC One S] mraabs:
no one has any suggestion?
[HTC One S] Rapier:
First I am wondering how you ever thought you've upgraded your firmware to 2.15 as your boot info says hboot 1.14.0002...

Sent from nowhere over the air...
[HTC One S] mraabs:
Sorry for wrong information. Im using hboot 2.5 (modded)
[HTC One S] Rapier:
I guess you wanted to say 2.15 cause there's no 2.5 hboot.

Ok...have you flashed only the hboot or the entire firmware? Could be that you didn't flashed wcnss which is responsible for wifi. There are some threads where it is only the hboot posted and that's why I'm asking.

There is a thread that contains the full firmware with the partitions for wifi and audio included. You should have flashed this one then, if you want to get rid of the red warning, flash just the modded hboot you talked about (I guess that's why you flashed that one) .

Sent from nowhere over the air...
[HTC One S] mraabs:
yea I wanted to say 2.15 (:silly:

your guess is quiet right I have flashed only hboot.

now Im trying to flash the whole firmware as you said . should I download one of the RUU available here or I need to download different specific firmware?!
[HTC One S] Rapier:
No, it is not a RUU. I'm on mobile so I can't search so easy but there's a thread that contained the whole firmware not only hboot. The firmware has a bigger size than the hboot only

Sent from nowhere over the air...
[HTC One S] mraabs:
I have found these threads:

http://xdaforums.com/showthread.php?t=2570112

http://xdaforums.com/showthread.php?t=2322755

Am I on the right path?
[HTC One S] Rapier:
Yesss... That's the one I was talking about. Use that firmware. There is another thread about changing just the splash screen and that has only the moded hboot with red warning gone. I guess you have flashed that one in the past

Sent from nowhere over the air...
[HTC One S] mraabs:
Much appriciated Rapier, I have flashed the official firmware and now the wifi is working :good:
[Xperia Z3 Q&A, Help & Troubleshooting] Desperanto86:
Maybe some one know how to open and view Sony OTA update_package? This is update_package from KK to LP.

I have Z3 Dual on KK and update center download this file... I don't want to update, I just want to view the structure of file. 7zip open it but say that file is broken :(

Who can help?

update_package 616.5 MB
[One (M7) Q&A, Help & Troubleshooting] kkaiser:
Hey guys my Htc M7 from tmoblie got its board damaged so i bought a verizon board and tried to replace it, but there is a small cable that i can not connect cause i dont see the place to do it, now my question is if i leave like that would it cause any problem?

does anyone know whats the function of that cable?
[One (M7) Q&A, Help & Troubleshooting] alray:
Probably, yes.....

How could we know without seeing it? Any picture?
[G2 Q&A, Help & Troubleshooting] Sponzo:
How to root my lg g2 on V30B ?

Auto root and recovery install v1.1 Not working.

EDIT: Rooted with this method: http://xdaforums.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
[8125, K-JAM, P4300, MDA Vario ROM Development] ericizzy1:
--------------------------------------------------------------------------------

is it possible to active sync my calander on one exchange server(office) and email on another exchange server(home) mon the same wing?thnx
[Galaxy Tab 3 Q&A, Help & Troubleshooting] ravenmk:
Hello, I want to return back to the stock Samsung 4.4.2 firmware.

I would like to see if anyone has a firmware, but one that will wipe everything.

Thanks.
[Galaxy Tab 3 Q&A, Help & Troubleshooting] Komhir:
Check on sammobile
[Galaxy Tab 3 Q&A, Help & Troubleshooting] ravenmk:
I have but the thing is it takes too long. Plus, there is no version for USA. It's only Canada and cellular south.
[Galaxy Tab 3 Q&A, Help & Troubleshooting] DevMyAndroid:
cellular south is usa.......
[Galaxy Tab 3 Q&A, Help & Troubleshooting] ravenmk:
Oh. Thanks! I didn't know that.
[Galaxy Tab 3 Q&A, Help & Troubleshooting] DevMyAndroid:
hahaha. no prob. i didnt either at first
[Galaxy Tab 3 Q&A, Help & Troubleshooting] ravenmk:
Lol
[Amazon Fire Phone] nemo_meno:
Hi all,

I think many, like me have problem with carriers provided fire phones. Could you please share the original ROM wich come with the unlocked phones provided directly by Amazon.

Thanks

NeMo
[Amazon Fire Phone] najoor:
The original 3.68 firmware that came with the unlocked version was never made publicly available. The only non carrier firmware that you can find is the 4.6.1 version.

Even if you get your hands on the original version somehow, after upgrading to 4..6.1, there is no way to downgrade to the lower version.
[Amazon Fire Phone] s.raghuveer:
Fire phone unlocked os 4.6.1

Here is the link to the latest update of Unlocked fire phone os 4.6.1 which I downloaded and installed successfully.

https://

fire-phone-updates.s3.amazonaws.com/update-fire-phone-35.4.6.1_user_461013820.bin

Regards

Raghuveer
[Meizu MX] tudorlv:
Hello guys,

I just got my MX4 today, of course rooted it, and I can't find a custom recovery for this device.

Do you guys managed to install a custom recovery yet, or do some flashing?

Thanks in advance!
[Meizu MX] psycmos:
No possibility!!

Tudorlv, we not have any costum rom yet because meizu team not released the sources for flyme and kernel.

We can't unlock it and install any custom rom on it, and CWM.

Maybe one day they will release the sources.

There are one pepition on internet.

https://www.change.org/p/meizu-technology-co-ltd-unlock-bootloader-in-meizu-phones-and-release-flyme-source-for-mx4-mx4-pro-and-m1-with-their-kernel-source

Please subscribe, is the unique thing that we can do until now!!!

Best regards, Psycmos
[Meizu MX] iicc:
The only option is to flash zips with FlashGordon, nothing more...
[Meizu MX] rootcid:
What is flashgordon exactly?
[Meizu MX] iicc:
It is a recovery emulator. It simply translates Edify into Bash script.

Is the same as if you execute a script in a terminal emulator
[Meizu MX] tudorlv:
Thank you Psycmos,

I'm kind of dissapointed of the low activity here on XDA about the MX4 considerind it's a really great device, very well balanced (coming from an HTC M9)

Anyway, here is what I managed so far, working perfectly:

1. Nova launcher

2. Xposed, with:

- Amplify

- App Settings (mostly for immersive mode)

- Battery Stats Plus

- Enable Battery Stats

- Flyme tools, of course :)

- Greenify

- Immerse Me (disabled in xposed because also hides the statusbar in homescreen)

- Lucky Patcher ;)

- Smooth System Progress

3) Super User (chainfire)

To do list:

1) gain acces to system files via File Manager

2) Most important ! : somehow get the Xperia Z(1,2,3) video recording stabilizer, it's great!
[Meizu MX] iicc:
In my case I am doing some mods, this is the latest: MoreFlymeNotifications, each notification with his icon!! Not grouped in the same icon.

View attachment 3304908

Edit: published in this forum
[Meizu MX] punkmonkey1984:
How are you achiving this? with xposed or editing the systemui/framework files?

Also any updates ?
[Nexus 9 Q&A, Help & Troubleshooting] the.teejster:
I'd like to start off by saying that I have NEVER rooted this device and have been 100% stock since day 1.

The only thing I did was enable developer options to unlock the bootloader so I could sideload OTA updates in the event they take too long to hit my device... No custom recoveries, no custom roms, no custom kernels, no exposed framework... NOTHING.. pure stock.

I started getting the 5.0.2 upgrade notification yesterday. Everytime I download and install, about 30% of the way through the installation I get the android icon showing ERROR. When I open the last recovery log it mentions not being able to open /cache/update.zip with a status 7 error. .. All I can do it reboot and return back to 5.0.1

I did some reading and it was recommended to wipe / format the CACHE partition. So I went into the stock recovery and tried this but to no avail.

I REALLY don't want to factory reset (or flash a factor image) and lose all the progress on the various games I have been playing.

Is there anything else I can try ??
[Nexus 9 Q&A, Help & Troubleshooting] y2whisper:
you can try sideloading the update, grabbing the factory image and manually flashing the partitions (except userdata). you can try the factory image and just edit the flash-all.bat file to not wipe the device (sometimes the flash all file gave me an issue forcing me to do the partitions manually)
[Nexus 9 Q&A, Help & Troubleshooting] the.teejster:
Thanks for the feedback... I can try this but IMO it's more of a workaround than a solution.

What I'm trying to get at is..... How in the heck would Google or HTC expect the average consumer to resolve such an issue.

Needing to have a PC, have special drivers installed, etc.., is understandable for those who want to step away from STOCK but what about the average consumer who just purchased the tablet to use as is, continues to receive a notification that an update is available, but fails every time it is applied ? Surely there is something that can be done so allow the update to take without having to factory reset or RMA the device...
[Nexus 9 Q&A, Help & Troubleshooting] y2whisper:
From the sounds of it there is an issue with the OTA file. But I agree you shouldn't be having to do this. I worry about the non xda'ers of the world when this stuff happens
[Nexus 9 Q&A, Help & Troubleshooting] flywatt:
Mine is doing the same crap. Also unmodified Nexus 9. This is nonsense.
[Nexus 9 Q&A, Help & Troubleshooting] kurtis.austin2:
Same issue here. Error every time I hit Restart & Install after downloading the update. Have to long press the power bottom to get it to boot back again. Tried a factory reset, didn't work. Still getting same error.
[Nexus 9 Q&A, Help & Troubleshooting] the.teejster:
Thanks for sharing that you tried a factory reset. I am trying to avoid this for reasons mentioned in my 1st post.

I have tried numerous times now wiping cache and waiting for the upgrade to reappear but it continues to error out that the same place during the upgrade each time. Fortunately it's not bricking the device but IF this update is required as a stepping stone for subsequent updates then it will be extremely disappointing if Google doesn't address this issue.

I still cannot imagine google / htc not being able to resolve this WITHOUT having to make a user connect to a PC and manually flash imagess (or worse.. RMA the device). Hoping someone on XDA comes up with a magical sequence to allow the OTA to prcess properly.

In addition to wiping cache through recovery I have also ensured that I didn't have any apps / process or services disabled.

This is also being reported in google support forums:

https://productforums.google.com/fo...ter#!category-topic/nexus/nexus-9/MzHmJu4glkQ

I still haven't tried sideloading the OTA but at this point I don't think it would make a difference as the OTA does download properly and says it was verified.
[Nexus 9 Q&A, Help & Troubleshooting] adstro:
I found this -> http://www.telekom-presse.at/apps/n...sht_update_auf_version_5-1_fehlt.id.33675.htm. There is a comment claiming to have fixed the issue by sideloading the OTA. I have yet to try it myself though.
[Nexus 9 Q&A, Help & Troubleshooting] the.teejster:
On a side note,

Google has apparently finally released 5.1.1 for our device so it should be making it's way out soon.. HOPEFULLY we can go straight from 5.0.1 to 5.1.1 without having to worry about 5.0.2.
[Nexus 9 Q&A, Help & Troubleshooting] cam30era:
Have you seen any evidence of this unicorn? Just curious...
[Nexus 9 Q&A, Help & Troubleshooting] the.teejster:
Reported on the official Google+ page :

https://plus.google.com/+Nexus/posts/2hB9k5r2Z7T

But I can't find any reports of anyone actually receiving it yet. IF 5.0.2 needs to act as a stepping stone then maybe they delayed to get the 5.0.2 issue resolved 1st.. It seems to be getting more and more attention out there now.
[Nexus 9 Q&A, Help & Troubleshooting] the.teejster:
FWIW.

I went into recovery, wiped cache and tried to side load the 5.0.2 OTA update manually and got the same error. The error displayed approx. 40% into the upload process from the PC.
[Nexus 9 Q&A, Help & Troubleshooting] kurtis.austin2:
I'm getting frustrated I can't get 5.0.2 to install. This is ridiculous
[Nexus 9 Q&A, Help & Troubleshooting] tshoulihane:
When I get the error, Power/Vol+ switches to the recovery log - there is a warning about (from memory) a partition having been mounted R/W, and a suggestion to re-flash the device first.

All I can remember changing from stock is permitting bootloader-unlock from dev options (never got round to unlocking, so far as I remember).

Not too worried, will hang on for the next major update (or 6.x if there is a preview, maybe) - however, it seems 5.0.2 is a fix to allow 5.1.1 to download (from comments on the G+ thread)

My error is an SHA mismatch on /dev/block/platform/sdhci-tegra.3/by-name/APP. I have

47e96f7e7daa360947b456eca9dc5a8e45573b30
[Nexus 9 Q&A, Help & Troubleshooting] cam30era:
[MENTION=1146438]the.teejster[/MENTION], [MENTION=1974608]kurtis.austin2[/MENTION], [MENTION=2662726]tshoulihane[/MENTION]

Given that 5.0.2 is a significant improvement. Why don't you give up on trying to sideload the OTA, and fastboot flash the factory image? You won't get these errors.
[Nexus 9 Q&A, Help & Troubleshooting] kurtis.austin2:
How do I do this? Need adb from a computer?
[Nexus 9 Q&A, Help & Troubleshooting] cam30era:
Yes you need ADB and Fastboot. Follow this guide and don't hesitate to ask questions > http://xdaforums.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
[Nexus 9 Q&A, Help & Troubleshooting] kurtis.austin2:
Thank you ? very kind of you
[Nexus 9 Q&A, Help & Troubleshooting] cam30era:
Welcome
[Nexus 9 Q&A, Help & Troubleshooting] the.teejster:
Please read the OP.
[Nexus 9 Q&A, Help & Troubleshooting] cam30era:
Fair enough.
[Nexus 9 Q&A, Help & Troubleshooting] the.teejster:
Additionally.

Us early Nexus 9 adopters went through a similar issue in the past where I did bite the bullet and flashed the factory image..

http://xdaforums.com/nexus-9/general/ota-problem-lfw73w-recovery-t2940357

This is the 2nd time googles screws up with Nexus 9 owners and flashing factory images should not be the only recourse.

I'd like to see what would happen if Apple ran into this issue and offered that up as the only solution. ?
[Nexus 9 Q&A, Help & Troubleshooting] cam30era:
I'm assuming this is rhetorical in nature...
[Nexus 9 Q&A, Help & Troubleshooting] the.teejster:
Has anyone who is impacted by this issue tried downloading and flashing the 5.1.1 factory image via the included flash-all.bat file ?? (Assuming the use of fastboot from the latest android SDK).

Any issues encountered ?
[Nexus 9 Q&A, Help & Troubleshooting] cam30era:
Flash-all doesn't work. FWIW, it takes about two minutes to fastboot flash each separate .img file.
[Nexus 9 Q&A, Help & Troubleshooting] the.teejster:
Thanks..

I will likely cave in, take the hit on losing my data and manually flash the factory image.

For those interested the prerequisites are (Look elsewhere in the forum if unsure how to accomplish any of this)

1.) Android SDK is installed and working on your PC

2.) Developer options are enabled on your device

3.) USB debugging is enabled in Developer options

4.) "Enable OEM unlock" option is enabled in Developer options.

5.) Factory image is downloaded and extracted along with embedded zip file (needs to be extracted in same directory)

Once you have that.......

1.) Connect your device to PC

2.) Open CMD window and navigate to folder where you extracted the factory image

3.) Start issuing the following commands :

- adb devices (just to make sure adb can see your device... If it returns something then it can see it)

- adb reboot bootloader

(wait for device to reboot into boot loader)

- fastboot oem unlock

(If deviced wasn't previously unlocked this WILL WIPE your device. follow instructions on device. If your device is already unlocked this command won't do anything)

- fastboot flash bootloader bootloader-flounder-3.43.0.0114.img

- fastboot reboot-bootloader

(wait for device to reboot)

- fastboot flash recovery recovery.img

- fastboot flash boot boot.img

- fastboot flash system system.img

(This one will take awhile so be patient)

- fastboot flash vendor vendor.img

- fastboot flash cache cache.img

- fastboot reboot

DONE.
[Nexus 9 Q&A, Help & Troubleshooting] cam30era:
[MENTION=1146438]the.teejster[/MENTION],

Interested in hearing how it works for you. Good luck!

:svetius:

---------- Post added at 01:55 PM ---------- Previous post was at 01:50 PM ----------

[/COLOR [MENTION=1146438]the.teejster[/MENTION],

And FWIW, you shouldn't loose data when manually flashing each .img.
[Nexus 9 Q&A, Help & Troubleshooting] the.teejster:
Unfortunately that isn't the case with fastboot oem unlock.command.
[Nexus 9 Q&A, Help & Troubleshooting] cam30era:
Aahh, right. I forgot that your bootloader was still locked. Good luck.
[Nexus 9 Q&A, Help & Troubleshooting] the.teejster:
I took the plunge and followed the instructions below and successfully uploaded from 5.0.1 to 5.1.1

My boot loader was already unlocked so I didn't lose any data either.

Hopefully Google doesn't screw up the next update.
[Nexus 9 Q&A, Help & Troubleshooting] albsat:
[MENTION=1146438]the.teejster[/MENTION]

How about someone that has root and twrp. Is it necessary to install the recovery? I guess not..
[Nexus 9 Q&A, Help & Troubleshooting] the.teejster:
This thread is for the few who haven't modified their device.

But FWIW,

My instructions "should" work for anyone with the caveat being that you would lose root and TWRP. But as always, proceed at your own risk.
[Nexus 9 Q&A, Help & Troubleshooting] GedBlake:
[MENTION=1146438]the.teejster[/MENTION] They should work, even if you have modified your device... Since it wipes/replaces the contents of the three partitions that can be modified - system, boot (kernel) and recovery. It's why you loose root and TWRP Custom Recovery.

---

Anyway, your

guide

worked perfectly for me, leaving all my data and user installed apps intact and untouched:).

It took about half an hour for my Nexus 9 to upgrade from 5.0.2 to 5.1.1, most of which was spent waiting for 'system' to send and write, and then later, the interminable 'Android is upgrading' dialog box. (I have no idea how many hours of my life have been expended staring at computer related process gauges of one kind or another... just waiting, waiting, waiting for something to complete!! :)).

---

Re-acquiring root after you've upgraded to 5.1.1 is relatively simple...

Download

Chainfire's SuperSU-v2.46 root package

directly to the Nexus 9.

Next, fastboot flash

TWRP 2.8.5.0

to the recovery partition with...

fastboot flash recovery openrecovery-twrp-2.8.5.0-flounder.img

...or for simplicities sake, rename it to twrp.img, and the command is easier to type; just...

fastboot flash recovery twrp.img

Boot into TWRP, press the INSTALL button, and navigate to where Chainfires SuperSU package downloaded to earlier, usually the /download folder. Select it, and swipe to flash it.

---

And thats it... with [MENTION=1146438]the.teejster[/MENTION] helpful guide, it shouldn't take much more than 45 minutes to upgrade to Lollipop 5.1.1, and then reroot...

And with no loss of data.

---

Who needs OTAs when you've got fastboot;).

Rgrds,

Ged.
[Nexus 9 Q&A, Help & Troubleshooting] chogardjr:
FYI, you do not need to get the SU to flash. One you have flashed twrp back simply boot to recovery then immediately boot to system. Twrp will ask to root by installing su. This is fine and you'll only need to update the apk in the market, then open the app and install binaries. Much easier than the zip.
[Nexus 9 Q&A, Help & Troubleshooting] reisb:
I received 5.1.1 ota notification. Downloaded 400mb. Clicked install and got an error at the android robot logo installation portion. Version shows 5.0.2. Have received notification a few more times and get error at same place. I'm guessing the downloaded file is bad but it doesn't ask me to download anymore. Just install.

I'll never get it installed. How do I get past this. Thoughts?

Basically same problem as orig post except with 5.1.1. No root, no sideload. Just want standard fix. Can I delete the download file somehow?
[Nexus 9 Q&A, Help & Troubleshooting] the.teejster:
Just follow the instructions here and ( so long as your bootloader is already unlocked) you can upgrade w/o losing any data:

http://xdaforums.com/showpost.php?p=60706069&postcount=30
[Nexus 9 Q&A, Help & Troubleshooting] dassub:
"fastboot oem unlock" wipes the device (factory reset). I just went through this yesterday, after having a completely stock device have OTA fails after downloading the update.

I ended up unlocking the device and flashing the factory 5.1.1 image and wiped my user data anyway.

Now, my question to anyone is, can I just leave my bootloader unlocked at this point, and still be able to receive future OTA updates? I do not plan on rooting or using a custom recovery.
[Nexus 9 Q&A, Help & Troubleshooting] cam30era:
Yes, OTA package does not look at bootloader status.