Is booting a custom recovery with fastboot still possible? - Fire Q&A, Help & Troubleshooting

I've had a KFFOWI since Christmas but have been too busy to do anything with it. Unforutnately, this means that it has been updated to 5.1.4. Now I want to see what I can do with it.
I've read many posts on this excellent forum over the past few days about this device. I thought I'd start by trying to load the custom recoveries CM and TWRP.
I have ADB and Fastboot on a Linux box (I don't use Windows at all). I Can put the device into Fastboot mode; the way I do this is to boot to stock recovery and then choose "reboot to bootloader". I verify Fastboot from my Linux prompt like this:
Code:
$ sudo fastboot -i 0x1949 getvar product
product: FORD
finished. total time: 0.002s
I have downloaded the recoveries and try to boot them like this:
Code:
$ sudo fastboot -i 0x1949 boot TWRP_Fire_2.8.7.0_adb.img
downloading 'boot.img'...
OKAY [ 0.256s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.258s
However, as you can see, it does not work. I guess that the bootloader has been updated with one that does not have the boot command.
I also found this thread which would appear to confirm my suspicions but I can't find any more recent information about this.
So is this correct, that it's no longer possible to run a custom recovery like this? Or am I doing something wrong ?
I doubt it, but will downgrading to 5.1.2 fix this?
(I also read the KFFB thread and also this one thread about fastboot, but perhaps it is out of date with respect to this?).

ogpog said:
...So is this correct, that it's no longer possible to run a custom recovery like this? Or am I doing something wrong ?
I doubt it, but will downgrading to 5.1.2 fix this?
Click to expand...
Click to collapse
For the reasons stated in your full post custom recoveries can not be used/booted once FireOS has been updated beyond 5.0.1 via normal OTA (ie: no steps taken to protect bootloader).
As you probably know FlashFire can be used to install custom ROMs and take other actions normally performed in a custom recovery like twrp. However, stock recovery is still the only way to recover the device if the installed rom won't boot or unstable.

I see, so the ability to boot a recovery was lost after 5.0.1. I didn't catch that from my reading. I am working on getting FlashFire up and running but I need to get root first. I won't pollute this thread with my efforts in that regard.

Related

[Q] Can't boot into recovery HTC one

Hi -
Thanks for any help in advance. I'm a bit of a rookie round here, I've rooted and flashed my past 3 HTC phones but taken the easy route every time.
But today, I've used ADB commands to flash the revone binary and unlock and get s-off on my HTC one m7. It took me several tries, but it eventually worked (or at least said successful). So my HBOOT 1.44 says UNLOCKED & S-OFF.
So onto the next step. fastboot flash recovery recoverytwrp.img
...
Another success!
So, I reboot into bootloader and prompt recovery boot like I'm about to get HAM on twrp and flash some superuser files. It shows me a developer screen full of red print saying that it's booting into recovery, and then after a while, it just rebooted back into system.
It does this every time. I reflashed the image, I flashed the stock image, I tried the hansoon tool. each time I can't actually get into the recovery.
So this is where I'm stuck. Why can't I get anywhere with this?
EDIT & ANSWER;
Sprint phone needed Sprint TWRP image
Have you tried
fastboot erase cache
BenPope said:
Have you tried
fastboot erase cache
Click to expand...
Click to collapse
This.
Just do evrything again until you finish installing custom recoveries. Before rebooting, erase the cache with "fastboot erase cache"
ryryzz said:
This.
Just do evrything again until you finish installing custom recoveries. Before rebooting, erase the cache with "fastboot erase cache"
Click to expand...
Click to collapse
Gave that all a shot all over again. Still can't boot into recovery
Is fast boot off?
Use the original cable your One came with, go into bootloader power/vol - then open a cmd window
Now connect the One with your computer, don't use a USB 3.0 connection, and a different one then before.
In bootloader choose fastboot, that should change to fastboot USB
In cmd window point to your fastboot directory where you also copied the recovery to, I would try CWM touch for now.
Type cd c:\fastboot (or what your toolfolder is called)
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
That installs the recovery, you can select it in bootloader abd boot into it.
Sent from my HTC One using xda premium
---------- Post added at 06:28 PM ---------- Previous post was at 06:23 PM ----------
BenPope said:
Is fast boot off?
Click to expand...
Click to collapse
You mean the fastboot option under Power Settings is unticked when booted up normally?
Sent from my HTC One using xda premium
hardstuffmuc said:
Use the original cable your One came with, go into bootloader power/vol - then open a cmd window
Now connect the One with your computer, don't use a USB 3.0 connection, and a different one then before.
In bootloader choose fastboot, that should change to fastboot USB
In cmd window point to your fastboot directory where you also copied the recovery to, I would try CWM touch for now.
Type cd c:\fastboot (or what your toolfolder is called)
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
That installs the recovery, you can select it in bootloader abd boot into it.
Sent from my HTC One using xda premium
---------- Post added at 06:28 PM ---------- Previous post was at 06:23 PM ----------
You mean the fastboot option under Power Settings is unticked when booted up normally?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Same deal. On it's way to booting into recovery it goes blank, resets and reboots into system
C:\adt\sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.078s]
finished. total time: 0.078s
C:\adt\sdk\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (7422 KB)...
OKAY [ 1.139s]
writing 'recovery'...
OKAY [ 0.640s]
finished. total time: 1.778s
C:\adt\sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.062s]
finished. total time: 0.062s
C:\adt\sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
There's the last log - and then on it's way to recovery there's a red disclaimer and a pink text saying "Entering Recovery"...then after 20 seconds it resets
Did you try various recovery (versions) ? May be , you just have corrupted recovery image.
tash2013 said:
Did you try various recovery (versions) ? May be , you just have corrupted recovery image.
Click to expand...
Click to collapse
at this point I've tried stock, twrp and cwm. All with the same results
Jman12000 said:
at this point I've tried stock, twrp and cwm. All with the same results
Click to expand...
Click to collapse
Ok , I see mysterious problem ))
Try, remaining unlocked, go back to s-on (you can always take s-off again) and check your recovery (enter and flashing) under s-on.
tash2013 said:
Ok , I see mysterious problem ))
Try, remaining unlocked, go back to s-on (you can always take s-off again) and check your recovery (enter and flashing) under s-on.
Click to expand...
Click to collapse
Is that something I can do with the revone binary? To be honest, I have no idea how to turn security back on. I can relock it and that may be about it.
I stumbled upon another thread, shares a common theme as my issue, but with a different twist. Using a superboot.img as a rooting method instead of flashing it via recovery. It somewhere says that the boot.img needs to be flashed as well, however I can't find a decent boot.img to flash. The superboot tool seems like unproven territory right now.
Here's the other thread, I've leafed through it and found no determinable answer for my particular issue.
http://forum.xda-developers.com/showthread.php?p=39852757#post39852757
Do not apply revone to return s-on!
Use fastboot by "fastboot oem writesecureflag 3".
Be convinced that bootloader is unlocked before return to s-on.
Regarding your issue: I suspect that a certain code in HBOOT tries to install TAMPERED flag when sees custom recovery, but isn't able to do it correctly because s-off (bypassing security) and a certain mistake or exception conducts to reset phone.
Jman12000 said:
Hi -
Thanks for any help in advance. I'm a bit of a rookie round here, I've rooted and flashed my past 3 HTC phones but taken the easy route every time.
But today, I've used ADB commands to flash the revone binary and unlock and get s-off on my HTC one m7. It took me several tries, but it eventually worked (or at least said successful). So my HBOOT 1.44 says UNLOCKED & S-OFF.
So onto the next step. fastboot flash recovery recoverytwrp.img
...
Another success!
So, I reboot into bootloader and prompt recovery boot like I'm about to get HAM on twrp and flash some superuser files. It shows me a developer screen full of red print saying that it's booting into recovery, and then after a while, it just rebooted back into system.
It does this every time. I reflashed the image, I flashed the stock image, I tried the hansoon tool. each time I can't actually get into the recovery.
So this is where I'm stuck. Why can't I get anywhere with this?
Click to expand...
Click to collapse
try to install recovery again
you can download recovery from here
http://www.clockworkmod.com/rommanager
tash2013 said:
Do not apply revone to return s-on!
Use fastboot by "fastboot oem writesecureflag 3".
Be convinced that bootloader is unlocked before return to s-on.
Regarding your issue: I suspect that a certain code in HBOOT tries to install TAMPERED flag when sees custom recovery, but isn't able to do it correctly because s-off (bypassing security) and a certain mistake or exception conducts to reset phone.
Click to expand...
Click to collapse
Code:
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>ad
b reboot bootloader
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>fa
stboot oem writesecureflag 3
...
(bootloader) writesecureflag: partitions siganture pass
OKAY [ 1.665s]
finished. total time: 1.666s
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>fa
stboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.045s]
finished. total time: 0.046s
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>ad
b reboot bootloader
error: device not found
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>ad
b reboot bootloader
So here's where I'm at
Right now I've done all the above, I've got a *** TAMPERED *** and ***UNLOCKED*** and S-ON
I've been through 4 boots, 2 of them attempts to get to recovery. Now instead of recovery rebooting into system, it just shuts off now.
Where do you think I go from here?
I've just skimmed through the posts and didn't see this mentioned
If you are still able to boot into the system, download either GooManager (for TWRP) or RomManager (for CWM) and use either of those apps to install recovery. Once done, you can use the app to boot into recovery instead of the fancy ADB commands or button presses.
Jman12000 said:
So here's where I'm at
Right now I've done all the above, I've got a *** TAMPERED *** and ***UNLOCKED*** and S-ON
I've been through 4 boots, 2 of them attempts to get to recovery. Now instead of recovery rebooting into system, it just shuts off now.
Where do you think I go from here?
Click to expand...
Click to collapse
This topic seems like your problem :
http://forum.xda-developers.com/showthread.php?t=2328983&page=3
The man resolved this by flashing the same recovery many many times.
And more.. Please print here your recovery flashing process
tash2013 said:
This topic seems like your problem :
http://forum.xda-developers.com/showthread.php?t=2328983&page=3
The man resolved this by flashing the same recovery many many times.
And more.. Please print here your recovery flashing process
Click to expand...
Click to collapse
So both that method through ADB shell and GooManager require root. Every rooting method requires recovery, so I don't have perm root yet.
You quoted me, but answered not to me.
Read a post #26 from my link above
Possible Solution
Hello I have the same problem and the solution was:
1. Settings - Energy- Fastboot uncheked
2. Flash Recovery usin one all-in-one-kit
3. Erase Cache 3 times
4. Unplug to PC, and load into system normal
5. Turn off phone - via stock menu NOT FORCE TO OFF pressing the off button
6. Wait 2 minutes, and boot into HBOOT - Power + Volume(-) pressing
7. Choose recovery
Ready.. May these work for you! Let me know

[Q] fastboot boot recovery.img on hboot 1.56

Just got my One back from warranty repair. Looks like they either gave me a new main board or updated my device, I'm on the latest Bell 4.19.666.8 with hboot 1.56.
I figured I would get a full nandroid backup of the phone at stock 4.4.2, but I can't seem to get fastboot boot to work. Don't want to flash the recovery as I want to get a backup of the stock one.
with the phone in FASTBOOT USB, I ran
$ fastboot boot openrecovery-twrp-2.7.0.0-m7.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 1.311s]
booting...
OKAY [ 0.000s]
finished. total time: 1.311s
But the device just sits at the fastboot screen and does nothing. It doesn't even respond to fastboot commands anymore so I have to force power off and reboot.
I saw on the Nexus 4 forum that on that phone you now have to specify a kernel command line with fastboot boot - something like
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
Is this true for the One too? If so, what is the command line? I'm guessing lge.kcal is specific to LG devices.
ergosteur said:
Just got my One back from warranty repair. Looks like they either gave me a new main board or updated my device, I'm on the latest Bell 4.19.666.8 with hboot 1.56.
I figured I would get a full nandroid backup of the phone at stock 4.4.2, but I can't seem to get fastboot boot to work. Don't want to flash the recovery as I want to get a backup of the stock one.
with the phone in FASTBOOT USB, I ran
$ fastboot boot openrecovery-twrp-2.7.0.0-m7.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 1.311s]
booting...
OKAY [ 0.000s]
finished. total time: 1.311s
But the device just sits at the fastboot screen and does nothing. It doesn't even respond to fastboot commands anymore so I have to force power off and reboot.
I saw on the Nexus 4 forum that on that phone you now have to specify a kernel command line with fastboot boot - something like
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
Is this true for the One too? If so, what is the command line? I'm guessing lge.kcal is specific to LG devices.
Click to expand...
Click to collapse
"fastboot boot ..." only worked on hboot 1.44.
and I can't answer about the N4 method if that would work or not; but I kinda doubt it.
nkk71 said:
"fastboot boot ..." only worked on hboot 1.44.
and I can't answer about the N4 method if that would work or not; but I kinda doubt it.
Click to expand...
Click to collapse
OK, thanks. Should I even bother trying to back up the stock recovery or just go ahead and flash a custom one? Would there be any way to do it without hboot 1.44? I see that temproot doesn't work on stock 4.4.2.
ergosteur said:
OK, thanks. Should I even bother trying to back up the stock recovery or just go ahead and flash a custom one? Would there be any way to do it without hboot 1.44? I see that temproot doesn't work on stock 4.4.2.
Click to expand...
Click to collapse
Couldn't find stock recovery 4.19.666.8, but if it's for future OTAs then any stock recovery 4.19.xxx.x should work (maybe even 3.xx.666.x)
This is a good source for stock recoveries [Recovery]Collection of Stock Recovery
If you're using a stock recovery that is not a 100% match, then the OTA would just hang, and you have to manually reboot for it to continue.... you can check my guide under CWM method about info on that.
There's also @SaHiLzZ guide for Canadian users: http://forum.xda-developers.com/showthread.php?t=2529225
Or do you need it for some other reason?
nkk71 said:
Couldn't find stock recovery 4.19.666.8, but if it's for future OTAs then any stock recovery 4.19.xxx.x should work (maybe even 3.xx.666.x)
This is a good source for stock recoveries [Recovery]Collection of Stock Recovery
If you're using a stock recovery that is not a 100% match, then the OTA would just hang, and you have to manually reboot for it to continue.... you can check my guide under CWM method about info on that.
There's also @SaHiLzZ guide for Canadian users: http://forum.xda-developers.com/showthread.php?t=2529225
Or do you need it for some other reason?
Click to expand...
Click to collapse
I was thinking more for archival purposes- Just in case. I restored my phone back to stock twice for warranty, your guide was very helpful.
I think I'll just go ahead and flash CWM/TWRP, my warranty is done anyway.
ergosteur said:
I was thinking more for archival purposes- Just in case. I restored my phone back to stock twice for warranty, your guide was very helpful.
I think I'll just go ahead and flash CWM/TWRP, my warranty is done anyway.
Click to expand...
Click to collapse
do go back to warranty you need to set phone to LOCKED, which is only possible with S-Off.
the fastboot oem lock command will set your bootloader to RELOCKED, so they would know you've unlocked it.... so stock recovery is the least of your worries if you want to ever go 100% back to stock.
stick with TWRP 2.6.3.3 or higher, but not 2.7.0.0 which seems to have problems with adb (and if i remember correctly charging when phone is off... though it could be a different one)
get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
or 2.7.0.4b: http://forum.xda-developers.com/showthread.php?t=2708134
EDIT: forgot to tell you why TWRP: it's compatible with 4.4 ROMs, CWM doesn't seem fully updated yet
Happy flashing :laugh:

Can't Flash N6

Long story short, woke up with my N6 stuck at the bootloader screen and cannot do anything at it. I can only see my serial number and if I try anything else, it reloads bootloader. I am trying to flash back to a stock 6.0.1 image, however I keep getting this error while trying to do so.
C:\Program Files (x86)\Android\android-sdk\platform-tools> fastboot flash bootloader bootloader-shamu-moto-apq8084-71.15.img
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (10387 KB)...
OKAY [ 0.332s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to flash partition
FAILED (remote failure)
finished. total time: 11.542s
I have tried Nexus Root Toolkit, tried flashing all and tried flashing each image one by one but I still get this "(bootloader) Failed to flash partition FAILED (remote failure)" on all attempts. Phone does show up if I try fastboot devices, and I have tried this on two different computers. Device is also unlocked as well, and I even tried flashing older versions of Lolipop but they all give me the same error. Drivers work fine, and I have everything up to date in terms of bootloader and Andriod SDK. I am starting to think that there is physical damage inside the phone, however I do not know how or why this occurred randomly. Any help would be awesome, as I am very new to flashing images onto my phone and frankly I am 99% sure that my warranty is out, and I really don't want to pay $175 cost .
You can try to use minimal adb and fastboot drivers, unpack for example latest npreview 5 factory Image into same folder and flash each .IMG step by step with cmd window, i always flash this way, if everything else fails.
http://forum.xda-developers.com/showthread.php?t=2317790
And here method 2:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
May this helps you
coremania said:
You can try to use minimal adb and fastboot drivers, unpack for example latest npreview 5 factory Image into same folder and flash each .IMG step by step with cmd window, i always flash this way, if everything else fails.
http://forum.xda-developers.com/showthread.php?t=2317790
And here method 2:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
May this helps you
Click to expand...
Click to collapse
I've already tried method 2 before so I tried method 1 with the program, and it gives me the same exact error as before. Thanks for the help though, it was worth a shot!
Are you able to enter twrp ? Try to reflash Bootloader through twrp
coremania said:
Are you able to enter twrp ? Try to reflash Bootloader through twrp
Click to expand...
Click to collapse
I did not have TWRP installed on my phone since I had it completely stock and unrooted, so I tried installing it in the hopes of that some chance it would work and I could access it. Still getting the same error as before (grumble grumble). It is starting to look like more of a physical problem to me, but thanks for the advice. Here is what I got...
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (11585 KB)...
OKAY [ 0.468s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 6.380s
Bootloader is unlocked i guess, may your Bootloader is messed up, did you try to flash only one Factory Image ? Corrupt Download possible ?
What happens if you try unlock command
Try to flash the latest full ota with these steps.
https://developers.google.com/android/nexus/ota
Since you already in the bootloader, select recovery and fpllow the steps from there.
blanco2701 said:
Try to flash the latest full ota with these steps.
https://developers.google.com/android/nexus/ota
Since you already in the bootloader, select recovery and fpllow the steps from there.
Click to expand...
Click to collapse
This was going to be my suggestion!!
Sent from my Nexus 6 using XDA-Developers mobile app
coremania said:
Bootloader is unlocked i guess, may your Bootloader is messed up, did you try to flash only one Factory Image ? Corrupt Download possible ?
What happens if you try unlock command
Click to expand...
Click to collapse
Any image I even try to flash I get the error with, no matter what order or which one I pick. I redownloaded the image again and still nothing, so I don't think it's a corrupt download. What is the unlock command? Sorry for being a noob, never heard of it since all my knowledge is from reading tons of flashing guides on the internet lol.
blanco2701 said:
Try to flash the latest full ota with these steps.
https://developers.google.com/android/nexus/ota
Since you already in the bootloader, select recovery and fpllow the steps from there.
Click to expand...
Click to collapse
Alright, I downloaded the OTA file and got the process to about 47% when suddenly I keep running into the error of "E:Can't open /cache/recovery/log" then followed by more things it can't open. I tried the OTA twice and it gets stuck on that same exact spot. I tried the wipe data/factory reset option from the recovery mode and I get a similar error of "Can't mount", "Can't open", "failed to mount" the recovery log. It seems like there is a problem with the recovery log files (or the folder) on my phone, but I have no idea what that means. I will mess around with some more and try Googling the source of error, but thank you for the help.
fastboot oem unlock
With this command you can unlock your Bootloader, better read here
first http://forum.xda-developers.com/showpost.php?p=56938530&postcount=1 , if have 47% done, may you can use twrp now. Good luck
Did you try the erase function from bootloader that may or may not help??
Sent from my Nexus 6 using XDA-Developers mobile app
coremania said:
fastboot oem unlock
With this command you can unlock your Bootloader, better read here
first http://forum.xda-developers.com/showpost.php?p=56938530&postcount=1 , if have 47% done, may you can use twrp now. Good luck
Click to expand...
Click to collapse
Oh yes, my device has already been unlocked from the start so that wasn't a problem. I still get the same error when I try to flash anything, including TWRP which means I have to install the OTA. The problem is a get a separate error when I try to install the OTA, which the only solution being to flash my device (or at least that is what most people have been saying when I googled the can't open cache recovery error) so this is a giant goose chase which leads me back to the start :/. I will keep trying however, I refuse to give up after going this far!
holeindalip said:
Did you try the erase function from bootloader that may or may not help??
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Should I try fastboot erase cache and then fastboot format cache? Would refresh the cache on there? I only just learned the erase command so I am not exactly sure what I should try.
Should be able to erase any partition if your unlocked
http://androidforums.com/threads/list-of-fastboot-command.714676/
Sent from my Nexus 6 using XDA-Developers mobile app
I don't know the commands to erase everything from the bootloader but I would try this:
Flash latest twrp and boot into recovery.
Assuming you don't care about anything that's on the phone, go to advance wipe and wipe EVERYTHING lol... reboot into bootloader and try to flash everything from scratch. If this doesn't work, I'll guess your phone have problems.
holeindalip said:
Should be able to erase any partition if your unlocked
http://androidforums.com/threads/list-of-fastboot-command.714676/
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I get the same failure error while trying to format and erase, so I am guessing something is really wrong with my phone or the bootloader is messed up beyond repair. I guess it could be the cable I am using as well, that is one thing I did not take into factor so I will try with another cable if I find a spare. Flashing might be beyond my solution at this rate though... Thanks anyways for the help.
blanco2701 said:
I don't know the commands to erase everything from the bootloader but I would try this:
Flash latest twrp and boot into recovery.
Assuming you don't care about anything that's on the phone, go to advance wipe and wipe EVERYTHING lol... reboot into bootloader and try to flash everything from scratch. If this doesn't work, I'll guess your phone have problems.
Click to expand...
Click to collapse
I really should have had TWRP installed before I guess lol, but I still get the same failure error. My phone has more problems than a teenager going through puberty I swear, thanks for the help though.
Yes try another cable, if it stops at 47%, the Bootloader should be replaced. May try everything without simcard, don't ask me why, i read something similiar in a Moto forum
fastboot erase recovery doesn't help ?
---------- Post added at 19:58 ---------- Previous post was at 19:34 ----------
http://forum.xda-developers.com/nexus-6/general/to-save-bricked-nexus-device-t3334660 otherwise try this, but read completely first, adb sideload with a npreview ota rom may help you.
coremania said:
Yes try another cable, if it stops at 47%, the Bootloader should be replaced. May try everything without simcard, don't ask me why, i read something similiar in a Moto forum
fastboot erase recovery doesn't help ?
---------- Post added at 19:58 ---------- Previous post was at 19:34 ----------
http://forum.xda-developers.com/nexus-6/general/to-save-bricked-nexus-device-t3334660 otherwise try this, but read completely first, adb sideload with a npreview ota rom may help you.
Click to expand...
Click to collapse
I tried it with another wire and nothing changed, and then I tried taking out my sim card and trying it.... and it worked! It flashed everything normally and loaded up just fine. I don't know whether I should be furious or happy but thank you and everyone who helped. Who would have known just taking out the sim card could have saved me 2+ days of stressing and trail and error. Once again thanks, you really saved me lol.
You're welcome, nice your phone works again !
Don't forget to activate oem unlock and debugging in the Developer options, and flash twrp, so maybe more save for upcoming problems
skipsoft android toolkit maybe help you in future

Solved with Corrections: Unable to flash TWRP, Failed (Remote: command not allowed)

Hi,
I just purchased a used Xperia Z1 C6903 and I am trying to put the latest Nougat Resurrection Remix on it. I need to get TWRP going first which I got stuck at trying to flash it.
I was able to get the phone downgraded to 14.1.G.1.534 using flash tool (ver 0.9.24.3). I did this following the guide here https://forum.xda-developers.com/showthread.php?t=2439328.
I was able to root it using Kingoroot.
I was able to unlock the bootloader using flashtool. Using *#*#7378423#*#*, the phone now reports Bootloader Unlocked: yes. See attached screenshot.
The part that I got stuck at is trying to flash TWRP in Fastboot. The command lines and error are below. The main error being "FAILED (remote: Command not allowed)"
I don't have an option in developer's options to "Unlock OEM bootloader". I read some other Xperia users being able to fix this problem by checking this.
I am running Windows 8.1. I am relatively sure that my drivers are correct. I had gotten a "drivers too old" error before in Flashtools but I was able to correct it by reinstalling new drivers.
I tried having debugging checked and unchecked before going into Fastboot and made no difference.
Tried both twrp-2.8.7.0-honami and twrp-3.0.2.0-honami with no success. Tried shortening file name to trp.img with no success.
Tried different 2 different adb files around the web with no success.
I read somewhere someone mentioned briefly that TWRP can be flashed using Flashtools. Is that true? I wasn't able to find a full guide for it.
Any help would be appreciated!
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery trp.img
target didn't report max-download-size
sending 'recovery' (13672 KB)...
OKAY [ 0.433s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.439s
Well I was able to get TWRP on there by installing the XY Dual Recovery. The problem with it is that the Resurrection Remix's installation instruction says to use TWRP 3x or higher. TWRP on XY is only at 2.8.7.0. I couldn't find a TWRP 3x flashable zip file for Honami and TWRP wouldn't flash TWRP 3x IMG file I found. Fastboot is still giving me the same Command Not Allowed error.
Any ways, I went ahead and flashed RR with 2.8.7.0. When I tried to flash GAPPs after it says there is insufficient space. I have at least 9GB+ internal storage. So not sure what the deal is there.
I also lost Dual Recovery and root after first RR boot.
Looking into getting re-rooted and reinstalling XY Dual Recovery now.. And then flashing GAPPS after.
Anyone know what the consequences are for installing RR with a lower rev of TWRP?
So the RR Rom does have root but it just doesn't have apps root. Only ADB root. I cant flash the su add on from Lineage's site since I lost recovery. I ended up FTF back to stock and then reflashed everything, the ROM then pico version of GAPPs (pico worked) and then the su addon. The su addon had an error when flashing in TWRP.
Any ways, long story short the whole thing didn't work. Still stuck with RR Without recovery. Su addon didnt work from the flash. And for whatever reason my SIM is not detected and I lost my IMEI in RR. I read that this is a known issue with C6902 but I have the C6903 and I had confirmed this through the service menu before ROM flash. Maybe problems with flashing RR without the latest TWRP.
The Command Not Allowed is still an issue that I dont know how to resolve. So I still can't flash newer version of TWRP.
Any help would be appreciated....
I guess I will try to find a ROM that 's compatible with TWRP 2.8.7.0.
OK! I figured out what the Command Not Allowed problem is!
I've been following the flash guides from a few websites. And they all reference this syntax for flashing TWRP.
Fastboot flash recovery twrp.img.
This syntax didn't work for me. All those websites properly copycat each other.
That syntax is either incorrect or just didnt work for my setup for some reason. I kept searching for ways to flash TWRP and found another website that uses a different syntax. I gave it a go and TWRP flashed right away. This is the syntax that worked for me.
Fastboot flash boot twrp.img
At least that part of the problem is resolved.
Even after flashing RR with TWRP 3.0.20, the SIM/IMEI is still not showing. Recovery is still lost on first boot. Reinstalling TWRP on top of RR causes RR to not boot any more. I will have to look into the RR thread to investigate more.
I will mark this thread as Solved for the Command Not Allowed.
Crossed out everything cause that was not the correct solution. Striked them out to keep them as part of the troubleshooting steps history.
Oops duplicated post.
OK! So it looks like I have to correct myself here on my previous solution.
My solution from earlier for using "Fastboot flash boot twrp.img" is incorrect apparently. Don't use this!
That was the reason why my TWRP was lost after RR boot. The recovery partition comes after the boot and system partition. By flashing the recovery into boot, it screws up the order.
Nevertheless, the Command Not Allowed was still a problem if I tried to use "Fastboot flash recovery twrp.img"
Any ways I was still looking into this problem and started looking into the boot.img stuff and saw someone uses this command line: "fastboot erase boot". This helps someone being able to flash a boot.img when the user was having the Command not Allowed problem trying to flash a different img for the boot partition.
This gave me an idea to try and use "fastboot erase recovery".
I gave it a try and I was able to use "fastboot flash recovery twrp.img" afterwards! It was done in a second.
Then I went through the normal steps of flashing RR and TWRP stayed this time. So now all is good with everything!
Any ways to recap, my full steps used for my RR Installation:
1. Flashtool to flash an Android 5.1.1 stock rom. I used C6903_14.6.A.1.236_1276. (obtained through Flashtool, Xperifirm) Your phone has to run in 5.1.1 for the SIM and IMEI to work in RR. Don't need to flash modem.zip, that's for C6902 only.
2. Fastboot flash erase recovery
3. Fastboot flash recovery twrp.img
4. Follow instructions to flash RR normally.
5. Resize system partition size (for flashing GAPPS micro size or larger).
6. Flash GAPPS.
7. Flash su addon from Lineage's website to allow root for apps and ADB.
I hope this helps someone with similar problems in the future. Thanks to those who stop in to see me ramble to myself about silly stuff
I had the same error message and was able to successfully flash using the phone and the Android Studio Emulator app.
I was already rooted and had an unlocked bootloader.
I tried this solution and it said error: cannot "recovery": No such file or directory LOL even though it's right here and I use it all the time..........I just can't figure it out.

[Stock ROM][Applied 1 October OTA Update]Trying to get TWRP custom recovery flashed

Hello. So, I got my Moto G5s Plus around the last week of October or beginning of November. It is a great device, but I learned about the camera flaws by Motorola and unlocked the bootloader to fix it by following this XDA thread here for camera fixing and the Chromatix mod. I learned that I could edit build.prop without flashing the TWRP recovery but using it temporarily following the guide here. build.prop edit would enable cam2api for third party cam apps. The Chromatix mod threads/posts were for the G5 Plus, which I didn't realize at the time and didn't backup original Chromatix files. However, That went successfully and I could still use my phone with better camera quality. Note that prior to doing this fix and before unlocking the bootloader (I believe) I had updated my device from Nougat to Oreo. My bootloader is indeed unlocked.
Now, when the 1 October OTA Update came I was hesitent because I had came across some rooting/custom rom/custom recovery/mod articles while learning about unlocking the bootloader. Yet and before reading more to get educated on this, I applied the update to my phone. I was hoping it wouldn't brick it or that it would fail if it didn't work. It failed (because of the modification on the stock ROM) at the last bit of the update and rebooted my phone. My phone worked and it let me know nothing was changed by the failed update. However, my phone since then has shown as if it is up-to-date in system updates.
So, basically I have been trying to flash TWRP for my Moto G5s Plus after that was done. I want to see about backing up my stock ROM (or the most important parts) possibly getting a good custom ROM installed (which I believe they have their own official Android security updates from Google?). However flashing TWRP hasn't worked. I get the following in PowerShell (cmd):
PS C:\Android SDK\platform-tools> fastboot flash recovery twrp.img
Sending 'recovery' (10236 KB) OKAY [ 0.407s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.172s]
Finished. Total time: 0.594s
Note that I renamed twrp-3.1.1-sanders.img to twrp.img as it was a suggestion I followed at the time. This I heard is normal, but when I go to Recovery Mode on my phone I see this:
Start Up Failed:
Repair message stuff
AP Fastboot Flash Mode (Secure)
Fastboot Reason: UTAG *bootmode* configured as fastboot
~~~
Error: failed to load kernel!
~~~
I also tried to find the latest stock ROM to flash because I believe I read I may need to do that. I found SANDERS_RETAIL_8.1.0_OPSS28.65-36-3_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and tried to use "Apply update from ADB" from the stock Recovery (when it was working normally after powering off and not with kernel errors because of this). It failed.
I couldn't find the right answer(s). Thank you to anyone that can help me or others who have done the same!!
EDIT (11/19/2018):
So, last night I tried wiping my data in stock recovery and then I tried to do this again. It still didn't work. I also tried to apply the same stock zip as well as boot_magisk.img from this thread here https://forum.xda-developers.com/moto-g5s-plus/development/stock-kernel-prerooted-8-1-0-t3863301.
PS C:\Android SDK\platform-tools> fastboot flash boot boot_magisk.img
Sending 'boot' (10702 KB) OKAY [ 0.391s]
Writing 'boot' (bootloader) Image not signed or corrupt
OKAY [ 0.141s]
Finished. Total time: 0.563s
It all still fails. However, now when I boot up my phone it goes straight to the bootloader instead of loading the OS right away. I can select START to start the phone normally from there.
I got all this resolved through XDA's Telegram group (& specific group for G5s Plus/sanders)! I have TWRP (Treble) and custom rom working after getting an official stock rom from them flashed using fastboot commands!
I don't know if I should or a mod can close/erase this thread now?
Try typing fastboot oem fb_mode_clear while in bootloader
Coala990 said:
Try typing fastboot oem fb_mode_clear while in bootloader
Click to expand...
Click to collapse
Thanks for the suggestion/tip. I will probably try that if I reflash twrp treble (or another version of twrp for Sanders) again. This has been resolved.

Categories

Resources