Database Users

[Q] Softbrick - Fastboot and Hboot only - Solved

While trying to flash my Tattoo I ran into some trouble, and now I'm pretty much stuck at using Fastboot and holding DownVolume+TurnON to get into HBoot.
click pvt ship s-on
hboot-0.52.0001 (clic10000)
microp-0203
radio-3.35.07.20
sep 22 2009, 14:40:39
Click to expand...
Click to collapse
To be more specific, I was following the " [GUIDE] All Tattoo questions and answers see here (from A to Z)! " from "TheSSJ" user and when I did:
# insmod ./tattoo-hack.ko
Click to expand...
Click to collapse
This was the answer:
insmod: init_module '/data/local/bin/tattoo-hack.ko' failed (file exists)
Click to expand...
Click to collapse
I thought, "hmm if it's there then it must've started" and proceeded. Once I entered:
- # ./flash_image boot /sdcard/boot.img
Click to expand...
Click to collapse
I got many errors, that I know are not supposed to happen.
I've tried a awfull lot of things and no success. Later I'm gonna get an adapter from microsd to Sd so I can directly change my files, and attempt to put a new recovery.img to flash, but any suggestions on how to solve this?
I also almost did a gold card, only have to use the hex editor to in fact create it. Since I no longer can use my Tattoo can I instead use a MicroSD->Sd card adaptor in order to finish it?
Edit:
I can also get into the recovery console, the one with a phone and the triangle with a "!" inside of it. However I have no idea on what I can do there.
Edit2:
Tried again to:
fastboot recovery recovery.img
Click to expand...
Click to collapse
Got the following:
sending 'recovery' (3998 KB)... FAILED (remote: not allow)
finished. total time: 0.000s
Click to expand...
Click to collapse
And to be clear, "fastboot devices" does indeed list one device.
This has been solved, look at the next post.

Since I had the info for a Golden Key I simply bought a MicroSD adapter for my computer, and finished turning it into one. Inserted it into the Tattoo.
Then I entered into VolDown+TurnON and choose back for fastboot, and connected the USB.
Now, I downloaded the RUU and HTC Sync. Since I had a problem connecting the Phone with Ruu, I, and I quote another post here on the forums:
7. "Start" > Right Click "Computer" > "Manage" > "Device Manager"
8. Check that the "ADB Interface" reads "My Hero", not "Android bootloader drivers" or anything else.
If it does then:
Right click "Android bootloader drivers" > "Update Driver Software" > "Browse my computer..." > "Let me pick from..." > "Have Disk..." > "Browse" > "C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64" > "androidusb.inf"
Once selected click "OK".
"My HTC" should show in the list of "compatible hardware" now, so select that and click "Next" to install the driver. Switch off the phone (may have to pull the battery).
Click to expand...
Click to collapse
Then just went along with RUU and everything went perfect. My Tattoo is now once again at my pocket. Of course you'll lose all your data, but I rather not win a new brick...
Now I'm going to search around on how to know exactly how my phone is after the RUU, since I intend to update it to 2.2.

Sorry do you know how to fix this?
{
"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"
}
because I already made a goldcard and press down vol + power still stuck at the same way...
I didn't do anything before this just make a hard reset and stuck in here

That's the factory recovery console (default), I think. I myself ain't a expert (newbie into this whole scene actually), just keep searching through the forums, although most of it is kind of messy and confusing. You just have to find the right words, and get a bit of luck.

mewmewmew said:
Sorry do you know how to fix this?
Click to expand...
Click to collapse
Same problem for me now. Please help me. My Tattoo is dead.

How open bootloader on Zuk Z2 (standard & pro)

Step 1:
Open System App
Go to: About > Status
{
"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"
}
Make a note of your 'Serial number'
Check if your serial is either 6 or 8 digits. If the digits are 8, you can use the Z1 unlocking tool method to unlock your ZUK Z2 Pro.
Note: Serial numbers with 6 digits after unlock command must use also CM ZUK Z1 command references. Another guide is being prepared for this at the moment. Please bare with us.
Step 2:
Obtaining the tools..
Visit http://developer.zuk.com/bootloader
In the box below the 'Z1' drop down enter your 8 digit serial number from Step 1. Enter your email in the box below the serial number and check both the boxes. To submit press the Blue button.
You will then see the following popup message box:
解锁bootloader
解锁文件已经发送到您的邮箱，请查看邮件并进行下一步。
Note: Ensure you are logged into your ZUK account to process this request. Also please pay attention for an email from ZUK.com - Check SPAM folders etc for this email as in some cases it lands inside this folder.
Step 3:
Unlocking the phone...
With the email now received it's time to do some dev stuff...
尊敬的ZUK用户，您好
&nbsp您已经在ZUK开发者平台申请了解锁您的ZUK智能设备的bootloader。
&nbsp附件是适用于您的设备的解锁文件，请妥善保管。
&nbsp请访问这里了解如何进行解锁操作。
&nbsp如果不是您本人操作或者您改变主意，请忽略这封邮件，您的设备将不会受到任何影响。
ZUK开发者平台
Download the unlock_bootloader.img from the email and place it somewhere easy to find for flashing.
Next step, boot your phone into Fastboot mode. You can do this via:
adb reboot bootloader
Next run the following command:
fastboot -i 0x2b4c flash unlock unlock_bootloader.img
You will see:
target reported max download size of 1610612736 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.037s]
writing 'unlock'...
OKAY [ 0.053s]
finished. total time: 0.090s
Now run the following:
fastboot -i 0x2b4c oem unlock-go
You will see:
...
OKAY [ 0.041s]
finished. total time: 0.041s
Finish up with:
fastboot reboot
NB if you have 8 digits on serial number, just put that
if you have 7 digits, add a 0 (zero) at the end
if you have 6 digits, add two 0 (zero) at the end
Credits: My work and image from zukfans.it and zukfans.eu

