Quick question coming from galaxy nexus I had to unlock and root via adb no problem.
Well I bought the developer edition because it was unlocked. Since one step is already done (bootloader unlocked). In theory I should be able to flash a custom recovery, install root app(super user) and be good?.
1) download custom recovery flash through adb or stock recovery?
2) flash super user
Should be profit correct? I searched and didn't see any info about the developer Edition that's why I posted sorry if this has been asked and I missed it.
Sent from my HTC One using xda premium
That is all I did and I'm now rooted and running custom recovery. I used the all in one toolkit but your way should work just fine...
Sent from my HTC One using xda app-developers app
Sweet thank you
Sent from my HTC One using xda premium
[Q] what steps/order to follow in Hasoon2000's all-in-one tool kit
trevb87 said:
That is all I did and I'm now rooted and running custom recovery. I used the all in one toolkit but your way should work just fine...
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I also tried to use the all-in-one toolkit on my HTC1 Dev Ed, but were confused by so many "boxes" and what order to follow in the flow of things... Could you please list the order of steps that you used to get rooted, skip the the top left box entirely since Dev Ed is already bootloader-unlocked? Thanks.
jcc266 said:
I also tried to use the all-in-one toolkit on my HTC1 Dev Ed, but were confused by so many "boxes" and what order to follow in the flow of things... Could you please list the order of steps that you used to get rooted, skip the the top left box entirely since Dev Ed is already bootloader-unlocked? Thanks.
Click to expand...
Click to collapse
yeah i skipped the bootloaded stuff cuz like you said its already unlocked. I went straight to the recovery stuff. I did the TWRP. I will say it took a few times for it to actually work. don't know if I was doing something wrong or if its just cuz the phone is the dev model. I also now the tampered thing on the bootloader that other have mentioned in the forums. after the recovery finally took, i did the perm root option. Hope it helps
trevb87 said:
yeah i skipped the bootloaded stuff cuz like you said its already unlocked. I went straight to the recovery stuff. I did the TWRP. I will say it took a few times for it to actually work. don't know if I was doing something wrong or if its just cuz the phone is the dev model. I also now the tampered thing on the bootloader that other have mentioned in the forums. after the recovery finally took, i did the perm root option. Hope it helps
Click to expand...
Click to collapse
Thanks for replying. So you did not do the the "Boot into Bootloader" command but went directly to "Flash Recovery" box? By using this toolkit we don't have to get into Bootload or Recovery Mode first (either by using the Commands in the toolkit box or by pushing Volume Up or Down + Power buttons)? Before I came across this toolkit, I was unable to boot my Dev Ed phone into Bootloader/Recovery mode by pushing those button combos which always took me to the regular phone boot mode... Did you ever have the similar problems with the button combos operation?
jcc266 said:
Thanks for replying. So you did not do the the "Boot into Bootloader" command but went directly to "Flash Recovery" box? By using this toolkit we don't have to get into Bootload or Recovery Mode first (either by using the Commands in the toolkit box or by pushing Volume Up or Down + Power buttons)? Before I came across this toolkit, I was unable to boot my Dev Ed phone into Bootloader/Recovery mode by pushing those button combos which always took me to the regular phone boot mode... Did you ever have the similar problems with the button combos operation?
Click to expand...
Click to collapse
if i remember correctly. when you hit the flash recovery button it will put your phone into bootloader for you. a box will pop up and saying it will do two things, one boot it into bootloader then flash the recovery. two command prompts will open the first one is to boot the phone into the bootloader, you close that one when your phone is in the bootloader then another command prompt will pop up after it to flash the recovery. you cant really go wrong using the toolkit. so if something doesn't work just close out and start again. hope this helps
I have yet to root because I really haven't needed to yet. I am going to use the phone for a few weeks. I got this phone because I wanted to have everything working. Sometimes you get into a viscous cycle of flashing because a custom Rom breaks something then you update to get the fix. Then that breaks something else lol. I will be rooting my phone, but thought I would just wait. We now have all the files(RUU) to return to stock if needed so the time is closer than later. It is a great phone, super nice I haven't had any issues. It has been awesome. I will say mikes Rom does sound super sweet.
Sent from my HTC One using xda premium
Related
Please try this and report back. The following procedure worked on a brand new Desire S with S-ON so I am assuming it will work on incredible as well.
With phone on go to:
Settings/Power/
Uncheck "fast Boot"
exit settings
Turn phone off
Boot with Power and volume down
wait
select "Recovery"
hit power to select
wait
you will now get a stupid icon on screen that won't go away
hit power and volume up
you should now be in recovery
From here you should be able to install a ROM as long as it is signed.
You may also be able to do some hackery if plugged into usb while in this screen using ADB or Fastboot. Please try and report back.
Best
Ty
Ref:http://forum.xda-developers.com/showthread.php?p=13216354#post13216354
Confirmed working.
Tried is on my S-ON IS.
You get into Android Recovery <3e> =)
Technically it should be possible to debrand a network branded handset with a P***.zip file on an sdcard?? Or am i barking up the wrong tree?
Yep, S-ON IS will boot into recovery using this method. Though I haven't flashed a ROM or tried any 'hackery' as yet.
Thanks for posting back with confirmation.
Hopefully some folks with some badass adb-foo will hit back with some test results on using adb or fastboot in this mode.
I am sure "fastboot oem unlock" won't work but one can dream.
Hope someone can try simply running these 2 commands in the recovery mode:
adb devices
and
fastboot devices
and let us know if either work.
Ty
Won't work, fastboot doesn't recognize it and adb is disabled in HTC recovery, I thought (but not sure) that usb is disabled completely. Almost everything has been tried to hack the recovery. But it checks the files to many times, so exploits through scripts doesn't work. It checks the file's signature before flashing and since hijacking cannot be done it will be one hell of a job. A lot of high skilled hackers tried it already for a month almost non-stop.
But if you can come up with a way to exploit, your the god in here haha
So its Not possible to sign a custom ROM? Apks Care able, so why no Rom?
shared from my HTC IncS using the xda app
Yes, it work but it show "E:Can't open /cache/recovery/command"
what's wrong on my device?
yes works on bell/canada s-on is now can someone post virgin gb update zip pls
erhm sorry for being a partypooper but, this is totally normal that u can enter recovery....
Leave it to hawky to make it short and simple
Sent from my HTC Incredible S using XDA App
You can sign a Rom, but it is not signed with HTC's key, they keep it private, the device has a public key within it, which can see if its from HTC, go look at a wiki about public and private keys/signing. Will make it a lot clearer!
So no use
Big step! I think we are closer to root!
Recovery working on my IS S-On, hope some devs will be able to make something for IS soon....
It's no step at all.... This is already known and found useless. Unless HTC releases signed s-off bootloader. So this "discovery" is already known and not worth anything
I think bruce needs another 20 steps, maybe than he realises he actually moved sidewards instead LOL
Sent from my HTC Incredible S using XDA Premium App
Hawkysoft said:
I think bruce needs another 20 steps, maybe than he realises he actually moved sidewards instead LOL
Sent from my HTC Incredible S using XDA Premium App
Click to expand...
Click to collapse
root has already been found. but it's costly. XTC Clip. I'm luckily beta tester and will be getting 5 extra clips to S-OFF any android phone... holla
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.
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
Hey guys, I need some help, also Im new to this sorta and I apologize if this thread isnt where its supposed to be, anywho i rooted my phone and was installing different roms, just trying them out, i had installed the android rev HD 12.1 rom on to my HTC One and it was working fine, but I watched a couple of reviews on the viperone roms so i decided to switch over just to check it out, i started the flashing and all was going well at first but then it froze for a good while stuck at 0% so i decided to restart the phone... turns out that was a horrible idea because now my back ups are gone and my other roms are missing too. well that was the original problem, I looked around and everywhere they said I had to reinstall my ruu to basically factory reset the phone and the first step is re-locking the bootloader... so i did, now it says "tampered- re-locked" and every now and then it says "security warning." then i started looking for my comapnies ruu and i cant find one... can anyone help?
i forgot to mention i have a T-Mobile HTC One.
kawazami said:
Hey guys, I need some help, also Im new to this sorta and I apologize if this thread isnt where its supposed to be, anywho i rooted my phone and was installing different roms, just trying them out, i had installed the android rev HD 12.1 rom on to my HTC One and it was working fine, but I watched a couple of reviews on the viperone roms so i decided to switch over just to check it out, i started the flashing and all was going well at first but then it froze for a good while stuck at 0% so i decided to restart the phone... turns out that was a horrible idea because now my back ups are gone and my other roms are missing too. well that was the original problem, I looked around and everywhere they said I had to reinstall my ruu to basically factory reset the phone and the first step is re-locking the bootloader... so i did, now it says "tampered- re-locked" and every now and then it says "security warning." then i started looking for my comapnies ruu and i cant find one... can anyone help?
i forgot to mention i have a T-Mobile HTC One.
Click to expand...
Click to collapse
Basically, if you want to stay back on root, i suggest you unlock your bootloader again and reflash your custom recovery and move on from there. After that you should flash a stock rom if you want to,by just searching it up in the htc one forums. After you have done that you probably have to start over, which means making a nandroid backup and NOT FORGETTING TO BACK UP. Your roms and all your info will be gone after you unlock the bootloader so remember to back up all your contacts and such into your google acc. Have fun rooting! XD
Bllooi said:
Basically, if you want to stay back on root, i suggest you unlock your bootloader again and reflash your custom recovery and move on from there. After that you should flash a stock rom if you want to,by just searching it up in the htc one forums. After you have done that you probably have to start over, which means making a nandroid backup and NOT FORGETTING TO BACK UP. Your roms and all your info will be gone after you unlock the bootloader so remember to back up all your contacts and such into your google acc. Have fun rooting! XD
Click to expand...
Click to collapse
This is probably the best advice for you.
Just something I wanted to add,
Unlock your boot loader then flash a custom recovery just like the first time you did it.
Then boot to recovery and "adb push ROM.zip /sdcard/ " to get a ROM on your phone, and flash away.
AT&T HTC One
GPe 4.3
CoryTallman said:
This is probably the best advice for you.
Just something I wanted to add,
Unlock your boot loader then flash a custom recovery just like the first time you did it.
Then boot to recovery and "adb push ROM.zip /sdcard/ " to get a ROM on your phone, and flash away.
AT&T HTC One
GPe 4.3
Click to expand...
Click to collapse
He could also use hassoon2000 's kit if that's too hard for him.
Can someone send me a link to bassoon2000 all in one kit?
Sent from my HTCONE using XDA Premium 4 mobile app
rhydrag83 said:
Can someone send me a link to bassoon2000 all in one kit?
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Search for it, I think its under the main htc one general. Stay away from RUU unless you have s-off. You can brick your phone if you don't know what your doing.
Hi i have a problem i cannot flash a custom recovery i open the bootloader and flash the recovery.
when i try to flash recovery its pool me out to htc logo please help
an0ther said:
Search for it, I think its under the main htc one general. Stay away from RUU unless you have s-off. You can brick your phone if you don't know what your doing.
Click to expand...
Click to collapse
I did a search. The thread I came across said that the link was removed.
Sent from my HTCONE using XDA Premium 4 mobile app
rhydrag83 said:
I did a search. The thread I came across said that the link was removed.
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You just need to unlock your bootloader again using htc developer page. As long as you can get your phone to bootloader you should be ok. I have never used one of the all in one root etc.. things since it is so easy on htc.
unlock bootloader, fastboot flash recovery newesttwrp.img.
Ok here goes, I unlocked my phone flash viper ROM I remember it like yesterday then the new ota update came out flash the ruu to back to stock everything was fine updated the phone unlocked the phone both on win8 and win 7 but I can't flash a custom recovery, any tips are great
Sent from my GT-N8000 using xda app-developers app
Grab a copy of TWRP or CWM recoveries, links are available in original dev section. Put it in the same folder as ADB - which you used in the console/terminal/command line to unlock the phone. Fire up ADB in console, just as you did to unlock the phone, and type:
adb reboot-bootloader
Your phone should go to that white screen with colorful text. Next type:
fastboot flash recovery nameOfRecoveryImage.img
As long as you're unlocked, which you are, this should work flawlessly.
cant get phone to load
I tried to install the maximushd 12.1 on my sprint htc one. I tried to do it thru twrp recovery and now the phone only loads to boot loader. Any suggestions to get the phone back working. I was using viper rom at the time.
I'm going to assume maximushd is some rom for the international HTC One. I would highly recommend against flashing international roms for obvious reasons.
Either way, RUU the phone. If you're on the new firmware (1.31), you'll need to listen to this guy. Then download the 1.29 RUU from one of the dev sections, wherever the hell it is. Then everything will be back to how it was the day you bought it. Then, just do it all again but don't **** it up - ha.
edit: I just reread, you can't get to the recovery from the bootloader? If all you did was install an international rom, you should still be able to access recovery unless twrp has the ability to repartition, which I suppose it possible. I'll do some reading.
edit2: Others were able to fix the problem utilizing the method I outlined. One of them even links directly to the guide above. Should work alright.
sshede said:
I'm going to assume maximushd is some rom for the international HTC One. I would highly recommend against flashing international roms for obvious reasons.
Either way, RUU the phone. If you're on the new firmware (1.31), you'll need to listen to this guy. Then download the 1.29 RUU from one of the dev sections, wherever the hell it is. Then everything will be back to how it was the day you bought it. Then, just do it all again but don't **** it up - ha.
edit: I just reread, you can't get to the recovery from the bootloader? If all you did was install an international rom, you should still be able to access recovery unless twrp has the ability to repartition, which I suppose it possible. I'll do some reading.
edit2: Others were able to fix the problem utilizing the method I outlined. One of them even links directly to the guide above. Should work alright.
Click to expand...
Click to collapse
Thanks I will try not to screw it up this time
---------- Post added at 04:46 PM ---------- Previous post was at 04:31 PM ----------
sshede said:
I'm going to assume maximushd is some rom for the international HTC One. I would highly recommend against flashing international roms for obvious reasons.
Either way, RUU the phone. If you're on the new firmware (1.31), you'll need to [URL="http://forum.xda-developers.com/showthread.php?t=2390821"listen to this guy[/URL]. Then download the 1.29 RUU from one of the dev sections, wherever the hell it is. Then everything will be back to how it was the day you bought it. Then, just do it all again but don't **** it up - ha.
edit: I just reread, you can't get to the recovery from the bootloader? If all you did was install an international rom, you should still be able to access recovery unless twrp has the ability to repartition, which I suppose it possible. I'll do some reading.
edit2: Others were able to fix the problem utilizing the method I outlined. One of them even links directly to the guide above. Should work alright.
Click to expand...
Click to collapse
I cannot get into recovery. It just keeps going in a vicious cycle. I can choose fastboot or recovery but noting happens.
Did you try to flash a new one with fastboot? fastboot will work in the bootloader.
sshede said:
Did you try to flash a new one with fastboot? fastboot will work in the bootloader.
Click to expand...
Click to collapse
my computer won't recognize the phone as usb
I'll give a try when I can, thanks man
After I did ruu I still had s-off do you that make a big difference
Sent from my HTCONE using xda app-developers app
skevin101 said:
I tried to install the maximushd 12.1 on my sprint htc one. I tried to do it thru twrp recovery and now the phone only loads to boot loader. Any suggestions to get the phone back working. I was using viper rom at the time.
Click to expand...
Click to collapse
Just a quick pro-tip for you... if you didn't find the ROM in this forum (because you didn't) then DON'T FLASH IT!
If you found it in the international forums (which you did.) DON'T FLASH IT
Next time do a search because about a hundred other people who aren't good at reading before flashing have done it too.
felacio said:
Just a quick pro-tip for you... if you didn't find the ROM in this forum (because you didn't) then DON'T FLASH IT!
If you found it in the international forums (which you did.) DON'T FLASH IT
Next time do a search because about a hundred other people who aren't good at reading before flashing have done it too.
Click to expand...
Click to collapse
granted I didn't follow the instructions. that's what I get for thinking I know what im doing. just because ive flashed some before. but I didn't realize this was an international forum ( http://forum.xda-developers.com/forumdisplay.php?f=2115&nocache=1&z=3553232956118556)
sshede said:
Grab a copy of TWRP or CWM recoveries, links are available in original dev section. Put it in the same folder as ADB - which you used in the console/terminal/command line to unlock the phone. Fire up ADB in console, just as you did to unlock the phone, and type:
adb reboot-bootloader
Your phone should go to that white screen with colorful text. Next type:
fastboot flash recovery nameOfRecoveryImage.img
As long as you're unlocked, which you are, this should work flawlessly.
Click to expand...
Click to collapse
i uninstalled the drivers install them used different usb port, phone does say fastboot usb and shows up in fastboot devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found