Database Develop

My rooting woes

So I finally rooted my N1 today using SuperOneClick. I'm on FRG83. Here's what I've done so far...
Rooted.
Installed ROM Manager.
Flashed with ClockworkMod.
Unable to do a NANDBackup -> Re-rooted -> Still unable -> Flashed with RA -> Successfully did a NAND Backup.
Downloaded MoDaCo's ROM -> Tried flashing -> "Signature Verification Error"
Tried flashing again -> Unable to enter recovery.
Flashed with an older version of Clockwork -> Entered recovery -> Tried flashing -> Same error.
Downloaded Cyanogen 6 -> After multiple tries -> Entered recovery -> Same error
Wiped/Factory Reset -> Cannot enter recovery.
There has to be a simple explanation. Please help!
Thanks a lot

Fastboot oem unlock

daveid said:
Fastboot oem unlock
Click to expand...
Click to collapse
Will that unlock the bootloader? Because I rather keep it locked for warranty!
Thanks

Try using RA recovery instead. You can install the last stable version through ROM manager.

fzr-r4 said:
Try using RA recovery instead. You can install the last stable version through ROM manager.
Click to expand...
Click to collapse
Did do it but it doesn't alway boot into recovery. It usually boots with a Android+triangle+! . If it does boot in recovery, it says signature verification error.

i.mac said:
So I finally rooted my N1 today using SuperOneClick. I'm on FRG83. Here's what I've done so far...
Rooted.
Installed ROM Manager.
Flashed with ClockworkMod.
Unable to do a NANDBackup -> Re-rooted -> Still unable -> Flashed with RA -> Successfully did a NAND Backup.
Downloaded MoDaCo's ROM -> Tried flashing -> "Signature Verification Error"
Tried flashing again -> Unable to enter recovery.
Flashed with an older version of Clockwork -> Entered recovery -> Tried flashing -> Same error.
Downloaded Cyanogen 6 -> After multiple tries -> Entered recovery -> Same error
Wiped/Factory Reset -> Cannot enter recovery.
There has to be a simple explanation. Please help!
Thanks a lot
Click to expand...
Click to collapse
hints on rooting without unlocking bootloader:
http://forum.xda-developers.com/showthread.php?t=792016
general Nexus One wiki:
http://forum.xda-developers.com/showthread.php?t=744720
besides I would not worry about unlocking the bootloader (fastboot oem unlock); it has been proven several times that HTC will honor the warranty if the device has a hardware failure, even if the bootloader is unlocked.
it also seems to be the easiest and safest way to get to root
... on another note... you want your thread to be in Q&A, not development. a moderator will probably move your thread soon.

daveid said:
Fastboot oem unlock
Click to expand...
Click to collapse
this. only. this.

I feel the guy (or gal). I like that my initial "X" screen doesn't have the unlocked icon on it. Big deal? I guess not? Personal preference? Yes.

I too like the boot logo with out the padlock, it looks tacky.

The one time I tried clockworkmod, it messed my phone up, I always go with RA's recovery.
Sent from my Nexus One using XDA App

Google's stock ROM overwrites the recovery at boot. That is why your RA or ClockworkMod is not sticking. As a workaround, you should flash your recovery before rebooting into it else you will boot into the stock one.

Here's where I'm at right now...
I can boot into recovery every time now.
On ClockworkMod... once I select the .zip file (tried 3 now), it starts. Opening, verifying. As soon as it gets to the installing command it exits and goes back into recovery.
On RA, it always says signature verification failed.
Any ideas?
Thanks for all your help guys!

i.mac said:
Here's where I'm at right now...
I can boot into recovery every time now.
On ClockworkMod... once I select the .zip file (tried 3 now), it starts. Opening, verifying. As soon as it gets to the installing command it exits and goes back into recovery.
On RA, it always says signature verification failed.
Any ideas?
Thanks for all your help guys!
Click to expand...
Click to collapse
1) did you unlock the bootloader (fastboot oem unlock)? -- i recommend it
2) which version of amon_ra are you using?... all above 1.8 (i am using 1.9 alpha) allow flashing unsigned *.zip files
3) make sure you have downloaded the CORRECT amon_ra recovery *.img file (for NEXUS, any other will not work)
4) rename the AR recovery file to recovery.img (for easier typing and error minimization when flashing in fastboot) then put it in a folder where fastboot can find it
5) fastboot flash recovery recovery.img
6) flash a ROM of your choosing (i like CM6) - make sure it's fully downloaded and the zip file is not corrupt (= check the md5 sum)
7) flash in amon_ra recovery
8) if you use CM6, have gapps ready (http://wiki.cyanogenmod.com/index.php?title=Gapps) and flash immediately after CM6
9) reboot

i.mac said:
Here's where I'm at right now...
I can boot into recovery every time now.
On ClockworkMod... once I select the .zip file (tried 3 now), it starts. Opening, verifying. As soon as it gets to the installing command it exits and goes back into recovery.
On RA, it always says signature verification failed.
Any ideas?
Thanks for all your help guys!
Click to expand...
Click to collapse
Get Amon RA 1.9a like so (has instructions for locked bootloader):
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Recovery_Images

I use RA 1.8.0.1 to skip around signatures. I'm not unlocked and haven't had issues flashing or the phone unrooting.
Sent from my Nexus One using XDA App

Ignore everyone saying you have to unlock the bootloader, there's zero reason to do so..
You just didn't follow instructions. As someone posted, follow the link for the XDA Wiki recovery images. You missed the part where you have to remove two files, or it restores the recovery image. /!\ symbol = stock recovery; the system restores it automatically if you don't remove the two files.
So right now, read the guide, re-flash RA, remove the two files, then your recovery will stick.
As for one this-or-that ROM doesn't install; ask in their thread.

khaytsus said:
Ignore everyone saying you have to unlock the bootloader, there's zero reason to do so..
Click to expand...
Click to collapse
HTC has proven that they will fix hardware (dust, power button) with or without an unlocked bootloader so circumventing 'fastboot oem unlock' for warranty purposes is not only a bit more trouble for those who can't read/are new.. its also counter productive in light of the whole G2 debacle.. kinda like they give us nice things and we abuse them anyways..

crachel said:
HTC has proven that they will fix hardware (dust, power button) with or without an unlocked bootloader so circumventing 'fastboot oem unlock' for warranty purposes is not only a bit more trouble for those who can't read/are new.. its also counter productive in light of the whole G2 debacle.. kinda like they give us nice things and we abuse them anyways..
Click to expand...
Click to collapse
They denied my warranty (trackball does not scroll downwards anymore) stating they would have to charge $200 for the repair. But, I found a local shop that will do it for $40 and have it done in an hour. I have no regrets unlocking my bootloader, that is why I bought this phone.
I do believe it is the best method, and I would not abuse it just for warranty claims - in hopes that there will be another device with this ability.

Honestly, what's the point of owning a Google Developer phone if you're going to *****-foot around unlocking the full potential of your device?
Honestly, the first thing I did when I got this phone in the mail was unlock it. Best decision ever.

wdfowty said:
Honestly, what's the point of owning a Google Developer phone if you're going to *****-foot around unlocking the full potential of your device?
Honestly, the first thing I did when I got this phone in the mail was unlock it. Best decision ever.
Click to expand...
Click to collapse
To each his or her own, but I have the potential of my phone fully available. If I'd gotten the N1 in January, I may have unlocked the bootloader.
Since there were good root options when I got the phone without unlocking the bootloader, though, I was happy to go that route.
Sent from my Nexus One using XDA App

Doesn't go into recovery

I followed the video tutorial and when I flash recovery, then proceed to boot into recovery it fails to boot into recovery, it just flashes then boots like normal when I perm root. I don't know what's going on. I tried the clear cache command with no response.
I have searched and didn't find anything.
Anyone able to help please?

It is most likely you did something wrong when you flashed the recovery img, just follow the tuto again and make sure to follow each step.
Here is a guide made by mike: http://forum.xda-developers.com/showthread.php?t=2265618

I have done that. Tried a few times. I am fairly "in the know" with rooting ect, but I just can't figure this out.

Disable fast boot
Sent from my PadFone 2 using Tapatalk 4 Beta

Did you reboot after flashing the recovery or did you just go straight into it? I had the same problem and what fixed it is rebooting after flashing the recovery 'fastboot flash recovery recovery.img'.

samflorin said:
Disable fast boot
Sent from my PadFone 2 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Tried that.
TarekElsakka said:
Did you reboot after flashing the recovery or did you just go straight into it? I had the same problem and what fixed it is rebooting after flashing the recovery 'fastboot flash recovery recovery.img'.
Click to expand...
Click to collapse
Tried that to.
When I press perm root, it just reboots normal like recovery doesn't even exist.

