ADB working ? Not sure if Cid correct....need some advice - HTC Sensation

Dear Forum,
I just managed to S-Off my Sensation, right afterwards I followed auggie2k´s advice to change cid throught this command:
fastboot oem writecid 11111111 (to change CID)
fastboot reboot-bootloader (bootloader will reboot)
fastboot getvar cid (it will confirm your CID as 11111111
fastboot reboot (to reboot back in your current ROM)
I went into Fastboot and opened a command window in the folder where I had located the 3 necessary files to achieve Hboot unlock.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As you can observe on the command window below it says cid 11111111, but when I tried first to locate my device through the command "adb devices" - no device is attached.... no serial number, nothing appears...this should not happen, or? A device should have been detected. Strangely, while entering the commands describe above, all worked out as explained, rebooted, confirmed cid... etc...
I have htc drivers installed.
But, if I use the app "CID getter" it reads VODAP304, which is my original CID...and I thought that it should read 11111111, as I just changed it.... I´m just wondering if I have done something wrong...if I´m really supercid or if something somehow went wrong ?
Could it maybe be that I did not update some SDK packages ? (see last screenshot below)
Any kind of advice is welcome.
Thank you again for reading me,
Kind regards,
Ken

K3nshiro said:
Dear Forum,
I just managed to S-Off my Sensation, right afterwards I followed auggie2k´s advice to change cid throught this command:
fastboot oem writecid 11111111 (to change CID)
fastboot reboot-bootloader (bootloader will reboot)
fastboot getvar cid (it will confirm your CID as 11111111
fastboot reboot (to reboot back in your current ROM)
I went into Fastboot and opened a command window in the folder where I had located the 3 necessary files to achieve Hboot unlock.
As you can observe on the command window below it says cid 11111111, but when I tried first to locate my device through the command "adb devices" - no device is attached.... no serial number, nothing appears...this should not happen, or? A device should have been detected. Strangely, while entering the commands describe above, all worked out as explained, rebooted, confirmed cid... etc...
I have htc drivers installed.
But, if I use the app "CID getter" it reads VODAP304, which is my original CID...and I thought that it should read 11111111, as I just changed it.... I´m just wondering if I have done something wrong...if I´m really supercid or if something somehow went wrong ?
Could it maybe be that I did not update some SDK packages ? (see last screenshot below)
Any kind of advice is welcome.
Thank you again for reading me,
Kind regards,
Ken
Click to expand...
Click to collapse
Hi,
You do not need to worry.
fastboot getvar cid will find your "Actual" cid.
CidGetter will show your "Original" cid.
So, you have succeeded .

Thanks malybru,
Ahh it's so nice to get positive news...
I will install my first RUU tonight then
However, I'm still puzzled with the command window, don't know why my device was not detected even though I managed to s-cid it.
I remember that a message appeared informing about "daemon something...." and also a message with "remote not
... ", can' t remember the full message.
I just hope that it will work fine when adding a recovery after installing the RUU.
Cheers,
Ken
Sent from my HTC Sensation Z710e using xda premium

Related

How to fix my bricked htc one x ???

I got my htc one x from rogers canada while trying to root the phone failed thats my phone condition now
*** TAMPERED ***
***RELOCKED***
***Security Warning***
EVITA PVT SHIP S-ON RL
HBOOT-1.11.0000
RADIO-0.18as. 32. 09.28L
OpenDSP-v28.1. 0. 32. 0504
eMMC-boot
Please help me to put back my phone to working state ! Thank you so much !!!
Need more details.
1. What method did you use to try to root?
2. Do have twrp or cwm installed? If so can you boot to recovery?
3. Can you boot to bootloader?
4. What software version is phone on?
4. Does you pc recognize the phone when plugged in?
5. Does the phone boot at all?
6
Let us know some more details do we can try to help
Sent from my HTC One XL using Forum Runner
You are Far from bricked. Your in the phones bootloader. All that stuff you see only means the phones benn rooted and unlocked before.
Your phone is fine. download a ruu ROM for Rogers, plug your phone to your computer and start ruu from there. It should take you back to stock. Then you can start to root the phone again. Contact the person you sold the phone for boot loader unlock file so you don't have to go through the whole process to get it from htcdev
Sent from my One X using xda app-developers app
I download and try to flash Rogers RUU but failed to install the rom here is the message I got !
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
davidnadon said:
I download and try to flash Rogers RUU but failed to install the rom here is the message I got !
Click to expand...
Click to collapse
Edit
Removed
Sent from my HTC One XL using Forum Runner
U can use the correct ruu, or you can go to htcdev.com and unlock your bootloader, flash a recovery, flash a rom and you will be rooted when it reboots.
Also, u can try a couple quik commands b4 any of this to get it booted. Use a cmd prompt, cd to your adb/fastboot folder type
Fastboot erase cache
Then
Fastboot reboot
If nothing, try
Fastboot reboot recovery
If u can get into the recovery do a factory reset and reboot.

[Q] Problem error FAILED ( remote: 99 unknown fails)

Hi everyone,
I was installing MaximusHD 10.0.0 on my One S but when i do:
fastboot flash zip firmware.zip
i received the error:
FAILED ( remote: 99 unknown error)
Please help me!!!!!!
Slevinstar said:
Hi everyone,
I was installing MaximusHD 10.0.0 on my One S but when i do:
fastboot flash zip firmware.zip
i received the error:
FAILED ( remote: 99 unknown error)
Please help me!!!!!!
Click to expand...
Click to collapse
It is normal to get an error, you have to use that command again and then it will work.
(like it said in the instructions)
tivofool said:
It is normal to get an error, you have to use that command again and then it will work.
(like it said in the instructions)
Click to expand...
Click to collapse
But I launch the command several time and it's always the same....everytime i have the error!!!!!!!!
And I don't know what to do...
Slevinstar said:
But I launch the command several time and it's always the same....everytime i have the error!!!!!!!!
And I don't know what to do...
Click to expand...
Click to collapse
Please tell me that you are S-Off
tivofool said:
Please tell me that you are S-Off
Click to expand...
Click to collapse
Yes yes, i do all that procedure:
http://forum.xda-developers.com/showthread.php?t=1583427
Slevinstar said:
Yes yes, i do all that procedure:
http://forum.xda-developers.com/showthread.php?t=1583427
Click to expand...
Click to collapse
When you look at your bootloader does it show unlocked and s-off like this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
tivofool said:
When you look at your bootloader does it show unlocked and s-off like this?
Click to expand...
Click to collapse
Yes, it looked like yours befero I lanchued fastboot oem rebootRUU ( the first point on the guide to install the ROM to use 4.2.2 )
Now I've just the HTC logo on the screen..
I tried to launch the command fastboot flash recovery TWRP2.6.1.0.img and it works...
but now i don't know if i restart the phone ( can i restart it?! ) it will work or not?? And can i enter in bootmode??
Slevinstar said:
Yes, it looked like yours befero I lanchued fastboot oem rebootRUU ( the first point on the guide to install the ROM to use 4.2.2 )
Now I've just the HTC logo on the screen..
I tried to launch the command fastboot flash recovery TWRP2.6.1.0.img and it works...
but now i don't know if i restart the phone ( can i restart it?! ) it will work or not?? And can i enter in bootmode??
Click to expand...
Click to collapse
If I read you correct you are on the htc logo screen
I would wait another 10 minutes, the first boot can take some time.
If nothing you would need to restart it and start over. Maybe this time the firmware will flash correctly.
If it does finally boot up, check settings >storage to see that firmware flashed correctly.
excuse me if I don't write so weel...but thank u very much for the support and the patience.
I try to do the point of the situation:
I do all that's write in the guide to install MaximusHD until "2.fastboot flash zip firmware.zip"
when i launch that command it appears the error "FAILED ( remote 99 unknown fail )
I launch more time "fastboot flash zip firmware.zip" but nothing change..so i try to skip this point and launch "fastboot flash recovery TWRP2.6.1.0.img" ...
Now i already have the screen black with only HTC write in the middle...
What can i do??? can i flash an other rom in certain way????
Slevinstar said:
excuse me if I don't write so weel...but thank u very much for the support and the patience.
I try to do the point of the situation:
I do all that's write in the guide to install MaximusHD until "2.fastboot flash zip firmware.zip"
when i launch that command it appears the error "FAILED ( remote 99 unknown fail )
I launch more time "fastboot flash zip firmware.zip" but nothing change..so i try to skip this point and launch "fastboot flash recovery TWRP2.6.1.0.img" ...
Now i already have the screen black with only HTC write in the middle...
What can i do??? can i flash an other rom in certain way????
Click to expand...
Click to collapse
type
fastboot oem rebootRUU
when I installed the rom, I used this post:
http://forum.xda-developers.com/showpost.php?p=45621060&postcount=68
---------- Post added at 01:25 PM ---------- Previous post was at 01:21 PM ----------
And if you are just fed up and want to return to flashing other ROMs
http://forum.xda-developers.com/showpost.php?p=46396024&postcount=2

[Q] Frozen at bootloader, no adb or fastboot

Hello,
I was attempting to clean out (format) everything on my phone and start over with a fresh ROM, and it looks like I went a bit overboard. Now I'm stuck at the bootloader, but it appears to be frozen. When it loads, I get:
Code:
FASTBOOT MODE - NO BOOT OR RECOVERY IMG
PRODUCT NAME - HERRING
HW VERSION - REV 11
BOOTLOADER VERSION - 19020XXLC2
BASEBAND VERSION - 19020XXKI1
CARRIER INFO - TMB
SERIAL NUMBER - (REDACTED)
LOCK STATE - UNLOCKED
The menu appears as well, but I am unable to change the current selection, or perform a selection. (My power button stopped functioning a couple months ago).
Occasionally when I unplug the usb cable I'll see a quick message "USB Control Init USB Control Init End" and it restarts the bootloader. FASTBOOT MODE then just appears empty, and I still cannot access the menu items.
ADB was working before, but now 2 separate computers cannot detect it using "adb devices". I hadn't tried 'fastboot devices' beforehand, but it doesn't detect the phone now.
I tried installing a couple different drivers (Google's, PDANet), and using Wugfresh NRT, but could never connect.
So how's it look, doc? Will it live? Or should I bury it?
Thanks!
Lanik42 said:
So how's it look, doc? Will it live? Or should I bury it?
Click to expand...
Click to collapse
As long as the bootloader isn't deleted there's a good chance.
I think you have deleted the OS and the recovery :silly:
When you are in the bootloader, only fastboot commands work.
Type "fastboot devices" to check the connection
Or "fastboot help"
https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
I had to force the "Google Nexus BootLoader Interface" driver onto the system (win 8.1)
I know it says Acer, but it is my Nexus S
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When fastboot.exe can see your device you can flash a recovery image.
"fastboot flash recovery recovery.img"
"fastboot boot recovery.img"
You should now be able to start the recovery and use the adb commands.
Hope some of this can help
Thanks for the response! I wasn't sure if I would even get a reply, as the board appears to be rather quiet.
Lar5 said:
As long as the bootloader isn't deleted there's a good chance.
I think you have deleted the OS and the recovery :silly:
Click to expand...
Click to collapse
Yeah, I'm afraid I did. I got a little overly aggressive in my data purge
Lar5 said:
When you are in the bootloader, only fastboot commands work.
Type "fastboot devices" to check the connection
Or "fastboot help"
Click to expand...
Click to collapse
Sadly, therein lies my problem. I haven't been able to get fastboot to recognize my device, at all
Lar5 said:
I had to force the "Google Nexus BootLoader Interface" driver onto the system (win 8.1)
I know it says Acer, but it is my Nexus S
View attachment 2936108
When fastboot.exe can see your device you can flash a recovery image.
"fastboot flash recovery recovery.img"
"fastboot boot recovery.img"
You should now be able to start the recovery and use the adb commands.
Hope some of this can help
Click to expand...
Click to collapse
I tried the driver install listed, and I assume it successfuly installed, though I'm not sure how I'd check. but I'm still having the same problem. neither fastboot nor adb recognize the device (though as you said, adb wouldn't at this stage either way).
It doesn't appear that it's even showing up in the device manager (using Windows 7 x64). No search for drivers, no unrecognized device, nothing
I'm afraid it means that my phone is actually freezing during the bootloader loading, since the computer does not appear to recognize it and I can't navigate its menu.
Is there anything I'm forgetting? I may try booting into a Linux live image, to see if windows is just ignoring due to some driver issue. Will follow up with those results.
Thanks again!
I suggest removing all drivers. Each and every trace of it to be removed. Then install the Google USB drivers.
You can also get drivers from Windows Update...

Bootloop

Bootloop
Hi there, i was on cm7, than i found this rom "Desire XS version 1.1" and I decided to install it, after aroma installation, I rebooted it and now i'm in bootloop and i can't access to hboot, what should I do?
Hi, I assume you are s-on with unlock bootloader? If yes, then enter fastboot(if my memory serves me right, hold vol down and power on). The instructions can be found here. I assume u have already wipe/format and flash the rom, so the next thing to do is flash the boot.img in fastboot, found in the link, step 4.
Thank you for your reply, but i think that i can't access to fastboot
evilken9555 said:
Thank you for your reply, but i think that i can't access to fastboot
Click to expand...
Click to collapse
pull the battery out for a min then put back in, u should be able to boot into bootloader then select fastboot in the menu
Got an update :
Both of the suggestions didn't work, so i've tried to connect my phone to a PC and tried to use adb to access into fastboot mode, once I've got into fastboot I've tried to install the stock firmware through ruu, but I get an error : USB error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
#Fear said:
Hi, I assume you are s-on with unlock bootloader? If yes, then enter fastboot(if my memory serves me right, hold vol down and power on). The instructions can be found here. I assume u have already wipe/format and flash the rom, so the next thing to do is flash the boot.img in fastboot, found in the link, step 4.
Click to expand...
Click to collapse
i can't find boot.img :|
edit: i've found the boot.img, now the problem is that when i connect my phone to the pc when it is in fastboot mode, after a bit a notification with a yellow exclamation mark appears and says "Usb device not recognized", i have windows 8.1, could it be the problem?
evilken9555 said:
i can't find boot.img :|
edit: i've found the boot.img, now the problem is that when i connect my phone to the pc when it is in fastboot mode, after a bit a notification with a yellow exclamation mark appears and says "Usb device not recognized", i have windows 8.1, could it be the problem?
Click to expand...
Click to collapse
the ruu wont work coz ur bootloader is "unlocked". u need to relock it then run the ruu. and yes windows 8 is a problem with fastboot, theres a few guides here on xda how to use fastboot with windows 8. so either find a way to get fastboot working then flash custom rom in recovery then flash the boot.img via fastboot or relock the bootloader (ul need fastboot commands working for that too) and then run ur ruu. either way, get fastboot working first.
jmcclue said:
the ruu wont work coz ur bootloader is "unlocked". u need to relock it then run the ruu. and yes windows 8 is a problem with fastboot, theres a few guides here on xda how to use fastboot with windows 8. so either find a way to get fastboot working then flash custom rom in recovery then flash the boot.img via fastboot or relock the bootloader (ul need fastboot commands working for that too) and then run ur ruu. either way, get fastboot working first.
Click to expand...
Click to collapse
thank you for your support guys, i'll try this in the afternoon =).
I wanted to thank you so much guys, thank you for your help and kindess, i've finally installed the original sense rom =).
Have a good day!

Help Moto G stoping in "Warning BootLoader"

Hello guys! I'm on a G 2015 bike to find a way around it. Good tried the procedures without unlocking the bootloader, but without success! Then I went and I was able to unlock Bootloader and repeat the process to install Roo Stock. But to no avail as well. Does anyone have any tips for solving this problem?
I would guess it stops in bootloader because it doesn't like the rom you've flashed.
Did you flash TWRP?
Boot to TWRP and clean flash something else.
Else flash TWRP and then do that.
Hi there! I had the same problem, but the solution was just wait. It took a full 5 minutes to boot since the warning appeared, but it worked fine. Give it a try, wait 5 minutes (literally) and see what happens. If it still stuck, then try the solution above.
KrisM22 said:
I would guess it stops in bootloader because it doesn't like the rom you've flashed.
Did you flash TWRP?
Boot to TWRP and clean flash something else.
Else flash TWRP and then do that.
Click to expand...
Click to collapse
Hi. I tried to do the way you said it, but it did not work. Take a look at the picture
I follow this GUIDE for install
https://forum.xda-developers.com/moto-g/general/guide-custom-recovery-moto-g-xt1033-t2972905
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I don't think your bootloader is unlocked.
Have you unlocked your bootloader using the Motorola site? No other method will work.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
which recovery are you using - copy/paste full module name.
The bootloader has been unlocked by the motorola website! When I insert the cell phone, the message appears that the bootloader is unlocked.
Jdoria said:
The bootloader has been unlocked by the motorola website! When I insert the cell phone, the message appears that the bootloader is unlocked.
Click to expand...
Click to collapse
"when you insert the cell phone" into what?
EDITED POST FOR WINDOWS:
for windows I think type cmd in search bar, right click on cmd.exe and choose administrative (you may have to enter a password) and do everything in that window.
fastboot flash recovery twrp.img
but first tell me exactly which twrp you are using - one is bad.
Better than that just grab the latest from squid and use that. I know it's good.
When it flashes successfully, DO IT AGAIN - don't ask why, just do it - same command.
THEN boot to TWRP and backup your stock if you still have one.
Then and only then, wipe and flash whatever your heart desires.
@Jdoria Please attach the output of "fastboot getvar all"
@KrisM22 "sudo" wont do anything, this is WINDOWS, not Linux.
acejavelin said:
@Jdoria Please attach the output of "fastboot getvar all"
@KrisM22 "sudo" wont do anything, this is WINDOWS, not Linux.
Click to expand...
Click to collapse
Yeah I put a note at the bottom of that post for that. My bad.
Hi I ran cmd.exe in managed mode. Is there any method to format the data of the phone and install everything from scratch?
Jdoria said:
Hi I ran cmd.exe in managed mode. Is there any method to format the data of the phone and install everything from scratch?
Click to expand...
Click to collapse
You need to run it in administrative mode.

Categories

Resources