I didt the s-off with Revone then ran the Super CID command in fastboot but Something seems off. Not sure If I have super CID becasue it comes up as boot-recovery..
see below.
c:\Android\sdk\platform-tools>fastboot oem writecid 11111111
...
(bootloader) Start Verify: 0
OKAY [ 0.023s]
finished. total time: 0.024s
c:\Android\sdk\platform-tools>adb shell getprop "ro.cid"
boot-recovery
c:\Android\sdk\platform-tools>adb reboot bootloader
c:\Android\sdk\platform-tools>fastboot oem readcid
...
(bootloader) cid: 11111111
OKAY [ 0.012s]
finished. total time: 0.014s
Click to expand...
Click to collapse
Do I have to HEX edit it so it reads correct or is this how it should read?
im pretty sure thats how it should look
Dont think its right..
Cant send out SMS or calls..
Noz85 said:
I didt the s-off with Revone then ran the Super CID command in fastboot but Something seems off. Not sure If I have super CID becasue it comes up as boot-recovery..
see below.
Do I have to HEX edit it so it reads correct or is this how it should read?
Click to expand...
Click to collapse
Get Prop command should be ran when phone is booted up fully, not in fastboot.
---------- Post added at 02:56 AM ---------- Previous post was at 02:53 AM ----------
Noz85 said:
Dont think its right..
Cant send out SMS or calls..
Click to expand...
Click to collapse
Change your fastboot CID back to what it should be untill the issues are ironed out. Hex editing is dangerous, wait for a script. You arent gaining a thing by having supercid for everyday use. If you need to do an update that requires supercid, you can change it in 5 seconds at that time.
nugzo said:
Get Prop command should be ran when phone is booted up fully, not in fastboot.
Click to expand...
Click to collapse
it was.
I was showing what is read in the bootloader and when the phone is live.
nugzo said:
Change your fastboot CID back to what it should be untill the issues are ironed out. Hex editing is dangerous, wait for a script. You arent gaining a thing by having supercid for everyday use. If you need to do an update that requires supercid, you can change it in 5 seconds at that time.
Click to expand...
Click to collapse
I've been trying to Revert back to the ATT CID but no luck.
The CID was changed when I first did it and it became the bootloader-recovery.
When I hex it back to either 11111111 or the ATT CID it doesnt change it.
Now I'm stuck with
C:\Android\sdk\platform-tools>adb shell getprop ro.cid
11111111.....
Click to expand...
Click to collapse
when I look at the rest of the file it seems corrupt to me.
{
"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"
}
Any ideas?
Forget it I got it.
I wasnt repulling the damn file.
This is no where near as simple as Xbox modding lol
Noz85 said:
it was.
I was showing what is read in the bootloader and when the phone is live.
I've been trying to Revert back to the ATT CID but no luck.
The CID was changed when I first did it and it became the bootloader-recovery.
When I hex it back to either 11111111 or the ATT CID it doesnt change it.
Now I'm stuck with
when I look at the rest of the file it seems corrupt to me.
Any ideas?
Forget it I got it.
I wasnt repulling the damn file.
This is no where near as simple as Xbox modding lol
Click to expand...
Click to collapse
Dont you still have the original unchanged un hex 'd version still? You should, just push that back.
The un hex'd version was messed up it read boot-recovery. So I had to do the hex edit to get it working again.
Sent from my HTC One using Tapatalk 2
Noz85 said:
The un hex'd version was messed up it read boot-recovery. So I had to do the hex edit to get it working again.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
I had the same issue with CID [boot-recovery], I tried to change it with HEX to 11111111 in case of i couldn’t call when I change the CID in fastboot to 11111111. CID getter show now [11111111.....] and it doesn't work again. When I change to HTC__001 (fastboot) everything works.
How do you change it from [boot-recovery] into [11111111] without to change the file size?
(Sorry for my bad English)
Edit: I had an issue with the HEX editor, now it works...
Related
Hey XDAers
In Settings-Tell HTC- at the bottom there is a warning that says
This is a test device. Accordingly, to collect critical information about the device, Tell HTC is enabled and cannot be turned off regardless of device settings
I have read this is due to S-OFF or due to custom hboot. Is there any way we can save some battery by disabling this? Can we freeze/uninstall Tell HTC? Any ideas?
{
"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"
}
kazprotos said:
Hey XDAers
In Settings-Tell HTC- at the bottom there is a warning that says
This is a test device. Accordingly, to collect critical information about the device, Tell HTC is enabled and cannot be turned off regardless of device settings
I have read this is due to S-OFF or due to custom hboot. Is there any way we can save some battery by disabling this? Can we freeze/uninstall Tell HTC? Any ideas?
Click to expand...
Click to collapse
search the dev forums, a methods been posted already
Been searching for a day now can't find a clear answer any link/help appreciated thanks
There is a HBOOT modification hack that will remove that red text, but it's dangerous if you forgot you did it. With the modified HBOOT, taking an OTA that installs a new HBOOT will automatically perma brick your device. You have to go back to stock HBOOT before updating any OTA's if you're on stock ROM.
kazprotos said:
Been searching for a day now can't find a clear answer any link/help appreciated thanks
Click to expand...
Click to collapse
it took me less than a minuite...
here you go: http://forum.xda-developers.com/showthread.php?t=2316726
Whist this has gotten rid of the red warning when entering fastboot, I was asking about the red text in the settings->about->Tell HTC and error reporting. Screenshot added.
i read somewhere that the sign is due to s-off and also if u get your device s-on again , the the red writing will go..
i didn't try that
ahmed83 said:
i read somewhere that the sign is due to s-off and also if u get your device s-on again , the the red writing will go..
i didn't try that
Click to expand...
Click to collapse
Correct it's due to s off... I think and I could be very wrong but...devices with s off are seen as engineering devices and such
a box of kittens said:
Correct it's due to s off... I think and I could be very wrong but...devices with s off are seen as engineering devices and such
Click to expand...
Click to collapse
I can confirm that going s-on makes the message go away.
And we can't go S-OFF again on 2.24 base
Dliemna
Problem solved
http://forum.xda-developers.com/showpost.php?p=43397722&postcount=72
kazprotos said:
Problem solved
http://forum.xda-developers.com/showpost.php?p=43397722&postcount=72
Click to expand...
Click to collapse
except that now if you go and press tell htc settings force closes ...
Mine just disappeared, no more Tell HTC button
samflorin said:
I can confirm that going s-on makes the message go away.
Click to expand...
Click to collapse
I'm almost at the last part of reverting. When I type "fastboot oem writesecureflag3" it says not found. Any idea what i'm doing wrong?
You're missing the spacebar
----------------------o('_')o----------------------
Sent from an HTC One using xda app and Bulletproof TrickDroid ROM 8.0
I have the exact same problem - what are the steps to resolve this? Status = locked and S-off.... someone please help!
dark_polok said:
I'm almost at the last part of reverting. When I type "fastboot oem writesecureflag3" it says not found. Any idea what i'm doing wrong?
Click to expand...
Click to collapse
fastboot oem writesecureflag 3 (notice the space)
Also make sure that fastboot is in your $PATH (on *UX) or %PATH%. You can try going to the folder (in command line) where fastboot resides before running the above command. The problem may be that you get "Device not found", case in which you have not selected "fastboot" from the menu (which seems to be the case of @rt1990 ). The menu should read "fastboot usb" i believe before writesecureflag will work.
Warnings:
1. Make sure that your hboot is stock! S-ON on custom hboot = you're screwed (brick).
2. If you upgrade to 4.2.2 you won't be able to get S-OFF back since the updated hboot does not currently work with revone!
3. Before S-ON run again revone -t to remove tampered flag (just in case)
3. If you have "TAMPERED" appearing after s-on/bl locked you must run a RUU for your device to make it go away (i have it and there is no 4.2.2 RUU that i can run to confirm this though)
What i'd suggest you is to take the advice and remove the damn apk from system and tell htc will completely go away. I could afford going back to S-ON/Locked BL because i won't run any custom roms. I have rooted my device but i have no use for root either
---------- Post added at 12:37 PM ---------- Previous post was at 12:35 PM ----------
See my above post.
---------- Post added at 12:38 PM ---------- Previous post was at 12:37 PM ----------
From @kazprotos' post above (quoting from the link he posted): Regarding Tell HTC app, delete the Udove.apk in system/apps.
i have the same message...are there any different methods to root it or same method as others?
athulpmenon said:
i have the same message...are there any different methods to root it or same method as others?
Click to expand...
Click to collapse
Read the post above you. removing the apk is the best way to get rid of the Tell HTC message if you want to stay S-OFF.
It's already solved.
Please see this:
http://forum.xda-developers.com/showthread.php?t=2488696
My phone is Hboot 1.13 with S-OFF already.
This is what is shown when I press volume down+power
VIVO PVT SHIP S-OFF RL
HBOOT - 1.13.0000
RADIO-3805.04.03.27_M
eMMC-boot
Apr 1 2011, 18:34:39
How do I root it and install custom recovery in this? Please guide.
moomal said:
My phone is Hboot 1.13 with S-OFF already.
This is what is shown when I press volume down+power
VIVO PVT SHIP S-OFF RL
HBOOT - 1.13.0000
RADIO-3805.04.03.27_M
eMMC-boot
Apr 1 2011, 18:34:39
How do I root it and install custom recovery in this? Please guide.
Click to expand...
Click to collapse
Reboot to fastboot.
Flash custom Recovery.
Flash superuser script.
Flash whatever ROM.
The specifics of how to do those 4 above steps should be in every guide. Just search the guide a bit
072665995 said:
Reboot to fastboot.
Flash custom Recovery.
Flash superuser script.
Flash whatever ROM.
The specifics of how to do those 4 above steps should be in every guide. Just search the guide a bit
Click to expand...
Click to collapse
Thanks a lot
072665995 said:
Reboot to fastboot.
Flash custom Recovery.
Flash superuser script.
Flash whatever ROM.
The specifics of how to do those 4 above steps should be in every guide. Just search the guide a bit
Click to expand...
Click to collapse
I tried to flash through my PC. But it says Failed (Not allowed) Can you tell what the problem might be?
moomal said:
I tried to flash through my PC. But it says Failed (Not allowed) Can you tell what the problem might be?
Click to expand...
Click to collapse
How can i fix your problem if i IBT even know what's wrong??
Can you post a screenshot of the cmd ??
Sent from my Incredible S using xda app-developers app
072665995 said:
How can i fix your problem if i IBT even know what's wrong??
Can you post a screenshot of the cmd ??
Sent from my Incredible S using xda app-developers app
Click to expand...
Click to collapse
{
"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"
}
moomal said:
Click to expand...
Click to collapse
i guess it doesn't work with win8. Try running cmd with admin rights. if fails then. try with Win7
mafie said:
i guess it doesn't work with win8. Try running cmd with admin rights. if fails then. try with Win7
Click to expand...
Click to collapse
Tried that too. Still won't work
moomal said:
Click to expand...
Click to collapse
windows 8 might be a bit different. Search a bit online.
Also search in google "writing recovery FAILED"
I'm sure other people have had this problem before.
072665995 said:
windows 8 might be a bit different. Search a bit online.
Also search in google "writing recovery FAILED"
I'm sure other people have had this problem before.
Click to expand...
Click to collapse
Can't find any for Incredible s.
mafie said:
i guess it doesn't work with win8. Try running cmd with admin rights. if fails then. try with Win7
Click to expand...
Click to collapse
My phone is refurbished and it's still on Android 2.3.3 (It won't update) In case it helps.
Okay. This is a stupid question.. but just in case.. is your bootloader locked or unlocked?? I feel something is wrong there..
The same happened with one of my friend too..
Sent from my HTC Incredible S
moomal said:
Click to expand...
Click to collapse
Were you able to flash anything? Mine says hboot 1.13 too but no locked or unlocked water mark with S-OFF but when I type in commands it sayas I cant. Did you fix it? I dont even have a custom recovery or rom. It's just dead
cowboysgz said:
Were you able to flash anything? Mine says hboot 1.13 too but no locked or unlocked water mark with S-OFF but when I type in commands it sayas I cant. Did you fix it? I dont even have a custom recovery or rom. It's just dead
Click to expand...
Click to collapse
Just run revolutionary. Flash custom recovery. Flash Superuser script and you're good to go.
Also stop posting the same issue multiple times. Its possibly the easiest way to piss another XDA member off. Post once about your issue in the general forum and DO NOT post again somewhere else.
cowboysgz said:
Were you able to flash anything? Mine says hboot 1.13 too but no locked or unlocked water mark with S-OFF but when I type in commands it sayas I cant. Did you fix it? I dont even have a custom recovery or rom. It's just dead
Click to expand...
Click to collapse
Yes I was able to do it. Since it's S-OFF but still unlocked so it won't allow you. So I followed this link:
http://forum.xda-developers.com/showthread.php?t=1591729
It would do it for sure
Hello. After tons of tries, I finally achieved S-OFF so I was going to try to turn my phone into a GPe by using RUU. Everything was going fine, the install failed once like it should, but then, my phone just couldn't get found by my computer, I unplugged it, plugged it back, and when on fastboot, the pc won't recognize the device. Also, now I'm getting this when I boot into fastboot
{
"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"
}
, BTW, I've been reinstalling drivers like crazy for like an hour now, nothing seems to work, when I boot the phone normally, it does find it though, any help? Thanks.
For starters you still need the correct cid or supercid to flash RUUs...
xcesivemastub8ah said:
For starters you still need the correct cid or supercid to flash RUUs...
Click to expand...
Click to collapse
I followed this tutorial http://forum.xda-developers.com/showthread.php?t=2358781 I had the correct CID and MID.
haZethew0rld said:
I followed this tutorial http://forum.xda-developers.com/showthread.php?t=2358781 I had the correct CID and MID.
Click to expand...
Click to collapse
Yea. That tutorial is very clear about hand holding for a reason... It's very vague That's why there are tons of other guides.
Your bootloader needs to be locked to flash ruu.zips unless it's the specific one that matches your cid and you're s-off. From the pic it says you're unlocked and your cid is tmobiles cid not the Google plays cid. Also you said you can reboot fine. That means you never flashed anything. Consider yourself lucky. Unplugging and rebooting on certain errors while in ruu mode can easily lead to a bricked phone. Don't do that unless you know exactly what your error is.
xcesivemastub8ah said:
Yea. That tutorial is very clear about hand holding for a reason... It's very vague That's why there are tons of other guides.
Your bootloader needs to be locked to flash ruu.zips unless it's the specific one that matches your cid and you're s-off. From the pic it says you're unlocked and your cid is tmobiles cid not the Google plays cid. Also you said you can reboot fine. That means you never flashed anything. Consider yourself lucky. Unplugging and rebooting on certain errors while in ruu mode can easily lead to a bricked phone. Don't do that unless you know exactly what your error is.
Click to expand...
Click to collapse
Thanks for the info, so pretty much all I need to do is lock the bootloader and change the cid? also, by locking the bootloader, does that fix the connection issue? cause I can't get fastboot usb to get detected by my pc, every time it says the device malfunctioned or something.
EDIT: Just locked the bootloader, I still can't get fastboot to work.
EDIT 2: I tried fastbook on a Mac and it worked right away, was able to change CID. Now I'll attempt to flash the RUU.
EDIT 3: SUCCESS! A mod can please close this thread now.
haZethew0rld said:
Thanks for the info, so pretty much all I need to do is lock the bootloader and change the cid? also, by locking the bootloader, does that fix the connection issue? cause I can't get fastboot usb to get detected by my pc, every time it says the device malfunctioned or something.
EDIT: Just locked the bootloader, I still can't get fastboot to work.
EDIT 2: I tried fastbook on a Mac and it worked right away, was able to change CID. Now I'll attempt to flash the RUU.
EDIT 3: SUCCESS! A mod can please close this thread now.
Click to expand...
Click to collapse
simply change the title to [SOLVED]blabla
hey guys
i have rooted device with ٍSuper CID + S-off + Flased stock recovery + Odexed Rom From revlation HD so i receive update and i download it then its show that msg any solo for that
{
"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"
}
sadeg111 said:
hey guys
i have rooted device with ٍSuper CID + S-off + Flased stock recovery + Odexed Rom From revlation HD so i receive update and i download it then its show that msg any solo for that
Click to expand...
Click to collapse
i am back to stock CID now triying to make update
Post your fastboot getvar all please, make sure you remove your imei and serial number before posting.
sadeg111 said:
i am back to stock CID now triying to make update
Click to expand...
Click to collapse
variant system version error is caused by MID not matching the ota. So you will have to change your MID to match the version you are on.
OTA Sense6 not installing with SuperCID 11111111!
Hi Guys,
I think the CID-change will do you good. I tried for several hours to get the OTA-applied, however, only after I changed my CID from 11111111 to "HTC__001" the update finally applied. Before that I only got "assert failed". What's strange:
In the updater-script the CID "11111111" is "regarded" in theory, however, it did not work for me! Maybe there's a bug in the code like Apple's "Goto fail"-bug?
For everyone having issues with the Sense6-OTA: CHANGE YOUR CID TO "HTC__001" (thats two underscores __, CID is always 8-digit). Took me really several hours, I found it strange that I didn't see this anywhere mentioned.
Greetz,
Hallu
so i should change my MID OR NOT ?
???
It wouldn't hurt to change it, but must be the same as the one in the ota, you can find out what that is by finding the ota download on your phone, it's a zip file, open it and in there you will see another zip called firmware.zip open that and there should be android-info.txt open it, opens in notepad, it will say what cid and mid it supports.
Seanie280672 said:
It wouldn't hurt to change it, but must be the same as the one in the ota, you can find out what that is by finding the ota download on your phone, it's a zip file, open it and in there you will see another zip called firmware.zip open that and there should be android-info.txt open it, opens in notepad, it will say what cid and mid it supports.
Click to expand...
Click to collapse
is there any other way to know CID & MID for OTA except that why /? cuz when download done the file deleted and can't to extrart it to know -_-
sadeg111 said:
is there any other way to know CID & MID for OTA except that why /? cuz when download done the file deleted and can't to extrart it to know -_-
Click to expand...
Click to collapse
It shouldn't delete it unless it installs it, when its downloaded, select install later, it should just sit on your internal memory.
well see almost done with downloading
hi
needed to revert my m7 back to stock for repair.
went from S-On to off. locked the bootloader, removed the "tempered". everything went okay
and then i tried going back to S-ON using this command --> fastboot oem writesecureflag 3
and now this is my phone
{
"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"
}
no matter what i click i cant leave bootloader, please please help me, WILL DONATE to whoever helps me out of this.
thanks
ps. found this thread, not very helpful though as it is for EVO 3D and with linux http://forum.xda-developers.com/showthread.php?t=1627897
SultanAlush said:
hi
needed to revert my m7 back to stock for repair.
went from S-On to off. locked the bootloader, removed the "tempered". everything went okay
and then i tried going back to S-ON using this command --> fastboot oem writesecureflag 3
and now this is my phone
https://fbcdn-sphotos-h-a.akamaihd...._=1414465116_f9731b2ccfdfdceab9769399b7cafa6b
no matter what i click i cant leave bootloader, please please help me, WILL DONATE to whoever helps me out of this.
thanks
ps. found this thread, not very helpful though as it is for EVO 3D and with linux http://forum.xda-developers.com/showthread.php?t=1627897
Click to expand...
Click to collapse
Did you do the final step and flash the RUU to the phone ?
this one should work >> http://www.androidruu.com/getdownlo...10.38r.1157.04L_release_353069_signed_2-1.exe
clsA said:
Did you do the final step and flash the RUU to the phone ?
this one should work >>
Click to expand...
Click to collapse
i stupidly tried going back to s-on before flashing the ruu
will this work now that i am S-ON and Locked?? and cant get out of the bootloader
SultanAlush said:
i stupidly tried going back to s-on before flashing the ruu
will this work now that i am S-ON and Locked?? and cant get out of the bootloader
Click to expand...
Click to collapse
yes just flash it from the screen in the pictures
plug the phone into the pc first
clsA said:
yes just flash it from the screen in the pictures
plug the phone into the pc first
Click to expand...
Click to collapse
do you mind just quickly telling me how to exactly do that? my first time..
and of course everything will be deleted right?
and i noticed the ruu says sense 5.5, im on sense 6 if that matters.
SultanAlush said:
do you mind just quickly telling me how to exactly do that? my first time..
and of course everything will be deleted right?
and i noticed the ruu says sense 5.5, im on sense 6 if that matters.
Click to expand...
Click to collapse
According to the OS in your bootloader screen you are on JB 3.62.401.1 the RUU provided is a higher version than what is presently on your phone. Since, you are S-ON you can only run an RUU that is the same or higher than your OS. Yes, it may wipe your information.
Connect your PC to your phone via the USB cable
Double-click the RUU.exe file on your computer
Follow the on-screen instrutions