Related
Hello, i try port miui to our galaxy...
I need partition layout of GT-I9305 to set up the installation script. Can anyone post it here?
Sent from my GT-I9305
I cant help
Gut it would be great if u create a miui Rom
Thanks For your work homey
Here you go
lrwxrwxrwx root root 2012-10-08 21:43 BOOT -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-10-08 21:43 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-10-08 21:43 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-10-08 21:43 CACHE -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2012-10-08 21:43 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-10-08 21:43 HIDDEN -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2012-10-08 21:43 OTA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2012-10-08 21:43 PARAM -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-10-08 21:43 RADIO -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-10-08 21:43 RECOVERY -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-10-08 21:43 SYSTEM -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2012-10-08 21:43 TOMBSTONES -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-10-08 21:43 USERDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs3 -> /dev/block/mmcblk0p6
---------- Post added at 12:11 PM ---------- Previous post was at 11:39 AM ----------
Let us know how you go, honestly I dont know why experienced devs have not done this yet to other roms, it really doesnt seem so hard for a dev that knows what they are doing, all it really needs is the base firmware changed and the edited files in the I9300 JB base can probably be used in replace of the non-edited ones in the i9305 base saves you from editing the files again. then all the system files should be easily transferable and then the mounting points changed , that sounds like pretty much it or am i missing something?
btemtd said:
Here you go
lrwxrwxrwx root root 2012-10-08 21:43 BOOT -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-10-08 21:43 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-10-08 21:43 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-10-08 21:43 CACHE -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2012-10-08 21:43 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-10-08 21:43 HIDDEN -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2012-10-08 21:43 OTA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2012-10-08 21:43 PARAM -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-10-08 21:43 RADIO -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-10-08 21:43 RECOVERY -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-10-08 21:43 SYSTEM -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2012-10-08 21:43 TOMBSTONES -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-10-08 21:43 USERDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs3 -> /dev/block/mmcblk0p6
---------- Post added at 12:11 PM ---------- Previous post was at 11:39 AM ----------
Let us know how you go, honestly I dont know why experienced devs have not done this yet to other roms, it really doesnt seem so hard for a dev that knows what they are doing, all it really needs is the base firmware changed and the edited files in the I9300 JB base can probably be used in replace of the non-edited ones in the i9305 base saves you from editing the files again. then all the system files should be easily transferable and then the mounting points changed , that sounds like pretty much it or am i missing something?
Click to expand...
Click to collapse
Because there is no Stock jb Version out for s3 but should Come in a few days maybe weeks....
What do you mean no stock JB ? There is stock jb out now for the i9300
Sent from my GT-I9305 using xda app-developers app
I ported MIUI JB for i9300 on AOSP CM10 base, maybe I can help. What base do you want to use?
Well the Xxali5 is the original release and most internationally used and most popular base at the moment
But Some countries released there ph0ne later with a firmware number xxali9. Not sure if there is even any changes. But your choice.
Sent from my GT-I9305 using xda app-developers app
btemtd said:
What do you mean no stock JB ? There is stock jb out now for the i9300
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
there is noch stock jb miui!!!!!!!!!!!!!!!!!!!!!!!! its coming in future
aosp or cm doesnt work for our device!
greetz
F1tty said:
there is noch stock jb miui!!!!!!!!!!!!!!!!!!!!!!!! its coming in future
aosp or cm doesnt work for our device!
greetz
Click to expand...
Click to collapse
Yes indeed...
But as u said there is no stock JB that is what got me confused cause you didnt say MIUI!!!!!!
btemtd said:
Yes indeed...
But as u said there is no stock JB that is what got me confused cause you didnt say MIUI!!!!!!
Click to expand...
Click to collapse
Cause that thread belongs to miui.... If miui for I9300 JB is aviable i Port IT for i9305 specially for english and german maybe more depending on Base rom
Then i think that is part of the instructions. Maybe u can use a miui i9300 jb base and merge it the i9305 base
Sent from my GT-I9305 using xda app-developers app
I cant wait
Can u tell us your progress?
dying to hear the good news
any advance on this? would be amazingg
is there some news on porting ?
Porting is easy, if no one is going to do it I might do it if I get some spare time.. just don't expect any support or updates ok?
Sent from my GT-I9300 using xda app-developers app
So normally, nexus devices have easy partition names... For example, the /dev/block/platform/by-name directory contains things like system, boot, recovery, data, modem, efs, etc.. Well here is the result of "ls -al" of the partition directory on my nexus 9.
[email protected]_lte:/ # ls -al /dev/block/platform/sdhci-tegra.3/by-name
lrwxrwxrwx root root 2014-12-30 12:10 APP -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2014-12-30 12:10 CAC -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2014-12-30 12:10 CDR -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-12-30 12:10 DIA -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-12-30 12:10 DTB -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-12-30 12:10 EF1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-12-30 12:10 EF2 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-12-30 12:10 EKS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-12-30 12:10 EXT -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-12-30 12:10 FST -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-12-30 12:10 GPT -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2014-12-30 12:10 KEY -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-12-30 12:10 LNX -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-12-30 12:10 MD1 -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2014-12-30 12:10 MD2 -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2014-12-30 12:10 MFG -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-12-30 12:10 MSC -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-12-30 12:10 NCT -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-12-30 12:10 OTA -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2014-12-30 12:10 PG1 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-12-30 12:10 PST -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2014-12-30 12:10 RCA -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-12-30 12:10 RV1 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-12-30 12:10 RV2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-12-30 12:10 RV3 -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2014-12-30 12:10 SER -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-12-30 12:10 SOS -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-12-30 12:10 SP1 -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-12-30 12:10 TOS -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-12-30 12:10 UDA -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2014-12-30 12:10 VNR -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-12-30 12:10 WB0 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-12-30 12:10 WDM -> /dev/block/mmcblk0p7
My question is, which is which? How can i tell which is the recovery block, system block, recovery and so on? Is there a list of translations for these partition names? Thanks
Not sure what need you are trying to fulfill but read this http://www.all-things-android.com/content/review-android-partition-layout as a starter.
peterk-1 said:
Not sure what need you are trying to fulfill but read this http://www.all-things-android.com/content/review-android-partition-layout as a starter.
Click to expand...
Click to collapse
For example, nexus 5 has a symlinks like /dev/block/platform/msm_sdcc.1/by-name/boot that is linked to /dev/block/mmcblk0p19. Clearly this is the kernel block. Because its called "boot". Right? So, the nexus 9 is different from most other nexus devices. The by-name folder has 3 character names that dont really translate to "boot" or "system" or "recovery". It has names like "dia" and "vnr". I know that the "vnr" is the Vendor block. So which one is the "boot" block, is it "dia", or is it"svn". Do you understand what im asking? How in the heck is one supposed to figure out which block device is which???
bynarie said:
How in the heck is one supposed to figure out which block device is which???
Click to expand...
Click to collapse
The "clever ****" reply is "google" but I've found that many pages go silent on the key issue and and others are way over my head.
Some pointers:
Reboot your device and look at the dmesg log and :
Search "target=" (6 hits in 1 file)
\\CORSAIR\CorsairG\junk\dmesg.txt (6 hits)
Line 1077: <14>[ 5.168004] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/APP,target=/system,type=ext4)=0
Line 1080: <14>[ 5.172727] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/VNR,target=/vendor,type=ext4)=0
Line 1114: <14>[ 5.507472] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/CAC,target=/cache,type=ext4)=0
Line 1127: <14>[ 5.527126] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/UDA,target=/data,type=f2fs)=-1
Line 1145: <14>[ 5.550663] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/UDA,target=/data,type=ext4)=-1
Line 1488: <14>[ 111.676664] fs_mgr: __mount(source=/dev/block/dm-0,target=/data,type=f2fs)=0
http://newandroidbook.com/Articles/Nexus9.html - note "tegra" names and Nvidia Shield.
https://android.googlesource.com/device/htc/flounder/+/android-5.0.2_r1/fstab.flounder
thanks!
peterk-1 said:
The "clever ****" reply is "google" but I've found that many pages go silent on the key issue and and others are way over my head.
Some pointers:
Reboot your device and look at the dmesg log and :
Search "target=" (6 hits in 1 file)
\\CORSAIR\CorsairG\junk\dmesg.txt (6 hits)
Line 1077: <14>[ 5.168004] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/APP,target=/system,type=ext4)=0
Line 1080: <14>[ 5.172727] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/VNR,target=/vendor,type=ext4)=0
Line 1114: <14>[ 5.507472] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/CAC,target=/cache,type=ext4)=0
Line 1127: <14>[ 5.527126] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/UDA,target=/data,type=f2fs)=-1
Line 1145: <14>[ 5.550663] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/UDA,target=/data,type=ext4)=-1
Line 1488: <14>[ 111.676664] fs_mgr: __mount(source=/dev/block/dm-0,target=/data,type=f2fs)=0
http://newandroidbook.com/Articles/Nexus9.html - note "tegra" names and Nvidia Shield.
https://android.googlesource.com/device/htc/flounder/+/android-5.0.2_r1/fstab.flounder
Click to expand...
Click to collapse
Thanks!! That fstab flounder page is a really good starting list of exactly what i was looking for. {{Presses Thanks Button}}
Is it possible to delete some partitions like system image and resize data partition?
wizzardsk said:
Is it possible to delete some partitions like system image and resize data partition?
Click to expand...
Click to collapse
No, system image system is a partition with android system. Other partitions are too small for redesigning to make sense.
Vartom said:
No, system image system is a partition with android system. Other partitions are too small for redesigning to make sense.
Click to expand...
Click to collapse
I am not sure about the name, but there are 2 system partitions on nexus 9 that i have not seen on other devices.
wizzardsk said:
I am not sure about the name, but there are 2 system partitions on nexus 9 that i have not seen on other devices.
Click to expand...
Click to collapse
you are mistaken, he has one system partitions (APP).
What is this?
wizzardsk said:
What is this?
Click to expand...
Click to collapse
Same thing. One is a regular backup, one is to backup as an image (system.img) pick the way you want to backup.
So both system partitions are necessary?
Edit: i understand, so there is only 1 system partition
wizzardsk said:
So both system partitions are necessary?
Edit: i understand, so there is only 1 system partition
Click to expand...
Click to collapse
Yes there is only 1 system partition. TWRP is offering 2 ways to make a system backup, either a standard backup, or backup as an image.
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
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.
I've spent so much time on this forum and learned so much that I thought this is best place to go for my last resort. I really need to root this phone. I want to be able to use some rooted apps and especially be able to get more apps on my SD Card. My phone is unlockable (In fact Cricket said all their current phones are) I have no fastboot, no proper recovery mode and not even a bootloader mode. When I type adb reboot bootloader it only reboots the phone. I've looked into flashing a new boot, but I don't completely understand how to make or how to get all the any of the Qualcomm flash tools required files. I'll need help with that if it comes to it. I can't even flash a different models stock, because all LG stock I can find is ARB00 and right now I'm ARB03 it doesn't matter if it's even a higher version stock like Pie or even a it's LG G7 ThinQ unless it's ARB03 or higher I can't flash it and of course I can't downgrade. Which would save me a lot of headaches because the Nougat version at least still has fastboot and is ARB00. Something I can work with.
I am about to go to Walmart and just buy it again, because their version is still Nougat. That's what I'll do if I find no answer here, but I want to give this phone another chance. I read this phone can be rooted with Magisk, but with no recovery and no fastboot unless there's another option I don't know if that's even an option. Is there any way to dd install Magisk? If so please let me know. I've also been told it needs to be manually rooted, but I don't know where to get started doing that. I know it's get the right su files in the right places, and busybox but how do I do that with no root to start with, and being unable to mount the system? Is there a way?
I'm seriously willing to try anything at this point even if it will brick my phone. I have insurance on it that will replace it no matter how much damage I cause it and like I said am willing to re-buy the phone at Walmart which might be the better option since getting it from Cricket will most likely just take me back to where I started with an 8.1 phone that I can't do anything with. I don't care much about custom roms or that sort of thing. There isn't any for this phone anyway. I just want it rooted! please if you can think of anything, anything at all please let me know!
I have Windows 10 and Ubuntu
Also If these will help
Partitions:
HTML:
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 DDR -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 aboot -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 abootbak -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 apdp -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 boot -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 cache -> /dev/block/mmcblk0p58
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 cmnlib -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 cmnlib64 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 cmnlib64bak -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 cmnlibbak -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 devcfg -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 devcfgbak -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 devinfo -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 dpo -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 drm -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 dsp -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 eksst -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 encrypt -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 factory -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 fota -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 fsc -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 fsg -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 ftm -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 grow -> /dev/block/mmcblk0p60
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 keymaster -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 keymasterbak -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 keystore -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 laf -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 lafbak -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 mcfg -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 misc -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 modemst1 -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 modemst2 -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 mpt -> /dev/block/mmcblk0p55
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 msadp -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 persist -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 persistent -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 raw_resources -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 raw_resourcesbak -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 rct -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 recovery -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 recoverybak -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 rpm -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 rpmbak -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 sbl1 -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 sbl1bak -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 sec -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 sns -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 spare1 -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 spare2 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 spare3 -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 spare4 -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 spare5 -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 srtc -> /dev/block/mmcblk0p56
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 system -> /dev/block/mmcblk0p57
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 tzbak -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 userdata -> /dev/block/mmcblk0p59
Nothing?
Okay from the lack of any reply I'm guessing there isn't a current way to root this device or nothing anybody knows. So I guess I'll get the Nougat version then, and see if I have better luck with it or wait until I save up enough money for another phone that I can unlock and root. If anybody thinks of anything I'm still willing to try, but I'm getting it's about time to give up and just never buy directly from cricket again.
@sjjtnj
Rooting a phone's Android doesn't depend on its Android version but whether it's bootloader can get unlocked or not what basically prevents rooting Android. Take note that not all OEMs/Carriers allow this.
If phone in question is accessable via ADB then to find this out you run this command sequence
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
If 1 is returned then phone's bootloader is unlockable otherwise not.
Thanks!
jwoegerbauer said:
@sjjtnj
Rooting a phone's Android doesn't depend on its Android version but whether it's bootloader can get unlocked or not what basically prevents rooting Android. Take note that not all OEMs/Carriers allow this.
If phone in question is accessable via ADB then to find this out you run this command sequence
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
If 1 is returned then phone's bootloader is unlockable otherwise not.
Click to expand...
Click to collapse
Thanks this is gave me some hope! I got a 1 so I guess it is unlockable! I can't use fastboot though. If I can figure a way to enable it maybe I can unlock and root it. The Nougat version still has fastboot enabled so that's why I wanted it, but it would be nice to find a way to unlock this one.
@sjjtnj
It's well known that not all OEMs/Carriers support Fastboot as intended by Google. They think that providing Revovery is enough.
FYI: The phone in question has a Recovery partition - as that's default with all Android devices. You enter Recovery mode this way
Code:
adb devices
adb shell "reboot recovery"
Now once you are in recovery, ADB will work instead of Fastboot.
Anyway:
Have you already tried
{
"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"
}
to unlock phone's bootloader - what requires the USB drivers suitable at 100% to the phone are got installed on your Windows computer?
How-To:
1. Download the Android Fastboot Tool v1.2 from here.
2. Once you have downloaded the file, extract the zip file.
3. When you are done with the extraction you open the tool by clicking on Android Fastboot .exe file as Adminstrator.
Note: Never have tried out this.
jwoegerbauer said:
@sjjtnj
It's well known that not all OEMs/Carriers support Fastboot as intended by Google. They think that providing Revovery is enough.
FYI: The phone in question has a Recovery partition - as that's default with all Android devices. You enter Recovery mode this way
Code:
adb devices
adb shell "reboot recovery"
Now once you are in recovery, ADB will work instead of Fastboot.
Anyway:
Have you already tried
to unlock phone's bootloader - what requires the USB drivers suitable at 100% to the phone are got installed on your Windows computer?
How-To:
1. Download the Android Fastboot Tool v1.2 from here.
2. Once you have downloaded the file, extract the zip file.
3. When you are done with the extraction you open the tool by clicking on Android Fastboot .exe file as Adminstrator.
Note: Never have tried out this.
Click to expand...
Click to collapse
Rebooting recovery gives me the little green guy passed out with a triangle with exclamation mark as a heart and says no command. I clicked the buttons you're supposed to click with that error to get the recovery options, but it just reboots. Sometimes though very randomly I do get to a place to wipe data and reset the phone. So I say the recovery works about .05% of the time. Unfortunately I can't flash new partitions with dd without root so no changing the boot.img or recovery.img like I had hoped either. Thank you! I haven't saw that tool before, I'm on Linux right now, but will download it as soon as I get back on Windows. I'll update after I try it.
Still need to try
jwoegerbauer said:
@sjjtnj
It's well known that not all OEMs/Carriers support Fastboot as intended by Google. They think that providing Revovery is enough.
FYI: The phone in question has a Recovery partition - as that's default with all Android devices. You enter Recovery mode this way
Code:
adb devices
adb shell "reboot recovery"
Now once you are in recovery, ADB will work instead of Fastboot.
Anyway:
Have you already tried
to unlock phone's bootloader - what requires the USB drivers suitable at 100% to the phone are got installed on your Windows computer?
How-To:
1. Download the Android Fastboot Tool v1.2 from here.
2. Once you have downloaded the file, extract the zip file.
3. When you are done with the extraction you open the tool by clicking on Android Fastboot .exe file as Adminstrator.
Note: Never have tried out this.
Click to expand...
Click to collapse
Sorry I haven't got this tried yet. I was trying to set up my Linux when it messed up and I had to restart the process. I'm keeping backups this time, but anyway just finishing that because I had to stop when I got a concussion. On the picture, it says to get in fastboot mode. I can't do that only download mode. So I don't think it will work, but I'll still try. I decided I'm going to rebuy the phone from Walmart that has Nougat and fastboot still enabled. That seems my only hope to unlock a phone and root it. The Nougat version is also ARB00 so I can flash firmware of a variant on that one if I need to as well. I know it sounds crazy to buy the same phone, but it's really all I can afford at this time. I'm saving up money for a better phone though, and my nephew has a really bad phone right now. So I can just give this one to him. He doesn't need root or anything so he'll like it.