Related
I flashed a I9100 firmware on my I9100M on bell and now I don't have the M on the bootlogo anymore. Also, the bell stock download mode start directly to downloading, but now it ask for downloading or cancel with volume up/down.
Does anybody have a way to fix this (like have the original boot.bin, sbl.bin and param.lfs from bell firmware I9100MUGKG2) because I downloaded the original firmware and these files are not included.
If you have a rooted I9100M running stock firmware, use this step and upload me the file please:
adb shell
$ su
# dd if=/dev/block/stl6 of=/sdcard/param.lfs bs=4096
or you can use terminal emulator if you prefer (remove adb shell).
The param.lfs will be in your internal sd card.
But if you have all the file I ask (if you did a nandroid backup with CWM before upgrading or modding the phone), please upload for me.
I need warranty and now my phone isn't stock.
Thankx
Download full stock rom from Samfirmware.com & extract the files yourself.
NLSGS2beast said:
I flashed a I9100 firmware on my I9100M on bell and now I don't have the M on the bootlogo anymore. Also, the bell stock download mode start directly to downloading, but now it ask for downloading or cancel with volume up/down.
Does anybody have a way to fix this (like have the original boot.bin, sbl.bin and param.lfs from bell firmware I9100MUGKG2) because I downloaded the original firmware and these files are not included.
If you have a rooted I9100M running stock firmware, use this step and upload me the file please:
adb shell
$ su
# dd if=/dev/block/stl6 of=/sdcard/param.lfs bs=4096
or you can use terminal emulator if you prefer (remove adb shell).
The param.lfs will be in your internal sd card.
But if you have all the file I ask (if you did a nandroid backup with CWM before upgrading or modding the phone), please upload for me.
I need warranty and now my phone isn't stock.
Thankx
Click to expand...
Click to collapse
I too have a simular problem, I dont need to send it in for warranty but am wanting to get the Sbl.bin file and param.lfs for Bell Canada's GT-i9100M phone, I downloaded the old GB KG2 FM and also have the new ICS LD3 FM and none contain the Sbl.bin file or the param.lfs that Bell uses.
I have access to another i9100M that has not been changed with anything custom, does anyone know of a way that I can get the Sbl.bin data and how to get the param.lfs off of another phone?.
Thank you.
OK I think I figured this out, I found out the partitions to backup by listing them by name
Code:
[email protected]:/sdcard # ls -l /dev/block/platform/dw_mmc/by-name/
lrwxrwxrwx 1 root root 20 May 12 21:24 CACHE -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 May 12 21:24 DATAFS -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 May 12 21:24 EFS -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 May 12 21:24 FACTORYFS -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 May 12 21:24 HIDDEN -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 May 12 21:24 KERNEL -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 May 12 21:24 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 May 12 21:24 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 May 12 21:24 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 May 12 21:24 UMS -> /dev/block/mmcblk0p11
Then I just did a dd on partitions 2 and 3 I didn't do the param because I have modified my boot logo and know enough from changing it before Hellcats easy app to know it is not specific to the phone since it has all variant logos at the same time and it shows the correct one by file name.
shadowofdarkness said:
OK I think I figured this out, I found out the partitions to backup by listing them by name
Code:
[email protected]:/sdcard # ls -l /dev/block/platform/dw_mmc/by-name/
lrwxrwxrwx 1 root root 20 May 12 21:24 CACHE -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 May 12 21:24 DATAFS -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 May 12 21:24 EFS -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 May 12 21:24 FACTORYFS -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 May 12 21:24 HIDDEN -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 May 12 21:24 KERNEL -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 May 12 21:24 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 May 12 21:24 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 May 12 21:24 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 May 12 21:24 UMS -> /dev/block/mmcblk0p11
Then I just did a dd on partitions 2 and 3 I didn't do the param because I have modified my boot logo and know enough from changing it before Hellcats easy app to know it is not specific to the phone since it has all variant logos at the same time and it shows the correct one by file name.
Click to expand...
Click to collapse
Lol I was on the toliet and found the directory too, I already found out that the MMCBLK's where the data to dump and was cross refernceing from PIT file information, but then low and behold looking by name confirmed for sure which one, however how did you extract the exact data from those mmcblocks? , when I do a data partition dump, it dumps the whole partition so for example the param.lfs partition is 8MBs, how were you able to access the specific data and convert it/get it out of those blocks?, I will need to repeat this process on my family members phone so that I can get the param file, also how did you tar them up so that they are Odin flash-able?.
Also will it be fine to flash both sbl 1 and 2 bins just as they are and will Odin properly flash them in the correct sections? or should I just use sbl1 to be safe and rename it to sbl.bin ?(since that is how it comes in firmware packages etc)
In my picture here I was using Yaffs Explorer app but the options are very limiting.
dbzgod said:
Lol I was on the toliet and found the directory too, I already found out that the MMCBLK's where the data to dump and was cross refernceing from PIT file information, but then low and behold looking by name confirmed for sure which one, however how did you extract the exact data from those mmcblocks? , when I do a data partition dump, it dumps the whole partition so for example the param.lfs partition is 8MBs, how were you able to access the specific data and convert it/get it out of those blocks?, I will need to repeat this process on my family members phone so that I can get the param file, also how did you tar them up so that they are Odin flash-able?.
Also will it be fine to flash both sbl 1 and 2 bins just as they are and will Odin properly flash them in the correct sections? or should I just use sbl1 to be safe and rename it to sbl.bin ?(since that is how it comes in firmware packages etc)
In my picture here I was using Yaffs Explorer app but the options are very limiting.
Click to expand...
Click to collapse
I didn't do anything special and those should be entire partition images. I doubt that tar is Odin flashable since the filenames will be off. I just put them in a tar.bz2 by right clicking the files on my Desktop and selecting compress since xda wouldn't allow me to attach bin files
shadowofdarkness said:
I didn't do anything special and those should be entire partition images. I doubt that tar is Odin flashable since the filenames will be off. I just put them in a tar.bz2 by right clicking the files on my Desktop and selecting compress since xda wouldn't allow me to attach bin files
Click to expand...
Click to collapse
Ah okay, yeah thats what I was able to do as well just got copys of the partitions from 2 ways, one was using the partition raw dump that makes a .raw file from within Yaffs Explorer, and the second was just using the shell cmds
dd if=/dev/block/mmcblk0p4 of=/sdcard/param.lfs
dd if=/dev/block/mmcblk0p2 of=/sdcard/Sb1l.bin
dd if=/dev/block/mmcblk0p3 of=/sdcard/Sbl2.bin
So now im thinking that they probably arnt Odin flash-able and what I will half to do is just:
dd if=/sdcard/param.lfs of=/dev/block/mmcblk0p4 to copy them over? or would that be bad/corrupt the the mmc partitions?
The raw data dumps from Yaffs Explorer makes them just to be their names mmcblk0p4.raw so would it be better to just use those raw dumps instead when copying over to the dev/block section?
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...
Is there already a way to root the CAT S40?
yes
Important Update:
A few months after using this method, I realise that now system updates fail on my phone.
I managed to unroot the phone using supersu, but no luck, updates still fail...
If I manage to bypass this, I will update this post, but so far, no luck...
#######################################################
RAFd3v said:
Is there already a way to root the CAT S40?
Click to expand...
Click to collapse
Got root yesterday, but not sure how safe method is...
Steps performed:
- I first downloaded KingRoot-4.1.0.245.apk from an untrusted source that I can't remember I still have the file though, and could share it if needed, but again, I don't really trust it - I just hope there's no malware.
md5 of the file is 8b411efbf70b8d7f70d12bb4984775e2
- Once succesfully rooted with Kingroot, I Installed "supersu me" from playstore and used it to replace kingroot with supersu
https://play.google.com/store/apps/details?id=darkslide.com.supersumepro&hl=en
This seems to have removed all the chinese bloatware installed by KingRoot... but here again, I can't know for sure...
root access remains after reboot, titanium backup allowed me to remove some apps (like the cat ones) so it seems to work fine.
nandroid backup seemed to backup things correctly, but the recovery.img with a size of 8192 leaves me dubious....
So far I was unable to find any custom recovery for the CAT S40 though... I guess that should be the next step before starting to try to find custom roms... ^^
Any clue about safety of the method I used, custom recovery or custom roms for S40 would be welcome
edit:
When searching manually, I believe I got a better recovery dump;
JuPiTeR ~ # adb shell
[email protected]:/ $ su
[email protected]:/ # ls -al /dev/block/platform/7824900.sdhci/by-name/
lrwxrwxrwx root root 1970-04-29 16:19 DDR -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-04-29 16:19 aboot -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-04-29 16:19 abootbak -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-04-29 16:19 boot -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-04-29 16:19 cache -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-04-29 16:19 config -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-04-29 16:19 devinfo -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-04-29 16:19 fsc -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-04-29 16:19 fsg -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-04-29 16:19 keystore -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-04-29 16:19 misc -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-04-29 16:19 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-04-29 16:19 modemst1 -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-04-29 16:19 modemst2 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-04-29 16:19 oem -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-04-29 16:19 pad -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-04-29 16:19 persist -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-04-29 16:19 persistbak -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-04-29 16:19 recovery -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-04-29 16:19 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-04-29 16:19 rpmbak -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-04-29 16:19 rsv -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-04-29 16:19 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-04-29 16:19 sbl1bak -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-04-29 16:19 sec -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-04-29 16:19 splash -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-04-29 16:19 ssd -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-04-29 16:19 system -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-04-29 16:19 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-04-29 16:19 tzbak -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-04-29 16:19 userdata -> /dev/block/mmcblk0p31
dd if=/dev/block/mmcblk0p27 of=/storage/sdcard1/recovery_backup.img
65536+0 records in
65536+0 records out
33554432 bytes transferred in 16.404 secs (2045503 bytes/sec)
I couldn't mount the file, but it seems to open correctly with hexedit:
[email protected]
console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboo
t.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=
3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled
=1 earlyprintk..................................................
..... then unreadable
Anyway, I feel more confident with a 32Mb recovery dump than with the previous 6k
I have success root my cat s40 with kingroot but i wanted change root app to SuperSU and phone had software brick :/
Is any method to reset this phone without warrianty? ( i have now on warrianty sent this phone)
Is any program from CAT for recover ROM? e.g. for samsung odin?
And where can download roms for this phone?
No clue about roms or recoveries so far... I got root with the method described, but again, not sure how safe.
How did you brick it? did you do as indicated in post or did you try manually?
someone has problems with the touch?
Wirusx said:
I have success root my cat s40 with kingroot but i wanted change root app to SuperSU and phone had software brick :/
Is any method to reset this phone without warrianty? ( i have now on warrianty sent this phone)
Is any program from CAT for recover ROM? e.g. for samsung odin?
And where can download roms for this phone?
Click to expand...
Click to collapse
Do you think this (brick) also happens when i use:
-NewKingRoot (uptodate)
after that
-SuperSume Pro.
jeroensky said:
Do you think this (brick) also happens when i use:
-NewKingRoot (uptodate)
after that
-SuperSume Pro.
Click to expand...
Click to collapse
i know kingroot working good on this phone but
SuperSU bricked my Cat S40
Now i use galaxy s6 Duos.
i recommended DON'T USE SuperSume App if you want change KingRoot to SuperSU = brick s40.
if you want try you must know
s40 + brick = send for warrianty
Samsung phones + brick = samart switch or odin
Problem isn't program for change to SuperSU but SuperSU.
When i used on my galaxy s6 SuperSU root via TWRP without custom boot.img (lollipop 5.1.1)
I had too brick for using SuperSU on lollipop 5.1.1 must be boot.img MOD but i don't know what. when i used custom kernel with supersu my phone normal boot but zelf rooted = brick this is too in s40.
when you find problem 5.1.1 lollipop + supersu i think you can slove problem with SuperSU on s40.
I don't found this slove to SuperSU i used custom boot.img with my zelfcompiled kernel.
when you find slove to this problem met SuperSU + boot.img write here i want too know what is problem met boot.img in lollipop 5.1.1 met SuperSU
Wirusx said:
i know kingroot working good on this phone but
SuperSU bricked my Cat S40
Now i use galaxy s6 Duos.
i recommended DON'T try change KingRoot if you have SuperSU = brick s40.
if you want try you must know
s40 + brick = send for warrianty
Samsung phones + brick = samart switch or odin
Problem isn't program for change to SuperSU but SuperSU.
When i used on my galaxy s6 SuperSU root via TWRP without custom boot.img (lollipop 5.1.1)
I had too brick for using SuperSU on lollipop 5.1.1 must be boot.img MOD but i don't know what. when i used custom kernel with supersu my phone normal boot but zelf rooted = brick this is too in s40.
when you find problem 5.1.1 lollipop + supersu i think you can slove problem with SuperSU on s40.
I don't found this slove to SuperSU i used custom boot.img with my zelfcompiled kernel.
when you find slove to this problem met SuperSU + boot.img write here i want too know what is problem met boot.img in lollipop 5.1.1 met SuperSU
Click to expand...
Click to collapse
Thanks, then i won't root my Cat S40 for the moment. Because i don't want to keep Kingroot on it all the time.
Oh, and i send Super-sume Pro developer 'MrgatesJunior' a email with request to solve the Super-Sume pro issue on Android 5.1 CAT S40 with link to this postings. Hope he 'll find a solution / update Super Sume pro soon
We can confirm that removing King(o)Root with scripts and replacing it with SuperSU (as would be highly desirable) leads to a bricked S40.
Has anyone perhaps found a way of doing a full backup using a tool similar to SP Flash Tool for MTK devices?
That would help play around without sending the phone in on warranty claim every couple of days...
Cat s40 success SuperSU rooted
Hey i have no idea if there is a new topic for this .....i have a CAT S40 nothing will root it..it's running android 5.1 no app will root this phone and i must have tried most of them
the phone dose not have a fastboot mode and i have not seen any bootloader unlocking tools i see all over internet use this or that but none work....
avrel820 said:
Hey i have no idea if there is a new topic for this .....i have a CAT S40 nothing will root it..it's running android 5.1 no app will root this phone and i must have tried most of them
the phone dose not have a fastboot mode and i have not seen any bootloader unlocking tools i see all over internet use this or that but none work....
Click to expand...
Click to collapse
Cat S40 android 5.1
Same problem.
I tried to do it by adb & fastboot. But I cannot make the option "OEM unlocking" visible in "Developer options". Tried to change dates as recommended in www, but nothing. I have one idea - my s40 from USA. Mb use VPN for router... But I lost few days for finding resolve. I'm tired.
I never will buy production of Caterpillar. This production not for people.
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