Hi,
Please forgive me if there is already a thread existing for this, as I am new here.
I have a question regarding my HTC Sensation XL, which is currently running Android 2.3.
I rooted my phone some time after I got it. I'll admit that my knowledge of such things is extremely limited, so I may have done something stupid. Anyway, I used some sort of one-click-rooting program (I honestly can't remember what it was called) to root my device. The root was successful and I was happy with this. However, I found that this caused my phone to show the bootloader menu, whenever I turned it on.
This caused an issue when I attempted to update my phone to Android 4.0. I could download the update, but the installation would be interrupted upon reboot, due to the bootloader menu showing up (or so it would seem).
To fix this, I attempted to unroot my phone using an app called 'Ginger Unroot', which seemed to work. However, the issue with the bootloader menu interrupting the update still occurs.
I'm aware that I've probably done something very stupid by opting for these one-click methods of rooting/unrooting, as many sites seem to suggest different, more complex methods. This is probably a lesson for me not to mess around with things that I don't quite understand.
Anyways, does anyone have any advice on how I may go about either solving or getting around this problem?
Your help is most appreciated!
N.B: My device has recently started turning itself off for no apparent reason, if that has anything to do with the problem at hand.
Related
I've had the SGP 4.2 since August (North American version) and have become very fond of it. Although I've followed most of the dev areas, I have never rooted or installed any recovery, custom roms, etc...so it's on the stock Android 2.3.6 with 2.6.35.7 kernel and build number GINGERBREAD.UELD3. I have only installed things from the play store and amazon app store.
Sometime in the past week it has started shutting down randomly. Most times I notice when picking it up after hours of standby and it's fully off and need to boot up. A few times it has happened while in use - it just turns off. The battery level doesn't seem to matter, it can happen at 99%, 5%, and anywhere between.
Is there any way to tell if this is a hardware problem vs a software problem? Any other thoughts? I've not seen this problem in other threads, or at least not when running everything stock.
maybe a hardware issue.
see if samsung will fix/replace it
imgthat said:
I've had the SGP 4.2 since August (North American version) and have become very fond of it. Although I've followed most of the dev areas, I have never rooted or installed any recovery, custom roms, etc...so it's on the stock Android 2.3.6 with 2.6.35.7 kernel and build number GINGERBREAD.UELD3. I have only installed things from the play store and amazon app store.
Sometime in the past week it has started shutting down randomly. Most times I notice when picking it up after hours of standby and it's fully off and need to boot up. A few times it has happened while in use - it just turns off. The battery level doesn't seem to matter, it can happen at 99%, 5%, and anywhere between.
Is there any way to tell if this is a hardware problem vs a software problem? Any other thoughts? I've not seen this problem in other threads, or at least not when running everything stock.
Click to expand...
Click to collapse
that was happening to me too. i just bought mine from best buy about 1.5 months ago. everything was fine, mine also wasnt ever rooted or flashed anything - just oem with playstore apps. then every now and then after about a month of having it, it would turn off and on by itself (only if it was idle though, without me touching it) its never happend to me while i was messin around with it. and then it started freezin up on me and gettin really laggy at times with certain programs but it was random and i couldnt reproduce it to try and pinpoint the program that was causing it. but then i read up on rooting it and the benefits of root and cwm and backingup everything and roms and since then, everythings perfect. better than new as a matter of fact. so in my opinion, you owe it to yourself to root your device so you can make changes to your lil buddy. i made sure i learned all about rooting and flashing and backups etc first though so i can do it safely. i mean, cmon i dont know about you but i paid alot of money for mine which is why i owed it to myself to 'safely' release the full potential of my device. :cyclops:
Totally agree that I want to start to release the full potential, thats' whay I've been poking aorund here for months (and tinering with my Acer tablet is getting old). My hesitation to start down that path is if there's a hardware issue I don't want to compound the inevitable probelms and end up with an out of warranty bricked device
Maybe I'll see what Samsung says. Like the previous poster - i can't directly replicate the issue so perhaps they won't replace, I'll see and update this post accordingly.
imgthat said:
Totally agree that I want to start to release the full potential, thats' whay I've been poking aorund here for months (and tinering with my Acer tablet is getting old). My hesitation to start down that path is if there's a hardware issue I don't want to compound the inevitable probelms and end up with an out of warranty bricked device
Maybe I'll see what Samsung says. Like the previous poster - i can't directly replicate the issue so perhaps they won't replace, I'll see and update this post accordingly.
Click to expand...
Click to collapse
well one of the good things bout this forum is that it explains how to un-brick our devices if it happens. it was kind of intimidating at first for me too as this is the first android ive ever rooted and flashed diff roms. but as long as you make backups thru titanium and also a nand backup thru cwm and then use roms and kernals specifically made for your device that have been tried and tested and retried....then you really have nothing to worry about. and i also read somewhere that if you flash it yourself and somehow manage to brick your device, you can flash everything back to stock so your warranty wont be voided anymore - i could be wrong but im almost positive ive read that somewhere.
Please read the OP (below). I am in serious need of assistance. I am attaching an updated Logcat to this Edited OP. Please read through the Log if you do not mind, and let me know what all you think may be going on here. I am getting a little frustrated to be honest. There is rarely that time when I have run across a problem that I could not fix with a bunch of reading, and study. But, this quite frankly is a bear that won't go away. I will not leave this problem unresolved. And I hope that with the friendly folks here at XDA that together we can resolve one more issue. I know there are others that are suffering from a similar issue. People just get too intimidated to ask questions sometimes. I can say that after almost 3 weeks of reading, I am far from afraid of asking for an assist. So, again, Thank You to anybody willing to help. I will attach the Logcat to this Edited post.
edit:20131128_0747mst-ev_attachment(1)
Briefly: I had the honor of meeting a fellow XDA Member in person by total accident. Together we have been attempting to troubleshoot her DNA. She has been working to resolve the following issue for a couple of months, and I have been reading endlessly & searching endlessly for a solution to the following problem. Please give any advice that you are capable of giving. Thank you.
The issue we are having is that once we get the ROM completely loaded (Venom v. 2.01) & the device boots up completely, as soon as the screen is touched the phone flashes back to the white HTC screen and begins to bootloop! I had the wise idea to check inside the phone thinking it may be a grounding issue. Sure enough there were 3 screws missing. Still this did not solve the problem.
Is there a step we are missing? Is there another issue that others may have had that is similar or that you have resolved prior?
We have even reflashed the stock RUU by relocking the bootloader, then unlcoking, reloading the recovery, and again the ROM. Still have the same issue. Anybody have any input? I know this is kind of a brief explanation, but I tend to get long winded. Below is the information for what is currently running.
Unlocked,MONARUDO PVT SHIP S-OFF, CID=22222222, H-Boot - 1.33.0001, Radio - 1.00.00.1023_3, OpenDSP - v4.120.240.0920 eMMC-booT, Oct 23, 2012, 21:34:05, Running TWRP Recovery v 2.06 ROM - ViperDNA 2.01 Sense5
P.S. I have a similar issue with an HTC Sensation that I have been working on for a while. However, the issue with the Sensation is something to do with the aftermarket digitizer and the firmware loaded on the chip on the digitizer and something to do with the diagnostic software. I am stuck there too as I am unable to get the pyramid.nbh file to load correctly.
Did you have this problem with stock rom?
Please you should get a logcat from this phone. I am guessing a problem with the touch screen or battery.
WellTrainedVC said:
Briefly: I had the honor of meeting a fellow XDA Member in person by total accident. Together we have been attempting to troubleshoot her DNA. She has been working to resolve the following issue for a couple of months, and I have been reading endlessly & searching endlessly for a solution to the following problem. Please give any advice that you are capable of giving. Thank you.
The issue we are having is that once we get the ROM completely loaded (Venom v. 2.01) & the device boots up completely, as soon as the screen is touched the phone flashes back to the white HTC screen and begins to bootloop! I had the wise idea to check inside the phone thinking it may be a grounding issue. Sure enough there were 3 screws missing. Still this did not solve the problem.
Is there a step we are missing? Is there another issue that others may have had that is similar or that you have resolved prior?
We have even reflashed the stock RUU by relocking the bootloader, then unlcoking, reloading the recovery, and again the ROM. Still have the same issue. Anybody have any input? I know this is kind of a brief explanation, but I tend to get long winded. Below is the information for what is currently running.
Unlocked,MONARUDO PVT SHIP S-OFF, CID=22222222, H-Boot - 1.33.0001, Radio - 1.00.00.1023_3, OpenDSP - v4.120.240.0920 eMMC-booT, Oct 23, 2012, 21:34:05, Running TWRP Recovery v 2.06 ROM - ViperDNA 2.01 Sense5
P.S. I have a similar issue with an HTC Sensation that I have been working on for a while. However, the issue with the Sensation is something to do with the aftermarket digitizer and the firmware loaded on the chip on the digitizer and something to do with the diagnostic software. I am stuck there too as I am unable to get the pyramid.nbh file to load correctly.
Click to expand...
Click to collapse
Logcat from DNA
removed
Still having this issue. Even with the Stock Rom. I am also unable to upgrade via OTA to the newer firmware releases as I am unable to keep the phone on long enough to use it, plus the touch screen/digitizer I believe is the main problem.
I read another article online about how HTC utilizes a digitizer which uses resistive (sp sorry) feedback on their touchscreens. It really has me thinking that this issue can be similar to the issue I am having with my Sensation. That issue is digitizer related, and happens with aftermarket digitizers. There is a way to fix the issue with the sensation however. I can post another logcat if any member is willing to lend me their eyes & knowledge? Or you can just use the logcat above.
Thinking about joining another discussion in the mean time. I am slightly concerned for this thread is a developer thread, and I don't quite have the chops to hang with the dev's. Although I do understand a majority of what they are saying, and can even put into practice the things they are doing. Ability to read & comprehend is a wonderful gift.
Still Having Issue
Still having this issue. Even with the Stock Rom. I am also unable to upgrade via OTA to the newer firmware releases as I am unable to keep the phone on long enough to use it, plus the touch screen/digitizer I believe is the main problem.
I read another article online about how HTC utilizes a digitizer which uses resistive (sp sorry) feedback on their touchscreens. It really has me thinking that this issue can be similar to the issue I am having with my Sensation. That issue is digitizer related, and happens with aftermarket digitizers. There is a way to fix the issue with the sensation however. I can post another logcat if any member is willing to lend me their eyes & knowledge? Or you can just use the logcat above.
Thinking about joining another discussion in the mean time. I am slightly concerned for this thread is a developer thread, and I don't quite have the chops to hang with the dev's. Although I do understand a majority of what they are saying, and can even put into practice the things they are doing. Ability to read & comprehend is a wonderful gift.
First off, I'd like to say my S2 is the Virgin Mobile version (model i9210) so I'm not sure if it's okay for me to post this in this forum or not. Feel free to move it where it should be, I won't be offended.
Edit: Originally had posted this in the Samsung Galaxy S2 forum, but it was nicely moved to this forum in hopes that it would be seen more~ So to clarify, my phone is the Virgin Mobile Samsung Galaxy S2, running Android 4.1.2, model number SPH-D710.
The ROM I have is BiftorROM-V8-JB-XWLSN-NoWipe.
Onward. This is my first Samsung phone AND my first Galaxy, and when I decided to root my phone, I had no idea how much different it would be from my past phones. How I didn't completely brick this phone, is nothing short of a miracle. I had trouble with some ROMs so someone eventually linked me to a Sprint stock ROM, saying it was compatible with my phone.
Since then I've been using that ROM, despite having a Virgin Mobile phone, with no problem. Recently I noticed an app I use (SD Maid) was listing my phone as unrooted. It was weird but I ignored it, because the app still worked. Even later, I noticed other apps that require root access were not working correctly, so I decided to download a root checker.
Status: Unrooted
Well, then. I'm not sure how this happened, or what's going on, but I figured again, it was no big deal because my ROM was running perfectly and I had no desire to change my ROM or anything else soon. Last night my phone started acting completely different. Lagging like crazy, and when I tried to unlock my phone, it would take a good 15 seconds just for the screen to turn on and my lock screen to start functioning normally. Then another 20 seconds or so for the screen to register my touch and actually unlock my phone. I tried disabling all lockers, but my screen would just turn black and I would still have to wait.
A friend suggested that I simply go through the process of rooting as though my phone really were unrooted and just hope that fixes it, but I'm not sure if that would be a good idea. If my phone wasn't operating so slowly this wouldn't be as big of a problem, but it is, and I'm pretty afraid that I'll mess my phone up somehow.
I once found a forum with the topic the same as mine but I haven't been able to find it since, so I'm hoping someone here could point me in the right direction. Do I go through the root process, maybe try just reflashing my current ROM? I've also thought about just doing a system restore on my phone and see if that helps. Thanks in advance.
Hi All, this is my first post here. I'm fairly new at this, having only recently flashed my Nexus 4 with CyanogenMod.
My brother gave me his old vibrant to setup for our mom, and it was working ok with the stock Android 2.1. I started to transfer some data out of it (old pictures, etc) and the thing crashed and got stuck on a bootloop. This is before I ever attempted anything flashing related.
I tried various procedures that I found here and elsewhere to flash the phone, using both Heimdall and Odin and ran into various issues with each. One of the problems that I had is that a lot of the downloads linked from articles (like ROMs and other files) are gone since it's been a few years since they were posted. I scrounged pretty hard for a few days and was able to get bits and pieces here and there, but no success yet. These were not the only issues either. I had problems with both Heimdall and Odin doing the actual flashing. Various errors with handshaking and flashing in both, from what I recall (this was actually a couple of weeks ago).
In fact, I ended up making things even a little worse. The phone used to show the large battery gauge screen when it was plugged in and powered off, but now I got it to where it just shows the phone---!---PC screen. However, I can still get it to download mode so I'm thinking that not all hope is lost!
Anyway, to make a long story short I hope that someone here could perhaps point me to a reliable article that would help me go from the current state to a working phone, or provide any other pointers or files that may help me resolve this.
Thank you in advance, I appreciate any help you can provide. I would just hate to throw this phone away if there's any way it can be saved. It just feels wasteful, regardless of it being old and cheap.
Okay, a dual question here. One specific and one general but they are both related and one will help the other. Hopefully if anyone provides good answers others will find this post useful. I have a Asus Zenfone Selfie which has begun boot-looping. The phone is rooted and has TWRP installed. Once in a while it boots up as far as the home screen, then sometimes only up to the Asus logo. I have flashed several different ROMs (stock and custom) and again, it boots up to the setup screen then only up to the Asus logo so I was assuming this must mean it's hardware related. However, I can boot into TWRP and stay there for hours with no bootlooping. If it were hardware then it should bootloop for TWRP too so it must be software related, right? One more thing: I usually flash in TWRP but many times it crashes during the flash process. Sometimes it does succeed with no issues though. On my PC I might be running some disk or RAM checking tools to see if there was a bad sector or track on my hard drive or a bad module... Yeah, I'm confused. Why is it bootlooping and what, if anything, can I do to fix it?
This leads to my general question. Over the past 20 years I have had several phones, many of which ended up bootlooping. I know the LG G4 & G5 had a hardware flaw that cased them to bootloop and I know screwy flashes can cause bootlooping. But what about all my phones? Some were new, well, only a year or two old, some were 6 or 7 years old. Some were Android, some were Windows Phone. Some were rooted, some were unrooted, some were stock, some were custom ROMs. Some had updated or recently got new apps installed, others hadn't had anything new in ages. Some were in use when they started bootlooping, some were just sitting there. Some had a full charge on the battery, some were close to empty. What can be done to prevent this? What can be done once it has started, especially with one of these newer phones that they STUPIDLY like to make with sealed in batteries. And the given button combination just reboots the phone - again. Depending on who I talk to (or where I read) they say one thing or the other. It's software related. Okay, how? Why? I know on my PC Windows will sometime crash and reboot just for the hell of it, but that's usually just MS fixing an issue with a PC that runs too smoothly. And when that happens, it can be fixed. As an aside to any software developers reading this, I know you may not want to take the time to rewrite everything to work on Linux but you could take a little bit and make your software work with WINE, just a thought guys.
Anyway, so if it's software related, what can really be done to fix it? I can understand the big companies may like it if your phone bootloops so you'll need to buy a new one, but there are tons of developers out there making great custom ROMs. I know they don't have the resources to really fix all the bugs but I assume they would do a better job than certain big companies right? And why would the software suddenly crash like that? Sometimes literally NOTHING is happening, so why the sudden desire to bootloop? What about hardware? Can't we design software to work around the flaw? I would think manufacturers would want to fix problems to make their products as good as they can be but from what we have seen, I guess not. If you read my list above, many of those phones have nothing in common except the bootlooping. So where is the error coming from? Is there really nothing that we can do?
Any ideas and explanations would be appreciated, as would any help on my more recent bootloop device the Asus Zenfone Selfie Z00UD/z00T. Just to mention, that is a newer phone. It may not be now but it bootlooped probably a little over a year ago. It takes me a while to get around to things sometimes, like writing a letter to post on a forum. I had in mind to take it to this one repair shop (they had to replace the USB charging port maybe 3 months before the bootlooping so I assumed there might be a connection) but when I finally got there they told me it was software related and wouldn't look at it. Also, I don't want to make it sound like all my phones bootloop. I have had many many phones that died due to other issues and many more that are still in use, even old ones. I just want to try to understand and grasp any common factors that cause some phones to bootloop, and to maybe use that knowledge to prevent future phones from bootlooping even if I can't repair the ones that already do.
Thanks for your time in reading this and in advance for your answers. If you googled your way here, I hope there is info here that can help you too.