Hi, any help would be greatly appreciated. Disclaimer - I'm only about 6 hours old into the world of unlocking, rooting, and S-OFF. I have an AT&T HTC One M8 and clearly made a poor choice in attempting a GPE conversion and should have just been patient for the 5.0 update. Anyhow, I successfully unlocked by device using the HTC unlock process. The trouble came during the middle of this guide (URL blocked) for achieving S-OFF.. I think the problem was that I downloaded the insertcoin OTA update instead of the insertcoin Full Rom and tried flashing that. Clearly didn't work. After that I tried flashing directly to the GPE ROM, but that failed as well. Then tried flashing back to stock AT&T HTC One M8, but still getting a myriad of errors ranging from FAILED (remote: 99 unkown fail), FAILED (remote: 12 signature verify fail), FAILED (remote:32 header error), etc. The main problem I'm running in to is that when i boot the device, it hangs on the HTC loading screen. When I check the bootloader it shows "S-On" and "Unlocked" and "Tampered".
My only idea at this point is to get a microSD card to load the appropriate insertcoin Full Rom and pick up the S-Off process where I left off. Any ideas on how to fix this via the RUU process?
Thanks in advance.
Hi,
You could ask for help in the thread of the guide you followed, but I will have your thread moved to your device section.
Good luck!
kylezumstein said:
Hi, any help would be greatly appreciated. Disclaimer - I'm only about 6 hours old into the world of unlocking, rooting, and S-OFF. I have an AT&T HTC One M8 and clearly made a poor choice in attempting a GPE conversion and should have just been patient for the 5.0 update. Anyhow, I successfully unlocked by device using the HTC unlock process. The trouble came during the middle of this guide (URL blocked) for achieving S-OFF.. I think the problem was that I downloaded the insertcoin OTA update instead of the insertcoin Full Rom and tried flashing that. Clearly didn't work. After that I tried flashing directly to the GPE ROM, but that failed as well. Then tried flashing back to stock AT&T HTC One M8, but still getting a myriad of errors ranging from FAILED (remote: 99 unkown fail), FAILED (remote: 12 signature verify fail), FAILED (remote:32 header error), etc. The main problem I'm running in to is that when i boot the device, it hangs on the HTC loading screen. When I check the bootloader it shows "S-On" and "Unlocked" and "Tampered".
My only idea at this point is to get a microSD card to load the appropriate insertcoin Full Rom and pick up the S-Off process where I left off. Any ideas on how to fix this via the RUU process?
Thanks in advance.
Click to expand...
Click to collapse
I think you're highly mistaken on the whole ordeal you're in. You're not going to obtain S-OFF from a ROM. Only way you're going to get S-OFF is from Firewater or Sunshine, most likely Sunshine but it costs $25. Also you cant just flash a GPE rom over Sense and assume that you now have a GPE phone, there's way more to it than that. You're lucky that you havent bricked your phone yet. We have the 4.4.3 RUU here, download it and flash through ADB. I'd recommend staying on stock until you learn more about what you're doing.
CavyS said:
You're not going to obtain S-OFF from a ROM. Only way you're going to get S-OFF is from Firewater or Sunshine, most likely Sunshine but it costs $25.
Click to expand...
Click to collapse
I think some folks have mentioned that InsertCoin works okay with firewater, but stock ROM (with root) should work as well (if firewater is going to work at all).
---------- Post added at 01:02 PM ---------- Previous post was at 12:46 PM ----------
kylezumstein said:
Then tried flashing back to stock AT&T HTC One M8, but still getting a myriad of errors ranging from FAILED (remote: 99 unkown fail), FAILED (remote: 12 signature verify fail), FAILED (remote:32 header error), etc.
Any ideas on how to fix this via the RUU process?
Click to expand...
Click to collapse
If you are trying to RUU and getting those messages, you are either running the improper RUU (needs to be for AT&T version specifically) or (my guess) you have not relocked the bootloader (required to RUU when S-on).
Fail errors when trying to flash a ROM from recovery can often be fixed by fastboot erase cache, and install recovery again by fastboot (and update the version, if you are not on a current one already).
Also, if you are trying to adb sideload flash (and failing), its sometimes more reliable to adb push a ROM to phone storage, or transfer to the removable SD (as you already mentioned you will try) then flash via custom recovery.
Thanks for your help. Quick update: I was able to get booted on a working rom (insertcoin), but my wifi doesn't work. I'm trying to get back to Stock AT&T Sense with working wifi. For some reason adb and fastboot no longer recognize my phone when on the bootloader. Interestingly, adb does recognize the phone when it is booted into the OS. I've tried on Windows 7, 8.1, and linux. Uninstalled adb and fastboot and reinstalled, updated windows drivers, tried different cables; no dice. I'm still S-On, unlocked bootloader, on the Insertcoin rom (http://insertcoin-roms.org/category/devices/onem8/).
Since I can't work via adb or fastboot, I downloaded the stock backup for my CID (CWS_001) from this page (http://forum.xda-developers.com/showthread.php?t=2701376) - under "stock nandroid backups" and CWS_001. I tried flashing this (1.58.502.1.zip) both through Flashify and through TWRP recovery, but both approaches returned "Failed".
Any thoughts on how to fix the adb/fastboot issue, why the stock backup failed, or more generally - other approaches to getting back to stock/working wifi?
kylezumstein said:
Thanks for your help. Quick update: I was able to get booted on a working rom (insertcoin), but my wifi doesn't work. I'm trying to get back to Stock AT&T Sense with working wifi. For some reason adb and fastboot no longer recognize my phone when on the bootloader. Interestingly, adb does recognize the phone when it is booted into the OS. I've tried on Windows 7, 8.1, and linux. Uninstalled adb and fastboot and reinstalled, updated windows drivers, tried different cables; no dice. I'm still S-On, unlocked bootloader, on the Insertcoin rom (http://insertcoin-roms.org/category/devices/onem8/).
Since I can't work via adb or fastboot, I downloaded the stock backup for my CID (CWS_001) from this page (http://forum.xda-developers.com/showthread.php?t=2701376) - under "stock nandroid backups" and CWS_001. I tried flashing this (1.58.502.1.zip) both through Flashify and through TWRP recovery, but both approaches returned "Failed".
Any thoughts on how to fix the adb/fastboot issue, why the stock backup failed, or more generally - other approaches to getting back to stock/working wifi?
Click to expand...
Click to collapse
I have the exact same situation but haven't been able at all to flash a Sense ROM, I've tried ARHD, Viper, CleanROM 3.0, GPe RUU, both 1.58.502 and 2.23.502 ruu executables and none have worked for this. I'm stuck with Cyanogenmod 11 and can't even sinunlock the device, which is in South America right sitting as a brick on my desktop.
Please anyone, can help?
The wifi is due to mismatched firmware Im thinking, you need to flash back to your original build of software if on an att device it would be a 4.4.2 build or the 2.23 4.4.3 build. Unsure of the adb and fastboot issues.CWS_001 is not right should be CWS__001 if you have changed cid to what you posted this could be an issue as well.
kylezumstein said:
Thanks for your help. Quick update: I was able to get booted on a working rom (insertcoin), but my wifi doesn't work. I'm trying to get back to Stock AT&T Sense with working wifi. For some reason adb and fastboot no longer recognize my phone when on the bootloader. Interestingly, adb does recognize the phone when it is booted into the OS. I've tried on Windows 7, 8.1, and linux. Uninstalled adb and fastboot and reinstalled, updated windows drivers, tried different cables; no dice. I'm still S-On, unlocked bootloader, on the Insertcoin rom (http://insertcoin-roms.org/category/devices/onem8/).
Since I can't work via adb or fastboot, I downloaded the stock backup for my CID (CWS_001) from this page (http://forum.xda-developers.com/showthread.php?t=2701376) - under "stock nandroid backups" and CWS_001. I tried flashing this (1.58.502.1.zip) both through Flashify and through TWRP recovery, but both approaches returned "Failed".
Any thoughts on how to fix the adb/fastboot issue, why the stock backup failed, or more generally - other approaches to getting back to stock/working wifi?
Click to expand...
Click to collapse
rafucho said:
I have the exact same situation but haven't been able at all to flash a Sense ROM, I've tried ARHD, Viper, CleanROM 3.0, GPe RUU, both 1.58.502 and 2.23.502 ruu executables and none have worked for this. I'm stuck with Cyanogenmod 11 and can't even sinunlock the device, which is in South America right sitting as a brick on my desktop.
Please anyone, can help?
Click to expand...
Click to collapse
kylezumstein said:
Since I can't work via adb or fastboot, I downloaded the stock backup for my CID (CWS_001) from this page (http://forum.xda-developers.com/showthread.php?t=2701376) - under "stock nandroid backups" and CWS_001. I tried flashing this (1.58.502.1.zip) both through Flashify and through TWRP recovery, but both approaches returned "Failed".
Click to expand...
Click to collapse
Its not a ROM zip, its a nandroid backup folder. You need to extract the files from the zip, and place it in the exact location specified in the 2nd post of the backup collection thread (see second question under "Questions & Answers"). Then once the files are in the correct location, TWRP will see it and show it under the Restore main menu selection.
However, you also have the added complication that adb/fastboot are not working. You can try to change the default TWRP backup location to the removeable SD (it uses internal storage by default), make a backup in order to create the proper backup folder (your serial number) on your SD card. Then transfer the downloaded nandroid files to that folder.
But its probably easier to just download a ROM zip that matches your firmware, and put it on the SD card. The difference is that a ROM zip can be anywhere, and you can browse in TWRP, find the ROM zip and flash it. A nandroid backup has to be in the exact correct location, otherwise TWRP will never even show it under "Restore".
---------- Post added at 10:44 AM ---------- Previous post was at 10:39 AM ----------
rafucho said:
I have the exact same situation but haven't been able at all to flash a Sense ROM, I've tried ARHD, Viper, CleanROM 3.0, GPe RUU, both 1.58.502 and 2.23.502 ruu executables and none have worked for this. I'm stuck with Cyanogenmod 11 and can't even sinunlock the device, which is in South America right sitting as a brick on my desktop.
Please anyone, can help?
Click to expand...
Click to collapse
No, we really can't help. Mostly because you haven't provided enough information.
1) When you say "none have worked" what does that even mean??? What is the outcome, what are the error messages, etc.
2) Do yourself a favor, and don't ever say on this forum you have the "exact same situation". Do you really have the exact same situation as the OP down to every single detail? I can virtually guarantee you don't. And therefore, we can only guess what critical details are the same, and which are different. Its impossible to try to help without knowing those details.
3) What hboot, what radio, what recovery and version number?
4) S-on or s-off?
5) If s-on, did you relock the bootloader when trying to run RUU? If not, it will FAIL by definition.
Provide as much detail as possible, if you want the proper help.
Hi @redpoint73
1) When you say "none have worked" what does that even mean??? What is the outcome, what are the error messages, etc.
Ok this is the output of the installation for Viper ROM 2.5.0:
see attached
Creating toolbox symlinks
Installing busybox
set_perm: chown of /system/xbin/busybox to 0 1000 failed: No such file or directory
set_perm: chmod of /system/xbin/busybox to 755 failed: No such file or directory
script aborted: set_perm: some changes failed
set_perm: some changes failed
Installer Error (Status 7)
Click to expand...
Click to collapse
2) Do yourself a favor, and don't ever say on this forum you have the "exact same situation". Do you really have the exact same situation as the OP down to every single detail? I can virtually guarantee you don't. And therefore, we can only guess what critical details are the same, and which are different. Its impossible to try to help without knowing those details.
3) What hboot, what radio, what recovery and version number?
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.58.502.1
(bootloader) version-misc: PVT SHIP S-ON
(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: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.060s
4) S-on or s-off?
S-ON
5) If s-on, did you relock the bootloader when trying to run RUU? If not, it will FAIL by definition.
I did relock the bootloader befor using the RUUs, and also got the error message: IMAGE ERROR, I mostly think this is due to the fact the partition sizes are smaller
Code:
[email protected]:/ $ df
Filesystem Size Used Free Blksize
/dev 912.2M 132.0K 912.1M 4096
/sys/fs/cgroup 912.2M 12.0K 912.2M 4096
/mnt/asec 912.2M 0.0K 912.2M 4096
/mnt/obb 912.2M 0.0K 912.2M 4096
/mnt/fuse 912.2M 0.0K 912.2M 4096
/system 1006.7M 417.8M 588.8M 4096
/data 26.3G 3.1G 23.2G 4096
/cache 678.4M 10.8M 667.6M 4096
/firmware/radio 199.8M 44.3M 155.5M 4096
/firmware/adsp 199.8M 8.9M 190.9M 4096
/firmware/wcnss 199.8M 3.8M 196.0M 4096
/devlog 29.5M 23.6M 5.9M 4096
/fataldevlog 19.6M 13.0M 6.6M 4096
/custdata 49.2M 4.0M 45.2M 4096
/mnt/shell/emulated: Permission denied
/storage/emulated 912.2M 0.0K 912.2M 4096
/mnt/media_rw/sdcard1: Permission denied
/mnt/secure/asec: Permission denied
/storage/sdcard1 29.2G 352.0K 29.2G 16384
/storage/emulated/0 26.3G 3.1G 23.2G 4096
/storage/emulated/legacy 26.3G 3.1G 23.2G 4096
1|[email protected]:/ $
rafucho said:
Hi [MENTION=660462]
I did relock the bootloader befor using the RUUs, and also got the error message: IMAGE ERROR, I mostly think this is due to the fact the partition sizes are smaller
Click to expand...
Click to collapse
Incorrect, going from Sense ROM and running a Sense RUU, there isn't a difference in partitions.
Image error usually means you are running the wrong RUU, but the ones you mentioned are correct for the AT&T version.
Download the RUUs again, and verify the bootloader is RELOCKED, and I don't see any reason why it shouldn't run. Make sure you have a minimum of firewalls on your PC, running with PC admin rights, etc.
Try this bootable RUU: http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486
As far as flashing custom ROMs, try fastboot erase cache, and re-install custom recovery (latest version, if not already). This fixes a great many ROM flashing errors.
redpoint73 said:
Its not a ROM zip, its a nandroid backup folder. You need to extract the files from the zip, and place it in the exact location specified in the 2nd post of the backup collection thread (see second question under "Questions & Answers"). Then once the files are in the correct location, TWRP will see it and show it under the Restore main menu selection.
However, you also have the added complication that adb/fastboot are not working. You can try to change the default TWRP backup location to the removeable SD (it uses internal storage by default), make a backup in order to create the proper backup folder (your serial number) on your SD card. Then transfer the downloaded nandroid files to that folder.
But its probably easier to just download a ROM zip that matches your firmware, and put it on the SD card. The difference is that a ROM zip can be anywhere, and you can browse in TWRP, find the ROM zip and flash it. A nandroid backup has to be in the exact correct location, otherwise TWRP will never even show it under "Restore".
Click to expand...
Click to collapse
THANK YOU! The restore process you outlined is exactly what I was missing. I'm still going through and restoring apps and testing a number of other things, but after going through the process you outlined above, I now have working wifi and everything appears to be back to stock.
I will update with any other irregularities, but so far my problem seems to be solved.
This was my RUU process
{
"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"
}
rafucho said:
This was my RUU process
Click to expand...
Click to collapse
Hold on a second. From your photo, I see you have the black hboot screen which is only for GPE.
Did you try to run a GPE RUU?
Thanks again for your help. I was able to get back on stock Sense via the backup process you outlined and have restored most of my apps and settings via HTC backup. Wifi is now working as well. I'm running into issues removing the "tampered", "unlocked" flags from the bootloader as well as unrooting. (I did the unroot process via SuperSU, but I'm not sure if it completed or how to check if I am unrooted. I also seem to understand that unrooting might be the last step of the process here).
I think I have two main challenges in completing those final three steps: 1. I'm still S-ON and 2. I'm having trouble connecting to my laptop via adb and fastboot. adb devices works when the phone is booted into the OS, but it doesn't return anything when the phone is on fastboot usb mode on the bootloader. Likewise, fastboot devices returns nothing on the OS or in the bootloader, but it does return the device when preceeding it with sudo (still only in the bootloader). S-Off seems like it could be achieved simply with $25 and Sunshine (confirmed via the Sunshine test).
Normally I wouldn't bother with these final three steps, but it seems to be preventing me from taking an OTA update (I'm listed on 4.4.2 and I'm pretty sure AT&T pushed 4.4.3 a few months ago) as well as preventing my work email via Mobile Iron from fully installing (although there are workarounds for this issue).
Any thoughts on how to resolve the above? The adb/fastboot issue has been plaguing my phone for multiple ROM and recovery flashes now (e.g. it's not a new issue).
redpoint73 said:
Hold on a second. From your photo, I see you have the black hboot screen which is only for GPE.
Did you try to run a GPE RUU?
Click to expand...
Click to collapse
Hi there, I bought the phone off eBay... Sadly I received it like this, I think they tried the GPE RUU and later on a Cyanogenmod.
rafucho said:
Hi there, I bought the phone off eBay... Sadly I received it like this, I think they tried the GPE RUU and later on a Cyanogenmod.
Click to expand...
Click to collapse
I suggest going back to the seller. Unless the seller clearly stated in the item description that a bootloader inappropriate for the version is installed, and the device possibly can't be returned to Sense, then I'd say the description was misleading and deceptive. They may have sold the device knowing they botched it. Or at least, the seller didn't fully know what they were doing.
You can also look to see if others with a similar GPE partition problem have solved the issue. But I have a feeling S-off is needed to do so, and to me, its not worth spending $25 on sunshine s-off for a device that was sold in a seemingly deceptive manner.
Also, since the device is 2nd hand, its hard to know exactly what was done to it. Its very possible the device was s-off, then the seller returned it to s-on in order to sell it.
---------- Post added at 10:51 AM ---------- Previous post was at 10:36 AM ----------
kylezumstein said:
Thanks again for your help. I was able to get back on stock Sense via the backup process you outlined and have restored most of my apps and settings via HTC backup. Wifi is now working as well. I'm running into issues removing the "tampered", "unlocked" flags from the bootloader as well as unrooting. (I did the unroot process via SuperSU, but I'm not sure if it completed or how to check if I am unrooted. I also seem to understand that unrooting might be the last step of the process here).
Click to expand...
Click to collapse
You can check root simply by trying an app that requires root. Titanium Backup is one (of probably many) that will return an error message immediately when you open the app for the first time (after installation) saying the device is not rooted. Or there are various "root checker" apps on the Play Store.
I believe if you still have custom recovery installed, you will have the TAMPERED banner.
You can only go to RELOCKED with s-on. With s-off, you can make this flag LOCKED. But this isn't necessary to get OTAs, or any other functions on the phone. For the few functions that check the bootloader lock status, RELOCKED will do the same as LOCKED.
kylezumstein said:
I think I have two main challenges in completing those final three steps: 1. I'm still S-ON and 2. I'm having trouble connecting to my laptop via adb and fastboot. adb devices works when the phone is booted into the OS, but it doesn't return anything when the phone is on fastboot usb mode on the bootloader. Likewise, fastboot devices returns nothing on the OS or in the bootloader, but it does return the device when preceeding it with sudo (still only in the bootloader).
Any thoughts on how to resolve the above? The adb/fastboot issue has been plaguing my phone for multiple ROM and recovery flashes now (e.g. it's not a new issue).
Click to expand...
Click to collapse
Those aren't issues, those are working as they are intended to work.
Fastboot only works when the phone is in fastboot mode (selected in bootloader and USB cable connected).
Adb only works within the OS, or alternately in recovery. It won't work in bootloader.
kylezumstein said:
Normally I wouldn't bother with these final three steps, but it seems to be preventing me from taking an OTA update (I'm listed on 4.4.2 and I'm pretty sure AT&T pushed 4.4.3 a few months ago) as well as preventing my work email via Mobile Iron from fully installing (although there are workarounds for this issue).
Click to expand...
Click to collapse
4.4.3 OTA was released, but then "pulled" due to battery drain issues experienced by some folks. Therefore, 4.4.2 is actually the current version until 4.4.4 is released. You can still install 4.4.3 by RUU if you like (RUU does not suffer the battery issue).
Also, locked bootloader is not required for OTA. Nor do you need to unroot. What is required to install the OTA is for system files all be in the "stock" condition (none modified by root) and stock recovery. But even so, none of this will prevent the OTA notification, it will just cause the install to fail.
The TAMPERED banner should go away once stock recovery is installed.
So in short, stock ROM and stock recovery to get and install OTAs. Bootloader unlocked doesn't matter, nor does root. For the AT&T OTAs, you also need to be on AT&T's network. This is a specific AT&T thing, most other versions/carriers don't have this requirement.
Folks having issues going back to Sense from a full GPE conversion can try the method here: http://forum.xda-developers.com/showthread.php?t=2733523
Or here: http://forum.xda-developers.com/showthread.php?t=2721435
Only works with s-off.
Related
Sorry for long post but I've tried to provide a sufficient level of detail. If the answer is in another thread let me know. I've read quite a few of them now!
I've had my flyer for a short time and was loving it until I tried to mod it.
I installed CWM and Superuser root and had it "S-Off". I tried to flash the Leedroid HC rom. It seemed to be dead on re-boot just the HTC screen. I did a restore from CWM and got Gingerbread back. Some apps like default browser did not work though.
Now I had a mostly working system I followed the O'brian (think' that correct name) including using official HTC unlocker as was in instructions. Tried to use another HC rom and the ARU wizard. I got an error 155 and an RUU failure msg on device. Not sure what to do know. I have download this file "Best RUU_Flyer_HTC_WWE_2.23.405.3_R_Radio_20.3504.30.089BU_3809.07.04.06_M_release_204108_signed". Nothing much happens when I run it other than seeing the install screen, then it exits. I really need some help to get back to some kind of working system.
Been through thread "[GUIDE][Flyer+View]Gingerbread S-
OFF/Recovery/Permaroot"
Can't follow post 17 to get S-Off as device will not boot into android!
From CWM Backup, the external SD card I used seem to have got corrupted. This could have been root of problems
data.img - file error
cache.img - file error
nandroid.md5 - file error
Boot.img, recovery.img and system.img files seem ok...
Got this msg from "revolutionary.exe" when tried to get -"S-Off" again.
Found your device: /sbin/sh: getprop: not found (/sbin/sh: getprop: not-/sbin/sh
: getprop: not, Android: /sbin/sh: getprop: not, ROM version: /sbin/sh
Your device: /sbin/sh: getprop: not, with HBOOT /sbin/sh: getprop: not is
not supported at this time.
Here are my device details:
INFOversion: 0.5
INFOversion-bootloader: 1.11.0011
INFOversion-baseband: 3822.10.08.07_M
INFOversion-cpld: None
INFOversion-microp: 0950
INFOversion-main: 2.23.405.4
INFOserialno: HT15WT403213
INFOimei: xxxxxxxxxxxxxxxx
INFOproduct: flyer
INFOplatform: HBOOT-7230
INFOmodelid: PG4110000
INFOcidnum: HTC__054
INFObattery-status: good
INFObattery-voltage: 4143mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: f0e1145e
INFOhbootpreupdate: 12
INFOgencheckpt: 0
I have hboot 1.11.0011 with CWM and access via ADB
Your help appreciated, at end of my tether!
allot to take in but best I could tell you were on gingerbread and maybe tried to flash Lee Droid HC version so that would not work. So then you followed an old thread to update to HC using Paul Obrien's method whcih requires HTC Dev unlock of the boot loader. At this point in time you can not flash any roms via recovery and your system will not boot into android.
Please confirm if I am following what happened to you and if while in your hboot screen it says Unlock up top.
Thanks for replying.
In summary that's correct.
If I hold down the vol-down button I get the screen that says:
"*** UNLOCKED ***"
"flyer PVT SHIP S-ON RL
HBOOT-1.11.0011
Micro P-0950
Radio 3822.10.08.07_M
eMMc-Boot
I still have USB access to it via fastboot I think
ok so here we go
no hc rom will just directly flash and boot because you can not overwrite the boot.img via recovery with HTC dev unlock. If you wanted to flash say Leedroid you would have to pull the boot.img from the rom package then fastboot flash it first then back to recovery and flash the rom. This is a hacky way to do it and to be honest every time you flashed a rom you would have to do the same. Here is what I suggest:
follow this thread here to downgrade
http://forum.xda-developers.com/showthread.php?t=1307759
you may likely be able to skip the misc version part. Hopefully you are aware of what your stock ruu is. If you tried running it before and it failed it was because you did not relock the boot loader prior to trying as is described in the thread I linked
Once, hopefully, you are back on GB, I would run this method to get to HC
http://forum.xda-developers.com/showthread.php?t=1358758
now, if you flashed a hc rom on your device and it will not boot, just as mentioned flash the boot.img via fastboot from the rom and it should boot. This is if you are looking for the easy fix, and assuming I understand everythign you have done to this point
I have downloaded this file to use as my stock RUU
"RUU_Flyer_HTC_WWE_2.23.405.3_R_Radio_20.3504.30.089BU_3809.07.04.06_M_relea
se_204108_signed.exe".
I will go through steps 1 to 8 of the thread and the rest if I can. I am not sure about step 8, it says boot to android. Are you saving if I managed to get that far I will have some kind of working system back before I proceed further?
I will have a go now and let you know how I get get long.
Cheers!
as I stated you may not need to do the misc version part. and you do not need to flash recovery and su if you already have both
I followed the steps and apllied the HTC unlocker again, then flashed the recover.img with no error messages and put the Super User zip on my external SD card. I used the CWM install from zip option, seemed to proceed, no errors reported. When I re-booted the tablet I just have an empty black screen and nothing else. Should I proceed with the RUU or stop and try something else?? If I turn it off it immediately comes back on again to blank screen. The only way to keep it turned off is to use the power down option on hboot menu.
you were unlocked
you already had recovery
you already had super user
you did not have to repeat any of these steps
if you can get into hboot then follow the instructions to revert assuming you have the three things mentioned above. You can likely skip the misc-version step. If you get a message while flashing the ruu that states older version you will have to do the misc-version step which since you can not boot into android can be done in recovery as adb will see your device in recovery
I do not really think you are in too bad of a way right now, but without meaning to offend you, you scare me with not paying attention to what is being said. One concern I have is to make sure you have enough battery life left. If you hit less than 30% you will not be able to run the RUU. If you are confident that you have that much continue. If not power down through fastboot and charge for a couple of hours.
Please read, read, read, and do nothing unless you are atleast 50% confident that you understand
Hi
I really appreciate the help you are giving me. The only did all the steps just in case as I am paranoid about missing something important. I do think I have enough battery so I will see if I can use the RUU I downloaded
Thanks
I am now running the RUU, it says "updating rom image". It is showing a black screen with the letters HTC in white in the middle. I hope this works.
Thanks for your help.
Comment has been edited, sorry for silly question, answered in thread you mentioned
that is normal
My god, I am so relieved. To tired to be estatic. It's taken me 24 hours and only two hours sleeps to get back to Stock! You save my bacon Mcord! The battery after flashing was nearly 100%. Thankfully I kept it charging even though it was bricked in an attempt to increase the rescue time I had. The only downside is I missed a ski class I'd paid for and having to pay the "Filefactory" company for a subscription so I could reliably download the RUU.
I've learnt the hard way for sure. Anybody else reading this don't assume that just reading the instructions is enough. My SD Card had corrupt backup recovery files on it. How often do we double-check the integrity of our backups? the SD card may have also mean that the rom loaded onto it was corrupt as well. I should have checked the MD5 of all the files.
Thanks again!! I think I'll pause a bit before Honeycomb and def backup!
happy your back up and running. your problem was just not fully understanding the differences between GB and HC and S off and HTC Dev unlock. the thread I linked you is the one to use going forward if moving to HC and looking to run custom roms. As I mentioned before read, read, read.
What if in addition adb don't work ?
Hello,
I tried to downgrade, but the adb command don't work : device not found response...
So I connot follow the process explained http://forum.xda-developers.com/showthread.php?t=1307759
Second the CWN is broken too... Is that a problem ?
Thanks
Been a lurker for a while, now I need some input if possible. I have a Thunderbolt whose touchscreen is not fully working, there is a strip about 1/4" wide top to bottom that does not respond to input. I rooted it using trter's Thunderbolt Tool and have been running Santod's ICS. When I decided to return to stock I did not read anything and merely ran trtr's tool and used the unroot option. This has me stuck now with a weird state.
Boot screen:
*** UNLOCKED ***
MECHA XD SHIP S-ON
HBOOT-1.05.0000
MICROP-/
RADIO-1.48.00.0930w_3
eMMC-boot
Jul 19 2011, 14:51:08
4ext recovery is still installed for some reason.
Here are things I have tried:
1. Unroot using trtr's tool - leaves me in a non-booting state with a Security warning and Main Version failure.
2. Used HTCDev unlock and pushed PG05IMG.zip of 2.11.605. This allows me to boot to a seemingly stock ROM.
3. OTA's get pushed, device reboots but OTA's fail to install.
4. Tried recovering Nandroid backups with 4ext, no matter which one I try to restore I get stuck in a boot loop (BAMF SoaB, ICS Santod, Liquid ICS, Multi-source ICS, ICS stock deodex).
5. Tried using 4ext to install the above ROMS directly, along with full wipes and partition formats before each attempt. They seem to install but get stuck in a boot loop on each.
6. Other various combinations of HTCdev, Thunderbolt Tool, FastBoot boot.img pushes, etc. Trtr's tool connecting in booted and fastboot modes fails to unroot or root or change S-ON state.
7. Did step 2 again to get me a working phone (except touch screen problem) until I can figure out WTH is going on.
Current state - the above Boot Screen details, 2.11.605.19 deodexed-signed image, and lucky I have not totally bricked it yet.
Help please? I've googled for the last 3 days and read countless posts and am not sure what to do from here. All I need is to get it back to stock so I can send it back to HTC and get a replacement. I have a working ADB set up and am willing to follow steps exactly or read whatever page you believe I have missed, or call me a dumb n00b, berate me for not reading something, anything... at this point I have no interest in retaining data on the phone or SD card or my dignity, just a stock phone that I can send back.
Thanks all!
Me too
google thunderboltforums How to Fix Security Warning - this is what trtr10 himself recommended to me . It didn't let me post, when I tried direct link.
Your #2 & #6 is similar, but maybe not exactly the same. It didn't work for me, though. And I had to add an adb manual lock step, because you need to be locked before trying trtr10s tool to unroot (or at least locked before it runs the final flash update, which fails for me with Main Version is older. Update Fail!
Also, technically the adb fastboot oem lock yields error #1:
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.459s
That's major coincidence I have exact same problem, down to dead touch screen strip. I've been trying to get unrooted for a week and was supposed to mail the thing back last Friday . .
Here's hoping a solution gets posted. I don't want to pay cuz the insurance refurb was fail, when my warranty service is supposed to be free replacement and it is stupid hardware failure.
All I can say is trter supposedly updated his tool to work with the latest ota, but its been about a week and he hasn't released it yet.
He did say something about having a problem with his host though.
washuai said:
google thunderboltforums How to Fix Security Warning - this is what trtr10 himself recommended to me . It didn't let me post, when I tried direct link.
Click to expand...
Click to collapse
This is how I fixed the security warning when I first got it, using HTCDev unlock. I also used adb fastboot relock to lock back before trying the tool.
washuai said:
Your #2 & #6 is similar, but maybe not exactly the same. It didn't work for me, though. And I had to add an adb manual lock step, because you need to be locked before trying trtr10s tool to unroot (or at least locked before it runs the final flash update, which fails for me with Main Version is older. Update Fail!
Also, technically the adb fastboot oem lock yields error #1:
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.459s
Click to expand...
Click to collapse
Yep - got that too...
Weird. Guess I'll wait for the new tool and see what it does...
As far as the identical touchscreen issue, this phone is also a refurb, my second with a touchscreen problem. The really weird part is that it works sometimes, particularly after all this work flashing and re-flashing, but I don't think it has anything to do with the ROMS or software, rather the fact that during all this work I am constantly doing battery pulls and SD card swaps and maybe it's because of a flaky ribbon connection or something - if it was not under warranty I would open it up and just try reseating anything I could find inside.
Have you tried to RUU back? It is a way manufacturers refurb or make the software new again without having to figure out what state it is in.
As long as you can get in fastboot it will work... Also could you possibly fastboot an ENG HBOOT? It doesn't show if it's unlocked nor does
it have any of those pink banners up at top.... Those I believe allow you to flash anything you couldn't normally do before... Try that.. Also I
ALWAYS manually push and flash my stuff through ADB and fastboot. It is faster (if you know what you are doing) AND it has better control
over what I am doing. I made a tut on how to flash boot screens (the very first image that comes up when you turn it on) and it is just about
same commands to flash normally stuff.
I run a Linux Box and always use root terminal so I am not certain at what point you would need superuser if any but as follows
#fastboot devices
#fastboot flash zip "name of zip" (no it doesn't have to be called anything specific, it could be called file1.zip)
#fastboot erase [option] /cache /data /system
to force it into the special RUU mode to use HTC's RUU, this is the command
#fastboot oem rebootRUU
Linux too Yes, I can flash via fastboot, I'm concerned about which one to flash though, I don't want to brick...
jnorth said:
Linux too Yes, I can flash via fastboot, I'm concerned about which one to flash though, I don't want to brick...
Click to expand...
Click to collapse
If you can give me today and I'll send you either the link to download the RUU or the exe itself.
You have the new radios installed and need to downgrade them by going s-off again. Need to do this to avoid main version errors.
The ota's don't install because of the custom recovery.
Backups don't work because your s-on and the kernel can be installed.
You may be able to install santod's ota rom in recovery and install the boot.IMG from the rom (kernel) in fasboot = ./fastboot flash boot boot.img
Relock the boot loader and send it in looking like stock.
There is also a way to spoof your main version and downgrade from ICS to GB Ruu stock. That is posted on another site.
Sent from my ConD3m3dPaC-man ADR6425LVW using xda app-developers app
tburns said:
You have the new radios installed and need to downgrade them by going s-off again. Need to do this to avoid main version errors.
Click to expand...
Click to collapse
Working on this now, as soon as I figure out how to get s-off again. Thanks!
http://androidfiles.org/ruu/?developer=Mecha
The RUU's to take you back to stock
Thanks to hints from you both, I am back to stock... probably more steps than were needed but it worked for me LOL.
1. Used part of the Revolutionary tool to get S-Off again and let it install CWM over 4ext
2. Re-rooted
3. Installed 2.11.605.9 radio and GB OTA rom
4. Used fastboot to put stock hboot back
Appears to be normal stock now and OTA in progress.
Thank you both again!
jnorth said:
Thanks to hints from you both, I am back to stock... probably more steps than were needed but it worked for me LOL.
1. Used part of the Revolutionary tool to get S-Off again and let it install CWM over 4ext
2. Re-rooted
3. Installed 2.11.605.9 radio and GB OTA rom
4. Used fastboot to put stock hboot back
Appears to be normal stock now and OTA in progress.
Thank you both again!
Click to expand...
Click to collapse
that is what the community is all about , right?
Exactly!
One last question - bootloader says ***RELOCKED*** instead of ***LOCKED*** - presumably because I used the HTCdev unlocker at one point... is that fixable or permanent?
jnorth said:
Exactly!
One last question - bootloader says ***RELOCKED*** instead of ***LOCKED*** - presumably because I used the HTCdev unlocker at one point... is that fixable or permanent?
Click to expand...
Click to collapse
you could ALWAYS use an ENG and nobody would be non-the-wiser if you rooted or not! It would look like a developer phone instead..
when it says ***RELOCKED*** it tells anybody and everybody you have been rooted at one point or another (no bueno for warranty)
jnorth said:
Exactly!
One last question - bootloader says ***RELOCKED*** instead of ***LOCKED*** - presumably because I used the HTCdev unlocker at one point... is that fixable or permanent?
Click to expand...
Click to collapse
this -SHOULD- take care of the pink banner up at top BE CAREFUL WITH THIS!!!
there again... I run constant root terminal so I do not know if it requires root or not soooo.....
#fastboot oem mw 8d08ac54 1 31302E30
#fastboot flash hboot whateverhbootfile.nb0
I was trying to root my HTC One Mini and I bricked it.
I was following the tutorial on AndroidRootCentral and things were going well until I needed to install the SuperSU zip file. I couldn't find the file. My file structure as shown through TWRP was nothing like the file structure as seen though HTC Sync Manager. I tried rebooting the phone and placing the SuperSU zip in many locations. I'm not exactly sure what when wrong.
I probably screwed myself even further when I tried various things to get the phone to reset. Nothing I've read seems to work and I've been reading things and trying to get it to work since Friday. I've tried relocking the phone and then using an AT&T (my carrier) RUU. None of the RUUs I've found for AT&T work. All come back with a message about something being too long (I could look this up if you really need to know).
So ... help!
Is there a way to basically format and start over?
chilort said:
I was trying to root my HTC One Mini and I bricked it.
I was following the tutorial on AndroidRootCentral and things were going well until I needed to install the SuperSU zip file. I couldn't find the file. My file structure as shown through TWRP was nothing like the file structure as seen though HTC Sync Manager. I tried rebooting the phone and placing the SuperSU zip in many locations. I'm not exactly sure what when wrong.
I probably screwed myself even further when I tried various things to get the phone to reset. Nothing I've read seems to work and I've been reading things and trying to get it to work since Friday. I've tried relocking the phone and then using an AT&T (my carrier) RUU. None of the RUUs I've found for AT&T work. All come back with a message about something being too long (I could look this up if you really need to know).
So ... help!
Is there a way to basically format and start over?
Click to expand...
Click to collapse
More specifics please. What version of the firmware were you on? What RUUs have you found / tried to run? Please provide the exact error to further expedite the process. Also, if you have fastboot set up, boot to the bootloader and run:
fastboot getvar all
and post the results.
es0tericcha0s said:
More specifics please. What version of the firmware were you on? What RUUs have you found / tried to run? Please provide the exact error to further expedite the process. Also, if you have fastboot set up, boot to the bootloader and run:
fastboot getvar all
and post the results.
Click to expand...
Click to collapse
I'm going to bring some of this to you in pieces so I may edit this post for more info to answer your questions (I have a toddler running around and it is dinner time).
I do not know my firmware version. Under relocked my phone says:
M4_UL PVT SHIP S-ON RL
HBOOT-2.22.0000
RADIO-1.29.40g.00.19
OpenDSP-v19.2.0268.0927
OS-4.13.502.3
eMMC-boot 1024MB
Jul 11 2014,20:49:19.0
I cannot hotlink but the one in this thread (http://forum.xda-developers.com/showthread.php?t=2777778) is one of the RUUs I tried. I tried others but in my haste to try to get this thing running again I didn't exactly take good records.
After running getvar all
version: 0.5
version-bootloader: 2.22.0000
version-baseband: 1.29.40g.00.19
version-cpld: None
version-microp: None
version-main: 4.13.502.3
version-misc: PVT SHIP S-ON
serialno: HT385WA00294
imei: 356482050078674
meid:
product: m4_ul
platform: HBOOT-8930
modelid: PO5822000
cidnum: CWS__001
battery-status: good
battery-voltage: 4314mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-0e1af350
hbootpreupdate: 11
gencheckpt: 0
Edit:
Okay, when trying the RUUs I get Error 155: Unknown error.
My PC is a an old Core 2 Duo and crashed a few times just trying to load the RUU. The RUU then asks to go through a recovery mode. It shows a picture with four exclamation points in the corners of the screen on the phone. My phone does not have the exclamation points. I've tried the recovery process a few times and it doesn't do anything.
The error about something being too long was when I was trying to load a .zip using fastboot from my Mac.
Seems like you're in a bit of a pickle then... There aren't any current RUUs for your phone. The one that you linked to would not be able to work unless you are S-Off because S-On will not let you downgrade. That version is 4.2.2 and it appears that you have accepted the OTA which means you will not be able to just run that RUU and get back to normal. Now, that doesn't mean there aren't any options, but probably at this point, it might be easiest just to install a custom rom since you still have TWRP. Just have to remember to pull the boot.img out of the rom zip and use fast boot to install or you will bootloop. If you really want to be back on bone stock, you would need to jump through some hoops. Basic outline is as follows:
Put rom on phone.
Boot to TWRP
Wipe and install rom
Boot to bootloader and flash boot.img
Once back up and running you'd need to S-Off (I believe Rumrunner for 4.2.2, but you'll need to double check that)
Once S-Off is achieved, then you would need to relock the bootloader and then you should be able to run the RUU and accepts the OTA(s) to get up to date and stock / non rooted
Unless this is for warranty issues, I'd just use a custom rom. I'm certain there is one that is completely stock or just stock + root if that is all you want / need.
es0tericcha0s said:
Seems like you're in a bit of a pickle then... There aren't any current RUUs for your phone. The one that you linked to would not be able to work unless you are S-Off because S-On will not let you downgrade. That version is 4.2.2 and it appears that you have accepted the OTA which means you will not be able to just run that RUU and get back to normal. Now, that doesn't mean there aren't any options, but probably at this point, it might be easiest just to install a custom rom since you still have TWRP. Just have to remember to pull the boot.img out of the rom zip and use fast boot to install or you will bootloop. If you really want to be back on bone stock, you would need to jump through some hoops. Basic outline is as follows:
Put rom on phone.
Boot to TWRP
Wipe and install rom
Boot to bootloader and flash boot.img
Once back up and running you'd need to S-Off (I believe Rumrunner for 4.2.2, but you'll need to double check that)
Once S-Off is achieved, then you would need to relock the bootloader and then you should be able to run the RUU and accepts the OTA(s) to get up to date and stock / non rooted
Unless this is for warranty issues, I'd just use a custom rom. I'm certain there is one that is completely stock or just stock + root if that is all you want / need.
Click to expand...
Click to collapse
Thank you for the help! I am not at all opposed to a custom rom (I thought going backward might be easier than forward). But that goes beyond what I've read so far. I know I could Google it, but would appreciate any links, pointers, or other primers.
Stock + root is what I was trying to achieve.
Here's a version of stock rooted rom from the international version (no AT&T bloatware - yay!):
http://forum.xda-developers.com/showpost.php?p=51779967&postcount=294
You need either the odexed or deodexed version from this post since you are on hboot 2.22. Odexed is fine if you aren't planning on trying to theme anything though there really isn't that much difference between them. Odexed used to be preferred for smoothness but with phones as powerful as they are now, you would be very hard pressed to tell them apart. Basically you just need to make sure you are on the right recovery, flash the rom, then use the boot.img to flash via the bootloader and you should be good to go.
Because you do not have an SD card slot, you will need to use adb while in recovery to push the rom zip from the computer to the phone. Like so:
adb push rom.zip /sdcard/ (replace rom.zip with the name of the rom you downloaded - Hint: you can name it whateveryouwant.zip to make it easier).
If you need adb/fastboot: http://forum.xda-developers.com/showthread.php?t=2317790
Just make sure you have the right drivers and ^ and the rom zip in that folder ^ and use the Command Prompt (make sure you change directories to the adb/fastboot folder) to enter the commands.
es0tericcha0s said:
Here's a version of stock rooted rom from the international version (no AT&T bloatware - yay!):
http://forum.xda-developers.com/showpost.php?p=51779967&postcount=294
You need either the odexed or deodexed version from this post since you are on hboot 2.22. Odexed is fine if you aren't planning on trying to theme anything though there really isn't that much difference between them. Odexed used to be preferred for smoothness but with phones as powerful as they are now, you would be very hard pressed to tell them apart. Basically you just need to make sure you are on the right recovery, flash the rom, then use the boot.img to flash via the bootloader and you should be good to go.
Because you do not have an SD card slot, you will need to use adb while in recovery to push the rom zip from the computer to the phone. Like so:
adb push rom.zip /sdcard/ (replace rom.zip with the name of the rom you downloaded - Hint: you can name it whateveryouwant.zip to make it easier).
If you need adb/fastboot: http://forum.xda-developers.com/showthread.php?t=2317790
Just make sure you have the right drivers and ^ and the rom zip in that folder ^ and use the Command Prompt (make sure you change directories to the adb/fastboot folder) to enter the commands.
Click to expand...
Click to collapse
The version of TWRP on my phone is 2.6.0.0. This is not version listed in the link you posted. They list 2.7.0.5. Will this be problematic?
I went ahead and gave it a try. I loaded TWRP and went into the adb sideload feature. The screen for sideload listed the following:
Updating partition details...
E: Unable to mount '/cache'
E: Unable to mount '/cache'
Running boot script ...
Finished running boot script.
E: TWFunc::Copy_Log -- Can't open destination log
E: Unable to mount '/cache'
Starting ADB sideload feature ...
I saved the rom as rom.zip to make things easier as suggested. In my terminal window I typed the command as listed (ADP and the rom are in the same folder). In the terminal window I received:
error: closed
error: closed
You will definitely need the newer TWRP before it will work. But you don't use adb sideload. As long as the PC recognizes the phone correctly, then you just need to open the Command Prompt, change directories to the folder where adb and rom.zip are store and then copy and paste the command into it and hit enter. It should start to send. It will take awhile and there is no timer so just go grab a sandwich or drink or something and be patient.
You can use this video for reference:
https://www.youtube.com/watch?v=Hn4E3fKX7WM
It's a different device, but the same exact steps. He does state that he puts the name of the rom after /sdcard/ in the command, but it's not necessary. Won't make a difference for this.
Okay. That was somewhat helpful. I couldn't find TWRP 2.7.0.5, but I did get 2.7.1.1 and I got it loaded.
I've tried the adb command. It sits there for a long time, then the phone reboots into TWRP. I get no messages back in the terminal window and nothing is loaded into the /sdcard directory (or anywhere else as far as I can tell).
Edit: wait. Formatted it and am going to try again.
Edit 2: loading rom!!!
Don't forget to fastboot the boot.img or it won't boot. If it is still stuck in a bootloop after the rom and boot.img are installed, then reboot to recovery and perform another factory reset. Should work. If not, then you might need the other TWRP. The link for it is right on the same post as the rom. Not sure how you missed it...
es0tericcha0s said:
Don't forget to fastboot the boot.img or it won't boot. If it is still stuck in a bootloop after the rom and boot.img are installed, then reboot to recovery and perform another factory reset. Should work. If not, then you might need the other TWRP. The link for it is right on the same post as the rom. Not sure how you missed it...
Click to expand...
Click to collapse
I missed it because I didn't read carefully and am doing this in bits and spurts.
The good news is that I have a running phone again. Thank you so much for the help!:good:
chilort said:
I missed it because I didn't read carefully and am doing this in bits and spurts.
The good news is that I have a running phone again. Thank you so much for the help!:good:
Click to expand...
Click to collapse
:good::highfive::victory:
es0tericcha0s said:
:good::highfive::victory:
Click to expand...
Click to collapse
Thank you again for walking me through this. It is nice to have my HTC back. My slow, piece of junk work phone can now go back to running BOINC.
No problem. It's how I give back to the community.
Pretty much this is what happened. I wanted to convert my version to the GPE. It was working fine, but as soon as I did the 4.4.4 OTA, I got stuck in boot loop. So, I looked up some guides and I somehow wound up flashing something I wasn't supposed to. Now I have the GPE bootloader, and for some reason, no matter what recovery I use, the installation of any sense based rom fails. I have no idea how I manged to do what I did, considering I was never able to get s-off. So now, I've finally given up trying to figure it out myself. I was wondering if anybody has had experience with this. I have no idea what to do. I would like to have the option to be able to install sense roms too. Not sure what information I can give to help, but please ask me if you can. Thank you.
Edit: getvar.
version: 0.5
version-bootloader: 3.18.0.0000
version-baseband: 1.16.21331931.LA11G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
imei2: Not Support
meid: 00000000000000
product: m8_ul_ca
platform: hTCBmsm8974
modelid: 0P6B12000
cidnum: CWS__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 6e0f5a3d
hbootpreupdate: 11
gencheckpt: 0
The full GPE conversion changes the partitioning on the memory, which is not compatible with Sense ROMs. But as you mentioned, AFAIK you need s-off to do the full conversion. So not sure what's going on.
Do adb getvar all to confirm hboot, CID and S-off (remove serial number and IMEI if you cut/paste getvar output, as these are sensitive personal info).
Have you tried flashing a GPE ROM?
Is your ultimate intent to stay on GPE (and get OTAs) or go back to Sense ROMs?
My recommendation would be to just run the RUU and start over to stock Sense hboot, ROM, recovery, etc. But it somewhat depends on your final intent. Since you are s-on, you will need to relock the bootloader to RUU. Also, CID will need to be AT&T's or SuperCID; and you can't "downgrade" hboot version with s-on (RUU hboot has to be equal or greater than what is installed on the device).
redpoint73 said:
The full GPE conversion changes the partitioning on the memory, which is not compatible with Sense ROMs. But as you mentioned, AFAIK you need s-off to do the full conversion. So not sure what's going on.
Do adb getvar all to confirm hboot, CID and S-off (remove serial number and IMEI if you cut/paste getvar output, as these are sensitive personal info).
Have you tried flashing a GPE ROM?
Is your ultimate intent to stay on GPE (and get OTAs) or go back to Sense ROMs?
My recommendation would be to just run the RUU and start over to stock Sense hboot, ROM, recovery, etc. But it somewhat depends on your final intent. Since you are s-on, you will need to relock the bootloader to RUU. Also, CID will need to be AT&T's or SuperCID; and you can't "downgrade" hboot version with s-on (RUU hboot has to be equal or greater than what is installed on the device).
Click to expand...
Click to collapse
Right now my goal is to go back to sense if I can't get gpe to work properly with functioning OTA. I tried an RUU but it gave me an error. I've been trying to s-off using firewater, but I've had no luck. I'm at work at the moment but I will try to do what you suggested when I get home. Thank you for your response.
deviousconundrum said:
I tried an RUU but it gave me an error.
Click to expand...
Click to collapse
It would be useful to know what error message it gave you. And which RUU you tried.
With S-on, you can't run an RUU with an hboot version that is older than what is on the phone (fails version check). I can tell you more (which RUU should work) once you've had a chance to supply the getvar info requested previously.
Also, if you happened to change the CID and/or MID to convert to GPE, it might cause those checks to fail.
Or you might just have a general USB connectivity issue, or a corrupt RUU file. Its impossible to know if you aren't specific. Be sure to check if the command "adb devices" works to make sure there isn't a general USB connection issue.
redpoint73 said:
It would be useful to know what error message it gave you. And which RUU you tried.
With S-on, you can't run an RUU with an hboot version that is older than what is on the phone (fails version check). I can tell you more (which RUU should work) once you've had a chance to supply the getvar info requested previously.
Also, if you happened to change the CID and/or MID to convert to GPE, it might cause those checks to fail.
Or you might just have a general USB connectivity issue, or a corrupt RUU file. Its impossible to know if you aren't specific. Be sure to check if the command "adb devices" works to make sure there isn't a general USB connection issue.
Click to expand...
Click to collapse
I'm going to try to install GPE and see what happens. I will post what happens afterwards. I also noticed that in my recovery. /data keeps failing to mount. At the moment I'm running Pacman Rom.
Edit: I got the error executing updater binary in zip 'extenrnal_sd/Downloads/GPE4.4.3_m8.zip message when I tried flashing it.
It appears I have a gpe image on my m8 phone??? Do I flash firmware?
{
"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"
}
deviousconundrum said:
I also noticed that in my recovery. /data keeps failing to mount.
Click to expand...
Click to collapse
This is a known issue for some folks, particularly with TWRP. It will cause a lot of other things to fail, like ROM flashing. You may need to format your internal memory. But RUU should have sorted this out, so RUU failing is probably a separate issue. Need more details before I can give more help.
redpoint73 said:
This is a known issue for some folks, particularly with TWRP. It will cause a lot of other things to fail, like ROM flashing. You may need to format your internal memory. But RUU should have sorted this out, so RUU failing is probably a separate issue. Need more details before I can give more help.
Click to expand...
Click to collapse
Which RUU are you talking about though? The actual executable one? or the one invoked through adb/fastboot? I tried the exe and when it got to the current version, it was blank, and only option was update. I did that, but then that's when it failed because of a mismatch I think.
deviousconundrum said:
Which RUU are you talking about though? The actual executable one? or the one invoked through adb/fastboot? I tried the exe and when it got to the current version, it was blank, and only option was update. I did that, but then that's when it failed because of a mismatch I think.
Click to expand...
Click to collapse
I'm talking about the exe one, or the bootable one here (which you should try, if you haven't): http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486
You also haven't stated which RUU you tried, which I asked for previously. Was it the 1.58 or 2.23 RUU?
Not sure, but I don't think main version being blank would cause RUU to fail. The number just can't be higher than the main version of the RUU. Blank should be okay, I think. But if that is the issue, I wonder if there is a way to change main version using an adb command? There must be a way, I just don't know it.
redpoint73 said:
I'm talking about the exe one, or the bootable one here (which you should try, if you haven't): http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486
You also haven't stated which RUU you tried, which I asked for previously. Was it the 1.58 or 2.23 RUU?
Not sure, but I don't think main version being blank would cause RUU to fail. The number just can't be higher than the main version of the RUU. Blank should be okay, I think. But if that is the issue, I wonder if there is a way to change main version using an adb command? There must be a way, I just don't know it.
Click to expand...
Click to collapse
It was the one to update from 4.4.2 to 4.4.3 I believe. And thank you, I will try the bootable one.
Edit: I tried it and I got the error wrong zipped image. Seriously don't know what else to do.
Even though for some reason I can't get the GPE version to install anymore. SkyDragon GPE edition works for me. But, no matter what I try I can't s-off. Both firewater and sunshine don't work for me. Firewater fives me that message after the first chug, that says firewater doesn't work on my version, sorry. What can I do as S-on to get back to sense? Is it even possible? Nandroid back ups? Hehe, I have no idea. Maybe there's something I'm not seeing here. Anyways,thank you for your help, I see I'm going to have to do a bit more research to maybe find the answer I seek.
deviousconundrum said:
Even though for some reason I can't get the GPE version to install anymore. SkyDragon GPE edition works for me. But, no matter what I try I can't s-off. Both firewater and sunshine don't work for me. Firewater gives me that message after the first chug, that says firewater doesn't work on my version, sorry. What can I do as soon to get back to sense? Is it even possible? Nandroid back ups? Hehe, I have no idea. Maybe there's something I'm not seeing here. Anyways, thank you for your help, I see I'm going to have to do a bit more research to maybe find the answer I seek.
Click to expand...
Click to collapse
I had a similar problem a while back ago. I had to install a stock recovery and do a factory reset. It fixed my problems and I went back to flashing.
BR7fan said:
I had a similar problem a while back ago. I had to install a stock recovery and do a factory reset. It fixed my problems and I went back to flashing.
Click to expand...
Click to collapse
Which stock recovery should I download though? The stock sense one or the gpe one? Are recoveries independent from the rom itself?
same
I am having the same problem, i have a converted GPE skydragon m8 with s-on, firewater hasnt worked. i want to return to stock sense but im having trouble finding the solution.
Mirzatron said:
I am having the same problem, i have a converted GPE skydragon m8 with s-on, firewater hasnt worked. i want to return to stock sense but im having trouble finding the solution.
Click to expand...
Click to collapse
Yeah, I've tried everything. Unfortunately I don't remember the steps I took to get into this sort of situation. I know I did flash a lot of things. Thus explaining why my bootloader is different. It's black with an android in the bottom instead of the stock one I had that was 3 of them on skateboards, also, the HTC boot screen, has a little pic of an open lock. Before it just had red words in the bottom. Do you also have those same things I described?
Mirzatron said:
I am having the same problem, i have a converted GPE skydragon m8 with s-on, firewater hasnt worked. i want to return to stock sense but im having trouble finding the solution.
Click to expand...
Click to collapse
I used the sense one.
BR7fan said:
I used the sense one.
Click to expand...
Click to collapse
what do you mean?
Mirzatron said:
what do you mean?
Click to expand...
Click to collapse
Stock recovery. Find one,flash it and do a factory reset
BR7fan said:
Stock recovery. Find one,flash it and do a factory reset
Click to expand...
Click to collapse
I read that flashing sense wouldn't work since the gpe partition is smaller.
Mirzatron said:
I read that flashing sense wouldn't work since the gpe partition is smaller.
Click to expand...
Click to collapse
Useca gpe stock recovery
BR7fan said:
Useca gpe stock recovery
Click to expand...
Click to collapse
Do you think by using the stock gpe recovery, i will be able to s-off?
Hello there.
I have been trying at this for a while now but simply cannot figure out how to get around this issue. I have successfully rooted my M8 but now I am trying to install OTA updates. I looked up a guide on how to do this and came to this video:
Everything was going swimmingly until about minute 7 in the video where the step is to and go ahead with the OTA updates. When my phone restarts to install the updates the progress bar loads to about 1/5 and then stops for a few moments before giving me the triangle red exclamation mark icon.
How do I get around this? I'm fairly certain I have the right stock recovery. All I want to do is install the OTA updates without losing any of my current apps/settings. If an easier process is to unroot my phone and leave it that way then so be it.
Phone INFO:
CID: T-MOB010
version 4.4.4
HTC sense v. 6.0
software #: 3.32.531.2
SDK API level: 6.25
Any help pointing me in the right direction would be swell. I apologize in advance for the tall order. Thanks.
blinkdagger said:
Hello there.
I have been trying at this for a while now but simply cannot figure out how to get around this issue. I have successfully rooted my M8 but now I am trying to install OTA updates. I looked up a guide on how to do this and came to this video:
Everything was going swimmingly until about minute 7 in the video where the step is to and go ahead with the OTA updates. When my phone restarts to install the updates the progress bar loads to about 1/5 and then stops for a few moments before giving me the triangle red exclamation mark icon.
How do I get around this? I'm fairly certain I have the right stock recovery. All I want to do is install the OTA updates without losing any of my current apps/settings. If an easier process is to unroot my phone and leave it that way then so be it.
Phone INFO:
CID: T-MOB010
version 4.4.4
HTC sense v. 6.0
software #: 3.32.531.2
SDK API level: 6.25
Any help pointing me in the right direction would be swell. I apologize in advance for the tall order. Thanks.
Click to expand...
Click to collapse
If I remember correctly, you can't be rooted doing official ota updates. Finish updates, then root
BR7fan said:
If I remember correctly, you can't be rooted doing official ota updates.
Click to expand...
Click to collapse
Ok, do you think it's worthwhile to manually do the updates?
blinkdagger said:
Ok, do you think it's worthwhile to manually do the updates?
Click to expand...
Click to collapse
Yeah I found them to be those guys get the latest up very quick. Make sure your s-off
BR7fan said:
Yeah I found them to be those guys get the latest up very quick. Make sure your s-off
Click to expand...
Click to collapse
Ok thanks a lot. I will try to manually install the updates.
BR7fan said:
If I remember correctly, you can't be rooted doing official ota updates. Finish updates, then root
Click to expand...
Click to collapse
You would be remembering incorrectly. Root has no impact itself on whether an OTA will install. As long as no system files have been altered by the user (using root permissions), and stock recovery is installed. Root and unlocked bootloader are both okay. Although you will most likely lose root after the update.
---------- Post added at 09:52 AM ---------- Previous post was at 09:50 AM ----------
blinkdagger said:
Phone INFO:
CID: T-MOB010
version 4.4.4
HTC sense v. 6.0
software #: 3.32.531.2
SDK API level: 6.25
Click to expand...
Click to collapse
Is your phone the T-Mob version, or an AT&T version converted to T-Mob? Because this is the AT&T version specific forum section.
Another option to update would be to just run the T-Mobile Lollipop RUU. Relock the bootloader if you are s-on. Biggest downside, is that RUU will wipe the phone; and keeping user data may be your reason for seeking the OTA route.
redpoint73 said:
You would be remembering incorrectly. Root has no impact itself on whether an OTA will install. As long as no system files have been altered by the user (using root permissions), and stock recovery is installed. Root and unlocked bootloader are both okay. Although you will most likely lose root after the update.
---------- Post added at 09:52 AM ---------- Previous post was at 09:50 AM ----------
Is your phone the T-Mob version, or an AT&T version converted to T-Mob? Because this is the AT&T version specific forum section.
Another option to update would be to just run the T-Mobile Lollipop RUU. Relock the bootloader if you are s-on. Biggest downside, is that RUU will wipe the phone; and keeping user data may be your reason for seeking the OTA route.
Click to expand...
Click to collapse
I think I may have posted in the wrong forum. My phone is simply the T-Mobile version as far as I know. I think I may have changed some system files around. Do you know of a way to reset them to default that way I can proceed with the OTA updates? I do want to keep all the apps and user settings. My plan was to re root the phone after the OTA updates were done. Thanks for your help.
blinkdagger said:
I think I may have posted in the wrong forum. My phone is simply the T-Mobile version as far as I know.
Click to expand...
Click to collapse
T-Mobile has its own section, so yes this is the wrong forum section. But I'll try to help anyway, as your issues aren't that carrier specific.
blinkdagger said:
I think I may have changed some system files around. Do you know of a way to reset them to default that way I can proceed with the OTA updates?
Click to expand...
Click to collapse
Few different options.
1) Just restore the nandroid backup you made before messing with system files. And you did this, like you should before making any such mods, RIGHT? Well if not:
2) You can manually change them all back. Probably the most tedious method, especially since you don't seem sure of what you changed.
3) Find the right stock nandroid and flash it. Find corresponding stock recovery, and flash it.
4) Relock the bootloader and RUU to stock, and since you can just RUU to the current OS version, no need to OTA. After that, just unlock the bootloader again via HTCDev.com (of if you want to avoid that, sunshine) in preparation for installing custom recovery (and root) again. Yes, RUU will wipe that phone, but that brings us to the next point:
blinkdagger said:
I do want to keep all the apps and user settings. My plan was to re root the phone after the OTA updates were done. .
Click to expand...
Click to collapse
You are rooted, so back up your apps and app data with Titanium Backup (or similar root app). Then you can just restore all the apps and app data after you RUU. You should be backing them up anyway. Saying you want to keep your app data; then not having them backed up is a contradiction. If you data is important to you, back it up. And that advice goes for whether you decide to RUU or not.
Backing up setting with Titanium across ROM versions is not recommended. But unless you have a really large amount of settings customizations, it usually doesn't take that much time to set these up again manually, anyway (as long as your apps and app data are already restorable).
Option 4 above is what I would consider. Its really up to you whether options 3 or 4 are best for you. But the reason I like RUU, even though it has the extra steps of relocking/unlocking the bootloader, and backing up your data; what it saves you is from finding the right stock nandroid and stock recovery, and putting them to the correct location on the phone to then Restore with TWRP. And these steps are ones with potential for mistakes that can make them exhaust a lot more time than you would think. RUU is a complete factory image, so everything is sure to play well together, no guesswork or potential for mistakes.
redpoint73 said:
T-Mobile has its own section, so yes this is the wrong forum section. But I'll try to help anyway, as your issues aren't that carrier specific.
Few different options.
1) Just restore the nandroid backup you made before messing with system files. And you did this, like you should before making any such mods, RIGHT? Well if not:
2) You can manually change them all back. Probably the most tedious method, especially since you don't seem sure of what you changed.
3) Find the right stock nandroid and flash it. Find corresponding stock recovery, and flash it.
4) Relock the bootloader and RUU to stock, and since you can just RUU to the current OS version, no need to OTA. After that, just unlock the bootloader again via HTCDev.com (of if you want to avoid that, sunshine) in preparation for installing custom recovery (and root) again. Yes, RUU will wipe that phone, but that brings us to the next point:
You are rooted, so back up your apps and app data with Titanium Backup (or similar root app). Then you can just restore all the apps and app data after you RUU. You should be backing them up anyway. Saying you want to keep your app data; then not having them backed up is a contradiction. If you data is important to you, back it up. And that advice goes for whether you decide to RUU or not.
Backing up setting with Titanium across ROM versions is not recommended. But unless you have a really large amount of settings customizations, it usually doesn't take that much time to set these up again manually, anyway (as long as your apps and app data are already restorable).
Option 4 above is what I would consider. Its really up to you whether options 3 or 4 are best for you. But the reason I like RUU, even though it has the extra steps of relocking/unlocking the bootloader, and backing up your data; what it saves you is from finding the right stock nandroid and stock recovery, and putting them to the correct location on the phone to then Restore with TWRP. And these steps are ones with potential for mistakes that can make them exhaust a lot more time than you would think. RUU is a complete factory image, so everything is sure to play well together, no guesswork or potential for mistakes.
Click to expand...
Click to collapse
Hey thanks for all the help. I have decided to use Option 4 but I have discovered that my phone is still S-ON. I found this thread which seems to be able to provide me with the right RUU file.
http://forum.xda-developers.com/showthread.php?t=2754063
The only issue is that at the top of the thread it says that these RUUs are meant for S-OFF users. After searching a bit I learned that supposedly http://theroot.ninja/ is the only way to change my phone from S-ON to S-OFF. I just don't want to pay 25 bucks if I don't have to. Is this the only way?
blinkdagger said:
Hey thanks for all the help. I have decided to use Option 4 but I have discovered that my phone is still S-ON. I found this thread which seems to be able to provide me with the right RUU file.
http://forum.xda-developers.com/showthread.php?t=2754063
The only issue is that at the top of the thread it says that these RUUs are meant for S-OFF users. After searching a bit I learned that supposedly http://theroot.ninja/ is the only way to change my phone from S-ON to S-OFF. I just don't want to pay 25 bucks if I don't have to. Is this the only way?
Click to expand...
Click to collapse
Yes. As of this date, Sunshine is the only way to gain S-Off for the M8. Firewater is discontinued.
blinkdagger said:
Hey thanks for all the help. I have decided to use Option 4 but I have discovered that my phone is still S-ON. I found this thread which seems to be able to provide me with the right RUU file.
http://forum.xda-developers.com/showthread.php?t=2754063
The only issue is that at the top of the thread it says that these RUUs are meant for S-OFF users. After searching a bit I learned that supposedly http://theroot.ninja/ is the only way to change my phone from S-ON to S-OFF. I just don't want to pay 25 bucks if I don't have to. Is this the only way?
Click to expand...
Click to collapse
The s-off statement in the thread you linked was specific to firmware packages. S-off is required to flash a firmware.zip, not an RUU. Those are 2 very different things.
RUU will run fine with s-on, as long as you relock the bootloader; and also you can only run an RUU that is equal or greater than the software version you rooted (looks like Android 4.4.4). So what you want is a T-Mobiel RUU for either Android 4.4.4 (software 3.xx) than OTA to Android 5.0; or RUU right to Android 5.0 (software 4.xx).
redpoint73 said:
The s-off statement in the thread you linked was specific to firmware packages. S-off is required to flash a firmware.zip, not an RUU. Those are 2 very different things.
RUU will run fine with s-on, as long as you relock the bootloader; and also you can only run an RUU that is equal or greater than the software version you rooted (looks like Android 4.4.4). So what you want is a T-Mobiel RUU for either Android 4.4.4 (software 3.xx) than OTA to Android 5.0; or RUU right to Android 5.0 (software 4.xx).
Click to expand...
Click to collapse
Hey I know it has been a while but I just got around to taking care of this. I want to use an RUU to reset everything like you mentioned. The trouble I am now having is with the re-locking procedure.
I am trying to to relock the bootloader using the "fastboot oem lock" command. When I enter the command I get this message.
(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) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
finished. total time: 1.194s
I have done this about 5 times now and the lock status remains "UNLOCKED". Thank you for all your help thus far. I will continue to try to search for a solution.