Hello, after looking into my problem all night (it is 4 a.m. now) I still cannot get my One X out of its issue.
Background to this story:
Bought this phone from a friend who had TWRP2 as the recovery, unlocked, s-on, supercid. I wanted to upgrade to a newer ROM, specifically Carbon on Jellybean 4.2.2, and I needed to update hboot to accept the newer ROM. Follow the procedures of multiple threads and they all lead me down the same path of re-locking your bootloader and let the install do the rest. However, the installer has failed multiple times (error codes 140 and 158) and I am now stuck and have no idea where to go next.
The current status of the One X is not to great. It now has a relocked bootloader, HBOOT version of 2.14.0000, A broken recovery, what seems to be a mismatched baseband, Stuck at FASTBOOT USB, no ADB, will not boot into a ROM, RUU will not complete its job (fails at sending ROM), and I am all out energy and grammar.
*Trying to re-unlock the bootloader via HTCdev will NOT unlock it.
I am stuck, (yea I am a noob). If you need anymore info, just ask.
I'm not entirely sure, but I think you should try and flash the stock recovery and then RUU. I couldn't find the stock recovery in RedPoint's compilation roll-up thread, but I found it on a youtube video when I searched "att one x stock recovery". After you get the stock recovery installed I believe you should be able to then RUU.
Flashing the stock recovery only really applies when you're trying to take an OTA, it isn't required for an RUU.
Sent from my Evita
whoooops just kidding then. might worth a shot to give it a try though? I was just tossing out ideas.
brotherross said:
I'm not entirely sure, but I think you should try and flash the stock recovery and then RUU. I couldn't find the stock recovery in RedPoint's compilation roll-up thread, but I found it on a youtube video when I searched "att one x stock recovery". After you get the stock recovery installed I believe you should be able to then RUU.
Click to expand...
Click to collapse
I am not exactly sure how to do that.
I honestly don't think that's going to help you anyway.
Sent from my Evita
timmaaa said:
I honestly don't think that's going to help you anyway.
Sent from my Evita
Click to expand...
Click to collapse
Alright, gonna need to fix it later. (Recovery still broken, I assume because of the failed RUU)
Which RUU are you trying to run?
Is this the AT&T version of the One X?
Be aware that running any Jellybean RUU (3.18, 3.17) with S-on and SuperCID will brick the phone. So if you were trying to run a JB RUU, it might actually be a good thing it didn't install.
If you were trying to run an older RUU (2.20, etc.) then it will fail since the hboot version is older (hboot 2.14 goes with 3.1x).
Do you still have a TWRP nandroid available (if not, whey the heck not?!?!). Have you tried to flash TWRP again using fastboot? If that works you can try to get your nandroid restored. With S-on, be aware that you will need to flash the boot.img for that ROM separately using fastboot.
---------- Post added at 09:21 AM ---------- Previous post was at 09:20 AM ----------
brotherross said:
After you get the stock recovery installed I believe you should be able to then RUU.
Click to expand...
Click to collapse
As already pointed out by timmaaa, this is incorrect. RUU installs stock recovery on its own, and stock recovery is therefore not needed for an RUU (only an OTA).
redpoint73 said:
Which RUU are you trying to run?
Is this the AT&T version of the One X?
Be aware that running any Jellybean RUU (3.18, 3.17) with S-on and SuperCID will brick the phone. So if you were trying to run a JB RUU, it might actually be a good thing it didn't install.
If you were trying to run an older RUU (2.20, etc.) then it will fail since the hboot version is older (hboot 2.14 goes with 3.1x).
Do you still have a TWRP nandroid available (if not, whey the heck not?!?!). Have you tried to flash TWRP again using fastboot? If that works you can try to get your nandroid restored. With S-on, be aware that you will need to flash the boot.img for that ROM separately using fastboot.
---------- Post added at 09:21 AM ---------- Previous post was at 09:20 AM ----------
As already pointed out by timmaaa, this is incorrect. RUU installs stock recovery on its own, and stock recovery is therefore not needed for an RUU (only an OTA).
Click to expand...
Click to collapse
Yes, this is the AT&T version.
I was trying to do an RUU with RUU_Evita_UL_Cingular_US-1.73.502.2_2FE6772699D8596307CC997452BB8D25.
Anytype of backup was made on the phone with TWRP, if TWRP still exists on the phone, it should be there.
I have not tried flashing TWRP back. I can try that next, can you point me in the right direction? Which version of TWRP do you recommend? (I am a noob)
"With S-on, be aware that you will need to flash the boot.img for that ROM separately using fastboot." I am not aware of this, (again, noob) do I just extract the boot.img from the zip and use 'fastboot flash boot boot.img' ?
It looks like the problem is that you're trying to run an RUU that is older than your current firmware version. So, you would need to use a later RUU. But, like Redpoint said, if you are s-on and SuperCID this will brick your device. Maybe what you should try first is flashing TWRP recovery again and seeing if you can restore a backup or even just flash another ROM.
Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery on your phone and see if you can restore a backup. You are s-on so you will need to flash the boot.img from the ROM that's backed up after restoring it. If you didn't backup the boot partition you might be out of luck.
If this is the case, download a ROM (and gapps if it's an aosp ROM), extract the boot.img from the ROM zip and place it in your fastboot folder on your PC, copy the ROM zip (and gapps if applicable) to your phone, flash ROM zip (and gapps if applicable) in TWRP, reboot to bootloader, connect to pc, give this command:
Code:
fastboot flash boot boot.img
Reboot your phone and hopefully it will boot.
Sent from my Evita
timmaaa said:
It looks like the problem is that you're trying to run an RUU that is older than your current firmware version. So, you would need to use a later RUU. But, like Redpoint said, if you are s-on and SuperCID this will brick your device. Maybe what you should try first is flashing TWRP recovery again and seeing if you can restore a backup or even just flash another ROM.
Download TWRP 2.6 from . Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery on your phone and see if you can restore a backup. You are s-on so you will need to flash the boot.img from the ROM that's backed up after restoring it. If you didn't backup the boot partition you might be out of luck.
If this is the case, download a ROM (and gapps if it's an aosp ROM), extract the boot.img from the ROM zip and place it in your fastboot folder on your PC, copy the ROM zip (and gapps if applicable) to your phone, flash ROM zip (and gapps if applicable) in TWRP, reboot to bootloader, connect to pc, give this command:
Code:
fastboot flash boot boot.img
Reboot your phone and hopefully it will boot.
Sent from my Evita
Click to expand...
Click to collapse
I may need to reiterate, that my bootloader is still locked.
MDAWG25 said:
Yes, this is the AT&T version.
I was trying to do an RUU with RUU_Evita_UL_Cingular_US-1.73.502.2_2FE6772699D8596307CC997452BB8D25.
Click to expand...
Click to collapse
This is why you are getting errors 140 and 158. As timmaaa mentioned, you can't run an older RUU than the hboot that is already on your phone. The RUU you stated is very old, the 1.73 firmware with 1.09 hboot that came out at the phone's release. You are on hboot 2.14, so once the RUU sees that your hboot version is greater than that of the RUU (1.09), it fails.
Thye 3.18 RUU (which comes with hboot 2.14) would be what you want. BUT as already mentioned, you should not run this with S-on and SuperCID, as there is a bug with the Jellybean RUUs where this combo will brick the phone (not fixable without JTAG or new motherboard).
Follow timmaaa's steps in the previous post.
---------- Post added at 10:40 AM ---------- Previous post was at 10:37 AM ----------
MDAWG25 said:
I may need to reiterate, that my bootloader is still locked.
Click to expand...
Click to collapse
You might be in a catch-22 here then. As you know, you can't install custom recovery with a relocked bootloader (and S-on). You can keep trying to unlock it, but I'm not sure if that can be done if the phone can't boot.
MDAWG25 said:
I may need to reiterate, that my bootloader is still locked.
Click to expand...
Click to collapse
Sorry, I missed that. As Redpoint said above, you might be in a catch 22 situation here unfortunately.
Sent from my Evita
Yeah, normally RUU would be the answer. But the RUU bricking bug mentioned is stopping you from going that route.
Keep trying to unlock the bootloader. If you were able to relock in the current condition, maybe you can unlock. Unlocking is quirky and will fail, then will succeed after multiple attempts. So just the fact it hasn't worked yet, doesn't necessarily mean it won't.
redpoint73 said:
Yeah, normally RUU would be the answer. But the RUU bricking bug mentioned is stopping you from going that route.
Keep trying to unlock the bootloader. If you were able to relock in the current condition, maybe you can unlock. Unlocking is quirky and will fail, then will succeed after multiple attempts. So just the fact it hasn't worked yet, doesn't necessarily mean it won't.
Click to expand...
Click to collapse
I am currently not home to interface with the device physically (RDP). I should be returning around 4PM EST.
The superCID was written by the previous owner. Writing a generic CID (like HTC_001) is not an option with s-on, is it?
*Are there any RUUs that won't brick when flashing?
<Sorry for the double post but this post is different then my last>
Interesting thing, I can still write the recovery image even though fastboot claims it is 'relocked'. Here is the command line output.
sending 'recovery' (8028 KB)...
OKAY [ 0.993s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.720s
The signature checking failed, but it still accepted the image. Not sure if this means anything.
You could try hex editing your CID back to its original CID, but it must be the original CID to match the CID that the RUU is looking for, not just any CID. In order for this to work your would need to have adb fully working though. Please note the method I linked to above is to gain SuperCID, but the principle is the same, you just want to change 11111111 back to CWS__001 for an at&t phone.
The only RUUs that won't brick are the lower ones, which you can't run because you're s-on.
Sent from my Evita
---------- Post added at 01:26 AM ---------- Previous post was at 01:25 AM ----------
MDAWG25 said:
Interesting thing, I can still write the recovery image even though fastboot claims it is 'relocked'. Here is the command line output.
sending 'recovery' (8028 KB)...
OKAY [ 0.993s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.720s
The signature checking failed, but it still accepted the image. Not sure if this means anything.
Click to expand...
Click to collapse
Can you actually enter recovery? The failed message tells me that it hasn't worked.
Sent from my Evita
timmaaa said:
You could try hex editing your CID back to its original CID, but it must be the original CID to match the CID that the RUU is looking for, not just any CID. In order for this to work your would need to have adb fully working though. Please note the method I linked to above is to gain SuperCID, but the principle is the same, you just want to change 11111111 back to CWS__001 for an at&t phone.
The only RUUs that won't brick are the lower ones, which you can't run because you're s-on.
Sent from my Evita
---------- Post added at 01:26 AM ---------- Previous post was at 01:25 AM ----------
Can you actually enter recovery? The failed message tells me that it hasn't worked.
Sent from my Evita
Click to expand...
Click to collapse
Fastboot claims it wrote the recovery image, it just failed the signature check, unless it reverted, should it still be there?
I am not home to try it. I am RDPing to my computer at home, which the phone is connected to. I should be home at 4PM EST (4 hours from now).
Here is a 'getvar all'
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.17.32.09.12
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.18.502.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT246*********** (omitted for privacy)
(bootloader) imei: 359****************** (omitted for privacy)
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4177mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
See anything out of the usual?
Being able to unlock the bootloader will solve all my issues, I should be able to try again when I get home.
It looks to me like it failed while writing, but I may be wrong. The info you just posted looks to be ok. I'd continue to try unlocking the bootloader.
Sent from my Evita
timmaaa said:
It looks to me like it failed while writing, but I may be wrong. The info you just posted looks to be ok. I'd continue to try unlocking the bootloader.
Sent from my Evita
Click to expand...
Click to collapse
I won't post again until 4pm est, as I do not have full access to the device.
Thank you for your help, I really do appreciate it.
Related
I have a rooted MT4GS w/ the Revolutionary bootloader. I noticed that running
fastboot oem ?
Click to expand...
Click to collapse
brings up the list of commands that can be run.
(bootloader) command list
(bootloader) checkSbl1
(bootloader) checkHWSecurity
(bootloader) mw
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) heap_test
(bootloader) rtask
(bootloader) task
(bootloader) enableqxdm
(bootloader) gencheckpt
(bootloader) readpid
(bootloader) writepid
(bootloader) readcid
(bootloader) writecid
(bootloader) readimei
(bootloader) writeimei
(bootloader) readsecureflag
(bootloader) writesecureflag
(bootloader) list_partition_emmc
(bootloader) load_emmc
(bootloader) check_emmc
(bootloader) check_emmc_mid
(bootloader) read_mmc
(bootloader) load_modem_emmc
(bootloader) get_wp_info_emmc
(bootloader) send_wp_info_emmc
(bootloader) get_ext_csd_emmc
(bootloader) get_sector_info_emmc
Click to expand...
Click to collapse
Coming from the G2, I know that a couple of commands are missing. I'm most concerned with this command
fastboot oem emapiWlanMac
Click to expand...
Click to collapse
so that I can mac spoof in order to use my university's wifi.
If I have a copy of HBOOT 1.44.0006, obtained using
dd if=/dev/block/mmcblk0p? of=/sdcard/hboot.img
Click to expand...
Click to collapse
and I have S-OFF (via unrevoked), do you think I can switch to the HBOOT 1.44.0006 using the inverse of the previous dd command? And if so, does anybody know the mmcblk0p? number or have a copy of that specific HBOOT version?
Thanks in advance
i wonder if you could flash that HBOOT by using this stock RUU for our device?
http://forum.xda-developers.com/showthread.php?t=1178082
IF you have the .0006 HBOOT in the proper format, i bet you could delete everything in the RUU zip except perhaps the android_info.txt, then paste in the copy that you have of the HBOOT. this is basically what i did to flash ClockworkMod thru the bootloader. you could always test it by renaming it PG59IMG.zip, putting it on the root of your sdcard and booting into the bootloader. you could see if it reads the file properly and prompts you to update(it should show that you will only be 'updating' the HBOOT). if it does this and you're brave, you could try updating.
not sure if this is what you mean or not also not positive if this is the way to do it. but the RUU definitely does flash an HBOOT, so if you have it in the proper format, maybe it could work?
I messed up a little with strings (1) and file (1). Apparently hboot is stored in /dev/block/mmcblk0p12. If you feel really adventurous you can try to flash a new hboot via dd as you suggested.
I am not 100% sure it will help you: revolutionary hboot (1.44.1107) contains some reference to emapiWlanMac even if it gives an error if you try to use the command.
---------- Post added at 03:29 PM ---------- Previous post was at 02:36 PM ----------
question: where have you got 1.44.0006 ???
I just compared 1.44.0007 (the original hboot) with 1.44.1107 (revolutionary's). They are almost identical: I guess they simply hexedited the significant bits to unlock it (they also changed version number and added the "-Revolutionary-" signature) so none of them will help you change your mac address.
Hboot 1.45.0013 (the latest hboot) is a significantly different beast and might have the desired features but I would not flash it since it will lock your phone again.
I'm down to try the dd command, but I'll still need a copy of the 1.44.0006 hboot. If anybody has the 1.44.0006 hboot, can you please open a terminal and run
dd if=/dev/block/mmcblk0p12 of=/data/local/tmp/hboot.img
mv /data/local/tmp/hboot.img /sdcard/
Click to expand...
Click to collapse
Then send me the file on you sdcard?
Etn40ff said:
I messed up a little with strings (1) and file (1). Apparently hboot is stored in /dev/block/mmcblk0p12. If you feel really adventurous you can try to flash a new hboot via dd as you suggested.
I am not 100% sure it will help you: revolutionary hboot (1.44.1107) contains some reference to emapiWlanMac even if it gives an error if you try to use the command.
---------- Post added at 03:29 PM ---------- Previous post was at 02:36 PM ----------
question: where have you got 1.44.0006 ???
I just compared 1.44.0007 (the original hboot) with 1.44.1107 (revolutionary's). They are almost identical: I guess they simply hexedited the significant bits to unlock it (they also changed version number and added the "-Revolutionary-" signature) so none of them will help you change your mac address.
Hboot 1.45.0013 (the latest hboot) is a significantly different beast and might have the desired features but I would not flash it since it will lock your phone again.
Click to expand...
Click to collapse
I know that HTC's engineering bootloader enables the use of more "fastboot oem xxx" commands, and many of them are missing with revolutionary's bootlaoder
at least these 2 guys had 1.44.0006 sometime in the past
daniel60104 and nyolsson
try to pm them and see if they can help (I'd love an ENG bootloader).
Man, me too. I'd love a copy of that to play with.
I just PM'd them now. I hope we can still find a copy, at least for reference sake, since there no XDA Wiki entry for the MT4G yet
Sent from my HTC myTouch_4G_Slide using xda premium
yogi2010 said:
i wonder if you could flash that HBOOT by using this stock RUU for our device?
http://forum.xda-developers.com/showthread.php?t=1178082
IF you have the .0006 HBOOT in the proper format, i bet you could delete everything in the RUU zip except perhaps the android_info.txt, then paste in the copy that you have of the HBOOT. this is basically what i did to flash ClockworkMod thru the bootloader. you could always test it by renaming it PG59IMG.zip, putting it on the root of your sdcard and booting into the bootloader. you could see if it reads the file properly and prompts you to update(it should show that you will only be 'updating' the HBOOT). if it does this and you're brave, you could try updating.
not sure if this is what you mean or not also not positive if this is the way to do it. but the RUU definitely does flash an HBOOT, so if you have it in the proper format, maybe it could work?
Click to expand...
Click to collapse
i jsut tested this theory and it does work. when i had a custom recovery and custom rom, my hboot was 1.44.1107. when i reflashed the stock rom posted in these forums, it reverted to 1.44.0007.
But its still S-OFF no?
Sent from my myTouch_4G_Slide using xda premium
It should still be S-OFF after having done that, that's the result I always end up with.
If it somehow magically went back to S-ON, a whole lot of people (myself included) will be dying to know what happened and how to do it again.
yep, so far S-OFF has been a key safety valve that no one has managed to lose once they had it, whether downgrading or updating
thrice43 said:
But its still S-OFF no?
Sent from my myTouch_4G_Slide using xda premium
Click to expand...
Click to collapse
It IS, in fact, still s off. Pretty sure that's been determined as passing the point of no return, once you turn it off.
Sent from my myTouch_4G_Slide using XDA App
We would know for sure if its truly the "point of no return" if somebody can grab ahold of that ENG_Hboot 1.44.0006. As with 1.44.0007 or any other hboot, I know the S-off status is irreversible.
Sent from my myTouch_4G_Slide using xda premium
Upon running dd if=S-OnHboot of=mmcblk0p12, then m5sum check, it seems that mmcblk012 cannot be written to. Therefore, I believe its safe to assume write protection is still enabled for select partitions, even though revolutionary claims otherwise.
Anybody know a workaround? I found a kernel module that's compiled for htc vision, called wpthis.ko, that enables writing to hboot partition but it wouldnt work cuz its not for mt4gs.
Sent from my myTouch_4G_Slide using xda premium
like i was saying before, if you had a copy of it, couldn't you just flash it thru the HBOOT itself as a PG59IMG.zip? when you flash the full factory firmware that way, it changes you back to the stock HBOOT, but still S-OFF of course.
yogi2010 said:
like i was saying before, if you had a copy of it, couldn't you just flash it thru the HBOOT itself as a PG59IMG.zip? when you flash the full factory firmware that way, it changes you back to the stock HBOOT, but still S-OFF of course.
Click to expand...
Click to collapse
This is most likely what you'll have to do to get it on - making a copy of what's there should be no problem.
To my understanding, the kernel prevents you from writing outside of a certain memory range unless you are in fastboot mode or flashing a failsafe-recovery (PG59...)
This is why I was unable to include a bootsplash as part of what changed when you flashed my ROM - I wasted a solid day of development pre-release trying to figure out how to get it to flash the boot splash as well when you flashed the ROM.
In fastboot or using a failsafe-recovery image, it happens before any higher-level software (kernel ...cough...cough) starts up and you aren't held to that limitation.
Edit -
re-writing the software to allow you to flash things out of the safe memory range in recovery mode would be a disastrously bad idea. We will start getting reports of bricked phones left and right if someone does that.
The obvious (since it was not mentioned yet):
Code:
fastboot erase hboot
fastboot flash hboot hboot.img
The only issue here might be that the new hboot has no fastboot in it so you may nit be able to revert using the same flashing metod.
Why not just flash the whole stock rom image? It includes the hboot
Sent from my myTouch_4G_Slide using XDA App
he's looking for the stock ENG HBOOT, which very few people have had.
but here is another guy who did have it: http://forum.xda-developers.com/showthread.php?t=1330617
yogi2010 said:
he's looking for the stock ENG HBOOT, which very few people have had.
but here is another guy who did have it: http://forum.xda-developers.com/showthread.php?t=1330617
Click to expand...
Click to collapse
Beautiful. Thanks yogi!
Sent from my myTouch_4G_Slide using XDA App
I recently acquired an HTC Inspire 4G to replace my old potato phone. The bootloader is unlocked and when I turn it on, it shows the white HTC screen and then immediately goes to Clockworkmod Recovery. I've tried two different RUU's and both of them said that they could not restore my devices. Can anyone help me fix this?
Are your volume buttons working? Have you tried flashing a new ROM from CWM?
Yes
bananagranola said:
Are your volume buttons working? Have you tried flashing a new ROM from CWM?
Click to expand...
Click to collapse
yes, the volume buttons are working. and i have tried flashing the stock rom for my device.
DakotaWhitis said:
yes, the volume buttons are working. and i have tried flashing the stock rom for my device.
Click to expand...
Click to collapse
Just to clarify, when you say stock do you mean RUU or ROM? Did you use fastboot or recovery?
Both
bananagranola said:
Just to clarify, when you say stock do you mean RUU or ROM?
Click to expand...
Click to collapse
I've tried both.
DakotaWhitis said:
I've tried both.
Click to expand...
Click to collapse
And both fastboot and recovery? What happened with the RUU? did it run?
Yes
bananagranola said:
And both fastboot and recovery? What happened with the RUU? did it run?
Click to expand...
Click to collapse
Yes. RUU said it could not restore my device.
DakotaWhitis said:
Yes. RUU said it could not restore my device.
Click to expand...
Click to collapse
I'm having the exact same issues, like exactly the same and trying to fix. Fastboot does work for me and hboot 0.85.024 tells me that I'm unlocked (htcdev), s-on, and my radio is 26.10.04.03_M. My cid CWS__001 and current version is 2.52.0.0.
Is there a way I can just get back to out-of-box stock?
Have you tried using adb to reboot to system? Since you are not S-Off, you need to find a RUU compatible with your phone's build, specifically for US AT&T. Or you could create a gold card and run any RUU that way.
bananagranola said:
Have you tried using adb to reboot to system? Since you are not S-Off, you need to find a RUU compatible with your phone's build, specifically for US AT&T. Or you could create a gold card and RU any RUU that way.
Click to expand...
Click to collapse
could you link me to these?
bananagranola said:
Have you tried using adb to reboot to system? Since you are not S-Off, you need to find a RUU compatible with your phone's build, specifically for US AT&T. Or you could create a gold card and RU any RUU that way.
Click to expand...
Click to collapse
Just to be safe, I'm creating a gold card right now and in terms of rebooting to system using, is the command fastboot reboot-system or something like that?
I'm sure I have a us att radio laying around somewhere and will post links for you Dakota if I need to go web hunting.
DakotaWhitis said:
could you link me to these?
Click to expand...
Click to collapse
No, because I don't know where they are anymore.
---------- Post added at 03:33 PM ---------- Previous post was at 03:32 PM ----------
shadowboxx said:
Just to be safe, I'm creating a gold card right now and in terms of rebooting to system using, is the command fastboot reboot-system or something like that?
I'm sure I have a us att radio laying around somewhere and will post links for you Dakota if I need to go web hunting.
Click to expand...
Click to collapse
Yes, without the hyphen.
bananagranola said:
No, because I don't know where they are anymore.
---------- Post added at 03:33 PM ---------- Previous post was at 03:32 PM ----------
Yes, without the hyphen.
Click to expand...
Click to collapse
Dang, now I can't get the phone to respond to fastboot or adb. Under the devices command, there's an output of List of devices with a bunch of blank space underneath. There's a USB chime when I plug in the phone and unplug it so I know the PC recognizes it but no dice in terms of getting it to show up in a cmd window anymore.
I also found the RUU's BUT they're exe's and I can't find the Local Files trick in Windows 8. Does anyone know where I can find this section on my PC?
Okay, sorry for posting again but I am completely lost. My HTC Inspire 4g is bricked and stuck in a boot loop between hboot and CWM Touch. At least these things work but trying to flash a rom or go back to stock is not possible for me to do right now and I have zero idea why.
C:\Users\*******\Android\android-sdk\platform-tools>fastboot getvar al
< waiting for device >
INFOversion: 0.5
INFOversion-bootloader: 0.85.0024
INFOversion-baseband: 26.10.04.03_M
INFOversion-cpld: None
INFOversion-microp: 0438
INFOversion-main: 1.00.000.0
INFOserialno: HT15HT204036
INFOimei: ***************
INFOproduct: ace
INFOplatform: HBOOT-7230
INFOmodelid: PD9812000
INFOcidnum: CWS__001
INFObattery-status: good
INFObattery-voltage: 4172mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-ae32a7eb
INFOhbootpreupdate: 11
INFOgencheckpt: 0
INFOregion-id: 0
all: Done!
finished. total time: 0.012s
I'm S-On, unlocked, hboot 0.85.0024, and current version is now 1.00 (CWS__001). It used to be version 2.52 but I apparently did the downgrade step ok. What I'm having trouble with is S-OFF, Super-CID, and SimUnlock. I'd be happy with going back to stock, but since I ultimately want this rooted and rom'ed it might be better to see how I can finish the job.
Thanks for the help! I can't believe I still haven't figured this out.
Is there a good reason why you started a new thread at http://forum.xda-developers.com/showthread.php?t=2270143...? Why not post clearly here on this thread, the one you already have, exactly what you've done and exactly what state you're in, instead of cluttering up the forums? In the interest of full disclosure, I've reported your other thread as a duplicate post.
bananagranola said:
Is there a good reason why you started a new thread at http://forum.xda-developers.com/showthread.php?t=2270143...? Why not post clearly here on this thread, the one you already have, exactly what you've done and exactly what state you're in, instead of cluttering up the forums? In the interest of full disclosure, I've reported your other thread as a duplicate post.
Click to expand...
Click to collapse
Touche, there's really no good reason I had for posting at all or even registering in the first place. I meant no ill will by posting again and will do things differently in the future.
What I have done:
Unlocked the bootloader from htc dev
--during these steps I may have inadvertantly wiped the original rom because I can't get back to it.
Gained at least temp root access judging from the # sign I get when typing the adb shell command
Tried flashing custom roms, RUU's, recoveries, boots.
all of which bring me to the boot loop. (see pics) If I turn the phone on normally, it will stay stuck on the white htc screen. I can get into the bootloader screen easily and also can get access via adb and fastboot as well (I had this connectivity issue earlier and restarting my PC when/if it acts up has been the solution for me!), however from the bootloader screen if I choose recovery, it will reboot into CWM touch. CWM is responsive and I can install zips and have been trying to install Jellytime and Cleardroid but I believe it is because I am still S-OFF that I'm unable to get these to work. The end result of me rebooting from CWM is a quick round trip through the white htc screen and back to CWM as if nothing has happened.
Sorry for the long post, I hope there are enough details to give someone an idea of what's happening.
Read my signature. There is nothing wrong with your phone and it is not bricked. Is it just not S-Off, it is S-On, so you need to fastboot flash the ROM zip's boot.img every time you flash a ROM. This is a question that is answered all over the forums as well as my signature.
bananagranola said:
Read my signature. There is nothing wrong with your phone and it is not bricked. Is it just not S-Off, it is S-On, so you need to fastboot flash the ROM zip's boot.img every time you flash a ROM. This is a question that is answered all over the forums as well as my signature.
Click to expand...
Click to collapse
so you're saying all I need to do is: 1) take the said rom's boot.img file and 2) flash that through fastboot to the device, then 3) reboot, then 4) install the same rom through CWM and it should roar back to life just fine?
Awesome, thanks! I'll try that real quick and post results quickly thereafter!!
---------- Post added at 06:06 PM ---------- Previous post was at 05:36 PM ----------
bananagranola said:
Read my signature. There is nothing wrong with your phone and it is not bricked. Is it just not S-Off, it is S-On, so you need to fastboot flash the ROM zip's boot.img every time you flash a ROM. This is a question that is answered all over the forums as well as my signature.
Click to expand...
Click to collapse
Good news- The boot.img flashed over perfectly and the htc screen will go to the JellyTime screen
Bad news- The screen goes black after a few minutes and nothing responds. I tried flashing the rom zip over fastboot but this is the message I got:
C:\Users\******\Android\android-sdk\platform-tools>fastboot flash zip cm-JellyTi
me_42_R7.zip
sending 'zip' (176023 KB)... OKAY [ 29.406s]
writing 'zip'... FAILED (remote: not allowed)
finished. total time: 29.407s
Any ideas on what to try next?
shadowboxx said:
Bad news- The screen goes black after a few minutes and nothing responds. I tried flashing the rom zip over fastboot but this is the message I got:
C:\Users\******\Android\android-sdk\platform-tools>fastboot flash zip cm-JellyTi
me_42_R7.zip
sending 'zip' (176023 KB)... OKAY [ 29.406s]
writing 'zip'... FAILED (remote: not allowed)
finished. total time: 29.407s
Any ideas on what to try next?
Click to expand...
Click to collapse
Did you full wipe? Did you verify the ROM download? Did you try another ROM?
bananagranola said:
Did you full wipe? Did you verify the ROM download? Did you try another ROM?
Click to expand...
Click to collapse
Can't full wipe now because CWM has disappeared. The rom is good and I'm flashing another one now.
I was on Maximus HD 10.0
Then i tried another rom. but i don't like, so i downloaded 10.2 latest nightly but it on my internal storage-->full wipe-->and then i can't install cm10.2 then i want to but another rom on my internal storage but i can't put anything on the phone without an running rom...
then i changed my recovery to CWM 6. cause i knower there was an option to mount usb storage, but it don't work nothings happened when i click on it. Pleas help me i can do nothing
Some more Infos:C:\test>fastboot getvar all
version: 0.5
version-bootloader: 2.16.0000
version-baseband: 1.20.50.05.16
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: *************
imei: **************
product: vle
platform: HBOOT-8960
modelid: PJ4010000
cidnum: 11111111
battery-status: good
battery-voltage: 4128mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-4958290506
hbootpreupdate: 11
gencheckpt: 0
all: Done!
finished. total time: 0.078s
Jojo1992 said:
I was on Maximus HD 10.0
Then i tried another rom. but i don't like, so i downloaded 10.2 latest nightly but it on my internal storage-->full wipe-->and then i can't install cm10.2 then i want to but another rom on my internal storage but i can't put anything on the phone without an running rom...
then i changed my recovery to CWM 6. cause i knower there was an option to mount usb storage, but it don't work nothings happened when i click on it. Pleas help me i can do nothing
Some more Infos:C:\test>fastboot getvar all
version: 0.5
version-bootloader: 2.16.0000
version-baseband: 1.20.50.05.16
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: SH26RW404047
imei: 359901049107937
product: vle
platform: HBOOT-8960
modelid: PJ4010000
cidnum: 11111111
battery-status: good
battery-voltage: 4128mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-4958290506
hbootpreupdate: 11
gencheckpt: 0
all: Done!
finished. total time: 0.078s
Click to expand...
Click to collapse
I hope this Infos can help to solve my Problem, i have access via Fastboot!
The best would be if i can go back to stock.
Jojo1992 said:
I hope this Infos can help to solve my Problem, i have access via Fastboot!
The best would be if i can go back to stock.
Click to expand...
Click to collapse
You need the old firmware like you had before you updated to Maximus.
Run a RUU.exe and clear storage/factory reset in bootloader when you have the stock recovery back on.
From your other thread I posted more details
http://forum.xda-developers.com/showpost.php?p=47586067&postcount=7
tivofool said:
You need the old firmware like you had before you updated to Maximus.
Run a RUU.exe and clear storage/factory reset in bootloader when you have the stock recovery back on.
From your other thread I posted more details
http://forum.xda-developers.com/showpost.php?p=47586067&postcount=7
Click to expand...
Click to collapse
i downloaded an RUU:
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed
then i make this:
fastboot devices
fastboot oem lock
then start RUU, but error no connection to device but in cmd i get a connection
I have a CID 111111 is that the Problem?
Jojo1992 said:
I have a CID 111111 is that the Problem?
Click to expand...
Click to collapse
I've never changed my CID, no need to. So I'm not an expert.
But from what I have read here:
"You can use any ruu while s-OFF, just simply plug phone to computer and run ruu. No need to relock bootloader.
For the supercid, it is recommended to change it back to original with fastboot command.
Fastboot oem write cid xxxxxxxx.
There has been a few bricks takin Jb ota while still supercid. "
So, not a problem, unless you install a OTA (over the air) update while SuperCid.
Here's a good guide from another forum
http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html
Glancing at that, I noticed it recommends running the RUU on the PC as administrator, maybe it's something simple like that.
tivofool said:
I've never changed my CID, no need to. So I'm not an expert.
But from what I have read here:
"You can use any ruu while s-OFF, just simply plug phone to computer and run ruu. No need to relock bootloader.
For the supercid, it is recommended to change it back to original with fastboot command.
Fastboot oem write cid xxxxxxxx.
There has been a few bricks takin Jb ota while still supercid. "
So, not a problem, unless you install a OTA (over the air) update while SuperCid.
Here's a good guide from another forum
http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html
Glancing at that, I noticed it recommends running the RUU on the PC as administrator, maybe it's something simple like that.
Click to expand...
Click to collapse
I changed my CID back to HTC__102
and tried zwo different RUU.exe one ICS on JB but both have an error...
i relocked my boot loader how can i unlock again?
Jojo1992 said:
I changed my CID back to HTC__102
and tried zwo different RUU.exe one ICS on JB but both have an error...
i relocked my boot loader how can i unlock again?
Click to expand...
Click to collapse
When trying the RUU did you go to bootloader (fastboot USB)?
To Unlock
Locate your Unlock_code.bin on your pc, probably saved it somewhere or it is still in your fastboot folder.
Type this into your command prompt window fastboot flash unlocktoken Unlock_code.bin
or go through the process of getting a new one http://forum.xda-developers.com/showthread.php?t=1583427
Nice tool (Windroid)
http://forum.xda-developers.com/showthread.php?t=2471151
tivofool said:
When trying the RUU did you go to bootloader (fastboot USB)?
To Unlock
Locate your Unlock_code.bin on your pc, probably saved it somewhere or it is still in your fastboot folder.
Type this into your command prompt window fastboot flash unlocktoken Unlock_code.bin
or go through the process of getting a new one http://forum.xda-developers.com/showthread.php?t=1583427
Nice tool (Windroid)
http://forum.xda-developers.com/showthread.php?t=2471151
Click to expand...
Click to collapse
Yes I was in fast boot USB
I will try it one time again and when it don't work then unlock again
Jojo1992 said:
Yes I was in fast boot USB
I will try it one time again and when it don't work then unlock again
Click to expand...
Click to collapse
Oh yeah, I've also read from someone that they got error 155 then they flashed stock recovery and relocked bootloader and then RUU proceeded to work.
tivofool said:
Oh yeah, I've also read from someone that they got error 155 then they flashed stock recovery and relocked bootloader and then RUU proceeded to work.
Click to expand...
Click to collapse
I unlocked and now i could flash:
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed
that worked for me.
So which is the latest CM what i could install now?
Hboot: 1.14.0002
UNLOCKED
S-OFF
Running:
Android 4.0.4 HTC Sense4.1 Softwarenumber:2.31.401.5
Jojo1992 said:
I unlocked and now i could flash:
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed
that worked for me.
So which is the latest CM what i could install now?
Hboot: 1.14.0002
UNLOCKED
S-OFF
Running:
Android 4.0.4 HTC Sense4.1 Softwarenumber:2.31.401.5
Click to expand...
Click to collapse
Glad you were able to get the RUU working. But right now you won't be able to flash many ROMs with that low of a Hboot. You will need to update the firmware.
Since you put your CID back, you would have to put back stock recovery and relock bootloader. Then you could go through settings and do the OTA to update to 2.15 hboot.
Or...this firmware update thread
http://forum.xda-developers.com/showthread.php?t=2322755
tivofool said:
Glad you were able to get the RUU working. But right now you won't be able to flash many ROMs with that low of a Hboot. You will need to update the firmware.
Since you put your CID back, you would have to put back stock recovery and relock bootloader. Then you could go through settings and do the OTA to update to 2.15 hboot.
Or...this firmware update thread
http://forum.xda-developers.com/showthread.php?t=2322755
Click to expand...
Click to collapse
where can i find stock recovery?
flash it like this or?: fastboot flash recovery recover.img
and relock bootloader with: fastboot oem lock ???
Jojo1992 said:
where can i find stock recovery?
flash it like this or?: fastboot flash recovery recover.img
and relock bootloader with: fastboot oem lock ???
Click to expand...
Click to collapse
There is a stock recovery here
http://www.modaco.com/topic/353006-...ch-recovery-for-the-htc-one-s-stock-download/
The SECOND download is the stock one
Unless you change the name of the recovery the command will probably look more like this:
fastboot flash recovery ville_recovery_signed.img
And yes
fastboot oem lock
after you have flashed the stock recovery of course
tivofool said:
Since you put your CID back, you would have to put back stock recovery and relock bootloader. Then you could go through settings and do the OTA to update to 2.15 hboot.
[/url]
Click to expand...
Click to collapse
Or he could just change cid to HTC__001 and flash jb ruu. (The European version)
Sent from HTC One S using android 4.2.2 sense 5
tominozh said:
Or he could just change cid to HTC__001 and flash jb ruu. (The European version)
Sent from HTC One S using android 4.2.2 sense 5
Click to expand...
Click to collapse
That don't work
I tried:
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4
I will try it over ota now --> my Handy ist loading the update 4.1.1 i will report as soon as it is ready
Ok edit:
Hboot 2.15.0000
Unlocked
can i now flash CM10.2?
O.T.: Is CM10.2 running stable?
Jojo1992 said:
That don't work
I tried:
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4
I will try it over ota now --> my Handy ist loading the update 4.1.1 i will report as soon as it is ready
Ok edit:
Hboot 2.15.0000
Unlocked
can i now flash CM10.2?
O.T.: Is CM10.2 running stable?
Click to expand...
Click to collapse
Eh.. It is stable besides for some bootlooping. Like you start it up and it bootloops a few times before finally loading. I like the Avatar Rom which is CM 10.2 based, and noticed a little bootlooping. But it wasn't terrible, just something that happened a few times.
So if that doesn't bother you, go for it. Other than that you would need to stick with sense based roms for stability.
Gosh, so many to choose from you will have to try some out.
http://forum.xda-developers.com/showthread.php?t=2243895
tivofool said:
Eh.. It is stable besides for some bootlooping. Like you start it up and it bootloops a few times before finally loading. I like the Avatar Rom which is CM 10.2 based, and noticed a little bootlooping. But it wasn't terrible, just something that happened a few times.
So if that doesn't bother you, go for it. Other than that you would need to stick with sense based roms for stability.
Gosh, so many to choose from you will have to try some out.
http://forum.xda-developers.com/showthread.php?t=2243895
Click to expand...
Click to collapse
Is the Avatar Rom really 10.2 based? cause on their page they tell 10.1 based or?
but i can install now any rom or?
with the flashed rue which i have actually i don't get mobile internet working. just wlan
Jojo1992 said:
Is the Avatar Rom really 10.2 based? cause on their page they tell 10.1 based or?
but i can install now any rom or?
with the flashed rue which i have actually i don't get mobile internet working. just wlan
Click to expand...
Click to collapse
Ya, guess you are right, 10.1
You can flash any as long as they don't require hboot 2.16 (which they state in the first page OP)
tivofool said:
Ya, guess you are right, 10.1
You can flash any as long as they don't require hboot 2.16 (which they state in the first page OP)
Click to expand...
Click to collapse
ok thank you very much for the help!
So I am a little (a lot) scared to touch my new phone.
I recently acquired an AT&T One X, and it is currently rooted, and running CleanROM 6.5.0. I don't have the history of the device, so I am not sure how its previous owner got it to here, and what the safest steps would be to get it back to pure stock.
I am not worried about resetting the tamper indication or warranty issues. I just would like to get back to the stock AT&T software, and then I can go from there getting it where I want it.
The phone has TWRP Recovery, but had no recovery images. I have made a recovery for where it is at currently.
Bootloader currently shows:
*** LOCKED ***
EVITA PVT SHIP S-ON RL
CID- 11111111
HBOOT-2.15.0000
RADIO -0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Aug 14 2013, 16:02:22 -1
I would say my skill level with phones is "moderate". I at least know enough to not mess with something if I am not 100% sure.
So, from what I am seeing, the phone is S-on, and bootloader is locked, and I have superCID, so I should be able to just flash the proper RUU?
Or, is there anything else I need to do first?
Absolutely do not run an RUU while s-on, SuperCID + s-on + RUU = bricked phone. Where did you read that you can run an RUU with that combination? It's completely untrue. You can't run any RUU anyway, there are no RUUs after your current firmware version and you can't RUU backwards while s-on.
May I ask why you want to return it to a stock at&t ROM though? There is really no benefit of doing so, it's seriously a step backwards because at&t intentionally break some features and leave others out on their ROMs. What is your end goal for this device? I'll help you get there in the most efficient and safe way.
PS. Questions go in the q&a section, please make sure you post in the right section in future.
Sent from my Evita.
timmaaa said:
Absolutely do not run an RUU while s-on, SuperCID + s-on + RUU = bricked phone. Where did you read that you can run an RUU with that combination? It's completely untrue. You can't run any RUU anyway, there are no RUUs after your current firmware version and you can't RUU backwards while s-on.
May I ask why you want to return it to a stock at&t ROM though? There is really no benefit of doing so, it's seriously a step backwards because at&t intentionally break some features and leave others out on their ROMs. What is your end goal for this device? I'll help you get there in the most efficient and safe way.
PS. Questions go in the q&a section, please make sure you post in the right section in future.
Sent from my Evita.
Click to expand...
Click to collapse
Thanks for the heads up! I have been through so many posts in the last couple hours, I probably got confused about where I needed to be to safely RUU.
I don't necessarily want to be on a stock ROM, as much as I just want to return the phone to stock, and start over myself. I don't like the idea of having a customized device, and not knowing how it got there.
BUT, where I would to end up, is with CleanROM 7.0, or something similar. I am just looking for a stock(ish), rooted JB ROM, with sense 5.0.
I don't trust my skills enough to like messing with kernels and such, so I am just looking for a good JB ROM to run.
Thanks for the help! And sorry for the wrong forum.
Your thread is now in the Q&A section:good:
floodx4 said:
Thanks for the heads up! I have been through so many posts in the last couple hours, I probably got confused about where I needed to be to safely RUU.
I don't necessarily want to be on a stock ROM, as much as I just want to return the phone to stock, and start over myself. I don't like the idea of having a customized device, and not knowing how it got there.
BUT, where I would to end up, is with CleanROM 7.0, or something similar. I am just looking for a stock(ish), rooted JB ROM, with sense 5.0.
I don't trust my skills enough to like messing with kernels and such, so I am just looking for a good JB ROM to run.
Thanks for the help! And sorry for the wrong forum.
Click to expand...
Click to collapse
I admire the fact that you want to get it there yourself, the learning aspect of unlocking a device is very important in my eyes. The first thing you need to do is get s-off so you can safely run an RUU without bricking your device. I'll give you a quick run down of the entire process first though.
1. Get s-off.
2. Run the 3.18 RUU.
3. Change CID from SuperCID to original CID.
4. Use the 3.18 root method to gain SuperCID again.
5. Unlock your bootloader at htcdev.
6. Install TWRP recovery.
7. Upgrade to the 2.15 firmware package.
8. Flash Cleanrom 7.x.
So, first you'll need s-off. The easiest way is probably to use the Rumrunner method, you'll find it here:
Http://Rumrunner.us
Even before doing that though you'll need to setup an adb/fastboot environment on your PC. Adb.exe and fastboot.exe are programs you install on Windows in order to communicate with your phone via the usb cable and command prompt. In order for these to work you'll also need HTC drivers installed.
This thread is the easiest way to install adb/fastboot:
http://forum.xda-developers.com/showthread.php?p=42407269
This is where you can find the latest HTC drivers:
http://forum.xda-developers.com/showthread.php?t=2535581
Once you have those both installed you should test out the communication. Connect your phone in fastboot mode (boot into bootloader and connect device, it'll say fastboot usb on the phone), open a command prompt from within your fastboot folder (navigate to where fastboot is located on your PC, shift + right click anywhere in that folder, select open command prompt here), and issue this command:
Code:
fastboot devices
It should now return your device serial number, if it does you can go ahead and attempt Rumrunner s-off. If it doesn't return the serial you have a problem with communication.
Sent from my Evita.
How do I know what the original CID should be?
The above post by me lists how to go about the entire process, which isn't completely necessary but I've outlined it because you said you want to start from the beginning. There is a shorter way to do this, if you'd like to go for that just let me know and I'll outline though too. Your steps there look ok but I'd make a slight change.
Sent from my Evita.
floodx4 please be sure to click timmaaa thanks button.
That's how we show appreciation on XDA
Dang.......
Went through the Rumrunner process, everything seemed to go as it should, but I am still S-on.
Also, tried to unlock through HTC DEV, and I get nothing after flash the unlock token. (phone never gives me the "accept" screen.
Communication is good through fastboot, but something doesn't seem right.
Any ideas, or should I just leave well enough alone and live with 4.1?
Oh, that's my fault, I forgot you need an unlocked bootloader for Rumrunner to work. Sometimes it can take several attempts at flashing the unlock token for it to work, so keep trying that.
Sent from my Evita.
Man.....not sure what the previous owner did here, but....
I tried flashing the unlock token several times....all seemed to go through, but no "accept" screen on the phone.
Finally, I sent the fastboot oem lock command, and it "somewhat" acted like it relocked it. (I did get a FAILED message in there somewhere).
Resent the flash token command, and viola! I got the "accept" screen. Accepted the warning....and.....still locked
Went through Rumrunner again, just to see, and same result. I get the success message, but still have a locked bootloader, and still have s-on.
Back to the drawing board.......
EDIT: Went back through the process again, and noticed that when I send the fastboot oem lock command, the status changes to ***RELOCKED***, and after I flash the token, and accept the warning, the phone resets back to factory.....but bootloader still shows locked.
2nd EDIT: I think I may be on to something here!
Could the phone have one of the tools installed that "spoof" the hboot screen?
Here is what I get from a getvar all:
C:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 0.24p.32.09.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.20.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT255W302399
(bootloader) imei: 3xxxx6
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4052mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.083s
Could I be s-off and unlocked, and just not seeing it?
Yeah, the previous owner has spoofed the hboot, so even though the phone shows locked after you flash the token I believe it's unlocked. Test the theory by trying to install a custom recovery.
Download the modified version of TWRP 2.6.3.0 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now disconnect your phone and select recovery from the bootloader screen on your phone. Hopefully it boots into TWRP recovery, this proves that your bootloader is in fact unlocked.
Sent from my Evita.
timmaaa said:
Yeah, the previous owner has spoofed the hboot, so even though the phone shows locked after you flash the token I believe it's unlocked. Test the theory by trying to install a custom recovery.
<snip>
Click to expand...
Click to collapse
OK, we are getting somewhere!
I have the TWRP recovery. (I believe I already may have had this same recovery, but It did flash successfully via the commands, so I think I'm good)
So....now what? Can I "un-spoof" the hboot to be sure? Or just be satisfied with the above experiment? And if so, does this put me at Step #2 "Flash the 3.18 RUU"?
Yeah I believe you're good to go, I'd like to be doubly sure first though. You can change your CID as many times as you like if you have s-off, but with s-on you can't do that. So I'd suggest trying to change it and this will confirm your security status. The command is:
Code:
fastboot oem writecid 22222222
Hopefully that'll work, confirm by giving this command:
Code:
fastboot oem readcid
Hopefully you'll see eight two's. Once you've confirmed that works you can change it back, and you'll be good to go with the 3.18 RUU. The RUU will install the official 2.14 hboot so the locked/unlocked/relocked flags at the top of your bootloader screen will be normal again.
PS. You might want to edit the IMEI out of your post above, you should never post that publicly.
Sent from my Evita.
Cool, writecid worked.
And speaking of that, Step 3, Change CID to original......what would the original CID be?
I wouldn't worry about that step, the point of that was to use the 3.18 root method.as a learning tool, it's completely unnecessary for you, but to be honest it's more trouble than it's worth. Right now I think you're learning quite a lot so you can run the 3.18 RUU, skip step 3 and 4, you've already unlocked your bootloader so skip step 5, you'll need to install TWRP recovery again after the RUU so do step 6, then you can continue on with steps 7 and 8.
Sent from my Evita.
timmaaa said:
I wouldn't worry about that step, the point of that was to use the 3.18 root method.as a learning tool, it's completely unnecessary for you, but to be honest it's more trouble than it's worth. Right now I think you're learning quite a lot so you can run the 3.18 RUU, skip step 3 and 4, you've already unlocked your bootloader so skip step 5, you'll need to install TWRP recovery again after the RUU so do step 6, then you can continue on with steps 7 and 8.
Sent from my Evita.
Click to expand...
Click to collapse
Awesome.
Just to be sure here....do I want my bootloader locked or unlocked when I flash the RUU?
You're s-off so you can leave the bootloader unlocked. Here's a link for the RUU.
http://dl3.htc.com/application/RUU_..._10.130.32.34_release_signed_With_Partial.exe
Sent from my Evita.
I cant hit the thanks button enough!
CleanRom 7 installed and working great, and best of all, I know where it came from.
Now its time to take this thing for a test drive.......
Oohhhh yeah! That's what I'm talkin bout!
Great news, and once again I admire you for actually wanting to put in the effort and do some learning along the way. Most people want to take the shortest road possible, and they're inevitably the ones who have no idea what to do when something goes wrong.
If you do ever need help in the future just let me know.
Sent from my Evita.
Hello. I am not sure if I am the only one with this issue but here it is.
I have a Verizon HTC One M8. Here is the condition:
NOT rooted
NO OS installed
Stock recovery installed (Can't flash a custom recovery)
S-ON
LOCKED bootloader
Here is some other useful information:
HBoot-3.19.0.0000
Radio-1.14.20.0930
OS-6.21.605.3
Okay, so it is very possible that there is no hope for this phone, but I still feel like there could be. In the state that it is in, I have assumed that I could just flash an RUU so that I would return to stock. This wouldn't work. Every time I would try to flash it through fastboot on the device, I would get part of the way through flashing and then it would say:
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
I have been told that this could mean that the that I have downloaded is possibly corrupt. This seems to not be the case as I have tried downloading it 3 different times. I have also checked the MD5 and they match. I have also tried flashing the RUU by using the executable version. This as well doesn't work. When I try to flash, It gets near to the end of the process and then fails with the error [132] stating that I need to find a RUU that matches my firmware (You can see this in the video linked below). The problem with this is that the RUU that I am using seems to match my firmware. Here is a copy of the txt document that is located within the rom for the RUU.
DelUserData:0
modelid: 0P6B20000
cidnum: VZW__001
mainver: 6.21.605.3
btype:1
aareport:1
hbootpreupdate:12
DelCache:1
DelFrp:1
Seeing the mainver number leads me to believe that this will work on my device. Feel free to link me to the proper RUU if this is wrong.
One other problem is that in order to install a recovery, I need access to adb. I don't have access to adb as I can't turn on USB Debugging because my device doesn't have a OS installed on it. If you have any suggestions or solutions to my problem, please let me know! Thanks!
Here is the link to the video of the RUU error: https://www.youtube.com/watch?v=9aKecZuhWl0&authuser=0
This error happens when attempting to flash RUU through executable file.
Cozmikk said:
Hello. I am not sure if I am the only one with this issue but here it is.
I have a Verizon HTC One M8. Here is the condition:
NOT rooted
NO OS installed
Stock recovery installed (Can't flash a custom recovery)
S-ON
LOCKED bootloader
Here is some other useful information:
HBoot-3.19.0.0000
Radio-1.14.20.0930
OS-6.21.605.3
Okay, so it is very possible that there is no hope for this phone, but I still feel like there could be. In the state that it is in, I have assumed that I could just flash an RUU so that I would return to stock. This wouldn't work. Every time I would try to flash it through fastboot on the device, I would get part of the way through flashing and then it would say:
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
I have been told that this could mean that the that I have downloaded is possibly corrupt. This seems to not be the case as I have tried downloading it 3 different times. I have also checked the MD5 and they match. I have also tried flashing the RUU by using the executable version. This as well doesn't work. When I try to flash, It gets near to the end of the process and then fails with the error [132] stating that I need to find a RUU that matches my firmware (You can see this in the video linked below). The problem with this is that the RUU that I am using seems to match my firmware. Here is a copy of the txt document that is located within the rom for the RUU.
DelUserData:0
modelid: 0P6B20000
cidnum: VZW__001
mainver: 6.21.605.3
btype:1
aareport:1
hbootpreupdate:12
DelCache:1
DelFrp:1
Seeing the mainver number leads me to believe that this will work on my device. Feel free to link me to the proper RUU if this is wrong.
One other problem is that in order to install a recovery, I need access to adb. I don't have access to adb as I can't turn on USB Debugging because my device doesn't have a OS installed on it. If you have any suggestions or solutions to my problem, please let me know! Thanks!
Here is the link to the video of the RUU error: https://www.youtube.com/watch?v=9aKecZuhWl0&authuser=0
This error happens when attempting to flash RUU through executable file.
Click to expand...
Click to collapse
Do you have an SD-Card?
I find the best way to do an RUU is using the SD-Card. Very safe, as power could turn off or something.
EDIT: I see in the video you tried that.
Sorry. :-/
more RUU's to try?
https://www.androidfilehost.com/?fid=24438995911975667
https://www.androidfilehost.com/?fid=24052804347813946
andybones said:
Do you have an SD-Card?
I find the best way to do an RUU is using the SD-Card. Very safe, as power could turn off or something.
EDIT: I see in the video you tried that.
Sorry. :-/
more RUU's to try?
https://www.androidfilehost.com/?fid=24438995911975667
https://www.androidfilehost.com/?fid=24052804347813946
Click to expand...
Click to collapse
I have already tried the android 6.0 RUU. I can't try the 5.0.1 RUU because I don't have S-Off and I am already on the 6.0 firmware and can't downgrade.
Cozmikk said:
I have already tried the android 6.0 RUU. I can't try the 5.0.1 RUU because I don't have S-Off and I am already on the 6.0 firmware and can't downgrade.
Click to expand...
Click to collapse
Wish I could be of help.
andybones said:
Wish I could be of help.
Click to expand...
Click to collapse
Its okay. I am talking to someone right now who should be able to help me with javacard or something near to it so I can at least get s-off.
Cozmikk said:
Its okay. I am talking to someone right now who should be able to help me with javacard or something near to it so I can at least get s-off.
Click to expand...
Click to collapse
Glad to hear. :good:
Hey did you find a solution? I have pretty much the same problem (Except, I do have S-OFF, but I relocked my bootloader so I still can't flash a custom recovery...)
MSFTGhoul said:
Hey did you find a solution? I have pretty much the same problem (Except, I do have S-OFF, but I relocked my bootloader so I still can't flash a custom recovery...)
Click to expand...
Click to collapse
You can. I have posted ruu mode custom firmware zips that have twrp included just for this scenario. Then you can unlock the bootloader. Your scenario is not at all the same as the above.
Sent from my HTC6545LVW using Tapatalk