YOTA 3+ FIRMWARE news

Search This thread

paolinger

Senior Member
Oct 31, 2008
106
60
UPGRADE YOTA3 TO YOTA3+

It seems that yota3+ firmware is really a great step forward:

*ttps://youtu.be/C_aAnEm8_u8

Here the FILES you need:
http://www.mediafire.com/folder/yt2dgy6a8j82w/YOTA_3+_files
*ttp://www.mediafire.com/folder/yt2dgy6a8j82w/YOTA_3%2B_files



Here the TUTORIAL yota3 to yota 3+
128gb and 64gb
This will erase everything so doesn't matter if is rooted, r05, twrp recovery, unlocked or locked.. This will flash with oem firehose programmer and you will have a brand new yota3+ ,has everybody expected, finally a good double screen smartphone after yota2.

Thanks to:
Yunyao shopkeeper
and team.

String dooradd friendgreetSend a message
Direct elevator
Jump to the specified floor Landlord
Posted yesterday 19:18 | Show author | reverse view
Thanks again to the global yota machine friends for their efforts! !
This success is a success of cooperation. It is
not just domestic cooperation,
but also international cooperation. Because of our common interests, we get together
because of our common hobbies, so
hard to
work together, break through together,
have hard work,
have joy
and sweat,
and have tears at
first. It is only hope that there is no opportunity,
and it is hopeful to wear, and
finally made a breakthrough,
this is a big step for our majority of 3 users, and
also a big event and a happy event for dual-screen e-book users!

Thanks to those comrades
who have failed to become bricks in their attempts, and to those who have made us successful!
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++
++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++


Notes: 1. If you are not a local tyrant, please don't let your curiosity expand;
2. Brush your machine to risk bricks. In the second, so the brush machine is not after-sale;
3, the current brush machine has no retreat, that is, after brushing into yota3+ there is no way to brush back yota3;
4, brush machine process to confirm the stability of usb, brushing process interrupted meeting bricks ;
5. brush once again that the process needs to follow the tutorial to go! ! ! !


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

How to install Yota3+ rom on Yota3
(translate by skirep)

We can update our Yota3 phones to the "new" rom of Yota3+ from Yota Technologies. We need it:

1. We need the Yota 3.
2. (Backup QCN file) *rooted* here
3.
4.
5.
6. Install the QPST2.7.474 --> QPST Qualcomm tool and 9008 driver.
7. Put the Yota 3 on 9008 mode ( edl mode ) --> 'adb reboot edl' or press "Vol +" + "Vol -" + "Power" buttons.
8. Uncompress the rom new9008-0112.zip:
Qualcomm-HS-USB-QDLoader-9008-min.png



8. Execute the QFil.exe app from Desktop.
9. Configure the app like the image
https%3A%2F%2Fi.ibb.co%2FzNZbz0y%2Ffirst.png



10. Select Flat build in Select Build type.
11. Select the mbn file from the rom into a the Programmer Path.
12. Click on Load XML... and select the two xml files:
https%3A%2F%2Fi.ibb.co%2FyRGmfj2%2Fsecond.png





13. And finally click on Download like the image:
https%3A%2F%2Fi.ibb.co%2F7VfxM3Z%2Fthird.png


14. It will do somethings... but nothing will happen. Then, you need to click on Load XML, and only select the Rawprogram0.xml and the patch0.xml.
15. Click another time the Download button.

Is important to enter edl mode pushing the 3 buttons till you ear the windows sound of device connection and soon click download.
16. After that... the Phone will reboot. and will appear a screen with "Decryption unsuccessful", and you will need to Reset the Phone. Later you need to follow the steps appearing in the screen.
224006qnuj5nptdmpd6hnp.jpg


Now you have the Yota 3+ phone with stock rom and, actually, will receive the OTA updates, but the 2 updates have some bugs so is better, for the moment, leave the basic firmware.

Be sure to hit the thanks button when someone helps you.
 
Last edited:

depple

