Database Users

Kindle fire utility prob [Solved]

hello all, I seem to be having a prob with KFU, im trying to install recovery per video instructions.
***********************************************
* Kindle Fire Utility 0.9.1 *
***********************************************
'findstr' is not recognized as an internal or external command,
operable program or batch file.
ADB Status: Online
ADB Rooted: Yes
Boot Status: Unknown
Please make a selection or hit ENTER to exit:
This is happening with 0.9.2 and 0.9.1
I tryed both
I read that someone else is or was having same issue.
findstr.exe is in the system32 folder also
{
"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"
}

a good practice is to put kfu 0.9.2 to c:\ and rename it to "kfu" that it is c:\kfu
to use it with stock 6.2.2 and burritoroot3 you have to patch the run.bat:
http://forum.xda-developers.com/showpost.php?p=21749205&postcount=792

Ok I will try that, um I have another question.
Is it ok that I flashed firefirefire on before I put the recovery on it.
Or do I have to remove it before I put the recovery on?
Thks

cloud71 said:
Ok I will try that, um I have another question.
Is it ok that I flashed firefirefire on before I put the recovery on it.
Or do I have to remove it before I put the recovery on?
Thks
Click to expand...
Click to collapse
it is ok but twrp will overwrite fff with a older version cause it has it integrated in the installation - would reinstall fff 1.2 afterwards

ok thankyou all very much, I will look for the newer version when recovery is on.
whats weaid now is when the adb server starts up now it says its an older version and needs to be updated. I guess as long as it works I'm not going to cross that bridge LOL.
God Bless

cloud71 said:
ok thankyou all very much, I will look for the newer version when recovery is on.
whats weaid now is when the adb server starts up now it says its an older version and needs to be updated. I guess as long as it works I'm not going to cross that bridge LOL.
God Bless
Click to expand...
Click to collapse
would use only the tools folder of kfu - there are all commands you ever need and no weird messages ...
if your question is answered or your problem is solved
please mark the subject of the topic (edit first post) with [Solved]

Looks like im still having the same prob.
***********************************************
* Kindle Fire Utility 0.9.2 *
***********************************************
'findstr' is not recognized as an internal or external command,
operable program or batch file.
ADB Status: Online
ADB Rooted: Yes
Boot Status: Unknown
Please make a selection or hit ENTER to exit:
I downloaded and patched the run.bat
still getting the samething

findstr.exe is a system command located in c:\windows\system32 !
would search over your c:\ if it is even there
how do you call the run.bat ?
open a (elevated) command prompt, cd to c:\kfu, type "run.bat" and enter
edit: just saw in your first post that it is there - maybe reregister it:
1) Click Start
2) Click Run
3) Type regsvr32 findstr.exe
4) Press Enter
5) Restart your computer
or "c:\windows\system32" is'nt in your "path" variable - type "path" at a command prompt and check
or it is corrupted (ie by maleware) - then you have to reinstall/repair it from system cd

Yes the findstr is in the system32 folder I chked.
I ran run.bat by clicking on it and have also ran it by using cmd prompt
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Mac>cd C:\KFU
C:\KFU>run.bat
I still get this :
***********************************************
* Kindle Fire Utility 0.9.2 *
***********************************************
'findstr' is not recognized as an internal or external command,
operable program or batch file.
ADB Status: Online
ADB Rooted: Yes
Boot Status: Unknown
Please make a selection or hit ENTER to exit:
not sure what is going wrong errrrr

just updated my last post ...
tried to register it ? - checked path variable ? - do simply "findstr -?" from command line ?

YAY putting that in the path var. worked thks bro
***********************************************
* Kindle Fire Utility 0.9.2 *
***********************************************
1 Bootmode Menu
2 BurritoRoot (Temporary)
3 Install Permanent Root with Superuser
4 Obtain Stock update.zip
5 Install latest TWRP Recovery
6 Extras
0 Recheck Device Status
ADB Status: Online
ADB Rooted: Yes
Boot Status: 4000
Please make a selection or hit ENTER to exit:
fingers and toes crossed

