Guide backup recovery stock Meizu M2 Mini - Meizu M2 / M2 Mini Guides, News, & Discussion

Step :
Install adb driver
Root devices
Open adb type :
adb shell
su
ls -al /dev/block/platform/mtk-msdc.0/by-name (see from update-script file stockrom)
lrwxrwxrwx root root 2015-12-14 15:21 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-12-14 15:21 cache -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-12-14 15:21 custom -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-12-14 15:21 expdb -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-12-14 15:21 flashinfo -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2015-12-14 15:21 frp -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-12-14 15:21 keystore -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-12-14 15:21 lk -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-12-14 15:21 logo -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-12-14 15:21 metadata -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-12-14 15:21 nvdata -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-12-14 15:21 nvram -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-12-14 15:21 oemkeystore -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-12-14 15:21 para -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-12-14 15:21 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-12-14 15:21 protect1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-12-14 15:21 protect2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-12-14 15:21 recovery -> /dev/block/mmcblk0p8 <<=========<<<
lrwxrwxrwx root root 2015-12-14 15:21 seccfg -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-12-14 15:21 secro -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-12-14 15:21 system -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-12-14 15:21 tee1 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-12-14 15:21 tee2 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-12-14 15:21 userdata -> /dev/block/mmcblk0p23
dd if=/dev/block/mmcblk0p8 of=/sdcard/recovery.img
(reference of @broadways on post http://forum.xda-developers.com/showpost.php?p=64312955&postcount=125 )​
Take backup recovery.img from sdcard and save in folder ImgExtractor_32-64Bit
Open folder and click menu - Run as administrator
Select 3 - unpack process
Select 4 - repack process
Rename recovery-new.img to recovery.img
Flash recovery.img with Flashify-premium-1.8.3.apk / fastboot or etc,
Open Rebootmanager.apk - reboot to recovery
Finished
___
{
"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"
}
___
___
___
Files :
ImgExtractor_32-64Bit source from boycracked
Flashify-premium-1.8.3.apk
recovery-stock-M2-flyme-4.5.4iglobal
recovery-stock-M2-flyme-5.1.6.0global
recovery-stock-M2-flyme-5.1.8.0global
recovery-stock-M2-flyme-5.1.9.0global
recovery-stock-M2-flyme-5.1.10.0global
recovery-stock-M2-flyme-5.1.11.0global
recovery-stock-M2-flyme-5.1.12.0global

and the possibility of this method can be used for other android,

Great..it very useful

Related

Moto e us lte / boot.img / mounts

Im not really a dev but i know my way around android. I figured this could help kickstart development for us. I have pulled my boot.img and attached it below.
Here are the mount points for building a rom. May differ from the different varients. My model is XT1527 US LTE.
HTML:
ls -al /dev/block/platform/soc.0/by-name
lrwxrwxrwx root root 1970-01-23 12:12 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-23 12:12 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-23 12:12 abootBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-23 12:12 boot -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-23 12:12 cache -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-01-23 12:12 carrier -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-23 12:12 cid -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-23 12:12 clogo -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-23 12:12 dhob -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-23 12:12 factorytune1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-23 12:12 factorytune2 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-23 12:12 frp -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-23 12:12 fsc -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-23 12:12 fsg -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-23 12:12 hob -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-23 12:12 hyp -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-23 12:12 hypBackup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-23 12:12 keystore -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-23 12:12 kpan -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-23 12:12 logo -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-23 12:12 logs -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-23 12:12 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-23 12:12 misc -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-23 12:12 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-23 12:12 modemst1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-23 12:12 modemst2 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-23 12:12 oem -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-23 12:12 padA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-23 12:12 padB -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-23 12:12 padC -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-23 12:12 persist -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-23 12:12 recovery -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-23 12:12 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-23 12:12 rpmBackup -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-23 12:12 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-23 12:12 sec -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-23 12:12 sp -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-23 12:12 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-23 12:12 system -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-23 12:12 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-23 12:12 tzBackup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-23 12:12 userdata -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-01-23 12:12 utags -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-23 12:12 utagsBackup -> /dev/block/mmcblk0p17
Excellent.... Thank u....I will try to release a ROM within a week
Shawn5162 said:
Excellent.... Thank u....I will try to release a ROM within a week
Click to expand...
Click to collapse
good news, good luck for your build
Shawn5162 said:
Excellent.... Thank u....I will try to release a ROM within a week
Click to expand...
Click to collapse
awesome, if you need a tester, please pm.
Shawn5162 said:
Excellent.... Thank u....I will try to release a ROM within a week
Click to expand...
Click to collapse
Shawn, you got a Moto E 2015? :laugh:
I find myself fortunate getting MotoG 2015 n Moto E 2015, both being worked upon by you! Thanks man!
If anybody who us good at linux knows how to add these mount points to cwm or philz touch im trying to port a build for us pm me.
WIFI tethering
I just picked this phone up today and cricket has ripped out the WIFI tethering. If anyone has a stock rooted rom please send me a link.
Mounting points are different on my cmda moto e2 will try to upload them later
bzo22 said:
Mounting points are different on my cmda moto e2 will try to upload them later
Click to expand...
Click to collapse
yup the cdma models and the 3g only models will probably have different mounts.
cmda xt1526 boostmobile surina
s -al /dev/block/platform/soc.0/by-name <
/dev/block/platform/soc.0/by-name: Permission denied
1|[email protected]_cdma:/ $ su
s -al /dev/block/platform/soc.0/by-name <
lrwxrwxrwx root root 1970-01-31 14:18 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-31 14:18 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-31 14:18 abootBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-31 14:18 boot -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-31 14:18 cache -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-31 14:18 carrier -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-31 14:18 cid -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-31 14:18 clogo -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-31 14:18 dhob -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-31 14:18 factorytune1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-31 14:18 factorytune2 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-31 14:18 frp -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-31 14:18 fsc -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-31 14:18 fsg -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-31 14:18 hob -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-31 14:18 hyp -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-31 14:18 hypBackup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-31 14:18 keystore -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-31 14:18 kpan -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-31 14:18 logo -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-31 14:18 logs -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-31 14:18 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-31 14:18 misc -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-31 14:18 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-31 14:18 modemst1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-31 14:18 modemst2 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-31 14:18 padA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-31 14:18 padB -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-31 14:18 padC -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-31 14:18 persist -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-31 14:18 recovery -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-31 14:18 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-31 14:18 rpmBackup -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-31 14:18 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-31 14:18 sec -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-31 14:18 sp -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-31 14:18 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-31 14:18 system -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-31 14:18 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-31 14:18 tzBackup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-31 14:18 userdata -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-01-31 14:18 utags -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-31 14:18 utagsBackup -> /dev/block/mmcblk0p17
[email protected]_cdma:/ #
bzo22 said:
s -al /dev/block/platform/soc.0/by-name <
<SNIP>
[email protected]_cdma:/ #
Click to expand...
Click to collapse
How did you get root on the xt1526 boost phone bzo22? Any chance you could post the stock boot loader img file or direct me to a working copy of a bootloader for it?
phliptrip said:
How did you get root on the xt1526 boost phone bzo22? Any chance you could post the stock boot loader img file or direct me to a working copy of a bootloader for it?
Click to expand...
Click to collapse
I used twrp to flash super user the recovery works for our device too...but do not flash it just boot it from fastboot. Which partition is boot loader stored . is it aboot or boot section
aboot.img
bzo22 said:
I used twrp to flash super user the recovery works for our device too...but do not flash it just boot it from fastboot. Which partition is boot loader stored . is it aboot or boot section
Click to expand...
Click to collapse
Here u go the aboot.img
Rooted this Phone
{
"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"
}
phliptrip said:
How did you get root on the xt1526 boost phone bzo22? Any chance you could post the stock boot loader img file or direct me to a working copy of a bootloader for it?
Click to expand...
Click to collapse
---------- Post added at 08:32 PM ---------- Previous post was at 08:29 PM ----------
i have root on this phone look and see.
http://imgur.com/tll9LYH,TeVRm5I,4dBA7v5,TdZJI1m,vJyFZEa
---------- Post added at 08:35 PM ---------- Previous post was at 08:32 PM ----------
here are some more pictures of my phone.
http://imgur.com/tll9LYH,TeVRm5I,4dBA7v5,TdZJI1m,vJyFZEa#1
http://imgur.com/tll9LYH,TeVRm5I,4dBA7v5,TdZJI1m,vJyFZEa#2
http://imgur.com/tll9LYH,TeVRm5I,4dBA7v5,TdZJI1m,vJyFZEa#3
http://imgur.com/tll9LYH,TeVRm5I,4dBA7v5,TdZJI1m,vJyFZEa#4.
there you go. im not giving you the files.because i can
fix-this! said:
Im not really a dev but i know my way around android. I figured this could help kickstart development for us. I have pulled my boot.img and attached it below.
Here are the mount points for building a rom. May differ from the different varients. My model is XT1527 US LTE.
HTML:
ls -al /dev/block/platform/soc.0/by-name
lrwxrwxrwx root root 1970-01-23 12:12 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-23 12:12 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-23 12:12 abootBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-23 12:12 boot -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-23 12:12 cache -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-01-23 12:12 carrier -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-23 12:12 cid -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-23 12:12 clogo -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-23 12:12 dhob -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-23 12:12 factorytune1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-23 12:12 factorytune2 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-23 12:12 frp -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-23 12:12 fsc -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-23 12:12 fsg -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-23 12:12 hob -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-23 12:12 hyp -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-23 12:12 hypBackup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-23 12:12 keystore -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-23 12:12 kpan -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-23 12:12 logo -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-23 12:12 logs -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-23 12:12 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-23 12:12 misc -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-23 12:12 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-23 12:12 modemst1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-23 12:12 modemst2 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-23 12:12 oem -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-23 12:12 padA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-23 12:12 padB -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-23 12:12 padC -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-23 12:12 persist -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-23 12:12 recovery -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-23 12:12 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-23 12:12 rpmBackup -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-23 12:12 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-23 12:12 sec -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-23 12:12 sp -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-23 12:12 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-23 12:12 system -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-23 12:12 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-23 12:12 tzBackup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-23 12:12 userdata -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-01-23 12:12 utags -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-23 12:12 utagsBackup -> /dev/block/mmcblk0p17
Click to expand...
Click to collapse
hey bro i needed some help. first can this boot image be used for 3g version.
If not then please can you tell me how to extract the boot.img of moto e 3g version
I've got the XT1527 for cricket and I'm willing to test. I'm no dev but ive been flashing roms constantly on all sorts of devices for a few years and id like to get involved and learn more if possible. This is my daily driver though so I might be a little cautious until there's a working twrp or something for the US version but this is a good phone so I'm very eager to see what ends up being made for this phone. Normally I'll look a phone up before buying it to make sure there's plenty of stuff available to keep me busy with it but when I saw this one had very little I actually got excited since Im sure this one will wind up with some good stuff and for the first time I won't be starting with a phone months after the forum died down lol
hakr4life said:
I've got the XT1527 for cricket and I'm willing to test. I'm no dev but ive been flashing roms constantly on all sorts of devices for a few years and id like to get involved and learn more if possible. This is my daily driver though so I might be a little cautious until there's a working twrp or something for the US version but this is a good phone so I'm very eager to see what ends up being made for this phone. Normally I'll look a phone up before buying it to make sure there's plenty of stuff available to keep me busy with it but when I saw this one had very little I actually got excited since Im sure this one will wind up with some good stuff and for the first time I won't be starting with a phone months after the forum died down lol
Click to expand...
Click to collapse
Same here keep me in the loop. I'm eager to brick my new phone
Sent from my MotoE2(4G-LTE) using XDA Free mobile app
+1 for at%t/aio/cricket users on the XT1527 model. there has got to be a workaround for the unlock on this. @mdewii23 @hakr4life
Can someone provide stock recovery?
I've scoured the internet over and over and come up with nothing yet
Sent from my Nexus 4 using XDA Free mobile app

Persist data partition of xt1540

hi dear members and developers i just want to share the persist data partition of motorola xt1540
this was readed by this way to coolaborate in a solution for bring us the " OEM UNLOCK " option enabled for unlock bootloader on locked devices
here is what i did
here is the parititons map
[email protected]_umts:/ # ls -al /dev/block/platform/msm_sdcc.1/by-name
ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1969-12-31 18:16 DDR -> /dev/block/mmcblk0
p3
lrwxrwxrwx root root 1969-12-31 18:16 aboot -> /dev/block/mmcbl
k0p4
lrwxrwxrwx root root 1969-12-31 18:16 abootBackup -> /dev/block
/mmcblk0p11
lrwxrwxrwx root root 1969-12-31 18:16 boot -> /dev/block/mmcblk
0p31
lrwxrwxrwx root root 1969-12-31 18:16 cache -> /dev/block/mmcbl
k0p40
lrwxrwxrwx root root 1969-12-31 18:16 carrier -> /dev/block/mmc
blk0p38
lrwxrwxrwx root root 1969-12-31 18:16 cid -> /dev/block/mmcblk0
p25
lrwxrwxrwx root root 1969-12-31 18:16 clogo -> /dev/block/mmcbl
k0p28
lrwxrwxrwx root root 1969-12-31 18:16 customize -> /dev/block/m
mcblk0p39
lrwxrwxrwx root root 1969-12-31 18:16 dhob -> /dev/block/mmcblk
0p22
lrwxrwxrwx root root 1969-12-31 18:16 frp -> /dev/block/mmcblk0
p17
lrwxrwxrwx root root 1969-12-31 18:16 fsc -> /dev/block/mmcblk0
p24
lrwxrwxrwx root root 1969-12-31 18:16 fsg -> /dev/block/mmcblk0
p23
lrwxrwxrwx root root 1969-12-31 18:16 hob -> /dev/block/mmcblk0
p21
lrwxrwxrwx root root 1969-12-31 18:16 hyp -> /dev/block/mmcblk0
p7
lrwxrwxrwx root root 1969-12-31 18:16 hypBackup -> /dev/block/m
mcblk0p14
lrwxrwxrwx root root 1969-12-31 18:16 keystore -> /dev/block/mm
cblk0p36
lrwxrwxrwx root root 1969-12-31 18:16 kpan -> /dev/block/mmcblk
0p30
lrwxrwxrwx root root 1969-12-31 18:16 logo -> /dev/block/mmcblk
0p27
lrwxrwxrwx root root 1969-12-31 18:16 logs -> /dev/block/mmcblk
0p16
lrwxrwxrwx root root 1969-12-31 18:16 metadata -> /dev/block/mm
cblk0p26
lrwxrwxrwx root root 1969-12-31 18:16 misc -> /dev/block/mmcblk
0p9
lrwxrwxrwx root root 1969-12-31 18:16 modem -> /dev/block/mmcbl
k0p1
lrwxrwxrwx root root 1969-12-31 18:16 modemst1 -> /dev/block/mm
cblk0p19
lrwxrwxrwx root root 1969-12-31 18:16 modemst2 -> /dev/block/mm
cblk0p20
lrwxrwxrwx root root 1969-12-31 18:16 oem -> /dev/block/mmcblk0
p37
lrwxrwxrwx root root 1969-12-31 18:16 padA -> /dev/block/mmcblk
0p10
lrwxrwxrwx root root 1969-12-31 18:16 padB -> /dev/block/mmcblk
0p18
lrwxrwxrwx root root 1969-12-31 18:16 padC -> /dev/block/mmcblk
0p34
lrwxrwxrwx root root 1969-12-31 18:16 persist -> /dev/block/mmc
blk0p29
lrwxrwxrwx root root 1969-12-31 18:16 recovery -> /dev/block/mm
cblk0p32
lrwxrwxrwx root root 1969-12-31 18:16 rpm -> /dev/block/mmcblk0
p5
lrwxrwxrwx root root 1969-12-31 18:16 rpmBackup -> /dev/block/m
mcblk0p12
lrwxrwxrwx root root 1969-12-31 18:16 sbl1 -> /dev/block/mmcblk
0p2
lrwxrwxrwx root root 1969-12-31 18:16 sp -> /dev/block/mmcblk0p
35
lrwxrwxrwx root root 1969-12-31 18:16 ssd -> /dev/block/mmcblk0
p33
lrwxrwxrwx root root 1969-12-31 18:16 system -> /dev/block/mmcb
lk0p41
lrwxrwxrwx root root 1969-12-31 18:16 tz -> /dev/block/mmcblk0p
6
lrwxrwxrwx root root 1969-12-31 18:16 tzBackup -> /dev/block/mm
cblk0p13
lrwxrwxrwx root root 1969-12-31 18:16 userdata -> /dev/block/mm
cblk0p42
lrwxrwxrwx root root 1969-12-31 18:16 utags -> /dev/block/mmcbl
k0p8
lrwxrwxrwx root root 1969-12-31 18:16 utagsBackup -> /dev/block
/mmcblk0p15
[email protected]_umts:/ #
Click to expand...
Click to collapse
since " oem unlock " ability is set on the pesist data partition i read partition using this command
adb shell dd if=/sdcard/unlock.img of=/dev/block/mmcblk0p29
Click to expand...
Click to collapse
all this is based on @playahate post , that talk about nexus 6 & 9 oem set on solution on semibricked devices , if anyone need to test this solucion on semibricked moto g3 xt1540 is invited
hope it helps to anyone
also i still loking for a temp root or full root acces without bootloader unlock , if anyone have this kind of solution please share
Wait....I don't quite understand....does this unlock the bootloader? If so, how do you push it there without unlocking first??
hp420 said:
Wait....I don't quite understand....does this unlock the bootloader? If so, how do you push it there without unlocking first??
Click to expand...
Click to collapse
(I think) in short what this does is enable OEM unlocking found in developer options, if you don't have access which has actually happened to me once before because of the first CAF 6.0 test we had.
The important part is the adb code used I believe.
christopherrrg said:
(I think) in short what this does is enable OEM unlocking found in developer options, if you don't have access which has actually happened to me once before because of the first CAF 6.0 test we had.
The important part is the adb code used I believe.
Click to expand...
Click to collapse
Oh, ok. That makes sense. Thanks!
Hello, can you share with me the hbo dhob & fsc files / partitions only, the one attached has all the partitions on it, thanks

Oh Boy - Its Official "desire 820s "

So here we are
Its officialy confirmed
{
"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"
}
Cant wait to create a rom / kernel for This Beast
Who has received it
Itsnot reciveable , just spam them tell them that htc dev didnt publish it yet
Just copy and paste this to them ,, they should know their ota system sucks
We need a download link for HTC desire 820s Dual Sim Software Version 1.14.709.1 Sense 7 , Lolipop 5.0.2 Build as itsn't recievable as OTA " we didn't and will never recive it as kk users " it only come out of the box by luck.
Please publish it . we are stuck at kitkat
There's no way they can send lollipop and Sense 7 OTA. That's about 4 GBs!!!!
---------- Post added at 04:07 PM ---------- Previous post was at 04:04 PM ----------
I've been spamming them the entire week. They are too reluctant to give the source code or OTA
I think going to get refund and reppace this device
Mohamed Yaser said:
I think going to get refund and reppace this device
Click to expand...
Click to collapse
Let me be patient until December
What about battery ,charging 6% / Hour ??
Too slow?
Wait a minute. Isn't a50mldtul desire 820s?
where u got that from
http://www.droidviews.com/list-of-android-device-codenames/
Yeah it is
i think also we are getting a recovery soon
[email protected]_a50ml_dtul:/ $ su
/platform/mtk-msdc.0"This is our chip"/by-name <
lrwxrwxrwx root root 2015-07-08 00:46 boot -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-07-08 00:46 cache -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-07-08 00:46 cota -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-07-08 00:46 dkb -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-07-08 00:46 expdb -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-07-08 00:46 flashinfo -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-07-08 00:46 kb -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-07-08 00:46 lk -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-07-08 00:46 logo -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-07-08 00:46 metadata -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-07-08 00:46 nvram -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-07-08 00:46 para -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-07-08 00:46 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-07-08 00:46 protect1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-07-08 00:46 protect2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-07-08 00:46 recovery -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-07-08 00:46 seccfg -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-07-08 00:46 secro -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-07-08 00:46 system -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-07-08 00:46 tee1 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-07-08 00:46 tee2 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-07-08 00:46 userdata -> /dev/block/mmcblk0p21
[email protected]_a50ml_dtul:/ #
http://forum.xda-developers.com/desire-820/orig-development/desire-820-models-msm-chipset-twrp-2-8-t3147260/page4
http://forum.xda-developers.com/des...20-models-msm-chipset-twrp-2-8-t3147260/page4
The kernel source code for a50mldtul is at htcdev
There's this one I flashed. Seems to be working fine. It can backup. Haven't tried restoring or installing zip though.
CWM
Isn't this the greatest breakthrough for our phone
Oh , May be i will start work on a rom
PS ,, Give me a link to our source code and How u did unlock the bl
I'm not sure how I unlocked it. I remember trying to unlock it at htcdev.com and using kingo htc bootloader unlock but I wasn't successfull. I don't know maybe it's still locked.
At htcdev there are kernel source codes with a50mldtul name under Desire 820 dual sim. But again I'm not if sure they are for Desire 820s.
You can get the CWM I flashed here
http://www.4shared.com/rar/SM6wcBzyce/CWM_820s.html
It's fully working for me
Gibz97 said:
I'm not sure how I unlocked it. I remember trying to unlock it at htcdev.com and using kingo htc bootloader unlock but I wasn't successfull. I don't know maybe it's still locked.
At htcdev there are kernel source codes with a50mldtul name under Desire 820 dual sim. But again I'm not if sure they are for Desire 820s.
You can get the CWM I flashed here
http://www.4shared.com/rar/SM6wcBzyce/CWM_820s.html
It's fully working for me
Click to expand...
Click to collapse
who made this cwm
I found it here
http://forum.xda-developers.com/and...6732-64bit-t2998980/post61761125#post61761125
Pretty old thread
---------- Post added at 12:19 AM ---------- Previous post was at 12:18 AM ----------
Mohamed Yaser said:
who made this cwm
Click to expand...
Click to collapse
Have you tried it?
Gibz97 said:
I found it here
http://forum.xda-developers.com/and...6732-64bit-t2998980/post61761125#post61761125
Pretty old thread
---------- Post added at 12:19 AM ---------- Previous post was at 12:18 AM ----------
Have you tried it?
Click to expand...
Click to collapse
i didn't find the kernel source ??
no not yet

[HELP][BOOT LOGO][SPLASH] How to edit or create new splash screen

Device- Xiaomi Redmi2 running CM 12.1
Here's the partition info of my device
HTML:
lrwxrwxrwx root root 2016-01-11 17:56 DDR -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2016-01-11 17:56 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2016-01-11 17:56 abootbak -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2016-01-11 17:56 boot -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2016-01-11 17:56 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2016-01-11 17:56 config -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2016-01-11 17:56 fsc -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2016-01-11 17:56 fsg -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2016-01-11 17:56 hyp -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2016-01-11 17:56 hypbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2016-01-11 17:56 keystore -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2016-01-11 17:56 misc -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2016-01-11 17:56 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2016-01-11 17:56 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2016-01-11 17:56 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2016-01-11 17:56 oem -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2016-01-11 17:56 pad -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2016-01-11 17:56 persist -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2016-01-11 17:56 recovery -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2016-01-11 17:56 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2016-01-11 17:56 rpmbak -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2016-01-11 17:56 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2016-01-11 17:56 sbl1bak -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2016-01-11 17:56 sec -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2016-01-11 17:56 splash -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2016-01-11 17:56 ssd -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2016-01-11 17:56 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2016-01-11 17:56 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2016-01-11 17:56 tzbak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2016-01-11 17:56 userdata -> /dev/block/mmcblk0p30
As you can see "mmcblk0p18" belongs to splash partiton.
I used "dd" command to dump splash.img on sdcard with adb shell.
But now what?
How to edit it?
I've searched for many hours but came up with mediatek or HTC thereads which is pretty annoying
Tools I've tried so far--> Android Kitchen, Kernel Kitchen, Logo Builder.
Please help me through this.. I desperately want to make a splash image for my device.
Thanks.

How can I backup everything on my rooted N4? (Every single thing)

This might seem like a newbie question but this isn't the case.
I already know Titanium backup exists and I have been using it for years. However a few months back I suffered from the ''infamous brick'' seen everywhere on this thread caused by the unofficial CM13 ROM.
This brick corrupted everything on my phone (EFS Partition, etc) and the ONLY thing i could ever boot into was the recovery.
2 months and $150 later in repairs (literally everyone failed to fix it software-side) I learned my lesson
I need to back up my entire phone incase something like this happens again. What app should I use, and what should I back up?
Thanks
Do a nandroid backup from the recovery
Nortabun said:
This might seem like a newbie question but this isn't the case.
I already know Titanium backup exists and I have been using it for years. However a few months back I suffered from the ''infamous brick'' seen everywhere on this thread caused by the unofficial CM13 ROM.
This brick corrupted everything on my phone (EFS Partition, etc) and the ONLY thing i could ever boot into was the recovery.
2 months and $150 later in repairs (literally everyone failed to fix it software-side) I learned my lesson
I need to back up my entire phone incase something like this happens again. What app should I use, and what should I back up?
Thanks
Click to expand...
Click to collapse
Here is a snapshot of everything on the entire phone.
[email protected]:/dev/block/platform/15540000.dwmmc0/by-name # ls -la
ls -la
lrwxrwxrwx root root 2015-12-31 13:08 BOOT -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-12-31 13:08 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-12-31 13:08 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-12-31 13:08 CACHE -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-12-31 13:08 CARRIER -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-12-31 13:08 CDMA-RADIO -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-12-31 13:08 DNT -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-12-31 13:08 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-12-31 13:08 HIDDEN -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-12-31 13:08 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-12-31 13:08 PARAM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-12-31 13:08 PERSDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-12-31 13:08 RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-12-31 13:08 RECOVERY -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-12-31 13:08 RESERVED2 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-12-31 13:08 SYSTEM -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-12-31 13:08 TOMBSTONES -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-12-31 13:08 USERDATA -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-12-31 13:08 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-12-31 13:08 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-12-31 13:08 m9kefs3 -> /dev/block/mmcblk0p6
Option 1 Command line:
Quick and easy way to backup /system
dd if=/dev/block/mmcblk0p18 of=/sdcard/system.img bs=4096
Quick and easy way to backup the kernel
dd if=/dev/block/mmcblk0p9 of=/sdcard/boot.img bs=4096
Quick and easy way to back up EFS
dd if=/dev/block/mmcblk0p3 of=/sdcard/efs.img bs=4096
Quick and easy way to back up Radio
dd if=/dev/block/mmcblk0p13 of=/sdcard/radio.img bs=4096
Quick and easy way to back up Recovery
dd if=/dev/block/mmcblk0p10 of=/sdcard/recovery.img bs=4096
Create a directory on your machine. C:\Phonerecovery
Copy all those files from /sdcard to that directory.
With those images you can build a ODIN flash file
Using Cygwin or a Linux machine: tar -H ustar -c boot.img kernel.img recovery.img system.img > Unf*ckMyNote4.tar
Using ODIN to restore stock firmware usually will unf*ck a CM flashed phone. Keeping one handy from a provider of stock Samsung Note 4 firmware is also a good thing.
Option 2:
Custom recovery like CWM / TWRP installed on your phone
Since you were able to reboot into recovery having a TWRP backup probably would have saved you.
{
"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"
}

Categories

Resources