Member
Nov 9, 2018
6
4
Hello, guys, I have Yota 3+. I can try to copy the ROM from it, but I'm afraid to make a brick from my smartphone. I'm afraid of any risc, because there's no way to unbrick 3+ nowdays. If someone needs the ROM and knows any safe way to copy ROM, please contact me.

hope that there will be technical experts to help dump rom as soon as possible.
 

a396889843

Member
Nov 21, 2010
21
7
Hello, guys, I have Yota 3+. I can try to copy the ROM from it, but I'm afraid to make a brick from my smartphone. I'm afraid of any risc, because there's no way to unbrick 3+ nowdays. If someone needs the ROM and knows any safe way to copy ROM, please contact me.
I'm trying to extract the ROM of your phone while keeping the device safe

---------- Post added at 05:48 PM ---------- Previous post was at 05:37 PM ----------

Hello, guys, I have Yota 3+. I can try to copy the ROM from it, but I'm afraid to make a brick from my smartphone. I'm afraid of any risc, because there's no way to unbrick 3+ nowdays. If someone needs the ROM and knows any safe way to copy ROM, please contact me.

Because of the network limitation, could you please contact me through qq? My qq number is 396889843, or add my teamview ID:1111578722. I will operate your computer remotely through teamview
 
  • Like
Reactions: Sodasistso

joygram

Senior Member
Oct 26, 2015
54
82
if you want dump rom

first unlock boot loader yotaphone.
yota's boot loader unlock is simple. but all data lost.

and enter twrp recovery mode.

you can dump with adb shell dd command.

yota's partition like this.
/dev/block/bootdevice/by-name/
HTML:
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 aboot -> /dev/block/mmcblk0p20
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 abootbak -> /dev/block/mmcblk0p21
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 apdp -> /dev/block/mmcblk0p47
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 boot -> /dev/block/mmcblk0p22
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 cache -> /dev/block/mmcblk0p26
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 cdt -> /dev/block/mmcblk0p15
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 cmnlib -> /dev/block/mmcblk0p41
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 cmnlib64 -> /dev/block/mmcblk0p43
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 cmnlib64bak -> /dev/block/mmcblk0p44
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 cmnlibbak -> /dev/block/mmcblk0p42
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 config -> /dev/block/mmcblk0p30
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 custom -> /dev/block/mmcblk0p52
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 ddr -> /dev/block/mmcblk0p16
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 devcfg -> /dev/block/mmcblk0p10
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 devcfgbak -> /dev/block/mmcblk0p11
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 devinfo -> /dev/block/mmcblk0p25
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 dip -> /dev/block/mmcblk0p35
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 dpo -> /dev/block/mmcblk0p49
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 dsp -> /dev/block/mmcblk0p12
lrwxrwxrwx    1 root     root            20 Mar 14 08:15 fsc -> /dev/block/mmcblk0p2
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 fsg -> /dev/block/mmcblk0p17
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 junklog -> /dev/block/mmcblk0p51
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 keymaster -> /dev/block/mmcblk0p45
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 keymasterbak -> /dev/block/mmcblk0p46
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 keystore -> /dev/block/mmcblk0p29
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 letvconfig -> /dev/block/mmcblk0p50
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 limits -> /dev/block/mmcblk0p33
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 lksecapp -> /dev/block/mmcblk0p39
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 lksecappbak -> /dev/block/mmcblk0p40
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 logdump -> /dev/block/mmcblk0p53
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 mcfg -> /dev/block/mmcblk0p38
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 mdtp -> /dev/block/mmcblk0p36
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 misc -> /dev/block/mmcblk0p28
lrwxrwxrwx    1 root     root            20 Mar 14 08:15 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 mota -> /dev/block/mmcblk0p34
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 msadp -> /dev/block/mmcblk0p48
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 oem -> /dev/block/mmcblk0p31
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 params -> /dev/block/mmcblk0p32
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 persist -> /dev/block/mmcblk0p27
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 recovery -> /dev/block/mmcblk0p23
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 recoverybp -> /dev/block/mmcblk0p24
lrwxrwxrwx    1 root     root            20 Mar 14 08:15 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx    1 root     root            20 Mar 14 08:15 rpmbak -> /dev/block/mmcblk0p7
lrwxrwxrwx    1 root     root            20 Mar 14 08:15 sbl1 -> /dev/block/mmcblk0p4
lrwxrwxrwx    1 root     root            20 Mar 14 08:15 sbl1bak -> /dev/block/mmcblk0p5
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 sec -> /dev/block/mmcblk0p18
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 splash -> /dev/block/mmcblk0p19
lrwxrwxrwx    1 root     root            20 Mar 14 08:15 ssd -> /dev/block/mmcblk0p3
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 syscfg -> /dev/block/mmcblk0p37
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 system -> /dev/block/mmcblk0p54
lrwxrwxrwx    1 root     root            20 Mar 14 08:15 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx    1 root     root            20 Mar 14 08:15 tzbak -> /dev/block/mmcblk0p9
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 userdata -> /dev/block/mmcblk0p55