Have you tried flashing stock recovery and trying to boot in it? I know that doesn't fix anything, I am just curious if your device will actually boot into any recovery state at all. I have read on XDA about some devices not being able to boot into recovery for some reason.
Here's the stock recovery, just in case: http://forum.xda-developers.com/showthread.php?p=38504123

Okay give me a shot at that.
I noticed after flashing recovery, mine doesn't tampered like it should?

The stock recovery says it's not available anymore.

If it doesn't say TAMPERED then the recovery must have not been flashed to begin with and that is why it's not booting into it. Which recovery are you trying to install? I use TWRP 2.5.0 and I flashed it with fastboot then restarted and it booted fine. My device is S-ON, by the way, and running Trickdroid 7.5.
US Developer Edition Recovery: http://d-h.st/b5g
T-Mobile Recovery: https://www.dropbox.com/s/hvs38223dfrzsny/recovery_tmobile.img
I am not sure if either one will work with your device since I am guessing it's international? But they might be worth a shot.
Never mind, I found the stock international recovery for you: https://dl.dropboxusercontent.com/u/22045273/htc1-stock-recovery.img it was on page 4 of the thread. Give it a go.

I flashed the stock recovery and it still boots like there is no recovery there. and it doesn't say "tampered"
This is crap
EDIT: Yeah I figured it's not being flashed since it's not tampered, but no matter what I try it won't flash.
I'm navigating to the folder: CD C:\One_All-In-One_Kit_v\Data\Recoveries then typing fastboot flash recovery recovery.img and it doesn't work.
It says it's flashed ect, but doesn't boot into it, nore show tampered.

This is very weird and unfortunately I do not know the solution to that. I do not use the All-In-One-Kit, actually, but just a mini-SDK with fastboot files inside. I use shift + right click and "open command prompt window here" rather than navigate to the location, it's just much easier that way. Can you try flashing the latest TWRP recovery?

aussiesausage said:
I followed the video tutorial and when I flash recovery, then proceed to boot into recovery it fails to boot into recovery, it just flashes then boots like normal when I perm root. I don't know what's going on. I tried the clear cache command with no response.
I have searched and didn't find anything.
Anyone able to help please?
Click to expand...
Click to collapse
Are you under s-off ?

tash2013 said:
Are you under s-off ?
Click to expand...
Click to collapse
Nope S-ON
I just downloaded TWRP and flashed it ( fastboot flash recovery recovery.img ) it said all the jabber, like it worked, rebooted and still no "tampered" just reboots like nothing ever happen.
I give up.

Would ADB be any better?

Ugh man that's horrible. I honestly do feel your frustration because I have faced similar situations with my HTC devices (One X and One) countless times, and it sucks because you know the correct steps yet it's not working. I sure hope someone knowledgeable about this can come in and help you. Best of luck.
EDIT: I have only used ADB to sideload a ROM but I don't know about flashing recoveries. If you know how to do it, then why not? It's worth a shot for sure.
EDIT #2: And if you're not familiar with ADB, this article should get you started: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
Make sure you follow all the steps to the word and also install HTC Sync Manager for the proper drivers to be loaded.

I know right, driving me nuts.
I've never done adb to flash a recovery before but don't know if I would want to be the pidgeon to try lol

aussiesausage said:
Nope S-ON
I just downloaded TWRP and flashed it ( fastboot flash recovery recovery.img ) it said all the jabber, like it worked, rebooted and still no "tampered" just reboots like nothing ever happen.
I give up.
Click to expand...
Click to collapse
Try reboot to system (OS), then power off , then go to bootloader -> try enter to recovery again

tash2013 said:
Try reboot to system (OS), then power off , then go to bootloader -> try enter to recovery again
Click to expand...
Click to collapse
Tried that, no go.
Also checked the drivers, re-installed no go.
I am quite up there with adb, but not with flashing recovery with a HTC device lol.

There seems to be another method for flashing recoveries besides fastboot.
http://androidforums.com/cdma-evo-3...lash-recovery-image-via-fastboot-sd-card.html
This is an HTC Evo section but it could work for the One as well, although I am not sure of it. I have done some Googling and I did not come across any articles/threads saying that it is possible to flash a recovery using ADB, so that might not be possible.

