Help Un-Rooting Bell Canada HTC One M9 - One (M9) Q&A, Help & Troubleshooting

I have an HTC One M9 that's rooted with the CM 13 based on 6.0.1, and I have TWRP Recovery installed. I wanted to unroot my phone and install the stock ROM to my phone because I have some physical problems with the phone and some software problems that aren't related to the root or CM 13. I followed a guide that said to get ADB and Fastboot on my computer so I did that (AT this point I had already gone to TWRP and wiped the device including the OS) and then it said to get the stock ROM. I tried to look for the stock ROM and I found a few so I tried one. It said to flash it by using commands on ADB to flash it. I did all of the commands it asked and when it came to typing "fastboot flash recovery (file name here)" it said waiting for device and didn't ever change. I tried putting the zip file onto my device and then lashing it using install on TWRP and it failed then automatically restarted the phone with no OS so it was bricked. I waited for the battery to die and then booted the phone into recovery mode. This is currently where I'm at. I live in Canada and use Bell so I can't find the stock ROM on the Official HTC website, or anywhere else for that matter. I would like to use my phone so any help would be appreciated. Thanks!

Related

Help urgent!!!!!!! Gn stuck on google symbol

So I was trying to put JB on my GN using this:
pcworld.idg.com.au/article/429778/how_update_your_galaxy_nexus_jelly_bean/[/url]
I reached to apoint where i had 4.04 yakju, but when I put the file to get JB, It said error and aborted, i went to wipe data and reboot, wipe data worked fine, reboot led me to the google home screen and is stuck there.
I can access fastboot. Recovery mode takes me to that android with the danger sign, doing another reset doesnt work, clicking reboot doesnt work.
I'm pretty nooby at this. I read a few other forums and they said something about flashing a new rom or something but I don't understand.
Please help! The phone isn't mine! Need help ASAP before owner finds out I messed up their phone, thanks!
If you can access fastboot and your bootloader is unlocked just flash a stock system image.
These are the reasons people shouldn't just one click everything they do. If you understood how fastboot worked you would be golden.
Reflash recovery. Then mount USB storage and then get a ROM on there and flash it.
Sent from my Galaxy Nexus using xda app-developers app
xjman said:
If you can access fastboot and your bootloader is unlocked just flash a stock system image.
These are the reasons people should just one click everything they do. If you understood how fastboot worked you would be golden.
Click to expand...
Click to collapse
The site I went to dumbed down everything, and all i had to do was input numbers into some program. I double checked what a fastboot was. I definitely don't know how to work that. I mixed up the fastboot with the bootloader...
how do i reflash recovery and get a rom on there? I know this is asking alot....sorry
My bootloader is unlocked but im not rooted. I will (figure out how to) root if needed.
Open up a terminal on your computer use fastboot to flash the recovery image.
Since you didn't take the time learn what you were doing to begin with, I would take the time now to go read. The answers are easily found with google, or searching this site.
Roughly, install adb and fastboot on your computer, load drivers for your phone, download the proper recovery and put it in the fastboot directory on your pc, plug in the phone boot to the bootloader
open term
./fastboot oem unlock
./fastboot flash recovery <nameofrecoveryimage>
I reached the fastboot part, but when i type in "fastboot flash recovery (file name) it says it cannot load file name...
What is the proper file that I should use? Running 4.04 YAKJU looking to just recover the phone back or switch to jelly bean, whichever is easier. (jelly bean if they are both the same)
okay okay okay, i think im almost there...got a rom and extraced it, i know how 4 files:
Boot 4,148KB
Recovery 4,478 KB
System 316,112 KB
Userdata 137,555 KB
Which one do I put for fastboot oem recovery (fileimagename)
Thanks
Stuck on Google screen
Background: GN is unclocked and rooted. I've had quite a few devices and have rooted them all and run custom ROMs. I am fairly familiar with all of the tools needed, but by no means an expert. I have the Android SDK with adb and fastboot installed on my Win 7 x64 machine as well as the samsung drivers. I loaded a Jelly Bean ROM the day after it was announced at Google I/O and ran it for awhile before I started having touchscreen issues. I removed the battery and restarted the phone and had no problems for about a week or so.
Problem: I started having touchscreen problems again, but figured it was perhaps due to the early version of JB that was ported over from the GSM version (I believe). I tried a few other versions that were released later and they would work for a few days and then the touchscreen issue would pop up again. At this point I started thinking it might be a hardware problem because if I twisted the phone (weird, but it worked) the touchscreen would respond. I flashed another version of the Jelly Belly ROM yesterday (//rootzwiki.com/topic/28677-rom-jelly-belly-v33-07122012-jellybean-411-pure-aosp-its-all-about-speed/") to see if it would work by chance. Unfortunately, I still encountered the touchscreen problem. After rebooting a few times my GN started bootlooping and would not load into Android.
Actions: At this point I tried to recover from a backup, but much to my dismay it failed (don't remember exact error). I tried a few other backups with no luck. I tried reflashing another ROM, no luck. Then I started seeing some errors when booting into recovery (E: can't mount cache/recovery/log. Around this time I also noticed I was getting errors with sdcard. I decided to take the phone back to stock using the verizon ICL53F factory image. I tried via numerous toolkits (Odin, Galaxy Nexus Toolkit and directly from fastboot) and have been unsuccessful. I've searched every forum and have literally tried everything I with no luck. I can flash new recoveries, but it doesn't solve my problem. Right now phone is back to stock with stock recovery and just bootloops at the Google screen.
I assume my phone is completely hosed, but am hoping someone might know something I don't and might be able to help me restore this phone.
Edit: I tried flashing an imm76k factory image via fastboot and was finally able to get in. I must have had a bad icl53f factory image...close call.

[Q] Help Please with possible bricked phone after upgrade to 4.0.4

Hello
This is my last ditch attempt to fix my HTC ONE X, before I resign and send it to HTC for a repair. The phone was rooted and locked to T-mobile UK when the update for 4.0.4 came through 2 days ago. I downloaded it OTA and installed the update. After the update had installed the phone was in a bootloop. It kept loading the home screen and rebooting.
I have tried the following with no success!
Initially couldn't get access to recovery, but when I reflashed recovery I have no access to the sd card. The drive shows up on my computer when connected via usb but it says there is no drive connected and all my files appeared to have been deleted, although the reset folders are visible! So can't transfer a custom ROM and flash.
I have reflashed a boot.img and now the ONE X doesn't even get to the home screen it just hangs at the htc splash screen.
I have also relocked the bootloader to flash a RUU. This hasn't worked either. It appears to be working and the phone screen turns black with an install icon, but the RUU stops after approx 1 min, says it's completed, but nothing has changed on the phone.
This has been a nightmare and am just about to package it up and send to HTC and accept any charges for rooting!
Please help!!!
Can you get the phone in hboot/fastboot ?
What do you see when you enter
Fastboot devices or adb devices ?
If it works unlock your bootloader again with the unlock token.google the exact fastboot command, don't know it for sure now i'm on my phone.
Reflash custom cwm recovery (5.8.0.4 if i'm guessing it right) you can mount sd card within recovery
From there flash a custom rom again.
Flash kernel from the rom and install it with a full wipe.
Think it's your best option as far as I can see now
If your bootloader is locked and you have a stock recovery you can not flash anything
Verstuurd van mijn HTC One X
Thank you for your reply.
I managed to finally get access to the SD card and transfer a custom ROM. Which I flashed and the phone is working again!!
Thank you for your help!! So relieved!

[Q] Help with firmware flash screw-up

I bought an AT&T M8 on eBay a few months ago. My carrier is T-Mobile. Everything actually worked fairly well but there are a few nagging issues. No OTA updates, MMS doesn't work, etc.
I did some research on the forums here and elsewhere and the solution seemed to be flashing the phone to a stock T-Mobile firmware. Tonight I set out to do that.
I downloaded and paid for Sunshine. Installed with no issues.
I installed HTC Synch and ADB on my PC
I flashed CWM recovery onto the phone using fastboot. TWRP wouldn't work for some reason.
I used CWM to install SuperSU to root the phone.
I used fastboot to change the CID to T-MOB010.
I used scotty1223's instructions here to change the MID from 0P6B12000 to 0P6B13000.
There were some false steps along the way but I think everything worked fine to this point.
Next I used fastboot to flash the firmware I found here. At this point I don't even remember why I decided that was the right choice.
The firmware flash failed the first time but apparently that isn't uncommon. I ran it a second time and it seemed to succeed. I rebooted the phone using fastboot. When it comes up I see the HTC logo on a white background and I can still hear the AT&T "chimes" but I don't see the AT&T globe. And that's it. The phone won't finish booting. I can reboot into the fastboot menu but Recovery just gives me an red triangle with an exclamation point. ADB can't communicate with the phone anymore. So I feel like I'm stuck.
Any advice on what to do next?
AlphaJ23 said:
I bought an AT&T M8 on eBay a few months ago. My carrier is T-Mobile. Everything actually worked fairly well but there are a few nagging issues. No OTA updates, MMS doesn't work, etc.
I did some research on the forums here and elsewhere and the solution seemed to be flashing the phone to a stock T-Mobile firmware. Tonight I set out to do that.
I downloaded and paid for Sunshine. Installed with no issues.
I installed HTC Synch and ADB on my PC
I flashed CWM recovery onto the phone using fastboot. TWRP wouldn't work for some reason.
I used CWM to install SuperSU to root the phone.
I used fastboot to change the CID to T-MOB010.
I used scotty1223's instructions here to change the MID from 0P6B12000 to 0P6B13000.
There were some false steps along the way but I think everything worked fine to this point.
Next I used fastboot to flash the firmware I found here. At this point I don't even remember why I decided that was the right choice.
The firmware flash failed the first time but apparently that isn't uncommon. I ran it a second time and it seemed to succeed. I rebooted the phone using fastboot. When it comes up I see the HTC logo on a white background and I can still hear the AT&T "chimes" but I don't see the AT&T globe. And that's it. The phone won't finish booting. I can reboot into the fastboot menu but Recovery just gives me an red triangle with an exclamation point. ADB can't communicate with the phone anymore. So I feel like I'm stuck.
Any advice on what to do next?
Click to expand...
Click to collapse
check that your cid and mid are now correct for T-Mo by doing a fastboot get var all.
Firmware you flashed is fine.
your phone is stuck in a bootloop which isn't un-common, due to the rom version and firmware version mis-maych I expect.
red triangle is stock recovery, so that's also normal.
at this point, rather than trying to reboot the phone, you should of just booted back to the bootloader fastboot usb mode and run the T-mo RUU, the first thing the RUU does anyway is boot your phone to the bootloader anyway, your just manually doing the first part yourself.
Thanks a lot for the help. A couple of follow-up questions for you. Adb/fastboot can't connect to the phone now. I've tried at the HTC white screen and the bootloader fastboot screen. It just says '< waiting for device >'.
I'm also having a problem with the RUU. When I accept the license agreement on the install it seems to crash. No errors but nothing else happens and the process isn't running. I'm going to try that on a different machine and see what happens. Thanks again.
Another update. The RUU install works fine on a different machine. I think that was a Windows 8.1 issue. The problem now is that the RUU can't see the phone either. So I can't get a PC to see the phone over USB at all. I assume that's because of the bootloop. Is there anything I can do from the bootloader to fix this?
Some progress. The RUU finally found the phone. I guess that was a timing issue. Now it seems to be stuck at 'Updating.... (1/7) Sending....'. It's been doing that for over an hour.
Finally, success!! I found a Reddit thread about the RUU failure. It recommended finding the ROM.zip that gets dropped in a temp folder by the installer, renaming that to 0P6BIMG.zip, moving it to the sdcard, and rebooting. It worked like a charm. Fastboot found the zip automatically and prompted me to install it. It took a little while to update but now I have a stock T-Mobile HTC One.
please help
AlphaJ23 said:
Finally, success!! I found a Reddit thread about the RUU failure. It recommended finding the ROM.zip that gets dropped in a temp folder by the installer, renaming that to 0P6BIMG.zip, moving it to the sdcard, and rebooting. It worked like a charm. Fastboot found the zip automatically and prompted me to install it. It took a little while to update but now I have a stock T-Mobile HTC One.
Click to expand...
Click to collapse
my phone has exactly the same problem but i really dont know what to do from here

Another boot loop problem!

Hi All,
I know this is my first post and its asking for help already but I can usually find the answer to anything I need by just searching.
But this time i'm really stumped
I can see that a lot of other people are having this problem and have tried all the solutions to no avail.
I was rooted before and had the notification that update was available.
I followed this guide How to get OTA Updates on a rooted HTC One M8 by sakitech on youtube as I have done before.
I flashed the stock recovery and rebooted fine.
then I applied the update from the notification you get and now I am stuck with this brick...
I can get into boot loader using a combination of up and down buttons with the power button.
I am S-on
OS4.16.401.13
Ive tried putting various 0P6BIMG.zip on the sd card and have had the following results
Device halted due to large image update fail
that's the best I have so far.
If anyone could help me get my phone back that would be great
if there is anything else I need to tell you let me know
Thanks Loads
Toefudge
On lollipop, OTA will fail when the stock ROM is rooted due changes in binary.
You need a pure non-rooted stock ROM. Re-unrooted a rooted stock ROM won't work either.
How to get OTA Updates on a rooted HTC One M8 is not applicable on lollipop
Install TWRP and restore non-rooted TWRP 4.16.401.10 backup and then install 4.16.401.10 stock recovery then redo the OTA.
You can restore only system if you want to keep your data or backup your data and restore later after the OTA successfully update your device.
Thanks for the reply
sorry I am in way too deep lol
would you be a super star and give me a little walk through of what to do as I have been trying for hours today already
Also if you could provide the links I need that would be most excellent
I need all the help I can get )
Read How-to and all the files needed are here : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Thanks again
but the phone is not recognised with adb now?
was before but now I open it up type adb devices and it lists nothing?
Help me Jesus lol
I'm having the exact same issue as the OP. Took an OTA and got bootlooped. S-On, Bootloader Unlocked, Bootloader 3.19.0.000, CID CWS_001. I flashed a GPE custom rom in TWRP to have a working OS, but now I can't figure out how to return to stock. I tried relocking the bootloader and then using the ATT RUU on HTC's website, but it failed because the system version was wrong or something like that. I have a backup of my data, but I can't figure out how to get this OTA so I can go back to stock and restore my data and not take an OTA again. Radio is [email protected] if that helps.
Toefudge1975 said:
Thanks again
but the phone is not recognised with adb now?
was before but now I open it up type adb devices and it lists nothing?
Help me Jesus lol
Click to expand...
Click to collapse
Why adb ? adb works only while in recovery or running system.
And the tutorial that I linked to you has nothing about adb, only fastboot
So what are you trying to do with "adb" ?
HI again day 3
How do I install TWRP without adb?
I can get into fastboot menu and have the TWRP .img on my SD card
How do I install it?
PLease Thanks
Toefudge
You don't need adb commands but fastboot commands !
so would you help me?
how and where do I use fastboot commands please?
as you can tell I haven't got a clue lol
so I type the fastboot commands in the same place but it just says waiting for device?
In your post #1, you mentioned you flashed stock recovery, how did you do that ?
It's the same fastboot command
after put your device in bootloader/fastboot mode and connect to PC, run this command:
fastboot flash recovery NameOfRecovery.img
If you don't have fastboot/adb properly installed, try this : http://forum.xda-developers.com/showthread.php?t=2317790
Yes I flashed the stock recovery to start when it was working
Then tried to do the update then it went into boot loop
I tried every thing including a factory reset.
Would this turn off the USB debugging? Stopping me from seeing the phone with fast boot/adb?
Many thanks for all that have helped me so far
No.. usb debugging on is needed for adb
fastboot doesn't need usb debugging on
Try the fastboot/adb link that I posted.
Also fastboot work when you put your device on bootloader/fastboot mode, most likely won't work while bootlooping
Ok cool thanks loads
I will try again I'm a bit
Just making my 3 boys dinner and then I'm back on it
Then I'll be back asking for help probably lol
What can i say ..
Thankyou so much for your help and patience
its all sorted now followed your instructions on the link after i reinstalled the fast boot software
You guys .

Stuck on team win recovery project please help

I have no idea how to root or anything like that, I bought this oneplus 3 and had a update a week later.. so when I did the software update it took me into teamwin recovery mode and now I don't know how to get back into my phone please help....
Did you buy the phone second hand or did you try to flash TWRP yourself? It shouldn't have TWRP installed by default.
Regardless, you can use TWRP to flash the latest update.
Given that you have TWRP, I'm assuming that you have an unlocked bootloader. Did you notice a warning pop up everytime you reboot your phone before? It should say something along the lines of "your device has been unlocked and can't be trusted". If not, you'll have to unlock it (it wipes your phone in the process).
If the bootloader is unlocked, you can simply download and flash the latest zip for OOS 4.0.3 in TWRP. This will update you phone and replace TWRP with the stock recovery (so you don't run into this problem again in the future when installing an OTA). If you don't intend to modify your phone in any way, then this is all you need to do, your phone should be functional.
There are plenty of threads with detailed guides on how to do all of this.
I'm also stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off.
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditiontally'
- Another zip flashes, but gets stuck at the end, no reboot option (manually but that's not the way)
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please
sndr1384 said:
I'm also stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off.
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditiontally'
- Another zip flashes, but gets stuck at the end, no reboot option (manually but that's not the way)
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please
Click to expand...
Click to collapse
Simple, check the OnePlus D/L sites for this one http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img and flash it by TWRP or fastboot to RECOVERY. Boot once with the official Recovery and all ist fine again.
This is issue of using a faulty twrp so for that when ur phone us booting up go to fastboot and flash twrp 3.0.4-1 and everything will work
emuandco said:
Simple, check the OnePlus D/L sites for this one http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img and flash it by TWRP or fastboot to RECOVERY. Boot once with the official Recovery and all ist fine again.
Click to expand...
Click to collapse
Similar Problem here:
just wanted to flash latest OOS 4.0.3, so I flashed back stock recovery with flashify and rebooted into recovery mode to flash the already downloaded OOS 4.0.3. zip. That's when it began to go poop! After rebooting it just went dark with no Chance to power it on again! No dice with power button, Volume up/down + power button, nothing! Not even the LED's are blinking when plugged in. So this one seems to be basically dead!
I got it once booting again after randomly pushing the buttons (after x minutes!?), but everytime I reboot the phone it just shuts off without beeing able to power it on again. At the Moment it's dead!
Any ideas what might happened? If I get it on again, should I immediately reset it to factory Settings?
I am kinda lost here! Any help/ideas would be much appreciated!
Flashify? Never used it and never trusted apps which flash stuff on a running system. Use fastboot and reflash the recovery partition. Link to recovery is in my former post.
fastboot flash recovery PATHTOIMGFILE
Thank you for your advice! Still a lot to learn! Got it up again, will try as you suggested!
It appeared that my stock recovery file was corrupted , but all is fine again! Thank you very much!
Mannycolon85 said:
I have no idea how to root or anything like that, I bought this oneplus 3 and had a update a week later.. so when I did the software update it took me into teamwin recovery mode and now I don't know how to get back into my phone please help....
Click to expand...
Click to collapse
I may have been the person you traded with to get the OnePlus 3, but I took the phone back and after 5 hours I got it up and running.
The phone would boot to TWRP, but even after wiping the entire system and dragging a ROM zip to the internal storage, reinstalling did nothing. It just kept booting back to recovery.
The solution entailed the following.
Download stock recovery IMG. Flashed through TWRP. Rebooted recovery and now was back to stock recovery.
Download the official OxygenOS ROM zip from the OnePlus website and changed the name to update.zip
Next I downloaded Android studio for access to ADB. I had never used ADB before, but I knew this was needed to push a file to the phone.
Needless to say, ADB kept freezing my computer when I would type in the commands to side load.
I deleted Android studio and installed a minimal ADB/Fastboot I found online. I opened my command prompt, typed the command for sideloading, and immediately got my installation starting. It took about 10 minutes to fully install. When it was finished, I rebooted and had a fully functioning OnePlus 3
Sent from my ONEPLUS A3000 using Tapatalk

Categories

Resources