yashsingh1/xdaforums huggingface dataset:
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] jordan0001:
Hi

I will try to be brief.

I have a ST18 (which has a bad flash that stops the screen working - if I press power button I can press power off/airplane mode etc but otherwise the screen is unresponsive).

The phone will not go into fastboot mode or be recognised in fb mode in windows (tried 3 different cables and 3 different pcs).

Windows 7 will recognise the phone but will not allow me to install the fb drivers ( I have tried everything, including disabling driver signing and getting windows to ask me what drivers to install).

On an XP machine, I still cannot install fb drivers but PC companion/flashtool/s1tool recognise the phone.

I have tried to work through the advice on here and reflash with various fw with flashtool but it will not fb and flash mode always stops with a security issue at the start of flashing. S1tool stops at the start of flashing with different issues depending on fw such as cannot send s1 command. DoomLord's toolkit does not recognise the phone.

I have tried everything I can find on this forum and on the web but don't want to write pages for you to sift through.

Any pointers would be really appreciated.

Thanks
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] justmpm:
Can you post your log from flashtool and give some more information, like what you did before the problem started, if your bootloader is unlocked, are you rooted, and if you are on a custom ROM or running stock. If your bootloader is locked, have you tried to use PC Companion or SUS to fix your phone?
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] jordan0001:
Thanks for the quick reply justmpm

Sorry I cannot be too specific - the problem started after the phone was "unlocked" by a mobile shop.

From what I can work out, the bootloader is locked and the phone is not rooted. The phone was updated by SEUS to the latest stock.

I have had various flashtool errors, the latest of these was Read error :31 : A device attached to the system is not functioning. If I try another flash to save the log, would it be a good idea to use a particular fw as different fw give different logs?

Thanks
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] jordan0001:
Any ideas at all would help.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] mihahn:
And you have installed the drivers from flashtool -> drivers?
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] jordan0001:
Hi

Yes, installing the flashtool drivers was the only way anything would work. Before that nothing worked which made me think this was more of a driver problem but then it does seem like the phone may be a problem with not being able to go into fastboot.

Thanks
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] a|\|droid_user:
Re: [Q] Help with ST18 bad flash

i think usb debugging is disabled on your phone and the unlocking procedure has your touchscreen firmware corrupted...

did u try repair phone option in SEUS..?

the reason why you got the device is not functioning error is because the usb debugging feature is disabled,not sure though..:confused:

can provide me the other errors you encountered in flashtool,maybe i can help you out..:)
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] jordan0001:
May sound stupid but I have just found the thanks button (really) to thank mihahn and alokbina whose guides were the one's I tried before joining here.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] alund:
So this is your problem?

20/016/2013 13:16:35 - ERROR - Read error :31 : A device attached to the system is not functioning.

20/016/2013 13:16:35 - ERROR - Error flashing. Aborted

i havent see this before :confused:

but, try reinstall the driver and flashtool or check your cabel. or you can try another PC maybe :confused:
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] jordan0001:
Hi alund

Thanks, I have tried different cables and PCs and eventually got one working but not with the standard drivers, only with flashtool and Gordon's gate drivers.

I am not sure if the drivers I have are good or not (I found them on a download site) or if it is a problem with the phone not going into fastboot (so the system not knowing it needs the fb drivers) but when I try to install drivers for fb mode they are not recognised.

Another thing is that, from what was said and from a small mark on the phone, it may have been dropped.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] jordan0001:
I am still searching for answers but I have still not got any ideas where I need to start.

Does anyone think it is a particular issue (maybe the phone or maybe the pc/drivers)?

Thanks
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] rob rich:
AW: [Q] Help with ST18 bad flash.

try flashing a kernel only..maybe this will work...
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] jordan0001:
Hi

Thanks, it was worth a go but the result was the same.

If anyone has got any idea what it might be, it would be a big help so I could start searching for clues.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] rob rich:
AW: [Q] Help with ST18 bad flash.

the same error in flashtool?
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] jesudas:
Crazyyyyyyyyyyyyyy...................

Hi its really sounds crazy to you but believe me i have gone through this with my MINI..................... you have to find another MDPI device or RAY itself an added advantage............ just tick MTP in USB Connectivity and connect it to your another PC i mean try different PC....... let your PC install its drivers after that install Flashtool and now you are good to go its worked for me...........in my case i have installed my friends LWW drivers n its worked for me:good::good: i think you have to try.................... and plz do let me know if it worked happy flashing..........................:D:D
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] jordan0001:
Thanks jesudas - you're a star!

