First post here, please excuse my ignorance. This is a Virgin Mobile HTC One V. I never rooted a phone before, and was just trying to do a basic rooting, and somehow got into trouble. I would like to return the phone to stock and start over.
Right now the phone boots itself into bootloader, and shows me this:
Relocked
Security warning
PRIMOC PVT SHIP S-ON RL
HBOOT-1.57.0000
RADIO-1.00.00.0928
eMMC-boot
Jun 18 2012, 10:22:43
I am able to do this: fastboot getvar cid. The response is this: cid: SPCS_002.
I am also able to do this: fastboot devices. The response is this: FA2AKX405758 fastboot.
I have attempted to use this RUU:
RUU_PRIMO_C_ICS_40A_Sprint_WWE_VM_1.08.652.6_Radio_1.00.00.0521_2_NV_VM_3.46_0503_PRL61008_release_262414_signed.exe
It gives me error 170, USB connection error (even though I have installed the HTC drivers). I relocked the phone in an attempt to get that RUU to work, but it didn't help. I also tried to extract the rom.zip from the RUU.exe (by finding it in a temp folder, as described on another XDA thread), but the rom.zip acts corrupt. Various zip programs refuse to open it.
Before relocking the phone (in an attempt to get the RUU to work) I tried this:
fastboot flash boot boot.img
I did that with various boot.img files I found via threads here. This just created various problems. One result was that I was in a bootloop. Another result was that I booted to the screen that said "this build is for development purposes only do not distribute outside of htc without written permission." And it would hang there.
Now my condition is that I boot directly to bootloader.
Starting from the beginning: I unlocked the phone using the unlock bootloader procedure at htcdev. No problem. Then I figured I should do a backup right away, so I installed CM Recovery. Right away I knew I had a problem because it did not run correctly. It would present a menu. Then I would select "backup and restore." It would present a splash screen (with the hat) and just hang there. When I pressed power, it would return to the menu. That's when I started trying various other things.
I never got as far as doing anything with superboot or superuser, which is what I thought I was going to do after doing the backup.
I have read a zillion threads here, and tried various things from those threads, but I'm afraid that without specific help I'm just going to make it worse. I'm pulling my hair out, so I hope someone here can help me while I still have a few left. Thanks!
OK, I have made some progress but I'm still pretty stuck.
I have been able to solve two problems I had before. Before when I ran the RUU, it gave me a USB error. And I could not extract recovery.img from the RUU. I solved both those problems by moving to a different PC.
So now I can run the RUU, and it gives me a bunch of progress messages I didn't see before, but at the end it tells me this:
"Error 155, unknown error. The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again."
So then I tried the procedure described here:
http://forum.xda-developers.com/showpost.php?p=27301573
I unlocked the phone again, and I did this:
fastboot flash recovery recovery_signed.img
I did that using the img file I extracted from the RUU. Then I relocked the bootloader, and I ran the RUU again. But it gave me the exact same error (155).
What should I try next? I notice that the RUU also contains these img files:
system.img
radio.img
boot_signed.img
Should I try flashing those?
Any ideas would be greatly appreciated!
Edit: One more thing. When I ran the RUU, at the end the phone said this:
RUU
Hboot version is older!
Update Fail!
OK, the next thing I tried is the method described here:
http://forum.xda-developers.com/showthread.php?t=1674226
I extracted rom.zip from the RUU, and I renamed it PK76IMG.zip, and I put it on the sdcard, and then I rebooted the phone. The phone found that file and tried to install it, but in the end it gave me the same error message: "Hboot Version is older." On that same screen I see that my current Hboot is 1.57.0000. I guess the RUU contains an older Hboot?
Anyway, that's the same error I get when I run the RUU as an exe.
I notice a couple of people in that thread reported the same problem (Hboot is older), but it's not clear how or if they got around this.
Any ideas?
OK, so here's the next stage in this saga.
Looking around, it seems that there is no RUU for this phone, because I have Hboot 1.57.0000 and radio 1.00.00.0928. I have noticed that people with those specs cannot find a RUU that works, but they have been able to get the phone working with RhythmicRom. I see that discussed here:
http://forum.xda-developers.com/showthread.php?t=2147407
So what I'm trying to do now is install RhythmicRom, but I'm having trouble doing that, I guess because I don't have CM Recovery installed, so the standard recovery is running instead.
I have placed RhythmicRom_v1.4.zip on my sdcard. I am able to boot into bootloader, and I have done factory reset. In the bootloader, I can select Recovery and I see a screen that indicates the phone is looking for something (green circle containing green arrow pointing down, and with a progress bar at the bottom, and an icon of an sdcard). But I guess it doesn't find what it's looking for, and then I see the screen with the red triangle/exclamation mark.
I'm thinking that maybe it will work if on the sdcard I rename RhythmicRom_v1.4.zip to whatever the phone is looking for. Maybe I should rename it to PK76IMG.zip? Just a guess.
Many thanks in advance.
OK, that sort of almost worked. On the sdcard, I renamed RhythmicRom_v1.4.zip to PK76IMG.zip. I booted into bootloader, and it looked like the phone found that file, and loaded it. Then I did this:
fastboot flash boot boot.img
With the boot.img that was inside RhythmicRom_v1.4.zip. Then I rebooted. Now the phone gets to the red animated Virgin Mobile splash screen with the annoying audio. That seems like a good sign, since I haven't seen that in a while. But instead of continuing to boot, then I see the white HTC screen that says "this build is for development purposes only do not distribute outside of htc without written permission." And then it continues to loop between those two screens, so I am stuck in a bootloop. Although I found I was able to interrupt it and get back to the bootloader.
Not sure what to try next. Any suggestions?
Wow, I can't believe you haven't had a single reply.
Ok. First of all.... Use TeamWinRecoveryProject
( TWRP ) as your recovery img
So easy to use
Use fastboot the flash
fastboot flash recovery recovery.img
Then boot into your new touch screen recovery
Now click wipe
Cashe,Dalvick,Factory Reset, System
In that order. It makes sure every thing is wiped thoroughly.
Now navigate to where the Rom is you would like to use and flash it in recovery.
After It's flashed click the wipe cashe/dalvick
Then click home,reboot,bootloader.
Once in bootloader, flash the kernel/bootimg
fastboot flash boot boot.img
After the boot.img is finished,
fastboot reboot
Victory and enjoy the awesomeness of custom ROMs!
P.S. don't forget to unlock your bootloader again. First and foremost
fastboot flash unlocktoken Unlock_code.bin
Russell, thank you for your response. After 24 hours with over 100 views and zero replies, I figured that meant that I had already done the proper steps, and there wasn't some obvious solution I was missing. Although I can see now that I should have tried TWRP. It couldn't have made things worse, and maybe it would have worked better for me than CM Recovery (which seemed to fail as soon as I installed it).
Another key thing was when I figured out that there is no RUU for my specs (because there was an OTA that installed a newer hboot and radio). I like the idea of trying different custom ROMs, but I don't like the idea of never being able to go back to stock, since I would expect that all the custom ROMs have some quirks that I might find unacceptable. But I notice that you have the same hboot and radio, and I assume you have a backup of your stock ROM, so maybe you could have helped me with that.
Anyway, at literally the exact moment that you were posting your comment, I was standing at the UPS counter handing them the phone. If the phone had been working, we would have heard it buzzing inside the box as your email came in! The phone is heading to the HTC repair facility in Houston. They told me they would unbrick it for me for less than $35. I haven't seen anyone else report this, so maybe I was misled and it's too good to be true? We'll see. I don't like being without the phone for a week, but $35 seems like a cheap price to clean up the mess I made.
Anyway, thanks again for speaking up.
Check out the CDMA development thread
Whenever you get your phone back.....
Good luck
I see the thread you're talking about. I just did the download (might as well have it handy). Thank you.
Hope it helped or helps in some way
:beer:
---------- Post added at 02:40 AM ---------- Previous post was at 02:35 AM ----------
I gave you a thanks for first download
Similar problem
Hi,
I had a similar problem. Following this thread I have successfully "unbricked" my phone. My main concern though is activating my phone on VM, which I'm unable to do as I can't go back to stock. I bought the phone as is from craigslist. Any suggestions?
Edit: Internet seems to work though. No go on phone calls or texts, when trying to call this is what I get(Audio):"Account couldn't be verified"
Visit the HTC one v CDMA thread I have a stock rooted Rom there for the taking
Yes, here's the link to that thread:
http://forum.xda-developers.com/showthread.php?t=2321904
It would be interesting to hear if your rom works for cellphoneman.
Related
I have officialy given up on repairing my phone. Looks like it's not possible to fix this thing. Just spent the better part of 3 pays (4hours of sleep a night) trying to get my phone fixed. My sister bought this EVO through some work deal and gave me it on Christmas. I rooted it that night, and bricked it 30mins later, because of the newer partition scheme it is currently impossible to get this phone back working...
This is what I have now. A EVO 4G that boots normally to this screen. ftp://eto.homeip.net/shared/IMAG0003.jpg
A Vol Down + Power Boot boots to this screen. ftp://eto.homeip.net/shared/IMAG0004.jpg
I can also navigate to this screen. ftp://eto.homeip.net/shared/IMAG0005.jpg
Because of the S-OFF it is obvious to those in the know that I rooted my phone.
I'm just wondering if you guys think this scenaro will work.
_________________________________________________________________
Walk into a Sprint Repair Store, tell them my sister just bought the phone new (about a week ago) and gave it to me as a X-Mas gift. I chose to do the latest OTA-Update, and after it stopped booting and only went to this screen. ftp://eto.homeip.net/shared/IMAG0003.jpg
Where I'd have to pull the battery to turn it off.
They will probably try VolDown+Power and might comment on S-OFF (which I will say I don't know what that is).
Hope they give me a new/refurbished EVO for free or less then $50.
===============================
Questions
* Should I go to a Sprint Store I've never been to? (There are stores within 20miles of me) (Closest knows I root phones, then other I've been into a bunch of times and may have given up on me)
* Should I get the receipt from my sister, who I don't want to tell I rooted/bricked phone
* Also please give me suggestions of anything that will help
BTW
* Am well within 30days of buying phone, though I'm not sure if my sister bought it through Sprint or not (Think she did though)
* I have pin/name/number on account and can easily activate a different phone they give me.
* Would rather not tell my sister or even get the receipt from her room to keep her from suspecting anything, but can if need be
Thanks for your suggestions, wanted to get this done by the end of the week before I head back down to San Luis Obispo for college. (Where there are fewer Sprint Stores to spam)
The Good news: If you're screen is turning on (using ANY method) you're Evo isn't bricked.
The Bad news: I don't know what you did. I would suggest trying the unroot method and seeing if you can get yourself out of this pickle that way. My first rooitng experience everything went horribly array, and I ended up just accepting an OTA to get out of it.
http://forum.xda-developers.com/showthread.php?t=884060
Pick which ever one you like and put it on the root of the sdcard. I couldnt tell you because if you didnt record what software you started with niether could I.
LaloHigh said:
http://forum.xda-developers.com/showthread.php?t=884060
Pick which ever one you like and put it on the root of the sdcard. I couldnt tell you because if you didnt record what software you started with niether could I.
Click to expand...
Click to collapse
What do you mean record what software I started with? I had 2.02, now have 0.76 (But my screen says 2.10). I've tried both the exe and the PC36IMG.zip that you've linked.
Using .exe gives me a Error 170 (Not recognizing my phone is plugged in)
Putting PC36IMG.zip on sd and using hboot gives me Failed-PU, Partition Update Fail! for every category but Radio_V2. BTW I'm supposed to use the first two files from that link
SUPERSONIC EVT1 ENG S-OFF
HBOOT-2.10.0001 (PC36*****)
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Mar 30 2010,11:24:04
Greenfieldan said:
The Good news: If you're screen is turning on (using ANY method) you're Evo isn't bricked.
The Bad news: I don't know what you did. I would suggest trying the unroot method and seeing if you can get yourself out of this pickle that way. My first rooitng experience everything went horribly array, and I ended up just accepting an OTA to get out of it.
Click to expand...
Click to collapse
Well what I did was messup the way it sees my partition. I have a nwer partition scheme i believe but the 0.76 software thinks I have the older partition settup.
If you mean unroot method from this post http://forum.xda-developers.com/showthread.php?t=829045 the one I rooted with then I can't do it cause I have no recovery. I can't get to it cause bad partition settup.
I know I can run fastboot erase commands, do you guys think I should run
Code:
fastboot erase boot
to create an unbootable system. One that doesn't even have the screen turn on?
*Which if any partition can I delete in order to never have the phone even turn the screen on?
Here's the choices (wimax, misc, recovery, boot, system, cache, userdata)
if your getting error 170, the RUU can't communicate with the phone.\
Can you get Hboot USb on? IF so, the RUU may run with it.
Drivers installed on computer?
Otherwise, you mave have blown out USB port, like I did.
Try putting the RUU, rom.zip (rename rom.zip to PC36IMG.zip) to your sd card, and see if that saves your a$$.
If that don't work, better run it over with a car or something and take it back.
The good news is you are still in your 30 day warranty. The solution I would suggest is try to flash the bootloader back to hboot 2.10. I would find a pc36 with 2.10 and flash away. Maybe even fastboot erase every partition except boot and hboot first. Don't do radio or wimax either or it will brick your radio and wimax. Then flash a full pc36. Other than that, manually brick. I would erase hboot and boot to brick.
Good luck
If you erase boot.img, it will still go to hboot. Erase the touchpanel image. That way they cant see it. By the time your phone gets to its repair destination, "they" wont be looking for that type of thing. They will just repartition. Also, it wont let you erase hboot
What error are you seeing when you select recovery from the bootloader menu?
The RUU that you tried, what version was it? You MUST use the 3.70.651.1 RUU because your phone thinks you are on hboot 2.10. Do not try an older RUU.
--------------------------------
Try the following
1) Download File PC36IMG_Recovery.zip and Rename to PC36IMG.zip.
copy to the root of your SDCard and power off phone
2) Power your phone back on into the boot loader by holding power and vol-down until your presented with a white screen. It will read the pc36img.zip and as you if you want to flash. Say yes. Then it will ask if you want to reboot, VOL+UP for yes.
3) If your rom gets tossed in the process. Reboot your phone into bootloader select recovery, and reflash your rom....DONE
4) Once in recovery, flash HBoot 2.10 zip
6) Now try RUU 3.70.651.1
-----------------------------------------------
If that does not work then try the following:
1) Download the img file for the modified Amon_Ra Recovery
2) Put evo-test.img on the root of your sdcard
3) Put the phone in fastboot mode
4) fastboot boot evo-test.img
5) Once in recovery, flash HBoot 2.10 zip
6) Now try RUU 3.70.651.1
Update
thanks to some help I have gotten farther on this issue. Can get past USB Erro 170. Now get to Error 171 when trying to flash image. When i run RUU.exe it tries flashes then reboots into stuck image of 3 androids skating. Which I alwasy need to battery pull to fix. Heres the log
ftp://eto.homeip.net/shared/RUU_101228T160722.log
__________________________________________
So how could I remove touchpanel img? thanks
josh4trunks said:
Update
thanks to some help I have gotten farther on this issue. Can get past USB Erro 170. Now get to Error 171 when trying to flash image. When i run RUU.exe it tries flashes then reboots into stuck image of 3 androids skating. Which I alwasy need to battery pull to fix. Heres the log
ftp://eto.homeip.net/shared/RUU_101228T160722.log
__________________________________________
So how could I remove touchpanel img? thanks
Click to expand...
Click to collapse
But if you can't flash a RUU.exe, then you can probably flash a zip file of a ROM.
This can or be or is not correct, I am just curious how this well happened to you.
nope tried flashing ROM through hboot, fastboot... Tried 'fastboot erase boot' didn't do anything. I'm gonna update the OP on the current situation, giving up...
Are you able to use the bootloader to flash only the custom recovery amon RA zip? If you can get into custom recovery you will be fine. Once in recovery you can flash hboot radio etc 1 at a time with a reboot in between each flash. After that you can flash a custom rom and be happy.
i think he said multiple times that he was totally screwed and his partitions were messed up so he either needs a total memory reflash or god's private java code
illogos said:
Are you able to use the bootloader to flash only the custom recovery amon RA zip? If you can get into custom recovery you will be fine. Once in recovery you can flash hboot radio etc 1 at a time with a reboot in between each flash. After that you can flash a custom rom and be happy.
Click to expand...
Click to collapse
Can't flash through bootloader. Get Fail-PU
Which is a Partition Update Error
Hi, I need some help with my Desire HD.
I've been running Android Revolution for nearly a year now and had 6.1.5 running well until about a fortnight ago.
Initially, the volume keys started malfunctioning and the volume down would get stuck. Occassionally, the phone would freeze and I'd have to take the battery out and reset, and it would seem fine except the date was set to 11:00AM on January 1, 1980. Same date and time every time. Strange!
In the past week some processes have been failing, some downloaded apps and some google service framework. The phone then rebooted itself into bootloader and when i tried to reboot it would just loop back in to bootloader. after 10 or so reboots it would eventually boot back up properly.
Yesterday I ran SuperWipe and reinstalled Revolution 6.1.5 and things seemed to be running smoother. Then my phone froze again and is now stuck in the bootloader and nothing will work. The volume up key works nearly always and the volume down key has occasionally worked with alot of force, but i think this problem may be seperate to the software issues.
I once selected Reboot Bootloader and rebooted to a weird fuzzy static screen.
I've recorded a video of what is happening and posted it here: h tt p:// youtu.be/Sgp8pYin6yY
I've also posted a picture of the green text that flashes up in bootloader, I'm not allowed to post links so please go to the link in the comments on the youtube video.
From looking at other forum topics I think loading an RUU could be a solution, but I'm not sure how to do that.
Any help would be greatly appreciated!
Cheers,
Bickers
to flash an ruu or its pd98 equivilent is simple.
For an RUU what you do is in hboot select fastboot. then Plug in your phone and run the RUU.exe from your pc.
OR
If you prefer the PD98 method. what you do is place the pd98 file in the root of your sd card(not in a folder). boot into hboot. and hit up to accept the installation
its your choice on which RUU to flash but personally i would choose either the new sense 3.0 3.12 or the sense 2.1 2.50.
One thing to note is the issue with your volume down. If you still have warranty on it, i would get it replaced
Making RUU into .exe or PD98IMG.zip
Ok I think it's best for me to reinstall the original Vodafone Rom.
The "The Complete Guide 2 Return Rooted Phone Back 2 Stock for Vodafone Australia Warranty" guide relies on using Clockworkmod - which I can't get into because my phone won't boot past bootloader.
I have downloaded the 1.32 ROM from the above thread and it's a zip file but I need to know how to get it into either RUU.exe to run through my computer or PD98IMG.zip to run through bootloader.
Do I simply rename it PD98IMG.zip?
I've been searching and reading lot on RUUs and unrooting etc. but can't figure out how to do it.
I also have a goldcard that I created last time I flashed a custom ROM but I can't find the guide that I followed and I'm not sure if I need a goldcard.
Please take the time to help me and provide step by step instructions of how to take the 1.32 Vodafone AU ROM back up and install it onto my phone through bootloader.
Thanks a million and one!
No you can't rename that zip and flash in hboot. Unfortunately you need access to cwr to do that method.
I think first we should try and get you back up and running on any rom before you decide to go back to stock. Unfortunately for you their isn't a ruu for vodafone au to make it and easier process.
So for now try and reflash cwr and or a different ruu, to atleast get you in a working state. Give me a min to find a link to a guide to see if that will help you
Edit- try this
http://forum.xda-developers.com/showthread.php?t=1396253
Use the mirror links in the second post. If you have no way to transfer the files use the ruu method at the end. Links to the wwe and hopefully faster links are found in my last post in the thread
Partition Update Fail!
Thanks for your help.
Unfortunately when I try to flash the PD98 of the recovery image I get Fail-PU in red next to BOOTLOADER and RECOVERY.
and "Partition Update Fail!" in black underneath.
I also tried another recovery pd98 and got the same thing. About to try the RUU method from the PC, but if that doesn't work i'm not sure what to do
Hi, I have foolishly (possibly?) wiped Android off of my OneX
I was attempting to apply the Tegra tweak and well things went downhill.
I successfully unlocked the bootloader from HTCdev.
I proceeded to apply Interim ClockworkMod to gain root access
This is where things started to go wrong. Any new reboot would only take me to Clockworkmod screen.
I tried http://forum.xda-developers.com/showthread.php?t=1599748
clear cache, davik cache... relocking the bootloader - This results in the device constantly rebooting.
I attempted to apply the RUU ROM's ( from: http://forum.xda-developers.com/showthread.php?t=1543604)
From within ClockworkMod I was then able to:
adb push One_X_1.26.401.2_odexed.zip /sdcard/
Once there I used ClockworkMod to apply an update zip (which I was hoping was the Stock ROM).
A reboot just brought me back to Clockwork.
I then locked the bootloader ( fastboot oem lock. ) hoping it would then proceed to boot as expected.
It didn't just going to HBOOT or an attempted recovery (isometric view of a phone with a green arrowed circle -> RED triangle).
Please someone help, starting to panic a bit. The fact I can upload, the fact that there is some basic interactions should imply this is fixable, but how?
The boot to recovery sounds like you have the same problem that I had.
Perhaps you followed the same incorrect instructions as I did. See here for a solution.
mwhincup said:
The boot to recovery sounds like you have the same problem that I had.
Perhaps you followed the same incorrect instructions as I did. See here for a solution.
Click to expand...
Click to collapse
This may help.
with the locked bootloader you will only be able to run a proper ruu so before even attempting the instruction above unlock your bootloader again and proceed from there.
I might start working on some core .IMG files that can be flashed through fastboot to get you going again tomorrow
Sent from my HTC One X using XDA
THANKS!!!
booted back to the lovely ICS desktop
It looks like I did end up flashing RUU since none of the Vodafone branding is present (and it is actually better!)
No idea what went wrong but probably flashed over the boot as hinted at in the other thread.
The provided img files assisted. just need to get this Tegra thing working (not showing up as a running/registered process but thats another story)
Thanks all
So i recently purchased an unlocked HTC one x (white), and tempted by the improvements from mike1986's HD revolution ROM I decided to give it a try.
my phone had firmware 1.19 installed, i wasn't able to update the firmware due to the cid none error. I read a few posts in his thread saying to just install the rom anyway, so I did. the rom installed without error, i also performed the super wipe as instructed.
the phone booted up with the new rom, but about 3 mins after the OS loads (im able to choose my language, and i can see all the new languages introduced by mike1986's rom) it will always tell me that i have 0 battery charge remaining and automatically shut down(, regardless of how much battery is actually left. I had at least 80% charged. so basically im stuck in this boot loop.
Im not able to reload my original rom since my nandroid back up mysterious got wiped. what can i do to get my phone back to stock rom?
PS. ive basically spent the entire day reading multiple posts trying to find how i can get this fixed. Fastboot seems to be the only option but i just don't see any clear cut answers on how to do that exactly. i can't place any zip files in my SD ext, because the OS wont stay open long enough to transfer it through PC.
easy :-D i had this problem like 5 times , you need to back to stock again
snowwhite007 said:
1) Flash stock recovery:
Grab it from here: http://forum.xda-developers.com/showthread.php?t=1579797
Then Boot in bootloader >> Fastboot and issue the following command (assuming that the offical recovery is named recovery.img): fastboot flash recovery recovery.img
2) Relock Bootloader:
Boot in bootloader >> Fastboot and issue the following command: fastboot oem lock
3) Find and run/flash the RUU for your device, find it here: http://forum.xda-developers.com/showthread.php?t=1543604
Courtesy of DaDoctor
Mod or Die
Mod or Die
Click to expand...
Click to collapse
cool thx!
yah i read something like this, so i started to download a RUU 1.26 from TW unfortunately its taking forever. My original firmware was 1.19 does it matter that im upgrading to 1.26 also what commands do i need to use to flash this on to my phone? basically i need help with step 3.
edit: saifullah made me realize that there were others with the same problem, so i searched the forums and found the solution. just follow the 3 steps above, and make sure you have the exact same RUU number. mine being 1.19.707.1 i need to get an RUU with the same 3 middle digits ex. x.xx.707.x this is like an area code if that helps anyone else. there are a ton of different ruu and you need the exact one.
I had the same problem, extract the boot.img from the CWM rom that you tried to flash in the first place and flash it via fastboot with the command "fastboot flash boot boot.img"
It took me ages to find a fix, hopefully this can help!
It boot it Up! Thanks
Using Android Revolution 1.2.3
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