[Q] My ONE is in dead space - One (M7) Q&A, Help & Troubleshooting

I've got a 32GB Sprint HTC One m7, unlocked bootloader and operating on a Mac. I wanted to try and use this ROM (http://forum.xda-developers.com/showthread.php?t=2265820) to flash over what I have and see (with a sense of humor) if it would unlock my SIM.
I installed TWRP (http://forum.xda-developers.com/showthread.php?t=2173870), and before I could flash SuperSU, my dumb ass did a full wipe and erased the current ROM without backing up. So here's what my phone can do currently:
-Boot into boot loader
-Run fastboot/adb commands
-Boot into recovery [only after flashing via fastboot; will not stick]
The phone will not mount SD to a computer and when I flash a ROM via sideload or fastboot, it shows the HTC Developer boot screen, then the screen goes black and the orange charging LED stays on. I have to hard reset the phone and start back up in bootloader to get anywhere. I want to get back to square one, so I can actually do this the correct way. I've been flashing ROMs since the original Motorola Droid, so I know the biz, I'm just flat out of ideas at this point. Halp, please?

Null missed a part in the post
Sent from my HTC One

Didnt the Sprint version have an official RUU somewhere ... best to return to stock and restart

Yes, found the RUU. Give this a go!
http://forum.xda-developers.com/showthread.php?t=2250904
EDIT: OP, in the future, I'd avoid flashing things from here onto your Sprint version. Especially something like that, which is an unmodified stock HTC base. Most ROMs made for GSM phones need to be edited and further modified for CDMA devices, in my experience.
Sent from my HTC One

Maybe try adb push a rom onto your phone in recovery..

Thanks for the replies, guys. As stupid as it sounds, I really didn't think the builds between carriers would be THAT different (I was also unaware of a separate forum for Sprint *facepalm*). International vs AT&T versions? Definitely, but not between domestic carriers. Weird.
Anyway, I flashed a recovery out of the Sprint HTC One forum and then a custom ROM out of there, too, through ADB sideload and it's all running swell so far. Again, thanks a lot for the help!

Other way around, actually. International and AT&T are very compatible and similar. Same with T-Mobile. Best way to think of the same phone on different carriers is GSM vs CDMA, but even then CDMA specializes further.
Glad you got squared away!
Sent from my HTC One

Related

[Q] Not sure which recovery to install, not sure which version of the device I have

Got the HTC One (says M7 in the bootloader) from HTC directly. Popped in my SIM card and it connected right away to AT&T's LTE network. Now I'm unlocking and installing the recovery in hopes of a new ROM.
so...
1) Which version of the HTC One is this, ie which version of Recovery software do I install?
2) Does this matter, or is the recovery compatible across versions of the One?
Sorry for the newbage, but I figure I'd better ask than potentially brick myself.

GSM rom on CDMA phone (aka how do I unscrew my phone)

