yashsingh1/xdaforums huggingface dataset:
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] badbadtz.carlo:
i'm using this and it works seemlessly on the Hima..

just need info on where to download the cube, and how to install it on the hima
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] ^^rac:
Touchflo Cube

I see a few devices with the Touchflo cube working onnit (Youtube)

Itll be great to get it working on Hima!!!

Hope someone cracks this one!!!

http://www.youtube.com/watch?v=pB8O_xSzdBE&mode=related&search=

Cube on the Wizard.looks awesome!
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Bingoig11:
ByKa's flash cube is great now, only taking 98kb memory and charging CPU not more than 2% ;)
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Maggy:
I believe this cube is still maturing, actually faster than Byka himself.

I'm very curious what Slither's cube will bring...
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Bingoig11:
A link to post for Slither's cube Maggy? :)

Edit: Found it with a little search, indeed, it promises to be great!
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] ^^rac:
Slither's Cube!

Slithers cube is coming on nicely!

I have installed it on my device! The transition etc is great! Smooth!

It basically gets updated everyday!!!!

Im sure we should have a HTC Cube working soon!!!:)

Keep your fingers crossed!!
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Bingoig11:
Indeed, I checked on Slither's topic, sounds great! :D

Think I'm gonna uninstall my Byka's cube and install both efrost TouchFlo and Slither's cube to test that!

Just hope that I'll have enough space on my device :P
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Bazzz66:
Touchflo running

Hi,

I installed efrosts touchflo_a4. But I can't seem to get it running.

When I calibrate it, I see in the middle on top the "L" & "S".

And then???

I also copied the latest files of Viijay, but it does not seem to work, anyone help??
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] ^^rac:
Thread

Hi!

Follow this thread!

You need to still install the cube file

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

There it says exactly howto! Im sure this cube is going to rock our devices!!

They busy with it!

Cheers
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Bazzz66:
Yep it works now, tnx

Tnx ^^rac,

I got it working, I noticed I installed flashlight to \RAMdisk instead of directly on the device. So I changed the path in the text file.

TouchFlo hangs everytime I try to calibrate, but it works. So I think it is fine.

However TouchFlo does not start the cube if I do not start flash manually, after that it goes perfect. Any suggestions...
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] gangstaunitg:
I bought Qtek 2060 yesterday, is it possible to run touchflo in it? pls answer , thanks
[General Questions and Answers] GenMcLai:
My unit is an mtk6572 the stock rom has analog tv support but all available roms for my device do not have it so i need help in integrating analog tv to amy custom rom
[Galaxy S6 Q&A, Help & Troubleshooting] mwtvz:
Hello XDA,

I could use a little help. I have an Galaxy S6 G920F with stock marshmallow on it. At this moment the phone boots fine and I can fully use it, but I can't enter recovery mode. When I try to enter recovery mode I get the follow error:

"recovery is not seandroid enforcing"

Now I looked up on XDA/Google but the mayority of the problems posted are cases where the phone could't even boot up, in some form of bootloop. Is there any way I can use CWM or TWRP on my phone?

How did I get in this situation?

I downloaded TWRP from the official website, and downloaded 3.0.2-zeroflte and flashed it with Odin (using AP)

I hope somehone can help me with his issue,

Thanks, Mark

TLDR: Phone working properly, cant enter recovery mode.
[Galaxy S6 Q&A, Help & Troubleshooting] GuestD0807:
you have to install a marshmallow BL compatible recovery

like this: https://drive.google.com/uc?id=0B40ItdHKfkyQWTZWS0l3MkVvSDA&export=download

flash it in odin(AP)
[Xperia Z3 Q&A, Help & Troubleshooting] nailyk:
Hi,

First I expect my post is in the right section.

I would like to work on a unbricking process for the sony xperia Z based MSM8974AC phones.

I read a lot of posts about LG nexus 5 and other phones based on the same soc, which, in a bricked state, present himself in a "QD Loader 9006" under windows. Also some other devices, under ubuntu, are external storage attached (emmc directly on /dev/sdb)

What I have understand:

when the emmc is corrupt (but not fried) a rom, somewhere, had basics to present the device to the computer and interact with this loader.

With this loader, the computer should load a emergency hex into ram. Then the phone should be recognized as "QD Loader 9008" under windows. At this step the emergency loader is able to 'serial flash'/'jtag-flash' over usb the emmc.

This process had been applied to the z1 (rhine based board) but, AFAIK, not yet on the shinano.

With some research I found the emergency mode on z3 is hidden, it can only be activated with the testpoint. (Are this one the right one? )

Also on every posts I found, the emergency msm8974.hex loaded into ram is device specific. As I have a working d6603 is there a way to extract it? Where can we found it? (I won't break/open my device!)

Another point is the TA partition. The other unbricking guide I found never had TA partitions. I know our boot choinload is signed:

If you check in the ta partitions they are qualcomm and other sony certificates.

strings TA.emmc.win| grep -i x509

Do you think this certificates are used to sign the chainload? If not where are they stored? (somewhere I read the famous rom with the SPL reside is OTP).

As my goal is to reflash a full emmc (in case of corrupt gpt partition table for example) a ta backup could be enough?

Last think: I plan to buy a xperia to dev on this but it is really expensive for my (about 80$) so my progress on this can be really slow.....

Sorry for long post but I would be the more accurate possible :)

What do you think about it? Is there any chance to get an working unbricking process?

P.S.: for reference.
[Xperia Z3 Q&A, Help & Troubleshooting] Bäcker:
No idea if this is useful info but here goes:

On some devices, i.e. Xiaomi , you get into the Qloader Mode if alle Partitions on the EMMC are deleted. I had the impression that this is similar to the starting point of a newly produced device which has not been flashed with any ROM and thus only offers the "naked" emmc.
[Xperia Z3 Q&A, Help & Troubleshooting] nailyk:
Really interesting!

Also I'm following a thread about swapping emmc on a nexus 5 (also snapdragon 801) and they are able to reflash full emmc.

From your xiaomi information I found this post, and this post. But somewhere i read that our shinano boards can't be placed in disaster recovery without a test-point. (here for the z1).

I'm currently discussing with a z3c seller :) it could be interresting if i can test on a shinano device!

Also, all the xperia bootchain is signed. So what is happening if we start with a empty emmc? Afaik there is a special tag in the GPT header which contain a hash. Could it be the bootchain signature?
[Xperia Z3 Q&A, Help & Troubleshooting] nailyk:
First, yes:

is exactly what i mean. Every thread, forums, blogs, TA dumps, s1 sources i can found, make me understand there is no way to get back. Also a lot of rom (ftf versions) flash weird bootloader to the device. Everything on our xperia bootchain is crappy. If you touch one bit of your GPT headers, you are screwed.

BUT i never try the xperia pc companion as i am a Linux guy which refuse to spend 4 days to install a ****ty os on my computer for one software. So i had a windows7 vm with emma. But every times i try sony pc companion, the device reboot 10 seconds after plugin-in and nothing else happened.

So you are right, my information on this are obsolete as i don't try the 'hero' loader.

I have not yet upgraded the op but now i own a third z3, buy to brick it for this kind of experiments. Do you think it is relevant to give a try with pc companion? (I have not found the testpoints yet)

Are you sure? Did you try it personally? I'm really surprised because i parse my TA dump before unlocking, after unlocking, after upgrading and the structure is heavily modified, so if the bootloader is downgraded with PC companion, the TA partition get downgraded too?

(personally interested because sony refused my repair in despite of the law due to bootloader 'rooted' ;))

