Hello everyone,
That's my problem:
almost a year since I turned in different custom rom, which had never caused any problems. Then my screen started to lose its sensitivity, or even move all alone. So I recommend it as everywhere trying to return to the origin.
I am currently in the 2.1 HTC last updated.
The screen is much better. But I want to return to 1.5, to really be sure I completely reset.
And that's where the trouble begins. Unable to install the HTC RUU, always the same error (Error 170: bad version of bootloader), whereas it normally means a problem with drivers. I checked several times these drivers, be it XP or Win 7 64. Always the same message.
And then I fell in that you (really sorry) I had completely forgotten. So I tried to follow the tutorial "How to restore the firmware of the HTC hero.
There can not run the commands, I put: "Into rebooting bootloader ... FAILED <remote: allow> not verbatim or 'downloading' boot.img '... FAILED <remote: not allow>
And I do not see what I could do differ between the two responses.
I'm starting to believe I'm even more noob than I thought.
I guess the question has to be asked of you, but then it starts making long as I want and I can not find.
I see no reason why it does not work because he sees in fastboot My phone devices.
Does anyone have an idea for the method I should follow or tell me why this command does not work. (Although for lines order Now began with the first root of my phone, then virtually unknown).
If there is already a topic or a wiki, thank you for giving me the links if possible.
Counting on a pretty fast response from you all.
In advance thank you for the help you can give me.
PS: sorry for the novel, but I think I managed to summarize all the parameters of my worries.
PS: I think I have tried all methods so far found only one positive is that I'm sure my drivers, still appears in them because MyHTC, it is in bootloader or in sync.
Sorry for my bad english but it's a traduction for google.
Replied in thread above pal.
Sent from my HTC Hero using XDA App
Related
To All and specially moderator,
I recently just lost all rom image and now my himalaya are totally dead, because I try to upgrade software from a program.
Probably you have seen many of these posting from a newbie like myself. Speaking of the truth, even after browsing many hours in this forum I still have no Idea at all how to restoring my operating system.
Well, my plea is, could one of the senior/expert on this forum to post new instruction how to restore the rom (even how to upgrade to wm2003SE, one by one, not just reverting to old post) I believe many of newbie ( lack of software knowledge) have the same problem with me.
Thank you.
Regards.
Do you get anything on screen, do you have "serial", when you connect to usb do you get "usb" on screen. If yes then you just need to download original rom for your phone and restart flashing procedure. If there is nothing on screen I cant help, sorry.
Sorry for annoying every one here. The problem with phone is this.
I have a O2 XDA Mini S which I recently bought. The person I bought it off had removed the O2 stuff with some other ROM. There was a few niggly problems mainly the symbol keys were assigned to the wrong keys etc.
I followed a link on the O2 website which said it was an upgrade. I installed this and it appears to actually have "downgraded" the phone. Now my phone once again has all the O2 branded stuff, I'm not an O2 customer. I'm on Meteor in Ireland.
I've tried downloading almost every file I could find related to this. New ROMs etc but once I try to install them the screen goes RGB and I get Error 300 invalid update tool
As I said I've try almost all links I can find to rectify this with no joy.
Could some very nice person out there, talk me through the steps to get my phone back running with an up to date ROM?
I'd greatly appreciate it guys. I'm a total newbie at this so I hope you'll take it easy on me
you need to use shelltool.
you will find it at the top of the G4 forum.
hope this helps.
Thanks Stabloid.
I'll give that a try when I get home. Do I just run the shell tool and then install the ROM?
Hey Stabloid,
I downloaded Shelltool. Unfortunately there was no instructions with it.
From what I could figure out I put the two cab files on the xda/ wizard and installed them there. I rebooted the xda then tried running the shell tool.
I've tried it a few times. I let the program run for an hour last night and nothing happend it just kept saying "Do not disconnect..."
The other error I kept getting was "please make hard reset" followed by a list of instructions which I followed and yet still got the same results.
Can someone please help me out with this or supply full instructions for the shell tool?
Thanks.
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)
After reading and reading and reading I am officially stuck hopefully someone or @stifilz can help. Hoping that i just missed something after reading too much info.
UK Sony Tablet S region changed when ICS came out for early update from US. Decided do JB update yesterday the flasher V3 got up to the end of data transfer part and tablet froze up and all coms went. left it for a while but nothing. After a hard switch off it hung at the sony logo. Got into recovery and did factory reset to try clear any issues or so i thought. Still hung at logo. Downloaded various ICS files and renamed to update.zip and tried to reflash. They all fail with the E: Prohibit error, occasionally error failed to mount system1.
I've attached my recovery log if anyone can help sort this il be a happy man.
TIA
After reading http://forum.xda-developers.com/showthread.php?t=2433323 I am starting to think a lot of these topics go unanswered and point to a flaw in the flasher, my region.prop is also missing and can only presume the tablet requires this for an update and the factory reset removes the root so cannot push another .prop over. So for all intents and purposes the tablet be fooked. I really do hope I am wrong but if i am right then why is this flashing tool still available after so many screw ups.
Well the screw up your are referring to is your own as if you had done your research you would know that trying to flash jb to the tablet s and not the xperia s will mess the tablet up as pointed out in numreouse posts and questions. so the reason people don't reply is that the questions have all ready been answered serveal times and the warings are there
rooted lighting wildfire on unoffical j.b from benni
and sony XTS rooted stock j.b thanks djrbliss
I presumed I had done enough reading beforehand as the tool said Sony Tablet S so seemed the right tool for the job. I've flashed many things over the years and never screwed one up so this is bit of a shock to the system, My first reaction to your reply was to reply don't be smart then my second was to go check tool again, then third was ah f*#k. 26 letters in the alphabet and sony had to call the next model an S too. I cant say i keep up with tablet technology so thought they same thing pre flash,I didnt expect my tablet to be replaced in market so quickly after i bought one. Oh well lesson learnt now the question is wtf can be done if anything. If i send in for repair do they spot this instantly and try hammering me for a heavy bill to fix. Its under guarantee but they do say software issue they wont touch it.
I did read a lot about these problems but only reference i can find was today on page 36 of the flasher tool post. I blame mondays and my obvious lack of cognitive skills on them.
dex9mm said:
Well the screw up your are referring to is your own as if you had done your research you would know that trying to flash jb to the tablet s and not the xperia s will mess the tablet up as pointed out in numreouse posts and questions. so the reason people don't reply is that the questions have all ready been answered serveal times and the warings are there
rooted lighting wildfire on unoffical j.b from benni
and sony XTS rooted stock j.b thanks djrbliss
Click to expand...
Click to collapse
Can it be fixed?
nkxtc said:
I presumed I had done enough reading beforehand as the tool said Sony Tablet S so seemed the right tool for the job.
Click to expand...
Click to collapse
I read this article and made the same mistake:
androidadvices.com/sony-tablet-steps-update-latest-jellybean-firmware-click
I should have read the details better. I commented to the article that I bricked my device but it was apparently deleted...
The important thing I would appreciate knowing is if the tablet is completely unfixable. I just spent $150 on a new tablet but was hoping i could at least recover my tablet S and give it away.
soilchemist said:
I read this article and made the same mistake:
androidadvices.com/sony-tablet-steps-update-latest-jellybean-firmware-click
I should have read the details better. I commented to the article that I bricked my device but it was apparently deleted...
The important thing I would appreciate knowing is if the tablet is completely unfixable. I just spent $150 on a new tablet but was hoping i could at least recover my tablet S and give it away.
Click to expand...
Click to collapse
Now thats why i thought it was ok i read that site first too rather than here. Too much reading after the event not before. So who are these idiots at androidadvices.com? The advice below is from that site and is what got me to reset tablet. Now i'm even more annoyed at this.
Note: Just in a rare case if the device doesn’t boot up or show the home screen then long press the power button to turn off and then re follow the instructions.
nkxtc said:
After reading and reading and reading I am officially stuck hopefully someone or @stifilz can help. Hoping that i just missed something after reading too much info.
UK Sony Tablet S region changed when ICS came out for early update from US. Decided do JB update yesterday the flasher V3 got up to the end of data transfer part and tablet froze up and all coms went. left it for a while but nothing. After a hard switch off it hung at the sony logo. Got into recovery and did factory reset to try clear any issues or so i thought. Still hung at logo. Downloaded various ICS files and renamed to update.zip and tried to reflash. They all fail with the E: Prohibit error, occasionally error failed to mount system1.
I've attached my recovery log if anyone can help sort this il be a happy man.
TIA
Click to expand...
Click to collapse
Naming the file update.zip does not help as we can not see what is fully going on. Anyway it fails due to a messed up vendor. This would make sense as JB files would mess them up. Then it switches partition and that also fails due to vendor, but a slightly different error.
Anyway installing 0042 should work as they do not rely on vendor files. This is HoneyComb 3.2.1R2 and it is ROOTABLE. From there you can use flasher again. See my signature for links
EDIT:
4shared.com/zip/m-xXuCCv/signed-nbx03_001-ota-0042001.html
4shared.com/zip/03dah__B/signed-nbx03_001-ota-0042001.html
4shared.com/zip/8nuDXOQZ/signed-nbx03_001-ota-0042001.html
Hey thanks for getting back to me its appreciated. Tried all three files you sent link for. None worked it gives the prohibit/sku error. I've attached recovery files of each files attempt if you like to look at it. I've looked through a lot of your other posts and a few very similar ones as this and come to conclusion its damaged beyond repair and am tempted to use the warranty and chance my luck as its got few month left. Unlocked bootloader or the legendary files you have mentioned in another post would be useful but doubt we get to see either soon.
edit
Here's a shot in the dark...As tablet was originally a UK model and was changed for ICS is there any possibility that it has somehow defaulted back to UK and file signed-nbx03_003-ota-0042.001.zip would help. Its only thing i think ive not tried but cant find that version anywhere. Idea popped in head last week as there was a lot of reference to sku error being a region specific problem but then it went away until just now.
stifilz said:
Naming the file update.zip does not help as we can not see what is fully going on. Anyway it fails due to a messed up vendor. This would make sense as JB files would mess them up. Then it switches partition and that also fails due to vendor, but a slightly different error.
Anyway installing 0042 should work as they do not rely on vendor files. This is HoneyComb 3.2.1R2 and it is ROOTABLE. From there you can use flasher again. See my signature for links
EDIT:
4shared.com/zip/m-xXuCCv/signed-nbx03_001-ota-0042001.html
4shared.com/zip/03dah__B/signed-nbx03_001-ota-0042001.html
4shared.com/zip/8nuDXOQZ/signed-nbx03_001-ota-0042001.html
Click to expand...
Click to collapse
nkxtc said:
Hey thanks for getting back to me its appreciated. Tried all three files you sent link for. None worked it gives the prohibit/sku error. I've attached recovery files of each files attempt if you like to look at it. I've looked through a lot of your other posts and a few very similar ones as this and come to conclusion its damaged beyond repair and am tempted to use the warranty and chance my luck as its got few month left. Unlocked bootloader or the legendary files you have mentioned in another post would be useful but doubt we get to see either soon.
edit
Here's a shot in the dark...As tablet was originally a UK model and was changed for ICS is there any possibility that it has somehow defaulted back to UK and file signed-nbx03_003-ota-0042.001.zip would help. Its only thing i think ive not tried but cant find that version anywhere. Idea popped in head last week as there was a lot of reference to sku error being a region specific problem but then it went away until just now.
Click to expand...
Click to collapse
Sorry should have mention (but thought you would notice) they were the same file. Ok that is failing for the same reasons. Seems it is pretty messed up. You tried a factory reset yet? If not you may have some adb access on the boot logo???
Here comes a rant
stifilz said:
Sorry should have mention (but thought you would notice) they were the same file. Ok that is failing for the same reasons. Seems it is pretty messed up. You tried a factory reset yet? If not you may have some adb access on the boot logo???
Click to expand...
Click to collapse
I did notice but i eternal optimist and sorta hoped they different files even though filesize gave it away plus I already had that file from your links in sig but wouldnt be first time a company names files the same but different regions. Factory reset did numerous times now.
Didnt realise could get adb from logo screen so got hopes up again when lo and behold there in device manager was MTP device. After couple hours messing with it and getting lots of errors saying no driver etc I figured out putting hardware id in different adb usb driver inf files (USB\VID_054C&PID_05B3&REV_0100) would give me a working driver or so I thought. The PC decided after few minutes to give yellow exclamation and driver no longer works. Persevered with it until got driver stable but from command prompt adb says no devices in list.
Now all this happened early hours since 3am so not having greatest amount of patience (4hours not bad) i took a huff turned everything off and said [email protected]#k it ive had enough. This aint ever gonna work im resigned to this fact.
Now i may have not read one tiny part of the AIO tool which turned out to be biggest mistake i made in all this however for anyone else unfortunate to have a blonde moment would it not be possible to put some sort of checker in the tool to determine what is actually attached to be flashed based on hardware ID or something before any system changes occur. Having flashed many many devices from phones to consoles each and every one has a check of some sort before hand.
However putting that aside I think its disgraceful how Sony have treated this tablet and how locked down it actually is. This pains me but the £300 wouldve been better on a damn ipad.
@stifilz appreciate help you tried to give mate
Hello all!
First of all, I am no developer.
Long story short.. I purchased an HTC 10 because I was sick and tired of my at&t galaxy s5 being bootlocked. I received the 10 and set out the next day to root it. I followed a video on youtube (not saying that the info was not correct...I may have done something wrong...not trying to discredit anybody) to the letter and lo and behold I ended up in a bootloop. My heart probably came close to a complete blockage at this point. This bootloop lasted maybe a minute before it would reboot. So... In my infinite wisdom I chose to relock the bootloader. Oh Boy!!! Fun times were ahead for me!! As soon as I relocked said bootloader, the bootloop increased its timing to about 1 point 5 seconds. I remember waking up on the floor in the fetal position. Now I am stuck with a phone that adb will not recognize. It does however recognize the device at the fastboot devices prompt. So my question is this.... Is this a salvageable phone? If so, How would one go about fixing this problem?
*** Relocked ***
htc_pmew1 pvt S-ON
os-2.28.617.8
I would prefer that the money I spent on this thing would amount to something more than a small ant bed.
Any help at all would be greatly appreciated. Also I have been doing a lot of digging around and (I may be wrong) but. I could not find this scenario in the forums here. I apologize if this has already been covered.
...So..after looking around for a bit more, I discovered out that there is a way to flash a ruu/zip from an sd card. I have tried multiple times with what I thought were the right ones. As I am unable to boot into recovery, I feel I am limited as to what I should do. I have read about that I should wipe dalvik but I am very limited in my knowledge on an android system and would prefer to not mess this phone up anymore than it already is. I was trying to root and I used TWRP as the recovery but I never made it to the end before it started the loop. The Phone is an htc 10 unlocked version. and it just constantly reboots about 3 seconds apart. ADB says no device connected, so I cannot execute commands that way... really at a loss here. all the tutorials I have read refer to using and and being able to boot into rrecovery. when i boot into recovery, I get an immediate reboot and the 3 second bootloop forever. Is there a way to use twrp to somehow resolve this?Is there a tool that will help me at least get into recovery mode?
SOLVED... Ran across Batchtool by sneakyghost. Quite the bunch of tools there! Ended up solving my problem by placing the stock RUU in the root folder as the batch tool. Before I could not install from a factory RUU (would not recognize the phone through ADB or install the RUU. After the install of the batch tool I was able to get a clean install back to my factory settings.. Now I am free to mess it up again!!
BIG THANKS TO SNEAKYGHOST!!!!!
I'm unsure why the batch tool has worked for you and the sdcard method didn't - getting fastboot to work and all the bits and pieces together (drivers, Windows VCRedist, correct fastboot, correct adb) is usually more error prone than just identifying the correct zip and placing that in your sdcard root.
At this time, I'm a bit in a "scratch my head" mood, thinking this is weird. Same zip? Really the same zip didn't work from sdcard but would work in fastboot? I think I haven't come across that myself yet (non booting phones are a daily thing, almost).
I wish I had the time to analyze your steps with you, so I could gain understanding as to why that happened, so I can use that in the future, but alas! I have no time for XDA and deep digging around in issues of other people. Lately I can't even solve my own phone's problems anymore due to too many other things going on.
Well, glad it worked for your phone, anyhow. I'll keep this in mind for the next one messing up his/her phone.