Hi all. Today I did on my HTC Flyer S-ON.
to get S-ON you need:Only these numbers CID
============================================================
HTC__001,HTC__E11,HTC__N34,HTC__203,HTC__102,HTC__405,HTC__Y13,HTC__A07,HTC__304,HTC__032,HTC__016,HTC__054
============================================================
1) unpack the archive file and put it on sdcard
2)reboot into recovery
3)In cmd run the following commands (after each command press enter):
adb devices
adb shell
su (do not enter if Flyer ROOTED)
4))backup your alpharev hboot dd if=/dev/block/platform/msm_sdcc.2/mmcblk0p18 of=/sdcard/backup.img
5) flash new hboot dd if=/sdcard/hboot_1.11.0003.nb0 of=/dev/block/platform/msm_sdcc.2/mmcblk0p18
reboot to hboot and check your hboot version it must be something like this
***LOCKED***
then install the firmware version 2.23.405.3
Use HBOOT _-_ - _.nb0 of firmware for your region instead hboot_1.11.0003.nb0, and use your firmware.
sorry my English
Why is this restriction on cid??? my cid is HTC__048
How to extract nb0 from RUU???
krish.gh said:
Why is this restriction on cid??? my cid is HTC__048
Click to expand...
Click to collapse
this hboot from 2.23.405.3 rom...
Use HBOOT _-_ - _.nb0 of firmware for your region instead hboot_1.11.0003.nb0, and use your firmware.
use your firmware, unplug your Flyer from your computer and then double click to run. Somewhere buried in your user account folder will be the image file. In my case, it was buried in C:\Documents and Settings\PeeCee\Local Settings\Temp\{0E03141E-27B1-4E3A-B9B9-18DA9C1FCBEC}\{50F2F878-636A-496F-A7CB-544C067E0C4B}ROM.zip
copy and replace , then extact hboot_######.nb0 and use instead hboot_1.11.0003.nb0 ....after run updateinstaler from PC
sorry my English
thanks dude..it worked for me...back to S-ON...
piramida13 said:
Hi all. Today I did on my HTC Flyer S-ON.
to get S-ON you need:Only these numbers CID
============================================================
HTC__001,HTC__E11,HTC__N34,HTC__203,HTC__102,HTC__405,HTC__Y13,HTC__A07,HTC__304,HTC__032,HTC__016,HTC__054
============================================================
1) unpack the archive file and put it on sdcard
2)reboot into recovery
3)In cmd run the following commands (after each command press enter):
adb devices
adb shell
su (do not enter if Flyer ROOTED)
4))backup your alpharev hboot dd if=/dev/block/platform/msm_sdcc.2/mmcblk0p18 of=/sdcard/backup.img
5) flash new hboot dd if=/sdcard/hboot_1.11.0003.nb0 of=/dev/block/platform/msm_sdcc.2/mmcblk0p
18
reboot to hboot and check your hboot version it must be something like this
***LOCKED***
then install the firmware version 2.23.405.3
Use HBOOT _-_ - _.nb0 of firmware for your region instead hboot_1.11.0003.nb0, and use your firmware.
sorry my English
Click to expand...
Click to collapse
....which means, we can flash the HC stock without a problem, isn't it?
ovigt71 said:
....which means, we can flash the HC stock without a problem, isn't it?
Click to expand...
Click to collapse
No, you need à custom recovery
geek78 said:
No, you need à custom recovery
Click to expand...
Click to collapse
no, I mean, I was supposed to run the RUU posted by Paul, which is executable ...
I install HC from this instruction........
downloaded in the form of rum RUU utility
extracted from the utility rom.zip (start the installation RUU, after the first dialog box, click the "Start" menu in the search bar write% TEMP%, go into the resulting folder, find the two folders format {492B38D3-5B64-491D-8FC3-C45D5808841F} corresponding time running RUU, in one of these folders will rom.zip copy in any directory)
extracted from the file rom.zip hboot_1.11.0006.nb0 copied this file to your memory card
device connected to the computer and proceeded to install RUU_Flyer_HC_S_HTC_WWE_3.10.405.1 (so my CID HTC_A07 installation was successful, almost)
loaded machine in a mode rekaveri (if installing rekaveri changed and go to he can not set it as a separate file from the PG41IMG)
introduced in adb the following command (after each command press enter)
adb devices
adb shell
dd if = / sdcard/hboot_1.11.0006.nb0 of = / dev/block/platform/msm_sdcc.2/mmcblk0p18 flash new bootloader
Reboot. likely to be compromised and will not be able to go download. This is normal.
Connect with flyer FastBoot regime.
Visit htcdev.com and select "Unlock Bootloader". Do not pay attention to the supported device list.
Registration and further unlocking procedure.
reboot and use RUU_Flyer_HC_S_HTC_WWE_3.10.405.1
soory my Enlish
i got theese errors
~ # dd if=/dev/block/platform/msm_sdcc.2/mmcblk0p18 of=/sdcard/backup.img
dd if=/dev/block/platform/msm_sdcc.2/mmcblk0p18 of=/sdcard/backup.img
2048+0 records in
2048+0 records out
1048576 bytes (1.0MB) copied, 0.058380 seconds, 17.1MB/s
~ # dd if=/sdcard/hboot_1.11.0003.nb0 of=/dev/block/platform/msm_sdcc.2/mmcblk0p
18
dd if=/sdcard/hboot_1.11.0003.nb0 of=/dev/block/platform/msm_sdcc.2/mmcblk0p
18
dd: can't open '/sdcard/hboot_1.11.0003.nb0': No such file or directory
what can i do?
kohlil said:
i got theese errors
~ # dd if=/dev/block/platform/msm_sdcc.2/mmcblk0p18 of=/sdcard/backup.img
dd if=/dev/block/platform/msm_sdcc.2/mmcblk0p18 of=/sdcard/backup.img
2048+0 records in
2048+0 records out
1048576 bytes (1.0MB) copied, 0.058380 seconds, 17.1MB/s
~ # dd if=/sdcard/hboot_1.11.0003.nb0 of=/dev/block/platform/msm_sdcc.2/mmcblk0p
18
dd if=/sdcard/hboot_1.11.0003.nb0 of=/dev/block/platform/msm_sdcc.2/mmcblk0p
18
dd: can't open '/sdcard/hboot_1.11.0003.nb0': No such file or directory
what can i do?
Click to expand...
Click to collapse
Do u have cwm installed...if yes, go to recovery mode and then mount sd card first...
thanks for trip i did it without errors but nothing changed.
on hboot screen;
***UNLOCKED***
FLYER PVT SHIP S-ON RL
HBOOT-1.11.0006
MICROP-0950
RADIO-3821.08.00.26_M
eMMC-boot
i^ve used pauls guide to flash honeycomb. and everything worked. but now i want to return orginal rom. i've tried all the shipped roms on xda but everytime i got error "155 unknown error"
how can i solve this problem?
Help..
instead of "locked" mine show "security warning"
why is it so?
update: after restart, nothing is written on that line anymore
kohlil said:
thanks for trip i did it without errors but nothing changed.
on hboot screen;
***UNLOCKED***
FLYER PVT SHIP S-ON RL
HBOOT-1.11.0006
MICROP-0950
RADIO-3821.08.00.26_M
eMMC-boot
i^ve used pauls guide to flash honeycomb. and everything worked. but now i want to return orginal rom. i've tried all the shipped roms on xda but everytime i got error "155 unknown error"
how can i solve this problem?
Click to expand...
Click to collapse
unfortunately... you can't.
I think it only works if you own a dev device with factory s-off which you probably dont.
This is also the reason why I am not ready to move to HC yet :-/
kohlil said:
thanks for trip i did it without errors but nothing changed.
on hboot screen;
***UNLOCKED***
FLYER PVT SHIP S-ON RL
HBOOT-1.11.0006
MICROP-0950
RADIO-3821.08.00.26_M
eMMC-boot
i^ve used pauls guide to flash honeycomb. and everything worked. but now i want to return orginal rom. i've tried all the shipped roms on xda but everytime i got error "155 unknown error"
how can i solve this problem?
Click to expand...
Click to collapse
go to fastboot, connect the FLYER to PC
at the command line is typed fastboot oem lock
after the operation, the top line menu fastbut *** RELOCKED ***
without leaving the menu fastbut start installing the firmware 2.23.405.3(this my original rom), after installing 2.3.4 rejoice
*** RELOCKED *** inscription remains.
piramida13 said:
go to fastboot, connect the FLYER to BB
at the command line is typed fastboot oem lock
after the operation, the top line menu fastbut *** RELOCKED ***
without leaving the menu fastbut start installing the firmware 2.23.405.3, after installing 2.3.4 rejoice
*** RELOCKED *** inscription remains.
Click to expand...
Click to collapse
Thanks piramida13! I have tried the steps and it's working. I have posted the brief steps at development section. For those wanting to revert back to GB, you may refer to the link below.
http://forum.xda-developers.com/showthread.php?t=1257909
hey with this i can turn my Flyer s-on? it is a Wifi only USA flyer , only follow the steps can i s-off then do this work With Gingerbread??
Related
Hi!
I have found similar problems in the forums, but none of the post seem to help my problem here.
My phone can't startup, it just continue to reboot after 15-20 seconds (showing the white screen with the HTC logo)
Hboot info:
*** UNLOCKED *** <- (used the HTCdev.com method)
Shooter_U PVT SHIP S-ON RL
HBOOT-1.49.0018
eMMc-boot
(date and time)
I can enter Hboot, have managed to get revolutionary CWM v4.0.1.4 on it. Tried a few different ROM's trough the Rev. tool - they seem to install fine, but I still can't start up the phone. Also tried to change my hboot by dl a (PG86IMG.zip) file, seems like it's installing/unzipping when I turn on my device (blue bar at the right hand side of the screen fills up to the top) then nothing happens. The version is the same and so on.
I know I have USB debugging checked and fastboot checked, but I cant turn it off as long as I can't startup my phone? - if this is what causing the problem? Any ideas?
EDIT: I also tried the factoryreset/wipedata/wipe cache from the revo-tool.
Thanks to steveruthless this case is now SOLVED - Thanks again!
how did you fix it?care to share how? thanks
Same problem. How did you solve??
Sent from my HTC EVO 3D GSM using XDA App
Same problem. If someone got an answer, I would be pleased to know.
If u have hboot 1.49 it would be best to use revaluationarys
Sent from my PG86100 using XDA App
i have 149.00.18 and revaluationarys says not sppourtedwt can i do now
I'm not 100% sure since i'm S-On HTC Unlocked CDMA version, but with S-On/ Unlocked, you have to enter recovery via fastboot command prompt (ie: type: fastboot boot YourRecoveryFilename.img ). The filename has to exactly match the filename you flashed to the phone AND the filename that resides in your fastboot folder (you have to leave a copy there, idk why). Once in recovery you can format system, wipe data, and flash rom's & kernels. If you don't enter recovery this way the kernel won't load and you will boot loop.
There are other options, such as JoeyKrim's Flashimage to flash the kernel first, then enter recovery by any method to flash the rest, or you can extract/copy the "boot.img" from the rom's zip, put it in fastboot folder and (type: fastboot flash boot boot.img ) to flash the kernel separately via fastboot command. Doesn't the first option to enter recovery via fastboot just sound more straight forward?
Note: I have some examples in my Guide/flashing notes thread (in my signature) that may help you understand better, but keep in mind its for CDMA version so none of the files I've linked will work with GSM, but the 3rd or 4th post for flashing roms/kernels should help.
Lonely khan said:
i have 149.00.18 and revaluationarys says not sppourtedwt can i do now
Click to expand...
Click to collapse
If Dats the case it seems like u would be better off with hboot 1.5
Sent from my PG86100 using XDA App
Sorry for this taking so long guys..
I fixed my issue by simply using a cmd prompt and boot the img from the zip/rom you have downloaded. I'll try to my make a step by step here:
1. Boot into fastboot and plug in your usb
2. Copy boot.img from the zip/the rom you want installed) and paste it to your Android SDK tools folder. Prob: C:\Android SDK\tools
4. Open a command prompt in C:\Android SDK\tools
5. Write in fastboot boot boot.img the CMD prompt
Voila! Your phone should now be working again.
Whenever you try to flash ROMs always follow these steps , if you are unlocked via HTC method.
Boot your phone in bootloader > Select fastboot > connect to PC >phone should say fastboot-USB > open cmd > navigate to fastboot folder > put your recovery in that folder > pull the boot.img from the ROM you are trying to flash and put it in fastboot folder > then type "fastboot flash boot boot.img" > then type "fastboot boot recovery.img (your recovery name might be different so use that name instead) > Your recovery will boot > Wipe everything first > then flash the ROM.....
htc evo 3d gsm rebooting problem
Hi!
I have found similar problems in the forums, but none of the post seem to help my problem here.
My phone can't startup, it just continue to reboot after 15-20 seconds (showing the white screen with the HTC logo)
Hboot info:
*** UNLOCKED *** <- (used the HTCdev.com method)
Shooter_U PVT SHIP S-ON RL
HBOOT-1.49.0018
eMMc-boot
(date and time)
I have similer problem and i dont now what do i do with my phone
its at the brogramer guy but it take long time to fix me phone problem
ithink to weeks
seriasly I need to help
excusme for my writing I am still studing english
and thanks to help if u help or traing to help me
Amphel said:
Sorry for this taking so long guys..
I fixed my issue by simply using a cmd prompt and boot the img from the zip/rom you have downloaded. I'll try to my make a step by step here:
1. Boot into fastboot and plug in your usb
2. Copy boot.img from the zip/the rom you want installed) and paste it to your Android SDK tools folder. Prob: C:\Android SDK\tools
4. Open a command prompt in C:\Android SDK\tools
5. Write in fastboot boot boot.img the CMD prompt
Voila! Your phone should now be working again.
Click to expand...
Click to collapse
the command is fastboot FLASH boot boot.img
you can not forget the flash part... it is an integral part of the system to modify it....
---------- Post added at 03:35 AM ---------- Previous post was at 03:31 AM ----------
ko0o0ky said:
Hi!
I have found similar problems in the forums, but none of the post seem to help my problem here.
My phone can't startup, it just continue to reboot after 15-20 seconds (showing the white screen with the HTC logo)
Hboot info:
*** UNLOCKED *** <- (used the HTCdev.com method)
Shooter_U PVT SHIP S-ON RL
HBOOT-1.49.0018
eMMc-boot
(date and time)
I have similer problem and i dont now what do i do with my phone
its at the brogramer guy but it take long time to fix me phone problem
ithink to weeks
seriasly I need to help
excusme for my writing I am still studing english
and thanks to help if u help or traing to help me
Click to expand...
Click to collapse
for you .... you have a boot/img file problem... the backup... if you did one.... pull the boo9ot.iumg file from there and rewrite it to the boot partition and it should boot up
Since you have 1.4 just Look for a guide for soff then flash your rom
Sent from my PG86100 using XDA Premium App
i have the same problem...endless boot
Hboot info:
*** UNLOCKED *** <- (used the HTCdev.com method)
Shooter_U PVT SHIP S-ON RL
HBOOT-1.49.0018
eMMc-boot
(date and time)
- I can`t run adb shell because the phone does`n start
- I can`t flash old radio img via flashboot
D:\GSM 2011\htc\evo 3d gsm\ADB_Flash_Tool>fastboot flash radio radio.img
sending 'radio' (22145 KB)... OKAY
writing 'radio'... INFOsignature checking...
FAILED (remote: signature verify fail)
- I can`t write rru image file maybe becose i have new image file (1.22.720.1) and can`t downgrade - error 140 or another error
- I can write any recovery cwm file, but the phone doesn enter in recovery
D:\GSM 2011\htc\evo 3d gsm\ADB_Flash_Tool>fastboot flash recovery cwm-5.0.2.0-sh
ooter.img
sending 'recovery' (4726 KB)... OKAY
writing 'recovery'... OKAY
D:\GSM 2011\htc\evo 3d gsm\ADB_Flash_Tool>
- I can write boot_signed.img, from PG68IMG.ZIP i flash via sdcard, but doesn help, the phone is in the same condition
D:\GSM 2011\htc\evo 3d gsm\ADB_Flash_Tool>fastboot flash boot boot_signed.img
sending 'boot' (3604 KB)... OKAY
writing 'boot'... OKAY
- I can write any PG86IMG.ZIP full or only radio file via sdcard, but doesn help, the phone is the same
gabrielgsm said:
i have the same problem...endless boot
Hboot info:
*** UNLOCKED *** <- (used the HTCdev.com method)
Shooter_U PVT SHIP S-ON RL
HBOOT-1.49.0018
eMMc-boot
(date and time)
- I can write any recovery cwm file, but the phone doesn enter in recovery
D:\GSM 2011\htc\evo 3d gsm\ADB_Flash_Tool>fastboot flash recovery cwm-5.0.2.0-sh
ooter.img
sending 'recovery' (4726 KB)... OKAY
writing 'recovery'... OKAY
Click to expand...
Click to collapse
I'm on Sprint Cdma, but it looks like u might be using the CDMA Recovery (shooter) vs Gsm Recovery (shooteru).
Here are some notes to review:
http://forum.xda-developers.com/showthread.php?p=22732146
[Tutorial] [UNLOCK/ROOT] EVO 3D GSM Hboot 1.49.0011> + S-On [HTC Unlock method]
Here are links to Gsm Shooteru recoveries (give one of these a try):
http://forum.xda-developers.com/showthread.php?p=23099222
[Tutorial] [UNLOCK/ROOT] EVO 3D GSM Hboot 1.49.0011> + S-On [HTC Unlock method]
Sent from my PG86100 using Tapatalk
hi,my htc got stuck logo.i format my desire z with no backups.i unlocked bootloader with htcdev.com........temp root.....S-on..........nothing flashing any Rom...neither custom roms..Nor default roms.....plzzzz help....only fastboot is working....no adb.....plzzzzzzzzzz heellppppppp
klassikkamii said:
hi,my htc got stuck logo... ....only fastboot is working....no adb.....plzzzzzzzzzz heellppppppp
Click to expand...
Click to collapse
Hello,
I am not sure If someone can help in this case.
Please provide more information.
* Do you confirm, that you cannot boot in recovery from HBOOT?
* What is your exact HBOOT version? Do you have an "Engineering HBOOT"?
When only fastboot is working then I only see a little chance for your phone when you have an engineering HBOOT.
Best regards,
Catherall
P.S: Seems like you really tortured you helpless Desire Z
thxx for reply......i try to provide in detail.
* Do you confirm, that you cannot boot in recovery from HBOOT?
yes , i can boot in recovery-clockwork-3.0.2.4-vision.
* What is your exact HBOOT version? Do you have an "Engineering HBOOT"?
No i think i am on stock hboot but i dont know indeed.
More Detail are,
My Hboot Screen shoes it.
****Unlocked****
Vision pvt ship S-on
HBoot-0.85.0015
Microp-0425
Radio-26.10.04.03_M
emmc-boot
Dec 20,2011,16:21:13
Also,should know.i installed Clockwork Recovery.which is working perfectly.when i flash rom it all goes success.but when i reboot with hope ,stuck in logo.i flashed Villision1.0 ,Android_Revolution_HD-4G_7.0.3,C7 succesfully but never start normally just stuck in logo.i use also fastboot flash boot boot.img as well but nothing happened.same stucking.when i use adb commands or adb shell ,getting error device not found.plzz give me back earlier position as company setting it was gingerbread 2.3.3.
i am sorry abount my low english language capabality.
Get your phone back on track with proper unlocking (S-OFF)
klassikkamii said:
thxx for reply......i try to provide in detail.
* Do you confirm, that you cannot boot in recovery from HBOOT?
yes , i can boot in recovery-clockwork-3.0.2.4-vision.
* What is your exact HBOOT version? Do you have an "Engineering HBOOT"?
No i think i am on stock hboot but i dont know indeed.
My Hboot Screen shoes it.
****Unlocked****
Vision pvt ship S-on
HBoot-0.85.0015
Microp-0425
Radio-26.10.04.03_M
Also,should know.i installed Clockwork Recovery.which is working perfectly.when i flash rom it all goes success.but when i reboot with hope ,stuck in logo.
Click to expand...
Click to collapse
Two things are not clear to me:
1) How did you "unlock" you phone, did you use http://htcdev.com/bootloader/ method to get "****Unlocked****" in HBOOT? This is important to know for me.
When you indeed unlocked using http://htcdev.com/bootloader/ method, then you have to install an suitable "boot.img" every time you flash a new ROM.
Otherwise the old boot.img tries to boot the old ROM that was overwritten with the new one you flashed.
2) When you can boot ClockworkMod Recovery then you can connect using adb. Just use adb while booted into your custom recovery.
I really recommend to proper unlock your HTC Desire Z as described in
http://goo.gl/aXNr
The advantage of this method is, that you can flash any custom ROM without the need to flash the kernel of the ROM (boot.img) separately!
ATTENTION: Before doing anything like "fastboot oem lock"
you have to use "misc_version 0.1" and "flashgc". Do not continue without that!
When you do not know how to use that then ask (here or in freenode IRC channel #G2ROOT)!
Then you can go on to downgrade your phone:
[GUIDE] Downgrade G2 (2.3.X) & DZ (2.3.X) & mT4g (2.3.4) & DHD w/ S-ON to Stock Froyo
http://forum.xda-developers.com/showthread.php?t=1178912
Please make sure that you follow the steps described under the topic ***If you have used the "official" htcdev.com unlock option***
Then you can gain S-OFF (real unlock) using gfree
If you have questions then come to the awesome freenode IRC channel #G2ROOT.
Best regards,
Catherall
yes i unlocked with htcdev.com,so i will lock it again with "fastboot oem bootlock" command and will try to unlock as your advice.
i am so happy after seeing your advices.and i didn't know that i can use adb shell in recovery.you mean boot in recovery than use adb terminal from pc.ok i check it and try to apply it.and thankyou very much again for your help.
I will tell you results.
Attention
Before using fastboot oem lock make sure that downgrade would work.
Run the commands "misc_version 0.1" and "flashgc" successfully before doing anything like
fastboot oem lock!
Visit freenode IRC channel #G2ROOT
I am not 100% sure what happens on your semi-bricked phone with fastboot oem lock!
Best regards,
Catherall
one more plzz
ok i will make sure but plzzz tell me can i restore officialy stock rom with adb support ( may be with golcard support ) sothat i dont wanna take any risk.no downgrade,no s-off just my previous position.
I went to #G2Root but i didnt understand how talk anybody.i am not familiar on that.again thxx for your attention for me.
P.E : ok i tried adb commands while booted in recovery. adb devices command works and show serial number, but when i command ' adb shell ' got " # " instead " $ " so stuck again need more advice plzzzzzzzzzzzz.how can get " $ "
PLssss Help
i am getting " ~ # " Error in adb shell please helppp....
Options for S-OFF/root or reverting to Stock
Hello klassikkamii,
most custom Recoveries provide root access when you use "adb shell" to connect to them.
So adb shell returns "#" to indicate root access. When you get the prompt "$" then you have access as a user.
I would do the following steps. They allow you to get full S-OFF, Engineering HBOOT and a ROOTed ROM, or if you prefer return to stock ROM.
Returning the latest stock is much easier and safer when you do the following steps to change the internal software version number of the phone an make your SD card a goldcard.
Download misc_version 0.1:
http://forum.xda-developers.com/attachment.php?attachmentid=661216&d=1311237785
Download flashgc:
http://forum.xda-developers.com/attachment.php?attachmentid=819704&d=1324116910
And then use the following procedure to change version number and make a goldcard (as provided by Setherio in his guide [GUIDE] Downgrade G2 (2.3.X) & DZ (2.3.X) & mT4g (2.3.4) & DHD w/ S-ON to Stock Froyo:
1) Unzip misc_version_01.zip and flashgc.zip in the platform-tools directory.
2) Run the following commands from you platform-tools directory:
Code:
adb shell mount /data
adb push misc_version /data/local/tmp/misc_version
adb push flashgc /data/local/tmp/flashgc
adb shell chmod 777 /data/local/tmp/*
adb shell
Now you are in the phone shell with root access (indicated by the prompt "#").
Continue with the commands:
Code:
cd /data/local/tmp
./misc_version -s 1.00.000.0
This should return:
--set_version set. VERSION will be changed to: 1.00.000.0
Patching and backing up partition 17...
Continue to make you SD card a goldcard:
Code:
./flashgc
Note: If you get the following error, please make sure your sdcard is inserted in your phone: Error opening backup file.
Continue with the command
Code:
sync
Double check that you phone's software version number is set to 1.00.000.0 with the command:
Code:
dd if=/dev/block/mmcblk0p17 bs=1 skip=160 count=10
The first line of the command output must be:
1.00.000.010+0 records in
Exit the phone's shell with
Code:
exit
From here you can get an Engineering HBOOT and a custom, rooted ROM, or revert to a stock ROM. Both ways are about the same effort.
Please post how this worked out for you.
Best regards,
Catherall
still stuck
adb push misc_version /data/local/tmp/misc_version
Getting Error
failed to copy 'misc_version' to /data/loca/tmp/misc_version :Not a directory
As i am already with "~ #" i try direct command :cd /data/local/tmp
Got Error This :/sbin/sh: cd:can't cd to /data/local/tmp
if i use command for sd card,
adb push misc_version /Sdcard/misc_version
it show size of file or push succed but not in local/tmp.
i think if i would get "$" instead " ~#" May be i can do all u advice me.
Better do it interactive
Hello,
there might be several reasons why the command did not work.
Not having "$" is none of them.
Please come to freenode IRC and login to channel #G2ROOT. Ask for Catherall, I should be there for the next hours. When I am not there then check back later.
Best regards,
Catherall
ok i solved all Puzzle.solution was only use " GoldCard Method".i use command mmc2 instead mmc1 and voilaaaaaa i got my CID then everything was eassy.....in the End i really thanks to Catherall,You help me well...your information was helpfulln from your instructions i got my way thanksssss...
ONLY FOLLOW THIS GUIDE FOR WARRANTY REPLACEMENTS OR IF YOU NEED TO BE STOCK FOR A SALE. THERE IS NO OTHER REASON TO FOLLOW THIS GUIDE.
ALSO MAKE SURE YOU FOLLOW THE GUIDE PROPERLY. FAR TOO MANY ERRORS ARE BEING MADE BY NOT READING OR FOLLOWING STEPS IN ORDER.
This guide will help you get your phone back to stock after using any of the 5 S-Off methods that either have been or are currently available to us.
Credit to Scotty1223. I edited his One S guide for the DNA.
First post is for Facepalm and JTAG S-off only. RevOne instructions are in the second post. Moonshine and Rumrunner is in post 3.
***IF YOU HAVE A CUSTOM SPLASH SCREEN INSTALLED, THE STOCK SPLASH SCREEN MUST BE FLASHED BEFORE DOING ANYTHING! SEE FOURTH POST FOR LINKS AND INSTRUCTIONS FOR FLASHING THE STOCK SPLASH SCREEN***
***DO NOT ISSUE ANY OF THE WRITESECUREFLAG COMMANDS ON AN ENG HBOOT AS IT WILL BRICK THE DEVICE. JUST FOLLOW THE GUIDE.***
For those who want to return to stock and have used the JTAG method for achieving S-Off, this guide will also work for you. It all depends on what you did AFTER you got your JTAG phone back. If you wrote a new CID using fastboot and HTCDev unlocked, follow the guide as it is written out.
If you didn't write a new CID and use HTCDev unlock and just merely flashed a modified/ENG HBOOT, then the process would be: Fastboot flash stock hboot, RUU to stock, fastboot oem writesecureflag 3, then allow phone to update using the OTA process. You can find the commands/files/steps for these 3 simple steps below as well.
Files needed:
Lock bootloader zip: lock bootloader MD5: f335f78f9f46469c823da0c671026de5
3.06 RUU: 3.06 RUU
Steps:
1.Copy the "lock bootloader zip" onto root of internal storage and flash in recovery of your choice. Once it is flashed Reboot your phone.
2.Reboot into bootloader either using 4 in 1 power menu (if your ROM supports it). Or plug your phone into a USB port, turn on USB debugging and open a command prompt and type:
Code:
adb devices (Your device ID should be listed)
adb reboot bootloader
Verify you are **LOCKED** If not, re-flash the zip. If still not locked, try downloading the file again and re-flashing.
IF YOU ARE RUNNING ANY HBOOT THAT IS NOT THE 3.06 HBOOT (1.54 in bootloader), YOU MUST FLASH 3.06 HBOOT BEFORE CONTINUING - SEE POST 4
3. run the RUU as admin (right click, run as administrator)
4. After RUU completes and phone reboots, make sure usb debugging is on and in charge only mode and open cmd prompt
5. Run the following:
Code:
adb devices (your device should be listed)
adb reboot bootloader
fastboot devices (your device should be listed)
fastboot oem writecid VZW__001 (2 underscores)
fastboot reboot-bootloader
fastboot getvar cid (verify your stock CID)
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
Should now be 100% stock, S-ON, with CID 100% stock as well.
Returning to stock from RevOne
It is pretty much the same process, but with a slight deviation.
AGAIN, IF YOU HAVE A MODIFIED/ENG HBOOT, DO NOT ISSUE ANY WRITESECURE FLAG COMMANDS. JUST FOLLOW THE GUIDE.
First, download these two files:
Files needed:
Lock bootloader zip: lock bootloader MD5: f335f78f9f46469c823da0c671026de5
3.06 RUU: 3.06 RUU
Steps:
1.Copy the "lock bootloader zip" onto root of internal storage and flash in recovery of your choice. Once it is flashed Reboot your phone.
2.Reboot into bootloader either using 4 in 1 power menu (if your ROM supports it). Or plug your phone into a USB port, turn on USB debugging and open a command prompt and type:
Code:
adb devices (Your device ID should be listed)
adb reboot bootloader
Verify you are **LOCKED** If not, re-flash the zip. If still not locked, try downloading the file again and re-flashing.
IF YOU ARE RUNNING ANY HBOOT THAT IS NOT THE 3.06 HBOOT (1.54 in bootloader), YOU MUST FLASH 3.06 HBOOT BEFORE CONTINUING - SEE POST 4
3. run the RUU as admin (right click, run as administrator)
4. After RUU completes and phone reboots, make sure usb debugging is on and in charge only mode and open cmd prompt
5. Run the following:
Code:
adb devices (your device should be listed)
adb reboot bootloader
fastboot devices (your device should be listed)
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
You are now out of box stock.
Return to stock on Moonshine, Rumrunner and Firewater S-Off
Files needed:
Lock bootloader zip: lock bootloader MD5: f335f78f9f46469c823da0c671026de5
3.06 RUU: 3.06 RUU
Steps:
1.Copy the "lock bootloader zip" onto root of internal storage and flash in recovery of your choice. Once it is flashed Reboot your phone.
2.Reboot into bootloader either using 4 in 1 power menu (if your ROM supports it). Or plug your phone into a USB port, turn on USB debugging and open a command prompt and type:
Code:
adb devices (Your device ID should be listed)
adb reboot bootloader
You are locked. The s-off process removes the flag from displaying, but it is now locked.
IF YOU ARE RUNNING ANY HBOOT THAT IS NOT THE 3.06 HBOOT (1.54 in bootloader), YOU MUST FLASH 3.06 HBOOT BEFORE CONTINUING - SEE POST 4
3. run the RUU as admin (right click, run as administrator)
4. After RUU completes and phone reboots, make sure usb debugging is on and in charge only mode and open cmd prompt
5. Run the following:
Code:
adb devices (your device should be listed)
adb reboot bootloader
fastboot devices (your device should be listed)
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
You are now out of box stock.
FLASHING THE STOCK HBOOT:
*Credit to .torrented*
1. download 3.06 HBOOT: 3.06 HBOOT
2. Rename stock hboot file to : PL83IMG.zip and place in the folder that contains your fastboot.exe file (On your computer)
3. Flash hboot
Code:
Step 1) adb reboot bootloader
Step 2) fastboot oem rebootRUU
Step 3) CD to directory containing hboot zip (i.e. cd C:\sdk\)
Step 4) fastboot flash zip PL83IMG.zip
*** When it says it is done in the terminal/cmdprompt execute the following ***
[The green bar only fills up about 75% of the way]
Step 5) fastboot reboot-bootloader
Flashing the Stock Splash Image
*All credit goes to E.T.Heil
1. Download the stock splash image here.
2. Rename file to splash1.img
3. Place the file in the same folder you have adb.exe and fastboot.exe located.
4. Plug in your phone to a USB port, turn on USB debugging and open a command prompt. cd to the directory your adb/fastboot is located
5. Run the following:
Code:
adb devices (your device ID should be displayed)
adb reboot bootloader
Once in the bootloader, run:
Code:
fastboot flash splash1 splash1.img
Once complete, reboot the phone using the menu or
Code:
fastboot reboot
updated with RevOne and Moonshine...
If anyone sees anything I missed let me know. Otherwise guide is complete.
Thank you so much for making this post. This is exactly what I needed. I am not quite sure which method I uses but it was the first one that required changing the CID, unlocking via htc dev and all that stuff. Would that be facepalm? Sorry if this is a dumb question, it was so long ago that I don't quite remember.
Imacellist said:
Thank you so much for making this post. This is exactly what I needed. I am not quite sure which method I uses but it was the first one that required changing the CID, unlocking via htc dev and all that stuff. Would that be facepalm? Sorry if this is a dumb question, it was so long ago that I don't quite remember.
Click to expand...
Click to collapse
Yes that was the Facepalm method. So follow the OP guide for that.
I love you! (no homo).
when i run RUU i get error 155 so i tried to flash the 1.15 hboot and i get this error in cmd
D:\Documents and Settings\Jonathan\My Documents\HTC\adt-bundle-windows-x86-20130
219\sdk\platform-tools>fastboot flash zip PL83IMG.zip
sending 'zip' (2047 KB)...
OKAY [ 0.375s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 0.562s
am i doing something wrong? i want to get my phone back to complete stock because i flashed a rom after moonshining without making a backup first. so i really want to get to stock so i can do the whole process over again (moonshine again if needed)
Prodiigy said:
when i run RUU i get error 155 so i tried to flash the 1.15 hboot and i get this error in cmd
D:\Documents and Settings\Jonathan\My Documents\HTC\adt-bundle-windows-x86-20130
219\sdk\platform-tools>fastboot flash zip PL83IMG.zip
sending 'zip' (2047 KB)...
OKAY [ 0.375s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 0.562s
am i doing something wrong? i want to get my phone back to complete stock because i flashed a rom after moonshining without making a backup first. so i really want to get to stock so i can do the whole process over again (moonshine again if needed)
Click to expand...
Click to collapse
Possibly a bad download, Download the HBOOT again and give it another go.
Also, with that error you are getting during the RUU process, did you lock the bootloader back up before running the RUU? That error sometimes shows up from not doing that.
I don't know if this will help anyone or not, or if this was known and I was just being stupid, but I was getting the ERROR [155] as well when running the RUU and I knew my hboot was correct as well as locked so that wasn't the problem, so I attempted to run the RUU again and saw that it was saying my current version was 1.28.xxxxxx which made me realize that that was the Sense 5 roms version number and not the actual version number of my phone causing it to fail. What I then did was i downloaded an AOSP based rom (but I would surmise that a sense 4 DNA rom would work as well) and flashed that then tried again. After doing that it showed the correct version number in the RUU and processed correctly!!
For a little more in site I was on the following setup:
Moonshine S-OFF
Joelz Stock Sense 5 <-- What caused the Error 155
Carbon ROM (Built by Pio) <--- What fixed the error (Would work with any AOSP or Sense 4 Rom ***Needs tested***)
**Edit**
Also incase anyone was wondering I was doing this to fix my phones radio, for some reason when flashing certain roms it gets stuck in Roaming no matter what you do. To fix it I just take my phone completely back to stock S-ON etc, then go into the bootloader and hit factory reset with the stock recovery and it seems to fix it, then S-Off and unlock again and go about my business. I couldn't actually find an answer besides "RMA the thing" to fix the radio roaming issue, so i figured i'd add that incase anyone else was/is in the same boat.
Hmm... I'll do a bit of testing on that with random Sense 5 vs AOSP/Sense 4 ROMs. If that is the case, I'll edit the guide.
I successfully restored my droid dna to untouched stock with this method. I had to exchange my DNA for a new one due to problems I was having and I am trying to do everything I can to make sure that there is no evidence of my tampering. One thing someone mentioned was to take the OTA's to get the device up to current 2.06 since I have been rooted and such since the first day it was available and am on 1.15. I have tried manually checking for software updates and it doesn't seem to find anything. It hasn't prompted me yet and I am wondering if because I am so far behind if they update system isn't checking or something else it wrong. Any thoughts? Any ways to manually update to 2.06 like flashing a new RUU (if that exists)? Thanks.
Just leave the phone on... I did it a few weeks back. It will eventually update.
Phaded said:
Just leave the phone on... I did it a few weeks back. It will eventually update.
Click to expand...
Click to collapse
Thanks. Verizon is only giving me 5 days to ship it back haha. So I just wanted to figure it out as quickly as possible.
Confirmed that on Sense 5 ROMs it randomly errors out. Editing guide.
I flashed the hboot zip and the hboot version is1.33 The phone is s-off and locked on viper rom. The RUU will reboot the phone into the black screen with the silver HTC logo, then the RUU stops working and asks to close the program. I downloaded three times and checked the md5 each time and its good. I am stuck. Any suggestions?
gris1016 said:
I flashed the hboot zip and the hboot version is1.33 The phone is s-off and locked on viper rom. The RUU will reboot the phone into the black screen with the silver HTC logo, then the RUU stops working and asks to close the program. I downloaded three times and checked the md5 each time and its good. I am stuck. Any suggestions?
Click to expand...
Click to collapse
The RUU itself crashes on the computer or the phone crashes and reboots?
Also the hboot I have linked should give you version 1.31 I do believe.
Thanks for this, worked perfectly!
Phaded said:
Return to stock on Moonshine S-Off
First, download the stock RUU
Stock RUU: 1.15 RUU: Mirror #1 or Mirror #2
Plug your phone into a USB port, turn on USB debugging and open a command prompt. cd to the directory that has adb/fastboot.
**NOTE** I noticed on the XDA mobile app that it breaks the echo command line up and makes it look like 2 separate commands. Do not separate it. The command starts at echo and ends at 33796.
Run:
Code:
adb devices (verify device ID is listed)
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
exit
Your bootloader is now locked. Lets verify...
Reboot into bootloader either using 4 in 1 power menu (if your ROM supports it). Or plug your phone into a USB port, turn on USB debugging and open a command prompt and type:
Code:
adb devices (Your device ID should be listed)
adb reboot bootloader
Verify you are **LOCKED**
Click to expand...
Click to collapse
I am having issues not getting the phone to return to "Locked" status. I have and am running the stock ROM. Just reset back to factory. I am following the commands to the T. Below is what my CMD prompt shows that I typed in, or copied and pasted for the echo command. I was trying to follow the note about the echo command but I could see nothing wrong with it... also in the end I had to type exit command twice for it exit and go back to the prompt for the next folder.
C:\android-adb>adb devices
List of devices attached
FA2C2S510423 device
C:\android-adb>adb shell
[email protected]:/ # su
su
[email protected]:/ # echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 s
eek=33796
d of=/dev/block/mmcblk0p3 bs=1 seek=33796 <
4+0 records in
4+0 records out
4 bytes transferred in 0.007 secs (571 bytes/sec)
[email protected]:/ # exit
exit
[email protected]:/ # exit
exit
C:\android-adb>
Click to expand...
Click to collapse
Hi everyone,
I know there's a thousand threads on this already but I've yet to find a definitive process for completely returning the T-Mobile HTC One back to stock. There's bits and pieces here and there but I'm not confident that I can piece them all together in the proper sequence. Hopefully we can get everything answered in one thread and point to this one in the future.
My goal: No "***TAMPERED***" in bootloader. No "***UNLOCKED***" in the bootloader. No red "This build is for development purposes only" when jumping into recovery.
My bootloader states:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.15
OpenDSP-v26.120.274.0202
eMMC-boot
Mar 25, 2013,22:02:35:-1
Currently running clockwork recovery 6.0.3.2 and stock odex'd rooted 1.27.431.7 rom.
I have on hand:
- nandroid of factory unrooted odex'd image
- factory boot.img
- factory recovery_tmobile.img
Here's is what I *think* the process is to get me back to the factory out-of-the-box state:
1) Restore factory nandroid via clockwork recovery's restore
2) Push factory recovery: boot into fastboot and run "fastboot flash recovery_tmobile.img"
3) Push revone using the standard revone install process
4) S-Off via "./revone -P" then "./revone -s 0"
5) Remove ***TAMPERED*** by running "./revone -t"
6) Remove ***UNLOCKED*** by running "./revone -l" (These two commands can probably be combined: ./revone -t -l)
7) Now to remove the red hboot (I used Sneakyghost's process for this but I can't link to it... topic 2316726)
- Download 1.44.0000 Original unmodified hboot from sneakyghost's thread
- From fastboot: "fastboot flash zip hboot.zip"
- Finish hboot update: fastboot reboot-bootloader
**** I don't think this is correct. Where can I get the factory 1.44.0000 that works with T-Mobile CID?? ****
8) Relock device via revone: "./revone -l"
9) Get S-On: "fastboot oem writesecureflag 3"
10) Run factory reset in hboot.
Is this correct?
Can anyone comment on the line in red? Is there a T-Mo specific hboot? I can't find one.
DELETED.
delete
I am trying to restock Verizon Droid DNA
Followed all the guided method , got to a point of where Relocked/S-ON
Unable to use RUU downloaded , check MD5 all correct
Try moonshine to enable S-OFF
flashed firmware and now stuck at 2.06 firmware
How do i restock?
I am unable to boot anything just the bootloader
fastboot is working fine
Unable to flash any zip hboot downloaded , keep getting signature fail
Unable to Unlocked the bootloader too
I am unable to execute adb commad tho
any suggestion?
BloodRaven2011 said:
I am trying to restock Verizon Droid DNA
Followed all the guided method , got to a point of where Relocked/S-ON
Unable to use RUU downloaded , check MD5 all correct
Try moonshine to enable S-OFF
flashed firmware and now stuck at 2.06 firmware
How do i restock?
I am unable to boot anything just the bootloader
fastboot is working fine
Unable to flash any zip hboot downloaded , keep getting signature fail
Unable to Unlocked the bootloader too
I am unable to execute adb commad tho
any suggestion?
Click to expand...
Click to collapse
You said you tried moonshine to get s-off? did it not work?
You need to be a bit more clear. You are trying to go complete stock or use moonshine to unlock and soff? What error do you get when trying to use ruu?
Hit thanks if I helped! Check out my site at www.circuitsaviors.com
Use moonshine to s off. Go to the thread on how to go back to stock. Follow the directions. The signature is obviously failing because you are s on...
Sent from my HTC6500LVW using xda app-developers app
You might want to check out my thread (http://forum.xda-developers.com/showthread.php?t=2438199), but it's not good news...
jtag is ur only answer. I have a htc dna sitting in my drawer because of this very same reason. I've looked and looked. Sorry
People, you need to RUU BEFORE issuing any s-on commands. I'm seeing this repeatedly.
Phaded said:
People, you need to RUU BEFORE issuing any s-on commands. I'm seeing this repeatedly.
Click to expand...
Click to collapse
This is where the problem rise
I did not realize that is no way to downgrade to stock HBOOT
and the worst part now is i cant do anything
yes , option is to JTAG
BloodRaven2011 said:
This is where the problem rise
I did not realize that is no way to downgrade to stock HBOOT
and the worst part now is i cant do anything
yes , option is to JTAG
Click to expand...
Click to collapse
You could've downgraded your hboot... This also needs to be done before issuing any s-on commands
I am unable to issue a new hboot , i got the signature verification failed. If anyone know how to , it be great , JTAG is my last option tho
Check your PMs. I'd be interested in your results.
I think I had the same signature error a few days ago u need to be on the 1.15 Hboot I couldn't figure it out until i read somewhere not to add a .zip when you rename the hboot zip file and it will flash correctly thru adb hope this helps
http://forum.xda-developers.com/showthread.php?p=42352912
Sent from my HTC6435LVW using Tapatalk 2
xaalfx said:
I think I had the same signature error a few days ago u need to be on the 1.15 Hboot I couldn't figure it out until i read somewhere not to add a .zip when you rename the hboot zip file and it will flash correctly thru adb hope this helps
http://forum.xda-developers.com/showthread.php?p=42352912
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
i am unable to use adb command.
I've been reading thru that before i ask this question
try flashing this is fastboot http://www.mediafire.com/download.php?pj2lknq5gr0jkmf
rename to just PL83IMG.zip
then try to execute
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip PL83IMG.zip
and this will return you to stock hboot let me know how it works out and ill try to help you from there
I'm confused. Maybe someone can answer.
He flashed the 2.06 firmware successfully. That will flash a the new hboot, radio and recovery.
Unless he has a custom splash screen, why would RUU'ing fail.
What happens if the 2.06 firmware it's flashed again?
Does it pass the checks?
Nvm: he can't RUU because the hboot has to 1.15.
Gungrave223 said:
try flashing this is fastboot http://www.mediafire.com/download.php?pj2lknq5gr0jkmf
rename to just PL83IMG.zip
then try to execute
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip PL83IMG.zip
and this will return you to stock hboot let me know how it works out and ill try to help you from there
Click to expand...
Click to collapse
all the above failing due to higher fw
and this causing sgnature verification fail
Gungrave223 said:
try flashing this is fastboot http://www.mediafire.com/download.php?pj2lknq5gr0jkmf
rename to just PL83IMG.zip
then try to execute
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip PL83IMG.zip
and this will return you to stock hboot let me know how it works out and ill try to help you from there
Click to expand...
Click to collapse
fr4nk1yn said:
I'm confused. Maybe someone can answer.
He flashed the 2.06 firmware successfully. That will flash a the new hboot, radio and recovery.
Unless he has a custom splash screen, why would RUU'ing fail.
What happens if the 2.06 firmware it's flashed again?
Does it pass the checks?
Nvm: he can't RUU because the hboot has to 1.15.
Click to expand...
Click to collapse
YEAP ,
It need 1.15
anyhow i can fake this to accept a lower hboot?
with a different sgnature?
BloodRaven2011 said:
YEAP ,
It need 1.15
anyhow i can fake this to accept a lower hboot?
with a different sgnature?
Click to expand...
Click to collapse
It's not a signature issue, it's encryption issue. Newer hboots are unable to decrypt the older ruu zip. If you have a "stockish" rom, you can reflash the 2.06 firmware zip. this will flash a signed kernel and recovery and allow the device to _attempt_ to boot to android. If you can get to android, you can then attempt to s-off again.
If moonshine repeatedly fails (don't drink and shine) and also revone repeatedly fails try this:
In moonshine folder you'll see dnashellroot.apk package
1.) adb install dnashellroot.apk
2.) adb shell
3.) am start -n c.fyf/.MainActivity
4.) (wait 10 seconds)
5.) /dev/sh ($ should turn into #)
6.) echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
^do NOT screw that command up, copy/paste it or risk a brick
7.) exit
8.) exit
9.) adb reboot bootloader
10.) fastboot getvar cid
if it's 22222222, you are good. Proceed to htcdev to unlock, then you can s-off using facepalm.
beaups said:
It's not a signature issue, it's encryption issue. Newer hboots are unable to decrypt the older ruu zip. If you have a "stockish" rom, you can reflash the 2.06 firmware zip. this will flash a signed kernel and recovery and allow the device to _attempt_ to boot to android. If you can get to android, you can then attempt to s-off again.
If moonshine repeatedly fails (don't drink and shine) and also revone repeatedly fails try this:
In moonshine folder you'll see dnashellroot.apk package
1.) adb install dnashellroot.apk
2.) adb shell
3.) am start -n c.fyf/.MainActivity
4.) (wait 10 seconds)
5.) /dev/sh ($ should turn into #)
6.) echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
^do NOT screw that command up, copy/paste it or risk a brick
7.) exit
8.) exit
9.) adb reboot bootloader
10.) fastboot getvar cid
if it's 22222222, you are good. Proceed to htcdev to unlock, then you can s-off using facepalm.
Click to expand...
Click to collapse
I wish i can execute adb command
What seems to be an issue
i dont have any ROM installed now , and the only thing that i can use is fastboot command
I am familiar with adb , and plus i've created custom ROM before but not for HTC
trying to help a cousin but hell , JTAG here is unfamiliar with this model ( not available in Malaysia )
so i would think , this is a deadend but i never gave hope.
Will try to figure something and all help is much appreaciated.