[History]
I suspect the phone was edited before
bought the phone used. It is unlocked. The phone was constantly rebooting, I bought a lemon from some low life.
Sent the phone in to Rogers [Canada] to get fixed.
Rebooting was fixed (YEAH!).
I proceeded to unlock the bootloader and install ViperOne.
Once ViperOne was installed, I noticed the camera wasn't working.
NOTE: I did not A) check if the camera worked once I got it back. B) I didn't update my phone from STOCK when I got it back.
[Where I am now]
relocked the phone.
I used the Signed RUU exe from htc1guru -- Rogers edition.
I then used the stock ROM to update the phone.
M7 is now Lollipop.
Still no Camera.
Unlocked phone, installed newest TWRP, newest ViperOne [8.0.0.0, I believe].
no camera, but I was expecting that haha.
[Specs]
See Attached.
Thoughts, suggestions?
I had the same issue as you have.
There may be two areas of investigation.
a) Faulty Camera - failing to initialise and therefore creating an error.
Solution - get a new camera replaced.
b) Daughter board may be faulty.
Solution - get a new replacement daughter board.
c) A combination of both.
Hope that helps.....?
cheers
_FBi said:
[History]
I suspect the phone was edited before
bought the phone used. It is unlocked. The phone was constantly rebooting, I bought a lemon from some low life.
Sent the phone in to Rogers [Canada] to get fixed.
Rebooting was fixed (YEAH!).
I proceeded to unlock the bootloader and install ViperOne.
Once ViperOne was installed, I noticed the camera wasn't working.
NOTE: I did not A) check if the camera worked once I got it back. B) I didn't update my phone from STOCK when I got it back.
[Where I am now]
relocked the phone.
I used the Signed RUU exe from htc1guru -- Rogers edition.
I then used the stock ROM to update the phone.
M7 is now Lollipop.
Still no Camera.
Unlocked phone, installed newest TWRP, newest ViperOne [8.0.0.0, I believe].
no camera, but I was expecting that haha.
[Specs]
See Attached.
Thoughts, suggestions?
Click to expand...
Click to collapse
Best suggestion so far haha
Thanks!
Related
Hello,
I have a stock Bell HTC Raider, locked, unrooted, basically never touched, all original software and state. It is updated to latest OTA software.
I'm trying to wipe it and reinstall the stock rom because it is starting to act funny and I want to start from scratch.
I am trying to flash the version 3.5 bell RUU, and it will see that I have version 3.38 on phone, and RUU is same version 3.38, and when I click "next" it will go to screen which says "sending" and it will just hang there. The "sending" progress bar just keep incrementing continuously but nothing else happens. the phone is on the white HTC logo.
I gave up after 2 hours of this. Tried several times. Phone info is not wiped, same old ROM is still on it with my apps and everything.
I also tried to put the PH39.zip file for rogers on the card (can't find one for bell) and it gives me a "wrong CID, flash fail" error.
I'm running windows 7, I am admin on the PC, I also ran the RUU as administrator.
I installed latest HTC Synch, and I can open the phone as a USB drive and copy data to it, but I don't see it in HTC synch.
HTC synch does automatically launch when I plug phone in, so it sees something, but when I go to the "home" tab it says that no device is connected. I did select "htc synch" as the connection method on phone. USB debug mode is on.
Any ideas of what could be wrong?
Is there any working link for the PH39 zip file for bell?
each umaxces
Update:
in the mean time I bit the bullet and unlocked the bootloader (still S-ON), put WCX recovery on and flashed the cyanogenmod 11 *kitkat) rom.
That had the low call volume problem, so I flashed Holic's 1.3 ROM (back to ICS) which so far works perfectly.
So I am in fact able to flash other roms in recovery but I can't get back to stock using the Bell RUU.
If I ever want to return to stock, what do I do?
tudorvictor said:
Update:
in the mean time I bit the bullet and unlocked the bootloader (still S-ON), put WCX recovery on and flashed the cyanogenmod 11 *kitkat) rom.
That had the low call volume problem, so I flashed Holic's 1.3 ROM (back to ICS) which so far works perfectly.
So I am in fact able to flash other roms in recovery but I can't get back to stock using the Bell RUU.
If I ever want to return to stock, what do I do?
Click to expand...
Click to collapse
Might want to check out http://forum.xda-developers.com/showthread.php?t=2013122 which explains:
How to run the RUU
1: Make sure your bootloader is re-locked and by using the fastboot oem lock code
2: Plug in your device and make sure you have the drivers installed ( or HTC Sync )
3: Run the RUU specific to your carrier and wait for it to load ( could take up to 20 min depending on your PC )
4: A box should popup on your screen and a progress bar will be shown ( wait )
5: Once it's done loading follow the steps to return to stock.
6: You are now unrooted
Been years since I did that. KitKat low volume? Are you running the latest nightly? http://www.chronic-buildbox.com/nightly/holiday/ Best rom I've tried and I've tried em all. (Can't wait to see what pacman can add to what Albinoman is doing an awesome job with)
I managed to return to stock using the RUU without problems.
I didn't do anything different this time, it's just that I wasn't trying to flash the stock ROM while already on the stock ROM.
Maybe that doesn't work?
you can close this thread now. thanks.
Hi guys,
this is gonna be a long story, but I'm at end of my wits.
So my phone (HTC One M7_UL Vodafone DE) got water damaged (it was submerged in water for at least a minute). I tested it again last weekend and it seemed to work in terms of hardware. I managed to test the speakers, the charge jack, the headphones jack, wifi, gsm, both cameras, etc. it all seems to work fine, and it's not about that anyways. I kept getting a "com.htc.htcdialer" issue, saying the process had unexpectedly crashed and then a few minutes later the phone would reboot. I tried finding out what this error was and how to fix it but I couldnt find anything. Also its weird that I got a software error.
So I unlocked the bootloader (via htcdev.com), flashed the latest recovery (I tried both cwm and twrp), which was also fine. I managed to install the latest Android Revolutions HD (53.0) and thats where the problems started again: I would get to the lock screen but as soon as I would swipe up to unlock it I would the white screen with the HTC letters on it. I tried wiiping all the cache and partitions i could find and reinstalled that rom, but the problem remained the same. Tried a different recovery (twrp) repeated all the steps and still no more luck than before.
So I decided to give a different rom a try and just flashed the latest stable cyanogenmod rom on it, and that boots fine, but eventually without error message reboots as well.
Then I tried flashing the latest viper rom, but there I have the same issue as at the beginning, that I get as far as the lock screen and then it just wont let me unlock it.
And that's where Im at the end of my wits. I cant imagine its a hardware related issue, but i might be wrong.
Ideally I would love to get my hands on a nandroid backup to restore the phone to stock, a stock rom ruu, but I cant find any of those either.
I'd really appreciate your help.
Let me know if you need specific details of installations, versions, decide numbers, etc
Ok Kinda long but want to cover everything:
So I rooted my htc one m8 (sprint) about 6 months ago I have twrp recovery and I flashed android revolution 8. A few months later I installed android revolution 11 no problems with it what so ever. A cpl days ago I tried to flash android revolution 22 but had no luck just kept boot looping and I lost everything on my phone after some research It seems I wouldnt be able to go to kit kat 4.4.4 without going back to stock rom so I relocked my bootloader ran rom utility updater and flashed it back to stock and reset up my phone tried to flash over to android revolution again after unlocking bootloader and all that good stuff still did not work so just decided to go back to stick 4.4.4 kept bootloader locked and didn't re root my phone didn't see much of a need to at this point could only seem to use stock but anyway after a day or so of phone running just fine well today it wont connect to my mobile network or wifi (can't make or receive phone calls can't send or receive texts and am unabke to get any internet on my phone wont even connect to wif) I have even restored the phone from original back-up that I had also tried 2 other back-ups of stock roms the phone is pretty much just an mp3 player at this point sprint said everything was fine on their end nothing they can do all the icons are there for 4g and wifi and such the phone shows me its connected to sprint shows signal strength and all that so I don't know whats wrong and don't think htc will help me since I rooted it hopefully some one here can i'm
well I must be screwed if over 300 views on my post and not reply well that's what I get I guess
As far as I know ARHD is not Sprint compatible so you probably messed up your partitions.
RUU will fix it.
Only flash roms that are in the Sprint section.
Apart from compatibility off ARHD to Sprint M8 ... There is also that dreaded HTC service pack that was released on 11th Dec which screwed the network n Wi-Fi on my phone (stock Rom)
First time itty happened due to auto update install via play store and started working after I did multiple attempts at cache delete through TWRP
2nd time even after researching and knowing the service pack was the culprit I thought I should try...ending up with factory reset...so do check it
If you too had that service pack installed
Btw even htc acknowledges the sh#@ this update is causing to the phones and wants to collect more data... I don't know if anything else can be called a legit rip off or not...
BD619 said:
As far as I know ARHD is not Sprint compatible so you probably messed up your partitions.
RUU will fix it.
Only flash roms that are in the Sprint section.
Click to expand...
Click to collapse
I used ruu after I tried to flash it and messed everything up and everything worked fine after a cpl days of it working is when it started to have the networking issues I used ruu several times after and it didn't work still is there a different version I need?
I have an untouched HTC One M7 Google Play Edition phone that is stuck on Android 4.4.4. I am not sure what I should do at this point to get lollipop. I tried manually updating the phone by booting into recovery mode and selecting "Apply from phone storage". (I previously manually downloaded the update on the phone). This just quickly flashes "invalid operation" on the screen and the phone reboots. I see that there are many directions I can go from here, but I am not sure which one is best for my phone. I have concluded that Google has forgotten about me and I am not going to automatically get Lollipop. Incidentally, I bought my phone unlocked from Expansys and not from a Carrier. I am currently with Telus.
MZimbaro said:
I have an untouched HTC One M7 Google Play Edition phone that is stuck on Android 4.4.4. I am not sure what I should do at this point to get lollipop. I tried manually updating the phone by booting into recovery mode and selecting "Apply from phone storage". (I previously manually downloaded the update on the phone). This just quickly flashes "invalid operation" on the screen and the phone reboots. I see that there are many directions I can go from here, but I am not sure which one is best for my phone. I have concluded that Google has forgotten about me and I am not going to automatically get Lollipop. Incidentally, I bought my phone unlocked from Expansys and not from a Carrier. I am currently with Telus.
Click to expand...
Click to collapse
Anybody?
Hey all,
Looking for some assistance here. I apologize in advance for not having specifics on everything, but it's been a couple years since I've needed to do anything with this phone (SM-G900A). I picked it up used a couple years ago and shortly after, I did a NOX unlock and rooted the phone for two reasons - using Titanium Backup and to unlock the WiFi hot spot. I recently noticed that something had happened and my root access wasn't working correctly- guessing from one of the OTA updates that was attempting to occur on my phone. I say attempt, because I don't believe they ever successfully installed since they always seemed to error out. I'm currently on StraightTalk, not an AT&T customer. Something weird was up with it though, because I could never uninstall the Xposed Framework or app, yet Pokémon Go was recognizing it was rooted and blocking my access. I should also mention that I had towelroot running on the phone and it's showing the custom unlocked padlock on startup.
Fast forward to last night- I wanted to return it back to the stock ROM so I did my research, found a couple different tutorials that included the correct ROMs and applied one - G900AUCU1ANCE_G900AATT1ANCE_ATT.zip. After flashing, the phone will not boot and freezes halfway through the swirls around the Samsung logo, then goes blank. The blue notification light also stays lit on the phone.
Thinking it was most likely bootloader related, I found another ROM that included separate AP, BL, CSC files. I attempted to flash the bootloader, which failed and I got the following error on the phone - SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
At any rate, it seems like my boot loader somehow got corrupted or isn't compatible with this ROM, but I was hoping some of you experts out there could provide some answers. At this point my phone is dead, so I'm hoping I can get it restored very soon.
Thanks in advance guys!
The issue identified in this thread (http://forum.xda-developers.com/galaxy-s5/help/g900a-stuck-samsung-logo-black-screen-d-t3050369) seems very similar to mine as well as what's described on this website- http://www.galaxys5update.com/fix-black-screen-with-pulsating-blue-led-on-galaxy-s5-g900a/
I'm seeing the pulsing blue light as well. How do I find the 4.4.4 OA1 Kernel identified in the first link?