FORUMS
Remove All Ads from XDA

Does anyone out there have a Gome U7 and knows how to root it?

44 posts
Thanks Meter: 10
 
By SkynyrdZ, Member on 5th April 2019, 06:40 AM
Post Reply Email Thread
24th May 2019, 11:36 PM |#41  
Junior Member
Thanks Meter: 5
 
More
the instructions in my last post seem still not to work properly
on a new phone (or a fully set-back one)

so here is my last try:
(I'm tired off this)

----- ----- ----- ----- ----- -----


these instructions will let you root your GOME U7
but they will also delete ALL personal DATA on it,
so make a backup of them to an external place (sd-card, internet)
before you start to root your phone if they are important to you
(remove then the sd-card with your personal stuff from the phone
until all rooting work is done) (just to avoid accidents)

---

(on Windows 10 x64 usually other driver-installation-methods fail, so)
install ReiBoot-for-Android-2.0.0.15 (the free version is good enough)
>>> and run it at least once to let it finish its usb-driver-installation

extract platform-tools_r28.0.3-windows.zip somewhere
rename the folder to adb and place it in C:\

extract Gome_2017M27A_MT6757_V01_20180122.zip somewhere
(and delete the Gome_2017M27A-folder later to save space)
copy folder Firmware from it to C:\adb and rename it to stock
you have now the original-images in C:\adb\stock

create a folder C:\adb\twrp
and extract Gome_U7_3.2.3.rar in it

create folder C:\adb\2017
place these files there:
Magisk-v19.2.zip
no-verity-opt-encrypt-6.0.zip
MagiskManager-v7.2.0.apk
Root_Essentials_v2.4.9.apk
Magisk-uninstaller-20190520.zip [maybe]

---

first, connect the phone with the usb-cable to the pc

then go into recovery-mode
>>> for this turn the phone on
let it boot normally
and start ReiBoot on your PC
and click enter-recovery-mode

if this not works (but it should)
>>> press and hold the power-button on your phone
and (then at the same time) the (volume-)up-button
until a menue appears,
release then first the power-button
and then the (volume-)up-button,
select what you want there with the (volume-)up-button
and press then the (volume-)down-button to confirm it

in [stock-]recovery-mode
>>> select wipe-data/factory-reset
confirm this with the power-button
>>> select yes-delete-everything
confirm it with the power-button
>>> select power-off
confirm it with the power-button

phone charges (should be 100%)

turn it on

GOME-logo stays for 5 minutes and phone gets newly initialised
what you choose now is not so important because it gets deleted later

go to settings >>> scroll down to about phone
>>> push build-number 7 times >>> this makes developer-options available >>> go back
settings >>> developer-options >>> activate oem-bootloader-unlock and usb-debugging [if they are not]

on pc >>> in windows-menue >>> windows-system >>> shell (/cmd)
[it's the command-line-modus in a window] (maybe start it as administrator)

go to platform-tools-folder (C:\adb) (for example with the command cd\adb)
>>> type: adb devices >>> no device found [maybe] (or unauthorized)
confirm/allow the connection on phone (permanently)
>>> type: adb devices >>> phone found (shows serial)
>>> type: adb reboot bootloader
phone boots in fastboot-mode [small writing in left down corner in phone display]

on pc in shell >>> type: fastboot flashing unlock
>>> push (volume-)up-bottom on phone to confirm

(don't flash anything now, because it doesn't save time) [believe me]

>>> type: fastboot reboot

GOME-logo stays for 5 minutes and phone gets newly initialised
what you choose now is not so important because it gets deleted later

make developer-options and usb-debugging available again
(you can verify it again with: adb devices)

on pc in shell >>> type: adb reboot bootloader
phone boots in fastboot-mode [small writing in left down corner in phone display]

on pc in shell >>> type: fastboot flash boot twrp\boot.img
--- DO NOT FLASH THE RECOVERY-IMAGE NOW ---
on pc in shell >>> type: fastboot reboot

phone reboots and after a while
the message -- ERASING -- appears
and the phone reboots again

on pc in shell >>> type: adb reboot bootloader
on pc in shell >>> type: fastboot flash recovery twrp\recovery.img

now turn off the phone
now turn on the phone

phone boots to normal system

now go into recovery-mode
for this start ReiBoot on your PC and click enter-recovery-mode

you can do it also this way:
>>> press and hold the power-button on the phone
and (then at the same time) the (volume-)up-button
until a menue appears,
release then first the power-button
and then the (volume-)up-button,
select what you want there with the (volume-)up-button
and press then the (volume-)down-button to confirm it

the phone reboots to TWRP-recovery

TWRP-recovery wants to decrypt data now
(because it can't access the data-partition)
>>> press cancel

then something in Russian appears

press the right grey button, scroll up and choose english
now slide the blue-white arrow on the bottom to the right

now >>> choose Wipe (in the right upper corner)
>>> choose Format Data
>>> type yes
... let it work / erase all your data
>>> push Reboot System

phone boots and GOME-logo stays for 5 minutes
>>> wait until your phone is initialized / ready again

choose now what you really want (name, ...) / setup your phone properly

then >>> make developer-options and usb-debugging available again

on pc in shell >>> type: adb push 2017 /sdcard

>>> start ReiBoot on PC and click enter-recovery-mode

phone reboots to twrp-recovery in Russian

press right grey button, scroll up, choose english and press ok
(maybe mark never-show-this-question-again)
slide the blue-white arrow on the bottom to the right

in TWRP-recovery choose Install (left upper corner)
choose Magisk-v19.2.zip from /sdcard/2017
add more zips
choose no-verity-opt-encrypt-6.0.zip
mark reboot after installation
slide blue-white arrow on bottom to right

phone reboots to normal system

MagiskManager_7.2.0 is now already installed [for whatever reason]
[the full version] (it is recommended to run it at least once)
[if it's not the full version you can install it from /2017]

install Root_Essentials_v2.4.9.apk now
to do so open settings and allow unknown-sources
run Root-Essentials now
a super-user-request appears >>> grant (and allow-forever)
in its tools >>> scroll down and choose root-checker
message: root-privileges found


>>> ROOT <<<


---

Magisk-Manager seems to be necessary [with these instructions]
if you uninstall it, some things will work, some things not,
because of the settings it has already stored somewhere

---

and: do not lock your phone again
with twrp-recovery is flashed / installed
because it's totally not working (but I can't remember exactly)

---

UNTESTED / maybe you want to go an additional round
and Format Data again in twrp
> because magisk was installed after the format <
[just a thought] [theoretically this could be good (or wrong)]
(but every data would be gone again after that)
(and you would have to repeat some of the steps before)
(so, normally you shouldn't do that)

---

in rare cases if you try to install apk-files
which you have copied from your pc to your phone
with the apk-push-command a message appears
that the file-format of the files is not supported
then simply change the name of the folder
on your phone in which the apk-files are stored
this works but has to be done again for new files
(decide by yourself that this is reason enough
to setup / re-install everything new or not)

---

IF YOUR PHONE ENDLESSLY LOOPS TO TWRP-RECOVERY

you have flashed the modified-boot-image
and the modified-recovery-image at the same time

solution: flash the stock-recovery-image again

then the -- ERASING -- message appears
and the phone boots normally after that to GOME

you can now flash the modified-recovery-image again
and try to get everything working

but it's better to give it a completely new start
and to FOLLOW THESE INSTRUCTIONS:


connect usb-cable to pc and phone

in twrp press Reboot >>> Bootloader

on pc >>> windows-menue >>> windows-system >>> shell (/cmd)
go to platform-tools-folder (C:\adb) (for example with cd\adb)

on pc in shell >>> type: fastboot continue

phone boots normally (this one time) [in most cases]

backup your personal data to an external place (sd-card, internet)
then remove the sd-card (as example) with your personal stuff
from the phone until everything is done / you are root

restart the phone >>> you are now in twrp-recovery-again

in TWRP-recovery choose Wipe (right upper corner)
>>> choose Format Data
>>> type yes
... let it work / erase all data
>>> push Reboot System

phone boots to twrp-recovery again

press Reboot >>> Bootloader

on pc in shell >>> type: fastboot continue

phone boots and GOME-logo stays for 5 minutes
>>> wait and let it start

go to settings >>> scroll down >>> about phone
>>> push build-number 7 times (makes the developer-options available) >>> go back
(in settings) >>> developer-options >>> activate oem-bootloader-unlock and usb-debugging

on pc >>> in windows-menu >>> windows-system >>> shell (/cmd)
go to platform-tools-folder (C:\adb) (for example with cd\adb)
>>> type: adb devices >>> no device found [maybe] (or unauthorized)
confirm/allow the connection on the phone (permanently)
>>> type: adb devices >>> phone found (shows serial)

on pc in shell >>> type: adb push 2017 /sdcard

on pc in shell >>> type: adb reboot

in TWRP-recovery choose Install (left upper corner)
choose Magisk-uninstaller-20190520.zip from /sdcard/2017
(or Magisk-uninstaller-20190204.zip if you have used Magisk-v18.1.zip)
mark reboot-after-installation
slide blue-white arrow on the bottom to the right

phone boots to twrp-recovery again

choose Reboot (lower right corner)
choose Bootloader

phone reboots in fastboot-mode

fastboot flash boot stock\boot.img
fastboot flash cache stock\cache.img
fastboot flash recovery stock\recovery.img

fastboot flashing lock
>>> push (volume-)up-bottom on phone to confirm

push and hold the power-button on your phone until it turns off

now let it charge to 100%

>>> START NEW <<<
from the beginning

[and: you can skip
the backup-of-personal-data-part
then because you have already done that]

---

file-references: (adresses may look strange, [correct them!]
but new posters is it not allowed to post fully working links)

1. >>> reiboot-for-android.exe / ReiBoot for Android 2.0.0.15
https:##zzz.tenorshare.com/products/reiboot-for-android.html
((even) the free version) installs (on x64) working USB-drivers
which you need to have on your pc before you can do anything else
adb and fastboot didn't find the phone before I had these USB-drivers installed

2. >>> adb and fastboot you can get from here
https:##developer.android.com/studio/releases/platform-tools
for example platform-tools_r28.0.3-windows.zip

3. >>> Magisk-v19.2.zip (or an earlier version like Magisk-v18.1.zip)
https:##github.com/topjohnwu/Magisk/releases/tag/v19.2
(on this official site there is also the uninstaller)

4. >>> no-verity-opt-encrypt-6.0.zip
https:##build.nethunter.com/android-tools/no-verity-opt-encrypt/
(other advanced stuff is also there)

5. >>> MagiskManager-v7.2.0.apk
https:##github.com/topjohnwu/Magisk/releases/
after all flashing you should have this app installed on your phone or you will not get root [in most cases]
they forgot to mention this important thing on https:##unofficialtwrp.com/gome-u7-twrp-3-2-root/
[sometimes this app gets installed with the Magisk.zip, depending on the version of it (or whatever)]

6. >>> Gome_U7_3.2.3.rar (which contains modified boot.img and recovery.img)
https:##zzz.mediafire.com/file/gw83x1y8d25gg5f/Gome_U7_3.2.3.rar
origin: https:##unofficialtwrp.com/gome-u7-twrp-3-2-root/

7. >>> original boot.img and recovery.img (also cache.img) from Gome_2017M27A_MT6757_V01_20180122.zip
for the case that something bad happens you can restore your phone with these
origin: https:##naijarom.com/gome-2017m27a
http:##zzz.mediafire.com/file/29985rqdffoa0m5/Gome_2017M27A_MT6757_V01_20180122.zip

8. >>> Root_Essentials_v2.4.9.apk (to verify your success)
http:##root-essentials.apk.black/
or somewhere else

---

things / files which didn't work (for me) are these:

1. >>> Windows 10 x64 rejects these because of missing signatures
android_cdc_driver.zip
https:##androiddatahost.com/b9cyw
android_vcom_driver.zip
https:##androiddatahost.com/56gty7
latest_usb_driver_windows-3.zip
http:##androidmtk.com/category/drivers

2. >>> starts, but hangs on doing something
maybe a working Windows-x64-vcom-driver is missing
SP_Flash_Tool_v5.1904_Win.zip
http:##spflashtools.com/category/windows
values for readback (as backup) should be
recovery START 108000 LENGTH 1138000
boot START c000000 LENGTH A25000

3. >>> starts, but I don't understand it
it's old and to advanced
SN_Write_Tool_v1.1828.00.zip
http:##snwritetool.com/category/download

4. >>> offers only much less than the twrp-recovery-mode
the official-twrp-app / twrpapp-26.apk
[and also the root-essentials-app offers much more]
The Following User Says Thank You to m2m4m5 For This Useful Post: [ View ] Gift m2m4m5 Ad-Free
 
 
25th May 2019, 09:33 AM |#42  
Junior Member
Thanks Meter: 5
 
More
the boot.img in Gome_U7_3.2.3.rar
seems to be specifically for Magisk-v18.1.zip

something about creating modified-boot-images
on magisk.me lead me to this conclusion

[you can create a new one for Magisk-v19.2.zip
with the instructions for that on Magisk.me]

what I really want to say is
that with Magisk-v18.1.zip
it's maybe really not necessary
to format anything and so on
like I said in my second post
(with the boot.img you have at the moment)
but I'm not sure about that
(and, finally, I don't think that it is so)

(anyway it will be hard to have Magisk-v18.1.zip and
no-verity-opt-encrypt-6.0.zip ready on a accessible
place without formating when needed in twrp-recovery)

---

I have tried my own instructions from post number two
except that I used Magisk-v18.1.zip instead of Magisk-v19.2.zip

the result was partly as described and partly not

root was possible, but only after installing the MagiskManager-app
(which was not pre-installed this time), but formating anything was not required

---

I'm sorry for the instability of the results,
but I'm pretty sure, that I not left the paths of the ways I described
(and set everything proper back before (but maybe this wasn't the case))

maybe I did tiny things in a different way, but they were so small that
I didn't notice it, the difference in results, anyway, seems to be huge

that is also why my third post is also so huge, I tried to pin-point
everything to an exact place, maybe it got to longwinded because of this

but, of course, my third post wouldn't exist, if everything in
the second post was in order, especially that Data-Formating-thing
is still something which is not fully clear, I think it's necessary,
because of removing the encryption, but as I tested it now, it wasn't
The Following User Says Thank You to m2m4m5 For This Useful Post: [ View ] Gift m2m4m5 Ad-Free
9th June 2019, 02:39 PM |#43  
Senior Member
Thanks Meter: 41
 
More
My U7 installed Magisk 19.3
Click image for larger version

Name:	Screenshot_20190609-082901.png
Views:	36
Size:	138.2 KB
ID:	4774031
10th June 2019, 04:50 PM |#44  
Junior Member
Thanks Meter: 0
 
More
I also have GOME U7 and I'm having trouble with the fingerprint scanner, after the screen is off by 20 seconds or more unlocking the phone by fingerprint doesn't seem to work, unless I press a button (power or vol+/-) then immediatly touch the sensor then the phones unlocks, it sort of "sleeps" and I couldn't find any clue on how to fix it, supposedly it's an always on FP scanner, does anyone share the same problem?
11th June 2019, 07:42 PM |#45  
Senior Member
Thanks Meter: 41
 
More
Quote:
Originally Posted by Ben Elias

I also have GOME U7 and I'm having trouble with the fingerprint scanner, after the screen is off by 20 seconds or more unlocking the phone by fingerprint doesn't seem to work, unless I press a button (power or vol+/-) then immediatly touch the sensor then the phones unlocks, it sort of "sleeps" and I couldn't find any clue on how to fix it, supposedly it's an always on FP scanner, does anyone share the same problem?

My is slow, I have to touch the FP about 8-10 seconds to unlock phone.
12th June 2019, 11:23 PM |#46  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by KimLe

My is slow, I have to touch the FP about 8-10 seconds to unlock phone.

Whoa, I never realized I had to keep my finger on the sensor for more than 10 seconds to unlock, what a joke
anyway thanks for the heads up!
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