you can dump with `dd` command in `adb shell`
adb shell
dd if=/dev/block/bootdevice/by-name/system of=/sdcard/system.img
dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
exit

and copy with `adb pull` in command line
adb pull /sdcard/system.img
adb pull /sdcard/boot.img
 

depple

Member
Nov 9, 2018
6
4
Dear paolinger:
something that i have to explain to you . in the above reply paste, first, i am the freeca.W who replied to your Youtube video, coming from China; a396889843, who come from China too; joygram, who come from Korea and he modifies yota3 rom and post in Xda forum, they are all having good skill and familiar with dumping rom. you can trust them .at last ,Thank you very much.
let's have a pleasant cooperation and wish us success !
 
  • Like
Reactions: Sodasistso

gor516don

Member
Sep 14, 2016
40
11
44
NanHai
I use software to capture the update package of the system. Some Netizens found boot. img in the package and made a new local update package with magisk patch's boot. img. The ROOT is implemented.
 
  • Like
Reactions: Sodasistso

Sodasistso

Member
Oct 17, 2018
9
3
I love the Yota 3, especially for the e-ink screen. The phone is so cool, but the original software is crappy. The custom rom R05 is not bad, but the backscreen isn´t useful integrated yet. The Yota3+ Firmware would be so nice to have. I hope, you guys can do that soon. Good luck
 

depple

Member
Nov 9, 2018
6
4
first unlock boot loader yotaphone.
yota's boot loader unlock is simple. but all data lost.

and enter twrp recovery mode.

you can dump with adb shell dd command.

yota's partition like this.
/dev/block/bootdevice/by-name/
HTML:
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 aboot -> /dev/block/mmcblk0p20
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 abootbak -> /dev/block/mmcblk0p21
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 apdp -> /dev/block/mmcblk0p47
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 boot -> /dev/block/mmcblk0p22
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 cache -> /dev/block/mmcblk0p26
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 cdt -> /dev/block/mmcblk0p15
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 cmnlib -> /dev/block/mmcblk0p41
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 cmnlib64 -> /dev/block/mmcblk0p43
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 cmnlib64bak -> /dev/block/mmcblk0p44
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 cmnlibbak -> /dev/block/mmcblk0p42
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 config -> /dev/block/mmcblk0p30
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 custom -> /dev/block/mmcblk0p52
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 ddr -> /dev/block/mmcblk0p16
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 devcfg -> /dev/block/mmcblk0p10
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 devcfgbak -> /dev/block/mmcblk0p11
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 devinfo -> /dev/block/mmcblk0p25
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 dip -> /dev/block/mmcblk0p35
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 dpo -> /dev/block/mmcblk0p49
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 dsp -> /dev/block/mmcblk0p12
lrwxrwxrwx    1 root     root            20 Mar 14 08:15 fsc -> /dev/block/mmcblk0p2
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 fsg -> /dev/block/mmcblk0p17
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 junklog -> /dev/block/mmcblk0p51
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 keymaster -> /dev/block/mmcblk0p45
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 keymasterbak -> /dev/block/mmcblk0p46
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 keystore -> /dev/block/mmcblk0p29
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 letvconfig -> /dev/block/mmcblk0p50
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 limits -> /dev/block/mmcblk0p33
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 lksecapp -> /dev/block/mmcblk0p39
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 lksecappbak -> /dev/block/mmcblk0p40
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 logdump -> /dev/block/mmcblk0p53
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 mcfg -> /dev/block/mmcblk0p38
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 mdtp -> /dev/block/mmcblk0p36
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 misc -> /dev/block/mmcblk0p28
lrwxrwxrwx    1 root     root            20 Mar 14 08:15 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 mota -> /dev/block/mmcblk0p34
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 msadp -> /dev/block/mmcblk0p48
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 oem -> /dev/block/mmcblk0p31
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 params -> /dev/block/mmcblk0p32
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 persist -> /dev/block/mmcblk0p27
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 recovery -> /dev/block/mmcblk0p23
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 recoverybp -> /dev/block/mmcblk0p24
lrwxrwxrwx    1 root     root            20 Mar 14 08:15 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx    1 root     root            20 Mar 14 08:15 rpmbak -> /dev/block/mmcblk0p7
lrwxrwxrwx    1 root     root            20 Mar 14 08:15 sbl1 -> /dev/block/mmcblk0p4
lrwxrwxrwx    1 root     root            20 Mar 14 08:15 sbl1bak -> /dev/block/mmcblk0p5
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 sec -> /dev/block/mmcblk0p18
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 splash -> /dev/block/mmcblk0p19
lrwxrwxrwx    1 root     root            20 Mar 14 08:15 ssd -> /dev/block/mmcblk0p3
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 syscfg -> /dev/block/mmcblk0p37
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 system -> /dev/block/mmcblk0p54
lrwxrwxrwx    1 root     root            20 Mar 14 08:15 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx    1 root     root            20 Mar 14 08:15 tzbak -> /dev/block/mmcblk0p9
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 userdata -> /dev/block/mmcblk0p55

you can dump with `dd` command in `adb shell`
adb shell
dd if=/dev/block/bootdevice/by-name/system of=/sdcard/system.img
dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
exit

and copy with `adb pull` in command line
adb pull /sdcard/system.img
adb pull /sdcard/boot.img


we have invited Rissian friend paolinger( George white)to discuss dumping 3+'s rom via WeChat(a chinese communication tools), would you like to join? if you agree,Please register in Wechat and tellus your ID, then we'll invite you to join. we need your guidance. and looking forward to your joining, welcome!
 
  • Like
Reactions: Kibiru

depple

Member
Nov 9, 2018
6
4
welcome to discuss dumping 3+ rom on Wechat

first unlock boot loader yotaphone.
yota's boot loader unlock is simple. but all data lost.

and enter twrp recovery mode.

you can dump with adb shell dd command.