Anyway thanks for pointing that, i will take a further look on the hero loader.
[Xperia Z3 Q&A, Help & Troubleshooting] xxlsm:
After upgrading to the Android N Developer Preview and downgrading back with the Xperia PC Companion, I did a new TA Backup just to compare the origin TA-Partions with included DRM functions. I actually noticed a difference in the size of the two backups. But the restore dry run function of TA-Backup didn't show any errors, therefore all signature checks of the tool were executed succesfully on the device with the downgraded bootloader. For this reason I came to my conclusion that a bootloader downgrade is revertible and old backups are restorable. The "cat /proc/cmdline" command output also showed an older bootloader version (no "hero" term included anymore).I didn't restore it in reality because I din't want to mess with my daily rom. I don't know if a downgrade with the "unofficial" Flashtool would lead into the same results with the downgraded bootloader because I haven't given it a try. Maybe I will test it in the future when I plan a clean install anyway. I actually prefer windows either because of the better compiler collection, but I use dualboot because of a specific software I have to use which is only available for windows right now. That's why I din't try to downgrade with the "unofficial" flashtool.
[Xperia Z3 Q&A, Help & Troubleshooting] nailyk:
Just a point, if you get a problem with your TA partition, your device is done, that is why i open this topic: restore a device with screwed TA partition or empty emmc.

All the xperia toolchain is signed, the preloader (not the right word but can remember at the moment), the GPT table, s1 (bootloader), the TA partition and finally the kernel if your bootloader is locked. So if one part of this signed toolchain is 'corrupted' your device won't boot anymore.

I never used the unofficial flashtool too. I never flash ftf files as they always includes TA patches and 'new' bootloader.

I tries multiples times to downgrade my bootloader with the official emma but every times without success, so i guess i will give a try with pc companion on someone else computer.

Thanks.
[Xperia Z3 Q&A, Help & Troubleshooting] xxlsm:
Well in fact I use the unofficial Flashtool, but I haven't tried to downgrade the bootloader with this tool yet because I sticked with the PC Companion for downgrading. You have the opportunity to exclude every component of the tft file (including TA-Updates). Apart from that, our situation is a bit different. I upgraded to the OpenDevices Bootloader with the PC Companion and my TA-Partition remained locked and untouched because I didn't have to unlock it with the PC Companion like with emma. I will wait until an Android N root exploit gets revealed, so that I can backup the origin TA-Partition on the new bootloader to be on the safe site. But in your place, I would still give the Xperia Companion a try in order to unbrick the device. I just wanted to let you know that. And in my case a downgrade from the Android N Hero Bootloader to an earlier version was possible, so maybe it could be worth to try for you.
[Xperia Z3 Q&A, Help & Troubleshooting] mattia.bf:
Cross post with the boot guide thread.

Good evening everyone,

I spoke briefly with [MENTION=6979267]nailyk[/MENTION] about bootloaders and he suggested me to write these pieces of info here.

I'm not a developer nor an expert, so I can't go much in depth, but I was messing around with my D6603 and I flashed the .200 firmware with upgraded bootloader using EMMA.

After that I flashed this firmware (it's Sony's Concept for Marshmallow, latest build), originally posted by [MENTION=7062270]yecomixer[/MENTION] on the thread for this ROM here on xda. Flashing it substituted my upgraded bootloader with the Hero bootloader (This one). So I guess that everyone looking to revert back from the EMMA upgraded bootloader may try that since it worked fine on my device.

The same Hero bootloader can be found on the N Developer Preview for the Xperia Z3, but, even though I flashed that ROM (both DP3 and DP4), I didn't try going from the EMMA firmware to the Developer Previews, so I can't say if it would work in the same way.
[Xperia Z3 Q&A, Help & Troubleshooting] nailyk:
For some few days I have a (sik!) windows computer. Install pc companion and update my brickable device to N preview. Sadly I don't know how to root N so no TA backups before unlock of this device (never rooted, never unlocked).