Hi there,
Yesterday I bought a Japanese HTC ONE (HTC J one, HTL22, M7-WLJ, Provider is AU-KDDI, it has a simcard).
As it was full of bloatware I S-offed using revolutionary (htcdev isnt allowed by AU) and flashed a recovery. Then I proceeded to flash Viper One. I asked in the thread if it would work and the answer was as long as it's not a dual sim device you should probably be fine.
So I flashed and ended up with a bootloop. No big deal as I backed up my original rom. I turned off my phone as it was pretty late already. When I turned my phone back on again it wouldn't boot into recovery anymore, it would just say entering recovery and then reboot. I tried reflashing the recovery again but it still just reboots when entering recovery.
So I asked in the TWRP thread what to do. "flash a RUU". Now the problem is that I can't a RUU.exe for this model.
Long story short, how do I get my phone working again? I assume I can't just flash a WWE asia version? From what I can gather the hardware still supports GSM networks.. so maybe it doesnt matter? I suppose if the hardware supports both networks it's just a matter of the correct settings/drivers being available in a rom?
sjaak1234 said:
Hi there,
Yesterday I bought a Japanese HTC ONE (HTC J one, HTL22, M7-WLJ, Provider is AU-KDDI, it has a simcard).
As it was full of bloatware I S-offed using revolutionary (htcdev isnt allowed by AU) and flashed a recovery. Then I proceeded to flash Viper One. I asked in the thread if it would work and the answer was as long as it's not a dual sim device you should probably be fine.
So I flashed and ended up with a bootloop. No big deal as I backed up my original rom. I turned off my phone as it was pretty late already. When I turned my phone back on again it wouldn't boot into recovery anymore, it would just say entering recovery and then reboot. I tried reflashing the recovery again but it still just reboots when entering recovery.
So I asked in the TWRP thread what to do. "flash a RUU". Now the problem is that I can't a RUU.exe for this model.
Long story short, how do I get my phone working again? I assume I can't just flash a WWE asia version? From what I can gather the hardware still supports GSM networks.. so maybe it doesnt matter? I suppose if the hardware supports both networks it's just a matter of the correct settings/drivers being available in a rom?
Click to expand...
Click to collapse
Look up hasoon2000 on bing and click the second link (should be a dev-host site)
Navigate to the One folder.
Download and extract the One all in one toolkit version 3.1
Put your phone in fastboot mode (Power and volume down button, should say "FASTBOOT USB" in red.
Try reflashing TWRP from toolkit to see if it works.

[Q] Problems with Flashing a Usable ROM on Sprint HTC One, 4.3, on hboot 1.55

I've been struggling with this for over a day now.
I unlocked and rooted my phone just fine (HTC One on Sprint, 4.3) - but when I flashed a ROM, I flashed Maximus HD, which was apparently an International version and not a Sprint one. I think that messed some things up. After trying a few different ROMs on top of that, nothing works.
Each ROM I flash will "install" correctly, but when it boots to the lock screen, upon unlocking it gives me the HTC splash screen.
I'm convinced that my accidental upgrade to hboot 1.55 is rendering it impossible for me to flash any working ROMs - be it stock or otherwise. I can enter Recovery mode, adb sideload, and flash ROMs, but none of them work.
I've tried Superwipe and then Bad Boyz, but it's the same thing. After installation, it sticks at the HTC splash screen.
So, my options are limited. I think I need to find a way to revert my hboot to 1.44 from 1.55 - that way at least the stock RUU is compatible. However, I can't find any way to do this; since I'm S-On, and I can't access any ROM to mess with settings, I have no idea how to do this, or how to flash a workable ROM in order to switch to S-Off.
Anyone have any ideas. I'm seriously distraught. I just bought this phone, and I love it. I'm so sad that I decided to try this rooting/unlocking/ROM flashing business because it's disrupted my sanity.
Any thoughts or ideas will help immensely. I will give more information if needed. Thanks!
WayneQuasar said:
I've been struggling with this for over a day now.
I unlocked and rooted my phone just fine (HTC One on Sprint, 4.3) - but when I flashed a ROM, I flashed Maximus HD, which was apparently an International version and not a Sprint one. I think that messed some things up. After trying a few different ROMs on top of that, nothing works.
Each ROM I flash will "install" correctly, but when it boots to the lock screen, upon unlocking it gives me the HTC splash screen.
I'm convinced that my accidental upgrade to hboot 1.55 is rendering it impossible for me to flash any working ROMs - be it stock or otherwise. I can enter Recovery mode, adb sideload, and flash ROMs, but none of them work.
I've tried Superwipe and then Bad Boyz, but it's the same thing. After installation, it sticks at the HTC splash screen.
So, my options are limited. I think I need to find a way to revert my hboot to 1.44 from 1.55 - that way at least the stock RUU is compatible. However, I can't find any way to do this; since I'm S-On, and I can't access any ROM to mess with settings, I have no idea how to do this, or how to flash a workable ROM in order to switch to S-Off.
Anyone have any ideas. I'm seriously distraught. I just bought this phone, and I love it. I'm so sad that I decided to try this rooting/unlocking/ROM flashing business because it's disrupted my sanity.
Any thoughts or ideas will help immensely. I will give more information if needed. Thanks!
Click to expand...
Click to collapse
Check PM
same problem like TS have
Having the same issues like TS..
Can somebody point me where to look for the answers,the difference is that im on .44 boot
Somebody please
MeiTeS said:
Having the same issues like TS..
Can somebody point me where to look for the answers,the difference is that im on .44 boot
Somebody please
Click to expand...
Click to collapse
Look HERE

[Q] Flashing KitKat on a Moto X with 139.12.35.ghost_row.AmericaMovil.en.PR

Hello!
I'm currently stationed in Singapore and bought a Moto X about a month or so ago from eBay. While I am anxiously waiting for my Moto X to receive the 4.4 update, I realised that the system version (after the previous camera update) is 139.12.35.ghost_row.AmericaMovil.en.PR, which I found to be a Latin America version after some searching on the forums and Googling here and there.
I also found this thread, where OP said that they can be flashed over to either the T-Mobile version. Does this continue to work for the 4.4 updates by T-Mobile or AT&T, and would there be anything else required for flashing? (I saw something about flashing new radios and all, but was quite confused by contradicting explanations and suggestions :/)
Thanks in advance!
// EDIT:
To add on after a bit of searching, I realised that I am allowed to unlock my bootloader, despite claims from the original retailer on eBay that the phone came from AT&T (which is notorious, even here, for their stance on bootloader unlocking). What gives?
I got the same Moto X from a buddy yesterday. I did a lot of searching and also discovered the thread about the phone being flashed to t- mobile.
I fooled the steps on another thread titled " Return to stock 100%" out something like that...
I downloaded the correct Att firmware and with the use of RSDLite, I successfully flashed my Moto X to ATT.... it took less than 10 minutes. And as soon as it booted up, I got hit with the "update available" message ( kit Kat)
Sent from my XT1058 using Tapatalk
Thanks for the information!
I've successfully upgraded my phone to the Verizon version (minus all the bloatware that I hastily blasted off), with root and TWRP. So this is what I did, for future reference:
It seems that AmericaMovil versions are not bound by the AT&T's locked bootloader policies, and other Latin America versions are probably free from the restriction too. So I managed to get my hands on the Motorola Fastboot and unlocked my bootloader. TWRP was installed (remember to use 2.6.3.1 and above for 4.4 support), and then flashed the Verizon system dump available here. Root was installed by TWRP.
After getting on the device and setting things up, I rebooted to recovery to remove lots of bloatware (available in /system/app and /system/priv-app). Had to remove some of them through Titanium Backup as the file names were not always indicative that it came from Verizon. I made the extra step of killing the god-awful boot animation that they had by replacing it with this.
And... that concludes my experience with this, I suppose.
I've been looking through a few threads and I am not comfortable enough to flash the T-Mobile rom over my AmericanMovil one yet.
I can't seem to find step by step instructions on how to do this.. Would anyone like to explain it from the ground up?
My understanding
1) unlock bootloader
2) flash a recovery like twrp or cmw
3) flash the rom that is given in the OG post here http://forum.xda-developers.com/showthread.php?t=2477180
4) this should now give us the t-mobile version of things and we should be able to do the standard OTA from there?
[Q] So can this all be done without ever having to root the phone?
alternetconcept said:
I've been looking through a few threads and I am not comfortable enough to flash the T-Mobile rom over my AmericanMovil one yet.
I can't seem to find step by step instructions on how to do this.. Would anyone like to explain it from the ground up?
My understanding
1) unlock bootloader
2) flash a recovery like twrp or cmw
3) flash the rom that is given in the OG post here http://forum.xda-developers.com/showthread.php?t=2477180
4) this should now give us the t-mobile version of things and we should be able to do the standard OTA from there?
[Q] So can this all be done without ever having to root the phone?
Click to expand...
Click to collapse
I'm not too sure whether flashing via TWRP/CMW will allow you to get OTA, unfortunately. Which is why I went straight for the Verizon system dump. But yes, you can change firmware without ever having to root the phone. Heck, I think there's a guide on restoring mentioned by @plmiller0905 below that will allow you to do it without unlocking the bootloader, even.
RagnaParadise said:
I'm not too sure whether flashing via TWRP/CMW will allow you to get OTA, unfortunately. Which is why I went straight for the Verizon system dump. But yes, you can change firmware without ever having to root the phone. Heck, I think there's a guide on restoring mentioned by @plmiller0905 below that will allow you to do it without unlocking the bootloader, even.
Click to expand...
Click to collapse
I believe the bootloader does have to be unlocked in order to flash a different firmware.
Sent from my XT1058 using Tapatalk
RagnaParadise said:
I'm not too sure whether flashing via TWRP/CMW will allow you to get OTA, unfortunately. Which is why I went straight for the Verizon system dump. But yes, you can change firmware without ever having to root the phone. Heck, I think there's a guide on restoring mentioned by @plmiller0905 below that will allow you to do it without unlocking the bootloader, even.
Click to expand...
Click to collapse
Yeah after doing so more reading.. (at least the way I'm willing to do it) is to just unlock my bootloader and then using RSD Lite (Which i still have no idea what that is / where it is) flash an SBF found here (http://sbf.droid-developers.org/ghost_rcica/list.php)
I guess following this video somewhat http://www.youtube.com/watch?v=Fr0JHSAXJDI#t=15
Does that sound right?
Should I flash the TMO_RETAIL_XT1053_4.2.2-13.9.0Q2.X-116-X-17-57_MR1_CFC.xml.zip
Or just jump straight to the 4.4 version TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_CFC.xml.zip
??
As far as I know, the use of RSD Lite doesn't require an unlocked bootloader (at least, that's what it shows in the video you showed me anyway), especially since these are images supposedly signed by Motorola themselves. Let me know if you've found something else?
As for your question on which to flash... I'm not sure, but you'd skip a lot of the hassle if you could flash 4.4 straight, so how about trying that?
RagnaParadise said:
As far as I know, the use of RSD Lite doesn't require an unlocked bootloader (at least, that's what it shows in the video you showed me anyway), especially since these are images supposedly signed by Motorola themselves. Let me know if you've found something else?
As for your question on which to flash... I'm not sure, but you'd skip a lot of the hassle if you could flash 4.4 straight, so how about trying that?
Click to expand...
Click to collapse
Rsdlite is a shell for a flash boot flash supposedly with an XML doing all the steps together. Just makes it easier.
You need unlocked boot loader only to flash an image that doesn't match your current boot loader. So if you have a. At&t phone you can only flash at&t images by rsdlite. But if you unlock your amerimovil phone you can flash any xt1058 image I think. So amerimovil could take say a rogers or at&t or telcel image. Not sure if T-Mobile image will work on a full rsdlite flash as it is an xt1053 image. I think you can flash most of a T-Mobile image by twrp but not by rsdlite not sure
sleepyguy007 said:
Rsdlite is a shell for a flash boot flash supposedly with an XML doing all the steps together. Just makes it easier.
You need unlocked boot loader only to flash an image that doesn't match your current boot loader. So if you have a. At&t phone you can only flash at&t images by rsdlite. But if you unlock your amerimovil phone you can flash any xt1058 image I think. So amerimovil could take say a rogers or at&t or telcel image. Not sure if T-Mobile image will work on a full rsdlite flash as it is an xt1053 image. I think you can flash most of a T-Mobile image by twrp but not by rsdlite not sure
Click to expand...
Click to collapse
So if I flash the at&t image found here (http://sbf.droid-developers.org/ghost_rcica/list.php), would it come pre-loaded with all the bloatware AT&T has even though I'm not using AT&T network?
alternetconcept said:
So if I flash the at&t image found here (http://sbf.droid-developers.org/ghost_rcica/list.php), would it come pre-loaded with all the bloatware AT&T has even though I'm not using AT&T network?
Click to expand...
Click to collapse
yes of course. think about it like if you took a dell windows 7 install CD , and put it on an HP. all the dell customizations would still be there.
obviously since you have unlocked bootloader, once you do the RSDlite you can always flash twrp, and superuser, and delete all that stuff. but then you wouldn't get updates again. i dont think the at&t image is really THAT bad. though i've heard the rogers one is better (though maybe not 4.4 yet)
sleepyguy007 said:
yes of course. think about it like if you took a dell windows 7 install CD , and put it on an HP. all the dell customizations would still be there.
obviously since you have unlocked bootloader, once you do the RSDlite you can always flash twrp, and superuser, and delete all that stuff. but then you wouldn't get updates again. i dont think the at&t image is really THAT bad. though i've heard the rogers one is better (though maybe not 4.4 yet)
Click to expand...
Click to collapse
Yeah unfortunately that's what I thought. Hence why I would of liked to flash the t-mobile image but I'm going to hold off until someone that is a bit more adb savvy then myself tries it out. I wouldn't know what to do if I ended up soft bricking my phone
Well it didn't take long to try it out myself...
It worked out!
I used this thread here http://forum.xda-developers.com/showthread.php?t=2446515
I downloaded the Tmobile 4.4 Image and used RSD.
All you have to do is unlock your BL. (Note: I was completely bone stock with NO root and NO special recovery like CMW or TWRP)
Have all the proper drivers installed, enable USB debugging in developer settings on the phone
Go into Fastboot on the phone
Plug in the phone and just follow the video
I do not take any responsibitliy if you brick your phone. It is fairly easy process and took only a few mins.
Hope this helps!
- deleted because I was sleepy enough not to notice that replies were done on the next page -_- -
alternetconcept said:
I've been looking through a few threads and I am not comfortable enough to flash the T-Mobile rom over my AmericanMovil one yet.
I can't seem to find step by step instructions on how to do this.. Would anyone like to explain it from the ground up?
My understanding
1) unlock bootloader
2) flash a recovery like twrp or cmw
3) flash the rom that is given in the OG post here http://forum.xda-developers.com/showthread.php?t=2477180
4) this should now give us the t-mobile version of things and we should be able to do the standard OTA from there?
[Q] So can this all be done without ever having to root the phone?
Click to expand...
Click to collapse
I've been doing some research on this since yesterday and I've been hesitant on doing it. I saw in your last post that you successfully flashed the TMO 4.4 ROM on your AmericaMovil phone, so I have a few questions for you before I go ahead and do the same:
1. Can you please confirm that your model is XT1058 and not XT1053?
2. Does the TMO ROM have the TMO boot logo and any TMO bloatware?
3. Does the TMO ROM have the Tethering & portable hotspot option under Settings > More?
4. Does the TMO ROM have the Mass Storage option under Settings > Storage > | > USB computer connection?
5. Have you been having any radio problems since you flashed the TMO ROM?
I wonder if I install the ROM in here http://forum.xda-developers.com/showthread.php?t=2477180 using RSDLite, would I get the OTA update to 4.4? The reason I want to install this ROM is because it only flashes system and boot.img without flashing bootloader, modem, logo etc... and I know the XT1058 radio is different from the XT1053 radio, so I've been reluctant to flash a full XT1053 ROM on my XT1058 phone.
But what I also would like to know is if an OTA update would flash a full ROM or not. In other words, if I flash the ROM above and then OTA update to 4.4 and the OTA update flashes the full ROM including the radio, I might as well flash the full 4.4 immediately.
What do you or anyone else think?
I'll answer to the best of my ability. heh
mschumacher69 said:
1. Can you please confirm that your model is XT1058 and not XT1053?
Click to expand...
Click to collapse
Mine was an XT1058, and has been flashed to XT1060. (I didn't notice that T-Mo had a 4.4 ROM on the list, so I went straight for the flashable ZIP for Verizon instead. silly me.)
mschumacher69 said:
2. Does the TMO ROM have the TMO boot logo and any TMO bloatware?
Click to expand...
Click to collapse
At least according to this article, the TMO version shouldn't have any bloatware.
mschumacher69 said:
4. Does the TMO ROM have the Mass Storage option under Settings > Storage > | > USB computer connection?
Click to expand...
Click to collapse
There's no reason why there shouldn't be; I'm seeing it on my Verizon version.
mschumacher69 said:
5. Have you been having any radio problems since you flashed the TMO ROM?
Click to expand...
Click to collapse
I can't say for sure if you'll face any problems, but I flashed the T-Mo radio provided here with my Verizon ROM, and I had no problems connecting to my network in Singapore.
--
I can't answer the rest unfortunately. Sorry. Hope I've helped.
RagnaParadise said:
I can't answer the rest unfortunately. Sorry. Hope I've helped.
Click to expand...
Click to collapse
Thank you for your answers!
Regarding Mass Storage, the reason I'm asking is because I don't have it on my AmericaMovil ROM.
The ROM is basically exactly what you get when you buy the T-Mobile version.
I figured the radios are nearly identical from the AT&T version and the T-Mobile version so my XT1058 is running on the XT1053 radios. There is no bloatware. tethering is there but I'm not sure if t-mobile will allow it. There is NO tmobile logo that comes up on boot. USB connect to computer is there.
As for the radio section again.. I was getting only EDGE in my house before I switched to this ROM (Meaning when I was on the ORIGINAL XT1058 image) and I am still getting only EDGE in my house.. Unfortunately I haven't left my house since yesterday flashing the image but when I'll be back at work in NYC and should see '4G/LTE' over there.
We'll see.
alternetconcept said:
The ROM is basically exactly what you get when you buy the T-Mobile version.
I figured the radios are nearly identical from the AT&T version and the T-Mobile version so my XT1058 is running on the XT1053 radios. There is no bloatware. tethering is there but I'm not sure if t-mobile will allow it. There is NO tmobile logo that comes up on boot. USB connect to computer is there.
As for the radio section again.. I was getting only EDGE in my house before I switched to this ROM (Meaning when I was on the ORIGINAL XT1058 image) and I am still getting only EDGE in my house.. Unfortunately I haven't left my house since yesterday flashing the image but when I'll be back at work in NYC and should see '4G/LTE' over there.
We'll see.
Click to expand...
Click to collapse
Thanks for ur reply! Which network are you on right now?
mschumacher69 said:
Thanks for ur reply! Which network are you on right now?
Click to expand...
Click to collapse
I've always been on T-mobile network. Both when i was on original XT1058 AmericanMovil system version and still on T-mobile when I switched the image to XT1053.
Back on my Nexus 4 though.. I would have HSPA+ in my house.. So I thought it was a bit odd that as soon as I received this phone that I wasn't getting anything other than EDGE..

[Q] bootloader for verizon htc one working in EU

Hi
It is possible to flash bootloader for Verizon HTC ONE that goes to standard HTC ONE ? - I will be using the phone in the EU.
After flashing TWRP m7vzw version and instal viper one I got message after system boot that simcard isnt from verizon. I skip that and choose wright carier and everything gooes fine for now.
klujek said:
Hi
It is possible to flash bootloader for Verizon HTC ONE that goes to standard HTC ONE ? - I will be using the phone in the EU.
After flashing TWRP m7vzw version and instal viper one I got message after system boot that simcard isnt from verizon. I skip that and choose wright carier and everything gooes fine for now.
Click to expand...
Click to collapse
it seem that this is not working for now. I flash TWRP 2.7.0.0 m7 version and system can't boot. Go back to the TWRP 2.7.0.8 m7vzw for now and waiting for updates.
klujek said:
Hi
It is possible to flash bootloader for Verizon HTC ONE that goes to standard HTC ONE ? - I will be using the phone in the EU.
After flashing TWRP m7vzw version and instal viper one I got message after system boot that simcard isnt from verizon. I skip that and choose wright carier and everything gooes fine for now.
Click to expand...
Click to collapse
You can't flash a bootloader that is not intended for your phone variant, you will brick it. But wait, you are talking about TWRP which is not the bootloader, its the recovery. You can't neither flash a recovery that is not intended for your phone variant!! Recovery and bootloader version have absolutely nothing to do with the message you got about your sim card.
klujek said:
it seem that this is not working for now. I flash TWRP 2.7.0.0 m7 version and system can't boot. Go back to the TWRP 2.7.0.8 m7vzw for now and waiting for updates.
Click to expand...
Click to collapse
Stop flashing things that are not intended for your M7VZW !!! You will end up messing your partitions. Go read the forums or ask here before doing thing you don't understand.
There also a specific forum for the Verizon Htc one here, you could probably find more precise information for your phone variant.
alray said:
You can't flash a bootloader that is not intended for your phone variant, you will brick it. But wait, you are talking about TWRP which is not the bootloader, its the recovery. You can't neither flash a recovery that is not intended for your phone variant!! Recovery and bootloader version have absolutely nothing to do with the message you got about your sim card.
Stop flashing things that are not intended for your M7VZW !!! You will end up messing your partitions. Go read the forums or ask here before doing thing you don't understand.
There also a specific forum for the Verizon Htc one here, you could probably find more precise information for your phone variant.
Click to expand...
Click to collapse
You are right, my mistake - I mean recovery flash
I was using HTC HD2 on several androids builds before so I get to use with partition mess
All I neet is to get rid of verizon from my toy. Do you think that flashing fimware, radio etc could help ? Something like described here for m7vzw phones http://forum.xda-developers.com/showthread.php?p=46506621 but for m7.

Categories

Resources