Hello all. So my rooted HTC Rezound ran into a software problem. After powering it onn, it would get into the system, activate bluetooth (on its own), shut down and restart the cycle again. The only way to stop once it started was by removing the battery. For this reason I was forced to find a technician to replace my OS. However, the software with which he replaced the old one has problems of its own. compatibility issues with applications for instance. Somehow I found myself with this new OS running into its own problems too. the System UI is not responding which basically means I can do nothing on the phone. once I get the device powered up. the only functional element or command left of this ware is the dropdown status bar which is showing not even a single drop-down menu. This compelled me to try and install the CM10. OS package, the PH98IMG.zip in the ClockworldMod Recovery v6.0.3.2 but every time I try it aborts with the message, "Installation aborted"
please help me out what am I doing wrong and how do I make it right?
Telltower said:
Hello all. So my rooted HTC Rezound ran into a software problem. After powering it onn, it would get into the system, activate bluetooth (on its own), shut down and restart the cycle again. The only way to stop once it started was by removing the battery. For this reason I was forced to find a technician to replace my OS. However, the software with which he replaced the old one has problems of its own. compatibility issues with applications for instance. Somehow I found myself with this new OS running into its own problems too. the System UI is not responding which basically means I can do nothing on the phone. once I get the device powered up. the only functional element or command left of this ware is the dropdown status bar which is showing not even a single drop-down menu. This compelled me to try and install the CM10. OS package, the PH98IMG.zip in the ClockworldMod Recovery v6.0.3.2 but every time I try it aborts with the message, "Installation aborted"
please help me out what am I doing wrong and how do I make it right?
Click to expand...
Click to collapse
The recovery fails or the rom install fails? If it is the recovery, then you'll need to install it manually via the PC using fastboot. One of the more important things to note, is if your device is S-On or S-Off. It will tell you on the bootloader screen. If you are S-On (most likely), then you will have to install the rom in recovery, as well as take the boot.img out of the rom zip and install that via fastboot while in the bootloader as well. If this sounds like gibberish to you, then that just means you have a lot of research to do before you get this fixed...
Related
So, I managed to brick my Atrix 4G. It was originally running on Gingerbread 2.3.6, but I wanted the 4.0, so I set about rooting it and everything, which, as you can see, backfired.
What I did was:
1. Root it using the pre-install method (No "One-Click"- I actually tried that method, but it didn't work for me; thus, I had to go about doing it manually)
2. Unlocked the Bootloader.
3. Tried to install ClockWorkMod Recovery.
4. Tried installing the Custom Rom 4.0. WHICH FAILED BADLY. My phone wouldn't start at all. I mean it would switch on, and I could see the "Unlocked" on the top left, but it wouldn't go further than that.
Also, I was wondering if my phone's really rooted? because, after unlocking my Bootloader, my Superuser app's icon disappeared. The ROM manager wouldn't even work. I would get an error stating that "An error occurred while attempting to run privileged command," but I went ahead anyway, using the "Press vol. button while switching on..." method. I then cleared every single thing- i.e. factory reset, clear cached, etc. Then, I tried loading the zipped custom ROM file on my SD card; everything looked fine, as if the files were correctly uploading- at last, it even said the whole process was done. But, switching on, and waiting and waiting led me to nowhere.
Today, I re-installed the stock 2.3.4, but I wanted a 2.3.6, so I did a software update, but now my phone is stuck on the goapk logo screen. I read somewhere that this is because the Bootloader is unlocked.
HOW DO I GO BACK? D:
Hello, XDA forumites!
I've been lurking and reading a lot of threads in here for years, using all your knowledge to fix various phones. Today though is the day I first post and it is for good reason. I'm a guy who loves challenges but this one is making me go insane. I've spend the last two days looking for ways to fix this phone but NOTHING works.
So, the deal is that this phone turns on fine. It boots, it gets to the lockscreen and... it restarts itself. Again and again and again until the battery is removed. To fix it, I've tried the following:
- recovering/updating it through the Huawei official "firmware" supplied by the site: you put the file they supply on an SD card, inside a folder named "dload" and then hold vol up and down along with the power button to make the phone install the contents of that file, named UPDATE.APP. Needless to say it doesn't work. A menu appears with the options reboot system now, apply update from sdcard, apply update from cache, wipe/data factory reset, wipe cache partition and calibrate touch screen. Trying to apply update from sdcard only lets me browse the SD looking for the file but doesn't actually see the file itself, it just shows the dload folder empty (I've tried with 4 different versions of the file compatible with phones from Central America which is where I am ATM). Also, the factory reset does nothing (although it shows it wipes data), everything's there when I start the phone up.
- flashing it with SD Flash Tool: apparently partially works with the last version 3 of the tool (although nothing changes) while version 5 of SDFT doesn't even see the phone (drivers are correctly installed, adb detects it, more on this later). A problem that arises is that I can't flash the SEC_RO package on it (don't know why) nor the PRELOADER (not that one is supposed to normally, but I feel like it would fix my problem in this case).
- cleaning it in safe mode: booting it in safe mode made me notice that it was an app pretending to be Whatsapp causing the restarts (or, perhaps, the one that loads immediately after? The phone has several malware apps). In safe mode those apps didn't load so the phone stayed on. So I cleaned everything, activated USB debugging (for later use in adb mode) and restarted only to find everything as it was before I did the cleanup. I tried rooting it in safemode, cleaning again, still reverts to full "normality" after the restart. Same results when using the phone's proprietary SW HiSuite.
- installing CWM's recovery img through adb+fastboot: I installed all the possible - necessary or unnecessary - drivers (Google's, phone's official ones, PDANet ones) and the phone is correctly detected by the PC (visible in Device Manager) and is visible through the adb devices command. But as soon as I adb reboot bootloader it to fastload the CWM image, the phone stops being seen correctly and doesn't show up in fastboot devices, only showing "NEW: SAFE OLD:RISK" on a black background on its screen.
So, to recap: the phone restarts because of a malware at startup, reverts any and all changes made to it in safemode, doesn't wipe from the recovery menu, apparently has a corrupted bootloader and is impervious to normal flashing SW... Anyone got any more ideas on how to deal with it? The only option left that comes to mind is to fix it directly by flashing the internal memory using JTAG/RIFF but I don't have the equipment (nor do I intend to buy it).
Bump, hoping for some help...
One more bump, still stuck
First, don't get happy: I have no answer to your problem. Sorry. But I have a similar one. I was running a very efficient, rooted, stock ROM G730-U251, until I decided to switch from 'Ninjamorph Free' to 'Pro'. I've been made a lot of changes with Free version for a long time without any issues at all. Then, one day, when making a small, useless change with 'Pro', something went wrong; phone just rebooted and refused to get past bootanimation. With no custom recovery on hand, only solution for this is to flash ROM. Though I had no problem finding the official, stock UPDATE.APP, which flashed smoothly from the SD card to be fair. Mess came when, once flashed, I decided to install OTA update available, which I overlooked since phone was new. Big, BIG mistake. It just came with more restrictions than ever, letting me root, yes, but this time with 'Kingroot' only (as stock, I had no problem rooting with Framaroot) but soon discovered I wasn't able to use 'Super-Sume', 'Adaway' and 'Link2SD', because some system parts now CAN'T be mounted rw, even using ES File Explorer. To avoid any complication, decided to reflash UPDATE.APP just as I did before. No way I can do it this time. Don't know exactly why, but assuming it's not possible to update with a previous version of the 'same' ROM. So now I'm looking for a flashable stock ROM in order to try SP flash tool. Phone is in working state right now (not as yours), but I just don't feel comfortable with it as it is right now, because those apps are always the main reason why I actually root every single of my devices and simply because I like to have my stuff as my own way as possible. You know, truth is there's not much of an advanced support for this phone, not even here at XDA and I think that's because this is a Latin America version. We owners of G730-U251 devices are pretty much on our own, to say the least. Whatever, if the whole deal gets more complicated than it is, there's a strong possibility for me to end up getting rid of this phone. Sad. Really. It's actually a good phone. Though it WAS better...
DISCLAIMER: I'm completely new to Rooting devices.
My phone is an HTC One M9 running Marshmallow 6.0.1 on Telus.
I attempted to root my device recently to try and solve an unrelated issue that factory reset could not, which is no longer important.
I followed this guide and got all the way up to "Power off your device. Now, to boot into recovery mode.", which I can get into TWRP no problem. However, I cannot push "SuperSU" as it comes up as "device not found"(ADB drivers not installed? Though I got this far somehow). I thought this wasn't a big problem and I could install it later.
Now I'm stuck in infinite boot. The HTC logo shows up, and after a bit it changes and does the animation into the logo for the HTC One. Then it's stuck like this(bootloop?), the longest I've tried being 40 minutes. I can do a fake battery removal and then access the "download" bootloader, regular bootloader, and the recovery (TWRP) no problem still.
If I manage to get SuperSU installed will this solve my problem? Or are they separate issues? Can I flash another image to at least go back to "stock"?
I no longer have any idea what to do. Any and all help or suggestions are appreciated and I'll provide whatever information I can manage.
Further information: I have wiped the appropriate caches(dalvik included) as well as factory reset through TWRP in different instances. I've even downloaded the stock recovery image and wiped again. I simply fail to see what the issue is.
Edit: Managed to get SuperSU installed. I don't know what was different this time. Exactly how many times is it supposed to reboot on its own until it's done? Because it's been restarting for over 20 minutes now.
Hello. I have a Sprint M9. It had been acting flaking lately (I would try to install the latest update, and it would reboot without installing and report that the phone had recovered from an error and ask if I wanted to send to HTC). Tonight, I was trying to use DLNA to play video from my phone to my TV, I was in settings and gave DLNA permission to access my storage. As soon as I did that the phone rebooted without warning and continues in a loop of displaying the HTC logo, then restarting over and over.
I can get into bootloader, download, and recovery mode by holding down the volume down key. I have tried Wipe Cache Partition and Wipe Data, but the phone still will not get out of the loop.
Phone is stock. I have never tried to root or disable S-on or load my own recovery.
What, if anything, can I do to get my phone working again?
Just tried doing what I think is called RUU? I downloaded the .exe from this site:
http://www.htc.com/us/support/htc-one-m9-sprint/news/
It found my phone, and rebooted into download mode. It tried to flash my rom, but shortly after trying to send the file (progress bar jumped from 0% to 100% in 1/2 second). The utility gives me a Error [155]: Unknown Error. I've tried a couple times and get the same problem each time.
The utility reports I have version 3.41.651.21 and tries to flash to 3.41.651.31
Great, now it is telling me my software has been modified. (it hasn't) The only things I've done is run the RUU and reboot into recover to clear cache/data. Bad NAND?
Well, found out why RUU wouldn't work. Low battery. Apparently it ate a lot more battery than I realized while it was in the reboot cycle. Tried manually flashing the firmware and fastboot told me the reason it was failing. C'mon HTC, if the CLI can tell me there's not enough battery to proceed, your GUI utility should be able to as well.
Still leads to the question of:
- Why did this happen in the first place
- This is actually the second time I've had a problem with OTA, with the phone thinking the system had been modified. So either the OTA failing somehow modified the system before failing, or there's a bigger issue afoot. (as noted above, this phone is stock, I've never tried to root, install a custom recovery, or anything else)
shawndoc said:
Still leads to the question of:
- Why did this happen in the first place
- This is actually the second time I've had a problem with OTA, with the phone thinking the system had been modified. So either the OTA failing somehow modified the system before failing, or there's a bigger issue afoot. (as noted above, this phone is stock, I've never tried to root, install a custom recovery, or anything else)
Click to expand...
Click to collapse
Same thing happened to me. The update that Sprint pushed last Wednesday completely bricked my HTC One M9. Same failure mode that you experienced. Sprint technical center was unable to do anything with it, so they are replacing it, allegedly ( been waiting a week for said replacement ).
I talked to a few other people who had the same problem, by the way. Someone in Sprint's QA team completely dropped the ball on this update.
Well, even after RUU it says my system has been modified and the phone will no longer boot into recovery. Just errors back to Download with the message that recovery couldn't launch.
I've also now got intermittent problems with the com.android.settings crashing. So I've thrown in the towel and purchased my first non HTC phone since the original Windows Mobile days.
Hello there. The same problem has come to my mind and the phone has been off for almost a month. Did you solve your problem? If you could solve it, how did you do it? I sent you above the original stock rom set. Nothing changed. The phone developer rum works. but the original 0pja200 rom is starting again.
my phone soft bricked, unlocked bootloader and S-off. Whether it is possible without blocking bootloader flashed RUU rom?
Htc M9
unlocked
S-ON
os 3.38.502.31
Hello. i am very lost, very confused, and yeah much help appriciated.
i fix phones for a living, but have never dipped into the development side of things, so i gave it a shot by trying to root my m9.
i installed the android studio ADB thing and of course the htc drivers from htc-sync manager needed to do this.
i unlocked the bootloader with no issue and was able to use the OS just fine after that. after that it was onto rooting my device.
i was unaware of Nanadroid backups or similar programs so theres that
i used superSU 2.64 and TWRP 2.8.7.1a-CTB1-B1 for the custom recovery
when flashing superSU i was prompted it was successful and would now boot into the OS and a few reboots is normal. after waiting a while i knew it wasnt going to go through and that i had screwed myself.
i tried a couple different SuperSU versions with no luck, perhaps the TWRP is too outdated? could not find a way to update TWRP.
eventually after trying multiple different things, on the bottom of the download screen it prompt the 0PJAIMG.zip file was missing, searched for the right one but could not find it.
found an older one and it now gives me an option as soon as booting into the downloader to flash /mnt/media_rw/ext_sd/0PJAIMG.zip or cancel.
selecting cancel puts it intodownload mode.
when selecting "flash" it prompts "RU_MODELID_FAIL modelid in android info mismatched" flash fails, and then turns off.
the phone will reboot continously until power and vol down are held and put into download mode
Can anyone tel me where i need to go from here? What adb/fastboot do i need to be using?
Can anyone spell it out for me? im seriously so lost.
TIA