Database Info

[Q] Running X Server on the atrix 2

Hi. I saw and interesting blog post where someone was able to run arch linux on a nook color and run X server directly.
thomaspolasek.blogspot.ca/2012/04/arch-linux-lxde-w-xorg-mouse-keyboard_16.html
So I tried to do this with the Atrix 2, and managed to get Arch working fine through chroot but when I try startx there is a problem accessing the virtual terminal and I get this error.
Code:
Fatal server error:
xf86OpenConsole: Cannot open /dev/tty0 (No such file or directory)
So I checked /dev and found tty, tty00 tty01. Assuming that they were simply named differently by the kernel I symblinked tty0 > tty, but unfortunately I get this error
Code:
Fatal server error:
xf86OpenConsole: Cannot find a free VT: Invalid argument
So I'm wondering if there is there any workaround that will allow X to use the VT? Or is some sort of kernel patch/module required? (wich I don't think would be possible due to the locked bootloader)
Also might it be possible to point X to the VT used by webtop?

bump

usus transformer infinity t700t
Alias.TDP said:
bump
Click to expand...
Click to collapse
When I read the article it seemed like a custom kernel was installed. Stock kernels may not be compiled with VT support, anyhow
my t700t is as follows
ls -l /dev/tty*
[email protected]:/dev# ls tty*
tty tty0 tty1 tty2 ttyFIQ0 ttyHS1 ttyHS2 ttyHS3 ttyHS4 ttyS0 ttyS1 ttyS2 ttyS3
[email protected]:/dev# ls -l tty*
crw-rw-rw- 1 root root 5, 0 May 11 17:58 tty
lrwxrwxrwx 1 root root 3 May 12 14:45 tty0 -> tty
lrwxrwxrwx 1 root root 5 May 12 14:44 tty1 -> ttyS1
lrwxrwxrwx 1 root root 5 May 12 14:44 tty2 -> ttyS2
crw------- 1 root root 254, 0 May 11 17:58 ttyFIQ0
crw-rw-r-- 1 root system 244, 1 May 12 14:26 ttyHS1
crw-rw---- 1 bluetooth bluetooth 244, 2 May 11 17:58 ttyHS2
crw------- 1 root root 244, 3 May 11 17:58 ttyHS3
crw------- 1 root root 244, 4 May 11 17:58 ttyHS4
crw------- 1 root root 4, 64 May 11 17:58 ttyS0
crw------- 1 root root 4, 65 May 11 17:58 ttyS1
crw------- 1 root root 4, 66 May 11 17:58 ttyS2
crw------- 1 root root 4, 67 May 11 17:58 ttyS3
[email protected]:/dev#
I added the -> links myself...
when I run x (using Xorg to start it) it tells me:
Current Operating System: Linux android-fe30b4a8071b23ff 3.1.10-00001-gdc9b6cf #1 SMP PREEMPT Fri Dec 28 19:02:52 CST 2012 armv7l
Kernel command line: tegra_wdt.heartbeat=30 tegraid=30.1.3.0.0 [email protected] commchip_id=0 androidboot.serialno=015d2a508b080209 androidboot.commchip_id=0 video=tegrafb no_console_suspend=1 console=ttyS0,115200n8 debug_uartport=lsport,0 usbcore.old_scheme_first=1 [email protected] [email protected] core_edp_mv=0 audio_codec=wm8903 board_info=245:0:44:de:28 tegraboot=sdmmc gpt gpt_sector=124174335 android.kerneltype=normal androidboot.productid=0x04 androidboot.carrier=wifi-only
Build Date: 11 April 2013 01:10:43PM
so the console is using ttys0 at 155baud
so I'm going to have a look at VT support, though I probably need a custom kernel to get it up and running.
---------- Post added at 04:21 PM ---------- Previous post was at 04:02 PM ----------
here's a list of devices on my t770t as reported by sysfs
[email protected]:/sys# ls -l dev/char/ | grep tty
lrwxrwxrwx 1 root root 0 May 12 15:12 244:1 -> ../../devices/platform/tegra_uart.1/tty/ttyHS1
lrwxrwxrwx 1 root root 0 May 12 15:12 244:2 -> ../../devices/platform/tegra_uart.2/tty/ttyHS2
lrwxrwxrwx 1 root root 0 May 12 15:12 244:3 -> ../../devices/platform/tegra_uart.3/tty/ttyHS3
lrwxrwxrwx 1 root root 0 May 12 15:12 244:4 -> ../../devices/platform/tegra_uart.4/tty/ttyHS4
lrwxrwxrwx 1 root root 0 May 12 15:12 254:0 -> ../../devices/virtual/tty/ttyFIQ0
lrwxrwxrwx 1 root root 0 May 12 15:12 4:64 -> ../../devices/platform/serial8250/tty/ttyS0
lrwxrwxrwx 1 root root 0 May 12 15:12 4:65 -> ../../devices/platform/serial8250/tty/ttyS1
lrwxrwxrwx 1 root root 0 May 12 15:12 4:66 -> ../../devices/platform/serial8250/tty/ttyS2
lrwxrwxrwx 1 root root 0 May 12 15:12 4:67 -> ../../devices/platform/serial8250/tty/ttyS3
lrwxrwxrwx 1 root root 0 May 12 15:12 5:0 -> ../../devices/virtual/tty/tty
lrwxrwxrwx 1 root root 0 May 12 15:12 5:1 -> ../../devices/virtual/tty/console
lrwxrwxrwx 1 root root 0 May 12 15:12 5:2 -> ../../devices/virtual/tty/ptmx
[email protected]
You can start xorg as follows
Xorg vt##
replacing ## with the number of the vt e.g.
Xorg vt0
This gives me a mix of three sperate errors, a file not found if the vt# isn't in /dev/vtt#, and io error if i symlink to a ttys and ad error saying the device doesn't exist if i symink tty0 to tty

[Q] Mounting internal memory in recovery

I successfully ported TWRP for my OT-6012X with almost all functions working but i have one problem. TWRP need /emmc (internal memory to store settings, etc) but I am unable to find method to mount internal memory because my device have no dedicated partition for internal memory but uses folder on of mmcblk0p8 (/data/media/) instead.
My NAND is EMMC and here are device emulators from android:
dev_mount sdcard /storage/sdcard0 [email protected] /devices/platform/goldfish_mmc.0 /devices/platform/mtk-msdc.0/mmc_host
dev_mount sdcard2 /storage/sdcard1 auto /devices/platform/goldfish_mmc.1 /devices/platform/mtk-msdc.1/mmc_host
But in recovery all I could mount is here, you will spot there is no any emulated drives
Code:
drwxr-xr-x 3 root root 280 Mar 19 19:40 .
drwxr-xr-x 4 root root 80 Mar 19 19:40 ..
drwxr-xr-x 2 root root 200 Mar 19 19:40 by-num
lrwxrwxrwx 1 root root 18 Mar 19 19:40 mmcblk0 -> /dev/block/mmcblk0
lrwxrwxrwx 1 root root 23 Mar 19 19:40 mmcblk0boot0 -> /dev/block/mmcblk0boot0
lrwxrwxrwx 1 root root 23 Mar 19 19:40 mmcblk0boot1 -> /dev/block/mmcblk0boot1
lrwxrwxrwx 1 root root 20 Mar 19 19:40 mmcblk0p1 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 Mar 19 19:40 mmcblk0p2 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Mar 19 19:40 mmcblk0p3 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 Mar 19 19:40 mmcblk0p4 -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Mar 19 19:40 mmcblk0p5 -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Mar 19 19:40 mmcblk0p6 -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Mar 19 19:40 mmcblk0p7 -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 Mar 19 19:40 mmcblk0p8 -> /dev/block/mmcblk0p8
Here is an idea: How about to create some script which will mount /data and create symlink /emmc -> /data/media/ just to get rid of error messages from TWRP which appears each time TWRP start (while trying to load/save config, etc...)
Question: How can i create script which will start automatic as TWRP load to mount and create that symbolic link? Is there any trick like init.d or so? Can i put my code in init.rc? Any suggestions?
Solved with injecting code in init.rc (mount /data, symlink /data/media)

[Q] OnePlus One won't boot if USB is UNPLUGGED

So, I have an issue with my OPO when I unplug the USB cable it reboots and start to boot loop.
I had tried many things like this Guide to go back to Stock,
I also downloaded the latest Cyanogen Mod Stable and tried with that without good results.
Then tried this custom rom , nothing change.
I even tried the persist.img fix but didn't fix it.
Even if i'm in the recovery and I unplug the usb,
it reboots and stay boot looping.
I have access to fastboot and TWRP.
If you have any idea about how can I get near to fix this I would greatly appreciate your help.

Omegakenshin said:
So, I have an issue with my OPO when I unplug the USB cable it reboots and start to boot loop.
I had tried many things like this Guide to go back to Stock,
I also downloaded the latest Cyanogen Mod Stable and tried with that without good results.
Then tried this custom rom , nothing change.
I even tried the persist.img fix but didn't fix it.
Even if i'm in the recovery and I unplug the usb,
it reboots and stay boot looping.
I have access to fastboot and TWRP.
If you have any idea about how can I get near to fix this I would greatly appreciate your help.
Click to expand...
Click to collapse
What ROM does your phone currently have?
If you leave the USB cable plugged in, can you successfully boot into and use your system?

JeffDC said:
What ROM does your phone currently have?
If you leave the USB cable plugged in, can you successfully boot into and use your system?
Click to expand...
Click to collapse
Thanks for replying, currently i'm in the latest Cyanogen Mod version,
but after some attempts to fix it, right now I can't boot to any rom,
if I do a Factory Reset from the TWRP recovery,
it shows the Cyanogen logo and suddenly starts to boot loop.
Why do you ask, is there something I can do if I get to boot the system again? Just in case
(Note: I leave the phone boot looping all the night to discharge the battery but it was no use)

I'm back, now I can boot into the OxygenOS with
OnePlus_Bacon_OxygenOS_201601190107.zip
But have the same problem, when I'm not plugged to a source of energy,
it stay for some seconds on and then reboots and start to boot loop.

This is the last lines of adb logcat I'm able to get until I unplug the cable
Code:
E/QSEECOMAPI: (10932): Error::opening QSEECom device
E/EntSec (10932): [ML_DMN] [Listener ] "Error: qseecom_register_listener failed (-1)"
E/EntSec (10932): [ML_DMN] [Main ] "Error: ML daemon failed to start"
D/Ulp_jni ( 1164): Location CB invoked
E/NetlinkEvent( 344): NetlinkEvent::FindParam(): Parameter 'TIME_NS' not found
D/TelephonyIcons( 2599): getDataActivity, sub=0, activity=4
D/TelephonyIcons( 2599): getDataActivity, sub=0, activity=0
I/Crashlytics(10116): Crashlytics report upload FAILED: 57BFB69902C7-0001-2784-8F82A85B21D0.cls
D/KeyguardUpdateMonitor( 2599): received broadcast android.intent.action.BATTERY_CHANGED
D/KeyguardUpdateMonitor( 2599): handleBatteryUpdate
I/OemPowerUI( 1164): battery charge 100% level=100 temperature=345 voltage=4255 plugged=1 chargeType=0
D/charger_monitor( 544): vchg_loop stable: 1, is_settled = 0,usb_target_ua = 0, usbin_current_now = 100000,fastchg_sts = 0, num_attempts = 0
D/TelephonyIcons( 2599): getDataActivity, sub=0, activity=3
D/TelephonyIcons( 2599): getDataActivity, sub=0, activity=0

What happens if you leave the phone boot looping, until he battery drains out?
Then plug in and let charge for a short time?

Are you sure you've flashed tz.img from latest COS?

erorcun said:
Are you sure you've flashed tz.img from latest COS?
Click to expand...
Click to collapse
Yes I try that, but maybe the memory could be corrupted because I flashed a custom recovery and when I reboot I still had the stock one, until I erase the recovery partition and flash it again.
Is there a way to verify if the partitions are corrupted?

