Database Develop

[Guide/How To] Flash Hboot's OTG

How To Flash A Different HBoot On The Go. I miss the good ol days when we could just flash an hboot on the go via the bootloader itself. Looks like this is the closest were getting for now.
Requirements:
S-Off
Terminal Emulator (Get it free from Google Play)
Commom ADB/Fastboot experience to understand this...
On the device, open Terminal Emulator
Step 1:
Run:
su
Step 2:
Run:
cd sdcard
Step 3:
Run:
dd if=/sdcard/LOCATIONOFHBOOT/HBOOT.img of=/dev/block/mmcblk0p12
Notes:
Replace "LOCATIONOFHBOOT" with the actual location it is stored on. For example, the 3 Hboots I have are stored on /sdcard/System/HBoot/
Replace "HBOOT.img" with the actual name of the hboot file. Example: enghboot.nbo or stock_hboot.img
Final example for my device would be: dd if=/sdcard/System/Hboot/hboot.img of=/dev/block/mmcblk0p12
KEEP IN MIND, ONCE YOU FLASH AND BOOT INTO THE ENG HBOOT, YOU WILL NOT BE ABLE TO BOOT BACK UP UNTIL FLASHING ANOTHER HBOOT VIA FASTBOOT.
Sent Via My HTC One, On The Now Network By Sprint!

Or you could just have an hboot.zip (hboot.nb0 and android-info.txt) and flash it from the hboot screen. ._.

Have you done it? Doesn't seem to work that way anymore unless I missed something...
Sent Via My HTC One, On The Now Network By Sprint!

Seems that every way I've seen to flash hboot involves adb. Does either mentioned method here actually work on a One?
Sent from my HTCONE using xda app-developers app

Scrufdog said:
Seems that every way I've seen to flash hboot involves adb. Does either mentioned method here actually work on a One?
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Lol I wouldn't post it if it didn't work. xD
Sent Via My HTC One, On The Now Network By Sprint!

For it to work you need to use a USB OTG cable.

@Indirect no. Lol I didn't list that anywhere in O.P. -_- I simply named the thread OTG for on the go...
Sent Via My HTC One, On The Now Network By Sprint!

Rydah805 said:
@Indirect no. Lol I didn't list that anywhere in O.P. -_- I simply named the thread OTG for on the go...
Sent Via My HTC One, On The Now Network By Sprint!
Click to expand...
Click to collapse
I was saying to flash through hboot using PN72IMG.zip's

Indirect said:
I was saying to flash through hboot using PN72IMG.zip's
Click to expand...
Click to collapse
This is what I want to do, but can't get it to work.
To be clear, on my old Evo 4G LTE, I would package the hboot or recovery into a zip file with android_info.txt, put it on my SD card, and at next boot it would find it and flash it (having s-off of course).
Now with the Sprint HTC One, I connected a USB stick via an OTG cable, verified the phone can see the drive fine while running Android normally (using Solid Explorer), placed a recovery or hboot zip on the USB drive named PN72IMG.zip, and rebooted to the bootloader, but no dice.
In the past you could see the bootloader searching for a valid file on the external card, but now the bootloader doesn't seem to do that anymore, it just starts right up in the fastboot screen, even with my OTG cable and USB drive attached.
So, have you been able to do this successfully, and if so, can you post an example file with that IMG name I could try to get recognized (I don't actually need to flash it), because maybe there is something wrong with the contents of my android_info.txt file? Can anyone think of something I am missing that prevents my quest for bootloader flashing via USB OTG from happening?

PillowMetal said:
This is what I want to do, but can't get it to work.
To be clear, on my old Evo 4G LTE, I would package the hboot or recovery into a zip file with android_info.txt, put it on my SD card, and at next boot it would find it and flash it (having s-off of course).
Now with the Sprint HTC One, I connected a USB stick via an OTG cable, verified the phone can see the drive fine while running Android normally (using Solid Explorer), placed a recovery or hboot zip on the USB drive named PN72IMG.zip, and rebooted to the bootloader, but no dice.
In the past you could see the bootloader searching for a valid file on the external card, but now the bootloader doesn't seem to do that anymore, it just starts right up in the fastboot screen, even with my OTG cable and USB drive attached.
So, have you been able to do this successfully, and if so, can you post an example file with that IMG name I could try to get recognized (I don't actually need to flash it), because maybe there is something wrong with the contents of my android_info.txt file? Can anyone think of something I am missing that prevents my quest for bootloader flashing via USB OTG from happening?
Click to expand...
Click to collapse
I haven't been able to get that to work. Maybe @Indirect knows a trick or two.
Sent Via My HTC One, On The Now Network By Sprint!

Still trying to get flashing from the bootloader to work and tried renaming files to PN72IMG.zip, PN07IMG.zip, and even PN072IMG,zip to no avail
Something I noticed though is that while in Android where my OTG connection works fine, a little light illuminates on my USB drive to show that I am getting power/data. However, when I boot into the bootloader that light is not on, indicating to me that no power/data is being supplied to the port for the USB. So no attempt is even being made to try and read it.
So my question stands if anybody has ever gotten this to work? Maybe it depends on the model of USB drive being used?

HTC One Dev edition root question

Hey guys, I have been looking through the forums and have not found an answer to my confusion. I have the dev edition in the US, and I am not sure what steps to follow to root and unlock the bootloader. I don't know the difference between unlocked and s-off, so I am not sure where to start.
I have rooted a number of phones before, but they were always carrier versions so I knew exactly where to start from. Any direction would be great, and I apologize if this has been asked 50 times before.
Sent from my HTC One using Tapatalk 2

Mindstar1 said:
Hey guys, I have been looking through the forums and have not found an answer to my confusion. I have the dev edition in the US, and I am not sure what steps to follow to root and unlock the bootloader. I don't know the difference between unlocked and s-off, so I am not sure where to start.
I have rooted a number of phones before, but they were always carrier versions so I knew exactly where to start from. Any direction would be great, and I apologize if this has been asked 50 times before.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
What version of hboot do you have? If you have 1.44.0000 you can do S-Off and Unlock the bootloader using Revone
If you have 1.54.0000 you can't do S-Off

Dev edition comes with an unlocked bootloader, all you would need to do is flash a custom recovery,twrp will root the device for you,simplest way if JUST looking for root

Dev edition comes with an unlocked bootloader, all you would need to do is flash a custom recovery,twrp will root the device for you,simplest way if JUST looking for root
Click to expand...
Click to collapse
Pardon my ignorance, but what would I gain by looking for more than root?
Sent from my HTC One using Tapatalk 2

What version of hboot do you have? If you have 1.44.0000 you can do S-Off and Unlock the bootloader using Revone
If you have 1.54.0000 you can't do S-Off
Click to expand...
Click to collapse
How do I check which hboot I have?
Sent from my HTC One using Tapatalk 2

At some point you will need a USB cable and a computer (with the android sdk installed on it) to make any of the changes you are contemplating, and there are commands you can run from your computer's terminal app (while the phone is connected to the computer via USB) that tell you what HBOOT you have, but for purely informational purposes, the is a non- technical way to determine your HBOOT:
- power off phone all the way (make sure "fast boot" is turned off in settings..power)
-hold down volume-down and power buttons simultaneously for several seconds until screen turns white
- HBOOT version is clearly visible from this screen. Write down every version number or other info that you see for future reference. Consider taking a photo of this screen.
-to leave this environment, use volume key to change the highlighted selection, and the power button to actually invoke it: select "fastboot" then "reboot" to reboot gracefully
Sent from my HTC One using xda app-developers app

NxNW said:
At some point you will need a USB cable and a computer (with the android sdk installed on it) to make any of the changes you are contemplating, and there are commands you can run from your computer's terminal app (while the phone is connected to the computer via USB) that tell you what HBOOT you have, but for purely informational purposes, the is a non- technical way to determine your HBOOT:
- power off phone all the way (make sure "fast boot" is turned off in settings..power)
-hold down volume-down and power buttons simultaneously for several seconds until screen turns white
- HBOOT version is clearly visible from this screen. Write down every version number or other info that you see for future reference. Consider taking a photo of this screen.
-to leave this environment, use volume key to change the highlighted selection, and the power button to actually invoke it: select "fastboot" then "reboot" to reboot gracefully
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
OK, I just did what you said and the HBOOT is 1.44.0000. So, based on what was said earlier, I am good to do the Revone option? If I do Revone, what am I missing out on compared to any other option? Thanks for the help!

Go for it. I had 1.44 and eventually got revone to work. [ there is an undocumented tip that may help you (power off the device "hard", ie hold down power button for like 15 or 20 seconds, between each step), but you'll want to discuss that and any other issues you encounter with revone in the revone thread of course. ] I cant think of any negative side effects that i have experienced. And as those with hboot 1.55 have discovered, its always good to get S-OFF while you can. You may not have the chance later. Good luck.

Well obviously your looking to flash thngs,there are many options,this is why i said if you were just looking to root the device
Mindstar1 said:
Pardon my ignorance, but what would I gain by looking for more than root?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse

Wonders_Never_Cease said:
Well obviously your looking to flash thngs,there are many options,this is why i said if you were just looking to root the device
Click to expand...
Click to collapse
Yeah, I want to flash. If all I do is root, am I still able to flash other ROMs? I can never keep straight what each of the different processes do.

NxNW said:
Go for it. I had 1.44 and eventually got revone to work. [ there is an undocumented tip that may help you (power off the device "hard", ie hold down power button for like 15 or 20 seconds, between each step), but you'll want to discuss that and any other issues you encounter with revone in the revone thread of course. ] I cant think of any negative side effects that i have experienced. And as those with hboot 1.55 have discovered, its always good to get S-OFF while you can. You may not have the chance later. Good luck.
Click to expand...
Click to collapse
Whats the deal with Revone and the HTC One tool kit here http://forum.xda-developers.com/showthread.php?t=2183942. My goal is to flash 4.2.2 roms and soon 4.3, so would I want to do both or just Revone.

Mindstar1 said:
Whats the deal with Revone and the HTC One tool kit here http://forum.xda-developers.com/showthread.php?t=2183942.
Click to expand...
Click to collapse
Here is an old article that covers some basic terminology, specifically geared toward HTC phones. Much of it applies to the HTC One (although the stuff about the difficulty flashing kernels in recovery does not pertain- we have it much easier).
http://www.pocketables.com/2012/08/...nlocked-bootloader-in-the-htc-evo-series.html
Also check out this famous post https://plus.google.com/103583939320326217147/posts/P1i8qzLfkTm
The second article clearly states you don't need S-Off to flash ROMs, but the first article also notes those who are going through the trouble of unlocking/rooting generally do S-OFF while they are at it.
As for hasoon's toolkit, I personally have avoided it. There are other ways to root.
For instance, if you install the latest version of a custom recovery such as TWRP or CWM, they actually give you a menu option to root whatever ROM is currently installed.
Check back again after you've gotten caught up on your reading.

NxNW said:
Here is an old article that covers some basic terminology, specifically geared toward HTC phones. Much of it applies to the HTC One (although the stuff about the difficulty flashing kernels in recovery does not pertain- we have it much easier).
http://www.pocketables.com/2012/08/...nlocked-bootloader-in-the-htc-evo-series.html
Also check out this famous post https://plus.google.com/103583939320326217147/posts/P1i8qzLfkTm
The second article clearly states you don't need S-Off to flash ROMs, but the first article also notes those who are going through the trouble of unlocking/rooting generally do S-OFF while they are at it.
As for hasoon's toolkit, I personally have avoided it. There are other ways to root.
For instance, if you install the latest version of a custom recovery such as TWRP or CWM, they actually give you a menu option to root whatever ROM is currently installed.
Check back again after you've gotten caught up on your reading.
Click to expand...
Click to collapse
Its funny, I came across the first article while looking for answers while I waited for your response. I never mess with radios so S-Off is not really important to me. The second article was even better and more clear so I think I know where I am now.
The last question for you is what you would suggest I use for the most trouble free rooting process. I am looking for a pretty low impact route, and you did seem to imply that it took some work to get revone working for you. The toolkit seems to be a good way to go, but it also says that it unlocks the boot, which I already have with the dev edition. Will that be a problem if the process tries to unlock an already unlocked phone?

Ok one last reading assignment, a good guide from the guy who does ARHD:
Read http://forum.xda-developers.com/showthread.php?t=2265618
For your case, my interpretation of his guide would go like this:
The dev edition came unlocked. A lot of "rooting guides" spend a long time explaining how to unlock since they assume you are not already. but if you *are* unlocked already then any time you stumble across any procedure that involves htcdev.com or "get identifier token" etc you can ignore it.
[If, at some time in the future, someone persuades you to "re-lock" your bootloader for some reason (and as far as i'm concerned there are very few good ones), fine, it won;t hurt anything, but later on if you ever wanted to be unlocked again you would need to go to htcdev.com and follow all those steps to re - un - lock your bootloader. but for now, you're unlocked, life is good.]
with an unlocked bootloader, you can flash a custom recovery.
you want to do this.
using a custom recovery is the simplest and easiest way to flash ROMs going forward.
the most reliable recovery available on the One is CWM non-touch version. so go to http://d-h.st/users/flyhalf205/?fld_id=11322#files and find a file with the highest version number (currently 6.0.x something) that does not say "touch" in it.
The basic steps to loading a custom recovery are
- make sure phone's bootloader is unlocked (with stock dev edition obviously you are already set)
- make sure your computer has android sdk installed and you know where the fastboot executable is
- once you have the latest recovery zip from location above, check its md5, and then rename it something simple like recovery.img and place it in the same folder as your fastboot executable
- on your phone, make sure "fast boot" feature is turned off
- boot phone into HBOOT then Fastboot
(in case it is not obvious, connect your phone now via USB and type the necessary commands into a terminal emulator on the computer)
- while phone is in fastboot, use command "fastboot erase cache"
- while phone is in fastboot, use command "fastboot flash recovery recovery.img" where recovery.img is the name you chose above
at this point you should be able to reboot the phone into your new recovery and have a look around.
first step is always make a backup (known as a "nandroid" backup).
if your goal was to root your existing ROM, then you don;t actually have to do the steps in the guide i linked to above anymore: as soon as you try to exit CWM it will notice you are not already rooted and prompt you if you want to root it.
But if you want to do it the old fashioned way where you go and flash your own super user zip and other useful files that go with it, just refer back to the guide above. If the crucial link to the "rooting tools" is still broken, let me paste it again for you here http://www.androidrevolution.nl/dow...le=Android_Revolution_HD_Root_and_BusyBox.zip
I'll let you read up on how to "flash a zip from recovery". It should be pretty straightforward. (download zip and put zip somewhere on phone, reboot into recovery, say you want to flash a zip, navigate to where it is on the phone, start flash, profit)
Once you have an unlocked bootloader, you can flash a custom recovery
Once you have a custom recovery, you can
- root an existing rom and/or
- flash a custom rom compatible with your setup, presumably one with root baked in
Once you have root on any rom, you can run titanium, wireless tether etc.
Hopefully this is enough to get you started down the right path.

NxNW said:
Ok one last reading assignment, a good guide from the guy who does ARHD:
Read http://forum.xda-developers.com/showthread.php?t=2265618
For your case, my interpretation of his guide would go like this:
The dev edition came unlocked. A lot of "rooting guides" spend a long time explaining how to unlock since they assume you are not already. but if you *are* unlocked already then any time you stumble across any procedure that involves htcdev.com or "get identifier token" etc you can ignore it.
[If, at some time in the future, someone persuades you to "re-lock" your bootloader for some reason (and as far as i'm concerned there are very few good ones), fine, it won;t hurt anything, but later on if you ever wanted to be unlocked again you would need to go to htcdev.com and follow all those steps to re - un - lock your bootloader. but for now, you're unlocked, life is good.]
with an unlocked bootloader, you can flash a custom recovery.
you want to do this.
using a custom recovery is the simplest and easiest way to flash ROMs going forward.
the most reliable recovery available on the One is CWM non-touch version. so go to http://d-h.st/users/flyhalf205/?fld_id=11322#files and find a file with the highest version number (currently 6.0.x something) that does not say "touch" in it.
The basic steps to loading a custom recovery are
- make sure phone's bootloader is unlocked (with stock dev edition obviously you are already set)
- make sure your computer has android sdk installed and you know where the fastboot executable is
- once you have the latest recovery zip from location above, check its md5, and then rename it something simple like recovery.img and place it in the same folder as your fastboot executable
- on your phone, make sure "fast boot" feature is turned off
- boot phone into HBOOT then Fastboot
(in case it is not obvious, connect your phone now via USB and type the necessary commands into a terminal emulator on the computer)
- while phone is in fastboot, use command "fastboot erase cache"
- while phone is in fastboot, use command "fastboot flash recovery recovery.img" where recovery.img is the name you chose above
at this point you should be able to reboot the phone into your new recovery and have a look around.
first step is always make a backup (known as a "nandroid" backup).
if your goal was to root your existing ROM, then you don;t actually have to do the steps in the guide i linked to above anymore: as soon as you try to exit CWM it will notice you are not already rooted and prompt you if you want to root it.
But if you want to do it the old fashioned way where you go and flash your own super user zip and other useful files that go with it, just refer back to the guide above. If the crucial link to the "rooting tools" is still broken, let me paste it again for you here http://www.androidrevolution.nl/dow...le=Android_Revolution_HD_Root_and_BusyBox.zip
I'll let you read up on how to "flash a zip from recovery". It should be pretty straightforward. (download zip and put zip somewhere on phone, reboot into recovery, say you want to flash a zip, navigate to where it is on the phone, start flash, profit)
Once you have an unlocked bootloader, you can flash a custom recovery
Once you have a custom recovery, you can
- root an existing rom and/or
- flash a custom rom compatible with your setup, presumably one with root baked in
Once you have root on any rom, you can run titanium, wireless tether etc.
Hopefully this is enough to get you started down the right path.
Click to expand...
Click to collapse
I ran into an issue following your directions (which were basically the same as the YouTube video about the "easiest way to install custom recovery for the htcone" that I got off another xda thread. I run the command to fastboot flash recovery, and my PC gives me an error saying that fastboot is not a valid command. I have the proper drivers installed, and I am in fastboot on my phone but it won't work. I did notice that on the thread you linked to above, they want my recovery file to be in some sdk folder or something. My directions didn't mention that and the directions you linked to mention an sdk file in the bootloader section, but it tells me to skip that if I have a dev edition. Is the sdk file the reason why my computer won't recognize the command? For what it's worth, I tried that toolkit and it did not seem to recognize my phone either.
Sent from my HTC One using Tapatalk 2

EDIT Just a general tip - you can copy the text of any error message you get and paste it into google and you will doubtless turn up a bunch of interesting info - you are very likely not the first person to encounter the issue.
Anyway here's what I think is happening:
Sometimes when you try to give a command from the command line, a computer doesn't know where the necessary executable file is.
If the SDK was installed ok , then somewhere on your computer is the actual fastboot.exe executable.
Find it.
If it is in a folder called C:\path\to\files\blah\blah then you need to actually type out C:\path\to\files\blah\blah\fastboot.exe to run it.
If you will be doing more commands in this location or any commands that refer to other files in the same location (and some if these procedures assume you will since you'll be putting the flashable image files in this location), you really should tell your terminal program to just change the "working directory" to that location: then whenever you refer to something the computer will look there first. Here's how that looks:
cd C:\path\to\files\blah\blah
fastboot
(Final note- going forward you can make it easier to launch executables by adding their location to your "PATH variable" - google it. )
Maybe you knew all this? But for the benefit of anyone else following these bread crumbs, here's the upshot: Most of these "procedures" that people write down assume some general knowledge of command line syntax. If you're not comfortable with that yet, you're going to need to be persistent and search google a lot.

[Q] HTC One Sprint M7WLS softbricked, don't know what else to do.

With the new 4.3 OTA I thought I might be good to delve into updating my phone today. That was around Noon, it's now 9PM, and I just don't know where else to turn. I know where I screwed up a few things and I feel like I've tried everything. Hopefully you guys will have some helpful suggestions, if not I guess I'll have to bite the bullet.
I'm a noob at rooting. I did root my HTC Evo Shift a year or two ago. Put CM 7.something on it, but I really wasn't happy with the performance so I just RUU'd back to stock and haven't messed with it since. I did leave it rooted for some root required apps though.
I rooted my HTC One a couple months ago using this method:
On gizmodo how-to-root-your-nexus-htc-one-or-samsung-galaxy-s4-990847878 (can't link it because I just signed up)
With 4.3 out I thought I would be able to find a modified update and keep my phone Stock rooted or try InsertCoin or something. My first mistake, I believe, was thinking that root was fine without S-Off.
I've got Drivers and Android SDK on my Win7 machine (I have a Mac and Fedora box if anyone knows any solutions using those OS's). I have on the phone TWRP 2.5.0.0, root, S-On. I try to upgrade to TWRP 2.6.0.0 and that doesn't work so well. I read somewhere that the M7WLS doesn't like that build, and I should try 2.6.0.1, I just strait to 2.6.3.0.
Read some articles on TWRP, watched some videos, so I go to do factory data wipe, cache wipe, dalvik cache wipe, and I do system wipe thinking I need to do that too. Whenever I reboot I basically stop at the HTC splash screen. Mistake number two, I have no OS now.
I hunt down a recovery.img from a site that is supposedly offical Sprint, flash it, try to do a factory restore, no good.
I try getting it back to stock with this:
How to Unroot / Unbrick the HTC One M7: Back to Stock by C4Etech
youtube.com C0G0hKY4P9Y
fastboot oem rebootRUU
fastboot flash zip <rom>.zip
I get errors whether locked or unlocked. I still have S-On and I'm guessing that's why I'm getting signature validation errors.
I try TWRP and ClockworkMod 6.0.4.3 to see if I can mount to my PC, no go.
Fastboot devices recognizes the M7WLS so after more reading I'm going to try ADB sideload. ADB devices does not see my phone. HT Sync is already installed, I remove it and try HTCDriver_4.2.0.001, no go. I remove it and try Universal_Naked_Driver_0.73, still nothing on adb devices. Whether TWRP or ClockworkMod Recovery I can't side seem to sideload.
I go to the store and pick up a cable:
Staples.com Belkin-4-Ports-USB-20-External-Flex-Hub product_IM1QZ5590 (Can't link)
Put
insertcoin-m7-4.0-4.zip AND
Guru_Reset_M7_Sprint_1.29.651.10.zip
on a USB stick, but the phone doesn't recognize it so I can load from either recovery.
I'm sure I've missed a few things in there. Right now I'm sunk, I'm tired, and suggestions are appreciated.

Try buy a USB to go and put a Rom on a Memory stick them using TWRecovery flash the Rom if you have any questions feel free to ask

Demo3827 said:
Try buy a USB to go and put a Rom on a Memory stick them using TWRecovery flash the Rom if you have any questions feel free to ask
Click to expand...
Click to collapse
Thanks for the input Demo. I actually connected it to OSX and the adb devices came right up so I was able to do a rom side load. Thanks again though.

your welcome
pwjohnston79 said:
Thanks for the input Demo. I actually connected it to OSX and the adb devices came right up so I was able to do a rom side load. Thanks again though.
Click to expand...
Click to collapse
your welcome =] anytime :good:

[Q] I messed up

So today I tried to flash one of the GE ROMs, and I overlooked that it needed you to be S-Off. I'm S-On. In the instructions it suggested to wipe storage, so I did, and now my phone loops from turning on to the first page of the set up before rebooting. I have no back up files or other roms on my phone since I wiped storage. I am currently setting up adb on my mbp to push a ROM file, but I don't know if that will work while I'm at the bootloader or in CWM. While in CWM I can't seem to mount the USB storage. Have I completely ruined my phone? I hope this will turn into a learning experience that doesn't include buying a new phone.
Thanks in advance for any advice.

From recovery
adb push nameofrom.zip /sdcard/ (<--- may or may not work)
or
3.04.651.2 RUU
3.05.651.5 RUU
Rumrunner S-OFF

BD619 said:
From recovery
adb push nameofrom.zip /sdcard/ (<--- may or may not work)
or
3.04.651.2 RUU
3.05.651.5 RUU
Rumrunner S-OFF
Click to expand...
Click to collapse
Wow, fast reply. Thanks a lot. I'll probably have to wait to the morning to try.

Looks like the files are failing during transfer. They get to about 2mb, when they should be closer to 200. Is there a way to mount SD card from TWRP? I can flash that instead if it makes this process easier.
Really appreciate the help.

And I'm an idiot. That was kb/s not kb. It was the whole files. Thanks again for the help. I was honestly thinking that I was going to have to walk of shame through the Sprint store after this one.

cntchds said:
Looks like the files are failing during transfer. They get to about 2mb, when they should be closer to 200. Is there a way to mount SD card from TWRP? I can flash that instead if it makes this process easier.
Really appreciate the help.
Click to expand...
Click to collapse
If you can write your recovery, which I assume you can since you can get to it via bootloader, honestly I'd consider loading up PhilZ so you can use an OTG cable to flash a new zip. Why folks continue to live with the current TWRP limitations confuses me, but hey, who am I anyway .
Adding: If you do RUU (probably best anyway after a major failure as you've had), when you get to the point of flashing the recovery -- think about getting yourself an OTG (usb) cable so you can flash PhilZ and keep all your nandroids on USB flash. I keep one or two nandroid copies on the phone just for convenience, but keep *all* of 'em on a USB flash so I'm never out in the weeds and screwed. It works really quite well, including good battery charge/status and whatnot.
Only problem I've seen is some ROM mistakenly assume the device properties will always be "m7wls" and in fact, CWM based recoveries set the device to m7spr. In those cases, I've been able to work in a fix with the ROM developer so all recoveries get supported properly.
Anyway -- give it a thought, might save you from this mess in the future!

tdhite said:
If you can write your recovery, which I assume you can since you can get to it via bootloader, honestly I'd consider loading up PhilZ so you can use an OTG cable to flash a new zip. Why folks continue to live with the current TWRP limitations confuses me, but hey, who am I anyway .
Adding: If you do RUU (probably best anyway after a major failure as you've had), when you get to the point of flashing the recovery -- think about getting yourself an OTG (usb) cable so you can flash PhilZ and keep all your nandroids on USB flash. I keep one or two nandroid copies on the phone just for convenience, but keep *all* of 'em on a USB flash so I'm never out in the weeds and screwed. It works really quite well, including good battery charge/status and whatnot.
Only problem I've seen is some ROM mistakenly assume the device properties will always be "m7wls" and in fact, CWM based recoveries set the device to m7spr. In those cases, I've been able to work in a fix with the ROM developer so all recoveries get supported properly.
Anyway -- give it a thought, might save you from this mess in the future!
Click to expand...
Click to collapse
I do have an OTG cable, and that is a good idea. The main reason I use CWM is because it is extremely comfortable; I've used it for years and it hasn't let me down, TWRP I think has a silly- read: gimicky - interface, and Devs usually explicitly say to flash using one of those two recoveries so I've never used PhilZ. I usually keep a couple nandroids on my sd card, but since I wiped the SD card after flashing it got rid of everything. I should set it up to back up to some cloud storage so I can recover them when the phone goes on the fritz again.
Anyhow, the phone is up and running again. I could not find the files when I used adb push to sdcard so I pushed them to data instead and then it was very easy to find.

PhilZ is just CWM with additions. Touch interface, etc. CWM is good all by itself if you're used to it. All three ultimately do well, it's just TWRP needs some fixes, OTG at a minimum.

[Q] Messed up my HTC ONE M7 (BIG PROBLEM)

Hello guys !
So i will try to keep this short but i have to give you all the details regarding my problem. I was an iOS user for almost 4 years but now i switched to Android. I currently own an HTC One M7 (since july 2014). The phone was brand new and came with android 4.4.2 installed. Recently (2 weeks ago) i updated my phone to 4.4.3. Everything was just perfect. But then i found out about rooting and all the endless modifications so i said i should give it a try. I rooted my phone (and unlocked the bootloader) and installed TWRP 2.6.3.0. Now it gets a little bit more complicated. I tried to turn the S-OFF but couldnt do it and entered in TWRP (by mistake i guess) . From there i had the urge (again i made a mistake) to format everything and i formated even the OS. Thing is after that my phone was bricked. Couldn't connect it to the computer (Linux or windows no matter what i tried the phone wasn't recognised by any PC). So i grabbed an OTG cable and managed to install an operating system named "Guru_Reset_M7_2.24.161.1.zip" from an RUU collection . So i finally managed to install an OS onto my phone and i was happy that my phone wasn't bricked anymore. But then i realised i downgraded to 4.2.2 and the OS is pretty crappy. Besides the WIFI is not working properly all the time , the camera doesn't start and cannot update to 4.4.3 . I have to mention that i don't have any recovery saved or backup. Now i tried to lock the bootloader and gain the S-OFF again but couldn't do it. The thing is i can't enter in recovery , i can't install a custom ROM on my phone and cannot update to the latest (4.4.3) stock htc one android. I need your help because i don't know what to do anymore. I tried to gain S-OFF with rumrunner , moonshide and revone and still no luck. My phone is now recognized by my PC and i can enter the adb devices from command prompt so i guess that is a good thing. But the bad thing is that i can't enter in recovery (it just gives me a black screen with a red triangle and an exclamation sign). I am pretty much a noob but i learned alot about android in the last 3 days. Please help me because i don't know what to do anymore i feel drained exhausted and sad. I just want a normal OS that can run properly on my phone and use my camera and WIFI at maximum proficency (as intended). If i can't run a custom ROM at least help me to revert back to stock and get updates for my OS. Thank you for listening !!
This is my phone info
- Model: HTC One M7
- IMEI SV : 01
- Operator : Vodafone
- Mobile Network Type : HSDPA
- Android OS version : 4.2.2
- HTC Sense version : 5.0
- Software number : 2.24.161.1
- HTC SDK API level : 5.34
- Kernel Version : 3.4.10-g445d072 [email protected] # 1 SMP PREEMPT
- Baseband Version 4T.29.3218.08_10.33F.1718.01L
- Build number : 2.24.161.1 CL211355 release-keys
- Browser version : WebKit/534.30
- TAMPERED
- RELOCKED
- M7_UL PVT SHIP S-ON RH
- HBOOT-1.57.0000
- OpenDSP-v32.120.274.0909
- OS-6.09.401.5
- eMMC-boot 2048MB

That's difficult.
The correct way would be to go S-Off and do a RUU.
But it seems you cannot get S-Off. Did you install the latest HTC Drivers and latest adb and fastboot version?
And your CID would be helpful too.
You can get it with this app: Simple CID Getter

AndyyyFTW said:
That's difficult.
The correct way would be to go S-Off and do a RUU.
But it seems you cannot get S-Off. Did you install the latest HTC Drivers and latest adb and fastboot version?
And your CID would be helpful too.
You can get it with this app:
Thank you very much for your fast response . My CID is HTC_032 HTC-EastEurope. I have all the drivers installed and updated. I've heard about this CID but don't know how to use it or what is it for. Im now trying to install clockwork manager (maybe i can get into recovery with it). If you have any ideas please keep me posted. thanks again
Click to expand...
Click to collapse

Did you uninstall HTC Sync Manager after installing it?

AndyyyFTW said:
Did you uninstall HTC Sync Manager after installing it?
Click to expand...
Click to collapse
No ! Should i do that?

Yes, you should do that. Then try to get S-OFF again.

​
AndyyyFTW said:
Yes, you should do that. Then try to get S-OFF again.
Click to expand...
Click to collapse
Unfortunately that did not work. I am still S-ON .

If all you need is a custom recovery so you can flash a 4.4.2 rom then I suggest just doing so. Pretty sure ViperOne 6.2 is 4.4.2 and works wonderfully, 7.x is a different story. I have seen a lot of issues with folks attempting s-off on hboot 1.57. If your goal is functionality I suggest reading up on TWRP 2.7.1.1 (seems to work best with ViperOne) and then getting yourself a ViperOne 6.2 from the previous version on their thread.
Was reading OP again, if you had 4.4.3 working fine there is no reason you can't just flash the viper 7.1 or any other 4.4.3 rom. If you formatted you recovery partition you just need to fastboot another one in there. Unless I am missing something?

I finally managed to repair the recovery (i reinstalled TWRP recovery again as if the phone was not rooted) and now it's working. Still need to turn the S-OFF (im S-ON right now) but i can't do it. If you know a ROM that does not require to have S-OFF then please tell me. Thanks in advance

No "rom" requires s-off. I personally use ViperOne 7x on my 4.4.3.
Edit: You can try CM11, I did not like the feel of CM or PAC or any AOSP Rom on my M7, this is only a personal preference, they work. You mentioned the camera, For this I suggest staying on a more stock rom like ViperOne or any other for that matter per the camera on the AOSP is not tip top, functional, but seen better days.
Honestly, you can not do much harm so flash and flash away until you find one you like and that meets your needs. Just take care when formatting any partitions the only three you need worry about really is cache, data and system <-- this ones your rom.

I downloaded ViperOne and attempted to install it. After extracting the files in twrp installer to 100% it gave the message that some elements have failed. Now the phone boots only in TWRP recovery. that's horrible. I am now installing the old guru OS that i previously had.

Tabquer said:
I downloaded ViperOne and attempted to install it. After extracting the files in twrp installer to 100% it gave the message that some elements have failed. Now the phone boots only in TWRP recovery. that's horrible. I am now installing the old guru OS that i previously had.
Click to expand...
Click to collapse
Didn't say what failed did it? You might want to try using recovery to format you system, cache and data.. Sounds like you have had a rough time with it and there could be some garbage left behind.
Edit: When you say extracting.... Are you choosing to install the zip and going through the Aroma installer prompts?

Yeah i was going through the aroma installer and hit next next (selected all the apps i needed) and then i hit install . Then it says that the files are extracting and i have to be patient (because it will take like 10 minutes). and after the extracting was completed (showing 100% ) it said that something something failed. And i rebooted the device but i was surprised to see that the phone went into the recovery mode (the old OS dissapeared or couldnt boot it) and i had to reinstall the old guru OS. This os is friggin garbage. Camera still wont work and wifi is still crappy. I tried to install CM11 (before trying the viperone) but couldn't load it. Dont know why but it failed from the beggining of the install. Maybe is something wrong with the kernel (i have no idea what that is and what to do to change it - or if i should ).

Tabquer said:
Yeah i was going through the aroma installer and hit next next (selected all the apps i needed) and then i hit install . Then it says that the files are extracting and i have to be patient (because it will take like 10 minutes). and after the extracting was completed (showing 100% ) it said that something something failed. And i rebooted the device but i was surprised to see that the phone went into the recovery mode (the old OS dissapeared or couldnt boot it) and i had to reinstall the old guru OS. This os is friggin garbage. Camera still wont work and wifi is still crappy. I tried to install CM11 (before trying the viperone) but couldn't load it. Dont know why but it failed from the beggining of the install. Maybe is something wrong with the kernel (i have no idea what that is and what to do to change it - or if i should ).
Click to expand...
Click to collapse
First thing, the reason that viperone didn't install was because of the version of TWRP you are using. You need to use the latest version for it to work
Secondly, CM11 does not flash at all in TWRP. You need to use CWM recovery (Google it and you will find the recovery file to flash).
To achieve s off is difficult on hboot 1.57 - some users have reported success with various methods. One namely installing CM11 and running firewater. If you get a Whelp this sucks message nothing you can do other than using sunshine app (Google root ninja). This will cost you $25 but honestly, with all the hard work these guys put it to make obtaining s off so easy it's worth it. Plus to restore your phone back to working order again!
For sunshine to work you need a stock(ish) ROM like ARHD/ViperOne and run the app. It checks the phone to make sure it'll work then redirect you to pay for the app. Good luck!

Well.. when you flash your custom it comes with a boot.img which is your kernel so it can't really be that. Kinda makes wonder, you can flash the 4.2.2 which won't match the current installed firmware and is why your camera,WiFi,mms and who knows what countless other things don't work. But fails to install the others... What variant are you?
Edit: That information in the OP did you get it from "fastboot getvar all"? if not can you post one of those here, dont need serial or IEMI

MrLizm said:
Well.. when you flash your custom it comes with a boot.img which is your kernel so it can't really be that. Kinda makes wonder, you can flash the 4.2.2 which won't match the current installed firmware and is why your camera,WiFi,mms and who knows what countless other things don't work. But fails to install the others... What variant are you?
Edit: That information in the OP did you get it from "fastboot getvar all"? if not can you post one of those here, dont need serial or IEMI
Click to expand...
Click to collapse
Use twrp 2.6.3.3 from here and flash viper one http://techerrata.com/browse/twrp2/m7

wow it's getting a little overwhelming but i will try to listen to your advice and update the TWRP (if i can) and keep you updated with the progress. Give me a little time to answer the questions and i will get back to you tomorrow . Thanks in advance.

Tabquer said:
wow it's getting a little overwhelming but i will try to listen to your advice and update the TWRP (if i can) and keep you updated with the progress. Give me a little time to answer the questions and i will get back to you tomorrow . Thanks in advance.
Click to expand...
Click to collapse
Its a cake walk. Goto that link download the 2.6.3.3, boot to fastboot, in your cmd type "fastboot flash recovery filename.img", reboot to recovery select install, find zip on sd do a full wipe and send it!!! You Got this

MrLizm said:
Its a cake walk. Goto that link download the 2.6.3.3, boot to fastboot, in your cmd type "fastboot flash recovery filename.img", reboot to recovery select install, find zip on sd do a full wipe and send it!!! You Got this
Click to expand...
Click to collapse
I updated TWRP to 2.6.3.3 from your link and installed viper one and it's working ! so far so good ! Thanks mate ! you are a lifesaver

Nothing failed this time ! WIFI works like a charm