Database Info

Sprint HTC Touch Pro 2 in reboot loop

We recently purchased a Sprint HTC Touch Pro 2 phone from Ebay. I accessed the Bootloader mode to see if the device was locked and now the device is in a constant reboot loop. We have tried a soft and hard reset and now the device will get to the Windows loading screen and then reboot all over again.
I can enter Bootloader mode without any problem. I have searched through the forums and found the procedures for flashing the ROM in bootloader mode but the problem still persists. The flashing shows 100% complete and the device reboots, but then it goes right back in to the reboot loop. I have to remove the battery for several minutes to get the device to shut off completely.
Can anyone provide some guidance on how we can get this fixed? Do I need to unlock the device before flashing the ROM? Can someone provide me with the links to the downloads I need?
Any help would be greatly appreciated!

No replies...
233 views and no one has replied? Anyone have any ideas or suggestions? Please!

Force to bootloader and reflash the stock rom.

Stock Rom
Thank you for your reply, but I have forced into Bootloader and flashed the stock ROM several times but the reboot loop continues. I have also tried flashing the stock ROM from the SD card. Flashing the ROM using either method appears to be successful, but everything I tried still results in the reboot loop.
Other things I have tried
Charged with wall charger for 48 hours
Swapped battery
Removed SD card and then flashed ROM
If there is anything else that you can think of that I should try, please let me know. We are passed the point of being able to return the device to the EBAY seller and this device was purchased to be used as a Hand-held PC so we do not have a contract with any service provider.
Thank you!

You could try flashing to a verizon or other CDMA operator's rom and see what results you get. Also could try unlocking and flash a custom rom. If you run out of options, send it to me and I will try to fix it for you free of charge. I will send it back to you within 48 hours of receiving it. Just include postage paid return packaging.

I appreciate the offer, but I think we have decided to just cut our losses with this device and move on. Thank you to everyone for your help!

[Q] Desire S stuck on boot - cant get to recovery

Hi,
I will prefix this (as there are a few people around with this problem who can get into recovery mode) with the fact that holding down Vol- on boot is not getting me to the recovery / bootloader screen.
I have a rooted HTC Desire S (rooted it nearly a year ago, so info about the hboot etc is a distant memory).
Anyhoo, I decided to have a play about with one of the ICS roms but it was a bit buggy and the camera drivers still aren't working for video so I decided to go back to Endymion V3.4 - http://forum.xda-developers.com/showthread.php?t=1310845
I did a full wipe, installed base rom, installed optional addons and then upgraded to 3.4 - booted fine into the OS so set about getting my system set up the way I like it.
I noticed that endy came with a theme installer so clicked on one of them to have a look, it asked for root, said it was installed and would need to reboot to take effect...
SO
the problem is, it now won't boot and is stuck on the white HTC boot screen.
Holding vol+/- and power buttons reset it but it just ends up back hanging on the boot screen.
Have tried pulling battery and trying again.
Holding Volume Down when powering up is no longer doing anything
So, I either need a saviour to point me in the direction of a fix.. or a kindly sould to break it to me gently when they tell me my phone has gone to the USB Dock in the sky..
Any help will be greatly appreciated.
Thanks

update:
After pulling battery again, pulling out sim and sd cards, booting with vol- held down, i got into recovery. Am going to try and flash a different rom after doing a full wipe, I'll update once it's done but any insights in the meanwhile will still be appreciated

Sorted, cleared the thing out, stuck reaper CM rom on it, rebooted and everything is peachy for now.
Thanks me
Curious if anyone knows why this might have happened?

because you didnt flash the addon zip which was released alongside endymon and then tried to use the addons,it does say on the screen do not use these unless you have installed the addons

[Q] Please help me on this i cant seem to find the answer anywheres

i have rooted my g2x several time but after i shut if off to charge at night i tuirned it on and it went straight to the cwm recovery screen i wiped it and restarted it and it went right back to it i flashed several other roms and when i went to reboot it it still rebooted to recovery screen i formated everything i new of what am i doing wrong. i had a stable rom in it and it was working for like 3 weeks before this happened . I hope someone can help me on this i love my phone and dont want to lose it. My computer is running on windows 7 i have tried these
http://forum.xda-developers.com/showthread.php?t=1056847
http://forum.xda-developers.com/show....php?t=1056847
and i even tried one where i tried to flash it back to stock and and now it stuck on a white box with an arrow coming out of it with and android robot in front of it
Did i brick this can it be saved i hope someone can help me one this i just pray i didnt brick it