Not completely solved but I've got the right drivers installed so I'm pretty sure it is a phone problem.

Can anyone tell me if it is possible to change the USB settings of my phone without using the touchscreen (maybe using a pc connection or something)?

:)
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] jesudas:
Gr8..........

Hey you are most welcome buddy.......................:laugh::laugh: i think you have to ggogle about ANDROID COMMANDER may be this will help you to solve your problem best of luck buddy.......................:D:D
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] jordan0001:
Solved

Thanks for all of your help.

I downloaded fresh copies of flashtool and drivers and re-installed everything.

As I was setting administrator privileges I noticed that the start menu shortcut was pointing to the 32 bit version not 64.

As my system is 64 bit, I started up the right version and it flashed ok.

:D
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] mnishamk:
Re: [Q] Help with ST18 bad flash.

Please add solved in the title. :D
[Nexus 7 General] Miguelost:
Hi guys, sorry for my english

I have a nexus rooted, stock room and cwm installed but i didint recive the ota update to 4.2.2

Its normal?

Enviado desde mi Nexus 7 usando Tapatalk 2
[Nexus 7 General] licaxda:
I concur, precisely the same situation, stock ROM, stock kernel but rooted

Have also tried to flash using the downloaded .zip but fails with an error code of 7.

Any ideas guys?
[Nexus 7 General] filipathtc:
AW: I cant recive ota update

It depends on which country you're in. I live in Germany and I still haven't got the update
[Nexus 7 General] Miguelost:
I live in chile, but the nexus was buy in EEUU

Enviado desde mi Nexus 7 usando Tapatalk 2
[Nexus 7 General] licaxda:
UK. Sat next to my sister who had received the update...

Could rooting be causing as problem because that's threw only difference between our devices, besides storage sizes, mine being a 16gb, hers being a 32gb.

