yashsingh1/xdaforums huggingface dataset:
[YotaPhone] lexman941:
thx a lot for explanations , I had 4.4.3 Vod rom bought at Uni too.

I downloaded Yotaflash and the adb official usb drivers (quite a pain to understand where to find original ones, but it seems I was lucky) and after connecting the phone in download mode, I flashed with 4.4.3 EU (downloaded through yotaflasher).

It brought me to 4.4.3 EU and started immediately to download several updates, now it is upgrading to lollipop.

Hope everything will go smoothly till 1.60 EU. Then I think I will wait for next EU to be released, do not want to risk with RU 1.99 as for now.

-----

Update: finished updating to lollipop 1.60 Eu, no bugs found as for now. Touch response of both screens seems to be equal to kitkat. The back screen seems to be a bit more responsive, but maybe it is my personal feeling.

Now phone correctly works with AC router (with kitkat only N bandwith was found, now it recognizes both 2.4 ghz and 5 ghz).

No gravity bug nor swipe problems. Seems I was lucky :)
[YotaPhone] Superbia:
Can this firmware be rooted? Was something in the custom recovery thread about it not working on 1.99 ?
[YotaPhone] lexman941:
really do not know anything about rooting cause I do not want to lose warranty, as for now 1.60 seems fine to me.

Update: after installing lollipop and playing a bit my phone started to drain battery much faster than kitkat . Do not really know what it is due to. Anyone has found this behavior with EU 1.60 rom?

As for now I removed LTE option, disabled g.now and some other features, but it is a bit frustrating.
[YotaPhone] lexman941:
has anyone understood how to fix the fast drain of the battery with the 1.60 eu release?

BTW: today some yota apps received update though the playstore :)
[YotaPhone] TKPL:
Try disabling YotaFit (the fitness app).

Let us know if this helps! :o
[YotaPhone] lexman941:
Already done thx. will let you know :D
[YotaPhone] polocanada:
Hoping for 5.1 for Yotaphone 2

Hope they release 5.1 for YP 2 before the YP 3 comes out. Having issue with "android.process.acore" has stopped and I have new device, installed maybe a 100 major apps and almost NO social apps and still have this issue. Difficult to fix, basically requires freezing the contacts storage app. Bug has been around since 2009 and according to reports in Lollipop 5.1 this bug was fixed!

So am wondering why Youta Devices releasing incremental updates for 5.0 when we have 5.1 which is much more stable and with improved performance. I am not even suggesting for 6.0 because that is not gonna happen. I am clear about that one. Update to 5.1 should be one to work on and not 5.0 versions.

---------- Post added at 07:40 AM ---------- Previous post was at 06:59 AM ----------

Apparently this site talks about rooted 1.99. Can you confirm?

http://www.hipda.cc/redirect.php?tid=1808193&goto=lastpost&sid=fH3J43

Translation into EN

http://is.gd/rq5eEn
[YotaPhone] TKPL:
Finally I made it! :fingers-crossed:

The only firmware I was able to flash was he 5.0 RU 1.59

, all others RU and EU gave me error.

So, from 5.0 EU 1.60, I manually flashed the RU 1.59, and then the phone got OTA 1.87 and 1.99.

Really nice improvements with 1.87! 1.99 is a little update.

No more errors with screen detection! :fingers-crossed:

I have cyrillic chars in phone dialer, but is not a big mess... :)

---------- Post added at 10:20 AM ---------- Previous post was at 10:18 AM ----------

I rooted normally as I made with 4.4.3 ;)

---------- Post added at 10:21 AM ---------- Previous post was at 10:20 AM ----------

Yes :)
[YotaPhone] polocanada:
I have 1.60 EU. I am just reading on all this stuff for the last 1 hour or so, I didn't have clue about what Nandroid is before.

So to flash to RU 1.99 here is what I think I need to do. Makes sense?

1. Root.

2. Titan Backup / Helium Backup for apps and settings and for things like Google Launcher settings.

3. TWRP or CWM for Nandroid backup (does it make sense?)

4 Flash to RU with YotaFlasher (which ever-version works and then update to 1.99)

5. Root again (if root is lost?)

6. Restore apps with TitanBackup (or shall I not mess around with that and just reinstall apps?)

7. Restore settings with Helium Backup such as Google Launcher (??? does it make sense?)

Could steps 6 and 7 potentially mess up the phone if I load configuration from the app or settings like Google Launcher from 1.60?

