Related
Hi there,
I've got a desire that keeps looping on the HTC screen. Stays there for a few seconds and then restarts.
I can go into the HBOOT menu and FASTBOOT mode, I can easily access it through the fastboot from windows as well. But I wasn't able to get revolutionary to detect it. (I guess it needs the device to be in the OS which can't happen cuz of the boot loop).
I tried to fastboot boot into 4ext recovery through recovery.img file it says:
downloading 'boot.img'...
OKAY [ 0.563s]
booting...
FAILED (remote: not allowed)
finished. total time: 0.568s
When I try to fastboot flash an img it says:
sending 'recovery' (3784 KB)...
OKAY [ 0.564s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.227s
I also can't use the method on htcdevs for unlocking the bootloader cuz it says :
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.009s
Here's my fastboot vars dump:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.02.0001
(bootloader) version-baseband: 5.17.05.23
(bootloader) version-cpld: None
(bootloader) version-microp: 031d
(bootloader) version-main: 3.14.405.1
(bootloader) serialno: HT047PL00475
(bootloader) imei: 357841032013118
(bootloader) product: bravo
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PB9920000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3982mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: a7cdbe26
(bootloader) hbootpreupdate: 11
all: Done!
finished. total time: 0.030s
I've also tried creating a goldcard but I can't read the goldcard's CID from windows, none of the applications work for me, even when I am using a card slot on my laptop and not a USB card reader.
Can anyone guide me here?
I am pretty much banging my head on the wall right now
Thanks a ton.
Did you unlock your bootloader?
Two beer or not two beer, that's the question
Nope, I couldn't unlock the bootloader cuz I couldn't complete the htcdev tutorial.
Neither could i use revolutionary
At this point RUU would be safest bet
Try the 2.3.3 gingerbread RUU
eddiehk6 said:
At this point RUU would be safest bet
Try the 2.3.3 gingerbread RUU
Click to expand...
Click to collapse
Great!
So, looking at my fastboot vars dump above, can you recommend a link for the RUU, cuz I've tried a number of RUUs but most of them give that "you need to upgrade" message and don't work .
eddiehk6 said:
At this point RUU would be safest bet
Try the 2.3.3 gingerbread RUU
Click to expand...
Click to collapse
In fact, I am trying this one: http://www.htcdev.com/process/legal_download/152 as mentioned in the thread http://forum.xda-developers.com/showthread.php?t=1931014.
Lets hope it works.
Is this the right one?
shabeepk said:
Nope, I couldn't unlock the bootloader cuz I couldn't complete the htcdev tutorial.
Neither could i use revolutionary
Click to expand...
Click to collapse
Why can't you use revolutionary?
Your hboot is supported and you have obviously fastboot working.
So this should be the easiest method for you to unlock and get s-off!
tom0769 said:
Why can't you use revolutionary?
Your hboot is supported and you have obviously fastboot working.
So this should be the easiest method for you to unlock and get s-off!
Click to expand...
Click to collapse
Revolutionary stays stuck at "waiting for device". I don't know why but for some reason it does. It seems to be that it needs the phone to be in the OS loaded with usb debugging enabled.
No?
shabeepk said:
In fact, I am trying this one: http://www.htcdev.com/process/legal_download/152 as mentioned in the thread http://forum.xda-developers.com/showthread.php?t=1931014.
Lets hope it works.
Is this the right one?
Click to expand...
Click to collapse
:S I downloaded the RUU, and now it keeps saying ur battery is less than 30% ...
eddiehk6 said:
At this point RUU would be safest bet
Try the 2.3.3 gingerbread RUU
Click to expand...
Click to collapse
Eddie,
Do you think you could help me with this battery issue?
I downloaded the RUU, and now it keeps saying ur battery is less than 30%, even though I think I've charged the battery, the charge LED shows green and fastboot vars say:
(bootloader) battery-status: good
(bootloader) battery-voltage: 4187mV
Do you know what might be wrong ?
shabeepk said:
Eddie,
Do you think you could help me with this battery issue?
I downloaded the RUU, and now it keeps saying ur battery is less than 30%, even though I think I've charged the battery, the charge LED shows green and fastboot vars say:
(bootloader) battery-status: good
(bootloader) battery-voltage: 4187mV
Do you know what might be wrong ?
Click to expand...
Click to collapse
Okay, after trying for a few hours I was finally able to run the RUU... some how :S. I really don't know how.
However, the update process went smooth, no issues, BUT ! :s the bootloop is still there.
Do you think this might be a hardware fault? Do you think this phone doesn't have its actual stuff i.e. the ROM. the RADIO and HBOOT? Do you think I should check other info on the phone tag or something to guess the correct firmware?
This RUU seemed like an all Desire one. No ?
Dead end ... :S
So the RUU successfully flashed but it still won't even boot? Strange
Try revolutionary again, did you install the relevant hboot drivers? Find the revolutionary.io documentation page, instructions should be on there
eddiehk6 said:
So the RUU successfully flashed but it still won't even boot? Strange
Try revolutionary again, did you install the relevant hboot drivers? Find the revolutionary.io documentation page, instructions should be on there
Click to expand...
Click to collapse
Yes, I know its very strange :S
I did try that, however, it wasn't that simple. The drivers present on the revolutionary website didn't detect my device in HBOOT, it was only detecting the device in FASTBOOT, and in FASTBOOT revolutionary still didn't detect the device.
Then I had to download the altered driver and then install it manually. Now My device is detected in both; Fastboot and HBOOT mode. But revolutionary still can't detect it, in neither of the modes.
Any Idea why ? And what I may have done wrong there.
Try and follow this exactly, see if it makes any difference. The video helps
http://theunlockr.com/2011/08/02/ho...android-phone-using-the-revolutionary-method/
eddiehk6 said:
Try and follow this exactly, see if it makes any difference. The video helps
http://theunlockr.com/2011/08/02/ho...android-phone-using-the-revolutionary-method/
Click to expand...
Click to collapse
Tried that, but the problem I am probably facing is that to gain s-off, revolutionary needs to phone to be in USB debugging mode i.e. adb mode with the OS running ofcourse. While I can't get past HBOOT / FASTBOOT. So revolutionary ain't working for me.
I don't know what to do now.
Any suggestions?
ah...
Only thing I can think of is keep trying the RUU until it boots properly.
Print out any error messages if it has any.
Ive been reading this section of the forum for 2 nights now. read various threads and none the wiser.
Ive unlocked my htc one x using the windroid htc one app which worked fine, but installing a rom was not as easy. now < i admit, i dived in and installed a ROM without seeing what else it needs to work ( am used to flashing nexus roms) and now its stuck at the HTC screen. Now i've tried various ways to rectify the proplem. uisng various roms, flashing boot.img before flashing the rom, no go. tried older roms, no go.
I know the hboot needs updating, but without a cid id then i cant find a matching firmware.zip.
Ive tried to do a RUU boot by locking the bootloader but get this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip rom.zip
sending 'zip' (153709 KB)...
OKAY [ 19.444s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 29.009s
So am at a loss and asking for help.
(bootloader) version: 0.5a
(bootloader) version-bootloader: 0.95.0000
(bootloader) version-baseband: 2.1204.135.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.11
(bootloader) serialno: HT
(bootloader) imei:
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: None
(bootloader) battery-status: good
(bootloader) battery-voltage: 3990mV
(bootloader) devpower: 82
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
hope the above info helps.
ajg008 said:
Ive been reading this section of the forum for 2 nights now. read various threads and none the wiser.
Ive unlocked my htc one x using the windroid htc one app which worked fine, but installing a rom was not as easy. now < i admit, i dived in and installed a ROM without seeing what else it needs to work ( am used to flashing nexus roms) and now its stuck at the HTC screen. Now i've tried various ways to rectify the proplem. uisng various roms, flashing boot.img before flashing the rom, no go. tried older roms, no go.
I know the hboot needs updating, but without a cid id then i cant find a matching firmware.zip.
Ive tried to do a RUU boot by locking the bootloader but get this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip rom.zip
sending 'zip' (153709 KB)...
OKAY [ 19.444s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 29.009s
So am at a loss and asking for help.
(bootloader) version: 0.5a
(bootloader) version-bootloader: 0.95.0000
(bootloader) version-baseband: 2.1204.135.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.11
(bootloader) serialno: HT
(bootloader) imei:
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: None
(bootloader) battery-status: good
(bootloader) battery-voltage: 3990mV
(bootloader) devpower: 82
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
hope the above info helps.
Click to expand...
Click to collapse
Lock your bootloader fastboot oem lock after this run RUU 1.29.401.11 as administrator and follow the instruction. After RUU finish update the phone to latest JB from Settings/About/Software Updates!
Report back
thanks. Downloading now, will try when i return home from work
Thant said:
Lock your bootloader fastboot oem lock after this run as administrator and follow the instruction. After RUU finish update the phone to latest JB from Settings/About/Software Updates!
Report back
Click to expand...
Click to collapse
thanks for your help that got the phone back to booting properly
I flashed it and it worked. I got myself back to the latest update. Now i tried various roms again as i'm one for experimenting but some of the newest ones dont seem to want to work.
ones i've tried>
Android_Revolution_HD-One_X_33.1
HTC_One_X_-_MaximusHD_21.0.0
OneX The Next Chapter! v1.2
but none of them worked for me.
So i went lower with
cm-10.1.3-endeavoru which worked
then updated to
cm-10.2.0-endeavoru and flashed the boot.img for it to work.
Now for the other roms, what am i missing? is it the firmware.zip? hboot level?
Am bowing down to Thant, and hoping he can tell a mere minion what he's doing wrong
I don't think you updated far enough ! Post the outcome of :
Fastboot getvar version-main
Edit :
I see thant is offline, so i chip in......
Mr Hofs said:
I don't think you updated far enough ! Post the outcome of :
Fastboot getvar version-main
Edit :
I see thant is offline, so i chip in......
Click to expand...
Click to collapse
the result is:
version-main: 2.17.401.2
What i thought. You need to run another ruu and update many more ota's
Here is the ruu
http://www.persianhtc.net/index.php...Radio_2.1204.135.20_release_274900_signed.exe
Mr Hofs said:
What i thought. You need to run another ruu and update many more ota's
Here is the ruu
[ul]h*tp://w*w.persianhtc.net/index.php?dir=One%20X%28Endeavor%29/rom/original/exe/&file=RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe[/url]
Click to expand...
Click to collapse
downloading now, but need sleep now and will report back tomorrow.
thanks very much for your help.
bows to Mr Hofs
Same here.
cyanogenmod stable rom not recognising sim, and not being recognised by htc sync
Hi i just unlocked and rooted my phone. one of the first things i did after having rooted it was go into rom-manager and download the highest rated cyanogen mod stable rom...expecting it to reboot itself and do the update automatically once id downloaded the file i was suprised when nothing happened...so i put it into recovery mode myself and searched the phone's storage for the rom file...it was infact two files, one the rom, the other gapps...i installed both of them and rebooted the phone...at first i was left on cyanogenmod bootloop...after a few restarts, and factory resets, i eventually got past the cyanogen mod intro wheel, to its actual introduction *asking me to choose a language*, as soon i choose my language i get notification asking me to insert my simcard (it already is, OF COURSE...), as i go through the rest of the setup there is no network coverage or internet..so i cant simply download rom-manager and try another flash..it also wont come up as a recognised device on my macbook...ive downloaded another flash of cyanogenmod on my laptop along with a new gapps, but im utterly lost about what to do now...i cant even put them on the phone....
wud love any help
The recovery version I'm using is clockworkMod Recovery v5.8.2.7
And here is my bootloader
ENDEAVORU PVT SHIP 2-ON RL
HBOOT-1.72.0000
CPLD-None
RADIO-5.1204.167.31
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF
Jun 21 2013,18:24:21
tekkr said:
Hi i just unlocked and rooted my phone. one of the first things i did after having rooted it was go into rom-manager and download the highest rated cyanogen mod stable rom...expecting it to reboot itself and do the update automatically once id downloaded the file i was suprised when nothing happened...so i put it into recovery mode myself and searched the phone's storage for the rom file...it was infact two files, one the rom, the other gapps...i installed both of them and rebooted the phone...at first i was left on cyanogenmod bootloop...after a few restarts, and factory resets, i eventually got past the cyanogen mod intro wheel, to its actual introduction *asking me to choose a language*, as soon i choose my language i get notification asking me to insert my simcard (it already is, OF COURSE...), as i go through the rest of the setup there is no network coverage or internet..so i cant simply download rom-manager and try another flash..it also wont come up as a recognised device on my macbook...ive downloaded another flash of cyanogenmod on my laptop along with a new gapps, but im utterly lost about what to do now...i cant even put them on the phone....
wud love any help
The recovery version I'm using is clockworkMod Recovery v5.8.2.7
And here is my bootloader
ENDEAVORU PVT SHIP 2-ON RL
HBOOT-1.72.0000
CPLD-None
RADIO-5.1204.167.31
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF
Jun 21 2013,18:24:21
Click to expand...
Click to collapse
Rom manager not working on S-ON devices flash the boot.img manually from fastboot with command fastboot flash boot boot.img take the boot.img from rom arhiv wich you want to install
Thant said:
Rom manager not working on S-ON devices flash the boot.img manually from fastboot with command fastboot flash boot boot.img take the boot.img from rom arhiv wich you want to install
Click to expand...
Click to collapse
the reason i'm so frustrated is aside from the supposedly stable build of cyanogen mod i downloaded in rommanager not working, the rom doesnt recognise my sim, i dont have access to the internet, so i cant simply download a new rom to flash straight from rom manager...as well as this the wifi doesn't seem to work on this flash...and to make matters worse it's not being recognised by the drivers...i'm using htc sync manager..when i plug in the phone it will open htc sync manager but wont show that a phone is paired to my macbook
...when u say manually can i do this directly from my phone or do i need to connect it to a computer?
You must connect it to PC..And then go to fastboot and flash boot.img file..Then you will have signal,wifi etc..
big noob said:
You must connect it to PC..And then go to fastboot and flash boot.img file..Then you will have signal,wifi etc..
Click to expand...
Click to collapse
its not being recognised as a device since i flashed the *cyanogen mod stable rom*...i plugged it to my computer though, and put it into fastboot and it says FASTBOOT USB...the options it gives me from here are
HBOOT
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Here is guide how to use ADB on macbook:
http://forum.xda-developers.com/showthread.php?t=1917237
And then you can use fastboot commands..
Mr Hofs said:
What i thought. You need to run another ruu and update many more ota's
Here is the ruu
[ul]ht*p://w*w.persianhtc.net/index.php?dir=One%20X%28Endeavor%29/rom/original/exe/&file=RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe[/url]
Click to expand...
Click to collapse
ive tried that but keep getting signature error
ajg008 said:
ive tried that but keep getting signature error
Click to expand...
Click to collapse
Relocked the bootloader ?
Mr Hofs said:
Relocked the bootloader ?
Click to expand...
Click to collapse
yep fastboot oem lock
Then it might be easier to flash the 3.14.401 firmware to upgrade the hboot to 1.39. Then you can flash any rom you want, and there is also a ruu for that. Sorry i have no time to explain now (heading home from work)
Look for the firmware placeholder thread, read the instructions and download the 3.14.401 firmware.zip from there.
http://forum.xda-developers.com/showthread.php?t=1957376
Mr Hofs said:
Then it might be easier to flash the 3.14.401 firmware to upgrade the hboot to 1.39. Then you can flash any rom you want, and there is also a ruu for that. Sorry i have no time to explain now (heading home from work)
Look for the firmware placeholder thread, read the instructions and download the 3.14.401 firmware.zip from there.
[rl]htp://forum.xda-developers.com/showthread.php?t=1957376[/url]
Click to expand...
Click to collapse
i already had the ota 3.14.401 and got the firmware.zip from there.
its installed fine and i now can put most roms onto it.
:victory: thank you Mr Hofs
So i get this right in my head. The phones firmware.zip needed updated so it would update hboot and other things.
Now to flash roms is the procedure to flash the boot.img contained inside first then install the rom <----which is they way ive being doing it
Hi Guys,
It's been a while since I wrote on this forum... I may be tired, but I can't work out a few things:
I have a T-Mobile UK HTC One X, due to some circumstances I needed to completely wipe...
I was already running an unbranded stock firmware on it, but after the complete wipe i wanted to install JB 4.2.2 S5 - I usually unlock the bootloader, install clockworks, copy the original unedited complete firmware zip on it and install it via the recovery, then relock the bootloader and job done, but I cannot seem to find a complete unedited rom, is either RUU.exe (which I cannot run as the PC wont see the phone due to no firmware on it, I think) or nandrom backups which I don't really want, all the OTA ones seem to just be updates and am stuck with a phone that only has clockwork recovery on it....
Where can I get an official unedited zip that I can install via clockworks?
Thanks
LondonVirus said:
Hi Guys,
It's been a while since I wrote on this forum... I may be tired, but I can't work out a few things:
I have a T-Mobile UK HTC One X, due to some circumstances I needed to completely wipe...
I was already running an unbranded stock firmware on it, but after the complete wipe i wanted to install JB 4.2.2 S5 - I usually unlock the bootloader, install clockworks, copy the original unedited complete firmware zip on it and install it via the recovery, then relock the bootloader and job done, but I cannot seem to find a complete unedited rom, is either RUU.exe (which I cannot run as the PC wont see the phone due to no firmware on it, I think) or nandrom backups which I don't really want, all the OTA ones seem to just be updates and am stuck with a phone that only has clockwork recovery on it....
Where can I get an official unedited zip that I can install via clockworks?
Thanks
Click to expand...
Click to collapse
Give the result from command fastboot getvar version-main
Thant said:
Give the result from command fastboot getvar version-main
Click to expand...
Click to collapse
version-main: 3.16.110.4
cidnum: T-MOB005
But as I said, I want a non branded, complete flash room please
LondonVirus said:
version-main: 3.16.110.4
cidnum: T-MOB005
But as I said, I want a non branded, complete flash room please
Click to expand...
Click to collapse
sorry fastboot getvar all and delte your S/N and IMEI from the info I didn't read what you wamt you want rom with sense 5 give the result to see your hboot version
Thant said:
sorry fastboot getvar all and delte your S/N and IMEI from the info I didn't read what you wamt you want rom with sense 5 give the result to see your hboot version
Click to expand...
Click to collapse
C:\Android\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.39.0000
(bootloader) version-baseband: 5.1204.163R.30
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.110.4
(bootloader) serialno: -
(bootloader) imei: -
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: T-MOB005
(bootloader) battery-status: low
(bootloader) battery-voltage: 3446mV
(bootloader) devpower: 0
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.826s
Sorry it took me a while... life and kids eh lol... I am trying to sort this phone for the MRS, I have a Galaxy S5, great device
I must say I would even be happy with the TMO UK RUU, this pone is doing my head in at the moment and really don't have the time to be messing with it now, just need it working...
I wanted to change Super CID it but apparently it will need to be s-off and cant get round to do that, I wanted to install a non branded RUU but this is not allowed due to the wrong CID arg, stupid phones, was easier to flash unbranded firmware to old Nokia on Symbian...
LondonVirus said:
C:\Android\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.39.0000
(bootloader) version-baseband: 5.1204.163R.30
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.110.4
(bootloader) serialno: -
(bootloader) imei: -
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: T-MOB005
(bootloader) battery-status: low
(bootloader) battery-voltage: 3446mV
(bootloader) devpower: 0
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.826s
Sorry it took me a while... life and kids eh lol... I am trying to sort this phone for the MRS, I have a Galaxy S5, great device
I must say I would even be happy with the TMO UK RUU, this pone is doing my head in at the moment and really don't have the time to be messing with it now, just need it working...
I wanted to change Super CID it but apparently it will need to be s-off and cant get round to do that, I wanted to install a non branded RUU but this is not allowed due to the wrong CID arg, stupid phones, was easier to flash unbranded firmware to old Nokia on Symbian...
Click to expand...
Click to collapse
You have good hboot for sense 5 rom 4.2.2 install MaximusHD or ARHD or any sense 5 rom and you are ready to go.
I wanted a stock ROM, the Mrs is not very technical minded lol and a customer ROM won't help her, either TMO UK or in branded, where can I get the RUU for it?
Thanks all
Unfortunately T-Mobile skipped the sense 5, 4.2.2 update, I have the same device and cid and called them countless times, spoke to managers and had it escalated to the highest level only to be told they would not be updating past 4.1.1
Every other network pushed that but them, if you stick to stock T-Mobile ROM you would be missing 2 very important updates, one being the heartbleed patch.
Just grab MaximusHD from the development forum, its the best sense 5 ROM out there and has important ota updates too.
I suppose I will have install it via the custom recovery, could I not install the unbranded RUU 4.2.2? Does anyone know how to s-off correctly, so that I can change the CID.
By the way thank you all for your replies
LondonVirus said:
I suppose I will have install it via the custom recovery, could I not install the unbranded RUU 4.2.2? Does anyone know how to s-off correctly, so that I can change the CID.
By the way thank you all for your replies
Click to expand...
Click to collapse
NO S-OFF for HOX
Thant said:
NO S-OFF for HOX
Click to expand...
Click to collapse
I assume that HOX means Htc One X lol... so I will not be able to change the CID?
Any "re-pack" unedited versions of the genuine unbranded europe RUU that I can install via custom recovery?
Thanks again all
There must be a way to s-off the Maximus HD ROM says "1. Make sure your device is unlocked or have s-off"
Why would it say that on "http://forum.xda-developers.com/showthread.php?t=2410320" if there was no s-off ways? am confused lol
LondonVirus said:
There must be a way to s-off the Maximus HD ROM says "1. Make sure your device is unlocked or have s-off"
Why would it say that on "http://forum.xda-developers.com/showthread.php?t=2410320" if there was no s-off ways? am confused lol
Click to expand...
Click to collapse
Don't be confused mate..HOX can s-off but via java card( will cost money to make it).In here no have chance to be s-off.
Installation of Maximus HD no hanging on this screen, flashed Kernel and wiped the memory fkn phones!
LondonVirus said:
Installation of Maximus HD no hanging on this screen, flashed Kernel and wiped the memory fkn phones!
Click to expand...
Click to collapse
Never mind, seems to have worked lol
LondonVirus said:
Never mind, seems to have worked lol
Click to expand...
Click to collapse
Phone hanging on boot screen don't know why...
LondonVirus said:
Phone hanging on boot screen don't know why...
Click to expand...
Click to collapse
are you flashed the boot.img from maximushd archive via fastboot with the command fastboot flash boot boot.img
Thant said:
are you flashed the boot.img from maximushd archive via fastboot with the command fastboot flash boot boot.img
Click to expand...
Click to collapse
Thank you for your reply, I did flash the boot via the "Kernel+Flasher+21.0.0" looking at the coding inside the batch file, it calls a batch in a sub-folder with the command fastboot flash boot boot.img, and I did run it and got Okay message in the command window...
LondonVirus said:
Thank you for your reply, I did flash the boot via the "Kernel+Flasher+21.0.0" looking at the coding inside the batch file, it calls a batch in a sub-folder with the command fastboot flash boot boot.img, and I did run it and got Okay message in the command window...
Click to expand...
Click to collapse
do it manually like I write you in my post not with flasher or tool
Thant said:
do it manually like I write you in my post not with flasher or tool
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------------------------------------
C:\Android\sdk\platform-tools>fastboot flash zip rom.zip
sending 'zip' (716000 KB)...
OKAY [ 90.451s]
writing 'zip'...
(bootloader) Can not find [android-info.txt] in zipped image!
FAILED (remote: 24 parsing android-info fail)
finished. total time: 125.830s
---------------------------------------------------------------------------------------------------------------------
fastboot oem rebootRUU
fastboot flash zip rom.zip <----- This is Maximus HD....
and this is after a flashed the correct kernel/boot.img....
I have been rooted for a few weeks and decided to go back. Well I had S-off but when I started the transition to stock I turned s-on and that is when the **tampered** flag came on. I stupidly continued using the code (fastboot oem lock) which gave me the **Relocked** status but now I have a security warning and It will ONLY boot into bootloader. I have tried multiple times re-flashing TWRP and I cant get it to go into recovery. From what I have read I need to flash stock rom onto it but I cant get into the recovery to flash or even sideload. So where should I go from here? Everything I need to do requires S-off and I cant seem to get it.
*ALSO I am currently on InsertKoin ROM* <--That might change something
*HtcDev will not work for my phone.*
fastboot oem unlock gives ERR [command error]
Last flashed TWRP version was 2.7.0.1
Specs.
M7_WLV PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-1.13.41.0109_2
OpenDSP-v32.120.274.0909
OS-3.11.605.1
eMMC-boot 2048MB
GetVar info below also.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 1.13.41.0109_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.605.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA3B6S906771
(bootloader) imei: 990004282795917
(bootloader) meid: 99000428279591
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4134mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.055s
Oh! If someone would mind explaining what any of that means (even just an acronym) would help for me learning this!
Thank you in advance. John
I've been S-Off since day one so double check everything but this will get you in the right direction. You need to S-off and unlock, flash an RUU and then relock (to remove the red text warning). Going back to S-on I understand is pretty dangerous and appears to be unnecessary. Go to this thread and start with the 3rd tutorial to re-S-off. If you can get S-off'd the rest should be pretty easy.
jman036 said:
I have been rooted for a few weeks and decided to go back. Well I had S-off but when I started the transition to stock I turned s-on and that is when the **tampered** flag came on. I stupidly continued using the code (fastboot oem lock) which gave me the **Relocked** status but now I have a security warning and It will ONLY boot into bootloader. I have tried multiple times re-flashing TWRP and I cant get it to go into recovery. From what I have read I need to flash stock rom onto it but I cant get into the recovery to flash or even sideload. So where should I go from here? Everything I need to do requires S-off and I cant seem to get it.
*HtcDev will not work for my phone.*
fastboot oem unlock gives ERR [command error]
Last flashed TWRP version was 2.7.0.1
Specs.
M7_WLV PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-1.13.41.0109_2
OpenDSP-v32.120.274.0909
OS-3.11.605.1
eMMC-boot 2048MB
GetVar info below also.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 1.13.41.0109_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.605.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA3B6S906771
(bootloader) imei: 990004282795917
(bootloader) meid: 99000428279591
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4134mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.055s
Oh! If someone would mind explaining what any of that means (even just an acronym) would help for me learning this!
Thank you in advance. John
Click to expand...
Click to collapse
That should be early enough to use Firewater on. Let me know if you run into problems because I can help via team viewer.
@pmterp & @dottat Thanks for the reply and that sounds like a good idea but I have to push the file via adb. I cannot get there because I am stuck in the fastboot section. So I don't think firewater or anything that uses adb will work.
Crud. I don't remember if you can get to RUU mode without being S-off. In fastboot the command is fastboot OEM rebootRUU If you can then you could re-RUU but I'm thinking you have to be S-off to get there. Hopefully someone else will chime in with some better ideas.
pmterp said:
Crud. I don't remember if you can get to RUU mode without being S-off. In fastboot the command is fastboot OEM rebootRUU If you can then you could re-RUU but I'm thinking you have to be S-off to get there. Hopefully someone else will chime in with some better ideas.
Click to expand...
Click to collapse
You can go into ruu mode while s-on, but need a signed ruu. Last signed ruu we had was 2.x
Sent from my HTC6500LVWBLU using XDA Free mobile app
pmterp said:
Crud. I don't remember if you can get to RUU mode without being S-off. In fastboot the command is fastboot OEM rebootRUU If you can then you could re-RUU but I'm thinking you have to be S-off to get there. Hopefully someone else will chime in with some better ideas.
Click to expand...
Click to collapse
I tried that command and it did do something different now. It is an all black screen with silver HTC however it is not doing anything.
jman036 said:
I tried that command and it did do something different now. It is an all black screen with silver HTC however it is not doing anything.
Click to expand...
Click to collapse
That is RUU mode and will accept an RUU file to flash at this point. I believe Uzephi is correct that the RUU you flash must be signed (which I think is the same as encrypted). I'm not sure where you would find them but I'm sure Google will be your friend on that. Be careful what version you flash because I think it can cause problems if you move down. I'm not sure how open he is to helping via PM (he's super helpful but also very busy) but if it were me I'd reach out via PM to @santod040 and ask for advice. He's a highly skilled dev who's been with this device a long time.
I think I might be in the same boat as jman036, only difference being that I'm on a later OS version (5.28.605.2). I've tried flashing signed RUUs for my particular OS version from both santod's and dottat's AndroidFileHosts but both give me this error:
"(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)"
Sucks man.
tflogic said:
I think I might be in the same boat as jman036, only difference being that I'm on a later OS version (5.28.605.2). I've tried flashing signed RUUs for my particular OS version from both santod's and dottat's AndroidFileHosts but both give me this error:
"(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)"
Sucks man.
Click to expand...
Click to collapse
Both of their 5.28.605.2 ruus are decrypted and thus unsigned. You will get a signature check fail if you are s-on
Sent from my HTC6500LVWBLU using XDA Free mobile app
Uzephi said:
Both of their 5.28.605.2 ruus are decrypted and thus unsigned. You will get a signature check fail if you are s-on
Click to expand...
Click to collapse
Dang really? I thought they would be since they both have "signed" in the filenames.
HSM_M7_WL_K443_SENSE60_VZW_MR_VERIZON_WWE_5.28.605.2_HSM_Radio_1.13.41.0702_NV_VZW_4.64_002_release_387332_signed.zip
Click to expand...
Click to collapse
Any idea what to do then?
tflogic said:
Dang really? I thought they would be since they both have "signed" in the filenames.
Any idea what to do then?
Click to expand...
Click to collapse
Yes. Will fail. You should try installing the latest HTC sync and seeing if the repair button lights up for you on the home page of the app.
---------- Post added at 10:55 PM ---------- Previous post was at 10:55 PM ----------
Uzephi said:
Both of their 5.28.605.2 ruus are decrypted and thus unsigned. You will get a signature check fail if you are s-on
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
Actually I have one of each ?
---------- Post added at 10:58 PM ---------- Previous post was at 10:55 PM ----------
jman036 said:
I tried that command and it did do something different now. It is an all black screen with silver HTC however it is not doing anything.
Click to expand...
Click to collapse
See if you can flash this zip while your phone is in this ruu mode.
Fastboot flash zip firmware3.zip
May require flashing twice.
https://www.androidfilehost.com/?fid=23681161096070340
dottat said:
Yes. Will fail. You should try installing the latest HTC sync and seeing if the repair button lights up for you on the home page of the app.
Click to expand...
Click to collapse
HTC Sync doesn't recognize the phone. Getting a "no phone connected" message. Any other ideas?
tflogic said:
HTC Sync doesn't recognize the phone. Getting a "no phone connected" message. Any other ideas?
Click to expand...
Click to collapse
If installed drivers are correct htc sync will see the phone. I just responded to your post in a different thread. Can you try that first before we troubleshoot drivers?
pmterp said:
Crud. I don't remember if you can get to RUU mode without being S-off. In fastboot the command is fastboot OEM rebootRUU If you can then you could re-RUU but I'm thinking you have to be S-off to get there. Hopefully someone else will chime in with some better ideas.
Click to expand...
Click to collapse
Fastboot oem rebootRUU mode is supported in both s on/off scenarios. An s on user can always use this to reflash same firmware or even upgrading to newer firmware. Bootloader unlocked phones often take advantage of this before s off exploits are found.
Uzephi said:
Both of their 5.28.605.2 ruus are decrypted and thus unsigned. You will get a signature check fail if you are s-on
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
Yeah I cant seem to find any RUU files that match my phone!
dottat said:
Fastboot oem rebootRUU mode is supported in both s on/off scenarios. An s on user can always use this to reflash same firmware or even upgrading to newer firmware. Bootloader unlocked phones often take advantage of this before s off exploits are found.
Click to expand...
Click to collapse
Well I made it one step further with it recognizing that I have a phone connected but said "no software available."
I think if I can find a signed RUU file then I can fix this. I just have to find it.....
See if you can flash this zip while your phone is in this ruu mode.
Fastboot flash zip firmware3.zip
May require flashing twice.
https://www.androidfilehost.com/?fid=23681161096070340
Click to expand...
Click to collapse
Well I tried this and sadly I can send it but it always gets signature check fail. :/ (I ran it twice also)
Hi folks.
I have searched this forum for assistance to my problem. Although i have read issues which are similar to mine, however, i'm still not able to find definitive instructions.
My problem is that two phones i have acquired - HTC One M8 and HTC One M9 are both stuck on the HTC logo screen. However, I can get into the Bootloader screen (power + vol down instructions from the forum), but that's as far as my knowledge takes me. I am not a complete novice, so am prepared to follow instructions, and am aware of the risks involved.
May be i should've posted in the M9 forum too??
The Bootloader screen for the M8 shows:
*** Software status Official ***
*** LOCKED ***
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.29.214500021.12G
OpenDSP-v51.2.2-00593-M8974_F0.1015
OS-6.12.401.4
eMMC-boot 2048MDec 17 2015,14:15:48.0
And the M9 shows:
hTC download mode
*** UNLOCKED ***
htc_himauhl PVT S-ON
LK-1.0.0.0000
RADIO-01.01_U11440792_97.00.51203G_F
OpenDSP-15.6.1.00522.8994_1026
OS-3.35.401.12
Dec 16 2015,15:37:25(671758)
Now, what confuses me, is the jargon been thrown about in the forums - supercid, twrp, firmware, rom, recovery, fastboot, ruu, s-on, s-off, stock, custom, root....etc. I have an idea of what these terms may mean, but i want to be 100% certain.
So, my question is, can someone provide me with laymans instructions (or point me in the right direction), on how i can get the phones back to UK factory default state so they work again please. Even basic instructions and i will do all the research.
What do i need to download, and where do i download too, do i need to use SD card, which program to install UK software with............etc. I have seen many instructions, but there doesn't seem to be an accompanying explanation as to what these files or programs do.
Finally, please excuse me for the long boring (probably tedious) explanation.
Any help would be greatly appreciated.
bashme said:
The Bootloader screen for the M8 shows:
*** Software status Official ***
*** LOCKED ***
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.29.214500021.12G
OpenDSP-v51.2.2-00593-M8974_F0.1015
OS-6.12.401.4
eMMC-boot 2048MDec 17 2015,14:15:48.0
Click to expand...
Click to collapse
Skip the relocking part ...
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
bashme said:
May be i should've posted in the M9 forum too??
Click to expand...
Click to collapse
That is what I would suggest (discuss only the M8 in this tread; and make a separate thread in the M9 forum section, only discussing the M9). Its going to confuse the issue, discussing both phones in the same thread.
The M9 is a completely different piece of hardware, so its best not to lump it together in the same conversation.
You'll find a lot more folks in the M9 forum, with specific knowledge of that device. Folks on this forum section will know about the M8, but may or may not know anything about the M9 (I sure don't).
Hello.
Thank you for your response.
OK so these are the steps i have followed for the HTC One M8. Please let me know if they are correct.
1. I already have Android SDK on my windows pc.
2. I downloaded and install htc sync manager.
3. I downloaded RUU file from this link: https://www.androidfilehost.com/?fid=24369303960687057
0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip
4. I downloaded htc_fastboot.exe from this link: https://drive.google.com/file/d/0B8L...dKVEdHX1U/view
5. Copied the two downloaded files into the platform-tools folder of my android sdk.
6. I renamed 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip
to RUU.zip
7. I opened command window here and typed the following:
fastboot reboot-bootloader (reboot to bootloader to ensure the connection is good)
fastboot oem rebootRUU (put the device in RUU mode)
htc_fastboot flash zip RUU.zip (to install RUU)
First command is a success
Second command is a success
Third command fails with following output:
fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.013s]
finished. total time: 0.014s
fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.038s]
finished. total time: 0.039s
htc_fastboot flash zip RUU.zip
sending 'zip'... (53965 KB) OKAY
sending time = 3.039 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) total_image_number=8
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
(bootloader) current_image_number=1
(bootloader) current_image_number=2
(bootloader) current_image_number=3
(bootloader) current_image_number=4
(bootloader) current_image_number=5
(bootloader) current_image_number=6
(bootloader) current_image_number=7
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
For "hboot-preupdate" response, restart the same procedure for device SH4BJWM03231...
Then it automatically starts this command, but does not do anything:
sending 'zip'... (53965 KB)
Not sure what to do now!
Thanks very much.
@redpoint73
OK, sorry about this. I guess i should've known.
I will post my problem with the HTC One M9 on the M9 forum.
Cheers for that.
ckpv5 said:
Skip the relocking part ...
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Click to expand...
Click to collapse
Unfortunately it has failed to flash the RUU (see my previous post).
Also, here is the getvar information
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.864s
Please can you help?
bashme said:
2. I downloaded and install htc sync manager.
Click to expand...
Click to collapse
Did you follow the instruction correctly ?
HTC USB drivers - Install HTC Sync Manager - http://www.htc.com/us/support/softwa...c-manager.aspx
- it will install the needed drivers then uninstall the HTC Sync Manager but leave the drivers.
There are 3 different method to install RUU zip - read and pick one and try again.
http://forum.xda-developers.com/showpost.php?p=67314040&postcount=1749
ckpv5 said:
Did you follow the instruction correctly ?
HTC USB drivers - Install HTC Sync Manager - http://www.htc.com/us/support/softwa...c-manager.aspx
- it will install the needed drivers then uninstall the HTC Sync Manager but leave the drivers.
There are 3 different method to install RUU zip - read and pick one and try again.
http://forum.xda-developers.com/showpost.php?p=67314040&postcount=1749
Click to expand...
Click to collapse
Yes i installed HTC Sync Manager. Do i need to uninstall it? Or can it stay on the PC without causing any problems for flashing RUU??
OK, i will try a different method.
Will post update.
Thank you.
bashme said:
Yes i installed HTC Sync Manager. Do i need to uninstall it? Or can it stay on the PC without causing any problems for flashing RUU??
OK, i will try a different method.
Will post update.
Thank you.
Click to expand...
Click to collapse
..
ckpv5 said:
Did you follow the instruction correctly ?
HTC USB drivers - Install HTC Sync Manager - http://www.htc.com/us/support/softwa...c-manager.aspx
- it will install the needed drivers then uninstall the HTC Sync Manager but leave the drivers.
There are 3 different method to install RUU zip - read and pick one and try again.
http://forum.xda-developers.com/showpost.php?p=67314040&postcount=1749
Click to expand...
Click to collapse
Worked at last!
Thank you very much, really appreciate it. You are a star!
Just one question, is it the same process for the HTC One M9? (of course the RUU will be different)
I am heading over to the M9 forum now.
Thanks again.
bashme said:
Worked at last!
Thank you very much, really appreciate it. You are a star!
Just one question, is it the same process for the HTC One M9? (of course the RUU will be different)
I am heading over to the M9 forum now.
Thanks again.
Click to expand...
Click to collapse
It's best to ask there. The microSD & ARUWizard methods will be different.
The htc_fastboot flash same process but you may need htc_fastboot for M9.
I don't get it. Your bootloader says that the software status is official (which means no modification) but for some reason your phone had gone into a bootloop. I would like to learn more about Android and help this community can anyone tell me why this happens?
justinchao740 said:
I don't get it. Your bootloader says that the software status is official (which means no modification) but for some reason your phone had gone into a bootloop. I would like to learn more about Android and help this community can anyone tell me why this happens?
Click to expand...
Click to collapse
that's happened for some people now anyone receive the latest OS by OTA have this issue it solved by flashing RUU
I believe it's something conflicting in the system after OTA
Sent from my HTC M8 using XDA Labs
Previously, i successfully managed to flash my M8, great.
Unfortunately i did not put my sim in the M8, as i needed to copy contacts from my sim (i shouldn't have saved on sim ;-/ ) and wanted to get my M9 sorted too.
Anyway, today i put in my sim EE UK into the M8 and it cannot get a network connection. In fact I tried other UK sims too (VF UK, O2 UK, Three UK) and none were able to connect to their respective networks.
One other thing i noticed when i dialled *#*#4363#*#* and selected Phone information, is that Set preferred network type shows WCDMA. I changed this to GSM/WCDMA/LTE, but after a restart, again it showed WCDMA.
Can someone make any sense of this please?
:-/