Related
Hi, I am trying to S-ON my HTC Sensation again.
I have run a stock ruu.exe, and changed the hboot to 1.27.0000
The device is unrooted by that if I am right.
If I follow step 5 from this thread ( http://forum.xda-developers.com/showthread.php?t=1192300 ) via the fastboot oem writesecureflag 3 way, when the bootloader reloads, it stays S-OFF
I have tried a lot, and I hope somebody knows whats wrong.
C:\android-sdk-windows\platform-tools>fastboot oem writesecureflag 3
... OKAY
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader... OKAY
It says Locked
PYRAMID PVT SHIP S-OFF RL
I have now tried another RUU.exe and tried another way by getting rom.zip and making this PG58IMG.zip, but it still won't S-ON
HBOOT- 1.17.0008
RADIO- 10.11.9007.15_M
eMMC-boot
it doesn't say LOCKED anymore <- is that a problem?
please help me!!! anyone..
rickolie said:
Hi, I am trying to S-ON my HTC Sensation again.
I have run a stock ruu.exe, and changed the hboot to 1.27.0000
The device is unrooted by that if I am right.
If I follow step 5 from this thread ( http://forum.xda-developers.com/showthread.php?t=1192300 ) via the fastboot oem writesecureflag 3 way, when the bootloader reloads, it stays S-OFF
I have tried a lot, and I hope somebody knows whats wrong.
C:\android-sdk-windows\platform-tools>fastboot oem writesecureflag 3
... OKAY
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader... OKAY
It says Locked
PYRAMID PVT SHIP S-OFF RL
I have now tried another RUU.exe and tried another way by getting rom.zip and making this PG58IMG.zip, but it still won't S-ON
HBOOT- 1.17.0008
RADIO- 10.11.9007.15_M
eMMC-boot
it doesn't say LOCKED anymore <- is that a problem?
please help me!!! anyone..
Click to expand...
Click to collapse
Check the cid.. If it is supercid then SON command might not work
So change back to original cid of the phone
Then try SON
Another thing is.. The locked/unlocked status is available from 1.18 hboot only so it normal that 1.17 hboot doesn't show anything
Sent from my HTC Sensation using xda premium
ganeshp said:
Check the cid.. If it is supercid then SON command might not work
So change back to original cid of the phone
Then try SON
Another thing is.. The locked/unlocked status is available from 1.18 hboot only so it normal that 1.17 hboot doesn't show anything
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Tnx for replying
I am trying to get the stock cid, I have found my MID is PG5813000 (Fastboot getvar MID), and that means that my cid is VODAPE17?
I have vodafone and I am from the netherlands so I think it should be that one.
When I use fastboot oem writecid VODAPE17 this comes up:
...
(bootloader) Start Verify: -1
(bootloader) erase sector 65504 ~ 65535 (32)
OKAY [ 1.559s ]
finished total time: 1.564s
fastboot getvar cid
cid: 11111111
finished. total time: 0.019s
I have also installed the app CID getter, it said I had HTC__E11, when i tried to write it I got the same error
I can't find any solutions, help again pls
rickolie said:
Tnx for replying
I am trying to get the stock cid, I have found my MID is PG5813000 (Fastboot getvar MID), and that means that my cid is VODAPE17?
I have vodafone and I am from the netherlands so I think it should be that one.
When I use fastboot oem writecid VODAPE17 this comes up:
...
(bootloader) Start Verify: -1
(bootloader) erase sector 65504 ~ 65535 (32)
OKAY [ 1.559s ]
finished total time: 1.564s
fastboot getvar cid
cid: 11111111
finished. total time: 0.019s
I have also installed the app CID getter, it said I had HTC__E11, when i tried to write it I got the same error
I can't find any solutions, help again pls
Click to expand...
Click to collapse
is the phone locked to vodafone netherlands ? then the cid you mentioned is fine
but the RUU cid is saying its HTC_E11 so try that ...
also after changing the cid
do a fastboot reboot-bootloader then verify the cid ..it should change
EDIT: earlier cid change worked fine (check it now it will change )..btw make sure that RUU cid and the cid you are giving is fine and proper one ..then only do SON
ganeshp said:
is the phone locked to vodafone netherlands ? then the cid you mentioned is fine
but the RUU cid is saying its HTC_E11 so try that ...
also after changing the cid
do a fastboot reboot-bootloader then verify the cid ..it should change
EDIT: earlier cid change worked fine (check it now it will change )..btw make sure that RUU cid and the cid you are giving is fine and proper one ..then only do SON
Click to expand...
Click to collapse
That doesn't work like I allready said, after trying numorous times it still won't doesn't change.
or is there a code to verify a cid? because I can't find any.
rickolie said:
That doesn't work like I allready said, after trying numorous times it still won't doesn't change.
or is there a code to verify a cid? because I can't find any.
Click to expand...
Click to collapse
fastboot oem readcid
and
fastboot getvar cid
should give you your cid
try
fastboot oem writecid HTC__E11
then
fastboot reboot-bootloader
then
faatboot getvar cid
ganeshp said:
fastboot oem readcid
and
fastboot getvar cid
should give you your cid
try
fastboot oem writecid HTC__E11
then
fastboot reboot-bootloader
then
faatboot getvar cid
Click to expand...
Click to collapse
That is what i am doing, won't work
look at the image I added
rickolie said:
That is what i am doing, won't work
look at the image I added
Click to expand...
Click to collapse
Flash a gb ruu and try cid change again... Looks like mmcblk6,7 partitions got corrupted
Edit: wait are you on 1.17 hboot now?
Then go back to the ics ruu and change the cid
Sent from my HTC Sensation using xda premium
ganeshp said:
Flash a gb ruu and try cid change again... Looks like mmcblk6,7 partitions got corrupted
Edit: wait are you on 1.17 hboot now?
Then go back to the ics ruu and change the cid
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Done that, now on hboot 1.27.0000 again, but the same error as in the image.
after I writecid HTC__E11 , and than readcid, I get HTC__E11, but when I reboot and than readcid again it is changed to 11111111
ganeshp said:
Flash a gb ruu and try cid change again... Looks like mmcblk6,7 partitions got corrupted
Edit: wait are you on 1.17 hboot now?
Then go back to the ics ruu and change the cid
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
What should I do now?, please help me,
I'm trying this for weeks now, and would be very happy if it worked
rickolie said:
What should I do now?, please help me,
I'm trying this for weeks now, and would be very happy if it worked
Click to expand...
Click to collapse
there is a work around ..but for that you need to root your device again ..install busybox (ginger bread or ics both will do )
then give me the outputs of these terminal commands
(if using terminal emulator app from phone )inside shell:
su
strings -n 8 /dev/block/mmcblk0p4
and
strings -n 8 /dev/block/mmcblk0p5
also verify what the CID in this output
strings -n 8 /dev/block/mmcblk0p6
terminal outputs
ganeshp said:
there is a work around ..but for that you need to root your device again ..install busybox (ginger bread or ics both will do )
then give me the outputs of these terminal commands
(if using terminal emulator app from phone )inside shell:
su
strings -n 8 /dev/block/mmcblk0p4
and
strings -n 8 /dev/block/mmcblk0p5
also verify what the CID in this output
strings -n 8 /dev/block/mmcblk0p6
Click to expand...
Click to collapse
I have rooted again, and installed busybox, and installed the terminal app.
When I type the codes excactly like you say, I get no output? can you show me how to get output?, I just hit enter:silly:
rickolie said:
I have rooted again, and installed busybox, and installed the terminal app.
When I type the codes excactly like you say, I get no output? can you show me how to get output?, I just hit enter:silly:
Click to expand...
Click to collapse
That's all I wanted.. It supposed to give you certain output... It should technically give you IMEI and cid as output..
Can you verify your Imei it might have changed by now
Sent from my HTC Sensation using xda premium
ganeshp said:
That's all I wanted.. It supposed to give you certain output... It should technically give you IMEI and cid as output..
Can you verify your Imei it might have changed by now
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Here is my IMEI: 355195000000017
just got it by dialing *#06#
rickolie said:
Here is my IMEI: 355195000000017
just got it by dialing *#06#
Click to expand...
Click to collapse
Now I'm 100% sure that... The Imei has changed.. Verify the Imei with the one present on the original box.. I can help you in rectifying it.. But I need the actual Imei first
Sent from my HTC Sensation using xda premium
ganeshp said:
Now I'm 100% sure that... The Imei has changed.. Verify the Imei with the one present on the original box.. I can help you in rectifying it.. But I need the actual Imei first
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
The one on the box says: 205442641317453
rickolie said:
The one on the box says: 3*************************7
Click to expand...
Click to collapse
Edit the Imei here.. And PM me the actual Imei and cid you want to change again again.. I'm out of station now... So 48 hrs from now i will send you detailed instructions as to what to do
Sent from my HTC Sensation using xda premium
back?
ganeshp said:
Edit the Imei here.. And PM me the actual Imei and cid you want to change again again.. I'm out of station now... So 48 hrs from now i will send you detailed instructions as to what to do
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
I have send you my IMIE, can you send me the instructions?
rickolie said:
I have send you my IMIE, can you send me the instructions?
Click to expand...
Click to collapse
Ok ill send you a PM in an hour
Sent from my HTC Sensation using xda premium
rickolie said:
I have send you my IMIE, can you send me the instructions?
Click to expand...
Click to collapse
Done check your PM
OK, so, I really didn't want to ask, because I feel like this has probably already been covered, but I have searched and haven't found anything, and now I am stuck, so ask I shall. Anyway, I have a Rogers One X, and I want to get S-OFF. Now, in the S-OFF thread, it says I need supercid. So, I checked the cid on my phone, and it is ROGER001, not the 11111111 that I want, right? So, my question now is, how do I get supercid? I have tried the X-Factor exploit, but that didn't help, it failed on the 'adb shell "/data/local/tmp/pwn"' line. I don't want to try flashing the S-OFF without supercid first because it specifically says not to do that in the S-OFF thread. So, that is my problem, any help would be greatly appreciated.
Oh, not sure if it matters, but according to my bootloader, I have HBOOT 1.11.0000.
PS: Side question: What exactly will S-OFF do for me? According to other stuff I have read, I will be able to flash stuff like radios, splash screens and boot.img without using fastboot, but I can already do all that without fastboot, so what is the point of S-OFF?
Thanks in advance!
Re: [Q] S-OFF questions and help, please!
Last page of s-off thread twisteddroid posted the answer to your cid question.
To your other question. You answered it for yourself.
Sent from my HOX w/CM10.1 4.2.2 s-off
Thanks for the quick reply. I just tried what you said, using "fastboot oem writecid 11111111" but it fails with this message:
Code:
(bootloader) elite_init_sd, SD card already power on
(bootloader) sdhw_7xxx_open: id=0
(bootloader) [SD_HW_ERR] SD: No device attached
(bootloader) 902910 902E20
FAILED (status read failed (No such file or directory))
finished. total time: 1.261s
and then the phone freezes up and I have to hard reboot it. When I check the cid again it is still ROGER001. I am doing this all from the bootloader, I am assuming that is correct?
Re: [Q] S-OFF questions and help, please!
Do steps 1-11 here to get supercid. I did this on a rogers and a telus one x no problem.
http://forum.xda-developers.com/showthread.php?t=1671396
Oh and the only benefit to s-off for you is to remove the red text from the splash screen and possible future benefits such as dual booting or free SIM unlock.
Sent from my VENOMized HoxL
@area51avenger: Thanks, that did the job perfectly. Like you said, I only did up to step 11, as I already have an unlocked bootloader, and I am now running an S-OFF CM10.1 HTC One X! Thank you all very much.
Re: [Q] S-OFF questions and help, please!
person66 said:
Thank you very much, area51avenger. That post did the job perfectly. Like you said, I only did up to step 11, as I already have an unlocked bootloader, and I am now running an S-OFF CM10.1 HTC One X! Thank you all very much.
Click to expand...
Click to collapse
There's a thanks button for that
Sent from my VENOMized HoxL
I've just had my Telstra phone replaced due to the screen smashing on the first one.
I rooted through HTC Dev, installed TWRP on it, and flashed CM. Then to my horror realised the touchscreen didn't work.
read back through and found out that the touchscreen doesn't work with CM on 2.14.
I've installed another sense ROM on it, but want to go back to a stock CM.
This is the point I'm reaching confusion, I realise I need to downgrade my hboot - but how do I go about that?
I tried somewhere to gain SuperCID, so that I can get S-OFF ... but I can't seem to get SuperCID to work...
Any suggestions on where to start - or for that matter if there is anything I can do at all even?
You need supercid to s-off. You don't need to downgrade hboot, just your touchscreen firmware.
http://forum.xda-developers.com/showthread.php?t=2159863
You may have to hex-edit your CID after unlocking.
And I need both SuperCID and S-OFF to downgrade the touchscreen firmware though?
Is there another thread with procedures to get SuperCID?
Fastboot oem writecid 11111111
Then
http://forum.xda-developers.com/showthread.php?p=38174259
[S-Off] Facepalm S-Off for HTC One XL
Sent from my HOX w/CM10.1 4.2.2 s-off
subarudroid said:
Fastboot oem writecid 11111111
Click to expand...
Click to collapse
Can he do that without s-off or supercid? I thought that was a restricted command.
http://forum.xda-developers.com/showthread.php?p=38600532
[S-Off] Facepalm S-Off for HTC One XL
Quite a few on the thread.
I've seen this method work several times there. And once personally with a Rogers member with the jb ota that I assisted with this. :sly:
Sent from my HOX w/CM10.1 4.2.2 s-off
subarudroid said:
Fastboot oem writecid 11111111
Then
http://forum.xda-developers.com/showthread.php?p=38174259
[S-Off] Facepalm S-Off for HTC One XL
Sent from my HOX w/CM10.1 4.2.2 s-off
Click to expand...
Click to collapse
./fastboot-mac getvar cid
returns: cid: TELST001
So I'm guessing that didn't work?
subarudroid said:
Fastboot oem writecid 11111111
Then
http://forum.xda-developers.com/showthread.php?p=38174259
[S-Off] Facepalm S-Off for HTC One XL
Sent from my HOX w/CM10.1 4.2.2 s-off
Click to expand...
Click to collapse
Actually what I get from running that command is:
Code:
./fastboot-mac oem writecid 11111111
... INFO elite_init_sd, SD card already power on
INFOsdhw_7xxx_open: id=0
INFO[SD_HW_ERR] SD: No device attached
INFO902910 902E20
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
1) find thread with instructions to hex edit cid . There's a link to this thread earlyish in the soff thread if you can't find it by searching.
2) follow soff instructions in that thread.
3) follow touchscreen downgrade instructions from sticky in original development.
Or simply:
1) research on xda and find all the above yourself
I stupidly took the stock jb update from HTC, so could only use aosp recently after all the above was released.
Dacra said:
1) find thread with instructions to hex edit cid . There's a link to this thread earlyish in the soff thread if you can't find it by searching.
2) follow soff instructions in that thread.
3) follow touchscreen downgrade instructions from sticky in original development.
Or simply:
1) research on xda and find all the above yourself
I stupidly took the stock jb update from HTC, so could only use aosp recently after all the above was released.
Click to expand...
Click to collapse
I found it hard to find a guide for hex editing the CID even though I KNOW one exists, so I just made another one:
http://forum.xda-developers.com/showthread.php?t=2212737
http://forum.xda-developers.com/showthread.php?t=1671396
exad said:
I found it hard to find a guide for hex editing the CID even though I KNOW one exists, so I just made another one:
http://forum.xda-developers.com/showthread.php?t=2212737
Click to expand...
Click to collapse
Dacra said:
http://forum.xda-developers.com/showthread.php?t=1671396
Click to expand...
Click to collapse
Yeah, I found it too after. Didn't search the General Section. Alas, it was too late as I already made another one. Thanks though.......
Some info
C:\Users\e073175\Downloads\HTC_ONE_X\rom>fastboot getvar version-main
version-main: 2.20.502.7
finished. total time: 0.026s
And I have HBOOT-1.14.0002
I show
TAMPERED
RELOCKED
I can not seem to flash back to stock using htc_one_x_RUU_2.20.502.7_att_us_08022012.exe, it fails.
So then I get the rom.zip file from htc_one_x_RUU_2.20.502.7_att_us_08022012.exe and run...
C:\Users\e073175\Downloads\HTC_ONE_X\rom>fastboot flash boot boot_signed.img
sending 'boot' (6156 KB)...
OKAY [ 0.983s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.433s
Im guessing this is because I followed the instructions (to relock the bootloader) before I ran htc_one_x_RUU_2.20.502.7_att_us_08022012.exe
What would you recommend as my next step?
Im following this guide http://forum.xda-developers.com/wik...ashing_a_RUU_to_completely_restore_your_phone
I was able to unlock the bootloader... Now Im stuck here...
C:\Users\e073175\Downloads\HTC_ONE_X\rom>fastboot flash boot boot_signed.img
sending 'boot' (6156 KB)...
OKAY [ 0.981s]
writing 'boot'...
OKAY [ 1.548s]
finished. total time: 2.531s
C:\Users\e073175\Downloads\HTC_ONE_X\rom>fastboot flash system system.img
sending 'system' (1048572 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.016s
"Please note that this method isn't 100% reliable and should be considered a last resort; there have been various reports of this not working due to system.img file being to large."
The error that you are getting seems to be indicative of a known issue. I am sure someone who knows whats up will be along shortly. At least you can take comfort in knowing you are not the only person with this issue. That is when things get scary lol.
Are you s-on or s-off? Do you have SuperCID? I would not use the methods you have chosen to return to stock.
Sent from my Evita
timmaaa said:
Are you s-on or s-off? Do you have SuperCID? I would not use the methods you have chosen to return to stock.
Sent from my Evita
Click to expand...
Click to collapse
I am S-ON and I do not have SuperCID.
LanceM said:
I am S-ON and I do not have SuperCID.
Click to expand...
Click to collapse
fastboot oem readcid
...
(bootloader) cid: HTC__621
OKAY [ 0.010s]
finished. total time: 0.010s
fastboot getvar cid
cid: HTC__621
finished. total time: 0.003s
When I try and flash
1.85 or 1.83
I get this error
<T111504><DEBUG><OUT>FAILED (remote: 42 custom id check fail)</OUT>
You can't RUU backwards unless you're s-off.
Sent from my Evita
timmaaa said:
You can't RUU backwards unless you're s-off.
Sent from my Evita
Click to expand...
Click to collapse
Ok Tim... So what do I do to get 2.20 on the phone, stock...
If you're wanting to run the at&t RUU you'll also need the at&t CID. Otherwise you need to run the RUU that corresponds with the HTC__621 CID. Why is it the 2.20 in particular that you want?
Sent from my Evita
Im not stuck on 2.20. I just want the phone back to stock.
Ok, so then you need to run an RUU that's compatible with the CID you have, and it can't be a backyard update.
Sent from my Evita
timmaaa said:
Ok, so then you need to run an RUU that's compatible with the CID you have, and it can't be a backyard update.
Sent from my Evita
Click to expand...
Click to collapse
Well, that is my question... What RUU is compatible with my CID? And can I change the CID to work for an AT&T RUU, because it seems like 621 is a tawian RUU. If I can, what do I need to change the CID too?
Did you change the CID to HTC__621? It doesn't look like an Evita CID.
Sent from my Evita
timmaaa said:
Did you change the CID to HTC__621? It doesn't look like an Evita CID.
Sent from my Evita
Click to expand...
Click to collapse
No, when I got the phone a while ago, I rooted and superCID'ed it. It was changed to 1111111, but now for some reason it has changed to 621, which I dont quite understand and has caused quite an issue for me trying to go back to stock.
The CID can't just change by itself, that doesn't make any sense. Are you certain that you were successful in getting SuperCID when you rooted the phone?
Sent from my Evita
timmaaa said:
The CID can't just change by itself, that doesn't make any sense. Are you certain that you were successful in getting SuperCID when you rooted the phone?
Sent from my Evita
Click to expand...
Click to collapse
I bought the phone in San Antonio at an AT&T store.... Way back when the phone just came out...
At that point, after XDA had root and SuperCID, I did those... And put CM10 on it... Through many upgrades and tinkering, somehow the phone got the CID 621. An Asian CID, I did NOT do this.
Regardless, it is fixed now. I followed the instructions in this thread to change the CID back to 1111111. It worked, then what I did was push the recovery and boot from 2.20 to the phone, then re-locked it.
At this point, I ran the 2.20 RUU and it took... Then I ran the 3.18 phone and now... QHSUSB_DLOAD
Off to http://forum.xda-developers.com/showthread.php?t=1966850
Now downloading linux...
I will fix this damn thing lol!
You pulled a classic megadoug. S on super Cid ruu strikes again. JTAG is the only way to fix it now
Sent from my HTC One XL
Yep. S-on + SuperCID + jb RUU = brick. So you'll need a jtag repair. It's worth tying the unbrick method but nine times out of ten it doesn't work.
Sent from my Evita
UPDATE: Phone is in QHSUSB_DLOAD mode. I've tried HTC Unbricking Project but it didn't detect my phone. Also I've tired the Ultimate Recovery tool Unbrick and it also didn't help.
I guess the only solution is JTAG / New phone.
Hello,
I think I'm in a real big trouble.
background story:
I was on ARHD 7.3, S-off, Firmware 3.33 Uni. Suddenly after about a month of use, phone started to lose signal. I could recover the signal only with a reboot (hidden menu options and airplane mode didn't help).
I thought it was a problem with the ROM so I've installed an Official RUU RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.33.401.153 after installing 3.33.401.x firmware. This didn't solve the problem I had, signal still was going off few times a day and each time I had to reboot. Furthermore, I've lost my IMEI Number, I got a new IMEI number 355195000000017 which I googled and found more people with that number. However the IMEI change didn't interrupt anything.
Realizing that RUU didn't help I've decided to go back to Mike's ROM ARHD 7.3. (after unlocking bootloader again and etc..)
Then the problem started:
com.google.process.gapps and acore.process.android and basically all the phone started to crash. Nothing helped, I've tried to reflash ROM, reflash Google Package, Nothing. Suddenly, the phone was bricked. won't charge, won't boot.
However a very strange thing happened. Suddenly I could boot Into HBOOT (maybe the phone didn't had enough battery power before).
But the HBOOT was getting stuck, I couldn't do anything So I've used the Ultimate Recovery Tool and downgraded my HBOOT. (http://forum.xda-developers.com/showthread.php?t=1653777)
The Problem now:
1. I can go to 4EXT recovery but it won't let me flash any ROM, installing is aborted.
2. HBOOT won't let me flash any recovery, boot, etc saying permission denined.
3. Rebooting bootloader doesn't work, it goes just to a black screen with backlight on.
4. I've tried to change firmware with PG58IMG it won't update saying hboot partition update failed failed-pu
5.I've tried to install the previous RUU @fastboot but it says battery power below 30%. I've checked the voltage it was around 3800~ and in the recovery it had like 50% so I don;t think problem lies here.
Information about HBOOT:
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.49.0007 <--- Bad Bad HBOOT, I know I did a mistake here. This Hboot is for Evo 3D GSM.
RADIO-11.24.3504.31_M
OPENDSP- BLAH BLAH BLAH
eMMC-boot
I don't think I have SuperCID. when I type the command fastboot getvar cid and getvar all I see the CID number is 0418.
However, when I type fastboot oem readcid I get 11111111.
I've tried to change to superCID but again, permission denined.
I'm thinking maybe if I could somehow change the superCID then I could update the firmware and then I could run the RUU?
Or can I somehow via linux box flash a different HBOOT?
Thank everyone who read this long story
I would be truly grateful for anyone who tries to help me.
EDIT: Phone Info:
[email protected]:~# ./fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.49.0007
INFOversion-baseband: N/A
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 0.33.401.106
INFOserialno: SH19XV803513
INFOimei: 355195000000010
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG58*****
INFOcidnum: 0418
INFObattery-status: good
INFObattery-voltage: 4000mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: edba812f
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
Click to expand...
Click to collapse
[email protected]:~# fastboot oem readcid
... INFOcid: 11111111
OKAY
Click to expand...
Click to collapse
failed-pu
man is a serious problem AFAIK
did you try to reflash ruu.exe or install 3.33 universal firmware again?
did they show you failed-pu again?
edit: what hboot version is that?
edit 2: why did you use a tool from htc evo 3D forum?
since you are on S-OFF and supercid you could use any ruu.exe you wanted including GB's one
that would take care also of your hboot version(gingerbread ruu->hboot downgrade)
Thanks for your reply,
rzr86 said:
failed-pu
man is a serious problem AFAIK
did you try to reflash ruu.exe or install 3.33 universal firmware again?
did they show you failed-pu again?
Click to expand...
Click to collapse
Yes, Flashing RUU still giving me the below 30% battery (I've charged all night).
And Installing Firmware 3.33 gives me fail-pu
rzr86 said:
edit: what hboot version is that?
edit 2: why did you use a tool from htc evo 3D forum?
since you are on S-OFF and supercid you could use any ruu.exe you wanted including GB's one
that would take care also of your hboot version(gingerbread ruu->hboot downgrade)
Click to expand...
Click to collapse
Idk, I saw ultimate Recovery tool, thought it would help since nothing worked..
I do have S-Off but I don't have SuperCID (my CID num is very strange only 4 digits now).
Romansko said:
Thanks for your reply,
Yes, Flashing RUU still giving me the below 30% battery (I've charged all night).
And Installing Firmware 3.33 gives me fail-pu
Idk, I saw ultimate Recovery tool, thought it would help since nothing worked..
I do have S-Off but I don't have SuperCID (my CID num is very strange only 4 digits now).
Click to expand...
Click to collapse
try to change your cid again
fastboot oem writecid 11111111
fastboot reboot bootloader
fatsboot getvar cid
Failed-PU
rzr86 said:
try to change your cid again
fastboot oem writecid 11111111
fastboot reboot bootloader
fatsboot getvar cid
Click to expand...
Click to collapse
I've tried that already but it didn't work.
./fastboot oem writecid 11111111
... INFOStart Verify: -1
INFOerase sector 65504 ~ 65535 (32)
INFOemmc_erase(1852): sd_write_sector failed!
OKAY
Romansko said:
I've tried that already but it didn't work.
./fastboot oem writecid 11111111
... INFOStart Verify: -1
INFOerase sector 65504 ~ 65535 (32)
INFOemmc_erase(1852): sd_write_sector failed!
OKAY
Click to expand...
Click to collapse
i don't know what else to suggest man
only ganeshp can help you with that
he has more experience about F-PU
the only thing i can tell you is go for jtag
rzr86 said:
i don't know what else to suggest man
only ganeshp can help you with that
he has more experience about F-PU
the only thing i can tell you is go for jtag
Click to expand...
Click to collapse
Thanks for trying! My phone doesn't boot or charge at all now. I guess JTAG it is.
Romansko said:
Thanks for trying! My phone doesn't boot or charge at all now. I guess JTAG it is.
Click to expand...
Click to collapse
give a try with unbricking project
http://forum.xda-developers.com/showthread.php?t=1522351
rzr86 said:
give a try with unbricking project
http://forum.xda-developers.com/showthread.php?t=1522351
Click to expand...
Click to collapse
I did. My phone's in a QHSUSB_DLOAD mode but it doesn't get detected by the Unbricked project script. I saw other people had the same problem and Dexter advised them to JTAG.
Romansko said:
I did. My phone's in a QHSUSB_DLOAD mode but it doesn't get detected by the Unbricked project script. I saw other people had the same problem and Dexter advised them to JTAG.
Click to expand...
Click to collapse
if dexter advised it then go for it