STANC1 said:
i have rooted my g2x several time but after i shut if off to charge at night i tuirned it on and it went straight to the cwm recovery screen i wiped it and restarted it and it went right back to it i flashed several other roms and when i went to reboot it it still rebooted to recovery screen i formated everything i new of what am i doing wrong. i had a stable rom in it and it was working for like 3 weeks before this happened . I hope someone can help me on this i love my phone and dont want to lose it. My computer is running on windows 7 i have tried these
http://forum.xda-developers.com/showthread.php?t=1056847
http://forum.xda-developers.com/show....php?t=1056847
and i even tried one where i tried to flash it back to stock and and now it stuck on a white box with an arrow coming out of it with and android robot in front of it
Did i brick this can it be saved i hope someone can help me one this i just pray i didnt brick it
Click to expand...
Click to collapse
I don't exactly know how to fix your problem, but to shine some light, your not bricked. If u were, u wouldn't be able to access anything
Sent from my LG-P999 using XDA

STANC1 said:
i have rooted my g2x several time but after i shut if off to charge at night i tuirned it on and it went straight to the cwm recovery screen i wiped it and restarted it and it went right back to it i flashed several other roms and when i went to reboot it it still rebooted to recovery screen i formated everything i new of what am i doing wrong. i had a stable rom in it and it was working for like 3 weeks before this happened . I hope someone can help me on this i love my phone and dont want to lose it. My computer is running on windows 7 i have tried these
http://forum.xda-developers.com/showthread.php?t=1056847
http://forum.xda-developers.com/show....php?t=1056847
and i even tried one where i tried to flash it back to stock and and now it stuck on a white box with an arrow coming out of it with and android robot in front of it
Did i brick this can it be saved i hope someone can help me one this i just pray i didnt brick it
Click to expand...
Click to collapse
Use this to put cwm and then flash the rom you like.
If phone still boots into recovery you may have a stuck vol- button.
http://forum.xda-developers.com/showthread.php?t=1590523
Sent from my LG-P999 using XDA

i cant get into recoveery now im stuck in it relaoding as i tried to flash the recovery again and its stuck

try and flash again, if it doesn't stick, then try again. If it gives you an error report the error. Try what mansa_noob posted, it usually works for everyone, it fixes everything (partition and issues) and then flashes the recovery for you.

TP2 not booting

My TP2 (Sprint) battery went too low and turned off. After charging the battery, the phone just comes up to the Sprint splash screen (Yellow Sprint Symbol) and gives a little vibrate and reboots again. This goes on continuously till I pull the battery . I on am Stock Sprint WM6.1
I can enter into the bootloader screen. I have tried
1. Task 29s
2. Flashed a different radio.
3. Reflashed Stock 6.1 ROM again.
4. Hard Reset it a couple of times
My phone is HSPL unlocked in that I see *olinex 1.0 when I go into the bootloader.
I have tried flasing ROMS from both the SD card as well as from the PC. I cannot go past the green Win 6.1 screen .
I am out of ideas and would really appreciate it if anyone saw this signature previously or has any ideas as to how to solve this.
TIA

baikal2 said:
My TP2 (Sprint) battery went too low and turned off. After charging the battery, the phone just comes up to the Sprint splash screen (Yellow Sprint Symbol) and gives a little vibrate and reboots again. This goes on continuously till I pull the battery . I on am Stock Sprint WM6.1
I can enter into the bootloader screen. I have tried
1. Task 29s
2. Flashed a different radio.
3. Reflashed Stock 6.1 ROM again.
4. Hard Reset it a couple of times
My phone is HSPL unlocked in that I see *olinex 1.0 when I go into the bootloader.
I have tried flasing ROMS from both the SD card as well as from the PC. I cannot go past the green Win 6.1 screen .
I am out of ideas and would really appreciate it if anyone saw this signature previously or has any ideas as to how to solve this.
TIA
Click to expand...
Click to collapse
You could try re-locking the phone, installing the stock 6.5 rom, and then unlocking the phone again.
Also be sure to give it lots of time during the first boot (like do the install, and then leave to make dinner or something). There have been days where I though the phone had locked up, only to have it finish booting when I was about to pull the battery.

wizardknight said:
You could try re-locking the phone, installing the stock 6.5 rom, and then unlocking the phone again.
Also be sure to give it lots of time during the first boot (like do the install, and then leave to make dinner or something). There have been days where I though the phone had locked up, only to have it finish booting when I was about to pull the battery.
Click to expand...
Click to collapse
Wizard,
I ma noob and was wondering the need for relocking. Does it have any benefits as opposed to simply flashing WM 6.5 on to the phone. I have flashed WM 6.5 onto the phone and it goes all the way to the Orange screen(Preparing for activation or something like that with the progress bar) and then reboots again endlessly.
My hesitancy with re-locking comes from the fact that to unlock you need to be in a position to active sync and if the flash fails after the relock ,I might not be in a position to unlock again.

baikal2 said:
Wizard,
I ma noob and was wondering the need for relocking. Does it have any benefits as opposed to simply flashing WM 6.5 on to the phone. I have flashed WM 6.5 onto the phone and it goes all the way to the Orange screen(Preparing for activation or something like that with the progress bar) and then reboots again endlessly.
Click to expand...
Click to collapse
In rare cases re-locking and then re-unlocking resolves rom loading issues.
baikal2 said:
My hesitancy with re-locking comes from the fact that to unlock you need to be in a position to active sync and if the flash fails after the relock ,I might not be in a position to unlock again.
Click to expand...
Click to collapse
As your phone does not boot, I don't see why you are worried about it. You have nothing to lose. Your phone does not work now at all.
You can always flash a stock rom to a locked phone anyway. The only tool that would rule out is the task 29, and you already said that didn't work.
Either way I would try to load the stock wm 6.5 rom, and give it a very long time to finish loading before doing anything else first.

I have to echo WizardKnight's advice here... It seems crazy, but it fixed one of my dead TP2's. It wouldn't boot past the first white HTC screen, I never even got the OS screens to load...
I tried literally everything I could think of... for some reason relocking it revived it...

[Q] Galaxy S2 Soft Bricked after root....

Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!

addamT989 said:
Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
Click to expand...
Click to collapse
Try flash a stock firmware by using flashtool, it will work 100%:angel:

revernwe therefore
addamT989 said:
Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
Click to expand...
Click to collapse
hi,
can 'be that your device has some residual old. Do as you have advised. install a stock rom and firmware, so it becomes a new cell phone. After odin starts TWRP (much better) and root.

I would flash a complete bone stock Rom using Odin and start over. Also rom manager was highly discouraged on the AT&T version of the s2 so I don't know what the stance is on T-Mobile's version
Sent from my CLEAN Note ll

brandonarev said:
I would flash a complete bone stock Rom using Odin and start over. Also rom manager was highly discouraged on the AT&T version of the s2 so I don't know what the stance is on T-Mobile's version
Sent from my CLEAN Note ll
Click to expand...
Click to collapse
Thanks for the advice! Should i flash it back to ICS then try to root again via Odin before i upgrade back to JB? I'm guessing there's something that isn't getting wiped. Since i can run CWM and Root with Odin without a hitch. it's the initial reboot after all that is done that I go into the boot loop.

tainiun rioters
pierm said:
hi,
can 'be that your device has some residual old. Do as you have advised. install a stock rom and firmware, so it becomes a new cell phone. After odin starts TWRP (much better) and root.
Click to expand...
Click to collapse
Sorry for my ignorrance, what exactly is TWRP, and is it now on there because i used Odin and it installed it automaticly? And do i want to use this vice CWM?

One more question...before i try all this, can i backup everything on Kies just like i would be able to with CWM and reinstall if my root fails again? I've only used Kies for firmware upgrade, never to reinstall a backed up copy of my phone.
Thanks!

addamT989 said:
Sorry for my ignorrance, what exactly is TWRP, and is it now on there because i used Odin and it installed it automaticly? And do i want to use this vice CWM?
Click to expand...
Click to collapse
addamT989 said:
One more question...before i try all this, can i backup everything on Kies just like i would be able to with CWM and reinstall if my root fails again? I've only used Kies for firmware upgrade, never to reinstall a backed up copy of my phone.
Thanks!
Click to expand...
Click to collapse
Hi
TWRP and the 'one touch recovery, better than CWM.
The backup kies can not recover from CWM
steps:
install odin, after recovery, nandroid backup, ROM, and root.
hi

Flash the stock firmware using odin!!..it will work!
Sent from my GT-N7100 using xda premium

freezes then booted
Hello I have this problem with my galaxy s2 i9100. After reboot the phone wasn't booting something like "boot loop" so I re flashed the firmware and now the phone boots up but after the boot it freezes immediately. So I decided to install clock work mod recovery and install cyanogen mode 11 with cyanogen mode the phone boots up and are able to be used again until the screen goes to sleep mode or the power button is pressed then the screen goes black and doesn't turn on after long pressing the power button it reboots. So I don't know what else to do I have tried kernels, operating systems re flashing reseting and nothing helps. No need to tel me to do resettings. Also my galaxy s2 i9100 chip has insane chip bug but I don't know if it has to do something with my problem.