yota's partition like this.
/dev/block/bootdevice/by-name/
HTML:
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 aboot -> /dev/block/mmcblk0p20
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 abootbak -> /dev/block/mmcblk0p21
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 apdp -> /dev/block/mmcblk0p47
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 boot -> /dev/block/mmcblk0p22
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 cache -> /dev/block/mmcblk0p26
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 cdt -> /dev/block/mmcblk0p15
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 cmnlib -> /dev/block/mmcblk0p41
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 cmnlib64 -> /dev/block/mmcblk0p43
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 cmnlib64bak -> /dev/block/mmcblk0p44
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 cmnlibbak -> /dev/block/mmcblk0p42
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 config -> /dev/block/mmcblk0p30
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 custom -> /dev/block/mmcblk0p52
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 ddr -> /dev/block/mmcblk0p16
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 devcfg -> /dev/block/mmcblk0p10
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 devcfgbak -> /dev/block/mmcblk0p11
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 devinfo -> /dev/block/mmcblk0p25
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 dip -> /dev/block/mmcblk0p35
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 dpo -> /dev/block/mmcblk0p49
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 dsp -> /dev/block/mmcblk0p12
lrwxrwxrwx    1 root     root            20 Mar 14 08:15 fsc -> /dev/block/mmcblk0p2
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 fsg -> /dev/block/mmcblk0p17
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 junklog -> /dev/block/mmcblk0p51
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 keymaster -> /dev/block/mmcblk0p45
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 keymasterbak -> /dev/block/mmcblk0p46
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 keystore -> /dev/block/mmcblk0p29
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 letvconfig -> /dev/block/mmcblk0p50
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 limits -> /dev/block/mmcblk0p33
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 lksecapp -> /dev/block/mmcblk0p39
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 lksecappbak -> /dev/block/mmcblk0p40
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 logdump -> /dev/block/mmcblk0p53
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 mcfg -> /dev/block/mmcblk0p38
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 mdtp -> /dev/block/mmcblk0p36
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 misc -> /dev/block/mmcblk0p28
lrwxrwxrwx    1 root     root            20 Mar 14 08:15 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 mota -> /dev/block/mmcblk0p34
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 msadp -> /dev/block/mmcblk0p48
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 oem -> /dev/block/mmcblk0p31
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 params -> /dev/block/mmcblk0p32
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 persist -> /dev/block/mmcblk0p27
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 recovery -> /dev/block/mmcblk0p23
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 recoverybp -> /dev/block/mmcblk0p24
lrwxrwxrwx    1 root     root            20 Mar 14 08:15 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx    1 root     root            20 Mar 14 08:15 rpmbak -> /dev/block/mmcblk0p7
lrwxrwxrwx    1 root     root            20 Mar 14 08:15 sbl1 -> /dev/block/mmcblk0p4
lrwxrwxrwx    1 root     root            20 Mar 14 08:15 sbl1bak -> /dev/block/mmcblk0p5
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 sec -> /dev/block/mmcblk0p18
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 splash -> /dev/block/mmcblk0p19
lrwxrwxrwx    1 root     root            20 Mar 14 08:15 ssd -> /dev/block/mmcblk0p3
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 syscfg -> /dev/block/mmcblk0p37
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 system -> /dev/block/mmcblk0p54
lrwxrwxrwx    1 root     root            20 Mar 14 08:15 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx    1 root     root            20 Mar 14 08:15 tzbak -> /dev/block/mmcblk0p9
lrwxrwxrwx    1 root     root            21 Mar 14 08:15 userdata -> /dev/block/mmcblk0p55

you can dump with `dd` command in `adb shell`
adb shell
dd if=/dev/block/bootdevice/by-name/system of=/sdcard/system.img
dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
exit

and copy with `adb pull` in command line
adb pull /sdcard/system.img
adb pull /sdcard/boot.img

we have invited Rissian friend paolinger( George white)to discuss dumping 3+'s rom via WeChat(a chinese communication tools), would you like to join? if you agree,Please register in Wechat and tell us your ID, then we'll invite you to join. we need your guidance. and looking forward to your joining, welcome you!
 
  • Like
Reactions: Kibiru and Jedso

megasounds

Senior Member
May 7, 2007
317
119
Hi joygram:
Quote: Originally Posted by joygram
first unlock boot loader yotaphone.
yota's boot loader unlock is simple. but all data lost.
Can you please tell me HOW ??
Can you show us with some nice screenshots ?

and enter twrp recovery mode.
Can we do ( just like the yotaphone 2 ) LOAD the TWRP
On the yotaphone 2 it was : fastboot boot twrp-v5.img
can you please post the latest working TWRP for the yotaphone 3+ here ??

When i recieve my yotaphone 3+ i will dump all the rom(s)
Many thanks inadvance

Michael
 
  • Like
Reactions: Kibiru

gor516don

Member
Sep 14, 2016
40
11
44
NanHai
Hi joygram:

Can you please tell me HOW ??
Can you show us with some nice screenshots ?


Can we do ( just like the yotaphone 2 ) LOAD the TWRP
On the yotaphone 2 it was : fastboot boot twrp-v5.img
can you please post the latest working TWRP for the yotaphone 3+ here ??

When i recieve my yotaphone 3+ i will dump all the rom(s)
Many thanks inadvance