Sadly I install N, oem unlock, flash twrp then reboot. N refused to start (as usual, fastboot oem unlock empty the partition but doesn't recreate it :s). Hopefully fastboot format userdata/cache solve this.

Now I hope I will be able to dump the hero loader and install it on my other devices.

Then I will test your downgrade process.

One day, by accident, I restore a (unlocked) TA backup of my daily driver on my dev device (both bootloader 'v2'). Nothing changed, device running fine and was on stock o0.

P.S. we notice this partition scheme:

Number Start (sector) End (sector) Size Code Name
1 256 4351 2048K 0700 TA
2 4352 5375 512K 0700 sbl1
3 5376 5887 256K 0700 s1sbl
4 5888 6015 65536 0700 dbi
5 6016 7039 512K 0700 aboot
6 7040 8063 512K 0700 rpm
7 8064 9087 512K 0700 tz
8 9088 10111 512K 0700 sbl1bak
9 10112 10623 256K 0700 s1sblbak
10 10624 10751 65536 0700 dbibak
11 10752 11775 512K 0700 abootbak
12 11776 12799 512K 0700 rpmbak
13 12800 13823 512K 0700 tzbak
14 13824 54783 20.0M 0700 boot
15 54784 75263 10.0M 0700 ramdump
16 75264 108031 16.0M 0700 recovery
17 108032 108095 32768 0700 DDR
18 147456 150527 1536K 0700 modemst1
19 155648 158719 1536K 0700 modemst2
20 163840 166911 1536K 0700 fsg
21 172032 188415 8192K 0700 apps_log
22 188416 189439 512K 0700 misc
23 189440 190463 512K 0700 persistent
24 196608 4382719 2044M 0700 system
25 4382720 5406719 500M 0700 oem
26 5406720 5816319 200M 0700 cache
27 5816320 30535646 11.7G 0700 userdata

edit: maybe I will test downgrade quicker than expected because now I'm stuck at error 7 into twrp with empty device ;)
[Xperia Z3 Q&A, Help & Troubleshooting] nailyk:
So this hero loader is the worst ever.

With non stock kernel he refused to work at all. No way to enter into recovery, no commands accepted.

I'm now downloading the .575 with emma. At the bottom of the windows the bootloader version included is mentioned. All the version proposed for my device are '27' which is the 2nd one.

So I really don't get how do you downgrade to '15' [MENTION=7029289]xxlsm[/MENTION] ... Maybe you have another list of rom proposed and mine doesn't include the first version.

While flashing with pc companion and with emma device is in flashmode and recognized as "SOMC Flash Device".
[Xperia Z3 Q&A, Help & Troubleshooting] munjeni:
Sony devices is diferent at least which I found on z1c. Sony unbrick bin is caled s1 boot preloader. Binary file is very similar to mprg binary (the same header have) but sony certificate is at the end of the bin file. That bin is signed with sony certificate. How things work. Test point puts phone into s1 boot download mode, preloader is sent to phone, verified header (0x40 bytes), sent body, and finaly certificate verified, after that unbricking things is sent similar like flashing with ftf. You can't use mprg files which is not signed by sony! Sony unbrick proces you can sniff by an usb protocol sniffer by sniffing for example s1tool which have unbrick binary for z1c, trought sniff dump you can see all protocol things and also construct/extract that preloader as I allready done, that binary file is signed by sony which mean pbl indeed expects sony certificate. If trim area is broken or formated there is no way to unbrick by preloader, only by direct emmc for example by using z3x easy jtag tool with emmc adapter, for that you will need pinout. Just to save your time :)
[Xperia Z3 Q&A, Help & Troubleshooting] nailyk:
Thanks a lot.

I read many times your mission impossible thread and found a bunch of useful information about a possible unbricking process. With this and some other topics (listed into the OP iirc) I have in mind exactly what you described: sniffing emma to dump the preloader.

I also subscribe this thread which learn me there is a raw eMMC access into the soc.

Maybe you know I'm currently reading free-electrons documentation? Last one. They have some slides about the boot process. So I can't understand something: if we have an empty eMMC and put the phone into qdloader mode, there is no eMMC access by the soc as the minimal loader (s1 boot download) is too small to handle it, that is why we need the preloader. If the preloader isn't signed (custom one or something like this) why would it prevent rewriting TA or the full eMMC?

btw all of this is still untested because I didn't find pinouts. How do you find it for your z1c?
[Xperia Z3 Q&A, Help & Troubleshooting] munjeni:
If you brick trim area in hard way as I done 2 years ago, you will not be able to repair trim area by test point anyway (which is a main problem). You can flash other things but not trim area since we don't have trim_area in sin format - mean signed format! In that case your trim area is damaged device will not boot which mean hard bricked. All things put to sony must be signed by sony cert. Not signed mean can't use. But Z3X jtag tool with emmc adapter alow you to solder box pinouts to the your phone emmc pinc - direct access (pins you need to locate on mainboard). In time when I bricked my phone I didn't found pinouts :( but now after I updated pc software of the easy jtag some devices is updated including my z1c, now I have pinout but thats too late since I already got new mainboard and it was a year ago...

About qhsusb bulk I think it will not work since on nexus device boot chain is totaly diferent that sony one.
[Xperia Z3 Q&A, Help & Troubleshooting] nailyk:
I wanna ask you [MENTION=4120742]munjeni[/MENTION] about how you find the testpoint but rereading your post make me feel it will be hard.

Anyway I will be more active on this thread now as I just f*ck my device replacing the tz partition.

Who can use tz to boot. Those sony bootchain is a real crap.

some links:

testpoint: https://xdaforums.com/z3/help/help-z3-hard-bricked-t3216404

testpoint: http://www.forensicfocus.com/Forums/viewtopic/t=15219/

hardware manuals: http://gsm-manuals.com/59-Sony schematics and service manuals.html
[Xperia Z3 Q&A, Help & Troubleshooting] nailyk:
So the test point of my d6603 is at the same location. I will edit this post with a picture later.

Recognized at:

Bus 001 Device 022: ID 0fce:9dde Sony Ericsson Mobile Communications AB
[Xperia Z3 Q&A, Help & Troubleshooting] nailyk:
Looks like there is no s1tool for z3. The most recent version I found is 19.05.2015 and get this output:

Welcome S1 Tool [19.05.2015].
That is small and crippled subset of SETOOL2 service tool.

TO CONNECT NEXT PHONES
X10 Xperia,E10 Mini,E15 Xperia X8,U20 Mini Pro
LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
PRESS AND HOLD "BACK" BUTTON...

ST18 Xperia RAY,ST15 Xperia Mini,SK17 Xperia Mini Pro
and Sony Xperia phone
PRESS AND HOLD "Volume Down" BUTTON...

PLEASE ATTACH TURNED OFF PHONE NOW
Waiting for phone ...
PROCEDURE STOPPED BY USER
supported phone was not detected
Elapsed:65 secs.

SELECT FIRMWARE PACKAGES
YOU CAN SELECT SEVERAL PACKAGES WITH CTRL BUTTON
CHECKING PACKAGES ...

DETACH USB CABLE FROM PHONE
REMOVE BATTERY FROM PHONE
ATTACH TESTPOINT
PRESS "READY", THEN ATTACH USB CABLE TO PHONE

will use Sahara protocol ...
REMOVE TESTPOINT NOW, THEN PRESS "READY"

PROCESSING ...
SERIAL NUMBER : 196A460E
HARDWARE ID : 04000100E1407B00
HASH :CF19D6FAD8029B66B15246BF3C9D216FC1D2235D87706E0458C7125BB1E436EC
[B]HARDWARE ID 04000100E1407B00 NOT SUPPORTED
[/B]Elapsed:35 secs.

Edit: Looks like the official website for s1.
[Xperia Z3 Q&A, Help & Troubleshooting] nailyk:
d6603 testpoint

sony xperia z3 D6603 testpoint

recognized as

SOMC Flash Device

or

0fce:9dde Sony Ericsson Mobile Communications AB

After blinking red one time.

Battery need to be removed.
[Xperia Z3 Q&A, Help & Troubleshooting] nailyk:
[MENTION=4124152]mathorv[/MENTION] why you deleted your post?

Links looked fine.

I didn't try SEMCTool Flasher but will do asap. [MENTION=7006025]BigCountry907[/MENTION] also tell me about a specific revival cable.

Will try this too asap and report.
[Xperia Z3 Q&A, Help & Troubleshooting] mathorv:
About https://xdaforums.com/showthread.php?t=1333818

Wanted to help but I was afraid of making fool of myself :)

million different ideas ( no neccessary OPs, but maybe some clues in threads)

http://forum.gsmhosting.com/vbb/f778/sony-xperia-z-c6602-c6603-c6606-c6616-dead-boot-repair-1877259/

http://forum.gsmhosting.com/vbb/f778/sony-xperia-z1-c6902-c6903-dead-boot-repair-1876818/

http://sony.yt/topic/7732-sony-xperia-z3-d6616-bricked/

Explanation of why s1 tool is not for z3 - no broken z3 rsa 4k key(missing vulnerability):

http://sony.yt/topic/7820-sony-xperia-z3-dual-d6633-damaged-ta-trim-area/

s1tool info

http://sony.yt/topic/5324-s1tool-tu...l-xperia-qsd8250-msm7227-msm8255-smartphones/

You are sure that buying one with "borken" screen is out of the question?

some people mentioned holding vol button for two minutes while reviving z3
[Xperia Z3 Q&A, Help & Troubleshooting] nailyk:
Thanks.

Don't be, am a bit desesperated right now and try everything.

I already read almost all his posts.

I also tried lot of z1 related things. Some nexus 5 too.

AFAIK the qcom keys get leaked but cannot find something helping me on this.

My devices are already broken device with replaced parts. Now I have a lot of unusable spare parts :s

Thanks trying to help. It seems that all 8974 devices are unbrickable, except sony.

Also after some readings it seems a jtag flash wont work too as it require a z3 specific software.
[Xperia Z3 Q&A, Help & Troubleshooting] mathorv:
To be honest I would even ask sony service about firmware failure if they can restore anything, doubtful yet theoretically possible.

I'd register on hsony.yt and gsmhosting.com and asked there (on a different handle if you re not comfortable with this one)

Despite shady reputation of gsmhosting there are very knowledgeable people there.

I remember my first alternative soft experiments with HTC desire, bricking it so many times and sometimes being on the edge of despair.
[Xperia Z3 Q&A, Help & Troubleshooting] nailyk:
Serial output of the BL without test point:

Format: Log Type - Time(microsec) - Message
Log type: B - since boot(excluding boot rom). D - delta
B - 288896 - SBL1, Start
B - 294142 - scatterload_region && ram_init, Start
D - 0 - scatterload_region && ram_init, Delta
B - 311100 - pm_device_init, Start
D - 27511 - pm_device_init, Delta
B - 338794 - boot_flash_init, Start
D - 14975 - boot_flash_init, Delta
B - 354105 - boot_config_data_table_init, Start
D - 0 - boot_config_data_table_init, Delta
B - 360235 - PBS setup, Start
D - 1159 - PBS setup, Delta
B - 366091 - sbl1_ddr_set_params, Start
B - 370605 - Pre_DDR_clock_init, Start
D - 274 - Pre_DDR_clock_init, Delta
D - 0 - sbl1_ddr_set_params, Delta
B - 384025 - pm_driver_init, Start
D - 37423 - pm_driver_init, Delta
B - 421906 - clock_init, Start
D - 152 - clock_init, Delta
B - 425017 - Image Load, Star

Nothing with the testpoint.

P.S.: last "Start" is not complete, not a typo.