FORUMS

Is there a way to root Hisense A5? [Solved]

19 posts
Thanks Meter: 6
 
By gowin132, Junior Member on 26th February 2020, 04:16 AM
Post Reply Email Thread
19th May 2020, 11:35 PM |#111  
Junior Member
Thanks Meter: 3
 
More
Quote:
Originally Posted by lichobg

I think this is not true. Hier in [Hisense A5] Root & Gapps Customizer theme
user Smaxsom wrote:
" I found that after I reflashed firmware L1657.6.08.06.00, it was possible to disable the Hisense Play Store, Browser, and some other built-in applications. So I took the following steps:

1) reflashing firmware L1657.6.08.06.00 that I downloading per my previous post
2) disabling and/or unstalling the Hisense applications where possible
3) upgrading the firmware through Settings
4) running back through @joygram's instructions in the OP

When disabling before step #3 above, it stayed disabled after the upgrade, even for the Hisense Play Store "

So now my Plans are to try with 6.08.06.00 and no i dont uninstal launcher. I have uninstall unknoun **** with unknoun name

Fyi - After making that post, I had read through feedback from others in the forums and found that freezing apps in Titanium Backup is the most flexible approach if your willing to pay for the premium key. I was able to freeze a majority of the built in apps that way including system apps.

Just be aware you might freeze apps that are essential and have to troubleshoot issues (or worse case, reformat if you brick the phone). E.g. I disabled apps found my eink button started to crash, but I was able to isolate the issue down to the floating navigation which I then reenabled.
20th May 2020, 07:58 AM |#112  
Senior Member
Thanks Meter: 218
 
More
@JLowe
Your modemst files are still online.

Giuseppe quoted you when answering and the links still work.
The Following User Says Thank You to Anghirrim For This Useful Post: [ View ] Gift Anghirrim Ad-Free
20th May 2020, 06:45 PM |#113  
Junior Member
Thanks Meter: 3
 
More
Quote:
Originally Posted by Smaxsom

Fyi - After making that post, I had read through feedback from others in the forums and found that freezing apps in Titanium Backup is the most flexible approach if your willing to pay for the premium key. I was able to freeze a majority of the built in apps that way including system apps.

Just be aware you might freeze apps that are essential and have to troubleshoot issues (or worse case, reformat if you brick the phone). E.g. I disabled apps found my eink button started to crash, but I was able to isolate the issue down to the floating navigation which I then reenabled.

This is good information to help others in the future troubleshoot freezing apps. I have found titanium well worth the money.

This is slightly unrelated, but can someone who can read Chinese give a little bit of insight on the cost and process to order/preorder the new A5 from jd.com? https://item.jd.com/100007001395.html

It looks like it costs some amount of money just to get your spot in the line to order, but I am not sure. Has anyone shipped to the US before from jd.com. Sorry for the slightly off topic question, but I thought there would be someone here with experience. Thank you!
21st May 2020, 09:49 AM |#114  
JLowe's Avatar
Senior Member
Thanks Meter: 64
 
More
Quote:
Originally Posted by samplebird

This is good information to help others in the future troubleshoot freezing apps. I have found titanium well worth the money.


The disadvantage of TB is it's quite hard to read on an eink screen. 1st you can just freeze some apps in the normal stock app settings. 2nd there at the f-droid store some apps which you can try:


ADBungFu
https://f-droid.org/en/packages/com.oF2pks.adbungfu/

SuperFreezZ
https://f-droid.org/en/packages/supe....tool.android/
21st May 2020, 01:06 PM |#115  
Junior Member
Thanks Meter: 1
 
More
On the topic of hard to read, what's the best browser people have found that allows force white background and black text for all pages.

I got it going in Firefox, but I find Firefox a bit bulky and the interface a bit tedious compared to Chrome.
21st May 2020, 10:06 PM |#116  
Member
Thanks Meter: 7
 
More
Quote:
Originally Posted by JLowe

Exactly.

https://forum.xda-developers.com/sho...3&postcount=31


You can backup your firmware with adb connected to smartphone very easy


Code:
adb devices
adb shell
su
find /dev | grep by-name$
/dev/block/platform/soc/7123400.sdhci/by-name  <- example
ls -al --color /dev/block/platform/soc/7123400.sdhci/by-name


lrwxrwxrwx 1 root root   21 1970-01-06 20:36 DDR -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 aboot -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 abootbak -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 apdp -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 boot -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 cache -> /dev/block/mmcblk0p58
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 cmnlib -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 cmnlib64 -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 cmnlib64bak -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 cmnlibbak -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 config -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 databackup -> /dev/block/mmcblk0p64
lrwxrwxrwx 1 root root   20 1970-01-06 20:36 devcfg -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 devcfgbak -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 devinfo -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 diag -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 dip -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 dpo -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 dsp -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 dspbak -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 dtbo -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 dtbobak -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 flag -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root   20 1970-01-06 20:36 fsc -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 fsg -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 grow -> /dev/block/mmcblk0p67
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 kdebug -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 kdebuginfo -> /dev/block/mmcblk0p60
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 keymaster -> /dev/block/mmcblk0p55
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 keymasterbak -> /dev/block/mmcblk0p56
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 keystore -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 limits -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 logdump -> /dev/block/mmcblk0p61
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 logo -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 logo1 -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 mcfg -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 mdtp -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 mdtpbak -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 metadata -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 misc -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 modem -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 mota -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 msadp -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 oem -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 persist -> /dev/block/mmcblk0p62
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 phonelog -> /dev/block/mmcblk0p59
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 prospecfg -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 recovery -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 reserve -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 reserve2 -> /dev/block/mmcblk0p65
lrwxrwxrwx 1 root root   20 1970-01-06 20:36 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root   20 1970-01-06 20:36 rpmbak -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root   20 1970-01-06 20:36 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root   20 1970-01-06 20:36 sbl1bak -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 sec -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 splash -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root   20 1970-01-06 20:36 ssd -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 syscfg -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 system -> /dev/block/mmcblk0p63
lrwxrwxrwx 1 root root   20 1970-01-06 20:36 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root   20 1970-01-06 20:36 tzbak -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 userdata -> /dev/block/mmcblk0p66
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 vbmeta -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 vbmetabak -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root   21 1970-01-06 20:36 vendor -> /dev/block/mmcblk0p57
Then you can backup:

i.e. boot.img to root of SdCard
Code:
dd if=/dev/block/mmcblk0p47 of=/sdcard/boot.img
i.e. recovery

Code:
dd if=/dev/block/mmcblk0p48 of=/sdcard/recovery.img
with the recovery you can try to build a twrp
https://forum.xda-developers.com/and...ource-t3843473



Uploads International Firmware L1657 6.03.02.00 / Kernel 4.9.112 / Security-Updates 2019/09 (incl. Gapps by Default)

https://www.upload.ee/files/11708238/boot.img.html
https://www.upload.ee/files/11708271/recovery.img.html
https://www.upload.ee/files/11708346/modem.img.html
https://www.upload.ee/files/11741280....twrp.img.html


The last upload is a test build for Twrp - you can test with unlocked bootloader - no guarantee that it's working and responsibility if you brick your device.


Edited: New Upload Test Build twrp

Hi,
thanks for the TWRP!
I dare not to try yet cause I don't know if my bootloader is unlocked or not.
I have rooted my A5, does it count as bootloader unlocked?

Thanks!
22nd May 2020, 06:16 AM |#117  
JLowe's Avatar
Senior Member
Thanks Meter: 64
 
More
Quote:
Originally Posted by zizicici

I have rooted my A5, does it count as bootloader unlocked?
Thanks!

If you aren't shure if your booloader is unlocked just check it with adb command

Code:
adb devices
adb reboot bootloader
fastboot oem device-info
if you get this:
Code:
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
-> your bootloader isn't unlock