Michael
Y3 Unlock code:
fastboot flashing unlock
OR
fastboot flashing oem

Y3 TWRP
fastboot recovery TWRP.img
AND
fastboot recoverybp TWRP.img
 
  • Like
Reactions: Kibiru

whynot4444

Senior Member
May 27, 2012
251
30
Hello, guys, I have Yota 3+. I can try to copy the ROM from it, but I'm afraid to make a brick from my smartphone. I'm afraid of any risc, because there's no way to unbrick 3+ nowdays. If someone needs the ROM and knows any safe way to copy ROM, please contact me.

first, you need to turn on OEM lock on developer, then go to fastboot : type fastboot oem unlock to unlock it
and try flash twrp of yota 3, because i think it same boot
 
  • Like
Reactions: skirep

Kibiru

New member
Nov 18, 2018
4
2
Bucharest
Here's some unfortunate news.

Customer Rep. yotaeshop.com

My question:

Since both devices are essentially the same and differ only in terms of firmware I don't see why it won't be possible for you guys to register our SN's as Yota 3+ and push the updated version as OTA.? Please let me know. Thank you in advance.

Reply:

Thanks for your interest in our YOTA3+. Since new set of device ID would be associated with yeti4 and our new y3+ software platform, and thus it is not feasible to do pure software upgrade although they have the same hardware. Only new device ID are granted or associated with our new software.
2018-11-22 23:11PM
 

