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
Related
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
Hi and sorry if I am misplacing this question.
I have been trying for hours to get my phone to "S-Off" without any luck.
I have gone over 10-15 different tutorials but none of them work.
Htc One
HBoot 1.55
Anyone who knows a proper guide to the entire unlock/root/s-off procedure?
I can't watch the youtube tutorial due to youtube lag.
Have you tried this tutorial:
http://forum.xda-developers.com/showthread.php?t=2488772
And if so, what errors did you get?
alireza_simkesh said:
Have you tried this tutorial:
http://forum.xda-developers.com/showthread.php?t=2488772
And if so, what errors did you get?
Click to expand...
Click to collapse
Tried this just now (did this a couple of times earlier today aswell) and not much happening.
There is a screenshot attached.
benjamin336 said:
Tried this just now (did this a couple of times earlier today aswell) and not much happening.
There is a screenshot attached.
Click to expand...
Click to collapse
I used to get the same error.
I restarted my laptop (and didn't open or use anything else but just ran the script) and the problem was solved.
Apparently, there was another application that was using adb in the background and was not killed, so after restarting my laptop i didn't get this error anymore.
alireza_simkesh said:
I used to get the same error.
I restarted my laptop (and didn't open or use anything else but just ran the script) and the problem was solved.
Apparently, there was another application that was using adb in the background and was not killed, so after restarting my laptop i didn't get this error anymore.
Click to expand...
Click to collapse
Did this and came further though now it tells me to download a newer version even though I have the latest one.
Am I missing something?
benjamin336 said:
Did this and came further though now it tells me to download a newer version even though I have the latest one.
Am I missing something?
Click to expand...
Click to collapse
Hmm not quite sure, but can you write all the information shown on your bootloader?
Make sure you keep the screen alive during the process and hit allow when super user permissions are requested.
Same happened to me, because i let the screen turn off and rum runner couldnt get su.
AlwaysDroid said:
Make sure you keep the screen alive during the process and hit allow when super user permissions are requested.
Same happened to me, because i let the screen turn off and rum runner couldnt get su.
Click to expand...
Click to collapse
Placed autosleep to 30 min, watched the screen carefully and saw that SU was granted twice.
Same message came up again.
Code:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.62.401.1
eMMC-boot 2048MB
Oct 17 2013,23:06:14.0
That's all the info in bootloader.
Love how they define this as "tampered", in my opinion this is for the better not worse
Any thoughts anyone?
Tried at work today and got the following messages up, does anyone have a clue what this is about?
{
"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 news on this matter?
This stock sense rom is killing me...
Sent from my HTC One using xda app-developers app
which ROM/Kernel are you running? I find it works best if you flash a stock 4.1.2 ROM and the kernel included with moonshine.
I had the same problem with hboot v1.55
after a sleepless night i was able to do s-off
but..... don't really know how i did it: D
iiNFAMOUS CHRiS said:
which ROM/Kernel are you running? I find it works best if you flash a stock 4.1.2 ROM and the kernel included with moonshine.
Click to expand...
Click to collapse
Code:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.62.401.1
eMMC-boot 2048MB
Oct 17 2013,23:06:14.0
This is what I have.
I have been trying every god damn instruction out there and every one-in-all toolkits, it just wont work...I really hate this phone. Id rather use my HOX though the battery life is equal to a 90 year old guy sexlife...
/dev/null/ said:
I had the same problem with hboot v1.55
after a sleepless night i was able to do s-off
but..... don't really know how i did it: D
Click to expand...
Click to collapse
How would you concider another sleepless night just to figure out how you did it?
You know Red Bull give you wings!
Windows 8.1?
benjamin336 said:
How would you concider another sleepless night just to figure out how you did it?
You know Red Bull give you wings!
Click to expand...
Click to collapse
Dude, rumrunner on Ubuntu Live USB: http://forum.xda-developers.com/showthread.php?t=2606577
(no need to install, just use the "Try Ubuntu")
here's a practical result: http://forum.xda-developers.com/showpost.php?p=49673069&postcount=46 (check the summary of what was used)
nkk71 said:
Dude, rumrunner on Ubuntu Live USB: http://forum.xda-developers.com/showthread.php?t=2606577
(no need to install, just use the "Try Ubuntu")
here's a practical result: http://forum.xda-developers.com/showpost.php?p=49673069&postcount=46 (check the summary of what was used)
Click to expand...
Click to collapse
I simply dont understand how Ubuntu works, I cant get any of the commands to work from the terminal.
Extract the archive
tar -zxf rumrunner<device>_<version>.tgz (Linux)
Click to expand...
Click to collapse
Nothing happens, though I can easily extract it within the folder without using the terminal.
Execute soju: linux: sudo ./soju
Click to expand...
Click to collapse
./soju: No such file or directory
Is there a guide for Linux dummies somwhere?
@ kamilmirza, I use Windows 7. [well normally, now I am on Ubuntu]
benjamin336 said:
Any news on this matter?
This stock sense rom is killing me...
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I've chosen an old post to quote, but you do know you don't need to be s-off to flash a custom rom don't you?
cr1960 said:
I've chosen an old post to quote, but you do know you don't need to be s-off to flash a custom rom don't you?
Click to expand...
Click to collapse
I have tried to flash MIUI but whenever I start the installation it tells me it cant get access to the right directory.
Isnt this what S-Off grants you?
*Sorry for the sloppy english but Ubuntu has a completely different keyboard layout at the moment then what I am used to*
Hello guys, first of. Sorry if this was answered a million times already.
Second, I have an issue I've been trying to solve for 3 days now.
3 days ago I was trying to flash a new ROM to my already-rooted HTC One (M7).
I copied all the files as usual and before I flash the new ROM I went to wipe cache, etc.
The problem is that I retardly wiped my system and "memory card" too...
Now Im stuck with no OS. and since the HTC One doesnt use a SD card, I need to use fastboot to transfer files.
Now my problem is: Files dont transfer...
I tried locking the bin, unlocking it again, I can access my TWRP recovery menu and tried to use Sideload. Nothing works.
I pretty much get stuck with this error:
Code:
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Me\Desktop\Root Files\Root_HTC_One_Sprint>fastboot flash unloc
ktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.012s]
finished. total time: 0.154s
C:\Users\Me\Desktop\Root Files\Root_HTC_One_Sprint>fastboot flash recov
ery philz_touch_6.08.9-m7spr.img
sending 'recovery' (9552 KB)...
^ The above is just an example of me trying to install a new recovery, but same thing applies to "push files" and so on...
Ive done my homework and the only conclusion I can draw from all these hours of frustration is that my phone, somehow disabled USB debugging. Therefore the files cannot be copied.
:::EDIT:::
Oh, I forgot to add. I also followed the guides from: http://qbking77.com/development/how-to-unrootunbrick-the-htc-one-to-stock-2/
As I go trough the steps I get an error after running the step #3 into installing the RUU (6:00 onto the video). After I get the "Verifying phone if its connected to PDA..." I get an error that says "Your phone battery is lower than 30%, please charge your phone and try again". But the thing is that my phone is at 100% battery.
Also, the information on my phone itself is:
Code:
***TAMPERED***
*** RELOCKED ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-1.00.20.1108
OpenDSP-32.120.274.0909
OS-
eMMC-Boot 2048MB
Feb 25 2014,21:52:07.0
FASTBOOT USB
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Please help. Thanks:crying:
What RUU are you attempting to install? If it is the one Tim has on his website it is way too old.
Sent from my HTCONE using Tapatalk
prezmater said:
What RUU are you attempting to install? If it is the one Tim has on his website it is way too old.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Same thing happened to me, turns out I was using an outdated RUu. Make sure it is the latest one.
I personally updated my hboot and installed the latest RUU available and then updated my phone. But I wasn't interested in getting s-off, I just wanted a stock phone.
prezmater said:
I personally updated my hboot and installed the latest RUU available and then updated my phone. But I wasn't interested in getting s-off, I just wanted a stock phone.
Click to expand...
Click to collapse
I cant find anywhere the latest version though.
The only version I find is version: 3.04.651.2
I cant find any other except older ones.
:::EDIT:::
I also used the 2 versions from sprint posted on this site: http://www.htc1guru.com/downloads/ruu-file-downloads/
and I still get this error:
Code:
ERROR [120]: MAIN BATTERY POWER
This error message will appear when the Android phone’s battery power is not sufficient (Batter power should be more than 30%). Although RUU will instruct you to plug in the AC adapter, it will still need to make sure that your Android phone has enough power to complete the update. (The Android phone cannot charge the battery when it is connected to the PC while installing the RUU).
Kagerusui said:
I cant find anywhere the latest version though.
The only version I find is version: 3.04.651.2
I cant find any other except older ones.
:::EDIT:::
I also used the 2 versions from sprint posted on this site: http://www.htc1guru.com/downloads/ruu-file-downloads/
and I still get this error:
Code:
ERROR [120]: MAIN BATTERY POWER
This error message will appear when the Android phone’s battery power is not sufficient (Batter power should be more than 30%). Although RUU will instruct you to plug in the AC adapter, it will still need to make sure that your Android phone has enough power to complete the update. (The Android phone cannot charge the battery when it is connected to the PC while installing the RUU).
Click to expand...
Click to collapse
RUU - 3.04.651.2 - http://forum.xda-developers.com/showthread.php?t=2508907
RUU - 4.06.651.4 - http://forum.xda-developers.com/showthread.php?t=2658910
RUU - 5.03.651.3 - http://forum.xda-developers.com/showthread.php?t=2795856
All Credits due to O.M.J. for the posts and those who helped.
EDIT* - I believe with HBOOT 1.56 you would want to use the 5.03.651.3 version, but I would double check.
fryguy503 said:
RUU - 3.04.651.2 - http://forum.xda-developers.com/showthread.php?t=2508907
RUU - 4.06.651.4 - http://forum.xda-developers.com/showthread.php?t=2658910
RUU - 5.03.651.3 - http://forum.xda-developers.com/showthread.php?t=2795856
All Credits due to O.M.J. for the posts and those who helped.
EDIT* - I believe with HBOOT 1.56 you would want to use the 5.03.651.3 version, but I would double check.
Click to expand...
Click to collapse
WOOT! Thanks a lot!. Ill try and update you.
:::EDIT:::
I tried all 3 versions and all 3 of them ran into the same error.
30% Battery error.
My phone its been charging for 4 days now lol, its 100%...
Kagerusui said:
WOOT! Thanks a lot!. Ill try and update you.
:::EDIT:::
I tried all 3 versions and all 3 of them ran into the same error.
30% Battery error.
My phone its been charging for 4 days now lol, its 100%...
Click to expand...
Click to collapse
if you are s-on you'll need the stock recovery( I think) also and have your bootloader locked
Aldo101t said:
if you are s-on you'll need the stock recovery( I think) also and have your bootloader locked
Click to expand...
Click to collapse
My bootloader is locked, I can lock or unlock at will. But its locked.
As far as recovery goes, I have TWRP. How would I go about getting it back to stock recovery without the ability of going back to stock ROM/Recovery ?
Kagerusui said:
My bootloader is locked, I can lock or unlock at will. But its locked.
As far as recovery goes, I have TWRP. How would I go about getting it back to stock recovery without the ability of going back to stock ROM/Recovery ?
Click to expand...
Click to collapse
i'm not quite sure you need stock recovery or not, but you flash it in fastboot the same as twrp. the stock recovery is here in the forums somewhere I can't remember where, maybe someone will chime in here who knows for sure if you need it or not.
Aldo101t said:
i'm not quite sure you need stock recovery or not, but you flash it in fastboot the same as twrp. the stock recovery is here in the forums somewhere I can't remember where, maybe someone will chime in here who knows for sure if you need it or not.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2236418
This might be it. @Kagerusui
StormyNight said:
http://forum.xda-developers.com/showthread.php?t=2236418
This might be it. @Kagerusui
Click to expand...
Click to collapse
Thanks for the reply, I tried flashing this and nothing changed. I was actually using your Viper's ROM prior to me running into this issue >_<!
Anyway, as stated in post #1. This is the error I run into whenever I try to push or flash anything to the 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"
}
This happens with both modes, with Locked OEM and Unlocked OEM.
The "error" is that it can hang there for hours without actually copying anything to the phone. lol
This also applies whenever I try to use TWRP's Sideload. I get the same result: "Sending to x..."
Kagerusui said:
Thanks for the reply, I tried flashing this and nothing changed. I was actually using your Viper's ROM prior to me running into this issue >_<!
Anyway, as stated in post #1. This is the error I run into whenever I try to push or flash anything to the phone:
This happens with both modes, with Locked OEM and Unlocked OEM.
The "error" is that it can hang there for hours without actually copying anything to the phone. lol
This also applies whenever I try to use TWRP's Sideload. I get the same result: "Sending to x..."
Click to expand...
Click to collapse
Have you tried using USB-OTG to flash a ROM? Make sure your bootloader is unlocked before you flash though.
Recovery shouldn't matter because when you install an RUU the recovery is replaced with stock. I don't understand your battery issue though.
---------- Post added at 05:27 PM ---------- Previous post was at 05:25 PM ----------
Don't think it would matter but maybe make sure everything is utd on your SDK manager.
StormyNight said:
Have you tried using USB-OTG to flash a ROM? Make sure your bootloader is unlocked before you flash though.
Click to expand...
Click to collapse
I just ordered the USB adapter from amazon. It will take 3-5 weeks to get here... -_-
In the meantime I hope there is an actual fix to it.
As for the battery error:
After I get this screen:
I get this:
My battery is at 100%
Have you tried another USB cable in the first place?
It could be something as simple as that.
MFOsaka said:
Have you tried another USB cable in the first place?
It could be something as simple as that.
Click to expand...
Click to collapse
+1 I have seen weird issues with poor quality or bad USB cables.
---------- Post added at 06:48 PM ---------- Previous post was at 06:46 PM ----------
Maybe try this:
Unlock the Device
Flash CWM
Recharge the Phone to 100%
Reset Battery Stats (Honestly unsure if the HTC One CWM has this option)
Lock
Flash the stock recovery
Flash the RUU
...
Profit
I tried multiple ports and multiple cables.
While doing troubleshoots I found that adb does seem trying to move them but I get an "Permission Denied error"
Kagerusui said:
I tried multiple ports and multiple cables.
While doing troubleshoots I found that adb does seem trying to move them but I get an "Permission Denied error"
Click to expand...
Click to collapse
try uninstalling and reinstalling your htc drivers on your computer
Aldo101t said:
try uninstalling and reinstalling your htc drivers on your computer
Click to expand...
Click to collapse
I also did that multiple times over
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