erorcun said:
Are you sure you've flashed tz.img from latest COS?
Click to expand...
Click to collapse
I was checking into this and when I "ls -l" in adb shell from the recovery this is what it shows
Code:
~ # ls -l
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x 2 root root 0 Jan 17 02:32 boot
drwxr-xr-x 2 root root 0 Jan 17 02:32 cache
lrwxrwxrwx 1 root root 13 Jan 1 00:00 charger -> /sbin/healthd
drwxr-xr-x 2 root root 0 Jan 1 00:00 data
-rw-r--r-- 1 root root 4908 Jan 1 00:00 default.prop
drwxr-xr-x 10 root root 4140 Jan 17 02:32 dev
drwxr-xr-x 2 root root 0 Jan 17 02:32 etc
-rw-r--r-- 1 root root 35567 Jan 1 00:00 file_contexts
dr-xr-x--- 3 system system 16384 Jan 1 00:00 firmware
-rw-r----- 1 root root 1730 Jan 1 00:00 fstab.bacon
-rwxr-x--- 1 root root 320204 Jan 1 00:00 init
-rwxr-x--- 1 root root 4163 Jan 1 00:00 init.rc
-rwxr-x--- 1 root root 2122 Jan 1 00:00 init.recovery.bacon.rc
-rwxr-x--- 1 root root 1718 Jan 1 00:00 init.recovery.qcom.rc
drwxr-xr-x 3 root root 0 Jan 1 00:00 license
drwxrwx--x 8 system system 4096 Jan 17 01:06 persist
dr-xr-xr-x 155 root root 0 Jan 1 00:00 proc
-rw-r--r-- 1 root root 3227 Jan 1 00:00 property_contexts
drwxr-xr-x 2 root root 0 Jan 17 02:32 recovery
drwxr-xr-x 3 root root 0 Jan 1 00:00 res
drwx------ 2 root root 0 Jun 20 2015 root
drwxr-x--- 2 root root 0 Jan 17 02:32 sbin
drwxrwxrwx 2 root root 0 Jan 17 02:32 sdcard
-rw-r--r-- 1 root root 1278 Jan 1 00:00 seapp_contexts
-rw-r--r-- 1 root root 57 Jan 1 00:00 selinux_version
-rw-r--r-- 1 root root 180887 Jan 1 00:00 sepolicy
-rw-r--r-- 1 root root 10597 Jan 1 00:00 service_contexts
drwxr-xr-x 2 root root 0 Jan 17 02:32 sideload
drwxr-xr-x 2 root root 0 Jan 1 00:00 supersu
dr-xr-xr-x 14 root root 0 Jan 17 02:32 sys
drwxr-xr-x 2 root root 0 Jan 1 00:00 system
drwxrwxr-x 2 root shell 60 Jan 17 02:32 tmp
drwxr-xr-x 4 root root 0 Jan 1 00:00 twres
-rw-r--r-- 1 root root 9101 Jan 1 00:00 ueventd.bacon.rc
-rw-r--r-- 1 root root 9101 Jan 1 00:00 ueventd.qcom.rc
-rw-r--r-- 1 root root 7439 Jan 1 00:00 ueventd.rc
drwxrwxrwx 2 root root 0 Jan 17 02:32 usb_otg
drwxr-xr-x 3 root root 0 Jan 1 00:00 vendor
There is something wrong there, when I flash tz it says ok, but this shows otherwise,
what do you think it could be?

i'm also facing issue ....so what did you do???
Still using the OPO??

thxxht said:
i'm also facing issue ....so what did you do???
Still using the OPO??
Click to expand...
Click to collapse
After trying almost everything, I buy a battery online and after change it my phone could boot again.
It almost seems weird, but seems like the power provided wasn't enough for the processor to boot into system or something and it keep rebooting.
You'll have to search how to open your OnePlus and change the battery if you wanna try this.
Good luck, let me know if you fix it

[PE-UL00] Honor 6 PLUS - Urgent partition layout question

