Need help flashing a phone caught in boot cylce - Touch Pro2, Tilt 2 Windows Mobile General

Hello,
I have a AT&T Tilt 2 that is caught in the boot cycle. Splash screen comes on, it reboots. I'm quite confident that flashing a new ROM will fix it it but the phone has not had hard SPL installed so I can only flash the original AT&T ROM, which as far as I can tell is not available?
I've tried to install SPL but it won't take in the state that phone is in. Is there a way to flash SPL from the memory card? Any other suggestion on how to flash it? Is the original AT&T ROM available?
Any other suggestions on how to proceed?
Your input is greatly appreciated.

try this
copy recovery img from wiki to root of micro sd card. img should be named xxx.img, insert microsd card into phone
with phone off hold down the vol down key and the red/phone call end button then power on, with any luck you should see the tricolour boot screen and the img should be detected and flashed automatically. ensure at least 50% battery

try taking your sd card out of your phone and then reboot. if that takes it out of the boot cycle, then you have installed a program to your sd card that is putting it into the endless boot cycle. after your phone boots up, uninstall whatever program that you installed to your sd card. hopefully that helps.
if all else fails, try a hard reset. just hold down the send button, end call button and power button simultaneously. it will ask you to press the volume up button to proceed. that will wipe your phone to factory settings and then you can hardspl your phone and flash away!

Milo, thanks for your reply... I can't seem to locate that recovery img on Wiki, hate to ask but can you post the link?
spacemonkey, I've tried those steps and it's still caught in the boot cycle.

You might want to explain how your phone got caught in the boot cycle to begin with. If it happened randomly, and you weren't trying to mod the phone, then just take it in for service. But somehow I doubt that's what happened. What were you doing? How come you don't have hard spl on there? What did you try to flash onto your phone, and how did you try to do it? These are all important questions that you should answer first before blindly flashing things to your phone.

The unit froze up. Tried to reboot the phone, it boot looped. Tried a hard reset, it continued to reboot.
It initially happened when a text message was coming in.
May just have to send it in. It doesn't want to take a flash of any kind it seems.

omegacell said:
The unit froze up. Tried to reboot the phone, it boot looped. Tried a hard reset, it continued to reboot.
It initially happened when a text message was coming in.
May just have to send it in. It doesn't want to take a flash of any kind it seems.
Click to expand...
Click to collapse
If it just crapped out on its own, then the last thing you want to do is try to fix it on your own (other than doing the obvious like hard resetting and pulling the battery). Just return it and get another.

Well it's not that easy since I'm in Canada and it has to go to AT&T so I thought if I could get it going it would save me a lot of hassle but it seems I have no choice!

Related

[Q] Can't access bootloader at all. Please help!

Hi guys
I've searched the forum for something like this but I'm coming up empty handed. But then again, I'm freaking out a bit.
I just tried flashing ARHD 9.7.0 and I've hit a big snag... For a bit of background, I was previously running ARHD 9.4.2 with the Endeavoru-Faux123-010b3 kernal. The battery was at 35% when I started the process...
I downloaded the zip, put it onto my SD card and rebooted into CWM. No worries there.
Did a wipe/factory reset and wiped the cache aswell. No worries there.
I did NOT flash the boot.img in the zip as I believed it would work okay with the current kernel (possibly the issue)
Went to install zip from SD card and chose the zip to install. AROMA starts up and I go through the familiar install process. No problem there.
I checked the reboot now option in AROMA and let it reboot. This is where the fun begins...
I get the beepy boopy start up sound and let it sit there because, as we all know, first boot can take a while. 10 minutes later, it's stuck at the HTC One splash screen. So I thought I'd reboot into CWM and start over like I've done with other ROM/kernal incompatibilities.
So I hold down the power button, let the three lights blink and the screen go blank and hold down the volume down button. And it goes back to attempting to boot up. I've tried different combinations of holding the buttons down and letting them go and hell, I've even sat there hammering the volume down button while it starts up! Still, I can't get into the bootloader.
Obviously, no bootloader, no ADB connection so I can't go through CMD and can't re-flash the kernel.
I'm currently sitting here looking at it. The USB cable is plugged in and the orange light is lit up so I hope it's charging. I'm at a loss here guys. Please, if anyone can give me some help, I will be most appreciative.
I'm really sorry to have wasted your time. It worked eventually after about 50 tries! :laugh:
Looks like it ws a kernel incompatibility.
But out of curiosity and for anybody else who gets this problem and really can't boot into the bootloader, what would be the steps involved in recovering a device in that state? I'd rather look like a knob in public as long as something constructive comes from it. :silly:
It's a bit tricky to get into hboot after a forced reboot, I think we've all been there
Just avoid the problem altogether by flashing the boot.img inside the zip first to make sure that it boots. Once up and running, flash your custom kernel and modules.
Try this http://forum.xda-developers.com/showthread.php?t=1734365
And don't let go when reboots keep hold of buttons and it should go to bootloader
Sent from my HTC One X using xda premium

VM Soft-Bricked...I know...

Well, guys was doing pretty well there for a second, I had just installed CarbonROM, was tweaking to my heart's content. Flashed a bad file in an attempt to improve speaker clairity, and boom stuck on the HTC boot logo.
Popped open the back, unplugged the battery, rebooted into HBOOT, rebooted into recovery and attempted to restore one of my backups I took right before flashing the bad zip. Failed. Can't load the data partition.
Ok, got the RUU file from this thread: http://forum.xda-developers.com/desire-816/general/ruu-htc-desire-816-a5chl-ruu-file-t2920254
Downloaded, put on root of SD card, renamed, rebooted to HBOOT, it picked it up, seemed to flash it, but it also seemed to go faster than it should. I'm suspecting it failed as well.
So now I've just got my phone sitting in recovery. Unable to mount the data partition.
Any clue on what I can do now? Hoping I haven't bricked this sucker...
Ok, my persistence paid off....Mods feel free to close this thread, I came up with a fix.
For anyone else in the same rut, this is how I fixed it...
Downloaded stock recovery from this link: https://drive.google.com/file/d/0B4NAwrQOaS7QVkxFYnhFZmhjOGc/view
Flashed stock recovery from Fastboot.
Loaded into stock recovery, key combo'd Volume UP + Power, got to the menu. Did a factory reset. Guess it reset partition mount points or something.
Rebooted to Fastboot, flashed TWRP, rebooted to recovery, restored a backup, and bam I'm back!
kenmoini said:
Ok, my persistence paid off....Mods feel free to close this thread, I came up with a fix.
For anyone else in the same rut, this is how I fixed it...
Downloaded stock recovery from this link: https://drive.google.com/file/d/0B4NAwrQOaS7QVkxFYnhFZmhjOGc/view
Flashed stock recovery from Fastboot.
Loaded into stock recovery, key combo'd Volume UP + Power, got to the menu. Did a factory reset. Guess it reset partition mount points or something.
Rebooted to Fastboot, flashed TWRP, rebooted to recovery, restored a backup, and bam I'm back!
Click to expand...
Click to collapse
Haha I had this same problem before, was ready to send my phone back. I was so scared and it wasn't working for like 3 days.
FoxyDrew said:
Haha I had this same problem before, was ready to send my phone back. I was so scared and it wasn't working for like 3 days.
Click to expand...
Click to collapse
Yeah, note to self, never get a phone without a removable battery. The sticky pads under the back cover while I was popping it off were annoying. Thankfully my phone was only down for a few hours.
kenmoini said:
Yeah, note to self, never get a phone without a removable battery. The sticky pads under the back cover while I was popping it off were annoying. Thankfully my phone was only down for a few hours.
Click to expand...
Click to collapse
This phone has a non-removable battery. You don't need to take out anything, all you do is hold volume up + the power button for 10 seconds or more. It will ALWAYS hard power off no matter what state the phone is in.
Also, what file did you flash over to improve the speaker clarity which broke your phone? I spoke to you about this earlier in my CarbonROM thread. I actually was able to fix the boomsound issue and there is no more crackling in my speakers. I'm going to post how to do it when I get home.
Edit: SORRY! Volume UP, not DOWN. Got mixed up
LiquidPlacidity said:
This phone has a non-removable battery. You don't need to take out anything, all you do is hold volume up + the power button for 10 seconds or more. It will ALWAYS hard power off no matter what state the phone is in.
Also, what file did you flash over to improve the speaker clarity which broke your phone? I spoke to you about this earlier in my CarbonROM thread. I actually was able to fix the boomsound issue and there is no more crackling in my speakers. I'm going to post how to do it when I get home.
Edit: SORRY! Volume UP, not DOWN. Got mixed up
Click to expand...
Click to collapse
I tried Vol Up/Down + Power for at least 30 seconds, was just stuck at HTC logo screen and I could feel the phone getting hotter so instead of having it run down the battery I decided to pop off the top. The back is meant to be non-removable but starting at the SD/SIM slot...slot, a guitar pick works great to undo the clips. Used a credit card to separate the sticky pads from the back. Pulled out the battery cable from the mainboard and reseated it, started it back up in HBOOT.
I flashed some sorta ZIP that's used with the HTC One M8 phones, figured if they have BoomSound it'd help too but noooope, haha. Can't remember what it was called. Did a lot of searching, tried Viper4Android, that sucked, tried tweaking the DSP, nothing came close to the original.
Sharing my own bricking experience
I'm a newbie, but I wanted to share my own experience from a few days ago. I bricked my VM/USA 816 when I was restoring a ROM backup of CM12 over a stock ROM. I was stuck on the CM12 blue "alien head" boot screen. I tried to get into the recovery screen by holding down power & volume, but it would only reboot and load CM12 again and not TWRP.
After a couple of hours of trying to get into recovery and deciding not to wait for the battery to drain because I thought the blue CM12 logo might burn into the screen. I decided to try to remove the cover and unplug the battery. I started at the SIM/SD Card slot trying to pop the cover off a little with a small screw driver to get a credit card(CC) between the cover and phone. Once I got it started I moved clockwise(cover side up) around with either a bent CC or a smaller cut up piece of CC to pop the tabs. I wasn't very gentle since I knew I wasn't going to return the phone and I bought the phone from VM with account balance so I didn't feel like I was really going to waste $300. Thank HTC the plastic cover is very forgiving. Once you get past the HTC logo you have to worry about the sticky tape around the bottom half of the phone where the battery is located. The bent CC was the best tool here and as I said earlier I wasn't very gentle while pulling off the cover once the tabs were loose.
Once I had the cover off I didn't know how to unplug the battery connector so I decided to pry the battery out. Once I did that I could see that the connecter pops up. I plugged the battery back in but the phone tried to load CM12 again. I don't remember if I had to press power button to turn on phone or it started when I connected the battery. I got back into the same state as before with a boot loop with no way getting back into recovery. So I unplugged battery again and connected the phone to my PC. I could see the screen the flashing between the charging screen and TWRP, but I couldn't get into recovery with buttons or screen touches. I then went into a command window on my PC to try the adb command. First I did a "adb devices" then I did a "adb reboot recovery" to get into TWRP. Once in TWRP I did an advanced wipe and installed CM12, gapps and supersu again from my ext SD Card. I'm not sure but I may have done a format of the internal storage just to be safe. Once I was up and running again I replaced the cover starting again clockwise from the SIM/SD Card corner and all the way around the phone till you get near the SIM/SD Card slot and have to replace the flap which is held in place by the cover/phone.
I hope this helps anyone who runs into the same problem.
kenmoini said:
Well, guys was doing pretty well there for a second, I had just installed CarbonROM, was tweaking to my heart's content. Flashed a bad file in an attempt to improve speaker clairity, and boom stuck on the HTC boot logo.
Popped open the back, unplugged the battery, rebooted into HBOOT, rebooted into recovery and attempted to restore one of my backups I took right before flashing the bad zip. Failed. Can't load the data partition.
Ok, got the RUU file from this thread: http://forum.xda-developers.com/desire-816/general/ruu-htc-desire-816-a5chl-ruu-file-t2920254
Downloaded, put on root of SD card, renamed, rebooted to HBOOT, it picked it up, seemed to flash it, but it also seemed to go faster than it should. I'm suspecting it failed as well.
So now I've just got my phone sitting in recovery. Unable to mount the data partition.
Any clue on what I can do now? Hoping I haven't bricked this sucker...
Click to expand...
Click to collapse
You have to flash and use CWM 6.0.5.1 and wipe the same partitions that were backed up in your STOCK nandroid backup.
Once you do this, reboot to hboot. Enter fastboot. Flash the stock recovery. Wipe the data/cache/dalvik. Reboot and go to hboot again. (Your device won't be able to boot yet.) Enter fastboot again.
Flash CWM (ONLY CWM) and make sure it flashes by flashing it twice back to back without leaving fastboot at any point.
Boot into recovery and once loaded reboot into hboot once more then go once again to fastboot and flash Philz Recovery with the same double flash process.
Now boot into it, mount as a USB and create a clockworkmod/backup folder on the device root directory since Philz Recovery doesn't use the buried part of the system like CWM.
Drag and drop your stock root nandroid backup. Use Philsz recovery to restore it. Boot up and your phone will boot after 3-5 minutes.
Flash back CM11/12 if you'd like.
Sent from my 710C using XDA Free mobile app
kenmoini said:
Ok, my persistence paid off....Mods feel free to close this thread, I came up with a fix.
For anyone else in the same rut, this is how I fixed it...
Downloaded stock recovery from this link: https://drive.google.com/file/d/0B4NAwrQOaS7QVkxFYnhFZmhjOGc/view
Flashed stock recovery from Fastboot.
Loaded into stock recovery, key combo'd Volume UP + Power, got to the menu. Did a factory reset. Guess it reset partition mount points or something.
Rebooted to Fastboot, flashed TWRP, rebooted to recovery, restored a backup, and bam I'm back!
Click to expand...
Click to collapse
Hello
Thank you for sharing your solution.
I have a problem which is described in this thread: http://forum.xda-developers.com/des...im-boots-fastboot-t3316255/page3#post65409302.
My questions to you:
1. My bootloader is locked. Is it possible to flash stock recovery on it?
2. I tried to flash official rom but I received the message "Partition update fail!". Can what you did, resolve this problem?

Samsung galaxy s2 sgh-t989 boot loop!

My daughter has this phone and she gave it to me to fix it was doing the same thing as stated in op kept rebooting on its own and would vibrae over an over , playing with the power button it would try to reboot sometimes it would get to the home screen but would rebot again i took the back piece off and cleaned around the power button and i would try to go into recovery but it kept rebooting, i kept trying and messing around with it and i got it to go into recovery and just enough time to clear cache brfote it robboted angian by itself still same thing, kept at it and got it to go into recovery again but i accidentally push update adb and it started to do what it does when you pushed that but i kept pressing power from a panic then i finally rebooted successful now im currently got it working its plugged into my computer it installed successfully but i don't see the storage on my computer, it does not have a sd card in it tho i have one to put in it and it does not have a sim card it it either tho i have the one my daughter gave me that she had to to her phone, i quickly turned on usb debuugging incase i need to odin firmware or something im not sure what do do from here so im asking any one that might know what i should do? If it was the power button i clean it as best as i can and aired it out too, im thinking this might tho do it again since im not sure what fixed it to this point except from what i did to it from what i wrote here. Please if anyone has any ideas out there so i can keep this thing fixed let me know in your replys TY!
mrdreamers said:
My daughter has this phone and she gave it to me to fix it was doing the same thing as stated in op kept rebooting on its own and would vibrae over an over , playing with the power button it would try to reboot sometimes it would get to the home screen but would rebot again i took the back piece off and cleaned around the power button and i would try to go into recovery but it kept rebooting, i kept trying and messing around with it and i got it to go into recovery and just enough time to clear cache brfote it robboted angian by itself still same thing, kept at it and got it to go into recovery again but i accidentally push update adb and it started to do what it does when you pushed that but i kept pressing power from a panic then i finally rebooted successful now im currently got it working its plugged into my computer it installed successfully but i don't see the storage on my computer, it does not have a sd card in it tho i have one to put in it and it does not have a sim card it it either tho i have the one my daughter gave me that she had to to her phone, i quickly turned on usb debuugging incase i need to odin firmware or something im not sure what do do from here so im asking any one that might know what i should do? If it was the power button i clean it as best as i can and aired it out too, im thinking this might tho do it again since im not sure what fixed it to this point except from what i did to it from what i wrote here. Please if anyone has any ideas out there so i can keep this thing fixed let me know in your replys TY!
Click to expand...
Click to collapse
First off, that's one hell of a long sentence!
Had you (or your daughter) recently installed a ROM and forgot to factory reset (clear all caches) the phone after doing so? Many at times, this is what causes boot loops. And you cleared cache, which I think has resolved the problem. However, MAKE A BACKUP on your phone (and onto your computer, just in case the phone hard-bricks) using your Recovery right away! Once you make the backup, there's no need to worry about whether you soft-brick your phone again; you can simply restore that backup. It's also highly possible that it was your power button, but since you said you did clean it up thoroughly, it might just be the cache preventing you from rebooting normally.
Either way, it's good to hear you got your phone working now. I would highly recommend that you make a backup before doing anything else with the phone - just to be on the safe side. Good luck!

Note 2 boot load loop fix - cause System Memory full

Hi everyone. This is the first time ive posted anything on here. I will try to fully describe my problem that i really need help to fix.
My wife got my old Note 2 is rooted and she got my
Dad's old unrooted Note 2. After deciding that she didnt want a rooted phone she decided to use my father's unrooted phone. Due to apps updating and the internal memory getting full she ingored the warning message not really realising the outcome. The phone eventually shut itself down and is stuck on the Samsung logo (boot loop). So i gave her my old rooted phone back because she said that it just died. The same happened to the rooted phone too.
I asked before what she did and i was told nothing it just died. So i had nothing to go on. It wasn't until a week later when I tried to sort the problem out she said the System Memory was getting full and a message came up warning of this. So now I believe the problem is that the on board memory has got full and the phone seized. Much like what happens to a PC when the main hard drive gets full!
When i attempt to boot the phone up the Samsung logo show and stays on, never booting up. This happens with both phones. When i hold the Home key, Power button and Up volume switch. The phone loads the first Part of the boot up and at the moment it goes to the system screen it goes blank for a split second and back to the start of the boot. No matter how many times i try it fails. So I can't Factory reset or erase anything because i can get to it that screen.
So I try something else. I press the Home button, Power button and the Down on the volume to access the Download mode. This works fine. So i used Odin to try to put Rom onto the phone hoping this will solve the problem. Both phones connects to Odin alright and I can set up ready to load a rom onto it, however when i press start on Odmin to do its job everthing starts ok but then it goes red with a Failed error message. This happens when i try this on both phones, I seem to be stuck no knowing what to do. I have tried using all the ports on my laptop (window 7) and that makes no difference. The same happens on both devices.
I think i need to clear the memory somehow but have no idea how to do it when i can only access Download mode. I would be very grateful for any help on this but if all else fail I will try to build up static on a ballon and see if putting the near will wipe the memory, lol. Only joking. Im desperate to sort this out.
Any ideas?
try to flash twrp with Odin and download mode. Then enter recovery, connect it to PC and make some space.
But I really doubt it, apps won't install even when you have 500Mb free, so I think it might be hardware problem

Z-Play boot loop, even after doing a factory reset

So I've had my Play for a while now, and it's been a lovely phone, no issues (until now), great device.
I was laid in bed last night and as I was feeling poorly I just wanted my phone off completely so I shut it down (power button -> Power Off). This morning I woke up (feeling better, thanks for asking) and turned my phone back on (held power button until the screen came on) and went about my morning routine. I came back to my phone a good 10 or so minutes later and noticed it was still booting, which I thought was strange, so I watched it and it would start loading and then turn off again and start booting up again. I did a bit of Googling and found very little (which is not surprising for a new phone) but I tried some of the X solutions, such as going into recovery mode (power+vol down) and clearing the cache (made no difference) and doing a factory reset (made no difference, soo glad I have backups). One of the things I noticed in the kernel logs is that the date is 01-01-1970: epoch. I have posted a 5 minute video of it booting, and scrolling through the logs on YouTube, but as a new user cannot post a link to it, the video's ID is xoCfPCB6Gmk
Any idea on how I might fix this, or is it a warranty job?
My advice would be go to the ROM section of these forums. Find the thread about the stock firmware. Then first find your region and download the stock firmware. Follow the instructions on how to flash that. If you're still not out of a boot loop then you want to put it in for warranty. Do not flash a custom firmware or root as that will void your warranty.
Awesome idea thanks.
I just gave it a go, and as my Play's SD card is encrypted (formatted as internal storage) I copied the image to a different SD card, then I thought about the enycryption and I tried booting it up normally with no SD card and it worked! So whetever the issue was, it was related to the encypted SD card.
Thanks for the inspiration, I hope this post helps someone else in the future!

Categories

Resources