Top Liked Posts

  • There are no posts matching your filters.
  • 14
    UPGRADE YOTA3 TO YOTA3+

    It seems that yota3+ firmware is really a great step forward:

    *ttps://youtu.be/C_aAnEm8_u8

    Here the FILES you need:
    http://www.mediafire.com/folder/yt2dgy6a8j82w/YOTA_3+_files
    *ttp://www.mediafire.com/folder/yt2dgy6a8j82w/YOTA_3%2B_files



    Here the TUTORIAL yota3 to yota 3+
    128gb and 64gb
    This will erase everything so doesn't matter if is rooted, r05, twrp recovery, unlocked or locked.. This will flash with oem firehose programmer and you will have a brand new yota3+ ,has everybody expected, finally a good double screen smartphone after yota2.

    Thanks to:
    Yunyao shopkeeper
    and team.

    String dooradd friendgreetSend a message
    Direct elevator
    Jump to the specified floor Landlord
    Posted yesterday 19:18 | Show author | reverse view
    Thanks again to the global yota machine friends for their efforts! !
    This success is a success of cooperation. It is
    not just domestic cooperation,
    but also international cooperation. Because of our common interests, we get together
    because of our common hobbies, so
    hard to
    work together, break through together,
    have hard work,
    have joy
    and sweat,
    and have tears at
    first. It is only hope that there is no opportunity,
    and it is hopeful to wear, and
    finally made a breakthrough,
    this is a big step for our majority of 3 users, and
    also a big event and a happy event for dual-screen e-book users!

    Thanks to those comrades
    who have failed to become bricks in their attempts, and to those who have made us successful!
    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++
    ++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++


    Notes: 1. If you are not a local tyrant, please don't let your curiosity expand;
    2. Brush your machine to risk bricks. In the second, so the brush machine is not after-sale;
    3, the current brush machine has no retreat, that is, after brushing into yota3+ there is no way to brush back yota3;
    4, brush machine process to confirm the stability of usb, brushing process interrupted meeting bricks ;
    5. brush once again that the process needs to follow the tutorial to go! ! ! !


    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

    How to install Yota3+ rom on Yota3
    (translate by skirep)

    We can update our Yota3 phones to the "new" rom of Yota3+ from Yota Technologies. We need it:

    1. We need the Yota 3.
    2. (Backup QCN file) *rooted* here
    3.
    4.
    5.
    6. Install the QPST2.7.474 --> QPST Qualcomm tool and 9008 driver.
    7. Put the Yota 3 on 9008 mode ( edl mode ) --> 'adb reboot edl' or press "Vol +" + "Vol -" + "Power" buttons.
    8. Uncompress the rom new9008-0112.zip:
    Qualcomm-HS-USB-QDLoader-9008-min.png



    8. Execute the QFil.exe app from Desktop.
    9. Configure the app like the image
    https%3A%2F%2Fi.ibb.co%2FzNZbz0y%2Ffirst.png



    10. Select Flat build in Select Build type.
    11. Select the mbn file from the rom into a the Programmer Path.
    12. Click on Load XML... and select the two xml files:
    https%3A%2F%2Fi.ibb.co%2FyRGmfj2%2Fsecond.png





    13. And finally click on Download like the image:
    https%3A%2F%2Fi.ibb.co%2F7VfxM3Z%2Fthird.png


    14. It will do somethings... but nothing will happen. Then, you need to click on Load XML, and only select the Rawprogram0.xml and the patch0.xml.
    15. Click another time the Download button.

    Is important to enter edl mode pushing the 3 buttons till you ear the windows sound of device connection and soon click download.
    16. After that... the Phone will reboot. and will appear a screen with "Decryption unsuccessful", and you will need to Reset the Phone. Later you need to follow the steps appearing in the screen.
    224006qnuj5nptdmpd6hnp.jpg


    Now you have the Yota 3+ phone with stock rom and, actually, will receive the OTA updates, but the 2 updates have some bugs so is better, for the moment, leave the basic firmware.

    Be sure to hit the thanks button when someone helps you.
    10
    How to install Yota3+ rom on Yota3

    We can update our Yota3 phones to the "new" rom of Yota3+ from Yota Technologies. We need it:

    1. We need the Yota 3.
    2. Activate the Developer tools.
    3. Enable USB debugging mode on Developer Tools.
    4. Enable the Unlock OEM Bootloader.
    5. Go to Fastmode and unlock the OEM bootlader. ( fastboot oem unlock ).
    6. Install the QPST2.7.474 --> QPST Qualcomm tool and 9008 driver.
    7. Put the Yota 3 on 9008 mode ( edl mode ) --> 'adb reboot edl' or press "Vol +" + "Vol -" + "Power" buttons.
    8. Uncompress the rom new9008-0112.zip:
    8. Execute the QFil.exe app from Desktop.
    9. Configure the app like the image:
    10. Select Flat build in Select Build type.
    11. Select the mbn file from the rom into a the Programmer Path.
    12. Click on Load XML... and select the two xml files:

    13. And finally click on Download like the image:

    14. It will do somethings... but nothing will happen. Then, you need to click on Load XML, and only select the Rawprogram0.xml and the patch0.xml.
    15. Click another time the Download button.
    16. After that... the Phone will reboot. and will appear a screen with "Drecyption unsuccessful", and you will need to Reset the Phone. Later you need to follow the steps appearing in the screen.

    When you have installed the Yota3+ rom, you can update the androiod normally. Now will appear 2 updates from the system.

    Now you have the Yota 3+ phone.
    7
    Hello, guys, I have Yota 3+. I can try to copy the ROM from it, but I'm afraid to make a brick from my smartphone. I'm afraid of any risc, because there's no way to unbrick 3+ nowdays. If someone needs the ROM and knows any safe way to copy ROM, please contact me.
    4
    if you want dump rom

    first unlock boot loader yotaphone.
    yota's boot loader unlock is simple. but all data lost.

    and enter twrp recovery mode.

    you can dump with adb shell dd command.

    yota's partition like this.
    /dev/block/bootdevice/by-name/
    HTML:
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 aboot -> /dev/block/mmcblk0p20
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 abootbak -> /dev/block/mmcblk0p21
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 apdp -> /dev/block/mmcblk0p47
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 boot -> /dev/block/mmcblk0p22
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 cache -> /dev/block/mmcblk0p26
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 cdt -> /dev/block/mmcblk0p15
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 cmnlib -> /dev/block/mmcblk0p41
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 cmnlib64 -> /dev/block/mmcblk0p43
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 cmnlib64bak -> /dev/block/mmcblk0p44
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 cmnlibbak -> /dev/block/mmcblk0p42
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 config -> /dev/block/mmcblk0p30
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 custom -> /dev/block/mmcblk0p52
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 ddr -> /dev/block/mmcblk0p16
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 devcfg -> /dev/block/mmcblk0p10
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 devcfgbak -> /dev/block/mmcblk0p11
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 devinfo -> /dev/block/mmcblk0p25
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 dip -> /dev/block/mmcblk0p35
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 dpo -> /dev/block/mmcblk0p49
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 dsp -> /dev/block/mmcblk0p12
    lrwxrwxrwx    1 root     root            20 Mar 14 08:15 fsc -> /dev/block/mmcblk0p2
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 fsg -> /dev/block/mmcblk0p17
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 junklog -> /dev/block/mmcblk0p51
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 keymaster -> /dev/block/mmcblk0p45
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 keymasterbak -> /dev/block/mmcblk0p46
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 keystore -> /dev/block/mmcblk0p29
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 letvconfig -> /dev/block/mmcblk0p50
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 limits -> /dev/block/mmcblk0p33
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 lksecapp -> /dev/block/mmcblk0p39
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 lksecappbak -> /dev/block/mmcblk0p40
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 logdump -> /dev/block/mmcblk0p53
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 mcfg -> /dev/block/mmcblk0p38
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 mdtp -> /dev/block/mmcblk0p36
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 misc -> /dev/block/mmcblk0p28
    lrwxrwxrwx    1 root     root            20 Mar 14 08:15 modem -> /dev/block/mmcblk0p1
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 modemst1 -> /dev/block/mmcblk0p13
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 modemst2 -> /dev/block/mmcblk0p14
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 mota -> /dev/block/mmcblk0p34
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 msadp -> /dev/block/mmcblk0p48
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 oem -> /dev/block/mmcblk0p31
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 params -> /dev/block/mmcblk0p32
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 persist -> /dev/block/mmcblk0p27
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 recovery -> /dev/block/mmcblk0p23
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 recoverybp -> /dev/block/mmcblk0p24
    lrwxrwxrwx    1 root     root            20 Mar 14 08:15 rpm -> /dev/block/mmcblk0p6
    lrwxrwxrwx    1 root     root            20 Mar 14 08:15 rpmbak -> /dev/block/mmcblk0p7
    lrwxrwxrwx    1 root     root            20 Mar 14 08:15 sbl1 -> /dev/block/mmcblk0p4
    lrwxrwxrwx    1 root     root            20 Mar 14 08:15 sbl1bak -> /dev/block/mmcblk0p5
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 sec -> /dev/block/mmcblk0p18
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 splash -> /dev/block/mmcblk0p19
    lrwxrwxrwx    1 root     root            20 Mar 14 08:15 ssd -> /dev/block/mmcblk0p3
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 syscfg -> /dev/block/mmcblk0p37
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 system -> /dev/block/mmcblk0p54
    lrwxrwxrwx    1 root     root            20 Mar 14 08:15 tz -> /dev/block/mmcblk0p8
    lrwxrwxrwx    1 root     root            20 Mar 14 08:15 tzbak -> /dev/block/mmcblk0p9
    lrwxrwxrwx    1 root     root            21 Mar 14 08:15 userdata -> /dev/block/mmcblk0p55

    you can dump with `dd` command in `adb shell`
    adb shell
    dd if=/dev/block/bootdevice/by-name/system of=/sdcard/system.img
    dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
    exit

    and copy with `adb pull` in command line
    adb pull /sdcard/system.img
    adb pull /sdcard/boot.img
    4
    If all goes well, please share the "image_X.img" files with megasounds, and anyone willing to convert a yota 3 to a 3+.

    What do you think?

    @yotadevices: It's actually a shame that you try to lock down the phone, with the yota2 this was a completely different story. Without the factory images, it is even quite risky to root one's phone.

    THE ROM OF YOTA3+
    https://pan.baidu.com/s/1L2V6_CFi3jfbXekhTXhUOw
    password:irc4
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone