Moto G4 plus relock bootloader

echo92

Senior Member
Jan 1, 2017
3,730
1,987
223
Plymouth
@echo92 is it suggestable to flash March's security patch, not complete, but only system/boot and required one only ?
So other stuffs will not be touched ?

Or
as he can boot into bootloader, if he get succeed to install TWRP, then he can flash custom ROM.
@clever_idiot let echo92 confirm above things.
1) You could do that, but the moment you flash an OTA from the March to June update, you run the real, very high risk of a hard brick (because of the mismatch between the bootloader, GPT and the rest of the system). Given clever_idiot's bootloader is downgraded, OTAs are generally a very risky idea, hence the idea of using the fastboot ROM to repair and flash a clean copy of both the GPT/bootloader. Of course, without knowing what stock build of 7.0 was on the device before, flashing the wrong fastboot Nougat ROM might itself invite a brick...

2)It might be safest, if in fastboot we can boot into TWRP (which TWRP are you using btw, clever_idiot?), then we might be able to flash a custom ROM, without having to worry about the bootloader/GPT and flash a custom logo.bin to hide the bootloader warning. That is, assuming the rest of the device firmware is okay, which is difficult to determine at the moment without a booting device.
 

____Mdd

Senior Member
Jul 26, 2016
721
330
63
24

clever_idiot

Member
Aug 15, 2017
41
0
0
1) You could do that, but the moment you flash an OTA from the March to June update, you run the real, very high risk of a hard brick (because of the mismatch between the bootloader, GPT and the rest of the system). Given clever_idiot's bootloader is downgraded, OTAs are generally a very risky idea, hence the idea of using the fastboot ROM to repair and flash a clean copy of both the GPT/bootloader. Of course, without knowing what stock build of 7.0 was on the device before, flashing the wrong fastboot Nougat ROM might itself invite a brick...

2)It might be safest, if in fastboot we can boot into TWRP (which TWRP are you using btw, clever_idiot?), then we might be able to flash a custom ROM, without having to worry about the bootloader/GPT and flash a custom logo.bin to hide the bootloader warning. That is, assuming the rest of the device firmware is okay, which is difficult to determine at the moment without a booting device.
So what shall I do? Download the rom from the link you provided and then flash it?

---------- Post added at 02:34 PM ---------- Previous post was at 02:30 PM ----------

@clever_idiot follow this and report,

Get sherps's TWRP from here : https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337

- Boot into bootloader
- flash twrp [ mfastboot flash recovery TWRP-xxxxxx.img ]
- boot into recovery
- download any custom ROM, place in memory card
- flash through recovery.

*** If flashing of twrp fails
Then boot into twrp without flashing
- boot bootloader
- mfastboot boot twrp-xxx.img
which one shall I use?
Code:
 recovery_stock_MPJ24.139-23.4.img 16.10MB 2016-07-26 14:09:42
 recovery_stock_MPJ24.139-63.4.img 16.10MB 2016-09-09 15:33:11
 recovery_stock_NPJ25.75-2.img 16.10MB 2016-10-24 10:15:12
 twrp-3.0.2-r1-athene_shreps.img 12.47MB 2016-08-02 22:28:34
 twrp-3.0.2-r3-athene_shreps.img 12.34MB 2016-09-07 16:04:44
 twrp-3.0.2-r4-athene_shreps.img 12.18MB 2016-11-05 15:38:24
 twrp-3.0.3-n1-athene_shreps.img 13.00MB 2017-01-03 16:08:14
 twrp-3.0.3-n2-athene_shreps.img 13.00MB 2017-02-18 17:50:30
 twrp-3.0.3-n4-athene_shreps.img 14.38MB 2017-02-25 23:21:26
 twrp-3.1.0-athene_shreps.img 13.47MB 2017-03-12 17:15:25
 twrp-3.1.1-athene_shreps.img 13.35MB 2017-06-05 13:20:21
 

echo92

