Hi guys
I really need your help!
Just unlocked my new z4 tablet and flushed a new kernel.
The short version, I've flushed androplus kernel v10 and rebooted the tab and completed the android wizard.
And the stupid thing is, I've forgot to activate usb debugging and rebooted the tab.
And now I have a black screen. The tablet doesn't show anything on the display.
After turn on it just vibrates shortly, but the screen is black.
The only thing I can do ist start fastboot, but since I did not enabled usb debugging I can't do anything, like reflush:
HTML:
C:\adb>fastboot flash boot boot.img
sending 'boot' (31948 KB)...
OKAY [ 1.239s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 1.256s
I'm pretty sure it is this stupid sony my xperia protection, I was so stupid to turn on "locate my device" or whatever.
(Before the fastboot oem unlock, I had to disable this thing in the android settings. If it was activated I got command not allowed from fastboot)
I have a black screen, usb debugging disabled and this stupid xperia protection is enabled, what can I do?
Please help
Thanks a lot!
Awesome, was able to fix it myself. With great help from this forum (Other older posts).
If anyone got the same problem, don't worry if fastboot doesn't work anymore.
You would be able to flush a new firmware (stock.)
1. Get latest version of flashtool
2. Download a firmware for your Device (Xperifirm)
3. Flush firmware in flashmode (Connect your device in flashmode, not fastboot)
4. Finish, your device will boot again!:laugh::laugh::laugh::laugh::
Related
@Diamondback
TF201 32GB
Android cardhu-user bootloader <1.00 e> released by "US_epad10.4.2.15-20120917"
Hi guys thanks in advanced for any assistance.
Like many others, I unlocked my tf201 bootloader, rooted my device, Did the OTA update and lost root.
After waiting a long while, I finally saw urkel's guide and figured I'd do a fresh start.
Something went wrong and now my device will not fully boot.
I can get into Fastboot with no problem and run fast boot commands, but that's all.
If I try something else it says:
Booting failed
Unrecoverable bootloader error (0x00000000).
From what I read, the only way you are hard bricked is when you can't get into anything, and you're stuck on the EEEpad splash screen. I can get to the ASUS splash screen, and in the top right corner it says this device is unlocked.
I've steps from lot's of threads, but none have really worked.
I did notice that anytime I flash something to the staging via fastboot, if I try to send another command I get something like,
C:\Users\...\Android SDK>fastboot -i 0x0B05 flash staging blob
sending 'staging' (537604 KB)...
OKAY [ 91.050s]
writing 'staging'...
OKAY [ 2.184s]
finished. total time: 93.235s
C:\Users\joshb\Android SDK>fastboot -i 0x0B05 reboot-bootloader
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.637s
The only time I get that failed is after I've sent something to staging.
Thank you far taking the time to look at my issue.
Bricked???
I have the same problem but i have fastboot and can get the 3 icons. RCK android wipeall. but if i do a fastboot getvar all it say's encrypted and unlocked:NO altough it is unlocked. I think that is the problem because now i can't install twrp or anythink els for that mather.
So i still belief that there is a way to get out off this.
I did sent it to ASUS but they wanted to charge me €344,- euro for repair(new MB € 223.- ex vat and work € 46.7 ex vat). and you can buy a new one for €399,- which i think is not fair. they sold me a machine whit components that not all work (eg GPS) and now they want €345,- for a new motherboard on which probebly the GPS still don't work.
They are able to make a tool so all encrytion is off and we have total controll off ou're machine.
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
Hi all,
it seem that I bricked my Sony Xperia X F5122.
I'll try to explain all the steps I took as detailed as possible hoping that I can recover my phone with your help somehow.
Steps:
- unlocked bootloaded following official Sony documentation (1)
- extracted TA partition
- installed Sailfish X according to official documentation (jolla.com/sailfishx-linux-instructions/)
- successfully ran Sailfish X for 1,5 years with all things functioning
- decided to reflash stock android to give phone to my daugther
- connected phone to Win10 PC in flashmode (Volume down while connecting to PC)
- started EMMA tools from Sony
- it detected the phone and presented several flashable images
- started flashing of latest image which finished successfully
- after flashing the phone boot-up failed with a message that the image is broken
- restarted phone and tried to get into flashmode again
- flashmode failed with LED blinking in a strange colors code (2)
- booted into fastboot mode (volume up while connecting to PC)
- booted TWRP (3) successfully
- flashed TA partition back to phone using abd mode available thanks to TWRP as I thought that it will enable the flashmode again
Current state:
- can set phone into fastboot mode
- all actions initiated with fastboot command are answered with "remote: Command not allowed" (4)
- tried to flash OEM using all available AOSP images from Sony (5)
- tried to unlock phone again (6)
- tried to boot TWRP image again (7) results in error "Your device has failed verification and will not work properly."
- cannot set phone into flashmode with LED blinking described above
- when booting phone the following error message is shown: "Your device has failed verification and will not work properly."
- when connecting to PC without any keys pressed, the same LED blinking is happening (2)
I assume that the commands are rejected due to enabled bootloader lock because of flashing the TA partition.
As no image I tried to run boots up due to verification error I cannot unlock the bootloader via developer settings thus not clear the TA partition again.
I also assume that I could flash the stock Xperia X image when I could enter the flashmode.
1) Does anyone of you know a way to unlock the bootloader via USB port?
2) Does anyone maybe know a boot image which succeeds verification and I could boot using fastboot mode?
(1) developer.sony.com/develop/open-devices/get-started/unlock-bootloader/how-to-unlock-bootloader/#tutorial-step-1
(2) dark red (~1 second), light red (~1 second), green (~3 seconds), yellow (< 1 second), restart with dark red
(3) twrp.me/sony/sonyxperiax.html
(4) several command outputs:
Code:
$ fastboot flash oem SW_binaries_for_Xperia_AOSP_N_MR1_3.10_v13_loire.img
target reported max download size of 536870912 bytes
sending 'oem' (164639 KB)...
OKAY [ 5.194s]
writing 'oem'...
FAILED (remote: Command not allowed)
finished. total time: 5.198s
(5) developer.sony.com/develop/open-devices/downloads/software-binaries
(6) unlock command:
Code:
fastboot oem unlock 0x<valid-unlock-code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.004s
(7) boot TWRP
Code:
fastboot boot /home/aa_ulm/Downloads/twrp-3.3.1-0-suzu.img
downloading 'boot.img'...
OKAY [ 0.704s]
booting...
FAILED (status read failed (No such device))
finished. total time: 12.245s
Hi guys.
New to the forums. I know that there are three threads that already detail what I am asking for. I just don't get it. I try to follow one of them and it says "run Qfil; install QPst." I would be happy to do that, but I just do not know where they are or how to run them.
Then one of the twrp files (whatever that is) has been taken down because of "gross violations." I cannot figure out how to do what the threads say to do.
Can someone please tell me how to root this thing? Step-by-step. With all the downloads. Thanks for your help.
Feel free to close this thread when a response appears.
Can someone please respond to this now that it is in the correct forum?
@wsmyth
May be this detailled guide helps you: https://www.getdroidtips.com/twrp-recovery-unimax-umx-u683cl-root/
Good luck.
Thank you
Thank you very much. I am starting there!
Help
I followed all instructions. I cannot get a twrp to load.
Good instructions, but I had these problems.
1. There is no link to a TWRP file. I use the link shown, and I get "Stock April Patch" from mediafire. None of the files here have TWRP in the filename.
2. I did go to https://rootmygalaxy.net/root-twrp-umx-u673c, a similar site. It did have a link to a TWRP file to use. Your instructions are identical.
So I turn off the device. I turn it on with power and volume-up button. The device goes to Mr. Android lying down with the message "No Command." I look at some other sites, and it tells me to hold power, and press power-up.
This takes me to Android Recovery menu. On Windows cmd line (ADB and Fastboot folder), I type adb reboot bootloader. The Windows screen responds no device/emulators found.
So I select option on the Android to Reboot to Bootloader. The device boots into FASTBOOT MODE with START at the top. I imagine that this is what the above command is intended to do. For fun, I type the same command above in Windows, and I get the same response. But when I type fastboot devices , I get the device serial number (as shown on the START screen) and the word fastboot.
I imagine the device is ready to install TWRP. I use the TWRP file that I downloaded from the other page (remember, yours and their instructions are identical). I type fastboot flash recovery twrpname.img in Windows, and I get this set of messages:
target reported max download size 26214400
sending 'recovery' (20220 KB)...
OKAY [ 0.650s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.668s
Any help is GREATLY APPRECIATED.
wsmyth said:
I type fastboot flash recovery twrpname.img in Windows, and I get this set of messages:
target reported max download size 26214400
sending 'recovery' (20220 KB)...
OKAY [ 0.650s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.668s
Click to expand...
Click to collapse
IMO you didn't do anything wrong.
To me it seems that OEM/Carrier did not put the typical Fastboot commands into the boot-loader.
BTW:
To test the TWRP recovery without permanently flashing, run the following:
Code:
fastboot devices
fastboot boot twrpname.img
Follow up
Thanks. When I type that code, I get...
downloading 'boot.img'...
OKAY [ 0.640s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.646s
Thanks again
Does it matter that I have no SIM card in this device. on the START screen, I have this...
Press volume key to select, and press power key to select
FASTBOOT MODE (in red)
PRODUCT_NAME - MSM8909
VARIANT - QRD eMMC
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - a10b7526
SECURE BOOT - disabled
DEVICE STATE - unlocked (in red)
Is there anyone that can help me on this? Should I take a magnet to the back of the device? Would that help?
UMX U683CL root?
hey guys, when it comes to all of this i would say i am beyond a newb. so if i violate any protocol i plead ignorance and hope that you will bear with me. i have my disable sister who lives with me and i am responsible for who has had a...
forum.xda-developers.com