[Q] T-Mobile M8 S-On no OS installed HELP!!!!! - One (M8) Q&A, Help & Troubleshooting

info:
Tampered
Unlocked
S-ON
Hboot-3.16.0.0000
Radio-1.16.21331931
CID:T-MOB010 V.1.12.531.19
I wiped everything trying to go back to stock. I can only manage to get to TWRP recovery and tried to use the images but doesn't show up. Tried to install the recovery as a .zip but still no luck. Downloaded android sdk, but don't know how to use it. I just wanted to go back to stock. And my guess was if I could manage to S-Off y could install stock recovery.img, I'm desperate.

Easy.
Boot into TWRP, hit the advanced tab, hit adb sideload.
Open terminal in directory of any rom and type
Code:
adb sideload nameof.zip
nameof.zip is obviously gonna be replaced by the actual name of the zip
Let it do its thing

mikeyinid said:
Easy.
Boot into TWRP, hit the advanced tab, hit adb sideload.
Open terminal in directory of any rom and type
Code:
adb sideload nameof.zip
nameof.zip is obviously gonna be replaced by the actual name of the zip
Let it do its thing
Click to expand...
Click to collapse
Thanks for taking the time to answer me, it didn't work but managed to fix it by putting the back up in TWRP/BACKUPS/[folder with your unique device id/Folder with my actual recovery all I know is I had it un zipped and zipped just in case. But really Thank you I'm so glad I fixed it.

Related

Cannot install Recovery 3.0

