[Guide/How To] Flash Hboot's OTG - Sprint HTC One (M7)

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?

Related

[Q] Help flashing blackrose hboot

So this has been mind breaking for me. I failed to flash the blackrose hboot everytime i trie and on every rom. It gets to the point where it has sent it files and then it says <waiting for device>. This happens on stock, BuglessBeast, rcadsmixhd 2.3 & 1.6 and hypersense (i like sense ). Anyone has any advice . Btw it did not brick it.
the problem your having isn't actually related to which rom your using on your phone. its that its not being detected as an adb device. you need to make sure that your drivers are installed and you see it in device manager as an ADB interface under Android Phone.
m0_t3 said:
the problem your having isn't actually related to which rom your using on your phone. its that its not being detected as an adb device. you need to make sure that your drivers are installed and you see it in device manager as an ADB interface under Android Phone.
Click to expand...
Click to collapse
Ehm, usb debugging is enabled and detected by the software at first. It gets to the point that it sends its hboot and after that it says something like error: deviceoffline and then stuck on waiting for device forever.
it could be that another program like PDAnet is interfering.
do you use any other programs on your PC that would use adb?
m0_t3 said:
it could be that another program like PDAnet is interfering.
do you use any other programs on your PC that would use adb?
Click to expand...
Click to collapse
well maybe htc sync but that was closed and its process was killed by taskmanager. No other programs i can think of.
well if your drivers are fine and there is nothing causing some form of interruption then. its probably an issue coming from the phone.
since you've tried it with so many different roms am guessing you didnt bother running/installing any apps
try it without the SD card inserted maybe.
thinking i should try and see if i can't replicate your issue find out what the issue is.
m0_t3 said:
well if your drivers are fine and there is nothing causing some form of interruption then. its probably an issue coming from the phone.
since you've tried it with so many different roms am guessing you didnt bother running/installing any apps
try it without the SD card inserted maybe.
thinking i should try and see if i can't replicate your issue find out what the issue is.
Click to expand...
Click to collapse
SO without my sd card it did not make any difference, apart from that it now mixes the message: adb server is out of date. Killing... and then waiting for device again.
the first time i installed blackrose i didn't use this method but maybe you can try flashing the hboot manually, which is what i normally do now, find it more straight forward.
[edit]
is your bootloader unlock?
m0_t3 said:
the first time i installed blackrose i didn't use this method but maybe you can try flashing the hboot manually, which is what i normally do now, find it more straight forward.
[edit]
is your bootloader unlock?
Click to expand...
Click to collapse
Ehm obviously yes how i can flash roms other wise? How do i flash this hboot then. BTW i have slcd nexesus one phone if that matters
http://forum.xda-developers.com/showthread.php?t=1270589
download the manual version zip file from there. the instructions are contained inside the zip.
he removed the caution about slcd N1's so i think that shouldn't be a problem anymore.
m0_t3 said:
http://forum.xda-developers.com/showthread.php?t=1270589
download the manual version zip file from there. the instructions are contained inside the zip.
he removed the caution about slcd N1's so i think that shouldn't be a problem anymore.
Click to expand...
Click to collapse
WOW you are awesome sir thank you now it works i wish you could click the thanks button 30.000 times.
race55 said:
Ehm obviously yes how i can flash roms other wise? How do i flash this hboot then. BTW i have slcd nexesus one phone if that matters
Click to expand...
Click to collapse
You can easily flash ROMs without unlocking the bootloader. All that is required is to root the original OS and install a custom recovery using a program like ROM Manager.
But I believe the phone is detected differently when in fastboot mode. Did you verify that the phone is still properly recognized in device manager when in fastboot mode?
What happens if you put the device into fastboot mode (holding the trackball when powering on) and you type fastboot devices at your command prompt?
Awesome.
Glad to help ^_^
Sent from my Nexus One using xda premium
Not directly related but I had to use BREditor and create a new hboot with the 200/16/220 layout and flash that. I just could not get the ICS roms to flash otherwise... strange...
bassmadrigal said:
You can easily flash ROMs without unlocking the bootloader. All that is required is to root the original OS and install a custom recovery using a program like ROM Manager.
But I believe the phone is detected differently when in fastboot mode. Did you verify that the phone is still properly recognized in device manager when in fastboot mode?
What happens if you put the device into fastboot mode (holding the trackball when powering on) and you type fastboot devices at your command prompt?
Click to expand...
Click to collapse
It gives me attached device: Ht9 and thencq lot of numbers
Sent from my HTC Nexus One using XDA App
race55 said:
It gives me attached device: Ht9 and thencq lot of numbers
Click to expand...
Click to collapse
Well, that definitely means that your device is recognized. Did you get it working?
bassmadrigal said:
Well, that definitely means that your device is recognized. Did you get it working?
Click to expand...
Click to collapse
Ehm using manual method it worked. It was kinda confusing because in the blackrose thread it says that u must use manual for osx. He should update his post
race55 said:
Ehm using manual method it worked. It was kinda confusing because in the blackrose thread it says that u must use manual for osx. He should update his post
Click to expand...
Click to collapse
If you throw a post at the end stating what you had to do, he would probably update his original post.
Not directly related but I had to use BREditor and create a new hboot with the 200/16/220 layout and flash that. I just could not get the ICS roms to flash otherwise... strange...
Click to expand...
Click to collapse
ICS is too big for the stock ROM space on the N1, so you need to make those alterations so it can fit. texasice did make a striped down version that works on stock though.
race55 said:
Ehm obviously yes how i can flash roms other wise? How do i flash this hboot then. BTW i have slcd nexesus one phone if that matters
Click to expand...
Click to collapse
If you are like me, you have been flashing ROMS on your phone for years before you ever unlocked the bootloader. I didn't do it until about 6 months ago because I needed to flash Blackrose. Also, don't bite the hand that is trying to feed you.

