Hey guys,
This will be an interesting first post... I do have to say I apologize for making a thread regarding this, but I really feel like I'm stuck and would really benefit from some direct help. I've been searching non-stop for the last 2 days, and currently have more than 20 hours infront of my computer trying to figure out why I cannot restore this HTC One.
Details;
Tampered
Unlocked
M7_UL pvt ship S-ON RH
Hboot 1.55
Radio-4a.20.3263.16
OpenDSP-v32.120.274.0909
OS-3.22.631.1
eMMC-boot 2048mb
Sep17/2013
ROGERS CANADA NETWORK
-Currently cannot get any further than HBOOT and TWRP 2.6
-Ends up in boot loop
-Recognized on Fastboot, and device manager, but cannot access via My Computer
-Phone had a garbage ROM, and I ended up wiping my entire phone. Every single file.
-If I could somehow get an install onto it I could try to get it going through TWRP?
-I've downloaded several gigs of roms that I've tried, and cant seem to get them to work.
-Phone is essentially bricked and non-functional. There is a way to save it I think??
-ABD device not found, have SDK, fully updated drivers all around... nothing.
I just want the phone back to factory... but ROGERS RUU files are .zip and not .exe
Very difficult to figure out a solution...
Please help guys,
Sorry I could not get it on my own. New to phones but not new to computers and troubleshooting.
I'll leave this tab open and constantly check whilst I look for more answers on my issue.
Thank you!
-Spence
I would try sideloading a rom through TWRP. If I remember correctly, you need the latest ADB which comes bundled with this:
http://developer.android.com/sdk/index.html
I think having the latest ADB binaries may also help your PC detect your phone. Once you have that downloaded, you can sideload a rom. More info on that here:
http://teamw.in/ADBSideload
Finally got it to recognize the device on ADB
However it says unauthorized, because I assume I couldnt activate debugging.
Still cant because it's bricked!
Drivers are all up to date to the best of my knowledge
Double and triple checked?
I will try to do something through TWRP... I dont have a lot of experience with it, I know I was fighting with it for a couple hours today, trying to get through all the errors - or to detect my computer properly.
ADB Sideload Complete
Failed
Unable to mount across the board.
-Spencer
UPDATE:
Sideload seems to be working. Still getting errors for being unauthorized I think..
12:33am
Via CWM I was able to get Android Revolution HD to install, and actually went through the entire install process...
At the end it said some files were unable to be installed, and then put me back in the bootloader/cwm cycle...
I just want to get the phone stable enough to use, so that I can revert it back to stock!
-Spence
Lets just say that the phone is completely non-functional.
What would be the step by step process of addressing such a problem?
As if the phone were not working at all...?
Can't seem to get it going, no matter how hard I try!
20 hours in!
Bawshawg said:
Lets just say that the phone is completely non-functional.
What would be the step by step process of addressing such a problem?
As if the phone were not working at all...?
Can't seem to get it going, no matter how hard I try!
Flash the last TWRP (2.6.3.4)
Flash ARHD 51
Fastboot erase cache
Erase davil'k cache
20 hours in!
Click to expand...
Click to collapse
Flash the last TWRP (2.6.3.4)
Flash ARHD 51
Fastboot erase cache
Erase davil'k cache
Uxepro said:
Flash the last TWRP (2.6.3.4)
Flash ARHD 51
Fastboot erase cache
Erase davil'k cache
Click to expand...
Click to collapse
Followed by what though?
If I'm basically just starting from the hardware up?
Nothing seems to be going in my favour! :S
Bawshawg said:
Lets just say that the phone is completely non-functional.
What would be the step by step process of addressing such a problem?
As if the phone were not working at all...?
Can't seem to get it going, no matter how hard I try!
20 hours in!
Click to expand...
Click to collapse
Uxepro said:
Flash the last TWRP (2.6.3.4)
Flash ARHD 51
Fastboot erase cache
Erase davil'k cache
Click to expand...
Click to collapse
ARHD 51 will not help as it still requires s-off
I'm going to recommend these instructions posted by @SaHiLzZ
Download Canadian 1.55 HBOOT recovery: http://goo.gl/2Kntxz
Download TWRP 2.6.3.3: http://techerrata.com/file/twrp2/m7/...2.6.3.3-m7.img
Make sure you're in the bootloader go into fastboot and make sure the downloaded image is in the same folder as your fastboot.
fastboot flash recovery recovery_stock_155hboot_htc_one_m7.img
fastboot erase cache
fastboot reboot-bootloader
Go into bootloader and then choose Factory Reset - let that finish running <<< Important!
Phone will go out and start bootlooping. Now power off and go back to bootloader mode:
Go into fastboot
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Now you can go into custom recovery and you should be good to proceed.
Click to expand...
Click to collapse
Sideload should work after this
Android revolution 51 does not require S-off...
Unless you want to upgrade the firmware
Uxepro said:
Android revolution 51 does not require S-off...
Unless you want to upgrade the firmware
Click to expand...
Click to collapse
please don't confuse things ... ARHD 51 will not boot / s-on
http://forum.xda-developers.com/showpost.php?p=50085331&postcount=185
http://forum.xda-developers.com/showpost.php?p=50084310&postcount=174
try Sideloading this one >> http://xda7.androidrevolution.nl/db_mirror/ROMs/HTC_One/Android_Revolution_HD-One_31.6.zip
clsA said:
please don't confuse things ... ARHD 51 will not boot / s-on
http://forum.xda-developers.com/showpost.php?p=50085331&postcount=185
http://forum.xda-developers.com/showpost.php?p=50084310&postcount=174
Click to expand...
Click to collapse
It's an uncommon thing. It can happen, but it does not require s-off.
"You need:
HTC One unlocked with htcdev.com (S-ON) or S-OFF"
Uxepro said:
It's an uncommon thing. It can happen, but it does not require s-off.
"You need:
HTC One unlocked with htcdev.com (S-ON) or S-OFF"
Click to expand...
Click to collapse
Dude he just posted he flashed it and it won't boot .. what don't you understand ?
clsA said:
Dude he just posted he flashed it and it won't boot .. what don't you understand ?
Click to expand...
Click to collapse
It doesn't boot because he used twrp 2.6, instead of 2.6.3.3 or didn't erase cache
I was S-on and everything was fine with flashing arhd 51.
No way a rom requires s-off to be flashed, unless an upgrade of hboot is mandatory.
Folks!
Somehow, I ended up getting the HTC Guru reset to work....
After literally 24 hours of messing with this thing.
So now I am running 4.3
and in the near future will try to completely restore back to all Rogers Canada software and update to their Kitkat OTA???
Or should I just wait a bit for someone to release one that works correctly?
Thank you for the help!
-Spence
Bawshawg said:
Folks!
Somehow, I ended up getting the HTC Guru reset to work....
After literally 24 hours of messing with this thing.
So now I am running 4.3
and in the near future will try to completely restore back to all Rogers Canada software and update to their Kitkat OTA???
Or should I just wait a bit for someone to release one that works correctly?
Thank you for the help!
-Spence
Click to expand...
Click to collapse
Just upgrade your TWRP, and flash the 4.4.2 rom you want
If you can Soff, then you will be able to run RUU for dev edition kitkat, or do the google edition conversion. That will give you an upgrade path in future by OTA
sent from my mobile device
Related
For maybe some more like me that want to go back to what it use to be with the hboot S-OFF, S-ON issue.
I had my phone S-OFF with alpharevx beta. Used CM7 -stable for couple days but decided i wanted to go back to all original. I first RUU my phone with the RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_signed.exe file. Boot it up, made sured it runs, then did what is instructed below here;
To be able to do this you need HTC USB drivers installed. Install the HTC pakage, reboot, uninstall the HTC-
Sync software, keep the drivers! reboot PC again.
Power off your phone. Plug in your USB cable to phone. Press volume down and powerup your phone. After it
settle navigate down and choose fastboot option.
1. Unpack these files to your c:\fastboot
2. Open up your windows command promt (WinVista/7 users rightclick choose run as Administrator)
3. in command promt type CD\ then press enter
4. then your should be in C:\
5. type cd fastboot
6. then you should now be in dir C:\fastboot
7. Im bored to death typing, look below. Beware of each command ends with enter. After success, reboot.
C:\fastboot>fastboot oem mb 9C068490 1 30
... OKAY
C:\fastboot>fastboot flash hboot hboot_buzz_7225_1.01.0001.nb0
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... OKAY
Files needed (Windows version): megaupload.com/?d=UO9L74I9
Works perfectly for me.
* NOTE: Im not responsible for your phone if you brick/kill it. These steps worked for me!
This should help a lot of people. Cheers for your post.
Tanks a lot man, this should be Sticky
can flash hboot-0.80.0008??????
I just have a question, ehm if i want to RUU my WF, do i have to follow the procedure you described in the first post Before or After using RUU***.exe?
gabryel48 said:
I just have a question, ehm if i want to RUU my WF, do i have to follow the procedure you described in the first post Before or After using RUU***.exe?
Click to expand...
Click to collapse
After is better to avoid potential problems with Custom Recoveries and ROMs. Which is precisely what the OP says as well.
I first RUU my phone with the RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.2 4H_3.35.20.10_release_160191_signed.exe file. Boot it up, made sured it runs, then did what is instructed below here;
I had to triple check what I typed out of fear of brick, but alas, it worked like a charm!
Small Edit: This method also works with AlphaRev X (version 0.2pre5) that they just released.
Is it possible to keep the root and to flash the stock hboot to get the s-on?
shiranmotha said:
Is it possible to keep the root and to flash the stock hboot to get the s-on?
Click to expand...
Click to collapse
Seems like no one tried it yet. For such a kind of thing, just after ruu, one should root the phone with superone click root method and then go for hboot flashing. But can't expect how the results will be. I think it will not brick since it is a fast boot flash. The possibility is the stock OS then becoming instable and unbootable. If so, just think there will not be alpharevx s-off option then, since it needs a full booted phone. And since there is no custom recovery, I think it becomes hard to make it normal (don't know if Su binary can be cleared from hboot menu through clear storage).
A better thing to try is retaining the custom recovery and flashing stock hboot. But still I can predict nothing. Ofcourse it might not brick the phone. But before doing anything, it is better to take the suggestion of the devs.
Sent from my HTC Wildfire using XDA App
ok im the frist to try relocked my hboot and keeping clockwork recovery it recovery still flashes roms wipes phone still boots and rooted but if i copy anything to system it it wont let me add anything if i do all the memory on system is droped
Sent from my Blade using XDA App
thank you very much it works!!!!!!!!!!!
alpharev x logo removed and again s-on ......thnx
Has anyone tried to flash 0.80?
can you please post hboot 1.01.0002 the latest one....
rickwyatt said:
ok im the frist to try relocked my hboot and keeping clockwork recovery it recovery still flashes roms wipes phone still boots and rooted but if i copy anything to system it it wont let me add anything if i do all the memory on system is droped
Sent from my Blade using XDA App
Click to expand...
Click to collapse
The S flag is there to prevent you from damaging your phone by messing around with its system partition when the phone is on, NOT when it is off or in recovery mode!!!
can you please post hboot 1.01.0002 the latest one....and also the stock recovery for froyo wildfire
Thanks so much for this..
Downgraded from AlphaRevX to hboot 0.80.007 this morning worked prefect. (hboot_7225_0.80.0007_100809.nb0)
Buzz PVT Ship S-ON
HBOOT -0.80.007
Aug 9 2010,22:37:43
This was done on a Telstra stock rom
RUU_Buzz_Froyo_Telstra_WWE_2.38.841.1_Radio_13.55.55.24H_3.35.20.10_release_167270
I ran the Rom throw Kitchen and removed all the Telstra Apps before for installing the Rom..
Fr3ddY303 said:
Downgraded from AlphaRevX to hboot 0.80.007 this morning worked prefect. (hboot_7225_0.80.0007_100809.nb0)
Buzz PVT Ship S-ON
HBOOT -0.80.007
Aug 9 2010,22:37:43
This was done on a Telstra stock rom
RUU_Buzz_Froyo_Telstra_WWE_2.38.841.1_Radio_13.55.55.24H_3.35.20.10_release_167270
Click to expand...
Click to collapse
How did you do that. What is the fastboot command for downgrading from alpharevx hboot to stock hboot 0.80
Sent from my HTC Wildfire using XDA App
bharatgaddameedi
I just used the fastboot commands that was listed.
C:\fastboot>fastboot oem mb 9C068490 1 30
C:\fastboot>fastboot flash hboot hboot_7225_0.80.0007_100809.nb0
Thanks to DeCex
From this thread http://forum.xda-developers.com/showthread.php?t=1160251
But if you try an use unrevoked v3.32 their is and error (version is to new)
So will try sometime today and go to hboot_7225_0.80.0004_100610.nb0
Fr3ddY303 said:
But if you try an use unrevoked v3.32 their is and error (version is to new)
So will try sometime today and go to hboot_7225_0.80.0004_100610.nb0
Click to expand...
Click to collapse
Use Unrevoked 3.14 - 3.21. It will work.
lex25288 said:
The S flag is there to prevent you from damaging your phone by messing around with its system partition when the phone is on, NOT when it is off or in recovery mode!!!
Click to expand...
Click to collapse
yea! I have tried the s-on hboot1.01 and 0.80 with DK ROM ^^
It works well =D
SOLVED - check post 35
..and I don't know how to solve it. So, I would really need and appreciate your help!
Device:
m7ul s-off, currently unlocked, running cm 10.1 nightly
The problem:
I experienced reboots and fc's on various aosp roms as pa, cm and pac. cm is running best so far, on pa i lost data connection from time to time.
I tryed everything. I flashed sense roms, I flashed stock, I did a nandroid restore of stock ruu, relocked my bootloader, flashed stock recovery and everything possible to fix my device.
If I was lucky, it booted, but it shut down after a few seconds and kept bootlooping.
I can't get it back to stock and that really worries me. I did everything as explained but nothing worked.
Now to what I did with my device:
unlocked, flashed cwm, perm root
flashed cm, but coming from the nexus4 i was looking forward for pa rom
flashed a pa dev build, which was made for m7tmo. this might be the point where my troubles started. build was a bit buggy so
flashed trickdroid 6.0.0, flashed some tweaks and had major issues as no status bar and frequent reboots
went back to cm and from then on I just flashed pa or cm roms (gave pac a try but had even more issues)
everything else is already explained (the problem).
If there is any further information I have to provide you, just tell me. I don't really know much about logcat, but I could upload a log if that would help. All I see is hundreds of errors with QC-DS-LIB, LocSvc, kickstart and others..
I spent days on trying to fix my phone. I'm also afraid of bricking it with all the **** I try... Maybe someone here can help me find a solution. Please
Do you have the appropriate radio for your ROM?
http://forum.xda-developers.com/showthread.php?t=2245615
That might be the root of all evil...
I did flash 1.29.401.12 WWE OTA - 4A.14.3250.13_10.33.1150.01L while running the stable pa rom. currently I'm on 4A.13.3221.27_10.31.1131.05L (I guess stock?)
edit: it's from RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
I am not sure but all the stuff you did it is likely that something got messed up.
Which recovery do you use? Please flash that again with
fastboot erase cache
fastboot flash recovery recovery.img (*recovery.img = the exact name of the recovery as it is in your platform-tools folder) followed by
fastboot erase cache
Use only the USB cable that came with the One, and don't use a USB 3.0 under Windows 8. Maybe try a different computer as well.
Flash a Sense ROM that is close to stock, and a matching radio based.
Before flashing a ROM.zip, wipe cache/factory reset and dalvik cache within the recovery first.
Hope you get it all sorted
hardstuffmuc said:
I am not sure but all the stuff you did it is likely that something got messed up.
Which recovery do you use? Please flash that again with
fastboot erase cache
fastboot flash recovery recovery.img (*recovery.img = the exact name of the recovery as it is in your platform-tools folder) followed by
fastboot erase cache
Use only the USB cable that came with the One, and don't use a USB 3.0 under Windows 8. Maybe try a different computer as well.
Flash a Sense ROM that is close to stock, and a matching radio based.
Before flashing a ROM.zip, wipe cache/factory reset and dalvik cache within the recovery first.
Hope you get it all sorted
Click to expand...
Click to collapse
Did exactly what you said, phone got stuck on boot (with beatsaudio) for over 10 mins (this actually happened every time i tried flashing arhd). rebooted, was able to do a first setup after 3 mins. downloaded catlog, havent had the errors mentioned above so far. running smooth for now. will post again if some crazy **** happens.
Thanks!
And again, after installing some apps I got reboots. The only difference to aosp is, that I have to do a reboot by holding the home button, hence this rom gets stuck on the bootlogo. The aosp roms rebootet after 15 secs.
Sent from my HTC One using xda app-developers app
George_Mn said:
And again, after installing some apps I got reboots. The only difference to aosp is, that I have to do a reboot by holding the home button, hence this rom gets stuck on the bootlogo. The aosp roms rebootet after 15 secs.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Download the RUU for your device. boot to fastboot and relock bootloader, then install ruu.exe from PC. That will fix you up. Nandroid restore of stock ruu is different. The ruu will replace all partitions.. U have something wrong somewhere that roms dont touch i bet. The ruu should do it. If s-off and supercid you dont even need your exact ruu. Any ruu will do.
nugzo said:
Download the RUU for your device. boot to fastboot and relock bootloader, then install ruu.exe from PC. That will fix you up. Nandroid restore of stock ruu is different. The ruu will replace all partitions.. U have something wrong somewhere that roms dont touch i bet. The ruu should do it. If s-off and supercid you dont even need your exact ruu. Any ruu will do.
Click to expand...
Click to collapse
I have actually tried that. I also think it does not depend on the rom I use. Since I can't remember wether I relocked my bootloader before trying the ruu.exe I will try again.
I was also thinking about flashing boot.img but i'm afraid of bricking.
Sent from my HTC One using xda app-developers app
George_Mn said:
I have actually tried that. I also think it does not depend on the rom I use. Since I can't remember wether I relocked my bootloader before trying the ruu.exe I will try again.
I was also thinking about flashing boot.img but i'm afraid of bricking.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Just do the ruu again, it should fix you up. Boot.img is no big deal, it gets flashed with all roms. If ruu doesnt work please let us know if it successfully installed or not. If it will be like first time you powered it on (minus the s-off, that will stay) if it installed correctly. It will install correct radio and boot.img.
Have you changed your MID? i think you should just installl the latest ruu for your CID and MID.
Also have you installed different hboot? like the modded one or the eng hboot? If so have you flashed the original back? The RUU will install the correct hboot.
Sorry top say but If completed ruu doesnt fix it, its broke. Nothing software can do.
nugzo said:
Just do the ruu again, it should fix you up. Boot.img is no big deal, it gets flashed with all roms. If ruu doesnt work please let us know if it successfully installed or not. If it will be like first time you powered it on (minus the s-off, that will stay) if it installed correctly. It will install correct radio and boot.img.
Have you changed your MID? i think you should just installl the latest ruu for your CID and MID.
Also have you installed different hboot? like the modded one or the eng hboot? If so have you flashed the original back? The RUU will install the correct hboot.
Sorry top say but If completed ruu doesnt fix it, its broke. Nothing software can do.
Click to expand...
Click to collapse
No I haven't, getvar says my cid is 102 and my mid pn0710000
I think I have installed different hboot but as you said ruu will revert...
guess thats the right one?: RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
I could also try: RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13. 3227.06_10.27.1127.01_release_308001_signed_2_4.ex e
edit: omg just checked md5sum of the ruu I used earlier... there should be a tool automatically checking every md5sum. no wonder it bootlooped..
Stuck on bootscreen after installing the ruu.exe
no fastboot usb, no custom recovery
what can i do now?
George_Mn said:
Stuck on bootscreen after installing the ruu.exe
no fastboot usb, no custom recovery
what can i do now?
Click to expand...
Click to collapse
Still stuck? What happened, did pc say it finished successfully ? Takes a few minutes after ruu. Which ruu did u use?
nugzo said:
Still stuck? What happened, did pc say it finished successfully ? Takes a few minutes after ruu. Which ruu did u use?
Click to expand...
Click to collapse
I used RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
pc said it finished successfully
turned it off to not kill the battery
waited for over 10 minutes.
currently talking to htc support usa since the german support is asleep..
i can access the bootloader, thats all
George_Mn said:
I used RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
pc said it finished successfully
turned it off to not kill the battery
waited for over 10 minutes.
currently talking to htc support usa since the german support is asleep..
i can access the bootloader, thats all
Click to expand...
Click to collapse
If you wish you can unlock again, install custom recovery and then side load a rom. I'm afraid HTC will just have you try the ruu again. Or tell you it's broke.
How long did the ruu install take? Did it restart phone a few times? If it was me, I'd unlock again and install a custom rom. If that doesn't work I don't know what else to try..tried everything. Most likely Something wrong with the hardware
nugzo said:
If you wish you can unlock again, install custom recovery and then side load a rom.
Click to expand...
Click to collapse
I don't think so, my pc does not recognize my phone because usb debugging is not enabled.. any solution?
in stock recovery it says MounT SDCARD failed, so I will try fixing that by performing a few factory resets lol
George_Mn said:
I don't think so, my pc does not recognize my phone because usb debugging is not enabled.. any solution?
in stock recovery it says MounT SDCARD failed, so I will try fixing that by performing a few factory resets lol
Click to expand...
Click to collapse
When in fastboot it doesn't matter if debugging is enabled. It must say fastboot USB . If not select fastboot and press power
What hboot do you have now? Since you r s off I don't know if boot loader needs to be unlocked. If you can get to fastboot and be seen by pc,download twrp recovery and put it in your adb folder. Then "fastboot flash recovery filename.img" then u can side load.
nugzo said:
When in fastboot it doesn't matter if debugging is enabled. It must say fastboot USB . If not select fastboot and press power
What hboot do you have now? Since you r s off I don't know if boot loader needs to be unlocked. If you can get to fastboot and be seen by pc,download twrp recovery and put it in your adb folder. Then "fastboot flash recovery filename.img" then u can side load.
Click to expand...
Click to collapse
omg i'm such a stupid person... I was checking my usb ports and unplugged the cable, plugged it to my phone and yeah guess what there was no FASTBOOT USB there was just FASTBOOT ...
Okay so I can still get a rom on it that's really good news. But, there is still the other problem..
George_Mn said:
omg i'm such a stupid person... I was checking my usb ports and unplugged the cable, plugged it to my phone and yeah guess what there was no FASTBOOT USB there was just FASTBOOT ...
Okay so I can still get a rom on it that's really good news. But, there is still the other problem..
Click to expand...
Click to collapse
What's the other problem? I can help
George_Mn said:
omg i'm such a stupid person... I was checking my usb ports and unplugged the cable, plugged it to my phone and yeah guess what there was no FASTBOOT USB there was just FASTBOOT ...
Okay so I can still get a rom on it that's really good news. But, there is still the other problem..
Click to expand...
Click to collapse
What's the other prob.. We're knocking them out.. Hang in there
---------- Post added at 08:02 PM ---------- Previous post was at 07:51 PM ----------
MacHackz said:
What's the other problem? I can help
Click to expand...
Click to collapse
Mac does he have to unlock boot loader if he's s off? To flash recovery?
MacHackz said:
What's the other problem? I can help
Click to expand...
Click to collapse
Well I've been through this (ruu>stuck on boot>unlock>flash cwm>sideload rom) twice.
The problems are still reboots from time to time and app shut downs or fcs. It happens with every rom i tryed. on sense roms its stuck on bootscreen until i reboot with power button, on aosp it just reboots within 15 secs
I'll have to admit, I did the ruu on win8 with usb 3.0
When does it reboot? Sometimes upon installing apps, accessing play store, on landscape mode, on unlocking sim. Much to often to just live with it..
just sideloaded cm10.1, it's alive..
I successfully had Cyanogenmod installed, but now when I turn my phone on it stays stuck at the loading screen and goes back and forth to the HTC start up (the screen before the Cyanogen loading screen). I tried reverting back to stock using the RUU but it fails every. single. time. and there's nothing I can find that will help me at least get my phone back working.
Any help? My carrier is T-Mobile
moneyhbags said:
I successfully had Cyanogenmod installed, but now when I turn my phone on it stays stuck at the loading screen and goes back and forth to the HTC start up (the screen before the Cyanogen loading screen). I tried reverting back to stock using the RUU but it fails every. single. time. and there's nothing I can find that will help me at least get my phone back working.
Any help? My carrier is T-Mobile
Click to expand...
Click to collapse
Sounds like possibly you need to flash the boot.img on it. I think , a senior member will correct me, but if your S-On and rooted, you should do that , S-Off don't require the boot.img.
leesumm said:
Sounds like possibly you need to flash the boot.img on it. I think , a senior member will correct me, but if your S-On and rooted, you should do that , S-Off don't require the boot.img.
Click to expand...
Click to collapse
I don't know what S-On or S-Off means, but it's been like 20 minutes and it's now stuck at the HTC quietly brilliant screen.
I did do a back-up before I rooted it. I tried re-installing Cyanogenmod but the installer says my phone is unrecognizable.
edit: still stuck at Cyanogen loading screen =(
moneyhbags said:
I don't know what S-On or S-Off means, but it's been like 20 minutes and it's now stuck at the HTC quietly brilliant screen.
I did do a back-up before I rooted it. I tried re-installing Cyanogenmod but the installer says my phone is unrecognizable.
edit: still stuck at Cyanogen loading screen =(
Click to expand...
Click to collapse
S-ON or off means security is on or off, If you haven't done the mod to S-Off , your still stock S-On. To see for sure though , in the bootloader mode at the top it will say Tampered first line , then the second should say something like M7 ??? PVT ship. S-On
What recovery are you using? CWM or TWRP . Do you know or use ADB?
I just reread your OP and you said you RUU'd. why? I think too with S-On you have to relock the bootloader to RUU then unlock after boot. You can use the same unlock.bin code that you used to unlock the first time if you still have it too . Best if you done the root and everything else , do some reading on S-Off procedure and do that .
leesumm said:
S-ON or off means security is on or off, If you haven't done the mod to S-Off , your still stock S-On. To see for sure though , in the bootloader mode at the top it will say Tampered first line , then the second should say something like M7 ??? PVT ship. S-On
What recovery are you using? CWM or TWRP . Do you know or use ADB?
Click to expand...
Click to collapse
Just checked, it's Tampered, Unlocked, M7, and S-On.
I used CWM for recovery and I have ADB.
moneyhbags said:
Just checked, it's Tampered, Unlocked, M7, and S-On.
I used CWM for recovery and I have ADB.
Click to expand...
Click to collapse
I have had better luck with TWRP the latest one which is I think 2.6.3.
leesumm said:
I have had better luck with TWRP the latest one which is I think 2.6.3.
Click to expand...
Click to collapse
Yeah well I'll switch to that once I figure out how to get my phone to at least start working...
any help?
moneyhbags said:
Just checked, it's Tampered, Unlocked, M7, and S-On.
I used CWM for recovery and I have ADB.
Click to expand...
Click to collapse
I had the same problem like you... I have installed first twrp 2.6.3.3 then root the VIPER ROM, so I finelly got into the phone... Then I have flashed again vith ARHD 41.0 ROM and my phone is working perfect But I had the same problem as you... this is becouse of the S-ON and you stuck in boot-loop
moneyhbags said:
Yeah well I'll switch to that once I figure out how to get my phone to at least start working...
any help?
Click to expand...
Click to collapse
IF you can get to recovery, do you have a backup that is working ? If not you may have to unzip the CM rom, look for the boot.img , put that into the adb folder then run adb with fastboot flash boot.img , then reboot and it should go. If you have a back up of the Cm rom you might be able to go to recovery and do a restore from the backup there. And another thing you might do. Not sure if it will mess it up but/ fastboot erase cache then boot
peca_slo said:
I had the same problem like you... I have installed first twrp 2.6.3.3 then root the VIPER ROM, so I finelly got into the phone... Then I have flashed again vith ARHD 41.0 ROM and my phone is working perfect But I had the same problem as you... this is becouse of the S-ON and you stuck in boot-loop
Click to expand...
Click to collapse
I just fixed it. I downloaded the stock T-Mobile recovery.img for HTC One, then opened the command line used fastboot uploaded the recovery.img then used that to recover and it just magically reinstalled the Cyanogenmod.
moneyhbags said:
I just fixed it. I downloaded the stock T-Mobile recovery.img for HTC One, then opened the command line used fastboot uploaded the recovery.img then used that to recover and it just magically reinstalled the Cyanogenmod.
Click to expand...
Click to collapse
Good glad to know it works again.. Now do some reading on S-Off sounds like you have some idea of ADB so it really isn't that hard and it will make flashing easier in the future. You might even consider a full GPE conversion. I did it and like the Kit Kat but running Elegancia and once in a while revert back to the GPE with Xposed and Gravity Box KK for a mod. Super good battery.
moneyhbags said:
Yeah well I'll switch to that once I figure out how to get my phone to at least start working...
any help?
Click to expand...
Click to collapse
boot to recovery
clear cache and delvik
reboot to bootloader
fastboot USB and type
fastboot erase cache
now see if your phone will bootup
If no, find a different rom to flash
and here is a recovery flashable version of TWRP, flash it the same you do a rom and reboot to recovery to see it
moneyhbags said:
I just fixed it. I downloaded the stock T-Mobile recovery.img for HTC One, then opened the command line used fastboot uploaded the recovery.img then used that to recover and it just magically reinstalled the Cyanogenmod.
Click to expand...
Click to collapse
whoops looks like i got here late ..
I've been having some problems recently. I've been wanting to update to Kitkat but I have replaced the stock recovery software with CWM, and thus it doesn't work.
To solve this problem I've figured out that I need to get my claws on an RUU, which I have. Hopefully I've grabbed the right one. It doesn't seem like the RADIO serial-thingy matches though. Device has
Code:
4A.21
whilst the RUU has
Code:
4A.23
.
I've tried using the RUU in fastboot but later figured out that I need to have S-OFF for that. That is currently not the case. I've tried using both Firewater and Rumrunner. According to the instructions I'm required to have the phone on in the usual way. As in, not in the bootloader. The problem is that my phone is stuck in some restart loop. When reaching the PIN-screen it will automatically restart/crash after a few seconds. I can however use the phone as usual during this time. Sometimes, it alerts me with an error.
It also seems like the battery completely empties itself sometimes. This is when trying to restore it, getting in and out from the bootloader and the like.
Here's some software info:
CID: HTC__Y13
MIDN0710000
Bootloader info:
Code:
M7_UL PBT SHIP S-ON RH
Code:
HBOOT-1.55.0000
Code:
RADIO-4A.21.3263.04
Code:
OpenDSP-v32.120.274.0909
Code:
OS-3.62.401.1
Great thanks in advance and pardon my useless formatting (and my lacking knowledge of this forum as there might be some rules I'm not following), I'm damn tired of this device.
Tmplt said:
I've been having some problems recently. I've been wanting to update to Kitkat but I have replaced the stock recovery software with CWM, and thus it doesn't work.
To solve this problem I've figured out that I need to get my claws on an RUU, which I have. Hopefully I've grabbed the right one. It doesn't seem like the RADIO serial-thingy matches though. Device has
Code:
4A.21
whilst the RUU has
Code:
4A.23
.
I've tried using the RUU in fastboot but later figured out that I need to have S-OFF for that. That is currently not the case. I've tried using both Firewater and Rumrunner. According to the instructions I'm required to have the phone on in the usual way. As in, not in the bootloader. The problem is that my phone is stuck in some restart loop. When reaching the PIN-screen it will automatically restart/crash after a few seconds. I can however use the phone as usual during this time. Sometimes, it alerts me with an error.
It also seems like the battery completely empties itself sometimes. This is when trying to restore it, getting in and out from the bootloader and the like.
Here's some software info:
CID: HTC__Y13
MIDN0710000
Bootloader info:
Code:
M7_UL PBT SHIP S-ON RH
Code:
HBOOT-1.55.0000
Code:
RADIO-4A.21.3263.04
Code:
OpenDSP-v32.120.274.0909
Code:
OS-3.62.401.1
Great thanks in advance and pardon my useless formatting (and my lacking knowledge of this forum as there might be some rules I'm not following), I'm damn tired of this device.
Click to expand...
Click to collapse
If the RUU is an .exe file, then try placing it in the same folder as your ADB/FASTBOOT files. Plug-in your phone to your PC so that it is recognized on the PC then double click the RUU.exe file. Follow the on-screen instructions. You don't need S-OFF to run an RUU for your phone with the correct CID & MID providing the RUU is the same version or higher.
majmoz said:
If the RUU is an .exe file, then try placing it in the same folder as your ADB/FASTBOOT files. Plug-in your phone to your PC so that it is recognized on the PC then double click the RUU.exe file. Follow the on-screen instructions. You don't need S-OFF to run an RUU for your phone with the correct CID & MID providing the RUU is the same version or higher.
Click to expand...
Click to collapse
sigh... How could I be so dense? I should know this. Thanks for the quick response. I will try this at once.
majmoz said:
If the RUU is an .exe file, then try placing it in the same folder as your ADB/FASTBOOT files. Plug-in your phone to your PC so that it is recognized on the PC then double click the RUU.exe file. Follow the on-screen instructions. You don't need S-OFF to run an RUU for your phone with the correct CID & MID providing the RUU is the same version or higher.
Click to expand...
Click to collapse
The RUU crashes when launching it, "InstallScript Setup Launcher has stopped working". I'm quite sure I have the required stuff to run it. Running it as admin didn't help.
Tmplt said:
The RUU crashes when launching it, "InstallScript Setup Launcher has stopped working". I'm quite sure I have the required stuff to run it. Running it as admin didn't help.
Click to expand...
Click to collapse
It looks like a PC issue. Check out this post Installscript setup launcher has stopped working! In the reply they list two methods it looks like you did the first one. Sometimes, I just have to reboot the computer to get everything set correctly.
majmoz said:
It looks like a PC issue. Check out this post ** In the reply they list two methods it looks like you did the first one. Sometimes, I just have to reboot the computer to get everything set correctly.
Click to expand...
Click to collapse
Unfortunately, none of these methods helps. The device is supposed to be in Fastboot USB mode when the RUU is launched, yes?
Tmplt said:
Unfortunately, none of these methods helps. The device is supposed to be in Fastboot USB mode when the RUU is launched, yes?
Click to expand...
Click to collapse
what is the ruu version you are trying to use (complete file name)?
easiest way: download this guru reset file, its exactly the same version you have on your phone now.
http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
put TWRP 2.6.3.3 (recommended) recovery on your phone
copy the zip to your SDcard
Enter recovery and flash like you would do with a custom rom
in the Aroma installer, select wipe data, install stock recovery, install stock radio when prompted.
This file will put you back to fully stock.
Help also
Hi, I'm a newbie and I was supposed to post a thread regarding a problem I'm facing similar to this. So if it's alright, I'll post it here also and ask for your advice. I recently unlocked my HTC One w/ 4.4.2 amd Sense 6.0 a few days ago and was also able to flash CWM custom recovery and root it. I then tried flashing the latest Android Revolution HD, when I rebooted the phone after intallation, it just stays on the first spash screen. I forgot that I needed to S-off my device. So now, I can only access the bootloader and recovery. The status of my device currently is *Tampered*, Unlocked and S-On with 1.57 Hboot. Also, I can't copy files from my PC to the device. I don't know what to do. I've been reading around but I think I need some concrete advice. Thank you in advance.
Baconnugget said:
Hi, I'm a newbie and I was supposed to post a thread regarding a problem I'm facing similar to this. So if it's alright, I'll post it here also and ask for your advice. I recently unlocked my HTC One w/ 4.4.2 amd Sense 6.0 a few days ago and was also able to flash CWM custom recovery and root it. I then tried flashing the latest Android Revolution HD, when I rebooted the phone after intallation, it just stays on the first spash screen. I forgot that I needed to S-off my device. So now, I can only access the bootloader and recovery. The status of my device currently is *Tampered*, Unlocked and S-On with 1.57 Hboot. Also, I can't copy files from my PC to the device. I don't know what to do. I've been reading around but I think I need some concrete advice. Thank you in advance.
Click to expand...
Click to collapse
Best to start your own thread, but on a quick fix, your problem is CWM, you need to use TWRP recovery to flash that rom, also recommend 2.6.3.3
Tampered and unlocked is normal, nothing to worry about, and you don't need s-off to flash custom rom's, just an unlocked bootloader
alray said:
what is the ruu version you are trying to use (complete file name)?
Click to expand...
Click to collapse
Bugger, I have it renamed to RUU.exe and it's md5 doesn't match any file from the site I remember I downloaded it from. I am, however, currently downloading
Code:
RUU_M7_UL_K44_SENSE55_MR_O2_UK_4.20.206.16_Radio_4A.23.3263.28_10.38r.1157.04L_release_353143_signed_2.exe
CID and MID matches, but I didn't buy it in the UK. It was bought in Europe.
Seanie280672 said:
Best to start your own thread, but on a quick fix, your problem is CWM, you need to use TWRP recovery to flash that rom, also recommend 2.6.3.3
Tampered and unlocked is normal, nothing to worry about, and you don't need s-off to flash custom rom's, just an unlocked bootloader
Click to expand...
Click to collapse
Thank you, I appreciate your advice. I tried flashing TWRP recovery but when I go into TWRP recovery, my touchscreen doesn't respond. Any thoughts on why? It works when I'm on CWM though.
Tmplt said:
Bugger, I have it renamed to RUU.exe and it's md5 doesn't match any file from the site I remember I downloaded it from. I am, however, currently downloading
Code:
RUU_M7_UL_K44_SENSE55_MR_O2_UK_4.20.206.16_Radio_4A.23.3263.28_10.38r.1157.04L_release_353143_signed_2.exe
CID and MID matches, but I didn't buy it in the UK. It was bought in Europe.
Click to expand...
Click to collapse
Did you name that file yourself, that's the wrong file, that one is O2 "206", hence 4.20.206.16 you need 401, 3.62.401.1 which is WWE, the same number under your os information in your first post and the same as the guru reset I linked.
Tmplt said:
Bugger, I have it renamed to RUU.exe and it's md5 doesn't match any file from the site I remember I downloaded it from. I am, however, currently downloading
Code:
RUU_M7_UL_K44_SENSE55_MR_O2_UK_4.20.206.16_Radio_4A.23.3263.28_10.38r.1157.04L_release_353143_signed_2.exe
CID and MID matches, but I didn't buy it in the UK. It was bought in Europe.
Click to expand...
Click to collapse
download this file: http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
this is a reset rom
flash it from twrp 2.6.3.3 or from cwm recovery
select to restore stock radio and stock recovery
then you'll be fine to take ota updates.
the file you are currently downloading isnt for your phone.
edit:
well @Seanie280672 already suggested you to do this (just saw his previous post)
will be the easiest and fastest solution in your case.
Seanie280672 said:
easiest way: download this guru reset file, its exactly the same version you have on your phone now.
**
put TWRP 2.6.3.3 (recommended) recovery on your phone
copy the zip to your SDcard
Enter recovery and flash like you would do with a custom rom
in the Aroma installer, select wipe data, install stock recovery, install stock radio when prompted.
This file will put you back to fully stock.
Click to expand...
Click to collapse
TWRP 2.6.3.3 has been flashed and I'm currently downloading the .zip file. Is there a way to put the archive on the device staying in TWRP/Fastboot?
Tmplt said:
TWRP 2.6.3.3 has been flashed and I'm currently downloading the .zip file. Is there a way to put the archive on the device staying in TWRP/Fastboot?
Click to expand...
Click to collapse
with your phone booted in twrp main menu, and the rom.zip in the same folder of adb.exe and fasboot.exe:
Code:
adb push guru_reset_m7_3.62.401.1.zip /sdcard/
wait for the file to transfer (5-10 min) (there is no progress bar just wait adb to tell you the file transfer is complete)
then in twrp hit "install" and then choose guru_reset_m7_3.62.401.1.zip
alray said:
with your phone booted in twrp main menu, and the rom.zip in the same folder of adb.exe and fasboot.exe:
Code:
adb push guru_reset_m7_3.62.401.1.zip /sdcard/
wait for the file to transfer (5-10 min) (there is no progress bar just wait adb to tell you the file transfer is complete)
then in twrp hit "install" and then choose guru_reset_m7_3.62.401.1.zip
Click to expand...
Click to collapse
Thanks!
On an unrelated side-note; if I "thank" someone in the forum, does that count as an upvote or a complete fix regarding my problem (like StackOverflow works)?
Tmplt said:
if I "thank" someone in the forum, does that count as an upvote or a complete fix regarding my problem (like StackOverflow works)?
Click to expand...
Click to collapse
no, hitting the "thank" button doesn't count as an upvote like on other forum. This is only to say thank you to a person who helped you.
Seanie280672 said:
easiest way: download this guru reset file, its exactly the same version you have on your phone now.
**
put TWRP 2.6.3.3 (recommended) recovery on your phone
copy the zip to your SDcard
Enter recovery and flash like you would do with a custom rom
in the Aroma installer, select wipe data, install stock recovery, install stock radio when prompted.
This file will put you back to fully stock.
Click to expand...
Click to collapse
alray said:
download this file: **
this is a reset rom
flash it from twrp 2.6.3.3 or from cwm recovery
select to restore stock radio and stock recovery
then you'll be fine to take ota updates.
the file you are currently downloading isnt for your phone.
edit:
well @Seanie280672 already suggested you to do this (just saw his previous post)
will be the easiest and fastest solution in your case.
Click to expand...
Click to collapse
alray said:
with your phone booted in twrp main menu, and the rom.zip in the same folder of adb.exe and fasboot.exe:
Code:
adb push guru_reset_m7_3.62.401.1.zip /sdcard/
wait for the file to transfer (5-10 min) (there is no progress bar just wait adb to tell you the file transfer is complete)
then in twrp hit "install" and then choose guru_reset_m7_3.62.401.1.zip
Click to expand...
Click to collapse
The ROM was successfully installed and I'm currently configuring my phone! The phone did not implode when restarting, something I take as a sign of a functional phone! A truckload of thanks for the both of ya!
Long story short usually first thing I do is root and rom my phones, but I recently got an HTC One off of swappa and loved it, didnt see a reason to root. I figured I would give dual-booting via multiboot a shot, so I HTC Dev unlocked it, rooted it, installed elemental kernel, and flashed CM11. Well CM11 wouldnt boot and I tinkered so I just figured I would cut my losses, so I followed the instructions to remove it which wiped my SD card. I was on linux, and couldn't get fastboot usb, just fastboot ac. So I hopped on a friends computer, Win8.1 and downloaded a special set of drivers and whatnot, got ADB and fastboot running. TWRP wasnt working very well, it wouldnt let me use ADB so I fastboot installed CWM. I managed to push cyanogenmod to it, but kept getting an error that wouldnt let me install it. So I figured next thing to do would be RUU it, and I got my version number and matched the CID and all that, it failed with an error 12. Both .exe and .zip give me the same error. Well not its 3am and I've been at it for 5 hours now, I dont know what to do. It seems like everything I try to do fails. Please give me some advice.
RELOCKED
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.000
RADIO-4T.27.3218.14
OS-
eMMC-boot 2048MB
flapflip22 said:
Long story short usually first thing I do is root and rom my phones, but I recently got an HTC One off of swappa and loved it, didnt see a reason to root. I figured I would give dual-booting via multiboot a shot, so I HTC Dev unlocked it, rooted it, installed elemental kernel, and flashed CM11. Well CM11 wouldnt boot and I tinkered so I just figured I would cut my losses, so I followed the instructions to remove it which wiped my SD card. I was on linux, and couldn't get fastboot usb, just fastboot ac. So I hopped on a friends computer, Win8.1 and downloaded a special set of drivers and whatnot, got ADB and fastboot running. TWRP wasnt working very well, it wouldnt let me use ADB so I fastboot installed CWM. I managed to push cyanogenmod to it, but kept getting an error that wouldnt let me install it. So I figured next thing to do would be RUU it, and I got my version number and matched the CID and all that, it failed with an error 12. Both .exe and .zip give me the same error. Well not its 3am and I've been at it for 5 hours now, I dont know what to do. It seems like everything I try to do fails. Please give me some advice.
RELOCKED
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.000
RADIO-4T.27.3218.14
OS-
eMMC-boot 2048MB
Click to expand...
Click to collapse
Your problems started at trying to install cm11 with elementalx kernel, that's a sense kernel and cm is not a sense Rom, so unlock your bootloader again and flash twrp 2.6.3.3 to your phone, push a sense Rom of your choice to the phone and flash it, I'm guessing the ruu isn't working as you can't back flash with s-on and you already have the newest os / firmware on your phone according to your hboot version
Seanie280672 said:
Your problems started at trying to install cm11 with elementalx kernel, that's a sense kernel and cm is not a sense Rom, so unlock your bootloader again and flash twrp 2.6.3.3 to your phone, push a sense Rom of your choice to the phone and flash it, I'm guessing the ruu isn't working as you can't back flash with s-on and you already have the newest os / firmware on your phone according to your hboot version
Click to expand...
Click to collapse
Will give this a try, thanks
and dont forget, 4.4+ sense roms (i.e arhd) must be flashed using twrp 2.6.3.3 or 2.6.3.4 and newest CM11 roms must be flashed using twrp 2.7.1.1 because of the new fstab layout introduced May, 2014
alray said:
and dont forget, 4.4+ sense roms (i.e arhd) must be flashed using twrp 2.6.3.3 or 2.6.3.4 and newest CM11 roms must be flashed using twrp 2.7.1.1 because of the new fstab layout introduced May, 2014
Click to expand...
Click to collapse
Noted, just flased 2.6.3.3 and adb pushing a sense 6 rom. Kinda funny, 2.6.3.3 connects to adb on linux but no other recovery would. Granted it wont let me side-load but as long as I can push files I'm good. Just tested it by pushing a random zip file, all is good. Just gonna wait for it to finish downloading, adb push it and try to flash it. If all goes as well as I hope it should work. I'll let you guys know if I need more help.
Thank you so much.
flapflip22 said:
Noted, just flased 2.6.3.3 and adb pushing a sense 6 rom. Kinda funny, 2.6.3.3 connects to adb on linux but no other recovery would. Granted it wont let me side-load but as long as I can push files I'm good. Just tested it by pushing a random zip file, all is good. Just gonna wait for it to finish downloading, adb push it and try to flash it. If all goes as well as I hope it should work. I'll let you guys know if I need more help.
Thank you so much.
Click to expand...
Click to collapse
if you cant sideload its probably because you are using an outdated version of adb. latest version of adb is 1.0.31. however, you'll be fine using adb push.
alray said:
if you cant sideload its probably because you are using an outdated version of adb. latest version of adb is 1.0.31. however, you'll be fine using adb push.
Click to expand...
Click to collapse
Alright, managed to adb push to files to my phone but now it just says "updating partition details..." then "error flashing zip /sdcard/myrom.zip" and FAILED at the bottom. What next?
flapflip22 said:
Alright, managed to adb push to files to my phone but now it just says "updating partition details..." then "error flashing zip /sdcard/myrom.zip" and FAILED at the bottom. What next?
Click to expand...
Click to collapse
you might want to wipe everything + format data then push the rom again and install it. Also check MD5 of the rom
alray said:
you might want to wipe everything + format data then push the rom again and install it. Also check MD5 of the rom
Click to expand...
Click to collapse
It worked! Followed your instructions, then I used a CM 10.2 rom and a JB kernel and it worked just fine. Next I'm gonna s-off and superCID it so I wont have to go through any of this again, and then flash the ROM and kernel I want. Probably not gonna tinker anymore until later when the newest HTC sense release comes out.
flapflip22 said:
It worked! Followed your instructions, then I used a CM 10.2 rom and a JB kernel and it worked just fine. Next I'm gonna s-off and superCID it so I wont have to go through any of this again, and then flash the ROM and kernel I want. Probably not gonna tinker anymore until later when the newest HTC sense release comes out.
Click to expand...
Click to collapse
:good: happy flashing