Hi There,
I searched the threads available to the best of my ability, but im not sure exactly what im looking for. Purchased an HTC one used, flashed with cyanogenmod 10.2. When I tried to update it to 11, it soft bricked (im assuming) as it cant get past the recovery mode. I factory wiped it, in my ignorance thinking this would be able to fix the issue, boot up the stock rom. This cleared the OS so I was more stuck then I previously was.
I figured out how to push roms onto it, and I got the new android revolution rom on there, and when i install it, it says its successful as it goes through all the rom specific steps, but when it system reboots it goes back into this loop.
Are there any suggestions to get out of this? Should i somehow flash the latest RUU?
Thanks a lot I appreciate any help
bronsonb said:
Hi There,
I searched the threads available to the best of my ability, but im not sure exactly what im looking for. Purchased an HTC one used, flashed with cyanogenmod 10.2. When I tried to update it to 11, it soft bricked (im assuming) as it cant get past the recovery mode. I factory wiped it, in my ignorance thinking this would be able to fix the issue, boot up the stock rom. This cleared the OS so I was more stuck then I previously was.
I figured out how to push roms onto it, and I got the new android revolution rom on there, and when i install it, it says its successful as it goes through all the rom specific steps, but when it system reboots it goes back into this loop.
Are there any suggestions to get out of this? Should i somehow flash the latest RUU?
Thanks a lot I appreciate any help
Click to expand...
Click to collapse
what recovery are you using? what version?
also post a fastboot getvar all wihout imei/sn
alray said:
what recovery are you using? what version?
also post a fastboot getvar all wihout imei/sn
Click to expand...
Click to collapse
Im using TWRP 2.5.0.0, and im trying to run the fastboot getvar but its stuck on <waiting for device> ill post an update if that changes, thank you for your response!
bronsonb said:
Im using TWRP 2.5.0.0, and im trying to run the fastboot getvar but its stuck on <waiting for device> ill post an update if that changes, thank you for your response!
Click to expand...
Click to collapse
You must use latest twrp version to flash arhd rom! 2.5.0.0 is very outdated.
Are you using a windows 8.1 computer? If yes then you miht have issue with fastboot.
and make sur your phone variant is M7_U or M7_UL in bootloader screen. (not a sprint version M7wls)
What is the hboot version in bootloader screen?
from the OP of arhd thread:
Android Revolution HD 51.0
--- MD5 Checksum: 1F9253A64D5B0A0566C8B40EC809D05F ---
You need TRWP 2.6.3.3 recovery!
Flashing KitKat F.A.Q. - click here
Click to expand...
Click to collapse
alray said:
You must use latest twrp version to flash arhd rom! 2.5.0.0 is very outdated.
Are you using a windows 8.1 computer? If yes then you miht have issue with fastboot.
and make sur your phone variant is M7_U or M7_UL in bootloader screen. (not a sprint version M7wls)
What is the hboot version in bootloader screen?
Click to expand...
Click to collapse
I had no idea, Ill figure out how to do that right away I really appreciate that.
Im using a mac actually, so i understand everything isnt really made to work with it, though i can use parallels windows 7 if necessary
it shows:
TAMPERED
UNLOCKED
M7_UL PVT SHIP S-ON RH
HBOOT - 1.44.0000
bronsonb said:
I had no idea, Ill figure out how to do that right away I really appreciate that.
Im using a mac actually, so i understand everything isnt really made to work with it, though i can use parallels windows 7 if necessary
it shows:
TAMPERED
UNLOCKED
M7_UL PVT SHIP S-ON RH
HBOOT - 1.44.0000
Click to expand...
Click to collapse
ok so flash twrp 2.6.3.3 and reflash your rom.
Code:
./fastboot flash recovery <name_of_file>.img
./fastboot erase cache
./fastboot reboot-bootloader
then flash arhd again.
alray said:
ok so flash twrp 2.6.3.3 and reflash your rom.
Code:
./fastboot flash recovery <name_of_file>.img
./fastboot erase cache
./fastboot reboot-bootloader
then flash arhd again.
Click to expand...
Click to collapse
is there a line of code to flash the rom through fastboot, rather then rebooting recovery and installing it?
bronsonb said:
is there a line of code to flash the rom through fastboot, rather then rebooting recovery and installing it?
Click to expand...
Click to collapse
No, you'll need a custom recovery to flash a rom.
or
Use a ruu to restore back to 100% stock but you will need to post a ''fastboot getvar all'' to determine if this is possible.
What is going wrong?
You can also post screenshots of you terminal window when you get errors.
alray said:
No, you'll need a custom recovery to flash a rom.
or
Use a ruu to restore back to 100% stock but you will need to post a ''fastboot getvar all'' to determine if this is possible.
What is going wrong?
You can also post screenshots of you terminal window when you get errors.
Click to expand...
Click to collapse
Actually, I just installed it through the newly flashed recovery and it worked perfectly (Android Revolution)
Thank you so much! Saved me a lot of time
bronsonb said:
Actually, I just installed it through the newly flashed recovery and it worked perfectly (Android Revolution)
Thank you so much! Saved me a lot of time
Click to expand...
Click to collapse
np
Related
Hey I tried installing a 4.4 rom, got a boot loop recovery keeps crashing and I can get into fastboot now.
The computer is recognizing the phone and I can use fastboot to flash a new recovery but CWM and TWRP recoveries continue to crash on reboot... What can I do?
S-On or s-off ?
either way your best bet is an RUU. the GPE RUU if your s-off or the proper carrier/region RUU if your s-on.
mopardroid said:
Hey I tried installing a 4.4 rom, got a boot loop recovery keeps crashing and I can get into fastboot now.
The computer is recognizing the phone and I can use fastboot to flash a new recovery but CWM and TWRP recoveries continue to crash on reboot... What can I do?
Click to expand...
Click to collapse
ipfreelytech said:
S-On or s-off ?
either way your best bet is an RUU. the GPE RUU if your s-off or the proper carrier/region RUU if your s-on.
Click to expand...
Click to collapse
Thank you for the reply, I believe it is s-On the top of the bootloader screen shows tampered & unlocked..
if it doesn't say s-off and you don't remember doing S-off then you're s-on.
What is your CID? you'll need to track down an RUU that matches. Also since your s-on you can only go up in versions, not down so you have to match the mainver.
mopardroid said:
Thank you for the reply, I believe it is s-On the top of the bootloader screen shows tampered & unlocked..
Click to expand...
Click to collapse
ipfreelytech said:
if it doesn't say s-off and you don't remember doing S-off then you're s-on.
What is your CID? you'll need to track down an RUU that matches. Also since your s-on you can only go up in versions, not down so you have to match the mainver.
Click to expand...
Click to collapse
Yeah it says S-On, how would I find my CID and mainver from fastboot?
ipfreelytech said:
if it doesn't say s-off and you don't remember doing S-off then you're s-on.
What is your CID? you'll need to track down an RUU that matches. Also since your s-on you can only go up in versions, not down so you have to match the mainver.
Click to expand...
Click to collapse
Alright I found my CID: TELUS001 and main version: 1.29.661.5..
mopardroid said:
Yeah it says S-On, how would I find my CID and mainver from fastboot?
Click to expand...
Click to collapse
fastboot getvar all
dingdong3000 said:
fastboot getvar all
Click to expand...
Click to collapse
I cant find any RUU's that match that Main version # but I found a nandroid with the matching CID and Mainver.. is there anything I can do with that?
ipfreelytech said:
if it doesn't say s-off and you don't remember doing S-off then you're s-on.
What is your CID? you'll need to track down an RUU that matches. Also since your s-on you can only go up in versions, not down so you have to match the mainver.
Click to expand...
Click to collapse
Ok so I used fastboot to flash a bunch of different recoveries the only recoveries that will work are the CWM Sprint and TWRP sprint recoveries.. I can get into the recovery without it crashing but I am stuck there... I have tried to adb push a rom to the phone, that worked then the install failed.. any suggestions?
mopardroid said:
I cant find any RUU's that match that Main version # but I found a nandroid with the matching CID and Mainver.. is there anything I can do with that?
Click to expand...
Click to collapse
What hboot do you have
1. Download a fresh copy of the latest twrp 2.6.3.3 from here ------> http://techerrata.com/browse/twrp2/m7
2. Throw that recovery image into your fastboot folder and rename it twrp
Fastboot erase cache
Fastboot flash recovery twrp.img
Fastboot erase cache
Fastboot reboot-bootloader
Sometimes that erase cache command does the trick
Sent from my HTC One using Tapatalk
Sent from my HTC One using Tapatalk
InflatedTitan said:
What hboot do you have
1. Download a fresh copy of the latest twrp 2.6.3.3 from here ------> http://techerrata.com/browse/twrp2/m7
2. Throw that recovery image into your fastboot folder and rename it twrp
Fastboot erase cache
Fastboot flash recovery twrp.img
Fastboot erase cache
Fastboot reboot-bootloader
Sometimes that erase cache command does the trick
Sent from my HTC One using Tapatalk
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thank you very much I will give that a shot in just a moment. I checked my Hboot and it is 1.44. This is killing me I really appreciate the help.
InflatedTitan said:
What hboot do you have
1. Download a fresh copy of the latest twrp 2.6.3.3 from here ------> http://techerrata.com/browse/twrp2/m7
2. Throw that recovery image into your fastboot folder and rename it twrp
Fastboot erase cache
Fastboot flash recovery twrp.img
Fastboot erase cache
Fastboot reboot-bootloader
Sometimes that erase cache command does the trick
Sent from my HTC One using Tapatalk
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
That recovery worked without crashing. ADB is recognizing the device.. im going to sideloading a rom now, is there something else worth trying if that doesnt work?
mopardroid said:
That recovery worked without crashing. ADB is recognizing the device.. im going to sideloading a rom now, is there something else worth trying if that doesnt work?
Click to expand...
Click to collapse
Not really bro. Try to sideload any ROM, I'd shoot for a GE ROM since its a little smaller. As soon as you can get into an OS I hope you try to s-off lol. If you were s-off your problem would be fixed
Sent from my HTC One using Tapatalk
InflatedTitan said:
Not really bro. Try to sideload any ROM, I'd shoot for a GE ROM since its a little smaller. As soon as you can get into an OS I hope you try to s-off lol. If you were s-off your problem would be fixed
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Well sideload got to 100% then the phone shut off and when I turned it back on it just looped back into recovery again... going to try again :/ hope it works
InflatedTitan said:
Not really bro. Try to sideload any ROM, I'd shoot for a GE ROM since its a little smaller. As soon as you can get into an OS I hope you try to s-off lol. If you were s-off your problem would be fixed
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thank you SO much man its finally working and I can go to bed honestly I really appreciate the time you took to help!
I was trying to install ViperOne and everything went south. I somehow deleted my OS in the process. ADB is not working it only freezes my computer. I was able to ADB Push my viperone.zip but I tried the install and it fail for some reason and now it seems to be in a boot loop please help me with this.
also
i have been read all threads on here and there not really helping. just want to put that out there so i dont get called lazy for not searching.
1. Fix ADB issues.
SaHiLzZ said:
1. Fix ADB issues.
Click to expand...
Click to collapse
not sure of the reason for the freezing om the computer.
MuskRat40 said:
not sure of the reason for the freezing om the computer.
Click to expand...
Click to collapse
without adb you can't do anything.
please tell us more about what you did? What recovery are you using? What version? What rom version (and link please)? also post the output of ''fastboot getvar all'' minus IMEI/SN when in bootloader.
and what operating system are you using on your computer?
alray said:
without adb you can't do anything.
please tell us more about what you did? What recovery are you using? What version? What rom version (and link please)? also post the output of ''fastboot getvar all'' minus IMEI/SN when in bootloader.
and what operating system are you using on your computer?
Click to expand...
Click to collapse
***TAMPERED***
***UNLOCKED***
M7_UL PUT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.62.206.1
eMMC-BOOT 2048MB
I rooted my phone with the Hasoon2000 AIO kit
downloaded ViperOne5.5.0 from the link Here on XDA
I tried to install said ROM but it said it failed
so i thought I might delete a few thing and trying to rush because im at a library my OS was one of the things to go.
ADB pushed Viper back onto phone tried to install again and failed
tried to reboot and its a loop only thing opening now is fastboot and hboot
recovery flashes on for a sec then its gone.
fastboot erase cache did let me back into recovery but will not install
ViperOne v5.5.0 install failed
installer status 7
MuskRat40 said:
I rooted my phone with the Hasoon2000 AIO kit
Click to expand...
Click to collapse
Never use toolkit, learn how to use adb and fasboot. Toolkit are for lazy ppl imo. When something goes wrong with a toolkit then you can't know why.
MuskRat40 said:
downloaded ViperOne5.5.0 from the link Here on XDA
Click to expand...
Click to collapse
Did you downloaded the M7 version of viperone or the sprint version?
MuskRat40 said:
I tried to install said ROM but it said it failed
so i thought I might delete a few thing and trying to rush because im at a library
Click to expand...
Click to collapse
Take your time and don't rush, you will make things worse.
please answer all my questions:
please tell us more about what you did? What recovery are you using? What version? What rom version (and link please)? also post the output of ''fastboot getvar all'' minus IMEI/SN when in bootloader.
and what operating system are you using on your computer?
Click to expand...
Click to collapse
erase cache and flash latest twrp (2.6.3.3 or 2.6.3.4)
then use adb to push rom to sdcard or adb sideload your rom.
---------- Post added at 04:15 PM ---------- Previous post was at 04:07 PM ----------
MuskRat40 said:
fastboot erase cache did let me back into recovery but will not install
ViperOne v5.5.0 install failed
installer status 7
Click to expand...
Click to collapse
make sure you are using the correct recovery for your phone variant
md5 checksum the recovery.img after download before you flash it
also md5 checksum the rom before pushing it to the phone
did you selected ''full wipe'' at the installation?
alray said:
Never use toolkit, learn how to use adb and fasboot. Toolkit are for lazy ppl imo. When something goes wrong with a toolkit then you can't know why.
Did you downloaded the M7 version of viperone or the sprint version?
Take your time and don't rush, you will make things worse.
please answer all my questions:
erase cache and flash latest twrp (2.6.3.3 or 2.6.3.4)
then use adb to push rom to sdcard or adb sideload your rom.
Click to expand...
Click to collapse
right now im usind twrp touch v2.6.0.1 i downloaded the m7 verson and the tool is not getting the other stuff
alray said:
Never use toolkit, learn how to use adb and fasboot. Toolkit are for lazy ppl imo. When something goes wrong with a toolkit then you can't know why.
Did you downloaded the M7 version of viperone or the sprint version?
Take your time and don't rush, you will make things worse.
please answer all my questions:
erase cache and flash latest twrp (2.6.3.3 or 2.6.3.4)
then use adb to push rom to sdcard or adb sideload your rom.
---------- Post added at 04:15 PM ---------- Previous post was at 04:07 PM ----------
make sure you are using the correct recovery for your phone variant
md5 checksum the recovery.img after download before you flash it
also md5 checksum the rom before pushing it to the phone
did you selected ''full wipe'' at the installation?
Click to expand...
Click to collapse
md5?? not sure how to do that
MuskRat40 said:
right now im usind twrp touch v2.6.0.1 i downloaded the m7 verson and the tool is not getting the other stuff
Click to expand...
Click to collapse
your recovery version is pretty out dated.
as i said before, don't use toolkit, you know why now...
download latest twrp recovery here
Code:
fastboot flash recovery <name_of_file>.img
fastboot erase cache
fastboot reboot-bootloader
then go back in recovery and flash the rom again and select full wipe.
alray said:
your recovery version is pretty out dated.
as i said before, don't use toolkit, you know why now...
download latest twrp recovery here
Code:
fastboot flash recovery <name_of_file>.img
fastboot erase cache
fastboot reboot-bootloader
then go back in recovery and flash the rom again and select full wipe.
Click to expand...
Click to collapse
you are the man!!! TWRP was out dated. It says it was successful. its loading now. Thank you so much.
MuskRat40 said:
you are the man!!! TWRP was out dated. It says it was successful. its loading now. Thank you so much.
Click to expand...
Click to collapse
np, glad it worked
hope you learned this:
don't use toolkit
don't rush
newer roms don't like old recoveries (especially 4.4 roms) So in the future be sure to update your recovery to latest version (or that one specified in the rom thread) before flashing.
hope you'll enjoy your new rom :highfive:
Hi Everyone
While trying to unroot my one i eventually got stuck on my bootloader. What happened was that I typed in "fastboot oem lock" in adb and now I can't go into recovery or reboot. I know I should install a RUU at this point but I can't find an RUU for my phone! When I get "fastboot getvar all" I see that my "version-main" is 3.23.666.1 (is that the right one to look at?) and so I've scoured for hours for an RUU but only found OTAs which I don't know how to use. If it helps I'm on HBOOT 1.55.
I also remember pressing unroot in OTA unroot (I don't remember the exact app name) and tried pressing restore root but it did nothing so I started doing the above stuff with RUUs.
I'm pretty stumped right now and I would appreciate any help at all, thank you!
KoalaSuccess said:
Hi Everyone
While trying to unroot my one i eventually got stuck on my bootloader. What happened was that I typed in "fastboot oem lock" in adb and now I can't go into recovery or reboot. I know I should install a RUU at this point but I can't find an RUU for my phone! When I get "fastboot getvar all" I see that my "version-main" is 3.23.666.1 (is that the right one to look at?) and so I've scoured for hours for an RUU but only found OTAs which I don't know how to use. If it helps I'm on HBOOT 1.55.
I also remember pressing unroot in OTA unroot (I don't remember the exact app name) and tried pressing restore root but it did nothing so I started doing the above stuff with RUUs.
I'm pretty stumped right now and I would appreciate any help at all, thank you!
Click to expand...
Click to collapse
If you have an unlocktoken flash it with fastboot flashunlocktoken Unlock_code.bin
If you dont have it, go to htcdev.com and visit unlock bootloader section and follow instructions there.
Once your bootloader is unlocked again, flash twrp recovery and ABD sideload some ROM.
After this you can start all over again whatever it is you were trying to do.
P.S. this will not get you the right RUU package but it will get your phone back to useful condition.
My advice is first you find an RUU for your phone and then do the bootloader manipulations.
7ftnick said:
If you have an unlocktoken flash it with fastboot flashunlocktoken Unlock_code.bin
If you dont have it, go to htcdev.com and visit unlock bootloader section and follow instructions there.
Once your bootloader is unlocked again, flash twrp recovery and ABD sideload some ROM.
After this you can start all over again whatever it is you were trying to do.
P.S. this will not get you the right RUU package but it will get your phone back to useful condition.
My advice is first you find an RUU for your phone and then do the bootloader manipulations.
Click to expand...
Click to collapse
Thanks for the reply! I did that and my phone was working fine again. I went to go flash a stock rom that I found and it flashed fine but now the NFC logo flashes in the status bar even though it's not on. Also, my wifi doesn't work! It constantly says turning on wifi.. I'm trying to flash a different stock rom but I can't enter recovery anymore I would be fine except no wifi is a bit of a problem. Thank you for the reply by the way, is there a chance you can help me find an RUU for my phone? I've searched everywhere but there doesn't seem to be one.
KoalaSuccess said:
Thanks for the reply! I did that and my phone was working fine again. I went to go flash a stock rom that I found and it flashed fine but now the NFC logo flashes in the status bar even though it's not on. Also, my wifi doesn't work! It constantly says turning on wifi.. I'm trying to flash a different stock rom but I can't enter recovery anymore I would be fine except no wifi is a bit of a problem. Thank you for the reply by the way, is there a chance you can help me find an RUU for my phone? I've searched everywhere but there doesn't seem to be one.
Click to expand...
Click to collapse
There is no RUU for Bell devices. Have you checked my restore to stock for canadian users thread? Post #1 should be ok for you
SaHiLzZ said:
There is no RUU for Bell devices. Have you checked my restore to stock for canadian users thread? Post #1 should be ok for you
Click to expand...
Click to collapse
I took a look and I'll try it! Do you know if my device is Bell? I'm not sure how to tell.
SaHiLzZ said:
There is no RUU for Bell devices. Have you checked my restore to stock for canadian users thread? Post #1 should be ok for you
Click to expand...
Click to collapse
So I managed to get my phone working again thanks to your guide! but once I went in to get my S-OFF the program got stuck on pouring 2 after I left it for an hour I hard reset my phone and now I can't boot into recovery or main OS, just bootloader. But in bootloader I see at the top that it says my phone is S-OFF but I can't do the remove tampered because I can't use adb because I can't boot into main OS! I've tried flashing different recovery TWRP but it isn't changing anything..
Any help would be greatly appreciated
KoalaSuccess said:
So I managed to get my phone working again thanks to your guide! but once I went in to get my S-OFF the program got stuck on pouring 2 after I left it for an hour I hard reset my phone and now I can't boot into recovery or main OS, just bootloader. But in bootloader I see at the top that it says my phone is S-OFF but I can't do the remove tampered because I can't use adb because I can't boot into main OS! I've tried flashing different recovery TWRP but it isn't changing anything..
Any help would be greatly appreciated
Click to expand...
Click to collapse
did you erased cache after flashing the recovery?
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
then try to boot in recovery again.
alray said:
did you erased cache after flashing the recovery?
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
then try to boot in recovery again.
Click to expand...
Click to collapse
Yeah I did try to erase cache, no luck. but I managed to fix it by turning my S-OFF back to S-ON by typing fastboot oem writesecureflag 3
after that I flashed twrp again and then i was able to boot up to OS again. Thanks for the help everyone!
KoalaSuccess said:
Yeah I did try to erase cache, no luck. but I managed to fix it by turning my S-OFF back to S-ON by typing fastboot oem writesecureflag 3
after that I flashed twrp again and then i was able to boot up to OS again. Thanks for the help everyone!
Click to expand...
Click to collapse
well that is strange, you should have kept s-off and try other things first but well, its to late. At least your phone is working now
Hello. im new here and i ive just bricked my phone , and i wana get back to stock RUU and i dont know whick RUU to download anny sollutions how to check what RUU do i need? Ps.sorry for my bad english. Anny help would be awesome
ubas98 said:
Hello. im new here and i ive just bricked my phone , and i wana get back to stock RUU and i dont know whick RUU to download anny sollutions how to check what RUU do i need? Ps.sorry for my bad english. Anny help would be awesome
Click to expand...
Click to collapse
post the ouput of "fastboot getvar all" except the IMEI and SERIALNO so we can help you determine which RUU you can use if any available for your phone.
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.27.3218.14
OpenDSP -v32.120.274.0909
OS-5.16.161.2 eMMC-boot 2048MB
Ive writed everything that i saw on my screen.if i mised anything please tell me
ubas98 said:
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.27.3218.14
OpenDSP -v32.120.274.0909
OS-5.16.161.2 eMMC-boot 2048MB
Ive writed everything that i saw on my screen.if i mised anything please tell me
Click to expand...
Click to collapse
that's not your fastboot getvar all, however, the most important part is there which is your OS number, 5.16.161.2 is Vodafone, there is no RUU for your device, do you not have a backup ? how did you brick ?
Seanie280672 said:
that's not your fastboot getvar all, however, the most important part is there which is your OS number, 5.16.161.2 is Vodafone, there is no RUU for your device, do you not have a backup ? how did you brick ?
Click to expand...
Click to collapse
well ive wanted to get to stock so i unlocked my bootloader and tried to install ruu but it failed. and because i locked the bootloader ive somehow bricked my phone one cm11 loading screen. ive unlocked my bootloader and my recovery was all mesed up it couldnt load anny storage so i cant instal other rooms so im stuck here .i have no clue what to do
ubas98 said:
well ive wanted to get to stock so i unlocked my bootloader and tried to install ruu but it failed. and because i locked the bootloader ive somehow bricked my phone one cm11 loading screen. ive unlocked my bootloader and my recovery was all mesed up it couldnt load anny storage so i cant instal other rooms so im stuck here .i have no clue what to do
Click to expand...
Click to collapse
well as your s-on, you can forget about any RUU's at all for now.
I would recommend you flash twrp recovery, use 2.6.3.3 and then erase cache, then reboot bootloader (see commands below).
Code:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
after that go into twrp recovery and select wipe then format data, this will completely wipe your phone of everything, but as its already messed up then it doesn't really matter, does it.
once that is done, download a sense rom from the development section and try and push it to your internal sdcard, if successful then flash it.
Seanie280672 said:
well as your s-on, you can forget about any RUU's at all for now.
I would recommend you flash twrp recovery, use 2.6.3.3 and then erase cache, then reboot bootloader (see commands below).
Code:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
after that go into twrp recovery and select wipe then format data, this will completely wipe your phone of everything, but as its already messed up then it doesn't really matter, does it.
once that is done, download a sense rom from the development section and try and push it to your internal sdcard, if successful then flash it.
Click to expand...
Click to collapse
well everything worked but when i enter recovery mode it askes me a pasword and i dont know it anny solution?
ubas98 said:
well everything worked but when i enter recovery mode it askes me a pasword and i dont know it anny solution?
Click to expand...
Click to collapse
password ? never seen that before, could you post a photo of it ?
Seanie280672 said:
password ? never seen that before, could you post a photo of it ?
Click to expand...
Click to collapse
http://postimg.org/image/ucolu3a83/ here is the img
ubas98 said:
http://postimg.org/image/ucolu3a83/ here is the img
Click to expand...
Click to collapse
I have never seen that before in all my years of using TWRP, maybe one of the other guys can help you with that
Seanie280672 said:
I have never seen that before in all my years of using TWRP, maybe one of the other guys can help you with that
Click to expand...
Click to collapse
maybe i could use another recovery .if yes anny what is other best recovery?
ubas98 said:
maybe i could use another recovery .if yes anny what is other best recovery?
Click to expand...
Click to collapse
oh somehow the pasword screen went out and now im in the recovery in which folder i could trasfer my rom to the phone?
ubas98 said:
oh somehow the pasword screen went out and now im in the recovery in which folder i could trasfer my rom to the phone?
Click to expand...
Click to collapse
adb push it straight to the sdcard, make sure your phone is plugged into the computer and the rom is in the same folder as adb and fastboot files, then issue this command:
Code:
adb push (name of rom).zip /sdcard/
it will look like its not doing anything but will let you know when its done, then uplug your phone before flashing the rom.
and both TWRP and CWM have their good points, you need CWM to flash AOSP rom's and TWRP to flash sense rom's
Seanie280672 said:
well as your s-on, you can forget about any RUU's at all for now.
I would recommend you flash twrp recovery, use 2.6.3.3 and then erase cache, then reboot bootloader (see commands below).
Code:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
after that go into twrp recovery and select wipe then format data, this will completely wipe your phone of everything, but as its already messed up then it doesn't really matter, does it.
once that is done, download a sense rom from the development section and try and push it to your internal sdcard, if successful then flash it.
Click to expand...
Click to collapse
Strangely this is exactly the position I'm in today too.
I wanted to revert to stock after trying cyanogen, relocked the bootloaded and tried to run an RUU. However it stopped with an 'unknown error'. So I tried to push a zip file to it but the adb can't connect to the device and the phone isn't showing up in the device manager (because it's in boot mode?).
I then tried your advice about twrp and tried a different RUU but still get an unknown error and still can't push to the device.
Any ideas of what to try next? My OS is now showing as empty, there was something there previously.
I figured it was time to get some help before I broke things any more.
SGSII_LEDnotify said:
Strangely this is exactly the position I'm in today too.
I wanted to revert to stock after trying cyanogen, relocked the bootloaded and tried to run an RUU. However it stopped with an 'unknown error'. So I tried to push a zip file to it but the adb can't connect to the device and the phone isn't showing up in the device manager (because it's in boot mode?).
I then tried your advice about twrp and tried a different RUU but still get an unknown error and still can't push to the device.
Any ideas of what to try next? My OS is now showing as empty, there was something there previously.
I figured it was time to get some help before I broke things any more.
Click to expand...
Click to collapse
first thing to do is unlock your bootloader again, if you've not already done that, then get TWRP 2.6.3.3 recovery on there, that maybe a problem though as your phone isn't showing in device manager.
So put your phone into the bootloader and see what device manager says then, it should say something if its detecting your phone, even if drivers arnt installed.
also, which HBOOT are you on ? and which Windows OS are you using ?
Seanie280672 said:
first thing to do is unlock your bootloader again, if you've not already done that, then get TWRP 2.6.3.3 recovery on there, that maybe a problem though as your phone isn't showing in device manager.
So put your phone into the bootloader and see what device manager says then, it should say something if its detecting your phone, even if drivers arnt installed.
also, which HBOOT are you on ? and which Windows OS are you using ?
Click to expand...
Click to collapse
I think I've unlocked the bootloader again, fastboot is available and it's showing 'unlocked' at the top. twrp is on there too and I've done the wipe again. The fastboot commands work but pushing doesn't
error: device not found
HBOOT is 1.55.0000 / win7 64 home
Btw Twrp said it couldn't find cache but the wipe was successful.
Thanks for the help.
SGSII_LEDnotify said:
I think I've unlocked the bootloader again, fastboot is available and it's showing 'unlocked' at the top. twrp is on there too and I've done the wipe again. The fastboot commands work but pushing doesn't
error: device not found
HBOOT is 1.55.0000 / win7 64 home
Btw Twrp said it couldn't find cache but the wipe was successful.
Thanks for the help.
Click to expand...
Click to collapse
ok I see what your saying now, what you need to do is boot into TWRP, main screen only, no sub menu's, at that point is your phone still detected in device manager ?
if so then............
put the rom you want to flash in the same folder as adb and fastboot files on your computer, then type:
Code:
adb push (name of rom).zip /sdcard/
you cant push files to your phone using fastboot or whilst its in the bootloader, that's strictly for flashing simple files like Radio's, HBOOTS, recoveries.
Seanie280672 said:
ok I see what your saying now, what you need to do is boot into TWRP, main screen only, no sub menu's, at that point is your phone still detected in device manager ?
if so then............
put the rom you want to flash in the same folder as adb and fastboot files on your computer, then type:
Code:
adb push (name of rom).zip /sdcard/
you cant push files to your phone using fastboot or whilst its in the bootloader, that's strictly for flashing simple files like Radio's, HBOOTS, recoveries.
Click to expand...
Click to collapse
Well at least I've got something in the device manager even if it is a SAMSUNG Android Phone and not my HTC!
The push command hasn't brought up an error, the cursor is just flashing on the next line. It appears to be doing nothing like you said. So I guess I'm playing the waiting game for ten minutes or so. Will there be a notification when it's completed?
---------- Post added at 08:03 PM ---------- Previous post was at 08:00 PM ----------
Ok, transfer complete
SGSII_LEDnotify said:
Well at least I've got something in the device manager even if it is a SAMSUNG Android Phone and not my HTC!
The push command hasn't brought up an error, the cursor is just flashing on the next line. It appears to be doing nothing like you said. So I guess I'm playing the waiting game for ten minutes or so. Will there be a notification when it's completed?
---------- Post added at 08:03 PM ---------- Previous post was at 08:00 PM ----------
Ok, transfer complete
Click to expand...
Click to collapse
ok, unplug your phone, then goto install and select the rom from the list you just pushed, follow the Aroma options and instructions and also id recommend when given the option, to wipe data.
Seanie280672 said:
ok, unplug your phone, then goto install and select the rom from the list you just pushed, follow the Aroma options and instructions and also id recommend when given the option, to wipe data.
Click to expand...
Click to collapse
I renamed the zip file because there were spaces in the name causing errors, would that cause a failure when trying to install?
skipping MD5 check: no md5 file found
Error flashing zip '/sdcard/****.zip'
updating partition details
failed
Hi guys i got an htc one in placw of my samsung grand
I managed to unlock the bootloader using cmd and tried flashing a recovery. However after the flash when i try booting into recovery mode from bootloader, it first gives the entering recovery screen but then screen blacks out and then it reboots as normal.
Now htc just got a lollipop update and i want to update, but when it enters recovery, it blacks out and then reboots as normal due to the fail recovery
Before i tried flashing each and every reocvery and the same happened... Then i just left it at a version of cwm ( didnt work also) .
Now shall i flash stock recovery? What if that dosent work? Is there any way to do it without a pc or any other computer?
arushawasthi said:
Hi guys i got an htc one in placw of my samsung grand
I managed to unlock the bootloader using cmd and tried flashing a recovery. However after the flash when i try booting into recovery mode from bootloader, it first gives the entering recovery screen but then screen blacks out and then it reboots as normal.
Now htc just got a lollipop update and i want to update, but when it enters recovery, it blacks out and then reboots as normal due to the fail recovery
Before i tried flashing each and every reocvery and the same happened... Then i just left it at a version of cwm ( didnt work also) .
Now shall i flash stock recovery? What if that dosent work? Is there any way to do it without a pc or any other computer?
Click to expand...
Click to collapse
no .. you will need a PC to restore stock recovery / or RUU back to stock
Darn
clsA said:
no .. you will need a PC to restore stock recovery / or RUU back to stock
Click to expand...
Click to collapse
Hi,
Thanks for the reply.
I tried RUU, turns out theres no file for my cid (HTC_039).
I also tried alternate methods, turns out i cant use Guru reset as i need functioning recovery, and i have S-ON so no Nand.
pl help.
arushawasthi said:
Hi,
Thanks for the reply.
I tried RUU, turns out theres no file for my cid (HTC_039).
I also tried alternate methods, turns out i cant use Guru reset as i need functioning recovery, and i have S-ON so no Nand.
pl help.
Click to expand...
Click to collapse
Did you use the correct version of the recovery you flashed? I mean are you sure it wasn't a Sprint or Verizon recovery?
Secondly did you fastboot erase cache after flashing recovery?. This is the no.1 reason for recovery bootloop. Flashing recovery should be done like so.
Code:
fastboot erase cache
fastboot flash recovery "name-of-recovery".img
fastboot reboot-bootloader
Then select recovery from the bootloader for the first time load.
Sent from my M7 ARHD 84-Kitkat
arushawasthi said:
I tried RUU, turns out theres no file for my cid (HTC_039).
Click to expand...
Click to collapse
Yes there is one. 7.19.980.5 posted in the general section
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
see post #2.
If your phone is already on a 6.xx.980.x or 7.xx.980.x firmware you can flash it.
Danny201281 said:
Did you use the correct version of the recovery you flashed? I mean are you sure it wasn't a Sprint or Verizon recovery?
Secondly did you fastboot erase cache after flashing recovery?. This is the no.1 reason for recovery bootloop. Flashing recovery should be done like so.
Code:
fastboot erase cache
fastboot flash recovery "name-of-recovery".img
fastboot reboot-bootloader
Then select recovery from the bootloader for the first time load.
Sent from my M7 ARHD 84-Kitkat
Click to expand...
Click to collapse
Hi,
i didnt do the exact thing. Ill try like you said.
And how do i find out my firmware version? In settings?
arushawasthi said:
Hi,
i didnt do the exact thing. Ill try like you said.
And how do i find out my firmware version? In settings?
Click to expand...
Click to collapse
To find your firmware version it's best to use command
Code:
fastboot getvar all
this will show you a list of your devices version information.
You can post the list here if you need help but please remove your imei and serial number before posting for your own security.
There are 3 models of HTC One.
Sprint = m7_wls Downloads here http://techerrata.com/browse/twrp2/m7wls
Verizion = m7_vzw Downloads here http://techerrata.com/browse/twrp2/m7vzw
International = m7_ul or m7_u Downloads here http://techerrata.com/browse/twrp2/m7
There are also more model numbers for dual sim variants.
You must have the correct version of recovery depending on your model. The getvar info would be very helpful for me to make a recommendation :good:
Sent from my SM-T230 using Tapatalk