Senior Member
Jan 1, 2017
3,730
1,987
223
Plymouth
So what shall I do? Download the rom from the link you provided and then flash it?
I'd firstly suggest follow ____Mdd's post above - see if you can boot into or flash TWRP (shrep's TWRP 3.1.1 is a safe choice - that's twrp-3.1.1-athene_shreps.img ), and if you can, flash a custom ROM. If you can flash a custom ROM and your device boots, that might be the safest way to get out of the situation.

See how you get on with that.
 
  • Like
Reactions: clever_idiot

clever_idiot

Member
Aug 15, 2017
41
0
0
@clever_idiot follow this and report,

Get sherps's TWRP from here : https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337

- Boot into bootloader
- flash twrp [ mfastboot flash recovery TWRP-xxxxxx.img ]
- boot into recovery
- download any custom ROM, place in memory card
- flash through recovery.

*** If flashing of twrp fails
Then boot into twrp without flashing
- boot bootloader
- mfastboot boot twrp-xxx.img
I did but the same thing is happening, the unlock message pops, screen turns off, goes on again message pops up agaim ,switches off and reapeats infinite time:crying:

this is what I did
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp-3.1.1-athene_shreps.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
downloading 'boot.img'...
OKAY [  0.438s]
booting...
OKAY [  0.266s]
finished. total time: 0.712s

C:\Program Files (x86)\Minimal ADB and Fastboot>
C:\Program Files (x86)\Minimal ADB and Fastboot>
 

echo92

Senior Member
Jan 1, 2017
3,730
1,987
223
Plymouth
I did but the same thing is happening, the unlock message pops, screen turns off, goes on again message pops up agaim ,switches off and reapeats infinite time:crying:

this is what I did
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp-3.1.1-athene_shreps.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
downloading 'boot.img'...
OKAY [  0.438s]
booting...
OKAY [  0.266s]
finished. total time: 0.712s

C:\Program Files (x86)\Minimal ADB and Fastboot>
C:\Program Files (x86)\Minimal ADB and Fastboot>
Okay, what about flashing TWRP to your recovery partition (with the command 'fastboot flash recovery twrp-3.1.1-athene_shreps.img' )? Does that work or still give you the bootloop?
 

clever_idiot

Member
Aug 15, 2017
41
0
0
Okay, what about flashing TWRP to your recovery partition (with the command 'fastboot flash recovery twrp-3.1.1-athene_shreps.img' )? Does that work or still give you the bootloop?
nope. still the same.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.1.1-athene_shreps.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (13674 KB)...
OKAY [  0.441s]
writing 'recovery'...
(bootloader) Image not signed or corrupt

OKAY [  0.210s]
finished. total time: 0.660s

C:\Program Files (x86)\Minimal ADB and Fastboot>
 

echo92

Senior Member
Jan 1, 2017
3,730
1,987
223
Plymouth
Bootloop, the same thing that used to happen, on off on off
Hrm, then you may have to flash the stock fastboot ROM. Without knowing what stock ROM you had previously, you may have to flash the March or June 2017 stock fastboot ROM. As ____Mdd asked earlier, can you remember if you took an OTA to NPJS25.93-14-4 or NPJS25.93-14-8?