I'm sure that won't matter, would it?
[Nexus 7 General] spitfire2425:
Force stop and clear data in google play services a couple times. ( I think that's what it is) worked for me.
[Nexus 7 General] Letitride:
Numerous threads popping up all over asking the same questions, Mods are going to shut & lock many of these out soon - suggest that one read and use the SEARCH button. My OTA was downloaded already and ready to install but choose to wait 48 hours first.

4.2.2 rollout is for USA / North America now - gradually - and OTA if you are essentially running stock rom & kernel - simple update without losing Apps or data (CWM backup, always, as best practices) - took me 15 minutes from downloading, prep & backup to actual flashing and reboot, etc.

I opted to take a shortcut and went from 4.1.2 directly to 4.2.2 using the zipped, deodexed rooted version w busy box - bootloader stayed on 3.41 running JDQ39 now, smooth. I uninstalled the DSP/Beats Audio/Noozxoide EIZO-rewire audio Apps, just in case - and reinstalled EIZO from Play Store afterward, freeze Chrome browser & switched back on Boat Browser w. Flash Player, OTG mount is working for external USB, etc.

Using N7 from other regions of the world, download using the links here on XDA, check MD5's and then go thru the steps - profit & enjoy.
[Nexus 7 General] licaxda:
Just to confirm then, and this will help a lot of other users:

Being on a stock but rooted rom with a stock kernel would make no hindrance to receiving the ota update, and the advice for people experiencing this situation would be to just be patient and wait?
[Nexus 7 General] K0v4L:
I had same problem, I downloaded stock image of 4.1.2, flashed and found my n7 going in to the bootloop. Downloaded stock image of 4.2.2, flashed and everything is ok. Restored with carbon backup. That is all.
[Nexus 7 General] Letitride:
Yes, my N7 was on rooted 4.1.2 factory rom & stock kernel, with minor tweaks for audio, Chrome browser frozen but no major mods otherwise, and the OTA file was downloaded already on the device when I checked yesterday, ready to install. From various threads posted in the last 48 hours, it's a mixed bags - some install easily while others ran into problems, reasons varied & solutions simple to unknown. I opted for a safer approach - reverse some of my tweaks/uninstalled the audio tweaks, unfreeze Chrome, rebooted & then wipe, before using CWM to flash. It was easy, rebooted and up & running in less than 10 minutes, ALL of the apps & data intact and no FC'd.

For (folks in Europe or Asia, etc.) not willing to wait or access to OTA and prepared to do it on your own (thus, taking the risks, however - small, do your backup first and save your data/settings/etc. with CWM or TWRP and Titanium Backup - to a HDD or USB drive (suggested: 8GB & up) or PC - just in case, for restoration in the "unlikely event" that something go wrong.

Here's the XDA-linked Factory IMG 4.2.2 Nakasi file links, either odexed or deodexed (rooted, insecure boot, etc.) that I used - also, download the bootloader zip in post #2 (not required or needed, but in case you needed it or wanted to use it as the latest bootloader) - http://xdaforums.com/showthread.php?t=2148337

Download, check MD5's and transfer to the N7. Next - launch into bootloader (make sure USB debugging is enabled & unknown source is allowed too) and WIPE dalvik cache and cache (2 times or 3 times each) - then selected the zip to flash. Once done, exit & reboot and wait for it to boot up for the 1st. time and allow it to settle for a few minutes. Click Settings & confirmed that I'm on 4.2.2 and check a few Apps for functionality. Let it sit & shutdown, reboot & proceed to restore most of my tweaks, played videos & music, surf the web to reconfirm that it's running smooth - next, do a new baseline CWM Backup.

Of course, YMMV - if it doesn't work for you, re-trace your steps and take your time, do not RUSH. If all else failed, go back to stock first 4.1 or 4.2 - then, update to 4.2.1 in its rooted state - your saved Apps & data, settings, etc. saved to your PC or USB/portable drive will eventually help you "rebuild" - just a matter of time. (If my other 2 HTC's are that easy to update from GB to JB, I would be very, very happy)

Please give credit for "thanks" to "teshxx" for preparing the Roms and refer to that thread for future questions ...

Good Luck to all.
[Nexus 7 General] licaxda:
Great information, thanks for the hefty reply, may be worth stickying for a few weeks I'm sure others will have the same questions.

I believe installing Beats audio can screw things up too? Can some one confirm?
[Xperia Arc Q&A, Help & Troubleshooting] nblxtu:
Hi everyone!

I have a little trouble with my navigation system sounds on Xperia Arc S.

I'm using iGO Primo and this app is using sounds in *.mp3 format, so these sounds are automatically added to the Walkman application.

The question is : Can i somehow make the folder with these sound hidden for Walkman? Or any other solutions for this issue?

Thanks everyone!
[Xperia Arc Q&A, Help & Troubleshooting] Deleted member 4988456:
create .nosound file in a folder with these mp3 files then clean data for walkman and media scanner and reboot. You don't have to clean data but it will take a while for these files to disappear from walkman app.

.nomedia file is a file that tells android media scanner to not scan this directory and its a plain text file named ".nomedia" without an txt extension. If you cant create this file then you can copy it from "android" folder in you sdcard.
[Xperia Arc Q&A, Help & Troubleshooting] nblxtu:
Did everything as u've adviced (coppied the file from android folder and put in every sound directory) ; unfortunately didn't work (
[Xperia Arc Q&A, Help & Troubleshooting] Deleted member 4988456:
If walkman is using media scanner then there is no way this cant work. Maybe you have to wait for these files to be deleted from app.
[Xperia Arc Q&A, Help & Troubleshooting] nblxtu:
Well, today i have changed ROM and now it works :)) hopefully, that will work forever

Thanks very much !!
[Xperia Arc Q&A, Help & Troubleshooting] Retrosid:
Actually the file was .nomedia that's why it didn't work
[Xperia Arc Q&A, Help & Troubleshooting] nak89:
Flash other Walkman!

You should flash other Walkman now.
[Off-topic] theDroidfanatic:
Alright.

So yeah, there's just one other memes thread, but it has died out, so I thought I'd start a new one here.

Basically, you posts memes here, related to XDA, devving etc.

The rules are the same, little trolling is tolerated, but not hating or flaming, and absolutely no NSFW stuff or stuff with Sexual References.

Let the Fun begin :)

Cheers
[Off-topic] Archer:
The memes thread was merged with the images thread. Please use that :)