Thanks.
[YotaPhone] polocanada:
So with 1.99 RU do you still have problem with unlocking the EPD ink display? My understanding is the recent RU update has replaced "swipe" with "double-tap" to unlock. Does double-tap only work on the AMOLED display on 1.99 and the EPD needs to be unlocked by pressing the power button? Is this issue with every device or just related to devices that do the hackery of moving from 1.60 EU to 1.99 RU?
[YotaPhone] a43:
Hi there! Double-tap works on both screens fine, swipe gestures also works fine on both screens, three fingers to lock also works fine... The issue may be because you don't wiped your phone data after upgrading to RU firmware? I don't know for sure but I think this can help.

Yota will not update us to 5.1 or 6.0. They said that officially. Unfortunately :(

As for the battery I can say only that in my case 4.4.3 was the best. But there are a lot of nice improvements in 5.0 with EPD screen (a lot of bugs fixed) so I don't want to get back again.

Absolutely no problem to root. Just use kingroot 4.8.5 apk from here KingRoot After rooting you can replace kingroot with SuperSU using SuperSUMe 9.1.3 Super-Sume

By the way, russian betatesters got 5.0.0-RU1.1.109 OTA update already. If you want you can download it and apply on top of the .99 before rooting (since this is a patch OTA, you need unmodified system from 99 firmware and no root). It is nice. Nothing was fixed there but new nice animations for EPD added and some nice features like when you press notification on EPD screen it opens that application in mirror mode right there. No need to rotate to color screen anymore. And they added few Yota apps like YotaTravel and YotaTasks. Also nice ones...
[YotaPhone] polocanada:
Thank you for answering - Will there be update to EU or just RU?

Будет ли YotaDevices обновить версию ЕС до 1,99 или 1,109 ? В настоящее время он стоит на 1,60 .

Если обновление не планируется , ну я думаю, я должен мигать с версией RU .

---------- Post added at 05:31 AM ---------- Previous post was at 05:28 AM ----------

For fellow posters in this forum:

Here is official forum for YotaDevices. It's in Russian.

http://4pda.ru/forum/index.php?showtopic=550302&st=8180
[YotaPhone] a43:
I don't know. I'm not working in Yota Devices. In your place I'd rather flash RU firmware and use different dialer if you don't like russian letters in Stock one.
[YotaPhone] polocanada:
Great.

According to this post by YotaDevices there will be EU firmware update. Stay put...

YotaDevices

1) We actually offered to use some new types of unlock the screens (both screens) in one of the new version of software - "double tap", "swipe gesture", "power button only". All the unlock types is placed in the separate settings - "Lock & Unlock". The user can choose different types of unlock for the front screen and the back screen (e- ink display) according to personal preferences.

2) The new version of software for EU will be published in the nearest time. Please making sure that you keep their YotaPhones' firmware up-to-date.

http://4pda.ru/forum/index.php?showtopic=550302&st=8200

---------- Post added at 12:30 AM ---------- Previous post was at 12:18 AM ----------

Couple of interesting points - I copy past there in case somebody has issue reading Russian:

from YotaDevices:

We don't recommend to use bumpers that are made of metal materials. Radio signal may worsen because of the using metal bumpers. Besides metal bumpers could lock GPS signal.

According to the forum:

Some users report no problems with unlocking the screens both front and EPD, there are some users who experienced issues are reporting improvements.

There are however stark differences in battery life, some users reporting long battery drop a few percent during the day, other users saying battery doesn't last through the day. Apparently YMMW.

Interesting enough I noticed phone can get hot when battery consumption is high when it looks for signal. That was confirmed by another poster here...

http://4pda.ru/forum/index.php?showtopic=550302&st=8180

Keep in mind if you are outside of Europe, you most likely don't need LTE enabled because it won't work.
[YotaPhone] a43:
Who told you that? We have LTE even in some villages far far away from Europe in Far Eastern part of Russia near Japan and China... I've travelled to India two weeks ago and LTE was there also...
[YotaPhone] TKPL:
No problem with unlocking at all :)

There is no more swype, neither amoled neither EPD. You can:

- press power button

- double tap. In this case, amoled simply unlocks, while the EPD unlocks and opens the apps / activates the widget you double tapped on :fingers-crossed:
[YotaPhone] nexkat:
5.0.0-EU1.1.87a

Hi!

I got an email that there is a new EU firmware. There was no OTA option, so I downloaded from

ftp://fw.ydevices.com/YotaPhone2/Firmwares/EU/5.0.0-EU1.1.87a.zip

and installed with yotaphone_flasher.

rooting with custom recovery still works as usual.

