UPDATE on 09/23:
Thanks Modding.MyMind for all the hard work!
Finally our beloved MT2-L03 have TWRP recovery...Mission Accomplished!!
Please go here for the recovery thread:
http://forum.xda-developers.com/showthread.php?t=2885144
======================
Now we have the phone rooted, before I dare to try anything dangerous, I really hope we can have a recovery first.
Following is the partition of our phone
Code:
[email protected]:/dev/block/platform/msm_sdcc.1/by-name $ ls -l |sort -k 7
lrwxrwxrwx root root 1970-01-01 07:14 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 07:14 modemst2 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-01 07:14 modem -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-01 07:14 fsg -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-01 07:14 fsc -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-01 07:14 ssd -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-01 07:14 log -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-01 07:14 bkbootup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-01 07:14 persist -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-01 07:14 boot -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-01 07:14 recovery -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-01 07:14 sdi -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 07:14 cust -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-01 07:14 cache -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-01 07:14 misc -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-01 07:14 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-01 07:14 userdata -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-01 07:14 grow -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-01 07:14 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 07:14 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 07:14 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 07:14 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 07:14 pad -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-01 07:14 oeminfo -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 07:14 modemst1 -> /dev/block/mmcblk0p9
And I already dd them out as backup, following is their dd out file size:
Code:
09/05/2014 01:01 PM 524,288 mmcblk0p1.img
09/05/2014 01:02 PM 4,194,304 mmcblk0p10.img
09/05/2014 01:02 PM 100,663,296 mmcblk0p11.img
09/05/2014 01:02 PM 4,194,304 mmcblk0p12.img
09/05/2014 01:03 PM 1,024 mmcblk0p13.img
09/05/2014 01:03 PM 8,192 mmcblk0p14.img
09/05/2014 01:03 PM 33,554,432 mmcblk0p15.img
09/05/2014 01:03 PM 67,108,864 mmcblk0p16.img
09/05/2014 01:03 PM 8,388,608 mmcblk0p17.img
09/05/2014 01:03 PM 12,582,912 mmcblk0p18.img
09/05/2014 01:03 PM 16,777,216 mmcblk0p19.img
09/05/2014 01:01 PM 32,768 mmcblk0p2.img
09/05/2014 01:04 PM 268,435,456 mmcblk0p20.img
09/05/2014 01:04 PM 201,326,592 mmcblk0p21.img
09/05/2014 01:05 PM 4,194,304 mmcblk0p22.img
09/05/2014 01:06 PM 1,073,741,824 mmcblk0p23.img
09/05/2014 02:34 PM 0 mmcblk0p24_toolarge.txt
09/05/2014 02:34 PM 0 mmcblk0p25_toolarge.txt
09/05/2014 01:01 PM 32,768 mmcblk0p3.img
09/05/2014 01:01 PM 512,000 mmcblk0p4.img
09/05/2014 01:01 PM 512,000 mmcblk0p5.img
09/05/2014 01:02 PM 5,726,208 mmcblk0p6.img
09/05/2014 01:02 PM 1,048,576 mmcblk0p7.img
09/05/2014 01:02 PM 67,108,864 mmcblk0p8.img
09/05/2014 01:02 PM 4,194,304 mmcblk0p9.img
09/05/2014 02:17 PM 4,194,304 mmcblk0rpmb.img
09/05/2014 02:34 PM 0 mmcblk1p1_toolarge_4GB.txt
So, maybe someone can help us build a recovery image? I like to learn, but really don't have much experience on these.
http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device
That might help you out if you haven't already looked into it.
Thanks, I will take a look that.
Right now, I am using their online builder:
http://builder.clockworkmod.com/
Still I am wondering, how that online builder (or the manual compile steps in your link) decide which partition is system/data/cache etc? Is that device-by-name is universal?
Also, is that safe to flash the recovery? if recovery image is bad, am I be able to boot normally to phone, and use adb to restore stock recovery?
Thanks.
Man, I wish I could help but I don't know anything about this.
If there's a CWM forum, try asking there. Hopefully we can find someone to help us.
xordos said:
Thanks, I will take a look that.
Right now, I am using their online builder:
http://builder.clockworkmod.com/
Still I am wondering, how that online builder (or the manual compile steps in your link) decide which partition is system/data/cache etc? Is that device-by-name is universal?
Also, is that safe to flash the recovery? if recovery image is bad, am I be able to boot normally to phone, and use adb to restore stock recovery?
Thanks.
Click to expand...
Click to collapse
I will answer my own question..
That online builder looks like is not working.
The build process will extract recovery.fstab from the the ramdisk image inside the recovery image.
The local build of the recovery did went through, but the whole process is so complex, and I have never done this before. I am pretty sure I will miss here and there. So my confident of the generated recovery.img is very low.
-rwxr--r-- 1 16777216 Sep 6 18:36 recovery_mmcblk0p19.img
-rw-r--r-- 1 8456192 Sep 6 21:53 recovery_new.img
Anyway, following command can flash the recovery easily.
Code:
fastboot.exe devices
fastboot.exe flash recovery recovery.img
The things is, with my recovery image flashed, it can't enter the recovery mode, following is detail:
1. "fastboot flash" to flash recovery.
2. hold 10 seconds to reboot ( or use fastboot reboot)
3. The phone will boot normally into android OS.
4. Then I shutdown the phone.
5. Before it completely shutdown, it showed Huawei logo once as usually, then it show the BootLoader screen. means the phone won't shut off completly.
(or In step 4. I use usb adb cmd "adb reboot recovery" it will same result in step 5)
If I flash back the original recovery in step 1, then in step 4, "adb reboot recovery" will easily reboot into recovery without hold any key. So keys holding is not a issue here.
So, I am not sure "always go into bootloader" means what, the recovery image is bad? or the phone has some checksum/sig check before it load recovery.
Anyway, I didn't try fastboot flash system, but looks like fastboot is one way to flash some partitions, following is the help:
Code:
...
flashall flash boot, system, and if found,
recovery, tos
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
.
I also searched some other Chinese varies Mate2 ROM, they are very differnt, the CPU is different, and the kernel command line (which is configured in the recovery partition) is quite different, so I doubt MT2_L03 can use recovery image from others like MT2_C00.
For ROM Developers, please see attachment for the device files.
I only updated BoardConfig.mk on those partition size. ( I double checked the size from /proc/partitions as well as the dd file size, they matching)
The recovery.fstab is original that extract from stock recovery image by the build tool automatically.
I am build on CM souce code branch 10.2.
Please let me know if you have any idea.
Without a working recovery to backup/restore, Having root on the phone is pretty dangerous. That's also the reason I am still not try xposed on my phone yet.
Hope we can have a working recovery soon.
Thanks.
I wouldn't bother with CWM.. Personal preference I guess. I would aim to build TWRP. Also, sync OmniRom. TWRP is officially located within the OmniRom source now.
http://docs.omnirom.org/Setting_Up_A_Compile_Environment
Can someone pull me their boot.img, recovery.img, build.prop and collect all of their "getprop" information. Zip it all up and throw it up on dev host or another cloud service. Would like to review.
hey, i am outside right now,will upload tonight
EDIT: @Modding.MyMind
uploaded....Here is the list of files in the zip:
09/05/2014 01:03 PM 12,582,912 boot_mmcblk0p18.img
09/07/2014 04:19 PM 13,109 build.prop
09/06/2014 02:17 AM 2,966 device_mount.txt
09/06/2014 02:18 AM 9,104 device_names.txt
09/07/2014 04:19 PM 20,936 getprop.txt
09/07/2014 04:14 PM 1,168 md5sum.txt
09/07/2014 04:18 PM 1,194 proc_partition.txt
09/06/2014 06:36 PM 16,777,216 recovery_mmcblk0p19.img
File location:
https://drive.google.com/file/d/0B-nJFDpWA4MdaWFEckVfUERSRk0/edit?usp=sharing
md5: c73da57ebc630a244ec86f15937251ea mt2_l03_upload.zip
Please let me know if you need anything else.
Thanks a lot.
You guys are simply amazing! :good:
Thanks, will be syncing OmniRom to my computer tomorrow after work. Meanwhile, will be looking over the contents inside the zip. Don't remove them on the cloud just yet lol. Won't be able to download it until tomorrow. I will let you know when that happens so if you wish to remove them later on you may.
@xordos and @ScoobSTi, can either of you confirm that you can currently install a recovery to your device now that ya'll are unlocked. Pull your stock recovery and in turn try to install that same recovery to see if the screen reports back successful.
yes, I already did that when i test my cwm recovery. The phone will boot normally into OS, so I dd out new partition image, and verified using bvi or other binary editor. Then i can restore stock recovery back. pls see post #6 for details.
xordos said:
yes, I already did that when i test my cwm recovery. The phone will boot normally into OS, so I dd out new partition image, and verified using bvi or other binary editor. Then i can restore stock recovery back. pls see post #6 for details.
Click to expand...
Click to collapse
Awesome, great news. Just wanted to verify so I had reassurance that if my first TWRP build is buggy you or another tester could get back to your stock recovery .
@xordos, Syncing OmniROm now. Downloaded your zip that you provided. Will begin my work.
Quick question, is the storage sdcard path located at /data/media, or no? Need to know. Reviewing the zip I got and it was giving me mixed feelings on that issue.
Almost done building the device configuration folder.
---------- Post added at 02:33 PM ---------- Previous post was at 02:32 PM ----------
Also, what is ya'lls device resolution? Need that as well lol.
Modding.MyMind said:
Quick question, is the storage sdcard path located at /data/media, or no? Need to know. Reviewing the zip I got and it was giving me mixed feelings on that issue.
Almost done building the device configuration folder.
---------- Post added at 02:33 PM ---------- Previous post was at 02:32 PM ----------
Also, what is ya'lls device resolution? Need that as well lol.
Click to expand...
Click to collapse
/storage/sdcard0 - I think
720x1280
aragon257 said:
/storage/sdcard0 - I think
720x1280
Click to expand...
Click to collapse
Thanks. Makes it easier for me.
---------- Post added at 02:54 PM ---------- Previous post was at 02:52 PM ----------
Is this device CDMA or GSM? Looking at it tells me it is GSM but wanted to verify with you guys.
---------- Post added at 03:00 PM ---------- Previous post was at 02:54 PM ----------
I'm also not seeing a partition for the internal sdcard. I have to assume it's fused with /data/media. Will hit up the build.prop to verify. It will tell me there. And I see there is an external sdcard as well (up to 64 gigs). Useful info for building.
---------- Post added at 03:02 PM ---------- Previous post was at 03:00 PM ----------
And I see it is CDMA with no SIM card according to the build.prop. Also, just so you guys know, the internal sdcard is in fact fused with /data/media.
Modding.MyMind said:
Thanks. Makes it easier for me.
---------- Post added at 02:54 PM ---------- Previous post was at 02:52 PM ----------
Is this device CDMA or GSM? Looking at it tells me it is GSM but wanted to verify with you guys.
---------- Post added at 03:00 PM ---------- Previous post was at 02:54 PM ----------
I'm also not seeing a partition for the internal sdcard. I have to assume it's fused with /data/media. Will hit up the build.prop to verify. It will tell me there. And I see there is an external sdcard as well (up to 64 gigs). Useful info for building.
---------- Post added at 03:02 PM ---------- Previous post was at 03:00 PM ----------
And I see it is CDMA with no SIM card according to the build.prop. Also, just so you guys know, the internal sdcard is in fact fused with /data/media.
Click to expand...
Click to collapse
It is GSM ..Also, very few 64GB microSD cards are compatible with this device. 32GB is preferred.
USHAM2 said:
It is GSM ..Also, very few 64GB microSD cards are compatible with this device. 32GB is preferred.
Click to expand...
Click to collapse
Thanks, knowing if it were GSM or CDMA was very important to me. I looked back at the build.prop and saw that is in fact GSM. Read the info wrong lol. It happens . Working to complete the device configuration before the syncing is complete so I can jump straight in to building TWRP for you guys.
Related
Hi,
I'm a bit of a noob when it comes to Linux but i'm trying to take the Chinese based firware for my device unpack it, modify it and re pack it to make a English starting vanilla build.
Let me begin, i've got a Ubuntu 12.04 install with ext4_utils. I've used a allwinner kitchen to extract the RFSFAT16_SYSTEM_000000000.fex file. I've used simg2img to convert it to original.img and then mounted it as tempdir.
I make changes and all seems ok.
the thing i'm struggling with now is once i've made changes to the output.img through the tempdir through nautilus i try to convert it back to sparse and the conversion completes BUT then when i re pack it into an image and flash the rom doesn't work and gets stuck on boot animation. If if leave the file as ext4 and repack it.. it loads fine but the system image is huge.
If i try to use ./mkuserimg.sh -s /home/Desktop/Android/ext4_utils ./Onda.img ext4 ./temp 512M it creates a .img file with a padlock on it.. (permissions). If i rename this to RFSFAT16_SYSTEM_000000000 and repack the root doesn't boot.
Ive followed this thread and whilst i can get it to work in ext4 i can't get it to work as sparse.
Any help please?
hi,
i have the same problem.
when i mount the repacked image.
original:
drwxr-xr-x 2 root 2000 4096 2012-02-23 09:20 .
drwxr-xr-x 14 root root 4096 1970-01-01 01:00 ..
-rwxr-xr-x 1 root 2000 97144 2012-02-23 09:15 adb
-rwxr-xr-x 1 root 2000 191 2012-02-23 09:02 am
-rwxr-xr-x 1 root 2000 50056 2012-02-23 09:15 applypatch
-rwxr-xr-x 1 root 2000 165772 2012-02-23 09:15 applypatch_static
-rwxr-xr-x 1 root 2000 9920 2012-02-23 09:17 app_process
mount after repack (sparse)
drwxr-xr-x 2 root root 4096 2012-02-23 09:20 .
drwxr-xr-x 14 root root 4096 1970-01-01 01:00 ..
-rw-r--r-- 1 root root 97144 2012-02-23 09:15 adb
-rw-r--r-- 1 root root 191 2012-02-23 09:02 am
-rw-r--r-- 1 root root 50056 2012-02-23 09:15 applypatch
-rw-r--r-- 1 root root 165772 2012-02-23 09:15 applypatch_static
-rw-r--r-- 1 root root 9920 2012-02-23 09:17 app_process
onyone a clue?
Hello
Would you give me a block file of DROID DNA?
I want the following files.
/dev/block/mmcblk0p11
/dev/block/mmcblk0p12
/dev/block/mmcblk0p13
/dev/block/mmcblk0p14
/dev/block/mmcblk0p15
/dev/block/mmcblk0p17
/dev/block/mmcblk0p18
/dev/block/mmcblk0p19
/dev/block/mmcblk0p20
/dev/block/mmcblk0p21
/dev/block/mmcblk0p22
/dev/block/mmcblk0p23
/dev/block/mmcblk0p24
/dev/block/mmcblk0p25
/dev/block/mmcblk0p26
/dev/block/mmcblk0p27
/dev/block/mmcblk0p28
/dev/block/mmcblk0p29
/dev/block/mmcblk0p30
The extracting methods are as follows.
adb shell
$ su
# dd if=/dev/block/mmcblk0p** of=/sdcard/p**
There is p** file in Internal Storage.
Sorry for asking too much...
Ill pull this for you when I get home if nobody else has.
Uploading now, 48.26MB.
sent via electromagnetic radiation.
---------- Post added at 08:57 PM ---------- Previous post was at 08:54 PM ----------
PM sent with link.
sent via electromagnetic radiation.
---------- Post added at 08:58 PM ---------- Previous post was at 08:57 PM ----------
http://db.tt/qex4bZ5I
sent via electromagnetic radiation.
Electromagnetic radiation!?!?
Time to pull out my tinfoil hat.
Correct. RF is a form EM radiation.
sent via electromagnetic radiation.
ibsk8 said:
Correct. RF is a form EM radiation.
sent via electromagnetic radiation.
Click to expand...
Click to collapse
Those are initials for secret government agencies?
Roger Fudd (offspring or Roger Rabbit and Elmer Fudd)?
Just having fun, it' Sadurday night!
Forgive my ignorance on this but what r the block files? something vzw related? So I can learn something new 2day
Sent from my HTC6435LVW using Xparent BlueTapatalk 2
ibsk8 said:
Uploading now, 48.26MB.
sent via electromagnetic radiation.
---------- Post added at 08:57 PM ---------- Previous post was at 08:54 PM ----------
PM sent with link.
sent via electromagnetic radiation.
---------- Post added at 08:58 PM ---------- Previous post was at 08:57 PM ----------
http://db.tt/qex4bZ5I
sent via electromagnetic radiation.
Click to expand...
Click to collapse
very thanks!!!
I can't thank you enough!
This partition apparently holds the IMEI (well on the Moto G 2013 it does) but I don't even see that it exists on this phone (xt1527). I can't seem to make a backup of it but the phone works so, is it even there or have they changed how it works?
bump, same issue
seems a bunch of us have this issue.
sad there seems to be no answer anywhere..
edit:
here is what i got listing partitions.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
[email protected]_umts:/ $ su
[email protected]_umts:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name/
lrwxrwxrwx root root 1970-06-10 11:47 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-06-10 11:47 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-06-10 11:47 abootBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-06-10 11:47 boot -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-06-10 11:47 cache -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-06-10 11:47 carrier -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-06-10 11:47 cid -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-06-10 11:47 clogo -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-06-10 11:47 dhob -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-06-10 11:47 factorytune1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-06-10 11:47 factorytune2 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-06-10 11:47 frp -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-06-10 11:47 fsc -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-06-10 11:47 fsg -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-06-10 11:47 hob -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-06-10 11:47 hyp -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-06-10 11:47 hypBackup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-06-10 11:47 keystore -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-06-10 11:47 kpan -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-06-10 11:47 logo -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-06-10 11:47 logs -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-06-10 11:47 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-06-10 11:47 misc -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-06-10 11:47 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-06-10 11:47 modemst1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-06-10 11:47 modemst2 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-06-10 11:47 oem -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-06-10 11:47 padA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-06-10 11:47 padB -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-06-10 11:47 padC -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-06-10 11:47 persist -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-06-10 11:47 recovery -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-06-10 11:47 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-06-10 11:47 rpmBackup -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-06-10 11:47 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-06-10 11:47 sec -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-06-10 11:47 sp -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-06-10 11:47 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-06-10 11:47 system -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-06-10 11:47 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-06-10 11:47 tzBackup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-06-10 11:47 userdata -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-06-10 11:47 utags -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-06-10 11:47 utagsBackup -> /dev/block/mmcblk0p17
[email protected]_umts:/ #
Not up to speed on this device yet but it seems to me that if you know where the PDS partition is from a terminal you should be able to use a form like:
dd if=/dev/block/mmcblk??? of=pds.img
provided your current working directory has enough room in it to hold the .img file
conductive said:
Not up to speed on this device yet but it seems to me that if you know where the PDS partition is from a terminal you should be able to use a form like:
dd if=/dev/block/mmcblk??? of=pds.img
provided your current working directory has enough room in it to hold the .img file
Click to expand...
Click to collapse
on another phone it's mmcblk12 (i have been doing a LOT of searching on this)
i looked at the root folder on my phone and i see a shortcut to "pds"
when i open it it's empty.
i have some experience with Linux but i am no pro and it's been a while for my nix activity.
and i have almost no experience with Android.
i am good with computer stuff though. cracking, coding reversing, graphics etc.
i love modding everything i can.
i say that to give a bit of context to this..
if anyone else has any idea or leads on what i can do or where to look i am all ears.
i posted that partition command because i found it on Google
and i remember using it (ls) before trouble shooting driver issues on Linux in the past.
you guys will notice the console log i posted does not list a pds partition by-name..
is it because it's not mounted maybe ? or is it using a different name on this phone ?
i'd love to try and update to 5.1 (from 5.0..2) on my Telus XT1527 but i think it's time i make a PDS backup before i carry on any further.. so far i have installed a custom kernel and TWRP + root.
So i can't continue until i figure out a way to back that stuff up (irresponsible otherwise i think)
Based on this post http://forum.xda-developers.com/showthread.php?t=1138220 the OS uses /dev/block/mmcblk0p3 and it was dumped to the /tmp directory.
from here you can use dd to flash it to an sd card where you can read it to see if it has pds information. You can also use (mount -a) to mount all partitions and do another ls -l
conductive said:
Based on this post http://forum.xda-developers.com/showthread.php?t=1138220 the OS uses /dev/block/mmcblk0p3 and it was dumped to the /tmp directory.
from here you can use dd to flash it to an sd card where you can read it to see if it has pds information. You can also use (mount -a) to mount all partitions and do another ls -l
Click to expand...
Click to collapse
That says Atrix though and on another posting i found it was mmcblk0p12
If you look at the log i posted earlier that number mmcblk0p3 is mapped to DDR
I have been dumping the partitions and checking them (if the file size is roughly correct)
I heard it was suppose to be about 8mb as an .img on another device.
and i have one downloaded as an image and extracted (some other guys data)
so if i find the files on my phone i think i can match them to my downloaded files.
i also got a windows tool to extract the images ready..
One last thing i said i seen a shortcut to "pds" on the filesystem of my Telus XT1527
so i take it that it's there just that i can't see it or something.
I'm basically poking around in the dark LOL
edit:
oh and i seen on other phones that pds partition can be backed up with TWRP.
The TWRP i have installed does not show it for me (i am using Squid's TWRP)
The partitions are probably associated with the OS version and not the hardware so you should probably compare your version to a similar version.
If you can find fstab file you should be able to (cat fstab) and see what the partitions are mounted as.
The partition should be mounted or else your device will not work.
I've modded fstab on linux before but i am not finding it i think on the XT1527
found a couple with "fstab" in the title and it don't say much..
just one line about mounting the sdcard.
Thanks but i am lost.. i wonder how it's created because it's prob not files in the Firmware package right ?
So then i'd have to assume the contents of PDS would be created on the phones first boot maybe.
i don't know what else to do really i am going around in circles ..i might just say screw it and give up.
too bad guys here who DO have the ability to find it can't help
100% of Moto-E users seem to carry on flashing their phones with out it
so i take it backing up the PDS is pointless ?
Just kind of dumb i see tutorials on how to do it all over but no one can claim it actually works LOL
If you google it you will see what i am saying (people tell you to you to do it becuase it's sooooo important..
then it doesn't work ahahaha
thanks for your help conductive.
edit:
Oh and guys.. i tried to do this because... Q13:
http://forum.xda-developers.com/moto-e-2015/help/faq-frequently-questions-moto-e-2015-t3044929
The stickied topic here tells us all how to do it.
..but did anyone at all bother to verify it actually works ?
Ok so i think i got it.. sort of.
I installed "Root Explorer Pro" and when i opened it this time it showed files/folders.
I then selected .zip it up and copied it manually to my sdcard then to my PC.
I have been hex viewing the contents with UltraEdit and the files contain data.
I also compared to a pds dump from an Atrix and they are some what similar.
I did see a reference in one of the root config files about the pds partition though..
I can't recall which file it was but it said something about
setting the dummy directory "pds" as persistent.
I don't know what is going on but i got the content off the phone i think.
edit:
Here is what the root of that folder looked like (folder names)
Code:
.bt_nv.bin
batt_health
bt
camera
data
factory
lost+found
public
security
WCNSS_wlan_dictionary.dat
wifi
wmdrm
STOCK FIRMWARE FOR E2303 FLASHABLE ZIP
UPDATE: Uploading because this time IT WORK! Thanks to @TheVektor for updater-script! But this isn't pre-rooted, because it not flash SuperSU. But it's still awesome because if you have problems with flashmode or other you can flash this as a recovery zip! Tested on E2303 with TWRP. Made with PRFCreator
alby_var said:
STOCK PRE-ROOTED FIRMWARE FOR E2303 FLASHABLE ZIP
Hey guys! I had a problem entering flashmode and the only way for unbrick my phone was enter into recovery/flash a zip or fastboot flash.
For this, i made a pre-rooted firmware with PRFcreator. Now I am testing it. It will not install a recovery because xzdualrecovery is not compatible with our device. That means you have to flash it manually before start installing this.
STATUS: RECOVERY NOT INSTALL ZIP FILE....
Download: testing and uploading...
Click to expand...
Click to collapse
Hey! I'm interested in this ROM, my device has a locked bootloader and I think this would solve out the issue of rooting without unlocking the bootloader. I can test the ROM. My model is: E2306
Do you have any finished projects?
Quien mucho abarca poco aprieta
rascayus said:
Quien mucho abarca poco aprieta
Click to expand...
Click to collapse
English please
Don'te bite more than you can chew
I think every thread you have created is pointless. "Uploading"... yeah great.
Maybe get something uploaded first, then create a thread instead of having multiple threads that are pointless...
I respect your efforts but still
Guys, the rom are completed, the problem is that we haven't a working updater-script file. It is needed for flash roms, and I am working to make one that work. I can upload the rom and give you the link, but if it not flash, where is the sense in that?
Code:
if
run_program("/tmp/busybox", "ls", "/dev/block/platform/msm_sdcc.1/by-uuid/F9CDF7BA-B834-A72A-F1C9-D6E0C0983896") != "0"
then
abort("Error: UUID link to system partition does not exist");
endif;
assert(package_extract_file("system.ext4", "/dev/block/platform/msm_sdcc.1/by-uuid/F9CDF7BA-B834-A72A-F1C9-D6E0C0983896"));
M4 Aqua (E2303) does not have "msm_sdcc.1" and "by-uuid" folders or whatever is it....
We have MMC device partitions:
Code:
lrwxrwxrwx root root 1970-02-06 11:48 DDR -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-02-06 11:48 FOTAKernel -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-02-06 11:48 LTALabel -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-02-06 11:48 TA -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-02-06 11:48 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-02-06 11:48 alt_aboot -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-02-06 11:48 alt_hyp -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-02-06 11:48 alt_rpm -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-02-06 11:48 alt_s1sbl -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-02-06 11:48 alt_sbl1 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-02-06 11:48 alt_tz -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-02-06 11:48 apps_log -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-02-06 11:48 boot -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-02-06 11:48 cache -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-02-06 11:48 config -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-02-06 11:48 fsg -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-02-06 11:48 hyp -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-02-06 11:48 modem -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-02-06 11:48 modemst1 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-02-06 11:48 modemst2 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-02-06 11:48 oem -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-02-06 11:48 persist -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-02-06 11:48 rdimage -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-02-06 11:48 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-02-06 11:48 s1sbl -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-02-06 11:48 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-02-06 11:48 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-02-06 11:48 system -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-02-06 11:48 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-02-06 11:48 userdata -> /dev/block/mmcblk0p29
So we need create updater-script using similar formats:
Code:
run_program("/tmp/busybox", "ls", "/dev/block/mmcblk0p30") != "0"
AND
assert(package_extract_file("system.ext4", "/dev/block/mmcblk0p30"));
Im not 100% sure this is the problem, but i hope it can help for you.
Edit:
OK! zip flashing finished (system flashed!), but supersu not installed by updater-script... idk why.
My updater-script: http://pastebin.com/8Lg7UseV
Ohh! Really Really Really thank you!! Now i can unbrick my phone and finally complete the roms!
alby_var said:
STOCK FIRMWARE FOR E2303 FLASHABLE ZIP
UPDATE: Uploading because this time IT WORK! Thanks to @TheVektor for updater-script! But this isn't pre-rooted, because it not flash SuperSU. But it's still awesome because if you have problems with flashmode or other you can flash this as a recovery zip! Tested on E2303 with TWRP. Made with PRFCreator
Click to expand...
Click to collapse
Its flashable zip too... not important pre-rooted or not after flashing is done, simple you can install supersu.zip too. :good:
But You try to build pre rooted Rom?
Wysłane z mojego E2303 przy użyciu Tapatalka
Later I will try to make a flashable working prerooted, tomorrow i will upload it ( i tried today but still at 60% uploading) but for now I will complete de-bloated and other projects....
Ok, I uploaded to Mediafire but it not give me the link.... I am uploading again to Mega and its at 30%
alby_var said:
Ok, I uploaded to Mediafire but it not give me the link.... I am uploading again to Mega and its at 30%
Click to expand...
Click to collapse
And ?? Can you upload pre rooted Rom ?
I not successfully can upload it. All hosting websites stop uploading or still for 2-3 days and i have to shut down pc.
Upload it to google drive and share link,ty
Stock firmware for e2303 flashable zip
Link?
26.1.a.2.167/r12a
Can someone explain what means R12A in 26.1.A.2.167/R12A ?
so, does anybody have this flashable stock rom? I could really use it right now...
Hey, so I got the new Gionee M6S Plus from China and was having problems trying to use Google Play (downloaded by apk). I also downloaded the Google Play Services apk and ran that (if I didn't, Google Play wouldn't even open). But whenever I try to open Google Play, it only shows the white loading screen and seems to "freeze" on the white screen. Also, I keep getting errors messages about "Google Play Services has stopped" messages and was wondering if that was related.
Thanks
WhyChineseAndroidWhy said:
Hey, so I got the new Gionee M6S Plus from China and was having problems trying to use Google Play (downloaded by apk). I also downloaded the Google Play Services apk and ran that (if I didn't, Google Play wouldn't even open). But whenever I try to open Google Play, it only shows the white loading screen and seems to "freeze" on the white screen. Also, I keep getting errors messages about "Google Play Services has stopped" messages and was wondering if that was related.
Thanks
Click to expand...
Click to collapse
U will need to install cwm and flash gapps according to ur Android version
Sent from my ONE A2005 using Tapatalk
Brandon Indar said:
U will need to install cwm and flash gapps according to ur Android version
when you say android version, does this mean like Android 6.0 or the Amigos 3.5 firmware its running?
Thanks
Click to expand...
Click to collapse
WhyChineseAndroidWhy said:
Brandon Indar said:
U will need to install cwm and flash gapps according to ur Android version
when you say android version, does this mean like Android 6.0 or the Amigos 3.5 firmware its running?
Thanks
Click to expand...
Click to collapse
Android 6.0
Sent from my ONE A2005 using Tapatalk
Click to expand...
Click to collapse
Brandon Indar said:
WhyChineseAndroidWhy said:
Android 6.0
Sent from my ONE A2005 using Tapatalk
Click to expand...
Click to collapse
This made be a dumb question, but what is cwm? and where can I find resources on cwm and flash gapps for Android 6.0? Also does this require root?
Thanks
Click to expand...
Click to collapse
Gionee M6S Plus -Need help in installing google apps
Hi ,
I am also facing the same problem . I also have bought Chinese version gionee m6s plus and want to install gapps. I have also tried installing apks like service framework,account manager,play store but in vain and it crashes every time I open . I want to root this phone only to install gapps. Can any one please post the link or help as how to root this version of phone ?
Thanks
Hi just send me ur recovery and boot.img I can port cwm recovery so u guys can flash gapps.
Sent from my ONE A2005 using Tapatalk
Brandon Indar said:
Hi just send me ur recovery and boot.img I can port cwm recovery so u guys can flash gapps.
Sent from my ONE A2005 using Tapatalk
Click to expand...
Click to collapse
Hi Brandaon thanks for your reply.I am a noob in this and need further help. I used following link https://forum.xda-developers.com/showthread.php?t=2027311 to get recovery image.However I am getting error when I run the command
cat proc/mtd
/system/bin/sh: cat: proc/mtd: No such file or directory
Suhi02 said:
Hi Brandaon thanks for your reply.I am a noob in this and need further help. I used following link https://forum.xda-developers.com/showthread.php?t=2027311 to get recovery image.However I am getting error when I run the command
cat proc/mtd
/system/bin/sh: cat: proc/mtd: No such file or directory
Click to expand...
Click to collapse
U can Google ur device and see if there is a stock frimware and send me a link.
Sent from my ONE A2005 using Tapatalk
Hi I found following link
Its not allowing to post the link URL hence typing in below format
https front slash www dot amigo dot cn front slash mobile.php?id=83&mobile=1
It is 64 gb rom black color phone. With the help of google translator I can see it says Download and brush tutorials. My device is running on marshmallow 6.0.1, Amigo version 3.5.3 ,secure version 1.2.a. Does this help you ?
Thanks
Boot Image for M6S PLUS
Brandon Indar said:
Hi just send me ur recovery and boot.img I can port cwm recovery so u guys can flash gapps.
Sent from my ONE A2005 using Tapatalk
Click to expand...
Click to collapse
HI I have attached boot.img file. However I couldn't get recovery img file yet.
Thanks
Suhi02 said:
HI I have attached boot.img file. However I couldn't get recovery img file yet.
Thanks
Click to expand...
Click to collapse
I will need recovery.img too because i will need to post cwm recovery so u can flash the super su zip and get root.
See if u can get ur device firmware online and send me link
Thanks
Brandon Indar said:
I will need recovery.img too because i will need to post cwm recovery so u can flash the super su zip and get root.
See if u can get ur device firmware online and send me link
Thanks
Click to expand...
Click to collapse
Hi , please find following link. It says 2.3GB as size. Is this what is required ?
https://www.amigo.cn/mobile.php?id=83&mobile=1
Thanks a lot
Brandon Indar said:
I will need recovery.img too because i will need to post cwm recovery so u can flash the super su zip and get root.
See if u can get ur device firmware online and send me link
Thanks
Click to expand...
Click to collapse
Hi just like miracle box which is for mediatek devices ,Do we have any such software for snapdragon devices , so that I can read and extract boot image and recovery image without root ?
Thanks
Please help to get recovery file on PC or access it
Brandon Indar said:
I will need recovery.img too because i will need to post cwm recovery so u can flash the super su zip and get root.
See if u can get ur device firmware online and send me link
Thanks
Click to expand...
Click to collapse
HI I am able to get root access from kingroot. But it says it is temporary and after restart will loose the root. I was able to get image file . However I cannot access those files
127|[email protected]_G1602A:/storage/emulated/0 # ls
lmms
qmt
qqsecure
qt
recovery.img
I have extracted recovery image file this is the recovery.img file using dd if=/dev/block/mmcblk0p22 of=/sdcard/recovery.img. However I cannot copy to my pc and sdcard. It is not visible via explorer too. But the file is there. Can you please help me . I tried adb pull /Sdcard/ but it says adb not found. Please help. Thanks
Which files should I extract for boot and recovery image ?
HI ,
I have following thing. Thanks in advance.I have temporarily got root access till i restart my device via kingroot. If not can you please tell me step by step , so that I can sideload gapps and set permissions using root explorer to google play store and other files ? If I give permissions and restart my device will I be able to boot up properly or get stuck ?Because it has locked bootloader and any changes it finds I think it reverts to original stock rom Thanks in advance
Please let me know which one should I extract from the below list? There are 2 files aboot which is of 10 MB and other boot is 65MB. Recovery file also seems to be of 65MB.
lrwxrwxrwx root root 1970-06-06 11:56 DDR -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-06-06 11:56 aboot -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-06-06 11:56 abootbak -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-06-06 11:56 apdp -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-06-06 11:56 boot -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-06-06 11:56 cache -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-06-06 11:56 cmnlib -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-06-06 11:56 cmnlib64 -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-06-06 11:56 cmnlib64bak -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-06-06 11:56 cmnlibbak -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-06-06 11:56 config -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-06-06 11:56 devcfg -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-06-06 11:56 devcfgbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-06-06 11:56 devinfo -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-06-06 11:56 dip -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-06-06 11:56 dpo -> /dev/block/mmcblk0p45
lrwxrwxrwx root root 1970-06-06 11:56 dsp -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-06-06 11:56 fsc -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-06-06 11:56 fsg -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-06-06 11:56 keymaster -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-06-06 11:56 keymasterbak -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-06-06 11:56 keystore -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-06-06 11:56 limits -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-06-06 11:56 mcfg -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-06-06 11:56 mdtp -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-06-06 11:56 misc -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-06-06 11:56 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-06-06 11:56 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-06-06 11:56 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-06-06 11:56 mota -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-06-06 11:56 msadp -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-06-06 11:56 oem -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-06-06 11:56 persist -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-06-06 11:56 recovery -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-06-06 11:56 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-06-06 11:56 rpmbak -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-06-06 11:56 sbl1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-06-06 11:56 sbl1bak -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-06-06 11:56 sec -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-06-06 11:56 splash -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-06-06 11:56 ssd -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-06-06 11:56 syscfg -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-06-06 11:56 system -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-06-06 11:56 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-06-06 11:56 tzbak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-06-06 11:56 userdata -> /dev/block/mmcblk0p46
Boot and recovery file
Brandon Indar said:
Hi just send me ur recovery and boot.img I can port cwm recovery so u guys can flash gapps.
Sent from my ONE A2005 using Tapatalk
Click to expand...
Click to collapse
Hi ,
After phone got restarted root was lost. My bootloader is still in unlocked state.
Please find recovery image and boot image link. Please help me to install google apps.
Recovery image URL = https://ufile.io/y88gt
Boot image URL = https://ufile.io/sk85f
Kindly do the needful.
Thanks
Hi, It seems my bootloader is unlocked .I tried fastboot oem unlock-go
c:\adb>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.000s]
finished. total time: 0.000s
I have attached boot image and recovery file image in the previous post
Recovery image URL = https://ufile.io/y88gt
Boot image URL = https://ufile.io/sk85f
Please help me to install google apps. Thanks