Across multiple ROMs and daily hard-resets, the problem persists. After a certain point, the OS can no longer read/open files that are part of the ROM image. It can't, e.g., launch File Explorer. The Start menu is completely empty, etc.
At this point, if I soft reset, the phone gets stuck at the bootloader screen (i.e., listing the image version numbers in red text). If I hard reset, it works okay for a couple hours.
I didn't "do" anything to make this start. I switched back to the tilt after my Fuze was stolen, and it worked fine for a couple weeks before this all started.
Any advice? Things to test? I can get an mtty shell on it, but I don't know what commands there are, and I'd rather not brick my device.
Related
Hello All,
I have the TNT 1933 image loaded on my Cingular 8125 and have been running it fine for almost a month with little to no issues. The issues I had were minor kinks here and there but did not hinder the phone usage at all and has been working fine till up to this point. I was reading my e-mails via the exchange setup to my company exchange server and then closed out of it via the task manager and decided to soft reset it. I always soft reset during the morning just because I noticed there are memory leaks and soft-resetting normally resets the memory back to normal. After soft-resetting, it would hang at the Windows Mobile 6 Professional boot loader screen and will not continue. I even left it sitting there thinking it would load but I even let it sit while it drained the whole battery. I then plugged it into the charger and proceeded to soft reset it again and still does the same thing. Yes, I originally flashed it to the Tmobile rom before flashing the Tnt1933 image and yes its both unlocked (forgot the terminology). I tried taking the battery out for awhile thinking it would clear the memory or whatever and that didn't do anything. What I can do though is enter it into the bootloader mode with the 3 color screen but I do not want to reflash since I have important files that were not copied to my SD card. If there is a way for my PC to recognize my phone so I can at least copy the files I need, then I can reflash the OS again via the bootloader screen since I can get to that mode at least.
EDIT- Could this have been caused by the battery mem program overclocked at 247Mhz (the recommended for the 8125)? Since I never installed anything else except the main programs that were included in the image of the TNT 1933, the only thing I could think of was the extended overclock and overtime, corrupted the files from overclocking...just my 2 cents
lenell86 said:
Hello All,
I have the TNT 1933 image loaded on my Cingular 8125 and have been running it fine for almost a month with little to no issues. The issues I had were minor kinks here and there but did not hinder the phone usage at all and has been working fine till up to this point. I was reading my e-mails via the exchange setup to my company exchange server and then closed out of it via the task manager and decided to soft reset it. I always soft reset during the morning just because I noticed there are memory leaks and soft-resetting normally resets the memory back to normal. After soft-resetting, it would hang at the Windows Mobile 6 Professional boot loader screen and will not continue. I even left it sitting there thinking it would load but I even let it sit while it drained the whole battery. I then plugged it into the charger and proceeded to soft reset it again and still does the same thing. Yes, I originally flashed it to the Tmobile rom before flashing the Tnt1933 image and yes its both unlocked (forgot the terminology). I tried taking the battery out for awhile thinking it would clear the memory or whatever and that didn't do anything. What I can do though is enter it into the bootloader mode with the 3 color screen but I do not want to reflash since I have important files that were not copied to my SD card. If there is a way for my PC to recognize my phone so I can at least copy the files I need, then I can reflash the OS again via the bootloader screen since I can get to that mode at least.
EDIT- Could this have been caused by the battery mem program overclocked at 247Mhz (the recommended for the 8125)? Since I never installed anything else except the main programs that were included in the image of the TNT 1933, the only thing I could think of was the extended overclock and overtime, corrupted the files from overclocking...just my 2 cents
Click to expand...
Click to collapse
I highly doubt that batterystatus was what caused this because I have used batterystatus with every ROM I have ever used and have never had this problem.
As much as I hate to say this... As for your important files, you might as well kiss them goodbye because they're already gone. If your device will do nothing buy enter bootloader then the boot sequence on your phone is corrupt and you have no other choice, if you want your phone to work again, but to flash that T-Mobile ROM(or you can flash the 8125 official ROM found HERE.)
I know this isn't what you wanted to hear but you cannot connect to your device from activesync if you can only reach bootloader and nothing else and if the files are not on your storage card, they're gone.
Well, even if you were running Battery status, did you actually do an overclock or did u just leave it on default settings upon installing? OMG I'm gonna cry Those files are like my life I just want to understand how this happened when I installed nothing at all and it had been working fine for almost 4 weeks with no issues. Just went to hell after soft-resetting.
I had posted this in the stickied bootloader thread, but I'm pretty sure I posted to the wrong spot. If a mod wants to move this to another thread then by all means...
My kaiser is doing something I haven't heard of yet. Recently its started to act funny after 6 months of no new software, tinkering, flashing - nothing.
3 days ago I had to restart due to the sound cutting out and I got stopped at the bootloader. After fiddling with it, soft resetting multiple times, taking out the battery (just random low level troubleshooting) it booted into windows. This happened sporadically one or two more times.
I have also noticed that in the last 3 days the phone will suddenly drain to no battery without any warning. I will have 25% battery and be on a call for 20 minutes, then have the phone completely power off. normally, windows alerts me to high heaven with multiple warnings, etc. None - just powered off. After 30+ minutes of recharging in the off state, I powered on... bootloader again.
I hooked it into USB and sent the mtty "boot" command. This worked, it booted straight into windows. Due to my frequent sound problems I figured I'd load on a new radio "just in case" - so I loaded on the eMo radio via the sd card method, and soft reset. Again, bootloader. So I gave it the mtty BOOT command and got into windows... so far so good.
I soft reset just to see what would happen - bootloader.
Now I find myself having to soft reset frequently because the sound will just stop working at random. Of course when I soft reset I get bootloader but just today I found something very interesting: If I plug the phone into USB then simply soft reset it will restart and go right into loading windows. This works from inside windows as well as when I'm stuck at bootloader.
Is this common? My rom is Dutty's 6.1 from April 29. My radio is currently 1.71.09.01.emo. Thanks guys
*edit* now every time I hang up a phone call the earpiece starts making a "TV snow" or "power lines" kind of noise. This of course requires a soft reset which may or may not send me into bootloader. it varies.
I'm no flashing or rom expert by any means but if I were you, I would remove SD card, flash a different hardSPL other than what you're using now, flash a another cooked rom, and another radio. Starting from scratch sounds like the way to go. Good luck ...
I flashed a new SPL (3.29 fixed) and switched from dutty's to hyperdragon III Nov 6. I'm pretty sure this has fixed it.
The other day my TP hung after I ignored a call while using it tethered. I soft reset it, but now it only boots to the TouchPro screen with red lettering on the bottom. Even though I have Sprite, it has been awhile since I ran a backup, however most of my important data is on a SD card. I was able to get into the firmware update screen and there use TeraTerm to run info commands. However I was very disappointed to find out that all of the MFG commands, such as 'd2s', 's2d', 'r2sd' have been removed. Obviously using Sprite ever day would help (I still use Archie for SMS messages), however it seems odd to me that no one has a ROM reader for this phone. When it is flashed does it not do a read back verify? I figured a post here wouldn't hurt, as I have looked extensively everywhere else. Has anyone put the boot loader back to .25 which had the ROM to SD command? I understand HTC reasoning behind removing these commands, still it would be nice if there was a way of pulling an image that way. Maybe Sprite could add it in to their backup software? My next step will be to re-flash and in doing so wipeout any chance of recovering more of my data. With a Windows based OS, there really needs to be more recovery options than what we currently have.
J!
Hi,every time my phone switches off and I try and switch it back on it just goes straight to the fastboot screen. Pressing the reboot just brings me back here. Doing a factory reset does exactly the same thing, and does not reset. It has been doing it for a while now, and if i reboot enough times it eventually reboots normally, and functions fine until I run out of battery or something, then it takes ages to get it up and running again.
I haven't unlocked it in any way, it's completely stock. Htc are trying o get me to install an update, but as soon as it starts to install it switches off, and goes straight to the fastboot screen.
It's driving me mad, and is obviously just outside the warranty period.
Any help or advice on what to try would be much appreciated.
Cheers, Tom
I had the same problem a year ago but was still on warranty then, so I sent it in. When they returned it to me, there was no sign of them having opened up the phone so I guess it can be fixed software-side, but I'm not sure. You could probably try flashing a fitting RUU in fastboot and see if that fixes your problem (I guess that was what HTC has done when my device showed a similar behavior). Just be sure you're on the right version, as KitKat e.g. has a new partition layout and this could lead to problems with your phone not booting up properly.
Is your phone unbranded? What version are you currently on (Android, hboot)?
Okay,
I have a Gretel G1 (MT6580) here. I backed up the data and decided to flash it (like most cheap phones, it eventually got filled with Malware). So I followed the typical flashing procedure: Drivers, Flashtools, scatter, etc.
But this time, I was stupid enough to select "Format All + Download", so inevitably, it's not very usable right now.
Since then, and despite all the things I've tried (different drivers, versions, etc.) the phones been pretty much bricked. However, I did notice that the phone seems to be booting despite the display not showing much more than lines. I even unlocked the phone by trying the standard gesture (confirmed by the Android unlock sound effect).
I still seem to be able to flash the phone effectively, and access the non-system files normally (via file manager when the phone is on). I cannot however, get into system restore via the usual route (power and volume keys) or if I can, I can't tell if I'm in it due to the confused display.
I reckon I've probably removed an element that wasn't included in the needrom rom that makes the display stop working. Has anybody else got any ideas?