stefan
[YotaPhone] a43:
We have got 5.0.0-RU1.1.112 update few days ago. Nice improvements there but mostly it fixes .109 bugs.
[YotaPhone] TKPL:
I got 1.112 (never seen the 1.109): new transitions in ink panel (nice but slower) and loop between last and first tab, some useless (IMHO) app like Yota Travel and there is always the bug on YotaEnergy: when turned on it turns OFF mobile data everytime, even with mobile date enabled in YotaEnergy setting.
[YotaPhone] Biker78:
Hi everyone....

I'm on 112 rom and I noticed that, when phone is turned off, the "always on display" shows the last screen or widget used, while whith previous rom you could only read "Yotaphone"...

So now if you look the back display it seems that phone is always turned on...

Anybody noticed that?
[YotaPhone] lexman941:
same here with EU rom 1.87a, it is normal, it is appositely done sto be always on
[YotaPhone] zute333:
I'm loving the new 112 ROM. Feels like if the phone had been running that when first sold their sales may have been helped a lot.

The EPD screen transition animations are gorgeous and really remove the sense of lag. The larger range of apps, settings options, customisations etc also make the phone feel more complete. Battery life has also definitely improved for me again. Still not quite back to KK levels, but best LL battery life so far for my Yota.

Seems happy times so far, hopefully this ROM stays functional for a good while.
[YotaPhone] tarlcab:
I wonder how much difference there is, or any improvement when you compare EU1.87a and RU1.112
[YotaPhone] Vuche:
EU1.87a = RU1.87 minus Russian apps/customisation. Definitely same date of build and no animations or new features like on RU1.112 . So with the latest EU version you're for sure two evolutions behind the latest RU version.

Up to you to choose: Cyrillic alphabet on dialer and some unusefull apps with an updated rom, or keep an older EU rom.

I'm personally very pleased with the first choice. It will maybe even help me learn Russian a little faster!
[YotaPhone] tarlcab:
Very cool. Here's hoping if there is any important changes/improvements the EU version will get an update as well. With the 1.87, I wanted the opportunity to double-tap to wake both screens (an introduction at the 1.87 level). If I did use the RU version, perhaps I could replace the dialer via the Play Store.
[YotaPhone] tarlcab:
No longer explained there. Original poster deleted any explanation.

But you do have the firmware and Yotaflasher:

ftp://fw.ydevices.com/YotaPhone2/

Some on other versions like HK, CN need to:

-Revert back to one of the S01 verisions of the Firmware (EU or RU), then OTA will finish the job. Use Yotaflasher. Only Yotaflasher and OTA work to upgrade.

This post should be all you need to get the job done. I want to help those like me that had a difficult time at first.
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
Unofficial release -TWRP recovery for the Galaxy A3 - SM-A310F/FD/Y/M Exynos7580

UPDATE 14/4/2016: TWRP 3.0.2-0 released. TWRP build updated to 3.0.2-1

https://twrp.me/site/update/2016/04/05/twrp-3.0.2-0-released.html

Seandroid warning fix.

New feature available in TWRP 3.0.0-x is system image backup and restore and factory image flashing (see TWRP changelog for details)

Basically this means factory images from the official firmware can now be flashed with TWRP instead of ODIN. I have extended this feature to include BOOT, RECOVERY, SYSTEM, CACHE, HIDDEN and RADIO(MODEM) partitions.

This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.

NOTE: To flash the modem, first it needs to be renamed to modem.bin.img

F2FS support added.

Internal SUPERSU root option removed. This is to prevent boot loops on 5.11/6.0 devices

You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.

Instructions:

Flash with ODIN 3.10.7 in the AP slot.

Uncheck Auto reboot.

Load the respective file below into the AP slot and hit start.

After flashing immediately reboot to recovery by holding POWER + HOME + VOL DOWN.

As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.

You should now see TWRP recovery.

twrp_3.0.2-1_sm-a310

PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST

To Root:

Flash the file below with TWRP:

DO NOT LET TWRP ROOT YOUR DEVICE IF IT ASKS. USE ONLY THE FILE BELOW:

http://download.chainfire.eu/969/SuperSU/

DEVICE TREE: soon

Guide

http://www.theandroidsoul.com/galaxy-a3-2016-twrp-recovery-89527/

NOTE: ON SOME ANDROID 5.1.1> DEVICES IT IS NECESSARY TO GO TO:

Settings -> Developer Options -> OEM unlocking

AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.

Credits: Me, Teamwin and my testers - nhthiencp

Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.

FEEDBACK IS APPRECIATED PLEASE.

THANKS.

DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU

.
[Galaxy A3, A5, A7, A8, A9 Android Development] yareodigiy:
xmodgames

