Database Users

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?

[Resolved] LON-L29 - Cannot install opengapps + FRPlock problem

Hello there,
I have a problem, my Huawei Mate 9 Pro (C636) device does not install OpenGApps when I do, although no error messages appear in TWRP (3.2.1-0)
I have in the logs the installation of the different applications that are running. But during the OS boot (Lineage OS 15.1 OpenKirin) I don't have any of the applications (I tried the pico, nano, and super versions of opengapps).
In addition to this concern, since the last re-installation of my lineageOS firmware, I have the FRPLock option which is activated in my bootloader that I can't uninstall, which prevents me from reinstalling my OS.
How to disable it knowing that I can't reactivate the "OEM Unlock" option in the developer options because, according to android, the OEM lock is already disabled.
Thanks to all those who will try to help me, I have not found anyone else in the same case as me, I get stuck.
{
"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"
}
---
Edit : I've just remove my os, I got no OS and FRP Lock
Can you help me to rollback to the right OS ?
>fastboot getvar rescue_version
rescue_version: rescue0.6
Finished. Total time: 0.066s
> fastboot getvar rescue_phoneinfo
rescue_phoneinfo: LON-L29C636B233
Finished. Total time: 0.004s
Click to expand...
Click to collapse
---
EDIT 2 : I've try to reinstall the update with `Multi-Tool 8`
I've download the 3 updates files from `firmware finder` :
LON-L29C636B378 (8.0.0.378)
LON-L29CC636B378 (8.0.0.378)
--------------------------------------
FullOTA-MF
--------------------------------------
2.97 GB
--------------------------------------
From hi cloud : full/update.zip
From hi cloud : full/public/update_data_full_public.zip
From hi cloud : /full/LON-L29_hw_spcseas/update_full_LON-L29_hw_spcseas.zip
Click to expand...
Click to collapse
But I can't install them via adb or fastboot, how can I install them ?
The update fail when I extract theses files one by one in dload folder of my USB stick.
Can you Help me please ?

Shiishii said:
Hello there,
I have a problem, my Huawei Mate 9 Pro (C636) device does not install OpenGApps when I do, although no error messages appear in TWRP (3.2.1-0)
I have in the logs the installation of the different applications that are running. But during the OS boot (Lineage OS 15.1 OpenKirin) I don't have any of the applications (I tried the pico, nano, and super versions of opengapps).
In addition to this concern, since the last re-installation of my lineageOS firmware, I have the FRPLock option which is activated in my bootloader that I can't uninstall, which prevents me from reinstalling my OS.
How to disable it knowing that I can't reactivate the "OEM Unlock" option in the developer options because, according to android, the OEM lock is already disabled.
Thanks to all those who will try to help me, I have not found anyone else in the same case as me, I get stuck.
---
Edit : I've just remove my os, I got no OS and FRP Lock
Can you help me to rollback to the right OS ?
---
EDIT 2 : I've try to reinstall the update with `Multi-Tool 8`
I've download the 3 updates files from `firmware finder` :
But I can't install them via adb or fastboot, how can I install them ?
The update fail when I extract theses files one by one in dload folder of my USB stick.
Can you Help me please ?
Click to expand...
Click to collapse
I finally succeeded on my own ^^
I'm so happy.
Here the solution to fix it :
To solve the problem if others are in the same situation, I have performed an update via e-Recovery but using the Wifi sharing of my PC. On the connection sharing network card of my PC, I put the DNS given by the "Multi-Tool 8" software via the firmware finder, I took the latest firmware from my smartphone and I launched the search on e-recovery in Wifi.
After long waits, it restarted

Problem unlocking RedMi Pro

Hi everyone!
I hope everyone is warm wherever they are, because it's bleeping cold here!
A friend of mine picked up a Xiaomi Redmi Pro on a business trip to China 2 years ago. He just upgraded with his teleco and tossed me the phone. I got to admit, it looks nice!
However, I'm having trouble unlocking it. If I try with fastboot, I get the following:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
HQAM8DGE69MFQSVG fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock failed - Err:0xffffffff
)
finished. total time: 0.008s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock-go
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock failed - Err:0xffffffff
)
finished. total time: 0.010s
fastboot oem device-info
...
FAILED (remote: unknown command)
finished. total time: 0.004s
The current ROM on the device is MIUI Global 8.0 | Stable 8.0.0.1 (MHQMIDG).
I've tried using different recommended tools to flash a different ROM on to the phone with no successes. Using the MiPCSuite, I get the following error:
{
"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"
}
However, there is no way for me to update the device.
XiaoMiFlash.exe gives me this error:
I go into Developers options and there is no field for Mi Unlock status. I did register the device on Mi and have access the it's cloud storage on the phone.
Smart Phone Flash Tool just sits there with no activity:
Does anyone have any suggestions?
Thanks!
zog

I got this phone as in import like 3 years ago and do wonder why my phone automatically updated to MIUI 10.something while you are stuck on 8.
That said I unfortunately don't have any answers for you. The forum is pretty much dead so you might wanna switch phones soon

I've got same problem. There is no OEM unlock and no Mi unlock status in developer options. Anyone can help?

davinci M1903F10G (locked bootloader) bootloop, it is possible to recover the user data ?

Hello,
i have here a Xiaomi M1903F10G from a good friend, which stuck in a boot loop: phone seems to boot normal, home screen is visible for roundabout 1 second and the phone reboot immediately. Do we have a chance to get the user data (family photos etc.) ?
With Vol+ + Power button i get a "main menu mi-recovery 3.0" with the following options:
Reboot
Wipe Data
Connect with MIAssistant
With Vol- and Power button i can enter Fastboot mode, here are some info:
Bash:
[email protected]$ fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.001s]
Finished. Total time: 0.001s
I can successful enter the EDL mode (i think) via shorting the pins on the main pcb, then phone shows up as "Qualcomm HS-USB QDLoader 9008 (COM6)". According to [GUIDE] How to dump and write back the storage on most of Qualcomm devices i should then use the right firehose file and try to open the partition manager. I tried many different firehose files(see attachments)/storage settings/2 computers(win10x64)/cables(usb-a 2.0/usb-a 3.0/usb-c), i can never successfully open the partition manager.
{
"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"
}
Now the question:what i can do to recover the user data for my friend ? I know i could oem unlock and try to boot into twrp, but as far as i know unlock would wipe all user data. (My friend has also the bill from when he bought the device if that helps).

there is not much you can do on locked bootloader. you can dump raw partitions, that's it. it isn't of any use because of encryption. all you could try is check file system for possible errors (if not metadata encrypted)
have you found loader that worked? try this python script in linux
https://github.com/bkerler/edl

Hello Alecxs,
thanks for your reply. Unfortunately, in the meantime i had to give the phone back to my friend. She told me, she want to try her luck with a commercial data recovery store. Hopefully they are lucky and are able to recover the photos.
Best,
Marcel

Recover photos? Aren't photos synchronised with Google?

Nope.

Then, all data should be backuped. No way to retrieve as data is encrypted anyway

yaro666 said:
Then, all data should be backuped. No way to retrieve as data is encrypted anyway
Click to expand...
Click to collapse
That is not correct, but thanks anyway.