Related
Hi,
Was changing the ROM on my Kaiser, using JUMPspl as I had got the white screen using Hardspl. During the upgrade got an error at about 18%, went through the recovery procedure only to get back to the Bootloader screen with the screen saying
SPL-1.93.0000
I think it should say something different here!
At the moment can only get the the tri-colour bootloader screen with usb at the bottom.
Please any help would be much appreaciated.
Thanks
If you are at the tri-color bootloader screen, reflash a ROM.
that's where the process starts at anyhow,the bootscreen.
But doesn't the SPL have to be either Hardspl or jumpSPL.
I have tried to do the rom update again but sticks on 0% and gives error 262
Alemaker said:
If you are at the tri-color bootloader screen, reflash a ROM.
that's where the process starts at anyhow,the bootscreen.
Click to expand...
Click to collapse
Not advisable if he has the default SPL still though which by the number appearing at the tri col screen it appears to be the case.
Try doing a hard reset and see if it boots into the original ROM then at least you will find out if it is bricked or not, however, i'm not sure it will work based on the fact you got part way through in the first place.
Hold down the keys directly next to the Send and End (green and Red) Hold in the stylus and keep them all held untill you get a screen telling you to press the green (send) key.
Tried the hard reset, takes me back into the bootloader. Any other ideas?
Hmm... ok then.... you are pretty much looking at a very expensive paperweight at this moment in time then.
Look at this thread...it "may" (i'm not promising anything but it may point you in the right direction) help you out. Let us know how it goes.
http://forum.xda-developers.com/showthread.php?t=361612&highlight=bricked
cmcmill01 said:
Hi,
Was changing the ROM on my Kaiser, using JUMPspl as I had got the white screen using Hardspl. During the upgrade got an error at about 18%, went through the recovery procedure only to get back to the Bootloader screen with the screen saying
SPL-1.93.0000
I think it should say something different here!
At the moment can only get the the tri-colour bootloader screen with usb at the bottom.
Please any help would be much appreaciated.
Thanks
Click to expand...
Click to collapse
Hate to joint the parade, but the exact same thing happened here - 18% now stuck at 1.93.0000
For anyone else reading this BEFORE flashing a new ROM please read, read and read again EVERYTHING related to flashing on this site, wikis and wherever else you can get info.
Another idea for you. Search around here for how to flash from an SD card that may solve the issue out for you. As previously noted though....READ READ READ and be 110% certain you understand what you are doing before you do anything.
http://forum.xda-developers.com/showthread.php?t=276963&highlight=stuck+bootloader
details some info for a Wizard, should it be the same for a Kaiser?
Will Mtty get me any further?
MTTY will at least give you a USB connection to the device it is worth a shot given your current situation.
There is hope!
I did a clean reboot of my PC and disabled my antivirus (avast) and was able to sucessfully reflash the new 1.62 rom (released from ATT site today).
Thanks will try the new 1.62 rom.
What commands can you use with MTTY?
tried the At&t rom gives me an error on the vendor id. Will try a HTC rom
I have tried multiple roms and they all give me the same error Error 294:Invalid Vender ID
Any ideas
Am starting to get worried because if the misses finds out that I have bricked the new phone, I am up to my neck i it.
If you are stuck in boot loader & would like some help via MSN Messenger, please PM me or look for me on MSM messenger at [email protected]. I will be available to help later this evening or tomorrow morning.
I have most of the files to fix these issues & can use MSN fileshare folders to help you.
Good chance that you can be up again in a matter of minutes
cmcmill01 said:
I have tried multiple roms and they all give me the same error Error 294:Invalid Vender ID
Any ideas
Am starting to get worried because if the misses finds out that I have bricked the new phone, I am up to my neck i it.
Click to expand...
Click to collapse
Invalid Vendor I.D. is cuz it's locked.
Had the exact issue myself and found a ATT ROM that will boot. It saved me bigtime, so I saved it. It's in one of the posts on one of the threads but I have the actual ROM, it'll overide that lock.- PM me if ya need it.
Got the same solution, Holy S**t about to have a heart attack. Tried nearly ever ROM out there, it was the Asia one that got me going.
Lesson learned: make sure you Hardspl after jumpspl.
Thanks for all the help folks
Glad ya got it fixed. One quick question?
Is your original ROM ATT or HTC ?
It is a HTC ROM. Done My Hardspl and got Sleuth v3.0 on it already
Happy days
As the title says, I seriously think I am just being stupid. But I have just spent the last 5 hours searching, trying, and just about anything I can. But I can't seem to get anything to work.
Now on to my situation:
I just got a new Tilt, it is not my first. My first one was when it first came out for AT&T. So it was still the WM6Pro and I SIM CID and HardSPL'd it. So I do know how to do this stuff. Just now with this new one, it must be a newer one, because it came with WM6.1 on it.
Here is what I know I have on it. Bootloader shows this.
KAIS1*0
SPL-3.56.0000
CPLD-8
And this is when the AT&T logo pops up.
R 1.65.21.18
G 25.88.40.05H
D 3.57.00.00
Now the first thing I am trying to do is HardSPL it.
I swear I have tried everything.
First thing I tried was the simple, Kaiser SIM/CID Unlocker & Changer , I start with the Flash-HardSPL and get to the Bootloader saying USB with the Rom updater showing the status bar. Then with the phone still in bootloader, I get Error [260] : Connection, The Update Utility cannot connect to your PDA. and so on.
So I exit that. Go on to the next try.HardSPL v3.07-3.56
All of them end up as the same result as the first. But I will explain what V3.28 as I have heard and read that that is one of the best ones to use.
Get to bootloader, Computer monitor shows status bar, and phone shows status bar. And I wait for it to do anything and then maybe a minute or two it gives me an error. Error [262] : Update Error, The ROM Update Utility has encountered communication errors during the update process. and so on for recovery.
I've also tried to do the HTC Kaiser Hard-SPLv1 - CID Unlock & Flash any ROM to your device (4 free)
When I start this one up it gets me to my screen being completely white. and I can not continue after that without taking the battery out and starting the phone again.
I have also tried other things that I just cant remember right now, cause I have been trying to do this for so many hours, and downloaded so many different things. So if you can and may help me, anything and everything will be appreciated beyond the gratitude I can give. Once again, I do know what I am doing, but I do not know what I am doing ARGHHH! lol.
I think you need JumpSPL1.56-KAIS, then hardspl , Im assuming this because you didnt say you did this step in your post.
Read post #2 here http://forum.xda-developers.com/showthread.php?t=396922
pretty sure you have to downgrade to 6.0. Its been a while though and i could be wrong. also try this you should always be security unlocked
http://forum.xda-developers.com/showthread.php?t=361236
sd73ta said:
pretty sure you have to downgrade to 6.0. Its been a while though and i could be wrong. also try this you should always be security unlocked
http://forum.xda-developers.com/showthread.php?t=361236
Click to expand...
Click to collapse
I tried that one, and for 2nd poster, I did try that also. Sorry for not listing. But I still appreciate the help guys.
I was also thinking I had to go back to 6.0 but I went 55 pages back on this section of the forum, and I still cant find it. I'm still looking, but it seems like a dead end to me. =/
there was a guy having this issue a while back, look in the white screen thread towards the end! I will see what I can find for you!
Right now I found a 6.0 ATT rom, so I got that to work, now I will try unlocking it, thank you guys, and thanks to this post (70+ pages back!) http://forum.xda-developers.com/showthread.php?t=326933
Edit 1 :
Alright I got it back down to 6.0, but yet I still cant do anything with HardSPL, CID, or Security. If anyone has any solutions I will listen! Even if its bashing my head against anything! LOL! Sucks!
downgrade I don't believe is necessary
sd73ta said:
pretty sure you have to downgrade to 6.0. Its been a while though and i could be wrong. also try this you should always be security unlocked
http://forum.xda-developers.com/showthread.php?t=361236[/quote
Nope, I didn't have to. My tilt came with 6.1. I had some problems, ended up switching to an XP laptop, was using Vista(prem. sp-whatever). It's too late here, but maybe tomorrow I can figure out what I did, but I think the main thing was using a windows XP pro machine - don't know if it needed to be pro, but that's what I had. Thereafter I've used the vista machine without problem. Good luck.
Click to expand...
Click to collapse
Meh, you need to use JumpSPL first. I've had this happen before, and JumpSPL cleared it right up for me.
I think Jocky has a few you can use. Check his HardSPL thread.
I first tried to use Vista, but then went back to my xp machine.
Edit :
I've tried to the JumpSPL but had major brain damage last night. trying it again with a fresh day. Will let you know.
Just got it, thanks guys. I apologize for just being completely brain dead. But I really am happy that you guys helped out. I finally got it flashed with the HardSPL It was really easy now. I just could not remember how to get to the file explorer. And the JumpSPL 1.56 worked. Thanks!
Yeah, well I can NEVER find anything via search here. Hell, to prove that point, I just typed "stupid" in the subject search line and found: NOTHING!!! I don't know what the deal is, but I've just pretty much given up searching this site.
Which leads to more reading than I'd typically care to do.
J
Munchys said:
Just got it, thanks guys. I apologize for just being completely brain dead. But I really am happy that you guys helped out. I finally got it flashed with the HardSPL It was really easy now. I just could not remember how to get to the file explorer. And the JumpSPL 1.56 worked. Thanks!
Click to expand...
Click to collapse
Glad to hear you got it fixed.
Awesome, fully got it unlocked and everything! Thanks for telling me what I might have missed and messed up on!
Ok, just like all of you I have rooted, experimented to the limits and pushed them well little did i Know is that you cant reflash the 1.56 ruu so needless to say I ended up with a brick but luckily for us it will still connect in fastboot
so this is a solution to at least get it up and running
Pros-
Reactivate your phone since it will be formated
All functions will work
can still root, install .apk's use wifi etc
camera etc
so the pros are it will operate just like nothing ever happened now to the con's
YOU WILL HAVE TO DO THIS EVERYTIME YOU TURN OFF YOUR DEVICE
Ok here is how to fix it
Connect your phone to your PC
open command and navigate to your android tools folder
type in
fastboot devices
make sure it detects your device
should show the HTC logo on your phone
now simply type
fastboot oem boot
wait a couple minutes while your phone reboots
viola you phone is back to running again...just dont turn it off LOL
can you launch the RUU again and (hopfully) have it restore your phone correctly?
You can launch but it will still fail like before, I havent been successful in finding a full solution as of yet
rayborn said:
You can launch but it will still fail like before, I havent been successful in finding a full solution as of yet
Click to expand...
Click to collapse
hmmmm interesting man. honestly you should be able to rebuild all the / partitions. such as /misc and /radio. we need some linux junkies in this thread to tell us how to rebuild failed / partitions
This is amazing. Sure did work for me. I just wish there was a way to get it flash the original radio. I have only had this thing two weeks and would love to take it back and exchange it, but I am just paranoid since it shows radio 2.41.04.02.03.
wait, what exactly did you do to get your near-bricked phone?
you used the 1.56 RUU on your phone that had a 2.xxxxxx radio?
have you tried both of the RUU's? the original and 1.56?
My phone was the Sprint Hero *with Google model, so I had rooted it and loaded a custom rom on it etc and was playing around with it but I wanted to go back to stock so i flashed this ruu
RUU_Hero_C_Sprint_1.56.651.2_signed_release
And BAM at the end error 110
wouldnt boot anylonger
spent all day on figuring out this solution
did you try the 1.29 RUU?
yeah i tried every sprint hero ruu i promise you i left no stone unturned trying to fix this
BRILLIANT!
I can't tell you how impressed I am that somebody has found what i now consider to be the first step towards getting the RUU 110 error solved.
I still feel that the issue comes down to the lack of ADB that seems to happen once you get 110... maybe a driver issue on the phone vs. driver issue on the computer? after all the RUU starts failing on all the ADB commands when you check out the RUU logs...
sorry i can't help take it from there, i returned my phone to sprint inside of the 30-day window and just told them something i installed form the market "bricked" my phone...
I eagerly await your results though for a final step towards solution, as I am dreading the day i have to RUU my phone for whatever reason that may be, although I've been running a personally customized Pancake ROM for almost a week and totally happy with it so won't be doing anything until 2.1 is official...
R
rayborn said:
My phone was the Sprint Hero *with Google model, so I had rooted it and loaded a custom rom on it etc and was playing around with it but I wanted to go back to stock so i flashed this ruu
RUU_Hero_C_Sprint_1.56.651.2_signed_release
And BAM at the end error 110
wouldnt boot anylonger
spent all day on figuring out this solution
Click to expand...
Click to collapse
Same exact thing for myself. Multiple people said the way to go back to the stock radio was to use the RUU. I tried both RUU's and same results. Now I am just trying to decide what is better.
Live with this and hope for a better option to come or take back a "bricked" hero that shows Radio 2.41.04.02.03 and hope I don't end up getting charged later.
IMHO I think the best thing for you guys to do is wait for our 2.1 update, which will more than likely have a smiliar radio update. Then you can just say the update bricked the phone.
If we get the same radio version, then just take it back, if we get a different version then maybe we can find a file to edit the number to make it say what ever version you want it to say, something like editing Build.prop. Then Sprint has nothing to ask questions about. Should be out in a few weeks if the rumors are right. Maybe you can deal with this soultion until then.
As far as the don't turn your phone off issue, mines been up for 13 days. I hate turning it off, partially because of the missed emails and partially because I worry that it won't come back up.
Subscribing. When Sprint releases the official 2.1 in a few weeks, I was planning on using the 1.56 RUU and then doing the 2.1 update. Apparently this isn't going to be possible since I did the Radio update. What is going to be the proper way to get the 2.1 update through Spring for phones with the Radio update to keep from bricking a phone?
SamXp said:
Subscribing. When Sprint releases the official 2.1 in a few weeks, I was planning on using the 1.56 RUU and then doing the 2.1 update. Apparently this isn't going to be possible since I did the Radio update. What is going to be the proper way to get the 2.1 update through Spring for phones with the Radio update to keep from bricking a phone?
Click to expand...
Click to collapse
I was of the same mind, but reading this thread has me wondering the same thing. Are we just screwed now?
mginther said:
I was of the same mind, but reading this thread has me wondering the same thing. Are we just screwed now?
Click to expand...
Click to collapse
There's been plenty of people who have flashed back and forth between the radio versions, using the RUU programs...there's only been a few that have bricked from what I've read.
It's still a bit iffy on whether or not it's actually safe to go between the two, but it shouldn't matter since the new radio versions apparently work just fine with all ROM's that I've seen
tatonka_hero said:
There's been plenty of people who have flashed back and forth between the radio versions, using the RUU programs...there's only been a few that have bricked from what I've read.
It's still a bit iffy on whether or not it's actually safe to go between the two, but it shouldn't matter since the new radio versions apparently work just fine with all ROM's that I've seen
Click to expand...
Click to collapse
True, and if we elect to continue to use either a Fresh or Damageless version of an official 2.1 Sprint ROM, then we should be ok. But if we wanted to go to the Sprint ROM, there are going to be a lot of bricked phones if there isn't a way to understand what is going on when a 1.56 RUU is used over a phone with the 2.x Radio update.
Just wanted to pass along some more information in case anyone else is having this problem. I had reactivated an old phone temporarily since this one was bricked. This morning I reactivated my hero due to this semi fix and immediately I could call and textimg was fine, but i kept getting vision error 67 for data. Sprint reset my data about three times and it never worked. I tried updating my profile multiple times and it never worked. Finally I Ran the RUU again and sure enough after a reboot or an "oem boot" I had error 67again. I went ahead and updated my profile and this time it worked and data started working. Still hoping someing else comes along though.
well I think the issue here might be that it does not have the recovery backup on it after you do an RUU. I could be wrong but who knows? I would say install flashrec-1.1.3-20091107-2.apk on your phone once you are able to get it up and running then flash the recovery backup and restart. That could possibly fix the issue? I have the files if anyone needs them, I'm not sure how to upload them on here...
~Danny
I'm not sure if it's possible boot into recovery console using this method, but if you can, has anyone tried manually flashing the old radio in the same manner they flashed the new one to revert back and then RUU. Perhaps that may do the trick.
My phone isn't bricked so I can't try it out, but seems like it might be worth a shot in theory.
I probably certified idiot for this. So i tried to root evo and didnt work. First, i flashed the pc3 but got that radio v2 error. Then i went to unrevoked but my firmware was too new. Then my battery fried and had to get another. Tried to run ruu and now i got 4 exlamaction points in the corner. When i run the ruu I end up getting error 110. Can someone please help me out?
anybody if you out there please help me
Legendary20 said:
I probably certified idiot for this. So i tried to root evo and didnt work. First, i flashed the pc3 but got that radio v2 error. Then i went to unrevoked but my firmware was too new. Then my battery fried and had to get another. Tried to run ruu and now i got 4 exlamaction points in the corner. When i run the ruu I end up getting error 110. Can someone please help me out?
Click to expand...
Click to collapse
Make sure the HTC drivers are properly installed, and make sure the RUU file is the correct one. When I tried to restore my evo, it only worked with 2 out of 7 different RUU's I used. shipped-roms is a good place to start
Hi,
First of all, I'm new to this Forum, but i've been following it for quite a while now since almost everything Android related you can find here. And People around here seem really knowledgeable.
I've trying to update my One SV K2_UL, and i seem to got it messed up.
I was able to flash the update, and everything went smoothely, until i got to the firmware files, a cannot get them to flash.
I guess the problem is my phone is S-ON, and i cannot change it's CID, although a tried several ways of doing it.
And i cannot guet my phone to be S-OFF, i tried Moonshine but it gets stuck on second test. - "Waiting for ADB".
My phone is exactly the same as leegreenaway refers in this post:
http://forum.xda-developers.com/showthread.php?t=2512742&page=9
so i guess, it's not an equipment problem, it was really my order of doing things that screwed this.
Can someone please help me? What can I do?
I tried to revert to old version but with no luck.
Thank you in advance.
Rui
Yes, as long you are S-On, you can't flash the firmware files.
If moonshine don't work for you, you can try the new rumrunner S-Off (which is made from the same people).
Take care on the instructions on the page there, as it is new, i can not really tell you how it will work.
I have tried rumrunner also, it behaved a little different from moonshine since it passed the second test, and found the device, but than nothing, it didn't go further it just said - "Press Enter to Exit.".
Thanks for the fast reply btw.
Then maybe this post, can give you a helping hand.
If you have Norton Antivirus, disable it. Make sure, you have a sdcard in the phone.
I did had Norton in the beginning of my day, but i already uninstalled it, just to make sure,.
I do have a sdcard on my phone.
So i tried running rumrunners once again, and took a ps of what is happening.
View attachment 2398349
When i see it right, you are on windows 8?
Windows 8 is known as not "driver-friendly" related to android/adb.
Maybe you have a chance to use a Windows 7 PC or even Linux.
Maybe @beaups knows whats the problem is...
Yes you're right,
i'm on windows 8.
unfortunately i do not own any PC with win7, althought ADB looks to be working right since i was able to use the shell and other adb stuff, i might as well give it a try tomorrow at work. I just hope i can turn this around, the phone is working great appart from that fantastic noise the speaker makes.
Thank you.
Well, today I tried to use both moonshine and rumrunner at work, but with no luck. The pc at work is running win7, althought the problem persisted exactly the same in rumrunner, in moonshine it was a bit different because it only stopped the second time it was waiting for adb. I was wondering if someone with the orange phone from UK could provide the firmware from that update, and if this souls male a difference.
Thanks again,
Sent from my HTC One SV using xda app-developers app
Last idea on my side:
You wrote in first post, you flashed everything except firmware. That means, you have the Sense 5 software already installed?
I think you should try then with the stock software, moonshine is made for.
Maybe its checking the version (HTC One SV (k2_ul) 2.14.401.6) and fails, because it is wrong.
Well, actually I got that same conclusion in my mind yesterday, just when I arrived at home from work. So I used the 2.14 odexed stock you provided in a thread, and from there I was able to run moonshine, it completed successfully, and after I just had to re-flash the 3.22 odexed, change the cid and flash the firmware. Voila, problems solved everything is in order now.
So the problem was only, the boot img moonshine was trying to flash would never work on my sys version.
Thank you very much for your help, this was a great learning experience.
Cheers,
Rui
Sent from my HTC One SV using xda app-developers app
Glad you got it sorted out.
old.splatterhand said:
Yes, as long you are S-On, you can't flash the firmware files.
If moonshine don't work for you, you can try the new rumrunner S-Off (which is made from the same people).
Take care on the instructions on the page there, as it is new, i can not really tell you how it will work.
Click to expand...
Click to collapse
Thankyou thiese s-off utility helped me to take s-off