yes rooted. but xmodgames not working on sm-a310f :(:(:(
[Galaxy A3, A5, A7, A8, A9 Android Development] chandarakk:
try use supersu 2.45 :D
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
No, don't it will brick your device. :o
[Galaxy A3, A5, A7, A8, A9 Android Development] yareodigiy:
thanks. do you have a suggestion for xmod work ? :confused: :) :confused:
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
Sorry I don't really play games, what's the issue?
[Galaxy A3, A5, A7, A8, A9 Android Development] alexax66:
Removed
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
Can you please not modify the work of others without getting permission first.

I would have got around to doing this myself, but it wasn't high on my priority list as its just a warning.

It will still trip knox regardless.
[Galaxy A3, A5, A7, A8, A9 Android Development] alexax66:
ОК!
[Galaxy A3, A5, A7, A8, A9 Android Development] hohosanta:
does anyone tried to install xposed frameworks? if you did, which one should i install?
[Galaxy A3, A5, A7, A8, A9 Android Development] Noryakky:
It's works perfectly, fast and stable so far :)

Thanks for your hard work and time :)

I'm using a310f from PLUS GSM in Poland, 16GB.

Custom recovery, root and xposed are working on this phone :)

Sorry for my English :p
[Galaxy A3, A5, A7, A8, A9 Android Development] fook42:
stuck in download-screen

i'm stuck in the flashing of twrp using your files.

after booting the device into the download-mode, selecting the twrp-tar-file into the AP-slot of odin and pressing "Start!", odin prints:

but the device is still in the download-mode and the small progress-bar stopped a few pixels before the end... :(

[see the picture]

[IMG="stuck@download-mode"]https://i.imgsafe.org/57cbd85.jpg[/IMG]
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
Nothing is stuck, you haven't followed the instructions in the OP.
[Galaxy A3, A5, A7, A8, A9 Android Development] fook42:
you're right ..

i thought there should be more "feedback" on the device that tells me, the flashing was successfully finished.

"after flashing" means, when ODIN states the process is done, it is done.
[Galaxy A3, A5, A7, A8, A9 Android Development] l_EMPEROR_l:
hi guys

thanks for your great rec

i have a problem , in voice calls the other side suddenly dont hear my voice but i do i after few second again the voice comes and go

its very annoying on voice calls for me , is this about radio? if yes where can i found mine? A310F Asia Iran

thanks all waiting for your help
[Galaxy A3, A5, A7, A8, A9 Android Development] ulfmais:
I get a "failed" thread, seems like Odin doesn't connect properly to my phone.

* plug in the phone with usb cable

* downloaded the Samsung USB driver (SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.25.0-retail.exe)

* opened odin

* unchecked auto-reboot

* loaded the twrp file to AP

=> fail

Attached photo:

Any ideas?
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
You need to put the device in download mode first. Also make sure OEM unlock is enabled and FRP lock is off.
[Galaxy A3, A5, A7, A8, A9 Android Development] ulfmais:
Cheers [MENTION=4899305]ashyx[/MENTION] :good:

Confirmed working like a charm for my new A3 2016 (bought in Norway)

Now I can uninstall all the crap bloatware :)

