Database Develop

Now it can be S-OFF, how to install a permanent ROOT?

Just finished the S-OFF using alpharevx, want to know how to do the permanent ROOT.
Any tips?

http://forum.xda-developers.com/showthread.php?p=14693680
check this out, pretty detailed

There is a Sticky at top of the IncS General Forum about this.

You need to install gingerbreak on your phone it's here http://forum.xda-developers.com/showthread.php?t=1044765 and Open Gingerbreak and click Root Device. that's all.

nikkuy said:
You need to install gingerbreak on your phone it's here http://forum.xda-developers.com/showthread.php?t=1044765 and Open Gingerbreak and click Root Device. that's all.
Click to expand...
Click to collapse
Not quite...
I have rooted 4 IncS wit GingerBreak now, and non of them succede first time.
2 got rooted thrid time i ran GB, and 2 of them i had to take the SD card out when the error message came.
But GinderBreak can root the IncS, but somthimes you need some "Ninja" tricks.

Are you done?

geeti said:
http://forum.xda-developers.com/showthread.php?p=14693680
check this out, pretty detailed
Click to expand...
Click to collapse
This just worked for me - it was simple in the end!
I used a spare SD card (I don't think I needed to), just copy/pasted the clockwork recovery .zip file to the card (not in a folder on the card) and rebooted, holding volume down on start-up. After that, it automatically prompted me to install the file, so I let it install.
Then, I rebooted the phone and deleted the above file from the SD card, and replaced it with the signed root .zip file and rebooted with the volume down button again.
Just follow the steps, one by one, 'To root:' in the above linked post, after you have installed the recovery file - it worked first time for me and was actually simple to follow!!
My phone works as it always has done (as you would expect/hope), but now I have root - confirmed with Root Explorer app from Market.
Thanks to all involved in the linked post above.
I also tried GingerBreak a few times but it just didn't work for me, so I gave this a go and it worked first time.

jkolner said:
Not quite...
I have rooted 4 IncS wit GingerBreak now, and non of them succede first time.
2 got rooted thrid time i ran GB, and 2 of them i had to take the SD card out when the error message came.
But GinderBreak can root the IncS, but somthimes you need some "Ninja" tricks.
Click to expand...
Click to collapse
My phone is still on 2.2 Froyo, Gingerbreak is for 2.3 correct?

geeti said:
http://forum.xda-developers.com/showthread.php?p=14693680
check this out, pretty detailed
Click to expand...
Click to collapse
I dont quite understand step 4, 5, 6:
4. Extract recovery.img from the archive and put it with fastboot.
5. Put the phone is Fastboot USB mode (HINT: Android is not up and running - access it from your hboot screen - see how below)
6. fastboot flash recovery <recovery.img> <<< from a command line (use root for Linux- sudo ./fastboot yadda)
Step 4, it says put it with fastboot, does it mean after i extracted the recovery.img, move it to the same folder with the fastboot app (i.e. to the folder android-win-tools where the fastboot app is located?).
Step 5, Fastboot USB mode, this is done by holding the volume down button and the pressing the power button, when the white screen comes up, select Fastboot, and then plug the phone back to the computer via USB?
Step 6, after the phone is plugged to the computer via USB, double click on the fastboot app (the one inside the android-win-tools folder) and when the black prompt screen comes up, type in Linux- sudo ./fastboot yadda?
Btw, I am on Windows computer, not Linux, so is the command prompt Linux- sudo ./fastboot yadda correct?
Also, if I want to bluetooth the su-2.3.6.1-ef-signed.zip to the phone, will it go directly to the SD root location? If not, when I do clockworkmod recovery and "install zip from sdcard", will it able to locate the file?

netwr said:
I dont quite understand step 4, 5, 6:
4. Extract recovery.img from the archive and put it with fastboot.
5. Put the phone is Fastboot USB mode (HINT: Android is not up and running - access it from your hboot screen - see how below)
6. fastboot flash recovery <recovery.img> <<< from a command line (use root for Linux- sudo ./fastboot yadda)
Step 4, it says put it with fastboot, does it mean after i extracted the recovery.img, move it to the same folder with the fastboot app (i.e. to the folder android-win-tools where the fastboot app is located?).
Step 5, Fastboot USB mode, this is done by holding the volume down button and the pressing the power button, when the white screen comes up, select Fastboot, and then plug the phone back to the computer via USB?
Step 6, after the phone is plugged to the computer via USB, double click on the fastboot app (the one inside the android-win-tools folder) and when the black prompt screen comes up, type in Linux- sudo ./fastboot yadda?
Btw, I am on Windows computer, not Linux, so is the command prompt Linux- sudo ./fastboot yadda correct?
Also, if I want to bluetooth the su-2.3.6.1-ef-signed.zip to the phone, will it go directly to the SD root location? If not, when I do clockworkmod recovery and "install zip from sdcard", will it able to locate the file?
Click to expand...
Click to collapse
No, follow step 6 you use command line like this: "fastboot flash recovery C:\recovery.img". After you choose "install zip from sdcard" you have to choose the location where you put the file you want to install.

coy1987 said:
No, follow step 6 you use command line like this: "fastboot flash recovery C:\recovery.img". After you choose "install zip from sdcard" you have to choose the location where you put the file you want to install.
Click to expand...
Click to collapse
So this is exactly how it should be typed in the command prompt?
fastboot flash recovery C:\recovery.img
Are the rest of other steps correct?

I am still getting stuck at the Clockworkmod installation part, without this I cannot get to the root step.
I extracted the android-win-tools.zip, which contains the following files:
adb
AdbWinApi.dll
AdbWinUsbApi.dll
android-info
fastboot
and then extracted the cwm-vivow-4.0.0.4-recovery.img.zip, contains the following:
recovery.img
then I moved all the above 6 files directly to the C: directory. After that went into cmd and typed the prompt exactly like following:
fastboot flash recovery C:\recovery.img
Did I miss anything? Because after typing that line and hit return it came out nothing. Is that prompt correct?

Why not root with superoneclick -> download clockworkmod from market and install recovery from app? Work perfectly for me...
Sent from my HTC Incredible S

adaca said:
Why not root with superoneclick -> download clockworkmod from market and install recovery from app? Work perfectly for me...
Sent from my HTC Incredible S
Click to expand...
Click to collapse
clockworkmod from market, is it aka ROM Manager?
This app won't work because it requires a ROOT phone, which is what I am trying to do.

Yes, and before use superoneclick.
Sent from my HTC Incredible S

adaca said:
Yes, and before use superoneclick.
Sent from my HTC Incredible S
Click to expand...
Click to collapse
How did you get it from market, is it not up currently

Superoneclick is not from market, use google. Its for rooting.
Sent from my HTC Incredible S

You can also try Gingerbreak if you can't get SuperOneClick to work (again you'll have to search for this as it's not in the market).

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just installed SuperOneClick and clicked Root, it said the phone is rooted successfully. Then clicked on the "allow non market apps" and the result said non-market apps enabled.
But then I went to market and installed a screen cap app (one needs root), launched the app and it said Root required - Your phone does not appear to be rooted or has not been given root privileges.
Did the SuperOneClick really root it?

doctorsax said:
You can also try Gingerbreak if you can't get SuperOneClick to work (again you'll have to search for this as it's not in the market).
Click to expand...
Click to collapse
Does Gingerbreak work with 2.2?

Flash 4.3 WITHOUT losing losing data

READ THE WARNING
READ THE ENTIRE POST
DETAILED INSTRUCTIONS AFTER FILE
I am not responsible for bricked devices, firings due to the alarm not going of, thermonuclear war caused by a missed phone call or anything that goes wrong because of this. Try at your own risk (it'll work if you do it right)
Click to expand...
Click to collapse
I just finished flashing the 4.3 Factory images without losing user data.
I was previously running 4.2.2 Stock unrooted, with an unlocked bootloader.
You can do this simply by taking the .sh or .bat file they provide and removing the
Code:
-w
flag from the
Code:
fastboot update
command
This is my modified flash-all.sh for a mac:
Code:
#!/bin/sh
# Copyright 2012 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
fastboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img
fastboot reboot-bootloader
sleep 5
fastboot update image-occam-jwr66v.zip
Prerequisites:
1. Download the file for flashing from here.
2. Make sure your bootloader is unlocked. If it is not, you will have to unlock it which WILL WIPE YOUR DEVICE. Wait for the OTA or make a backup somewhere if you like your data. If you want to unlock the bootloader use:
Code:
fastboot oem unlock
Detailed steps:
1. Extract the downloaded tgz. You should have the following files: bootloader-mako-makoz20i.img, flash-all.bat, flash-all.sh, flash-base.sh, image-occam-jwr66v.zip and radio-mako-m9615a-cefwmazm-2.0.1700.84.img.
2. Depending on your platform open either the flash-all.bat (Windows) or the flash-all.sh (UNIX/Linux/Mac) file in a text editor, and remove the -w flag from the last line.
3. Open a terminal, connect your device, enable USB Debugging and then:
Code:
adb reboot bootloader
sh flash-all.sh
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WARNING: This will probably not work if you're running custom recoveries and/or custom ROMs. Having a rooted stock ROM should not be a problem, though you will almost definitely lose root

Is the headphone output fixed? Does it sound louder than before?

vickpick said:
Is the headphone output fixed? Does it sound louder than before?
Click to expand...
Click to collapse
There doesn't seem to be any difference to me, but I have fairly crappy headphones.

Raghav Sood said:
There doesn't seem to be any difference to me, but I have fairly crappy headphones.
Click to expand...
Click to collapse
Okay, just making sure, lol. I have the same experience and I was just wondering if I screwed up something while flashing. Thanks!

Raghav Sood said:
I just finished flashing the 4.3 Factory images without losing user data.
I was previously running 4.2.2 Stock unrooted, with an unlocked bootloader.
You can do this simply by taking the .sh or .bat file they provide and removing the
Code:
-w
flag from the
Code:
fastboot update
command
WARNING: This will probably not work if you're running custom recoveries and/or custom ROMs. Having a rooted stock ROM should not be a problem, though you will almost definitely lose root
Click to expand...
Click to collapse
I am sorry for the noob question, but I keep getting an "installation aborted" message when trying to flash the factory image. It's a .tgz file and in the past, i've only flashed .zip's. How do I flash that file?
Thanks

Please make a tutorial more specific

Triune said:
I am sorry for the noob question, but I keep getting an "installation aborted" message when trying to flash the factory image. It's a .tgz file and in the past, i've only flashed .zip's. How do I flash that file?
Thanks
Click to expand...
Click to collapse
You'll have to ensure a couple of things:
Extract the tgz. You'll end up with a bunch of img, sh, zip and bat files. Depending on whether you're on Windows or Mac or Linux, you're going to want to run the flash-all.sh or flash-all.bat file. DO NOT RUN IT RIGHT AWAY. First edit it as shown in the Opening Post.
Also make sure that fastboot is in your PATH variable (you'll get an error saying fastboot is not a command if it isn't)

javier13javier said:
Please make a tutorial more specific
Click to expand...
Click to collapse
Editing the OP with more detailed instructions now

Triune said:
I am sorry for the noob question, but I keep getting an "installation aborted" message when trying to flash the factory image. It's a .tgz file and in the past, i've only flashed .zip's. How do I flash that file?
Thanks
Click to expand...
Click to collapse
After unzipping with 7zip for example, you should have available
image-occam-jwr66v.zip
and other files like bootloader-mako-makoz20i.img and radio-mako-m9615a-cefwmazm-2.0.1700.84.img

Raghav Sood said:
You'll have to ensure a couple of things:
Extract the tgz. You'll end up with a bunch of img, sh, zip and bat files. Depending on whether you're on Windows or Mac or Linux, you're going to want to run the flash-all.sh or flash-all.bat file. DO NOT RUN IT RIGHT AWAY. First edit it as shown in the Opening Post.
Also make sure that fastboot is in your PATH variable (you'll get an error saying fastboot is not a command if it isn't)
Click to expand...
Click to collapse
What do you exactly mean with make fastboot variable? I keep getting the fastboot error.

Infinite104 said:
What do you exactly mean with make fastboot variable? I keep getting the fastboot error.
Click to expand...
Click to collapse
fastboot is part of the developer tools, and Google assumes you have it in your PATH. The Cyanogen Wiki has a great page on how to set that up here

RASTAVIPER said:
After unzipping with 7zip for example, you should have available
image-occam-jwr66v.zip
and other files like bootloader-mako-makoz20i.img and radio-mako-m9615a-cefwmazm-2.0.1700.84.img
Click to expand...
Click to collapse
I've extracted, but what i'm not understanding up to this point is how to flash it. Do you re-zip it then flash it through the stock recovery?

Just a heads up, you have to unzip twice before u get to flash.bat
TGZ, then TAR.
---------- Post added at 09:38 PM ---------- Previous post was at 09:37 PM ----------
Triune said:
I've extracted, but what i'm not understanding up to this point is how to flash it. Do you re-zip it then flash it through the stock recovery?
Click to expand...
Click to collapse
no, you copy all the files into the fastboot folder (iincluding modified bat or sh), then run the bat or sh
Oh and phone should be in download mode and connected.
you don't use the recovery, just press your power down and power and connect when the black screen comes up.

vickpick said:
Just a heads up, you have to unzip twice before u get to flash.bat
TGZ, then TAR.
---------- Post added at 09:38 PM ---------- Previous post was at 09:37 PM ----------
no, you copy all the files into the fastboot folder (iincluding modified bat or sh), then run the bat or sh
Oh and phone should be in download mode and connected.
you don't use the recovery, just press your power down and power and connect when the black screen comes up.
Click to expand...
Click to collapse
That's the difference, i'm in a mac. I don't have a fastboot folder. I wish Google would just release flashable zips. Smh

Triune said:
I've extracted, but what i'm not understanding up to this point is how to flash it. Do you re-zip it then flash it through the stock recovery?
Click to expand...
Click to collapse
Check this:
- YOU MUST HAVE ADB & USB Driver for the device (I used the SDK file from google and PDAnet)
- ENABLE USB Debugging via Developer settings (press the build button 7 times to activate it the "settings --> about phone --> Build Number"
- Launch command prompt (start --> run --> "cmd")
- type in command prompt "cd directory where you have the adb & fast boot" for example here is mine "cd C:\Users\sdk\platform-tools"
- Type in the command prompt each step one at a time
"fastboot flash bootloader bootloader-mako-makoz20i.img"
"fastboot reboot-bootloader"
"fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img"
"fastboot reboot-bootloader"
"fastboot update image-occam-jwr66v.zip"

Will this work if we're on a stock 4.2.2 ROM but with LTE changes (older radio, edited build.prop and soc file?)

Triune said:
That's the difference, i'm in a mac. I don't have a fastboot folder. I wish Google would just release flashable zips. Smh
Click to expand...
Click to collapse
On a mac you should also have fastboot-mac in addition to fastboot.
Replace fastboot in the description with fastboot-mac and you shouldn't get any error messages

bioyuki said:
Will this work if we're on a stock 4.2.2 ROM but with LTE changes (older radio, edited build.prop and soc file?)
Click to expand...
Click to collapse
Just tested, it works fine.

RASTAVIPER said:
Check this:
- YOU MUST HAVE ADB & USB Driver for the device (I used the SDK file from google and PDAnet)
- ENABLE USB Debugging via Developer settings (press the build button 7 times to activate it the "settings --> about phone --> Build Number"
- Launch command prompt (start --> run --> "cmd")
- type in command prompt "cd directory where you have the adb & fast boot" for example here is mine "cd C:\Users\sdk\platform-tools"
- Type in the command prompt each step one at a time
"fastboot flash bootloader bootloader-mako-makoz20i.img"
"fastboot reboot-bootloader"
"fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img"
"fastboot reboot-bootloader"
"fastboot update image-occam-jwr66v.zip"
Click to expand...
Click to collapse
Thats the same of deleting the -w and run the .bat on windows.
EDIT: Ok guys, this will work for windows (you have to install adb on your computer and have bootloader unlocked)
1- Remove the -w from the bat (with any editor), that came with the zip.
2- On cmd put adb reboot bootloader
3- Run the modified bat that dont have the -w, just wait and you will have 4.3.
Proof:

For me I had a custom recovery installed and custom rom, so at first I didn't wipe data. It did not boot. So I flashed twrp, and wiped data, not personal data though, and it booted.

[Q] Soft Brick

My phone is soft bricked, I tried flashing to the stock rom using odin but the phone fails to boot up once the flash has finished it just stays on the 'Samsung Galaxy S III GT-I9305 screen, I can get the phone into download mode but not recovery mode, could anybody please help?

You have two phones ???
see your identical post .

Have you tried after flashing in odin to boot to stock recovery and do a factory reset?

trippy202 said:
Have you tried after flashing in odin to boot to stock recovery and do a factory reset?
Click to expand...
Click to collapse
Yep, nothing happens, just stays on the boot up screen

bump

bluereus said:
bump
Click to expand...
Click to collapse
Do a factory reset then re flash a stock rom

Raistlin1158 said:
Do a factory reset then re flash a stock rom
Click to expand...
Click to collapse
I can't do a factory reset though can I? All I can do is enter download mode

Ok, inside the zip of the rom you flashed, there is a file called boot.
On your desktop, drag out the boot.img.
It's an easy way to get fastboot and adb access without having to download android sdk. Extract the folder to your desktop. put the boot.img inside the folder called ADB-Fastboot.
Now open up cmd. Then change the directory of the prompt so that it aims to the ADB-Fastboot folder. Then type "adb reboot bootloader" so your phones goes into bootloader.
It should boot into a mode called fastboot. On your phone's screen, you should see "Fastboot usb" in red.
Then type "fastboot flash boot boot.img" Then once it finishes flashing, you can either reboot to see if it gets passed the screen or reflash the rom and then try rebooting again.

Raistlin1158 said:
Ok, inside the zip of the rom you flashed, there is a file called boot.
On your desktop, drag out the boot.img.
It's an easy way to get fastboot and adb access without having to download android sdk. Extract the folder to your desktop. put the boot.img inside the folder called ADB-Fastboot.
Now open up cmd. Then change the directory of the prompt so that it aims to the ADB-Fastboot folder. Then type "adb reboot bootloader" so your phones goes into bootloader.
It should boot into a mode called fastboot. On your phone's screen, you should see "Fastboot usb" in red.
Then type "fastboot flash boot boot.img" Then once it finishes flashing, you can either reboot to see if it gets passed the screen or reflash the rom and then try rebooting again.
Click to expand...
Click to collapse
This is all I have in the zip
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

If anyone can sort this out for me I'll happily throw you a fiver on paypal

bluereus said:
If anyone can sort this out for me I'll happily throw you a fiver on paypal
Click to expand...
Click to collapse
Unzip the zip then unzip again to split up the rom, You don't need to pay as we are all here to help each other :good:

Raistlin1158 said:
Unzip the zip then unzip again to split up the rom, You don't need to pay as we are all here to help each other :good:
Click to expand...
Click to collapse
I've got this far, where is the ADB-Fastboot folder? (sorry)
And I'd like to as a thank you, it'd be £25+ to send it off for repairs

Any chance you could do this for me on teamviewer or something tomorrow? I'm really out of my depth here (like you couldn't tell)

bumping

come on guys

Put the boot.img inside the folder called ADB-Fastboot.
Now open up cmd.
Then change the directory of the prompt so that it aims to the ADB-Fastboot folder.
Then type "adb reboot bootloader" so your phones goes into bootloader.
It should boot into a mode called fastboot.
On your phone's screen, you should see "Fastboot usb" in red.
Then type "fastboot flash boot boot.img" Then once it finishes flashing, you can either reboot to see if it gets passed the screen or reflash the rom and then try rebooting again.

Raistlin1158 said:
Put the boot.img inside the folder called ADB-Fastboot.
Now open up cmd.
Then change the directory of the prompt so that it aims to the ADB-Fastboot folder.
Then type "adb reboot bootloader" so your phones goes into bootloader.
It should boot into a mode called fastboot.
On your phone's screen, you should see "Fastboot usb" in red.
Then type "fastboot flash boot boot.img" Then once it finishes flashing, you can either reboot to see if it gets passed the screen or reflash the rom and then try rebooting again.
Click to expand...
Click to collapse
What is the ADB-Fastboot folder?

bluereus said:
What is the ADB-Fastboot folder?
Click to expand...
Click to collapse
Create a folder called ADB-Fastboot
Put the boot.img inside the folder called ADB-Fastboot. then follow the instructions... :good:

Raistlin1158 said:
Create a folder called ADB-Fastboot
Put the boot.img inside the folder called ADB-Fastboot. then follow the instructions... :good:
Click to expand...
Click to collapse
By 'change the directory of the prompt what exactly do you mean?

In CMD you have to open the folder you created ie ADB-Fastboot
So type cd ADB-Fastboot , you are changing the directory to the one you created.
Then follow the other instructions.
Without being rude you do not seem to have sufficient knowledge to dabble with you phone....
Once you get it going I would not play with it till you have read a bit more and watched a few videos to bulk up the level of competency,

[Q] need help to get my phone working again

hey guys.
My M7 is stuck in the bootloop. I tried to install a new rom like 2 years ago and it didnt worked out, but i already had a new phone, so i didnt care too much. now id like to reactivate my old m7 but dont know how.
here is a link to a picture of my fastboot
imgur.com/tzQe7Xi
Im running Windows 10 on my computer
thanks in advance

zuppiger said:
hey guys.
My M7 is stuck in the bootloop. I tried to install a new rom like 2 years ago and it didnt worked out, but i already had a new phone, so i didnt care too much. now id like to reactivate my old m7 but dont know how.
here is a link to a picture of my fastboot
imgur.com/tzQe7Xi
Im running Windows 10 on my computer
thanks in advance
Click to expand...
Click to collapse
Boot into fastboot mode and install the latest version of TWRP, which is 2.8.7.0. You can download it from the TWRP official website.
Code:
fastboot flash recovery recovery-file-name.img
Boot into recovery and connect your phone to the PC.
Download any ROM from the forum, transfer it to the phone and flash it. Don`t since we don`t know anything about your previous ROM wipe cache, dalvik, data and system before flashing your chosen ROM.
Since you`re S-On, extract the boot.img file from the ROM zip and flash it manually in fastboot mode
Code:
fastboot flash boot boot.img
Reboot phone and enjoy.

proone said:
Boot into fastboot mode and install the latest version of TWRP, which is 2.8.7.0. You can download it from the TWRP official website.
Code:
fastboot flash recovery recovery-file-name.img
Boot into recovery and connect your phone to the PC.
Download any ROM from the forum, transfer it to the phone and flash it. Don`t since we don`t know anything about your previous ROM wipe cache, dalvik, data and system before flashing your chosen ROM.
Since you`re S-On, extract the boot.img file from the ROM zip and flash it manually in fastboot mode
Code:
fastboot flash boot boot.img
Reboot phone and enjoy.
Click to expand...
Click to collapse
No need to extract anything. S-on doesn't matter for kernel flashing on this phone. So, flash ROM.zip and enjoy

proone said:
Boot into fastboot mode and install the latest version of TWRP, which is 2.8.7.0. You can download it from the TWRP official website.
Code:
fastboot flash recovery recovery-file-name.img
Click to expand...
Click to collapse
Code:
fastboot flash recovery recovery-file-name.img
fastboot erase cache
fastboot reboot-bootloader
Always erase the cache and reboot the bootloader after flashing a recovery to avoid problems booting the recovery.
Download any ROM from the forum
Click to expand...
Click to collapse
"any ROM" from the forum won't work on his phone. For example, his actual firmware is way to old to run roms based on Sense + Lollipop. With this firmware version (2.24.401.8), he is limited to JellyBean or Kitkat Roms.
Since you`re S-On, extract the boot.img file from the ROM zip and flash it manually in fastboot mode
Code:
fastboot flash boot boot.img
Reboot phone and enjoy.
Click to expand...
Click to collapse
Won't hurt but not needed on the M7 (unlike some other HTC phones). The kernel partition isn't secured and is flashed with the rom from twrp.
@zuppiger
If you want the phone back to stock and be able to intall ota updates (or if you want to install a custom lollipop + sense rom), flash this rom using twrp recovery. Select "yes" for stock recovery and stock radio, select "no" to root. then reboot the phone to the OS, install all the ota updates (a lot) until your version is 7.19.401.30. Then you can use the phone like this or you'll be ready to flash a lollipop custom rom. Otherwise you can go like suggested above but with older (JB or KitKat) Sense rom or any CM/AOSP roms.

Thanks guys.
but i think i might need some more help.
i downloaded the sdk manager to install TWRP, but when i try to write "adb reboot bootloader" it says "is not recognized as an internal or external command, operable program or batch file" (not entirly sure if this is the correct translation, in german it says the command is either wrong or could not be found)
i think it could be because of some driver issues.
any advice??

zuppiger said:
Thanks guys.
but i think i might need some more help.
i downloaded the sdk manager to install TWRP, but when i try to write "adb reboot bootloader" it says "is not recognized as an internal or external command, operable program or batch file" (not entirly sure if this is the correct translation, in german it says the command is either wrong or could not be found)
i think it could be because of some driver issues.
any advice??
Click to expand...
Click to collapse
Download the android sdk tools:
https://developer.android.com/sdk/index.html#Other
Make sure you have the latest htc drivers installed:
http://www.mediafire.com/download/2lyl151pt5pah2v
Make sure you don't have HTC Sync installed on your computer, if yes, uninstall it since it will interfere with fastboot/adb commands
To use adb or fastboot commands, open a command window from the same folder where adb.exe and fastboot.exe are located on your computer (C::\Programs\Android SDK Tools\platform-tools). To start a command window from this folder, hold your left "shift" key and right click a blank space in that folder, then in the contextual menu, select "open a command window here".
Don't forget that adb commands can only works when the phone is booted in the OS with "USB debugging" turned on from the developer option menu or from a custom recovery. Fastboot commands only works from the bootloader (in the fastboot menu).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

alray said:
Download the android sdk tools:
https://developer.android.com/sdk/index.html#Other
Make sure you have the latest htc drivers installed:
http://www.mediafire.com/download/2lyl151pt5pah2v
Make sure you don't have HTC Sync installed on your computer, if yes, uninstall it since it will interfere with fastboot/adb commands
To use adb or fastboot commands, open a command window from the same folder where adb.exe and fastboot.exe are located on your computer (C::\Programs\Android SDK Tools\platform-tools). To start a command window from this folder, hold your left "shift" key and right click a blank space in that folder, then in the contextual menu, select "open a command window here".
Don't forget that adb commands can only when the phone is booted in the OS with "USB debugging" turned on from the developer option menu or from a custom recovery. Fastboot commands only works from the bootloader (in the fastboot menu).
Click to expand...
Click to collapse
Thanks. I installed everything like explained.
It worked better this time, but now I get "waiting for device".
On the phone itself it says "FASTBOOT USB"

zuppiger said:
but now I get "waiting for device".
Click to expand...
Click to collapse
When using what command?

alray said:
When using what command?
Click to expand...
Click to collapse
"fastboot flash recovery c:\twrp.img"

zuppiger said:
"fastboot flash recovery c:\twrp.img"
Click to expand...
Click to collapse
what is the output of "fastboot devices" ?

alray said:
what is the output of "fastboot devices" ?
Click to expand...
Click to collapse
Nothing.
I made the command again in the platform-tools folder

Anyone some more help? :good:

zuppiger said:
Anyone some more help? :good:
Click to expand...
Click to collapse
Well without any connectivity to the phone there is nothing we can do unfortunately. Might worth to try on another computer. Otherwise if you are 100% sure that the problem isn't the usb cable, the drivers or the computer then the phone usb port might be broken. This can be replaced (probably the "easiest" part to replace on that phone), you'll need to open the cover and replace that small usb/front mic board.
But the fact that your phone says FASTBOOT USB when in bootloader makes me believe its more a driver/computer problem since it would only says FASTBOOT if there were no connection detected...

thanks a lot for your help. I don't think I will get it working again anytime soon.
But i will look for a way

Trying to flash twrp recovery...getting error "target reported max download..."

Trying to flash twrp recovery...getting error "target reported max download..."
I'm trying to install twrp recovery but getting the error message: Target reported max download size of 536870912 bytes; error: cannot load 'twrp.img': unknown error
The phone was previously unlocked and rooted on lollipop....had problems and restored...took OTA update to Marshmallow 6.0.1
Any ideas? Please and thanks!

DoritoKing said:
I'm trying to install twrp recovery but getting the error message: Target reported max download size of 536870912 bytes; error: cannot load 'twrp.img': unknown error
The phone was previously unlocked and rooted on lollipop....had problems and restored...took OTA update to Marshmallow 6.0.1
Any ideas? Please and thanks!
Click to expand...
Click to collapse
1) how are you trying to install TWRP?
2) You are using the most recent version from our official TWRP maintainer?
January 12, 2017
twrp-3.0.3-0-Mod_01-quark.img
https://www.androidfilehost.com/?fid=745425885120699982
3) And you are showing known file extensions in Windows? Do you know what that means?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you have a jpg or pdf, and you see a file name -- do you also ALWAYS, ALWAYS see the extension like jpg or pdf? Default in Windows -- for idiotic reasons -- is to "hide known file extensions".
Make sure that box is UNchecked in your Windows settings. Because otherwise you are re-naming TWRP as TWRP.img(.img). You do NOT have to type the .img part, it's ALREADY an .img file.
That may or may not be your issue, but it messed up a lot of people in the past. ADB couldn't find TWRP.img because they had unknowingly called it TWRP.IMG.img -- because they couldn't see the file extension and thought they needed to add it to the file name.

1. I had the previous version 3.0.2-0...will try your link.
2. I unchecked the extension box...
will try again and let you know...thank you!

Just tried with the changes....still getting same error messages.

DoritoKing said:
1. I had the previous version 3.0.2-0...will try your link.
2. I unchecked the extension box...
will try again and let you know...thank you!
Click to expand...
Click to collapse
When you unchecked the extension box, what is now the visible name of your TWRP file? Does it say TWRP.img.img or just TWRP.img? Besides unchecking the extension box, you also need to make sure you are typing the actual name of the file. IF you had typed "TWRP.img"(.img) before, you now need to re-name it just "TWRP".img.
If you confirm that's not the issue, then we'll get @bhb27 involved over in the Quark TWRP thread.

I changed the filename to twrp and I'm using the command: fastboot flash recovery twrp.img and I've tried every other combination of twrp.img.img, twrp, etc just to make sure I wasn't missing something!
My goal is to be able to flash a new build.prop to allow for tethering...if there is a way to do that without installing twrp, that would be great

DoritoKing said:
I changed the filename to twrp and I'm using the command: fastboot flash recovery twrp.img and I've tried every other combination of twrp.img.img, twrp, etc just to make sure I wasn't missing something!
My goal is to be able to flash a new build.prop to allow for tethering...if there is a way to do that without installing twrp, that would be great
Click to expand...
Click to collapse
OK, just as a test, do this. Forget the name TWRP. That's just a convenience. Call it something else. Rename it box or chair. I'm not joking. Then, in your PC, what file name do you see? IF you renamed it "box", you should see box.img. You do NOT type .img. It's just the extension that should already be there!
then flash: fastboot flash recovery box.img
I'm suggesting this because somehow, somewhere it seems your file name is messed up?
Also you have done all this too? Permissions and stuff?
Enable USB debugging on your device:
Open Settings on your device.
Go to About phone and tap seven times on Build number, this will enable Developer options.
Now go back to Settings and you’ll see Developer options there, open it.
Tick the USB Debugging checkbox.
Connect your device to the PC. And type the following into the command window we opened to boot your device into bootloader/fastboot mode:
adb reboot bootloader
└ If you get a permission dialogue on your device to “Allow USB debugging”, tap OK.
Click to expand...
Click to collapse
Maybe revoke those permissions and re-enable them?

Renamed it "dummy"....the name I see on my file list is "dummy"......Still getting same error message. I tried recovery dummy.img and recovery dummy....still same error.
adb reboot bootloader works....cant flash the recovery image though. Do I need to do something else on the phone side prior to flashing the image? It has the android laying on its back with the "Start" option showing on top...

DoritoKing said:
Renamed it "dummy"....the name I see on my file list is "dummy"......Still getting same error message. I tried recovery dummy.img and recovery dummy....still same error.
adb reboot bootloader works....cant flash the recovery image though. Do I need to do something else on the phone side prior to flashing the image? It has the android laying on its back with the "Start" option showing on top...
Click to expand...
Click to collapse
I was just suggesting you revoke the USB permissions and re-enable them in Developer Settings, just to make sure. That's the only thing I'm aware of you need to do on the phone side... If anyone knows something different, feel free to correct me!
@bhb27 is our TWRP maintainer for our official TWRP. So, I'm mentioning him here so he'll see this issue. Maybe he'll have some ideas?
Also, you you can post this issue over in the Quark TWRP thread. You can put a link to this thread in your post, so people can see what all we've tried.
[RECOVERY][OFFICIAL TWRP 3.0.2-0][For all Quark][Moto Maxx/Turbo and Droid Turbo]
https://forum.xda-developers.com/mo...recovery-twrp-2-8-7-0-touch-recovery-t3180308

I need print screen of what is going on in the terminal when the problem is manifested...
need a print screen of the folder were adb, fastboot and the recovery files are.
need a print screen of the content of properties of the twrp.img

bhb27 said:
I need print screen of what is going on in the terminal when the problem is manifested...
need a print screen of the folder were adb, fastboot and the recovery files are.
need a print screen of the content of properties of the twrp.img
Click to expand...
Click to collapse
Here are the screenshots...if this isn't what you were looking for, just let me know.

DoritoKing said:
Here are the screenshots...if this isn't what you were looking for, just let me know.
Click to expand...
Click to collapse
Yes it is.
can you try this fastboot?
https://www.androidfilehost.com/?fid=24052804347845784
add a m to fastboot command
Code:
mfastboot flash recovery twrp
if it fails give
Code:
mfastboot devices
and print the screen...
:good:

bhb27 said:
Yes it is.
can you try this fastboot?
https://www.androidfilehost.com/?fid=24052804347845784
add a m to fastboot command
Code:
mfastboot flash recovery twrp
if it fails give
Code:
mfastboot devices
and print the screen...
:good:
Click to expand...
Click to collapse
Didn't recognize that command...here is the screenshot

You can't just flash a file called twrp and that's it. It needs to be twrp.img. Also, in order for mfastboot (or any other .exe file) to work in a command prompt, you need to navigate to the folder that it is present in. Is mfastboot.exe located in C:\Documents and Settings\Jason? If not, that's why it isn't found.

DoritoKing said:
Didn't recognize that command...here is the screenshot
Click to expand...
Click to collapse
did you download the file I share?

TheSt33v said:
You can't just flash a file called twrp and that's it. It needs to be twrp.img. Also, in order for mfastboot (or any other .exe file) to work in a command prompt, you need to navigate to the folder that it is present in. Is mfastboot.exe located in C:\Documents and Settings\Jason? If not, that's why it isn't found.
Click to expand...
Click to collapse
I didn't know how to open my command prompt in a particular folder, but I figured that out now. I was able to try again and run the original fastboot and it worked! I've got TWRP on my phone!!
I've attached a screenshot. I was told that when I type the commands, to not include the .img for the TWRP file.....so I just typed fastboot flash recovery twrp and it worked.
Thank you everyone for all your help. I'm a newbie, so I appreciate everyone being patient when I don't know how to do certain things correctly.

TheSt33v said:
You can't just flash a file called twrp and that's it. It needs to be twrp.img. Also, in order for mfastboot (or any other .exe file) to work in a command prompt, you need to navigate to the folder that it is present in. Is mfastboot.exe located in C:\Documents and Settings\Jason? If not, that's why it isn't found.
Click to expand...
Click to collapse
Right. His screenshot is showing other extensions, like .exe, .txt, .dll -- so his TWRP extension should be .img. It's missing.
What I cautioned him about was double naming the extension -- TWRP.img.img, which can accidentally be done if you have your Windows settings to hide known file extensions. Since his file extensions are no longer hidden, his TWRP file should say TWRP.img.
But naming it TWRP is just a convenience instead of using the regular file name like "twrp-3.0.3-0-Mod_01-quark.img". It's easier to type TWRP.img in the Windows command box than that long official file name. You could easily also re-name it "chair.img" or "box.img" as long as you were re-naming the correct file. I even suggested he do that because he seemed hung up over the TWRP name.
At this point, he probably needs to also re-download the TWRP file and re-name it. Now that he can see file extensions, it should automatically have the .img extension.

Me again...the guy who probably shouldn't be messing with his phone
I got TWRP installed. Tried flashing a zip for tethering...upon reboot it was getting stuck at bootloader warning screen. Eventually tried a wipe through TWRP (data, cache, and dalvik) and a factory reset through the phone menu, but still keeps getting stuck at bootloader. I can still get into TWRP, but not sure where to go from here
Do I need to do the wipe differently? Anyway to get past the bootloader screen?

DoritoKing said:
Me again...the guy who probably shouldn't be messing with his phone
I got TWRP installed. Tried flashing a zip for tethering...upon reboot it was getting stuck at bootloader warning screen. Eventually tried a wipe through TWRP (data, cache, and dalvik) and a factory reset through the phone menu, but still keeps getting stuck at bootloader. I can still get into TWRP, but not sure where to go from here
Do I need to do the wipe differently? Anyway to get past the bootloader screen?
Click to expand...
Click to collapse
I'm going to hazard a guess here that you also flashed SuperSu in TWRP and you are running the new Marshmallow update. (Yeah, confirmed, I just checked your first post. You took Marshmallow update.) In which case, it sounds like you flashed the wrong version of SuperSu. You have to flash an older version for initial root or your phone will stick at the bootloader warning screen. This has been discussed in all the Marshmallow threads.
What version SuperSu are you using? If on stock Marshmallow or stock-based Marshmallow ROM, the one required is BETA-SuperSU-v2.62-3-20151211162651). You can boot into TWRP, plug your phone into a PC and drag it over like a flash drive. It will show up in the root folder. Flash it, wipe all caches, reboot.
I've attached it to this post.
AFTER initial root, and after you successfully boot, then you can update to newest version of SuperSu. You just need it for initial root and to successfully boot the first time.
PREDICTION: Your next question will be how to get rid of the unlocked bootloader screen. Because you will see it every time you reboot your phone. When you do, here's your answer. But first, you need to flash the correct SuperSu to get past the bootloader screen.

DoritoKing said:
I didn't know how to open my command prompt in a particular folder, but I figured that out now. I was able to try again and run the original fastboot and it worked! I've got TWRP on my phone!!
I've attached a screenshot. I was told that when I type the commands, to not include the .img for the TWRP file.....so I just typed fastboot flash recovery twrp and it worked.
Thank you everyone for all your help. I'm a newbie, so I appreciate everyone being patient when I don't know how to do certain things correctly.
Click to expand...
Click to collapse
Congratulations on installing TWRP.