Hi all, I have an ATT m9 and received my bootloader bin file for unlocking. I flashed the unlock code just fine and the unlock bootloader confirmation popped up and froze.
There is a green loading bar on top of the message completely full, however i cannot accept the unlock or power cycle my device at all. I have tried holding the power button for more than a minute, fastboot commands, nothing works. Fastboot shows the device when i connect it, but it does not respond to any command.
Here is the terminal output when i flashed the unlock.
Code:
fastboot flash unlocktoken Unlock_code.bin
< waiting for device >
target reported max download size of 800000000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 2.002s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : disable
(bootloader) unlock token check successfully
OKAY [ 0.008s]
finished. total time: 2.011s
Now I am just waiting for my FULLY CHARGED battery to die....
What should I do?
Any help appreciated. Thanks!
Have you tried pressing the power and volume up buttons at the same time for at least 10 seconds or better?
fernandezhjr said:
Have you tried pressing the power and volume up buttons at the same time for at least 10 seconds or better?
Click to expand...
Click to collapse
That worked! Thanks! rebooted, but boot loader still says locked. Should I try again?
Edit: I figured it out. You have to be in download mode to unlock and NOT RUU mode.
Related
I was unlocking the bootloader. I entered the final command fastboot oem unlock UNIQUE_KEY and the device said Unlock...
It was supposed to reboot but it's stuck. It's not completely bricked coz after 10 min or so I entered
fastboot oem get_unlock_data and got this response:
...
(bootloader) Could not get unlock data!
OKAY [ 0.018s]
finished. total time: 0.020s
What can I do? Should I send a command to reboot?
I am having the same problem, you already decided?
First off, I received this phone from a friend of mine who received it brand new from textnow through the mail. I went through the steps to unlock the bootloader and errors came of that, but on the device it says "Device is UNLOCKED. Status Code: 3" so i assumed the bootloader was already unlocked based on what i have already researched and found. If this is incorrect, let me know and i will answer accordingly.
Assuming that my assumption is right, I keep getting errors when i try to install twrp. either that, or it appears to do nothing.
Going by the instructions on the cyanogenmod wiki for flashing twrp, fastboot returns this when i enter the "fastboot flash recovery your_recovery_image.img" command where "twrp.img" was my image name and then does nothing:
C:\Users\Me\Downloads\android-sdk_r24.4.1-windows\android-sdk-windows\platform-tools>fastboot flash recovery twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 268435456 bytes
sending 'recovery' (6808 KB)...
OKAY [ 0.219s]
writing 'recovery'...
OKAY [ 0.302s]
finished. total time: 0.524s
I did the same with mfastboot and there are no errors, but it still does nothing:
C:\Users\Me\Downloads\mfastboot-v2>mfastboot flash recovery twrp.img
target max-sparse-size: 256MB
sending 'recovery' (10270 KB)...
OKAY [ 0.329s]
writing 'recovery'...
OKAY [ 0.448s]
finished. total time: 0.779s
I tried each of these a few times to no avail. Ive tried waiting at each step, tried the "fastboot reboot" and "mfastboot reboot" commands after the flash commands to where it booted straight up to android, tried the "fastboot reboot" and "mfastboot reboot" commands after the flash commands where i held the buttons to go back to fastboot mode and nothing.
Other things to note:
-Power+Volume down boots to a screen that has "AP Fastboot Flash Mode (Secure)" in red letters where there is device information at the bottom and I can only cycle through one option at a time at the top (if that makes sense).
-Selecting "Restart Bootloader" and "Recovery Mode" brings me back to this same screen mentioned.
Thank you in advance for your replies. I am completely new to this and appreciate the help.
I am only able to boot into fastboot mode and not the bootloader if that was not clear previously. I was up until 6am last night (or this morning) trying to figure it out and it didnt cross my mind this may be my actual issue. Thanks.
Hi all,
First of all, sorry for my english...
I've got a problem to root a phone.
I followed this guide :
https://forum.xda-developers.com/android/development/root-ulefone-armor-2-easy-rooting-t3780055
But I just realized, it's for ulefone Armor 2, while I try to root a Armor 2S..
I followed instructions, but I've got a problem on the point 2.
Code:
C:\Users\greg\Downloads\root\platform-tools>fastboot.exe flashing unlock
(bootloader) Start unlock flow
OKAY [ 5.301s]
Finished. Total time: 5.305s
C:\Users\greg\Downloads\root\platform-tools>fastboot.exe flash recovery recovery.img
Sending 'recovery' (15218 KB) OKAY [ 0.405s]
Writing 'recovery' OKAY [ 0.356s]
Finished. Total time: 0.777s
C:\Users\greg\Downloads\root\platform-tools>fastboot boot recovery.img
Downloading 'boot.img' OKAY [ 0.392s]
booting FAILED (remote: 'invalid ramdisk address: overlap with the download image')
Finished. Total time: 0.417s
After few test, who doesn't work at all, I've decide to reboot my phone.
Now, It's stuck on the main screen with this text :
Code:
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds.
And after 5 seconds, the screen go black for one second and return to the message.
And I can't go to recovery mode anymore. Volume+ and Power button don't do anythong but show this "Orange state" screen.
Please tell me there is a solution to unbrick this phone..
Thanks in advance
Try to relock again bootloader with command : fastboot oem lock maybe it can fix that issue but do at your own risk !!!
Thank you for your answer, but the phone is not recognized by the computer at this point.
I can not send command from the PC (adb or fastboot)
Try some key combination keys like :
hold Vol + and plug usb
hold Vol - and plug usb
hold Vol + ; Vol - and plug usb
If that doesn't work , let your battery to be completely empty 0% and repeat process . Good luck
Hey guys,
I have an European LG G5 H850 with an unlocked bootloader. It is my first time rooting, and after unlocking the bootloader, I wanted to boot TWRP once, but I didn't want to install it, but instead keep the stock recovery untouched. So I booted into the bootloader, entered "fastboot boot twrp.img" and I got this message:
downloading 'boot.img'...
OKAY [ 0.462s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.482s
I have absolutely no idea what I'm doing wrong. I made sure twrp.img is referring to the correct file, and I tried both the Android SDK platform tools and the 15 seconds ADB installer, but none of them worked. When I try flashing the recovery with "fastboot flash recovery twrp.img", it seems to work because this appears:
target reported max download size of 536870912 bytes
sending 'recovery' (20900 KB)...
OKAY [ 0.471s]
writing 'recovery'...
OKAY [ 0.198s]
finished. total time: 0.670s
But when I try to boot into the bootloader again, it just gives me the option to do a factory reset, nothing else. So I assume that something went wrong. I have absolutely no idea what it could be, so please help me. I also asked on reddit, but didn't get any answers so far. Any help would be greatly appreciated!
Thanks in advance!
JonSchnee777 said:
Hey guys,
I have an European LG G5 H850 with an unlocked bootloader. It is my first time rooting, and after unlocking the bootloader, I wanted to boot TWRP once, but I didn't want to install it, but instead keep the stock recovery untouched. So I booted into the bootloader, entered "fastboot boot twrp.img" and I got this message:
downloading 'boot.img'...
OKAY [ 0.462s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.482s
I have absolutely no idea what I'm doing wrong. I made sure twrp.img is referring to the correct file, and I tried both the Android SDK platform tools and the 15 seconds ADB installer, but none of them worked. When I try flashing the recovery with "fastboot flash recovery twrp.img", it seems to work because this appears:
target reported max download size of 536870912 bytes
sending 'recovery' (20900 KB)...
OKAY [ 0.471s]
writing 'recovery'...
OKAY [ 0.198s]
finished. total time: 0.670s
But when I try to boot into the bootloader again, it just gives me the option to do a factory reset, nothing else. So I assume that something went wrong. I have absolutely no idea what it could be, so please help me. I also asked on reddit, but didn't get any answers so far. Any help would be greatly appreciated!
Thanks in advance!
Click to expand...
Click to collapse
The "fastboot boot twrp.img" command didn't work for me either, but the keystroke to do a "factory reset" -- which is really a keystroke to enter recovery -- did work. Specifically, I
powered down the LG G5 completely (nothing attached to the USB-C port, or battery pull)
with the power off (preferably via battery pulled), held down the Volume Down and Power/Fingerprint buttons
As soon as the LG logo appeared, released and re-pressed the Power/Fingerprint button, all the while continuing to hold down Volume Down
Held down both while the LG logo showed, releasing them after the white screen appeared asking whether you want to do a full erase. Answer yes (Press and release Volume Down until the Yes is grey, then press Power/Fingerprint button)
It prompts you once again. Answer yes again the same way.
At this point after a few seconds, TWRP starts. It hasn't actually done an erase.
This is important: after fastboot flash recovery twrp.img, you need to pull the battery to power down, and then follow the instructions above to enter TWRP. Do not boot into system with the stock ROM after fastboot. It will replace TWRP with the stock recovery at boot time, and in that scenario, the full erase mentioned above actually does erase data and internal storage.
TWRP will on first start change the system image (once you "allow modification") so that the stock ROM stops replacing it at boot time.
If you did boot up the stock ROM after fastboot, you will need to re-enter fastboot and flash TWRP again (power down with USB-C port clear, hold down Volume Up, insert USB-C cable, fastboot flash recovery twrp.img). Then pull the battery with fastboot still running, then boot into TWRP as above.
Unfortunately most writeups aren't crystal clear about the correct sequence of steps. Most cover some steps and gloss over others.
You aren't doing anything wrong.
LG did not put the typical Fastboot commands into the bootloader.
Fastboot flash does not work either.
You need to follow the other methods available on xda to get TWRP on your device.
Edit: woops. That's only with H830. Follow the instructions in the H850 TWRP thread.
Sent from my LG-H830 using Tapatalk
I have been trying for the past few days to try to recover my CMR-W09(C00) device with no luck.
What it looks like now?
At the moment there is nothing showing on the screen regardless of what button combinations I've tried (Vol Up+Vol Down+Pwr/Vol Up + Pwr/Vol Down + Pwr, and each with USB power cable plugged in and without). The phone is able to get into fastboot mode (detected by running fastboot devices) automatically, fastboot reboot would get it to fastboot again (i.e., doesn't go to any other mode). The screen is completely dark with nothing at all.
From fastboot I can even see the current firmware version is 195. (CMR-W09C00B195 (8.0.0.195))
What did I do?
Flashed the 160 (CMR-W09C00E160R1P160B160 (9.0.1.160)) firmware which I found on firmware finder, and used EMUI Flasher to flash the firmware. (Found here: https://forum.xda-developers.com/mate-20-pro/how-to/guide-manual-updating-firmware-t3893171) Flash seems to have worked and at 100% it said something along the line of checksum failed, rebooted, and never came back to life again.
What I have tried?
1. No eRecovery (that would be easy)
2. Use HiSuite to repair devices, received unsupported device error.
3. Flashed recovery-ramdis, recovery-vbmeta and recovery-vendor and ramdisk that were extracted from 195 OTA (http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3776/g1699/v225819/f1/full/update.zip) and 160 OTA(http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3776/g1699/v234512/f1/full/update.zip). Nothing happened. In Fastboot I can flash these three partitions and system, anything else would return command not allowed.
4. Tried DC Unlocker, when flashing xloader I got command not allowed error, in the end DC Unlocker refunded me.
5. Tried dload method with UPDATE.APP in dload folder only as well as the entire contents (META-INF/tags files and mbn files together with UPDATE.APP) in dload file, reboot using three button combo
6. In desperation I even tried to buy some "factory flash" image which was supposedly to be used by Huawei repair centres internally (with two zip files) to extract to dload folder. Again didn't do anything.
7. Tried to contacted FH to see if they support unbricking this and didn't hear a response.
8. Went to local Huawei authorized repair centre and they don't seem to have seen this device. They told me they can only fix devices bought locally.
9. Tried to flash in TWRP by flash the recovery_ramdisk partition.
All of above leads to nothing (i.e., it goes back to the blank screen with fastboot, however I can hear the USB connected and disconnected sound and HiSuite popped up again which tells me the reboot actually took place).
Some output from fastboot command:
E:\Android\M5>fastboot devices
HYY6R189********** fastboot
E:\Android\M5>fastboot oem get-product-model
...
(bootloader) CMR-W09
OKAY [ 0.013s]
finished. total time: 0.013s
E:\Android\M5>fastboot getvar vendorcountry
vendorcountry: all/cn
finished. total time: 0.013s
E:\Android\M5>fastboot oem get-build-number
...
(bootloader) :CMR-W09 8.0.0.195(C00)
OKAY [ 0.014s]
finished. total time: 0.015s
E:\Android\M5>fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
finished. total time: 0.027s
E:\Android\M5>fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :CMR-W09 8.0.0.195(C00)
OKAY [ 0.015s]
finished. total time: 0.016s
Click to expand...
Click to collapse
I think I am pretty much out of options right now, but if there is anything
Just wondering if there is anything else I haven't tried that I should?
I think "command not allowed" indicates that your bootloader is locked. If I am right about that, you will need to unlock your bootloader again before you flash anything via fastboot.
Download ONLY the Chinese hisuite, it support CMR-W09C00 as i have already checked
consumer.huawei.com/cn/support/hisuite/
Then reconnect the device with your pc, go to system recovery and follow the instructions
The global hisuite support only few devices
Plz report back to me if it worked
This happened to me once in my CMR-W09C432 i stucked in fastboot mode ( black screen) while i was trying to install the emui 9 beta, but i sent it to huawei service centre, they replaced the whole motherboard and i had to unlock the bootloader again.
But first of all do what i wrote above (the chinese hisuite)
Regards
thref23 said:
I think "command not allowed" indicates that your bootloader is locked. If I am right about that, you will need to unlock your bootloader again before you flash anything via fastboot.
Click to expand...
Click to collapse
Thanks for your input, I am able to write to recovery_ramdisk, recovery_vbmeta and recovery_vendor, as well as system partitions, however XLOADER and ERECOVERY* and FASTBOOT partitions seems to be out of touch.
Here are some more output from fastboot:
fastboot oem check-rootinfo
...
(bootloader) status : RISK
(bootloader) version : v1.1
(bootloader) current status: SAFE
(bootloader) old status : SAFE
(bootloader) change_time : 0
(bootloader) item: root-prop, status: SAFE, credible: Y
(bootloader) item: setids, status: SAFE, credible: Y
(bootloader) item: verifyboot, status: SAFE, credible: N
(bootloader) item: verity-enable, status: SAFE, credible: Y
(bootloader) item: fblock, status: locked, credible: Y
(bootloader) item: userlock, status: unlocked, credible: Y
OKAY [ 0.031s]
finished. total time: 0.032s
fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.008s]
finished. total time: 0.009s
Click to expand...
Click to collapse
Are there multiple lock? What is the fblock? Would unlock that allow me to write to the XLOADER partition?
THE MAXIMUM POWER said:
Download ONLY the Chinese hisuite, it support CMR-W09C00 as i have already checked
consumer.huawei.com/cn/support/hisuite/
Then reconnect the device with your pc, go to system recovery and follow the instructions
The global hisuite support only few devices
Plz report back to me if it worked
This happened to me once in my CMR-W09C432 i stucked in fastboot mode ( black screen) while i was trying to install the emui 9 beta, but i sent it to huawei service centre, they replaced the whole motherboard and i had to unlock the bootloader again.
But first of all do what i wrote above (the chinese hisuite)
Regards
Click to expand...
Click to collapse
Thanks for your response, I've tried that and unfortunately it failed at 99% at the step Writing Recovery. (Simply said failed to repair with no other error).
zhuanyi said:
Thanks for your response, I've tried that and unfortunately it failed at 99% at the step Writing Recovery. (Simply said failed to repair with no other error).
Click to expand...
Click to collapse
Im sorry about that, try to send it to china huawei service as they might repair it their for free because yours is C00