glad to help ...
please mark the subject of the topic (edit first post) with [Solved]

Ok I did the backup, now the twrp is at 2.0, should I update it?
or can I just stay at this version, and also if I do update it. do I just install the update over top of the 2.0?
at some point I plan on putting a different rom like cm6 or cm7 or something else on it.
Oh and can I boot to recovery without it being plugged into pc and do the stuff on it without the pc now?

cloud71 said:
Ok I did the backup, now the twrp is at 2.0, should I update it?
or can I just stay at this version, and also if I do update it. do I just install the update over top of the 2.0?
at some point I plan on putting a different rom like cm6 or cm7 or something else on it.
Oh and can I boot to recovery without it being plugged into pc and do the stuff on it without the pc now?
Click to expand...
Click to collapse
there is only 1 twrp available and this is 2.0
you may want to install fff again that you have the newest version : http://forum.xda-developers.com/showthread.php?t=1369405
and you can boot into recovery by pressing the power button repeatently till it gets orange at startup (the yellow triangle)

Thkyou very much for all your help, couldnt have done it without you thanks

[GUIDE] CWM/TWRP ADB Sideload

Here's small guide about ClockworkMod Recovery / Team Win Recovery Project feature "ADB Sideload".
The example is done with TWRP but the basic idea with CWM is pretty much the same.
Required tools for uploading:
- Samsung Galaxy S3 mini with CWM/TWRP recovery
- Android SDK -> DOWNLOAD FOR OTHER PLATFORMS -> installer_r22.3-windows.exe
- Desired ROM to be installed, in this example it's DMod V6
The steps:
1) Install the SDK, start it and select "Android SDK Tools" and "Android SDK Platform-tools" and then "Install 2 packages"
{
"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"
}
2) Locate the "adb.exe" file that was installed with "Android SDK Platform-tools", It's usually in "C:\Program Files (x86)\Android\android-sdk\platform-tools". I decided to copy the "platform-tools" folder into c:\ and renamed it to "adb".
3) Copy the ROM you desire to install in the "adb" folder
4) Boot the phone into recovery, and select "Advanced":
5) Plug the USB cable in
6) Start "Command Prompt" in Windows (Start -> type in "cmd" to search box and select "cmd.exe")
7) Type: "cd \adb"
8) Type: "adb kill-server"
9) Type: "adb usb"
HTML:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
restarting in USB mode
10) Type: "adb devices"
HTML:
List of devices attached
sh3d7h3dj631f6a7 recovery
11) Select the "ADB Sideload" from the phone, swipe to start
12) Type: "adb devices"
HTML:
List of devices attached
sh3d7h3dj631f6a7 sideload
13) Type: "adb sideload DModV6.zip"
Wait for the upload to finish and you are done! Have fun installing DMod V6
WAIT! There's this error with adb:
HTML:
error: closed
1) Cancel the "ADB Sideload" from phone, return to "Advanced" menu
2) Read the guide again from step 8 and obey them!

can i fix this brick with side load?
http://img547.imageshack.us/img547/7113/4jmo.jpg

wareca said:
can i fix this brick with side load?
http://img547.imageshack.us/img547/7113/4jmo.jpg
Click to expand...
Click to collapse
Sideload might not be option for that because that is stock recovery.
Looks like you have lost atleast your cache partition, you might need to use Odin and reflash the whole phone again with PDA option.

I get the error no devices found. Any ideas how I can fix that?
Thanks

Thank you !
bro thanks to you you save me from 25 dollars i wish if someday i become rich you are on my mind i will donate you :angel:

mikma80 said:
Here's small guide about ClockworkMod Recovery / Team Win Recovery Project feature "ADB Sideload".
The example is done with TWRP but the basic idea with CWM is pretty much the same.
Required tools for uploading:
- Samsung Galaxy S3 mini with CWM/TWRP recovery
- Android SDK -> DOWNLOAD FOR OTHER PLATFORMS -> installer_r22.3-windows.exe
- Desired ROM to be installed, in this example it's DMod V6
The steps:
1) Install the SDK, start it and select "Android SDK Tools" and "Android SDK Platform-tools" and then "Install 2 packages"
2) Locate the "adb.exe" file that was installed with "Android SDK Platform-tools", It's usually in "C:\Program Files (x86)\Android\android-sdk\platform-tools". I decided to copy the "platform-tools" folder into c:\ and renamed it to "adb".
3) Copy the ROM you desire to install in the "adb" folder
4) Boot the phone into recovery, and select "Advanced":
5) Plug the USB cable in
6) Start "Command Prompt" in Windows (Start -> type in "cmd" to search box and select "cmd.exe")
7) Type: "cd \adb"
8) Type: "adb kill-server"
9) Type: "adb usb"
HTML:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
restarting in USB mode
10) Type: "adb devices"
HTML:
List of devices attached
sh3d7h3dj631f6a7 recovery
11) Select the "ADB Sideload" from the phone, swipe to start
12) Type: "adb devices"
HTML:
List of devices attached
sh3d7h3dj631f6a7 sideload
13) Type: "adb sideload DModV6.zip"
Wait for the upload to finish and you are done! Have fun installing DMod V6
WAIT! There's this error with adb:
HTML:
error: closed
1) Cancel the "ADB Sideload" from phone, return to "Advanced" menu
2) Read the guide again from step 8 and obey them!
Click to expand...
Click to collapse
getting this error while in recovery mode in adb
E:\Minimal ADB and Fastboot>adb usb
error: device not found
Edit: installed drivers from pdanet. done now. thanks

manikumary said:
getting this error while in recovery mode in adb
E:\Minimal ADB and Fastboot>adb usb
error: device not found
Edit: installed drivers from pdanet. done now. thanks
Click to expand...
Click to collapse
what drivers????????

bauerpower said:
what drivers????????
Click to expand...
Click to collapse
Dunoo:silly:
Done Google, Found those drivers, then worked.

bauerpower said:
what drivers????????
Click to expand...
Click to collapse
Oh the usual drivers required with windows. Best to install KIES, the drivers come with that.
Or http://developer.samsung.com/android/tools-sdks/Samsung-Andorid-USB-Driver-for-Windows
(LOL! "Samsung Andorid USB Driver for Windows")

Saved time and money
Thanks this really work, along with naked android driver that someone suggested. i saved time, money, and not having to replace my phone. now im full working and have the custom recovery working now, thanks a LOT!!

my command prompt is showing error
my command prompt shoows error in last when i send mt rom to my device
adb sideload rom.zip
it shows error
100 % but error sending

Mr22Me said:
my command prompt shoows error in last when i send mt rom to my device
adb sideload rom.zip
it shows error
100 % but error sending
Click to expand...
Click to collapse
And you got custom recovery installed? Not the default?

adb devices offline
hi, allways when i type adb usb and press enter he does this
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device offline

vdries said:
hi, allways when i type adb usb and press enter he does this
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device offline
Click to expand...
Click to collapse
Make sure the following:
1) Your phone is rooted and up and running in custom recovery (TWRP is better imo)
2) You have proper drivers installed in your Windows (KIES does this trick)
3) You have USB debugging enabled in the phone

after i do the guide it has install the rom i pushed but now when the phone get on
the LG logo showed and the rom logo showed and stuck there

THANK YOU! exactly what i was looking for and needed after completely "nuking" my phone of all data with TWRP.

when I type adb devices the second time when it should say sideload it says host instead??