HTC One original rom on root device update problem

...guys I was looking around, but couldn't find answer for my little problem. I have rooted HTC One, but rom is stock (didn't plan to change it at all just needed root), but the problem is today a new update came up, and when I tried to install it, it simple didn't do anything.
I go on Install now, phone restarts in recovery mode, then it gives me Installation aborted, and I have 3 thingies, - No; - Yes - Disable recovery flash: - +++++Go Back+++++
Whatever I choose, it just restarts and asks again for same recovery. What shall I do?
In console stands this:
ClockworkMod Recovery v6.0.3.4
E: Invalid command argument
E: Invalid command argument
Warning: No file_contexts
Finding update package...
E: unknown volume for path [DATA:data/cp,/amdrpod_HTC_Europe_2.24.401.8-2.24.401.1_release_331108tottoh71qygw07hf.zip]
E: Can't mount DATA:data/cp,/amdrpod_HTC_Europe_2.24.401.8-2.24.401.1_release_331108tottoh71qygw07hf.zip
Installation aborted
It seems that it cannot mount or something?!?
Cheers...

rex1825 said:
...guys I was looking around, but couldn't find answer for my little problem. I have rooted HTC One, but rom is stock (didn't plan to change it at all just needed root), but the problem is today a new update came up, and when I tried to install it, it simple didn't do anything.
I go on Install now, phone restarts in recovery mode, then it gives me Installation aborted, and I have 3 thingies, - No; - Yes - Disable recovery flash: - +++++Go Back+++++
Whatever I choose, it just restarts and asks again for same recovery. What shall I do?
In console stands this:
ClockworkMod Recovery v6.0.3.4
E: Invalid command argument
E: Invalid command argument
Warning: No file_contexts
Finding update package...
E: unknown volume for path [DATA:data/cp,/amdrpod_HTC_Europe_2.24.401.8-2.24.401.1_release_331108tottoh71qygw07hf.zip]
E: Can't mount DATA:data/cp,/amdrpod_HTC_Europe_2.24.401.8-2.24.401.1_release_331108tottoh71qygw07hf.zip
Installation aborted
It seems that it cannot mount or something?!?
Cheers...
Click to expand...
Click to collapse
Because HTC's updates only work on stock recovery.
Sent from my One using xda app-developers app

Tw1tchy said:
Because HTC's updates only work on stock recovery.
Sent from my One using xda app-developers app
Click to expand...
Click to collapse
Is there a way to update my phone now?

re
is it enough to put in cmd throuhg adb the "fastboot oem lock" command, since my rom is already stock?
Or do I need to flash stock recovery?
Cheers...

rex1825 said:
is it enough to put in cmd throuhg adb the "fastboot oem lock" command, since my rom is already stock?
Or do I need to flash stock recovery?
Cheers...
Click to expand...
Click to collapse
I'm sure you need stock recovery.
Sent from my One using xda app-developers app

Tw1tchy said:
I'm sure you need stock recovery.
Sent from my One using xda app-developers app
Click to expand...
Click to collapse
...ah, I knew it. I presume that stock recovery can't be flashed from custom recovery.
So I need to flash stock recovery, then to lock bootloader, and then I guess I'm good to go!?!
Can I flash it from custom recovery, or do I need to flash it differently? Anyone has link for it, or are all stock recoveries same (I mean from different providers)?
Thanks

You need to install stock recovery using fastboot command "fastboot flash recovery recovery.img"

AllAboutTheCore said:
You need to install stock recovery using fastboot command "fastboot flash recovery recovery.img"
Click to expand...
Click to collapse
...so only stock recovery, I do not need fastboot lock or something?
Cheers...

rex1825 said:
...so only stock recovery, I do not need fastboot lock or something?
Cheers...
Click to expand...
Click to collapse
Install stock recovery like I said above, once done type the following :- "fastboot oem lock"
You should be good to go then for the update. Re-locking your bootloader doesn't wipe your files either, only unlocking wipes the internal storage.

...OK, so here is what I did. From ADB restored the original recovery.img, then lock bootloader, and viola. Thanks guys for helping me out.
Cheers...
Edit: ...I forgot to uninstall SuperSU, and now I have a shortcut in apps and it cannot be removed. When I run it, phone says: "There is no SU binary installed, and SuperSU cannot install it. This is a Problem!" ...lolz me, what to do?

rex1825 said:
...OK, so here is what I did. From ADB restored the original recovery.img, then lock bootloader, and viola. Thanks guys for helping me out.
Cheers...
Edit: ...I forgot to uninstall SuperSU, and now I have a shortcut in apps and it cannot be removed. When I run it, phone says: "There is no SU binary installed, and SuperSU cannot install it. This is a Problem!" ...lolz me, what to do?
Click to expand...
Click to collapse
Just do update then reroot phone as before that's what I did but more than likely you won't be able to soff using revone th world have to use htcdev method
Sent from inside the T.A.R.D.I.S

joselv456 said:
Just do update then reroot phone as before that's what I did but more than likely you won't be able to soff using revone th world have to use htcdev method
Sent from inside the T.A.R.D.I.S
Click to expand...
Click to collapse
What is all this about S-Off and HTCDev ... You unlock your bootloader through HTCDev, S-Off is NOT something that can be done any other way than Revone and Moonshine and NOT on Hboot 1.54 ... Yet.
I've seen several people mention S-Off and HTCDev in the same breath and I think some of you are getting it all mixed up. Unlocking the bootloader and going S-Off are not the same thing and only unlocking the bootloader can be done through the HTCDev website.
I'm pretty sure HTC aren't going to help you remove the security from your device.

I stand corrected you are correct I had soff before that's why I guess it wasn't reset after update
Sent from inside the T.A.R.D.I.S

Original recovery and lock oem doesn't help.
Lads,
Would someone give me a hand here please.
There is a major update for HTC One.
I've flashed original recovery and locked back the phone.
Now it's downloading the update, then goes into reboot and opens fastboot bootloader, instead of installing the update.
What am i doing wrong here?
Thanks in advances

Hi,
I have the same problem as OP.
However the instructions in the replies are terribly confusing, I don't even know where to start!
Someone could do a step-by-step summary for less expert (or just android-retarded) people ?
Thanks a lot!

further to my post above

You need to be on stock recovery. Figure that out and you should be good.

Looking at the various guides somehow related to stock recovery doesn't make sense to me.
There's too many things I am not aware of such as how to flash the stock recovery, if the process will wipe all data, what is a fastboot command etc. etc. Has anybody ever created an easy guide to assess the problem?

AllAboutTheCore said:
What is all this about S-Off and HTCDev ... You unlock your bootloader through HTCDev, S-Off is NOT something that can be done any other way than Revone and Moonshine and NOT on Hboot 1.54 ... Yet.
I've seen several people mention S-Off and HTCDev in the same breath and I think some of you are getting it all mixed up. Unlocking the bootloader and going S-Off are not the same thing and only unlocking the bootloader can be done through the HTCDev website.
I'm pretty sure HTC aren't going to help you remove the security from your device.
Click to expand...
Click to collapse
I have HBOOT 1.54 and S-OFF with rumrunner_HTC_0.5.0

-marco- said:
further to my post above
Click to expand...
Click to collapse
For the sake of common knowledge and in case it may help other unknowing people like me, I'll post what I did here:
I sort of mixed these two guides: this one and this.
Premise:
A. It was impossible to make this whole thing run on my Win8.1 x64 computer. It would never recognize my Fastboot USB device plugged in. I had to use bloody WINXP x86 on my old-ass netbook....
B. Somehow I still had my fastboot/adb compiled folder that I used back in time to root my HTC at first.
C. My phone was Tampered, Unlocked, with HBOOT (i think 1.44 ?) and most definitely S-OFF I would say ? Still don't know for sure.
D. I updated from 4.1.2 through 4.2 to 4.3.
At the 4.2 upgrade the phone went on black screen twice (1st time at ~25%, and 2nd time after 100% was complete). Panic is useless in that case. I went to the bathroom, blasted the strongest lights I had and exposing the phone to the lights, I pressed the power button til the capacitative buttons blinked. After a while the phone rebooted and resumed exactly from the point it blacked out before.
The update to 4.3 went smooth as oil instead.
This is each step I did, following the quoted guides above:
1. Extract the stock recovery file (should be .img) that can be found in the OTA update firmware.zip file, in the firmware package (in some other thread it's explained the path of this file). Place the file in the folder with your fastboot commands.
2. Make sure fastboot and USB Debugging are unchecked on your phone in power settings>fastboot.
3. Power down phone by holding power button and pressing shut down.
4. Once phone is shut down, power phone into bootloader by holding volume down button and pressing power button.
5. Once in the bootloader navigate until it says fastboot usb (must have phone connected to computer).
6. Open up a command prompt where your fastboot commands are located.
7. Type the following with the filename of the stock recovery:
Code:
fastboot flash recovery <filename>
8. Navigate in the bootloader menu to the reboot option to restart your phone.
9. Download the latest SuperSU and place it on your sdcard.
10. Perform the OTA update normally.
11. Once it finishes installing, power down the phone like before and get back to fastboot usb.
12. Flash back the custom recovery using fastboot (I used latest CWM available):
Code:
fastboot flash recovery <filename>
or
Code:
fastboot flash zip <recovery>.zip
13. Then type :
Code:
fastboot reboot
14. Enter recovery by navigating with the volume buttons. Once in recovery, flash the zip of the SuperSU file you previously downloaded.
15. Restart once flashing is complete.

[Q] After flashing TWRP, XT1063 only boots to the unlocked warning screen

My apologies if this has already been posted. I've been looking all morning but haven't seen anyone with the same issue.
Unlock bootloader: no problem.
Flash TWRP: I downloaded from http://teamw.in/project/twrp2/275, and I got an error about partition size mismatch, but that's ok, right?
But when I try to enter recovery, all I get is the warning screen that my phone is unlocked. The drivers are certainly installed correctly, and fastboot is working fine. I just can't get into recovery to flash a ROM!

Restoring to 4.4.4 stock worked like a charm.
http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
I've re-enabled USB debugging. Do I dare try to flash a custom recovery again?

Pandae said:
Do I dare try to flash a custom recovery again?
Click to expand...
Click to collapse
You can use Flashify to make a backup of your current recovery and to flash TWRP.img. should work like a charm.

But Flashify requires root, I see? The reason I'm trying to flash a custom recovery is so I can root in the first place.

Pandae said:
But Flashify requires root, I see? The reason I'm trying to flash a custom recovery is so I can root in the first place.
Click to expand...
Click to collapse
You're right. Latest motorola driver and [TOOL]Minimal ADB and Fastboot will do the trick.

Sorry, I should have clarified that when flashing TWRP, I've already been using fastboot.exe from a command line (and administrator level), with the drivers correctly installed. That's how I was able to unlock in the first place.
I did try it with the version of Fastboot you linked to (what I have works peachy for my Nexus 7), still the same thing. I can't boot into recovery and only get stuck at the Motorola unlocked warning.

Pandae said:
I can't boot into recovery and only get stuck at the Motorola unlocked warning.
Click to expand...
Click to collapse
Oh. Sorry. Can you post the output (terminal & device) of
Code:
fastboot devices
fastboot flash recovery NAME_OF_RECOVERY.img

I'd done "fastboot devices" already to verify, and it returns the serial number, though as I said it's clearly working since I was able to unlock as well as flash recovery. I'm flashing "TWRP2801-titan-motog-2014.img" that I downloaded from the TWRP site, and fastboot gives the standard messages about size and success (and my phone gives the size mismatch error).
It's so strange to me. I've flashed a custom recovery dozens of times on both generations of my Nexus 7s, but I've never seen this.

Pandae said:
It's so strange to me.
Click to expand...
Click to collapse
Yeah......have to meditate about that problem....... is your battery low? Fastboot mode of the device gives me all sorts of problems if it detects low battery

I had been using fastboot at 100% (literally finished a full charge) and 84%, but thanks for the continued attempts at explanation.

Oh, did you check the md5 checksum of your download?

Ah, good thought! I rarely do, but I did just now...and they're the same. It's crazy, isn't it?

Pandae said:
Ah, good thought! I rarely do, but I did just now...and they're the same. It's crazy, isn't it?
Click to expand...
Click to collapse
If you are willing to risk it, try a fresh download and try again. I've flashed TWRP more than 20 times by now and never recieved an error whatsoever. It basically the easiest thing to do.
Incase you are stuck again, don't reflash the entire stock rom. Just flash the recovery.img from the stock rom files.
OR
Try this:
HOW TO ROOT MOTO G 2014 with Temporary Custom Recovery
Cheers

I've flashed a custom recovery many a time and have helped people through it, though on Nexus 7s.
Now shall I compound the mystery? I didn't think yet to use ADB to make my phone reboot to recovery. I had assumed recovery wasn't working. So here we go, after booting into Android:
adb reboot devices: my phone's there.
adb reboot recovery: TWRP's working?! And now root is complete!
It doesn't make sense to me why I can't get into recovery from the bootloader, but I can get into it with the simple ADB command. But I appreciate all the help, thanks!

Pandae said:
It doesn't make sense to me why I can't get into recovery from the bootloader
Click to expand...
Click to collapse
A little workaround:
Install Android Terminal Emulator
Add "Term shortcut" widget.
In "Arguments" enter
Code:
su -c reboot recovery

Problems with flashing TWRP

I have the bootloader unlocked and everything ready to go.
However, when I execute "fastboot flash recovry <recovery_file_name>.img" the first thing that pops up on the cmd is:
(bootloader) has_slot:recovery not found
(bootloader) is_logical:recovery not found
After this it continues the flashing process and finishes with the okay status
However, after rebooting using "fastboot reboot" when I go back into the bootloader and select the recovery option I end up with the droid on his back and an orange triangle with an exclamation mark over him and No Command written under him
Can anyone help with this issue? I really want to flash a new ROM onto my nexus and I also really really want TWRP to work
Thanks,
Danush

Have you tried spelling "recovery" with an "e"?
It may be that your file name isn't properly spelled. I either rename the image to "TWRP. img" or copy the file name in Explorer and paste it into the CMD window so that there is no possibility of mis-spelling.
And another thought - is the TWRP image in the same directory as the fastboot exe?

dahawthorne said:
Have you tried spelling "recovery" with an "e"?
Click to expand...
Click to collapse
Oh yeah that's just a typo in my post ?
Thanks for pointing it out.
I do spell the "recovery" with an "e" and yet I have these issues

I added more comments while you were replying.
Try this:
https://forum.xda-developers.com/showpost.php?p=73648849&postcount=6

Do you have stock Android installed? It will replace any custom recovery with the stock recovery when you boot, unless you've flashed a kernel, mod (e.g. Magisk) or similar that disables that feature.
Don't reboot the device after flashing, boot to recovery instead.
(Don't bother with those "errors", they're just telling you that your device isn't A/B or have logical partitions.)
Edit: oh yeah... Should have checked the link @dahawthorne posted before posting myself. It tells you the same thing. D'oh!

Didgeridoohan said:
Do you have stock Android installed? It will replace any custom recovery with the stock recovery when you boot, unless you've flashed a kernel, mod (e.g. Magisk) or similar that disables that feature.
Don't reboot the device after flashing, boot to recovery instead.
(Don't bother with those "errors", they're just telling you that your device isn't A/B or have logical partitions.)
Edit: oh yeah... Should have checked the link @dahawthorne posted before posting myself. It tells you the same thing. D'oh!
Click to expand...
Click to collapse
Thanks so much for all the help!! After you mentioned it, it kinda hit me that yeah maybe that is what is happening since I used to reboot the device so maybe it was replacing TWRP with the stock recovery.

Hi,
My problem with Redmi Note 4 Snapdragon 625 2,02 GHz and unlocked trying to flash TWRP is like this (phone is in fastboot mode):
PS C:\Users\Dell\Downloads\platform-tools-latest-windows\platform-tools> fastboot devices
55050ae09804 fastboot
PS C:\Users\Dell\Downloads\platform-tools-latest-windows\platform-tools> fastboot flash recovery
fastboot: error: ANDROID_PRODUCT_OUT not set
How can I solve it? Please, help!

Didgeridoohan said:
Do you have stock Android installed? It will replace any custom recovery with the stock recovery when you boot, unless you've flashed a kernel, mod (e.g. Magisk) or similar that disables that feature.
Don't reboot the device after flashing, boot to recovery instead.
(Don't bother with those "errors", they're just telling you that your device isn't A/B or have logical partitions.)
Edit: oh yeah... Should have checked the link @dahawthorne posted before posting myself. It tells you the same thing. D'oh!
Click to expand...
Click to collapse
Don't reboot after flashing? Like when i try it says img unsigned or corrupted, and when i try to then boot into recovery via "fastboot boot recovery" i get sent to the normal Android OS, so what im getting from this is that i somehow have to manually get into the "no command" error window and then power+volume up and that just works? Ill test that, would be really awesome if it does.
Oh yea and booting into the twrp image with "fastboot boot twrp.img" sends to normal os aswell btw.