Database Users

Why do I get this icon when trying to root my N4 ?

So I followed the instructions in this link so I could root my N4:
http://www.androidrootz.com/2012/11/how-to-root-nexus-4-on-mac.html
I get this when I reach the point in the video where he instructs me to enter recovery mode.. why ?
{
"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 aren't flashing your recovery properly in bootloader mode.
fastboot flash recovery <nameofrecovery>.img
Choose either: Clockwork Recovery of Team Win Recovery Project (TWRP) as your recovery. Put the .img file in the same folder as fastboot.exe.
I recommend TWRP.
So for example,
http://teamw.in/project/twrp2/129 Scroll down to recovery image method
Place the .img file in the same as fastboot
go into bootloader mode on your phone
fastboot flash recovery openrecovery-twrp-2.3.3.2-mako.img
it should say sending.... then done!
then use vol keys and you should be able to get into bootloader and the android with red ! isnt there.
And thank you for not using the toolkit <3

zephiK said:
You aren't flashing your recovery properly in bootloader mode.
fastboot flash recovery <nameofrecovery>.img
Choose either: Clockwork Recovery of Team Win Recovery Project (TWRP) as your recovery. Put the .img file in the same folder as fastboot.exe.
I recommend TWRP.
So for example,
http://teamw.in/project/twrp2/129 Scroll down to recovery image method
Place the .img file in the same as fastboot
go into bootloader mode on your phone
fastboot flash recovery openrecovery-twrp-2.3.3.2-mako.img
it should say sending.... then done!
then use vol keys and you should be able to get into bootloader and the android with red ! isnt there.
And thank you for not using the toolkit <3
Click to expand...
Click to collapse
This did not work

You have the latest version of Android Fastboot Binary? Bootloader unlocked?
.img file in the fastboot-mac folder
The error is pipe properties. Whatever that is.

BLL00 said:
This did not work
Click to expand...
Click to collapse
Check my post (#13) in this thread. http://forum.xda-developers.com/showthread.php?t=1997684
If you received an ota you have to delete a couple files to get the recovery to stick.
Edit: the pic I quoted didn't show up in the app. I'm not sure what that error means.
Sent from my Nexus 7 using Tapatalk HD

my problem is that after i flash recovery-clockwork-6.0.1.9-mako.img, it refuses to enter cmw and shows the icon I showed in my picture.

BLL00 said:
my problem is that after i flash recovery-clockwork-6.0.1.9-mako.img, it refuses to enter cmw and shows the icon I showed in my picture.
Click to expand...
Click to collapse
When you type fastboot-mac devices... your device shows up right?

zephiK said:
When you type fastboot-mac devices... your device shows up right?
Click to expand...
Click to collapse

BLL00 said:
Click to expand...
Click to collapse
Hmm okay well I don't know how a mac works. I know that you don't need drivers. I'm going to say that it's something wrong with the fastboot binary file. It's the error that you're seeing there. On the guide you used, the error is nonexistant in his picture. Bootloader is unlocked right?
You have the latest version of Android Fastboot Binary? Bootloader unlocked?
.img file in the fastboot-mac folder
The error is pipe properties. Whatever that is.
Click to expand...
Click to collapse
ensure USB debugging is enabled as well.

zephiK said:
Hmm okay well I don't know how a mac works. I know that you don't need drivers. I'm going to say that it's something wrong with the fastboot binary file. It's the error that you're seeing there. On the guide you used, the error is nonexistant in his picture. Bootloader is unlocked right?
Click to expand...
Click to collapse
-Yeah I unlocked my bootloader.
-The pipe properties error is gone, it was just a matter of switching usb ports!
I need to mention that when I flashed the cmw img and hit start on the fastboot menu, IT DID in fact enter cmw, but somewhere in there, I think I've done something wrong and my phone restarted normally. Now, I upload the zip file into the sdcard path and restart my phone into fastboot again, when I hit recovery mode, it then shows that icon!

BLL00 said:
-Yeah I unlocked my bootloader.
-The pipe properties error is gone, it was just a matter of switching usb ports!
I need to mention that when I flashed the cmw img and hit start on the fastboot menu, IT DID in fact enter cmw, but somewhere in there, I think I've done something wrong and my phone restarted normally. Now, I upload the zip file into the sdcard path and restart my phone into fastboot again, when I hit recovery mode, it then shows that icon!
Click to expand...
Click to collapse
Did you read my post?
From efrants android 101 sticky:
I just flashed CWM, but every time I try to boot into CWM, I keep seeing the stock recovery. Why?
If you updated your Android build using an OTA update file (either manually or over-the-air), the update placed two files on your device that re-flash the stock recovery every time you reboot your device. These two files are:
/system/etc/install-recovery.sh <== this is the script that installs the patch file
/system/recovery-from-boot.p <== this is the patch
You have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick.
Click to expand...
Click to collapse

El Daddy said:
Did you read my post?
Click to expand...
Click to collapse
yes i did and if you noticed in the photo i uploaded, there's an iphone under my nexus 4 so I'm VERY new to this. I couldn't find the system path ???

BLL00 said:
yes i did and if you noticed in the photo i uploaded, there's an iphone under my nexus 4 so I'm VERY new to this. I couldn't find the system path ???
Click to expand...
Click to collapse
You have to use a app that has root functionality. Go outside of the /sdcard/ folder and go into /system/
So basically here's what you want to do. By the way good job at switching USB port and having that work.
- Flash CWR
- Flash the superuser zip file to obtain root
- download a file manager that lets you go outside /sdcard/ and then go to the path el daddy mentioned and delete those files.
https://play.google.com/store/apps/...yLDEsImNvbS5qcnVtbXkucm9vdC5icm93c2VyZnJlZSJd here is a file manager you can use.
basically press "..." and go into /system/etc/ find file install-recovery.sh
and/or /system/ and find file recovery-from-boot.p
You have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick.
@El Daddy: He's just a little new. Don't be so harsh (you probably weren't and thought he didn't see it), I mean after all he didn't use the toolkit so, I have respect for him.

the first path is /system/etc/ delete install-recovery.sh
the path to the other file is /system/ find recovery-from-boot.p and delete that
You'll need root access first.
So basically, flash the custom recovery then boot into recovery.
Flash the su.zip file.
Boot into the OS and use a file explorer and delete those files.
Then the custom recovery will stick.
---------- Post added at 06:52 PM ---------- Previous post was at 06:50 PM ----------
zephiK said:
@El Daddy: He's just a little new. Don't be so harsh (you probably weren't and thought he didn't see it), I mean after all he didn't use the toolkit so, I have respect for him.
Click to expand...
Click to collapse
I didn't mean to come off harsh. Sometimes demeanor doesn't translate well through text.

El Daddy said:
the first path is /system/etc/ delete install-recovery.sh
the path to the other file is /system/ find recovery-from-boot.p and delete that
You'll need root access first.
So basically, flash the custom recovery then boot into recovery.
Flash the su.zip file.
Boot into the OS and use a file explorer and delete those files.
Then the custom recovery will stick.
---------- Post added at 06:52 PM ---------- Previous post was at 06:50 PM ----------
I didn't mean to come off harsh. Sometimes demeanor doesn't translate well through text.
Click to expand...
Click to collapse
Yeah agreed. Same goes with sarcasm in text. Just takes some patience with the new people, but I honestly don't mind as this is the Q&A section after all. As long as they're not using the toolkit I won't be upset hehe

zephiK said:
Yeah agreed. Same goes with sarcasm in text. Just takes some patience with the new people, but I honestly don't mind as this is the Q&A section after all. As long as they're not using the toolkit I won't be upset hehe
Click to expand...
Click to collapse
Yep. I'm willing to help anyone, (for as long as it takes) who wants to put the time in and learn. Anyone not using a toolkit is a win for me. :laugh:

El Daddy said:
Yep. I'm willing to help anyone, (for as long as it takes) who wants to put the time in and learn. Anyone not using a toolkit is a win for me. :laugh:
Click to expand...
Click to collapse
Amen, amen. Free training for these people to help others the non-toolkit way so people like us can take a break and relax

Thanks everybody for helping out. I managed to root my phone and this is what I have done to bypass that android logo with it chest open and a "!" floating on top of it:
1-Restarted phone into fastboot mode
2-Flashed CWR's .img
3-Went straight into recovery mode after flashing and was able to enter CMW and complete the procedure.

Next thing you wanna do is GET RID OF THAT TASK MANAGER! Let android work its magic... Enjoy !
Sent from my Nexus 4 using Tapatalk 2

Just to mention when you fastboot flash or use goo manager for twrp recovery it will automatically add .bak to the recovery- from-boot.p file
Sent from my Nexus 4

[help] Buying a bricked tf300

Hello guy,
I have the possiblity to buy a tf300 wich is bricked. And I would like to know if someone could tell me if it's fixable.
The guy says that he unlocked the bootloader, apparently it worked fine and the he flash a TWRP 2.6.3.0 then it went bad. He says the tablet is directly booting up into recovery (at least that's working) that TWRP says "Omb" whatever that means and that he doesn't see any files into recovery, only folders and subfolders (isn't supposed to be normal, I mean doesn't the recovery only display .zip files ??). He says volume down + power doesn't work, adb gives a " protocol failure" and fastboot is waiting for device (but I'm gessing it's normal since he can't boot into menu obviously fastboot is not working).
So what do you think is it fixable?
Thanks

the guy gave me 2 images of the recovery:
{
"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"
}

Apparently the password asked on the screenshots is here because the recovery can't mount the storage partitions. Clearly he flash the wrong recovery. He says that he can't get fastboot because he can't install driver (something I could figure out how to do ).
My last question is, will I get fastboot in this recovery, dispite the storage not mounting and the incompatibility?
if yes then I can do a "fastboot getvar all" to get bootloader version and flash the right recovery? What do you think??
thanks

ayziaa said:
Apparently the password asked on the screenshots is here because the recovery can't mount the storage partitions. Clearly he flash the wrong recovery. He says that he can't get fastboot because he can't install driver (something I could figure out how to do ).
My last question is, will I get fastboot in this recovery, dispite the storage not mounting and the incompatibility?
if yes then I can do a "fastboot getvar all" to get bootloader version and flash the right recovery? What do you think??
thanks
Click to expand...
Click to collapse
that has append to me couple of times( i think 3 -4 times actually) , if you are confident you can get fastboot and ADB working should be really easy to fix. but ull have to flash ASUS blob file then start over like if it was a new tablet

ayziaa said:
Apparently the password asked on the screenshots is here because the recovery can't mount the storage partitions. Clearly he flash the wrong recovery. He says that he can't get fastboot because he can't install driver (something I could figure out how to do ).
My last question is, will I get fastboot in this recovery, dispite the storage not mounting and the incompatibility?
if yes then I can do a "fastboot getvar all" to get bootloader version and flash the right recovery? What do you think??
thanks
Click to expand...
Click to collapse
Yeah I ran into that bug personally and I fixed is in less than 5 minutes with the right setup. Of course, it could be a different situation but there is the chance that it is easily fixable.

Sadly the guy allready sold it. Thank you guy for replying

help
Hi guys....
on my bad luck, looks like I did the same thing.... I had CMB Roms cmb4.4.2 with Philz CWM v6.0.4.5, as I did like this, I went to flash another rom. So, I put the TWRP 2.6 on sdcard with Cromi rom.... flash recovery, reboot and there it stock on recovery and state just like on pictures ...
I can go with ABD but not FASTBOOT... my sdcard is SYSTEM when I mount the system from twpr !!!!
can someone help me ?

srdjank said:
Hi guys....
on my bad luck, looks like I did the same thing.... I had CMB Roms cmb4.4.2 with Philz CWM v6.0.4.5, as I did like this, I went to flash another rom. So, I put the TWRP 2.6 on sdcard with Cromi rom.... flash recovery, reboot and there it stock on recovery and state just like on pictures ...
I can go with ABD but not FASTBOOT... my sdcard is SYSTEM when I mount the system from twpr !!!!
can someone help me ?
Click to expand...
Click to collapse
You put the wrong version of TWRP on your tablet probably? when you restart and it boots into TWRP, on the starting screen you should be able to use fastboot.
---------- Post added at 04:33 PM ---------- Previous post was at 04:31 PM ----------
When it happened to me, it was a bootloader and TWRP conflict: I flashed the jb version instead of the -42 Version. to fix it, I did fastboot reboot bootloader and then got back into android and flashed the correct one from Terminal Emulator. Or you could just flash it from there.

cmendonc2 said:
You put the wrong version of TWRP on your tablet probably? when you restart and it boots into TWRP, on the starting screen you should be able to use fastboot.
---------- Post added at 04:33 PM ---------- Previous post was at 04:31 PM ----------
When it happened to me, it was a bootloader and TWRP conflict: I flashed the jb version instead of the -42 Version. to fix it, I did fastboot reboot bootloader and then got back into android and flashed the correct one from Terminal Emulator. Or you could just flash it from there.
Click to expand...
Click to collapse
nope, I can't use it, if you meen on blue screen when twrp starts, when it boots is the same.... fastboot devices command and it just don't do anything, when twrp boots adb devices turn up : 0123456789ABCDEF recovery
I tryed meny things but I can get it to boot in bootloader with tree options....
when I type fastboot -i 0x0B05 flash c:\Android SDK\sdk\platform-tools\blob
just says <waiting for device> and stays that way.... tryed to reset tab with pin let it boot but nothing ...

srdjank said:
nope, I can't use it, if you meen on blue screen when twrp starts, when it boots is the same.... fastboot devices command and it just don't do anything, when twrp boots adb devices turn up : 0123456789ABCDEF recovery
I tryed meny things but I can get it to boot in bootloader with tree options....
when I type fastboot -i 0x0B05 flash c:\Android SDK\sdk\platform-tools\blob
just says <waiting for device> and stays that way.... tryed to reset tab with pin let it boot but nothing ...
Click to expand...
Click to collapse
What is your OS of your PC??

cmendonc2 said:
You put the wrong version of TWRP on your tablet probably? when you restart and it boots into TWRP, on the starting screen you should be able to use fastboot.
---------- Post added at 04:33 PM ---------- Previous post was at 04:31 PM ----------
When it happened to me, it was a bootloader and TWRP conflict: I flashed the jb version instead of the -42 Version. to fix it, I did fastboot reboot bootloader and then got back into android and flashed the correct one from Terminal Emulator. Or you could just flash it from there.
Click to expand...
Click to collapse
lj50036 said:
What is your OS of your PC??
Click to expand...
Click to collapse
HE's ALIVE ....
:fingers-crossed::fingers-crossed::fingers-crossed:
I''m on WIN7 64...... like I said I boot it up, all I needed is command : abd reboot-bootloader
that cat me in bootloader mode, with http://forum.xda-developers.com/showpost.php?p=44244313&nocache=1&z=9056634965818376
I boot it up on stock 4.2.1 JOP40D.ww_epad-10.6.1.8-20130225
sorry for trouble ...... thanks all for trying to help ....

P8lite has no operating sys. CAN ANYONE HELLP ?

I've P8lite .. Rom be deleted by mistake while trying install SU
Now, phone has no operating system, Trying a lot to install many of
Roms by twrp 3.0.2-0 ( C185B120, C185B525 And C185B560 ) more's the
pity to no end with message "Skipping MD5 check: no MD5 file found"
and "Could not find 'META-INF/com/google/android/update-binary' in the
zip file". "Error installing zip file". "Failed".
Thanks in advance
ALE-L21 UAE

hosamzaiher said:
I've P8lite .. Rom be deleted by mistake while trying install SU
Now, phone has no operating system, Trying a lot to install many of
Roms by twrp 3.0.2-0 ( C185B120, C185B525 And C185B560 ) more's the
pity to no end with message "Skipping MD5 check: no MD5 file found"
and "Could not find 'META-INF/com/google/android/update-binary' in the
zip file". "Error installing zip file". "Failed".
Thanks in advance
ALE-L21 UAE
Click to expand...
Click to collapse
Which rom are you trying to flash?

Suleiman01 said:
Which rom are you trying to flash?
Click to expand...
Click to collapse
thanx 4 reply .. i don't know which the suitable one 4 my phone, i tried to flash C185B120, C185B525 And C185B560

hosamzaiher said:
thanx 4 reply .. i don't know which the suitable one 4 my phone, i tried to flash C185B120, C185B525 And C185B560
Click to expand...
Click to collapse
Isn't it in Update.app format? This format is not supported by TWRP. Install original recovery first then update your phone.

Suleiman01 said:
Isn't it in Update.app format? This format is not supported by TWRP. Install original recovery first then update your phone.
Click to expand...
Click to collapse
I said that 2 my self " amazed " ! .. could u please tell me How ?
linking me to this recovery

hosamzaiher said:
I said that 2 my self " amazed " ! .. could u please tell me How ?
linking me to this recovery
Click to expand...
Click to collapse
You can extract original recovery from official firmware update.app using Huawei update extractor.
---------- Post added at 09:00 AM ---------- Previous post was at 08:59 AM ----------
Suleiman01 said:
You can extract original recovery from official firmware update.app using Huawei update extractor.
Click to expand...
Click to collapse
Link
https://goo.gl/aSMU9M

Suleiman01 said:
You can extract original recovery from official firmware update.app using Huawei update extractor.
---------- Post added at 09:00 AM ---------- Previous post was at 08:59 AM ----------
Link
https://goo.gl/aSMU9M
Click to expand...
Click to collapse
when i've never succeed flashing with TWRP, i converted into CWM
it stops to flash any thing more .. ZIP or IMG files with error message "couldn't un mount sdcard" !

hosamzaiher said:
when i've never succeed flashing with TWRP, i converted into CWM
it stops to flash any thing more .. ZIP or IMG files with error message "couldn't un mount sdcard" !
Click to expand...
Click to collapse
What are you talking about? I didn't say to flash cwm ( clockwork recovery) or twrp (team win recovery project).
Just install the Huawei update extractor on pc.
Extract original recovery from official firmware
Connect your phone to pc and go in fastboot mode
Open minimal adb on pc and type
Fastboot flash recovery recovery.img
Reboot your phone.
Done

Suleiman01 said:
What are you talking about? I didn't say to flash cwm ( clockwork recovery) or twrp (team win recovery project).
Just install the Huawei update extractor on pc.
Extract original recovery from official firmware
Connect your phone to pc and go in fastboot mode
Open minimal adb on pc and type
Fastboot flash recovery recovery.img
Reboot your phone.
Done
Click to expand...
Click to collapse
sorry dear
if i open minimal adb on pc and typ " adb devices " i've nothing till i back to check option " Apply from ADB " from cyanogen recovery then any command order followed by error message " phone closed " !

{
"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"
}
hosamzaiher said:
sorry dear
if i open minimal adb on pc and typ " adb devices " i've nothing till i back to check option " Apply from ADB " from cyanogen recovery then any command order followed by error message " phone closed " !
Click to expand...
Click to collapse

Suleiman01 said:
What are you talking about? I didn't say to flash cwm ( clockwork recovery) or twrp (team win recovery project).
Just install the Huawei update extractor on pc.
Extract original recovery from official firmware
Connect your phone to pc and go in fastboot mode
Open minimal adb on pc and type
Fastboot flash recovery recovery.img
Reboot your phone.
Done
Click to expand...
Click to collapse

https://s18.postimg.org/ic04061op/image.png

Use fastboot command when in fastboot mode, not adb. try fastboot devices

hosamzaiher said:
sorry dear
if i open minimal adb on pc and typ " adb devices " i've nothing till i back to check option " Apply from ADB " from cyanogen recovery then any command order followed by error message " phone closed " !
Click to expand...
Click to collapse
No. Type fastboot devices. Adb is used when phone is powerd on and usb debugging is enabled.
Go in fastboot mode by pressing power button and volume down key. Then attach it to pc and do the steps stated in previous post.

Suleiman01 said:
No. Type fastboot devices. Adb is used when phone is powerd on and usb debugging is enabled.
Go in fastboot mode by pressing power button and volume down key. Then attach it to pc and do the steps stated in previous post.
Click to expand...
Click to collapse
thanx brother, i back TWRP 3.0.2-0 and installed http://huaweip8lite.blogspot.com.eg/2016/07/custom-romtwrpemui-40p8-lite-ale.html?view=sidebar
but the screen stuck on logo

hosamzaiher said:
thanx brother, i back TWRP 3.0.2-0 and installed http://huaweip8lite.blogspot.com.eg/2016/07/custom-romtwrpemui-40p8-lite-ale.html?view=sidebar
but the screen stuck on logo
Click to expand...
Click to collapse
Maybe try flashing official firmware.

Suleiman01 said:
Maybe try flashing official firmware.
Click to expand...
Click to collapse
How to determined the suitable official firmware ?

hosamzaiher said:
How to determined the suitable official firmware ?
Click to expand...
Click to collapse
Which was your last firmware? Flash that firmware's recovery. Then using that recovery update your phone.
---------- Post added at 07:23 PM ---------- Previous post was at 07:23 PM ----------
Suleiman01 said:
Which was your last firmware? Flash that firmware's recovery. Then using that recovery update your phone.
Click to expand...
Click to collapse
Try flashing B120 recovery.

Suleiman01 said:
Which was your last firmware? Flash that firmware's recovery. Then using that recovery update your phone.
---------- Post added at 07:23 PM ---------- Previous post was at 07:23 PM ----------
Try flashing B120 recovery.
Click to expand...
Click to collapse
it seems to be Solved :laugh:
but with a bit trouble ..
first: i used HuaweiUpdateExtractor to extract all files inside, then, did 3 orders on fastboot . . ( flash boot.img - flash recovery.img - flash sys.img )
phone booted on 3.1 Emul with alot stopped functions ( wifi, sim card and so on) finally made a local update using app file stored in SD card for "B560" .. phone started correctly but there was a problem with WIFI wasn't stable .. connect and disconnect !

hosamzaiher said:
it seems to be Solved :laugh:
but with a bit trouble ..
first: i used HuaweiUpdateExtractor to extract all files inside, then, did 3 orders on fastboot . . ( flash boot.img - flash recovery.img - flash sys.img )
phone booted on 3.1 Emul with alot stopped functions ( wifi, sim card and so on) finally made a local update using app file stored in SD card for "B560" .. phone started correctly but there was a problem with WIFI wasn't stable .. connect and disconnect !
Click to expand...
Click to collapse
Update your phone to marshmallow. This might fix wifi issue. By the don't forget to hit thanks button :good: if your problem is solved.

Root question

So how do I root this thing?
Verstuurd vanaf mijn Moto E (4) met Tapatalk

aadvandersteeg said:
So how do I root this thing?
Verstuurd vanaf mijn Moto E (4) met Tapatalk
Click to expand...
Click to collapse
Did you try this?
Lucas Eugene said:
UNLOCK YOUR BOOTLOADER​
WARNING: UNLOCKING YOUR BOOTLOADER VOIDS YOUR WARRANTY.PROCEED AT YOUR OWN RISK.
NOTE: Unlocking the bootloader will Wipe/ factory reset your device, and will delete all personal data from your device such as apps, photos, messages, and settings.
INSTRUCTIONS:
Make sure to take a backup of your entire device data.
Download the Android SDK OR Download the Minimal ADB and Fastboot
Install the latest Motorola USB Drivers on your desktop. Download here.
Put your device in fastboot mode (power off, then press the power and volume down buttons simultaneously).
Open Command Prompt on androidsdk/platform-tools/ (Hold Shift and right click and press open command window here)
Connect your Phone to PC
Type this in the CMD prompt window - fastboot oem get_unlock_data
You will get a return string. Copy it. [Right Click-Mark- Mark the text by pressing the shift key-Now press Ctrl+C]
Paste all the lines together in a notepad. Remove the empty spaces.
Now go to the Motorola Site.Sign in using your Google account or Motorola ID. Scroll down the page and paste the copied string in the field at step #6. Then click on ‘Can my device be unlocked?’, after which a "REQUEST UNLOCK KEY" button will appear at the bottom of page.
To get your unlock key, select the ‘I Agree’ option. Note: You will receive an email with your Unlock Key at the email address you used to log in there.
Important – Copy the 20-character key that Motorola sent you via email. Make sure your device is connected.
Then in CMD type: fastboot devices (To check your device is connected)
Then type: fastboot oem unlock UNIQUE_KEY
NOTE: In above command, replace the word ‘UNIQUE_KEY’ with the unlock code that you got via email. Then hit enter and the unlocking process should begin. Wait for a while and soon you’ll see ‘Bootloader Unlocked’ warning on your Moto E.
To relock the bootloader:
Go to Fastboot and give the command fastboot oem lock
You can always appreciate my work by pressing the Thanks Button.:good:
Good Day
Click to expand...
Click to collapse
---------- Post added at 06:50 AM ---------- Previous post was at 06:48 AM ----------
After you unlock your bootloader you can flash SuperSU in a custom recovery but someone would need to make one of those

mendelgordon said:
Did you try this?
---------- Post added at 06:50 AM ---------- Previous post was at 06:48 AM ----------
After you unlock your bootloader you can flash SuperSU in a custom recovery but someone would need to make one of those
Click to expand...
Click to collapse
No I haven't.
Verstuurd vanaf mijn Moto E (4) met Tapatalk

Root Moto E4 (XT1768)
Here's what worked for me (I have the snapdragon version of this phone):
Follow the following at your own risk!
If you're an expert with rooting, the twrp build that works for this phone is at https://forum.xda-developers.com/g5/development/unofficial-twrp-3-1-0-0-moto-g5-t3574450. Otherwise, details are below.
I'm assuming whoever is reading this has some rooting familiarity.
The short version is:
1. Unlock the boot loader
2. Boot twrp
3. Flash su and no-verify zip
4. Reboot to root'd phone.
0. Prepare
Get the following:
i. Motorola usb drivers: your pc won't talk properly with the device without these. google around for these.
ii. adb and fastboot: used to unlock the bootloader and boot twrp https://developer.android.com/studio/releases/platform-tools.html
iii. su zip: I used phh's https://superuser.phh.me/superuser-r259.zip you can probably get chainfire's or whatever else working
iv. no-verity-opt-encrypt-5.1 zip: https://www.androidfilehost.com/?fid=24459283995297893
v. twrp: this build seems to work for the E4 https://forum.xda-developers.com/g5/development/unofficial-twrp-3-1-0-0-moto-g5-t3574450
vi: (optional) stock roms: in case you need to go back https://androidfilehost.com/?w=files&flid=195327 applying these with RSD lite (if RSD can *actually* detect your phone) or manually (https://www.youtube.com/watch?v=njXQYn53SPc) should work.
0.1 Prepare the phone:
Get developer options on android and turn on "OEM unlocking" and "USB debugging".
Test that your pc can see the phone by running:
Code:
adb devices
0.2 Dump your zips onto the phone:
For this, I dumped the superuser-r259.zip and no-verity-opt-encrypt-5.1 zip onto an sd card (formatted as external).
I didn't try this without an sd card.
0.3 (optional) install the superuser apk
Install the apk before flashing to get root immediately after booting back from twrp.
1. Unlock the boot loader
The post here details how to unlock the motorola boot loader. Keep in mind it will probably void any warranty on the phone. This process involves signing up for a motorola account to get the unlock code.
https://forum.xda-developers.com/showpost.php?p=72878183&postcount=2
2. Boot twrp
Read the warnings in https://forum.xda-developers.com/g5/development/unofficial-twrp-3-1-0-0-moto-g5-t3574450
Because we'll be flashing stuff here, the phone may refuse to boot afterwards since a part of it changed without its knowledge. That's why the no-verify zip is necessary, to bypass this check on boot.
Put your phone in fastboot and run:
Code:
fastboot boot twrp-3.1.0-0-cedric.img
3. Flash su and no-verify zip
In twrp, hit cancel on the decryption screen and start twrp in read.
Go to install, switch to sd card, find the the zip location and flash su then no-verify.
4. Reboot
That should be it. When you reboot back to android, install the superuser apk if you haven't already and feel free to use your root.

Moto e4 is not on the list of the phones that can be unlocked, I have already chatted with moto customer care and they told me its bootloader can't b unlocked yet.

fountain1 said:
Moto e4 is not on the list of the phones that can be unlocked, I have already chatted with moto customer care and they told me its bootloader can't b unlocked yet.
Click to expand...
Click to collapse
So how did mer2017 do it?

These are the important questions.
Like seriously. How the hell.

gogozombiii said:
These are the important questions.
Like seriously. How the hell.
Click to expand...
Click to collapse
I'm saying it obviously works because it's been done
---------- Post added at 10:11 PM ---------- Previous post was at 09:28 PM ----------
I just unlocked my bootloader so it obviously works
---------- Post added at 10:11 PM ---------- Previous post was at 10:11 PM ----------
I just unlocked my bootloader so it obviously works

Now my phone isn't booting, says it can't load the kernel, I flashed the no verify thing but that isn't helping
---------- Post added at 11:49 PM ---------- Previous post was at 11:44 PM ----------
And now after turning it on and off many times it's working!

I still can't figure out how to root it, any ideas? I flashed SuperSU in TWRP many times and it's still not working.

Maybe magisk 13?
Sent from my Moto G (5) Plus using Tapatalk

vettejock99 said:
Maybe magisk 13?
Sent from my Moto G (5) Plus using Tapatalk
Click to expand...
Click to collapse
I tried it, and magisk 12, and pph's superuser. Now what ?

mendelgordon said:
I tried it, and magisk 12, and pph's superuser. Now what ?
Click to expand...
Click to collapse
Kingoroot and kingroot and kingroot pc all don't work

mendelgordon said:
Kingoroot and kingroot and kingroot pc all don't work
Click to expand...
Click to collapse
Thanks for the update
Sent from my Moto G (5) Plus using Tapatalk

I've successfully gotten my Moto e4 rooted. Proof:
{
"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"
}

L551 said:
I've successfully gotten my Moto e4 rooted. Proof:
Click to expand...
Click to collapse
We know it's doable, we aren't looking for proof, we are looking for how to do it ourselves

mendelgordon said:
We know it's doable, we aren't looking for proof, we are looking for how to do it ourselves
Click to expand...
Click to collapse
First, I unlocked the bootloader through motorola's tool. Second, as there is no official TWRP for the e4, I used the Moto G5's TWRP img to BOOT from. (Flashing will not work, boot from it using fastboot) https://forum.xda-developers.com/g5/development/unofficial-twrp-3-1-0-0-moto-g5-t3574450
After in TWRP, I made a backup of stock everything. You'll need it if something goes wrong during the entire process.
After making sure that I was backed up, I then flashed Magisk 13.1. After that successfully flashed, I then flashed this file: https://www.androidfilehost.com/?fid=24459283995297893 . After rebooting (This may take a while), everything looked much the same, and it may look the same for you as well.
In my own case, the Magisk ZIP that I flashed did not install the Magisk Manager. Install that via the APK available in the Magisk 13.1 thread. After I did all that, I had successful root.

L551 said:
First, I unlocked the bootloader through motorola's tool. Second, as there is no official TWRP for the e4, I used the Moto G5's TWRP img to BOOT from. (Flashing will not work, boot from it using fastboot) https://forum.xda-developers.com/g5/development/unofficial-twrp-3-1-0-0-moto-g5-t3574450
After in TWRP, I made a backup of stock everything. You'll need it if something goes wrong during the entire process.
After making sure that I was backed up, I then flashed Magisk 13.1. After that successfully flashed, I then flashed this file: https://www.androidfilehost.com/?fid=24459283995297893 . After rebooting (This may take a while), everything looked much the same, and it may look the same for you as well.
In my own case, the Magisk ZIP that I flashed did not install the Magisk Manager. Install that via the APK available in the Magisk 13.1 thread. After I did all that, I had successful root.
Click to expand...
Click to collapse
I did all that but the magisk zip used to say it didn't Support my boot image and now it's just giving error 255

mendelgordon said:
I did all that but the magisk zip used to say it didn't Support my boot image and now it's just giving error 255
Click to expand...
Click to collapse
Hmm, I tried again and it gave an error that it couldn't mount the magisk image, here's some logs

Magisk won't install if your boot image is anything other than stock. So if you've attempted other methods, you'll need to restore the boot to stock.

[Tutorials] How To Root Lenovo K8 Note & Install TWRP(UnOfficial) + Stock Rom

Warning
Before Proceeding backup your data
TRY at OWN risk I'm NOT Responsibe if you BRICK YOUR DEVICE
Update- This method is tested & working with latest ota update NMB26.54-74
[/CENTER][/B][/SIZE][/COLOR]
IF ANYTHING GOES WRONG Download & Flash Stock ROM
Stock ROM link
SPFlashTool link
Updated Stock ROM 54-74 GDrive - here
New Oreo 27.43-20 Link
Old version Stock ROM Google Drive Link Stock Rom
nvram backup file by @peacelover94 - here
Solution For
>Tool img DL fail
Just check/tick these option in spflashtool settings & Flash stock rom again
{
"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"
}
Video Guide For Stock Rom Flashing - Youtube
How to Flash Stock Rom via Fastboot Method -
1. Open CMD by Shift + Right Click in Folder where your stock firmware .img files are.
2. Reboot to Fastboot Mode by using cmd command
adb fastboot reboot​Or
Switch off then Press & Hold Vol Up + Power button for while once menu appeared Select fastboot by using Vol Up key & confirm by pressing Vol Down Key
3. In fastboot type following command in CMD Window
For checking devices is connected in fastboot enter
fastboot devices​If Connected then proceed following commands
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img​ flashing system takes 10+ mins
fastboot flash data userdata.img
fastboot reboot​
Download & Install ADB from here
First Unlock your bootloader
1. First of all, enable the Developer Option
To Enable the Developer Option, Go to your Settings -> About -> Software Information -> More -> Now Tap on the Build Number 7-8 Times until you see a toast message “Developer option enabled"
2. Go back to settings -> Now you need to enable the OEM Unlock by going to Settings -> Developer Option and Enable OEM Unlock and USB Debugging
3. Now connect your phone to Computer using USB Cable.
4. When you connect your Phone to Computer, please wait until all the drivers get installed.
5. Open a command prompt window by pressing Shift Key + Right Mouse Click.
6. Now type the command below to reboot your phone to bootloader
adb reboot bootloader​7. If you see a pop up to allow USB Debugging on your phone, Click OK.
8. proceed to unlock the bootloader with the following command:
Remember that this step will wipe EVERYTHING off the phone
fastboot oem unlock​Say Yes to unlock bootloader and then it will some time format your data
9. Reboot Your Device , You will see Orange Status bla bla bla Don't panic Its normal thing now setup your device but do not restore backup yet
Flashing TWRP and ROOT
Updated Black Screen Fix TWRP - Download
Old Download TWRP
Download latest Magisk zip from here
Or
SuperSu zip from here
Flahed & Tested SuperSU v2.82 works fine but SafetyNet Fails
Sock Recovery if needed Link
1. Connect your device to PC
2. Open CMD by Shift+Right click open cmd where your TWRP_3.1.1.0.img is downloaded.
3. Reboot to Bootloader by
adb reboot bootloader​4. Now enter following command in fastboot
fastboot flash recovery TWRP_3.1.1.0.img​5. DO NOT USE fastboot reboot
Use "vol up + down + power button" to manually switch off you k8 note, otherwise twrp will restore to stock if you use fastboot reboot command.
6. After Switch Off Press & hold vol up + power button then select recovery by vol up & press vol down key to enter in recovery.
7. Now Wait for 30 Sec/ till phone vibrates, Then press power button + vol up simultaneously until you see twrp lock screen.
8. Just Cancel if It asks for Enter password to decrypt and Allow modification by swipe.
9. If you see internal storage 0mb Then GoTo Wipe and FORMAT DATA once & reboot to recovery
10. GoTo install browse and select Magisk.zip or SuperSU.zip & flash.(optional if needed install Busybox for Android NDK by osm0sis magisk module for busybox)
11. Reboot Enjoy.
Known bug in TWRP-
Battery always shows 50% in TWRP
Video Guide https://youtu.be/HrbppEWlOhs
Join Lenovo K8 Note Development Group on Telegram for direct Conversation Link
WhatsApp Group Link
Enable Wireless Display/MiraCast Magisk Module - Video
Thanks to:
@andy_zhang - for stock rom post link
and me @ysalunke007 for TWRP
NEXT CUSTOM ROM

Big Thanks for the Tutorial. If anything happens wrong while rooting like boot loop or something worse, is there stock rom or firmware to flash or push through adb ?

Yes
peacelover94 said:
Big Thanks for the Tutorial. If anything happens wrong while rooting like boot loop or something worse, is there stock rom or firmware to flash or push through adb ?
Click to expand...
Click to collapse
yes, there is stock ROM
link also provided in this post end.
btw here's direct link Stock ROM
FlashTool link

ysalunke007 said:
yes, there is stock ROM
link also provided in this post end.
btw here's direct link Stock ROM
FlashTool link
Click to expand...
Click to collapse
Thank you very much. The flash tool link does not seems to work. Hope its SP flash tool you are talking about.

flash via adb fastboot methoad i have succesfully flash adb method
peacelover94 said:
Big Thanks for the Tutorial. If anything happens wrong while rooting like boot loop or something worse, is there stock rom or firmware to flash or push through adb ?
Click to expand...
Click to collapse

Nice Job
Finally rooting tutorial for Lenovo K8 Note has become available.

Does SuperSu work fine?

Anas Rahman said:
Does SuperSu work fine?
Click to expand...
Click to collapse
Not tested by me but some user says in original rom post that he flashed superSU from old twrp also works fine.

peacelover94 said:
Thank you very much. The flash tool link does not seems to work. Hope its SP flash tool you are talking about.
Click to expand...
Click to collapse
Yes it's SP flash tool but you can use adb fastboot also

ysalunke007 said:
Not tested by me but some user says in original rom post that he flashed superSU from old twrp also works fine.
Click to expand...
Click to collapse
I'll confirm it tomorrow

ysalunke007 said:
Yes it's SP flash tool but you can use adb fastboot also
Click to expand...
Click to collapse
Please tell me how to flash firmware.Im new to this device firmware flashing

lenrussel said:
Please tell me how to flash firmware.Im new to this device firmware flashing
Click to expand...
Click to collapse
It's easy bro check this guide
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Fastboot Guide
http://www.stupdroid.com/2016/08/flash-stock-rom-via-fastboot-on-android.html?m=1

Does the rom link given here unzips perfectly?
Because i saw in another thread of Lenovo K8note titled firmware, users unable to unzip due to error in system img. Also downloading from baidu needs a user id. If its possible could you or anyone else reading this upload it in some other online storage drive. Im little bit worried about getting a worse situation while rooting. Even if it goes wrong i can use the stock firmware to make it back.

peacelover94 said:
Does the rom link given here unzips perfectly?
Because i saw in another thread of Lenovo K8note titled firmware, users unable to unzip due to error in system img. Also downloading from baidu needs a user id. If its possible could you or anyone else reading this upload it in some other online storage drive. Im little bit worried about getting a worse situation while rooting. Even if it goes wrong i can use the stock firmware to make it back.
Click to expand...
Click to collapse
There is mega download link available too
https://forum.xda-developers.com/an...8note-original-firmware-t3679499/post73946000

lenrussel said:
There is mega download link available too
https://forum.xda-developers.com/an...8note-original-firmware-t3679499/post73946000
Click to expand...
Click to collapse
Thanks for the reply. Anyhow got a work around for downloading from baidu using chrome extension, without account. Just wanted to confirm whether the firmware zip is working fine. If some one used it and been successful, please do tell me.

ysalunke007 said:
It's easy bro check this guide
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Fastboot Guide
http://www.stupdroid.com/2016/08/flash-stock-rom-via-fastboot-on-android.html?m=1
Click to expand...
Click to collapse
Do i have to unlock bootloader again after flashing the firmware in order to root the device?

lenrussel said:
Do i have to unlock bootloader again after flashing the firmware in order to root the device?
Click to expand...
Click to collapse
Yes, I think so. Anyhow there is no need to unlock oem again if you are flashing the rom via TWRP. Anyhow let someone confirm about it.

peacelover94 said:
Yes, I think so. Anyhow there is no need to unlock oem again if you are flashing the rom via TWRP. Anyhow let someone confirm about it.
Click to expand...
Click to collapse
There is a error while extracting zip file of the firmware .just checked, I downloaded it from mega.i want to confirm if its the same for baidu also

lenrussel said:
Do i have to unlock bootloader again after flashing the firmware in order to root the device?
Click to expand...
Click to collapse
No need to unlock bootloader again if you use fastboot method to flash stock firmware , & for spflashtool I'm not sure but I think it remains unlocked

lenrussel said:
There is a error while extracting zip file of the firmware .just checked, I downloaded it from mega.i want to confirm if its the same for baidu also
Click to expand...
Click to collapse
No error while extracting firmware downloaded from baidu