I searched for an answer but was unable to locate one for my issue.
This phone was originally VZW, and i'm trying to switch it to T-Mobile.
I have already gained s-off and root with Sunshine.
I wanted to use the VIPER ONE 7.0 ROM, After changing the MID and CID to supercid, I flashed the firmware using this http://forum.xda-developers.com/showthread.php?t=2485651 method sucessfully. I get this information when I,
fastboot getvar all
C:\ADB>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.57
INFOversion-baseband: 4T.28.
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 6.06.401.1
INFOversion-misc: PVT SHIP S
INFOserialno: FA39MS******(I blocked on purpose)
INFOimei: 990004282******(I blocked on purpose)
INFOmeid: 99000428******(I blocked on purpose)
INFOproduct: m7_wlv
INFOplatform: HBOOT-8064
INFOmodelid: PN0713000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 3944mV
INFOpartition-layout: Generi
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: RUU
INFOcommitno-bootloader: dir
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.064s
The ROM was successfully flashed too, but now the phone keeps restarting and when I screen unlock, all I get is the HTC logo, and can see the top bar when i touch it.
Any idea's.
Sorry for any incorrect formatting of this thread or if I left anything out. I am a novice.
Thanks for any help!
Coreopsis said:
I searched for an answer but was unable to locate one for my issue.
This phone was originally VZW, and i'm trying to switch it to T-Mobile.
I wanted to use the VIPER ONE 7.0 ROM, After changing the MID and CID to supercid, I flashed the firmware using this http://forum.xda-developers.com/showthread.php?t=2485651 method sucessfully. I get this information when I,
The ROM was successfully flashed too, but now the phone keeps restarting and when I screen unlock, all I get is the HTC logo, and can see the top bar when i touch it.
Any idea's.
Thanks for any help!
Click to expand...
Click to collapse
1. The Verizon phone is different from the GSM (T-Mobile, AT&T, International GSM) phones. Not only are the radios different but the partitions are different as well.
2. You flashed an Int'l firmware on a Verizon phone with MID for T-Mobile and expected it all to work out. S-OFF means that the security is disabled and it allows you to make the above mistake.
3. It would have been better for you to leave in on the Verizon firmware with MID PN073100, unlock your SIM and install the Verizon version of Viper. You need to change your MID back and install Verizon firmware and then flash the Viper rom for Verizon.
4. You could trade in your Verizon phone for a T-Mobile one and save yourself the grief!
@majmoz
Yikes. I did not know this phone was incompatible between the different carriers. The phone was working with T-Mobile; however, I was only getting 2G speeds.
To be clear:
I cannot achieve my goal to switch the phone entirely to T-Mobile? But, it may work to go back to Verizon firmware/rom/ect, and unlock the Verizon sim card.
The phone has a lot of wear and tear, therefore, I might have a hard time trading it, but I will use that option as last resort.
Thanks for you.
Coreopsis said:
@majmoz
Yikes. I did not know this phone was incompatible between the different carriers. The phone was working with T-Mobile; however, I was only getting 2G speeds.
To be clear:
I cannot achieve my goal to switch the phone entirely to T-Mobile? But, it may work to go back to Verizon firmware/rom/ect, and unlock the Verizon sim card.
The phone has a lot of wear and tear, therefore, I might have a hard time trading it, but I will use that option as last resort.
Thanks for you.
Click to expand...
Click to collapse
I would change my MID back to Verizon and run this RUU it is the latest. RUU will update both the firmware and rom you will be completely stock while still having S-OFF. If it fails, you might have to change the CID to Verizon as well. If you want to put on a custom rom after you could. The 2G speed might be the best you can get on T-Mobile's network because it is running on a different bands within the radio.
@majmoz
Thanks! Your advice fixed my issue.
I had really messed it up. Somehow I had wiped all my zips, TWRP would not work, and in the end I was able to change the MID back to VZW using CWM adb sideload.
Thanks again.
Related
So I've been trying my damnedest for the past week to un-root my HTC One, but I can't seem to make any progress. Unfortunately, I believe I may have flashed the wrong ROM at one point, making my situation much worse. I think the kernel is totally wrong, the CID, and god only knows what else. I never S-OFFed, so I can't imagine i screwed things up too bad, but nevertheless, I have had no luck running a valid RUU in Windows nor gotten fastboot to successfully flash the stock rom zip. I have an AT&T HTC One M7, currently showing the following info:
INFOversion: 0.5
INFOversion-bootloader: 1.54.0000
INFOversion-baseband: 4A.18.3263.15
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.06.1700.10
INFOversion-misc: PVT SHIP S-ON
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0712000
INFOcidnum: CWS__001
INFObattery-status: good
INFObattery-voltage: 4184mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-94cf81a8fd
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
All I want to do is un-root and restore the device entirely back to stock and somehow I've really messed my phone up. Total noob here, appreciating any direction and advice to get my phone back to it's original state. Can anyone help? Thanks in advance!
Move Thread
Would anyone know how I could move this thread to the more general HTC One board (http://forum.xda-developers.com/forumdisplay.php?f=2117)? Since this is not a carrier specific problem and nobody in the AT&T forum seem to know what to do either, it would make sense for more HTC One users to see this as they may have more advice. thanks
When you tried to Flash the stock RUU did you make sure to relock the bootloader first?
RespectTheTech said:
When you tried to Flash the stock RUU did you make sure to relock the bootloader first?
Click to expand...
Click to collapse
yep and I got Error 155 every time, after more than a handful of attempts. I tried troubleshooting the error by reading more than a dozen threads here on xda, but still could not get anything to work.
jinkus said:
yep and I got Error 155 every time, after more than a handful of attempts. I tried troubleshooting the error by reading more than a dozen threads here on xda, but still could not get anything to work.
Click to expand...
Click to collapse
Earlier today I had completely bricked my phone and inadvertently deleted the entire OS so that it wouldn't boot any further than the HTC Logo.
The Forum won't let me post links yet because my lack of posts so I will PM you the links I used to get back to stock.
RespectTheTech said:
Earlier today I had completely bricked my phone and inadvertently deleted the entire OS so that it wouldn't boot any further than the HTC Logo.
The Forum won't let me post links yet because my lack of posts so I will PM you the links I used to get back to stock.
Click to expand...
Click to collapse
That RUU file by DesignGears is one of the few RUU's I've attempted to use, and have gotten Error 155 with. In the video, the guy mentions that while running the RUU, the Image Version for both From and TO should be the same. Mine are not. The From version is 3.06.1700.10 and the To version is 1.26.502.12. So the ROM/kernel on my phone is for the Google Play Edition, yet I do not have a Google Play Edition phone.
If I try using fastboot to flash a 1.26.502.12 AT&T rom.zip file I downloaded, I get this error: usb_write failed with status e00002be
jinkus said:
That RUU file by DesignGears is one of the few RUU's I've attempted to use, and have gotten Error 155 with. In the video, the guy mentions that while running the RUU, the Image Version for both From and TO should be the same. Mine are not. The From version is 3.06.1700.10 and the To version is 1.26.502.12. So the ROM/kernel on my phone is for the Google Play Edition, yet I do not have a Google Play Edition phone.
If I try using fastboot to flash a 1.26.502.12 AT&T rom.zip file I downloaded, I get this error: usb_write failed with status e00002be
Click to expand...
Click to collapse
The Image versions I had didn't match either, but weren't off as far as yours. Mine was From 1.26.502.15 and To 1.26.502.12. So even though he says they have to match, They don't. Wondering if they problem lies with the Goog Edition ROM. Have you tried to clean install any of the AT&T ROM's? Curious if you are able to do that then it should let you Relock the bootloader and then Install the RUU. Hypothetically anyways.
I was running LiquidSmooth after obtaining S-OFF using Revolutionary on my Thunderbolt I had bought online. After a few days the charging port would no longer charge the phone. The device is under warranty so I readied a return and ordered an external battery charger to get the Thunderbolt back to stock.
My external charger showed up in the mail and I fully charged the battery while getting the files required to follow this guide to returned to a relocked bootloader, S-ON, and the "stock" Android. I was able to unroot the phone but after flashing the PG05IMG_no_hboot_2.11.605.19.zip, it returned "Failed-UZ" (or something along those lines, I know it failed to unzip though). After 3-4 retries, it returned the same error.
I decided to use a RUU executable from Shipped-Roms (stupid of me, I was S-OFF) and it failed with "wrong bootloader version". Now I believe I've dug a hole here.
Rather than digging a bit more and "throwing" the phone into it, I figured I'd ask for a bit of help.
--
My goal is to return it to the most stock it could be. Just so I don't get hit the replacement fee. This charging port is a bit finicky but it does work. It just takes a few plugs/unplugs to get it into FASTBOOT USB and recognized by the PC. I've tried using a couple methods to return to some sort of working order and it runs through and gives "Checking . . PG05IMG.zip..." then it just goes right back to HBOOT.
I'm unable to get into the phone and it doesn't help that the phone is old so 9/10 links are dead or lead to useless advertisements. Excuse my frustration as I understand some of what I'm doing. I'm just getting increasingly aggravated at the idea of paying for an out-of-date phone when it's under the seller's warranty.
Code:
*** UNLOCKED ***
MECHA XD SHIP S-ON
HBOOT-1.05.0000
MICROP-/
RADIO-1.48.00.0930w_3
eMMC-boot
Jul 19 2011,14:51:08
Many thanks ahead of time!
- H00k3d0nCr0n1cz / Zero
Can you give me the results of fastboot getvar all
Also you'll need to relock the boot loader in order to run an ruu(.zip or .exe)
Sent from my HTC One using Tapatalk
Thanks for the reply! I appreciate it. I can't seem to find much out between the missing downloads and my experience with this phone!
Let me get this half-working port to connect and I'll post the output ASAP (prolly 10 or so mins tops, it connects when it feels like it).
EDIT, EDIT:
It's all about using an OEM cable . It didn't like my Moto or Sammy cable at all. Here's the output:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.05.0000
(bootloader) version-baseband: 1.48.00.0930w_3
(bootloader) version-cpld: None
(bootloader) version-microp: /
(bootloader) version-main: 7.02.605.10
(bootloader) serialno: HT16TS018000
(bootloader) product: mecha
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG0510000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3678mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-47e85ff5
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
(bootloader) region-id: not support
all: Done!
finished. total time: 0.042s
version-main: 7.02.605.10 < Wouldn't that be ICS? So I'm stuck where the phone is expecting ICS or higher? It'd be unfortunate if I'm bricked due to not having a newer update.
Also, bootloader is relocked.
Anyone?
iamz3r0 said:
Anyone?
Click to expand...
Click to collapse
sorry,apparently i missed a notification of your other response
anyway,yes that is the ICS main version. you will need to install a recovery,then flash the "main version low" zip in recovery. you can then run the GB ruu.
basically you can follow this guide: http://androidforums.com/thunderbolt-all-things-root/689221-how-downgrade-root-ics.html
just skip the part about runing revolutionary im pretty sure the downgrade ruu is a release keys version,meaning you can let the phone OTA to current afterward if you want to.
holler in that thread if you have questions and youll prolly get faster responses from me
scotty1223 said:
sorry,apparently i missed a notification of your other response
anyway,yes that is the ICS main version. you will need to install a recovery,then flash the "main version low" zip in recovery. you can then run the GB ruu.
basically you can follow this guide: http://androidforums.com/thunderbolt-all-things-root/689221-how-downgrade-root-ics.html
just skip the part about runing revolutionary im pretty sure the downgrade ruu is a release keys version,meaning you can let the phone OTA to current afterward if you want to.
holler in that thread if you have questions and youll prolly get faster responses from me
Click to expand...
Click to collapse
Thanks! If you didn't point that out to me I would've spent forever looking around.
I unlocked the bootloader and flashed the recovery .img inside of PG05IMGrecovery-ra-mecha-3.06-gnm.zip with fastboot. Then I booted into recovery and flashed the "main version low" zip from here. After that I was able to relock the bootloader and RUU back to normal.
While everything started up, the phone still doesn't charge.
I'm assuming there isn't a way to get rid of the "relocked" message? I'm not quite sure it matters though. The phone is running software from the manufacturer and the charging port still doesn't work correctly. I'm not quite sure unlocking the bootloader would cause that. :laugh:
iamz3r0 said:
Thanks! If you didn't point that out to me I would've spent forever looking around.
I unlocked the bootloader and flashed the recovery .img inside of PG05IMGrecovery-ra-mecha-3.06-gnm.zip with fastboot. Then I booted into recovery and flashed the "main version low" zip from here. After that I was able to relock the bootloader and RUU back to normal.
While everything started up, the phone still doesn't charge.
I'm assuming there isn't a way to get rid of the "relocked" message? I'm not quite sure it matters though. The phone is running software from the manufacturer and the charging port still doesn't work correctly. I'm not quite sure unlocking the bootloader would cause that. :laugh:
Click to expand...
Click to collapse
Correct,unlocking the bootloader definately cannot cause hardware malfunctions
Unfortunately,with the thunderbolt,relocked is the best you can do. Revolutionary installs a patched hboot,wich gives most of the benefits of a true,radio s off,but does not allow you to write to write-protected partitions. As such,the flag that signals hboot as to wether it is locked,relocked,or unlocked cannot be modified.
I'd say you should fine with warrantying your device with a.malfunctioning charge port.
Sent from my HTC PG09410 using Tapatalk 2
scotty1223 said:
Correct,unlocking the bootloader definately cannot cause hardware malfunctions
Unfortunately,with the thunderbolt,relocked is the best you can do. Revolutionary installs a patched hboot,wich gives most of the benefits of a true,radio s off,but does not allow you to write to write-protected partitions. As such,the flag that signals hboot as to wether it is locked,relocked,or unlocked cannot be modified.
I'd say you should fine with warrantying your device with a.malfunctioning charge port.
Sent from my HTC PG09410 using Tapatalk 2
Click to expand...
Click to collapse
Alright! Time to OTA to ICS and use this half-working TBolt til the replacement arrives.
I still don't miss my DROID3 but I need a newer phone
Thanks again for all your help!
--
EDIT: They accepted the phone with the bootloader relocked. Funny thing was, they were out of Thunderbolts! Instead they're sending me a Galaxy Nexus instead. Gonna go check out that KitKat.
iamz3r0 said:
Alright! Time to OTA to ICS and use this half-working TBolt til the replacement arrives.
I still don't miss my DROID3 but I need a newer phone
Thanks again for all your help!
--
EDIT: They accepted the phone with the bootloader relocked. Funny thing was, they were out of Thunderbolts! Instead they're sending me a Galaxy Nexus instead. Gonna go check out that KitKat.
Click to expand...
Click to collapse
GNex.... isn't that kind of outdated these days?
Couldn't you get something a bit newer, maybe a One X (4G) or a Nexus 4....
At least its not as bad as an iPhone 4S.
Hey all, I know I know, I'm sure someone is going to tell me to search and figure it out, but I have and I cannot. I could REALLY use your help here.
I've used HTC phones since the G1, rooting, flashing, unlocking, etc, and nothing has been as unclear as this.
So here is my request. I need to send my phone back to T-Mobile for warranty replacement (the mic broke). I am rooted, and have the bootloader unlocked via the official HTC method.
Here is what I currently have on my phone.
Rom: ARHD 61.1
Bootloader: 1.55.0000
Baseband: 4A.21.3263.03
Firmware: 3.24.531.3
S-On (I did the rooting and unlocking and such before they had S-Off)
CIDnum: T-MOB010
ModelID: PN0713000
I just need to get back to stock (even if it says relocked or whatever) so I can send this back to them. Every post I've read, every video I've watched, all have directions that are for S-Off, or don't have downloads for what I have if the directions are for S-On. I've dug through the Gurureset stuff and can't seem to make heads or tails of it. Some of it seems to be close, but ends up usually being the 1.29 firmware which will break my touchscreen from what I've read.
Could someone explain what the best way of doing this is? I am willing to PAY you for the help, via paypal or whatever, if that's what it takes. Basically I just need to get back to a factory image/bootloader that can OTA so that if T-Mobile were to inspect it the only thing they'd really see is that it's been relocked.
Thank you so much for the help, I really appreciate it. :angel:
-Danny
I was also s-on and on 1.55. I had to use rumrunner to get s-off, then relock bootloader so that I could use a ruu to get back to bone stock JB.
danielelias90 said:
So here is my request. I need to send my phone back to T-Mobile for warranty replacement (the mic broke). I am rooted, and have the bootloader unlocked via the official HTC method.
CIDnum: T-MOB010
ModelID: PN0713000
Could someone explain what the best way of doing this is? I am willing to PAY you for the help, via paypal or whatever, if that's what it takes. Basically I just need to get back to a factory image/bootloader that can OTA so that if T-Mobile were to inspect it the only thing they'd really see is that it's been relocked.
Thank you so much for the help, I really appreciate it. :angel:
-Danny
Click to expand...
Click to collapse
Follow mike1986's guide on returning to stock. You can use the RUU from this post for Method 2. Good luck and for this method you don't have to be S-Off.
So I'm trying to flash the 1.58.502.1 RUU but I am s-on with an unlocked bootloader. And from the sound of things the only way to relock the bootloader is by going s-off which I don't want to pay $25 to do.
My current software is 1.12.502.8 but the current baseband matches up with the baseband from 1.58.502.1 (1.16.21331931. LA11G_20.31A.4145.02L). Are there any work arounds that you guys can think of, can I just flash the RUU since the basebands match up?
From what I've read it seems you do in fact need to S-OFF to relock the bootlooader.
Here's the thing,if you S-OFF than you won't need to relock the bootlooader to achieve what your looking to do .S-OFF enables you to flash all sorts of variations assuming they are for your specific device.
I will tell you that the $25 spent to have a safe hassle free S-OFF exploit is worth every cent.
You do not need to s-off to relock the bootloader.
"fastboot oem lock" from adb command prompt connection, while in fastboot mode is all you need to do.
Put your recovery back to stock first for safety but RUU should do that for you, better safe than sorry though...
- Sent from a payphone ...
Iconic24 said:
So I'm trying to flash the 1.58.502.1 RUU but I am s-on with an unlocked bootloader. And from the sound of things the only way to relock the bootloader is by going s-off
Click to expand...
Click to collapse
I don't know where you guys are getting this from. S-off is in no way required to relock the bootloader.
Further, s-off is not required to run an RUU (another common misconception, that I don't know where people get); unless you are trying to "break the rules" and either run an older RUU ("downgrade") or run another carrier's RUU.
Iconic24 said:
My current software is 1.12.502.8 but the current baseband matches up with the baseband from 1.58.502.1 (1.16.21331931. LA11G_20.31A.4145.02L). Are there any work arounds that you guys can think of, can I just flash the RUU since the basebands match up?
Click to expand...
Click to collapse
As long as you are using an AT&T RUU, you can run an RUU for any version number that is equal to or greater than the main version on the phone. The only thing you can't do is run an older RUU ("downgrade") with s-on.
But since you are on the oldest AT&T version (1.12) and there is no 1.12 RUU anyway; you can therefore run any AT&T RUU. This includes 1.58, 2.23, and any new RUUs that come in the future.
ruu
Oh my, I know this is necro thread but it is the closest to what I am trying to achieve and google search led me to it. So if I am on SkyDragon GPE 4.4.4 flashed on top of Stock Sense 4.4.2, hboot 3.16, tampered, unlocked, rooted, s-on there is no problem for me to go RUU and update to 5.x.x? However, shall I use RUU for 4.4.4 or 4.4..2? Thanks if anyone replies
?
i am thinking of just using a toolkit to root and unlock the bootloader but before i do that i gotta ask is it worth it ?
xCellHD said:
i am thinking of just using a toolkit to root and unlock the bootloader but before i do that i gotta ask is it worth it ?
Click to expand...
Click to collapse
Is it worth it to unlock the bootloader? That question is impossible to answer without knowing your individual desires, preferences and what you want from the device.
I gave an answer to a similar question a few days ago: http://forum.xda-developers.com/htc-one-m8/help/to-root-to-root-t3102598
If you are asking "is using a toolkit worthwhile"; I would say NO. The toolkits are not up to date, and therefore install obsolete versions of TWRP (which causes issues) and I personally recommend to do the steps "manually" as its not very hard, ande also a good learning experience that will yield better results.
My personal opinion, ditch the toolkits.
---------- Post added at 10:28 AM ---------- Previous post was at 10:22 AM ----------
innocencex said:
Oh my, I know this is necro thread but it is the closest to what I am trying to achieve and google search led me to it. So if I am on SkyDragon GPE 4.4.4 flashed on top of Stock Sense 4.4.2, hboot 3.16, tampered, unlocked, rooted, s-on there is no problem for me to go RUU and update to 5.x.x?
Click to expand...
Click to collapse
It sounds like you just flashed the GPE ROM, and did not "fully convert" to GPE with the RUU. You can confirm this by booting into hboot, if the hboot screen is white, its still the Sense hboot. GPE hboot is black.
Assuming you just flashed a GPE ROM, you can just RUU to current Sense RUU (5.0). You will need to relock the bootloader to RUU, since you are s-on.
innocencex said:
shall I use RUU for 4.4.4 or 4.4..2?
Click to expand...
Click to collapse
Just run the 5.0 RUU. No need to run intermediate RUUs or run them sequentially. OTAs need to be installed in sequence. RUUs do not.
redpoint73 said:
Is it worth it to unlock the bootloader? That question is impossible to answer without knowing your individual desires, preferences and what you want from the device.
I gave an answer to a similar question a few days ago: http://forum.xda-developers.com/htc-one-m8/help/to-root-to-root-t3102598
If you are asking "is using a toolkit worthwhile"; I would say NO. The toolkits are not up to date, and therefore install obsolete versions of TWRP (which causes issues) and I personally recommend to do the steps "manually" as its not very hard, ande also a good learning experience that will yield better results.
My personal opinion, ditch the toolkits.
---------- Post added at 10:28 AM ---------- Previous post was at 10:22 AM ----------
It sounds like you just flashed the GPE ROM, and did not "fully convert" to GPE with the RUU. You can confirm this by booting into hboot, if the hboot screen is white, its still the Sense hboot. GPE hboot is black.
Assuming you just flashed a GPE ROM, you can just RUU to current Sense RUU (5.0). You will need to relock the bootloader to RUU, since you are s-on.
Just run the 5.0 RUU. No need to run intermediate RUUs or run them sequentially. OTAs need to be installed in sequence. RUUs do not.
Click to expand...
Click to collapse
Sir I'm using GPe ROM to my HTC m8..it's S-ON "Unlocked" I can't unlock my bootloader.
Prvrt said:
Sir I'm using GPe ROM to my HTC m8..it's S-ON "Unlocked" I can't unlock my bootloader.
Click to expand...
Click to collapse
If it says UNLOCKED in bootloader, that means the bootloader is already unlocked.
Or are you trying to relock your bootloader?
It's not clear exactly what you are trying to do, or what steps you've already taken. I know you're new to the forum, so please try to provide as much detail as possible when asking for help. If youknow how, do fastboot getvar all, and post the result (delete IMEI and serial number before posting).
redpoint73 said:
If it says UNLOCKED in bootloader, that means the bootloader is already unlocked.
Or are you trying to relock your bootloader?
It's not clear exactly what you are trying to do, or what steps you've already taken. I know you're new to the forum, so please try to provide as much detail as possible when asking for help. If youknow how, do fastboot getvar all, and post the result (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
Im trying to root my phone again and unlock the bootloader..but i cant access when my phone is in Hboot my phone cant read on my laptop..and after i open it connect but my USB debugging is in "charging only" and i put it back again in MTP and after i put it in Hboot it disconnect again.. idont know if my laptop or my debugging mode
Prvrt said:
Im trying to root my phone again and unlock the bootloader..but i cant access when my phone is in Hboot my phone cant read on my laptop..and after i open it connect but my USB debugging is in "charging only" and i put it back again in MTP and after i put it in Hboot it disconnect again.. idont know if my laptop or my debugging mode
Click to expand...
Click to collapse
You do not need to unlock the bootloader if it says "UNLOCKED" near the top of the screen in bootloader. This specifically means the bootloader is already unlocked.
However, you will (somewhat obviously) need fastboot working if you want to flash TWRP via fastboot. There other means to install TWRP, since you also have working OS (TWRP app for instance). However, working fastboot is really valuable (possibly even critical in some situations) when modding the phone, so my recommendation would be to troubleshoot the problem, and have fastboot working (even despite the existence of "workaround" methods to install TWRP).
You actually do not need debugging enabled to use fastboot (only for adb, which is related to fastboot by there are distinct differences - so try to keep that in mind). Although having debugging enabled would not hurt anything (and obviously you will need it, if you want to use adb).
Another thing to note, the MTP connection mode selected in OS (charge only, file transfer, etc.) has not bearing once you are no longer in OS (when in bootloader) and fastboot will work regardless of whether there is even a working OS.
Fastboot connectivity issues are most usually on the PC side. Try a different USB port, different cable, re-install HTC Sync and HTC drivers. You can also try going into Windows Device Manager, finding the phone, then pick the option to manually select drivers, and select the "generic" Android MTP drivers. I often have to do this to make my PC "see" the M8 on fastboot/adb.
redpoint73 said:
You do not need to unlock the bootloader if it says "UNLOCKED" near the top of the screen in bootloader. This specifically means the bootloader is already unlocked.
However, you will (somewhat obviously) need fastboot working if you want to flash TWRP via fastboot. There other means to install TWRP, since you also have working OS (TWRP app for instance). However, working fastboot is really valuable (possibly even critical in some situations) when modding the phone, so my recommendation would be to troubleshoot the problem, and have fastboot working (even despite the existence of "workaround" methods to install TWRP).
You actually do not need debugging enabled to use fastboot (only for adb, which is related to fastboot by there are distinct differences - so try to keep that in mind). Although having debugging enabled would not hurt anything (and obviously you will need it, if you want to use adb).
Another thing to note, the MTP connection mode selected in OS (charge only, file transfer, etc.) has not bearing once you are no longer in OS (when in bootloader) and fastboot will work regardless of whether there is even a working OS.
Fastboot connectivity issues are most usually on the PC side. Try a different USB port, different cable, re-install HTC Sync and HTC drivers. You can also try going into Windows Device Manager, finding the phone, then pick the option to manually select drivers, and select the "generic" Android MTP drivers. I often have to do this to make my PC "see" the M8 on fastboot/adb.
Click to expand...
Click to collapse
I try on cmd my phone response. I type unlocktoken it works and after I type unlock code bin it success too but my phone didn't show the logo of unlock code and didn't reboot. But in my cmd it says successfully
Prvrt said:
I try on cmd my phone response. I type unlocktoken it works and after I type unlock code bin it success too but my phone didn't show the logo of unlock code and didn't reboot. But in my cmd it says successfully
Click to expand...
Click to collapse
You previously indicated UNLOCKED. Does it say UNLOCKED near the top of the bootloader screen?
Also, please refrain from quoting my whole entire post; as it clutters up the thread. I know it's the default when responding. But just leave in what is directly relevant to your response, and delete the rest.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.502.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT45SWM06618
(bootloader) imei: XXXXXXXXXXXXXXX ( Deleted)
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.125s
Bootloader - Unlocked
Recovery - TWRP
Rooted - Yes
Custom ROM - Resurrection Remis 5.8.5 Final
if want to go back to stock what is procedure
i have below RUU
RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502. 5_combined.exe
can i run this exe after relock the bootloader?
hotspot problem
i'm using htc one m9 at&t in india. i'm unable to turn on hotspot or bluetooth tethering. i heard a solution that i need to unlock bootloader and install cutome rom or edit some line in sql editor. so my question which is the safest method? could anyone please tell me the answer:crying:
Ashok_gajjala said:
i'm using htc one m9 at&t in india. i'm unable to turn on hotspot or bluetooth tethering. i heard a solution that i need to unlock bootloader and install cutome rom or edit some line in sql editor. so my question which is the safest method? could anyone please tell me the answer:crying:
Click to expand...
Click to collapse
This forum section is for the M8, not the M9. Anything we say here about the M8, may or may not be correct for the M9.
have a simple question I'm on firmware 3.16.617.2 there is update 3.16.617.3 if I am s-on unlocked Bootloader and attempt to flash RUU advance to 3.16.617.3 from earlier .2 will this relock my Bootloader ? as I don't want to relock it again my goal is to stall unlocked S-on .
Hello!
So I recently replaced my stolen AT&T HTC M8 with an a refurbished one and decided to root it for my first time. Unfortunately, I fell into the common mistake of using the outdated Hasoon2000 All-in-one toolkit. I'm not well-knowledged in phones, but I definitely want to learn (which is why I am here). I know I should've been more cautious and prepared prior, but all I can do is learn and move forward now. I've spent a few hours researching and trying to understand the process, but there is a lot of technical aspects that I haven't grasped yet. Well, here is my situation:
My phone is currently soft bricked and I am unable to access my phone's UI when I boot it. After the HTC One logo, the phone will be black and consistently bring up, "unfortunately AT&T ready2go has stopped". It will also say that the UI has stopped and I have no choice but to turn off my phone. Prior to this, I had an issue with Superuser where there was no binary so I tried to re-install it thinking that would do something; I then performed a factory reset (thinking it would somehow fix it). I realized after this that TWRP and SU were both out of date and now I'm here not sure what to do. I would like to be able to flash the RUU to revert back to stock and go through the rooting process manually but I haven't had much luck with the .exe file so far; do I need to have S-OFF and/or relock my bootloader? If so, how do I do that? I'm still learning, and it's a lot to pick up, so bear with me please as I try to piece together everything. I've been searching through the forums, but it hasn't really helped me too much.
Here is what my Hboot says:
*** Software Status: Modified ***
M8_UL_CA PVT SSHIP S-ON
HBOOT-3.19.0.0000
[email protected]
OpenDSP-v47.2.2-00564-M8974_F0.1024
OS-
eMMC-boot 2048MB
AUG 4 2015, 23:21:05.0
Getvar All (not exactly sure what this is, but I saw other help posts listing it and figured it's useful)
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
If anyone could give me some guidance/clarity then I would truly appreciate it! Thank you!
mtruong15 said:
Unfortunately, I fell into the common mistake of using the outdated Hasoon2000 All-in-one toolkit. I'm not well-knowledged in phones, but I definitely want to learn (which is why I am here). I know I should've been more cautious and prepared prior, but all I can do is learn and move forward now.
Click to expand...
Click to collapse
Were you on stock Lollipop or Marshmallow before you started modding the phone? From the radio number, I think its LP, but I'm not that familiar with the weird AT&T radio numbers (and how they correspond to LP, MM, etc.). It would be easy to see your main version, if you had not used an obsolete TWRP (from the toolkit) that deletes that info.
One piece of advice moving forward, and this goes for modding any Android device, is to always research the current methods based on your current Android version, firmware, etc.; and confirm the methods work for your setup, before you begin.
At least you've realized your mistake (outdated toolkit, outdated TWRP, outdated SuperSU), and also properly posted your getvar data. So you're not doing a bad job in that respect.
Also, did you make a TWRP backup before trying to root? If not, this is a basic step that is too frequently skipped by newer users. Having a backup of your stock (pre-root attempt) ROM would have given you an easy way to revert to a working OS.
---------- Post added at 09:44 AM ---------- Previous post was at 09:36 AM ----------
mtruong15 said:
I would like to be able to flash the RUU to revert back to stock and go through the rooting process manually but I haven't had much luck with the .exe file so far; do I need to have S-OFF and/or relock my bootloader? If so, how do I do that?
Click to expand...
Click to collapse
Do not need to s-off to run RUU.
But you do need to relock the bootloader, with fastboot command: fastboot oem lock
The RUU version will depend somewhat on your main version (Android version) which I asked above. I can give info, once you've answered that question.
After RUU back to stock, you'll need to unlock the bootloader again (try the same unlock bin code, or get another from HTCDev.com) in order to install TWRP, root, etc.
redpoint73 said:
Were you on stock Lollipop or Marshmallow before you started modding the phone?
Click to expand...
Click to collapse
I was on stock Lollipop when I received my phone.
redpoint73 said:
Also, did you make a TWRP backup before trying to root? If not, this is a basic step that is too frequently skipped by newer users. Having a backup of your stock (pre-root attempt) ROM would have given you an easy way to revert to a working OS.
Click to expand...
Click to collapse
I unfortunately did not, but will do this from now on. I've definitely learned a lot about the process, after the fact, and feel much more prepared to work on this phone. In the case that I need to do this on another phone I will do my research and take the appropriate steps as well.
redpoint said:
The RUU version will depend somewhat on your main version (Android version) which I asked above. I can give info, once you've answered that question.
Click to expand...
Click to collapse
From my understanding, the RUU version needs to be the same or above the previous. This is the only part that confuses me because I felt that I had everything right to run the RUU. What do you think is a potential reason for this specific case?
Update: I have already relocked bootloader
mtruong15 said:
From my understanding, the RUU version needs to be the same or above the previous. This is the only part that confuses me because I felt that I had everything right to run the RUU.
Click to expand...
Click to collapse
Its correct, with s-on, you need to run RUU that is equal or greater version number than the firmware on the phone (in addition to the RUU for your CID,MID so the RUU meant for AT&T M8). Meaning you can't "downgrade" or run the KitKat RUUs (only way to bypass with is with s-off, which is $25 by sunshine). Since you are on LP firmware, you can run the LP RUU.
There is another complication, in that you cannot run the Marshmallow AT&T RUU, unless you flash the MM firmware.zip separately first. Otherwise, the MM will fail with Error 155 if you try to flash from LP or KK. This is a new requirement with MM RUUs.
Link to details on how to flash the firmware.zip (if you want to RUU to MM) is in my Index thread, as well as all the AT&T RUUs (in the RUUs section): http://forum.xda-developers.com/showthread.php?t=2751432
redpoint73 said:
There is another complication, in that you cannot run the Marshmallow AT&T RUU, unless you flash the MM firmware.zip separately first. Otherwise, the MM will fail with Error 155 if you try to flash from LP or KK. This is a new requirement with MM RUUs.
Click to expand...
Click to collapse
I was able to successfully flash the MM firmware as referred to in the post and now it shows the OS number in my Hboot. However, when I used the MM .exe file (RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined), I am still running into the same issue. I see the first Install Wizard pop-up and then it disappears before I even get to the Terms and Conditions page. I feel that I have all the necessary steps now, but I can't seem to figure it out. I also haven't been able to find a .zip file of the update to manually run the RUU. Any ideas on what my options are?
mtruong15 said:
I was able to successfully flash the MM firmware as referred to in the post and now it shows the OS number in my Hboot. However, when I used the MM .exe file (RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined), I am still running into the same issue. I see the first Install Wizard pop-up and then it disappears before I even get to the Terms and Conditions page. I feel that I have all the necessary steps now, but I can't seem to figure it out. I also haven't been able to find a .zip file of the update to manually run the RUU. Any ideas on what my options are?
Click to expand...
Click to collapse
Just let it sit there after the first pop up, it does some background process and then the wizard starts , some times it takes more then 5 minutes, depends on your computer.
Sent from my HTC One_M8 using Tapatalk
grigoriisi said:
Just let it sit there after the first pop up, it does some background process and then the wizard starts , some times it takes more then 5 minutes, depends on your computer.
Click to expand...
Click to collapse
I waited for about 30 minutes and kept an eye on the process on task manager. The set-up application exited about a minute after the first loading screen passed and nothing happened afterward. I had tested out a Lollipop RUU from HTC and was able to immediately get to the Terms and Agreements page after the loading screen; however, after accepting it, the install wizard also shut down and did not give me any further screens/pop-ups. My computers is running on Windows 10 right now; would that possibly be a reason why I can't proceed further?
mtruong15 said:
I waited for about 30 minutes and kept an eye on the process on task manager. The set-up application exited about a minute after the first loading screen passed and nothing happened afterward. I had tested out a Lollipop RUU from HTC and was able to immediately get to the Terms and Agreements page after the loading screen; however, after accepting it, the install wizard also shut down and did not give me any further screens/pop-ups. My computers is running on Windows 10 right now; would that possibly be a reason why I can't proceed further?
Click to expand...
Click to collapse
Right click on the ruu exe and choose compatibility mode windows 7. It works like that for me on Windows 10.
Sent from my HTC One_M8 using Tapatalk
mtruong15 said:
However, when I used the MM .exe file (RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined), I am still running into the same issue. I see the first Install Wizard pop-up and then it disappears before I even get to the Terms and Conditions page.
Click to expand...
Click to collapse
You didn't properly describe that issue before (all you said was "haven't had much luck" with the RUU, which didn't really tell us anything), otherwise I could have given some insight earlier. Always be specific as possible when describing errors, failures, issues.
RUU can be very finicky with PC configuration. Win7 and USB2.0 have the best luck with compatibility. You can try compatibility mode, as the previous response indicated. Also try a different USB port. Also check if your PC has C++ 2008 Package installed, and if not, install it: https://www.microsoft.com/en-us/download/details.aspx?id=29
But if these still don't help, you may need to try a different PC, if possible.
redpoint73 said:
RUU can be very finicky with PC configuration. Win7 and USB2.0 have the best luck with compatibility. You can try compatibility mode, as the previous response indicated. Also try a different USB port. Also check if your PC has C++ 2008 Package installed, and if not, install it: https://www.microsoft.com/en-us/download/details.aspx?id=29
But if these still don't help, you may need to try a different PC, if possible.
Click to expand...
Click to collapse
I tried compatibility mode for Win7 and Win8, and attempted through various USB ports, but still couldn't get it to budge. I double checked the C++ Packages and already had the 2008 package and the others listed in another XDA post I found. I ended up trying on a friend's computer who was running Win8.1 and surprisingly got it to work in one go without any errors at all. Figures the problem was my computer that didn't allow me to run the .exe.
Thanks for your patience and guidance; I really do appreciate you helping me out. I was ready to throw in the towel a few days ago, but was able to get everything to work with your help.
mtruong15 said:
Thanks for your patience and guidance; I really do appreciate you helping me out. I was ready to throw in the towel a few days ago, but was able to get everything to work with your help.
Click to expand...
Click to collapse
You are very welcome, and glad to see you go the RUU to work.
If you still want to root, it looks like you've learned from your mistakes; but to summarize the proper root method:
1) Unlock bootloader again via HTCDev.com. If you still have the bin code from last time, you might be able to reuse it, with the proper fastboot command, to unlock the bootloader. Otherwise, just go through the HTCDev.com process again, and get a new code.
2) Install current TWRP 3.0. TWRP files, and instructions to install by fastboot method are here: https://twrp.me/devices/htconem8gsm.html
3) Download and flash SuperSU in TWRP. Recommend latest stable version SupersSU 2.76: https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip