YOTA 3+ FIRMWARE news - YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev
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
Related
[Q] N915F mounting points
Does anyone has by any chance the mount points table for the N915F? Thank you.
Instruction starbucks2010 said: Does anyone has by any chance the mount points table for the N915F? Thank you. Click to expand... Click to collapse If you can instruct me - I'll do it.
I tried with (adb shell) cat /proc/partitions and cat /proc/mounts but I don't know which partition is which mmcblk. I checked also in fstab file but the mount point information is missing from it. PS. Finaly I found out. If anyone need it: lrwxrwxrwx root root 2014-01-10 11:07 aboot -> /dev/block/mmcblk0p7 lrwxrwxrwx root root 2014-01-10 11:07 apnhlos -> /dev/block/mmcblk0p1 lrwxrwxrwx root root 2014-01-10 11:07 boot -> /dev/block/mmcblk0p17 lrwxrwxrwx root root 2014-01-10 11:07 cache -> /dev/block/mmcblk0p25 lrwxrwxrwx root root 2014-01-10 11:07 dbi -> /dev/block/mmcblk0p5 lrwxrwxrwx root root 2014-01-10 11:07 ddr -> /dev/block/mmcblk0p6 lrwxrwxrwx root root 2014-01-10 11:07 efs -> /dev/block/mmcblk0p13 lrwxrwxrwx root root 2014-01-10 11:07 fota -> /dev/block/mmcblk0p19 lrwxrwxrwx root root 2014-01-10 11:07 hidden -> /dev/block/mmcblk0p26 lrwxrwxrwx root root 2014-01-10 11:07 mdm1m9kefs1 -> /dev/block/mmcblk0p14 lrwxrwxrwx root root 2014-01-10 11:07 mdm1m9kefs2 -> /dev/block/mmcblk0p15 lrwxrwxrwx root root 2014-01-10 11:07 mdm1m9kefs3 -> /dev/block/mmcblk0p10 lrwxrwxrwx root root 2014-01-10 11:07 mdm1m9kefsc -> /dev/block/mmcblk0p16 lrwxrwxrwx root root 2014-01-10 11:07 misc -> /dev/block/mmcblk0p20 lrwxrwxrwx root root 2014-01-10 11:07 modem -> /dev/block/mmcblk0p2 lrwxrwxrwx root root 2014-01-10 11:07 pad -> /dev/block/mmcblk0p11 lrwxrwxrwx root root 2014-01-10 11:07 param -> /dev/block/mmcblk0p12 lrwxrwxrwx root root 2014-01-10 11:07 persdata -> /dev/block/mmcblk0p23 lrwxrwxrwx root root 2014-01-10 11:07 persist -> /dev/block/mmcblk0p22 lrwxrwxrwx root root 2014-01-10 11:07 recovery -> /dev/block/mmcblk0p18 lrwxrwxrwx root root 2014-01-10 11:07 rpm -> /dev/block/mmcblk0p8 lrwxrwxrwx root root 2014-01-10 11:07 sbl1 -> /dev/block/mmcblk0p3 lrwxrwxrwx root root 2014-01-10 11:07 sbl1bak -> /dev/block/mmcblk0p4 lrwxrwxrwx root root 2014-01-10 11:07 ssd -> /dev/block/mmcblk0p21 lrwxrwxrwx root root 2014-01-10 11:07 system -> /dev/block/mmcblk0p24 lrwxrwxrwx root root 2014-01-10 11:07 tz -> /dev/block/mmcblk0p9 lrwxrwxrwx root root 2014-01-10 11:07 userdata -> /dev/block/mmcblk0p27 Good luck.
does anyone knows which mount point is for "data": mmcblk0p26 (hidden) or mmcblk0p27 (userdata)? thank you
Here's some info from the N915T Code: lrwxrwxrwx 1 root root 20 Jan 3 2014 aboot -> /dev/block/mmcblk0p7 lrwxrwxrwx 1 root root 20 Jan 3 2014 apnhlos -> /dev/block/mmcblk0p1 lrwxrwxrwx 1 root root 21 Jan 3 2014 boot -> /dev/block/mmcblk0p17 lrwxrwxrwx 1 root root 21 Jan 3 2014 cache -> /dev/block/mmcblk0p25 lrwxrwxrwx 1 root root 20 Jan 3 2014 dbi -> /dev/block/mmcblk0p5 lrwxrwxrwx 1 root root 20 Jan 3 2014 ddr -> /dev/block/mmcblk0p6 lrwxrwxrwx 1 root root 21 Jan 3 2014 efs -> /dev/block/mmcblk0p13 lrwxrwxrwx 1 root root 21 Jan 3 2014 fota -> /dev/block/mmcblk0p19 lrwxrwxrwx 1 root root 21 Jan 3 2014 mdm1m9kefs1 -> /dev/block/mmcblk0p14 lrwxrwxrwx 1 root root 21 Jan 3 2014 mdm1m9kefs2 -> /dev/block/mmcblk0p15 lrwxrwxrwx 1 root root 21 Jan 3 2014 mdm1m9kefs3 -> /dev/block/mmcblk0p10 lrwxrwxrwx 1 root root 21 Jan 3 2014 mdm1m9kefsc -> /dev/block/mmcblk0p16 lrwxrwxrwx 1 root root 21 Jan 3 2014 misc -> /dev/block/mmcblk0p20 lrwxrwxrwx 1 root root 20 Jan 3 2014 modem -> /dev/block/mmcblk0p2 lrwxrwxrwx 1 root root 21 Jan 3 2014 pad -> /dev/block/mmcblk0p11 lrwxrwxrwx 1 root root 21 Jan 3 2014 param -> /dev/block/mmcblk0p12 lrwxrwxrwx 1 root root 21 Jan 3 2014 persdata -> /dev/block/mmcblk0p23 lrwxrwxrwx 1 root root 21 Jan 3 2014 persist -> /dev/block/mmcblk0p22 lrwxrwxrwx 1 root root 21 Jan 3 2014 recovery -> /dev/block/mmcblk0p18 lrwxrwxrwx 1 root root 20 Jan 3 2014 rpm -> /dev/block/mmcblk0p8 lrwxrwxrwx 1 root root 20 Jan 3 2014 sbl1 -> /dev/block/mmcblk0p3 lrwxrwxrwx 1 root root 20 Jan 3 2014 sbl1bak -> /dev/block/mmcblk0p4 lrwxrwxrwx 1 root root 21 Jan 3 2014 ssd -> /dev/block/mmcblk0p21 lrwxrwxrwx 1 root root 21 Jan 3 2014 system -> /dev/block/mmcblk0p24 lrwxrwxrwx 1 root root 20 Jan 3 2014 tz -> /dev/block/mmcblk0p9 lrwxrwxrwx 1 root root 21 Jan 3 2014 userdata -> /dev/block/mmcblk0p26
[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!
[Guide] Elephone U Pro User Manual (Flashtools,Unlock,ADB,etc)
Elephone U Pro Guide for:
1. set up ADB
2. set up QPST/QFIL Qualcomm Flashtool
3. How to use Qfil Flashtool / Flashing Guide and Drivers
4. How to Unlock Bootloader / enter Recovery
5. How to : U Pro is Very hard to Brick. very good thing
6. some infos about the phone ( Developer only)
----------------------------------------------------------------------------------------------------------------
First of all you have to enable USB Debugging in Developer Settings
(to enable it go to settings/system/about and tap 7 times on the Build number .
that enables Developer Settings in settings/system .)
Download this Zip. In it there is all you need:
https://1drv.ms/u/s!Am93l3qEx-D_hJVt9qwUVrxYwHvG3w
extract the zip folder to your desktop and install everything one by one like in this Guide.
Install Python2.7 and Python3.... neccesary for flashtools
1. Set up ADB
copy the adb folder to C:/ you can start it with a command window (cmd)
use cd.. (location back ) and cd (location up) to browse to it.
it has to look like
Code:
C:\>cd adb
Code:
C:\adb>
2. set up QPST/QFIL Qualcomm Flashtool
-Start the.exe file in QPST.2.7.460 folder.
-accept the terms
-dont change the install path . (
-choose complete installation
-install
- you have to browse to the QFIL.exe in C:\Program Files (x86)\Qualcomm\QPST\bin , best would be to make shortcut for it on the desktop.
it will look like this:
{
"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"
}
4. How to use it:
We need to reboot to edl (emergency download mode) use flashtools.
you can easy reboot to it via adb, use:
Code:
adb shell
reboot edl
have trouble, phone dont boot, look at part 5 of this guide
---------------------------------------------------------------------------
prepare the Flashtool:
in Select Build Type:
choose: Flat Build
in Select Programmer:
browse and choose the "prog_emmc_ufs_firehose_Sdm660_ddr.elf" file
Load XML:
now choose the rawprogram_unsparse.xml and right after the patch0.xml
you can press the "download content"
wait a bit , at the end of the flashing procedure it will make an error, thats normal if the patch0.xml is empty.
here:
Drivers
we need to use the Qualcomm HS-USB QDLoader 9008
in the downloaded zip is the driver , just install it .
this will install:
HS-USB QDLoader 9008 and Qualcomm HS-USB Diagnostics 900E
for Flashing we only need the HS-USB QDLoader 9008.
--------------------------------------------------------------------------------------
4. How to Unlock Bootloader
enable USB Debugging in Developer Settings and OEM UNLOCK BOOTLOADER
(to enable it go to settings/system/about and tap 7 times on the Build number .
that enables Developer Settings in settings/system .)
plug in the phone cable and open a cmd
go to the adb folder ( c:/adb)
and input
Code:
adb shell
(a Notification will pop up on the phone, apply it)
then input
Code:
reboot bootloader
phone will reboot to bootloader.
Now input
Code:
fastboot flashing unlock
and apply the unlock on your phone with the volume and power button.
You will get a warranty notification by each boot now. thats normal
The Reason to unlock the bootloader is that we can flash custom roms or kernels/recovery etc...
Notice: the bootloader itself (in the current state) dont allow fastboot commands, we will all do with QFIL flashtool.
Unlocking your bootloader will wipe the userdata , all your stuff will be gone. make a backup of your pictures/musik etc first
Enter Recovery
to Reboot to recovery there are no button Commands , so we can only have access to recovery by
booting to bootloader and choose recovery or via adb
Code:
adb shell
reboot bootloader
or
Code:
reboot recovery
you will see an android with a red icon. now hold power and press vol+ .
if that dont work, press power and vol- for togehter for ~3seconds and slide from vol- to vol+ and back to vol- while holding power button.
------------------------------------------------------------------------------------------------------------------------------------------------------------
5. how to solve a bootloop, not booting phone.
the U Pro is very hard to brick. nearly not possible.
with this method you can always go back to the EDL Mode and flash a Stock Rom.
open your device manager and connect your phone to your pc.
hold power vol- and vol+ togehter as long as the phone vibrates.
in device manager you will see the HS-USB QDLoader 9008 driver. then use flashtool to flash a Stock Rom.
if you see the HS-USB Diagnostics 900E make the procedure again, hold power vol- and vol+......
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
6. some infos about the phone ( Developer only)
there is no recovery images . its merged in the boot.img
also with the new Android 8.0 and project Treble we have A/B partitions
Code:
ls -l /dev/block/platform/soc/c0c4000.sdhci/by-name
Code:
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 abl_a -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 abl_b -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 apdp -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 bluetooth_a -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 bluetooth_b -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 boot_a -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 boot_b -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 cmnlib64_a -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 cmnlib64_b -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 cmnlib_a -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 cmnlib_b -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 ddr -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 devcfg_a -> /dev/block/mmcblk0p57
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 devcfg_b -> /dev/block/mmcblk0p58
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 devinfo -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 dip -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 dpo -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 dsp_a -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 dsp_b -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 factory -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 factorybak -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 frp -> /dev/block/mmcblk0p59
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 fsc -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 fsg -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 1970-01-08 10:22 hyp_a -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 1970-01-08 10:22 hyp_b -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 keymaster_a -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 keymaster_b -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 keystore -> /dev/block/mmcblk0p56
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 limits -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 logdump -> /dev/block/mmcblk0p60
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 logfs -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 mdtp_a -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 mdtp_b -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 mdtpsecapp_a -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 mdtpsecapp_b -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 misc -> /dev/block/mmcblk0p55
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 modem_a -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 modem_b -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 modemst1 -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 modemst2 -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 msadp -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 persist -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 20 1970-01-08 10:22 pmic_a -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 pmic_b -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 prodinfo -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 rawdump -> /dev/block/mmcblk0p63
lrwxrwxrwx 1 root root 20 1970-01-08 10:22 rpm_a -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 1970-01-08 10:22 rpm_b -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 sec -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 splash -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 ssd -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 sti -> /dev/block/mmcblk0p61
lrwxrwxrwx 1 root root 21 19
70-01-08 10:22 storsec -> /dev/block/mmcblk0p62
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 system_a -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 system_b -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 toolsfv -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 20 1970-01-08 10:22 tz_a -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 1970-01-08 10:22 tz_b -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 userdata -> /dev/block/mmcblk0p66
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 vbmeta_a -> /dev/block/mmcblk0p64
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 vbmeta_b -> /dev/block/mmcblk0p65
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 vendor_a -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 vendor_b -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 20 1970-01-08 10:22 xbl_a -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 1970-01-08 10:22 xbl_b -> /dev/block/mmcblk0p2
sector and start adress for making rawprogram_unsparse.xml ( i made a full one already,its in my stock rom 20180227 thread)
Code:
Number Start End Size File system Name Flags
1 131072s 138239s 7168s xbl_a
2 138240s 145407s 7168s xbl_b
3 145408s 153599s 8192s tz_a
4 153600s 161791s 8192s tz_b
5 161792s 162815s 1024s rpm_a
6 162816s 163839s 1024s rpm_b
7 163840s 164863s 1024s hyp_a
8 164864s 165887s 1024s hyp_b
9 165888s 166911s 1024s pmic_a
10 166912s 167935s 1024s pmic_b
11 167936s 172031s 4096s fsg
12 262144s 393215s 131072s boot_a
13 393216s 524287s 131072s boot_b
14 524288s 6815743s 6291456s ext4 system_a
15 6815744s 13107199s 6291456s ext4 system_b
16 13107200s 14745599s 1638400s ext4 vendor_a
17 14745600s 16383999s 1638400s ext4 vendor_b
18 16384000s 16386047s 2048s keymaster_a
19 16386048s 16388095s 2048s keymaster_b
20 16388096s 16390143s 2048s cmnlib_a
21 16390144s 16392191s 2048s cmnlib64_a
22 16392192s 16394239s 2048s cmnlib_b
23 16394240s 16396287s 2048s cmnlib64_b
24 16396288s 16404479s 8192s mdtpsecapp_a
25 16404480s 16412671s 8192s mdtpsecapp_b
26 16412672s 16478207s 65536s mdtp_a
27 16478208s 16543743s 65536s mdtp_b
28 16543744s 16769023s 225280s fat16 modem_a
29 16769024s 16994303s 225280s fat16 modem_b
30 16994304s 17027071s 32768s ext4 dsp_a
31 17027072s 17059839s 32768s ext4 dsp_b
32 17059840s 17061887s 2048s abl_a
33 17061888s 17063935s 2048s abl_b
34 17063936s 17065983s 2048s dip
35 17065984s 17065991s 8s devinfo
36 17065992s 17066503s 512s apdp
37 17066504s 17067015s 512s msadp
38 17067016s 17067017s 2s dpo
39 17067024s 17133871s 66848s splash
40 17133872s 17133879s 8s limits
41 17133880s 17135927s 2048s toolsfv
42 17170432s 17186815s 16384s logfs
43 17301504s 17303551s 2048s ddr
44 17303552s 17303583s 32s sec
45 17303584s 17305631s 2048s bluetooth_a
46 17305632s 17307679s 2048s bluetooth_b
47 17432576s 17436671s 4096s prodinfo
48 17436672s 17457151s 20480s ext4 factory
49 17457152s 17477631s 20480s ext4 factorybak
50 17477632s 17477633s 2s fsc
51 17477640s 17477655s 16s ssd
52 17477656s 17481751s 4096s modemst1
53 17481752s 17485847s 4096s modemst2
54 17485848s 17551383s 65536s ext4 persist
55 17551384s 17553431s 2048s misc
56 17553432s 17554455s 1024s keystore
57 17554456s 17556503s 2048s devcfg_a
58 17556504s 17558551s 2048s devcfg_b
59 17558552s 17559575s 1024s frp
60 17559576s 17690647s 131072s logdump
61 17690648s 17694743s 4096s sti
6
2 17825792s 17826047s 256s storsec
63 17956864s 18219007s 262144s rawdump
64 18219008s 18219135s 128s vbmeta_a
65 18219136s 18219263s 128s vbmeta_b
66 18350080s 244277214s 225927135s userdata
Code:
cat /proc/cmdline
Code:
rcupdate.rcu_expedited=1 console=ttyMSM0,115200,n8 androidboot.console=ttyMSM0 earlycon=msm_serial_dm,0xc170000 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 sched_enable_hmp=1 sched_enable_power_aware=1 service_locator.enable=1 swiotlb=1 androidboot.configfs=true androidboot.usbcontroller=a800000.dwc3 buildvariant=user veritykeyid=id:7e4333f9bba00adfe0ede979e28ed1920492b40f root=/dev/dm-0 dm="system none ro,0 1 android-verity /dev/mmcblk0p15" androidboot.verifiedbootstate=orange androidboot.keymaster=1 androidboot.veritymode=enforcing androidboot.bootdevice=c0c4000.sdhci androidboot.serialno=A208DDBK0402 androidboot.isn=A208DDBK0402 androidboot.baseband=sdm mdss_mdp.panel=1:dsi:0:qcom,mdss_dsi_sw43404_amoled_fhd_video:config0:1:none:cfg:single_dsi androidboot.slot_suffix=_b skip_initramfs rootwait ro init=/init
need something else, then write me a pm
enjoy.
Awesome! Thanks for this!
need something else, then write me a pm enjoy.[/QUOTE] Hi Skeleton, am going through a lot of xda materials trying to educate myself in this very interesting stuff and I just stumbled upon something I'm hoping could help with getting my Imei/meid back. According to this articlewww.leakite.com/2016/09/how-to-flash-qualcomm-mbn-firmware.html there may be an option when choosing the 'rawprogram'xml as "rawprogram_unsparse_without_qcn.xml" an option which preserves RF Calibration data, IMEI and WiFi/Bluetooth Address, I have no idea If that could be edited, I'm far from trying to play a 'smart pants', I'm pretty new to this and I have a total respect and appreciation for all the work you're putting into the XDA. Just a thought and thanks in advance if you'd find a moment to see that article.
mzsquared said: need something else, then write me a pm enjoy. Click to expand... Click to collapse Hi Skeleton, am going through a lot of xda materials trying to educate myself in this very interesting stuff and I just stumbled upon something I'm hoping could help with getting my Imei/meid back. According to this articlewww.leakite.com/2016/09/how-to-flash-qualcomm-mbn-firmware.html there may be an option when choosing the 'rawprogram'xml as "rawprogram_unsparse_without_qcn.xml" an option which preserves RF Calibration data, IMEI and WiFi/Bluetooth Address, I have no idea If that could be edited, I'm far from trying to play a 'smart pants', I'm pretty new to this and I have a total respect and appreciation for all the work you're putting into the XDA. Just a thought and thanks in advance if you'd find a moment to see that article.[/QUOTE]Sounds interesting. rawprogram_unsparse_without_qcn.xml I will take a look asap Gesendet von meinem U_Pro mit Tapatalk
skeleton1911 said: Hi Skeleton, am going through a lot of xda materials trying to educate myself in this very interesting stuff and I just stumbled upon something I'm hoping could help with getting my Imei/meid back. According to this articlewww.leakite.com/2016/09/how-to-flash-qualcomm-mbn-firmware.html there may be an option when choosing the 'rawprogram'xml as "rawprogram_unsparse_without_qcn.xml" an option which preserves RF Calibration data, IMEI and WiFi/Bluetooth Address, I have no idea If that could be edited, I'm far from trying to play a 'smart pants', I'm pretty new to this and I have a total respect and appreciation for all the work you're putting into the XDA. Just a thought and thanks in advance if you'd find a moment to see that article. Click to expand... Click to collapse Sounds interesting. rawprogram_unsparse_without_qcn.xml I will take a look asap Gesendet von meinem U_Pro mit Tapatalk[/QUOTE] Thank you! By_the_way that "leakite" site is loaded with resources on qualcom and everything else. Found detailed tutorial on how to back up the phone without Qfil, gonna try it tomorrow. It's under "How to unbrick Qualcomm Android devices"
mzsquared said: Sounds interesting. rawprogram_unsparse_without_qcn.xml I will take a look asap Gesendet von meinem U_Pro mit Tapatalk Click to expand... Click to collapse Thank you! By_the_way that "leakite" site is loaded with resources on qualcom and everything else. Found detailed tutorial on how to back up the phone without Qfil, gonna try it tomorrow. It's under "How to unbrick Qualcomm Android devices"[/QUOTE] That would be very interesting for all of us. I hope you can find something out. The flash via QFIL is a decent way, but one new app which is not working can cause a lot of trouble if you don't have the possibility to make a nandroid backup before installing it.
That would be very interesting for all of us. I hope you can find something out. The flash via QFIL is a decent way, but one new app which is not working can cause a lot of trouble if you don't have the possibility to make a nandroid backup before installing it.[/QUOTE] No, it didn't work. The phone doesn't see exFat formatted Sd card. Also, be aware of ads-attack on parallel sites linked for downloads. The main site is ok though.
Gracias Genios! salve mi U Pro que le habia hecho Hard Brick y pense que ya no servia mas. Lo salve con este metodo: 5. how to solve a bootloop, not booting phone. the U Pro is very hard to brick. nearly not possible. with this method you can always go back to the EDL Mode and flash a Stock Rom. open your device manager and connect your phone to your pc. hold power vol- and vol+ togehter as long as the phone vibrates. in device manager you will see the HS-USB QDLoader 9008 driver. then use flashtool to flash a Stock Rom. if you see the HS-USB Diagnostics 900E make the procedure again, hold power vol- and vol+...... y QFIL Saludos desde Argentina
Hello i have a bricked elephone u pro and try this procedure but i doesent work for me. Anyone here that can help me with that? The Phone always boot into qd loader 9008. Some help wold be great
Hi, does anyone have a copy of the file linked in post 1?
[re-partition]Hard-Bricked FRD-L09 ! i need backup of gpt.img
Hello everyone ive bricked my phone while trying to update to emui 8 first of all its was stuck at 99% ercovery update for hours, so ive shutdown it , so its stuck at honor logo with no erecovery no recovery , only fastboot was accessible(but mine was having a locked bootloader and locked frp so fastboot not going to help me at all) so ive google for solutions and i've managed to get the phone enter to EDL mode by shorting the two pins on the MB (after opening the phone case) when connecting the phone on my linux machine using usb it got reconeized as a serial usb, then after googling again i found that i can flash the board software while the phone is on EDL mode without unlocking the bootloader so i ve tried to search for the software board for my phone but unlucky all i got is password protected firmwares (i cant afford to buy something online or pay for dc-unlocker ) after lot of searching on the internet i found a similiar board firmware that belong to the huawei MATE 8 that got the same chipset and cpu (kirin 950) so i tried to flash it using EDL mode (load fastboot.img to ram then flash every image one by one using fastboot flash partiton) everything on the flashing process worked flashed all the partition on the phone with success but after rebooting the phone its no longer powering on when connecting to compter its reconeized as a adb device and it is detected as a fastboot device when taping command fastboot devices. so i ve tried to flash partitions from the official update package but unlucky the update package doesnt contain the GPT.img file. it is the necessary file for repartition the emmc ( because i ve flashed the gpt.img from the mate 8 and its no longer accepting images from honor 8 package. only mate 8 images that are successfully flashing through fastboot) so please if someone can provide me with the software board of the honor 8 FRD-l09 or the file gpt.img of the honor 8 frd-l09 or do a backup of it . i will be appreciated asking for help if there is another methode for unbricking the phone (obviously my only option is paying for dc-unlocker but i cant afford that ) and thank you all
hello, i can send you the gpt.img, but please explain how can i get it for you
kinkat1995 said: hello, i can send you the gpt.img, but please explain how can i get it for you Click to expand... Click to collapse thanks for reply. i dont know exactly the name of partitions but there is a guide provided by member @majdinj https://forum.xda-developers.com/showthread.php?t=2450045 Pr-requirement: -root -adb -sd card where backup will be saved -es file explorer or any root explorer first explore this directory using a root explorer /dev/block/platform/ then search every folder in the "/dev/block/platform" directory that contain a folder named "by-name" lets assume that your find the folder xxx that contain the "by-name" folder -run the following commands using adb terminal => adb shell => su => ls -al /dev/block/platform/xxx/by-name it will give you info about the dev block names and their familiar names search for the name gpt and check its dev block name it must be something like this gpt -> /dev/block/mcmcblkxxx then final part make a backup of it using this command => dd if=/dev/block/mmcblkxxx of=/sdcard/gpt.img (replace mmcblkxxx with the dev block name that matched the gpt partiton)
ay.amouch said: thanks for reply. i dont know exactly the name of partitions but there is a guide provided by member @majdinj https://forum.xda-developers.com/showthread.php?t=2450045 Pr-requirement: -root -adb -sd card where backup will be saved -es file explorer or any root explorer first explore this directory using a root explorer /dev/block/platform/ then search every folder in the "/dev/block/platform" directory that contain a folder named "by-name" lets assume that your find the folder xxx that contain the "by-name" folder -run the following commands using adb terminal => adb shell => su => ls -al /dev/block/platform/xxx/by-name it will give you info about the dev block names and their familiar names search for the name gpt and check its dev block name it must be something like this gpt -> /dev/block/mcmcblkxxx then final part make a backup of it using this command => dd if=/dev/block/mmcblkxxx of=/sdcard/gpt.img (replace mmcblkxxx with the dev block name that matched the gpt partiton) Click to expand... Click to collapse i listed the partitions but there are no with gpt name, see the output: Code: HWFRD:/ # ls -al /dev/block/platform/hi_mci.0/by-name total 0 drwxr-xr-x 2 root root 1200 2020-05-21 19:36 . drwxr-xr-x 4 root root 1320 2020-05-21 19:36 .. lrwxrwxrwx 1 root root 21 2020-05-21 19:36 3rdmodem -> /dev/block/mmcblk0p43 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 3rdmodemnvm -> /dev/block/mmcblk0p14 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 3rdmodemnvmbkp -> /dev/block/mmcblk0p15 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 bootfail_info -> /dev/block/mmcblk0p49 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 cache -> /dev/block/mmcblk0p44 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 cust -> /dev/block/mmcblk0p53 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 dfx -> /dev/block/mmcblk0p42 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 dto -> /dev/block/mmcblk0p35 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 dts -> /dev/block/mmcblk0p34 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 erecovery_kernel -> /dev/block/mmcblk0p22 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 erecovery_ramdisk -> /dev/block/mmcblk0p23 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 erecovery_vbmeta -> /dev/block/mmcblk0p37 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 erecovery_vendor -> /dev/block/mmcblk0p24 lrwxrwxrwx 1 root root 20 2020-05-21 19:36 fastboot -> /dev/block/mmcblk0p5 lrwxrwxrwx 1 root root 20 2020-05-21 19:36 frp -> /dev/block/mmcblk0p4 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 fw_hifi -> /dev/block/mmcblk0p29 lrwxrwxrwx 1 root root 20 2020-05-21 19:36 fw_lpm3 -> /dev/block/mmcblk0p3 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 hisitest0 -> /dev/block/mmcblk0p46 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 hisitest1 -> /dev/block/mmcblk0p47 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 hisitest2 -> /dev/block/mmcblk0p57 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 kernel -> /dev/block/mmcblk0p30 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 misc -> /dev/block/mmcblk0p20 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 modem -> /dev/block/mmcblk0p39 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 modem_dsp -> /dev/block/mmcblk0p40 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 modem_dtb -> /dev/block/mmcblk0p41 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 modem_om -> /dev/block/mmcblk0p18 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 modemnvm_backup -> /dev/block/mmcblk0p10 lrwxrwxrwx 1 root root 20 2020-05-21 19:36 modemnvm_factory -> /dev/block/mmcblk0p6 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 modemnvm_img -> /dev/block/mmcblk0p11 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 modemnvm_system -> /dev/block/mmcblk0p12 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 modemnvm_update -> /dev/block/mmcblk0p21 lrwxrwxrwx 1 root root 20 2020-05-21 19:36 nvme -> /dev/block/mmcblk0p7 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 odm -> /dev/block/mmcblk0p45 lrwxrwxrwx 1 root root 20 2020-05-21 19:36 oeminfo -> /dev/block/mmcblk0p8 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 patch -> /dev/block/mmcblk0p48 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 persist -> /dev/block/mmcblk0p16 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 product -> /dev/block/mmcblk0p56 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 ramdisk -> /dev/block/mmcblk0p31 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 recovery_ramdisk -> /dev/block/mmcblk0p32 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 recovery_vbmeta -> /dev/block/mmcblk0p36 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 recovery_vendor -> /dev/block/mmcblk0p33 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 reserved1 -> /dev/block/mmcblk0p17 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 reserved2 -> /dev/block/mmcblk0p25 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 reserved3 -> /dev/block/mmcblk0p51 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 rrecord -> /dev/block/mmcblk0p50 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 secure_storage -> /dev/block/mmcblk0p13 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 sensorhub -> /dev/block/mmcblk0p28 lrwxrwxrwx 1 root root 20 2020-05-21 19:36 splash -> /dev/block/mmcblk0p9 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 splash2 -> /dev/block/mmcblk0p19 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 system -> /dev/block/mmcblk0p52 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 teeos -> /dev/block/mmcblk0p26 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 trustfirmware -> /dev/block/mmcblk0p27 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 userdata -> /dev/block/mmcblk0p58 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 vbmeta -> /dev/block/mmcblk0p38 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 vendor -> /dev/block/mmcblk0p55 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 version -> /dev/block/mmcblk0p54 lrwxrwxrwx 1 root root 20 2020-05-21 19:36 vrl -> /dev/block/mmcblk0p1 lrwxrwxrwx 1 root root 20 2020-05-21 19:36 vrl_backup -> /dev/block/mmcblk0p2
kinkat1995 said: i listed the partitions but there are no with gpt name, see the output: Code: HWFRD:/ # ls -al /dev/block/platform/hi_mci.0/by-name total 0 drwxr-xr-x 2 root root 1200 2020-05-21 19:36 . drwxr-xr-x 4 root root 1320 2020-05-21 19:36 .. lrwxrwxrwx 1 root root 21 2020-05-21 19:36 3rdmodem -> /dev/block/mmcblk0p43 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 3rdmodemnvm -> /dev/block/mmcblk0p14 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 3rdmodemnvmbkp -> /dev/block/mmcblk0p15 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 bootfail_info -> /dev/block/mmcblk0p49 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 cache -> /dev/block/mmcblk0p44 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 cust -> /dev/block/mmcblk0p53 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 dfx -> /dev/block/mmcblk0p42 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 dto -> /dev/block/mmcblk0p35 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 dts -> /dev/block/mmcblk0p34 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 erecovery_kernel -> /dev/block/mmcblk0p22 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 erecovery_ramdisk -> /dev/block/mmcblk0p23 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 erecovery_vbmeta -> /dev/block/mmcblk0p37 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 erecovery_vendor -> /dev/block/mmcblk0p24 lrwxrwxrwx 1 root root 20 2020-05-21 19:36 fastboot -> /dev/block/mmcblk0p5 lrwxrwxrwx 1 root root 20 2020-05-21 19:36 frp -> /dev/block/mmcblk0p4 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 fw_hifi -> /dev/block/mmcblk0p29 lrwxrwxrwx 1 root root 20 2020-05-21 19:36 fw_lpm3 -> /dev/block/mmcblk0p3 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 hisitest0 -> /dev/block/mmcblk0p46 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 hisitest1 -> /dev/block/mmcblk0p47 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 hisitest2 -> /dev/block/mmcblk0p57 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 kernel -> /dev/block/mmcblk0p30 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 misc -> /dev/block/mmcblk0p20 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 modem -> /dev/block/mmcblk0p39 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 modem_dsp -> /dev/block/mmcblk0p40 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 modem_dtb -> /dev/block/mmcblk0p41 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 modem_om -> /dev/block/mmcblk0p18 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 modemnvm_backup -> /dev/block/mmcblk0p10 lrwxrwxrwx 1 root root 20 2020-05-21 19:36 modemnvm_factory -> /dev/block/mmcblk0p6 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 modemnvm_img -> /dev/block/mmcblk0p11 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 modemnvm_system -> /dev/block/mmcblk0p12 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 modemnvm_update -> /dev/block/mmcblk0p21 lrwxrwxrwx 1 root root 20 2020-05-21 19:36 nvme -> /dev/block/mmcblk0p7 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 odm -> /dev/block/mmcblk0p45 lrwxrwxrwx 1 root root 20 2020-05-21 19:36 oeminfo -> /dev/block/mmcblk0p8 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 patch -> /dev/block/mmcblk0p48 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 persist -> /dev/block/mmcblk0p16 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 product -> /dev/block/mmcblk0p56 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 ramdisk -> /dev/block/mmcblk0p31 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 recovery_ramdisk -> /dev/block/mmcblk0p32 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 recovery_vbmeta -> /dev/block/mmcblk0p36 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 recovery_vendor -> /dev/block/mmcblk0p33 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 reserved1 -> /dev/block/mmcblk0p17 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 reserved2 -> /dev/block/mmcblk0p25 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 reserved3 -> /dev/block/mmcblk0p51 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 rrecord -> /dev/block/mmcblk0p50 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 secure_storage -> /dev/block/mmcblk0p13 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 sensorhub -> /dev/block/mmcblk0p28 lrwxrwxrwx 1 root root 20 2020-05-21 19:36 splash -> /dev/block/mmcblk0p9 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 splash2 -> /dev/block/mmcblk0p19 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 system -> /dev/block/mmcblk0p52 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 teeos -> /dev/block/mmcblk0p26 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 trustfirmware -> /dev/block/mmcblk0p27 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 userdata -> /dev/block/mmcblk0p58 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 vbmeta -> /dev/block/mmcblk0p38 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 vendor -> /dev/block/mmcblk0p55 lrwxrwxrwx 1 root root 21 2020-05-21 19:36 version -> /dev/block/mmcblk0p54 lrwxrwxrwx 1 root root 20 2020-05-21 19:36 vrl -> /dev/block/mmcblk0p1 lrwxrwxrwx 1 root root 20 2020-05-21 19:36 vrl_backup -> /dev/block/mmcblk0p2 Click to expand... Click to collapse thanks for help. i ve just checked your reply on my post with the partitions info, as you said there is no gpt partition on it. i believe that partition is special and it is only provided with a full paid repair firmware because it is not a real partition, it is just a file named gpt.img contain info about every partition name and size and their infos , it is also called ptable.img on some other huawei honor devices i will try one more time to fix before dump it her is my email [email protected] send me these partitions : vrl - vrl_backup - fw_lpm3 you can backup them using following commands and make sure you have inserted an sd card on your device: dd if=/dev/block/mmcblk0p3 of=/sdcard/fw_lpm3.img dd if=/dev/block/mmcblk0p2 of=/sdcard/vrl_backup.img dd if=/dev/block/mmcblk0p1 of=/sdcard/vrl.img
Here are the files
kinkat1995 said: Here are the files Click to expand... Click to collapse thanks
ay.amouch said: thanks Click to expand... Click to collapse Hi my friend, I have the same issue, did u find any solution to this problem. My phone got bootloop, no erecovery no recovery and no dload, just fastboot working. Tried to flash boot and recovery stock images from fastboot but got error this command is not allowed. pls help me with this.
managed to repair imei on Sawshark (LEO-DLXX)
Hi, Just wanted to share that I was able to repair the imei on a Huawei Watch 2 (Sawshark,LEO-DLXX). It goes on just as any other snapdragon imei repair. There are many tutorials out there. The step I was stuck at was opening a diag port on the watch after issuing this command as root. Code: setprop sys.usb.config diag,adb The usb device does change, but not recognized even though Qualcomm drivers are installed. The solution? Manually load this driver named: Qualcomm HS-USB Diagnostics 9404 Some tutorials say some partitions need to be cleared for imei repair to work. Not sure if this is necessary, but these are the partitions that need clearing. Code: ls -al /dev/block/platform/soc/7824900.sdhci/by-name/ < total 0 drwxr-xr-x 2 root root 740 1970-01-29 07:08 . drwxr-xr-x 4 root root 820 1970-01-29 07:08 .. lrwxrwxrwx 1 root root 21 1970-01-29 07:08 DDR -> /dev/block/mmcblk0p21 lrwxrwxrwx 1 root root 20 1970-01-29 07:08 aboot -> /dev/block/mmcblk0p7 lrwxrwxrwx 1 root root 20 1970-01-29 07:08 abootbak -> /dev/block/mmcblk0p8 lrwxrwxrwx 1 root root 21 1970-01-29 07:08 boot -> /dev/block/mmcblk0p29 lrwxrwxrwx 1 root root 21 1970-01-29 07:08 cache -> /dev/block/mmcblk0p34 lrwxrwxrwx 1 root root 21 1970-01-29 07:08 cmnlib -> /dev/block/mmcblk0p24 lrwxrwxrwx 1 root root 21 1970-01-29 07:08 cmnlibbak -> /dev/block/mmcblk0p25 lrwxrwxrwx 1 root root 21 1970-01-29 07:08 config -> /dev/block/mmcblk0p18 lrwxrwxrwx 1 root root 21 1970-01-29 07:08 devinfo -> /dev/block/mmcblk0p23 lrwxrwxrwx 1 root root 21 1970-01-29 07:08 fsc -> /dev/block/mmcblk0p13 lrwxrwxrwx 1 root root 21 1970-01-29 07:08 fsg -> /dev/block/mmcblk0p22 lrwxrwxrwx 1 root root 21 1970-01-29 07:08 keymaster -> /dev/block/mmcblk0p26 lrwxrwxrwx 1 root root 21 1970-01-29 07:08 keymasterbak -> /dev/block/mmcblk0p27 lrwxrwxrwx 1 root root 21 1970-01-29 07:08 keystore -> /dev/block/mmcblk0p17 lrwxrwxrwx 1 root root 21 1970-01-29 07:08 misc -> /dev/block/mmcblk0p15 lrwxrwxrwx 1 root root 21 1970-01-29 07:08 modem -> /dev/block/mmcblk0p32 lrwxrwxrwx 1 root root 21 1970-01-29 07:08 modemst1 -> /dev/block/mmcblk0p11 lrwxrwxrwx 1 root root 21 1970-01-29 07:08 modemst2 -> /dev/block/mmcblk0p12 lrwxrwxrwx 1 root root 21 1970-01-29 07:08 nfc -> /dev/block/mmcblk0p19 lrwxrwxrwx 1 root root 21 1970-01-29 07:08 nvbin -> /dev/block/mmcblk0p10 lrwxrwxrwx 1 root root 20 1970-01-29 07:08 nvdata -> /dev/block/mmcblk0p9 lrwxrwxrwx 1 root root 21 1970-01-29 07:08 oem -> /dev/block/mmcblk0p28 lrwxrwxrwx 1 root root 21 1970-01-29 07:08 recovery -> /dev/block/mmcblk0p31 lrwxrwxrwx 1 root root 21 1970-01-29 07:08 reserved -> /dev/block/mmcblk0p20 lrwxrwxrwx 1 root root 20 1970-01-29 07:08 rpm -> /dev/block/mmcblk0p3 lrwxrwxrwx 1 root root 20 1970-01-29 07:08 rpmbak -> /dev/block/mmcblk0p4 lrwxrwxrwx 1 root root 20 1970-01-29 07:08 sbl1 -> /dev/block/mmcblk0p1 lrwxrwxrwx 1 root root 20 1970-01-29 07:08 sbl1bak -> /dev/block/mmcblk0p2 lrwxrwxrwx 1 root root 21 1970-01-29 07:08 sec -> /dev/block/mmcblk0p30 lrwxrwxrwx 1 root root 21 1970-01-29 07:08 splash -> /dev/block/mmcblk0p16 lrwxrwxrwx 1 root root 21 1970-01-29 07:08 ssd -> /dev/block/mmcblk0p14 lrwxrwxrwx 1 root root 21 1970-01-29 07:08 system -> /dev/block/mmcblk0p33 lrwxrwxrwx 1 root root 20 1970-01-29 07:08 tz -> /dev/block/mmcblk0p5 lrwxrwxrwx 1 root root 20 1970-01-29 07:08 tzbak -> /dev/block/mmcblk0p6 lrwxrwxrwx 1 root root 21 1970-01-29 07:08 userdata -> /dev/block/mmcblk0p35 sawshark:/ # sawshark:/ # dd if=/dev/zero of=/dev/block/mmcblk0p11 dd: /dev/block/mmcblk0p11: No space left on device 8193+0 records in 8192+0 records out 4194304 bytes transferred in 1.069 secs (3923577 bytes/sec) 1|sawshark:/ # dd if=/dev/zero of=/dev/block/mmcblk0p12 dd: /dev/block/mmcblk0p12: No space left on device 8193+0 records in 8192+0 records out 4194304 bytes transferred in 0.854 secs (4911362 bytes/sec) 1|sawshark:/ # dd if=/dev/zero of=/dev/block/mmcblk0p22 dd: /dev/block/mmcblk0p22: No space left on device 8193+0 records in 8192+0 records out 4194304 bytes transferred in 0.951 secs (4410414 bytes/sec) 1|sawshark:/ # The rest is same as any other snapdragon imei repair. Hope this helps some of you out there.