http://xdaforums.com/showthread.php?t=1005229
[7" Kindle Fire HD Themes and Apps] Sn0wdune:
THIS APPLICATION IS NOW DISCONTINUED AND IS NO LONGER SUPPORTED!!​

​

​

​

​

"A root checker for Kindle Fires"​

KindlR is a new android application for the Kindle Fire and Kindle Fire HD. KindlR will check your kindle fire for root access.

That is all it will do, nothing else.

Notes to take into consideration:

- KindlR will not root your kindle fire.

- KindlR will not brick your device in any way, shape or form.

- KindlR is based only for Kindle Fires, checking for root on another android device (e.g. Samsung Galaxy S III) will work the same way.

Screenshots:

Landscape:

​

Portrait:

​

Download:

Coming Soon!

Thanks for reading!​
[7" Kindle Fire HD Themes and Apps] xiro49:
Re: [APP] KindlR [DEVELOPMENT]

Y? They are ones on the playstore and if you rooted it youll know that it rooted
[7" Kindle Fire HD Themes and Apps] Krsmqn:
Re: [APP] KindlR [DEVELOPMENT]

Cool. Keep up the good work. Btw, ... wow... that's green!
[7" Kindle Fire HD Themes and Apps] Sn0wdune:
Thanks :) appreciated.

And i thought it was a bit greenish haha, ill change it :P
[7" Kindle Fire HD Themes and Apps] Sn0wdune:
Discontinued.

Sorry for any inconvenience.
[LG Optimus Black] rop12770:
Hi

My P970 is working with CM 10.1.

I have an unlock code, but when I try to enter the 2945#*970# code to insert the unlock code after, nothing happens....

The 10.1 doesn't support this code? Do I need to flash another ROM? If yes, which do you recommend, so I can get back to 10.1 again?

Thanks
[LG Optimus Black] rrgrrg:
For the most stable use izs or marvel d/e ,,they are the most stable
[LG Optimus Black] naveed_hind:
try to change firmware

try to change firmware
[LG Optimus Black] rop12770:
Problem solved.

I installed the Zeus Rom and it worked.
[LG Optimus Black] claus1953:
I bought the unlock codes but i found up to now no way to type it in. The hidden menu has no sim unlock code undermenu (i checked all). all other codes i checked give me no menu pop up (they just give me an error "MMI code not valid"). My phone is LGP970H from Mexico Telcel with stock 4.04 rom rooted.
[Nexus 4 General] randomnoob83:
http://phandroid.com/2013/02/15/ubuntu-mobile-os-developer-preview-feb-21-nexus-4/

cant wait to try it out, will you try it out do you think we'll be able to dual boot ? :laugh:
[Nexus 4 General] casonswag:
We already have a section on this topic
[Nexus 4 General] randomnoob83:
oh my bad lol can you direct me towards it please :)
[Nexus 4 General] jarjar124:
http://xdaforums.com/showthread.php?t=2078727
[HTC EVO 3D] gav83collins:
if ? but ? when ? not possible ? am i dreaming ? lol

this is just for general chat for now

anyone know more than someone else share it here

whats peoples views so far ?
[HTC EVO 3D] gk1984:
I know it isn't out yet, no release date announced, and most likely won't make it to our evo. Is there really a point for this? Stop acting like a kid a few days before Christmas. Only difference is, Christmas you typically get what you wanted.

We don't even have jelly bean except for a few roms. They work well, but aren't perfect. It's almost a year after jb and we just got it and bugs aren't worked out yet. Plus, a lot of developers have moved on. Contracts are getting close to up for a lot of early adopters and they, like myself, will likely move on too. We may only have a couple of devs left here by the time klp drops.

Sorry to be a downer, but we haven't been the thriving community we once were and htc seems to have abandoned us.
[HTC EVO 3D] Jsparta26:
So true so true. The evo 3d had a lot of potential and a great Dev community. As far as HTC was concerned, they care more about money than the consumer so its not surprising they dropped the evo 3d to work on another mid range device. Hardly worth the need to upgrade with very few spec upgrades. Evo 4g lte will probably abandoned sometime this year for a quad core 2gb ram device. Most carriers don't have lte set up everywhere where anybody can take advantage of it. It will be a miracle if HTC pushes a jb update to the evo 3d. If it did. You can guarantee that key lime pie will never see evo 3d
[HTC EVO 3D] ramjet73:
Are you asking about a port of an AOSP based ROM or a Sense based release from HTC? If it's the former, there's a slim chance if all the developers haven't moved on to other devices by the time KLP is released, but there is zero chance of an official Sense based version.

ramjet73
[HTC EVO 3D] dastin1015:
Actually even that won't be possible unless we can get our kernels to work with ION memory allocation. ION is a requirement for 4.1.2+, we were able to get 4.1.2 working by using hacks to use old code and 4.2.1 by using legacy code (same hacks, but much harder to implement).
[HTC EVO 3D] oohaylima:
So 4.2.2 will probably be the last hooray for our device?
[HTC EVO 3D] ipsuvedi:
"Much Ado About Nothing"...lol :D
[HTC EVO 3D] mingolianbeef:
If you want KLP, go buy a Gnex, I agree with all before me, KLP and E3D are not gonna happen
[HTC EVO 3D] Kiinasu:
wasn't ION memory allocation introduced in android 4.0? so shouldn't the stock HTC kernel support it? if not, what is the problem with getting it working?
[HTC EVO 3D] ramjet73:
Here's a post from dastin1015 that explains it in more detail.

ramjet73
[HTC EVO 3D] Kiinasu:
well we got the villec2 kernel source + the evo kernel source. can't we just port a part of the ION memory allocation from the one s to the evo?
[HTC EVO 3D] jekyll86:
R: Key Lime Pie for 3vo general chat

Dastin said that's a very difficult task :(

Inviato dal mio Evo 3D GSM
[HTC EVO 3D] dastin1015:
You still have to properly calculate the memory allocation. msm8660 actually has to use the frame buffer of an msm8960 device. The panel and board config files need to be changed to use the new frame buffer and memory allocation. The camera drivers also have to be changed to use ION and a common-ish camera driver. Not a simple port.

私のEVO 4G LTEから送信される。
[HTC EVO 3D] oohaylima:
You don't have to keep re-explaining yourself brother as to the reason why. People should just learn how to search better.
[HTC EVO 3D] 1ackass:
Dafuq did i just read :D

Sent from my Evo 3D GSM
[HTC EVO 3D] Kiinasu:
thanks for your answer. i started to realize the problem. sometimes i just forget how much depends on little devices differences. think the interest for devs on this device, will be to low, once klp comes out, to make this happen....

well if he would be super annoyed, i think he wouldn't answer. and it's extremely hard to find real information about hardware things.
[HTC EVO 3D] Lothaen:
What makes you sure gnex will get klp?
[HTC EVO 3D] mingolianbeef:
Nexus devices always get the latest and greatest because they r pure Google android devices. They rolled out JB for the nexus s and it is older (and less spec savvy IMO) than the Evo 3D. Whether or not SAMSUNG chooses to update, GOOGLE will, I'm sure the gnex is slighted for next two OS versions at the least, because it can with ICS and 4.1 and 4.2 were released so quickly that it really can't be seen as 2 MAJOR updates, just my take
[HTC EVO 3D] dastin1015:
The carriers do control you though. The Verizon Galaxy Nexus is in testers phase now for 4.2.2 meaning it's preparing for an OTA, while the rest of the GNEX devices have been updated.

私のEVO 4G LTEから送信される。
[HTC EVO 3D] Lothaen:
Nexus S only got 4.1. No official 4.2 update.
[AT&T Samsung Galaxy S II SGH-I777] KeeperOfThePizza:
Just wonder what modem people are using for AOSP Jellybean 4.2.1/4.2.2? Should i just use the lastest samsung jellybean modem? Or is there a specific optimal modem?
[AT&T Samsung Galaxy S II SGH-I777] 122ninjas:
It's location dependent. Like everything else here, TRY IT
[AT&T Samsung Galaxy S II SGH-I777] Pirateghost:
there is no such thing as a 'AOSP modem'

there are different zip files depending on what rom you are on, simply because of the different flashing methods between the 2...the actual modem.bin's are the same.
[AT&T Samsung Galaxy S II SGH-I777] KeeperOfThePizza:
Yes I know theres no such thing as a aosp modem. I should have put a comma between the two.
[AT&T Samsung Galaxy S II SGH-I777] fiffan86:
I personally use uckl7 modem, found it to be the best for my area rural California mountains. Just test each one out for while to see what the best one for you is. I don't think there is an almighty best modem.
[HTC EVO 3D] VictoriousShooter:
So far my 3Ds soft key lights just won't turn off. They're on in hboot, recovery, and on the splash screen. When the screen is off, the keys are on.

I've tried multiple roms, and I've even ran multiple ruus, no change.

Is there anyway to cure this?
[HTC EVO 3D] naveed_hind:
try to check hardware

i think its hardware problems it must be water damage
[HTC EVO 3D] VictoriousShooter:
But I never got it wet
[HTC EVO 3D] VictoriousShooter:
So no one has any ideas as to why this is happening?
[HTC EVO 3D] jekyll86:
R: Invulnerable Soft key lights?

It's hardware related

Inviato dal mio Evo 3D GSM