Database Info

[Q] HTC one mini boots into bootloader

*** LOCK ***
M4_UL PVT SHIP S-ON RL
HBOOT-2.19.0000
It boots right into boot loader without holding the volume button down
Is there a way to fix this without losing data?
Okay so now I am using ruu but keep getting error 171

Pretty sure you need to be s-off to use the RUU .. Why not use a stock based Rom off dev section?
Sent from my GT-I9000 using Xparent Skyblue Tapatalk 2

UnicycleWheelie said:
*** LOCK ***
M4_UL PVT SHIP S-ON RL
HBOOT-2.19.0000
It boots right into boot loader without holding the volume button down
Is there a way to fix this without losing data?
Okay so now I am using ruu but keep getting error 171
Click to expand...
Click to collapse
Can you tell us exactly what happened or what you did before you kept booting into bootloader?

Omarion23145 said:
Can you tell us exactly what happened or what you did before you kept booting into bootloader?
Click to expand...
Click to collapse
My friend brought the one mini (AT&T) to me in bootloader, she didn't know how it got there. she said she only pressed the power button and got there. It did have a case on it, and I thought that maybe it had the down volume key stuck and that's how.
In BL (bootloader) I have tried reboot, power down and pressing the power button, recovery, factory reset...and still comes up in BL.
I have this RUU
RUU_M4_UL_JB_50_Cingular_US_1.32.502.3_Radio_1.19.40d.00.14_10.20.40.4408L_release_333483_signed_2
And when I run it on my windows 7 64bit computer its gets to the end page and restarts the phone into fastboot and the phone says fastbootusb but then on my computer it just says waiting for bootloader................ and then ERROR[171]
I have tried different USB cables and front and back usb ports, I have also tried 2 other computers and still says ERROR 171
And yes, I have the drivers for the phone from HTC Sync... IDK what road to take now

UnicycleWheelie said:
My friend brought the one mini (AT&T) to me in bootloader, she didn't know how it got there. she said she only pressed the power button and got there. It did have a case on it, and I thought that maybe it had the down volume key stuck and that's how.
In BL (bootloader) I have tried reboot, power down and pressing the power button, recovery, factory reset...and still comes up in BL.
I have this RUU
RUU_M4_UL_JB_50_Cingular_US_1.32.502.3_Radio_1.19.40d.00.14_10.20.40.4408L_release_333483_signed_2
And when I run it on my windows 7 64bit computer its gets to the end page and restarts the phone into fastboot and the phone says fastbootusb but then on my computer it just says waiting for bootloader................ and then ERROR[171]
I have tried different USB cables and front and back usb ports, I have also tried 2 other computers and still says ERROR 171
And yes, I have the drivers for the phone from HTC Sync... IDK what road to take now
Click to expand...
Click to collapse
Okay. Is there an OS on there? Try flashing a custom recovery on it ( Try TWRP 2.7.0.0 or higher ), and go to recovery after you flash it, then press install and go into SDCARD. What do you see there? And how much internal memory does it show you?

Omarion23145 said:
Okay. Is there an OS on there? Try flashing a custom recovery on it ( Try TWRP 2.7.0.0 or higher ), and go to recovery after you flash it, then press install and go into SDCARD. What do you see there? And how much internal memory does it show you?
Click to expand...
Click to collapse
I'm not 100% but I think there is no os...and for the flash I did the fastboot and had the img twrp file I renamed it (twrp) and in the CMD typed fastboot flash twrp.img and it comes up with
C:\Users\Gigabyte\Desktop\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
fastboot flash twrp.img
unknown partition 'twrp.img'
error: cannot determine image filename for 'twrp.img'
C:\Users\Gigabyte\Desktop\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
fastboot flash twrp
unknown partition 'twrp'
error: cannot determine image filename for 'twrp'
And the htc one mini doesn't have a sdcard slot...it doesn't even show up in my Computer when its connected via usb

Omarion23145 said:
Okay. Is there an OS on there? Try flashing a custom recovery on it ( Try TWRP 2.7.0.0 or higher ), and go to recovery after you flash it, then press install and go into SDCARD. What do you see there? And how much internal memory does it show you?
Click to expand...
Click to collapse
okay I got this
C:\Users\Gigabyte\Desktop\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
fastboot flash recovery twrp.img
sending 'recovery' (8572 KB)...
OKAY [ 1.207s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.916s

UnicycleWheelie said:
okay I got this
C:\Users\Gigabyte\Desktop\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
fastboot flash recovery twrp.img
sending 'recovery' (8572 KB)...
OKAY [ 1.207s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.916s
Click to expand...
Click to collapse
you need to unlock your bootloader via htcdev website, then flash the recovery again in fastboot **this will void your warranty ** so if this just happened to your friends phone without any reason,probably better just taking it to your cell provider

Braddison said:
you need to unlock your bootloader via htcdev website, then flash the recovery again in fastboot **this will void your warranty ** so if this just happened to your friends phone without any reason,probably better just taking it to your cell provider
Click to expand...
Click to collapse
So I did the fastboot flash unlocktoken Unlock_code.bin
with htcdev
and it says
C:\Users\Gigabyte\Desktop\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.155s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.007s]
finished. total time: 0.162s
but its still locked so I do it again and it freezes and there is a green like loading bar on the side but the phone is froze untill you unplud it and replug it in and when you reboot into BL its still locked

when you flash the unlock token you should get a screen appear on your phone (see below)
hit yes...tghe phone will reboot a few times
i would try again but be patient, wait till the phone stops doing what it needs to

Braddison said:
when you flash the unlock token you should get a screen appear on your phone (see below)
hit yes...tghe phone will reboot a few times
i would try again but be patient, wait till the phone stops doing what it needs to
Click to expand...
Click to collapse
and when I do the flash it just stays in the boot loader
Alright will try it again,

UnicycleWheelie said:
and when I do the flash it just stays in the boot loader
Alright will try it again,
Click to expand...
Click to collapse
Yeah. If it doesn't work the first time, try again. Sometimes it doesn't work the first time .

Omarion23145 said:
Yeah. If it doesn't work the first time, try again. Sometimes it doesn't work the first time .
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=XZDuXmy4buY

C:\Users\Gigabyte\Desktop\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Users\Gigabyte\Desktop\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
adb devices
List of devices attached
C:\Users\Gigabyte\Desktop\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
fastboot devices
HT382WA01938 fastboot
so adb cant find the phone but fastboot can?

i think you deleted the os... can you boot into recovery???

htconemini said:
i think you deleted the os... can you boot into recovery???
Click to expand...
Click to collapse
When I turn it on it goes strigh to boot loader, in hboot/bootloader, I go to recovery and hit the power button, it vibrates and shoes an all white screen with the 3 androids in the middle, then goes to fastboot
I asked her what happened to the phone before this problem happened. and this is what she said...Hey! So, when it first crashed it was a few months ago and it pretty much just ran out of battery and powered down. I don't remember doing anything strange or anything weird happening before it died. And then I got the charger and plugged it in and the boot loader screen popped up. I was really confused and not really sure what was going on so I clicked on reboot and shut down and reboot boot loader and everything to try to get it back to normal. After I clicked those a few times it went back to normal. And it's done that about 4 times total in the past but I could always get it back to normal by selecting the options randomly. And it would always come up after the phone ran out of battery. And then the other night when it died I put it on the charger the screen came up and it wouldn't go away no matter what I did.

To unlock the bootloader do you need adb or only fastboot...because this phone takes the htcdev unlockcode.bin but the phone just stays in bootloader. when you do fastboot devices it shows up but when you do adb devices there is nothing.

UnicycleWheelie said:
To unlock the bootloader do you need adb or only fastboot...because this phone takes the htcdev unlockcode.bin but the phone just stays in bootloader. when you do fastboot devices it shows up but when you do adb devices there is nothing.
Click to expand...
Click to collapse
I'm not alone - The exact same scenario (almost) happened to me a few days ago with my HTC1Mini and now I am stuck at the BL screen also. I lost connectivity (no service), rebooted and the phone went straight to the BL screen. I have tried everything mentioned, including the HTCDev unlock code - no joy, even dough it stated successfully. Also, I did not get the "Yes/No Confirmation" on the phone, it remained on the boot loader screen. It seems that regardless of what method one uses, if the phone is "Locked" nothing will work. If you have figured out how to exist the BL screen, please share your methods/steps/files. Your time and consideration is greatly appreciated. Thanks.

Shacho said:
I'm not alone - The exact same scenario (almost) happened to me a few days ago with my HTC1Mini and now I am stuck at the BL screen also. I lost connectivity (no service), rebooted and the phone went straight to the BL screen. I have tried everything mentioned, including the HTCDev unlock code - no joy, even dough it stated successfully. Also, I did not get the "Yes/No Confirmation" on the phone, it remained on the boot loader screen. It seems that regardless of what method one uses, if the phone is "Locked" nothing will work. If you have figured out how to exist the BL screen, please share your methods/steps/files. Your time and consideration is greatly appreciated. Thanks.
Click to expand...
Click to collapse
I had to contact HTC via the help chat. and they walked me through all the "try this" and nothing still went into BL. so they had me ship it in, and I got it fix for free. took about a 11days
{
"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"
}
...it sounded like there is a problem/fault with this phone.

UnicycleWheelie said:
I had to contact HTC via the help chat. and they walked me through all the "try this" and nothing still went into BL. so they had me ship it in, and I got it fix for free. took about a 11days
...it sounded like there is a problem/fault with this phone.
Click to expand...
Click to collapse
the kept the SN the same but the IMEI changed (on the back sticker)

[Help] Honor 6 H60-L02 bricked, impossible to charge

Hello experts,
My Honor 6 H60-L02 bricked due to incorrect update. It seems to me I tried dozens of packages already but nothing helps. So it's accessible over fastboot only and it's impossible even to charge it.
boot is unlocked for sure
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash system system.img
are executable without any errors
at another point
C:\2017>fastboot erase boot
erasing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.004s
C:\2017>fastboot erase system
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.004s
C:\2017>fastboot erase cust
erasing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 0.004s
and then it's impossible to install UPDATE.dat with 3 buttons from SD card. I see only:
Func No : 10 (FUNC_BOOT_KERNAL) or
Func No : 9 (FUNC_BOOT_KERNAL)
Error No : 2
Could anybody provide the solution. I bought my Honor just six months ago :crying:

Facing same problem after trying to upgrade to latest firmware
I am also facing the same problem...
I am gonna try to unbrick using Huawei multi tool kit with the older version rom tomorrow...

atchuthantu said:
I am also facing the same problem...
I am gonna try to unbrick using Huawei multi tool kit with the older version rom tomorrow...
Click to expand...
Click to collapse
HI,
unfortunately, this way is not suitable for me. If I use multi tool kit restoration I get error like "Your device is not supported. Please send it to Huawei service". That is why I am looking for advanced method.

6_Honor said:
HI,
unfortunately, this way is not suitable for me. If I use multi tool kit restoration I get error like "Your device is not supported. Please send it to Huawei service". That is why I am looking for advanced method.
Click to expand...
Click to collapse
Is your bootloader unlocked?

atchuthantu said:
I am also facing the same problem...
I am gonna try to unbrick using Huawei multi tool kit with the older version rom tomorrow...
Click to expand...
Click to collapse
goldfinv said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
Yes, boorloader is unlocked as I mentioned before
Just in case I attached screenshot
{
"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"
}

I had exactly the same problem with honor 6 l02. I couldnt flash anything through fastboot,i had the same errors and also func boot kernel too, and it didnt charge. I tried everything, and then took it to a service center.they told me they bypassed and updated. The phone is working now almost normally.the only problem is that i still cannot flash any image through fastboot. So im telling you ,your phone can be recovered,i just want to know the way too... it seems everything started when i had flashed ar recovery for model l04 and messed up partitions... Forgot to say that my bootloader is unlocked

I have the same problem.. Func No : 10 (FUNC_BOOT_KERNAL).
Bootloader is unlocked but each command failed with error: `FAILED (remote: Command not allowed)` (I don't understand why I can't flash things)
Is there any solution?

if you can flah twrp?? you can flash a custom rom available and can proceed further..
but charging is something related to bootloader... as long as bootloader is accessable, phone must charge., else its a faulty hardware (i think, but im not sure)

Perhaps you should try the DC Unlocker method I've read about in the forums. Fixed some really bad cases of hard brick. Not free tho.

goldfinv said:
Perhaps you should try the DC Unlocker method I've read about in the forums. Fixed some really bad cases of hard brick. Not free tho.
Click to expand...
Click to collapse
It seems to me bad luck:
selection :
manufacturer - Huawei phones
model - Auto detect (recommended)
Model : Huawei phone in fastboot mode
IMEI : 864103020981442
Firmware : H60-C00B000
unlocked
Battery state: 3117mv
===================================================================
Factory reset protection Erase start
No username !
Any idea?

6_Honor said:
It seems to me bad luck:
selection :
manufacturer - Huawei phones
model - Auto detect (recommended)
Model : Huawei phone in fastboot mode
IMEI : 864103020981442
Firmware : H60-C00B000
unlocked
Battery state: 3117mv
===================================================================
Factory reset protection Erase start
No username !
Any idea?
Click to expand...
Click to collapse
Can you go into phones recovery???
If yes then do a factory reset and then try the fastboot method
Note:: if you were on marsh version then flash flash marsh files only dont flash lp or kk files.

xxXDeaDlyGhoStXxx said:
Can you go into phones recovery???
If yes then do a factory reset and then try the fastboot method
Note:: if you were on marsh version then flash flash marsh files only dont flash lp or kk files.
Click to expand...
Click to collapse
No, "Recovery mode" is not accessible as I mentioned before. Fastboot is only one interface I can use. Please have a look at the attached screenshot

6_Honor said:
No, "Recovery mode" is not accessible as I mentioned before. Fastboot is only one interface I can use. Please have a look at the attached screenshot
Click to expand...
Click to collapse
Hey, i had this problem also once. I tried everything, but nothing helped. I sent it back to the store, where i bought it. They repaired it somehow and i had to pay nothing. Either I was lucky or they are taking warranty not so serious.
Sent from my H60-L04 using XDA-Developers Legacy app
---------- Post added at 11:38 PM ---------- Previous post was at 11:34 PM ----------
https://tapatalk.com/shareLink?url=...share_tid=3349593&share_fid=3793&share_type=t
(Q) HELP!! <remote: command not allowed> with unlocked bootloader
Sent from my H60-L04 using XDA-Developers Legacy app

I have the same problem and i fix it easily with this tool !
DC Phoenix from dc unlocker the problem is that the fix cost 15 euro for each phone but phone is working so think it twice

donteo said:
I have the same problem and i fix it easily with this tool !
DC Phoenix from dc unlocker the problem is that the fix cost 15 euro for each phone but phone is working so think it twice
Click to expand...
Click to collapse
Unfortunately, factory repair file and flash empty board or by testpoint not available for H60-L02. I think this is a blocker to engage "DC unlocker"

Man believe me or not i dont give a **** i want to help ! I have the exact problem 100% you describe and non of multi tools can flash rom ! I download offical rom for L02 and flash it via DC Phoenix ... and now phone work! check my profile if you dont believe me i am member since 2009

donteo said:
Man believe me or not i dont give a **** i want to help ! I have the exact problem 100% you describe and non of multi tools can flash rom ! I download offical rom for L02 and flash it via DC Phoenix ... and now phone work! check my profile if you dont believe me i am member since 2009
Click to expand...
Click to collapse
No doubt, I believe you. But how to did you pass the last step of restoration: "Disconnect phone from PC and restart to end the process" ? Unfortunately, it's impossible to charge my phone. It can be accessible when it's connected to PC only. If I disconnect it I have black brick

I simply press down and connect usb to pc so i see the fastboot mode and after run Dc Phoenix ! Before this i use unbrick function of multi tool and phone always show only red battery indicator for ever ... after flashing

donteo said:
Man believe me or not i dont give a **** i want to help ! I have the exact problem 100% you describe and non of multi tools can flash rom ! I download offical rom for L02 and flash it via DC Phoenix ... and now phone work! check my profile if you dont believe me i am member since 2009
Click to expand...
Click to collapse
Hi donteo! Thank you so much for advises. Phone works now! :good:

Hi guys, sorry for bumping the old thread, just like you guys i have bricked my honor 6 also(H60-L02)
can you guys just provide me the files and the steps to follow to unbrick using DC-Phoenix ?
i have tried almost all the methods and files available on the internet except DC-Phoenix.
i will be very much thankful for you guys.

How to flash custom kernel/ROM in EMUI 10 via Software Testpoint mode

HOW TO FLASH IN EMUI10 VIA SOFTWARE TESTPOINT
1. Enter USB Update Mode
On older EMUI versions you would use vol up + vol down + power. This has changed now.
On EMUI 10, enter eRecovery by holding volume up and power until you see the Huawei logo appear. Then let go and press volume up again and wait for eRecovery screen. Then press USB Update and it should show an update screen at 5% complete.
2. Enable Software Testpoint
Using the update.app of the same firmware that you are currently on, turn factory mode on via whichever app you happen to be using. Personally I am using Octoplus Huawei Tool (paid), but you could also use Chimera (paid), Sigmakey (paid) and many others. There are free methods too by manual flashing in Linux but it is too involved to discuss here.
Output from Octoplus looks like:
Code:
Starting ON/OFF Factory Mode
Selected phone model: CLT-L29
To Enable Factory mode put the phone in Upgrade mode and connect USB cable!
To Disable Factory mode connect the phone in Factory mode or Factory Fastboot mode!
Checking the existence of the auto firmware file...
Selected firmware file file: C:/Users/srefs/Documents/HiSuite/ROM/Charlotte-L29C10.0.0.171_Firmware_EMUI10.0.0_05015AMH/Software/dload/UPDATE_BASE.APP
Performing ON Factory Mode operation...
Checking firmware package type
Searching device in Upgrade mode...
Connecting to phone..
Phone connect successfully!
Writing firmware partitions...
Writing ‪SHA256RSA‬ partition...
Writing ‪CRC‬ partition...
Writing ‪BASE_VERLIST‬ partition...
Writing ‪BASE_VER‬ partition...
Writing ‪PACKAGE_TYPE‬ partition...
Writing ‪HISIUFS_GPT‬ partition...
Writing ‪XLOADER‬ partition...
ON/OFF Factory Mode done.
Performed by ‪1.2.3‬ Software version.
You should now see this in Device Manager on Windows, which means you successfully entered testpoint mode without disassembling your hardware. You can now literally do anything to your hardware.
{
"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"
}
3. Write factory fastboot.
If you are using Octoplus, you just go to the Update backup tab, make sure 'Update OEMInfo' is NOT ticked and click Update. As soon as you see fastboot is flashed, you can cancel. For free method, see: Downgrade/Unbrick Huawei device (if other methods doesn't work) | XDA Developers Forums (xda-developers.com)
4. Flash whatever you want
Now you can flash whatever the heck you want over EMUI 10, such as a kernel. You will also need to disable verified boot so you can load unsigned images without getting the dreaded "your device has failed verification". Have fun!
Code:
PS C:\adb> .\fastboot flash kernel .\KERNEL.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.183s]
writing 'kernel'...
OKAY [ 0.275s]
finished. total time: 0.462s
PS C:\adb> .\fastboot flash kernel .\image-new.img
target reported max download size of 471859200 bytes
sending 'kernel' (20664 KB)...
OKAY [ 0.155s]
writing 'kernel'...
OKAY [ 0.081s]
finished. total time: 0.241s
PS C:\adb> .\fastboot oem get-build-number
...
(bootloader) :CLT-L29 10.0.0.171(C432E3R1P3)
OKAY [ 0.008s]
finished. total time: 0.011s
PS C:\adb> .\fastboot oem get-lockstate
...
(bootloader) locked
OKAY [ 0.004s]
finished. total time: 0.005s
5. Turn off Software Testpoint
Turn factory mode off in same software you used in step 2.
Code:
Performing OFF Factory Mode operation...
Searching Fastboot devices...
Found a fastboot device:
Device Model: ‪CLT-L29‬
System: ‪CLT-L29 10.0.0.171(C432E3R1P3)‬
...
Writing secure data...
Rebooting device...
ON/OFF Factory Mode done.
Performed by ‪1.2.3‬ Software version.
Now either you did the right thing by this stage and it boots up nicely... or you screwed up something and it doesn't boot up. As long as you can get to eRecovery again, you can let Huawei automatically recover. Note: If recovery fails the first time complaining about 'authorization', just run recover again and it will work.

Could that mean Possible Custom Roms in the Future?

I don't see why not. I'm just confused why the Huawei forums are totally devoid of custom kernels and ROMs.
I understand the lack of unlock bootloader, but with software testpoint this is really a moot point.

Me i
xsacha said:
I don't see why not. I'm just confused why the Huawei forums are totally devoid of custom kernels and ROMs.
I understand the lack of unlock bootloader, but with software testpoint this is really a moot point.
Click to expand...
Click to collapse
I Wonder myself aswell. The P20 Pro would be even better with Custom Firmware.
The Development should be there in my Opinion.
Good Phone, lag of Development.

By the way, you should be able to flash an older bootloader (but keep EMUI 10) using this method and then your bootloader will be unlocked again. Or, if not already unlocked, you can unlock with a key as per old way.
Advantages of bootloader unlock:
Flash kernels/roms without third-party software.
Disadvantages:
Have to root and use magisk hide for Google Pay to work again.

So, with this method, you can literally flash treble roms? Also, can we just the usb cable provided instead of a dongle for the paid programs?

xsacha said:
I don't see why not. I'm just confused why the Huawei forums are totally devoid of custom kernels and ROMs.
I understand the lack of unlock bootloader, but with software testpoint this is really a moot point.
Click to expand...
Click to collapse
Because without a bootloader unlock method, nobody bothered to keep maintaning the phone

AnotyClaws said:
So, with this method, you can literally flash treble roms? Also, can we just the usb cable provided instead of a dongle for the paid programs?
Click to expand...
Click to collapse
Dongle? I'm using the digital licence and it's just a key you paste in. No dongles required.

Is the same possible for honor 9 lite, lld-l31, EMUI 9.1 too? And how to make this free in linux?

sergeyzap said:
Is the same possible for honor 9 lite, lld-l31, EMUI 9.1 too? And how to make this free in linux?
Click to expand...
Click to collapse
Linux method requires you to open up your device, from what i see above. Shame that i don't have cash to buy the software required to root my phone.

Awesome there's some roms we can flash already?

Hi, does anyone know how to retrieve saved notes from the Huawei phone’s in-built note after a factory reset, without having it backed up in huawei’s cloud? Please help! Much appreciated

Nwl295 said:
Hi, does anyone know how to retrieve saved notes from the Huawei phone’s in-built note after a factory reset, without having it backed up in huawei’s cloud? Please help! Much appreciated
Click to expand...
Click to collapse
You can't. I'm sorry

I actually wonder, by "Flash anything" you mean i can just flash TWRP and, from there, do everything i want?

AnotyClaws said:
I actually wonder, by "Flash anything" you mean i can just flash TWRP and, from there, do everything i want?
Click to expand...
Click to collapse
@xsacha tell us more

Sorry to budge in, but Octoplus does not detect my phone at all, regardless of HiSuite version installed, reboots.
One weird thing I noticed is that even though I have USB debugging turned on and accept/approve the connection, HiSuite prompts me to approve the connection to my PC again while in USB update mode.
Any help is highly appreciated.
Edit: This is what it sees attached.
Found COM ports:
1: COM12 HUAWEI Mobile Connect - Fake Acm Interface
2: COM13 DBAdapter Reserved Interface
3: COM14 Android Adapter PCUI

this is great !
please can you share a simple how-to document when you have a valid ROM [e.g. TWRP]
i would like to flash my own p20 pro and dont have the skilset yet :-/

my p20pro is now wide open after battery change, and I wonder if it is possible to unlock bootloader by grounding test pin? Are there any good instructions?

xsacha said:
HOW TO FLASH IN EMUI10 VIA SOFTWARE TESTPOINT
[...]
4. Flash whatever you want
Now you can flash whatever the heck you want over EMUI 10, such as a kernel. You will also need to disable verified boot so you can load unsigned images without getting the dreaded "your device has failed verification". Have fun!
[...]
Click to expand...
Click to collapse
Hello dear xsache. I'm playing around with my P20 Pro since yesterday morning and I fked up.
I used DC Phoenix which can also set phone into Software TestPoint mode which is a great thing.
But... I'm now stuck exactly on that Device Verification, and I cant flash new Firmware because CURVER can't be flashed. I'm now wondering how I can deactivate Device Verification.
I can get into TestPoint Mode + Fastboot (with temp. unlocked bootloader), and I can get into Regular Fastboot (with locked bootloader).
I would like to run TWRP and install LineAgeOS, but I cant start TWRP out of TestPoint Mode.
I already ordered OctoPlus licence, but maybe you can give me a hint on how to deactivate verification.
Thx.
Update: With OctoPlus I managed to fully flash EMUI 8. Verification Message is gone.
But still no TWRP
I can get into Testpoint mode and Flash to recovery_ramdisk. Then get out of Testpoint Mode and phone reboots normally. Then shutdown. If I try Vol Down + Power I get into Fastboot, if I try Vol UP + Power I get into Huawei eRecovery...
If I go to fastboot mode and type "fastboot reboot recovery" it gets me into Huawei eRecovery too.
Do I need to flash another Partition? Or are changes reverted after I get out of Testpoint Mode?
UPDATE2:
FKIN HELL! FK HUAWEI!
I managed to boot into TWRP.
In DC Phoenix I went into Testpoint mode, temporarily unlocked bootloader, then:
fastboot flash erecovery_ramdisk twrp-3.5.0_9-0-charlotte.img (make sure its *e*recovery)
Then.... started holding Vol UP + Power, in DC Phoenix Disables TestPointed and holded the buttons all the time.
It then went into fastboot and then into ... TWRP!
Unfortunately, TWRP was not able to provide mounted partitions to windows and fastboot commands didnt work. But I was able to adb push the zip to /storage.
When I tried to install, I got following error:
huawei.verify_vendor_build_id() failed to read
current vendor build id: -2
updater process ended with ERROR: 7
Fking Huawei all over the place....
Update3:
Changed updater-script in LineAge Zip. remove first 3 assert lines... hehe xd
Successfully flashed.
It could have been so nice.... tried to reboot but it always went to TWRP. Not able to boot System.... :/
Gonna Flash EMUI 9 and Try again.
And then EMUI10 and Try again.
And then Give up and burn that fking phone.
Final(?) Update:
Phone Dead. Looks like I flashed a Bad FW.
(1) Verification failed msg back.
(2) eRecovery destroyed (recovery image load failed)
(3) Bootloader Locked
(4) FRP Locked, so no bootloader unlock
I then have thrown the phone out of the window.
OK, unfortunately that was just in my imagination.
I opened up the phone and used hardwaretestpoint, got into fastboot with DC Phoenix and was able to flash another firmware...
I think LineAge OS like it is (Install Script) wont work with termporary unlocked bootloader.
It looks like TWRP does some stuff it needs an unlocked bootloader for.
So we will have to wait until there is a working method.
BTW, Ministry of Solutions really offers CLT-L29 Bootloader unlock codes now. But it seems to doesnt work with every model. He was on my PC yesterday for hours trying to do so but the found Code didnt work. It was the second phone (P20 Pro) that didnt work for him. With some others he was successful. So there might be some hope for some people out there. He refunded my $15 same day even after I told him he could keep it.
To be continued...

Is it possible on Emui10 to just flash Magisk to get root and not go through all the hell posted above?

moto g8 plus flashing-locked

it does not start and I can not put any rom
{
"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"
}

Hi, try booting with a boot.img in the same version of your phone.
First, type in CMD fastboot getvar all
Second, Look for the line which states your installed rom version.
Third, Download the same rom and extract the boot.img from the zip file
Fourth, In CMD type fastboot boot boot.img If nothing goes wrong with the download, your device should boot up. Then check to see if you can activate the OEM lock. If not, try updating phone. Does it let you you update? great do it. If it show device system integrity corrupted, wait seven days without turning phone off and try updating again. If still no dice, then you're out of luck.
I had same problem as you, and what got mine back from the dead was to keep updating till one update fixed my issue.

mrsiri said:
Hi, try booting with a boot.img in the same version of your phone.
First, type in CMD fastboot getvar all
Second, Look for the line which states your installed rom version.
Third, Download the same rom and extract the boot.img from the zip file
Fourth, In CMD type fastboot boot boot.img If nothing goes wrong with the download, your device should boot up. Then check to see if you can activate the OEM lock. If not, try updating phone. Does it let you you update? great do it. If it show device system integrity corrupted, wait seven days without turning phone off and try updating again. If still no dice, then you're out of luck.
I had same problem as you, and what got mine back from the dead was to keep updating till one update fixed my issue.
Click to expand...
Click to collapse
Friend. could you help me?
I tried this method but it did not work, i tried with the version that the getvar gives me :
(bootloader) ro.build.fingerprint[0]: motorola/doha/doha:10/QPI30.28-Q3-
(bootloader) ro.build.fingerprint[1]: 28-26-4-1/2f8cb:user/release-keys
But it still don't work, i tried every other compilation too, excluding the Android 9 ones... I also tried blankflash but did not work.
It gives me error and goes to the "Your device is corrupt. It can't be trusted and will not boot" screen:
fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.845s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 32.039s

setryky said:
Friend. could you help me?
I tried this method but it did not work, i tried with the version that the getvar gives me :
(bootloader) ro.build.fingerprint[0]: motorola/doha/doha:10/QPI30.28-Q3-
(bootloader) ro.build.fingerprint[1]: 28-26-4-1/2f8cb:user/release-keys
But it still don't work, i tried every other compilation too, excluding the Android 9 ones... I also tried blankflash but did not work.
It gives me error and goes to the "Your device is corrupt. It can't be trusted and will not boot" screen:
fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.845s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 32.039s
Click to expand...
Click to collapse
Fastboot boot won't work because locked bootloader checks for a key which don't match correctly. You should try same version as the one installed on your phone or newer. Can you boot system?
The only way is to get blankflash to work. Try other computer, preferably older ones with intel, not AMD. If system is able to boot try OTA update because it fixed on mine.

mrsiri said:
Fastboot boot won't work because locked bootloader checks for a key which don't match correctly. You should try same version as the one installed on your phone or newer. Can you boot system?
The only way is to get blankflash to work. Try other computer, preferably older ones with intel, not AMD. If system is able to boot try OTA update because it fixed on mine.
Click to expand...
Click to collapse
I know that this version (QPI30.28-Q3-28-26-4-1) is the correct one because i had flashed my phone with it before trying to lock the bootloader, and it worked. I also tried every other compilation. I got the .rar from lolinet.
I tried blankflash, it did not work... It still gives me the same error. My computer on a i7 920, so it's very old. Anyways, thanks for any help you might be able to provide.

Setryky did you find any solution? I have the same problem

Fael.exe said:
Setryky did you find any solution? I have the same problem
Click to expand...
Click to collapse
I did not

setryky said:
I know that this version (QPI30.28-Q3-28-26-4-1) is the correct one because i had flashed my phone with it before trying to lock the bootloader, and it worked. I also tried every other compilation. I got the .rar from lolinet.
I tried blankflash, it did not work... It still gives me the same error. My computer on a i7 920, so it's very old. Anyways, thanks for any help you might be able to provide.
Click to expand...
Click to collapse
You should get boot.img from rom and use command fastboot boot boot.img to boot to rom. Then try oem unlock option activating or OTA updating if first doesn't work

mrsiri said:
You should get boot.img from rom and use command fastboot boot boot.img to boot to rom. Then try oem unlock option activating or OTA updating if first doesn't work
Click to expand...
Click to collapse
i did that with every rom in lolinet... did not work. And now it is saying that my device has "no bootable a/b slot".

Does your device show up as QCOM 9008? It's the EDL state and only way to install via blank flash

mrsiri said:
Does your device show up as QCOM 9008? It's the EDL state and only way to install via blank flash
Click to expand...
Click to collapse
no, it does not. I already tried blankflash... When i do blankflash it goes back to the "your device is corrupted" screen.

setryky said:
no, it does not. I already tried blankflash... When i do blankflash it goes back to the "your device is corrupted" screen.
Click to expand...
Click to collapse
You can't do blank flash if it's not showing QCOM 9008 mode on device manager, that's the device EDL mode. I'm afraid that's you only option, aside from opening back glass plate and shorting 2 points in motherboard or using a stripped USB cable and shorting green cable to black cable

setryky said:
i did that with every rom in lolinet... did not work. And now it is saying that my device has "no bootable a/b slot".
Click to expand...
Click to collapse
No bootable a/b slot... You wiped system?

mrsiri said:
You can't do blank flash if it's not showing QCOM 9008 mode on device manager, that's the device EDL mode. I'm afraid that's you only option, aside from opening back glass plate and shorting 2 points in motherboard or using a stripped USB cable and shorting green cable to black cable
Click to expand...
Click to collapse
Idk the points in motherboard so best way is to use cable method or buy an EDL cable online or use a "box" which flashes directly through JTAG but that is expensive. Just leave the green and black cables connected for 8 seconds if nothing happens try again this time for 20 seconds

mrsiri said:
Idk the points in motherboard so best way is to use cable method or buy an EDL cable online or use a "box" which flashes directly through JTAG but that is expensive. Just leave the green and black cables connected for 8 seconds if nothing happens try again this time for 20 seconds
Click to expand...
Click to collapse
i entered in the edl mode via the pins... the blankflash did work, but not to fix my system.

mrsiri said:
No bootable a/b slot... You wiped system?
Click to expand...
Click to collapse
no, its like when i do "fastboot boot boot.img" too many times, and when i do a blankflash it goes to that your device is corrupted screen.

The EDL should have worked... Well your last bet is on the box JTAG flasher. You'll either buy it and learn how to flash or ask some professional to do it

boa tarde eu to com esse problema no meu moto g8 plus flashing- locked ...alguem pode me ajudar por favor
Mod translation via GT: good afternoon I have this problem on my moto g8 plus flashing-locked ... can someone help me please

How To Guide Lock+Unlock Bootloader - Xiaoxin Pad Pro 2021 [TB-J716F]

How To Lock and Unlock Bootloader - Xioaxin Pad Pro 2021 - TB-J716F
Since I found out that the Tablet supports Project Treble I'm trying to get a GSI-ROM running on it.
Currently with many trial and error I got LiR-ROM to boot.
The first step is to unlock the Bootloader so I thought I will share the process here.
Your data will be deleted while unlocking, try it at your own risk.
Unlock Bootloader manually
Requirement: PC with ADB Fastboot
1. Go to Settings -> System -> About Phone, tab on it until developer settings are enabled.
2. Go to Developer Settings and enable "USB Debugging" and "OEM Unlocking".
3. Open Console and enter "adb devices". Allow USB-Debugging if tablets asks.
4. Enter command "adb reboot bootloader".
5. Write down the serial number shown on the bootloader screen
You can either get the unlock image via this link "http://cdn.zui.lenovomm.com/developer/tabletboot/[your sn number]/sn.img" or via the webseite
5. Go to the ZUI Unlock Website and request the unlock image
{
"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"
}
6. You should get a mail where you can download a file called "sn.img".
7. Flash the image with fastboot "fastboot flash unlock sn.img"
8. Enter command "fastboot oem unlock-go", bootloader will unlock now.
9. Restart with "fastboot reboot".
Done, your bootloader should be unlocked now.
Lock and Unlock Bootloader with Batchscript
I recently found a batch script for lenovo devices in an chinese forum and translated it.
It's easy and convenient to use. For unlocking you still need the sn.img from the ZUI Unlock Website.
Download BatchScript​

Thanks a lot for your contribution! Mine was unlocked when I received it but it's good to see some guides here.

What is the opposite process, to close the bootloader? Does Widevine L1 recover after closing the bootloader? In the case of doing so, can the bootloader be opened again?

@sakun-ice Sorry, I can't tell you that, sind I haven't tried it now. But I think it should be possible.
Currently I'm trying to get a Custom ROM running, if it doesn't work, I will try to install Stock ROM and lock bootloader again. If it happens, I will post it here.

Tropaion said:
@sakun-ice Sorry, I can't tell you that, sind I haven't tried it now. But I think it should be possible.
Currently I'm trying to get a Custom ROM running, if it doesn't work, I will try to install Stock ROM and lock bootloader again. If it happens, I will post it here.
Click to expand...
Click to collapse
Thank you very much, I hope you can install a custom rom and this tablet will not be forgotten, since it is one of the most powerful compact tablets.

@sakun-ice I got LineageOS to run on it today, but it still has 2-3 bugs.

Helloi received one unlocked with a globaoe fw without ota's and i flashed the cn one and took the boot.ipg and patched it with pagisk for root and when flashing it via fastboot the device reboots to fastboot everytipe 1nd had to reflash the fw via edl , i did flashed vbmeta img with the known command o disable verification but no success same thing again. Can anyone plz tell me how to root that crap , it was intended to root use only and took over xiaomi pad pro just because the xiaomi needs 7 days of waiting before unlocking , plz help guys .thx so much i can buy a couple beers for the helper

I'm able to flash back to China stock rom but i can't lock the bootloader.
i have placed the sn.img in both the batchscript folder and platform tools
Tried the batch script :
"
Please select your device status:
1. Fully booted
2. Fastboot mode
Status: 2
Start locking bootloader, don't disconnect device from PC!
FAILED (remote: Command not supported in default implementation)
Finished. Total time: 0.016s
FAILED (remote: Unrecognized command flashing lock)
Finished. Total time: -0.000s
If prompt says "OKAY", locking was successfull.
Use the volume keys to select "LOCK BOOTLOADER", press power key to confirm.
Done!
Press any key to continue . . .
"
Powershell :
"
PS C:\Users\weeteck\Downloads\platform-tools_r31.0.3-windows\platform-tools> ./fastboot flash lock sn.img
Sending 'lock' (5 KB) OKAY [ 0.000s]
Writing 'lock' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
"

@zeroflame15 Did install the driver correctly? For locking you don't need the sn.img, only for unlocking. And did you use the LockBootloader Script?

hmm..i'm not sure if i install the driver correctly. what should be shown in device manager? i did follow PHRS guide and installed the ADB driver but there is this !Android under Other Devices.
Any other driver that i need to install?
And should i be in bootloader mode or fastboot mode to run the command? I run the command at fastboot moder i will get the error above. If i run at bootloader mode will stuckedd at <waiting for device>

@zeroflame15 You have to be in bootloader mode. <waiting for device> is propably the driver.

Tropaion said:
@zeroflame15 You have to be in bootloader mode. <waiting for device> is propably the driver.
Click to expand...
Click to collapse
i have installed all the ADB driver mentioned in this section. Is there a lenovo driver? or any settings within the tablet need to be set to?
thanks for the help

zeroflame15 said:
i have installed all the ADB driver mentioned in this section. Is there a lenovo driver? or any settings within the tablet need to be set to?
thanks for the help
Click to expand...
Click to collapse
Try to connecting in another usb port with other usb cable.

zeroflame15 said:
i have installed all the ADB driver mentioned in this section. Is there a lenovo driver? or any settings within the tablet need to be set to?
thanks for the help
Click to expand...
Click to collapse
Check out this post:
Post in thread '[Solved] Re-locking bootloader - no fastboot commands working' https://forum.xda-developers.com/t/...stboot-commands-working.4330019/post-85755663
It can be a bit tricky to get the commands working because it's not always clear if you need to be in fastboot or bootloader.
This worked for me:
Reboot to bootloader by entering "adb reboot bootloader"
After that try "fastboot flashing lock"

Thanks @zxcv88
After installing the lenovo USB driver, the !Android in Other devices was updated.
LenovoUsbDriver_v1.1.34
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Boot into bootloader mode and "fastboot flashing lock" runs without any issue
Appreciate all for the advise and help! Appreciate ~

zeroflame15 said:
Thanks @zxcv88
After installing the lenovo USB driver, the !Android in Other devices was updated.
LenovoUsbDriver_v1.1.34
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Boot into bootloader mode and "fastboot flashing lock" runs without any issue
Appreciate all for the advise and help! Appreciate ~
Click to expand...
Click to collapse
sorry zeroflame15..... 2 question.... from (fake) global to china stock :
1 flash china
2 lock bootloader
right?
and most important.....lock bootloader is a "must" or is a choice?
if i dont lock bootloader i haven not ota and L1 ? im interested only in OTA updates....not l1 widevine...
thanks

fazioso said:
sorry zeroflame15..... 2 question.... from (fake) global to china stock :
1 flash china
2 lock bootloader
right?
and most important.....lock bootloader is a "must" or is a choice?
if i dont lock bootloader i haven not ota and L1 ? im interested only in OTA updates....not l1 widevine...
thanks
Click to expand...
Click to collapse
Sort of yes.
Initially after flash to stock china rom, i was able to OTA. But subsequent check for updates will get error saying devices is rooted.
After locked bootloader, tried OTA again and indeed there is another new updates.
Saw some chinese video for those who wanted the rooted status and also to perform OTA updates, they are using magdisk to hide the root.

zeroflame15 said:
Sort of yes.
Initially after flash to stock china rom, i was able to OTA. But subsequent check for updates will get error saying devices is rooted.
After locked bootloader, tried OTA again and indeed there is another new updates.
Click to expand...
Click to collapse
thanks!
its seems most difficult to lock/unlock bootloader that flash rom.....
but you need ZUI Unlock Website also for lock? cause seems need only for unlock...right?

No need for lock. Like what others have mentioned. Just a single line command and it works as long you got the right drivers installed.

Tropaion said:
How To Lock and Unlock Bootloader - Xioaxin Pad Pro 2021 - TB-J716F
5. Go to the ZUI Unlock Website and request the unlock image
View attachment 5432885
6. You should get a mail where you can download a file called "sn.img".​
Click to expand...
Click to collapse
my friend ....i have a unlocked bootloader ,cause for now i have the fake global....want to change in china stock....
but i ask anyway to the zui unlock website the sn.img in case i need in future.....
just a question.... after many hours or days i will receive the sn.img file? pass 10 minutes and nothing yet