I don't know where to begin. This is actually a couple of issues I'm experiencing with my AT&T HTC One. First, I cannot for the life of me get this thing to S-Off. I've tried Firewater (both methods) and I keep getting the same error, "welp this sucks Firewater can't work on your device, no amount of flashing, RUUing, etc. Tried Rumrunner, won't work. I've set SuperSu to grant default access, trust system user. I've also tried having those boxes unchecked. I've noticed I never get the RSA permission pop up on my phone (running ARHD 71.1, tried 31.6, 13.4, and 40.3). I have also tried Cyanogenmod 11, and 10.2.1. I've tried different USB cables, disabling virus protection, NOTHING will work. I'm thinking it could be the date the phone was built. I have a newer HTC One M7. I've tried every firewater method I could find by simply searching around the internet to no avail. Finally, I thought I would try going back to stock completely and start the process again, but when I go to get my OS number to get the proper download file, it shows up as blank. There's nothing there and when I go to the bootloader, next to OS where it would say 4.20.5(don't know the rest) there's nothing there. I'm not sure how that's possible. But if ANYONE can help me I would greatly appreciate it. I've run out of ideas, I just want to S-Off so I can convert my phone to a Google Play Edition. I managed it with my last HTC One but got rid of it like an idiot and now I'm paying the price.
Related
I'm having problems and I can't find any info that I haven't already tried...
The fist time I tried the new root method, with the batch file, it worked fine and I got root coming from 2.1v3, but then when messing around with different roms and such I believe I managed to screw something up.
I ended up doing a regular hboot back to 2.1v3 and I think I lost root. I can't get back to the recovery menu.
So I was thinking I could just rerun the runindos.bat but now when I run the command nothing happens on the phone. It looks like it's working on the command prompt, but nothing happens on the phone, no reboots, nothing.
Any suggestions? If you need more info, let me know what you need, but I've tried all different things and cant get it to work..
I need to know before I go to Sprint tomorrow... Thanks
(Oh, and I have a Hero)
Hard Resetting on a Official ROM, don't know if it would work.
But you could try to install some apps that needs root to work, to test if you either have it or not.
If you want to be on the safe side, download a RUU updater that installs your phone all over again.
Then it becomes like the day you bought it.
I don't think it will. If you flash an official RUU from your carrier that will get rid of it. (look on the Sprint site)
I tried that.. with this one..
http://forum.ppcgeeks.com/showthread.php?t=103776
but it would not work.. had the same problem other people had (through the comments).. but no fix was ever suggested, so I just hard reset it..
PROBLEM: "hey got a questions for anyone that could help me out. i cant get the RUU to see my Hero...? it just gives this error: "ERROR[170]: USB CONNECTION ERROR" but its conneted. and ive tried it both just plugging it in and by mounting it. but both dont work. any help would be greatly appreciated."
Does anyone know a different link to one or how to get this one to work?
http://support.sprint.com/support/a...n_your_HTC_Hero/case-gb746811-20091009-155624
Will this one work, then?
The 170 error is when the RUU updater can't get a connection to the Phone.
Have you installed HTC Sync? Or some other drivers for the Hero?
I had the same problem with the Sprint RUU download... kept telling me it wasn't connected.
Then I was messing with it and I manually pressed sync on the phone and then tried to install the RUU and it worked perfect.
So, I guess it was just that I needed to manually press sync.
Anyway, I did it.. it's on my phone... so does that mean the root is off?
If the RUU installation went fine, and finished.
Then you don't got root on your hero anymore.
lol ok.. just making sure!
Thanks for the help
No problem.
Evening all,
I have been advised to post here on XDA from Android Forums. This is a copy of my initial post on there to explain the background to my issue.....
Hi there,
I have HTC Desire from O2 and after 12 hours of online searching and tweaking I'm hoping someone may be able to help.
I received the OTA upgrade yesterday which I accepted because I thought O2 might have it sorted by now. Obviously not. Anyway update ran with no interruption but then rebooted to a frozen O2 screen.
I searched the net and eventually found the guide to update the phone using the RUU Rom. I followed this to the letter and the installer for the RUU wouldnt't open. I then realised that Google Chrome hadn't fully downloaded the file (113mb not 171mb). I then used a download manager to ensure I had the full file. It then ran and seemed to be working... until 80% in when I get ERROR 110 File Open.... please use a complete RUU. I downloaded it several more times in various ways but still same result. By this point my phone was pretty much bricked.
I had black screen with silver HTC logo in the middle and 4 exclamation marks in the corners.... this remained whilst the phone was plugged in and the buttons in any combination did nothing. When i removed the USB cable i got a white boot screen with RUU highlighted in orange and again.... buttons do nothing. Every time I ran the RUU file it brought up a green bar as if it was making progress but then errors at the same point every time. (Error 110 use complete RUU... file seems to be complete now at 171mb)
I tried it on two computers, one win7 and the other vista. The vista machine doesn't even see the phone, it gives a USB error before the update begins.
At 2am I used the SDK download and typed the following at command prompt.... "fastboot oem boot".... phone instantly boots into O2 Froyo and works fine. If i then unplug the phone, turn it off and on again.... i get the black HTC screen again, back to square one.
At the moment I have fastbooted it so its working and have used the goldcard tool to obtain the CID and created the .img file.
I don't know what to do from here!!.... the update obviously hasn't FULLY worked but it must have completed enough for the thing to fastboot and seems to have full functionality (calls, wireless, network etc)
I don't really want to void the warranty but O2's only option is to send it off for 14 days to have an engineer tell me its buggered and send a replacement.
Any advice is appreciated.
Rich.
A couple of helpful guys on there have tried to advise me but without success. They suggested rooting etc but here is my problem.....
At the moment the phone seems to be working fine with Froyo... but the only way I can get my phone to start up is by plugging in and running "fastboot oem boot" from command prompt. If my phone is powered off and I turn it on in the normal way, I get the black screen with silver 'HTC' and triangles in 4 corners and all buttons do nothing!
I have tried fastboot command whilst holding down the volume keys etc and it just boots normally. Obviously something isn't right and I can't let my battery run down otherwise its useless until I can fastboot it again.
So this is preventing me from accessing any of the menu's required in the flash/root tutorials.
Can anyone help or do I just need to ensure I don't run the battery down?!?
Thanks in advance
Rich
if you have a goldcard already, have you tried flashing a diffrent ruu from fastboot? maybe just a generic htc one rather than the o2 one?
Hi,
Thanks for your reply.
Could you advise me which RUU would be the best to use?
I have looked through the list on shipped-roms website but apart from the obvious O2 ones, I don't understand which ones are which!
Thanks
Rich
Hi Rich,
I have exactly the same problem. Have you got any feedback about whether you have solved this issue?
Thanks!
Kelk
Edit:
I think I may have got it sorted. Downgrade to 2.1 as per:
hxxp://forum.xda-developers.com/showthread.php?t=768256
(replace xx to tt in link above)
Hi there,
I haven't solved my issue yet. At the moment I am using my phone on 2.2 but trying not let the battery run flat (I have to use fastboot from command prompt to get my phone to boot up)
Did the tutorial above work for you?
My issue is getting a working goldcard. I'm not sure whether mine has worked succesfully because when i've tried running the RUU of either the unbranded froyo update or even the O2 original, i get and error message and it doesn't work.
I followed the goldcard creation tutorial but I still get the CID error when trying to run the various RUU files.
I hope I can sort this soon because i've been close to throwing my phone out of the window several times!!
Cheers
Rich
Hi Rich,
Yes, the above tutorial worked for me. I think this is because it downgrades to a former version of HBOOT.
rich0684 said:
Hi there,
I haven't solved my issue yet. At the moment I am using my phone on 2.2 but trying not let the battery run flat (I have to use fastboot from command prompt to get my phone to boot up)
Did the tutorial above work for you?
My issue is getting a working goldcard. I'm not sure whether mine has worked succesfully because when i've tried running the RUU of either the unbranded froyo update or even the O2 original, i get and error message and it doesn't work.
I followed the goldcard creation tutorial but I still get the CID error when trying to run the various RUU files.
I hope I can sort this soon because i've been close to throwing my phone out of the window several times!!
Cheers
Rich
Click to expand...
Click to collapse
Use Goldcard + your shipped o2 ROM (ROM that came originally with ur phone 1st time). you can get the rom from HTC official website. enter your Serial Number t download (i recommend using Mozilla built in download manager, coz Google Chrome always give me Corrupted Download when downloading Large files)
This is my third Android phone and fifth Android device. I've rooted all five and installed multiple ROMs and for the most part have not had too many problems.
I'm currently running Elegancia 5.3.0 on my AT&T One X+ and have a few issues that I'm tired of dealing with. I decided to flash the RUU to go back to stock and also to update to hboot 1.4 which is required for the Blackout ROM I was thinking about trying. The RUU cannot find my phone unless I connect while in the bootloader. Even then though, the RUU flash still fails. Since it cannot see my phone while it's running, I decided to check if ADB can see it. Nope. No luck at all. I have connected with ADB to my device many, many times... but it has been close to a year since the last time I did. I removed all HTC drivers and Sync from Add/Remove Programs, deleted my old version of the SDK and Java and followed LuckyThirteen's tutorial step-by-step.
My phone still shows up in Device Manager under PORTABLE DEVICES and I can't seem to make it connect any other way.
I've tried using every combination of search terms I can think of and have had no luck for the past 48 hours.
This is the same exact issue I am having! I am on hboot 1.35 however,and my phone won't even show up on device manager. I have done everything from factory reset, to trying other roms and back ups, to calling HTC, and still nothing. Good to see someone else has the same problem tho haha
Sent from my HTC One X+
Finally fixed my ADB problem using these steps.
Htc M9
unlocked
S-ON
os 3.38.502.31
Hello. i am very lost, very confused, and yeah much help appriciated.
i fix phones for a living, but have never dipped into the development side of things, so i gave it a shot by trying to root my m9.
i installed the android studio ADB thing and of course the htc drivers from htc-sync manager needed to do this.
i unlocked the bootloader with no issue and was able to use the OS just fine after that. after that it was onto rooting my device.
i was unaware of Nanadroid backups or similar programs so theres that
i used superSU 2.64 and TWRP 2.8.7.1a-CTB1-B1 for the custom recovery
when flashing superSU i was prompted it was successful and would now boot into the OS and a few reboots is normal. after waiting a while i knew it wasnt going to go through and that i had screwed myself.
i tried a couple different SuperSU versions with no luck, perhaps the TWRP is too outdated? could not find a way to update TWRP.
eventually after trying multiple different things, on the bottom of the download screen it prompt the 0PJAIMG.zip file was missing, searched for the right one but could not find it.
found an older one and it now gives me an option as soon as booting into the downloader to flash /mnt/media_rw/ext_sd/0PJAIMG.zip or cancel.
selecting cancel puts it intodownload mode.
when selecting "flash" it prompts "RU_MODELID_FAIL modelid in android info mismatched" flash fails, and then turns off.
the phone will reboot continously until power and vol down are held and put into download mode
Can anyone tel me where i need to go from here? What adb/fastboot do i need to be using?
Can anyone spell it out for me? im seriously so lost.
TIA