(f**k you Samsung for bundling all sorts of crap that I can't remove, even as the owner of the device)
[Galaxy A3, A5, A7, A8, A9 Android Development] cloooned:
Great work, thanks a lot!

Is the build configuration open source? Is it possible to build it by myself? Can you give me a link to the sources?

Thanks, regards
[Galaxy A3, A5, A7, A8, A9 Android Development] lucoski88:
Otg doesnt work...does exist a fix? Please
[Galaxy A3, A5, A7, A8, A9 Android Development] DerMoeJoe:
i'm having the same problem on my a310f (rooted with chainfire autoroot and then flashed your twrp.

ive got the problem now for over 1 month..... sometimes more and sometimes less.....

does someone has any idea how to fix this issue?
[Galaxy A3, A5, A7, A8, A9 Android Development] Khaon:
Thank you a lot for your work. It is nice to have a already working recovery.

I have spotted an issue. I cannt log throught adb shell. Here is the output :
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
It's because the kernel is preventing root access via adb shell.

I would need to rebuild the kernel to fix it
[Galaxy A3, A5, A7, A8, A9 Android Development] Khaon:
Oh. To remove the secure boot/root detection I would need to disable KNOX ?
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
No it's nothing to do with knox.

It's selinux denying permission.

A recompiled kernel with root protection removed is required.
[Galaxy A3, A5, A7, A8, A9 Android Development] Khaon:
Okaaaay, but I have no idea how to do so.

All I know is how to set up selinux to permissive with the default boot cmd line.
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
Setting permissive on the command line doesn't work with 5.1.1 and 6.0.

SElinux is hardcoded in the kernel.

You don't need to worry about it I will fix it.
[Galaxy A3, A5, A7, A8, A9 Android Development] Khaon:
Nice, but could you share a patch or explain how to do so ? SO I can learn smthing? :P
[Galaxy A3, A5, A7, A8, A9 Android Development] Khaon:
Hello,

I tried to format /data with f2fs formater.

It failed. Dunno if you can take a look at this. Since our kernel supports f2fs by default, it could be nice trying !
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
What's f2fs formatter?

Just use twrp to format to f2fs.

Also the kernel doesn't support f2fs by default. It needs to be enabled.
[Galaxy A3, A5, A7, A8, A9 Android Development] NiklasDahl:
Hi there i'm having same problem as Ashyx in post #18.

But i cant turn my phone on to enabled OEM unlock. and how do i make the FRP lock to off.

when i turn my phone on it just shows the battery logo and the text "custom binary blocked by FRP lock"

Is there any way around this. ?
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
Flash the stock firmware.
[Galaxy A3, A5, A7, A8, A9 Android Development] NiklasDahl:
Thanks i have found a stock firmware but it takes 3 hours because its a slow dl link.. do any of you have a fast link ?
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
Paste the build number into Google and see which links come up.

There is usually a few.

http://www.theandroidsoul.com/download-a3-2016-stock-firmware-88226/
[Galaxy A3, A5, A7, A8, A9 Android Development] Khaon:
Sup.

I tried to issue

/sbin/mkfs.f2fs /dev/block/mmcblk0p23

from some recovery flashable package. it failed.

So does formating data partition with f2fs from the builtin recovery feature.

When i was talking about formater it is the binary like mkfs.f2fs.
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
Try again using inbuilt twrp feature and post the recovery log.
[Galaxy A3, A5, A7, A8, A9 Android Development] Khaon:
I'll provide this by tomorrow.
[Galaxy A3, A5, A7, A8, A9 Android Development] Khaon:
Hello,

I encoutered some issues while trying to get what you want :P.

I tried, like you asked me, to format again with inbuilt twrp feature. So here is the recovery.log file

From TWRP I had the following output after formating with f2fs the /userdata partition:

"formating done"
"unable to mount /data"

Is the twrp kernel compatible with f2fs ?

According to the recovery.log file, it says my /data partition is well f2fs. However when I reboot I end up with an ext4 partition.

The current kernel my phone runs has f2fs enabled(see here, also

I added this line to the fstab (before the ext4's one)

/dev/block/platform/13540000.dwmmc0/by-name/USERDATA /data f2fs rw,noatime,nosuid,nodev,discard,nodiratime,inline_xattr,inline_data,active_logs=4 wait,check,encryptable=footer

W/e I try to do I end up with an ext4 partition.

Maybe is it related to the init binary(MM's is now formating to the first fstab occurrence line)

Or I am missing smthing :D.

Ty
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
F2FS support is enabled in the kernel but Samsungs code doesn't always work.

I will check the config and see if I've added support to the ramdisk.
[Galaxy A3, A5, A7, A8, A9 Android Development] Khaon:
It is long time ago for me :p and i can't remember,

is something like this required ?

my twrp.fstab for manta
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
Here we go, fixed the fstab, should now be able to mount data and cache as F2FS as long as Samsung hasn't borked the kernel source.

Also supports EXT4.

https://www.androidfilehost.com/?fid=24591020540822226

To boot F2FS support will need to be added to the kernel and ramdisk boot.img. If you need it let me know.
[Galaxy A3, A5, A7, A8, A9 Android Development] Khaon:
Great ! thank you, I am gonna try this and report.

I have enabled f2fs from the default defconfig, also this is the line I added into the fstab :

/dev/block/platform/13540000.dwmmc0/by-name/USERDATA /data f2fs rw,noatime,nosuid,nodev,discard,nodiratime,inline_xattr,inline_data,active_logs=4 wait,check,encryptable=footer

I don't think I am missing something, am I ?
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
That should do it. This is the boot image I presume?
[Galaxy A3, A5, A7, A8, A9 Android Development] Khaon:
yep it is from the boot image's ramdisk's fstab.
[Galaxy A3, A5, A7, A8, A9 Android Development] GoldSolitude:
You ashyx are a legend, you're the best. Thanks for this :D
[Galaxy A3, A5, A7, A8, A9 Android Development] Khaon:
Hello,

I have tried to format to f2fs with the latest build you provide me.

I coud not format. I remembered about TWRP screenshots. So here the log and some screen....

log

screenshot