true hard brick fix
wareca said:
can i fix this brick with side load?
http://img547.imageshack.us/img547/7113/4jmo.jpg
Click to expand...
Click to collapse
not sure about that but a true hard brick (nothing only activity is after pushing to two pins in the back right against mobo red light will come on for a few sec when plugged in other then that NO LIFE ) http://forum.xda-developers.com/showthread.php?t=2581166 (NOT MY WORK BUT I CAN VERIFY IT WORKS
ACTUALLY THIS IS THE LINK AND FILES I USED BUT TRUST XDA FOR ALL YOUR PROBLEMS....https://www.youtube.com/watch?v=wZEKzglmjtY

Nitefall said:
when I type adb devices the second time when it should say sideload it says host instead??
Click to expand...
Click to collapse
Sounds like you don't have sideload started from the custom recovery?

I have HTC One M7 and proper drivers (fastboot works). When I type
adb usb
I receive "error: device not found"
I just can get the bootloader, it can't load system. It is S-ON.
I found the way to do it here https://www.youtube.com/watch?v=PUjQnwULGzs

Lost ~180mb of RAM after flashing custom rom? Solution here.

This guide is for Mipad 1(mocha)
Download DiskInfo, if it says that you have only 1.8 GB of RAM, than this guide is for you.
1. You need to have ADB and fastboot drivers installed.
2. Download the nvboot.bin file, that is attached.
3. Put it into your ADB folder.
4. Enable USB debug on your device.
5. Open cmd in ADB folder and
A) Check if your device is attached properly.
Code:
adb devices
If it shows device status as 'device' everything is OK.
B)
Code:
adb reboot bootloader
If you see a rabbit on the screen, than everything is OK.
C) Write
Code:
fastboot flash nvtboot+nvtboot1 nvtboot.bin
C) Check the cmd's output, if you see OKAY there two times, than everything is OK.
D) Reboot.
E) ...
F) Profit!

Here is a file in an archive. Extract it to ADB folder.

correction
Star_king12 said:
Download DiskInfo, if it says that you have only 1.8 GB of RAM, than this guide is for you.
1. You need to have ADB and fastboot drivers installed.
2. Download the nvboot.bin file, that is attached.
3. Put it into your ADB folder.
4. Enable USB debug on your device.
5. Open cmd in ADB folder and
A) Check if your device is attached properly.
Code:
adb devices
If it shows device status as 'device' everything is OK.
B)
Code:
adb reboot bootloader
If you see a rabbit on the screen, than everything is OK.
C) Write
Code:
fastboot flash nvboot+nvboot1 nvboot.bin
C) Check the cmd's output, if you see OKAY there two times, than everything is OK.
D) Reboot.
E) ...
F) Profit!
Click to expand...
Click to collapse
Please, may be do you have a little error in last command line?.
where you put: fastboot flash nvboot+nvboot1 nvboot.bin
I must use: nvtboot in all words

JAMELGO said:
nvtboot in all words
Click to expand...
Click to collapse
Fixed.

Star_king12 said:
Fixed.
Click to expand...
Click to collapse
Ok!

Thanks for the guide

is this for mi pad 1 ????

ayushagarwal9753 said:
is this for mi pad 1 ????
Click to expand...
Click to collapse
Yup ;-;

Works! RAM went from 1.7 to 1.9Gigs.
Remember to unzip the file to get the .bin version.

not able
my device is not found in adb devices..kindly upload the required drivers for mi pad and clearly explain the procedure..whether the mi pad is to be put in fastboot or not..

rj4jhtconev said:
my device is not found in adb devices..kindly upload the required drivers for mi pad and clearly explain the procedure..whether the mi pad is to be put in fastboot or not..
Click to expand...
Click to collapse
I will not upload drivers here. The procedure is explained as clearly as possible.

Great!
Star_king12 said:
This guide is for Mipad 1(mocha)
Download DiskInfo, if it says that you have only 1.8 GB of RAM, than this guide is for you.
1. You need to have ADB and fastboot drivers installed.
2. Download the nvboot.bin file, that is attached.
3. Put it into your ADB folder.
4. Enable USB debug on your device.
5. Open cmd in ADB folder and
A) Check if your device is attached properly.
Code:
adb devices
If it shows device status as 'device' everything is OK.
B)
Code:
adb reboot bootloader
If you see a rabbit on the screen, than everything is OK.
C) Write
Code:
fastboot flash nvtboot+nvtboot1 nvtboot.bin
C) Check the cmd's output, if you see OKAY there two times, than everything is OK.
D) Reboot.
E) ...
F) Profit!
Click to expand...
Click to collapse
It worked! :fingers-crossed:
{
"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"
}

