Hello Everyone,
When i was in USA i ordered htc one m8 and it is AT&T phone i guess. Since i hate the AT&T apps in the phone i tried to flash a custom rom and i sort of succeeded. Yet i still have problem about it. Whenever i flash a custom rom form( http://forum.xda-developers.com/htc-one-m8/development#romList ) here its smooth and perfect first 1-2 weeks. No lagging no annoying problems. But after 2 weeks i am having lags (like slow app opening, late reactions, even freezing) It happens all the time, doesn't whichever rom i tried. And another problem is I can kill my battery in 2-3 hours just playing a game (lower than 500mb games). How can i make my phone stable smooth fast and longer battery life? (I love the room that i am using at the moment http://forum.xda-developers.com/htc...the-worlds-first100-m9-port-m8upload-t3064838) And i also started to consider that am i flashing the roms wrong??!
Please can somebody help me
Ryokan said:
When i was in USA i ordered htc one m8 and it is AT&T phone i guess.
But after 2 weeks i am having lags (like slow app opening, late reactions, even freezing).
Click to expand...
Click to collapse
Please do fastboot getvar all, and post the results (delete IMEI and serial number before posting), so we can take a look at a couple things.
But to some extent, all the Sense ROMs seem to lag to some degree over time. Wiping cache may help. But most folks are able to live with it. What you are describing may or may not be something more serious. I don't personally get any freezing (presently on stock Dev Edition 6.12.1540, previously on S.ROM) but do seem some lag most prominently in waking/unlocking the screen, and for the home screen to populate with my widgets and apps.
Another thing you might try is a GPE based ROM.
Ryokan said:
And another problem is I can kill my battery in 2-3 hours just playing a game (lower than 500mb games).
Click to expand...
Click to collapse
Games use battery, that's just a fact of current smartphones.
The storage size of the game has little (if anything) to do with how much battery will be used. If it uses the CPU/GPU intensively, its going to suck down the battery. And game devs don't seem to be shy about this. I guess they assume that if you are gaming intensively, you are willing to live with the fact that you'll need to charge the phone frequently.
Every game is different, of course. But you'll see many (or even most) games will drain just about any phone or tablet's battery in a few hours.
redpoint73 said:
Please do fastboot getvar all, and post the results (delete IMEI and serial number before posting), so we can take a look at a couple things.
But to some extent, all the Sense ROMs seem to lag to some degree over time. Wiping cache may help. But most folks are able to live with it. What you are describing may or may not be something more serious. I don't personally get any freezing (presently on stock Dev Edition 6.12.1540, previously on S.ROM) but do seem some lag most prominently in waking/unlocking the screen, and for the home screen to populate with my widgets and apps.
Another thing you might try is a GPE based ROM.
Games use battery, that's just a fact of current smartphones.
The storage size of the game has little (if anything) to do with how much battery will be used. If it uses the CPU/GPU intensively, its going to suck down the battery. And game devs don't seem to be shy about this. I guess they assume that if you are gaming intensively, you are willing to live with the fact that you'll need to charge the phone frequently.
Every game is different, of course. But you'll see many (or even most) games will drain just about any phone or tablet's battery in a few hours.
Click to expand...
Click to collapse
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.28.502.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ********
(bootloader) imei: *********
(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
all: Done!
finished. total time: 0.074s
someone in this forum told me to try "http://forum.xda-developers.com/devdb/project/dl/?id=15489&task=get" this rom. He told me something that i dont really understand. I think what he said is relvant with HBoot.. I bought the phone factory unlocked btw
Are you doing a full wipe (user data, cache, Dalvik) before flashing each ROM. This is the "default" wipe in TWRP, and recommended.
Ryokan said:
C:\adb>fastboot getvar all
(bootloader) version-bootloader: 3.19.0.000
(bootloader) version-baseband: [email protected]
(bootloader) version-main: 4.28.502.1
Click to expand...
Click to collapse
Your firmware (main version) should be fine for running any of the current ROMs. I don't see anything obvious that could be "wrong", and no easy fix for what you are describing.
Ryokan said:
someone in this forum told me to try "http://forum.xda-developers.com/devdb/project/dl/?id=15489&task=get" this rom. He told me something that i dont really understand. I think what he said is relvant with HBoot.. I bought the phone factory unlocked btw
Click to expand...
Click to collapse
That is the stock ROM I'm using, full ROM thread here: http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
I don't have any serious issues. But as mentioned, there is some minor lag at times; but nothing I would personally consider a "deal breaker".
Not sure what the person may have referred to with hboot. Your hboot and other firmware are fine to run this ROM. I'm running it with Lollipop firmware, as well (just the Developer Edition LP firmware, instead of stock AT&T).
As I mentioned before, you may also try a GPE based ROM, to see if it runs any smoother for you (unless you are married to Sense ROMs by preference).
redpoint73 said:
Are you doing a full wipe (user data, cache, Dalvik) before flashing each ROM. This is the "default" wipe in TWRP, and recommended.
Your firmware (main version) should be fine for running any of the current ROMs. I don't see anything obvious that could be "wrong", and no easy fix for what you are describing.
That is the stock ROM I'm using, full ROM thread here: http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
I don't have any serious issues. But as mentioned, there is some minor lag at times; but nothing I would personally consider a "deal breaker".
Not sure what the person may have referred to with hboot. Your hboot and other firmware are fine to run this ROM. I'm running it with Lollipop firmware, as well (just the Developer Edition LP firmware, instead of stock AT&T).
As I mentioned before, you may also try a GPE based ROM, to see if it runs any smoother for you (unless you are married to Sense ROMs by preference).
Click to expand...
Click to collapse
I want this rom http://forum.xda-developers.com/htc...the-worlds-first100-m9-port-m8upload-t3064838 and i am sure after 2-3 weeks it will get slowed down somehow. I am wonderin am i doing it wrong? or am i flashing it with missing parts?
Ryokan said:
I want this rom http://forum.xda-developers.com/htc...the-worlds-first100-m9-port-m8upload-t3064838 and i am sure after 2-3 weeks it will get slowed down somehow. I am wonderin am i doing it wrong? or am i flashing it with missing parts?
Click to expand...
Click to collapse
There aren't any additional "parts" you need to flash with that ROM.
I'll ask again: Are you doing a full wipe (user data, cache, Dalvik) before flashing each ROM? This is the "default" wipe in TWRP, and recommended.
Related
Alright,
I recently rooted, S-Off'd, custom rom'd my Amaze for T-Mobile. The process went very smooth, as I've done this for several phones that I've owned in the past (Sensation, G2X, N1, G1).
I decided that I'd like to have an OC'd Kernel that would also allow for undervolting, and went with what appears to be the only Kernel offered on this device: Faux's123.
I flashed it through 4ext whilst on the Speed 6.5 rom, and ran some Quadrant and Antutu benches to see if it stuck, and it was awesome.
Now comes the problem, when I awoke yesterday, my phone was boot-looping. It did it from the moment I woke until 5 hours later when it died... I've done everything I can think of, or have read to remedy the situation. I've factory data reset it through 4ext, I've flashed new roms, I've flashed stock roms, I've tried my damnedest to flash a stock kernel (can't find one), I re-locked my bootloader.... nothing stops it from this continuous boot loop.....
Someone please help!
The craziest thing about it is, after about 90k boot loops, sometimes it settles, and works....until I unlock the screen, and bam, boot loops again.
dlamb4prez said:
Alright,
I recently rooted, S-Off'd, custom rom'd my Amaze for T-Mobile. The process went very smooth, as I've done this for several phones that I've owned in the past (Sensation, G2X, N1, G1).
I decided that I'd like to have an OC'd Kernel that would also allow for undervolting, and went with what appears to be the only Kernel offered on this device: Faux's123.
I flashed it through 4ext whilst on the Speed 6.5 rom, and ran some Quadrant and Antutu benches to see if it stuck, and it was awesome.
Now comes the problem, when I awoke yesterday, my phone was boot-looping. It did it from the moment I woke until 5 hours later when it died... I've done everything I can think of, or have read to remedy the situation. I've factory data reset it through 4ext, I've flashed new roms, I've flashed stock roms, I've tried my damnedest to flash a stock kernel (can't find one), I re-locked my bootloader.... nothing stops it from this continuous boot loop.....
Someone please help!
Click to expand...
Click to collapse
Flash a Stock RUU, just get the one for your carrier in Krook6023's thread. Make sure you get the RUU, not the OTA.
Or if you're lazy, use this tool that I made.. http://forum.xda-developers.com/showthread.php?t=1762936
Downloading your tool now, but DevHost? Sooooo slow lol! I guess beggars can't be choosers!
2 hours from now is wayyyy better than an indefinite period of time for a fix lol.
Will let you know as soon as it's done.
Keylogger_0 said:
Flash a Stock RUU, just get the one for your carrier in Krook6023's thread. Make sure you get the RUU, not the OTA.
Or if you're lazy, use this tool that I made.. http://forum.xda-developers.com/showthread.php?t=1762936
Click to expand...
Click to collapse
dlamb4prez said:
Downloading your tool now, but DevHost? Sooooo slow lol! I guess beggars can't be choosers!
2 hours from now is wayyyy better than an indefinite period of time for a fix lol.
Will let you know as soon as it's done.
Click to expand...
Click to collapse
Really? I've never thought devhost as a slow source.
I downloaded ruu and put on 3 flash drives my external and my sd
Sent from my Energized Amaze 4G
Yes girls know about XDA
you can thank a girl on here
Keylogger_0 said:
Really? I've never thought devhost as a slow source.
Click to expand...
Click to collapse
sometimes it is... right now, i get 600kbytes/s, but at night, maybe 60-100kbytes/s... my top speed on speedtest.net is roughly 20MBit/s = 2.5mbytes/s
paperWastage said:
sometimes it is... right now, i get 600kbytes/s, but at night, maybe 60-100kbytes/s... my top speed on speedtest.net is roughly 20MBit/s = 2.5mbytes/s
Click to expand...
Click to collapse
Speed test may show 20mbps but the actual download speed is actually around 2mbps tops, for every 1mbps bandwidth speed the avg download speed is around 100kbps (more or less), so don't be fooled by speedtest, that just tells you what your bandwidth speed is, not actual download speed.
On the op question, just use keylogger's tool and restore to stock, you'll need to unlock your bootloader back for it to work, also for the custom kernel to work and avoid any bootloops, simply go in to the governor and choose either one of two things, a governor that uses regular voltages or one that doesn't OC too high, those two are the main causes of bootlooping and crashes on custom kernels, some devices can't handle one or the other or some times both.
I guess I'm just having the worst luck in the world right now....
After unzipping the ToolV2.zip file using WinRar, I double click on the RUN-ME.exe file, and get an error......
It says that it is NOT compatible with my version of Windows. I have to have a 32 or 64 bit version.... I have Windows 7 Ultimate 32-bit.... WTF!
Dark Nightmare said:
Speed test may show 20mbps but the actual download speed is actually around 2mbps tops, for every 1mbps bandwidth speed the avg download speed is around 100kbps (more or less), so don't be fooled by speedtest, that just tells you what your bandwidth speed is, not actual download speed.
On the op question, just use keylogger's tool and restore to stock, you'll need to unlock your bootloader back for it to work, also for the custom kernel to work and avoid any bootloops, simply go in to the governor and choose either one of two things, a governor that uses regular voltages or one that doesn't OC too high, those two are the main causes of bootlooping and crashes on custom kernels, some devices can't handle one or the other or some times both.
Click to expand...
Click to collapse
dlamb4prez said:
I guess I'm just having the worst luck in the world right now....
After unzipping the ToolV2.zip file using WinRar, I double click on the RUN-ME.exe file, and get an error......
It says that it is NOT compatible with my version of Windows. I have to have a 32 or 64 bit version.... I have Windows 7 Ultimate 32-bit.... WTF!
Click to expand...
Click to collapse
My apologies. That must be an error on my side. I've recompiled it with a 32 bit compiler. I plan to do a complete rebuild though.
Instructions:
Extract the zip file with your favorite file extraction utility.
Replace the RUN-ME.exe file with the 32 bit version, which can be found attached on this post.
Run the file as you normally would, and follow my directions posted on the thread.
And as the other poster said, make sure you're bootloader unlocked.
Thanks for all of the help!
Ran into another problem though, whilst running the program, it now tells me that my device is not S-Off, when Hboot clearly says so... I did the wire trick and all. Not sure, what the problem is now!
Could it be that this problem is derivative of the fact that my Hboot is locked?
Keylogger_0 said:
My apologies. That must be an error on my side. I've recompiled it with a 32 bit compiler. I plan to do a complete rebuild though.
Instructions:
Extract the zip file with your favorite file extraction utility.
Replace the RUN-ME.exe file with the 32 bit version, which can be found attached on this post.
Run the file as you normally would, and follow my directions posted on the thread.
And as the other poster said, make sure you're bootloader unlocked.
Click to expand...
Click to collapse
dlamb4prez said:
Thanks for all of the help!
Ran into another problem though, whilst running the program, it now tells me that my device is not S-Off, when Hboot clearly says so... I did the wire trick and all. Not sure, what the problem is now!
Could it be that this problem is derivative of the fact that my Hboot is locked?
Click to expand...
Click to collapse
It shouldn't be, as the script detects your S-Off state by doing the command fastboot getvar security.
It wouldn't matter if your device was locked or not. Apparently to the tool, it thinks your phone is S-On.
This is strange. Here's what I want you to do.
Click on the ToolV2 folder (don't go in that folder however), then while holding shift, right click. There should be an option that says "Open command window here"
After you've done that, it will automatically open command prompt, routed to that folder. While in that command prompt window, type in "fastboot getvar all" without quotes (Ensure your phone is booted into fastboot mode first! Also make sure your phone is connected too!)
After you typed it, press enter. The results should show up.
What I want you to do is take a screenshot of that command prompt window. (You can do this with the windows' snipping tool) And attach it. I will look at it and try to figure out.
This is what I got:
C:\Users\Don\Desktop\ToolV2>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.93.0002
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.531.1
(bootloader) serialno: SH23PVP01066
(bootloader) imei: 358927046036465
(bootloader) product: ruby
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH8511000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3730mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6298f8f6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.505s
Keylogger_0 said:
It shouldn't be, as the script detects your S-Off state by doing the command fastboot getvar security.
It wouldn't matter if your device was locked or not. Apparently to the tool, it thinks your phone is S-On.
This is strange. Here's what I want you to do.
Click on the ToolV2 folder (don't go in that folder however), then while holding shift, right click. There should be an option that says "Open command window here"
After you've done that, it will automatically open command prompt, routed to that folder. While in that command prompt window, type in "fastboot getvar all" without quotes (Ensure your phone is booted into fastboot mode first! Also make sure your phone is connected too!)
After you typed it, press enter. The results should show up.
What I want you to do is take a screenshot of that command prompt window. (You can do this with the windows' snipping tool) And attach it. I will look at it and try to figure out.
Click to expand...
Click to collapse
dlamb4prez said:
This is what I got:
C:\Users\Don\Desktop\ToolV2>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.93.0002
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.531.1
(bootloader) serialno: SH23PVP01066
(bootloader) imei: 358927046036465
(bootloader) product: ruby
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH8511000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3730mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6298f8f6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.505s
Click to expand...
Click to collapse
Then you should not get an error relating to your S-Off state. It states that your security state is off, which is normal for S-Off. Are you sure you don't have any other phones connected? I know this is a silly question, but I'm not sure how you're getting that problem
Do this command "fastboot getvar security"
It should just display this:
(bootloader) security: off
My script was designed to read that statement and detect whether it says off or not. For some reason, it's not detecting that phrase, "off".
As I said, I plan to do a rewrite. This tool still should work nonetheless.
After the ota update to 4.4.2, my phone will only let me make 1 or 2 calls when on 4g and then I can no longer make/receive any calls (until I remove the sim card or sometimes just resetting the radio or clearing the dialer app data then maybe I'll get another call or 2 if I'm lucky).
I'm looking for any help or suggestions. I'm stock, S-On, etc. I've already tried a hard reset... I also reflashed the ota firmware, but had no change.
I found a temporary fix by changing to "gsm only" in the *#*#4636#*#* menu. However, that resets every reboot, and I don't want to be stuck on edge forever.
I would prefer to stay stock, S-On, but I'll take any suggestions...
Thanks in advance
In case it is helpful:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxx
(bootloader) imei: xxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4270mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
UPDATE: I have a few more details: I tried to call my phone, LTE turns off (which is normal), but it never rings then the 4g icon disappears for a minute like it crashed somehow.
Well without achieving s off you are limited to running the ruu for your device. I suggest doing that first and if that don't help you might want to look Into s off for you can flash whatever you want.
"Coming to you live from my Straight Talk LTE One"
enigma2446 said:
Well without achieving s off you are limited to running the ruu for your device. I suggest doing that first and if that don't help you might want to look Into s off for you can flash whatever you want.
"Coming to you live from my Straight Talk LTE One"
Click to expand...
Click to collapse
I ran the ruu for the 4.18.502.7, but there was no change. Do you think there is any chance that it'll work if I flash something different, or is it a hardware issue?
As far as flashing is concerned: I've only done it before on my Galaxy S2 and it was fairly easy/straight-forward. Would you say it's the same for this phone? And is it easy to return to stock when I'm ready to trade-in?
G8trBryant said:
I ran the ruu for the 4.18.502.7, but there was no change. Do you think there is any chance that it'll work if I flash something different, or is it a hardware issue?
As far as flashing is concerned: I've only done it before on my Galaxy S3 and it was fairly easy/straight-forward. Would you say it's the same for this phone? And is it easy to return to stock when I'm ready to trade-in?
Click to expand...
Click to collapse
After u run RUU you must do a Factory Reset* or phone reset from stock recovery or setting
This will reset your radios and every setting to factory state.
finanandroid said:
After u run RUU you must do a Factory Reset* or phone reset from stock recovery or setting
This will reset your radios and every setting to factory state.
Click to expand...
Click to collapse
Still no luck. I think the ruu did a complete wipe too, but I tried anyways.
I have a few more details: I tried to call my phone, LTE turns off (which is normal), but it never rings then the 4g icon disappears for a minute like it crashed somehow.
G8trBryant said:
Still no luck. I think the ruu did a complete wipe too, but I tried anyways.
I have a few more details: I tried to call my phone, LTE turns off (which is normal), but it never rings then the 4g icon disappears for a minute like it crashed somehow.
Click to expand...
Click to collapse
easy way..... get a new SIM Card*
Hey everyone! I'm having issues booting my phone up. It might be bricked because one night my phone was working and the next morning it wouldn't boot at all after having not made any changes. I've messed around with it a lot, installing and wiping things. Anyway, I'd just like to make sure I've exhausted all attempts at getting the thing to boot again.
I am S-On, and have tried to use rumrunner to get s-off but was getting an error saying no adb connection. I wasn't able to turn off fastboot as instructed since I can't boot, but I have been able to run some adb commands. I get error: device not found sometimes and error: closed others. I have been using the windroid toolkit. I have tried running the ruu exe (yes, I first relocked) but got an error 155 and my bootloader said "HBoot Version is older!" I have installed several OTA roms and they seem to install properly through the recovery (I have been using TWRP, CWM and amonRa) but then do not make it to home screen. I had some progress where I was initially getting stuck at the white HTC screen, after flashing a kernel, I think it was, I made it to the 4G LTE screen but then it hung up there.
Hmm, I've done a lot of searching and trying things, but hopefully yall can help! I appreciate your efforts either way
Here are my getvars from fastboot
(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:
(bootloader) product: vigor
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH9810000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4144mV
(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.498s
Thanks!
JMBush1007 said:
Hey everyone! I'm having issues booting my phone up. It might be bricked because one night my phone was working and the next morning it wouldn't boot at all after having not made any changes. I've messed around with it a lot, installing and wiping things. Anyway, I'd just like to make sure I've exhausted all attempts at getting the thing to boot again.
I am S-On, and have tried to use rumrunner to get s-off but was getting an error saying no adb connection. I wasn't able to turn off fastboot as instructed since I can't boot, but I have been able to run some adb commands. I get error: device not found sometimes and error: closed others. I have been using the windroid toolkit. I have tried running the ruu exe (yes, I first relocked) but got an error 155 and my bootloader said "HBoot Version is older!" I have installed several OTA roms and they seem to install properly through the recovery (I have been using TWRP, CWM and amonRa) but then do not make it to home screen. I had some progress where I was initially getting stuck at the white HTC screen, after flashing a kernel, I think it was, I made it to the 4G LTE screen but then it hung up there.
Hmm, I've done a lot of searching and trying things, but hopefully yall can help! I appreciate your efforts either way
Here are my getvars from fastboot
(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:
(bootloader) product: vigor
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH9810000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4144mV
(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.498s
Thanks!
Click to expand...
Click to collapse
You need to get it bootable before you can S-OFF with Rumrunner... Unlock the bootloader again, boot or flash your recovery of choice (TWRP/PhilZ/CWM), wipe EVERYTHING thoroughly, at least 3 times, then flash in Tachyon to get it up and working (if you flashed the recovery and started it from the phone, remember to manually push the boot.img with fastboot). Give it time to boot, the first boot can take 10+ minutes in some cases. Once it is booted and stable, then you can try to S-OFF again.
acejavelin said:
You need to get it bootable before you can S-OFF with Rumrunner... Unlock the bootloader again, boot or flash your recovery of choice (TWRP/PhilZ/CWM), wipe EVERYTHING thoroughly, at least 3 times, then flash in Tachyon to get it up and working (if you flashed the recovery and started it from the phone, remember to manually push the boot.img with fastboot). Give it time to boot, the first boot can take 10+ minutes in some cases. Once it is booted and stable, then you can try to S-OFF again.
Click to expand...
Click to collapse
Hi acejavelin, thanks for the reply!
So, I was finally able to get it to boot again.. I put evervolv on it and then ran rumrunner once I had it booted. After running and getting most of the way through rumrunner, I got stuck in another boot loop. It seemed like rumrunner corrupted it or something. I couldn't it to book back up at that point, but I am now showing s-off! Not sure if it's possible to be halfway s-off or showing s-off but not, but the rumrunner never finished it got to pouring (2)... so I don't know.
Right now, I have evervolv on again (after trying many others) and it seems to be somewhat stable. I'm thinking I have a hardware issue. Something seems to be faulty and only working half the time. I tried a few different RUUs, OTA global rooted roms, etc.. Tachyon, cleanrom 4.5 pro, plain andy, carbon, etc. I have also been using Cleanwipe 10x before flashing new roms. Everything is unstable, so unfortunately, like I said, it seems to be hardware.
I have another rezound that has a bad ESN because I thought it was stolen, til I found it months later. It looks difficult, but possible to change the ESN.. I was thinking I could just switch the ESN and MEIDs and use the other phone? Any other suggestions on how to isolate the issue or find some stability would be very much appreciated. Thanks for the help!
Glad you got your answer! Also, cloning your IMEI and ESN is illegal and a major criminal offense. I suggest you don't go down that route.
JMBush1007 said:
Hi acejavelin, thanks for the reply!
So, I was finally able to get it to boot again.. I put evervolv on it and then ran rumrunner once I had it booted. After running and getting most of the way through rumrunner, I got stuck in another boot loop. It seemed like rumrunner corrupted it or something. I couldn't it to book back up at that point, but I am now showing s-off! Not sure if it's possible to be halfway s-off or showing s-off but not, but the rumrunner never finished it got to pouring (2)... so I don't know.
Right now, I have evervolv on again (after trying many others) and it seems to be somewhat stable. I'm thinking I have a hardware issue. Something seems to be faulty and only working half the time. I tried a few different RUUs, OTA global rooted roms, etc.. Tachyon, cleanrom 4.5 pro, plain andy, carbon, etc. I have also been using Cleanwipe 10x before flashing new roms. Everything is unstable, so unfortunately, like I said, it seems to be hardware.
I have another rezound that has a bad ESN because I thought it was stolen, til I found it months later. It looks difficult, but possible to change the ESN.. I was thinking I could just switch the ESN and MEIDs and use the other phone? Any other suggestions on how to isolate the issue or find some stability would be very much appreciated. Thanks for the help!
Click to expand...
Click to collapse
The result you got with rumrunner is very common, not sure exactly what it corrupts (probably the boot partition) but it is common to for it to freeze/bootloop after going S-OFF, as long as it's S-OFF in the bootloader, it is S-OFF... there is no "kinda S-OFF". Just restore the backup you did before running rumrunner (you did a Nandroid first, right ) or reflash your ROM and Gapps, no worries, this is kinda normal.
As far as the "most stable" ROM, this seems to vary a lot on the person, configuration/apps, ROM, and hardware build, some ROMs are better than others under various conditions and trial and error is the only real way to find out. Some Rezounds just do not like KitKat, others don't like JellyBean, etc... so if are having lots of issues with one, try a different one. A few ROMs you didn't mention that I think are very good on the Rezound are EclipticRez Revamped v9 (this is the most stable non-stock ROM I tried) and Nils Business Sense that are both ICS based, Beanstalk and Talon are two really good under-rated JellyBean ROMs just remember that some JB ROMs can swap your internal and external storage around in mounts (they appear swapped when the phone is booted, this is not really a bug if you see it). But to be honest, if you are flashing http://forum.xda-developers.com/showthread.php?t=2260154 or gone through @REV3NT3CH's full downgrade/upgrade guide and are still having issues, it could very well be hardware issues.
And yes, @kcipopnevets is correct... ESN/MEID swapping is illegal, although I don't know how much of a "major criminal offense" it is. But generally it is considered fraudulent activity and a violation of your terms of service on your cellular plan as well.
Hey Guys -
After being an iPhone fanboy for a while, i wanted a change so got an HTC One (M7 - AT&T) a few months ago. Since then, I've tried a couple of ROMS and liked ViperONE the best. Recently, I decided to completely redo my phone because:
- I had too much crap on my phone
- A new major ROM version (7) was released
- My signal strength seemed to be ~30% lower than usual at work and home - didn't know why
In hopes that the result would be the updated ROM with all other files/folders from the emulated SD gone, I downloaded the RUU I thought matched and applied it. Once done, I applied the new ViperONE 7.0 ROM for HTCOne then proceeded to root and get all apps installed and configured.
The next day, i found out that when I launched the phone app, it immediately quit. ARGH! I also can't receive calls. I wouldn't think this would be a ROM issue as the phone app would hopefully be the first thing they test. Therefore I am deciding to stick with the same ROM team since I like it so much.
So... this time around, I did a bit more research and am posting before doing anything to make sure I'm doing everything correctly or with the best chance of success. Below are details about my phone as well as the plan I currently have...
Phone Specifications via Recovery Menu + FastBoot Command
- Below specs noted before I had issues -
*** UNLOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-CWS__001
HBOOT-1.55.0000
RADIO-4A.19.3263.13
OpenDSP-v31.120.274.0617
OS-
eMMC-boot 2048MB
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT*********
(bootloader) imei: **************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3909mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Proposed Steps to Fix / Re-flash
1. Back up everything on phone (done)
2. Download following: (done)
- Newest TWRP img
- Guru Reset 5.12.502.2
- Stock Firmware stock firmware 5.12.502.2 (Just in case)
- Newest ViperONE (7.0.1) ROM for M7
3. Copy Guru Reset 5.12.502.2 to phone's root and install via TWRP in Recovery
I've never used Guru Reset before so don't know what state the phone will be in afterwards. If prompted to keep my root, should I or should I really go ahead and start all over? Depending on what the result is after that, I'd then re-root if need be then go back into recovery and flash ViperONE ROM.
Is that a good plan? If there's anything else you think may be a good idea to also add in or try (especially anything that may have a chance of fixing the radio) would be great - Thanks!
PS: I've seen online that I'm not the only one who has a "purple haze" on my M7's camera. While doing all the above, any suggestions for how any fix may be applied or is it a hardware issue? Thanks!
bzowk said:
Hey Guys -
After being an iPhone fanboy for a while, i wanted a change so got an HTC One (M7 - AT&T) a few months ago. Since then, I've tried a couple of ROMS and liked ViperONE the best. Recently, I decided to completely redo my phone because:
- I had too much crap on my phone
- A new major ROM version (7) was released
- My signal strength seemed to be ~30% lower than usual at work and home - didn't know why
In hopes that the result would be the updated ROM with all other files/folders from the emulated SD gone, I downloaded the RUU I thought matched and applied it. Once done, I applied the new ViperONE 7.0 ROM for HTCOne then proceeded to root and get all apps installed and configured.
The next day, i found out that when I launched the phone app, it immediately quit. ARGH! I also can't receive calls. I wouldn't think this would be a ROM issue as the phone app would hopefully be the first thing they test. Therefore I am deciding to stick with the same ROM team since I like it so much.
So... this time around, I did a bit more research and am posting before doing anything to make sure I'm doing everything correctly or with the best chance of success. Below are details about my phone as well as the plan I currently have...
Phone Specifications via Recovery Menu + FastBoot Command
- Below specs noted before I had issues -
*** UNLOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-CWS__001
HBOOT-1.55.0000
RADIO-4A.19.3263.13
OpenDSP-v31.120.274.0617
OS-
eMMC-boot 2048MB
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT*********
(bootloader) imei: **************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3909mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Proposed Steps to Fix / Re-flash
1. Back up everything on phone (done)
2. Download following: (done)
- Newest TWRP img
- Guru Reset 5.12.502.2
- Stock Firmware stock firmware 5.12.502.2 (Just in case)
- Newest ViperONE (7.0.1) ROM for M7
3. Copy Guru Reset 5.12.502.2 to phone's root and install via TWRP in Recovery
I've never used Guru Reset before so don't know what state the phone will be in afterwards. If prompted to keep my root, should I or should I really go ahead and start all over? Depending on what the result is after that, I'd then re-root if need be then go back into recovery and flash ViperONE ROM.
Is that a good plan? If there's anything else you think may be a good idea to also add in or try (especially anything that may have a chance of fixing the radio) would be great - Thanks!
PS: I've seen online that I'm not the only one who has a "purple haze" on my M7's camera. While doing all the above, any suggestions for how any fix may be applied or is it a hardware issue? Thanks!
Click to expand...
Click to collapse
The Guru Reset would put you back at stock if you so choose. You are given the option in Aroma to "root", chose that option since you are going on to flash ViperOne.
The Guru Reset should have the same firmware in Aroma check that you want the stock radio this will help in ViperOne. I believe the issue you had earlier was the result of incompatible firmware/radio.
Purple haze issue is more likely hardware, but there has been a lot of pseudo fixes.
Thanks for your reply! Just finished backup so starting on it now. Wish me luck!
OK - Already have a small question...
I started the Guru flash and went through the first couple of screens. On the "What to flash," it gives me the option to perform "Stock Recovery" and/or "Radio." I wanted to flash Radio due to my errors - but - on this screen it describes Radio as "Version 4M.27.3218.14 - Original Radio from the Stock ROM."
My phone, however, had the Radio listed as "4A.19.3263.13." Is this still ok or no? The Guru Flash I'm using is "Guru_Reset_M7_5.12.502.2_clsA"
I plan to stay at this screen for a few minutes so that hopefully I'll have a reply by then.
Thanks Again!
bzowk said:
OK - Already have a small question...
I started the Guru flash and went through the first couple of screens. On the "What to flash," it gives me the option to perform "Stock Recovery" and/or "Radio." I wanted to flash Radio due to my errors - but - on this screen it describes Radio as "Version 4M.27.3218.14 - Original Radio from the Stock ROM."
My phone, however, had the Radio listed as "4A.19.3263.13." Is this still ok or no? The Guru Flash I'm using is "Guru_Reset_M7_5.12.502.2_clsA"
I plan to stay at this screen for a few minutes so that hopefully I'll have a reply by then.
Thanks Again!
Click to expand...
Click to collapse
The radio (4A) is the older radio the newer version is 4M. Like I mentioned before you want to the new radio to try to solve your communication issues. Sorry for the late reply but I don't monitor this site.
majmoz said:
The radio (4A) is the older radio the newer version is 4M. Like I mentioned before you want to the new radio to try to solve your communication issues. Sorry for the late reply but I don't monitor this site.
Click to expand...
Click to collapse
Hey - I toitally understand. I just appreciate that you replied when you did. After reading your message, I had an idea. Perhaps the Phone app wouldn't open because the Radio was on such an old build. I went ahead and downloaded the newest compatible radio I could find - 4T.24.3218.09 from here. I booted to Recovery then applied the radio alone.
After reboot, it worked! I can now get into my Phone app! Since I've already set this build up, I think I'll leave it for now.
I learned a lot about radios today - Thanks again for your help!
bzowk said:
Hey - I toitally understand. I just appreciate that you replied when you did. After reading your message, I had an idea. Perhaps the Phone app wouldn't open because the Radio was on such an old build. I went ahead and downloaded the newest compatible radio I could find - 4T.24.3218.09 from here. I booted to Recovery then applied the radio alone.
After reboot, it worked! I can now get into my Phone app! Since I've already set this build up, I think I'll leave it for now.
I learned a lot about radios today - Thanks again for your help!
Click to expand...
Click to collapse
You are welcome, glad that you are back up and running! :good:
bzowk said:
Hey Guys -
After being an iPhone fanboy for a while, i wanted a change so got an HTC One (M7 - AT&T) a few months ago. Since then, I've tried a couple of ROMS and liked ViperONE the best. Recently, I decided to completely redo my phone because:
- I had too much crap on my phone
- A new major ROM version (7) was released
- My signal strength seemed to be ~30% lower than usual at work and home - didn't know why
In hopes that the result would be the updated ROM with all other files/folders from the emulated SD gone, I downloaded the RUU I thought matched and applied it. Once done, I applied the new ViperONE 7.0 ROM for HTCOne then proceeded to root and get all apps installed and configured.
The next day, i found out that when I launched the phone app, it immediately quit. ARGH! I also can't receive calls. I wouldn't think this would be a ROM issue as the phone app would hopefully be the first thing they test. Therefore I am deciding to stick with the same ROM team since I like it so much.
So... this time around, I did a bit more research and am posting before doing anything to make sure I'm doing everything correctly or with the best chance of success. Below are details about my phone as well as the plan I currently have...
Phone Specifications via Recovery Menu + FastBoot Command
- Below specs noted before I had issues -
*** UNLOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-CWS__001
HBOOT-1.55.0000
RADIO-4A.19.3263.13
OpenDSP-v31.120.274.0617
OS-
eMMC-boot 2048MB
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT*********
(bootloader) imei: **************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3909mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Proposed Steps to Fix / Re-flash
1. Back up everything on phone (done)
2. Download following: (done)
- Newest TWRP img
- Guru Reset 5.12.502.2
- Stock Firmware stock firmware 5.12.502.2 (Just in case)
- Newest ViperONE (7.0.1) ROM for M7
3. Copy Guru Reset 5.12.502.2 to phone's root and install via TWRP in Recovery
I've never used Guru Reset before so don't know what state the phone will be in afterwards. If prompted to keep my root, should I or should I really go ahead and start all over? Depending on what the result is after that, I'd then re-root if need be then go back into recovery and flash ViperONE ROM.
Is that a good plan? If there's anything else you think may be a good idea to also add in or try (especially anything that may have a chance of fixing the radio) would be great - Thanks!
PS: I've seen online that I'm not the only one who has a "purple haze" on my M7's camera. While doing all the above, any suggestions for how any fix may be applied or is it a hardware issue? Thanks!
Click to expand...
Click to collapse
Theirs one big Flaw in your method DO NOT SKIP from 3.x firmware to 5.x firmware .. you'll end up in QHSUSB_DLOAD mode and that's No fun at all.
The correct way to get to the 5.x firmware is
3.x.502 RUU to 4.x.502 Firmware to 5.x.502 firmware
then the Guru reset
im one of the ones that took the last OTA 2.95.651.6 that cant use the htcdev unlock... I get a response that it worked but I never get the accept on my phone. I am also stuck in a bootloop right after the sprint logo so I cant even verify if oem unlock or debugging are on...
Ive tried every ruu I could find for any 3d and all of them fail for different reason. The only fix I am aware of is applying the ota again but as far as I know that was never released... Any ideas? Im not afraid of braking it as its a funny looking paperweight right now...
Please let me know if you find any solution or working ROM, I tried all the links and they are all down
Koncrete said:
im one of the ones that took the last OTA 2.95.651.6 that cant use the htcdev unlock... I get a response that it worked but I never get the accept on my phone. I am also stuck in a bootloop right after the sprint logo so I cant even verify if oem unlock or debugging are on...
Ive tried every ruu I could find for any 3d and all of them fail for different reason. The only fix I am aware of is applying the ota again but as far as I know that was never released... Any ideas? Im not afraid of braking it as its a funny looking paperweight right now...
Click to expand...
Click to collapse
I just got a pure stock sprint 3vo already on that OTA version and had no issues with the htcdev unlock. I had to use it to root and get the MSL, or at least kinda needed it and Sprint had no interest in giving it to me without an active account.
have you been using the window$ .exe RUUs or the PG86IMG.zip files you put on the root of the sdcard before starting the phone to the bootloader? I've had better luck with the .zip files (well, honestly, I've never run a window$ RUU except in a virtual machine just to extract the zip anyway.)
when you flash the RUU from sdcard, you get error messages on screen (if any) which likely make more sense than whatever the .exe might spit out.
perhaps I can help, though I'm not on the forums a lot these days. PMs should pop up in my email to get my attention, but any tech support I'll respond in the thread so others can benefit from the info.
I also have a functional USPS mailbox for more serious debugging, I feel that I'm fairly honest and already have a plethora of other phones anyway (I believe 2 functioning Virgin 3vos and now one Sprint branded one have joined my collection of Android hacking-at toys.)
imraxy said:
Please let me know if you find any solution or working ROM, I tried all the links and they are all down
Click to expand...
Click to collapse
a lot of the external hosting sites have gone belly-up, or worse, like androidfilehost, they deleted everything old. I lost tons of files when they decided to purge with absolutely no warning and all I can figure out is that it had something to do with the age of the uploads, because it wasn't just my files that went AWOL.
for working ROMs, there's some older ones here and more goodies here (RUUs)
and the last LiquidSmooth kitkat is here
bear in mind you may have to find the original ROM threads for the archived ones above to know which HBOOT (and maybe even radio) you need to use for each. the 3vo is picky about those.
the mods hopefully won't get uppity about me cross-forum posting, since they already destroyed the organization of the evo 3d forum here by combining general threads with both of the entire CDMA and GSM development subforums at some point in time I missed seeing until it was too late.
for the 3d forum here, this thread is particularly useful.
Evo3d(CDMA)HBoot/S-off Differences & Rooting Background Info 10-13-12
this post here (linked from inside the one just above) has all the HBOOT zip files too.
Koncrete said:
im one of the ones that took the last OTA 2.95.651.6 that cant use the htcdev unlock... I get a response that it worked but I never get the accept on my phone. I am also stuck in a bootloop right after the sprint logo so I cant even verify if oem unlock or debugging are on...
Ive tried every ruu I could find for any 3d and all of them fail for different reason. The only fix I am aware of is applying the ota again but as far as I know that was never released... Any ideas? Im not afraid of braking it as its a funny looking paperweight right now...
Click to expand...
Click to collapse
you should also be able to see if it's unlocked or not in the bootloader itself in the text at the top of the screen. It'll say locked or unlocked. if it's unlocked but s-on, RUUs will fail to install.
if so, put it in fastboot from the bootloader and
fastboot oem lock
then it should accept the current RUU to match the OTA you took.
So as the phone sits now it hangs at the Sprint logo until the battery runs out or I reset it.
it is S-ON and Locked......
I cannot verify if debugging is enabled (Pretty sure it isnt)
Bootloader unlock.bin command says its successfully sent the unlock file from HTCdev with a sending time of 0.0, The dialog never shows on my phone to unlock and the bar on the right that is supposed to show the status of updates and such never comes on
Ive tried relocking and then unlocking
Ive tried from win7 32/64 os's and windows 10 64.
Ive also done this using USB 2.0, 3.0 and 3.1 slots as well as others.
I've used a known good samsung cable and a couple of off brand cables
Ive tried with and without the fastboot registry fix for HTC and mixes of fastboot/adb from everywhere
Koncrete said:
So as the phone sits now it hangs at the Sprint logo until the battery runs out or I reset it.
it is S-ON and Locked......
I cannot verify if debugging is enabled (Pretty sure it isnt)
Bootloader unlock.bin command says its successfully sent the unlock file from HTCdev with a sending time of 0.0, The dialog never shows on my phone to unlock and the bar on the right that is supposed to show the status of updates and such never comes on
Ive tried relocking and then unlocking
Ive tried from win7 32/64 os's and windows 10 64.
Ive also done this using USB 2.0, 3.0 and 3.1 slots as well as others.
I've used a known good samsung cable and a couple of off brand cables
Ive tried with and without the fastboot registry fix for HTC and mixes of fastboot/adb from everywhere
Click to expand...
Click to collapse
I've never used windows to flash an HTC, but if you downloaded fastboot from htcdev and their chunk of junk software that contains the drivers (htc sync or something, I forget) that part shouldn't matter (maybe)
you can get to the bootloader, so the phone isn't bricked.
to test the cable, you could try "fastboot getvar all" and see if there's output.
definitely no USB3 from what I've read, the phone predates that being in common use and the unlimited.io wire trick instructions say it's a no-no, they suggest the stock HTC cable too, but I used a solid offbrand cable to s-off, so the cable's not critical as long as its communicating.
try this RUU from here
put it on sdcard named PG86IMG.zip and put the phone into the bootloader (volume down while powering on.)
That'll at least get Windows out of the equation.
AndroidForums said:
How to use a PG86IMG.zip file!
SPOILER
1. Place the file on the root of your sd card (not in any folders).
2. Rename the file to PG86IMG.zip
3. Reboot into bootloader.
4. When asked to update, say yes by hitting volume up.
5. When it's all finished, hit power button to reboot.
7. *Important! After booting up, immediately rename or delete the file.
Click to expand...
Click to collapse
Let me know if that errors out or something. It's the best way to flash an RUU.
Main version is older....
[15:47:25] (bootloader) version: 0.5
[15:47:25] (bootloader) version-bootloader: 1.58.0000
[15:47:25] (bootloader) version-baseband: 1.09.00.0108
[15:47:25] (bootloader) version-cpld: None
[15:47:25] (bootloader) version-microp: None
[15:47:25] (bootloader) version-main: 2.95.651.6
[15:47:25] (bootloader) serialno:
[15:47:25] (bootloader) imei:
[15:47:25] (bootloader) product: shooter
[15:47:25] (bootloader) platform: HBOOT-8260
[15:47:25] (bootloader) modelid: PG8610000
[15:47:25] (bootloader) cidnum: SPCS_001
[15:47:25] (bootloader) battery-status: good
[15:47:25] (bootloader) battery-voltage: 3800mV
[15:47:25] (bootloader) partition-layout: Generic
[15:47:25] (bootloader) security: on
[15:47:25] (bootloader) build-mode: SHIP
[15:47:25] (bootloader) boot-mode: FASTBOOT
[15:47:25] (bootloader) commitno-bootloader: dirty-3f645641
[15:47:25] (bootloader) hbootpreupdate: 11
[15:47:25] (bootloader) gencheckpt: 0
ive tried running it from recovery for funz as well an I get "Invalid operation" oem=00
hm, maybe my sprint 3vo let me flash that because it's s-off , but if you can't even get it to flash that RUUzip off the sdcard with the bootloader, all I can think of is digging into the unbrick thread and getting creative.
or replacing it with a cheapie off ebay, my sprint model was under $7 shipped from eBay and moving the main board into one with a good screen...
within the week I intend to post a lineage 11 kitkat current build so the browser works on https, unlike any of the vintaged roms which are still downloadable, if you want incentive.
if you give up on yours, I'm game to poke at it, rather than it going in the refuse...
I've got some experience with this phone and reviving uppity devices.
I even work at an Apple repair shop for service credibility (and certified, though Apple really sucks, it's still a tech job.)
Honestly, I just dont like that it isnt working....
I have real use for it, just wanted to get it working to play with it. Its in REALLY poor condition. It was stolen from me twice and the second time it was damaged but still operational. I am pretty sure what I need to recover it is the final 2.95.651.6 from Sprint that isn't anywhere I can find online and as you said, customer service isnt very....helpful....
Now I saw the ruu unpacking thread and I wonder if a ruu could be built with the correct version all
with it locked and s-on any ruu will have to be signed by htc to install.
I'm fresh out of ideas. since all my 3vos but the one I just got are virgin mobile branded, most of my stored files are for that, the only sprint ruu files I've found yet are in the Android forums link.
and I didn't look very hard, since mine went s-off super easy on the very first tickle with the wire trick and I can install any ruu I want.
if you're desperate enough, maybe taking it s-off would allow you to flash an older ruu. if it'll s-off in its current condition. it's supposed to be unlocked for that and on stock rom.
the unlimited.io pages for the wire trick are gone, but they live on through the Wayback Machine (Internet Archive) including download links.
did you try using the stock recovery which should be on yours and do a factory reset through there?
That's the error I get going into recovery and the results from that factory reset...
My stuff is never easy to fix lol if I'mma have an issue it's gonna be complicated ?
can you get a picture of the hboot screen?
It's from fastboot menu but the tops the same
one more thing, can you
fastboot getvar all
I hate to give up on something like this where it's only soft bricked. still boots to the bootloader, and still has fastboot.
it clearly didn't unlock though, like you said.
also a thought:
have you tried retrieving the
fastboot oem get_identifier_token
again and getting a fresh download of the unlock token from htc? maybe the one you have got corrupted.
and since you're dealing with Micro$oft, you might have to uninstall all the htc drivers and install the htc sync program for the 3d to get the correct one. it sounds like you've been playing with a lot of modifications.
ubuntu live cd might be worth a try, there's no nonsense about device drivers in ubuntu for android phones.
I have gotten the unlock token 6 times now I've tried from win7 and win10, Kali Linux, FWUL, and from android to android (I have adb on my essential) I can try Ubuntu live though, won't hurt to try....
I was looking for a good copy of the urt HTC recovery bootable but no luck
C:\WINDOWS\system32>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.58.0000
(bootloader) version-baseband: 1.09.00.0108
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.95.651.6
(bootloader) serialno: removed
(bootloader) imei: removed
(bootloader) product: shooter
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG8610000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3800mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3f645641
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s