Hello,
I messed up my Honor 6 PLUS (PE-UL00) SENSORHUB partition - possibly overwriting it with an image other than the SENSORHUB.img (extracted from UPDATE.APP). Can someone with a stock Lollipop or MM please post their partition layout which can be obtained using the following command in ADB SHELL:
ls -l /dev/block/platform/hi_mci.0/by-name
My current layout (with corrupted SENSORHUB partition - phone does not boot) is as follows:
lrwxrwxrwx 1 root root 21 Nov 17 10:19 3rdmodem -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 Nov 17 10:19 3rdmodemnvm -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 Nov 17 10:19 3rdmodemnvmbkp -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 Nov 17 10:19 boot -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Nov 17 10:19 cache -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 Nov 17 10:19 cust -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 Nov 17 10:19 dfx -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Nov 17 10:19 dts -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 20 Nov 17 10:19 fastboot -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Nov 17 10:19 fw_hifi -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 20 Nov 17 10:19 fw_lpm3 -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Nov 17 10:19 hibench -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 Nov 17 10:19 hisitest0 -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 Nov 17 10:19 hisitest1 -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 Nov 17 10:19 misc -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Nov 17 10:19 modem -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 Nov 17 10:19 modem_dsp -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 Nov 17 10:19 modem_om -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 Nov 17 10:19 modemnvm_backup -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 20 Nov 17 10:19 modemnvm_factory -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 Nov 17 10:19 modemnvm_img -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 Nov 17 10:19 modemnvm_system -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 Nov 17 10:19 modemnvm_update -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 20 Nov 17 10:19 nvme -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 Nov 17 10:19 oeminfo -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Nov 17 10:19 recovery -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Nov 17 10:19 recovery2 -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 Nov 17 10:19 recovery3 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 20 Nov 17 10:19 reserved1 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Nov 17 10:19 reserved2 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Nov 17 10:19 secure_storage -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 Nov 17 10:19 sensorhub -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Nov 17 10:19 splash -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 Nov 17 10:19 splash2 -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 Nov 17 10:19 splash3 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Nov 17 10:19 system -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 Nov 17 10:19 teeos -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Nov 17 10:19 userdata -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 20 Nov 17 10:19 vrl -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 Nov 17 10:19 vrl_backup -> /dev/block/mmcblk0p2
I suppose the SENSORHUB partition should be on another mmcblk - that's why I get the following error when booting the phone:
Error!
Func NO: 12 (FUNC_LOAD_IOM3)
Error NO: 1
I suppose the partition layout can also be from similar models, such as the PE-TL10.
Thanks in advance for a fast help

Allright.. the layout seems OK - and thanks to Split74 I managed to resurrect the sensorhub partition :good:
However I found an interesting thing - the Huawei update extractor tool extracts images from UPDATE.APP - however these contain additional data in the header and cannot be directly cloned using the dd command in TWRP/ADB SHELL.
Thus I and Split74 need someone to dump their Honor 6 PLUS (PE-UL00 or PE-TL10 should also be OK) boot, recovery, system and cust partitions using dd - they contain only stock data and no personal files AFAIK.
Anyone is willing to help two desperate Honor 6 Plus owners? (I am stuck on MM (camera not focusing, sensors not working) and cannot downgrade do LL and Split74 cannot boot at all, only TWRP) Please kindly PM me or Split74, I will also post the necessary instructions in this post..

we are in deep s mate! =) no1 have Honor 6 plus! such a shame it's a fantastic device! (when you dont mess with android haha)
EDIT: Booting again DC-Phoenix tool did It!

YOTA 3+ FIRMWARE news

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:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.
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.
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.

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.

George white said:
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.
Click to expand...
Click to collapse
hope that there will be technical experts to help dump rom as soon as possible.

George white said:
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.
Click to expand...
Click to collapse
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 ----------
George white said:
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.
Click to expand...
Click to collapse
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

Please, can somebody explain to George White how he can extract the rom ??

a396889843 said:
could you please contact me through qq?
Click to expand...
Click to collapse
There are some problems with registration in QQ in my country today. I'll contact as soon as everything will be OK.

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

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 !

George white said:
There are some problems with registration in QQ in my country today. I'll contact as soon as everything will be OK.
Click to expand...
Click to collapse
I have used WeChat to add the wigwamchannel as a friend. Please agree to add

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.

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

joygram said:
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
Click to expand...
Click to collapse
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!

welcome to discuss dumping 3+ rom on Wechat
joygram said:
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
Click to expand...
Click to collapse
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!

Hi joygram:
Quote: Originally Posted by joygram
first unlock boot loader yotaphone.
yota's boot loader unlock is simple. but all data lost.
Click to expand...
Click to collapse
Can you please tell me HOW ??
Can you show us with some nice screenshots ?
and enter twrp recovery mode.
Click to expand...
Click to collapse
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

megasounds said:
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
Click to expand...
Click to collapse
Y3 Unlock code:
fastboot flashing unlock
OR
fastboot flashing oem
Y3 TWRP
fastboot recovery TWRP.img
AND
fastboot recoverybp TWRP.img

George white said:
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.
Click to expand...
Click to collapse
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

whynot4444 said:
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
Click to expand...
Click to collapse
Please... can somebody make it ? With that we will put the Yota3+ on our Yota 3
Thanks!

skirep said:
Please... can somebody make it ? With that we will put the Yota3+ on our Yota 3
Thanks!
Click to expand...
Click to collapse
first i dont have yota 3 + to test it

Any news from the rom ?
Sent from my Y3 using Tapatalk

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