yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi MIX  Questions & Answers] imapfsr:
So I am two or three weeks in with no protection, front or back, and I hate to say it but the back of my phone is scratched up pretty bad. I use a sleeve to carry it around and I'm not sure if that is what is causing it. Just curious if anyone else has had bad scratching our if it's just me.
[Xiaomi Mi MIX  Questions & Answers] thklinge:
No screen protector, no casing, no nothing. Had it since december 19th. No scratches, still pristine.
[Xiaomi Mi MIX  Questions & Answers] extrem0:
It's forbidden where I live, unfortunately.
[Xiaomi Mi MIX  Questions & Answers] vergilbt:
What is forbidden? Going naked?
[Xiaomi Mi MIX  Questions & Answers] Nicolfa:
I never use the film screen protectors, presently [as with all my past phones] using the provided leather case [will eventually go to a flip cover case - always have them so comfortable with them].
[Xiaomi Mi MIX  Questions & Answers] zunelander:
I prefer carrying my phone naked. Especially, when it's a nice looking phone. You just have to be conscious of having your phone and grip it tight while holding it as opposed to casually holding it in a relaxed manner. Nothing will happen to it if you consciously take care of it. At best, put it in your back pocket while walking and not using it, but don't forget it's there:)
[Xiaomi Mi MIX  Questions & Answers] bark1234:
i have been using this naked since i purchased in September 17. Only issue is ceramic is very slippery, so use side sticker atleast to increase grip.

something like this https://www.amazon.com/Decalrus-Pro...coding=UTF8&psc=1&refRID=2PK292A230JGWCC1JQTT

but put only on side, no back, no bottom and up
[Xiaomi Mi MIX  Questions & Answers] omerbagi10:
I have my MIX since the end of may 2017.

My phone is not totally naked but I dont have a glass screen protector (cause most of the ones I've ordered dont fit the screen well), I only use a rubber case with not much gap in front to protect the screen during a fall, and on 24.9.2017 I dropped my MIX on a sidewalk and the top left corner of the screen shattered a little bit and I have a small crack going down from the top left corner for 3cm to the left side of the screen.

My screen still works great and I have no touch issues and all the pixels on the top left corner are working, so besides some shattered glass I dont have any problem.
[About XDA developers] Templar3lf:
Sign up using Google account loops between "Select Google Account" and "Choose Name".

The signup never actually finishes; you select a Google account from the list, it switches to a page asking you to choose a username, which I know is available because it was available when creating this account normally, which I just did after trying the Google version. Once you choose a username and press enter it switches back to the select Google account page. Rinse and repeat.
[Miscellaneous Android Development] FirstMn:
Hello.

We have EMUI 3.1 Lite, which does not include some features. One of this feature is enable or disable camera shutter sound, it is not avaliable on our phone. I looked into build.prop and I saw here options, which were disabled, so I tried to enable them. First of them worked, it is enable/disable shutter sound option in camera settings, second not works, it's TimeLapse mode. TimeLapse mode showed in Camera app normally but when stopped recording, app started saving video infinitely,so this not work..

What do you need:

1. Huawei Y6 Pro or Huawei Enjoy 5

2. Unlocked bootloader and custom recovery like Cwm or two

3. Optionally root, which we don't have now (it will be faster)

What to do to enable it:

If you have root:

1. Open build.prop, find column ro.hwcamera.sound.muteable=false

2. Instead false write true, so it will look ro.hwcamera.sound.muteable=true

3. You have enabled this option!

If haven't root, but you have recovery and unlocked Bl:

0. Download Aroma FILE Manager flashable zip

0.1 Download root browser from Google Play

0.2 Open it, and go to system folder and open build.prop

0.3 Copy everything, exit build.prop and go to sdcard folder

0.4 Create new file, named build.prop

0.5 Open this new file. Paste everything.

0.6 Find ro.hwcamera.sound.muteable=false and set it to true

0.7 Save file

1. Reboot into recovery

2. Choose Aroma FILE Manager zip to install

3. It will open as normal file manager

3.1 On my TIT L01 CalrivWM recovery don't work touch, so I must use hardware keys, power and volume + -

4. Find your new saved build prop in sdcard folder, copy and paste it into system folder

4.1 For me touch not work. So I find my build prop, I had it in sdcard folder. I had to go down and click on Select all button (Power button is like OK, volume + is up and volume - Is down). Now I had to deselect all files, only build prop keep selected. When I have only build prop selected, I again went down and selected button Copy. Now I must go upside to go back to / and go to system folder where I pasted it.

5. Exit Aroma FILE Manager and reboot.

6. Complete!

If you want to enable TimeLapse, witch don't work for me, find column ro.hwcamera.timelapse=false and set it to true

Screenshot in attached file. I'm Czech, so Ztumit mean mute.

Link to screen (Google Photos)
[Samsung Galaxy S7 Questions and Answers] Kickazz080:
Heyo!

So.. I recently got the 930F and rooted successful with odin, but my question is now, how do I successfully flash a working TWRP without having all the issues ppl describe below the twrp thread for sgs7?

greetz
[Samsung Galaxy S7 Questions and Answers] MrBigWaffles:
after flashing TWRP with odin, enter your new recovery.

Wipe everything, then flash the rest of the files. You won't be able to boot otherwise.
[Samsung Galaxy S7 Questions and Answers] Senaxo:
You must in Odin remove the hook at autoreboot.

And then manually switch off the mobile phone with "Home-Vol--Power", then start with "Home-Vol+-Power" and wait until the TWRP screen comes and then let go.
[Samsung Galaxy S7 Questions and Answers] Kickazz080:
But I didnt flash TWRP yet, cuz I used the CF-Root method by Chainfire, just rooted with odin and got supersu installed, i cant even boot into a recovery? my phone just starts normally, doesnt samsung have a normal recovery?

can I just re-root with a method with TWRP included without worries or am I gonna brick my phone?
[Samsung Galaxy S7 Questions and Answers] Kickazz080:
bump
[Samsung Galaxy S7 Questions and Answers] Abuzar Uzair:
i suggest to full wipe after installing TWRP.
[Samsung Galaxy S7 Questions and Answers] d3adm8n:
Why would you suggest a full wipe? Is it needed?

I did the same thing... used CF-Auto-Root to root my S7 and noticed that I didn't have TWRP. So I just downloaded TWRP Manager from the Play Store and used that to flash TWRP to Recovery. It worked perfectly as far as I can tell, no need to wipe anything.

Unless I've missed something?
[Samsung Galaxy S7 Questions and Answers] Abuzar Uzair:
The full wipe will disable data & sd encryption, so you will not face any problem while flashing roms & kernals, or creating twrp backup.
[Samsung Galaxy S7 Questions and Answers] Kickazz080:
Did it really work? ive read a few other posts about ppl bricking their phones by doing that D:
[Samsung Galaxy S7 Questions and Answers] johnny8910:
Maybe a good read if your on Nougat?

https://xdaforums.com/galaxy-s7/how-to/root-official-stock-nougat-7-0-100-t3540765
[Samsung Galaxy S7 Questions and Answers] Kickazz080:
That's completely unrelated to my issue :(
[Samsung Galaxy S7 Questions and Answers] AzzyC:
I don't know if I'm too late, but this is what I did and it was the easiest way to get TWRP.

Go to the Play Store and download 'TWRP Manager App', when on there hit 'Install TWRP', look for the SG7 type for TWRP and choose the latest datedTWRP (People tend to get Recovery is not seandroid enforcing error because they use an out-of-date recovery image).

It will say there was an error flashing recovery and give the option to Reboot or Reboot Later, but it actually has managed to get TWRP onto your phone so just reboot there and then.

Boom you have TWRP; remember the first thing to do is Format Data.

Good Luck
[Samsung Galaxy S7 Questions and Answers] Kickazz080:
Format data when I first boot the phone after the twrp-installation-restart? or before flashing rom/kernel?
[Samsung Galaxy S7 Questions and Answers] AzzyC:
Format Data after TWRP Installation because our S7 phone has dm-verity and you will not be able to flash zips and ROMs properly. Formatting will get rid of that verity encryption.

Another reason why to format data after TWRP installation is because as this method does not fully get rid of stock recovery and is left dormant, so formatting the data will let TWRP read your Data.
[Samsung Galaxy S7 Questions and Answers] Kickazz080:
Is there any chance of me ****ing up and losing my imei or smth?
[Samsung Galaxy S7 Questions and Answers] AzzyC:
Nope. That is not part of the Data partition so the format shouldn't affect - IMEI No. is part of the EFS partition.

If you do come with any problems though, quote me and I'm here to help. But believe I'm telling you what even I did and I'm running ROMS and shiz now.
[Sony Xperia X Questions & Answers] Nidhal AKA the king:
hi everyone,

as you can see in the picture below, i have 2 Xperia X F5121.. on the left side, is the white one, and it has Color ID2 panel, and on the right side the black one and it has Color ID1 panel. I noticed that the black Xperia X has more warm tint in white color, while the white Xperia X has more cool tint in white color.

[IMG="image"]https://www.flickr.com/photos/53059225@N00/31940932191/sizes/c/[/IMG]

I flashed them both to the same Nougat firmware.

anyone know's the difference between Color ID1 and ID2, and which panel is better?

thanks for your contribution and help
[Xperia Arc Q&A, Help & Troubleshooting] smokerhunter:
Hi all

this is my first post hope it is in the right place ...

so i have a sony arc s device ... i used to have a custom rom on it ... however i wanted to restore the stock rom i have downloaded the files for bother GB and ICS ... when trying to install the ICS through the Flashtool i received an error so i extracted the files and tried to flash the system.sin file through fastboot and it comes with an error that the file has large size ... i tried using the -S argument but still no luck ... did anyone encounter any problems like this ?

and is it possible for someone to point me to a stable custom Rom that i might use ( Last one was very slow )

Note : i installed the GB Rom and it is working and didnt have any errors installing through the flashtool .

hope someone can help me

thanks in advance
[Xperia Arc Q&A, Help & Troubleshooting] M0umou:
Hi,

Which version of Flashtool do you have ?

The recent Flashtool are not compatible with Xperia 2011 devices.

Are you sure you ICS rom is not corrupted ?

Check this : All Stock Firmwares for Xperia Arc S

Read this tutorial to help you : [TUTORIAL] HOW TO FLASH STOCK ROMs WITH FLASHTOOL
[Xperia Arc Q&A, Help & Troubleshooting] GuestK00470:
As [MENTION=7978713]M0umou[/MENTION] said, you will need to get an older version of Flashtool from here (Windows | Linux | Mac) and continue on. I've got a .ftf of the Arc S .587 on my Google Drive so in case you can't flash with yours just download it from here.
[Xperia Arc Q&A, Help & Troubleshooting] PanTra1978:
Hi , I want to flash stock rom but i got this error from flash tool

09/021/2017 06:21:12 - INFO - Flashing data

09/021/2017 06:21:14 - INFO - Closing TA partition

09/021/2017 06:21:14 - INFO - Opening TA partition 2

09/021/2017 06:21:15 - INFO - Processing system.sin

09/021/2017 06:21:15 - INFO - Checking header

09/021/2017 06:21:16 - ERROR - Processing of system.sin finished with errors.

09/021/2017 06:21:16 - INFO - Ending flash session

09/021/2017 06:21:16 - ERROR -

09/021/2017 06:21:16 - ERROR - Error flashing. Aborted

09/021/2017 06:21:16 - INFO - Flashing finished.

what can i Do ? this is 3rd ftf file i downloaded and this error showing :crying:
[Xperia Arc Q&A, Help & Troubleshooting] M0umou:
Hi,

Can you tell me which version of Flashtool do you use to try to flash your stock rom ?

Are you sure you flash a rom for Xperia Arc / Arc S ?
[Xperia Arc Q&A, Help & Troubleshooting] PanTra1978:
Solved Thanks To My Self :D

After one Week Working on this Error i find a way at a moment

Just install older version of flashtool 9.11 in other hard drive and copy ftf file to frimware folder and done !!! :laugh::cool:
[Xperia Arc Q&A, Help & Troubleshooting] M0umou:
So, now is it working ??
[Xperia Arc Q&A, Help & Troubleshooting] PanTra1978:
Hi, Sorry for the late reply.

My Version of the Flash tool is ~ 9.0.11 (don't sure about number) Yes it's work Fine but another problem with my Arc S Is About Battery ?It is Always 100%

Note: The Charger Ic Is Changed by Sony Service In my Town

However Can anyone help me out with this one? Thanks
[G3 Q&A, Help & Troubleshooting] Takadi:
Hello

So my LG G3 D855 is stuck in a Bootloop, the phone was restarting itself only when i enter the Sim Card pin, when i remove the Sim car and turn it on it works fine but when Shoot a video with the camera it reboots itself aswell

i rooted it and installed CrDroid custom ROM on it hoping to work out but it's now stuck it bootloop BUT! it's working only when i plug in the charger after the LG boot animation and when i remove the charger it turns off
[G3 Q&A, Help & Troubleshooting] Sotiris02:
Hello there,

I've had the same problem and i just bought a new battery and it got solved.

Greetings and Happy New Year!
[G3 Q&A, Help & Troubleshooting] Takadi:
Really ? it's all because of the Battery ? i was so worried about the inside hardware (motherboard,Sim card reader ...etc)

i'll go and buy one tomorrow and hope it will fix the problem

Thanks mate
[JASJAR, XDA Exec, MDA Pro General] scholbert:
Hi Universal cracks,

i got a Qtek device which seems totally bricked.

The history of the device is unknown, so my investigation is getting deeper and deeper.

On gathering all information together it seems that the IPL and maybe also the SPL is damaged and cannot be easily revovered, because the bootmenu is not reachable in any way (believe me, i read everything about recovering intensely :o ).

That's why i'm looking for a general way to recover bricked devices using JTAG.

The idea is the following:

1. Access the device via jtag

2. Setup ram according to the setting used in wince or linux kernel

3. Rewrite IPL (it is yet unknown how to do it!)

4. Load SPL as executable binary into RAM using JTAG

5. Start the SPL from RAM

6. With SPL running from RAM Re-format the DOC reinstall SPL into DOC

Restart

That's it!

To resume my efforts so far i may report:

1. JTAG connection established (using OpenOCD or OCD Commander)

2. Init SDRAM (using intel PXA270 development kit setup)

3. Write a file to SDRAM and start it

4. Made a dump of IPL and SPL (using haret)

What did not work???

1. Access mDOC G3 in normal mode via JTAG (seems to stick in reset mode)...:confused:

2. Rewrite IPL using JTAG...:confused:

3. Start the SPL successful from SDRAM base address....:confused:

What do you think specialists!

Anyone willing to help?

Cheers,

scholbert
[JASJAR, XDA Exec, MDA Pro General] HellCrusher:
Hello Scholbert,

Sorry I couldn't help you out on this matter. But When I read your post I thought that you gone deeper than me in this technically.

So can Please go though my problem http://xdaforums.com/showthread.php?t=353063 & help me out to solve WHITE SCREEN Problem?

Thanks in Advance.
[JASJAR, XDA Exec, MDA Pro General] roglio:
bootloader

Hi scholbert, it couldn't be enough to simply rewrite the bootloader?

Please could you post the patched version of openwince jtag?
[JASJAR, XDA Exec, MDA Pro General] scholbert:
Hi roglio,

Maybe you're right :( , restoring the uni via JTAG could be mission impossible (at least the way described in my starting post).

As far as i got to know from various postings, the bootloader itself does some security checks during runtime (password checking, CRC checking ...).

It could require some real awful hacks, to start the SPL from RAM with an external debugger.

I made a lot experiments on other platforms using the openwince jtag.

In this case i used the famous OpenOCD:

http://openfacts.berlios.de/index-en.phtml?title=Building_OpenOCD

There's PXA270 support out of the box!

You have to download the sources from their SVN-repository :rolleyes: .

Anyway i'll have a look on my workstation in a few days, what could be of interest for the geeks out there.

Regards,

scholbert
[JASJAR, XDA Exec, MDA Pro General] roglio:
Geek inside :)

Hi scholbert, all bricked universal are broken because the bootloader was wrongly updated or overwritten with a bad update. If we look for a fresh bootloader, the right starting address and wrote it back we've fixed the major problem. Recover a universal starting from this point is already well documented...

Tomorrow I'll download OpenOCD and try to compile it on cygwin to start doing some experiments.

I lack of some informations anyway: the most important is the address where to put the correct bootloader...

I'll post any further step ahead.

Thanks.

roglio
[JASJAR, XDA Exec, MDA Pro General] scholbert:
Hi again,

this seemed to be happened to my device too. With single stepping starting at address 0x0 there's an error after some instructions. So it seems there's wrong assembler code in the IPL section already.

That's the theory :) .

Good luck for this action! I did compile it on a debian linux system.

Let's assume we got a working device :p .

As far as i know, this is what happens after coldboot (comments welcome):

1. DOC is in reset mode, processor jumps to address 0x0 and excutes IPL

2. IPL initializes RAM, switches DOC to normal mode and copies SPL to RAM

3. further details of IPL functions unknown

4. leaving IPL, jump to physical address 0xa0000000

5. execute SPL ....

The problem is, that at this point various system checks are following.

If something goes wrong before we good USB serial connection or bootloader screen. The processor simply could stop at any instruction and we won't know why :confused: .

Good luck for your next steps!!!

Maybe, we may draw some attention with this little discussion. It would be nice to get things rollin' and someday there'll be hope for all those bricked devices around :rolleyes: .

P.S.:

I already made bootloader dumps. See attachments!

IPL and IPL2 got the same content but they were dumped on different physical addresses. SPL was dumped from RAM. Of course these files were taken from a working device.

scholbert
[JASJAR, XDA Exec, MDA Pro General] roglio:
Hi, after your description of the boot process I'm not so optimist anymore...

Anyway, I've just finished to compile OpenOCD under cygwin, without any major problem.

Just a doubt: which configuration file are you using?

Does you have already configured also the flash banks?

I share your doubts about what's happen after SPL execution... IMHO anyway we should give a chance to a complete reflash: fully dump a working device and after wrote it back to a bricked uni just to see what happen.

Some time ago, I've accidentally overwritten the bootloader of a Toshiba e740 PDA (very nice device indeed). After using a proprietary jtag sw/hw I've resurrected it simply writing the bootloader back in place.

This give me at least a hope...
[JASJAR, XDA Exec, MDA Pro General] scholbert:
Hi roglio,

Great!!!

I will post the configuration file as soon as possible (it's on my linux machine at work :rolleyes:).

No, only the PXA270 chip select for the DOC device was set up. These NAND flashes need special initialisation to switch form reset mode to normal mode to be programmed or to read the filesystem.

This process was not yet successful using JTAG :confused: .

If we are able to access the DOC device in a proper way, this may work.

At least there are professionel programmers on the market, that are able to reprogram these devices using the JTAG interface. But these are very, very expensive :o .

Yes basically this also possible for the uni, but this damn#?=% DOC device is very hard to handle. There's also no linux device driver for these devices yet.

Great work anyway!!!

Our hope should never die ;) .

Best regards,

scholbert
[JASJAR, XDA Exec, MDA Pro General] roglio:
Googling

Hi, scholbert! Today I was googling around and I've found some interesting informations about mDOCs... These special flashrom are internally handled as NAND flash but with the cpu (when used to eXecute In Place XIP) are handled as NOR flash chips. I haven't still found useful information to understand how this could be useful for our goal.

Another interesting information about mDOCs is that exists some pc software that permit to flash them via jtag but are part of very expensive development packages!

Anyway mDOCs are handled by linux! Basically it is possible to patch the linux kernel to handle them via trueffs. I'll be more detailed tomorrow, but my first impression is that these information about linux drivers for mDOC family aren't useful for our project...

Does you have retrieved the conf file for openocd?
[JASJAR, XDA Exec, MDA Pro General] scholbert:
Hi roglio,

that's nice information. I also gathered together anything about the mDOC series i could find, all over the planet. If you need more details :)

Unfortunately, there's no source code of the low level routines to access this device. If someone would share m-systems BDK for the G3, you're welcome!

Yes, but i realized that i used a slightly modified one of the standard package (no SDRAM init, nothing but access PXA270).

You will find it attached!

My efforts with the uni using OpenOCD get stuck at a point, because i only got a very simple JTAG hardware. To use it as a debugger you also need to have influence on the systems reset.

That's why i decided to used some Macraigor stuff to get nice hardware debugger for accessing the universal hardware with OCD Commander.

Obviously both systems are very similar.

OpenOCD is completely GPL, so this should be first choice in the end!!!

You will also find the OCD Commander config file (htc-uni.zip) attached.

This could be the base for an OpenOCD script (very similar stuff).

Just an additional information:

I successfully disassembled the IPL :D . At the moment i'm in the process of clearing up, how the basic init process is working!

I nearly forgot to mention, that you'll need to update the description for the stepping of PXA270 in the OpenOCD source code. If i remember correctly, the C5 is missing. Without it the PXA is not recognized correctly. I will post the updated file tomorrow.

Stay tuned!!!

scholbert
[JASJAR, XDA Exec, MDA Pro General] roglio:
Yes! Post it! Thank you! (or send them to rapidshare or similar).

A weird idea... What do you think about relocate and then recompile IPL and run it from SDRAM?

You should remove and/or modify IPL routines related to SDRAM init anyway!

Which tools are you using to decompile IPL?
[JASJAR, XDA Exec, MDA Pro General] scholbert:
Hi,

I will somehow. Maybe i'll put on my website or post it here!

Very busy at the moment :o .

The first attempt will be to enhance the JTAG config file with all that stuff i already found out, e.g. setup all GPIO, alternate functions .....

Relocate and compile would be nice too, but more work :p .

Someone in the forum pointed out to use radare. This was the starting point for further investigation.

At least radare uses objdump for disassembly.

So i decided to use the tools itself.

Here's a short howto:

Of course you need some skills to point out how assembler code is organized and you'll have to find out where ASCII strings are stored. If you don't check this everything looks like instruction code!

Regards,

scholbert
[JASJAR, XDA Exec, MDA Pro General] roglio:
Ok... I'll look forward for these documents! Thanks!

Great!

After my jtag will be fully functional, I'll try to do some experiments running IPL from memory...

I'm a little rusty... but I'll try!:D

Anyway I found a very great tool for disassembling arm code: IDA Pro v5.2

It is awesome.;)

Cheers,

roglio