A few pointers:
Ensure you have plenty of time to flash this, so you do not rush. This process affects your device directly.
You may wish to flash the commands manually, so you can see if the flash was okay (should report [OKAY] if so).
Normally, I'd suggest flashing your GPT and bootloader of the newer stock ROM, to formally update your device to the same firmware level and reduce the chances of a brick - however, with your bootloader downgraded, I do not know if it's safe (and that's one of the issues with downgrading). You could flash initially without GPT/bootloader, see if your device is working first, you may wish for, or you could flash with the GPT/bootloader, up to you.

Without GPT/bootloader:
Code:
 fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot reboot
Of course, if you flash using these commands, then do not accept/install any OTA updates.
 

clever_idiot

Member
Aug 15, 2017
41
0
0
Hrm, then you may have to flash the stock fastboot ROM. Without knowing what stock ROM you had previously, you may have to flash the March or June 2017 stock fastboot ROM. As ____Mdd asked earlier, can you remember if you took an OTA to NPJS25.93-14-4 or NPJS25.93-14-8?

A few pointers:
Ensure you have plenty of time to flash this, so you do not rush. This process affects your device directly.
You may wish to flash the commands manually, so you can see if the flash was okay (should report [OKAY] if so).
Normally, I'd suggest flashing your GPT and bootloader of the newer stock ROM, to formally update your device to the same firmware level and reduce the chances of a brick - however, with your bootloader downgraded, I do not know if it's safe (and that's one of the issues with downgrading). You could flash initially without GPT/bootloader, see if your device is working first, you may wish for, or you could flash with the GPT/bootloader, up to you.

Without GPT/bootloader:
Code:
 fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot reboot
Of course, if you flash using these commands, then do not accept/install any OTA updates.
right now I am downloading this rom :- ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and as far as the OTA update is concerned it came around this date:- Dec 29, 2016
 

echo92

Senior Member
Jan 1, 2017
3,730
1,987
223
Plymouth
right now I am downloading this rom :- ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and as far as the OTA update is concerned it came around this date:- Dec 29, 2016
Okay, then you may wish to try the npj25.93-14 December stock ROM first with the same commands as I mentioned above
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369

That way, you still have an exit strategy, with the later updates you will likely not be able to downgrade.
 

clever_idiot

Member
Aug 15, 2017
41
0
0
Okay, then you may wish to try the npj25.93-14 December stock ROM first with the same commands as I mentioned above
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369

That way, you still have an exit strategy, with the later updates you will likely not be able to downgrade.
Okay so the rom is downloaded and I have to then extract all the files to Minimal and ADB folder, and then press shift+right click, open command window there, and paste one by one line from the command and press enter. OR copy paste all the commands at once?

---------- Post added at 04:38 PM ---------- Previous post was at 04:11 PM ----------

Okay, then you may wish to try the npj25.93-14 December stock ROM first with the same commands as I mentioned above
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369

That way, you still have an exit strategy, with the later updates you will likely not be able to downgrade.
HOLY ****! THIS TOO DIDNT WORK:confused:
 

____Mdd

Senior Member
Jul 26, 2016
721
330
63
24
Okay so the rom is downloaded and I have to then extract all the files to Minimal and ADB folder, and then press shift+right click, open command window there, and paste one by one line from the command and press enter. OR copy paste all the commands at once?
Copy one by one.. not all at once.
Check that you get "okay" after flash of each completes.

---------- Post added at 09:21 PM ---------- Previous post was at 09:10 PM ----------

@clever_idiot i wonder if this issue is same as phone always boots into recovery instead of system.

For that, these commands was solution for clearing bootloader malfunction.
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
 

clever_idiot

Member
Aug 15, 2017
41
0
0
Copy one by one.. not all at once.
Check that you get "okay" after flash of each completes.

---------- Post added at 09:21 PM ---------- Previous post was at 09:10 PM ----------

@clever_idiot i wonder if this issue is same as phone always boots into recovery instead of system.

For that, these commands was solution for clearing bootloader malfunction.
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
I copied each line from the command, got OKAY everytime ,but its still into the same thing.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo logo.bin
< waiting for any device >
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:logo: not found
target reported max download size of 536870912 bytes
sending 'logo' (2105 KB)...
OKAY [  0.077s]
writing 'logo'...
OKAY [  0.056s]
finished. total time: 0.143s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [  0.529s]
writing 'boot'...
(bootloader) Image signed with key bad key

OKAY [  0.391s]
finished. total time: 0.930s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [  0.528s]
writing 'recovery'...
(bootloader) Image signed with key bad key

OKAY [  0.438s]
finished. total time: 0.971s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash dsp adspso.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:dsp: not found
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [  0.526s]
writing 'dsp'...
OKAY [  0.259s]
finished. total time: 0.794s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash oem oem.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:oem: not found
target reported max download size of 536870912 bytes
sending 'oem' (96490 KB)...
OKAY [  3.043s]
writing 'oem'...
OKAY [  1.444s]
finished. total time: 4.492s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261001 KB)...
OKAY [  8.228s]
writing 'system'...
OKAY [  3.991s]
finished. total time: 12.226s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (250858 KB)...
OKAY [  7.896s]
writing 'system'...
OKAY [  3.897s]
finished. total time: 11.803s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.2
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (254625 KB)...
OKAY [  8.036s]
writing 'system'...
OKAY [  4.034s]
finished. total time: 12.080s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.3
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261577 KB)...
OKAY [  8.235s]
writing 'system'...
OKAY [  3.639s]
finished. total time: 11.884s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.4
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (260443 KB)...
OKAY [  8.210s]
writing 'system'...
OKAY [  4.251s]
finished. total time: 12.470s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.5
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (248842 KB)...
OKAY [  7.841s]
writing 'system'...
OKAY [  3.654s]
finished. total time: 11.505s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.6
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (259549 KB)...
OKAY [  8.178s]
writing 'system'...
OKAY [  4.521s]
finished. total time: 12.699s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.7
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (82497 KB)...
OKAY [  2.603s]
writing 'system'...
OKAY [  1.191s]
finished. total time: 3.804s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modem: not found
error: cannot load 'NON-HLOS.bin'

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modemst1: not found
erasing 'modemst1'...
OKAY [  0.030s]
finished. total time: 0.035s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modemst2: not found
erasing 'modemst2'...
OKAY [  0.033s]
finished. total time: 0.035s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:fsg: not found
target reported max download size of 536870912 bytes
sending 'fsg' (2040 KB)...
OKAY [  0.076s]
writing 'fsg'...
OKAY [  0.069s]
finished. total time: 0.156s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:cache: not found
erasing 'cache'...
OKAY [  0.020s]
finished. total time: 0.020s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [  0.075s]
finished. total time: 0.080s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase customize
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:customize: not found
erasing 'customize'...
OKAY [  0.020s]
finished. total time: 0.025s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase clogo
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:clogo: not found
erasing 'clogo'...
OKAY [  0.019s]
finished. total time: 0.024s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting...