[Q] Bricked my HTC ONE - please help will reward

All,
New to htc and flashing, and try doing at 3am didn't help either. hope someone can help. Will paypal $50 to anyone that can help. Thanks in advance.
Here's what i did
using One_S_All-In-One_Kit_v3.5 for all my modding
got token
unlocked bootloaded
didn't flash any recovery
flash a new .img kernel, but i used a boot.img from a zip file (home2wake zip) - don't ask why, i wasn't thinking lol
phone rom was all black, keeps rebooting
i managed to flash recovery, recovery-clockwork-6.0.3.1-m7wls.img
then wanted to restore stock rom
so i downloaded, this rom, http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
flashed zip using recovery
went through the rom custom installation of what i wanted installed.
After that it rebooted and stuck on green htc screen
i can get back into boot loader, but can't load recovery, can't factory reset, any option i select, the screen flash and sends me back to bootloader
rom won't load, can't get into recover, computer not detecting phone
Please help!!!
Check out this maybe a RUU will help -
http://forum.xda-developers.com/showthread.php?t=2251800
Why did you use one s kit, I'm confused
Sent from my HTCONE using xda premium
you can try to load ADB Fastboot on your PC, then connect your phone via usb, be sure to have all of the drivers.
in bootloader, if it reads FASTBOOT USB, then you can us
fastboot flash recovery (Name of recovery).img
once that is done you should be able to at least get back into recovery....
check the link for recovery file
http://forum.xda-developers.com/showthread.php?t=2236418
I am no expert, but my guess would be to go back to stock boot / recovery: http://forum.xda-developers.com/showthread.php?t=2236418
Relock your phone: fastboot oem lock
Install the RUU: http://forum.xda-developers.com/showthread.php?t=2250904
And in the future don't use an All-In-One-Kit meant for another phone (The One S in your case)
p.s. Another thread that may help get you back to square one: http://forum.xda-developers.com/showthread.php?t=2251800
thanks all,
will try all the suggestions above tonight, will let you guys know how it goes. i used the all one s because it was gui and easy and lots of extra and functions. but i guess the extra made it worst.
Right now when i plug in my phone the computer doesn't detect anything, hopefully the adb can talk to it to flash a new recovery/rom/kernel.
Pm me
Sent from my HTCONE using Tapatalk 2
It wasn't the extras that messed it up. It was the fact you were using an AIO that isn't for your device. That's a big no no.
Sent from my HTCONE using xda app-developers app
gu12u7 said:
thanks all,
will try all the suggestions above tonight, will let you guys know how it goes. i used the all one s because it was gui and easy and lots of extra and functions. but i guess the extra made it worst.
Right now when i plug in my phone the computer doesn't detect anything, hopefully the adb can talk to it to flash a new recovery/rom/kernel.
Click to expand...
Click to collapse
Once you get back to stock with the RUU, use Hassoon2000's all in one kit...n00b proof!
P_M_G said:
Once you get back to stock with the RUU, use Hassoon2000's all in one kit...n00b proof!
Click to expand...
Click to collapse
i was using this, all of the recovery on there were for samsung s3/s4/and special edition. so i couldn't get to the recovery. Then i started tweaking around with the extras and flashed a boot.img to a kernel. failed
Android Revolution ROM is not for the sprint htc one. fyi
First you'll need this file http://forum.xda-developers.com/showthread.php?t=2250904
Extract to someplace you can find it, maybe the desktop
if you power the phone down then hold the vol - button does it boot into bootloader?
if so make sure you have the htc fastboot drivers installed from htc sync
if your on a windows machine from command prompt navigate to the platform-tools folder
for example
mine is in C:/users/ray/downloads/adt-bundle-windows-x86_64/adt-bundle-windows-x86_64/sdk/platform-tools
in command prompt issue the command
fastboot oem lock
once the bootloader is re-locked
issue the command
fastboot oem rebootRUU
the phone should reboot into a black screen with greenish htc letters
find the setup.exe file from the ruu file and run it.
if all goes well you should be back to stock with a locked bootloader.
good luck
Awesome, unbricked it! Thank you wranglerray!!!!!!
Also thanks to everyone that replied, but it was wranglerray detailed step that helped me through it. awesome community.
as promised, send me your paypal account wranglerray, i'll send you the $50
Let this thread be a lesson that 1) don't mess with your phone if you don't know what you're doing and 2) don't flash a GSM ROM on your Sprint phone because it wipes your boot and recovery partition (on GSM phones, it wipes data and system but sprints partitions are different).
Sent from my HTCONE using Tapatalk 2
-viperboy- said:
Let this thread be a lesson that 1) don't mess with your phone if you don't know what you're doing and 2) don't flash a GSM ROM on your Sprint phone because it wipes your boot and recovery partition (on GSM phones, it wipes data and system but sprints partitions are different).
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
failing is learning. but more like read all the instructions before messing with your phone.
P_M_G said:
Once you get back to stock with the RUU, use Hassoon2000's all in one kit...n00b proof!
Click to expand...
Click to collapse
Isn't that a One X only kit?
gu12u7 said:
Awesome, unbricked it! Thank you wranglerray!!!!!!
Also thanks to everyone that replied, but it was wranglerray detailed step that helped me through it. awesome community.
as promised, send me your paypal account wranglerray, i'll send you the $50
Click to expand...
Click to collapse
That's what these forums are all about no need to send money. Glad I could help you.
gu12u7 said:
failing is learning. but more like read all the instructions before messing with your phone.
Click to expand...
Click to collapse
Failing after making a bunch of random attempts to do something doesn't constitute learning. Next time you should make sure you actually understand what it is that you are trying to do before you do it, and maybe then you won't end up almost completely wiping your phone clean.
You're lucky that the international One's and Sprint Ones partitions aren't like the Sprint/international S3, or else you would've overrided your bootloader as well and had a brick on your hands.

softbrick help!

Yesterday I bought an HTC One (in Thailand) and I with all the talent I could muster I put my phone into a sad state already. I can get into fastboot and access my device from the computer, but that is about it. Recovery doesn't work at all.
./fastboot flash recovery openrecovery-twrp-2.5.0.0-m7.img gets recovery working with twrp, but that doesn't seem to help much at the point I'm at now.
I have a Mac, so the all-in-one tool I've seen will not work for me (I'd prefer not to use a tool at this point anyway while I'm still learning the android ecosystem).
I tried to download the HTC One development image from HTC's website and thought I could use that with fastboot, to get myself up and running again. After the download, I noticed the .zip file seems corrupt though. I couldn't open in Mac's Archive Utility. Using the command-line unzip, it will unzip with errors. Subsequent downloads did not help.
But I tried an update anyway:
./fastboot update PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.zip
Whoops: didn't find expected signature
read_central_directory_entry failed
error: failed to access zipdata in '4?];g????
_m????jS??W??֏D?q??$ ?!?D??????*[?/5?????h???;?-գ?ѫ/??Z?ו?#j???W2l?d?k??s?#??g?+??]o?09?Q?l?}q??8??^K???Ǩi?m?~?pR7??????ggʼn??]+ꬷ??5Xּ??AP?ɏ??^?rIE6??gٶ??f?D?3w
S(?ڦGv?zW??.??K??OߓXQ7e?qg,y??????<:?8?7J?d*?v?b?~O?X?????F??4?t?h??3뺟??r?|[o鹟g??n'
I'm not even sure updating the phone with the factory image is the correct thing todo, but if it is, does anyone have a link to a uncorrupted zip file?
Is there another way to get my phone back in shape? I'd like to avoid using any tools other than adb or fastboot so I can really understand the process of what's going on myself.
The people that are more knowledgeable about fixing stuff like this will likely need to know which variant your phone is.
Have you tried the RUU thread? That might be able to get you back to at least stock.
----------------------o('_')o----------------------
Sent from an HTC One with using xda app:
TrickDroid ROM 5.4.0
Bulletproof 1.8
Tetsumi06 said:
The people that are more knowledgeable about fixing stuff like this will likely need to know which variant your phone is.
Have you tried the RUU thread? That might be able to get you back to at least stock.
----------------------o('_')o----------------------
Sent from an HTC One with using xda app:
TrickDroid ROM 5.4.0
Bulletproof 1.8
Click to expand...
Click to collapse
I'm not sure what other info to provide. It's an HTC One (m7), not tied to any carrier. I unlocked it and rooted it too. it's s-on (from what i gather it's not possible to have an HTC One in s-off yet). Prior to my messing around with it, the phone was running Android 4.1.2 when purchased...just the normal HTC One specs...until I blew all that away of course.
If there is some specific information I need to provide to help that I'm not aware please let me know.
Thanks!
kwaamkit said:
I'm not sure what other info to provide. It's an HTC One (m7), not tied to any carrier. I unlocked it and rooted it too. it's s-on (from what i gather it's not possible to have an HTC One in s-off yet). Prior to my messing around with it, the phone was running Android 4.1.2 when purchased...just the normal HTC One specs...until I blew all that away of course.
If there is some specific information I need to provide to help that I'm not aware please let me know.
Thanks!
Click to expand...
Click to collapse
Also forget to mention, as far as I know the ruu is an exe that only runs on windows.
Have you tried sideloading a stock ROM? When you're in TWRP are you able to mount cache/sdcard/system?
ryan9316 said:
Have you tried sideloading a stock ROM? When you're in TWRP are you able to mount cache/sdcard/system?
Click to expand...
Click to collapse
I only see 4 partitions available to mount: Cache, Data, System, USB-OTG. Of those I can only select Data and System.
Also, you could point me to where I could find a stock ROM for the HTC One?
Thanks,
kwaamkit said:
I only see 4 partitions available to mount: Cache, Data, System, USB-OTG. Of those I can only select Data and System.
Also, you could point me to where I could find a stock ROM for the HTC One?
Thanks,
Click to expand...
Click to collapse
have you tried to push the rom via fastboot
Please see general faq, item 10...
skinsfanbdh said:
have you tried to push the rom via fastboot
Click to expand...
Click to collapse
not sure how to do this correctly...i tried the following series of commands in this order:
./fastboot flash boot boot_signed.img
./fastboot flash recovery recovery_signed.img
./fastboot flash system system.img
so far so good...but then ./fastboot update PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.zip
failed (see my original post for why). it seems the developer rom downloaded from HTC is corrupt (I noticed this will unzipping it).
Golv said:
Please see general faq, item 10...
Click to expand...
Click to collapse
my phone is in a state where adb cannot see the device, only fastboot can see the device. this tip won't work unfortunately.
kwaamkit said:
I only see 4 partitions available to mount: Cache, Data, System, USB-OTG. Of those I can only select Data and System.
Also, you could point me to where I could find a stock ROM for the HTC One?
Thanks,
Click to expand...
Click to collapse
Ah, using twrp's adb sideload it looks like i can load a rom file onto the phone. But definitely the rom from HTC website is corrupt. Message on the phone indicated the sideload failed due to a corrupt zip file.
Can someone please point me to a sane HTC ROM file and I'll try that to sideload that?
Thanks again for all the help. much appreciated.

[Q] where to proceed next? - i F'd up!

all,
it was with reckless abandon and blind/naive decisions that got me to this point. i will just lay it all out what ive done in the hopes one of you brilliant minds will lead me into the light. before i lay out the steps in which ridiculous choices led me to this conundrum, here is the question...
Where do i go from here to resolve the issue that i have and can get into bootloader (tampered/unlocked and in S-ON) but i have no operating system?
keep in mind that Ive probably and admittedly should not have been dabbling in things i had no business doing with the little to no proper due diligence...."i am awarded no points and may god have mercy on my soul!!!!!!!!!!!!"
1) i used the htc dev process to unlock my bootloader and it worked well.
2) i then proceeded to flash some custom recovery .img files via "fastboot flash recovery <insert filename here" and the .img at the end of course.
recovery-clockwork-touch-6.0.3.4-m7 <---didnt take the first time or anytime. kept saying "entering recovery" but then the screen would go black, not boot into the recovery screen and then the phone would reboot as it would normally and go into stock OS
i then tried the following .img files below, all with the same result...
openrecovery-twrp-2.6.0.1-m7
openrecovery-twrp-2.6.0.0-m7
openrecovery-twrp-2.5.0.0-m7
recovery-clockwork-6.0.3.2-m7ul <<<---this was the only recovery .img file that would take so i then decided to play around with the options.
3) i then proceeded to make another ridiculous choice. under one of the options in clockwork recovery "classic" menus i went forth and selected the "wipe data/factory reset" option.
so what i have now is i believe a htc one sprint phone that has bootloader unlocked with what i believe is no OS. i hear on my computer the sound when it connects via "fastboot usb" but obviously the computer doesn't recognize it so i can copy and paste a zip file onto it.
i was looking at a few threads here and could really use some guidance/encouragement. the threads are
http://forum.xda-developers.com/showthread.php?t=2277892 <<< the FAQ sticky
http://forum.xda-developers.com/showthread.php?t=2368907 <<< the [ROM] stock sprint one 1.31.651.2 thread
http://forum.xda-developers.com/showthread.php?t=2368907 <<< the [RUU] sprint htc one 1.29.651.10 thread
what would be the best course of action for me to take? bear in mind that the end result would probably be obviously a working phone, probably stock or w/e seems best.
thank you for taking the time in reading my post. if you require any additional information, please ask. i am probably leaving out important pieces of info.
deadly
All you need to do is fastboot flash recovery a working recovery then check and see if adb works for you in recovery.
If it does then you can adb push a Rom to /sdcard and flash it in the recovery.
Sent from my HTCONE using xda app-developers app
insuusvenerati said:
All you need to do is fastboot flash recovery a working recovery then check and see if adb works for you in recovery.
If it does then you can adb push a Rom to /sdcard and flash it in the recovery.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
thank you for your quickresponse.
as i am very very "scared" to this up any further. what would the suggested "working recovery" file i should choose and then what rom should i use? honestly im tempted at the stock one that i linked but im worried that if that doesnt go smoothly, i will lose my unlocked bootloader feature.
deadlytwin said:
thank you for your quickresponse.
as i am very very "scared" to this up any further. what would the suggested "working recovery" file i should choose and then what rom should i use? honestly im tempted at the stock one that i linked but im worried that if that doesnt go smoothly, i will lose my unlocked bootloader feature.
Click to expand...
Click to collapse
Use this tool, you cant mess up http://forum.xda-developers.com/showthread.php?t=2236814 just make sure you use the Sprint recoveries and download and sideload a sprint Rom.
Konfuzion said:
Use this tool, you cant mess up http://forum.xda-developers.com/showthread.php?t=2236814 just make sure you use the Sprint recoveries and download and sideload a sprint Rom.
Click to expand...
Click to collapse
THANKS! i saw this thread earlier. ill take a look. ive at least watched wwjoshdew's video and i think that should work too. downloading the stuff now.
just tried wwjoshdew's directions. looks like i cant do the RUU 1.29xxxx. it goes through all the steps but at the end it says error because of the 1.31xxxx version i have already. i guess that means i have to wait until someone releases an RUU for 1.31.651.2
and if i am not sure if usb debugging mode ins enabled and i cant get back into normal bootup for the phone because i think i wiped my OS like stated in my first post. is my next step to do hansoon's AIO tool kit?
deadlytwin said:
all,
it was with reckless abandon and blind/naive decisions that got me to this point. i will just lay it all out what ive done in the hopes one of you brilliant minds will lead me into the light. before i lay out the steps in which ridiculous choices led me to this conundrum, here is the question...
Where do i go from here to resolve the issue that i have and can get into bootloader (tampered/unlocked and in S-ON) but i have no operating system?
keep in mind that Ive probably and admittedly should not have been dabbling in things i had no business doing with the little to no proper due diligence...."i am awarded no points and may god have mercy on my soul!!!!!!!!!!!!"
1) i used the htc dev process to unlock my bootloader and it worked well.
2) i then proceeded to flash some custom recovery .img files via "fastboot flash recovery <insert filename here" and the .img at the end of course.
recovery-clockwork-touch-6.0.3.4-m7 <---didnt take the first time or anytime. kept saying "entering recovery" but then the screen would go black, not boot into the recovery screen and then the phone would reboot as it would normally and go into stock OS
i then tried the following .img files below, all with the same result...
openrecovery-twrp-2.6.0.1-m7
openrecovery-twrp-2.6.0.0-m7
openrecovery-twrp-2.5.0.0-m7
recovery-clockwork-6.0.3.2-m7ul <<<---this was the only recovery .img file that would take so i then decided to play around with the options.
3) i then proceeded to make another ridiculous choice. under one of the options in clockwork recovery "classic" menus i went forth and selected the "wipe data/factory reset" option.
so what i have now is i believe a htc one sprint phone that has bootloader unlocked with what i believe is no OS. i hear on my computer the sound when it connects via "fastboot usb" but obviously the computer doesn't recognize it so i can copy and paste a zip file onto it.
i was looking at a few threads here and could really use some guidance/encouragement. the threads are
http://forum.xda-developers.com/showthread.php?t=2277892 <<< the FAQ sticky
http://forum.xda-developers.com/showthread.php?t=2368907 <<< the [ROM] stock sprint one 1.31.651.2 thread
http://forum.xda-developers.com/showthread.php?t=2368907 <<< the [RUU] sprint htc one 1.29.651.10 thread
what would be the best course of action for me to take? bear in mind that the end result would probably be obviously a working phone, probably stock or w/e seems best.
thank you for taking the time in reading my post. if you require any additional information, please ask. i am probably leaving out important pieces of info.
deadly
Click to expand...
Click to collapse
first off thats the wrong recovery, you want openrecovery-twrp-2.5.0.0-m7wls.img (this is for sprint the m7 is international)2.6 has been giving some problems, don't know if they have it worked out yet, 2.5 is good, so
deadlytwin said:
just tried wwjoshdew's directions. looks like i cant do the RUU 1.29xxxx. it goes through all the steps but at the end it says error because of the 1.31xxxx version i have already. i guess that means i have to wait until someone releases an RUU for 1.31.651.2
and if i am not sure if usb debugging mode ins enabled and i cant get back into normal bootup for the phone because i think i wiped my OS like stated in my first post. is my next step to do hansoon's AIO tool kit?
Click to expand...
Click to collapse
Use the tool I posted above and try to install htc drivers, install recovery and sideload a SPRINT rom. You could also try s-off and follow this guide for RUU on 1.31 if your still having trouble. http://forum.xda-developers.com/showthread.php?t=2390821
Konfuzion said:
Use the tool I posted above and try to install htc drivers, install recovery and sideload a SPRINT rom. You could also try s-off and follow this guide for RUU on 1.31 if your still having trouble. http://forum.xda-developers.com/showthread.php?t=2390821
Click to expand...
Click to collapse
appreciate it!
Update: yea my phone is not in usb debugging mode. ><
Aldo101t said:
first off thats the wrong recovery, you want openrecovery-twrp-2.5.0.0-m7wls.img (this is for sprint the m7 is international)2.6 has been giving some problems, don't know if they have it worked out yet, 2.5 is good, so
Click to expand...
Click to collapse
ill check this.
Update: im in recovery now. next step isnt looking so good ><
so this is starting to look bleak. i am now able to get into recovery but i cant do adb sideload. it fails. has it got to do with the possibility that usb debugging was not turned on before i wiped data?
any ideas on my next try?
deadlytwin said:
so this is starting to look bleak. i am now able to get into recovery but i cant do adb sideload. it fails. has it got to do with the possibility that usb debugging was not turned on before i wiped data?
any ideas on my next try?
Click to expand...
Click to collapse
go to file manager in twrp and see if there is an 0 folder at the top if so delete it(make sure its empty first) then try a sideload
or use es file explorer and look at your files

[Q] CWR or TWRP flashable Zip

Hi,
Is there a way to flash a custom recovery instead of pushing it with adb?
I'm not at all familiar with it, and it's not -only- laziness: my computer never worked well with android drivers (I think it comes from my laptop strange usb drivers), I never could recognize any android device on it.
Other computers I tried were fine.
So yeah, I only flash with otg or transferring through ftp.
I know there are zip files out there for recoveries (I did flash one for my Nexus 7), but I can't find anything working with the HTC One.
I anyone has an idea, I'd be happy to hear it
Bipo said:
Hi,
Is there a way to flash a custom recovery instead of pushing it with adb?
I'm not at all familiar with it, and it's not -only- laziness: my computer never worked well with android drivers (I think it comes from my laptop strange usb drivers), I never could recognize any android device on it.
Other computers I tried were fine.
So yeah, I only flash with otg or transferring through ftp.
I know there are zip files out there for recoveries (I did flash one for my Nexus 7), but I can't find anything working with the HTC One.
I anyone has an idea, I'd be happy to hear it
Click to expand...
Click to collapse
Stop being lazy and just push it using adb. It's rather simple. Not sure if there a zip versions of recoveries for the HTC One
Bipo said:
Hi,
Is there a way to flash a custom recovery instead of pushing it with adb?
I'm not at all familiar with it, and it's not -only- laziness: my computer never worked well with android drivers (I think it comes from my laptop strange usb drivers), I never could recognize any android device on it.
Other computers I tried were fine.
So yeah, I only flash with otg or transferring through ftp.
I know there are zip files out there for recoveries (I did flash one for my Nexus 7), but I can't find anything working with the HTC One.
I anyone has an idea, I'd be happy to hear it
Click to expand...
Click to collapse
and if you cant use adb from your usb port use adb wireless to do it from your wifi network (use adb konnect from play store is the easy way) you need root
OK, no easy way. I can't connect my device with a wire so I'll try with wifi tomorrow. Thanks!
Envoyé depuis mon HTC One avec Tapatalk
You can use Flashify app to flash recoveries..
Sent from my HTC One using XDA Premium 4 mobile app

Categories

Resources