If you root your device only, it doesn't mean your bootloader is unlocked. First check what Firmware you have. If it's lower than 6.09 then update OTA or flash this from microSD
https://forum.xda-developers.com/sho...3&postcount=28

Guide Entering TF-Mode
https://forum.xda-developers.com/sho...7&postcount=21

If you have the 6.09 Firmware installed, then you can follow OP here to Root your device. Maybe try first just installing Magisk (worked for me)
https://forum.xda-developers.com/and...mizer-t4097951

But beware of data loss and you might brick your device. Then you need to reflash the Firmware above in TF Mode. I would recommend first checking if you can enter this mode without any issues like other people have and then decide if you want to take the risk of "bricking" your device
https://forum.xda-developers.com/and...t4097951/page2

Good luck!
The Following 2 Users Say Thank You to JLowe For This Useful Post: [ View ] Gift JLowe Ad-Free
22nd May 2020, 06:32 AM |#118  
Member
Thanks Meter: 7
 
More
Quote:
Originally Posted by JLowe

If you aren't shure if your booloader is unlocked just check it with adb command

Code:
adb devices
adb reboot bootloader
fastboot oem device-info
if you get this:
Code:
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
-> your bootloader isn't unlock

If you root your device only, it doesn't mean your bootloader is unlocked. First check what Firmware you have. If it's lower than 6.09 then update OTA or flash this from microSD
https://forum.xda-developers.com/sho...3&postcount=28

Guide Entering TF-Mode
https://forum.xda-developers.com/sho...7&postcount=21

If you have the 6.09 Firmware installed, then you can follow OP here to unlock bootloader
https://forum.xda-developers.com/and...mizer-t4097951

But beware of data loss and you might brick your device. Then you need to reflash the Firmware above in TF Mode. I would recommend first checking if you can enter this mode without any issues like other people have and then decide if you want to take the risk of "bricking" your device
https://forum.xda-developers.com/and...t4097951/page2

Good luck!

Hi,

I just checked, the bootloader is locked.
My A5 is 6.09 and rooted following OP's guide: https://forum.xda-developers.com/and...mizer-t4097951
I think OP's guide is only to root the phone, right? I'm confused when you said follow OP's guide to unlock bootloader.

Best,
22nd May 2020, 12:42 PM |#119  
JLowe's Avatar
Senior Member
Thanks Meter: 64
 
More
Quote:
Originally Posted by zizicici

Hi,

I just checked, the bootloader is locked.
My A5 is 6.09 and rooted following OP's guide: https://forum.xda-developers.com/and...mizer-t4097951
I think OP's guide is only to root the phone, right? I'm confused when you said follow OP's guide to unlock bootloader.
Best,

You're right it's only rooting. Just installing Magisk Manager got me root access.
23rd May 2020, 11:25 AM |#120  
Junior Member
Thanks Meter: 3
 
More
Quote:
Originally Posted by JLowe

The disadvantage of TB is it's quite hard to read on an eink screen. 1st you can just freeze some apps in the normal stock app settings. 2nd there at the f-droid store some apps which you can try:


ADBungFu
https://f-droid.org/en/packages/com.oF2pks.adbungfu/

SuperFreezZ
https://f-droid.org/en/packages/supe....tool.android/

Agreed. In order to read TB, I had to turn off the High Contrast Text option in the phone settings. Apps that have a dark background seem easier to read without this setting activated, so that the dark colors don't bleed together. I wish it could be set on an app by app basis similar to Clear Mode. I wonder if Tasker could accommodate.
23rd May 2020, 12:54 PM |#121  
Junior Member
Thanks Meter: 3
 
More
Quote:
Originally Posted by Smaxsom

Agreed. In order to read TB, I had to turn off the High Contrast Text option in the phone settings. Apps that have a dark background seem easier to read without this setting activated, so that the dark colors don't bleed together. I wish it could be set on an app by app basis similar to Clear Mode. I wonder if Tasker could accommodate.

I found a way in Tasker to enable High Contrast Text for Dark Mode apps. Here are further details.

https://forum.xda-developers.com/sho...7&postcount=69
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes