Develop Bugs

the answar for splash screen it works on jasjar

heyyyyyyyy i have just finished my jasjar and it realy worked it was dead for 14 days her is wt i did i was searching for an answar for splash screen i tried mtty and her is the way
first disconect ur active synic and put ur jasjar at bootloder screen then open mtty( if set 14 0 didn't work and task 28 didnt work 2 try this task 2855aa then ) it will work then your screen will be total black and no hard rest or even soft rest will work don't panic just take the battry of the jas and let it out for 15 min then put it back 2 the device then charge it for 10 min or more as u like then try boot loder way (light+power+rest) it will be back at boot lod screen put any rom you wish and it will be back again best luck all
i don't know if it works with any other device so best luck

help with flashing (bricked) ASUS a696

I just bricked my a696 in the process of doing the official asus update and have been trying to unbrick it using the information in this forum (particularly here and here) without any luck. I was wondering if anyone could help me with this problem. this is what I have figured out and done from my reading:
1. I have downloaded the image file for my unit - A696_dump_wm6_2_eng.rar
2. I have also downloaded USBLoader.exe
when I connect my pda, I can get it into the mode where it accepts usb input (POWER + ENTER + RESET). However when I try to run usbloader I get a bunch of errors that seem to suggest that my computer can't open a connection to the usb port.
------------------------------------
C:\usbloader nk.nb0
#####################################################################
# USB image transfer tool for Intel PXA27X USB Development Board #
# Version: 1220'04 Author: O.C #
#####################################################################
try to open \\.\wceusbsh001
try to open \\.\wceusbsh002
try to open \\.\wceusbsh003
try to open \\.\wceusbsh004
try to open \\.\wceusbsh005
USB pipe opening error
------------------------------------
I am using vista business, and am running the command prompt in administrator mode. I have also tried doing the same procedure on a windows xp machine and it has given me the same error. When I connect my pda, windows does detect the connection and loads a usb device driver. Active Sync does not start. I feel like I am missing something very basic that I just don't know about. any help would be greatly appreciated, thanks in advance!

Same problem
OK ..I am now up to the same spot. The next step I am going to try is to try to do it from the SD card using this method. I will let you know how I get on.
Anyone else offer any suggestions?
JohnYW

Fixed
I managed to get my ASUS 696 back again, thanks to the info posted on this forum.
Using the NB0 file plus USBloader.exe finally got it to go. It seems the loader only looks at the first 5 USB ports and if you are plugged into anything higher it doesnt find it. I am using a laptop with a docking station and 2 monitors so had numerous USB ports. When I plugged it into one of the two ports on the laptop itself - Voila - it worked and I now have a working ASUS 696 - no longer a brick!
1. Download the A696_dump_wm6_2_eng.rar file plus USBLoader.exe files.
2. Unzip the rar file
3. Run command prompt and navigate to where these files are.
4. Connect USB cable to bricked unit
5. Hold power and Enter and hit reset and hold till unit goes into USBloader mode
6. From the command prompt run the USB tool with the unzip file and sit back and watch. About 2 minutes and it will reboot. Hopefully all well.
To find those files just google them - good luck

Not fixed for me
I only have 3 USB-ports on my Laptop and USBLoader works with none of them.
The PDA installs himselve as:
-Windows CE USB-device
-- ASUS USB Sync
Outside of the USB-Controller tree.
I get the exact same error as influxx described. Is there any other way to get USBLoader check all the USBs or getting the connection going?
My system is WIN-XP SP2.

Half fixed
Well, i managed to establish the usb connection by using a 10-years-old Laptop with only two USB1.1 ports.
Now i get to that point:
C:\PDA>USBLoader.exe nk.nb0
#####################################################################
# USB image transfer tool for Intel PXA27X USB Development Board #
# Version: 1220'04 Author: O.C #
#####################################################################
try to open \\.\wceusbsh001
The file nk.nb0 was opened
Image total Size 61808640 bytes
NB0 image downloading.....
File nk.nb0 total 61808640 byte read
Size of ACK_PACKET = 20 address of buffer=7c91ee18
<PIPE00> R : request 20 bytes -- 20 bytes read
What we read AckType < 55aa > dwRet < 99 >
Size of ACK_PACKET = 20 address of buffer=55aa
The PDA shows 100% ... but thats all...
No restart, nothing (I waited 15min). If i unplug or reset the PDA i get an infinite number of lines like this:
........
<PIPE00> R : request 20 bytes -- 0 bytes read
What we read AckType < 0 > dwRet < 0 >
Size of ACK_PACKET = 20 address of buffer=0
<PIPE00> R : request 20 bytes -- 0 bytes read
What we read AckType < 0 > dwRet < 0 >
Size of ACK_PACKET = 20 address of buffer=0.........
And my PDA acts like before. Is my Rom dead?
EDIT: No it wasn't. The mainboard kept analyzing the Battery as too low and so everything (flashing included) was locked.

Asus 696 bricked
Can anyone please post an .DIO and or other fix to get my Asus A696 back to work? (pref. WM6 engl)
It hangs on the ASUS bootscreen, after an unsuccesfull ROM upgrade...
I can't use usbloader.exe and nk.nb0 file since I have not a USB cable, and I am forced to use a method of recovery that use only the SD card.

CyBear said:
EDIT: No it wasn't. The mainboard kept analyzing the Battery as too low and so everything (flashing included) was locked.
Click to expand...
Click to collapse
So what did you do to fix it? I am having the exact same problem. (bricked 636N after failed update to WM6)
--EDIT--
Ok my problem was that I dumped a WM6 from another 636N and the bricked one was WM5. After restoring a dutch WM5 image (which worked) I updated to an english ROM that worked.
The one thing tipping me off to find a WM5 dump was that at around 84% when restoring, the counter jumped back to 1%, continued to 14% then jumped to 100%.
Thx for all the wonderful advice on this forum. Now I have not only a working 636N but also the knowledge to restore one if it breaks in the future (I have around 20)

CyBear said:
Well, i managed to establish the usb connection by using a 10-years-old Laptop with only two USB1.1 ports.
Now i get to that point:
C:\PDA>USBLoader.exe nk.nb0
#####################################################################
# USB image transfer tool for Intel PXA27X USB Development Board #
# Version: 1220'04 Author: O.C #
#####################################################################
try to open \\.\wceusbsh001
The file nk.nb0 was opened
Image total Size 61808640 bytes
NB0 image downloading.....
File nk.nb0 total 61808640 byte read
Size of ACK_PACKET = 20 address of buffer=7c91ee18
<PIPE00> R : request 20 bytes -- 20 bytes read
What we read AckType < 55aa > dwRet < 99 >
Size of ACK_PACKET = 20 address of buffer=55aa
The PDA shows 100% ... but thats all...
No restart, nothing (I waited 15min). If i unplug or reset the PDA i get an infinite number of lines like this:
........
<PIPE00> R : request 20 bytes -- 0 bytes read
What we read AckType < 0 > dwRet < 0 >
Size of ACK_PACKET = 20 address of buffer=0
<PIPE00> R : request 20 bytes -- 0 bytes read
What we read AckType < 0 > dwRet < 0 >
Size of ACK_PACKET = 20 address of buffer=0.........
And my PDA acts like before. Is my Rom dead?
EDIT: No it wasn't. The mainboard kept analyzing the Battery as too low and so everything (flashing included) was locked.
Click to expand...
Click to collapse
I have the exact problem, it loads to 100% then gives me these errors. How the hell do i fix this. PLEASE somebody give me some support on this, the battery has been charging for hours so i cant imagine it thinking i dont have enough battery power.

JohnYW said:
1. Download the A696_dump_wm6_2_eng.rar file plus USBLoader.exe files.
2. Unzip the rar file
3. Run command prompt and navigate to where these files are.
4. Connect USB cable to bricked unit
5. Hold power and Enter and hit reset and hold till unit goes into USBloader mode
6. From the command prompt run the USB tool with the unzip file and sit back and watch. About 2 minutes and it will reboot. Hopefully all well.
To find those files just google them - good luck
Click to expand...
Click to collapse
I have asked this in another thread as well with no response. What/where is this ENTER key??????? I know where the POWER button is and I know where the RESET button is but nothing on the unit or in the manual says ENTER.

same problemmm... which is the enter key ???? reset and power i understand... help me pls

The enter key is the one in the center of the circular directional pad. Press that button and the power button while hitting the reset. Hold these buttons until the USBloader screen comes up. Hope this helps, good luck!

[Q] Random reboots and frustrating boot loops

Hey all,
I've been having boot-loop problems for almost a month now. The phone just abruptly reboots and goes into a boot loop with just the HTC screen. The problem is fixed temporarily if I remove the battery for a while and then power it back up. If I start having too many things going on, such as several tabs in DolphinHD, downloading several updates, etc. [no gaming at all] it'll do the same thing and just reboot.
I was running Cyanogen 6 [stable] with Kingxkernel #2. I was not overclocked, but did have a few setcpu profiles active. I've tried everything imaginable since they began:
-Tried a different kernel [SNAP], didn't work
-Truned off setcpu, didn't work
Today, I got fed up with everything and then decided to flash a Sense ROM hoping that that would fix everything. I flashed the latest Fresh and after the install, even before I could skip all the set-up stuff, the phone started to reboot again.
As for the Fresh installation, I wiped fully including dalvik and cache all in RA.
I'm about to go crazy. I wan't my fully functioning phone back. Please help
EDIT: Also, I forgot to mention that around the same time the random reboots and bootloops began I got a new battery. It was the one from Best Buy made by Seido. Idk if that would affect anything seeing as I get the same problems with both batteries.

if i was you i would do all the following:
1. titanium backup all your apps...
2. flash clockwork recovery
3. nandroid backup everything
4. wipe /system
5. wipe /data
6. wipe /boot
7. wipe /cache
8. wipe /dalvik
9. install rom of your choice
10. run it for a few hours and push it as hard as you can to cause a reboot
- if it reboots -> plug into computer load up terminal/command prompt do adb logcat (copy and paste where and why it reboots)
- if it doesn't reboot -> start reinstalling your apps one at a time or in batches until you find the culprit (unlikely since most installed apps should only cause a force close rather than a reboot but still worth a shot)
11. post back with your findings... ?
fyi the nightly builds seem more stable than the stable build ever was... at least to me on my evo it was...

Thanks for the reply.
I'm going to try that to see what happens. I'll post asap.

Alright, I flashed Clockwork as you said and wiped/formatted everything you mentioned. After that, I flashed Fresh. Everything went well until it went through it's first routine reboot after flash; I didn't even get to pull down the lockscreen into activation before it randomly rebooted. I did a logcat on the first reboot. This is a little piece of the last part of that:
V/libgps ( 292): DeferredActionThread pthread_cond_wait returned
V/libgps ( 292): PA event: 0x00000040
V/libgps ( 292): PDSM_PA_EVENT_GPS_LOCK 0
D/dalvikvm( 292): GC_FOR_MALLOC freed 618 objects / 115992 bytes in 145ms
I/ActivityThread( 674): Publishing provider com.htc.dcs.provider.utility: com.htc.dcs.service.utility.UtilityProvider
D/dalvikvm( 292): GC_FOR_MALLOC freed 55 objects / 177104 bytes in 74ms
D/dalvikvm( 292): GC_FOR_MALLOC freed 296 objects / 253256 bytes in 86ms
I/ActivityThread( 674): Publishing provider com.htc.sync.provider.weather: com.htc.sync.provider.weather.Provider
D/ConnectivityService( 292): getMobileDataEnabled returning true
I/ActivityThread( 674): Publishing provider com.htc.socialnetwork.snprovider: com.htc.socialnetwork.provider.SocialNetworkProvider
horiveira:tools stgomez91$
Click to expand...
Click to collapse
It rebooted after the second to the last line. This is my first time using logcat, so I don't know too much about what any of that stuff is, except for the last line obviously.
Can anybody tell the reason why I get these problems by looking at that?
Here's a copy of the logcat file: http://www.sendspace.com/file/kt3lj1
I was hoping this would work, but alas...it did not. What do I do now??

Had the same problem.
For me the solution was to reset the GPS and after that all the random reboots stopped.
Dial : ##GPSCLRX#
Enter your MSL Code
let the phone reboot.
I hope this works for you.

How do you get your MSL code?

Gonna try that now, I hope it works...
How did you figure out it was the GPS?
EDIT: Just tried what you suggested. Didn't seem to work: after it rebooted and got past the Fresh screen, it rebooted without me touching it.

jthurs said:
How do you get your MSL code?
Click to expand...
Click to collapse
Use MSL reader, it's in the Market (and free).

Alright, after doing what aj74 mentioned and it not working, I left the battery out for a bit then powered it back on. That was at 3pm. At around 4, it had yet to reboot so I decided to restore all of my apps with Titanium Backup. I have yet to have a random reboot, though I highly doubt it's fixed.
I'm afraid to use my phone :-/

same problem. looks like this is becoming more and more frequent. i have tried unrooted, and a bunch of rooted roms. this is a problem that needs solving fast.

lo' and behold, as I was getting confident and rearranging things on the phone the loops began again.

I guess I feel better
Well, I feel better since it isn't just me. It has been working fine, then I took the phone on my first trip and as soon as I got off the plane on Wednesday, the random restarts started.
I'm guess some type of app update caused it, but god only knows which one. I did a factory reset, the gps reset, restored a nandroid backup from late september, and turned off all synching. Still get the reboot loop.
I seem to be able to make it stop for a little while by putting the phone in the freezer, but I can't believe we would all start having this problem at about the same thing if it was simply a overheating issue.
Update:
I was roaming when all of this happened, and now that I'm home, I haven't been able to get the phone to mess up. This will make it tough to take in for service. It still may be a heating issue, however, since it is not hot where I live, but it was hot where I was visiting.
Update 2:
I have now been able to get the problem to happen in my home area. The battery temp was > 100 F when it happened.

[Solved... kind of] Folders showing as binary via MTP?

I just got Google's official USB Type-C to USB A cable today. Weirdly, upon plugging my N5X into my computer for the first time, the file system did not come up as expected. What show as folders locally on my device, show up as binary files in Nautilus on Ubuntu 15.10. Never seen this behaviour before in any Android device. Using an MTP connection.
Screenshot attached helps to explain the issue a little bit better.
Additionally:
Code:
$ pwd
/run/user/1000/gvfs/mtp:host=%5Busb%3A001%2C014%5D/Internal storage
$ ls -la
total 29
drwx------ 1 sec sec 0 Dec 31 1969 .
dr-x------ 1 sec sec 0 Dec 31 1969 ..
drwx------ 1 sec sec 0 Jan 29 1970 Alarms
drwx------ 1 sec sec 0 Nov 21 16:38 Android
-rw------- 1 sec sec 4096 Nov 21 20:40 APG
-rw------- 1 sec sec 4096 Nov 21 20:40 data
drwx------ 1 sec sec 0 Nov 21 20:54 DCIM
drwx------ 1 sec sec 0 Nov 21 20:41 Download
-rw------- 1 sec sec 4096 Nov 21 20:40 Kik
drwx------ 1 sec sec 0 Jan 29 1970 Movies
drwx------ 1 sec sec 0 Jan 29 1970 Music
-rw------- 1 sec sec 11 Nov 21 20:38 .nds
drwx------ 1 sec sec 0 Jan 29 1970 Notifications
drwx------ 1 sec sec 0 Nov 21 20:30 owncloud
-rw------- 1 sec sec 63 Nov 21 20:46 pia vpn.txt
drwx------ 1 sec sec 0 Nov 21 20:45 Pictures
drwx------ 1 sec sec 0 Jan 29 1970 Podcasts
drwx------ 1 sec sec 0 Jan 29 1970 Ringtones
-rw------- 1 sec sec 4096 Nov 21 20:40 .secure
-rw------- 1 sec sec 4096 Nov 21 20:40 Snapseed
-rw------- 1 sec sec 8192 Nov 21 20:40 Tumblr
drwx------ 1 sec sec 0 Nov 21 21:41 yahoo
Notice that `APG`, `data`, `Kik`, `.secure`, `Snapseed`, and `Tumblr` all show as -rw------- files and not as regular directories. What gives? Anyone have a similar problem / solution?

Saw the same thing with that version of Ubuntu. It is known to have issues with android

zelendel said:
Saw the same thing with that version of Ubuntu. It is known to have issues with android
Click to expand...
Click to collapse
Strange. I had no issues with my old Moto G (on 5.1.x) on the same machine running 15.10. Do you have any more information? Can you point to a source that says this is true? 15.10 is a stable release and I can't think of a reason why a broken version of gvfs would be shipped with it.

Narwhal73 said:
Strange. I had no issues with my old Moto G (on 5.1.x) on the same machine running 15.10. Do you have any more information? Can you point to a source that says this is true? 15.10 is a stable release and I can't think of a reason why a broken version of gvfs would be shipped with it.
Click to expand...
Click to collapse
2 very different devices and very different OS versions. 15.10 has its own issues and many android developers have advised against using it. Even Google developers don't advise it.
You can have a look in the Ubuntu forums. I came across it awhile ago when android M first came out.

zelendel said:
2 very different devices and very different OS versions. 15.10 has its own issues and many android developers have advised against using it. Even Google developers don't advise it.
You can have a look in the Ubuntu forums. I came across it awhile ago when android M first came out.
Click to expand...
Click to collapse
I've done a lot of searching through the Ubuntu forums as you've mentioned and come up with nothing. I asked this same question on AskUbuntu, but no one else seems to know what's going on...
I have however determined it's not an issue with Ubuntu. I tested on a recent Arch Linux installation, and I got my hands on a Windows computer to test the issue, and its the same thing. Those folders still show up as files over MTP, which is really annoying and kind of concerning. Any leads on what I can do to fix it?

Narwhal73 said:
I have however determined it's not an issue with Ubuntu. I tested on a recent Arch Linux installation, and I got my hands on a Windows computer to test the issue, and its the same thing. Those folders still show up as files over MTP, which is really annoying and kind of concerning. Any leads on what I can do to fix it?
Click to expand...
Click to collapse
So it was definitely an issue with the Android file system. No idea what, why or how it happened, but obviously something went funky with some the folders on my device (still really curious as to what though).
Issue was fixed by painstakingly recreating the folder structures and moving files via Amaze File Manager from the old [corrupt?] folders to the new ones on my Nexus 5X. Hard problem to explain, easy enough to solve though I guess.
Thankfully data integrity was kept and I've yet to encounter any further issues with MTP on Ubuntu 15.10, Arch Linux, nor Windows 8.1. :good:

@Narwhal73. Just experienced the same folder problem. Occurred when Titanium Backup created it's backup folder. It was normal with ES or Root Explorer on the device, but on the computer (USB/MTB) it was a 4K file. Deleted it on the device, created the backup folder on the computer, ran TiBu and it's all normal now. Some crazy stuff going on. (Win7, 5X 6.0.1 Pure Nexus)
Update 1/18/16: (Found this -possible- solution on reddit)
Figured it out. Just in case anyone else is having the same problem, what you need to do is go to Settings>Apps> click on the three dots and "show system apps". Then delete the data from the External Storage and Media Storage apps. After a restart, everything should show up again once you are plugged in.
Click to expand...
Click to collapse

Mesmurized said:
@Narwhal73. Just experienced the same folder problem. Occurred when Titanium Backup created it's backup folder. It was normal with ES or Root Explorer on the device, but on the computer (USB/MTB) it was a 4K file. Deleted it on the device, created the backup folder on the computer, ran TiBu and it's all normal now. Some crazy stuff going on. (Win7, 5X 6.0.1 Pure Nexus)
Click to expand...
Click to collapse
I wish I knew of a way to reliably reproduce this issue... This happened for me on the stock ROM, but if it's happening on Pure Nexus too then it's definitely an issue in AOSP. A bug report should probably be made. I'll get around to that sometime soon, though I don't know how useful the report would be without instructions to reproduce it. :\

Xperia S (lt26i) - Bricked after trying to get marshmallow (doesnt turn over)

Hey, are you guys fine?
So, I've tried to install the new update to Xperia S (lt26i) using the aosp_marshmallow_r2.zip, but something was wrong. I tried to use the ADB Shell commmands but how I was in the dark cause I don't know how to use, I made some "d" "line(14 for exemple)" but I dont know how, after this, my cellphone dont turn it on anymore. Just, when I open Flashtool, shows "device connected with USB debugging off", but the led doesn't turn on too, and the steps to install kernels or roms aren't working. When I do the steps, and the last one is "connect the phone with the button "x" pressed", the only thing that happens is that the phone show: device connected with USB debugging off, nothing more. :crying:

Takamasu said:
Hey, are you guys fine?
So, I've tried to install the new update to Xperia S (lt26i) using the aosp_marshmallow_r2.zip, but something was wrong. I tried to use the ADB Shell commmands but how I was in the dark cause I don't know how to use, I made some "d" "line(14 for exemple)" but I dont know how, after this, my cellphone dont turn it on anymore. Just, when I open Flashtool, shows "device connected with USB debugging off", but the led doesn't turn on too, and the steps to install kernels or roms aren't working. When I do the steps, and the last one is "connect the phone with the button "x" pressed", the only thing that happens is that the phone show: device connected with USB debugging off, nothing more. :crying:
Click to expand...
Click to collapse
What did you do?
Repartition?
Are you sure you delete p14 or p1?
Your device turn off it self or you restsrt it?

darknessmc said:
What did you do?
Repartition?
Are you sure you delete p14 or p1?
Your device turn off it self or you restsrt it?
Click to expand...
Click to collapse
Yes, I deleted p14, p13 and p12, after this I try to create the new partition, but I didn't know how to, so I just uploaded the files (aosp_marshmallow_r2.zip and the gapps.zip) and made the instalation by TWRP.

Takamasu said:
Yes, I deleted p14, p13 and p12, after this I try to create the new partition, but I didn't know how to, so I just uploaded the files (aosp_marshmallow_r2.zip and the gapps.zip) and made the instalation by TWRP.
Click to expand...
Click to collapse
Oh god! On which guide you read that for repartition you have to delete p13 n p12....I think you bricked it hard...may be some 1 can help you in this situation...

nageswarswain said:
Oh god! On which guide you read that for repartition you have to delete p13 n p12....I think you bricked it hard...may be some 1 can help you in this situation...
Click to expand...
Click to collapse
:crying::crying::crying::crying::crying::crying::crying:
I hope that this can happen. I love this phone :c

Takamasu said:
:crying::crying::crying::crying::crying::crying::crying:
I hope that this can happen. I love this phone :c
Click to expand...
Click to collapse
Is there any symptoms of life on your phone?

nageswarswain said:
Is there any symptoms of life on your phone?
Click to expand...
Click to collapse
There is two kind of symptoms.
01 - When I plug the Data Cable on PC, shows (on PC only) a connected device, but the PC can't recognize it.
02 - When I plug the phone into the socket without battery, it lights the red light, just not like before when operated normally. This time the LED blinks rapidly and appears in a weaker tone, as if without strength enough.

Takamasu said:
There is two kind of symptoms.
01 - When I plug the Data Cable on PC, shows (on PC only) a connected device, but the PC can't recognize it.
02 - When I plug the phone into the socket without battery, it lights the red light, just not like before when operated normally. This time the LED blinks rapidly and appears in a weaker tone, as if without strength enough.
Click to expand...
Click to collapse
Then Read here and know your device situation and follow the procedures to solve...Best of Luck (Remember in most cases Rubber band trick works well)SO read that part carefully and follow...)

Code:
7 0 19782 loop0
179 0 31162368 mmcblk0
179 1 2048 mmcblk0p1
179 2 512 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 1 mmcblk0p4
179 5 512 mmcblk0p5
179 6 3072 mmcblk0p6
179 7 3072 mmcblk0p7
179 8 3072 mmcblk0p8
179 9 5120 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 16384 mmcblk0p11
179 12 1048576 mmcblk0p12
179 13 256000 mmcblk0p13
179 14 2097152 mmcblk0p14
179 15 27064320 mmcblk0p15
This is the phone Partition Table. If he deleted partition 14, 13 and 12
Then he deleted data partition (14), Cache partition (13) and system partition (12).
You should still be able to boot into recovery. Boot into TWRP>Change partition again you will be ok. Alternatively, Flash using flashtool you will be more than ok.