I work on an android project for my school and we got HTC Desire Z phones straight from HTC.
So now I got some time I wanted to root the phone which is using latest OTA update.
After checking the boot loader I saw I have S-OFF already:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So can I omit certain parts of this guide then?
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Introduction
If you are s-off why don't you just boot the phone, install an apk that will only run if rooted like setcpu or something, and if it works you just saved yourself a lot of time.
Just saying no reason to take a longer road than you need..ya know?
Sent from my HTC Vision using XDA Premium App
rooted apps do not work.
Since I apparently have S-OFF can I just flash to a custom ROM which is rooted already?
Download "ROM Manager" from the Market and try to install Recovery.
gascanieto said:
Download "ROM Manager" from the Market and try to install Recovery.
Click to expand...
Click to collapse
Code:
an error occurred while attempting to run privileged commands!
Is this a bug then that it says S-OFF on boot?
I'm in a similar situation. I just got a NAM Desire Z, A7275 (from eBay), mine's also S-OFF.
However my bootloader screen shows:
HBOOT-0.85.0012
MICROP-0425
RADIO-26.08.04.16_M
eMMC-boot
Feb 17,2011,16:39:08
I think this may have already been rooted/S-OFF etc...
I can't find an INFOCID using fastboot, but it does say "CID is super CID". This is indeed an unlocked phone.
There was also a su binary already in /system/xbin, so executing 'adb shell' takes me to a root prompt '#'. However even with the Superuser.apk installed, it doesn't ask for permission first. Root is always granted immediately (verified with root app). How can I fix this so it asks for permissions first? I tried replacing the su binary with one from the wiki, and set permissions 2755 on it. No luck, same behavior.
I'm not sure where to proceed since I'm not sure what state the phone is in. I've read the wiki and other forums where there's a risk of brick if I go all out on it.
It has the latest android 2.3.3 w/SenseUI, but I'm not sure what firmware version that corresponds to, to know if I need to downgrade or not.
From the post at: http://forum.xda-developers.com/showthread.php?t=1107911
it says: 'When you check your version at your phone now it should say "1.34"', but I'm not sure where to check that version. Nothing is even close to that number in the 'About Phone' section. It says 'Software number 2.30.405.1', 'HTC Sense version 2.1'.
Is there a risk I can trigger the S-OFF back to S-ON if I flash CM or stock image? I read that reflashing PC10IMG can break stuff.
EDIT: Here's the fastboot oem boot results:
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8D0878DC
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x25203
(bootloader) TAG:hero panel = 0xF
(bootloader) TAG:engineerid = 0x4
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is BM___001
(bootloader) setting->cid::BM___001
(bootloader) serial number: HT0xxxxxxxxx
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =492
(bootloader) active commandline: board_vision.disable_uart2=0 board_visio
(bootloader) n.usb_h2w_sw=0 board_vision.disable_sdcard=0 diag.enabled=0
(bootloader) board_vision.debug_uart=0 smisize=0 userdata_sel=0 androidbo
(bootloader) ot.emmc=true androidboot.baseband=26.08.04.16_M androidboot
(bootloader) .cid=BM___001 androidboot.batt_poweron=good_battery androidb
(bootloader) oot.carrier=BM androidboot.mid=PC1012000 androidboot.keycaps
(bootloader) =qwerty androidboot.mode=normal androidboot.serialno=HT0xxxx
(bootloader) xxxxx androidboot.bootloader=0.85.0012 zygote_oneshot=off km
(bootloader) emleak=off no_console_suspend=1
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) aARM_Partion[6].name=devlog
(bootloader) aARM_Partion[7].name=pdata
(bootloader) partition number=8
(bootloader) Valid partition num=8
(bootloader) jump_to_kernel: machine_id(2245), tags_addr(0x4000100), kern
(bootloader) el_addr(0x4008000)
(bootloader) -------------------hboot boot time:33453 msec
EDIT2: I've been doing some research, and it appears the ROM I have is a test ROM that was leaked back in March. So my question is, do I have a real S-OFF, or a fake S-OFF (how to tell)? Since I know what ROM it is, at least it gives me some information to work from.
Phoenix84118 said:
I'm in a similar situation. I just got a NAM Desire Z, A7275 (from eBay), mine's also S-OFF.
However my bootloader screen shows:
HBOOT-0.85.0012
MICROP-0425
RADIO-26.08.04.16_M
eMMC-boot
Feb 17,2011,16:39:08
.......
EDIT2: I've been doing some research, and it appears the ROM I have is a test ROM that was leaked back in March. So my question is, do I have a real S-OFF, or a fake S-OFF (how to tell)? Since I know what ROM it is, at least it gives me some information to work from.
Click to expand...
Click to collapse
Does the bootloader report SHIP S-OFF or ENG S-OFF?
theSpam said:
Does the bootloader report SHIP S-OFF or ENG S-OFF?
Click to expand...
Click to collapse
I guess I should've posted that line before.
It says:
VISION PVT SHIP S-OFF
See attached image.
Phoenix84118 said:
I guess I should've posted that line before.
It says:
VISION PVT SHIP S-OFF
See attached image.
Click to expand...
Click to collapse
Looks like you have real (i.e. radio) S-OFF. In the past, people gained fake S-OFF by flashing an engineering bootloader, which reported ENG S-OFF.
If you're radio S-OFF then by far the easiest way to get a custom ROM on it is to make a PC10IMG.zip with a working android-info.txt and a recovery.img (clockworkmod recovery).
Once the recovery image is flashed, just boot to recovery and flash whatever ROM you want, no need to bother rooting to get the custom recovery.
To repeat, this is the biggest advantage of S-OFF. You basically never have to root your phone again, because you can just flash a recovery. And we all know that with the custom recovery you can do anything, including flashing a rooted ROM.
I guess you'd only need to follow parts of the guide if you want SIM-unlock and debranding, but as far as custom ROMs go you are ready to go.
c00ller said:
If you're radio S-OFF then by far the easiest way to get a custom ROM on it is to make a PC10IMG.zip with a working android-info.txt and a recovery.img (clockworkmod recovery).
Once the recovery image is flashed, just boot to recovery and flash whatever ROM you want, no need to bother rooting to get the custom recovery.
To repeat, this is the biggest advantage of S-OFF. You basically never have to root your phone again, because you can just flash a recovery. And we all know that with the custom recovery you can do anything, including flashing a rooted ROM.
I guess you'd only need to follow parts of the guide if you want SIM-unlock and debranding, but as far as custom ROMs go you are ready to go.
Click to expand...
Click to collapse
Thanks for the response guys!
From my experience with my N1, I agree that once you get a custom recovery, you're free to do anything. I just wasn't sure what had been done to the phone before.
My phone is already SIM-unlocked and debranded (if it ever was) as far as I can tell. Since my AT&T SIM worked perfectly in it (it's not a G2, has no carrier labeling on the device, and has AT&T 3G freqs).
Just to clarify though, I should NOT flash a stock RUU image, as that would relock my radio/hboot. Is that correct?
Phoenix84118 said:
Thanks for the response guys!
Just to clarify though, I should NOT flash a stock RUU image, as that would relock my radio/hboot. Is that correct?
Click to expand...
Click to collapse
RUU will usually do that, correct
c00ller said:
RUU will usually do that, correct
Click to expand...
Click to collapse
Thanks everyone!
I think I have enough information to proceed safely now. At the moment I'm going to leave it as it is (since it has GB). After playing with SenseUI for a bit, I kinda like it. However it ultimately depends on what my fiancée wants (it's her phone). So far she's not liking the Sense dialer & contacts programs (I don't blame her, I don't like them either). I installed Dialer One for her to see if she can use that. Otherwise I may be flashing CM7.
EDIT:
Back to my original question: How to make it so root programs ask for permission first? It seems like it's probably a /etc/passwd,/etc/group issue. It makes me nervous to have root access doled out to anything that asks.
Hello,
+1 for @ashrack0 questions
My Desire Z is exactly the same, version numbers from first post match 100%. Phone is new, unbranded, S-OFF, 1.82 firmware @ android 2.2.1, it is also unlocked (CID is Super CID).
Basically, I want to overclock it, that means rooting + flashing custom ROM.
What are my options? Do i really have to follow WHOLE wiki guide, downgrade using goldcard (or at least i think i have to use goldcard, because my INFOCID is not on "the list", it just says "super CID"), follow every step in the guide, etc? Will it work (the guide was written with S-ON devices in mind)?
c00ller said:
If you're radio S-OFF then by far the easiest way to get a custom ROM on it is to make a PC10IMG.zip with a working android-info.txt and a recovery.img (clockworkmod recovery).
Once the recovery image is flashed, just boot to recovery and flash whatever ROM you want, no need to bother rooting to get the custom recovery.
To repeat, this is the biggest advantage of S-OFF. You basically never have to root your phone again, because you can just flash a recovery. And we all know that with the custom recovery you can do anything, including flashing a rooted ROM.
...
Click to expand...
Click to collapse
That sounds interesting, could you point me to a guide that explains in details what you are talking about? I'm new here, i've been reading and searching this forum many hours and for now it's quite overwhelming, i would be very grateful for some tips. Thank you
kbu said:
That sounds interesting, could you point me to a guide that explains in details what you are talking about? I'm new here, i've been reading and searching this forum many hours and for now it's quite overwhelming, i would be very grateful for some tips. Thank you
Click to expand...
Click to collapse
S-OFF lets you flash any PC10IMG.zip that contains a partition image (system.img, data.img, radio.img, recovery.img, etc) through the bootloader. This is how to typically flash a new radio.
In your case all you need is an android-info.txt (can be taken from any radio zip file in the link above) and the recovery.img of the recovery you want to flash (you can go here, download the zip and extract the img file, then rename to recovery.img). Then just zip the two files together and name the zip file PC10IMG.zip. Then the flashing process is the same as flashing a radio above.
Thanks a bunch, it worked perfectly and was super easy, i'm now running CM7
kbu said:
Thanks a bunch, it worked perfectly and was super easy, i'm now running CM7
Click to expand...
Click to collapse
Glad it worked out for ya, and more importantly I'm glad I taught you the significance of S-OFF, the bootloader and how to make PC10IMG.zip's
thx for all the help. Have flashed the clockworkmod. And then was able to put SU in /system/bin and install the superuser.apk.
So now I got root access as confirmed by root check app also.
Will play with custom roms later
Related
Hi all, this is my first post here but I have been reading and searching here for a while.
After weeks of searching and trying different things nows its time to ask for help.
I have recently jumped from iPhones to HTC One M8. Every iPhone I had a Jailbroken and thought I would root my HTC so Ima bit new to all this.
Here's what I've done.
I have a Telstra branded HTC One M8.
After a week I decided to root it, after a lot of reading I Unlocked the Bootloader and installed TWRP, Did a backup straight away with TWRP and then I tried to S-off but firewater said it couldn't be done after 1 chug so I left it s-on.
That night I got the new OTA update so now I have to undo all I have done. I thought I would try the HTC one toolkit by Hasoon and followed the step by step instructions from TheUnlocker site ( can't post links yet)
I used Nandroid: CID TELST001 - 1.12.841.17 and Recovery 1.12.771.17.
All went smoothly and I was back to a stock phone, well AFAIK. I then downloaded and tried to install thew OTA update. Then phone reboots into the bootloader saying security warning under the tampered flag. I have tried unlocking the bootloader again and re-flashing the phone, I have even tried to s-on just in case when I tried to S-off it left something undone.
I'm now at my wits end so I'm asking for help.
Here's what I get when I try to return to S-on
...
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
(bootloader) writesecureflag: Permission denied, value 1
OKAY [ 0.002s]
finished. total time: 0.003s
D:\Android\toolkit\One_M8_All-In-One_Kit_v\data>
Also I got some error msgs when doing the bootloader (i think).
This is a copy from someone else but its the same error msg
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -131073 (0xFFFDFFFF)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.170s
I hope someone can help out, I,m sick of the update screen popping up.
Thanks in advance.
Johnsy75 said:
Hi all, this is my first post here but I have been reading and searching here for a while.
After weeks of searching and trying different things nows its time to ask for help.
I have recently jumped from iPhones to HTC One M8. Every iPhone I had a Jailbroken and thought I would root my HTC so Ima bit new to all this.
I hope someone can help out, I,m sick of the update screen popping up.
Thanks in advance.
Click to expand...
Click to collapse
If you failed to get s-off then you are s-on. There is no middle state.
Run "fastboot getvar all" and post the output here please. Remember to hide your sensitive info like imei and serial.
stathis95194 said:
If you failed to get s-off then you are s-on. There is no middle state.
Run "fastboot getvar all" and post the output here please. Remember to hide your sensitive info like imei and serial.
Click to expand...
Click to collapse
Here's what I've got
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA15_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***********************
(bootloader) imei: ***************
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: TELST001
(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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.007s
Thanks
Johnsy75 said:
Here's what I've got
Thanks
Click to expand...
Click to collapse
OK good...first of all i'm not sure if you have relocked your bootloader, so if you did please unlock it again.
On stock backups thread i could find a TWRP stock nandroid for your cid but couldn't find a stock recovery so that's a bummer
I have found this:
http://forum.xda-developers.com/showpost.php?p=51906969&postcount=324
It's both stock rom and stock recovery but you will need to flash CWM instead of TWRP.
So to summarize
1. Unlock bootloader (if it's locked)
2. Flash CWM
3. Flash nandroid backup from the link above
4. Flash stock recovery from the link above
5. You will now be able to receive the OTA and upgrade firmware.
---------- Post added at 09:41 AM ---------- Previous post was at 09:34 AM ----------
by the way what message did you get from firewater? was it the whelp unfortunately??? i don't know how fast is Telstra releasing OTA's but you might consider s-off to be able to debrand and flash an even newer firmware and rom ie. 2.22.xxx.x
If firewater doesn't work you also have the option of sunshine but you will have to pay $25 for this
4725
stathis95194 said:
OK good...first of all i'm not sure if you have relocked your bootloader, so if you did please unlock it again.
On stock backups thread i could find a TWRP stock nandroid for your cid but couldn't find a stock recovery so that's a bummer
I have found this:
http://forum.xda-developers.com/showpost.php?p=51906969&postcount=324
It's both stock rom and stock recovery but you will need to flash CWM instead of TWRP.
So to summarize
1. Unlock bootloader (if it's locked)
2. Flash CWM
3. Flash nandroid backup from the link above
4. Flash stock recovery from the link above
5. You will now be able to receive the OTA and upgrade firmware.
Click to expand...
Click to collapse
The bootloader is locked, when I look in the bootloader menu I have the "Tampered" & "Relocked" Flags.
As for the recovery, in the tutorial in TheUnlocker he was saying along the lines that if I/you couldn't find a matching recovery for the backup just match the first two numbers of the CID to a recovery, which did work but it must not be "stock" enough for the OTA update.
Thanks for finding that info for me, I will give it a crack a bit later on and I'll post back with the out come.:good:
[/COLOR]by the way what message did you get from firewater? was it the whelp unfortunately??? i don't know how fast is Telstra releasing OTA's but you might consider s-off to be able to debrand and flash an even newer firmware and rom ie. 2.22.xxx.x
If firewater doesn't work you also have the option of sunshine but you will have to pay $25 for this[/QUOTE]
When I tried firewater I got welp on the first bottle. I tried around 8 times then gave up. I read somewhere that if I flash a different rom it might make it easier to S-OFF. But as I said before I'm still a noob to "Rooting" so there's a high chance I could be wrong
Johnsy75 said:
[/COLOR]by the way what message did you get from firewater? was it the whelp unfortunately??? i don't know how fast is Telstra releasing OTA's but you might consider s-off to be able to debrand and flash an even newer firmware and rom ie. 2.22.xxx.x
If firewater doesn't work you also have the option of sunshine but you will have to pay $25 for this
Click to expand...
Click to collapse
When I tried firewater I got welp on the first bottle. I tried around 8 times then gave up. I read somewhere that if I flash a different rom it might make it easier to S-OFF. But as I said before I'm still a noob to "Rooting" so there's a high chance I could be wrong [/QUOTE]
If you got the Whelp no matter how many times you try you cannot get s-off then you are out of luck.
If not, then keep trying because you might still have chances. Seeing that you are on an old base you might still have a chance for s-off without having to pay the $25 for sunshine
After all this time I finally got time to sit down and try the stock ROM and recovery you found. It worked and my HTC is updating as we speak.
It just done a software update and I checked the Android version and its still 4.4.2, software 1.54.841.8. It's D/L another update as I type this.
I'll let you know the outcome.
Once again thanks for your help.:good:
Johnsy75 said:
After all this time I finally got time to sit down and try the stock ROM and recovery you found. It worked and my HTC is updating as we speak.
It just done a software update and I checked the Android version and its still 4.4.2, software 1.54.841.8. It's D/L another update as I type this.
I'll let you know the outcome.
Once again thanks for your help.:good:
Click to expand...
Click to collapse
It's all good.
Version 4.4.3
Software 2.23.841.1
I have an htc one m7 for verizon. ulocked bootloader and s-off. For some reason recovery software will not load. I have tried every way possible to flash twrp and cwm. they just will not load. Anyway I was able to install a RUU file through fastboot. So since I can not get into twrp or cwm to try out different roms, is there custom roms is ruu format?.
I would really like to install NuSense 8.0. Anyone have it in ruu?
Here is my getvar info....
c:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0702
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.28.605.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3910mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.066s
You tried flashing recovery via fastboot?
fastboot flash recovery filename.img
http://mdmower.cmphys.com/flashing-recovery-on-htc-devices/
vaping redhead said:
I have an htc one m7 for verizon. ulocked bootloader and s-off. For some reason recovery software will not load. I have tried every way possible to flash twrp and cwm. they just will not load. Anyway I was able to install a RUU file through fastboot. So since I can not get into twrp or cwm to try out different roms, is there custom roms is ruu format?.
I would really like to install NuSense 8.0. Anyone have it in ruu?
Click to expand...
Click to collapse
For some reason your recovery partition is not getting written into. please double check that your bootloader is unlocked and you are S-off. if so then try the following options.
Via apps like flashify, rom toolbox pro try to flash the recovery image.
or via fastboot,
fastboot erase recovery (optional)
fastboot flash recovery recovery.img
MoonBlade said:
For some reason your recovery partition is not getting written into. please double check that your bootloader is unlocked and you are S-off. if so then try the following options.
Via apps like flashify, rom toolbox pro try to flash the recovery image.
or via fastboot,
fastboot erase recovery (optional)
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I have flashed several versions via flashify and fastboot. None of them load even though they flash with no errors. I also flashed an ruu of twrp that said it installed and still can not load recovery. It tries the screen says entering recovery then goes black then right back to the entering recovery screen. The phone will stay on that screen until I power it down.
can you link me to the recovery you are trying to install?
vaping redhead said:
I have flashed several versions via flashify and fastboot. None of them load even though they flash with no errors. I also flashed an ruu of twrp that said it installed and still can not load recovery. It tries the screen says entering recovery then goes black then right back to the entering recovery screen. The phone will stay on that screen until I power it down.
Click to expand...
Click to collapse
Perform this command in terminal, with device in fastboot:
fastboot erase cache
You then should be able to boot to your custom recovery.
santod040 said:
Perform this command in terminal, with device in fastboot:
fastboot erase cache
You then should be able to boot to your custom recovery.
Click to expand...
Click to collapse
I have tried that command, still no go.
vaping redhead said:
I have tried that command, still no go.
Click to expand...
Click to collapse
I noticed you changed your CID to Super CID.
Any particular reason for that?
May have nothing to do with your problem, but was just something I noticed.
santod040 said:
I noticed you changed your CID to Super CID.
Any particular reason for that?
May have nothing to do with your problem, but was just something I noticed.
Click to expand...
Click to collapse
I am not familiar with changing the cid. So I did not change it.
vaping redhead said:
I am not familiar with changing the cid. So I did not change it.
Click to expand...
Click to collapse
Your get var says differently...
(bootloader) cidnum: 11111111
That is super cid
Vzw cid is:
VZW__001
So somehow, some way, it got changed.
synisterwolf said:
can you link me to the recovery you are trying to install?
Click to expand...
Click to collapse
I have tried several. Twrp 2.8.0.1, 2.7.0.8-2.7.1.13 and I also tried cwm 6.0.4.8. Wich one would you like a link to.
santod040 said:
Your get var says differently...
(bootloader) cidnum: 11111111
That is super cid
Vzw cid is:
VZW__001
So somehow, some way, it got changed.
Click to expand...
Click to collapse
I got this phone on eBay. It came unlocked and s-off. Is super cid ok?
I looked up supercid. Yeah the person who sold it to me on eBay must have done that. Twrp was working. I did recently convert the phone from a silver case to a red one. I wonder if that has something do with it not loading. Everything on the phone works accept the recovery.
synisterwolf said:
can you link me to the recovery you are trying to install?
Click to expand...
Click to collapse
Here is a link to the latest version I have tried. This one too will not load.......
http://techerrata.com/file/twrp2/m7vzw/openrecovery-twrp-2.8.0.0-m7wlv.img
This is so frustrating. I have tried all the suggestions and my phone will not load recovery. Thank You to everyone's input, for now the only way for me to try something new is to install via fastboot and the rom update utility. This makes no sense because twrp was working fine, I had NuSense 7.8. I saw an update to 8.0. I downloaded NuSense 8.0 and went to load twrp and it would not load. So I tried all the suggestions on here still not loading. I then Installed the ruu file that keeps me rooted and s-off kitkat 4.4.3. That worked and wiped the phone. Ok now that the phone is completely wiped and brand new install, twrp should work. NO still not loading. I should have stuck with NuSense 7.8......
Here is a picture of what happens when I enter recovery from the bootloader..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It will stay like this until the battery dies or I reboot
Have you tried flashing the ruu mode flashable recovery in dottdat's ruu thread?
http://forum.xda-developers.com/showthread.php?t=2867643
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
Have you tried flashing the ruu mode flashable recovery in dottdat's ruu thread?
http://forum.xda-developers.com/showthread.php?t=2867643
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
That is the RUU I flashed. It works great. My one issue is recovery not loading. Everything else works, Including flashing a ruu file via fastboot. which is why I do not understand why the recovery just refuses to load. I have tried multiple suggestions all to no avail...
vaping redhead said:
That is the RUU I flashed. It works great. My one issue is recovery not loading. Everything else works, Including flashing a ruu file via fastboot. which is why I do not understand why the recovery just refuses to load. I have tried multiple suggestions all to no avail...
Click to expand...
Click to collapse
Read the ruu thread OP. He has an ruu flashable recovery link. Have you tried flashing that recovery in ruu mode?
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
Read the ruu thread OP. He has an ruu flashable recovery link. Have you tried flashing that recovery in ruu mode?
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
You think that would resolve the issue?
It is so hard to re-locate threads between this general HTC One M8 and the variant for the carriers....so I hate adding to repetitive questions in threads....
BUT... I was certain that I read countless times that you could flash recoveries from ADB with bootloader locked provided you had S-off.
And now I am getting this error:
FAILED (remote: not allowed)
I had two updates and wanted to flash stock recovery then reflash TWRP.... I thought it would take 20 minutes tops....
syntropic said:
It is so hard to re-locate threads between this general HTC One M8 and the variant for the carriers....so I hate adding to repetitive questions in threads....
BUT... I was certain that I read countless times that you could flash recoveries from ADB with bootloader locked provided you had S-off.
And now I am getting this error:
FAILED (remote: not allowed)
I had two updates and wanted to flash stock recovery then reflash TWRP.... I thought it would take 20 minutes tops....
Click to expand...
Click to collapse
SO I said f*ck it... no big deal, and I unlocked the bootloader and flashed the stock recovery (btw, I flashed a stock recovery I found in the TMO forums that had a version number identical to the software version I had installed, this is correct right????). I had no problems flashing the stock recovery....so apparently, you need to unlock the bootloader whenever you are flashing recoveries irrespective of whether you have S-off.
But then, I tried to run the OTA, and got the red triangle error.... — Is this because my bootloader is now unlocked?
This seems to be going against everything I have read numerous times (namely that if you are S-off, the bootloader is not that big of an issue). I am assuming this is because my bootloader is now unlocked... so I will unlock it.
IGNORE
Just adding my experiences as I don't want to start another thread with new information...
I have unlocked bootloader
flashed stock recovery
relocked bootloader
went into setting==>apps and enabled the 10 or so apps that I had previously disabled...
I even deleted all downloaded OTA updates and had the phone re-download them again.
However, I still cannot install OTA updates. I know that the standard instructions are to flash a stock rom or restore a nandroid that is stock, but my phone is stock!!! Nothing has touched any of the original software on it other than the stock recovery, which I flashed back on it...
I think my phone is techincally still rooted because it has the SuperSu binary installed... But (again) from everything I read, the way I understood it was that in order to get OTA updates you needed to have stock (or pretty close with no uninstalled/frozen/disabled system apps), and the stock recovery.... AND that is it....
Anyway, I did a fastboot getvar all if that is helpful.... I have pasted it below:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.213311491.03G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.22.531.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA44VWM00543
(bootloader) imei: ★★★★★★★★★★★★★
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.059s
syntropic said:
Just adding my experiences as I don't want to start another thread with new information...
I have unlocked bootloader
flashed stock recovery
relocked bootloader
went into setting==>apps and enabled the 10 or so apps that I had previously disabled...
I even deleted all downloaded OTA updates and had the phone re-download them again.
However, I still cannot install OTA updates. I know that the standard instructions are to flash a stock rom or restore a nandroid that is stock, but my phone is stock!!! Nothing has touched any of the original software on it other than the stock recovery, which I flashed back on it...
I think my phone is techincally still rooted because it has the SuperSu binary installed... But (again) from everything I read, the way I understood it was that in order to get OTA updates you needed to have stock (or pretty close with no uninstalled/frozen/disabled system apps), and the stock recovery.... AND that is it....
Anyway, I did a fastboot getvar all if that is helpful.... I have pasted it below:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.213311491.03G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.22.531.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA44VWM00543
(bootloader) imei: DO NOT POST IMEI NUMBER
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.059s
Click to expand...
Click to collapse
What OTA update are you trying to install?
version-bootloader: 3.18.0.0000 - latest
version-main: 2.22.531.5 - latest
Remove your IMEI from your post.
BerndM14 said:
What OTA update are you trying to install?
version-bootloader: 3.18.0.0000 - latest
version-main: 2.22.531.5 - latest
Remove your IMEI from your post.
Click to expand...
Click to collapse
I removed it just before I saw your post... but thanks! And thanks for replying.
I am trying to install the 2.22.531.6 OTA software.
I don't know if the bootloader/hboot version has any correlation to the software, but I have not touched anything... I did two updates, then a three days later did HTCDev unlock of bootloader, I flashed TWRP, flashed SuperSU, got Sunshine S-Off, then relocked bootloader. As mentioned I also disabled a bunch of apps. But as of now, I have re-enabled them.
The only variable that wasn't precisely in my control was the stock recovery. I didn't know which one to flash, but made the common sense decision to flash the 2.22.531.5-TMO-Recovery.img since the version number of the recovery matched exactly the version number of the software that is showing on my hboot screen. I thought that was a educated guess that wouldn't be too risky.
I haven't flashed or changed the hboot, or flashed any RUUs....nothing else.
really confused....because aside from the recovery, I didn't touch any of the firmware.
NB: I do have a nandroid that I made that is entitled: 2014-09-24-14-06{whatever) release keys I don't know what release keys means.... I have made a lot of nandroids in my time... 95% of them on HTC devices using TWRP (at least since its inception), and I have never seen a "release keys" appended to the name of an nandroid like that.
I could restore this nandroid... but then I would have to unlock the BL, fastboot flash TWRP, flash SuperSU (although I know TWRP now prompts you which is very cool), then restore the nandroid, fastboot flash the stock recovery, then (apparently) re-lock the bootloader, and get the OTAs.... if the OTAs even work...
syntropic said:
I removed it just before I saw your post... but thanks! And thanks for replying.
I am trying to install the 2.22.531.6 OTA software.
I don't know if the bootloader/hboot version has any correlation to the software, but I have not touched anything... I did two updates, then a three days later did HTCDev unlock of bootloader, I flashed TWRP, flashed SuperSU, got Sunshine S-Off, then relocked bootloader. As mentioned I also disabled a bunch of apps. But I have no re-enabled them.
The only variable that wasn't precisely in my control was the stock recovery. I didn't know which one to flash, but made the common sense decision to flash the 2.22.531.5-TMO-Recovery.img since the version number matched exactly the version number of the software as shown in the hboot screen. So I assumed it was the right one. I haven't flashed or changed the hboot, or flashed any RUUs....nothing else.
really confused.
Click to expand...
Click to collapse
Ok stock recovery flashed back is good then, you need to be completely stock to do OTA's i.e If you made changes to the system even removed pre-installed apps like Facebook, Twitter etc you need to restore those back as well. As the OTA will do a verification check to see that all those things are intact before it continues the update. If it's not stock then you're not getting OTA. Bootloader status won't make a difference, you can keep it unlocked.
When you do the OTA and it fails what error does it give? When an OTA gets applied it reboots the system to the stock recovery and proceeds to apply the update, if it fails you can view the error. You can press Volume Up and then TAP the power button and it'll show you the recovery log details at the bottom, there it should tell you what errors you have during the OTA installation.
/system/app/blahblahblah has unexpected contents, or cannot find /system/app/blahblah etc
If it requires missing files etc just get them and add them back on the device. Like I said above, you need to be stock.
BerndM14 said:
{...}
When you do the OTA and it fails what error does it give? When an OTA gets applied it reboots the system to the stock recovery and proceeds to apply the update, if it fails you can view the error. You can press Volume Up and then TAP the power button and it'll show you the recovery log details at the bottom, there it should tell you what errors you have during the OTA installation.
/system/app/blahblahblah has unexpected contents, or cannot find /system/app/blahblah etc
If it requires missing files etc just get them and add them back on the device. Like I said above, you need to be stock.
Click to expand...
Click to collapse
Cool... NEAT trick I didn't know about that...!!! thank you for the tip. They should put that in the documentation with the f*ckin phone.
The recovery/installation log says (in relevant part):
Verifying current sytem. . .
"/system/build.prop" has unexpected contents
Installation aborted.
I thought about why the build.prop would have changes, and remembered that I have an app called Android Tweaker Pro (but it is being renamed since Google now prohibits apks with 'Android' in the name). It requires root to make its tweaks. Its a good app, but it does make a lot of changes to build.prop. But... am pretty sure it has a reset/restore to default option on it... I am going to check and try that.
Will let you know...
Sh*t.... still can't believe I didn't know about the installation log screen... very impressed.
syntropic said:
Cool... NEAT trick I didn't know about that...!!! thank you for the tip. They should put that in the documentation with the f*ckin phone.
The recovery/installation log says (in relevant part):
Verifying current sytem. . .
"/system/build.prop" has unexpected contents
Installation aborted.
I thought about why the build.prop would have changes, and remembered that I have an app called Android Tweaker Pro (but it is being renamed since Google now prohibits apks with 'Android' in the name). It requires root to make its tweaks. Its a good app, but it does make a lot of changes to build.prop. But... am pretty sure it has a reset/restore to default option on it... I am going to check and try that.
Will let you know...
Sh*t.... still can't believe I didn't know about the installation log screen... very impressed.
Click to expand...
Click to collapse
And so we all learn new things everyday It's great!
[Recovery] [RUU 2.22.531.6] [TWRP Nandroid Backups] [Radio IMGs][ OTA 2.22.531.6]
There's a stock backup for 2.22.531.5 in there that you can restore to go back to stock for the OTA. Changes to build.prop usually is changes to system. Perhaps you could also try and pull the build.prop from there and restore that and see if it works
---------- Post added at 01:22 AM ---------- Previous post was at 01:20 AM ----------
BerndM14 said:
And so we all learn new things everyday It's great!
[Recovery] [RUU 2.22.531.6] [TWRP Nandroid Backups] [Radio IMGs][ OTA 2.22.531.6]
There's a stock backup for 2.22.531.5 in there that you can restore to go back to stock for the OTA. Changes to build.prop usually is changes to system. Perhaps you could also try and pull the build.prop from there and restore that and see if it works
Click to expand...
Click to collapse
They also have the 2.22.531.6 stuff there so just make sure you select the correct versions, it's under the "clickable" buttons so...
OK.... I used a app called Nandroid Manager (very helpful app) which extracts anything you want from a nandroid. Since I had already disabled the Android Tweaker 2 App, and realized I had an original build.prop in that nandroid, I just extracted that and renamed the old one, and used the extracted one. I did a chmod 644, and then attempted OTA install.. And it went fine! Very nice... A bigger headache then I had anticipated... but it serves me right for forgetting that I had root apps modifying sh*t that I had not considered.
Very big thanks for the tips.
Also...lastly, since I stupidly relocked the bootloader, I am now no longer root but cannot flash TWRP because the BL is locked. I cannot use Scotty1223's method (I don't think) because it requires su permissions in adb shell.
I could probably just use the htc .bin file.... but out of curiousity, is there any easy way to get temp root in this case?
EDIT: Actually.... I would really like to avoid the htc unlock token as that erases the data partition as some kind of existential pennace ordained by HTC for unlocking your bootloader.
syntropic said:
[...] And it went fine! Very nice... A bigger headache then I had anticipated... but it serves me right for forgetting that I had root apps modifying sh*t that I had not considered.
Very big thanks for the tips.
Click to expand...
Click to collapse
Glad it worked out :good:
Also...lastly, since I stupidly relocked the bootloader, I am now no longer root but cannot flash TWRP because the BL is locked. I cannot use Scotty1223's method (I don't think) because it requires su permissions in adb shell.
I could probably just use the htc .bin file.... but out of curiousity, is there any easy way to get temp root in this case?
Click to expand...
Click to collapse
Yeah you can use the unlock binary you had if you went through htc unlock method, or you can just do it again if you want(another headache).
You'll have to read up on temp root methods, I haven't used any at all, so I'm not entirely sure, sorry.
---------- Post added at 02:01 AM ---------- Previous post was at 01:58 AM ----------
BerndM14 said:
Glad it worked out :good:
Yeah you can use the unlock binary you had if you went through htc unlock method, or you can just do it again if you want(another headache).
You'll have to read up on temp root methods, I haven't used any at all, so I'm not entirely sure, sorry.
Click to expand...
Click to collapse
Just saw your edit...you're right it'll probably wipe everything again.
Did you get S-OFF with Sunshine? I don't know if maybe there's a way to unlock the bootloader again even if you're already S-OFF If you didn't then it probably won't be feasible to pAy $25 just to unlock the bootloader, I'd rather then just back up everything and let the data get wiped doing it the HTC way.
Check the Sunshine Thread maybe, they had some discussions in there about temp roots if I recall correctly.
BerndM14 said:
Glad it worked out :good:
Yeah you can use the unlock binary you had if you went through htc unlock method, or you can just do it again if you want(another headache).
You'll have to read up on temp root methods, I haven't used any at all, so I'm not entirely sure, sorry.
---------- Post added at 02:01 AM ---------- Previous post was at 01:58 AM ----------
Just saw your edit...you're right it'll probably wipe everything again.
Did you get S-OFF with Sunshine? I don't know if maybe there's a way to unlock the bootloader again even if you're already S-OFF If you didn't then it probably won't be feasible to pAy $25 just to unlock the bootloader, I'd rather then just back up everything and let the data get wiped doing it the HTC way.
Check the Sunshine Thread maybe, they had some discussions in there about temp roots if I recall correctly.
Click to expand...
Click to collapse
I have been spending the past 2+ hours researching this. Even worse, the HTC token no longer unlocks the bootloader.... So I have this great phone with S-Off, but no way to get root. In my first attempt with chatting with HTC, they said that they "were very sorry but [they] do not support 'unlocking the bootloader' as it is against the warranty". WTF????? I am trying to get though to HTCDev... luckily I didn't change my CID. But I hate waiting for this.... I do a lot of stuff on that phone with root privileges..
I tried adb root, adb root shell, adb shell su, and a whole bunch of combination.... no dice...
There is just no way to hack a way to get temporary root at this point. I have looked... Weaksauce has long been deprecated/useless once you are past 4.4.2.
My planned 20+ minute task today is now going into its sixth hour....!!
syntropic said:
I have been spending the past 2+ hours researching this. Even worse, the HTC token no longer unlocks the bootloader.... So I have this great phone with S-Off, but no way to get root. In my first attempt with chatting with HTC, they said that they "were very sorry but [they] do not support 'unlocking the bootloader' as it is against the warranty". WTF????? I am trying to get though to HTCDev... luckily I didn't change my CID. But I hate waiting for this.... I do a lot of stuff on that phone with root privileges..
I tried adb root, adb root shell, adb shell su, and a whole bunch of combination.... no dice...
There is just no way to hack a way to get temporary root at this point. I have looked... Weaksauce has long been deprecated/useless once you are past 4.4.2.
My planned 20+ minute task today is now going into its sixth hour....!!
Click to expand...
Click to collapse
how did you get S-OFF? Firewater?
BerndM14 said:
how did you get S-OFF? Firewater?
Click to expand...
Click to collapse
He said SunShine on OP.
OP - try towelroot to gain root then use scotty's guide to unlock bootloader
If you are still S-off, just use adb to unlock the bootloader again.
http://forum.xda-developers.com/showthread.php?t=2475914
No muss, no fuss, and no lost files.
jshamlet said:
If you are still S-off, just use adb to unlock the bootloader again.
http://forum.xda-developers.com/showthread.php?t=2475914
No muss, no fuss, and no lost files.
Click to expand...
Click to collapse
Really ?
Read his problem again... His device has no root so can't do what you suggested
ckpv5 said:
Really ?
Read his problem again... His device has no root so can't do what you suggested
Click to expand...
Click to collapse
I realized that shortly after posting.
However, there is still a solution. Use Sunshine to temp-root, then use a local terminal instead of adb.
jshamlet said:
If you are still S-off, just use adb to unlock the bootloader again.
http://forum.xda-developers.com/showthread.php?t=2475914
No muss, no fuss, and no lost files.
Click to expand...
Click to collapse
When ckpv5 referred to Scotty's method in the post above yours, he is talking about the thread you linked. I am aware of that method and think it is great, but you need to get a shell... and you need root privileges in that shell in order to run the dd= command. That is just the way it works. It doesn't matter if you are S-off (this is why I have been frustrated). Until HTC replies to me, I am stuck with an unrooted phone with S-off.
I am going to try the towelroot method though... I forgot about that (thank you ckpv5).
If I can get temporary root long enough to unlock the bootloader.... then I can flash TWRP and I am good to go. We'll see.
syntropic said:
When ckpv5 referred to Scotty's method in the post above yours, he is talking about the thread you linked. I am aware of that method and think it is great, but you need to get a shell... and you need root privileges in that shell in order to run the dd= command. That is just the way it works. It doesn't matter if you are S-off (this is why I have been frustrated). Until HTC replies to me, I am stuck with an unrooted phone with S-off.
I am going to try the towelroot method though... I forgot about that (thank you ckpv5).
If I can get temporary root long enough to unlock the bootloader.... then I can flash TWRP and I am good to go. We'll see.
Click to expand...
Click to collapse
Yeah, I had a bit of a brain fart on that one. I forgot you have to be able to su to execute that dd command, even s-off. However, I do know for a fact that you don't actually have to flash TWRP to re-root. When I did the same thing you are doing, I simply booted TWRP instead of installing it to preserve the stock recovery.
TWRP did have an issue booting for a while when using the firmware that came along with 4.4.3, but they appear to have fixed it in the last two versions. I ended up using CWM instead, but the effect is the same.
jshamlet said:
I realized that shortly after posting.
However, there is still a solution. Use Sunshine to temp-root, then use a local terminal instead of adb.
Click to expand...
Click to collapse
That is another good potential solution...and I know it works.... I will try and let you know!
Q&A for One m8 t mobile lollipop ota captured
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for One m8 t mobile lollipop ota captured. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
T-Mobile HTC One M8 won't update to lollipop
I just recently saw that the 5.0 update was available for my phone today, so i downloaded it and i installed it, but recieved this error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I went through these steps in order:
1.) Downloaded the update
2.) Swapped back to original recovery (from TWRP)
3.) Did full (permanent) unroot from SuperSU app
4.) Attempt #1 at updating. Failed with this error.
5.) Did factory restore from recovery.
6.) Attempt #2. Same result, same error.
So I'm really lost. Anyone have any ideas?
Before any one asks, my phone is running 4.4.4, is S-on, stock ROM, stock recovery (now) and is the T-mobile version, not the GPe.
CMP27240 said:
I just recently saw that the 5.0 update was available for my phone today, so i downloaded it and i installed it, but recieved this error.
I went through these steps in order:
1.) Downloaded the update
2.) Swapped back to original recovery (from TWRP)
3.) Did full (permanent) unroot from SuperSU app
4.) Attempt #1 at updating. Failed with this error.
5.) Did factory restore from recovery.
6.) Attempt #2. Same result, same error.
So I'm really lost. Anyone have any ideas?
Before any one asks, my phone is running 4.4.4, is S-on, stock ROM, stock recovery (now) and is the T-mobile version, not the GPe.
Click to expand...
Click to collapse
Your recovery is outdated, install this one. https://www.androidfilehost.com/?fid=95897840722642978
I had this same error. I just used the 4.4.4 RUU for T-mobile to return to complete stock. Then OTA updated. Worked like a charm. In your Bootloader, does the screen have "Software Status: Modified" at the top?
Mossy Canine said:
I had this same error. I just used the 4.4.4 RUU for T-mobile to return to complete stock. Then OTA updated. Worked like a charm. In your Bootloader, does the screen have "Software Status: Modified" at the top?
Click to expand...
Click to collapse
yes, but apparently all i had to do was update the recovery since i had an older version. completely went through this time.
Phone stuck on boot after twrp stock flash?
I've followed your instructions, but now my phone when booting for the first time after the stock rom flash, it stuck on the "htc one" screen. I reflashed again, still same result? not sure if i should move forward with the recovery.img step or have i done something wrong?
Please help!
jdub1983 said:
I've followed your instructions, but now my phone when booting for the first time after the stock rom flash, it stuck on the "htc one" screen. I reflashed again, still same result? not sure if i should move forward with the recovery.img step or have i done something wrong?
Please help!
Click to expand...
Click to collapse
When all else fails just cut your losses, do yourself a favor, and flash the RUU.
http://dl3.htc.com/application/RUU_...G_20.57.4198.02_F_release_420431_signed_2.exe
on a mac
I'm on a Mac! Otherwise that would have been my first. What do I do now if I only have a Mac available?
jdub1983 said:
I'm on a Mac! Otherwise that would have been my first. What do I do now if I only have a Mac available?
Click to expand...
Click to collapse
Well if somebody has time to unpack the RUU, you can flash the ROM zip through hboot with an SD card. Just rename it 0P6BING.zip, put it on an SD card, boot into hboot and confirm the flash. Maybe ask in @Garmig's thread.
Behold_this said:
Well if somebody has time to unpack the RUU, you can flash the ROM zip through hboot with an SD card. Just rename it 0P6BING.zip, put it on an SD card, boot into hboot and confirm the flash. Maybe ask in @Garmig's thread.
Click to expand...
Click to collapse
Sure! I'll post the rom.zip in my thread, uploading now.
jdub1983 said:
I'm on a Mac! Otherwise that would have been my first. What do I do now if I only have a Mac available?
Click to expand...
Click to collapse
Behold_this said:
Well if somebody has time to unpack the RUU, you can flash the ROM zip through hboot with an SD card. Just rename it 0P6BING.zip, put it on an SD card, boot into hboot and confirm the flash. Maybe ask in @Garmig's thread.
Click to expand...
Click to collapse
Garmig said:
Sure! I'll post the rom.zip in my thread, uploading now.
Click to expand...
Click to collapse
Posted: http://forum.xda-developers.com/showpost.php?p=51836733&postcount=4
Phone won't boot, stuck in HBOOT?
Garmig said:
Sure! I'll post the rom.zip in my thread, uploading now.
Click to expand...
Click to collapse
So, i found a copy of windows last night, installed on my mac so i could use the RUU. Got computer setup, drives etc installed. downloaded the RUU, relocked boot loader... this is when all the problems started.
Once the bootloader relocked, it went into a loop. Never being able to go anywhere besides the Hboot. None of the choices work, including factory reset.
In windows when i Run the RUU, it unpacks and then closes. tried downloading again. Same result. Got to frustrated so i turned phone off went to bed. This morning, tried to unlock bootoader again, but now i get this msg
Jeffreys-MacBook-Pro:~ TipTop$ fastboot flash unlocktocken /Users/TipTop/Desktop/Android/Unlock_code.bin
sending 'unlocktocken' (0 KB)...
OKAY [ 0.126s]
writing 'unlocktocken'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.128s
No idea?
Been searching all day for any kind of options i may have at my disposal but i am completely LOST. can someone with experience please help me and get my phone back alive?
Jeffreys-MacBook-Pro:~ TipTop$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.213311491.08G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.531.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: 038866fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Let me know if you need anymore info... Im going to be pretty close to my computer all day trying to figure what the heck to do
Thank you all!
jdub1983 said:
So, i found a copy of windows last night, installed on my mac so i could use the RUU. Got computer setup, drives etc installed. downloaded the RUU, relocked boot loader... this is when all the problems started.
Once the bootloader relocked, it went into a loop. Never being able to go anywhere besides the Hboot. None of the choices work, including factory reset.
In windows when i Run the RUU, it unpacks and then closes. tried downloading again. Same result. Got to frustrated so i turned phone off went to bed. This morning, tried to unlock bootoader again, but now i get this msg
Jeffreys-MacBook-Pro:~ TipTop$ fastboot flash unlocktocken /Users/TipTop/Desktop/Android/Unlock_code.bin
sending 'unlocktocken' (0 KB)...
OKAY [ 0.126s]
writing 'unlocktocken'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.128s
No idea?
Been searching all day for any kind of options i may have at my disposal but i am completely LOST. can someone with experience please help me and get my phone back alive?
Jeffreys-MacBook-Pro:~ TipTop$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.213311491.08G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.531.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: 038866fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Let me know if you need anymore info... Im going to be pretty close to my computer all day trying to figure what the heck to do
Thank you all!
Click to expand...
Click to collapse
Download the zip from @Garmig. make sure its named 0P6BIMG.zip. put it on the root of an SD card. put the SD card in your phone. boot into hboot and accept the update.
You know it was really nice for him to unpack it and upload for you the least you could do is use it appreciate it and THANK it.
Behold_this said:
Download the zip from @Garmig. make sure its named 0P6BIMG.zip. put it on the root of an SD card. put the SD card in your phone. boot into hboot and accept the update.
You know it was really nice for him to unpack it and upload for you the least you could do is use it appreciate it and THANK it.
Click to expand...
Click to collapse
Im very new at all this, so please don't take offense if i don't know proper lingo or appreciative techniques. it isn't meant to be disrespectful at all.. question regarding the sd card method. Is this the removable mini sd card? or the internal one?
jdub1983 said:
Im very new at all this, so please don't take offense if i don't know proper lingo or appreciative techniques. it isn't meant to be disrespectful at all.. question regarding the sd card method. Is this the removable mini sd card? or the internal one?
Click to expand...
Click to collapse
Must be external/removable sdcard. Zip must be named appropriately and on the root of the card eg sdcard/0P6BIMG.zip.
Many Thanks!
Garmig said:
Posted: http://forum.xda-developers.com/showpost.php?p=51836733&postcount=4
Click to expand...
Click to collapse
Garming & Behold_this, Thank you!
Once the Rom.zip is done, what else do i need to do?
for understanding purposes, what happened? I'm very curious person and followed directions very carefully. Anyway, again, thank you both for such quick replies.
---------- Post added at 09:39 PM ---------- Previous post was at 09:18 PM ----------
Behold_this said:
Must be external/removable sdcard. Zip must be named appropriately and on the root of the card eg sdcard/0P6BIMG.zip.
Click to expand...
Click to collapse
Garmig said:
Posted: http://forum.xda-developers.com/showpost.php?p=51836733&postcount=4
Click to expand...
Click to collapse
Thank you both for your input last night and today! I greatly appreciate all your help, and more so, your patience with a newbie!
Once the update has completed flashing from the SD card, is my phone back to stock minus the *relocked* stamp in bootloader? Or are there other flashes that I will need to apply to bring software and hardware up to date?
jdub1983 said:
Garming & Behold_this, Thank you!
Once the Rom.zip is done, what else do i need to do?
for understanding purposes, what happened? I'm very curious person and followed directions very carefully. Anyway, again, thank you both for such quick replies.
---------- Post added at 09:39 PM ---------- Previous post was at 09:18 PM ----------
Thank you both for your input last night and today! I greatly appreciate all your help, and more so, your patience with a newbie!
Once the update has completed flashing from the SD card, is my phone back to stock minus the *relocked* stamp in bootloader? Or are there other flashes that I will need to apply to bring software and hardware up to date?
Click to expand...
Click to collapse
You should have been able to watch the flash output right there in the bootloader assuming the flash completed successfully you are on the latest firmware and software for t-mobile. There's nothing else you need to do as far as that. If you want to unlock again go to HTC dev get a new token and unlock as usual
Behold_this said:
You should have been able to watch the flash output right there in the bootloader assuming the flash completed successfully you are on the latest firmware and software for t-mobile. There's nothing else you need to do as far as that. If you want to unlock again go to HTC dev get a new token and unlock as usual
Click to expand...
Click to collapse
I do, Id like to use a different rom as i got used to the ROM i was using.
Do you have any guides that you have posted yourself that I can read though. You are very good at what you do and appreciate your help!
Thank you! again!
jdub1983 said:
I do, Id like to use a different rom as i got used to the ROM i was using.
Do you have any guides that you have posted yourself that I can read though. You are very good at what you do and appreciate your help!
Thank you! again!
Click to expand...
Click to collapse
No, guides aren't really my thing, but there's a whole bunch a good ones out there. If I were you, I would start my search in the international M8 "general" subforum. Also Garmig's thread is another great resource. Happy reading.
Behold_this said:
No, guides aren't really my thing, but there's a whole bunch a good ones out there. If I were you, I would start my search in the international M8 "general" subforum. Also Garmig's thread is another great resource. Happy reading.
Click to expand...
Click to collapse
Thanks Brother!
Hello, I've been learning how to root my phone and flashing new ROMS. I was having a pleasant time doing it when I made the mistake of possibly flashing the wrong version of GPE to my phone. After that, it seems my phone won't connect to 3G, LTE, or even basic phone service to make calls.
I've been looking for two days trying to find answers on the forum but I couldn't find a straightforward answer to my question. If anyone could help, I would greatly appreciate it. I think my next step is to use SunShine to S-OFF my phone and attempt to install stock firmware, but I'm a bit hesitant after doing something so negative to my phone.
My bootloader has the following information:
Code:
*** Software status: Modified ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.19.0.0000
[email protected]
OpenDSP-v47.2.2-00564-M8974_F0.1024
OS-
eMMC-boot 2048MB
Mar 4 2016, 18.56.55.0
^ Yes, OS is actually empty. I haven't seen any instances of this on the forums yet...
fastboot getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) 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
Other steps I've taken:
- Tried SIM card in another phone, it was working fine
- Flash stock ROM and recovery using this thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860. The flashing worked but I still can't connect to AT&T.
- A couple of other miscellaneous things around the forums that didn't really amount to much when I tried them
Again, any help would be greatly appreciated!
EDIT:
SOLVED
I encourage you to read the details to make sure the case matches yours, but TL;DR: no need for S-OFF, simply use lock the bootloader again using "fastboot oem lock" and install the stock RUU. If stock RUU fails make sure you have the correct version. Thanks so much to redpoint73 for their help!
My responses below in red font:
norcrel said:
I made the mistake of possibly flashing the wrong version of GPE to my phone.
What exactly did you flash (exact file name)?
After that, it seems my phone won't connect to 3G, LTE, or even basic phone service to make calls.
I think my next step is to use SunShine to S-OFF my phone and attempt to install stock firmware
You don't need s-off to do that, I don't know why folks keeping thinking that you do. Don't spend the money on sunshine yet (at least, not just to restore to stock).
^ Yes, OS is actually empty. I haven't seen any instances of this on the forums yet...
I've seen this on the forums literally maybe 100 times or more. It means you used a very outdated (over a year old) version of TWRP, which has the known bug of wiping the main version info. What version TWRP did you use? And why?
- Flash stock ROM and recovery using this thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860. The flashing worked but I still can't connect to AT&T.
Which version number did you flash, if you don't know the version number?
Click to expand...
Click to collapse
My suggestion would be to relock the bootloader with fastboot command: fastboot oem lock
(don't worry, you can always unlock it again when the phone is working properly)
Then run the following RUU: http://dl3.htc.com.s3.amazonaws.com/application/RUU_M8_UL_L50_SENSE60_ATT_MR_Cingular_US_4.28.502.2_Radio_4.0.U605611%4050319A_40.45.C33065.00_F_release_446225_signed_2.exe
RUU is a Windows executable program. Just connect the phone to PC, boot into bootloader-fastboot mode, and run the RUU, and it will do the rest (restore all partitions to stock condition).
redpoint73 said:
My suggestion would be to relock the bootloader with fastboot command: fastboot oem lock
(don't worry, you can always unlock it again when the phone is working properly)
Then run the following RUU: http://dl3.htc.com.s3.amazonaws.com/application/RUU_M8_UL_L50_SENSE60_ATT_MR_Cingular_US_4.28.502.2_Radio_4.0.U605611%4050319A_40.45.C33065.00_F_release_446225_signed_2.exe
RUU is a Windows executable program. Just connect the phone to PC, boot into bootloader-fastboot mode, and run the RUU, and it will do the rest (restore all partitions to stock condition).
Click to expand...
Click to collapse
Thanks for the quick response. I used the GPe ROM in this thread: http://forum.xda-developers.com/showthread.php?t=2708589
The file name was HTC_One_M8_GPe_Marshmallow-6.0_MRA58K.H13_AROMA-Installer.zip
The TWRP version I used was 3.0.2, the file was named Flashable_TWRP_3.0.2-0_M8.zip and I found it here: https://www.androidfilehost.com/?w=files&flid=49756
Before using 3.0.2 I was using an earlier 2.x.x version. I believe it was 2.7.0.2, because I used the tool in this thread to do my initial unlock: http://forum.xda-developers.com/showthread.php?t=2699065
The stock TWRP backup/recovery version I used was 4.28.502.2, found on this thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860 I used TWRP 3.0.2 to perform the backup.
I actually already downloaded the RUU and attempted to use it, but it failed. I didn't perform a 'fastboot oem lock' before trying to use it, however, so I'll try that again when I get the chance and get back to you. Unfortunately at work I don't have a windows PC to run the executable, so I'll have to do it tonight when I get home in a couple of hours from now. Thanks again for taking time to give me advice!
norcrel said:
Thanks for the quick response. I used the GPe ROM in this thread: http://forum.xda-developers.com/showthread.php?t=2708589
The file name was HTC_One_M8_GPe_Marshmallow-6.0_MRA58K.H13_AROMA-Installer.zip
Click to expand...
Click to collapse
That version looks fine for use with your phone (not the wrong version, as you mention in your top post). Not sure why you have the SIM issue. Did you do a default wipe (user data, Dalvik, and cache) in TWRP before flashing the ROM? This is recommended.
Also recommended to make a TWRP backup, before wiping and flashing any ROM.
norcrel said:
The TWRP version I used was 3.0.2, the file was named Flashable_TWRP_3.0.2-0_M8.zip and I found it here: https://www.androidfilehost.com/?w=files&flid=49756
Before using 3.0.2 I was using an earlier 2.x.x version. I believe it was 2.7.0.2, because I used the tool in this thread to do my initial unlock: http://forum.xda-developers.com/showthread.php?t=2699065
Click to expand...
Click to collapse
As suspected, it was the 2.7 version TWRP that cause your version-main number to be erased in getvar and bootloader. This doesn't cause any particular issues, except making it harder to determine the firmware number. When you run the RUU, the version number will be restored.
Your main mistake was using the toolkit. As you see from the toolkit thread, it hasn't been updated since April 2014! So it contains a number of obsolete files, that will cause various issues. Its easy to do the steps manually (unlock bootloader, flash TWRP via fastboot, etc.) and use the current files; and I encourage folks to do so, as its a better learning experience.
norcrel said:
I actually already downloaded the RUU and attempted to use it, but it failed. I didn't perform a 'fastboot oem lock' before trying to use it
Click to expand...
Click to collapse
The RUU should work, once you unlock the bootloader. But if it fails again, not the Error number and error message, and post those here.
redpoint73 said:
The RUU should work, once you unlock the bootloader. But if it fails again, not the Error number and error message, and post those here.
Click to expand...
Click to collapse
When I tried to do fastboot oem lock I also got something strange. Here is the log posted below:
Code:
fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [ERR] Cannot halt SPMI arbiter!!
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Invalid argument))
finished. total time: 1.212s
But afterwards my phone still read *** RELOCKED ***, so I continued on.
I tried the RUU and it failed (error code 155 - unknown) but I realized I was using a different one than the one you posted. I got mine off HTC's webpage, a file named RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5. Downloading your file now and I'll give it another shot.
And it worked! Thank you so much for your help! I'll make some notes on the original post. Am I correct in thinking that I downloaded the wrong version for my stock RUU? How did you know which version to use?
norcrel said:
Am I correct in thinking that I downloaded the wrong version for my stock RUU? How did you know which version to use?
Click to expand...
Click to collapse
Wrong RUU? Yes and no, its a bit complicated.
The RUU you tried is correct, in that its for the AT&T version M8 (right CID and MID). And in the past, running a newer RUU (then the firmware currently on the phone) would have been fine (as long as its intended for your M8 version's CID and MID). But HTC did something new (and a bit strange IMO) with all the Marshmallow RUUs; in that if you try to come from a lower version (LP or KK) you get Error 155. Of course, the description of Error 155 "unknown error" isn't very helpful, and has left lots of folks puzzled. But the solution to running the MM RUU is to first flash the MM firmware manually with fastboot command, then run the RUU again. The process is described in more detail here: http://forum.xda-developers.com/showpost.php?p=66886759&postcount=23
Or the other option to update to MM, if you actually use AT&T as your provider, is to OTA update from LP to MM (which works fine).
Now how I guessed you were still on LP (and the corresponding RUU) is a bit complicated as well. As you know, your main version was blank, so you can't determine the firmware number that way. You can normally correlate the radio numbers with the firmware version (some RUUs actually include the radio number in the file name, otherwise you just have to know what radio numbers correspond to which OS version). But in your case, the baseband numbers actually didn't match any of the radio numbers known by me, or listed in the RUU file names. So frankly, it was an educated guess. I've assumed that many folks have not yet updated to MM firmware (by official OTA, or otherwise), so I picked the latest version LP RUU.
If my guess was wrong, it would have meant your device was already on MM firmware, and trying to run the LP RUU would similarly give you Error 155, or wrong version number error. In which case, I would have just told you to run the MM RUU (the 6.20.520 you first tried)!
Make sense? Of course not!