Related
im having trouble trying to root my phone again after it crashed and had to start from beginning. When i try fastboot flash boot Z_DooMLoRD_CF-Auto-Root-ported_FW-350.img it gives me fails and says FAILED <Remote: command not allowed> does any body know what im doing wrong? I managed to root it teh first time no problem.
Cheers
sturtz1987 said:
im having trouble trying to root my phone again after it crashed and had to start from beginning. When i try fastboot flash boot Z_DooMLoRD_CF-Auto-Root-ported_FW-350.img it gives me fails and says FAILED <Remote: command not allowed> does any body know what im doing wrong? I managed to root it teh first time no problem.
Cheers
Click to expand...
Click to collapse
Is you bootloader unlocked?
krabappel2548 said:
Is you bootloader unlocked?
Click to expand...
Click to collapse
yes the bootloader is unloack but i had my phone rooted before then had to use pc companion to repair it, ive unlocked it again to be sure.
It seems driver problem.
I met the same problem as well as others yesterday, when I unlock, relock, re-unlock, root locked, root unlocked, flash recovery... for some crazy reason.
Try these:
Connect to flashtool (beta2 or beta4) with device power-on debug off, to see if flashtool can recognize it, and how much it can recognize.
Connect to flashtool with device power-on debug on , to see if flashtool can recognize it.
Connect to flashtool with device in fastboot mode, to see if flashtool can recognize it.
Connect to flashtool with device in flashmode, to see if flashtool can recognize it.
Flashtool may fix some driver error. I just succeeded after hours of bungling like that.
Good luck.
orc.x.lei said:
It seems driver problem.
I met the same problem as well as others yesterday, when I unlock, relock, re-unlock, root locked, root unlocked, flash recovery... for some crazy reason.
Try these:
Connect to flashtool (beta2 or beta4) with device power-on debug off, to see if flashtool can recognize it, and how much it can recognize.
Connect to flashtool with device power-on debug on , to see if flashtool can recognize it.
Connect to flashtool with device in fastboot mode, to see if flashtool can recognize it.
Connect to flashtool with device in flashmode, to see if flashtool can recognize it.
Flashtool may fix some driver error. I just succeeded after hours of bungling like that.
Good luck.
Click to expand...
Click to collapse
Thank you i got it by turning of debugging mode, strange it worked but cheers
I have this problem as well, tried doing above things, uninstalling drivers, reinstalling - help appreciated.
and Phone is working normal but after 5 second reboot and FC 's
Plz Help
same issue...
Has anyone found a sure fix for the issue presented by the original post? I am having this issue and I have tried different drivers, ftf's, computers, adb/fastboot/versions and flashtool versions. I have unlocked and relocked. Is rooting status "unknown" normal after bootloader unlock? -Z Ultra 6833 EU
Still no solution?
With my C6603 it does not allow to write boot aswell. Any final solutions?
edit: solution found: bootloader was not unlocked
Error flashing kernel
I use an xperia M..
I was trying to install custom rom in it.. and every time i try to flash a kernel using any flashtool, it says FAILED (remote: Command not allowed)
what should i do?? please, someone help me..
aravindjr said:
I use an xperia M..
I was trying to install custom rom in it.. and every time i try to flash a kernel using any flashtool, it says FAILED (remote: Command not allowed)
what should i do?? please, someone help me..
Click to expand...
Click to collapse
This is the wrong forum to ask this. This is the Xperia Z section.
Despite that, you need to unlock your bootloader to flash kernels via fastboot.
Sent from my C6603 using Tapatalk
After months using stock everything I decided to flash CM11 yesterday, I'm doing exactly same step as I was doing when on 4.1/4.2 but it seems like it doesn't works, I'm not even sure that my BL is unlocked despite success message, when trying to reboot after unlock BL I had a bootloop and when trying to recover with Sony's Flashtool it says 'device not unlocked'. So I repaired with PCC and restarted from scratch but same results today.
I'm totally lost as like I said I was doing exactly same thing on the same PC.
Edit : Now my XZ doesn't even start! I have the red led blinking while connected with usb, power+ Vol+ doesn't do anything, no vibrations at all!
I was on latest sony official ROM
Edit2 : Tryied again to recover with Sony's Flashtool but it says "Mobile Locked" that's crazy!
aravindjr said:
I use an xperia M..
I was trying to install custom rom in it.. and every time i try to flash a kernel using any flashtool, it says FAILED (remote: Command not allowed)
what should i do?? please, someone help me..
Click to expand...
Click to collapse
Check PM
Relax!
4.3 introduced a new security feature. Look up "unlock bootloader 4.3 xperia z" for help :good:
babylonbwoy said:
After months using stock everything I decided to flash CM11 yesterday, I'm doing exactly same step as I was doing when on 4.1/4.2 but it seems like it doesn't works, I'm not even sure that my BL is unlocked despite success message, when trying to reboot after unlock BL I had a bootloop and when trying to recover with Sony's Flashtool it says 'device not unlocked'. So I repaired with PCC and restarted from scratch but same results today.
I'm totally lost as like I said I was doing exactly same thing on the same PC.
Edit : Now my XZ doesn't even start! I have the red led blinking while connected with usb, power+ Vol+ doesn't do anything, no vibrations at all!
I was on latest sony official ROM
Edit2 : Tryied again to recover with Sony's Flashtool but it says "Mobile Locked" that's crazy!
Click to expand...
Click to collapse
BatteryAidFree said:
4.3 introduced a new security feature. Look up "unlock bootloader 4.3 xperia z" for help :good:
Click to expand...
Click to collapse
I know I'm late but thanks anyway, just updated to 4.4.4 today, I'll look to your advice, thanks for replying, you're the only one that took time to write few words to help.
Hope it goes well!
babylonbwoy said:
I know I'm late but thanks anyway, just updated to 4.4.4 today, I'll look to your advice, thanks for replying, you're the only one that took time to write few words to help.
Click to expand...
Click to collapse
You're welcome! The only thing I can think is if you want to install/rate 5 stars my app, would be greatly appreciated! ("Battery Aid" - I can't post the link apparently, "To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!")
use flashtool to writ kernel
fastboot remote command not allowed Xperia Z3
I unlocked my boatloader, but have no way to confirm that it is still unlocked. I'm running Windows 7. Fastboot used to work just fine before I unlocked my bootloader. FLASHTOOL works fine. But if I try to flash anything with fastboot I get the remote command error. Can't flash recovery. Can't flash boot image.
stevenmanzano said:
I unlocked my boatloader, but have no way to confirm that it is still unlocked. I'm running Windows 7. Fastboot used to work just fine before I unlocked my bootloader. FLASHTOOL works fine. But if I try to flash anything with fastboot I get the remote command error. Can't flash recovery. Can't flash boot image.
Click to expand...
Click to collapse
Look in the service menu to confirm if your bootloader is unlocked.
Enter *#*#7378423#*#* in the dialler, then look in Service info -> Configuration. It will say "Bootloader unlocked: Yes" if it's unlocked.
Sent from my C6603
solved remote command not allowed
stevenmanzano said:
I unlocked my boatloader, but have no way to confirm that it is still unlocked. I'm running Windows 7. Fastboot used to work just fine before I unlocked my bootloader. FLASHTOOL works fine. But if I try to flash anything with fastboot I get the remote command error. Can't flash recovery. Can't flash boot image.
Click to expand...
Click to collapse
By installing FLASHTOOL by Sony I was instantly notified that my bootloader was not unlocked, even though I had already unlocked it three or four times without any errors. So I unlocked it again. Then fastboot flashed my images just fine.
Hello,
ok so the problem is I tired to update to Jelly beam, i read about it here and i follow the steps. I make it to recovery and when i wanted to install files from zip it gave me error - Installation Aborted. I read somewhere that i have to update my Clockwork recovery so i tried and since then i can't do anything. When i press the power button i go to bootloader, from there if i chose Recovery the phone reboots and stucks on the colored X. When i type "adb devices" in cmd so i can try to apply some method list of devices is empty. I think it can be fixed if i make it to recovery but i can't. I looked a lot and maybe its because im mad or something but i can't find a solution, so if anyone can help me i will be very happy. I don't bother if im back to stock.
Use fastboot in bootloader, adb is only available in os and recovery
fastboot flash recovery recovery.img
Sent from my Nexus One using xda app-developers app
demkantor said:
Use fastboot in bootloader, adb is only available in os and recovery
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Tried that, stuck on : <waiting for device>
EDIT: I tried on my brother laptop and it worked but when i exucute the command, it says FAILED(remote: image update error)
EDIT2: Thanks i fixed it its working now. WOOHO!
when in bootloader have phone in fastboot mode, connect to pc via usb, make sure you have the proper drivers
HERE, THIS SHOULD HELP this is for a different phone so dont use the files but the concept is the same
Now, I know this tutorial exists all over the place, like one-click and UnjustifiedDev tutorial but none seemed to work. I am sharing the steps and method I used IN-DEPTH command for command on how to unlock, flash, and root the LG G4 from Tmobile.
NOTE THIS WILL FACTORY RESET YOUR DEVICE SO BACKUP ALL YOUR DATA
1. Activate developer settings by entering the about section and tapping build number 7 times.
2. Enter your developer settings and MAKE sure you have 'Allow OEM unlock' and 'USB Debugging' enabled.
3. Download the latest SuperSU zip and move it onto your SD card.
4. Using the android issue SDK. Open a command window and link it to your SDK folder where ADB is located (typically Platform-Tools)
5. Once the Command window is linked to the folder, connect your device via USB and allow the connection.
6. On the command window type 'adb reboot bootloader' and the device should reboot with the fastboot options on the upper left of the phone screen
7. Once again on the command window type 'fastboot oem unlock' and the command window should say OKAY and complete the action.
8. To Confirm that the device is unlocked type 'fastboot getvar unlock' and the window should respond with 'Unlock: YES'
9. Now download the latest available TWRP and drop it into the platform-tools folder where your ADB.exe is located.
10. On your Command Window type 'fastboot flash recovery "NAME OF TWRP FILE" if you get the error ' cannot load 'twrp-X.X.X.X-h811' you need to add .img to the end of the filename
11. Once the process completes you will see 'target reported max download size of 536870912 bytes
sending 'recovery' (32968 KB)...
OKAY [ 1.088s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time:'
THE FAILED UNKNOWN COMMAND NOTICE CAN BE IGNORED
12. Once the process completes the device may not let you enter recovery from the traditional method using the buttons on the back of the phone so the easiest method is to, on your command window, type
'fastboot boot twrp-2.8.7.0-h811.img' and the device should respond within just a few seconds and reboot into TWRP.
13. Once the device reboots, enter twrp and tap on install and locate the SuperSU.zip and allow it to install.
14. Once the process completes successfully, wipe cache to be safe and reboot your device.
15. Resetup your device and restore your data if necessary and install a root checker from Google Play to confirm root!
THATS IT GUYS! This took me a long time to figure this out and it's a combination of different methods to get it to work!
All credit goes to the Devs of TWRP and SuperSU!
I posted in General because I'm a new user so please move to appropriate forums! thanks!
This thread should be closed as theres already a proper one on here..http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Its more of people really dont like to search and read things
Please refer to the first line of my post. I understand that there are a large series of posts about how to do this but this is the only one that works for me even with me running android M.
Shows how to install TWRP for devices on 6.0
marcviado said:
This thread should be closed as theres already a proper one on here..http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Its more of people really dont like to search and read things
Click to expand...
Click to collapse
The guide you linked does not show how to unlock the bootloader or install TWRP to allow the install of SU for users that are already on Marshmallow. The other guide would have been perfect if I already had bootloader unlocked and SU installed.
joeyicecream said:
The guide you linked does not show how to unlock the bootloader or install TWRP to allow the install of SU for users that are already on Marshmallow. The other guide would have been perfect if I already had bootloader unlocked and SU installed.
Click to expand...
Click to collapse
Uhm..like i said nobody likes to read now a days lol. If you look closely the guide i linked shows you how to unlock bootloader,flash twrp,root,downgrade,and have all the files you need.
marcviado said:
Uhm..like i said nobody likes to read now a days lol. If you look closely the guide i linked shows you how to unlock bootloader,flash twrp,root,downgrade,and have all the files you need.
Click to expand...
Click to collapse
It is totally there... I looked at that guide for a really long time too. I concede.
joeyicecream said:
The guide you linked does not show how to unlock the bootloader or install TWRP to allow the install of SU for users that are already on Marshmallow. The other guide would have been perfect if I already had bootloader unlocked and SU installed.
Click to expand...
Click to collapse
Yes it does. You do not need to use any codes, just enable oem unlocking in dev settings and type fastboot oem unlock and it will be unlocked.
Can't get twrp installed
Thanks for the step by step directions. I'm having trouble restarting my H811 after I've flashed TWRP. My device doesn't respond to the button method of entering recovery and 'fastboot boot twrp-2.8.7.0-h811.img' command doesn't do anything. My device is 20i and I've unlocked the bootloader. Any ideas? Seems like I've tried everything and can't get TWRP to install. Any help would be great...thanks
I have the G4 LGUS991 gotta can I tell if it's h811?
4. Using the android issue SDK. Open a command window and link it to your SDK folder where ADB is located (typically Platform-Tools)
Click to expand...
Click to collapse
What if your device could not be found despite having the latest LG drivers?
mr_blonde55 said:
Thanks for the step by step directions. I'm having trouble restarting my H811 after I've flashed TWRP. My device doesn't respond to the button method of entering recovery and 'fastboot boot twrp-2.8.7.0-h811.img' command doesn't do anything. My device is 20i and I've unlocked the bootloader. Any ideas? Seems like I've tried everything and can't get TWRP to install. Any help would be great...thanks
Click to expand...
Click to collapse
Can't remember which thread, but I ran into the same problem you have and solved it by using an additional command like fastboot erase userdata. If you google it, you'll see the commands I mean. Basically, I had to factory reset the device through fastboot first (it sits there for several minutes to do this) before installing/booting twrp. And yes, the log will show that the process was successful, not a failure as mentioned by OP. Once I did that, I booted in twrp and flashed the rom zip without any trouble.
So, you guys mean we have Marshmallow on T mobile G4, I didn't get it yet.
Please somebody give me a link to the OTA or update.zip for MM of LG G4
This one worked for me!
This is the only guide that worked for me.
I unlocked bootloader using adb, no problems...
I tried to flash TWPR with fastboot but kept getting errors. Booting into recovery got a dead android minion and red triangle with ! I ran this stupid recovery a dozen times and read a dozen threads with no obvious answers.
This guide says "ignore the error" and run fastboot boot twrp-2.8.7.1-h811.img which immediately opened TWRP and allowed SuperSU-2.71.zip to be flashed.
The part most guides are missing is the fastboot boot twrp-2.8.7.1-h811.img, so my thanks go here. Some other guides are so difficult to read and follow.
Thanks OP !
Yes, MM Android 6.0 went OTA for T-Mobile a month or so ago...
If you are already on Marshmallow, can't you do the 'fastboot oem unluck' with ADB and install SuperSU through the play store to get root? The part for TWRP would only give you the ablity to flash other roms.
Edit: Nevemind I'm wrong. You need TWRP to install SuperSU which roots the phone. SuperSU in the Play Store will only grant root acess to your apps.
Sent from my LG-H811 using XDA-Developers mobile app
NardVa said:
If you are already on Marshmallow, can't you do the 'fastboot oem unluck' with ADB and install SuperSU through the play store to get root? The part for TWRP would only give you the ablity to flash other roms.
Edit: Nevemind I'm wrong. You need TWRP to install SuperSU which roots the phone. SuperSU in the Play Store will only grant root acess to your apps.
Click to expand...
Click to collapse
Could you help me with is or point me in the right direction ? Please & thanks
Sent from my LG-H811 using XDA Labs
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
Majestyk007 said:
This is the only guide that worked for me.
I unlocked bootloader using adb, no problems...
I tried to flash TWPR with fastboot but kept getting errors. Booting into recovery got a dead android minion and red triangle with ! I ran this stupid recovery a dozen times and read a dozen threads with no obvious answers.
This guide says "ignore the error" and run fastboot boot twrp-2.8.7.1-h811.img which immediately opened TWRP and allowed SuperSU-2.71.zip to be flashed.
The part most guides are missing is the fastboot boot twrp-2.8.7.1-h811.img, so my thanks go here. Some other guides are so difficult to read and follow.
Thanks OP !
Yes, MM Android 6.0 went OTA for T-Mobile a month or so ago...
Click to expand...
Click to collapse
I keep getting this problem.
Sent from my LG-H811 using XDA Labs
I've just got a H811 and it automatically updated to Android 6 when I loaded it up. I will be giving this guide a go this evening. Many of the other links on the web are for lollipop and were released when the phone came out, so I'm thankful that this seems straight forward. http://uslugi.nie-spamuj.eu/rtv,1,0.html Hoping that it goes that way.
How to lock bootloader or hide status: bootloader state: unlocked?
Sr for my English!
So I followed this guide and I appear to be soft bricked at best and hard bricked at worst. I did read the other guide linked in the second response and I found a major difference that might be my problem. So in the guide linked in the second response it doesn't say to even try flashing TWRP from fastboot. It says to just boot from it then install it from within TWRP. I followed the steps verbatim and my phone is currently stuck at the T-Mobile splash screen. Any suggestions? I have tried to boot into recovery by holding down and the power and releasing the power for a second when the logo comes up. I get into the Factory data reset screen and select Yes twice then the green guy shows up and the phone resets but stays at the T-Mobile splash screen. I don't have ADB or fastboot with the phone in this state.
hi Guys,
So i just wanted to make sure and present my ask -
So, currently twrp flashing and obtaining root is still buggy for those who have android 6.0 preinstalled? Is this a correct assumption?
Also, my ask - I dont want root but i would like a custom recovery so that I may flash custom fonts. My work email (Good for Enterprise) is very much needed (although i hate it to the core).
Can someone please answer me / correct if I mentioned something wrong?
Thanks
rmdeathwish said:
hi Guys,
So i just wanted to make sure and present my ask -
So, currently twrp flashing and obtaining root is still buggy for those who have android 6.0 preinstalled? Is this a correct assumption?
Also, my ask - I dont want root but i would like a custom recovery so that I may flash custom fonts. My work email (Good for Enterprise) is very much needed (although i hate it to the core).
Can someone please answer me / correct if I mentioned something wrong?
Thanks
Click to expand...
Click to collapse
It's not buggy at all. All the tedium has already been bypassed if you already have Marshmallow installed.
Follow autoprime's original guide, steps 2, 4, 5, 6, and 8 under the Bootloader OEM Unlock + Root section. I would recommend a more up-to-date version of TWRP than 2.8.7.1 though. Go to TWRP's download site for the latest version.
Hi guys,
I am having a lot of difficulties flashing the OS I have. I have an old ZUI 1.9 and after a few years I just started getting fullscreen ads when launching aps like netflix.
My bootloader is locked, I was able to get the unlock file from the chinese lenovo website, but now the issue I have is that all the commands I try are wrong.
I am using SDK platform tools, I have adb setup installed and got the driver for my device. When I go into fastboot the computer doesn't recognise Zuk Z2 anymore.
What I did was set the driver manually to ADB bootloader in device manager. This prevents the command from returning "waiting for any device".
I have tried many commands but all the ones that have fasboot -i doesn't work.
IE: fastboot -i 0x2b4c flash unlock unlock_bootloader.img will return :"fastbook: unknown option --i"
If I can't get the bootloader to be unlocked commands like: "fastboot flash recovery twrp.img" will return :"fasboot: error: command failed". Sending goes OKAY, writing goes FAILED (remote: 'Partition flashing is not allowed').
In a last attempt to get this fix before I lose my calm I decided to register an account on the zukfans forums to ask for help. Once you register your account gets banned for spamlike behavior.
I found through an old post here that you can contact them through facebook to get that fixed, but now their pages have been deleted, and I have spent way too much time trying to flash this stupid device.
Any help is appreciated, if you need any more information don't hesitate to ask, I'll do my best to answer as this is the first time I try to flash a phone and none of the guides could help this far.
Thanks
Hi,
so I got myself a Z3 compact this week to play around a bit and see If I can get LineageOS or CarbonOS working with Magisk.
I came upon a nice site here (german): https://arnowelzel.de/carbonrom-auf-dem-sony-xperia-z3-compact
He bought a new device and the way I understood him he won't be updating any Sony sites.
I was trying to flash TWRP using simple ADB commands - but the devices does not react.
Funny though, Flashtool works just fine and seems to be able to communicate with the device just fine.
So I search around a bit and all I found was stuff like "don't use Flashtool to flash TWRP" or "simply use ADB commands to flash TWRP" and so on.
Now I got the following questions:
* Are there reasons that discourage oneself from doing just that (meaning flashing TWRP using Flashtool?)
* Arno flashed his TWRP to the FOTA partition instead of to the recovery partition. Any reason why?
Unrelated:
* Device keeps asking me for authorization, although I tap "Always allow from this computer". Any clues why that is?
Thanks for input!
Cheers
- A
Okay, so the way I understand it is that with Flashtool one mostly flashes Kernels ?
Did not yet figure out why "Install Recovery" is greyed out....
adb reboot bootloader did the trick and it was recognized now when using "fastboot devices"
So, all good now regarding this thread
Andro1dism said:
adb reboot bootloader did the trick and it was recognized now when using "fastboot devices"
So, all good now regarding this thread
Click to expand...
Click to collapse
Hi!!!
I have the same problem, how do you resolve specifically ?
Please give me a tip how to proceed.....thank you!!!!
I'm stucked here