Related
I appologize in advance if there is a lot of information about this but I have searched and searched and haven't found anything as of yet. I have the Verizon Touch Pro with the newest V2 stock ROM from several months back. Now I am interested and going back to a custom ROM. I have tried the latest HardSPL (I think it was 0.35) and when I run it I get "Loading..." on the TP and eventually "ERROR [260] : CONNECTION". If I pull the battery and put it back in it boots up to the way it was so clearly nothing is getting programmed. I have tried it on 3 computers and get the same thing. I had programmed it many times in the past successfully but that was before I upgraded to the V2 stock ROM. I'm wondering, is it that upgrade that is causing the problem? I have not tried via SD card yet but I plan to at some point today.
Thanks,
Tbone
Ok, I put the Verion HardSPL on my SDCard root and renamed it RAPHIMG.nbh. I forced the phone to the tri-color screen by holding power and volume down and then pressing soft reset. It flashed the tri-color and then went immediately to "Loading..." and has been there for 10 minutes. I do remember that when I did this previously it would ask if I wanted it to load the ROM and that is not happening. Any ideas?
Thanks,
Tbone
Ha, I got it. I put the ROM on the SDCard and then copied over VZW_TP_SSPL-Manual.exe and ran that on the TP. It initially showed "Loading..." and then quickly changed to "Checking..." followed by the option to load the rom on the SD card. Not sure if this is the only way to do it once you have installed the V2 ROM but it seemed to work at least with HardSPL. Interestingly, I then put the custom ROM on the SDCard and re-ran the SSPL and this time it went to "Loading..." and stayed there. So I reset and forced the boot in to the Tri-Color screen and this time it got past the "Loading..." screen without a problem. I'm definitely a bit puzzled over this but I'm now up and running with a custom ROM again.
Hopefully this might be helpful to others.
Tbone
Hi there,
Have been using since a while the Energy Rom's.
Always had HSPL2 in use with a Energy Rom and
the most stable Radio.
Well since a week of 2 I can't flash anymore. I still
have HSPL2, used TASK29 to clean everything up.
Now I can't flash a new Energy Rom, it keeps hanging
on 100%. I can do the TASK29, but after using TASK29,
and trying to flash a new rom it keeps hanging. It gives
me an Error-message called 262; but I checked everything
(other pc, cable, other USB port everything).
Has anyone a idea what to do? I haven't been able to
use my phone for 2 weeks now!
(last versions I used: RadioRUU_Leo_Radio_15.40.50.07U_2.12.50 ROM-Energy.Leo.23569.Sense2.5.Cookie.Jun.22)
Cheers!
Anyone? pleaaaaaaaaaaseeeeeee
what info does you're bootloader show
Well I've got some new info!
I installed HSPL3 this evening, with 2.08SPL,
wiped the phone with task29, rebooted, put
in the USB cable, flashed the new dinik glass
16th july Energy Rom and that worked. After
that I hard resetted my phone and again put
in the USB, tried to flash a radio but now THAT
keeps stucking @ 96% (Radio_2_12_50_02_2).
What could that be? Tried under Vista, Windows 7
XP, 3 different laptops, other cable; everything.
I wiped it again and again. Also tried with 2.07 one
but that also doesn't work!
Do you have any idea?
em this is a good en lol, have you tried to flash a radio then hard reset then task 29 then flash rom then hard reset again?? its just ideas
Also tried ;-)
Doesn't work for me
Keeps hanging
Did you try the micr sd method. the one where you do not need to use your PC. Might be silly but it would eliminate any problem with the PC or cable.
will try it this evening
but I don't think thats the problem? because I CAN use my usb
to flash the energy rom
how long are you waiting? the reason I ask is because I flashed Radio 2.12 just a few hours ago and it hung at 96% for a couple min before it finally finished up.
Faelok said:
how long are you waiting? the reason I ask is because I flashed Radio 2.12 just a few hours ago and it hung at 96% for a couple min before it finally finished up.
Click to expand...
Click to collapse
idd, that radio version hangs for some time on 96%, so give it more time
Serious guys?
Hmmm then I will task29 my phone within a few minutes
and flash rom again + radio, and then just wait with the
radio until it's ready! Good plan!!!!
Still not working guys! I'm really really fed up with this phone.
Haven't been able to use the phone for ages now. Have tried
to flash radio and rom for about 1000x times; the TASK29
works, after that I flash the ROM that works 6/10 times,
after that I hardreset the phone, and sometimes it will boot
untill the white bootscreen and otherwise I can't even turn
it on (problem with 3-pins battery connector?) and I have to
wait or have to pull out the battery again and again. But after
all, the radio can't be flashed at all, it keeps hanging on 96%
over and over and over again.
RATBORG said:
Still not working guys! I'm really really fed up with this phone.
Haven't been able to use the phone for ages now. Have tried
to flash radio and rom for about 1000x times; the TASK29
works, after that I flash the ROM that works 6/10 times,
after that I hardreset the phone, and sometimes it will boot
untill the white bootscreen and otherwise I can't even turn
it on (problem with 3-pins battery connector?) and I have to
wait or have to pull out the battery again and again. But after
all, the radio can't be flashed at all, it keeps hanging on 96%
over and over and over again.
Click to expand...
Click to collapse
Hello dude!
Try downloading another radio version.
Try also downloading again the 2.12 radio. It could be a download corruption! I heard a case like yours and it was caused by "bad download"
Tell us if it works, right?
Good luck!
Jooo
Tried with various versions, with more radio's and more CUSTOMRUU-versions, but it still doesn't work!
Any idea? Still doens't work
try
try flash your original rom from htc and change te HardSPL to the original one ike 1.66.00000 or 1.48.000000 and then flash the stock rom
It's not working, have done TASK29, tried to flash the stockrom but it's hanging on 9%, did task29 again and again and tried with various stockroms.
I was having the same problem but with radio , also 9% try flashing the original radio
Yeah well, what else can I do now?
I downloaded the WWE stockrom (1.43 or do I need a higher number) from the
official stock rom thread here at XDA
You should dowload it from htc site , at least is what i did then hardspl it to a 0000000 version like 1.48.0000000000000 or 43 what was that , then try an install the original os is should work at leas it worked for me
Hello, I have an unrooted Hero from Orange (Spain) that enters in a boot loop. I have tryed everything to restore it but with no success. In the hboot menu it says "touch panel-fail" and even if I flash again the original rom from the hboot, it still gets in a boot loop.
First of all I will explain my case.
I had the Hero rooted, with custom roms etc, but when I bought a Nexus One, I gave my Hero to my brother. In September he told me that the official 2.1 had arrived to the Hero, so he wanted it instead of a custom rom, so I just proceeded to do so. I created a GoldCard, installed the 1.5 RUU of WWE, made the two OTAs and all OK. The last week (I think) he received a new small OTA, he updated successfully. My brother went to sleep with the Hero almost charged, but when he woke up, the Hero was off. Then, when he turned it on, and after a while (15mins or so) the Hero finally boot up, but the touchscreen wasn`t working and using it with the trackball the Hero was always prompting FC of android.process.acore (every 2 seconds more or less).
After watching that, I installed the official 1.5 of Orange hoping that it will fix it, but no way. Now it gets stuck in a loop while booting after the Orange bootscreen.
I tryed again to flash the WWE version, but with my old GoldCard doesn't seem to work (incorrect cid) and not being able to boot it up, I cannot create a new GoldCard or even root it.
I have tryed a lot of fastboot comands but I can do just little things because for the most useful things I need root.
Other thing that might be good to know is that when I plug the power to the Hero nothing happens, the led is not turning on, and I don't know how much battery I still have. Thank goodness that the battery was full before I moved the Hero to this infernal boot loop.
Please I will be so thankful if anyone can help me or just giving me any clue about how can I fix this.
I had the same problem on a refurbished hero I had. It had touchpanel fail in hboot and was in a constant loop.
I managed to get it to boot into android once by installing the ruu while in fastboot mode, however the touchscreen did not work and when I rebooted the phone it went back to the loop.
I sent the phone back for a replacement. If u check my previous threads ull see the thread icreated. In it I said that it had worked as that was when it finally booted but before I realised the sgreen didn't work
Sent from my HTC Hero using XDA App
Thank you for your reply, I will check your posts when I arrive home this evening.
hi.
I had the same problem and solve it by flashing this rom (goldcard needed)
http://shipped-roms.com/shipped/Her...io_63.18.55.06P_6.35.15.11_release_signed.exe
I think I may have bricked my OG HD2 (T8585) while trying to undo everything I had done to it, which was HSPL, MAGLDR and a NAND Android ROM.
It all started when I first tried to flash Kingdom's Sense 3.0 Gingerbread ROM. It told me to create a 340MB partition using HD2 Toolkit which I did. I then flashed the ROM as per the instructions, but it kept getting stuck on the boot logo so I decided to go back all the way to stock WinMo.
I downloaded a stock 1.66 ROM from HTC's website, tried to flash it via USB which failed because I obviously have no ActiveSync in Android. So I loaded the image onto my SD card and tried to flash by holding Vol Down and Power.
That was the first sign of trouble, about 1/10th during upgrade process it gave me some errors and rebooted to a black screen with a silver warning triangle.
Trying to go back into bootloader, I got the message about "upgrade ROM code error."
Since it had reverted back to SPL 1.42 I tried to reflash HSPL2 through USB, which worked fine, got the "We bricked it " message and everything. But then I tried to install MAGLDR and nothing, it fails even though it recognizes the USB connection.
So what can I do? On the one hand my device can accept and load HSPL2 and my computer is recogonizing the USB connection, but other than that nothing, it won't even turn on without being connected to external or USB power.
I also tried installing stock 1.43 ROM and that goes fine, it gives me an okay on everything but it gets stuck in the white HTC bootscreen in a loop.
I know I probably made a huge glaring mistaking to cause this, it's probably because I've bought a Transformer tablet and a Galaxy S2 in the last month so the steps regarding the HD2 were probably a bit of a blur. I guess the stock ROM probably included a radio that I wasn't supposed to flash, causing my device to be bricked.
But is there anyway I can get some type of OS working on this poor HD2 now?
She lives!!!
Okay, I'm not actually sure if the problem is solved but I'm back in WinMo 6.5 for the time being.
Since it had been off for a few hours I tried my luck again, plugged it into the wall and saw that it was stuck in the boot loop again. But I got distracted and left it, and when I came back it was on the orange WinMo setup screen.
Not sure what happened to make it go from not even getting power from the battery to working normally. But I see now my radio version is 2.05 which is massively old, I'm going to try and upgrade that first and see... hopefully it won't go back to being dead the moment I power down.
Shawn_230 said:
I think I may have bricked my OG HD2 (T8585) while trying to undo everything I had done to it, which was HSPL, MAGLDR and a NAND Android ROM.
It all started when I first tried to flash Kingdom's Sense 3.0 Gingerbread ROM. It told me to create a 340MB partition using HD2 Toolkit which I did. I then flashed the ROM as per the instructions, but it kept getting stuck on the boot logo so I decided to go back all the way to stock WinMo.
I downloaded a stock 1.66 ROM from HTC's website, tried to flash it via USB which failed because I obviously have no ActiveSync in Android. So I loaded the image onto my SD card and tried to flash by holding Vol Down and Power.
That was the first sign of trouble, about 1/10th during upgrade process it gave me some errors and rebooted to a black screen with a silver warning triangle.
Trying to go back into bootloader, I got the message about "upgrade ROM code error."
Since it had reverted back to SPL 1.42 I tried to reflash HSPL2 through USB, which worked fine, got the "We bricked it " message and everything. But then I tried to install MAGLDR and nothing, it fails even though it recognizes the USB connection.
So what can I do? On the one hand my device can accept and load HSPL2 and my computer is recogonizing the USB connection, but other than that nothing, it won't even turn on without being connected to external or USB power.
I also tried installing stock 1.43 ROM and that goes fine, it gives me an okay on everything but it gets stuck in the white HTC bootscreen in a loop.
I know I probably made a huge glaring mistaking to cause this, it's probably because I've bought a Transformer tablet and a Galaxy S2 in the last month so the steps regarding the HD2 were probably a bit of a blur. I guess the stock ROM probably included a radio that I wasn't supposed to flash, causing my device to be bricked.
But is there anyway I can get some type of OS working on this poor HD2 now?
Click to expand...
Click to collapse
I had pretty much the same problem as you, but mine is the tmobile us version. I tried flashing back winmo from android via sdcard method but i got an upgrade error. I tried flashing with microSD card sizes 8gb, 16,gb, and then 2gb which was recommended, but still no luck. I managed to connect the hd2 through usb on the tricolor screen and flashed back to hspl2.08 and magldr and cwm were still on. But i would like to still get back to winmo stock as if it came from tmobile.
My question is if i download the latest update from tmobile which is T-Mobile HD2 MR Software (Version 3.14.531.1), what is the correct spl i should have installed on the hd2 so that htc and tmobile wont know that i messed with the spl? is it 3.03? I was going to connect via USB on the tri color screen again, run the EXE and manually install the SPL? I just need to know which SPL to install after i run the latest winmo update. Please advise on the SPL and the method i'm going to take on reverting back to winmo. Thanks.
germotlp said:
I had pretty much the same problem as you, but mine is the tmobile us version. I tried flashing back winmo from android via sdcard method but i got an upgrade error. I tried flashing with microSD card sizes 8gb, 16,gb, and then 2gb which was recommended, but still no luck. I managed to connect the hd2 through usb on the tricolor screen and flashed back to hspl2.08 and magldr and cwm were still on. But i would like to still get back to winmo stock as if it came from tmobile.
My question is if i download the latest update from tmobile which is T-Mobile HD2 MR Software (Version 3.14.531.1), what is the correct spl i should have installed on the hd2 so that htc and tmobile wont know that i messed with the spl? is it 3.03? I was going to connect via USB on the tri color screen again, run the EXE and manually install the SPL? I just need to know which SPL to install after i run the latest winmo update. Please advise on the SPL and the method i'm going to take on reverting back to winmo. Thanks.
Click to expand...
Click to collapse
So it sounds like you lucked out, huh? So your HD2 works at least? I believe if you succesfully flash an official ROM like from T-Mobile, it will replace everything including the SPL back to stock - this is what I was trying to do by flashing official 1.43, to go back to factory mode.
I seem to be worse off than you though. I posted last night how my HD2 was back up running WinMo, but as suspected the moment I rebooted it was back stuck in the boot loop.
Any ideas? I wish I could get the HD2 working again so I could set it aside and get to playing with my new Galaxy S2.
This is driving me crazy now...
I managed to flash HSPL 2.08, and then MAGLDR 1.3, and then CWM recovery on top.
But this still seems bricked to me, still needs external power to turn on and I can't actually flash a working ROM... flashing a ROM via USB gives connection error and flashing via SD card goes fine but gets stuck in a boot loop.
What can I do at this point short of tossing the phone? I've tried stock 1.48, stock 1.66, a bunch of radios from 2.05 to 2.15... everything.
I am doing some research but the only results I find are T-Mo HD2s being bricked by the wrong radio. I have an original HD2 and I never flashed a radio intended for another HD2 model, so how is my phone so bricked all of a sudden?
All the threads I've found say if you can get into the bootloader then there's some hope but I doubt it because I can't successfully flash anything with it. I don't even know how I managed to get back into WinMo briefly last night... think my HD2 is probably just toast.
Okay, I finally solved my problems for sure - bent charging leads in the battery compartment!
Anyone having boot issues, take out your battery and look at the metal leads and you will probably find them bent out of shape. They are incredibly flexible, so just make them straight again and it will work. I assume it cuts external power briefly right before booting into WinMo, which is why it was rebooting constantly.
So I suppose for me this was a huge case of confusion, I got all confused with bootloaders and MAGLDRs when the problem wasn't even software related.
Shawn_230 said:
So it sounds like you lucked out, huh? So your HD2 works at least? I believe if you succesfully flash an official ROM like from T-Mobile, it will replace everything including the SPL back to stock - this is what I was trying to do by flashing official 1.43, to go back to factory mode.
I seem to be worse off than you though. I posted last night how my HD2 was back up running WinMo, but as suspected the moment I rebooted it was back stuck in the boot loop.
Any ideas? I wish I could get the HD2 working again so I could set it aside and get to playing with my new Galaxy S2.
Click to expand...
Click to collapse
The problem with my hd2 is the CPU is overheating thus causing it to freeze or lock up, and gets it annoying. After hours of searching on XDA, that's what seems to be the problem. I can't even talk on the phone for more than ten minutes or else locks up. So my idea was to get it back to winmo stock and see if it still locks up. If it does then i will probably try to send it back to HTC and see if they send another one maybe or fix it.
Ive had no luck luck flashing back to winmo from sdcard so i think i should try flashing back to winmo via usb on the tri color screen. Ive read on XDA that if you flash winmo via usb that it doesn't replace your SPL, and you have to run HSPL4 and flash it manually. I'm just not sure which SPL i should flash. I'm assuming 3.03 maybe?
What you could try is using an sdcard that is 2gb or less. Ive read that anything higher than 2gb will cause issues. I'm still a noobie at this rooting biz. Hope that helps.
germotlp said:
The problem with my hd2 is the CPU is overheating thus causing it to freeze or lock up, and gets it annoying. After hours of searching on XDA, that's what seems to be the problem. I can't even talk on the phone for more than ten minutes or else locks up. So my idea was to get it back to winmo stock and see if it still locks up. If it does then i will probably try to send it back to HTC and see if they send another one maybe or fix it.
Ive had no luck luck flashing back to winmo from sdcard so i think i should try flashing back to winmo via usb on the tri color screen. Ive read on XDA that if you flash winmo via usb that it doesn't replace your SPL, and you have to run HSPL4 and flash it manually. I'm just not sure which SPL i should flash. I'm assuming 3.03 maybe?
What you could try is using an sdcard that is 2gb or less. Ive read that anything higher than 2gb will cause issues. I'm still a noobie at this rooting biz. Hope that helps.
Click to expand...
Click to collapse
Which model HD2 do you have?
Find and download the stock ROM from this thread, get 1.66 since it will work with HSPL2 which is the latest HSPL that will work with MAGLDR (for Android and WinPhone7).
You can flash that through SD card and it will go back to total stock, including stock SPL. I assume you know how to pull the .nbh file from the ROM you download, so just rename to LEOIMG.nbh and put it on your SD card.
Go into the tri-color screen and it should flash fine and give you factory reset. This is where it wasn't working for me, but not because I had flashed the wrong ROM or something but because I had messed up the charging leads in the back while popping the battery in and out to reboot as I was flashing.
Man I downloaded 1.66 last nite and tried to flash back to winmo from android and its toast. Not sure what went wrong. Oh well.
Sent from my HTC Sensation 4G using XDA App
alright here is where i start. I'm running the new leak, just flashed BAMF 2.0 a day or 2 ago. i have been updating roms regularly without a problem. i tried to flash Sebastian 1782 OC kernel. When i did i got a main ver error. I went into Sebastian thread and was reading where other people had problems with the main ver error and i did what was said to do to fix it. They said to open the android text file in the kernel and change the main ver to the same this i was running and to change the hboot to what i was running. So i did that. flashed into recovery and flashed the kernel. It flashes and then heres where i get a problem. It says reboot to bootloader to complete. The phone shuts down and thats it. It wont turn on. It wont do anything. i have pulled the battery and left it out for a few minutes and put it back in but nothing. I tried to charge it and the amber led wont even light up. What went wrong? I need help. This absolutely blows