Related
I am done with ROMs. There, I said it. The fact is, that they are usually more buggy than the stock ROM, and they really tend to jack things up when you want to revert.
The last one changed the MainVer and I cannot seem to get the phone back to stock. I followed the instructions for fixing Mainver, doesn't work.
Tried to RUU and also use the PH98IMG.Zip from HBoot, but those don't work because the last ROM changed the Mainver so neither of those methods work any more.
I thought I had it fixed by using Scott's CleanFlash tool to push the stock kernel to the phone and it did work for awhile, but now my phone is stuck in a bootloop and I really need to get this fixed, I need to get it to do a real RUU and completely restore the phone to stock. I can then just root it and debloat it and stop messing with ROMs which frankly are never enough benefit to justify the harm and aggravation they cause.
So can someone please point me in the right direction to find a way to correct Mainver so that I can just restore the phone with the latest OTA version of RUU and then leave my phone alone and stop messing it up? LOL
SquireSCA said:
I am done with ROMs. There, I said it. The fact is, that they are usually more buggy than the stock ROM, and they really tend to jack things up when you want to revert.
The last one changed the MainVer and I cannot seem to get the phone back to stock. I followed the instructions for fixing Mainver, doesn't work.
Tried to RUU and also use the PH98IMG.Zip from HBoot, but those don't work because the last ROM changed the Mainver so neither of those methods work any more.
I thought I had it fixed by using Scott's CleanFlash tool to push the stock kernel to the phone and it did work for awhile, but now my phone is stuck in a bootloop and I really need to get this fixed, I need to get it to do a real RUU and completely restore the phone to stock. I can then just root it and debloat it and stop messing with ROMs which frankly are never enough benefit to justify the harm and aggravation they cause.
So can someone please point me in the right direction to find a way to correct Mainver so that I can just restore the phone with the latest OTA version of RUU and then leave my phone alone and stop messing it up? LOL
Click to expand...
Click to collapse
I think I may have solved it. I think I finally got the Mainver fixed and RUU appears to be working, finally.
But I am still done with ROM's until an ICS OTA is pushed out. LOL
If anyone sees me installing a ROM before then, feel free to kick me in the neck...
SquireSCA said:
I think I may have solved it. I think I finally got the Mainver fixed and RUU appears to be working, finally.
But I am still done with ROM's until an ICS OTA is pushed out. LOL
If anyone sees me installing a ROM before then, feel free to kick me in the neck...
Click to expand...
Click to collapse
It's not all that bad bro.... ROM'ing = patience + experimentation + phone insurance.
That sucks you have been having so much trouble man. The whole change to a device with a only an unlocked bootloader along with the newer android version is really throwing Devs and Users for a loop. There is a lot to learn.
I hope all these events don't make you stray from flashing forever!
Sorry you've had such bad luck. My experience with custom roms has been the opposite. I've taken mediocre phones with buggy/laggy stock roms and turned them into solid, stable devices. Some of the features and extras baked into custom roms are so nice. I'm running Scott's Clean GB 1.6 and it has been 100% stable. I haven't had any fc's or reboots, and everything works. And no bloat!
Sent from my ADR6425LVW using XDA App
SquireSCA said:
I think I may have solved it. I think I finally got the Mainver fixed and RUU appears to be working, finally.
But I am still done with ROM's until an ICS OTA is pushed out. LOL
If anyone sees me installing a ROM before then, feel free to kick me in the neck...
Click to expand...
Click to collapse
Glad you got it fixed and working again Squire, what was your hang up by the way with getting the RUU to run ? I know you were having trouble getting it to see your device what ended up being the issue ?
Marcismo55 said:
That sucks you have been having so much trouble man. The whole change to a device with a only an unlocked bootloader along with the newer android version is really throwing Devs and Users for a loop. There is a lot to learn.
I hope all these events don't make you stray from flashing forever!
Click to expand...
Click to collapse
Yeah, it really is weird. In a lot of ways, I prefer the DroidX and Motorola experiences I had. They may have an encrypted bootloader, but you could still install ROMs and it sorta helped keep you from messing up the phone, and SDLite always worked for me.
Part of me wonders what the ROM craze is all about. I mean, I fall into it myself, but then I ask myself, why do I do this? I have yet to see a ROM that runs as well as the stock one, once you root and debloat it. Sure, some of them look nice, but when you see what bugs there are, how many things don't work, and then the issues that can come up when you have to revert... I dunno... I start out all jazzed up and then more frustrated than ever when they just never seem to work properly...
SquireSCA said:
Yeah, it really is weird. In a lot of ways, I prefer the DroidX and Motorola experiences I had. They may have an encrypted bootloader, but you could still install ROMs and it sorta helped keep you from messing up the phone, and SDLite always worked for me.
Part of me wonders what the ROM craze is all about. I mean, I fall into it myself, but then I ask myself, why do I do this? I have yet to see a ROM that runs as well as the stock one, once you root and debloat it. Sure, some of them look nice, but when you see what bugs there are, how many things don't work, and then the issues that can come up when you have to revert... I dunno... I start out all jazzed up and then more frustrated than ever when they just never seem to work properly...
Click to expand...
Click to collapse
I think some of the issue seems to be how much you need all the parts to work flawlessly for work. As far as my usage and what apps I use, I really can't complain about any of the builds. I just text, surf, browse the internet and play games and music. I never use exchange, blue tooth and those seem to be the biggest flaws with the leaks. So for me the experience is totally different. I think it really all depends on the users needs obviously. To bad you can't get work to spring for one phone for you and then you can have your personal phone to play with
But even the stock ROMs piss me off. I just did an RUU, unlocked it, rooted it, tested to make sure SU is installed and updated, and neither TI pro or ROM Toolbox can freeze my bloat apps. And Scott's CleanTool was never updated to work with the latest OTA, so I am left wondering how the hell I am supposed to disable all this crap.
There are definitely days when the iPhone and "just working" look very appealing... sigh...
I also think that part of the problem is that a lot of the apps and things are disjointed and don't work properly. There is no real checks and balances in the Androiud world, no review process. Any college kid taking a programming course is a "software engineer" and the results are that half the apps and stuff out there are hit or miss at best. It takes forever to weed through all the crap to find the one or two apps that actually work right...
This inability to debloat is driving me nuts.
This is what I am talking about, the plethora of **** apps out there that just don't work. ROM Toolbox, granted root access, go in and grab an app like Blockbuster and tell it to Freeze it.
says it is doing it.
Still says that 10 minutes later. Have to manually FC the app and then go back in and try another app. TIB does the same thing.
How the hell can you freeze apps or just delete them if neither ROM Toolbox nor TIB can do it?
SquireSCA said:
This inability to debloat is driving me nuts.
This is what I am talking about, the plethora of **** apps out there that just don't work. ROM Toolbox, granted root access, go in and grab an app like Blockbuster and tell it to Freeze it.
says it is doing it.
Still says that 10 minutes later. Have to manually FC the app and then go back in and try another app. TIB does the same thing.
How the hell can you freeze apps or just delete them if neither ROM Toolbox nor TIB can do it?
Click to expand...
Click to collapse
Dude, seriously. You have the worst freaking luck with this phone. At first I was just annoyed with your posts, but now I just feel bad for you lol Like, really...I'm sending you good phone vibes...hopefully your phone troubles go away
EDIT: Also, there are other apps that can freeze other apps, I think. Can't remember the name of them, but I think they're out there.
WasabiWa83 said:
Dude, seriously. You have the worst freaking luck with this phone. At first I was just annoyed with your posts, but now I just feel bad for you lol Like, really...I'm sending you good phone vibes...hopefully your phone troubles go away
Click to expand...
Click to collapse
Yeah, well if something can go wrong for me, it will.
I did a straight RUU, fully restored to stock. Unlocked. Rooted. Installed SU and updated it, and I cannot debloat any of the **** apps.
This used to work. It worked on my GF's Rezound last week, same OS, same OTA, same exact process, but when I do it, it just sits there doing nothing.
SquireSCA said:
Yeah, well if something can go wrong for me, it will.
I did a straight RUU, fully restored to stock. Unlocked. Rooted. Installed SU and updated it, and I cannot debloat any of the **** apps.
This used to work. It worked on my GF's Rezound last week, same OS, same OTA, same exact process, but when I do it, it just sits there doing nothing.
Click to expand...
Click to collapse
That sucks. I've had TiBu hang on backups and restores, but never on freezes. That's really strange. I would look for another app. You could try something like this. Just buy it and try for a second and then refund if it doesn't work right away. Just a thought. Hope it gets better for you.
WasabiWa83 said:
That sucks. I've had TiBu hang on backups and restores, but never on freezes. That's really strange. I would look for another app. You could try something like this. Just buy it and try for a second and then refund if it doesn't work right away. Just a thought. Hope it gets better for you.
Click to expand...
Click to collapse
Tried it, it also hangs on freezes just like all the others.
I am stumped. I am really starting to hate this phucking phone.
SquireSCA said:
Tried it, it also hangs on freezes just like all the others.
I am stumped. I am really starting to hate this phucking phone.
Click to expand...
Click to collapse
Just buy rootexplorer and mount to r/o in system and go to app and either rename all the bloatware to .bak or just delete the apk's you don't want like blockbuster etc.. thats what I did and I am not sure why people freeze over renaming or deleting personally.
by renaming to .bak then if you like you can just delete the .bak and viola app is restored !
mjh68 said:
Just buy rootexplorer and mount to r/o in system and go to app and either rename all the bloatware to .bak or just delete the apk's you don't want like blockbuster etc.. thats what I did and I am not sure why people freeze over renaming or deleting personally.
Click to expand...
Click to collapse
Good idea, though it would be mounted as R/W, would it not?
WasabiWa83 said:
Good idea, though it would be mounted as R/W, would it not?
Click to expand...
Click to collapse
er yes sorry.. I crossed that up
I was trying to picture the screen and was seeing the r/o at the top.. lol have to press that to change to read/ write to alter the actually files.
Tried that and even after renaming and rebooting, most of the apps are still in the app drawer...
The bottom line is that the last ROM I tried really screwed up my phone. I may have to smash it and get a new one under my insurance plan...
SquireSCA said:
Tried that and even after renaming and rebooting, most of the apps are still in the app drawer...
The bottom line is that the last ROM I tried really screwed up my phone. I may have to smash it and get a new one under my insurance plan...
Click to expand...
Click to collapse
Now, that is wierd did you try deleting them or just moving the apk's onto your SD card from the folder if you wanted to keep them ? There is no reason this shouldn't work that I can think of .
Well, I've had my vibrant and my gs2 for a long time and have always flashed all kinds of roms on both. I'm no pro but I try to learn from the people here. But lately I can't figure out what's wrong with my vibrant. I tried resetting it with odin and flashing different, stable, well known roms on it but it still acts funny. It will work for a bit then start shutting off, not letting me turn it on and just shows the spinning star circle for a little bit. I have to plug it in and mess with it a little to get it to turn on or go in download mode. I've searched a lot, tried to find a solution but nothing so this is my last resort. I'd like to hear form people who had the same problem and what did you do please
I just managed to get it to turn on again but I don't know what to do before it goes off again. It is on ics passion v13.1. It's also unlocked. If this is some stupidly simple problem I'm sorry but I am seriously getting annoyed with the phone. Thanks for any help.
Well Passion is definitely dated, and not in a good way. If ICS is your choice flavor, by all means don't let me talk you out of it.....
However. I personally suggest you Odin back to stock, with repartition checked and flash up to Helly Bean. I haven't used CM10 yet (official build) so I can't comment personally on it, but you could try that. At least they are new and still very much supported.
GPS is broken, and 911 may not work, but those issues aside I've heard nothing but good things about them. I've been on Helly Bean since 8/12 and it's quite smooth.
Your issue might be kernel related. Keep us posted on what route you take, maybe we'll learn more about your problem and discover a solution.
ginseng8888 said:
Well, I've had my vibrant and my gs2 for a long time and have always flashed all kinds of roms on both. I'm no pro but I try to learn from the people here. But lately I can't figure out what's wrong with my vibrant. I tried resetting it with odin and flashing different, stable, well known roms on it but it still acts funny. It will work for a bit then start shutting off, not letting me turn it on and just shows the spinning star circle for a little bit. I have to plug it in and mess with it a little to get it to turn on or go in download mode. I've searched a lot, tried to find a solution but nothing so this is my last resort. I'd like to hear form people who had the same problem and what did you do please
I just managed to get it to turn on again but I don't know what to do before it goes off again. It is on ics passion v13.1. It's also unlocked. If this is some stupidly simple problem I'm sorry but I am seriously getting annoyed with the phone. Thanks for any help.
Click to expand...
Click to collapse
Your battery could possibly be going bad. If it still acts funny on stock JFD then its probably your battery. I would flash back to stock 2.1 with Odin and see if the problem goes away, then flash back to ics if that's what you want. You could maybe try calibrating your battery too, not likely to be the problem but worth a shot.
Sent from my SGH-T959 using Tapatalk 2
well I tried just having the phone back to stock with odin and just rooted and unlocked. I also tried other roms that are not ics and things that people suggested. still, the problem is the same. it's so weird. I tried a new battery too. now i have to get a new phone pretty much. it's just a shame since there isn't a scratch on my vibrant.
ginseng8888 said:
well I tried just having the phone back to stock with odin and just rooted and unlocked. I also tried other roms that are not ics and things that people suggested. still, the problem is the same. it's so weird. I tried a new battery too. now i have to get a new phone pretty much. it's just a shame since there isn't a scratch on my vibrant.
Click to expand...
Click to collapse
Hm, interesting.
Did you overclock/undervolt a lot with this phone?
ginseng8888 said:
well I tried just having the phone back to stock with odin and just rooted and unlocked. I also tried other roms that are not ics and things that people suggested. still, the problem is the same. it's so weird. I tried a new battery too. now i have to get a new phone pretty much. it's just a shame since there isn't a scratch on my vibrant.
Click to expand...
Click to collapse
Im no pro or even a novice at this, but to me it sounds like a pending hardware failure. This sounds alot like what happened to my Toshiba laptop.
Try installing a good kernal, try subzero first.
I think I'll try that before I give up. I'll let you know what happens. Thank you for the suggestions
Nothing was the same after rooting my atrix.
-The HD games started to freeze, and on the worst cases crashing (e.g. GTA VC).
-Background apps (e.g. Gauge Battery Widget) rebooted very often (specially when browsing).
-When surfing multiple heavy pages, the browser tends to crash sometimes. Also when it crashes, it returns me to the start screen and if i have a live wallpaper running it stops and changes to a generic black screen.
-When trying to upload an image file on an image board, the browser refreshes the page.
-Overheats without reason from time to time. Seriously, its like a pocket heater.
-When the screen animations are activated, returning from landscape to vertical orientation turns the notification bar blurry and when i pull down the notifications tray it turns the screen blurry as well. Though it returns to normal when going back to landscape.
This is a major issue for me since if i turn off the screen animations, i can't tell if an app i opened is running (e.g. YouTube). And like i don't use the stock video player and use another player (e.g. MX player), when the animations are activated instantly crashes when opening a video.
Also before rooting, the battery only lasts me 5 hours without running apps and the problem persists ever since.
One thing. The first time i got the phone it came with stock FROYO 2.2.1 and i changed it right away to GINGERBREAD 2.3.6 skipping the 2.3.4, i unlocked the bootloader first and then rooted it.
Is there anything i can do to fix the problems previously mentioned?
I have a feeling you are an international user and did not flash the ramfix, search for it in development section, download to sd and flash.
jorno88 said:
I have a feeling you are an international user and did not flash the ramfix, search for it in development section, download to sd and flash.
Click to expand...
Click to collapse
Every tutorial i looked for didn't mentioned that, i'll give it a try.
But if i do that, does it mean i will have to do a hard reset?
It is surely mentioned in subsequent posts in the tutorial thread.
RAM fix has nothing to do with data so factory reset (or hard reset as you call it) is not needed.
ravilov said:
It is surely mentioned in subsequent posts in the tutorial thread.
RAM fix has nothing to do with data so factory reset (or hard reset as you call it) is not needed.
Click to expand...
Click to collapse
Not in the tutorials i've followed, they never mentioned it. FYI none of the tuts where from here.
Good to know i won't have to hard reset. So were does the zip go, internal or external?
always follow xda, it's the best
as for the zip, place it wherever you like and flash it with a custom recovery like cwm or twrp
Yeah I could never understand people who follow a tutorial on forum X then ask about it on forum Y... Makes no sense to me. Why are people on forum Y supposed to know anything about forum X or its contents?
Questions about a tutorial on some forum should be asked on that same forum.
And yeah, everything you need is on XDA, no need to go search for random sources.
Just to help the OP:
https://www.dropbox.com/sh/cu2bd61dh6ytzda/C-z3zfNBcr (just get the RAMfix.zip from this link)
http://www.youtube.com/watch?v=p5T9hJ4Yjek
Hope this helps OP. I have a At&t and I don't need to do the RAM fix. U can give this a shot. All the best.
5HoofedStallion said:
Not in the tutorials i've followed, they never mentioned it. FYI none of the tuts where from here.
Good to know i won't have to hard reset. So were does the zip go, internal or external?
Click to expand...
Click to collapse
Ramfix may not be mentioned in root tutorials because it's related with unlocking bootloader. Since you first unlocked, then rooted, you'll have to flash it anyway.
GH0ST DR0NE said:
Just to help the OP:
Hope this helps OP. I have a At&t and I don't need to do the RAM fix. U can give this a shot. All the best.
Click to expand...
Click to collapse
Off topic, but now that you brought the subject. I have seen this a while ago, and looks tempting but is it convenient for me to use the leaked ICS rom? Is there any bugs in it to be concerned about?
It's a shame that motorola decided to leave the atrix in the shadows with GB, they could at least made ICS the final and definitive update. I mean, the rom looks like it was 99% finished and ready to launch.
saldirai said:
Ramfix may not be mentioned in root tutorials because it's related with unlocking bootloader. Since you first unlocked, then rooted, you'll have to flash it anyway.
Click to expand...
Click to collapse
I followed both root and bootloader unlock tutorials and NONE brought that out. Since i'm LATAM, it made sense for me to seek in latin android forums instead here because of the firmwares, and boy they skip a lot of useful info in those forums.
Also, how do i exactly run the ramfix? Im eager to fix the buggy notification tray right away, that and fixing my battery not charging at 100%. I tried pulling the battery while charging and it turned worse, it went from 90% to 70%
I also need to know how to wipe the battery data from the CWM.
5HoofedStallion said:
... is it convenient for me to use the leaked ICS rom? Is there any bugs in it to be concerned about?
It's a shame that motorola decided to leave the atrix in the shadows with GB, they could at least made ICS the final and definitive update. I mean, the rom looks like it was 99% finished and ready to launch.
Click to expand...
Click to collapse
If it's running well for you, you should consider yourself very lucky. You should also read some of the threads concerning it and related ROMs (AtrICS etc) - the thing is so buggy very few people even wonder anymore how come it was never released.
Even if it's running so great for you as you say, I still wouldn't keep it if I were you. The ROM is a development build, it was never meant to be used as a daily driver. But that's just me.
5HoofedStallion said:
Off topic, but now that you brought the subject. I have seen this a while ago, and looks tempting but is it convenient for me to use the leaked ICS rom? Is there any bugs in it to be concerned about?
It's a shame that motorola decided to leave the atrix in the shadows with GB, they could at least made ICS the final and definitive update. I mean, the rom looks like it was 99% finished and ready to launch.
I followed both root and bootloader unlock tutorials and NONE brought that out. Since i'm LATAM, it made sense for me to seek in latin android forums instead here because of the firmwares, and boy they skip a lot of useful info in those forums.
Also, how do i exactly run the ramfix? Im eager to fix the buggy notification tray right away, that and fixing my battery not charging at 100%. I tried pulling the battery while charging and it turned worse, it went from 90% to 70%
I also need to know how to wipe the battery data from the CWM.
Click to expand...
Click to collapse
I agree with u. But Motorola is infamous for such antics. One if the reasons I don't have a RaZr anymore. But it is running good. I will b honest. Its OK. This phone isn't made for anything but GB in mind. I would pick a low end, second hand Windows Phone any day over this.
But this is as far as it goes for Atrix. Jelly Bean...naah.
Sent from my Π Σ Χ U S 4.
How am i supposed to run the ramfix?
Sent from my rooted & unlocked Motorola Atrix.
It's a flashable zip so just install it like gapps or a rom. Install from sd card
Which are the commands on the atrix?
Sent from my rooted & unlocked Motorola Atrix.
Use a custom recovery... You can manually adjust the cmdline but flashing the zip is much easier
You mean, with the RSD Lite?
Sent from my rooted & unlocked Motorola Atrix, using Tapatalk 2.
Don't ever touch RSD, RSDLite or any SBF (except pudding) unless you're at gunpoint.
Then how the hell do i run ramfix on clockwork!?!
Sent from my rooted & unlocked Motorola Atrix, using Tapatalk 2.
Would do you good if you could learn to search and read. It's all explained many times...
Hint: CWM = ClockWorkMod recovery
Another hint: How do you usually use a flashable zip?
I've always used TWRP on my phones, for years...but recently I keep getting stuck at the custom samsung screen during a reboot. I've seen others with this problem and heard that it may have something to do with the way it wipes the phone during a full wipe. But what is the fix? I almost refuse to go to CWM. I'm just tired of having to unroot and reroot, just to get TWRP to work normally. Let me know if you've experienced the same and what can be done. Thanks.
Been a lot of issues that have been obvious and many others that have been suggested to be due to twrp.
I switched to cwm probably 2 months ago
Sent from my SCH-I545 using Tapatalk 4
twiz0r said:
Been a lot of issues that have been obvious and many others that have been suggested to be due to twrp.
I switched to cwm probably 2 months ago
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
I really didn't want to have to...such a bummer. I guess I'm holding out because surely TeamWin knows about it and is fixing it. At least I hope they do. I knew that I wasn't the only one, was just hoping someone would have a tip that would save me some headache and keep me from having to switch.
For me sometimes it takes quite a long time to start. It seeming hangs at the teamwin startup screen for many minutes. Eventually it loads though.
ericstephani said:
For me sometimes it takes quite a long time to start. It seeming hangs at the teamwin startup screen for many minutes. Eventually it loads though.
Click to expand...
Click to collapse
Maybe I haven't been patient enough, but it never seems to get past that screen. It's weird though because guys like DROIDMODDERX on youtube flashes a ton of ROMS on his phone with seemingly no issues. I ended up just switching to CWM, even though I can't stand it. I guess I'll switch back when and if TeamWin address the issue. I wanted to try OUDHS and the other one that I can't think of the name of, but I'm leery of recoveries that I've never tried.
allforwon said:
Maybe I haven't been patient enough, but it never seems to get past that screen. It's weird though because guys like DROIDMODDERX on youtube flashes a ton of ROMS on his phone with seemingly no issues. I ended up just switching to CWM, even though I can't stand it. I guess I'll switch back when and if TeamWin address the issue. I wanted to try OUDHS and the other one that I can't think of the name of, but I'm leery of recoveries that I've never tried.
Click to expand...
Click to collapse
There are downloads of TWRP version 2.5.0.2 floating around that do not have the freezing issue. I will look around to see if I can find it or if I have it.
edit: check out this post for download: http://forum.xda-developers.com/showpost.php?p=45006486&postcount=289
Thanks for the reply. That's the version that was just before 2.6 right? If so, I was having the same issues with it as well. I read in another post somewhere that it had something to do with the format all function, the one where you have to type yes to erase everything. That being said, I emailed TeamWin and asked if a fix was in the works or if there was a recommendation that they could make about how to actually use the TWRP so that I wouldn't have problems. I never got a response. So maybe I'll try to go back to 2.5...this is just really weird for me because I never had issues with my Note 2, ever. The only time I ever Odin'd back to stock was to sell the phone. I could flash 10 ROMS a day and never get stuck. Could be that I'm just dumb or missing something and that I'm doing it all wrong, lol, we shall find out. Thanks again.
2.5.0.3 and 2.6 are buggy 2.5.0.2 is great. There is also a flashable 2.5.0.2 in the link on my Sig below.
sent from my Verizon Galaxy sIV
Dubbsy said:
2.5.0.3 and 2.6 are buggy 2.5.0.2 is great. There is also a flashable 2.5.0.2 in the link on my Sig below.
sent from my Verizon Galaxy sIV
Click to expand...
Click to collapse
Awesome! So Dubbsy have you had issues with the newer builds then too?
Also, just so I make sure that I remember how to do it correctly, I just flash the zip in recovery right? I have been spoiled with goomanager and rommanager.
Thanks.
Hello xda developers, i am new to this forum. Even tho i've used couple of guides from here i wasn't registered. So here is the thing:
My phone is the AT&T variant and is currently running GPe android 6.0 with OTA updates. When i was on sense 6/7 (i dunno) and 5.0.2 lollipop ( being rooted, unlocked, s-off) i was not experiencing any kind of casualties. When i proceeded to install the GPe, everything was perfect. But then i happen to open the camera app (Google's) and it starts making the buzzing noise and cant focus at all. my first thought was, maybe is the camera app. So i installed the latest version of htc one m8 camera and saw that it had the same issues. I'm starting to consider that this is a hardware problem. A friend told me to re-install everything as it was before this happend. Considering doing it but first i would like to ask you guya your opinion.
P.S: the front camera is just fine. The problem is on the rear one.
Change software (back to Sense) to eliminate the possibility that its a software issue.
Much easier than trying to eliminate the possibility of a hardware issue. Only way to do that, would be to replace the camera module.
Besides, if it worked fine on Sense, than suddenly doesn't work on GPE, its pretty suspicious.
It looks like it is a Hardware problem. Went back to sense and still the same problem.
I'm starting to think that this issue might have been triggered by the overheat during the software installation and it's many consecutives updates. It really did overheat a lot.
But anyways, i guess ill send it to someone to check just in case its not just the camera. It also happens to make the same static/buzz sound when i open the flashlight alone.
angel21612 said:
It looks like it is a Hardware problem. Went back to sense and still the same problem.
Click to expand...
Click to collapse
How did you go back to Sense? I'd suggest full RUU to stock, before concluding its not a software issue.
angel21612 said:
I'm starting to think that this issue might have been triggered by the overheat during the software installation and it's many consecutives updates. It really did overheat a lot.
Click to expand...
Click to collapse
What does that mean "overheat a lot"? Folks often think the phone is overheating, when its not even close. It would probably have to burn you to hold it, before it did any actual harm to the electronics. Temps of over 60C (140F) are probably needed to do any damage.
The phone has safeguards that shut it down, well before temps that would cause permanent damage.
Well first of all, i didn't find a full RUU to stock. I used a custom rom. Do you mind leaving a link below so i can download the RUU?
my phones CID and MID are changed too, did it so i could go GPe. i didnt write down anywhere what my old MID and CID. Im just saying because i dont know if it would affect the instalattion process of an official RUU of sense to stock.
And about the heating topic, i don't know if the phone activates those security measures in case of overheating when you're flashing a rom or downloading/installing the updates you get via OTA. I installed the 5.0.1 lollipop (maowdroid's guide from youtube to convert htc one m8 to GPe) so, i had to go through like 3 updates downloads/install and the phone really got hot and never shutdown.
angel21612 said:
Well first of all, i didn't find a full RUU to stock. I used a custom rom. Do you mind leaving a link below so i can download the RUU?
Click to expand...
Click to collapse
Go to the AT&T M8 General section. You'll find my Index thread sticky at the top of that forum section, and in that thread you will find links to every AT&T M8 RUU.
angel21612 said:
my phones CID and MID are changed too, did it so i could go GPe. i didnt write down anywhere what my old MID and CID. Im just saying because i dont know if it would affect the instalattion process of an official RUU of sense to stock.
Click to expand...
Click to collapse
Wrong CID and/or MID will cause the RUU to fail (although SuperCID is fine). Finding the proper CID and MID is not hard, if you just search around the forums.
You can also try the current GPE RUU (and why didn't you just run that in the first place, instead of all the updates?). But my gut tells me to return to true AT&T stock for your device.
angel21612 said:
And about the heating topic, i don't know if the phone activates those security measures in case of overheating when you're flashing a rom or downloading/installing the updates you get via OTA.
Click to expand...
Click to collapse
I see no reason why it wouldn't. Its a basic safety measure, so its probably enforced at all times the phone is powered on. HTC engineers are plenty smart enough to know that updates cause heat.
---------- Post added at 09:26 AM ---------- Previous post was at 09:21 AM ----------
angel21612 said:
i had to go through like 3 updates downloads/install and the phone really got hot and never shutdown.
Click to expand...
Click to collapse
Again, saying the phone "really got hot" is not at all quantitative, and means little. Folks say stuff like this a lot on this forum; and when prompted for more info, its almost always the case that the phone was not even close to any excessive temperature. These devices get warm when under CPU load, all computer devices do. They are designed to tolerate a significant amount of heat, shutoff long before any damage is done, and heat damage is unlikely. As mentioned, it probably would have gotten too hot for you to even hold, before it can cause any actual hardware damage.
I'll be looking forward for a stock sense RUU but there's just something that i don't understand. How come, everyone who fallowed the guide to convert to GPe with OTA updates haven't experienced that problem? And if they do, im sure they were just a few. That's why i think i am more convinced that it could be a hardware issue.
angel21612 said:
I'll be looking forward for a stock sense RUU but there's just something that i don't understand. How come, everyone who fallowed the guide to convert to GPe with OTA updates haven't experienced that problem? And if they do, im sure they were just a few. That's why i think i am more convinced that it could be a hardware issue.
Click to expand...
Click to collapse
Things often don't install correctly when patching by OTA. Especially since user data is retained, and as you mentioned multiple OTA updates. Folks frequently complain about random bugs after OTA updates. Sometimes, these are cleared by doing a factory reset, sometimes not.
RUU is a much cleaner install, and completely wipes/re-writes every single partition (around 41 of them).
Which again, makes me wonder why you did an RUU to an older version GPE, than 3 OTAs; instead of just RUU to Marshmallow GPE.
That's an interesting fact i didn't know. Very good point.
Well, in the end it was not a software problem.
**** me.
I'm facing the same problem right now
same here, phone buzzes/vibrates when torch is activated?? any ideas??