Hello friends, recently got an M8 Att, its already S-Off, BL Unlocked, Tried CIDs BS_US001, BS_US002 and Super CID 11111111 tried to install UL/DEV Ruu from HTC dev site but alwasys got error 155.
Any suggestion or what am i doing wrong? Thanks in advance.
My getvar:
(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: 4.28.502.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT4xxxxxxxxxxx
(bootloader) imei: 35xxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Which RUU are you trying to flash? If it's the Sense 7/ Marshmallow RUU then you need to first flash 6.x firmware. I found the same exact version as in the name of the RUU and flashed that first then the RUU flashed without a problem.
Sent from my Nexus 5 using Tapatalk
Hey thanks for your reply, yep I'm trying to flash marshmallow ruu because is the only one I found, where can I found such 6.X firmware? Or how can get it?
firultd said:
Hey thanks for your reply, yep I'm trying to flash marshmallow ruu because is the only one I found, where can I found such 6.X firmware? Or how can get it?
Click to expand...
Click to collapse
Search Google for 6.12.1540.4 firmware. I used the one in the first result uploaded by Einwod.
Flash that via fastboot oem rebootRUU.
Twice. It will fail the first time, wait about a minute for the bootloader to reload and flash it again. Don't unplug your phone at all. Once you successfully flash the firmware, do fastboot reboot-bootloader to get back into fastboot, then you should be able to flash the RUU
Sent from my Nexus 5 using Tapatalk
What happens in case of any ruu installation error? phone won't boot right? Can flash att stock run to recover device? Don't wanna end with a brick
Which error? Are you familiar with fastboot at all? And HTC oem commands? I take no responsibility for your flashing but what I posted worked fine for me.
Sent from my Nexus 5 using Tapatalk
firultd said:
What happens in case of any ruu installation error? phone won't boot right? Can flash att stock run to recover device? Don't wanna end with a brick
Click to expand...
Click to collapse
Depends on the error. If the RUU errors out before it actually installs anything, your phone will probably boot normally. But if it partially installs, then an error, it may be a no-boot situation.
Yes, in most cases if your phone won't boot after an RUU error, going back to the AT&T RUU should get your phone working again. But if you actually were successful in updating (even partially) to MM firmware, you may need to flash LP firmware before the LP RUU will work.
Not sure why, but it seems to be a glitch with the MM RUU. To go from LP>MM you need to flash the MM firmware, then RUU. And MM>LP the vice versa is also true, you may need to flash LP firmware in order for the LP RUU to work properly.
Yes i personally do boot loader unlock s -off and all that stuff. Don't worry I know that all responsibility is mine. I mean if after flashing firmware ruu still give an error obviously device will not but isn't it? In that case I still can flash att 5.0 stock ruu?
redpoint73 said:
Depends on the error. If the RUU errors out before it actually installs anything, your phone will probably boot normally. But if it partially installs, then an error, it may be a no-boot situation.
Yes, in most cases if your phone won't boot after an RUU error, going back to the AT&T RUU should get your phone working again. But if you actually were successful in updating (even partially) to MM firmware, you may need to flash LP firmware before the LP RUU will work.
Not sure why, but it seems to be a glitch with the MM RUU. To go from LP>MM you need to flash the MM firmware, then RUU. And MM>LP the vice versa is also true, you may need to flash LP firmware in order for the LP RUU to work properly.
Click to expand...
Click to collapse
OK. Very clear explanation that's give me a better look of the situation. Will keep in mind and try. Thank s a lot.
So now that i have a real keyboard in front of me....
I had very similar issue as you just two days ago where I have an AT&T Branded M8 that is S-Off and had an unlocked bootloader and superCID and I was not able to flash any RUU besides the AT&T one. Although I didn't investigate a lot into why the other Dev RUUs (earlier versions) didn't flash, I was beating my head against the wall trying to get the newest Marshmallow Dev RUU to flash.
Since you are trying to flash an HTC rom, which is signed by HTC the zip in the RUU has to be decrypted with the correct key from HTC. I believe (I'm not an expert on this) the key is embedded into HBOOT. HTC changed the encryption key sometime ago so when you use a firmware that preceeds the key change, the HBOOT will not be able to decrypt the rom.zip file and it fails.
By flashing the firmware I mentioned earlier, it has the correct key to decrypt the zip in the RUU and flash it.
The steps that I followed to get my phone converted are below. The only assumption I am making is that you are able to get into fastboot mode and you have a working knowledge of fastboot commands on a Windows PC.
1. Boot phone into fastboot mode
2. PC command: fastboot oem rebootRUU (Puts the phone into HTC RUU mode)
3. PC command: fastboot flash zip firmware-6.12.1540.4.zip (Flashes the firmware onto the phone)
4. The above command will fail with: FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Wait about a minute then...
5. PC command: fastboot flash zip firmware-6.12.1540.4.zip (Flashes the firmware onto the phone again)
6. PC command: fastboot reboot-bootloader (Restarts the bootloader)
7. At this point your phone should be ready to accept the Dev RUU RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe
8. Launch the RUU on the PC and follow the steps in the RUU Instructions to flash the phone.
9. After it successfully flashes the RUU it will reboot the phone and start optimizing the apps...and then it should drop you into the Welcome screen.
Now, the bricking your phone bit....You can read this thread about the errors you can get and how dangerous they are.
psychephylax said:
So now that i have a real keyboard in front of me....
I had very similar issue as you just two days ago where I have an AT&T Branded M8 that is S-Off and had an unlocked bootloader and superCID and I was not able to flash any RUU besides the AT&T one. Although I didn't investigate a lot into why the other Dev RUUs (earlier versions) didn't flash, I was beating my head against the wall trying to get the newest Marshmallow Dev RUU to flash.
Since you are trying to flash an HTC rom, which is signed by HTC the zip in the RUU has to be decrypted with the correct key from HTC. I believe (I'm not an expert on this) the key is embedded into HBOOT. HTC changed the encryption key sometime ago so when you use a firmware that preceeds the key change, the HBOOT will not be able to decrypt the rom.zip file and it fails.
By flashing the firmware I mentioned earlier, it has the correct key to decrypt the zip in the RUU and flash it.
The steps that I followed to get my phone converted are below. The only assumption I am making is that you are able to get into fastboot mode and you have a working knowledge of fastboot commands on a Windows PC.
1. Boot phone into fastboot mode
2. PC command: fastboot oem rebootRUU (Puts the phone into HTC RUU mode)
3. PC command: fastboot flash zip firmware-6.12.1540.4.zip (Flashes the firmware onto the phone)
4. The above command will fail with: FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Wait about a minute then...
5. PC command: fastboot flash zip firmware-6.12.1540.4.zip (Flashes the firmware onto the phone again)
6. PC command: fastboot reboot-bootloader (Restarts the bootloader)
7. At this point your phone should be ready to accept the Dev RUU RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe
8. Launch the RUU on the PC and follow the steps in the RUU Instructions to flash the phone.
9. After it successfully flashes the RUU it will reboot the phone and start optimizing the apps...and then it should drop you into the Welcome screen.
Now, the bricking your phone bit....You can read this thread about the errors you can get and how dangerous they are.
Click to expand...
Click to collapse
Well, lets do it, just give me some hours to backup and will try and post results, again thanks for your time.
A tiny question before proceed, firmware zip file is 30.88 MB size? Its the right one? feel like its too small
firultd said:
A tiny question before proceed, firmware zip file is 30.88 MB size? Its the right one? feel like its too small
Click to expand...
Click to collapse
Yeah, it's about 30mb (31626 KB)
Here's the md5 sum from my file: b5add816536334711fb2baa6e8a4d134
HAve no words to describe the happines to see my phone just like a real dev edition, many thanks to all of you for your time. Whole process was right and phone is working awesome.
Glad you got it working.
Sent from my Redmi Note 2 using Tapatalk
firultd said:
A tiny question before proceed, firmware zip file is 30.88 MB size? Its the right one? feel like its too small
Click to expand...
Click to collapse
Note that firmware.zip only contains a subset of partitions including hboot, radio, kernel, recovery, WiFi, Bluetooth, Audio and a few others. It doesn't contain the ROM, which is a much larger file (1.5 GB or so); nor is it a full RUU or ROM.zip, etc.
Firmware is important, but not a large file.
Any harm in flashing the 6.12.1540.4 but staying on Lollipop?
I don't know, but why would you want to stay on lollipop?
Sent from my Redmi Note 2 using Tapatalk
Related
Rezound FAILED (remote: not allowed)
I received this phone and it would boot to just the HTC screen. It will boot to the bootloader screen and I can access it with fastboot.
The filesystem seems to be locked down and I don't know how to unlock it. ADB won't work since it won't boot the OS. It also wouldn't boot into the stock recovery. When I try to boot into Amon Ra recovery, it shows the progress bar on the upper right side of the screen but then goes on into a boot loop. So parts of Amon Ra are being installed and working but not much.
At first it would boot to the HTC screen and sit there. I installed 605.2 via the PH98IMG.zip on SD method and it went along fine.
Now it just gets to the HTC screen and reboots like it has no or the wrong kernel. I unlocked the bootloader, flashed amon ra and it won't boot into recovery either. I tried to erase several things, it will only let me erase "cache" not "boot", "recovery" or "system. So I'm stuck until I find out how to allow writing to these areas of the system. It also doesn't read the files in light green in boot loader mode like it should.
I think if I can get s-off I can write over what I want, but I don't know how to downgrade or where to find the files. I tried RUU_Vigor_3.14.605.10_PH98IMG but that didn't help, it just gave me an error for trying to downgrade.
I am sure if I can get access to the complete file system I can get this thing going.
C:\ADB>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.27.0000
(bootloader) version-baseband: 2.22.10.0801r/2.22.10.0803r
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.03.605.2
(bootloader) serialno: FA28YS208261
(bootloader) imei: 990000652356066
(bootloader) product: vigor
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH9810000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3861mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ad3368f2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I received this phone and it would boot to just the HTC screen. It will boot to the bootloader screen and I can access it with fastboot.
The filesystem seems to be locked down and I don't know how to unlock it. ADB won't work since it won't boot the OS. It also wouldn't boot into the stock recovery. When I try to boot into Amon Ra recovery, it shows the progress bar on the upper right side of the screen but then goes on into a boot loop. So parts of Amon Ra are being installed and working but not much.
At first it would boot to the HTC screen and sit there. I installed 605.2 via the PH98IMG.zip on SD method and it went along fine.
Now it just gets to the HTC screen and reboots like it has no or the wrong kernel. I unlocked the bootloader, flashed amon ra and it won't boot into recovery either. I tried to erase several things, it will only let me erase "cache" not "boot", "recovery" or "system. So I'm stuck until I find out how to allow writing to these areas of the system. It also doesn't read the files in light green in boot loader mode like it should.
I think if I can get s-off I can write over what I want, but I don't know how to downgrade or where to find the files. I tried RUU_Vigor_3.14.605.10_PH98IMG but that didn't help, it just gave me an error for trying to downgrade.
I am sure if I can get access to the complete file system I can get this thing going.
C:\ADB>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.27.0000
(bootloader) version-baseband: 2.22.10.0801r/2.22.10.0803r
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.03.605.2
(bootloader) serialno: FA28YS208261
(bootloader) imei: 990000652356066
(bootloader) product: vigor
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH9810000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3861mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ad3368f2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
So what exactly happens when you try to run the 4.03.605.2 RUU again? Make sure your locked if your s-on trying to run the RUU. When you tried running it the first time. Did you let it run twice?
Relocked and re-RUU
Flyhalf205 said:
So what exactly happens when you try to run the 4.03.605.2 RUU again? Make sure your locked if your s-on trying to run the RUU.
Click to expand...
Click to collapse
First when relocking I get:
C:\ADB>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 134086008 (0x7FDFD78)
FAILED (status read failed (Too many links))
finished. total time: 0.936s
I boot to bootloader and get "TAMPERED" "RELOCKED". So according to the boot loader I am unlocking and relocking successfuly and it thinks that Amon RA is installed. Amon RA does not get written by the RUU it seems. If the stock recovery was written it would not say "TAMPERED".
I can access the device with fastboot but "boot", "system", "recovery are locked". I tried the wire trick for s-off, but the program fails at "testing "ADB" because the phone never gets that far, booting into OS.
I just tried rerunning the 605.2 RUU and it went through all of the steps. I may have attempted a downgrade and it seems to downgrade some things then when i go back to 605.2 it does the whole upgrade again. I'll try the 605.2 RUU upgrade twice to see if it makes any difference. This is my 5th Rezound I've tried to upgrade to 605.2 so I know to wait for it to do all of its thing. Maybe someone earlier aborted an upgrade and hosed it. Is the area with the boot, system, recovery removeable. If so, I'd replace the internal SD. For a while I was also getting a "security warning" just below "RELOCKED".
On the initial update phase it checks the image, then reboots and gives me a list of 18 things to upgrade and the option to proceed. I click vol up and it proceeds through the list "unzipping", "updating", "OK". No errors. It takes a while to update "system" which tells me it is doing something. Ends with "Update Complete". I also tried flashing the zip from a pc with fastboot. The screen on the phone thurned black with a HTC on it and the flash seemed to run a while but no good.I also tried flashing boot.img and Amon Ra. When trying to boot into recovery from the bootloader menu the progress bar on the right side moves up as normal with Amon RA but when it reboots it just does a boot loop like it does when trying to boot the OS. On the second and subsequent boots while holding vol down and power, it re-upgrades. So it seems that the system can't write to those areas and therefore keeps trying on subsequent tries. I don't understand why it says OK after each item updated if the updates are failing.
jcampolo said:
First when relocking I get:
C:\ADB>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 134086008 (0x7FDFD78)
FAILED (status read failed (Too many links))
finished. total time: 0.936s
I boot to bootloader and get "TAMPERED" "RELOCKED". So according to the boot loader I am unlocking and relocking successfuly and it thinks that Amon RA is installed. Amon RA does not get written by the RUU it seems. If the stock recovery was written it would not say "TAMPERED".
I can access the device with fastboot but "boot", "system", "recovery are locked". I tried the wire trick for s-off, but the program fails at "testing "ADB" because the phone never gets that far, booting into OS.
I just tried rerunning the 605.2 RUU and it went through all of the steps. I may have attempted a downgrade and it seems to downgrade some things then when i go back to 605.2 it does the whole upgrade again. I'll try the 605.2 RUU upgrade twice to see if it makes any difference. This is my 5th Rezound I've tried to upgrade to 605.2 so I know to wait for it to do all of its thing. Maybe someone earlier aborted an upgrade and hosed it. Is the area with the boot, system, recovery removeable. If so, I'd replace the internal SD. For a while I was also getting a "security warning" just below "RELOCKED".
On the initial update phase it checks the image, then reboots and gives me a list of 18 things to upgrade and the option to proceed. I click vol up and it proceeds through the list "unzipping", "updating", "OK". No errors. It takes a while to update "system" which tells me it is doing something. Ends with "Update Complete". I also tried flashing the zip from a pc with fastboot. The screen on the phone thurned black with a HTC on it and the flash seemed to run a while but no good.I also tried flashing boot.img and Amon Ra. When trying to boot into recovery from the bootloader menu the progress bar on the right side moves up as normal with Amon RA but when it reboots it just does a boot loop like it does when trying to boot the OS. On the second and subsequent boots while holding vol down and power, it re-upgrades. So it seems that the system can't write to those areas and therefore keeps trying on subsequent tries. I don't understand why it says OK after each item updated if the updates are failing.
Click to expand...
Click to collapse
I had a similar issue with mine last week. Woke up to a phone that booted to the white screen, and that's all. I tried pushing a new kernel, new recovery, nothing. I relocked and got the same error code, but regardless it DID relock the bootloader. I ran the RUU for the Global (which I was on) and that fixed the phone to a working stock again (stock to the Global Rom, which never went official). I had to flash it twice as a Ph98IMG. After the second flashing, I pulled the SD card and rebooted. It's been working fine since. I have yet to unlock again. Maybe tonight if I have time. I am missing my wireless tether.
318sugarhill said:
I had a similar issue with mine last week. Woke up to a phone that booted to the white screen, and that's all. I tried pushing a new kernel, new recovery, nothing. I relocked and got the same error code, but regardless it DID relock the bootloader. I ran the RUU for the Global (which I was on) and that fixed the phone to a working stock again (stock to the Global Rom, which never went official). I had to flash it twice as a Ph98IMG. After the second flashing, I pulled the SD card and rebooted. It's been working fine since. I have yet to unlock again. Maybe tonight if I have time. I am missing my wireless tether.
Click to expand...
Click to collapse
I tried it twice in a row as PH98IMG.zip with no luck. I've probably tried is a dozen or so times with "relocked" just as I have done four others. This is the only one that has this issue. How can you get s-off with no boot, fastboot is fine from the device or pc, I also cant boot to recovery. booting to recovery just puts in another loop. Is there a way to read the name of the recovery or address that partition?
As a side note: I also noted that anytime I plug the pc usb into the phone it powers up into bootloader. This happens anytime, even after a battery pull and reinsert. It's like the phone wants me to do something but I dont know what.
jcampolo said:
I tried it twice in a row as PH98IMG.zip with no luck. I've probably tried is a dozen or so times with "relocked" just as I have done four others. This is the only one that has this issue. How can you get s-off with no boot, fastboot is fine from the device or pc, I also cant boot to recovery. booting to recovery just puts in another loop. Is there a way to read the name of the recovery or address that partition?
As a side note: I also noted that anytime I plug the pc usb into the phone it powers up into bootloader. This happens anytime, even after a battery pull and reinsert. It's like the phone wants me to do something but I dont know what.
Click to expand...
Click to collapse
So you've been trying with the global RUU? What were you on before? Just curious.
Reply
318sugarhill said:
So you've been trying with the global RUU? What were you on before? Just curious.
Click to expand...
Click to collapse
I don't know what it was on before. When I got it it would only boot to the HTC screen that just has "HTC" on a white background.
So I took the battery to see if I could get to the bootloader screen. That worked so I figured the rest was simple, flash a RUU.
I should have checked the current version but just learned to do that while working on this thing.
I unlocked it, flashed Amon RA, relocked it and I flashed the 4.03.605.2 zip RUU and all looked good. OK, OK, OK, etc. Rebooted to a boot loop.
Tried to go to recovery, another boot loop.
It can't write to the boot, system or recovery, access is denied.
Thats where i am. Tried a ton of stuff, a million threads, no luck.
Now I'm trying to get it back to any stock rom that I can get to work and I know how to proceed from there.
tried RUU_Vigor_VERIZON_WWE_1.00.605.3 exe and RUU_Vigor_VERIZON_WWE_2.01.605.11 the installer goes through all of the steps and fails stating that the current rom is newer than the upgrade and stops. Maybe, just maybe if there was a version newer than 4.03.605.2 it would take. I'd like to just downgrade somehow and start from there. Or maybe an RUU exe for 4.03.605.2 would work if I could find one. The earlier exes work up to the point of quiting when the RUU is older than the installed version.
First, off, awesome NOOB video, and after watching it I can safely say I've done my due diligence. I have scoured our internet and several parallel earth internets with no luck in finding a solution. If any of you can give me a hand, I'd really appreciate it.
Phone Specs:
HTC Rezound
VIGOR PVT SHIP S-ON RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-V14.6.0.7708.00.0507
eMCC-BOOT
Sep 20 2012,17:40:22
SDK tools: "Pulled from the SDK of February 13, 2013"
PROBLEM: Cannot revert to stock rom by
1) using an RUU exe to revert, but it crashes on both my home and office PCs (Win7). The file is the only one I've been able to find: RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed
2) or flashing from Amon Ra or TWRP (can't mount eMCC/data)
3) or uploading PH98IMG.zip to SD card and letting Hboot handle the heavy lifting (sticks at HTC boot up screen on reboot)
4) or using "fastboot oem rebootRUU" followed by "fastboot flash zip PH98IMG.zip" gets
sending 'zip' (624366 KB)...
OKAY [ 55.743s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 142.046s
BACKGROUND: I'm obviously a noob, but the only way to learn is by digging in. Here's the progression that's led me to this point:
1) Learned to unlock bootloader
2) Installed cm-10.1-20130629-NIGHTLY-vigor (officially unsupported by available for Rezound from CyanogenMOD's website)
3) Noticed instability so I wiped everything (x3) and tried to revert to stock. Couldn't make any progress, especially since the RUU exe crashes on both Win7 systems I have.
4) To get functionality for work, switched to cm-10.1.0.1-vigor.
5) Still have stability issues, so I'm trying yet again to revert. Current results of attempts are listed above under "PROBLEMS"
Note1: Per Scott's suggestion over either at Phandroid or ScottsRoms (can't remember I've been so many different places), I've modified the android-info.txt in PH98IMG.zip as follows, making sure the version number is higher than the current from CID Getter:
"modelid: PH9810000
cidnum: VZW__001
mainver: 4.09.605.2
hbootpreupdate:12
DelCache:1
DelFat:1
"
Note 2: MD5s check out.
Note 3: Before my first installation of CyanogenMOD's latest nightly, adb worked fine and would list my phone. After CyanogenMOD's latest nightly, adb does succeed in starting daemon and lists what it think is my phone, but instead of listing a phone it lists a blank space and returns to the command prompt. if I try adb reboot, it returns error: device not found. BUT fastboot still works fine.
Appendix 1: fastboot getvar all returns:
C:\Users\Josh\Desktop\Root Project\sdk-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.28.0000
(bootloader) version-baseband: 2.23.10.0123r/2.23.10.0124r
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: (seem odd to anyone else that there's no number there?)
(bootloader) serialno: ******
(bootloader) imei:
(bootloader) product: vigor
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH9810000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3776mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: cecc19f7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.499s
Appendix 2: The sequence I've been following trying to get the thing to accept the stock rom is below...and I've tried small variations variations when what's below fails miserably.
1. Load TWRP or Amon Ra recovery
2. Wipe, wipe, wipe!
3. Reboot bootloader
4. fastboot flash recovery recovery_signed.img (have treated as interchangeable in sequence with step 5)
5. fastboot flash boot boot_signed.img (have treated as interchangeable in sequence with step 4)
6. (used this, also from Scott, before I started manually editing the android-info.txt in the image zip) fastboot flash zip SetMainVersionLOW.zip (to make sure the main version is lower than the stock ROM version--otherwise it'll think you're upgrading to a lower version and won't run)
7. fastboot oem lock
8. This step varies. I've tried
a. fastboot oem rebootRUU then fastboot flash zip PH98IMG.zip
b. fastboot boot TWRP or Amon Ra recovery, then flashing PH98IMG.zip from there
c. dropping PH98IMG.zip on the SD card and letting Hboot handle the heavy lifting
I take it you didn't take a back up of your previous rom before installing CM10.1?
mjones73 said:
I take it you didn't take a back up of your previous rom before installing CM10.1?
Click to expand...
Click to collapse
That's correct. And I deserve what I'm going through for that alone if nothing else.
One additional note I'm about to edit into the post above. I've also tried using an RUU exe to revert, but it crashes on both my home and office PCs (Win7). The file is the only one I've been able to find: RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed
JoshManning said:
That's correct. And I deserve what I'm going through for that alone if nothing else.
One additional note I'm about to edit into the post above. I've also tried using an RUU exe to revert, but it crashes on both my home and office PCs (Win7). The file is the only one I've been able to find: RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed
Click to expand...
Click to collapse
I believe won't be able to use the RUU anyway because your hboot version is too high, you can't back down if you're s-on (and I could be wrong but I haven't seen a RUU with the latest OTA included). I'd suggest just installing a stock rooted rom - http://forum.xda-developers.com/showthread.php?t=2260154
mjones73 said:
I believe won't be able to use the RUU anyway because your hboot version is too high, you can't back down if you're s-on (and I could be wrong but I haven't seen a RUU with the latest OTA included). I'd suggest just installing a stock rooted rom - http://forum.xda-developers.com/showthread.php?t=2260154
Click to expand...
Click to collapse
Thank you! The opening post notes that the ROM comes without the radio or firmware. Will I be ok? I build my own PCs and know that must be an idiot question, but I just don't yet understand enough about the way the phones work. Thank you very much for your help.
JoshManning said:
Thank you! The opening post notes that the ROM comes without the radio or firmware. Will I be ok? I build my own PCs and know that must be an idiot question, but I just don't yet understand enough about the way the phones work. Thank you very much for your help.
Click to expand...
Click to collapse
You already have the latest firmware on your phone, that doesn't get touched when you do a rom install.
Thank you, Matt! I'm downloading the ROM right now. Will post results once it's down.
SOLVED
JoshManning said:
Thank you! The opening post notes that the ROM comes without the radio or firmware. Will I be ok? I build my own PCs and know that must be an idiot question, but I just don't yet understand enough about the way the phones work. Thank you very much for your help.
Click to expand...
Click to collapse
Oh my gosh! I can't believe that did the trick. Matt, you rock! May I send you a Starbucks card or something?
Couple of clarifications if you have time:
1) TWRP wouldn't install the ROM, but Amon Ra would. Any idea why?
2) What in my original post led you to this solution? Just trying to learn. =)
Thank you again!
JoshManning said:
Oh my gosh! I can't believe that did the trick. Matt, you rock! May I send you a Starbucks card or something?
Couple of clarifications if you have time:
1) TWRP wouldn't install the ROM, but Amon Ra would. Any idea why?
2) What in my original post led you to this solution? Just trying to learn. =)
Thank you again!
Click to expand...
Click to collapse
The update-binary and the updater-script in the META-INF are not updated to work properly with TWRP in the rom you installed.
I learned that the hard way when I built my OTA Blue rom.
good to see you got it working
kc6wke said:
The update-binary and the updater-script in the META-INF are not updated to work properly with TWRP in the rom you installed.
I learned that the hard way when I built my OTA Blue rom.
good to see you got it working
Click to expand...
Click to collapse
Makes perfect sense. Rocking along now nicely thanks to you. Seriously, can I send you an Amazon card or something?
JoshManning said:
Oh my gosh! I can't believe that did the trick. Matt, you rock! May I send you a Starbucks card or something?
Couple of clarifications if you have time:
1) TWRP wouldn't install the ROM, but Amon Ra would. Any idea why?
2) What in my original post led you to this solution? Just trying to learn. =)
Thank you again!
Click to expand...
Click to collapse
You're welcome, kc6wke covered question 1, for number 2, I knew you couldn't RUU cause you are on the latest firmware and s-on, it's not possible to downgrade firmware unless you're s-off. Your only option really was to install a different rom so I gave you a stock rooted one.
Matt, I've got an additional question if you have time. Any idea why my attempts to root the new ROM aren't taking hold? The phone is running just fine off the ROM you directed me to. After installation, I booted into Amon RA 3.16, installed superuser and su, and rebooted. Nothing. SUChecker returns "su declined / not found"
Actually nevermind. SUChecker is returning a false negative. Apologies, and thanks again!
The one I gave you was already rooted, no need to do that.
mjones73 said:
The one I gave you was already rooted, no need to do that.
Click to expand...
Click to collapse
I now remember your saying that. Thank you so much for your help. I really appreciate it.
Josh,
I may be wrong but I think that the iemi is sensitive info so you might want to delete that from your original post. Maybe delete your serial number as well just in case.
btw... my phone doesn't show a mainver either, never got an answer as to why not, but it works fine.
Thanks! Done and done.
well he was a noob, but then he just became just like the rest of them
how did he uploaded the rom in Amon Ra.
band001 said:
how did he uploaded the rom in Amon Ra.
Click to expand...
Click to collapse
Depends, are you s-on or s-off?
mjones73 said:
Depends, are you s-on or s-off?
Click to expand...
Click to collapse
s-off
---------- Post added at 06:46 PM ---------- Previous post was at 06:31 PM ----------
band001 said:
s-off
Click to expand...
Click to collapse
Sorry but i am s-on not s-off yet. trying to get info on how to also if this does not work.
Apologies for the newbie (and probably already answered question), but I cannot find this question asked and answered explicitly:
Does going from an already S-OFF GPe conversion (via the GPe 4.3 RUU) to the T-Mobile 4.3 RUU (to get the 4.4 OTA) reset me back to S-ON?
I want to go back to T-Mobile stock 4.4 (want to give Sense another chance), but still be able to run the GPe 4.4 RUU and get back to where I am right now if I don't like it.
Thanks very much.
FayezZ said:
Apologies for the newbie (and probably already answered question), but I cannot find this question asked and answered explicitly:
Does going from an already S-OFF GPe conversion (via the GPe 4.3 RUU) to the T-Mobile 4.3 RUU (to get the 4.4 OTA) reset me back to S-ON?
I want to go back to T-Mobile stock 4.4 (want to give Sense another chance), but still be able to run the GPe 4.4 RUU and get back to where I am right now if I don't like it.
Thanks very much.
Click to expand...
Click to collapse
Running the 4.3 tmo RUU didnt change my s-off or bootloader state at all. After running RUU, I was able to push TWRP and go back to business as usual.
Is there a TMO stock 4.3 i can flash with twrp that will get me the OTA ? Or do I need stock recovery that came with 4.3?
BurnOne77 said:
Is there a TMO stock 4.3 i can flash with twrp that will get me the OTA ? Or do I need stock recovery that came with 4.3?
Click to expand...
Click to collapse
RUU needs stock recovery. just relock boot loader, RUU, take OTA, unlock/root/flash TWRP & profit
No need to even relock. stock recovery is all you need. My phone was was unlocked and rooted and i got the updates no problem. I was also S-OFF before I updated (from hboot 1.44), still S-OFF after 4.4.2 update.
Appreciate the feedback, everyone - thank you.
So, here's a follow-up question (and I'm still being a newbie here, unfortunately): I've flashed the T-Mobile 4.3 RUU (took a very long time to figure all that out; had to downgrade firmware, flash the rom.zip directly, etc.) and subsequently manually applied the 4.4 OTA via stock recovery. Before doing the RUU, I re-locked bootloader (so it now says "Relocked"). I'm still S-OFF. Now my issue is that I can't flash a custom recovery to get root because my bootloader is locked.
Is there an easy way to unlock bootloader (HBOOT 1.56 now)? I know I can go the "official" HTCDev way, but wanted to check and see if there's something easy/obvious/non-warranty voiding way first.
Thanks!
I've gotten the unlock bin file from HTCDev for two phones with absolutely no issues. You should try to do the same. The process is very simple, just follow their guide...
http://www.htcdev.com/bootloader
Choose 'All other supported models' at the bottom of the list.
shpitz461 said:
I've gotten the unlock bin file from HTCDev for two phones with absolutely no issues. You should try to do the same. The process is very simple, just follow their guide...
http://www.htcdev.com/bootloader
Choose 'All other supported models' at the bottom of the list.
Click to expand...
Click to collapse
Thank you. I ended up doing this because I figured it was a safer way to do what I needed without fumbling my way through non-official methods. Worked great. I'm now on TMo 4.4 and rooted, just like I was hoping to be.
having issues
I'm trying to achieve the same thing, but I'm having trouble flashing the stock recovery. I keep getting, "could not open recovery.img"
My phone is;
s-off
hboot 1.54
android 4.1.2
software # 1.27.531.11
Maybe unrelated, the kernel version is;
3.4.10-g04f3908
[email protected] #1
SMP PREEMPT
I'd be cool if you guys helped w/ fixing that too!
ilikecars212 said:
I'm trying to achieve the same thing, but I'm having trouble flashing the stock recovery. I keep getting, "could not open recovery.img"
My phone is;
s-off
hboot 1.54
android 4.1.2
software # 1.27.531.11
Maybe unrelated, the kernel version is;
3.4.10-g04f3908
[email protected] #1
SMP PREEMPT
I'd be cool if you guys helped w/ fixing that too!
Click to expand...
Click to collapse
You can start by telling us how you went on trying to flash the recovery...
Regardless of recovery, your firmware appear to be very old, I recommend you update that as well.
Are you on stock ROM? Didn't you get OTA notifications about upgrades?
Settings > About > System Updates
shpitz461 said:
You can start by telling us how you went on trying to flash the recovery...
Regardless of recovery, your firmware appear to be very old, I recommend you update that as well.
Are you on stock ROM? Didn't you get OTA notifications about upgrades?
Settings > About > System Updates
Click to expand...
Click to collapse
First off, thanks for helping.
I downloaded the stock recovery img, renamed it recovery, then tried "fastboot flash recovery recovery.img"
The img file is in my fastboot folder.
I am getting OTA notifications about upgrades, but they say the updates can't be installed after they are downloaded.
How do I go about updating my firmware?
I do have TWRP if that makes anything easier.
I'm very new to this if you cant tell. I bought my One used, and seller didn't say it was rooted and s-off in the listing.
Stock OTA will not work with a custom recovery (like TWRP or CWM). You have to flash stock recovery.
Boot into bootloader and do this:
fastboot getvar all
Click to expand...
Click to collapse
Paste the output, make sure you remove IMEI and serialno.
---------- Post added at 08:39 PM ---------- Previous post was at 08:31 PM ----------
You should also follow the guide here: http://forum.xda-developers.com/showthread.php?t=2355814
And flash to latest firmware (which includes stock recovery, which will allow you upgrade via OTA).
shpitz461 said:
Stock OTA will not work with a custom recovery (like TWRP or CWM). You have to flash stock recovery.
Boot into bootloader and do this:
Paste the output, make sure you remove IMEI and serialno.
---------- Post added at 08:39 PM ---------- Previous post was at 08:31 PM ----------
You should also follow the guide here: http://forum.xda-developers.com/showthread.php?t=2355814
And flash to latest firmware (which includes stock recovery, which will allow you upgrade via OTA).
Click to expand...
Click to collapse
Sorry it took me a few days.
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4T.21.3218.21
version-cpld: None
version-microp: None
version-main: 3.58.1700.5
version-misc: PVT SHIP S-OFF
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0713000
cidnum: t-mob010
battery-status: good
battery-voltage: 3926mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-5d4c562c
hbootpreupdate: 11
gencheckpt: 0
I followed the guide in the link you posted. I downloaded the 1.27.531.11 firmware file since it matches my software version. Then...
C:\SDK>fastboot flash zip firmware.zip
error: cannot open 'firmware.zip'
ilikecars212 said:
version-main: 3.58.1700.5
I followed the guide in the link you posted. I downloaded the 1.27.531.11 firmware file since it matches my software version. Then...
C:\SDK>fastboot flash zip firmware.zip
error: cannot open 'firmware.zip'
Click to expand...
Click to collapse
The firmware is 3.58.1700.5, not what is shown in Settings>About. What is shown in Settings is the software side of things. getvar in fastboot shows the hardware side of things.
The error you got indicates that firmware.zip is not in the folder you're in (C:\SDK). Either copy the zip over to C:\SDK or just specify a path in the fastboot command.
I think it's better to stick with a recovery image that is closer to your actual hardware firmware version (3.58), but i'm not 100% sure it makes any difference.
shpitz461 said:
The firmware is 3.58.1700.5, not what is shown in Settings>About. What is shown in Settings is the software side of things. getvar in fastboot shows the hardware side of things.
The error you got indicates that firmware.zip is not in the folder you're in (C:\SDK). Either copy the zip over to C:\SDK or just specify a path in the fastboot command.
I think it's better to stick with a recovery image that is closer to your actual hardware firmware version (3.58), but i'm not 100% sure it makes any difference.
Click to expand...
Click to collapse
I definitely had the firmware.zip folder in the same file that has adb and fastboot apps. I've gotten the same error when trying to flash just the stock recovery img. This is why I'm so confused.
NVM. Figured it out for the moment.
I'm officially back to being confused.
C:\SDK>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.111s]
finished. total time: 0.112s
C:\SDK>fastboot flash zip firmware.zip
target reported max download size of 1526722560 bytes
sending 'zip' (41648 KB)...
OKAY [ 3.247s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 3.728s
C:\SDK>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.104s]
finished. total time: 0.105s
C:\SDK>fastboot flash recovery recovery.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9596 KB)...
OKAY [ 1.234s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.270s
Click to expand...
Click to collapse
ilikecars212 said:
I'm officially back to being confused.
Click to expand...
Click to collapse
Once you switch to RUU mode, I don't think you can flash non-zipped firmware files.
Code:
C:\SDK>fastboot flash zip firmware.zip
target reported max download size of 1526722560 bytes
sending 'zip' (41648 KB)...
OKAY [ 3.247s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 3.728s
Once you had this fail the 1st time, you should've flashed the zip again immediately. You rebooted instead.
So do it again, but flash the same zip twice. That should do it.
Oh, and another thing, The zip you tried to flash doesn't match your model ID. Your getvar reports the phone to be T-Mobile, but you're trying to flash non-T-Mobile firmware.
You need to get the stock TMO firmware that matches your phone:
modelid: PN0713000
cidnum: t-mob010
Click to expand...
Click to collapse
Finally, since you're S-OFF, you can change your CID to the superCID (11111111), this will allow you to flash ANY firmware you'd like.
With your currect CID (t-mob010) you can only flash firmware that matches 't-mob010'.
shpitz461 said:
Once you switch to RUU mode, I don't think you can flash non-zipped firmware files.
Code:
C:\SDK>fastboot flash zip firmware.zip
target reported max download size of 1526722560 bytes
sending 'zip' (41648 KB)...
OKAY [ 3.247s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 3.728s
Once you had this fail the 1st time, you should've flashed the zip again immediately. You rebooted instead.
So do it again, but flash the same zip twice. That should do it.
Click to expand...
Click to collapse
I tried reflashing it 5 times before rebooting, I just went through the steps I took quickly to show what my problem is.
I get the same failure message every time.
Also, I don't understand what you're getting at when you mentioned only being able to flash .zip files in RUU mode. I only tried flashing a .zip file. When I tried flashing the recovery.img I put the phone back into fastboot.
Any more suggestions? Thank you for helping me
shpitz461 said:
Oh, and another thing, The zip you tried to flash doesn't match your model ID. Your getvar reports the phone to be T-Mobile, but you're trying to flash non-T-Mobile firmware.
You need to get the stock TMO firmware that matches your phone:
Finally, since you're S-OFF, you can change your CID to the master CID (11111111), this will allow you to flash ANY firmware you'd like.
With your currect CID (t-mob010) you can only flash firmware that matches 't-mob010'.
Click to expand...
Click to collapse
I unzipped the firmware.zip and checked the android-info.txt and my CID and MID were matching.
I'm not sure how to change to super CID. Is there a chance I'll lose any functionality?
ilikecars212 said:
I unzipped the firmware.zip and checked the android-info.txt and my CID and MID were matching.
I'm not sure how to change to super CID. Is there a chance I'll lose any functionality?
Click to expand...
Click to collapse
You can change to superCID following this: http://forum.xda-developers.com/showthread.php?t=2317536
have you tried following this? http://forum.xda-developers.com/showthread.php?t=2358738
I'm not sure why fastboot complains about a mismatch since the CIDs match. Your current firmware indicates the phone was converted to GPE (the .1700 in the version-main field).
Try to follow the guide above and see how that goes... Make sure you flash a .531 ROM as that is T-Mobile.
What is the model printed at the back-bottom-left of your phone? Is it PN07310?
Or maybe just backup your data and flash this: http://www.htc1guru.com/dld/ruu_m7_...3_10-38m-1157-04_release_336982_signed_2-exe/
This is the complete stock 3.24 image for T-Mobile.
Stuck on white background with htc logo, stock rom from RUU, relocked bootloader. am able to get into bootloader, Not sure where to go from here without screwing it more, any suggestions would be greatly appreciated.
Please provide some more information .. Like your phone build, also let us know of what were you trying to achieve and the things that you have done with the phone.
same problem
ethanon said:
Please provide some more information .. Like your phone build, also let us know of what were you trying to achieve and the things that you have done with the phone.
Click to expand...
Click to collapse
i have the same problem, stuck in here for .. 2 mabey 3 months...
here is some info:
hboot:1.40.0000(*** unlocked ***)
cid:htc_e11
s-on
enrc2b_u
i have installed twrp and that's pretty mutch everything what is on my phone..
i wiped my phone before installing the new rom.. and now i'm not able to get past my bootscreen please could anyone help me?
im sure there are a couple more phones like this ohh btw i have a "HTC One X +".
:angel:
If your bootloader says relocked, you won't be able to not a custom kernel. What are you trying to do specifically?
Sent from my HTC One X+ using xda app-developers app
santinobonotaa said:
i have the same problem, stuck in here for .. 2 mabey 3 months...
here is some info:
hboot:1.40.0000(*** unlocked ***)
cid:htc_e11
s-on
enrc2b_u
i have installed twrp and that's pretty mutch everything what is on my phone..
i wiped my phone before installing the new rom.. and now i'm not able to get past my bootscreen please could anyone help me?
im sure there are a couple more phones like this ohh btw i have a "HTC One X +".
:angel:
Click to expand...
Click to collapse
Did you install the boot.img that came within the rom ? to help you we need more exact steps .
No guys I just used the RUU to return it to stock, relocked the bootloader and have used the phone for 3 months as is without any problems and for some godforsaken reason its now stuck in a bootloop and all i want to do is use my phone like normal again.
Hboot 1.35
radio 3.1204.168.32
additional help required
ethanon said:
Did you install the boot.img that came within the rom ? to help you we need more exact steps .
Click to expand...
Click to collapse
heey,
i used the next steps but all failed
cmd.exe -> adb toolkit
fastboot(usb)(on phone)
(on computer)
fastboot flash cm10.0 (sorry i was desperate, but it failed)
adb sideload cm10.0 (also failed)(error code: E:Error executiong updater binary in zip '/data/media/sideload.zip')
im using team win recovery project v2.6.3.0
phone is always above 60%
any questions?
just ask
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
also is it possible to use an OTG cable to access a usb stick? that would be a very nice solution for phones that cannot change theyre sd card or there battery.
similar issue, yet to find a solution
Hi all,
I'm having a very similar issue to the one here. I have the HTC One X+ on AT&T. I had never rooted this phone. I got the OTA update in January, which seemed to go pretty smoothly. The phone was slow for a few days until I got all the apps updated and then was starting to be normal again. Every now and then it would hang and then I'd force restart and it would stick on the bootscreen until I restarted again. One day, however, it did this and then never exited the bootscreen. Got into the bootloader menu and did factory reset in hboot mode, which did nothing. Then I find out it wouldn't do anything because the settings of the phone were set to Fastboot and that needs to be unchecked for factory reset to work. But I can't get into the phone to change that, so I started looking through many many forums here at XDA and trying solutions to problems that were as close to mine as I could find. ...most people have this problem when first attempting the update or when putting on a custom rom, or using a different HTC phone.
So, I've learned quite a bit about flashing roms and the architecture of my phone, but not enough to fix this or to know where I may have may things worse. Here is a summary of what I attempted (all with battery >50% and HTC Sync has been installed on my computer--although the computer never recognizes the device and says driver install failed every phone reboot):
First was to get adb and fastboot and clear the cache
Then I ran the RUU: RUU_EVITARE_UL_JB_50_S_Cingular_US_2.15.502.1_Radio_2.21.5517.15_18.27.11.35L_release_341689_signed_0220
It claimed it updated my phone from 2.15.502 to 2.15.502 and then hung on the bootscreen. (it did CHANGE the bootscreen logo to a simple HTC)
Older RUUs return an error that they are not the right RUU for my phone.
Next, I attempted to directly flash the recovery_signed and boot.img from the zipped roms that were in the TEMP folder after initializing the RUU (according to one forum thread), but this method required a system.img to exist and it does not.
I flashed TWRP recovery (v2.6.3.0) and can access that just fine. The entire phone is wiped. There is no OS. I cannot mount the SD card.
Most recently, I attempted to sideload the zipped ROM from the RUU (http://forum.xda-developers.com/showthread.php?t=2317986). It failed (unable to find partition size..unable to mount anything), so I used adb push to put the rom onto the SD card. Install from TWRP also failed. Unable to find/mount anything. That's where I am now.
*** UNLOCKED ***
EVITARE_UL PVT SHIP S-ON RL
HBOOT-1.73.0000
CPLD-None
MICROP-None
RADIO-SSD:2.21.5517.15
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM TYPE : MDM9215M
Sep 30 2013, 17:16:15
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.73.0000
(bootloader) version-baseband: SSD:2.21.5517.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.15.502.1
(bootloader) serialno: ***********
(bootloader) imei: ***************
(bootloader) product: evitare_ul
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PM6310000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4160mV
(bootloader) devpower: 93
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
Thanks.
mabey case closed?!
heeyy,, i fixed my HOX+ (HTC ONE+) with the next steps:
download this rom, boot.img , recovery and gapps. ---> dropboxbox /sh/kzgnoqmfstuc53z/IEof1v7nL3
make sure you have the latest sdk tools
open the SDK Manager.exe only install: platform tools
once installed open it.. search cmd.exe on your computer. (easiest is windows-key -> type: cmd.exe -> right click -> copy) and paste it in the platform tools folder.
open cmd.exe in the platform tools folder, from here we go to the phone
now connect your phone and computer by cable.
now start your HOX+ in fastboot mode, press power button with volume-down button at the same time (make sure you unlocked your HOX+ on the htcdev website.)
now make sure the red text on your phone is: fastboot usb
and we go back to our laptop.
go to the cmd program, type the following: fastboot flash recovery [recovery.img*]
* drag the recovery of the downloaded recovery.img to the cmd
now when you flashed the recovery.. now lets flash the boot...
type the following: fastboot flash boot [boot.img**]
** drag the boot of the downloaded boot.img to the cmd
now reboot the phone in recovery mode.
go back to your cmd.
and type again the following:adb devices <-- and make sure your device is in there otherwise ther's a problem
and than:adb push [cm10.zip***]
*** drag the cm10 for the downloaded cm10 to the cmd
and wait.....
and wait more...
and when it's completed..
go to your phone and install zip from sdcard.
search: cm10 blablabla and install .. and now reboot ^^
im not a professional.. i just shared my solution with you and i hope it helped your bootlooped phone too!!
and if someone could help me with upgrading cm10 to a custom rom 4.4 (kitkat) with a detailed description would it encourage me to help other people and it would even encourage me to study for application devellopment <3
---------- Post added at 06:24 PM ---------- Previous post was at 06:09 PM ----------
sorry for dropbox link .. :$
santinobonotaa said:
heeyy,, i fixed my HOX+ (HTC ONE+) with the next steps:
download this rom, boot.img , recovery and gapps. ---> dropboxbox /sh/kzgnoqmfstuc53z/IEof1v7nL3
make sure you have the latest sdk tools
open the SDK Manager.exe only install: platform tools
once installed open it.. search cmd.exe on your computer. (easiest is windows-key -> type: cmd.exe -> right click -> copy) and paste it in the platform tools folder.
open cmd.exe in the platform tools folder, from here we go to the phone
now connect your phone and computer by cable.
now start your HOX+ in fastboot mode, press power button with volume-down button at the same time (make sure you unlocked your HOX+ on the htcdev website.)
now make sure the red text on your phone is: fastboot usb
and we go back to our laptop.
go to the cmd program, type the following: fastboot flash recovery [recovery.img*]
* drag the recovery of the downloaded recovery.img to the cmd
now when you flashed the recovery.. now lets flash the boot...
type the following: fastboot flash boot [boot.img**]
** drag the boot of the downloaded boot.img to the cmd
now reboot the phone in recovery mode.
go back to your cmd.
and type again the following:adb devices <-- and make sure your device is in there otherwise ther's a problem
and than:adb push [cm10.zip***]
*** drag the cm10 for the downloaded cm10 to the cmd
and wait.....
and wait more...
and when it's completed..
go to your phone and install zip from sdcard.
search: cm10 blablabla and install .. and now reboot ^^
im not a professional.. i just shared my solution with you and i hope it helped your bootlooped phone too!!
and if someone could help me with upgrading cm10 to a custom rom 4.4 (kitkat) with a detailed description would it encourage me to help other people and it would even encourage me to study for application devellopment <3
Click to expand...
Click to collapse
Still stuck
TWRP wouldn't let me sideload and returned many "unable to mount" errors.
I put CWM on (the one rated for my phone) and it also gives the "can't mount" errors (/system, /data, /cache, etc.)
But I was able to sideload the Elegancia 6.2 rom onto the phone. It immediately started the install after that, but hangs at some early % (9.07 one time, now 13.07%).
These are subsequent attempts. The first time I wasn't staring at the phone and it appeared to have installed, but rebooted into HTC screen and stayed there. I had already flashed the kernel, but did so again with no luck.
CWM still says it can't mount /cache/recovery, etc.
Again, at a loss.
mrg209 said:
Hi all,
I'm having a very similar issue to the one here. I have the HTC One X+ on AT&T. I had never rooted this phone. I got the OTA update in January, which seemed to go pretty smoothly. The phone was slow for a few days until I got all the apps updated and then was starting to be normal again. Every now and then it would hang and then I'd force restart and it would stick on the bootscreen until I restarted again. One day, however, it did this and then never exited the bootscreen. Got into the bootloader menu and did factory reset in hboot mode, which did nothing. Then I find out it wouldn't do anything because the settings of the phone were set to Fastboot and that needs to be unchecked for factory reset to work. But I can't get into the phone to change that, so I started looking through many many forums here at XDA and trying solutions to problems that were as close to mine as I could find. ...most people have this problem when first attempting the update or when putting on a custom rom, or using a different HTC phone.
So, I've learned quite a bit about flashing roms and the architecture of my phone, but not enough to fix this or to know where I may have may things worse. Here is a summary of what I attempted (all with battery >50% and HTC Sync has been installed on my computer--although the computer never recognizes the device and says driver install failed every phone reboot):
First was to get adb and fastboot and clear the cache
Then I ran the RUU: RUU_EVITARE_UL_JB_50_S_Cingular_US_2.15.502.1_Radio_2.21.5517.15_18.27.11.35L_release_341689_signed_0220
It claimed it updated my phone from 2.15.502 to 2.15.502 and then hung on the bootscreen. (it did CHANGE the bootscreen logo to a simple HTC)
Older RUUs return an error that they are not the right RUU for my phone.
Next, I attempted to directly flash the recovery_signed and boot.img from the zipped roms that were in the TEMP folder after initializing the RUU (according to one forum thread), but this method required a system.img to exist and it does not.
I flashed TWRP recovery (v2.6.3.0) and can access that just fine. The entire phone is wiped. There is no OS. I cannot mount the SD card.
Most recently, I attempted to sideload the zipped ROM from the RUU (http://forum.xda-developers.com/showthread.php?t=2317986). It failed (unable to find partition size..unable to mount anything), so I used adb push to put the rom onto the SD card. Install from TWRP also failed. Unable to find/mount anything. That's where I am now.
*** UNLOCKED ***
EVITARE_UL PVT SHIP S-ON RL
HBOOT-1.73.0000
CPLD-None
MICROP-None
RADIO-SSD:2.21.5517.15
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM TYPE : MDM9215M
Sep 30 2013, 17:16:15
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.73.0000
(bootloader) version-baseband: SSD:2.21.5517.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.15.502.1
(bootloader) serialno: ***********
(bootloader) imei: ***************
(bootloader) product: evitare_ul
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PM6310000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4160mV
(bootloader) devpower: 93
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
Thanks.
Click to expand...
Click to collapse
have you solved the problem ?
Unsolved
mobileplazza said:
have you solved the problem ?
Click to expand...
Click to collapse
No, I didn't solve it. I ran out of time (had a child) and got the Galaxy S5. But I still have the HTC and want to fix it when I have time to work on it again.
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 .