Database Develop

my one brickked. pleaase helppp am tired

hi there,
for some stupid reasons I flashed a random rom for my htc one then I couldn't start the fun it stucked at the screen logo
using the fastboot I tried to flash many recoveries including the stock one just to get my sd mount but I couldn't get it
please help me get this fixed
my cid is HTC__332
my modelid: PN0711000
mainver: 1.36.599.1
what I see in the bootloader is
UNLOCKED
M7_U PVT SHIP S-ON RH
please help me

Which error do you have with recovery?
Have you tried to use the stock recovery for do a factory reset and after push a rom into a custom recovery for flash it?

I have tried to flash the stock recovery and made the reset but nothing happened the phone still stucking in the logo screen. I also tried to flash the boot.img but nothing happened.
am trying to get a way to transfer the rom to my phone
I dunno why I cant get it by recovery it says error mount... am sure that my drivers are fine

ok good new I figured a way to transfer the files using adb can now I have the best rom? please be the last one and able to receive updates

mabooz said:
ok good new I figured a way to transfer the files using adb can now I have the best rom? please be the last one and able to receive updates
Click to expand...
Click to collapse
ViperOne is the best for customization and is very stable.
If you wnat something like stock, flash the ARDH...
Mobile Post

Guich said:
ViperOne is the best for customization and is very stable.
If you wnat something like stock, flash the ARDH...
Mobile Post
Click to expand...
Click to collapse
can u provide me a link for the last version

mabooz said:
can u provide me a link for the last version
Click to expand...
Click to collapse
ViperOne
ARHD

i need help i think my device is bricked

okk so i was trying to flash a rom for the first time and i really went at it the wrong way. i didin't backup my original RUU and now my device is stuck on the bootloader screen and i really have no idea what to do. i just want to get an OS running on my phone right now cause im freaking out. my company carrier is rogers and this is what my phone is showing right now:
***tampered***
***relocked***
m7_ul pvt ship s-on rh
hboot-1,55,0000
radio-4a.20.3263.16
opendsp -v32,120.274.0909
os-
emmc-boot 2048mb
i try looking for another ruu to flash in my phone but i cant seem to find one that works with my phone..even when i try using the flashboot getvar command to check for the version this is all i got.. : C:\Users\david\Desktop\sdk-tools>fastboot getvar version-main
version-main:
finished. total time: 0.001s
any help at this point would be greatly appreciated i need to get my phone up working so i can receive my calls
i have managed to bring back recovery mode by re-unlocking it via htcdev..now when the phone boots it goes to the google logo and then the language selecting screen then restarts after 10 secs everytime

Instead of the fastboot command you typed, write:
Code:
fastboot getvar all
Then look for "CID". Search for a RUU for that CID. If you can't find one, we'll discuss other solutions.

fenstre said:
Instead of the fastboot command you typed, write:
Code:
fastboot getvar all
Then look for "CID". Search for a RUU for that CID. If you can't find one, we'll discuss other solutions.
Click to expand...
Click to collapse
this is what i got from the fastboot getvar all command :
C:\Users\david\Desktop\sdk-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA346W904162
(bootloader) imei: 354439050131335
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4290mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-fe1214a4f2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.053s
cidnum says ROGER001? im i don't think ive seen cid what that number around
edit: could it be possible that this is what i need ? "M7 CWM Nandroid Backup / CID ROGER001 / 1.29.631.17"
since i did not make a backup is there a chance i can restore this ? ive tried the method that suggest sideloading but it didn't work or maybe i didin't do it right but it didn't wanna recognize my phone when i tried the command'
edit 2: also, im using twrp instead of cwm if that information can help in any way.

If you can let us know which rom you attempted to install and what you managed to do. Did you install custom recovery etc.

gffmac said:
If you can let us know which rom you attempted to install and what you managed to do. Did you install custom recovery etc.
Click to expand...
Click to collapse
well all i was trying to do was install the goole play edition rom (bigxie_m7_GPe_KRT16S_odexed-signed.zip) but after the installation it kept restarting after the language selection screen. i used twrp to flash the rom. right now all im able to do is cycle through the booloader, the recovery screen and to the language selection screen

Unless you have another rom (4.3 rom) copied onto the storage on your phone you will probably have to flash stock recovery and recover by installing a stock RUU for your carrier/CID version.
---------- Post added at 11:59 AM ---------- Previous post was at 11:54 AM ----------
Out of curiosity try going into twrp and doing a factory reset (wipe) and reboot see if you have the same issue.

