Hi All,
I have unlocked my HTC M8 eye with the help of HTCDev site and installed TWRP from playstore. I restarted the phone and went into Fastboot mode and using adb installed TWRP image file for this phone (v2.8.0.3), before it I have saved SuperSU zip file on my local storage. From TWRP in recovery mode I installed SuperSU everything goes good and its shows Success. When I reboot I shows "Your device does not seems to be rooted? Install SuperSu now?" When I gave install now it shows error msg "Failed to copy su binary in to /system/bin/". I tried re-flashing it and tried to install some other versions of SuperSU but none worked. After this phone goes re-booting and stuck in HTC logo screen till I use shortcut keys to enter recovery mode. In Fastboot mode my laptop was able to detect my phone from command prompt and also my internal storage.
I believe I can get back my phone on working. Please help me, I really need my phone back .
If you can still get into recovery, then you can install a custom rom and go that route. Keep in mind, if you are just HTCdev unlocked and you flash a custom rom, you will have to use fastboot to flash the boot.img.
If that doesn't work, then you should be able to find the RUU for your phone and restore it to stock and redo the custom recovery and root. For future reference, just flash the SuperSU zip. TWRP doesn't normally detect that correctly and trying it's method often makes things worse, as you experienced.
Related
hi guys iive unlocked my evo with the htcdev mod and no problem has come out , bun i'm unable to run any recovery.
iìve tryed all cwm twrp and any i found on the site.
i try with fastboot method and abd, all say that the recovery vas written , no error but when i try to lunch recovery the phone show the htc logo stay 10/15 second then reboot the phone.
pls help me
Have you tried downloading the twrp pg86img.zip & make sure it's named PG86IMG.zip then put it on the root of you're sdcard, boot into bootloader and update that way?
CM powered EVO 3D, enough said.
luca73n said:
hi guys iive unlocked my evo with the htcdev mod and no problem has come out , bun i'm unable to run any recovery.
iìve tryed all cwm twrp and any i found on the site.
i try with fastboot method and abd, all say that the recovery vas written , no error but when i try to lunch recovery the phone show the htc logo stay 10/15 second then reboot the phone.
pls help me
Click to expand...
Click to collapse
when the device either hangs on the htc logo or reboots while on the htc logo, it means there is an issue with the actual kernel/ramdisk.
when dealing with a custom recovery, they should always boot without any issues. the best suggestion off the top of my head is to make sure if you're on the CDMA version, use the shooter recovery and if you're on the GSM version, use the shooteru version of the custom recovery.
otherwise, as suggested above, reflash the confirmed correct custom recovery for your device. there are a few ways to flash the custom recovery although, being you used the htc unlock method, regular custom recovery mode will not have write access to the boot/kernel partition.
if you're interested in loading any ROMs which come with kernels or separately flashing a custom kernel, there are essentially two complete methods:
1) use my Flash Image GUI app from normal android mode to flash the kernel. then flash the ROM from custom recovery.
2) use fastboot boot c:\android\cwm-recovery.img . this will temporarily boot the custom recovery and htc unlock will grant it write access to the kernel/boot partition. this command is different than fastboot flash recovery c:\android\cwm-recovery.img. the fastboot boot will temporarily boot into the custom recovery while fastboot flash will permanently write it into the recovery partition.
hope all the extra details make sense and helps!
Ummm.....Just my 2 cents, but it sounds as though the most basic possible problem has been overlooked here. You need to go into menu>settings>power and uncheck the "fast boot" box or do a battery pull, then try to boot into your bootloader to access recovery. With your phone completely powered down (fast boot unchecked or after battery pull), hold volume down and press power. That will put you in your bootloader with an option to boot recovery from there.
ok i'm a noob i've used thr shooter and not the shooteru cwm img, now all works
ty guys
Hey! So I rooted and installed cyanogenmod on my HTC One M7, and It was working fine for a while. Then recently it wouldnt turn on. I can access the bootloader, but my recovery - ClockWorkMod - was not working. I cannot enter recovery or factory reset my device. Also when I try to flash a new recovery via fastboot, it says that it failed to write, and my devices freezes on the fastboot screen. In fact any command I try via fastboot fails. I Hope to be able to restore my phone back to stock sense. Any help?
So I am a first time rooter, so I'll try my best to use the proper terms and whatnot.
Anyways, I have an unlocked HTC One X+ that I am trying to root. I was using the AIO kit by Hasoon2000. I had my bootloader successfully unlocked, and so I proceeded to continue with rooting. I thought I pushed the SuperSU.zip to the device, because the cmd line said it was successful. So I booted into recovery mode, made a backup, and then when to flash the SuperSU.zip file. However, I could not find it in the file explorer in recovery mode.. so I went to push the file to the phone again, but now it says device not found. The only thing I can think that's happened is my USB debugging got turned off... which is bad. So is SuperSU.zip in my phone somewhere, or am I stuck with a phone that can only go into recovery mode?
Thanks for any help!
I have now similar problem too...
actually I had rooted successfully, but after many failed CM11 installation attempts, I decided to relock the bootloader, in order to update the Firmware. But it didn't work too and I came the way back again, in which I unlocked the bootloader with Unlock Token etc. again. Now the bootloader is unlocked but apparently not rooted!?! I can't push superuser via adb because **Device is not found** and I can only go to TWRP Recovery and bootloader...
COULD SOMEONE HELP??!
PS: when i press the reboot in TWRP, it says that "the phone seems not to be rooted, do you want to install the SuperUser? and when I accept it... it reboots only and nothing does change!
well... im not sure what I did differently but it finally recignized the device!! And now I managed to get everything installed... weird!
Device: Motorola Droid RAZR HD; unlocked bootloader; android 4.4
Backstory: I tried to load Cyanogenmod on my phone; but first I had to load TWRP recovery in order to get to load it. This is where the issue came; I decided to go the easy route and attempted to install it through Flashify (an app on the Google Play store); upon restarting my phone; it was bricked. I went into EVERYTHING, when I tried to go into recovery it would just send me through the bootloop and then send me to AP Fastboot.
Confused, I called Motorola; and was notified and Flashify had removed my prevoius recovery and failed to but TWRP resulting in this.
Issue: So what I did is I got the CWM recovery specific for my phone (XT926) and went into ADB fastboot and typed "fastboot flash cwm.img", from my ADB folder of course. Then when I booted into recovery, nothing happened; it would just send me through the bootloop again. Please help.
Hi,
I unlocked my Honor 9 bootloader using the "fastboot oem unlock 'unlock key'" method.
After that it did low level reset or something of the sort and booted to Android.
After that I wanted to install TWRP using fastboot, the problem is that every time I do "adb reboot bootloader" I get a message the device cannot be trusted (see pic) and it boots to android.
I tried pressing power button, up button (this gets me to the recovery), but it always gets back to Android and not to fastboot.
What can I do???
Thank you
Return fully stock, then try again
PalakMi said:
Return fully stock, then try again
Click to expand...
Click to collapse
How do I do that, use the original recovery?
OK, I managed to get to the bootloader by turning off the phone, pressing the volume down button and connecting the USB cable.
I flashed twrp and somehow booted to the recovery I wanted to flash the supersu.zip but all the folders and file names in the sdcard were gibberish.
I rebooted and everything was ok (not gibberish) but instead of having twrp I got the original recovery back.
Since then even if I flash using fastboot the twrp recovery I keep getting the original recovery.
In the fastboot screen there's a message "Android reboot reason: bootloader NA reboot_enter_fastboot_common_func" is it normal? (see pic)
And one last question, should I use SuperSU-v2.82-201705271822.zip or Magisk-v14.0.zip to root?
UPDATE:
I managed to get twrp working.
I did fastboot oem relock, and then unlocked the bootloader again, and it booted to twrp (without re-flashing twrp).
When I tried to flash supersu all the files were gibberish (see pic), what am I missing?
If I wipe data it seems fine, but then I boot to system to copy the supersu file and once I load twrp it is gibberish again.
Also should I use SuperSU-v2.82-201705271822.zip or Magisk-v14.0.zip to root?
Appreciate any help I can get.
This mate is called encryption
Put the SuperSU zip on a SD card and you should be able to flash it without any problems if you use the latest beta release.
Magisk is another story.
Midhon58 said:
This mate is called encryption
Put the SuperSU zip on a SD card and you should be able to flash it without any problems if you use the latest beta release.
Magisk is another story.
Click to expand...
Click to collapse
yeah I figured as much.
Didn't think of using external SD, thanks, was about to try adb sideload, I assume it would have worked too.
Many thanks, the external sd did the trick