finished. total time: 0.050s

C:\Program Files (x86)\Minimal ADB and Fastboot>


---------- Post added at 05:10 PM ---------- Previous post was at 04:58 PM ----------

A slight progress, I used to get KEY: N/A now I get KEY:bad key
 

____Mdd

Senior Member
Jul 26, 2016
721
330
63
24
@clever_idiot not a progress really. It's because you flashed Nougat firmware. MM to N, that was changed for everyone.

Did you try these commands ? (For clearing bootloader malfunction )
fastboot oem fb_mode_set
fastboot oem fb_mode_clear

Better way to try these commands is during flash, but you can try directly without flashing other stuff...
fb_mode_set must be used first.
fb_mode_clear must be last (but before reboot)
 
Last edited:

echo92

Senior Member
Jan 1, 2017
3,730
1,987
223
Plymouth
I copied each line from the command, got OKAY everytime ,but its still into the same thing.


---------- Post added at 05:10 PM ---------- Previous post was at 04:58 PM ----------

A slight progress, I used to get KEY: N/A now I get KEY:bad key
Any more luck with the fastboot commands ____Mdd suggested?

If not, we might have to look into flashing a GPT/bootloader (I don't know if the bootloader is having issues handing off to the kernel, which may be causing the bootloops) or we may have to consider the possibility that the flash memory on your device is failing... (hopefully not the second possibility...)
 

clever_idiot

Member
Aug 15, 2017
41
0
0
Right now I have to sleep, I have a meeting tomorrow, but I.ll keep you guys posted ASA I flash those commands. THANK YOU SO MUCH FOR THE HELP, I'll be in touch
 
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone