Hello,
This is my first time posting here, and I would like to request anyone on here to please assist me with the problem I am currently facing. I bought an unlocked, rooted HTC One with stock Android 4.3 installed as it's sole, primary OS this past summer. The person I bought it from is the one who actually rooted the phone, as my knowledge of such processes is fairly limited. I understand there are plenty of complications that I may run into dealing with this problem on my own and technical references may be lost on me, but I'm fairly competent enough to follow instructions from someone who may be able to help.
Here's the problem: I received an Android 4.4 OS update yesterday, which downloaded automatically and asked me if I wanted to install it. I thought the process would be fairly simple and I would not encounter any problems. However, when I asked the update to register and install, first it went into boot (I'm not certain which software was used for root), then the process started and everything seemed to be going fine until 'Patching files onto the whatever' came up and then it appeared that I encountered an error and the phone automatically went into what I can only assume is the bootloader menu? There were big Stock Android looking buttons on it which said things like Install, Root, Settings and a few others I don't recall. I tried to hit Install to see what happened and it brought me back to the part where 4.4 was supposed to be installed and I could read the error message at the end of it which said something like 'Error in patching files to zip folder or something', and I went back to the supposed bootloader menu. Confused and afraid, I think I pressed a button which I felt would allow me to reboot my phone and bring me back to my original 4.3 OS and that I would still be able to use my phone. First it said something like 'You no longer have root permissions', and there was an option where I could slide to apparently 'fix this', but I selected the 'don't fix' option as I obviously had no idea what I was doing. After this, the phone attempted to reboot, and a turquoise blue screen with strange markings came up on it and my phone hung. I killed the phone with the master power button and held it to switch off the phone.
BUT now, even since that has happened, my phone appears to be dead. It isn't starting up. When I put it on charge, the red LED doesn't show up. I have tried to used several ways to turn on my phone but it just wouldn't work.
I would like some light to be shed on this particular problem, and if anyone has experienced something similar to this, PLEASE, help me in fixing this. I am an eager learner and despite my limited, close to non-existent knowledge about dealing with a phone's OS, I know I can learn fast and follow instructions cleanly.
Please help me. Thank you.
Related
I've finally decided it's that time, Developers.
I really have no clue what I'm doing. I'm not well-versed with the inner mechanics of computer technology, or "flashing roms," or "cooking." Honestly, I just follow instructions very well.
With that said, I've flashed several roms from this site. My first was one of itje's, and it worked great. When I finally decided to try new ones and flashed the Open Touch line, it started to give me a hassle (now this isn't to say Open Touch is to blame, because I tried other one's after that, too).
Every time I flash a new rom, now, I'll put it on the device and say "this is incredible." I'll begin to customize it to my liking, manipulating the device settings and the such. Somewhere along the road, I'll say "time to soft reset!" At that point, the device will successfully power off, and power on. Then, the WM Loader screen appears, and stays right there. I've used a couple of troubleshooting techniques to figure out why, but I honestly have no clue what to look for. Hopefully, you do:
> This usually happens once I've FINISHED customizing it. I suspect (for some reason) it has to do with Windows Live Messenger.
> It also might be the "battery indicator" that I throw on the Today Screen.
> I STILL have no clue what "Hibernate" means, but I do it regularly because it seems to help.
> Soft resetting it again won't work. I actually need to use the hardware buttons to reset the device from factory defaults in order to make it run again (and of course it's no longer customized).
> Currently, I'm running the: Open Touch v2.7
In closing: If this is in the wrong sub-forum, I apologize. Please move it, and I'll know for next time. I didn't even really want to make this thread because I obviously sound like an idiot who doesn't belong holding a Wing. Hopefully one of you has an answer that will make some sense to me, because at this point I'm almost confused enough to digress back to a Samsung Blast.
are you overclocking it with battery status? if so try overclocking to 260mhz not 273mhz or even 243mhz.
I hope that helps.
You see, that's the problem. I don't even know what the heck "overclocking" means. All I know is it said "Be careful with this!" so I didn't even touch it.
Thanks for trying, though.
On wizard forum there were alot of people having trouble with "badflash" - I don´t even know what it is.
BUT before flashing a new rom they flash a stock rom!
AND they confrim a hardreset after flashing...
Maybe this helps
have you tried to flash then soft reset prior to cutomising the device? If it is OK it would point to something you are doing with your customisations, if not then I would look into what papamopps said.
if it is something you are doing then change one thing at a time and soft reset, eventually you will narrow it down to whatever you are doing that is causing this.
To the admins I apologize if this is in the wrong section if it is please move it accordingly.
Hello everyone, I have an issue, hopefully someone can hel me and it starts like this. I and everyone else have been waiting for months for a safe root method and a recovery system such as TWRP OR CWM just incase I fudge something up flashing custom roms so I can always go back to stock. I came across a safestrap article and decided it was something similar to what I was looking for. So I decided to root using the big K. I know not the best choice, you can boo me now.
After a successful root, I installed safestrap. Unfortunately safestrap kept crashing upon starting the app, I couldnt even get it to set up. thats fine, I was just going to unroot and keep on living life, but then I stumbled upon Xposed installer, that modified and tweaked like a custom rom but without all the risk according to a website. I said hey thats worth a try and I did. After the Xposed installer setup and a reboot, I wad looking for mods on the web and all of a sudden my apps and system files started crashing to the point that I could not use my phone. I immedeately uninstalled Xposed installer ss soon ad my phone stabalized and unrooted.
I thought everything was good, 4 hours later the apps and system files started crashing again, so I did a reboot and I noticed that custom with the lock came up on intial startup. though I was told I was unrooted by the K program and even double checked using a rootchecker app, which stated I had indeed an unrooted phone. I did another reboot and no custom or logo came out. At this point I just wanted a working phone and As much as I hated doing so I did a factory reset. This seemed to have fixed the problem, but 4 days later my phone randomly went into a bootloop. I couldnt get it to stop so I took out the battery and that did not fix it.It was strange becuase I thought it might have been unrelated since it wasnt doing this when I had the issue with Xposed installer.
After yet another factory reset my phone seems to be fine, its still too early to tell though since its only been about a day. I had the normal google playstore and gvoice app crashing...Sigh..the only thing different was that sometime yesterday after the second factory reset a notification popup of unfortunately a sytem file stopped working came up. I acknowledged it, but thankfully I havent gotten any problems. I forgot what the notification read. hopefully its not related to what happened the other day.I dont know if this is related to one another, but I did notice that before I rooted my android system had automatically upgraded. I looked for issues like this on the net and saw people where having random bootloops after system upgrades and that unchecking scanning for wifi fixed the problem. though I did this and it did not work, thats why I did the second factory reset.
Now Im asking for help if any further issues arise. I love my Note3 and at this point I just want a reliable working device. Im keeping my fingers crossed and hopefully that will be the end of it, but in case it started to act up again, what can I do? any information and help is greatly appreciated. thanks.
Never uninstall any Xposed app that changes system files without first reverting any changes you made with it. Some of them are permanent until they are turned off in the App. Then you can disable the module.
You may want to look into this http://forum.xda-developers.com/showthread.php?t=2559715
I cannot stress this enough.
READ READ READ.
Too many times have I seen someone read a line or 2 then rush right in ultimately turning their very nice phone into the most expensive paperweight one could own.
On that link I posted, read it until your eyes are bleeding if you truly need to start from scratch.
I am not joking here.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Thanks man. it makes sense. I will look into it. you mentioned read. I have read what I thought was plenty, but always ideas and opinions differ, sometimes knowing too much and causing what they say decision paralysis. Because I still read about the Xposed experiences and different people go about it in a different way. but what you mentioned about reverting back makes alot of sense.
Hello guys,
I've been messing around with my Motorola Razr i XT890 the last couple of days, trying to get it "back to life".
It suddenly shut down and would get stuck on the red "M" logo, right when the animation would start (the white wavey-type of lines freeze and that is all it would do. I, myself, am not really much up to date on rooting, installing custom roms, you know; the whole developing thing (I find it interesting, it is just that I lack time to be able to learn more). Anyway, the phone got stuck and I've managed to factory reset it, after a while the phone would freeze and again get stuck on the red logo, this went on until it would not boot at all. All I got was a short vibration and the green led would light up for like one second. Using this forum I've found a solution to bring it back to the point it would get back into fastboot (Actually holding the camera button down with usb attached, install some specific drivers and then run a batch file).
At this point this is my situation:
I'm stuck on fastboot, however I turn on the phone it will get into fastboot (see attached image to see what it says)
[IMG_20160914_210059.jpg](https://postimg.org/image/ptin5opgl/)
I, for some reason, have Philz Recovery installed and tried to use adb sideload to install a few files but my biggest problem is that I'm not sure which firmware I need, I'm really confused about all the terms and what not. I'm not the type of person that pays much attention and like knows the difference between JB or KitKat or whatever. All I know is that the phone was purchased in Germany along with a contract with either Vodafone or O2 (really not sure). I have so many files and tools installed on my PC and I would like to delete everything and start from scratch. I have fastboot and adb working (except for RSDLite, for some reason it just won't recognize the device, while adb sideload did work....haven't figured that one out yet.
If any one happens to know. or can post a link for 1 or 2 versions of the firmware and help me out. Just point me in the right direction, I know my way around a computer but like I said, I've never really done much in this area
I bought a new model Motorola soon after this one crashed the second time, so it's not even about the phone itself. I kind of challenged myself to get it working again, on top of that, it was a very good phone and I got really used to it. These new big screens are too much for me so if I get it working I might actually start using it again lol.
Also thanks to all of you who put time and effort in helping people who have these kind of problems, it's a really nice community overall and I've gotten to like it and will try to spend more time learning about this. I might just help out some lost soul myself some day
PS; sry about the green lol, I actually just realized it...I just can't be bothered cropping it out
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Before restarting, I'm confident the "ear sensor" that turns the screen off when I'm on a call as functioning. I'm also confident the auto-rotate functionality of the phone was working perfectly.
After I tried to factory reset the phone from the power-volume reset options, I actually ran into a TON of trouble trying to get the phone to properly reset. It tooks me countless tries to eventually get the phone to start after resetting it over and over again. I was stuck trying to get the phone to actually move through the setup steps. SUPER frustrating. I actually went to sleep while the phone was somewhere in the middle of setting up and when I woke up the phone somehow eventually made it through some setup steps.
I'm now using the phone as I normally would, but it's very odd. The phone is a LOT more unstable. At least 3 of the sensors I had working have just completely stopped working.
The phone is in otherwise perfect condition. I'm genuinely confused about how I should go about trying to resetting this thing to a pure stock configuration and slowly installing apps again to make the experience what I'd want.
And no, I'm not a super power user. I am a strong engineer happy to do crazy things like flashing bootloaders and whatnot, but I'm honestly confused about where to start. I understand other versions of this device may have had corrupted persist partitions during updates -- those problems seem like my problems -- but I don't know how I should go about simply flashing my phone at the lowest level into something stock that I can try to build back from.
And obviously when talking to google support their suggsetion is that I mail them the device and wait 10 days without a phone. I'm confused about how that could EVER be a reasonable way to get a phone repaired, sigh -- phones are not toys, they're pretty critical to the day-to-day work of so many people including myself. I'm pretty disappointing with that approach from Google and I had always considered them much better than that before this experience.
Anyway, I'm really lost and I'd love to understand how to repair the software on my phone.
(You all kick ass!)
aliljet said:
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Before restarting, I'm confident the "ear sensor" that turns the screen off when I'm on a call as functioning. I'm also confident the auto-rotate functionality of the phone was working perfectly.
After I tried to factory reset the phone from the power-volume reset options, I actually ran into a TON of trouble trying to get the phone to properly reset. It tooks me countless tries to eventually get the phone to start after resetting it over and over again. I was stuck trying to get the phone to actually move through the setup steps. SUPER frustrating. I actually went to sleep while the phone was somewhere in the middle of setting up and when I woke up the phone somehow eventually made it through some setup steps.
I'm now using the phone as I normally would, but it's very odd. The phone is a LOT more unstable. At least 3 of the sensors I had working have just completely stopped working.
The phone is in otherwise perfect condition. I'm genuinely confused about how I should go about trying to resetting this thing to a pure stock configuration and slowly installing apps again to make the experience what I'd want.
And no, I'm not a super power user. I am a strong engineer happy to do crazy things like flashing bootloaders and whatnot, but I'm honestly confused about where to start. I understand other versions of this device may have had corrupted persist partitions during updates -- those problems seem like my problems -- but I don't know how I should go about simply flashing my phone at the lowest level into something stock that I can try to build back from.
And obviously when talking to google support their suggsetion is that I mail them the device and wait 10 days without a phone. I'm confused about how that could EVER be a reasonable way to get a phone repaired, sigh -- phones are not toys, they're pretty critical to the day-to-day work of so many people including myself. I'm pretty disappointing with that approach from Google and I had always considered them much better than that before this experience.
Anyway, I'm really lost and I'd love to understand how to repair the software on my phone.
(You all kick ass!)
Click to expand...
Click to collapse
I would try flashing the latest factory image via fastboot.
[Guide] Root Pixel 4 XL with Magisk Android 13
[Guide] Root Pixel 4 XL With Magisk Android 13 Android Security Bulletin—Feburary 2023 Pixel Update Bulletin—Feburary 2023 Introduction This Guide is for Pixel 4 XL owners that want to Root their phone, and enjoy the benefits of rooting it. The...
forum.xda-developers.com
https://forum.xda-developers.com/t/guide-unlock-flash-root-for-the-pixel-2-xl-taimen.3702418/ (This is for a Pixel 2 XL but the process is the same. It's basically a condensed version of the one above.)
aliljet said:
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Click to expand...
Click to collapse
You did not provide the most important information we need- whether your phone is bootloader unlocked. Probably not, otherwise you would have already flashed it with a full Google image, which returns the phone to "out of the box" condition. You need to determine whether you can unlock your bootloader. If you cannot unlock (allow oem unlock is off and or greyed out in Dev options) then you will not be able to fastboot flash ANYTHING. If that is your case, the next best thing is flashing a full OTA image (sometimes called a rescue OTA) from recovery mode using the OTA via ADB option. This means you need fastboot/adb installed and working on your PC. Instructions on how are on the same Google dev page for OTA's.
So, my phone's bootloader is not unlocked. But I have an update for the crowd that may one day find this. I know your frustration and I can report that my phone is once again fixed.
A day (or two) after I sent this, a set of updates came down to my phone. And WebView was updated. That restored all of my sensors and also restored most of my crashing applications. It was an incredibly odd experience.
My phone once again functions. And the nightmare of owning a Google phone and talking to Google support has ended.
I'm in the process of trying to get a copy of my system from the lenovo assistant. I've looked around for a guide to installing TWRP and Magisk. But I noticed something when putting my phone into fastboot mode. The list of comments on the android screen states that my phone is an XT2045-3. On the box the phone came in, it states that it is an XT1925-6. So which is it? It's been a long time since I've attempted to meddle with my phone, so I am going slow. But this one makes me apprehensive about which files to use. And it's just weird.
Getting old I guess........I was wrong, the box was for my OLD phone, hence the confusion. Sorry.