I have ZUI 2.0 Beta install and can confirm this is working even for beta devices.

How to sign up in the zuk developer website? I entered my phone number in sms verification field but I never get any sms. Please help..

snugroho3 said:
How to sign up in the zuk developer website? I entered my phone number in sms verification field but I never get any sms. Please help..
Click to expand...
Click to collapse
Had the same issue, until I found out, you can register via email on their main website (google translation of webiste helped me ^^)

How long does it takes till the email arrives?
I´ve waited now one day and nothing happened. And the Spam-Folder is empty too

Is there a driver that I need to download? My computer is set up for adb (verified with my OP3) and it cannot see my z2 pro at all.
---------- Post added at 13:21 ---------- Previous post was at 13:14 ----------
Nordlord said:
How long does it takes till the email arrives?
I´ve waited now one day and nothing happened. And the Spam-Folder is empty too
Click to expand...
Click to collapse
You can contact them via email also. That's what I did to get mine.

The 'fastboot -i 0x2b4c flash unlock unlock_bootloader.img' don't do anything from my shell there is no information on going.
I bet some issue on the -i 0x2b4c how can I discover the ID of my device? Thank you.

Swarai said:
Is there a driver that I need to download? My computer is set up for adb (verified with my OP3) and it cannot see my z2 pro at all.
---------- Post added at 13:21 ---------- Previous post was at 13:14 ----------
You can contact them via email also. That's what I did to get mine.
Click to expand...
Click to collapse
Hello,
It has been almost one week I requested Zuk to get the booloader unlock file but so far no email in my mailbox (spam included)…
How did you contact them directly via email to get it?
What is the email address you used?
Many thanks

zyvex_14 said:
Hello,
It has been almost one week I requested Zuk to get the booloader unlock file but so far no email in my mailbox (spam included)…
How did you contact them directly via email to get it?
What is the email address you used?
Many thanks
Click to expand...
Click to collapse
[email protected]

Swarai said:
[email protected]
Click to expand...
Click to collapse
Hi,
Thanks for the email address.
I have just sent them the request.... Let's see now how long it will take
Will keep you posted.
Edit: I read on some other forum that it doesn't work with gmail and hotmail adresses.
that is the reason I didn't get the message back.
So I created a GMX address and within 2sec I got the file... I can now unlock my bootloaded.

miheilo said:
Had the same issue, until I found out, you can register via email on their main website (google translation of webiste helped me ^^)
Click to expand...
Click to collapse
What is the main website? I tried with www.zuk.com but it is the same registration form (need verification code via sms, which I never receive).
Please someone tell me how to register to that da*m site...

snugroho3 said:
What is the main website? I tried with www.zuk.com but it is the same registration form (need verification code via sms, which I never receive).
Please someone tell me how to register to that da*m site...
Click to expand...
Click to collapse
It works for me. On the main site go to register in the top right corner and then you have two tabs one for phone and the other for email registration.
Try also this link: https://passport.zuk.com/wauthen3/w...lenovoid.thirdname=null&lenovoid.qrstate=null

miheilo said:
It works for me. On the main site go to register in the top right corner and then you have two tabs one for phone and the other for email registration.
Try also this link: https://passport.zuk.com/wauthen3/w...lenovoid.thirdname=null&lenovoid.qrstate=null
Click to expand...
Click to collapse
Thanks! The link is working. I can register :highfive:

No mater what I do I can't get the unlocked_bootloader file on my email account. Tried 4 different addresses already and nothing

Does this procedure wipe userdata and internal sdcard.

Yes it does

Hi there,
I'm stuck trying to unlock the bootloader for my Zuk Z2 (not pro) - I've received the unlock_bootloader.img via email and transferred it to the adb_fastboot directory. When I try and run the command to unlock the bootloader, I keep getting an error:
target reported max download size of 1610612736 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.035s]
writing 'unlock'...
FAILED (remote: unlock failed)
finished. total time: 0.090s
I've tried with multiple stable stock roms, but I suspect the problem is that in the developer options, I cannot see an option "Enable OEM unlocking".
Can anyone help me unlock the bootloader?
Thanks

Hi all,
i am stuck with fastboot. I reboot into fastboot with "adb reboot bootloader", but then "fastboot devices" does not show any device. "fastboot --version" results in "fastboot version fd9e4d07b0f5-android". Is this the problem? Do i need an other version?
Greetings from Vienna,
Georg

oldie51 said:
Hi all,
i am stuck with fastboot. I reboot into fastboot with "adb reboot bootloader", but then "fastboot devices" does not show any device. "fastboot --version" results in "fastboot version fd9e4d07b0f5-android". Is this the problem? Do i need an other version?
Greetings from Vienna,
Georg
Click to expand...
Click to collapse
try this guide mate
http://zukfans.eu/community/threads/zuk-z2-bootloader-unlock.62/
command should be adb devices. initially it wont show, because it does have id, you need to provide id. follow the above guide.

lazydesi said:
try this guide mate
http://zukfans.eu/community/threads/zuk-z2-bootloader-unlock.62/
command should be adb devices. initially it wont show, because it does have id, you need to provide id. follow the above guide.
Click to expand...
Click to collapse
Thanks for your fast response, but i don't have a problem with adb. I followed the unlock instructions above, adb works fine ("adb devices" returns my S/N and "adb reboot bootloader" boots into bootloader). But then "fastboot devices" doesn't show anything and "fastboot -i 0x2b4c flash unlock unlock_bootloader.img" just answers "< waiting for device >". To sum it up, the Z2 (unmodiefied out of the box) does not respond to fastboot commands, even though the connection (drivers, debug mode, etc.) works fine.
Georg

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.

[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?