Hi to start id like to say F androidarea51.com they are little cry baby's on a power trip and banning ppl like crazy for no reason...anyways i have recenty purchased a Alcatel LTE One Touch Sonic on 4.1.2 and have been trying to find some help porting CWM to my device. I have MANAGED to pull the boot.img,system.img and recovery.img from my device. I rooted with SRS-Root which can be found here http://download.unlocksamsungonline.nl/~xtrusion/SRSRoot-Setup.exe
I have uploaded and decompled system.img,boot.img and recovery.img which can be found here http://www.mediafire.com/download/2nt0nt9tjrw449f/AlcatelIMG.rar
Once you open the extracted recovery.img you may notice that the fstab is a lil different than lower version android OS's and does not list the partitions name...I will provide a txt file within the next couple of days with the proper partition names and mmcblocks...
If anyone is willing to help me port CWM for this device please feel free to contact me via email or reply with a comment
[email protected]
Ps the system.img has been slightly modified it is rooted and is not stock...I changed some props to change the android OS version id and device id..
___________________________________________________________________________________________________
/dev/block/platform/msm_sdcc.1
lrwxrwxrwx root root 1969-12-31 20:27 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1969-12-31 20:27 abootbk -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1969-12-31 20:27 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1969-12-31 20:27 cache -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1969-12-31 20:27 fota -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1969-12-31 20:27 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1969-12-31 20:27 grow -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1969-12-31 20:27 iqap -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1969-12-31 20:27 iqbp -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1969-12-31 20:27 misc -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1969-12-31 20:27 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1969-12-31 20:27 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1969-12-31 20:27 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1969-12-31 20:27 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1969-12-31 20:27 persist -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1969-12-31 20:27 recovery -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1969-12-31 20:27 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1969-12-31 20:27 rpmbk -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1969-12-31 20:27 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1969-12-31 20:27 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1969-12-31 20:27 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1969-12-31 20:27 sbl3bk -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1969-12-31 20:27 ssd -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1969-12-31 20:27 system -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1969-12-31 20:27 traceability -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1969-12-31 20:27 tunning -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1969-12-31 20:27 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1969-12-31 20:27 tzbk -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1969-12-31 20:27 userdata -> /dev/block/mmcblk0p13
-------------------------------------------------------------------------------------------------------------------------------------------
/dev/block/platform/msm_sdcc.3
lrwxrwxrwx root root 1969-12-31 20:27 p1 -> /dev/block/mmcblk1p1
___________________________________________________________________________________________________
Model: MMC 004G90 (sd/mmc)
Disk /dev/block/mmcblk0: 3959MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 67.1MB 134MB 67.1MB fat16 modem
2 134MB 134MB 131kB sbl1
3 134MB 135MB 262kB sbl2
4 135MB 135MB 524kB sbl3
5 135MB 136MB 524kB aboot
6 136MB 136MB 524kB rpm
7 201MB 212MB 10.5MB boot
8 268MB 269MB 524kB tz
9 269MB 269MB 1024B pad
10 269MB 272MB 3146kB modemst1
11 272MB 275MB 3146kB modemst2
12 336MB 1409MB 1074MB ext4 system
13 1409MB 3288MB 1879MB ext4 userdata
14 3288MB 3297MB 8389kB ext4 persist
15 3297MB 3632MB 336MB ext4 cache
16 3691MB 3692MB 1049kB misc
17 3758MB 3769MB 10.5MB recovery
18 3769MB 3772MB 3146kB fsg
19 3825MB 3825MB 8192B ssd
20 3825MB 3826MB 524kB sbl3bk
21 3826MB 3826MB 524kB abootbk
22 3826MB 3829MB 3146kB tunning
23 3829MB 3830MB 1049kB traceability
24 3830MB 3847MB 16.8MB fota
25 3847MB 3848MB 524kB rpmbk
26 3848MB 3848MB 524kB tzbk
27 3848MB 3849MB 1049kB iqbp
28 3849MB 3856MB 6291kB ext4 iqap
29 3856MB 3959MB 104MB grow
___________________________________________________________________________________________________
I managed to get adb to work with full root access with the device powered off! the downside is there is no working recovery..i wiill leave a download link if anyone would like to see it for themselves however I AM NOT RESPONSIBLE if this ruins your device..Neverthe less im 99.9% positive nothing bad wil happen to your devices otherwise i would not leave a download link to it...
https://www.mediafire.com/?fna3sj08rsdv7w7
-------------------------------------------------------------------------------------------------------------------------------------------
MAKE SURE YOUR SYSTEM IS MOUNTED RW
adb shell
su
busybox mount -o remount,rw system system
-------------------------------------------------------------------------------------------------------------------------------------------
adb push recovery.img /system/bin
adb shell
su
dd if=/system/bin/recovery.img of=/dev/block/mmcblk0p17
rm /system/bin/recovery.img
-------------------------------------------------------------------------------------------------------------------------------------------
busybox poweroff
adb devices
adb shell
su
ls
------------------------------------------------------------------------------------------------------------------------------------------------------------------
Alcatel one touch sonic
I used kingroot to root my Alcatel one touch sonic, but now that I did, do I need the CWM or the other recovery app? Also, how can I flash my ROM? OK still can't find much on this. Did you get that cwm to work? If so could you dumb it Down lol! This is my first root
Hello There
i just brick my phone trying to get rip of a gosh virus wich installs apps on system...
and well now phone is stuck inTracfone logo
is there any way to restore my phone using ur system.img?
i set a fastboot adb and drivers
but the only thing i can do is "adb shell", where i can look into the phone directory
adb fastboot or fastboot flash system system.im is not working
if u can help me pliz that will be nice ><
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
I will be sharing my stock resources with the community here.
Individual Stock Files
Stock boot.img
https://drive.google.com/open?id=1TVKhFx1HAGRXds5U9BTxaEnLfGQuw7sD
Format: .img
Size: 32Mbytes
This is from "RIVER_AMZ_PPO29.114_16_7_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml"
I was successfully able to patch this image using magisk manager. Screenshots of the magisk app and root checker available in attachments.
Full Stock Files
https://drive.google.com/open?id=1U7asJXX1_lJkbateTl0R2adYwVsCg0Fo
Format: .7z
Size: 1.8Gbytes
"RIVER_AMZ_PPO29.114_16_7_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC"
Extract and use with RSD or XML>BAT
Tools
Lenovo MOTO Smart Assistant: https://download.lenovo.com/consumer/mobiles/lmsa_v4.1.0.8_setup.exe
Non-verizon solution for returning to stock (idk if it works for verizon as well, it should)
Moto Software Repair Assistant: https://www.verizonwireless.com/support/knowledge-base-209211/
Verizon solution for returning to stock
Portable Android Tools (adb+fastboot): https://drive.google.com/open?id=13ppb_xveLtP9BBMdz6zYW-R_p4BDO_oW
Partition Info
Code:
drwxr-xr-x 2 root root 1320 1970-01-23 13:12 .
drwxr-xr-x 3 root root 1380 1970-01-23 13:12 ..
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 DDR -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 20 1970-01-23 13:12 aboot_a -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 aboot_b -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 apdp -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 boot_a -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 boot_b -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 carrier -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 cid -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 cmnlib64_a -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 cmnlib64_b -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 cmnlib_a -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 cmnlib_b -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 1970-01-23 13:12 devcfg_a -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 1970-01-23 13:12 devcfg_b -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 devinfo -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 dpo -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 dsp_a -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 dsp_b -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 dtbo_a -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 dtbo_b -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 frp -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 fsc -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 fsg_a -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 fsg_b -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 hw -> /dev/block/mmcblk0p56
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 keymaster_a -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 keymaster_b -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 kpan -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 logo_a -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 logo_b -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 logs -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 metadata -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 misc -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 modem_a -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 modem_b -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 modemst1 -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 modemst2 -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 mota -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 msadp -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 oem_a -> /dev/block/mmcblk0p58
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 oem_b -> /dev/block/mmcblk0p59
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 padA -> /dev/block/mmcblk0p55
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 persist -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 persist2 -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 prov_a -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 prov_b -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 20 1970-01-23 13:12 rpm_a -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 1970-01-23 13:12 rpm_b -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 1970-01-23 13:12 sbl1_a -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 1970-01-23 13:12 sbl1_b -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 sp -> /dev/block/mmcblk0p57
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 syscfg -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 system_a -> /dev/block/mmcblk0p62
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 system_b -> /dev/block/mmcblk0p63
lrwxrwxrwx 1 root root 20 1970-01-23 13:12 tz_a -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 1970-01-23 13:12 tz_b -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 userdata -> /dev/block/mmcblk0p64
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 utags -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 utagsBackup -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 vbmeta_a -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 vbmeta_b -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 vendor_a -> /dev/block/mmcblk0p60
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 vendor_b -> /dev/block/mmcblk0p61
Will be providing more resources soon.
-reserved for flashable scripts-
Thanks for this--question regarding returning to stock
Hi,
Thanks for posting these resources--very useful. Question for you: do you happen to know what the process would be to "undo" root (via Magisk) and TWRP installation to be able to get back to stock 16_7 version? I've currently got a rooted 16_5 version with TWRP, and I think it might be good to get up to the 16_7 version. Thanks in advance.
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.