Tweet
Do we need to use the riffbox ?
-
-
thanksComment
-
How about phone that is not detected by PC ?
I have read all through 25 pages of this thread, but cant find how to revive dead boot phone.
I tried to unlock this phone by usb cable (with another software) but it kept showing reading . . . endlessly, so I cancelled and disconnected.
Later when I restarted the phone it could not power on any more - DEAD.
The area I was is where I clicked on Read Unlock code.
There was no error, only that I clicked cancel and disconnect when it wasnt reading anything for a very long time.
And now I just noticed the PC is not detecting the phone any longer. No Boot mode, No Bricked mode, noting. JUST DEAD
Any ideas?Comment
-
Just for to know ...how you have thinked of Unlock this One X (Tegra Chipset)????
Change Battery for first thing!!!!Last edited by Ripgsm; 09-23-2015, 06:49 PM.Comment
-
But on the software I used (LgTool), HTC One X is clearly supported. And I followed the process.
Though it did not unlock, but I didnt get any error!!!
I will try to charge battery outside (as I dont have another battery for now.Comment
-
Hi, how first thing you are in Wrong Thread if you device is TOTALLY DEAD.Originally posted by dannyogolo View Post
For this i suggest how first thing of Replace with New battery.
Other IMPORTANT Thing...you are Totally WRONG if want Unlock ONE X (Tegra Chipset) With LG TOOL, this is the result.
If you will have unlocked ONLY will have charged in Payed Server and Unlocked....other thing is S-OFF + SUPERCID, only SUPPORTED By "JAVA CARD" or "XTC2CLIP" so for me you not have nothing of clear after have read 25 pages...need other 50 pages for unbderstand when one Phone is SW BRICKED or HW DEAD.
All clear now?..i hope of yes, so no waste more time here if FIRST not try replacing Battery (Full Charged), and see if the PC recognize this in APX mode or in other mode.
It's all.Comment
-
is this unbrick htc one x ?Comment
-
C:\adb>nvflash --blob blob.bin --bct flash_enc.bct --setbct --odmdata 0x40080105 --configfile flash_32g.cfg --create --bl hboot_enc.img --go
Nvflash v1.2.57794 started
Using blob v1.1.57813 Files~Í·²n«
rcm version 0X30001
System Information:
chip name: unknown
chip id: 0x30 major: 1 minor: 3
chip sku: 0x81
chip uid: 0x015d25783b242206
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: flash_enc.bct
- 6128/6128 bytes sent
flash_enc.bct sent successfully
odm data: 0x40080105
downloading bootloader -- load address: 0x80108000 entry point: 0x80108000
sending file: hboot_enc.img
- 2097168/2097168 bytes sent
hboot_enc.img sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: DIA
creating partition: BIF
creating partition: GP1
creating partition: WLN
creating partition: WDM
creating partition: RCA
creating partition: LNX
creating partition: SOS
creating partition: PG1
creating partition: PG2
creating partition: PG3
creating partition: SIF
creating partition: SP1
creating partition: RV1
creating partition: APP
creating partition: CAC
creating partition: ISD
creating partition: UDA
creating partition: DUM
creating partition: MSC
creating partition: RFS
creating partition: DLG
creating partition: PDT
creating partition: GPT
failed executing command 13 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) message: nverror:0x8 (0x9) flags: 0
how can i fix this error ?Comment
-
update
managed to flash this by adding an extracted sys from an ruu rom i got this ...
C:\RD_release(with_sbk)without sis>nvflash --blob blob.bin --bct flash_enc.bct --setbct --odmdata 0x40080105 --configfile flash_32g.cfg --create --bl hboot_enc.img --go
Nvflash v1.2.57794 started
Using blob v1.1.57813nProgreÕ=Ù'¥
rcm version 0X30001
System Information:
chip name: unknown
chip id: 0x30 major: 1 minor: 3
chip sku: 0x81
chip uid: 0x015d25783b242206
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: flash_enc.bct
- 6128/6128 bytes sent
flash_enc.bct sent successfully
odm data: 0x40080105
downloading bootloader -- load address: 0x80108000 entry point: 0x80108000
sending file: hboot_enc.img
- 2097168/2097168 bytes sent
hboot_enc.img sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: DIA
creating partition: BIF
creating partition: GP1
creating partition: WLN
creating partition: WDM
creating partition: RCA
creating partition: LNX
creating partition: SOS
creating partition: PG1
creating partition: PG2
creating partition: PG3
creating partition: SIF
creating partition: SP1
creating partition: RV1
creating partition: APP
creating partition: CAC
creating partition: ISD
creating partition: UDA
creating partition: DUM
creating partition: MSC
creating partition: RFS
creating partition: DLG
creating partition: PDT
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 DIA please wait.. done!
Formatting partition 6 BIF please wait.. done!
Formatting partition 7 GP1 please wait.. done!
Formatting partition 8 WLN please wait.. done!
Formatting partition 9 WDM please wait.. done!
Formatting partition 10 RCA please wait.. done!
Formatting partition 11 LNX please wait.. done!
Formatting partition 12 SOS please wait.. done!
Formatting partition 13 PG1 please wait.. done!
Formatting partition 14 PG2 please wait.. done!
Formatting partition 15 PG3 please wait.. done!
Formatting partition 16 SIF please wait.. done!
Formatting partition 17 SP1 please wait.. done!
Formatting partition 18 RV1 please wait.. done!
Formatting partition 19 APP please wait.. done!
Formatting partition 20 CAC please wait.. done!
Formatting partition 21 ISD please wait.. done!
Formatting partition 22 UDA please wait.. done!
Formatting partition 23 DUM please wait.. done!
Formatting partition 24 MSC please wait.. done!
Formatting partition 25 RFS please wait.. done!
Formatting partition 26 DLG please wait.. done!
Formatting partition 27 PDT please wait.. done!
Formatting partition 28 GPT please wait.. done!
done!
sending file: hboot_enc.img
- 2097168/2097168 bytes sent
hboot_enc.img sent successfully
sending file: board_info.bin
- 20/20 bytes sent
board_info.bin sent successfully
sending file: WDM.img
/ 262144/262144 bytes sent
WDM.img sent successfully
sending file: boot.img
/ 4417536/4417536 bytes sent
boot.img sent successfully
sending file: recovery.img
/ 5974016/5974016 bytes sent
recovery.img sent successfully
sending file: SIF.img
- 6144/6144 bytes sent
SIF.img sent successfully
sending file: system.img
- 1013466364/1013466364 bytes sent
system.img sent successfully
sending file: userdata.img
\ 44118872/44118872 bytes sent
userdata.img sent successfully
C:\RD_release(with_sbk)without sis>pause
Appuyez sur une touche pour continuer...
but still in the same situation the phone still not booting ... flash it for the second time and nothing new could not revive the phone
any help please ?Comment
-
goooooooood sir thanksComment
-
You have done good thing,Originally posted by strongmen View Post
this:
becouse the Script is w/o SYS.img.extracted sys from an ruu rom
Procedure seem coming good, but wht ADB drivers are you using and what show in "Device Manager" first of Launch Adb Command?, can post Photo of "Device manager"?
Last question, (answer and see if can help you), first time this One X was showing "APX MODE" and you have given the Drivers?
Use these Adb file and Sys.img that Match with you Cid that had first of Brick, example HTC_001 itc...
Here ADB good:Comment
-
Hi,
got a HOX in APX and when trying to use nvflash i get "unable to retrieve platform info NvError 0x120002", like some other people in this thread.
Has anyone been able to resolve this error yet or can at least tell me a little more about this error?
Thanks in advanceLast edited by Atsuraelu; 10-11-2015, 01:06 PM.Comment
-
@Atsuraelu,
have only one post above one user that has discovery one Important TIP and do this question?....not worry not are tired if read only one above post.Comment
-
update
stuck in apx mode so after installing drivers i see only :
NVIDIA USB boot-recovery driver for mobile devices ( i will upload a pic in the next post ).
from the day that i stuck in apx mode until now lost access to adb functions or fastboot cant run any command ...pc not detecting any adb device.
note: after flashing over and over using nvflash tool sometimes pc not detect the device at all just like the phone is totally dead ... so what i did is putting the phone in the freezer for 2-3min then plug it in to the pc i shows as htc device + adb and red solid led comes but just for 4sec than disconnect and reconnect as NVIDIA USB boot-recovery driver for mobile devices (by it self means not unplug )...so i can flasj agin using nvflash tool.
is there any command or step i am missing ?
what should i try more ?Comment
-
@Ripgsm:
Not sure if you meant that, but I did add a system.img from a RUU.
The Problem seems to be some sort of communications error between nvflash and the device, so it does not even get to the point, where the imgs would be relevant (or am I missing something).Comment
Comment