Related
I'd like to say, straight off the bat, that I have searched relentlessly, with only hints of success, but nothing actually turning up fruitful.
My problem is this:
tonight i decided to try out Cursorsense, it looked simple enough. I flashed my radio and SPL, and got ready to flash the new rom.
As I stared up the AmonRA recovery image (1.5.2 H), it suddenly restarted, and went into a boot-loop.
*I have read suggestions of flashing "permanently" but I am unaware how to do this.
*I have read about wiping the system, but this does nothing.
*attempts to use "fastboot update" give me an error of "failed to load update.zip" or a series of completely garbled text and other crap.
*attempts to use "fastboot boot" using either a new version of AmonRa's recovery image, or a stock sapphire image, give me an error of
booting... FAILED (remote: reproduce boot image with on-flash ramdisk error)
I find myself sleepy, and at a loss. I might be missing something fundamental, but I do need your help in seeing this.
This wouldnt be such a terrible issue if this wasnt a phone I use for work, but... so it goes.
Regards, and thanks in advance for any help.
pal, you need the *hero* AmonRA's recovery!
okay! There's some solid help now, would this solve my biggest (and pretty much only) problem, of the RA-Sapphire freezing/hanging and suddenly rebooting?
I say only problem, as I've just bought a card reader, so I can at least bypass the process of getting files onto the SD.
Regards
retrograde said:
okay! There's some solid help now, would this solve my biggest (and pretty much only) problem, of the RA-Sapphire freezing/hanging and suddenly rebooting?
I say only problem, as I've just bought a card reader, so I can at least bypass the process of getting files onto the SD.
Regards
Click to expand...
Click to collapse
Your phone is rebooting because the new radio doesn't support the Sapphire recovery, you need to use the Hero recovery.
Very much a noob when it comes to Android phones and I have been working through the process to get a custom Rom on my HTC Sensation. I started following the instructions in this thread [Guide] to Installing S-off, Unlocking, ClockWork, Root, SuperCID & S-on and successfully completed step one, achieving s-off on the phone.
In step two things went badly wrong. Following the instructions I downloaded clockwork recovery and copied the PG58IMG onto my sd card, at least I thought I did. What I now realize is that since I had been doing a lot of reading and research on this topic before attempting it for the first time I had downloaded several relevant files in advance, one of which is the PG58IMG file from this thread [DEV] HTC Sensation & HTC Sensation XE firmware | Partitions Info | [01.03.2012 and it was this file that I put on the sd card. Obviously not what I should have flashed at all. Especially since it seems that the tool which would help me out of this mess is the one I just failed to install properly.
So the situation is that the phone loops constantly on startup when booting normally. When I boot into HBOOT with the SD card in it tries to update again and when that fails, gives no option but to reboot. If I remove the SD card then I get access to the following screen -
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-10.14.9035.01_M
eMMC-boot
and below the options -
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
I have tried connecting the phone to my computer at this stage but I cant get FASTBOOT USB and adb cant find any devices either. Am I completely stuffed at this point? If not, if anyone can help me out with some instructions on what to do here I would be extremely grateful.
Thanks,
Webba
So have you tried to go into recovery once your in bootloader ? what happens then ?
If you get the correct files onto your sd card via a card reader, then put it in the phone, bootloader should attempt to update the new correct files.
I have tried going into recovery, it comes up with a pic of a phone with a green circle, followed by a phone with a red triangle, followed by going into the boot cycle. This is with the sd card removed. Am I right in thinking that if I get the right files onto the card and then run recovery with the sd card in it will work?
If you run BOOTLOADER then it should do... Make sure you remove the old PG58IMG before putting the new one on.
Thanks so much, I will try it as soon as I can. I assume I will find the right stock rom somewhere on these forums?
webster84 said:
Thanks so much, I will try it as soon as I can. I assume I will find the right stock rom somewhere on these forums?
Click to expand...
Click to collapse
you will find anything and everything you will ever need on these forums
My Sensation was purchased in Hong Kong, after looking at the lists at shipped-roms this one - RUU_Pyramid_hTC_Asia_WWE_1.35.707.1_Radio_10.43a.9007.00U_10.51.9007.27_M3_release_198358_signed.exe
seems to be most likely correct. Can anyone more knowledgeable confirm this? I would hate to flash the wrong thing again.
did you successfully get superCID ? if so i do believe that you can flash any RUU / ROM
Im not 100% on this as im still new to the sensation myself, But im sure thats the whole point in having SuperCID
Unfortunately I dont have superCID. I was following the instructions pretty slavishly and the superCID setup is one step after clockwork
Is there a way to get superCID in my phones current state? From what I am reading I need it to at least hook up to adb which it is not doing at the moment so I assume I just have to get the right onto the sdcard to have any chance of it working, right?
Yes, You need clockwork mod before SuperCID. Have you tried to re download CWM and put it on sd card ? It could have just been a bad download, it happens to us all.
Download it again, Remove the previous PG58IMG from SD Card via a card reader (if you have one) Put the new PG58IMG on SD card. Pull battery out, Put SD Card back into the phone, put battery back in and boot into bootloader (volume down + Power)
Bootloader should automatically find the PG58IMG and ask if you want to update it, Select yes and theoretically you should be fine..
EDIT: Use this one http://forum.xda-developers.com/attachment.php?attachmentid=706572&d=1314848127
Yeah, I have re-downloaded CWM and made sure it is the right one I have to wait until the shops open here so I can pick up a micro sdcard reader but I will try the new CWM first, and if that fails then I will try the stock rom. Am I right in thinking that neither of this is likely to make the situation worse, even if they dont work?
No providing bootloader still works everything is fix-able..
We aint messing with bootloader so u will be ok.
Cant believe you dont have a card reader lol....
lol, up until today the only thing I needed to be able to read micro sd cards was the phone. Well, I will be better prepared next time anyway.
The thing that had me worried is that since I originally didn't realize PG58IMG was not a unique file name I am almost certain that the one on my sd card at the moment is not even CWM at all but one of the updated firmware ones I mentioned in the OP that I very stupidly mistook for it. It feels like a really serious mistake to make, but happy to know that if the boot loader is working then it should be fixable. I wasn't sure even about that.
I think the PG58IMG is a unique code that the phone reads and recognises as something to be flashed / updated.
Ive seen various things CWM / Firmwares / Updates with the same PG58IMG title. so maybe youre right and the original file you downloaded wasnt the correct one.
Dont panic, Keep calm, Ask questions, Get answers...... This is the only way to avoid a bricked phone
Yeah, you've saved me a lot of stress already. Ill be back in a few hours with the results of the next attempt. Thanks again!
Ok, the news is not great. I got hold of a micro sd adaptor so I could plug it into my computer and removed the old PG58IMG. I put the correct one (downloaded from this thread) on the sd card and rebooted the phone into HBOOT. It recognizes the file on the sd card but gets a cid fail and there is no option but to reboot which goes into the boot cycle.
Whats worse is that doing this apparently fries the sdcard. I tried it twice, because I am sucker for punishment and in both cases the sdcard is unreadable afterwards.
Maybe I should try and explain more clearly that I am now sure the PG58IMG that I first put on the card and flashed I am sure is the Firmware from 3.32.401.x & 3.32.401.10x RUU from this thread. It appeared to successfully update before rebooting the phone into its current state, causing me to realize I had the wrong file. I dont understand enough to know exactly whats going on but it seems pretty bad. Do you think I should try a 3rd sdcard with the Shipped ROM on it or is there something else I should do at this point?
Edit - The second sd card wasn't fried after all, but I am still searching for a shipped rom that isnt in .exe format, since the phone isnt connecting to the computer by usb at all right now. Anyone know where I can find one?
Edit - Ok, now I have fastboot usb which means I can use .exe shipped roms. adb devices cant find the phone though which means I cant superCID it which means I still have to find the right ROM. Since I brought the phone from HK I am trying all the asian ones first. Anyone know specifically which file at shipped-roms.com is the right one?
You flashed firmware for ics rom, so the stock rom won't boot and you have bootloop. If you flash the 3.12 firmware ( works for both ics and gb) that will resolve the loop and you will be able to continue with the guide and flash cwm.
Sent from my HTC Pyramid using xda premium
Hey Stringer7, do you mean this Firmware from 3.12.401.2/102 RUU available in the same thread? I will download it and give it a try.
edit - Gave it a try, I get CID incorrect from it too. Seems like CID incorrect for everything I try to flash atm.
What is your CID ??
Unfortunately I dont know. I didn't know I needed it before I started and now since the phone isn't talking to adb I cant use it to find out. All I know is that I bought the phone from Hong Kong about 6 months ago. Is there a way to check the CID with the phone the way it is now?
Hi all, here's a long story cut short:
1. Flashed the stock 2.23.707.2 de-odexed rom on my One XL (the S4 version of One X), was running 4.0.4 fine
2. Didn't like the new radio that came with 2.23, tried flashing back to the 1.88 Asia radio which worked best for me, took much longer than usual then appeared to be successfully flashed only to find in bootloader the radio version hasn't changed and once rebooted the baseband info becomes "unknown" and the phone sees no signal at all, probably a messed up radio...
3. (the stupidest of my moves) Relocked my phone using the HTCdev way in an attempt to RUU back to stock and start from scratch, failed with an error code140 (not surprisingly due to the higher hboot version), then noticed the HTCdev unlock code doesn't work anymore. Tried obtaining the unlock_code.bin again in case something changed, but new code is no good either.
Therefore I now have a phone that is Relocke and can't use TWRP recovery, can't boot up as it hits a block at the initial setup (explained below), and one that for some strange reason cannot be unlocked again. I can boot to bootloader, go to fastboot and push the unlock_code.bin file via usb, it will go through and i see the normal unlock confirmation screen on the phone, but choosing yes each time the phone will reboot and when checking in bootloader it still shows the phone is "Relocked". What's worse, after "unlcoking bootloader" the phone now goes into the setup wizard each time it boots up, but perhaps due to the messed up radio thing it can't read the carriers available and thus only shows the white screen with the HTC logo on it, no way forwar. This is where I get completely stuck now.
I can't post in the Development page due to my freshness in xda, but I am not a complete newbie and have owned a Desire, a Sensation and now the One X, each time going through the root/supercid/custom recovery/custom rom/flashing radios processes without major problems so I will say I do have basic knowledge with all these things.
Anyway if someone can shed some light on how I can get out of this mess without having to send the phone back to HTC for some pricey repair, it would be extremely appreciated.
Thanks for your attention,
Sunster
sunster00 said:
Hi all, here's a long story cut short:
1. Flashed the stock 2.23.707.2 de-odexed rom on my One XL (the S4 version of One X), was running 4.0.4 fine
2. Didn't like the new radio that came with 2.23, tried flashing back to the 1.88 Asia radio which worked best for me, took much longer than usual then appeared to be successfully flashed only to find in bootloader the radio version hasn't changed and once rebooted the baseband info becomes "unknown" and the phone sees no signal at all, probably a messed up radio...
3. (the stupidest of my moves) Relocked my phone using the HTCdev way in an attempt to RUU back to stock and start from scratch, failed with an error code140 (not surprisingly due to the higher hboot version), then noticed the HTCdev unlock code doesn't work anymore. Tried obtaining the unlock_code.bin again in case something changed, but new code is no good either.
Therefore I now have a phone that is Relocke and can't use TWRP recovery, can't boot up as it hits a block at the initial setup (explained below), and one that for some strange reason cannot be unlocked again. I can boot to bootloader, go to fastboot and push the unlock_code.bin file via usb, it will go through and i see the normal unlock confirmation screen on the phone, but choosing yes each time the phone will reboot and when checking in bootloader it still shows the phone is "Relocked". What's worse, after "unlcoking bootloader" the phone now goes into the setup wizard each time it boots up, but perhaps due to the messed up radio thing it can't read the carriers available and thus only shows the white screen with the HTC logo on it, no way forwar. This is where I get completely stuck now.
I can't post in the Development page due to my freshness in xda, but I am not a complete newbie and have owned a Desire, a Sensation and now the One X, each time going through the root/supercid/custom recovery/custom rom/flashing radios processes without major problems so I will say I do have basic knowledge with all these things.
Anyway if someone can shed some light on how I can get out of this mess without having to send the phone back to HTC for some pricey repair, it would be extremely appreciated.
Thanks for your attention,
Sunster
Click to expand...
Click to collapse
Try this
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
thanks to kilo89 for method
so this method allows u to downgrade no matter whats your version.. should workout
jags_the1 said:
Try this
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
thanks to kilo89 for method
so this method allows u to downgrade no matter whats your version.. should workout
Click to expand...
Click to collapse
Hi mate thanks for offering advice and help. I have not had to use your method as I decided to give the HTC bootloader unlock code one final try before proceeding to your rescue plan and all of a sudden it was successful again. I got into recovery and did a nandroid restore so am back online again, but have nevertheless made note of your method in case I become stuck again in the future. Thanks anyway for your reply! :good:
I have a AT&T One X rooted
HBOOT-1.09.0000
RADIO-0.17.32.09.12
I am attempting to do the OTA's or RUU to bring it up to current because I realized since I had not touched it since first purchased and rooted so none of the OTA's went through. I never gave myself time allowed to figure out how to send them.
Well now I'm trying and I have gotten myself in to a hot mess.
I first tried using the FUU Upgrades provided by Flashalot but it said "wrong update" and I could not find a reason. I backed up a couple and tried 2.14. Well eventually it just stayed at the fastboot "HTC" screen for nearly an hour and appeared locked up. So I pulled it and rebooted. It would not let me get past the boot up screen until I cleared cache's and went back to my stock rom (cmod 10).
Now it will not mount "SD Card" when connected USB and in TWRP. I am also unable to download any files to it via browser or launched phone because it says no SD Card installed.
I attempted to send any of the OTA's via fastboot and it hangs (giving it hours...overnight even). I did writecid 11111111 before sending some with same results.
Any suggestions?
Thanks
stampy101 said:
I have a AT&T One X rooted
HBOOT-1.09.0000
RADIO-0.17.32.09.12
I am attempting to do the OTA's or RUU to bring it up to current because I realized since I had not touched it since first purchased and rooted so none of the OTA's went through. I never gave myself time allowed to figure out how to send them.
Well now I'm trying and I have gotten myself in to a hot mess.
I first tried using the FUU Upgrades provided by Flashalot but it said "wrong update" and I could not find a reason. I backed up a couple and tried 2.14. Well eventually it just stayed at the fastboot "HTC" screen for nearly an hour and appeared locked up. So I pulled it and rebooted. It would not let me get past the boot up screen until I cleared cache's and went back to my stock rom (cmod 10).
Now it will not mount "SD Card" when connected USB and in TWRP. I am also unable to download any files to it via browser or launched phone because it says no SD Card installed.
I attempted to send any of the OTA's via fastboot and it hangs (giving it hours...overnight even). I did writecid 11111111 before sending some with same results.
Any suggestions?
Thanks
Click to expand...
Click to collapse
First question is do you have s-off?
Second question is did you perform a factory reset from the bootloader at some point? I ask this because it looks like your sd card is corrupt, and that's what happens when you perform a factory reset from the bootloader on a modified Evita. Either way I believe you need to wipe your sd card with TWRP before it'll become usable again. If it still isn't usable after a wipe, try mounting it to your PC again so you can format it with Windows.
My last question is what is your end goal? Are you wanting to run a stock ROM and that's why you're wanting to install OTA updates? The rule of thumb for modified phones is to never install OTA updates on them. If you're just looking to update to the latest/latest needed firmware, you can just flash a firmware package or run an RUU. You must have s-off to do this though.
Another thing I should mention is that you don't use fastboot to install OTA updates. It seems like you're not exactly sure about what you're doing, which can be a very dangerous thing when messing with a modified device. I think you need to do a bit more research before continuing ahead. Tell me exactly what your end goal is though and I'll provide as much information as I can.
Sent from my Evita
FUBAR?
timmaaa said:
First question is do you have s-off?
Second question is did you perform a factory reset from the bootloader at some point? I ask this because it looks like your sd card is corrupt, and that's what happens when you perform a factory reset from the bootloader on a modified Evita. Either way I believe you need to wipe your sd card with TWRP before it'll become usable again. If it still isn't usable after a wipe, try mounting it to your PC again so you can format it with Windows.
My last question is what is your end goal? Are you wanting to run a stock ROM and that's why you're wanting to install OTA updates? The rule of thumb for modified phones is to never install OTA updates on them. If you're just looking to update to the latest/latest needed firmware, you can just flash a firmware package or run an RUU. You must have s-off to do this though.
Another thing I should mention is that you don't use fastboot to install OTA updates. It seems like you're not exactly sure about what you're doing, which can be a very dangerous thing when messing with a modified device. I think you need to do a bit more research before continuing ahead. Tell me exactly what your end goal is though and I'll provide as much information as I can.
Sent from my Evita
Click to expand...
Click to collapse
OK So it sounds like I've probably corrupted my memory from what you are saying. Any going back?
1. S-Off. I'm going with no. It was 2 years ago when I rooted it and installed CM10. I do not recall doing this but just flashing CM.
1a. Attempting to do it now just shows error 99 unknown error...
2. Yes. I do believe that I had hit the factory reset. Attempting to do the wipe in TWRP shows "success" but it also shows it could not mount E:\
2a. Still will not let me turn on USB storage. It just spins for a while and ends up giving up when the display is changed.
3. End goal...I could care less about root. I've always used modded ROM's and prefer them. I only did "OTA" when the RUU would not take. I became a bull in a china shop and started banging with a hammer...Was dumb but I think I had already corrupted the memory by hitting factory reset. (I'll be honest I never meant to hit that).
I've rooted and installed many a custom ROM's, but I prefer the simple methods of following one of the many awesome easy setups on here. I'm not completely useless...
I would like to get it back to the SD card working and be able to update the firmware and a moderately functioning ROM.
Thank you for any help. I really do appreciate it.
stampy101 said:
OK So it sounds like I've probably corrupted my memory from what you are saying. Any going back?
1. S-Off. I'm going with no. It was 2 years ago when I rooted it and installed CM10. I do not recall doing this but just flashing CM.
1a. Attempting to do it now just shows error 99 unknown error...
2. Yes. I do believe that I had hit the factory reset. Attempting to do the wipe in TWRP shows "success" but it also shows it could not mount E:\
2a. Still will not let me turn on USB storage. It just spins for a while and ends up giving up when the display is changed.
3. End goal...I could care less about root. I've always used modded ROM's and prefer them. I only did "OTA" when the RUU would not take. I became a bull in a china shop and started banging with a hammer...Was dumb but I think I had already corrupted the memory by hitting factory reset. (I'll be honest I never meant to hit that).
I've rooted and installed many a custom ROM's, but I prefer the simple methods of following one of the many awesome easy setups on here. I'm not completely useless...
I would like to get it back to the SD card working and be able to update the firmware and a moderately functioning ROM.
Thank you for any help. I really do appreciate it.
Click to expand...
Click to collapse
There's no point in attempting s-off at the moment because s-off requires that a working OS is installed. You can tell whether you're s-off by looking at your bootloader, it'll say s-on or s-off in the first line under the unlocked and tampered banners.
Your problem with your sd might be that the version of TWRP you have installed is too old, only the newer versions are able to fix a corrupt sd card. Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now try wiping and mounting the sd card again. Once we have that sorted out we can move onto getting your firmware updated.
Sent from my Evita
OK! Looks like we are getting somewhere! It is now mounted.
Now you can copy files across to flash. You'll need to get s-off now so you can update your firmware. You'll need a bootable OS installed to do that, I'd suggest installing Kickdroid and then you can attempt getting s-off via the Rumrunner method.
Sent from my Evita
You are awesome! Thank you so very much for your help. Up and running.
How far have you gotten?
Sent from my Evita
S-Off and firmware updated and running with different ROM's. I'm golden man. Unless you can think of something I should consider?
As long as you're on the 2.15 firmware or higher, you are indeed golden. I was just curious.
Sent from my Evita
Hey there, I just noticed you made a donation to me with this thread as the reference. I just wanted to thank you, that's very generous of you. Donations aren't expected in return for my assistance but are greatly appreciated. Anyway, thanks again and have a great day.
Hi, I need help FAST!
I have an AT&T (sim unlocked - done so because I live in Europe, not US) HTC One.
So, a few days ago I was playing smart and decided to install custom ROM to my device.
I've done everything as said until the S-ON procces. I ran the Rumrunner but I obviously messed up something
without knowing so it was left S-ON. So I went on to the install of dustom ROM wich I did, but I 've got stuck in a boot loop and I could only enter my recovery and bootloader. And to make matters worse I somehow succeded to delete al my files from "sd card", HTC One doesn't have SD card slot, as you know, (it has internal storage) so I deleted all my personal files ( I backed up photos, and other personal stuff to my PC in case something like this happens )
and my SuperSU and custom ROM zip files. Then I found out about flashing stock ROM, so I relocked my device to do so but the proper RUU has prooved very hard to find, I 've tried 4-5 RUUs from htc1guru.com for Cingular (AT&T) bot none worked. Maybe I should look for SIM unlocked RUU because I 've SIM unlocked it from AT&T. Now I am really annoyed and angry because of being so stupid and trying something I obviously couldn't achieve so please don't write down trere " Oh you are a noob for doing that " because I know that and I don't need any extra comments for playing smart and bricking my device. SO PLEASE IF ANYONE ON THIS FORUM CAN HELP ME, DO SO!! If i don't manage to finally fix this somehow I'm going to pay someone to fix this.
Torcidas1950 said:
Hi, I need help FAST!
I have an AT&T (sim unlocked - done so because I live in Europe, not US) HTC One.
So, a few days ago I was playing smart and decided to install custom ROM to my device.
I've done everything as said until the S-ON procces. I ran the Rumrunner but I obviously messed up something
without knowing so it was left S-ON. So I went on to the install of dustom ROM wich I did, but I 've got stuck in a boot loop and I could only enter my recovery and bootloader. And to make matters worse I somehow succeded to delete al my files from "sd card", HTC One doesn't have SD card slot, as you know, (it has internal storage) so I deleted all my personal files ( I backed up photos, and other personal stuff to my PC in case something like this happens )
and my SuperSU and custom ROM zip files. Then I found out about flashing stock ROM, so I relocked my device to do so but the proper RUU has prooved very hard to find, I 've tried 4-5 RUUs from htc1guru.com for Cingular (AT&T) bot none worked. Maybe I should look for SIM unlocked RUU because I 've SIM unlocked it from AT&T. Now I am really annoyed and angry because of being so stupid and trying something I obviously couldn't achieve so please don't write down trere " Oh you are a noob for doing that " because I know that and I don't need any extra comments for playing smart and bricking my device. SO PLEASE IF ANYONE ON THIS FORUM CAN HELP ME, DO SO!! If i don't manage to finally fix this somehow I'm going to pay someone to fix this.
Click to expand...
Click to collapse
What is your phone's image version?
---------- Post added at 04:28 PM ---------- Previous post was at 04:18 PM ----------
Torcidas1950 said:
Hi, I need help FAST!
I have an AT&T (sim unlocked - done so because I live in Europe, not US) HTC One.
So, a few days ago I was playing smart and decided to install custom ROM to my device.
I've done everything as said until the S-ON procces. I ran the Rumrunner but I obviously messed up something
without knowing so it was left S-ON. So I went on to the install of dustom ROM wich I did, but I 've got stuck in a boot loop and I could only enter my recovery and bootloader. And to make matters worse I somehow succeded to delete al my files from "sd card", HTC One doesn't have SD card slot, as you know, (it has internal storage) so I deleted all my personal files ( I backed up photos, and other personal stuff to my PC in case something like this happens )
and my SuperSU and custom ROM zip files. Then I found out about flashing stock ROM, so I relocked my device to do so but the proper RUU has prooved very hard to find, I 've tried 4-5 RUUs from htc1guru.com for Cingular (AT&T) bot none worked. Maybe I should look for SIM unlocked RUU because I 've SIM unlocked it from AT&T. Now I am really annoyed and angry because of being so stupid and trying something I obviously couldn't achieve so please don't write down trere " Oh you are a noob for doing that " because I know that and I don't need any extra comments for playing smart and bricking my device. SO PLEASE IF ANYONE ON THIS FORUM CAN HELP ME, DO SO!! If i don't manage to finally fix this somehow I'm going to pay someone to fix this.
Click to expand...
Click to collapse
Also, see if this All-in-One Toolkit that @hasoon2000 has developed helps you. It could help you get S-Off from the bootloader or recovery or help you find the proper RUU image version of your HTC One:
http://forum.xda-developers.com/showthread.php?t=2183942
Also, can you get into recovery? Like TWRP or Clockwork? Have you tried installing a rom.zip image version for your phone instead? I understand the HTC One M7 doesn't have an external SD slot, so chances are that you don't already have a rom.zip file in your phones directory but you could always sideload one through TWRP or Clockwork from ADB on your computer.
I would search the forums for an HTC One M7 rom.zip image and sideload it.
T-Mobile HTC ONE M7 bricked?
So I did something pretty dumb yesterday. Installed the HTC Sense 6 update on my HTC ONE M7, hated it so decided to root my phone to revert back to Sense 5.0 or 5.5 or potentially try a custom ROM. Downloaded a Tmobile 4.3 JB RUU, downloaded android SDK, HTC sync manager, Fastboot. I unlocked boot loader, installed Wheaton recovery by Koush, installed SU, figured phone was rooted but it wasn't. Now I've somehow succeeded in deleting EVERYTHING. Phone continues booting into recovery. Commands using Fastboot aren't recognized because it cannot find any device. When plugged in via USB, PC recognizes that something is plugged in but that's about it. I tried using a tool that was guaranteed to help me revert back by helping me re-lock bootloader but of-course that didn't work because of the error code stating "device not found". Below are the information that is currently displaying on my screen.
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.27.3218.14
Open DSP-v32.120.274.0909
OS-5.14.531.1
eMMC-boot 2048MB
May 9 2014, 15:00:26.0
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
Any help will be greatly appreciated