SO I've been trying to install the 3.0 cwm recovery but I get errors in Android and in the FASTBOOT USB mode.
In Android is says cannot find flash_image or something like that.
and in FASTBOOT it says error: cannot load 'recovery.img/
I unplugged my device and plugged it back in, rebooted it.
Do I have to have a 2.0 recovery FIRST? or can I just do 3.0 first? Is that even the problem?
I can't figure out what the problem is and I've read like 10 different threads from different forums as well.
Of course I'm perm rooted and I've installed Hboot.
James_Caliber said:
SO I've been trying to install the 3.0 cwm recovery but I get errors in Android and in the FASTBOOT USB mode.
In Android is says cannot find flash_image or something like that.
and in FASTBOOT it says error: cannot load 'recovery.img/
I unplugged my device and plugged it back in, rebooted it.
Do I have to have a 2.0 recovery FIRST? or can I just do 3.0 first? Is that even the problem?
I can't figure out what the problem is and I've read like 10 different threads from different forums as well.
Of course I'm perm rooted and I've installed Hboot.
Click to expand...
Click to collapse
For flash_image, you need to make sure you have the binary. There is a thread all about it. (http://forum.xda-developers.com/showthread.php?t=902493)
For fastboot, is the recovery.img file located in whatever directory you are running the fastboot command from? What command are you running?
ianmcquinn said:
For flash_image, you need to make sure you have the binary. There is a thread all about it. (http://forum.xda-developers.com/showthread.php?t=902493)
For fastboot, is the recovery.img file located in whatever directory you are running the fastboot command from? What command are you running?
Click to expand...
Click to collapse
Yes I have flash_image in my tools folder :/
Does that answer the question?
James_Caliber said:
Yes I have flash_image in my tools folder :/
Does that answer the question?
Click to expand...
Click to collapse
Do you have an ENG. Hboot? If not, you can not use fastboot, youll have to flash recovery from terminal using flash_image.
Edit: See in your first post says you have HBoot installed, you mean ENG. Hboot right?
If you do have ENG. Hboot type
Code:
fastboot devices
Do you get a "serial # fastboot" ?
See if you have the right drivers installed. I had ADB up and running but when I tried fastboot it would not recognize my G2 so I had to install new drivers.
James_Caliber said:
SO I've been trying to install the 3.0 cwm recovery but I get errors in Android and in the FASTBOOT USB mode.
In Android is says cannot find flash_image or something like that.
and in FASTBOOT it says error: cannot load 'recovery.img/
I unplugged my device and plugged it back in, rebooted it.
Do I have to have a 2.0 recovery FIRST? or can I just do 3.0 first? Is that even the problem?
I can't figure out what the problem is and I've read like 10 different threads from different forums as well.
Of course I'm perm rooted and I've installed Hboot.
Click to expand...
Click to collapse
Take the .img file that you have for CM 3 and rename it to: recovery.img then place it on your sdcard. Open terminal emulator on your phone and type in the following 3 commands, hitting enter after each one:
su
flash_image recovery /sdcard/recovery.img
reboot recovery
If you need a copy of the latest CM 3 (3.0.0.5) you can download it from here:
http://phones.crackflashers.com/vision/recoveries/vision-cwm3src3.0.0.5-1-16-11.img
EdKeys said:
Take the .img file that you have for CM 3 and rename it to: recovery.img then place it on your sdcard. Open terminal emulator on your phone and type in the following 3 commands, hitting enter after each one:
su
flash_image recovery /sdcard/recovery.img
reboot recovery
If you need a copy of the latest CM 3 (3.0.0.5) you can download it from here:
http://phones.crackflashers.com/vision/recoveries/vision-cwm3src3.0.0.5-1-16-11.img
Click to expand...
Click to collapse
If you want to use flash_image, you need to place the binary on your phone and make it executable. The guide I linked to explains exactly what you are supposed to do.
For fastboot, do you have recovery.img in your tools directory?
I've got the same problem as the OP. How do i know if i have hboot? I have s off using the original visionary method. I try to push the image through termimal but it says the image isn't found. I need to do the entire binary method to get the path to work? this is why i want to wait for the update through rom manager, so i can flash back and forth anytime.
sent from my V I S I O N.
PatrickHuey said:
I've got the same problem as the OP. How do i know if i have hboot? I have s off using the original visionary method. I try to push the image through termimal but it says the image isn't found. I need to do the entire binary method to get the path to work? this is why i want to wait for the update through rom manager, so i can flash back and forth anytime.
sent from my V I S I O N.
Click to expand...
Click to collapse
Not exactly sure what you are saying about pushing things through terminal and the binary method, but if you want to use flash_image, you should follow the guide I linked to.
If you want to use flashboot, you need to make sure you have the engineering hboot (if you boot you phone while holding volume down, the first line should say something like ENG S-OFF instead of SHIP S-OFF).
If you want yet another method to flash the recovery, there is also the sticky at the top of this forum.
i found this to be the best and easiest way to flash CWM recovery 3.0.0.5
I found a really easy way to flash the new recovery. My fastboot didnt seem to have an option for a terminal so I thought of this genius yet n00b way. Here are the steps.
Steps:
1. Install clockworkmod from market.
2. Flash Clockworkmod recovery from Rom Manager.
3. Navigate to clockworkmod/download/koush.tandtgaming.com/recoveries (or where ever your recovery was downloaded to. This can be done in File Manager, Astro, or Androzip.
4. Mine was "recovery-clockwork-2.5.1.3-vision.img". Rename it to "recovery-clockwork-2.5.1.3-visionXXX.img" or something obviously different.
5. Download clockworkmod 3.0 from hereish:
http://forum.xda-developers.com/showthread.php?t=893933
6. Move your recovery.img to clockworkmod/download/koush.tandtgaming.com/recoveries and name it recovery-clockwork-2.5.1.3-vision.img
7. Go into ROM Manager and Flash Clockworkmod recovery, it will say its still 2.5.1.3 when your done. Reboot into recovery and you'll be welcomed by a new orange 3.0
Click to expand...
Click to collapse
If you rooted using rage, the flash_image kernel should be on your phone.
blackknightavalon said:
If you rooted using rage, the flash_image kernel should be on your phone.
Click to expand...
Click to collapse
I don't think that's true. Temp rooting with rage doesn't install any apps for you by itself (and the temp root to perm root guides only install Busybox, SuperUser, and the su binary). It's just that most people flash a custom rom after rooting, and many of those roms include flash_image. If you rooted and then stayed on stock for example though, you would have to get the flash_image program yourself (and it's something independent of the kernel).

[Q] installing custom roms

hi...
can any1 tell me how to install custom roms using pc...........
i have searched the forum....but couldnt find any answer.................
sorry for starting a new thread........
thanks in advance
General Method:
- find, download and copy a flashable rom called "fullwipe 1.3" to the sd
- copy the zip with the rom you want to load in it to your sd card
- reboot into cwm recovery
- install zip from sd card
- choose the fullwipe 1.3 zip
- install
- then choose the rom's zip
- install
- reboot
wait for it to load. there you go.
For more advanced rom's, you must make directory's on your sd card for them to work properly. Follow instructions posted by the Rom's developer for proper installation.
thanks bro..........4 all ur help..............
1 more question........
what about using it through the fone......
i mean .....after downloading through the rom manager..........should i follow the same procedure ????
question
I rooted today, s-off & eng-off, installed rom manager
what do i have to do to get clockwork to work
I try booting into recovery but, display goes blank & has a red triangle symbol & after many minutes nothing happens..... can some inform me of the step I may have missed or something i can do to verify that i have the device set up properly.
Hopefully Thanks in advance.
gixer131 said:
question
I rooted today, s-off & eng-off, installed rom manager
what do i have to do to get clockwork to work
I try booting into recovery but, display goes blank & has a red triangle symbol & after many minutes nothing happens..... can some inform me of the step I may have missed or something i can do to verify that i have the device set up properly.
Hopefully Thanks in advance.
Click to expand...
Click to collapse
Flash CWM recovery from rom manager again.
Hawks556 said:
Flash CWM recovery from rom manager again.
Click to expand...
Click to collapse
I can appreciate that, but I need to know what to do. I try to do that & i get an error while attempting to run privileged commands. Flashing sounds all great but I cant seem to get it to do anything in recovery... error issues trying to do that, or anything else, I also have super user update issues that say they put a recovery image on the sd card & to go boot that from within recovery.
Just hoping to find out why i cant do the simple things everyone speaks of.
gixer131 said:
I can appreciate that, but I need to know what to do. I try to do that & i get an error while attempting to run privileged commands. Flashing sounds all great but I cant seem to get it to do anything in recovery... error issues trying to do that, or anything else, I also have super user update issues that say they put a recovery image on the sd card & to go boot that from within recovery.
Just hoping to find out why i cant do the simple things everyone speaks of.
Click to expand...
Click to collapse
Well if you can't flash recovery from Rom Manager then there's something wrong with your root privileges or s-offs... Just to make things clear, how did you try to flash the recovery?
AT THE TOP OF THE BOOTLOADER IT MUST SAY "... ENG S-OFF RL" FOR THIS TO WORK
With the device connected, boot into bootloader and select FASTBOOT and press power once.
It will now show FASTBOOT USB, and give you 4 options.
Download the newest 4.x.x.x version of the cwm recovery from the dev section.
Download My Toolkit and Extract to C:\
In the recovery zip that you downloaded from the dev thread, find the "recovery.img" and extract it to the RESOURCE folder of my toolkit. (make sure its only the recovery.img and not the folders it sits in)
open up a command prompt (windows key + R, type "cmd" and hit enter)
type in: cd "C:\HTC ACE TOOLKIT\RESOURCE" and hit enter.
the prompt should now be in that directory.
now type in the following EXACTLY and press enter afterwards:
fastboot flash recovery recovery.img
Let it flash, and badaboom, you have just flash cwm recovery.
JSLEnterprises said:
AT THE TOP OF THE BOOTLOADER IT MUST SAY "... ENG S-OFF RL" FOR THIS TO WORK
With the device connected, boot into bootloader and select FASTBOOT and press power once.
It will now show FASTBOOT USB, and give you 4 options.
Download the newest 4.x.x.x version of the cwm recovery from the dev section.
Download My Toolkit and Extract to C:\
In the recovery zip that you downloaded from the dev thread, find the "recovery.img" and extract it to the RESOURCE folder of my toolkit. (make sure its only the recovery.img and not the folders it sits in)
open up a command prompt (windows key + R, type "cmd" and hit enter)
type in: cd "C:\HTC ACE TOOLKIT\RESOURCE" and hit enter.
the prompt should now be in that directory.
now type in the following EXACTLY and press enter afterwards:
fastboot flash recovery recovery.img
Let it flash, and badaboom, you have just flash cwm recovery.
Click to expand...
Click to collapse
The BOOTLOADER SAYs "... ENG S-OFF but no RL @ the end
Can someone instruct me to what I may have done wrong? I know if I try to s-off or ENG-off I now get a connection problem but the first time I tried it seemed to work properly.
Thanks
Thanks for the help, I have successfuly flached clockwork now & a new rom.... What should I do to update a radio for my device on telus? Thanks
gixer131 said:
Thanks for the help, I have successfuly flached clockwork now & a new rom.... What should I do to update a radio for my device on telus? Thanks
Click to expand...
Click to collapse
well, in that toolkit i told you to download is a command script that does pretty much what I told you do to for the recovery.
Since you and I have the exact same phone I recommend grabbing the radio from the 2.52 korean build (Radio_12.59.60.26U_26.11.04.21_M), and the rill's as well.
Here is the radio and ril (first 2 links, download via the dropbox links): http://forum.xda-developers.com/showthread.php?t=996630
make sure you're in bootloader > fastboot and it says FASTBOOT USB on the screen
take a radio.img from within the zip and drop it into the resource folder and then run the shorcut in the toolkit.
It will now flash the radio to your phone and reboot.
Now with the rill's you flash via cwm recovery, from the RIL zip you downloaded, off your sd card in the same way you would flash a rom.
JSLEnterprises said:
well, in that toolkit i told you to download is a command script that does pretty much what I told you do to for the recovery.
Since you and I have the exact same phone I recommend grabbing the radio from the 2.52 korean build (Radio_12.59.60.26U_26.11.04.21_M), and the rill's as well.
Here is the radio and ril (first 2 links, download via the dropbox links): http://forum.xda-developers.com/showthread.php?t=996630
make sure you're in bootloader > fastboot and it says FASTBOOT USB on the screen
take a radio.img from within the zip and drop it into the resource folder and then run the shorcut in the toolkit.
It will now flash the radio to your phone and reboot.
Now with the rill's you flash via cwm recovery, from the RIL zip you downloaded, off your sd card in the same way you would flash a rom.
Click to expand...
Click to collapse
I would Like to thank you for your help & support, I was a the step of having fastboot usb And on my pc I unziped the radio And droped the image in the resource folder, a window pops up (disk burner) only option to choose is DVD R Drive.... do I have to have the SD card unmouted as a disk drive to the computer?
leave disk burner outta this. lol
The phone should be in bootloader under "fastboot" so the highlighted area will say FASTBOOT USB (since your phone is connected to your pc).
If radio.img is in the RESOURCE folder of my toolkit, go back to the main folder (HTC ACE TOOLKIT) and just double click the "Flash Radio" shorcut.
JSLEnterprises said:
leave disk burner outta this. lol
The phone should be in bootloader under "fastboot" so the highlighted area will say FASTBOOT USB (since your phone is connected to your pc).
If radio.img is in the RESOURCE folder of my toolkit, go back to the main folder (HTC ACE TOOLKIT) and just double click the "Flash Radio" shorcut.
Click to expand...
Click to collapse
Most excellent! Thanks & Thank you, your help has been most usefull & is quite appreciated!
Changed Rom
Changed rom last night & wanted to know weather I should flash the "rill's" & "radio" each time I change roms. I just did the radio now so hope that cures the tinny sound, also it sounded kinda tinny just playing music, is there a patch or something else to do or is all that fixed in the radio?
Any suggestion on roms to try? using Revolution HD right now.

[Q] bootloader help

im in bootloader menu on my htc. i lost superuser access, and all root apps wont work either. im tryin to update superuser but cant get anything to work. please help
It sounds like perhaps you took an OTA and it replaced a lot of things, including removing root access and possibly placing you back on Stock Recovery instead of TWRP or CWM
If you're actually at the bootloader menu, does it say "UNLOCKED" at the top? I assume you've also done Rumrunner's S-OFF at some point, right?
For you to ever have had root access at some point, it means that you flashed in a custom recovery and flashed in a Superuser package ZIP file.
Being at the bootloader menu gives you the option to go to fastboot, or to go to recovery. What happens when you go to Recovery?
If you have a custom recovery (TWRP or CWM) then you'll have the option to ADB Sideload a ZIP file for installation to your phone.
Koush keeps his Superuser.zip in the description of his app on the Play Store: https://play.google.com/store/apps/d...uperuser&hl=en
ChainFire keeps his SuperSU.zip here: http://download.chainfire.eu/supersu
Don't forget to get more info about SuperSU from his official thread at http://forum.xda-developers.com/show....php?t=1538053
projektorboy said:
It sounds like perhaps you took an OTA and it replaced a lot of things, including removing root access and possibly placing you back on Stock Recovery instead of TWRP or CWM
If you're actually at the bootloader menu, does it say "UNLOCKED" at the top? I assume you've also done Rumrunner's S-OFF at some point, right?
For you to ever have had root access at some point, it means that you flashed in a custom recovery and flashed in a Superuser package ZIP file.
Being at the bootloader menu gives you the option to go to fastboot, or to go to recovery. What happens when you go to Recovery?
If you have a custom recovery (TWRP or CWM) then you'll have the option to ADB Sideload a ZIP file for installation to your phone.
Koush keeps his Superuser.zip in the description of his app on the Play Store: https://play.google.com/store/apps/d...uperuser&hl=en
ChainFire keeps his SuperSU.zip here: http://download.chainfire.eu/supersu
Don't forget to get more info about SuperSU from his official thread at http://forum.xda-developers.com/show....php?t=1538053
Click to expand...
Click to collapse
i ran rummer a month or so ago. i had s-off and on bootloader menu it says unlocked. when i click on recovery it just reboots. when i first did this i never flashed twrp. i did a root check when i did rumrunner it said root access granted. now when i check it it says no root access, and my superuser is gone. i tried dl all sdk again, but i cant get comp to find phone in cmp. i also tried to launch rumrunner again ,, it rebooted phone few times then ended with stupid problems with phone press enter to exit. im about to throw in towel after hours of trying different things..
projektorboy said:
It sounds like perhaps you took an OTA and it replaced a lot of things, including removing root access and possibly placing you back on Stock Recovery instead of TWRP or CWM
If you're actually at the bootloader menu, does it say "UNLOCKED" at the top? I assume you've also done Rumrunner's S-OFF at some point, right?
For you to ever have had root access at some point, it means that you flashed in a custom recovery and flashed in a Superuser package ZIP file.
Being at the bootloader menu gives you the option to go to fastboot, or to go to recovery. What happens when you go to Recovery?
If you have a custom recovery (TWRP or CWM) then you'll have the option to ADB Sideload a ZIP file for installation to your phone.
Koush keeps his Superuser.zip in the description of his app on the Play Store: https://play.google.com/store/apps/d...uperuser&hl=en
ChainFire keeps his SuperSU.zip here: http://download.chainfire.eu/supersu
Don't forget to get more info about SuperSU from his official thread at http://forum.xda-developers.com/show....php?t=1538053
Click to expand...
Click to collapse
this also all started after verizon came out with update and phone automatically updated but unsuccusfully
Thank you for re-affirming my suspicion that an OTA put you in this position.
Rumrunner wasn't ever going to help you in your situation. Rumrunner is purely for achieving S-OFF. Since you're still S-OFF, it didn't have anything to do with your phone. Your root access is gone because the OTA wiped it out. It's important to always be careful about OTA updates because OTA updates assume that you NEVER modified your phone and will write whatever they want to wherever they want.
Since you can at least get to the bootloader, your phone can be saved. You said that you tried to update your SDK so that you could have the fastboot files available. When you run the SDK updater (I assume you're on Windows) you have to right-click and run as Administrator to make it work.
The files you want for fastboot are hiding in c:\program files (x86)\Android\android-sdk\platform-tools\
Take adb.exe, fastboot.exe, adbwinapi.dll, and adbwinusbapi.dll and copy them to a separate folder. (Such as C:\adb\) Navigate to that folder and do shift+right-click in a blank area of the folder so you can run a command prompt. You will want to put a ROM and a recovery file in this same folder too. (You sound like you want the stock ROM)
Use the command 'fastboot devices' to see if the phone shows up. If the phone doesn't show up, then you need to go to the HTC Website so you can install HTC Sync, then remove Sync (while leaving the drivers behind) so that your phone has the correct drivers to make it show up in fastboot.
If 'fastboot devices' ends up revealing a device, then you can grab a custom recovery image file and do "fastboot flash recovery filename.img" to put a custom recovery in your phone. Then within the custom recovery you can do adb sideload romname.zip to install a ROM and that should put your phone back into a usable state.
projektorboy said:
Thank you for re-affirming my suspicion that an OTA put you in this position.
Rumrunner wasn't ever going to help you in your situation. Rumrunner is purely for achieving S-OFF. Since you're still S-OFF, it didn't have anything to do with your phone. Your root access is gone because the OTA wiped it out. It's important to always be careful about OTA updates because OTA updates assume that you NEVER modified your phone and will write whatever they want to wherever they want.
Since you can at least get to the bootloader, your phone can be saved. You said that you tried to update your SDK so that you could have the fastboot files available. When you run the SDK updater (I assume you're on Windows) you have to right-click and run as Administrator to make it work.
The files you want for fastboot are hiding in c:\program files (x86)\Android\android-sdk\platform-tools\
Take adb.exe, fastboot.exe, adbwinapi.dll, and adbwinusbapi.dll and copy them to a separate folder. (Such as C:\adb\) Navigate to that folder and do shift+right-click in a blank area of the folder so you can run a command prompt. You will want to put a ROM and a recovery file in this same folder too. (You sound like you want the stock ROM)
Use the command 'fastboot devices' to see if the phone shows up. If the phone doesn't show up, then you need to go to the HTC Website so you can install HTC Sync, then remove Sync (while leaving the drivers behind) so that your phone has the correct drivers to make it show up in fastboot.
If 'fastboot devices' ends up revealing a device, then you can grab a custom recovery image file and do "fastboot flash recovery filename.img" to put a custom recovery in your phone. Then within the custom recovery you can do adb sideload romname.zip to install a ROM and that should put your phone back into a usable state.
Click to expand...
Click to collapse
Ty for walk through! Will try tomorrow! I wanna get kit kat on here. I think some problems were from files on comp in wrong folders. Hope this works

[Q] can't root or power down device after trying

I have a nexus 7 2013 LTE build KOT49H
I initially managed to unlock and root using nrt 1.8...everything was perfect...there was some confusion getting adb setup though..
(for WugFresh...your instructions are fantastic but you should add a line to "check your device for the message to accept a connection for adb and select ok"...I found myself waiting and waiting, staring at my computer screen thinking that the nrt was hanging when all I needed to do was press "ok" on my device.)
Like I said...everything was perfect but I had to go one step further...
I then installed cyanogenmod 10.2 using twrp...tihs also went fine but I hated it and wanted to get back to my original google os. I had a really hard time getting adb set up once cyanogen was installed but once I finally did I was able to get back to stock again using nrt 1.8.
So now I'm back to stock image KOT49H. Everything runs fine and I see the unlocked logo when I boot so I assume I'm still unlocked.
Here's the problem..
When I try to root now, (I always run the NRT driver test until I get "success" message first) my device hangs on the "Booting modified boot.img to enable..." message.
And I mean hangs...can't even power it down without popping the cover and disconnecting the battery! Thankfully this gets me back to a running device but I still want to root this thing.
Any idea what might be wrong or where I should go to from here?
Thanks for any help you can suggest!
Did you re-enable USB debugging? Another thing is to switch to PTP mode instead of MTP. If none of that is the issue, it may be drivers, fire up wugs toolkit, hook up your device, and click the button "Full Driver Installation Guide", skip to Step 3 tab, and run the "Full Driver Test", if it fails then you're going to need to run through the steps in that "Full Driver Installation Guide, going through each step.
Well all you need to do for root is flash supersu.zip binary. If you have twrp on your device, boot to recovery. When you power on, hold down the volume down button also. When in boot loader mode, select recovery. If its not booting, you could just wipe to factory reset. Flash your supersu zip you'll be good.
Sent from my Nexus 7 using xda app-developers app
mdamaged said:
Did you re-enable USB debugging? Another thing is to switch to PTP mode instead of MTP. If none of that is the issue, it may be drivers, fire up wugs toolkit, hook up your device, and click the button "Full Driver Installation Guide", skip to Step 3 tab, and run the "Full Driver Test", if it fails then you're going to need to run through the steps in that "Full Driver Installation Guide, going through each step.
Click to expand...
Click to collapse
Thanks for the response...
All these check...I do have to switch to PTP to get adb functional and I do get success on the full driver test before I try rooting...device still hangs at "Booting modified boot.img to enable running privileged commands" message and then wont power down without disconnecting battery...
Which recovery are you on stock or still on twrp? If still on twrp, you might want to try flashing the supersu.zip yourself, just get the latest SuperSU put it on your device, and boot into twrp and manually flash it like datallboy suggests, this eliminates the PC/drivers/usb connection as a possible issue.
If you are on stock recovery either flash twrp, or if you want to keep stock recovery, you can boot into twrp temporarily without replacing the stock recovery.
datallboy said:
Well all you need to do for root is flash supersu.zip binary. If you have twrp on your device, boot to recovery. When you power on, hold down the volume down button also. When in boot loader mode, select recovery. If its not booting, you could just wipe to factory reset. Flash your supersu zip you'll be good.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the suggestions...
I lost twrp when I went back to stock build.
Sorry...I'm real green at all of this...
You think I should:
power up to fastboot mode...select boot loader mode...then select recovery to see if it boots?
You need to be real clear for me, I'm a total newb
I would need a link to thorough instructions for wiping to factory reset and flashing the supersu.zip...I do have adt installed and have my path modified so that I can run instructions like "adb devices" in a command window but I'm unclear as to where to place files so they will be seen if I try to flash them via adt. (like I say...this is all new to me and I'm not even sure if that last sentence makes sense)
mdamaged said:
Which recovery are you on stock or still on twrp? If still on twrp, you might want to try flashing the supersu.zip yourself, just get the latest SuperSU put it on your device, and boot into twrp and manually flash it like datallboy suggests, this eliminates the PC/drivers/usb connection as a possible issue.
If you are on stock recovery either flash twrp, or if you want to keep stock recovery, you can boot into twrp temporarily without replacing the stock recovery.
Click to expand...
Click to collapse
Thanks for responding!
TWRP was wiped when I went back to stock build...I'm assuming I have stock recovery now but when your device freezes in fastboot mode and wont power down without pulling the battery you cable you gotta wonder if you have any recovery at all!!!
I'll need instruction on how to flash twrp again...but I believe that this is the step that WugFresh's NRT is trying to do when the device freezes.
SMELZBAD said:
Thanks for responding!
TWRP was wiped when I went back to stock build...I'm assuming I have stock recovery now but when your device freezes in fastboot mode and wont power down without pulling the battery you cable you gotta wonder if you have any recovery at all!!!
I'll need instruction on how to flash twrp again...but I believe that this is the step that WugFresh's NRT is trying to do when the device freezes.
Click to expand...
Click to collapse
I typed this up on the fly so pardon any mistakes, there's more than one way to do this, but I'm basing this on already having wugs toolkit installed and updated and configured for your device on the PC you're going to do this on.
Plug device in, enable USB debugging mode, connect to PC, verify you can access your device through the PC, get the latest UPDATE-SuperSU-v1.XX zip, save it to your device (in the root of the sdcard).
EDIT: OR, even better, you can just boot the device and download it with chrome or whatever and save it to the sdcard, then you can continue:
Open windows explorer and navigate to (assuming you picked the default install directory):
C:\Program Files (x86)\WugFresh Development\data
...in that window, hold down shift, right click, select "Open command windows here", in it, type:
adb devices
...if nothing shows up post back (screenshot would be nice), if your device shows up, then open another windows explorer window and navigate to:
C:\Program Files (x86)\WugFresh Development\data\Recovery_Custom\TWRP\
...and copy the img (mine is openrecovery-twrp-2.6.3.1-flo.img) file you see in there to the other explorer window I told you to open earlier, now assuming you put the SuperSU file on your device in the root folder of the device, you should be able to do:
fastboot boot openrecovery-twrp-2.6.3.1-flo.img
This should reboot your device and boot twrp (this method does not replace whatever recovery you have on there now).
If you want to flash twrp and replace your current recovery you'd want to do:
fastboot flash recovery openrecovery-twrp-2.6.3.1-flo.img
Then once in twrp recovery you can select flash file, navigate to the UPDATE-SuperSU-v1.XX.zip file on your device, select it, and swipe to flash, reboot, run/install busybox and see what happens..it will let you know if there is a problem with root.
mdamaged said:
I typed this up on the fly so pardon any mistakes, there's more than one way to do this, but I'm basing this on already having wugs toolkit installed and updated and configured for your device on the PC you're going to do this on.
Plug device in, enable USB debugging mode, connect to PC, verify you can access your device through the PC, get the latest zip, save it to your device (in the root of the sdcard).
Open windows explorer and navigate to (assuming you picked the default install directory):
C:\Program Files (x86)\WugFresh Development\data
...in that window, hold down shift, right click, select "Open command windows here", in it, type:
adb devices
...if nothing shows up post back (screenshot would be nice), if your device shows up, then open another windows explorer window and navigate to:
C:\Program Files (x86)\WugFresh Development\data\Recovery_Custom\TWRP\
...and copy the img (mine is openrecovery-twrp-2.6.3.1-flo.img) file you see in there to the other explorer window I told you to open earlier, now assuming you put the SuperSU file on your device in the root folder of the device, you should be able to do:
fastboot boot openrecovery-twrp-2.6.3.1-flo.img
This should reboot your device and boot twrp (this method does not replace whatever recovery you have on there now).
If you want to flash twrp and replace your current recovery you'd want to do:
fastboot flash recovery openrecovery-twrp-2.6.3.1-flo.img
Then once in twrp recovery you can select flash file, navigate to the UPDATE-SuperSU-v1.XX.zip file on your device, select it, and swipe to flash, reboot, run busybox and see what happens.
Click to expand...
Click to collapse
Thanks a ton for the instruction!
I'm starting to make sense of this.
Found some other instruction for getting twrp back on the device which I think I'll try before flashing the superSU:
They're exactly what you're describing. I've also figured out where the flashboot.exe stuff is on my computer and added twp.img file there. I'' try getting twrp on and then I'll flash the superSU via twrp.
It'll probably be tomorrow before I get a chance to try all this but I'll be sure to post back once I do.
I'm still in the dark as to why missing this superSU thingy would be causing the device to freeze up the way it does when I try to root using WugFresh's NRT...I thought that flashing twrp and superSU is what the NRT is trying to do when it tries to root my device???
Anyway gtg...thanks all for assisting...I'll post back after the flash attempts...hopefully with happy news!
SMELZBAD said:
Thanks a ton for the instruction!
I'm starting to make sense of this.
Found some other instruction for getting twrp back on the device which I think I'll try before flashing the superSU:
They're exactly what you're describing. I've also figured out where the flashboot.exe stuff is on my computer and added twp.img file there. I'' try getting twrp on and then I'll flash the superSU via twrp.
It'll probably be tomorrow before I get a chance to try all this but I'll be sure to post back once I do.
I'm still in the dark as to why missing this superSU thingy would be causing the device to freeze up the way it does when I try to root using WugFresh's NRT...I thought that flashing twrp and superSU is what the NRT is trying to do when it tries to root my device???
Anyway gtg...thanks all for assisting...I'll post back after the flash attempts...hopefully with happy news!
Click to expand...
Click to collapse
Wug's toolkit is doing exactly that, the main difference in doing it manually is we get to see where the problem is.
If this fails then I would probably say you should backup anything on your device you don't want wiped, and try one click restore and try rooting again.
Good luck.
mdamaged said:
I typed this up on the fly so pardon any mistakes, there's more than one way to do this, but I'm basing this on already having wugs toolkit installed and updated and configured for your device on the PC you're going to do this on.
Plug device in, enable USB debugging mode, connect to PC, verify you can access your device through the PC, get the latest UPDATE-SuperSU-v1.XX zip, save it to your device (in the root of the sdcard).
EDIT: OR, even better, you can just boot the device and download it with chrome or whatever and save it to the sdcard, then you can continue:
Open windows explorer and navigate to (assuming you picked the default install directory):
C:\Program Files (x86)\WugFresh Development\data
...in that window, hold down shift, right click, select "Open command windows here", in it, type:
adb devices
...if nothing shows up post back (screenshot would be nice), if your device shows up, then open another windows explorer window and navigate to:
C:\Program Files (x86)\WugFresh Development\data\Recovery_Custom\TWRP\
...and copy the img (mine is openrecovery-twrp-2.6.3.1-flo.img) file you see in there to the other explorer window I told you to open earlier, now assuming you put the SuperSU file on your device in the root folder of the device, you should be able to do:
fastboot boot openrecovery-twrp-2.6.3.1-flo.img
This should reboot your device and boot twrp (this method does not replace whatever recovery you have on there now).
If you want to flash twrp and replace your current recovery you'd want to do:
fastboot flash recovery openrecovery-twrp-2.6.3.1-flo.img
Then once in twrp recovery you can select flash file, navigate to the UPDATE-SuperSU-v1.XX.zip file on your device, select it, and swipe to flash, reboot, run/install busybox and see what happens..it will let you know if there is a problem with root.
Click to expand...
Click to collapse
Followed your instructions...everything went as it should until I got to:
fastboot boot openrecovery-twrp-2.6.3.1-deb.img
instead of rebooting the device I only got waiting for device message in command window...
is device supposed to be put in bootloader mode before entering this instruction maybe???
okay I got twrp to flash...took like .7 seconds so I guess it was already on there...
when I tried to flash UPDATESuperSU (and by flash I assume you mean install???)
I get:
Updating partition details...
E: Unable to open zip file.
Error flashing zip ' /sdcard/UPDATE-SuperSU-v1.89.zip
Updating partition details...
and the in red underneath: Failed
and the 3 twrp button choices of home Wipe cache/davlik and Reboot System
I selected reboot system and then got message "this device is not rooted swipe to install SuperSU now
I swiped...and the system has rebooted and I now have SuperSU installer app icon in apps bit after running root checker I get device is not properly rooted message
I then ran the SuperSU installer app and it gave me an option to update via the play store...which I did...then ran SuperuserSU which was now updated and installed and it completed rooting...after rebooting the device Root Checker now shows device properly rooted!
THANKS A TON GUYS!!!
SMELZBAD said:
okay I got twrp to flash...took like .7 seconds so I guess it was already on there...
when I tried to flash UPDATESuperSU (and by flash I assume you mean install???)
I get:
Updating partition details...
E: Unable to open zip file.
Error flashing zip ' /sdcard/UPDATE-SuperSU-v1.89.zip
Updating partition details...
and the in red underneath: Failed
and the 3 twrp button choices of home Wipe cache/davlik and Reboot System
I selected reboot system and then got message "this device is not rooted swipe to install SuperSU now
I swiped...and the system has rebooted and I now have SuperSU installer app icon in apps bit after running root checker I get device is not properly rooted message
I then ran the SuperSU installer app and it gave me an option to update via the play store...which I did...then ran SuperuserSU which was now updated and installed and it completed rooting...after rebooting the device Root Checker now shows device properly rooted!
THANKS A TON GUYS!!!
Click to expand...
Click to collapse
Curious. It sounds like a permissions problem, not sure if fix permissions would have helped (no need to try if it's working as it should).
Oh well, glad to help and that it's sorted.
mdamaged said:
Curious. It sounds like a permissions problem, not sure if fix permissions would have helped (no need to try if it's working as it should).
Oh well, glad to help and that it's sorted.
Click to expand...
Click to collapse
Ya...something likely still abit wacky...I'll be sure to post if anything weird starts happening but for now all is good...I'm definitely rooted though...I was just able to mount a flash drive via Stick Mount and run a video off of it!

[Q] help for root

Hi guys,
I have already read dozens of pages regarding the procedure to root my new Htc M8 but I am still a bit confused.
In the picture attached you can see the status of my phone, I think the previous owner has already unlocked it .
What I am kindly ask you is to help me to find the next step to root the phone. I suppose that I have to download a TWRP file, copy it to the internal memory of the phone and then chose "Recovery" but I'm not sure and I don't want to make a disaster !!!
Can U help me? I'm on Mac.
thanks
ciao
fausto
now flash any custom recovery and then flash supersu.zip from recovery to make your handset root
fcasini said:
I suppose that I have to download a TWRP file, copy it to the internal memory of the phone and then chose "Recovery"
Click to expand...
Click to collapse
That is not the proper way to install TWRP, and I don't know how you got that notion.
The proper way to install TWRP is described on the TWRP website (see under "Fastboot Install Method"): https://twrp.me/devices/htconem8gsm.html
fcasini said:
Hi guys,
I have already read dozens of pages regarding the procedure to root my new Htc M8 but I am still a bit confused.
In the picture attached you can see the status of my phone, I think the previous owner has already unlocked it .
What I am kindly ask you is to help me to find the next step to root the phone. I suppose that I have to download a TWRP file, copy it to the internal memory of the phone and then chose "Recovery" but I'm not sure and I don't want to make a disaster !!!
Can U help me? I'm on Mac.
thanks
ciao
your lucky to have s-off already phone lol, install TWRP via fastboot command then flash supersu in TWRP
Click to expand...
Click to collapse
ok, thanks to all,
now I have downloaded the TWRP.IMG, adb and Fastboot files and I am approaching to connect my phone to mac, open terminal and then
./adb reboot bootloader
./fastboot twrp.img
SuperSU is already installed on the phone, so I think I don't need to download and install again.
Is it right?
Once Flashed the twrp image, phone will be wiped?
Thank you again, you help and patience is very appreciated
ciao
fausto
fcasini said:
SuperSU is already installed on the phone, so I think I don't need to download and install again.
Is it right?
Click to expand...
Click to collapse
Did you check to see if the phone was still rooted? It was clearly modded by the previous owner, so may still be rooted. You can check with one of the root checker apps; or simply any app that requires root (such as Titanium Backup).
Although its also possible they unrooted and left the SuperSU app still installed. Just having the app installed does not in itself give you root, the binary also has to be installed. So if that is the case (no root) then UES you will still need to download the current version SuperSU and flash in TWRP in order to gain root.
fcasini said:
Once Flashed the twrp image, phone will be wiped?
Click to expand...
Click to collapse
Nope, TWRP just overwrites the recovery partition. Completely separate partition from user data, ROM, etc.
Regardless, I still highly recommend you backup any personal data that is important to you (preferably backup to an off-phone location) before doing any mods, just in case something goes wrong.
Hi Redpoint73, thanks for the useful info.
I am pretty sure that it is unrooted. I unsuccessfully tried to install Titanium Backup and also the SuperSu application don't start because of the missing of root permission.
Then If I have understood your suggestions:
1) connect the phone with debug Usb ON
2) type ./fastboot twrp.img
3) Phone off
4) Power+Vol-
5) Fastboot menu
6) Recovery+Power
Is it right?
And then? What's happen after? The phone will reboot himself?
thanks
ciao
My comments below in red font:
fcasini said:
Then If I have understood your suggestions:
1) connect the phone with debug Usb ON Doesn't matter if Debugging is on, this only enables adb commands. Fastboot commands work regardless of debugging on or not. But Debugging on is good to have in other situations (so I usually leave it on).
2) type ./fastboot twrp.img Don't know where you got this syntax from. Its not correct. The command given on the link I gave previously (Post #3) states: fastboot flash recovery twrp.img
If the syntax is not exactly right, the command will fail or perform the wrong action. Also note that the TWRP img filename in the command needs to match the actual TWRP file you with to flash. You will notice when you download the TWRP file, the file name is actually much longer than just "twrp.img". So you can either type that whole filename exactly, or change the name of the file to actually be "twrp.img" (with no quotes)
3) Phone off
4) Power+Vol-
5) Fastboot menu
6) Recovery+Power
Click to expand...
Click to collapse
At some point before Step 6, you need to put the SuperSU zip on the phone. You can download it direct to your phone from here: https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
After step 6 (boot into TWRP) select "Install" from the main menu. Navigate to the SuperSU zip, then select it. Once its flashed, reboot. You should be rooted and good to go.
redpoint73 said:
My comments below in red font:
fastboot flash recovery twrp.img.
Click to expand...
Click to collapse
redpoint73, I need your precious help
I have connected my phone to the Mac but with the command "./fastboot flash recovery twrp.img" I get the message "Permission denied".
Even with other command like ./reboot or ./adb devices...
What is going wrong? Maybe I've missed something?
I followed also the instruction here https://www.youtube.com/watch?v=WOW38u-02I0 but without luck...
Help!!!
ciao
fausto
fcasini said:
redpoint73, I need your precious help
I have connected my phone to the Mac but with the command "./fastboot flash recovery twrp.img" I get the message "Permission denied".
Even with other command like ./reboot or ./adb devices...
What is going wrong? Maybe I've missed something?
Click to expand...
Click to collapse
I don't know anything about Mac's, so I probably will be of limited help in that regard.
Did you install the Android SDK, or other Mac friendly adb-fastboot environment?
it is really strange...
I have installed both Adb and fastboot but whenever I try to flash the image file I get the same error: Permission denied.
With Mac there is no need of driver to work and I don't know ho to proceed.
Thank you redpoint73, your help has been very appreciated, I will search again on the net to solve the problem.
Have a nice day
ciao
fausto
fcasini said:
it is really strange...
I have installed both Adb and fastboot but whenever I try to flash the image file I get the same error: Permission denied.
Click to expand...
Click to collapse
Make sure you are running fastboot command while the phone is in bootloader-fastboot mode. Run adb command while booted into OS (and Debugging needs to be enabled in Settings).
You are in the correct directory (where your fastboot and adb executables are located) when running the commands?
Try finding a thread specific to running adb/fastboot on a Mac (probably doesn't need to be M8 specific) and reading up or post a link to this thread. This may be some Mac-specific nuance that I am not knowledgeable in.
thanks again dear redpoint73,
I checked again and It seems to be all right but it doesn't work.
I have just one doubt yet. Perhaps I have to flash a root file like this http://www.androidrevolution.org/do...le=Android_Revolution_HD_Root_and_BusyBox.zip and then supersu.img through recovery menu?
Could it be the way to gain the permission?
thanks
ciao

Categories

Resources