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...
Related
First it was spl 3.8. Was having trouble but could still work with the phone. Suddenly I became flashoholic. Just the same way as I flashed 50 times before, I was flashing. It all went ok. After that I'm stuck at the splash screen. Says, Format Failed. But can get into bootloader and flash roms. But that's all. No booting business.
Guess this is the end of the road, unless there is any solutiion. Any one out there?
IPL 2.20.001
SPL 3.08.001
Radio 2.47.21
OS 4.0.0.0.6 (was)
Now the mobiz step 1
i think i'm having a similiar problem with u..
flashed to SPL2.20. Everything ok..
after a few flashes, only thing i get now is the bootloader screen..
i can flash ROMs, RUU tells me its successful, but PDA just restarts and goes back to bootloader
Waaah :'( I have a most similar problem I was running pdaviet 4.0.0.6 Touch for almost 2 weeks now without a single glitch.. the phone fell on my carpet and went to bootloader screen and eversince then it has never recovered I tried a hard reset it didn't work when I was pressing the send button it did nothing I did some forum searches and tried putting back the nvid RUU and it said that the update was succesfull and the progress bar on the phone moved accordingly but it went back to the bootloader screen ... then I tried pdaviet temp rom that was in the package still no go I can tell it works somehow because the USB lights up in the bottom left when I plug the usb cable and the progress bar that moves, but I'm getting desperate IPL and SPL info is in my sig...
I can go into bootloader, flash any wm5 roms without IPL SPL. But that is all. Unless we can find a way to unlock the cid and flashback the original dopod rom, we are stuck.
anyone??? I cant use my phone at all now :'( and I didn't even re-flash it... all was working fine I just DROPPED it on a CARPET no real shock and since then it's on the bootloader screen
In my oppinion you have to send it for repair... I think it's really a phisical damage...
really no progress..
i opened a thread in the WM6 area also...
seems to be stucked at bootloader no matter what i do..
tried every single ROM, tried reflashing radio rom, tried reflashing ipl/spl, tried every RUU available..
when u guys hard reset, does it say Format is Failed ?
ice_mouton, i'm something like you.. dropped it few weeks ago.. but it still ran fine.. upgraded to PDAVIET's 4.0.0.0.6 Touch.. had no problems for the first few days of use... suddenly it refused to reset and was stuck at vendor boot screen...
Hey guys,
Really sorry if this a repeat of a previous discussion. I am new to posting.
I have never had any problems loading new ROMS, have had an 8125 and an 8525 and installed several different roms with no problem at all. Recently I bought a tilt several days ago. I had the issue with the white screen when installing SPL so I used jumpSPL. This worked but when I was installing the ROM it only got to 19 percent. I completed the recovery but still nothing happened. After this I used mtty.exe, a very nice program I might add, and used the boot command. Phone boots fine and everything works, however whenever I soft/hard reset I am stuck back on the bootloader screen and have to use mtty again. My question is this: How can I recover the original bootloader? Whenever I try to run any ROMS it stays at 0 percent. Someone please help.
Thank you
Figured I left some information out. I currently have service with ATT. On the bootloader screen top left: KAIS1*0, SPL-1.56.0000, CPLD-8....top right:RUUNBH
Contact me if assistance is still required or see the post regarding MTTY by L26.
READ BEFORE YOU FLASH! You have flashed without the use of HardSPL. This is the quick way to a brick.
New issue @ post #5
I was downgrading to ButtonROM to flash later a 6.0 rom to see if missed calls issue of TNT 19199 was a rom related issue when at 90% flashing my vario rebooted! I tried to recover that setup but wizard kept rebooting in boot loader mode.
Note: battery was 100% full and i was following the wise flashing procedure.
I Tried to reflash both with RUU and SD card mode, also trying to change the rom to update, using imate or Tmobile stocks... no way.
Sd Card mode says that setup runs successfully but after rebooting wizard is again in bootloader mode...
Also after a while i keep it on bootloader connected to my laptop it starts rebooting continuously, I don't know what else to do than remove battery!!
One last thing it happens... after i remove battery and then plug charger instead of usb cable, wizard wakes up again in bootloader mode by himself.
Here's latest flash result
ROM - Error 302 @ - effects
------------------------------------------------------------------------
Button - 98% - none, reboots at 98% and keep rebooting
Xda mini - 85% - downgraded xpl from 3.08 to 1.05, keep rebooting
Love - 48% - none, rom flash crashes and wizard start rebooting in loop again
Flash from SD - none - Seems to be successful but then starts in bootloader mode instead of normal mode.
to answer youre question
try and take ure sd card, and flash using the XDA mini launch rom, and downgrade from there.
hope that works.
u can download it from here
updated post #1
My wizard is ALIVE!!!!!!
The problem was the battery! TNT 19199 has a weird battery indicator that doesn't show right battery charge! So it was showing me a full charge while it was almost empty. I bought a new battery and a separate charger. Now flashing succed with RUU and with both batteries (old and new) charged apart.
I downgraded to TNT 1620 WM 6.0 until WM6.1 will get more stable.
green to black splashes
So sad it's not completely over... my bootloader splashes show a green to black gradient. I tried to change it by using several methods but nothing changed, has anyone already managed to get rid of that green to black screen?
I was trying to install a rom, for the first time. everything went smooth, progress bar hit 100% and the phone reset. "Touch pro" came up, sits there for about 1 minute then the phone restarts...it keeps doing this in a loop.
what can I do?
Hi,
buffalolsx said:
I was trying to install a rom, for the first time. everything went smooth, progress bar hit 100% and the phone reset. "Touch pro" came up, sits there for about 1 minute then the phone restarts...it keeps doing this in a loop.
what can I do?
Click to expand...
Click to collapse
I guess you've done anything wrong, i guess it's a missing HardSPL
To fix it, get the official ROM for exact your branded device, your language and so, then
go into bootloader mode, connect to your pc, start the upgrade, then your device should work again.
--------
If you want to flash a custom made rom in the future, you have to install the proper HardSPL first (!),
HTH
I've had some previous experience with custom roms on my old Nexus 6P and thought I would try the same for my mate 9. Unfortunately I've discovered the Mate 9 is not as easy to install custom roms as I thought.
I've tried several things throughout the day and I feel I've accidently overwritten things I shouldn't have but can't remember everything I've done.
It is an Optus branded phone so I believe at the start of the day I had some version of L09C34. I currently have an unlocked boot loader and TWRP installed and would like to flash back to the stock firmware, but seem to be unable to do so. The boot loader is unlocked and when I try flashing extracted parts from fastboot, the phone will reboot, reboot again and sit at erecovery. Unfortunately while I can connect to wifi, no packages are found for recovery.
Additionally I now get this lovely colourful screen in lieu of the logo on initial boot.
Any help would be appreciated.
Okay, so I've managed to unbrick it and install a version of L09C432 and get it working again - thank you to various threads on XDA. I think what I noticed was that someone else had tried the C432 firmware on a C33 model and it worked. Without being able to get hold of the C34 firmware, I tried to flash nougat originally and it worked.
This morning, I've noticed I still have an issue where the touchscreen won't work when the phone is cold (i.e I can't click anything and can't turn alarms off). If I reboot the phone to recovery it's fine, so it leads me to believe its an OS thing. Also, if I give it a few minutes in my pocket, or holding my palm on the screen it then responds. This is the issue I tried to resolve by resetting and trying a different rom but seems I haven't been successful.
Finally, when I first turn the phone on and the screen lights up I see a green background with one blue and one red box. Any ideas what I have messed up there and how to fix it? I'm not too concerned, but it would be a nicety.
Just providing updates in case anyone comes a long with similar issues.
I have now fixed the strange coloured screen on initial power on. I've found the oeminfo for the C432 firmware on another XDA thread and took a backup of what was currently there, restored the C432 version and rebooted. I was presented with the eRecovery and no TWRP. Quick check in fastboot mode showed the phone relocked. I unlocked it again and it booted no issues, however was unsure if the custom rom was still installed as I was presented with the option of an OTA update. Initially my sim card was not recognised, so I had to remove and reinstall it but so far so good.
I've just reflashed my custom rom and will see how I go.
The only potential issue I have outstanding is my touchscreen not working either first thing in the morning, or when the phone is cold - i.e I've gone to the gym and left it sitting in the locker for 2 hours and I can't use the touchscreen when I come back. I can unlock it fine with the finger print reader and the phsyical buttons respond but touches on the screen won't. If the phone is left alone for a few minutes the screen shuts off and turns back on approx every 5 seconds until it becomes responsive. Has anyone seen anything like this before? My googling hasn't lead me to anything helpful.