edconocerte said:
This guide is for Mipad 1(mocha)
Download DiskInfo, if it says that you have only 1.8 GB of RAM, than this guide is for you.
1. You need to have ADB and fastboot drivers installed.
2. Download the nvboot.bin file, that is attached.
3. Put it into your ADB folder.
4. Enable USB debug on your device.
5. Open cmd in ADB folder and
A) Check if your device is attached properly.
If it shows device status as 'device' everything is OK.
B)
If you see a rabbit on the screen, than everything is OK.
C) Write
It worked! :fingers-crossed:
Click to expand...
Click to collapse
Having 1.9GB and not 2GB is normal in custom ROM?

Jankev said:
Having 1.9GB and not 2GB is normal in custom ROM?
Click to expand...
Click to collapse
Yep. Stock and custom ROM show 1.9GB.

Star_king12 said:
Fixed.
Click to expand...
Click to collapse
If the system1 and 2 are merged what should I use of below?
Code:
fastboot flash nvtboot+nvtboot1 nvtboot.bin
Code:
fastboot flash nvtboot nvtboot.bin

Flashing Factory 8.1 - After ADB Reboot Bootloader: Error "Connect USB Data Cable"

Flashing Factory 8.1 - After ADB Reboot Bootloader: Error "Connect USB Data Cable"
GOAL: flash factory stock 8.1 image on phone purchased from Swappa. Why? To eliminate any possibility of any lingering software (e.g. Cerberus) that might have been installed by the previous owner.
PROBLEM: after issuing command ADB Reboot Bootloader at Windows terminal, the phone boots in to bootloader mode, but says, Connect USB Data Cable despite the fact that it is, in fact connected to my Win10 computer via a USB cable (the very same one that forced the phone to reboot into bootloader mode).
{
"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"
}
Of course, I do notice that the above screen says, device is LOCKED, but my belief is that the bootloader on this phone is UNlocked. Why? Two reasons. (1) Because that's the way it was described in the Swappa listing. (2) the Developer Options \ OEM unlocking is set to "allow the bootloader to be unlocked."
By the way, if (while the phone is in bootloader mode) I run the flash-all.bat script, I get these errors:
C:\Users\me>"C:\BIN\angler-opm1.171019.011-factory-39448337\angler-opm1.171019.011\flash-all.bat"
error: cannot load 'bootloader-angler-angler-03.78.img': No such file or directory
rebooting into bootloader...
OKAY [ 0.022s]
finished. total time: 0.023s
error: cannot load 'radio-angler-angler-03.85.img': No such file or directory
rebooting into bootloader...
OKAY [ 0.022s]
finished. total time: 0.023s
W/ziparchive( 6844): Unable to open 'image-angler-opm1.171019.011.zip': No such file or directory
error: failed to open zip file 'image-angler-opm1.171019.011.zip': I/O error
Press any key to exit...
Click to expand...
Click to collapse
With the phone in normal mode (booted up normally), and then run ADB devices the system returns
List of devices attached
myserialnumber device
Click to expand...
Click to collapse
so I know that the computer and phone are talking. Immediately after that, if I try to run the same (flash-all.bat) command when the phone is not in bootloader mode, I get back waiting for any device as though computer and phone cannot communicate.
I am so confused. :cyclops:
What am I doing wrong?

UPDATE:
I just realized that I needed to issue the command fastboot flashing unlock at a Windows terminal prompt, then select (on the phone) to unlock the bootloader.
Furthermore.... I just noticed that in the Windows Termminal, I needed to navigate to the folder containing the IMG file to be flashed before running the flash-all.bat script. Since that location wasn't in my Windows 10 computer's PATH command, the script couldn't "see" the IMG file, which explains the errors above.