is there such thing as a stuck RUU for rogers in canada? ive been looking on the internet but i can't seem to find anything that could works for my phone. maybe you could point me in a direction so i could look ?

deerome said:
is there such thing as a stuck RUU for rogers in canada? ive been looking on the internet but i can't seem to find anything that could works for my phone. maybe you could point me in a direction so i could look ?
Click to expand...
Click to collapse
Cant see any for rogers
Just found this http://htconeroot.com/htc-one-tutorials/how-to-copy-files-to-htc-one-using-twrp-mount-and-adb/ if you can copy a rom to the phone it will probably work.
A nandroid backup for rogers is here http://forum.xda-developers.com/showthread.php?t=2207874 or you could flash a pre 4.4 rom. CWM needed to recover a CWM backup and backup would need to be in right directory.
You would need to unlock bootloader to do these things.
If I was you I would download a custom rom like Android Revolution HD 40.3 copy over via above process, do a wipe and install, without s-off you probably have to flash kernel via fastboot.

gffmac said:
Cant see any for rogers
Just found this http://htconeroot.com/htc-one-tutorials/how-to-copy-files-to-htc-one-using-twrp-mount-and-adb/ if you can copy a rom to the phone it will probably work.
A nandroid backup for rogers is here http://forum.xda-developers.com/showthread.php?t=2207874 or you could flash a pre 4.4 rom. CWM needed to recover a CWM backup and backup would need to be in right directory.
You would need to unlock bootloader to do these things.
If I was you I would download a custom rom like Android Revolution HD 40.3 copy over via above process, do a wipe and install, without s-off you probably have to flash kernel via fastboot.
Click to expand...
Click to collapse
thanks for your answers
i definitly am gonna try installing the android revolution hd rom to see if i can at least get an OS running on my phone. what command do i have to use to flash the kernel ?
also, i have tried sideloading/pushing the nandroid backup before but that didint seem to work, not sure if i did something wrong.

deerome said:
thanks for your answers
i definitly am gonna try installing the android revolution hd rom to see if i can at least get an OS running on my phone. what command do i have to use to flash the kernel ?
also, i have tried sideloading/pushing the nandroid backup before but that didint seem to work, not sure if i did something wrong.
Click to expand...
Click to collapse
To flash a kernel via fastboot 'fastboot flash boot boot.img'. Make sure the boot.img (if thats what its called) is in the same folder as fastboot. The corresponding kernel(boot.img) is inside the zip file of most roms.

gffmac said:
To flash a kernel via fastboot 'fastboot flash boot boot.img'. Make sure the boot.img (if thats what its called) is in the same folder as fastboot. The corresponding kernel(boot.img) is inside the zip file of most roms.
Click to expand...
Click to collapse
thanks to your help i was able to install an earlier version of android hd so after many hours of headache i somehow managed to install the android hd rom by sideloading it with cwm. what a pain in the arse -_-. nonetheless that was a great help, what should i do now so something like this don't happen again? i wanted to have the google edtion on my htc but i think im gonna wait until im better at this thing.
anyways thanks again man i really appreciate you have no idea how frustrated i was lol :good:

deerome said:
thanks to your help i was able to install an earlier version of android hd so after many hours of headache i somehow managed to install the android hd rom by sideloading it with cwm. what a pain in the arse -_-. nonetheless that was a great help, what should i do now so something like this don't happen again? i wanted to have the google edtion on my htc but i think im gonna wait until Im better at this thing.
Anyways thanks again man i really appreciate you have no idea how frustrated i was lol :good:
Click to expand...
Click to collapse
No probs glad you got it working again.
If you really want to try a Google Edition rom you would need to s-off your phone which is trickier than what you have done so far so may want to read up some more.

I had the exact same problem while i was flashing a GEdition ROM. The problem here is that my volume Keys dont work and i cant manage to enter recovery/bootloader over ADB. Tried all usb cords and porta. Still giving me Device not found. Any tricky way to access bootloader or recovery?
I've already sent it to warranty but without the original software.... Blablabla they told me that it would only work
with a board replacement... 180€
Any help?
Sent from my Desire HD using Tapatalk

deerxmoose said:
I had the exact same problem while i was flashing a GEdition ROM. The problem here is that my volume Keys dont work and i cant manage to enter recovery/bootloader over ADB. Tried all usb cords and porta. Still giving me Device not found. Any tricky way to access bootloader or recovery?
I've already sent it to warranty but without the original software.... Blablabla they told me that it would only work
with a board replacement... 180€
Any help?
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
You can get to bootloader and recovery via adb commands but thats from a running rom I presume http://forum.xda-developers.com/showthread.php?t=1853159
How come your volume keys dont work, did it come that way? I presume you have tried holding power and volume down for a prolonged length of time??

gffmac said:
You can get to bootloader and recovery via adb commands but thats from a running rom I presume http://forum.xda-developers.com/showthread.php?t=1853159
How come your volume keys dont work, did it come that way? I presume you have tried holding power and volume down for a prolonged length of time??
Click to expand...
Click to collapse
For no reason they stop working. And i think its a hardware malfunction. Besides that, i cant manage to enter bootloader or recovery to instala other ROM.
I guess with Samsung Phones there is a doubletap on the screen to enter bootloader.
Im really stressing here.
Sent from my Desire HD using Tapatalk

deerxmoose said:
For no reason they stop working. And i think its a hardware malfunction. Besides that, i cant manage to enter bootloader or recovery to instala other ROM.
I guess with Samsung Phones there is a doubletap on the screen to enter bootloader.
Im really stressing here.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
I would contemplate opening the phone up to check the behind the volume buttons but that is very risky.

gffmac said:
I would contemplate opening the phone up to check the behind the volume buttons but that is very risky.
Click to expand...
Click to collapse
Before trying that ill prefer to try Any other solutions. Anyone?
Sent from my Desire HD using Tapatalk

There is no bootloader in Samsung phones, and no doubletap. You need to hit the buttons as well. If you are able to boot into the phone and adb devices shows the device, you can do
adb reboot-bootloader or adb reboot recovery

SaHiLzZ said:
There is no bootloader in Samsung phones, and no doubletap. You need to hit the buttons as well. If you are able to boot into the phone and adb devices shows the device, you can do
adb reboot-bootloader or adb reboot recovery
Click to expand...
Click to collapse
Tried that over and over and it keeps saying device not found.
Sent from my Desire HD using Tapatalk

Then you should fix your computer/adb issues.

Stock Rom 4.2.2 update to 4.3 = brick

I put stock back on my phone "Guru_Reset_M7_2.24.771.3.zip" which I have done before without any problem.
Stock rom flashed fine, boots up fine and start reinstalling apps etc, OTA firmware starts downloading sense 5.5 etc
Install OTA update and then restart then phone just shows white background with htc logo then bootloops.
Tried going into recovery, restarting, power down, factory reset etc, doesn't work so I do fastboot oem relock to see if it helps.
So basically it's boot looping and now I have no idea how to fix it
EDIT: - I Wiped, reinstalled stock rom and tried again, SAME PROBLEM.

Anarchy89 said:
Hey guys I'll try and keep it short and sweet.
So here's what happened.
I installed android revolution HD 71.1 no problems, notice mobile signal is weak 1-2 bars I normally have 4-5 so I searched and someone said maybe firmware is not up to date.
So I wipe the rom and put stock back on there "Guru_Reset_M7_2.24.771.3.zip" which I have done before without any problem.
Stock rom flashed fine, boots up fine and start reinstalling apps etc, OTA firmware starts downloading sense 5.5 etc
Install OTA update and then restart then phone just shows white background with htc logo then bootloops.
Tried going into recovery, restarting, power down, factory reset etc, doesn't work so I do fastboot oem relock to see if it helps.
So basically it's boot looping and now I have no idea how to fix it, please help, it will be so appreciated
Click to expand...
Click to collapse
If you can flash and access custom recovery, adb push or adb sideload a custom rom..

thanks, I'm making progress, I unlocked the bootloader again and am reflashing the stock firmware...

I flashed stock firmware and stock recovery and downloaded and installed the OTA update and it's doing the same thing!! why?
Just bootlooping

Anarchy89 said:
I flashed stock firmware and stock recovery and downloaded and installed the OTA update and it's doing the same thing!! why?
Just bootlooping
Click to expand...
Click to collapse
Links to stock firmware and stock recovery?
Maybe something is wrong with the phone??
Your best start will be to flash a custom recovery and then flash a custom rom. What is the output of your fastboot getvar all ? (remove IMEI)

SaHiLzZ said:
Links to stock firmware and stock recovery?
Maybe something is wrong with the phone??
Your best start will be to flash a custom recovery and then flash a custom rom. What is the output of your fastboot getvar all ? (remove IMEI)
Click to expand...
Click to collapse
He is using this correct ?: http://www.htc1guru.com/dld/guru_reset_m7_2-24-771-3-zip/
He is having exactly the same problem as someone I was trying to help out who is having exactly the same issue and may join in this thread.
The guru reset puts them on 4.2.2 which works fine then they get a small OTA which installs fine, then a big update to 4.3 which installs, but upon restart for some reason gives a boot loop, doesn't get past the HTC quietly brilliant logo, im at a loss.

Seanie280672 said:
He is using this correct ?: http://www.htc1guru.com/dld/guru_reset_m7_2-24-771-3-zip/
He is having exactly the same problem as someone I was trying to help out who is having exactly the same issue and may join in this thread.
The guru reset puts them on 4.2.2 which works fine then they get a small OTA which installs fine, then a big update to 4.3 which installs, but upon restart for some reason gives a boot loop, doesn't get past the HTC quietly brilliant logo, im at a loss.
Click to expand...
Click to collapse
yes that's the exact one I am using

Seanie280672 said:
He is using this correct ?: http://www.htc1guru.com/dld/guru_reset_m7_2-24-771-3-zip/
He is having exactly the same problem as someone I was trying to help out who is having exactly the same issue and may join in this thread.
The guru reset puts them on 4.2.2 which works fine then they get a small OTA which installs fine, then a big update to 4.3 which installs, but upon restart for some reason gives a boot loop, doesn't get past the HTC quietly brilliant logo, im at a loss.
Click to expand...
Click to collapse
Oh ok.. Interesting.
S-OFF, and move to .401 base perhaps?

SaHiLzZ said:
Oh ok.. Interesting.
S-OFF, and move to .401 base perhaps?
Click to expand...
Click to collapse
I did suggest that, but, somehow he never got the sense 6 update but is on hboot 1.57 and cant s-off

SaHiLzZ said:
Oh ok.. Interesting.
S-OFF, and move to .401 base perhaps?
Click to expand...
Click to collapse
Sorry I don't understand.
Also couldn't I circumvent this hassle just by installing this ROM?
http://forum.xda-developers.com/showthread.php?t=2224752

Seanie280672 said:
I did suggest that, but, somehow he never got the sense 6 update but is on hboot 1.57 and cant s-off
Click to expand...
Click to collapse
ODD! 4.2/4.3 should be on 1.55 Hboot..
@OP.. whats your fastboot getvar all ?

C:\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *******************
(bootloader) imei: *******************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3838mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae8bbb39
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.049s

couldn't I circumvent this hassle just by installing this ROM?
http://forum.xda-developers.com/showthread.php?t=2224752

Its strange that you too have HBOOT 1.57, did you get the sense 6 update ?

Seanie280672 said:
Its strange that you too have HBOOT 1.57, did you get the sense 6 update ?
Click to expand...
Click to collapse
nope

Anarchy89 said:
couldn't I circumvent this hassle just by installing this ROM?
http://forum.xda-developers.com/showthread.php?t=2224752
Click to expand...
Click to collapse
Yes... You have 1.57 HBOOT.. you should NOT be using 2.x.771.x files. It does NOT gel well.
You have to stick with custom roms, just use adb push or adb sideload..

Anarchy89 said:
nope
Click to expand...
Click to collapse
Well you could try flashing twrp 2.6.3.3 and then flash that ROM your interested in, but it could make things worse, you have a very strange problem, I would love to know why custom rom's work and the guru-reset file, but the OTA's pretty much kill your phone.

SaHiLzZ said:
Yes... You have 1.57 HBOOT.. you should NOT be using 2.x.771.x files. It does NOT gel well.
You have to stick with custom roms, just use adb push or adb sideload..
Click to expand...
Click to collapse
Okay, well I don't know a lot about all this stuff, for example I don't know what HBOOT is, S-OFF/ON etc, I just look for ROMs I'm interested in, optimizing my phone, I just read guides and 99% of the time I don't have a problem.
Do you think my problem would go away if I had HBOOT 1.55? Is it even possible to downgrade?
I'll just flash the ROM I mentioned...but doesn't that mean I won't be able to get OTA updates? (because of the nonstock recovery)
IDFK

Don't know why your HBOOT is 1:57 while your device is not OTA to Sense 6.0. Certainly you can't downgrage HBOOT to 1:55 without S-OFF. You should flash TWRP 2.6.3.3, then adb sileload a custom rom to install

I just wiped and put android revolution hd 71.1 on there and it seems fine now, the other stock rom I mentioned earlier I flashed and I kept getting errors "unfortunately updater has stopped working" every 3 minutes.
I had a go at S-OFF with rumrunner but it didn't work on two ROMs, someone said to try it on linux as it's more reliable, any suggestions for how I can easily S-OFF? thanks :good:

Phone does not boot says tampered!

The Story
So a few days ago I decided I wanted to try rooting my phone despite not really knowing much about the process.
First I unlocked my bootloader, simple enough right? Even managed to change my recovery to twrp and it worked fine.
Being naive I decided to tried to root the phone by installing supersu using twrp. I placed a zip file on my phone and attempted to flash using twrp
Long be hold my phone was still booting but then I tried to update the version of supersu because it was not working. This is when the problems started.
A tampered flag appear in my bootloader which of course is because I was not S-OFF! (Did not know what that was at the time)
So now my phone appears to be bricked and I can no longer boot into the OS
After much research and trying out different solutions, nothing appears to work.
From what I have gathered the only thing I can do is to restore the stock image. That would be fine if it were possible to find!
Not sure how accurate this is but I have read that RUUs do not work if you are S-ON.
Please someone help me...Not having a phone for 2 days now is a bummer!
EDIT :adb and fastboot are installed and working. Though adb seems to only work when I am in recovery
UPDATE: So as suggested by alray I updated the supersu to newest version and my phone now boots!
Thank you to all who responded!

donking233 said:
The Story
So a few days ago I decided I wanted to try rooting my phone despite not really knowing much about the process.
First I unlocked my bootloader, simple enough right? Even managed to change my recovery to twrp and it worked fine.
Being naive I decided to tried to root the phone by installing supersu using twrp. I placed a zip file on my phone and attempted to flash using twrp
Click to expand...
Click to collapse
What version of twrp and what version of supersu?
Long be hold my phone was still booting but then I tried to update the version of supersu
Click to expand...
Click to collapse
What version of supersu?
From what I have gathered the only thing I can do is to restore the stock image. That would be fine if it were possible to find!
Click to expand...
Click to collapse
post the output of "fastboot getvar all"
Not sure how accurate this is but I have read that RUUs do not work if you are S-ON.
Click to expand...
Click to collapse
RUU works with s-on, you only need s-off if the ruu you want to use is a downgrade.

alray said:
What version of twrp and what version of supersu?
What version of supersu?
post the output of "fastboot getvar all"
RUU works with s-on, you only need s-off if the ruu you want to use is a downgrade.
Click to expand...
Click to collapse
Here is all the info
version: 0.5
version-bootloader: 1.61.0000
version-baseband: 4T.35.3218.16
version-cpld: None
version-microp: None
version-main: 7.17.631.7
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: ROGER001
battery-status: good
battery-voltage: 4320mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-eff4f609
hbootpreupdate: 11
gencheckpt: 0
For twrp I installed the latest version 2.8.7.0-m7
SuperSu intialled was v1.30 but I tried to update to v1.65 and thats when everything went wrong.
Thanks I really appreciate the help!

donking233 said:
Here is all the info
version: 0.5
version-bootloader: 1.61.0000
version-baseband: 4T.35.3218.16
version-cpld: None
version-microp: None
version-main: 7.17.631.7
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: ROGER001
battery-status: good
battery-voltage: 4320mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-eff4f609
hbootpreupdate: 11
gencheckpt: 0
For twrp I installed the latest version 2.8.7.0-m7
SuperSu intialled was v1.30 but I tried to update to v1.65 and thats when everything went wrong.
Thanks I really appreciate the help!
Click to expand...
Click to collapse
Whoa both supersu version are really outdated. You must use 2.46 on lollipop so boot in your recovery and flash 2.46 and if your phone still refuse to boot we will help you relfash the rom.
Sorry, forgot to say, don't post your IMEI, remove it from your above post.

Should blank out your serial and imei on the forum
Sent from my HTC One using XDA Premium HD app

alray said:
Whoa both supersu version are really outdated. You must use 2.46 on lollipop so boot in your recovery and flash 2.46 and if your phone still refuse to boot we will help you relfash the rom.
Sorry, forgot to say, don't post your IMEI, remove it from your above post.
Click to expand...
Click to collapse
Sieze said:
Should blank out your serial and imei on the forum
Sent from my HTC One using XDA Premium HD app
Click to expand...
Click to collapse
Thanks just removed them
Just curious why exactly is it a bad idea to post the imei and serial?
OK I will reply with the results of updating the superSU

This is actually quite weird but I have the exact same problem as you and seem to have the same MID and CID as you aswell.
I also happened to get the SuperSU 1.30 which didn't work (it kept crashing on me). I then updated it to 2.46 but then the phone stopped booting. I was just about to create a thread to ask for help but then I saw this, haha.
Edit: Would downloading a Nandroid restore from guru's stock nandroid backups work? (can't post link) I've downloaded the TWRP ROGER001 backup, extracted all the files into a folder in TWRP (which is visible to "Restore" on TWRP) but I'm not sure whether I should do it.

TheWijiBoard said:
This is actually quite weird but I have the exact same problem as you and seem to have the same MID and CID as you aswell.
I also happened to get the SuperSU 1.30 which didn't work (it kept crashing on me). I then updated it to 2.46 but then the phone stopped booting. I was just about to create a thread to ask for help but then I saw this, haha.
Edit: Would downloading a Nandroid restore from guru's stock nandroid backups work? (can't post link) I've downloaded the TWRP ROGER001 backup, extracted all the files into a folder in TWRP (which is visible to "Restore" on TWRP) but I'm not sure whether I should do it.
Click to expand...
Click to collapse
What is your version and what is the nandroid backup version?

TheWijiBoard said:
Edit: Would downloading a Nandroid restore from guru's stock nandroid backups work? (can't post link) I've downloaded the TWRP ROGER001 backup, extracted all the files into a folder in TWRP (which is visible to "Restore" on TWRP) but I'm not sure whether I should do it.
Click to expand...
Click to collapse
Just tried this; it did work and I've been reverted to Android 4.3 but my phone actually boots.
Edit: Whoops. Turns out this is a bad idea.

donking233 said:
Thanks just removed them
Just curious why exactly is it a bad idea to post the imei and serial?
OK I will reply with the results of updating the superSU
Click to expand...
Click to collapse
because the IMEI is a unique number identifying your phone, each phone have its own unique IMEI number. Lets say you loose your phone, you will call your carrier to declare your phone lost/stolen, they will blacklist your IMEI number so the phone can't be activated anymore on any GSM network.
Also your IMEI number could be used with other information like your sim card number / serial to clone your phone.
Its like sharing your social security number

alray said:
What is your version and what is the nandroid backup version?
Click to expand...
Click to collapse
Not sure I understand your question. What do you mean by version? My "getvar all" information is actually exactly the same as OP.
The nandroid backup that I downloaded was "M7 TWRP Nandroid Backup CID ROGER001 3.22.631.1". Hope that helps.

TheWijiBoard said:
Not sure I understand your question. What do you mean by version? My "getvar all" information is actually exactly the same as OP.
The nandroid backup that I downloaded was "M7 TWRP Nandroid Backup CID ROGER001 3.22.631.1". Hope that helps.
Click to expand...
Click to collapse
So you just created a mismatch between your software version and your firmware version.
Your software is now 3.22.631.1 and your firmware is 7.17.631.7, you want the firmware and software to be the same version hence why OP shouldn't do the same.
There is already a 7.17.631.7 ruu posted in the general section, use this instead and then root your phone using supersu 2.46
So if you are s-on, you will need to re-lock the bootloader first, flash the 7.17.631.7 ruu, unlock the bootloader, flash twrp and root.

alray said:
So you just created a mismatch between your software version and your firmware version.
Your software is now 3.22.631.1 and your firmware is 7.17.631.7, you want the firmware and software to be the same version hence why OP shouldn't do the same.
There is already a 7.17.631.7 ruu posted in the general section, use this instead and then root your phone using supersu 2.46
So if you are s-on, you will need to re-lock the bootloader first, flash the 7.17.631.7 ruu, unlock the bootloader, flash twrp and root.
Click to expand...
Click to collapse
Sorry, but I just don't happen to see it.
Nevermind; it seems to be available on htcdev. I hope that is okay to use.

TheWijiBoard said:
Sorry, but I just don't happen to see it.
Click to expand...
Click to collapse
The ruu is here:http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
relock your bootloader (only if the phone is s-on)
flash the ruu
unlock your bootloader again
flash your custom recovery
flash supersu 2.46
btw if you are using a recent twrp recovery like 2.8+ it should already have the latest supersu included so you don't need to flash supersu 2.46 manually, just enter twrp then exist, you'll prompted to root, select "yes" and the phone will reboot and be rooted.

alray said:
The ruu is here:http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
relock your bootloader (only if the phone is s-on)
flash the ruu
unlock your bootloader again
flash your custom recovery
flash supersu 2.46
btw if you are using a recent twrp recovery like 2.8+ it should already have the latest supersu included so you don't need to flash supersu 2.46 manually, just enter twrp then exist, you'll prompted to root, select "yes" and the phone will reboot and be rooted.
Click to expand...
Click to collapse
Ah, okay I shall do this now. Will update after I'm done. Thanks for all the help.
---------- Post added at 10:53 PM ---------- Previous post was at 10:48 PM ----------
alray said:
flash the ruu
Click to expand...
Click to collapse
Stupid question but to flash it, do I do the following:
reboot oem
fastboot flash zip *nameofruu* (twice if need be)
fastboot reboot-reloader

TheWijiBoard said:
Ah, okay I shall do this now. Will update after I'm done. Thanks for all the help.
---------- Post added at 10:53 PM ---------- Previous post was at 10:48 PM ----------
Stupid question but to flash it, do I do the following:
reboot oem
fastboot flash zip *nameofruu* (twice if need be)
fastboot reboot-reloader
Click to expand...
Click to collapse
no.
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot reboot
You need to use htc_fastboot.exe which is provided in that thread and no longer need to flash twice. After doing "fastboot flash zip ruu.zip" the ruu will flash the pre-update, reboot itself in ruu mode and continue the second flash automatically.

alray said:
no.
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot reboot
You need to use htc_fastboot.exe which is provided in that thread and no longer need to flash twice. After doing "fastboot flash zip ruu.zip" the ruu will flash the pre-update, reboot itself in ruu mode and continue the second flash automatically.
Click to expand...
Click to collapse
Will I be able to use htc_fastboot.exe on linux?

TheWijiBoard said:
Will I be able to use htc_fastboot.exe on linux?
Click to expand...
Click to collapse
well a .exe is for Windows. maybe it can work if you use Wine + cmd.exe + htc_fastboot.exe ? Never tried.....

alray said:
well a .exe is for Windows. maybe it can work if you use Wine + cmd.exe + htc_fastboot.exe ? Never tried.....
Click to expand...
Click to collapse
Is there an advantage of using the htc-fastboot other than not having to hit it twice? Because then I can just use the one I have been previously that does work on Linux.
If you google "htc one root linux", the first link from htconeroot is the tutorial I was following. He had shared fastboot/adb files that work on linux and those are the ones I am using.

TheWijiBoard said:
Is there an advantage of using the htc-fastboot other than not having to hit it twice? Because then I can just use the one I have been previously that does work on Linux.
If you google "htc one root linux", the first link from htconeroot is the tutorial I was following. He had shared fastboot/adb files that work on linux and those are the ones I am using.
Click to expand...
Click to collapse
the normal fastboot won't work to flash 7.xx.xxx.x ruu, you must use htc's version of fastboot which is only available in .exe. the "normal" fastboot from google can't handle the file size of new 7.xx.xxx.x RUUs.

[Q] HTC ONE in bootloop, flashing ROM.zip is failing?

Hello, so I rooted my phone successfully. But when I installed SuperSU the program didnt seem to work, so I replaced it with with a newer version on SuperSU.
Somewhere along those lines I managed to bootloop my HTC.
I have tried EVERYTHING to get my phone going. With little progress.
I am currently trying to reflash the stock ROM onto my phone using adb push, and adb sideload with both TWRP and CWM, but it keeps saying that it failed or its bad when I try to install it through recovery... i've tried 3 different RUU downloads.
What am I doing wrong?? Please help!

nmaart said:
Hello, so I rooted my phone successfully. But when I installed SuperSU the program didnt seem to work, so I replaced it with with a newer version on SuperSU.
Somewhere along those lines I managed to bootloop my HTC.
I have tried EVERYTHING to get my phone going. With little progress.
I am currently trying to reflash the stock ROM onto my phone using adb push, and adb sideload with both TWRP and CWM, but it keeps saying that it failed or its bad when I try to install it through recovery... i've tried 3 different RUU downloads.
What am I doing wrong?? Please help!
Click to expand...
Click to collapse
Had a similiar issue a day ago.
What happened was I put a old version of supersu on my phone that didnt work with the firmware I had so it bootlooped.
I had to update my SuperSu version and it worked. If you are running a newer firmware make sure SuperSu is the most current version (2.46)
If not try flashing 2.46 and see what happens.

donking233 said:
Had a similiar issue a day ago.
What happened was I put a old version of supersu on my phone that didnt work with the firmware I had so it bootlooped.
I had to update my SuperSu version and it worked. If you are running a newer firmware make sure SuperSu is the most current version (2.46)
If not try flashing 2.46 and see what happens.
Click to expand...
Click to collapse
I have never even thought of that!!
So I don't have to flash a new ROM like ive been trying to do this whole time?
I know I put an updated SuperSU on there, and accidentally left the old version on there too... I had already done a factory reset and all... does that matter ??
[EDIT] Can you run me through the steps to do this properly? I really don't want to screw up again lol

nmaart said:
I have never even thought of that!!
So I don't have to flash a new ROM like ive been trying to do this whole time?
I know I put an updated SuperSU on there, and accidentally left the old version on there too... I had already done a factory reset and all... does that matter ??
[EDIT] Can you run me through the steps to do this properly? I really don't want to screw up again lol
Click to expand...
Click to collapse
Like you I did factory reset which did nothing
All you have to do is place the zip with the newest version of SuperSu on your device.
Then using twrp or whatever recovery you have flash it on their
Phone will reboot and it should be working
Not sure if this will help or not but I made sure to update my twrp to latest as well

donking233 said:
Like you I did factory reset which did nothing
All you have to do is place the zip with the newest version of SuperSu on your device.
Then using twrp or whatever recovery you have flash it on their
Phone will reboot and it should be working
Not sure if this will help or not but I made sure to update my twrp to latest as well
Click to expand...
Click to collapse
Alright and it will cancel out the old SuperSU I hope ?
Wish me luck!

nmaart said:
Alright and it will cancel out the old SuperSU I hope ?
Wish me luck!
Click to expand...
Click to collapse
Alright I used adb sideload to flash the SuperSU 2.46 zip file onto my phone but it did nothing
Maybe I didn't do it right... I don't know

nmaart said:
Alright I used adb sideload to flash the SuperSU 2.46 zip file onto my phone but it did nothing
Maybe I didn't do it right... I don't know
Click to expand...
Click to collapse
Please post the out put of
Code:
fastboot getvar all
remove your imei and serial numbers before posting :good:
Which version of TWRP/CWM are you using? And which rom?
Sent from my SM-T230 using Tapatalk

Danny201281 said:
Please post the out put of
Code:
fastboot getvar all
remove your imei and serial numbers before posting :good:
Which version of TWRP/CWM are you using? And which rom?
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
version-bootloader: 1.61.0000
version-baseband: 4T.35.3218.16
version-main:
version-misc: PVT SHIP S-ON
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: ROGER001
security: on
I have both CWM and TWRP both of the latest versions. As for which ROM, I have no idea what's currently on there. I just know that it was running Lollipop before all this happened lol

nmaart said:
version-bootloader: 1.61.0000
version-baseband: 4T.35.3218.16
version-main:
version-misc: PVT SHIP S-ON
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: ROGER001
security: on
I have both CWM and TWRP both of the latest versions. As for which ROM, I have no idea what's currently on there. I just know that it was running Lollipop before all this happened lol
Click to expand...
Click to collapse
OK go here http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Download the "7.17.631.7" ruu. Instructions to flash are in the same thread
Sent from my SM-T230 using Tapatalk

Danny201281 said:
OK go here http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Download the "7.17.631.7" ruu. Instructions to flash are in the same thread
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
Thank you, everything is resolved!

nmaart said:
Thank you, everything is resolved!
Click to expand...
Click to collapse
Good to hear :good: For the record I believe your original problem was most likely your recovery version.
TWRP is definitely better for the M7 than cwm. But newer versions of TWRP tend to be a little buggy. If in doubt always flash roms with the recovery recommended in the roms main thread.
TWRP 2.6.3.3 has always been the most stable version
Sent from my M7 ARHD 84-Kitkat