Related
I am making this thread because I just bought a ATT Tilt 2 yesterday and i've been doing my best to flash this phone but it wont work! I know how to flash because I've done it plenty of times with the Fuze, but this phone keeps freezing when it gets to the percentage screen.
I've tried both methods, Via USB and Via Micro SD....
When I did the USB, everything goes fine until the percentage screen on my phone and the computer screen show up, then it stays on 0% until I get an error messages telling me to unplug my phone and retry.
When I tried Micro SD, at the bootloader screen it stays on the "Loading..." forever, it never goes to "Checking"...
So i'm thinking AT&T has something to do with this? They've found a way for customers to be blocked from flashing another rom? Please tell me there is a way out of this...i've seen other users with ATT Tilt 2's claiming they've flashed their phones...but I know I can't be the only one with this problem.
I take it you have already put Hard SPL on the device?
Plenty of other people have put custom ROMs on their Tilt 2. So it's nothing AT&T have done.
Dave
HardSL
It wont let me even put HardSPL....it wont let me do anything period... it just freezes.
The percentage screen stays at zero percent. So i'm lost.
Have you installed the enablerapinew cab? That's all I had to do in order to get HardSPL to go through on my Tilt2
http://forum.xda-developers.com/showpost.php?p=4727487&postcount=1
themasterhook2000 said:
It wont let me even put HardSPL....it wont let me do anything period... it just freezes.
The percentage screen stays at zero percent. So i'm lost.
Click to expand...
Click to collapse
I have a tilt 2 and I am running NRG Photon 10/17 ROM and loven it, but is was not easy to get to this point. My main issue was with HardSPL. I had to go through a couple extra steps in order for it to work. The first issue was a connection error, i followed the directions in the error message and went to the appropriate link.
The second issue is on the flashing page. "anyone having problems with the device entering SSPL without functional USB port ("ERROR 260 CONNECTION" RUU error), you can get SSPL-Manual-Rhodium.exe from attachment in this post, copy it to the *device* itself and run it. then once the screen is showing black, run the Hard-SPL package on the PC and select Manual flash option. please do not use Manual flash option for any other purposes
another reason for USB connection error: if your PC takes too long to load the drivers (if your device is in bootloader for the first time it needs to do that), then if RUU times out, but device is still in black screen, just leave it there and re-run the Hard-SPL package when driver installation finishes - you must use Manual Flash option in such a case. I recommend to wait for Windows to take its time searching for the USB drivers, then click Next in RUU only when they are installed.[/I]
These helped me out and all is good. Hope this helps you as well. If not, good luck my friend.
Decer said:
Have you installed the enablerapinew cab? That's all I had to do in order to get HardSPL to go through on my Tilt2
http://forum.xda-developers.com/showpost.php?p=4727487&postcount=1
Click to expand...
Click to collapse
That was my first step as well. I did not have the link handy...
try this. http://rhodium.htc-unlocks.com/ works like a treat and although I paid for it, I am also Security unlocked.
Hey guys, I've been looking for answer for my problem for several hours without any luck. When my phone is not plugged to USB it won't even start in bootloader mode nor the hard-reset works. When I plug it to USB then it starts in bootloader mode says Upgrade ROM code error Please try again. This screen shows only for about 2 seconds and the phone restarts itself and does the same over and over ... I'm getting desperate. Does anybody know what to do with this issue?
Am also having the same problem since yesterday. My HTC Diamond touch2 had the wm6 from htc..the battery was after every 9hrs dead so i decided to flash the "shania" rom which many says is better. The installation was all fine and shania started.I removed the Batt to put the sim-card and restarted the Phone. It did`nt start and now it gooes on and off with the bootloader tricolor and says "No Image". No access to pc due to "on/off" state. Please Help
No one can Help???
Have also tried to flash using an sd-card without success. The phone does not even charge itself. Please S.O.S
I have a similar problem on my Rhodium (tilt2). Been reading around on and off for a couple days now and have come across a couple possible solutions. I'm still experimenting with my phone.. going to poke around with mtty on my roommate's PC later today. I'm still searching the xda threads (which led me to this post) so I'm sure there is a solution which doesn't involve a service center or warranties. I did read one post about charging the battery in another HTC device and then re-flashing yours with the fully charged battery.. but I don't have that option myself.
cafecz said:
Hey guys, I've been looking for answer for my problem for several hours without any luck. When my phone is not plugged to USB it won't even start in bootloader mode nor the hard-reset works. When I plug it to USB then it starts in bootloader mode says Upgrade ROM code error Please try again. This screen shows only for about 2 seconds and the phone restarts itself and does the same over and over ... I'm getting desperate. Does anybody know what to do with this issue?
Click to expand...
Click to collapse
Do you have hard-spl and what model of diamond do you have,cdma or gsm?
HELICOPTER88 said:
Do you have hard-spl and what model of diamond do you have,cdma or gsm?
Click to expand...
Click to collapse
I'm sure I have GSM phone. I have HTC Diamond Touch P3700. I sucessfully installed Hard-SPL Olinex 1.40. But then I read there might be some problems with 1.40 version so I tried to downgrade to 1.93 and then this ON/OFF problem started.
cafecz said:
I'm sure I have GSM phone. I have HTC Diamond Touch P3700. I sucessfully installed Hard-SPL Olinex 1.40. But then I read there might be some problems with 1.40 version so I tried to downgrade to 1.93 and then this ON/OFF problem started.
Click to expand...
Click to collapse
a lot of time ago i read about upgrading from 1.40 to 1.93 and there was some problem,i don't remember where i read it,i'm not having any problem with 1.40
ok, later i also found out that 1.40 i fine. But it doesnt solve my problem right now. Any suggestions?
Bootloader´s "On/OFF" Solved
I cant believe it...my phone is breathing again..
Somehow I had the feeling that the phone wasnt charging at all. i also read in a forum that one should try to charge the batt in another device but i knew no one with my model..and this is what i did..
1) Connect to pc through USB
2) removed the battery from the phone
3) walla....Bootloader doesnt go off..USB sign shows..a smile on my face...puh!
4) Withought wasting a second I flashed the win6.1rom from my pc
5) Phone goes off ready 4 restart..I put the batt back, waits for it to charge for some minutes and startet the phone..walla...there it goes.
Hope this helps someone
Installed a rom on my tilt 2, or thought i did. phone now boots to windows and freezes. I can boot into bootloader screen and attempt to install other roms however it never gets past 0%.
When it tell me on the computer what image i have nothing appears for the phone image. its just blank. after a while the pda program with say there is a connection error and will rail installing the rom.
plz help =(
Genesis01 said:
Installed a rom on my tilt 2, or thought i did. phone now boots to windows and freezes. I can boot into bootloader screen and attempt to install other roms however it never gets past 0%.
When it tell me on the computer what image i have nothing appears for the phone image. its just blank. after a while the pda program with say there is a connection error and will rail installing the rom.
plz help =(
Click to expand...
Click to collapse
Did You HardSpl Your Phone First?
yes, however at first i thought my phone was cmda.....now i figured it is gsm. went through the process of hard-spl how can i be sure though?
Genesis01 said:
yes, however at first i thought my phone was cmda.....now i figured it is gsm. went through the process of hard-spl how can i be sure though?
Click to expand...
Click to collapse
Since You Can Boot Into Bootloader You Can Check Your SPL Version From There Check It Out & See What Is & Post What It Is Here.
just checked it again and the olinex isnt there anymore. sure that would be the problem. how do i go about fixing said problem?
spl-0.87.0000
Genesis01 said:
just checked it again and the olinex isnt there anymore. sure that would be the problem. how do i go about fixing said problem?
spl-0.87.0000
Click to expand...
Click to collapse
Follow The Instructions In This Thread ---> http://forum.xda-developers.com/showthread.php?t=550131
tried, the phone, even thought it is connected wont sync so the spl wont detect it and run the program
when i go to manual it will start but will hang at 0% until the comp says there was an error in connection =(
Genesis01 said:
tried, the phone, even thought it is connected wont sync so the spl wont detect it and run the program
Click to expand...
Click to collapse
Try Booting Phone Into Bootloader Screen Then Plug In Usb Cable Make Sure It Says Usb At The Bottom Of The Phone Screen Then Try To HardSpl Again.
Try Installing This Cab On Your Phone --> http://hpcmonex.net/roms/enablerapinew.cab Then Run HardSpl Again.
kk thank you, i will try. will post results as soon as i get them. Thanks again. kudos to you!
If your phone does not have the HardSPL on it, and it will not boot properly, you need to get it back into bootloader mode, wait for 'USB' to appear on the screen, and flash the stock ROM, then try again with the HardSPL program.
EDIT: To see what version of Rhodium you have, remove your battery and look at the sticker under there on the phone. you should see something like RHOD100, RHOD200, RHOD300, RHOD400, or RHOD500. RHOD100-300 is GSM. RHOD400 & 500 is CDMA. Make sure you flash the correct ROMs, radios, and HSPL for your device or you run the risk of bricking it.
Hey i hope all is good.
I really need your help. I have a TILT 2 cell phone and by mistake a friend activated the bootloader. Previously the ROM has been updated. the phone got stuck in that screen and the only way to turn it off is removing the battery. so, i try to reboot the phone and it only loads the bootloader with a flash message saying "no image file". ok, i though, the ROM was damaged and after reading a lot in the forums, i followed the instruction to put a new ROM. I connected the phone the the computer and the message in the phone changed to USB and my PC installed the HTC USB Sync driver (but Active Sync does not detect the phone); anyways, i ran the task 29 and a new rom. I was able to see the progress bar in both (PC and Phone) but then the phone reboots and loads again the bootloader. I tried to use the HARD SPL 1.00 as well but it does the same thing after finishing the flash it loads again the bootloader.
can some help me pls?? i'm new in this and the phone is a work tool for me i really need your help.
rgds
You should do the HSPL before flashing a ROM (unless it was already done).
I would try to flash the newest HSPL, then a ROM.
Hi, and thank you for you reply.
I already did it and apparently it flashed the HSPL . Now in the bootloader says SPL 0.85 OliMex; then i flashed the ROM and it showed me the progress bar in both system (PC and phone) but when it finish it booted back to the bootloader. I just noticed that sometimes (after been off for a while) if i turn it on it boots to the rom but it happens randomly and if I turn it back off i just got the bootloader again.
I really need your help pls
jsolanon said:
Hi, and thank you for you reply.
I already did it and apparently it flashed the HSPL . Now in the bootloader says SPL 0.85 OliMex; then i flashed the ROM and it showed me the progress bar in both system (PC and phone) but when it finish it booted back to the bootloader. I just noticed that sometimes (after been off for a while) if i turn it on it boots to the rom but it happens randomly and if I turn it back off i just got the bootloader again.
I really need your help pls
Click to expand...
Click to collapse
Hrm, have you tried doing a task29? Re-flash the ROM after task29.
yes already tried the task 29 and then flash the rom but the same issue...i've been reading a lot of post regarding issue with the bootloader and follow the instruction but nothing seems to work. I even tried the update from the AT&T site but the same issue...i have no idea what else to do
jsolanon said:
yes already tried the task 29 and then flash the rom but the same issue...i've been reading a lot of post regarding issue with the bootloader and follow the instruction but nothing seems to work. I even tried the update from the AT&T site but the same issue...i have no idea what else to do
Click to expand...
Click to collapse
So you've flashed the stock ROM? Have you tried relocking? Probably won't do much, but worth a shot I guess.
When you flash back to stock you flash the stock ROM, then relock, then reflash stock.
Yes, but the issue persisted.
I have noticed something. If i leave the cell phone turn off for a while (hours) and then i turn it on. Most of the time it works and all the things are fin; but as soon as i turn it off and turn it back on the bootloader starts appearing.
So, now i can use the cell but i cannot turn it off or leave the battery died on me...any suggestions?
BTW, thank you very much for your help
jsolanon said:
Yes, but the issue persisted.
I have noticed something. If i leave the cell phone turn off for a while (hours) and then i turn it on. Most of the time it works and all the things are fin; but as soon as i turn it off and turn it back on the bootloader starts appearing.
So, now i can use the cell but i cannot turn it off or leave the battery died on me...any suggestions?
BTW, thank you very much for your help
Click to expand...
Click to collapse
My phone is never turned off. I'm not sure what else to suggest, you've tried seemingly every step that could remedy this problem. Radio firmware probably won't help, but it shouldn't hurt either - you could try a new radio...
hi , this happened to me, solved it by reloading the rom again via sd, once it finish maybe you will see the bootloader screen again, so with stylus pres the reset buttom a few times until the rom boot , this can take several times to make it boot. after revive your cell , do a task29 then reload the rom again then do a hard reset, this happened to my 2 times, and its still alive ,good luck.
Same Problem
Hi,
I'm having the same problem. Installed the latest official ROM from HTC/ATT (gorgeous), and same problem after install. Whenever you try to reboot, it gets stuck in the bootloader screen. The last 50 tries it will not reboot at all, even after removing the battery and hitting the power button. This used to work occasionally.
Any other process anyone knows for getting the device to read the ROM?
Is the phone just worn out?
I suggest you reflash the shipped rom to your device and after the flash finishes and your device begins to boot immediately remove the battery to turn it off before it boots. Then replace the battery and press and hold the Send and End keys and while holding them down press the Power button and follow the instructions to factory reset(hard reset).
Okay, I tought i just could RUU my phone using RUU file. So I downloaded RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4. 06.00.02_2_release_126984_signed.exe and booted to fastbood mode -> connected USB -> ran RUU. Anyways, all wen fine and the gray HTC logo appeared on my screen but after few seconds the RUU gave me "Bootloader version error [140]". After that my phone is just dead. It wont turn on or anything, I cant get ADB to my phone. Screen is totally black. The phone just randomly vibrates when i plug it in the charger or press the power button after taking the battery out. But its just random. The charging led indicator wont even turn on.
I Had few weeks old XJ's MIUI installed, CWM 4.X.X.X and hboot 6.93.9999 (if i remember right, 6.93.XXXX it was anyways). After failing the RUU, I googled and found out that i shuold have downgraded hboot first? I recently bought a new phone so actually just didnt give s*** Im having proximity sensor problem in my old Desire, so I would like to return it to the shop after flashing the default rom.
So folks, how do I proceed? Totally bricked?
Thanks!
jaavaa said:
Okay, I tought i just could RUU my phone using RUU file. So I downloaded RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4. 06.00.02_2_release_126984_signed.exe and booted to fastbood mode -> connected USB -> ran RUU. Anyways, all wen fine and the gray HTC logo appeared on my screen but after few seconds the RUU gave me "Bootloader version error [140]". After that my phone is just dead. It wont turn on or anything, I cant get ADB to my phone. Screen is totally black. The phone just randomly vibrates when i plug it in the charger or press the power button after taking the battery out. But its just random. The charging led indicator wont even turn on.
I Had few weeks old XJ's MIUI installed, CWM 4.X.X.X and hboot 6.93.9999 (if i remember right, 6.93.XXXX it was anyways). After failing the RUU, I googled and found out that i shuold have downgraded hboot first? I recently bought a new phone so actually just didnt give s*** Im having proximity sensor problem in my old Desire, so I would like to return it to the shop after flashing the default rom.
So folks, how do I proceed? Totally bricked?
Thanks!
Click to expand...
Click to collapse
sounds like wrong RUU file meant for SLCD/Amoled.
try the first post in Q&A which should deal with this...it's a sticky for a reason
It looks like slcd brick look for droidzone slcd brick guide
Sent from my HTC Desire using XDA Premium App
Thanks, but as I already said, the phone cant be detected by PC. The phone wont even turn on. I tried again starting the phone to fastboot mode, but the phone wont even vibrate or show any signs of life. The only thing is that when i randomly plug the phone to the charger, it might vibrate and start warming up.
And yes, I've tried charging the phone over night assuming the battery would be empty.
jaavaa said:
Thanks, but as I already said, the phone cant be detected by PC. The phone wont even turn on. I tried again starting the phone to fastboot mode, but the phone wont even vibrate or show any signs of life. The only thing is that when i randomly plug the phone to the charger, it might vibrate and start warming up.
And yes, I've tried charging the phone over night assuming the battery would be empty.
Click to expand...
Click to collapse
so holding down back and power to get straight to fastboot doesn't work at all? i'm only referencing the troubleshooting guide
droidzone's slcd brick guide is more comprehensive, if that doesn't work then i dunno unfortunately...
Whoa, got some life to my phone! Started it somehow with usb plugged and vol down and i got it to recoverymode! ADB Devices gives me following:
List of devices attached
HT07XPL06736 recovery
Dont want to boot the phone again, what do i do now? tried running a RUU for SLCD spotted in the sticky thread here, but it gives me 170 USB error.
EDIT:
So I'm in this situation now? (taken from droidzone's guide)
"IF YOU SOFT BRICKED AN SLCD BRANDED DESIRE WHICH HAD AN UPDATED VERSION OF HBOOT BY FLASHING AN INCOMPATIBLE RUU, AND IF THE DISPLAY WONT TURN ON NOW, YOU CANNOT RESTORE THE PHONE TO WORKING CONDITION UNLESS YOU HAVE A CORRECT RUU FOR THE UPDATED HBOOT, OR A GOLDCARD. "
Click to expand...
Click to collapse
Well, is there a correct RUU for me?
as you are in recovery fastboot commands will not work try adb ones:
adb reboot bootloader
download fastboot commander you can find info there
kotag82 said:
as you are in recovery fastboot commands will not work try adb ones:
adb reboot bootloader
download fastboot commander you can find info there
Click to expand...
Click to collapse
Okay entered the command and now the phone cant be recognized in any ways again. Tried running RUU right after boot but still error 170. Cant get the phone visible to ADB again..
do you have goldcard? download WWE RUU 2.29 and try do it blind google some videos as pb99200 method is shown, how to use pb99200 method see bortak guide from stickies... im off now till wednesday