UPDATE # 2 - Solved
1. At windows terminal, issue command "adb devices" (to verify that computer and phone are connected).
2. At windows terminal, issue command "fastboot flashing unlock" then on phone choose the option to unlock bootloader.
3. At windows terminal, issue command adb reboot bootloader or on phone, with phone off, press power and volume-down simultaneously.
4. At windows terminal, with prompt located at the same drive and folder where the IMG you want to flash is located, run the flash-all.bat script.
5. After new OS is installed and phone reboots, then at Windows Terminal, , issue command "fastboot flashing lock" then on phone choose the option to re-lock bootloader. This will wipe the phone, reinstall the OS and reboot the phone.
There may be (probably are) smarter and better ways to skin this cat. If so, I hope that someone smarter than me will add that in the comments to help anyone who reads this thread.

[ROOT] Magisk for the Huawei Y6 (2018) - Root for Atomu

Root for Atomu​Patched Ramdisks for the HUAWEI Y6 (2018)​
{
"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"
}
This is a patched ramdisk for the Huawei Y6 (2018) that installs Magisk.
I'll keep this thread updated when Magisk updates.​
Supported Devices
(As tested by @Thespartann and Runner85sx)
ATU-L22 - Main device
ATU-L21 - should work as it uses the same ramdisk
More devices supported:
ATU-L11
ATU-L23
ATU-L31
ATU-L42
YGN-AL00
YGN-L21
YGN-L22
YGN-L23
YGN-L41
YGN-L42
YGN-L51
YGN-L61
YGN-TL10
Known issues
Reports tell that it's bootlooping on devices with firmware later than 8.0.0.143.
Installing modules on AOSP renders it bootlooping.
Before You Flash
Follow this guide to backup every partition before you mess up your device.
https://forum.xda-developers.com/huawei-y6/development/guide-backup-current-partitions-t3853831
Thanks @pascua28
How to Install
YOUR BOOTLOADER MUST BE UNLOCKED FIRST!
SEE HERE FOR INSTRUCTIONS
Download the latest Magisk ramdisk from the downloads section.
Reboot to fastboot using ADB
Code:
adb reboot bootloader
or turn off your device, then hold the power and volume down buttons until Fastboot shows up.
After that go into fastboot and type:
Code:
fastboot flash ramdisk ATOMU-Magisk_<xx.x>_<yyyyyyy>.img
Replace xx.x with Magisk version (e.g. 17.1) and yyyyyyy with the build date (e.g. 20181013)
Now type
Code:
fastboot reboot
Wait your phone to boot and now it should be rooted.
(You might have to install Magisk Manager separately from the Magisk thread)
How to Recover/Uninstall
If you have been bootlooped/it doesn't work/you're experiencing issues, simply do the following
Download the stock ramdisk from the downloads section.
Reboot to fastboot using ADB
Code:
adb reboot bootloader
or turn off your device, then hold the power and volume down buttons until Fastboot shows up.
After that go into fastboot and type:
Code:
fastboot flash ramdisk ramdisk.img
Now type
Code:
fastboot reboot
Wait your phone to boot and now it should be recovered and un-rooted.
Kernel.img, if you're stuck at the boot screen (not the animation):
Flash on kernel (instead of ramdisk).
https://mega.nz/#!KAoR3KYT!ufZv7ZbBs...OpUeIAFgUohKE0
(Tested on ATU-L22, EMUI 8.0.0.143)
(Tested on ATU-L22, Pixel Experience)
Download
Builds are available from my Google Drive:
Latest: Magisk v17.1 (20181013)
https://drive.google.com/open?id=1j_Eo6EOybB0AD6fwxnEycyseA2wdE_Jm​
Stock Ramdisk:
https://mega.nz/#!bdwTiD5I!STHIWQrCle_nCoPKe4_Mgvo9z_Qn4Etnnhbt0fmG1PE​
Thanks to
@Thespartann for introducing a method to root the Huawei Y6 (2018) and the stock ramdisk.
Runner85sx for testing ramdisk compatibility.

Please support development by donating.
Donate via PayPal
It works!

The ramdisk was from 8.0.0.142 or 8.0.0.143?

sh0w 0f said:
The ramdisk was from 8.0.0.142 or 8.0.0.143?
Click to expand...
Click to collapse
The ramdisk is of unknown version (presumably, that's from an older version) but this is tested with my ATU-L22 with EMUI 8.0.0.143.

TenSeventy7 said:
The ramdisk is of unknown version (presumably, that's from an older version) but this is tested with my ATU-L22 with EMUI 8.0.0.143.
Click to expand...
Click to collapse
Ok thanks

Before you flash anything, read my guide here: https://forum.xda-developers.com/huawei-y6/development/guide-backup-current-partitions-t3853831 that way, you can have the original partitions in case you want to go back

pascua28 said:
Before you flash anything, read my guide here: https://forum.xda-developers.com/huawei-y6/development/guide-backup-current-partitions-t3853831 that way, you can have the original partitions in case you want to go back
Click to expand...
Click to collapse
Thanks! Added to the OP.
Any news on your kernel?

TenSeventy7 said:
Thanks! Added to the OP.
Any news on your kernel?
Click to expand...
Click to collapse
Kernel is more stable now. I switched to clang compiler now and spent almost 4 damn hours trying to fix errors. Will upload tomorrow

pascua28 said:
Kernel is more stable now. I switched to clang compiler now and spent almost 4 damn hours trying to fix errors. Will upload tomorrow
Click to expand...
Click to collapse
Nice! Does it support 8.0.0.143 now?

TenSeventy7 said:
Nice! Does it support 8.0.0.143 now?
Click to expand...
Click to collapse
Not yet. My last system update failed and now it requires me to download 2.5GB which is expensive

TenSeventy7 said:
Root for Atomu
Patched Ramdisks for the HUAWEI Y6 (2018)
This is a patched ramdisk for the Huawei Y6 (2018) that installs Magisk.
I'll keep this thread updated when Magisk updates
Click to expand...
Click to collapse
Wew

Updated the OP with AOSP ISSUES ON THE RAMDISKS.
Installing any module will result to bootlooping. I'm already looking for a fix.

Hi! I've created a Telegram hub for Huawei Y6 (2018) users.
Report bugs, issues, ask a fellow user, or just talk about any kind of stuff.
Check it out here:
https://t.me/Y62018_EN

I'm currently running v145. Will it be OK?

gremory22 said:
I'm currently running v145. Will it be OK?
Click to expand...
Click to collapse
Don't for now. Reports tell that it isn't booting up on B145.

Is there any way..
TO get Bootloader Unlock code freee ?

enrich-xda said:
TO get Bootloader Unlock code freee ?
Click to expand...
Click to collapse
Unfortunatly Bootloader is unlock for pay only(

D:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash ramdisk C:\Users\KYL3\Downloads\ATOMU-Magisk_17.1_20181013.img
target reported max download size of 535822336 bytes
sending 'ramdisk' (11420 KB)...
OKAY [ 0.362s]
writing 'ramdisk'...
OKAY [ 0.174s]
finished. total time: 0.543s
D:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.002s
but still no root access hmmmm

ex3da.ex3 said:
D:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash ramdisk C:\Users\KYL3\Downloads\ATOMU-Magisk_17.1_20181013.img
target reported max download size of 535822336 bytes
sending 'ramdisk' (11420 KB)...
OKAY [ 0.362s]
writing 'ramdisk'...
OKAY [ 0.174s]
finished. total time: 0.543s
D:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.002s
but still no root access hmmmm
Click to expand...
Click to collapse
Have you installed MagiskManager-v6 apk to manage root access?

Will this work on ATU-LX3?